My Oracle Support Banner

Billing Operations Center Not Working Without IDM (Doc ID 2455211.1)

Last updated on SEPTEMBER 01, 2020

Applies to:

Oracle Communications Billing and Revenue Management - Version 12.0.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.0.0.0.0 version, Billing Operations Center

Steps:
Installed Billing Operations Center on Billing and Revenue Management (BRM) 12.0.0.0 in testing mode without Identity Manager(IDM). After followed the installation guide and when installation was complete, got an exception in the log that the authorization was not complete.

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

at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder$11.run(JMXConnectorSubjectForwarder.java:653)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
at weblogic.management.mbeanservers.internal.JMXConnectorSubjectForwarder.invoke(JMXConnectorSubjectForwarder.java:646)
at javax.management.remote.rmi.RMIConnectionImpl.doOperation(RMIConnectionImpl.java:1468)
at javax.management.remote.rmi.RMIConnectionImpl.access$300(RMIConnectionImpl.java:76)
at javax.management.remote.rmi.RMIConnectionImpl$PrivilegedOperation.run(RMIConnectionImpl.java:1309)
at java.security.AccessController.doPrivileged(Native Method)
at javax.management.remote.rmi.RMIConnectionImpl.doPrivilegedOperation(RMIConnectionImpl.java:1408)
at javax.management.remote.rmi.RMIConnectionImpl.invoke(RMIConnectionImpl.java:829)
at javax.management.remote.rmi.RMIConnectionImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:252)
... 88 more
Caused by: weblogic.jdbc.extensions.ConnectionDeadSQLException: weblogic.common.resourcepool.ResourceDeadException: 0:weblogic.common.ResourceException: Could not create pool connection for datasource 'LocalSvcTblDataSource'. The DBMS driver exception was: IO Error: The Network Adapter could not establish the connection
at weblogic.jdbc.common.internal.JDBCUtil.wrapAndThrowResourceException(JDBCUtil.java:268)
at weblogic.jdbc.common.internal.RmiDataSource.getPoolConnection(RmiDataSource.java:529)
at weblogic.jdbc.common.internal.RmiDataSource.getConnectionInternal(RmiDataSource.java:620)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:571)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:564)
at com.oracle.cie.servicetable.impl.ServiceTableImpl.getOnlineLocalSvcTblConnection(ServiceTableImpl.java:178)
at com.oracle.cie.servicetable.impl.ServiceTableImpl.getOnlineLocalServiceTableConnection(ServiceTableImpl.java:98)
... 155 more
, Policy Manager User Configuration:, OWSM Policy Manager connection cannot be established.]};
]]
[2018-09-24T11:02:46.558-07:00] [AdminServer] [NOTIFICATION] [JPS-10628] [oracle.jps.policymgmt] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 6dc20e06-bcf9-4714-a3de-20afd8c84e55-00000158,0] [partition-name: DOMAIN] [tenant-name: GLOBAL] Retry getApplicationPolicyChangeLog for the 3 times.
[2018-09-24T11:03:01.559-07:00] [AdminServer] [ERROR] [JPS-10603] [oracle.jps.policymgmt] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 6dc20e06-bcf9-4714-a3de-20afd8c84e55-00000158,0] [partition-name: DOMAIN] [tenant-name: GLOBAL] FAILURE: Retry getApplicationPolicyChangeLog failed after 3 times retries due to following exception oracle.security.jps.service.policystore.PolicyStoreConnectivityException: JPS-00027: There was an internal error: weblogic.jdbc.extensions.PoolDisabledSQLException: weblogic.common.resourcepool.ResourceDisabledException: Pool opss-data-source is Suspended, cannot allocate resources to applications...
Error in executing SQL script /opt/ri-user-1/opt/portal/BOC/scripts/schema/brm_grant.sql
Exception severity: 1
2018-09-21 06:57:52,334 INFO [92] oracle.sysman.oii.oiic.OiicAPISessionInterfaceManager - Retry Handler not registered, using Super class functionality
2018-09-21 06:57:52,336 OFF [92] oracle.sysman.oii.oiio.oiiol.OiiolTextLogger - Error in executing SQL script /opt/ri-user-1/opt/portal/BOC/scripts/schema/brm_grant.sql
2018-09-21 06:57:52,336 INFO [92] oracle.sysman.oii.oiis.OiisCompActions - Exception handling set to prompt user with options to Retry Ignore
[2018-09-20T23:51:03.404-07:00] [AdminServer] [NOTIFICATION] [] [oracle.wsm.diagnostic.logger.DiagnosticLogger] [tid: [ACTIVE].ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: 29f0efa2-381e-42c4-aeb4-6cc292578493-00000040,0] [APP: bi-security] [partition-name: DOMAIN] [tenant-name: GLOBAL] <Tracking Id:29f0efa2-381e-42c4-aeb4-6cc292578493-00000040,0#1537512656544> <Partition:DOMAIN> <agent> <PM Communication Failure> Diagnosis:wsm-pm:FAILED:[OWSM Policy Manager connection URL is "2"., oracle.wsm.policymanager.PolicyManagerException: WSM-02141 : Unable to connect to the policy access service due to Oracle WSM policy manager host server being down., Policy Manager Per Url Health:, Policy Manager Access status on URL "t3://<IP ADD>:7001" is "FAILED"., Policy Manager Access status on URL "t3://localhost:7502" is "FAILED"., Policy Manager Url Configuration:, Policy Manager Url in Service Table is "t3://<IP ADD>:7001,localhost:7502"., Policy Manager Url in runtime is "t3://<IP ADD>:7001,localhost:7502", Policy Manager Url publishing status to Service Table is "Published"., Policy Manager Url is "WIRED" succesfully with agent., Policy Manager User Configuration:, OWSM Policy Manager connection cannot be established.];agent:FAILED:[Enforcement has failed., Service URL: http://localhost:7502/wsm-pm-diagnostic/DiagnosticService?wsdl, Could not determine wsdl ports. WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at: "http://localhost:-diagnostic/DiagnosticService?wsdl", caused by: java.net.ConnectException.: java.net.ConnectException: Connection refused (Connection refused), Enforcement has failed., Service URL: http://<IP ADD>:7001/wsm-pm-diagnostic/DiagnosticService?wsdl, Could not determine wsdl ports. WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at: "http:///c/DiagnosticService?wsdl", caused by: java.net.ConnectException.: java.net.ConnectException: Connection refused (Connection refused)]; Root Cause:oracle.wsm.policymanager.PolicyManagerException: WSM-02141 : Unable to connect to the policy access service due to Oracle WSM policy manager host server being down.;[[
Verbose:{agent=[Enforcement has failed., Service URL: http://localhost:7502/wsm-pm-diagnostic/DiagnosticService?wsdl, javax.xml.ws.WebServiceException: Could not determine wsdl ports. WSDLException: faultCode=PARSER_ERROR: Failed to read wsdl file at: "http://localhost:7502/wsm-pm-diagnostic/DiagnosticService?wsdl", caused by: java.net.ConnectException.: java.net.ConnectException: Connection refused (Connection refused)
at oracle.j2ee.ws.common.jaxws.WSDLMetadata.initPorts(WSDLMetadata.java:174)








Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.