CMDTUX_CAT:1685:
ERROR: Application initialization failure
TUXLOG.MMDDYY:
TUXLOG.MMDDYY:
090957.machine!PSAPPSRV.4292.4296.0:
LIBTUX_CAT:250: ERROR: tpsvrinit() failed
090957.machine!tmboot.4140.4144.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
090957.machine!tmboot.4140.4144.-2: tmboot: CMDTUX_CAT:827: ERROR: Fatal error encountered; initiating user error handler
APPSRV_MMDD.LOG:
PSAPPSRV.4292
(0) [12/16/08 09:09:57](3) File: SQL Access ManagerSQL error. Stmt #: 2 Error
Position: 0 Return: 12560 - ORA-12560: TNS:protocol adapter error
PSAPPSRV.4292 (0) [12/16/08 09:09:57](1) GenMessageBox(200, 0, M): SQL Access Manager: File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 12560 - ORA-12560: TNS:protocol adapter error
PSAPPSRV.4292 (0) [12/16/08 09:09:57](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database PORTAL90 with user VP1.
PSAPPSRV.4292 (0) [12/16/08 09:09:57](1) GenMessageBox(200, 0, M): SQL Access Manager: File: SQL Access ManagerSQL error. Stmt #: 2 Error Position: 0 Return: 12560 - ORA-12560: TNS:protocol adapter error
PSAPPSRV.4292 (0) [12/16/08 09:09:57](1) GenMessageBox(0, 0, M): Database Signon: Could not sign on to database PORTAL90 with user VP1.
The
configuration file psappsrv.cfg for the application server has a section
Database Options, and in that section there is a parameter UseLocalOracleDB.
Possible settings are 0 (off / default value) and 1 (on).
This parameter is used to determine how to connect to the Oracle database. The parameter had been set to '1' and so the domain was looking to the ORACLE_SID at boot time. The problem was that the ORACLE_SID had not been set in the psappsrv.cfg file which will cause the connection to Oracle to fail. Make sure you set the ORACLE_SID in the psappsrv.cfg file and also uncomment this value out if you choose to use UseLocalOracleDB=1.
A value of UseLocalOracleDB=0 will cause the domain to read the tnsnames.ora when it tries to connect to the Oracle database.
A value of '1' is appropriate only if the database and application server reside on the same machine. Using a value of UseLocalOracleDB=1 should boot the domain faster since it uses a local connection to attach to Oracle. This setting also pertains to the process scheduler.
This parameter is used to determine how to connect to the Oracle database. The parameter had been set to '1' and so the domain was looking to the ORACLE_SID at boot time. The problem was that the ORACLE_SID had not been set in the psappsrv.cfg file which will cause the connection to Oracle to fail. Make sure you set the ORACLE_SID in the psappsrv.cfg file and also uncomment this value out if you choose to use UseLocalOracleDB=1.
A value of UseLocalOracleDB=0 will cause the domain to read the tnsnames.ora when it tries to connect to the Oracle database.
A value of '1' is appropriate only if the database and application server reside on the same machine. Using a value of UseLocalOracleDB=1 should boot the domain faster since it uses a local connection to attach to Oracle. This setting also pertains to the process scheduler.
