Error In Data Source Creation While Performing An OSM 7.3.0.0.4 Installation In A Cluster Environment. (Doc ID 2220883.1)

Last updated on AUGUST 21, 2017

Applies to:

Oracle Communications Order and Service Management - Version 7.3.0.0.0 and later
Information in this document applies to any platform.

Symptoms

After installation of OSM 7.3.0.0.4  without a built-in Proxy Server and restarting the managed servers, the customer received the following JDBC DataSource errors


ERROR
-----------------------

com.mslv.oms.dataaccesslayer.ProxyException: java.lang.ExceptionInInitializerErrorNested Exception: java.lang.ExceptionInInitializerErrorNested Exception: java.lang.RuntimeException: java.lang.ExceptionInInitializerError
at com.mslv.oms.dataaccesslayer.AbstractProxy.execute(AbstractProxy.java:294)
at com.mslv.oms.poller.RuleEngineChecking.dbOperation(RuleEngineChecking.java:46)
at com.mslv.oms.poller.RuleEngineChecking.init(RuleEngineChecking.java:31)
at javax.servlet.GenericServlet.init(GenericServlet.java:240)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:337)
at weblogic.servlet.internal.StubSecurityHelper$ServletInitAction.run(StubSecurityHelper.java:288)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:120)


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Install OSM 7.3.0.0.4 in cluster  without built-in WebLogic Proxy Server.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot run OSM

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