NTP configuration in Database servers caused issues
We know that NTP has to be configured in servers for time synchronization. So, in our production environment, we had done the time synch using NTP protocol in OAM, OID and DB servers. Earlier, the time was set manually in all the servers.
Though none of the other configurations were changed, the Oracle Internet Directory and OC4J services were not coming up properly. Some of the errors in all logs are given below:
Error1:
[gsdsiConnect] ORA-0,
Could not connect to the Database.
Error2:
oracle.security.sso.server.conf.ConfigurationException: Invalid SSO DB schema information
Error3:
Orion Launcher In class, DatabaseConfigReader: Could not get the DB connection
Wed Dec 29 12:46:12 IST 2010 [ERROR] Orion Launcher SSO Server initialization failed. Check the DB availability and restart SSO Server
Wed Dec 29 12:46:12 IST 2010 [ERROR] Orion Launcher Initializing the encryption/decryption objects failed
oracle.security.sso.server.conf.ConfigurationException: Invalid SSO DB schema information
Error4:
java.sql.SQLException: Listener refused the connection with the following error:
ORA-12514, TNS:listener does not currently know of service requested in connect descriptor
Resolution:
When the NTP configuration was removed from the DB servers, it started working fine. One more behavior seen after configuring NTP in DB servers is that db services were getting restarted unknowingly.
About the Author Mahendra
I am engulfed in Oracle Identity & Access Management domain. I have expertise on providing the optimized solutions for user provisioning, web access management, Single Sign-On and federation capabilities etc., I am also well versed with complex integrations within Identity Management and other product domains. I have expertise on building demos and implementation experience on products Oracle Access Manager, Oracle Adaptive Access Manager, Oracle Entitlement Server, Oracle Virtual Directory, Oracle Internet Directory etc., Look @ my blog: http://talkidentity.blogspot.com