Offline analysis or simulation study
/opt/ccj/etc/odbc.ini.ccj.analysis indicates the latest version of the DB in CCJ
for the offline analysis and simulation study. This DB have been updated automatically
everyday. Please be in contact with phenix-ccj-admin in the case of you have some problems.
Accessing with PHENIX offline library
source /opt/phenix/bin/phenix_setup.csh
setenv ODBCINI /opt/ccj/etc/odbc.ini.ccj.analysis
Direct access to the PostgreSQL server
source /opt/phenix/bin/phenix_setup.csh
unsetenv PGHOST
setenv PGHOST ccjams002.riken.go.jp
setenv PGPORT 5432 or 5440
Please, refer to the current status page
to check the correspondig port number.
Data production
This DB server is permitted to access only for the phnxreco account. Users, who are not
related with the data productions, please do not use the following DB server.
/opt/ccj/etc/production/odbc/odbc.ini.ccj.prod.p is a link to the latest available version
of the DB in CCJ for the data production, and the link actually indicates odbc.ini.ccj.prod.a
or odbc.ini.ccj.prod.b. odbc.ini.ccj.prod.c is prepared for the recording of the BadEvents
information at the production. It will not be deleted before the end of productions and
will be transferred to the RCF. Each ODBC file corresponds to the following servers and
ports, respectively.
ODBC file
$PGHOST
$PGPORT (reading DB)
$PGPORT (recording BadEvents)
odbc.ini.ccj.prod.a
ccjams001.riken.go.jp
5432
5448
odbc.ini.ccj.prod.b
ccjams001.riken.go.jp
5440
5448
Therefore, you can access the latest version by setting as,
You can check the available DB version and the status of the restoration for each port by a script as,
/ccj/u/script/postgres/psql-status-prod.csh
If you want to update the DB source files, please type as
/ccj/u/script/postgres/psql-update-prod.csh
This script will check the DB source files stored in CCJ, and start to the restoration
process for the secondary port. For example, in the case of odbc.ini.ccj.prod.p indicates
odbc.ini.ccj.prod.a, a new DB will be restored for odbc.ini.ccj.prod.b and switch the link
of odbc.ini.ccj.prod.p to dbc.ini.ccj.prod.b after the restoration process was finished.
The restoration process takes about 6 hours. If you want to avoid the interference on
your already running/queued jobs from the restoration process, please set your ODBCINI as