Tuesday, October 6, 2015

UCM Login Page inaccessible due to database error


ISSUE:


After starting the UCM managed server, the UCM Login page is inaccessible and returns "Error 404--Not Found"
http://hostname:16200/cs

ERROR OBSERVED: 


Logs @ $DOMAIN_HOME/servers/ucm_server/logs/ucm_server.out
              $DOMAIN_HOME/servers/ucm_server/logs/ucm_diagnostics.log

<Error> <oracle.ucm.idccs> <UCM-CS-050021> <UCM Server failed to initialize inside its servlet environment.>
<Error> <oracle.ucm.idccs> <UCM-CS-000001> <general exception
intradoc.common.ServiceException: !csProviderUnableToInitialize,SystemDatabase
at intradoc.server.IdcSystemLoader.loadProviders(IdcSystemLoader.java:2379)
...
Caused By: intradoc.data.DataException: !csDbUnableToInitalize,SystemDatabase
!csProviderFailedToExtractAndUseDataSource,CSDS
at intradoc.jdbc.JdbcManager.init(JdbcManager.java:92)
at intradoc.jdbc.JdbcWorkspace.init(JdbcWorkspace.java:77)
at intradoc.provider.Provider.init(Provider.java:71)
...
Caused By: intradoc.data.DataException: !csProviderFailedToExtractAndUseDataSource,CSDS

at intradoc.provider.ProviderPoolManager.init(ProviderPoolManager.java:134)
at intradoc.jdbc.JdbcManager.init(JdbcManager.java:79)
at intradoc.jdbc.JdbcWorkspace.init(JdbcWorkspace.java:77)
at intradoc.provider.Provider.init(Provider.java:71)
...
Caused By: intradoc.common.ServiceException: !csProviderFailedToAccessDataSource
at intradoc.provider.ProviderPoolManager.computeExternalConnectionObject(ProviderPoolManager.java:263)
at intradoc.provider.ProviderPoolManager.init(ProviderPoolManager.java:130)
at intradoc.jdbc.JdbcManager.init(JdbcManager.java:79)
at intradoc.jdbc.JdbcWorkspace.init(JdbcWorkspace.java:77)
at intradoc.provider.Provider.init(Provider.java:71)
at intradoc.server.IdcSystemLoader.loadProviders(IdcSystemLoader.java:2369)
...
Caused By: intradoc.common.ServiceException: !csUnableToExecMethod,getConnection
at intradoc.common.ClassHelperUtils.convertToStandardException(ClassHelperUtils.java:202)
at intradoc.common.ClassHelperUtils.convertToStandardExceptionAndThrow(ClassHelperUtils.java:179)
...
Caused By: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection. The DBMS driver exception was: IO Error: Socket read timed out


SOLUTION:


  • CSDS is the name of data-source which is used to connect Database and UCM Server.
  • The CSDS data source connection pool could not be constructed because the default timeout to construct a database connection was set too low (oracle.net.CONNECT_TIMEOUT=10000)
  • Increase the database connection timeout by setting "oracle.net.CONNECT_TIMEOUT=20000" in the CSDS connection pool properties as below.

Step 1) Open the WebLogic Server Console

Step 2) Click Lock & Edit

Step 3) Navigate to Services -> Data Sources

Step 4) Click on the "CSDS" data source

Step 5) Navigate to the Configuration -->Connection Pool tab

Step 6) In the Properties box, change 

OLD:
oracle.net.CONNECT_TIMEOUT=10000

NEW:
oracle.net.CONNECT_TIMEOUT=20000

Step 7) Click Save

Step 8) Click Activate Changes.

Step 9) Restart the ucm_server instance and verify that there are no more errors during the startup

Step 10) Confirm that the login page (http://hostname:16200/cs) is accessible.

No comments:

Post a Comment

Other Posts