Oracle DB connection errors seen in the Policy server and System logger logs (Doc ID 1623014.1)

Last updated on OCTOBER 22, 2016

Applies to:

Oracle Communications IP Service Activator - Version 7.2.0 and later
Information in this document applies to any platform.

Symptoms

The following Errors were detected in the Policy Server and System logs when trying to connect to the IPSA DB server.

The collection of log snips below from the policy server and system logger all indicate Oracle DB connection problems. Please ensure that sql and listener process are all running on the DB server before starting IPSA.


From the policy_server.log

Policy server ORA errors indicating loss of communications with the DB.

20140205-194320|0010|INF2|Transaction 20140205192808 TIMEDOUT.
20140205-194332|000b|INF1|CTable: Execute failed: ORA-03135: connection lost contact

20140205-194340|0001|INF1|CDatabaseSA: Rollback failed: ORA-03114: not connected to ORACLE
...............|....|....| Native Code: 3114
20140205-194340|0001|INF1|CDatabaseSA: Close failed: ORA-03114: not connected to ORACLE
...............|....|....| Native Code: 3114

20140205-194347|0001|INF1|CDatabaseSA: OpenEx failed: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
...............|....|....| Native Code: 12514
20140205-194347|0001|INF1|CLogSinkSA: Open database failed: Reason: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
...............|....|....|. Native Code: 12514


20140206-050557|000b|INF1|CTable: Execute failed: ORA-03113: end-of-file on communication channel
...............|....|....|Process ID: 3195
...............|....|....|Session ID: 474 Serial number: 9
...............|....|....|. Statement: select "Id" from "SptSystemUser" where "Id"=:1. Position: 0. Native Code: 3113
20140206-050557|000b|CRT0|OSLogger: Policy Server: Modify operation on database failed: CSptSystemUser:pal_cm_super:6000339ORA-03113: end-of-file on communication channel
...............|....|....|Process ID: 3195
...............|....|....|Session ID: 474 Serial number: 9


20140206-050710|0001|INF1|CDatabaseSA: OpenEx failed: ORA-12170: TNS:Connect timeout occurred
...............|....|....| Native Code: 12170
20140206-050710|0001|INF1|CLogSinkSA: Open database failed: Reason: ORA-12170: TNS:Connect timeout occurred
...............|....|....|. Native Code: 12170

 

From the system_log.log

System logger showing its DB connection failure and associated ORA messages.

20140205-194332|000b|INF1|CTable: Execute failed: ORA-03135: connection lost contact
...............|....|....|Process ID: 15688
...............|....|....|Session ID: 458 Serial number: 23
...............|....|....|. Statement: insert into "SptSystemMessageLog" values(:1,:2,:3,:4,:5,:6,:7, :8, :9, :10, :11, :12, :13). Position: 0. Native Code: 3135
20140205-194332|000b|INF1|SqlApiDb::Save: failed. Reason: ORA-03135: connection lost contact
...............|....|....|Process ID: 15688
...............|....|....|Session ID: 458 Serial number: 23
...............|....|....|
20140205-194332|000b|INF1|CDatabaseSA: Rollback failed: ORA-03114: not connected to ORACLE
...............|....|....| Native Code: 3114
20140205-194332|000b|DBG4|System exception caught in ProcessSysLogMsgs thread: thread exited

 The following may also be seen when starting IPSA and is directly caused by incorrect login credentials to the Oracle data base.  This can also be caused by an incorrect serial number so be aware of these parameters when inputting to the configGui.  They can be re-checked by doing a validation of the configGui.

...............|....|....|Copyright � 1997, 2011, Oracle and/or its affiliates. All rights reserved.
20150509-043159|0001|INF2|Created Server Component object
20150509-043159|0001|INF2|CDbFactory database connection found: OCI;DSN=IPServiceActivatorDb;UID=ipsaadm;PWD=ipSadm07
20150509-043159|0001|INF2|ParseConnection: ;DSN=IPServiceActivatorDb;UID=ipsaadm;PWD=ipSadm07 -> ;DSN=IPServiceActivatorDb;UID=ipsaadm;PWD=ipSadm07
20150509-043159|0001|INF2|ParseConnection: ;DSN=IPServiceActivatorDb;UID=ipsaadm;PWD=ipSadm07 -> ;DSN=IPServiceActivatorDb;UID=ipsaadm;PWD=ipSadm07
20150509-043852|0001|INF2|The policy server version is different than the version in the database.
20150509-050319|0001|CRT0|OSLogger: Policy Server: Opening database and table read failed: ORA-03113: end-of-file on communication channel
...............|....|....|
20150509-050319|0001|INF1|CDatabaseSA: Rollback failed: ORA-03114: not connected to ORACLE
...............|....|....| Native Code: 3114
20150509-050319|0001|INF1|CDatabaseSA: Close failed: ORA-03114: not connected to ORACLE
...............|....|....| Native Code: 3114
20150509-050325|0001|CRT0|Failed to initialise Object Model. Reason:<Exception type="ServerException" reason="Failed to read object model from database. Check your ConnectString. For an Oracle database, ensure the UID and PWD are specified in the correct case. For an Access database, ensure that the UID and PWD are not specified." detail="file:/ade/builder_IPSA.R5_3_0.150402.0603.B837_SPRO64/OSA/tornado/policy_server/PolicyServer.cpp,line:437,errno:9"/>

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms