My Oracle Support Banner

BPM SOA-INFRA Not Started When DB Connect String Changed From Thin To Sqlnet Descriptor (Doc ID 2347235.1)

Last updated on JANUARY 08, 2024

Applies to:

Oracle Business Process Management Suite - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

On : 12.2.1.3.0 version, Orchestration Engine

BPM Soa-infra not started when db connect string changed from thin to sqlnet descriptor

When changing the db url from thin syntax to full sqlnet descriptor including a standby database, the soa-infra is not started
The connect string was changed in all datasources and files jps-config-jse.xml and jps-config.xml
The datasources are started correctly. When logging in to console and navigate to Home-> Datasource-> tab Monitoring, it can be seen that all datasources are up and running and test datasource action succeeds.
In soa_server1.out i see warning

Connect string is set to
jdbc:oracle:thin:@(DESCRIPTION_LIST=(LOAD_BALANCE=off)(FAILOVER=on)(DESCRIPTION=(ENABLE=BROKEN)(CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=host_name1)(PORT=port_number)))(CONNECT_DATA=(SERVICE_NAME=service_name)))(DESCRIPTION=(ENABLE=BROKEN)(CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=host_name2)(PORT=port_number)))(CONNECT_DATA=(SERVICE_NAME=service_name))))
 

ERROR
-----------------------
<Dec 4, 2017 11:37:35,837 AM CET> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "mds-soa": IO Error: The Network Adapter could not establish the connection.>
<Dec 4, 2017 11:37:35,841 AM CET> <Trace> <oracle.ucp.jdbc.oracle> <BEA-000000> <oracle.ucp.jdbc.oracle.RACManagerImpl:selectConnectionPerRCLBAndAffinity:oracle.ucp.jdbc.oracle.RACManagerImpl@7f20f2d7:Application has affinity context established>
<Dec 4, 2017 11:37:35,952 AM CET> <Warning> <oracle.mds> <BEA-000000> <MDS-01367: Failed to create PConfig. Invalid MDS configuration specified in: "soa-infra-store"
oracle.mds.persistence.MDSIOException: MDS-01376: Unable to get database connection from data source "mds-soa" configured with JNDI name "jdbc/mds/MDS_LocalTxDataSource".
java.sql.SQLException: java.lang.ClassCastException: java.lang.Boolean cannot be cast to oracle.ucp.jdbc.oracle.OracleConnectionAffinityContext
at oracle.mds.internal.persistence.db.JNDIConnectionManagerImpl.init(JNDIConnectionManagerImpl.java:250)
at oracle.mds.internal.persistence.db.ConnectionManagerFactory.createConnectionManager(ConnectionManagerFactory.java:72)
at oracle.mds.internal.persistence.db.DBStoreUtils.getConnectionManager(DBStoreUtils.java:564)
at oracle.mds.persistence.stores.db.DBMetadataStore.checkRepositoryCompatibility(DBMetadataStore.java:1126)
at oracle.mds.persistence.stores.db.DBMetadataStore.checkCompatibility(DBMetadataStore.java:1511)
at oracle.mds.persistence.stores.db.DBMetadataStore.<init>(DBMetadataStore.java:413)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at oracle.mds.persistence.MetadataStore.create(MetadataStore.java:350)
at oracle.mds.persistence.MetadataStore.create(MetadataStore.java:237)
at oracle.mds.persistence.MetadataStore.create(MetadataStore.java:206)
at oracle.mds.config.PConfig.getMetadataStore(PConfig.java:2179)
at oracle.mds.config.PConfig.getStoreForStoreUsage(PConfig.java:2123)
at oracle.mds.config.PConfig.loadFromBean(PConfig.java:1047)
at oracle.mds.config.PConfig.<init>(PConfig.java:892)
at oracle.mds.config.MDSConfig.loadFromBean(MDSConfig.java:1288)
at oracle.mds.config.MDSConfig.loadFromElement(MDSConfig.java:1360)
at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:905)
at oracle.mds.config.MDSConfig.<init>(MDSConfig.java:852)
at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:585)
at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:260)
at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:187)
at oracle.mds.lcm.weblogic.WLLifecycleListener.preStart(WLLifecycleListener.java:134)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

[....]

 

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.run(BaseLifecycleFlow.java:240)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:326)
at weblogic.security.service.SecurityManager.runAsForUserCode(SecurityManager.java:197)
at weblogic.application.internal.ApplicationContextImpl$WLSSecurityProvider.invokePrivilegedAction(ApplicationContextImpl.java:1594)
at weblogic.application.internal.flow.BaseLifecycleFlow$LifecycleListenerAction.invoke(BaseLifecycleFlow.java:201)
at weblogic.application.internal.flow.HeadLifecycleFlow.prepare(HeadLifecycleFlow.java:245)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:729)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:45)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:241)
at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:66)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:158)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:65)
at weblogic.deploy.internal.targetserver.AppDeployment.prepare(AppDeployment.java:166)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:41)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:193)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:31)
at weblogic.management.deploy.internal.ConfiguredDeployments$2.doItem(ConfiguredDeployments.java:741)
at weblogic.management.deploy.internal.parallel.BucketInvoker$2.run(BucketInvoker.java:95)
at weblogic.work.ContextWrap.run(ContextWrap.java:46)
at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:670)
at weblogic.invocation.ComponentInvocationContextManager._runAs(ComponentInvocationContextManager.java:352)
at weblogic.invocation.ComponentInvocationContextManager.runAs(ComponentInvocationContextManager.java:337)
at weblogic.work.LivePartitionUtility.doRunWorkUnderContext(LivePartitionUtility.java:57)
at weblogic.work.PartitionUtility.runWorkUnderContext(PartitionUtility.java:41)
at weblogic.work.SelfTuningWorkManagerImpl.runWorkUnderContext(SelfTuningWorkManagerImpl.java:644)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:415)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:355)
>





Changes

When changing below thin syntax or simple sqlnet descriptor string

jdbc:oracle:thin:@host_name1:port_number/service_name
jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=host_name1)(PORT=port_number)))(CONNECT_DATA=(SERVICE_NAME=service_name)))

 

Into

jdbc:oracle:thin:@(DESCRIPTION_LIST=(LOAD_BALANCE=off)(FAILOVER=on)(DESCRIPTION=(ENABLE=BROKEN)(CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=host_name1)(PORT=port_number)))(CONNECT_DATA=(SERVICE_NAME=service_name)))(DESCRIPTION=(ENABLE=BROKEN)(CONNECT_TIMEOUT=5)(TRANSPORT_CONNECT_TIMEOUT=3)(RETRY_COUNT=3)(ADDRESS_LIST=(LOAD_BALANCE=on)(ADDRESS=(PROTOCOL=TCP)(HOST=host_name2)(PORT=port_number)))(CONNECT_DATA=(SERVICE_NAME=service_name))))

 

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.