After adcfgclone on Rel 12.2, managed servers were starting in “admin” mode

The Node Manager is already up.

ERROR: Unable to start up the managed server oacore_server1

ERROR: Unable to start up the managed server oacore_server3

Server specific logs are located at /u01/install/APPS/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/oacore_server1/logs

11/02/22-09:07:49 :: admanagedsrvctl.sh: exiting with status 1

================================================================================

Server specific logs are located at /u01/install/APPS/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/oacore_server3/logs

11/02/22-09:07:49 :: admanagedsrvctl.sh: exiting with status 1

================================================================================

ERROR: Unable to start up the managed server oacore_server2

Server specific logs are located at /u01/install/APPS/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/oacore_server2/logs

11/02/22-09:07:50 :: admanagedsrvctl.sh: exiting with status 1

================================================================================

ERROR: Unable to start up the managed server oacore_server4

Server specific logs are located at /u01/install/APPS/fs2/FMW_Home/user_projects/domains/EBS_domain/servers/oacore_server4/logs

11/02/22-09:07:52 :: admanagedsrvctl.sh: exiting with status 1

================================================================================

After creating a new EBS instance using Rapidclone, managed servers such as oacore_server2/oacore_server3/oacore_server4 and forms_server1 fail to start and their status on WLS console are not “RUNNING” but “ADMIN” while oafm_server1 is “RUNNING”.

ORA-01017 is shown in the log files of oacore_server1 and forms_server1 as follows.

###<Nov 26, 2021 11:45:44 AM JST> <Error> <Deployer> <hostname.domain> <oacore_server1> <[ACTIVE] ExecuteThread: ‘0’ for queue: ‘weblogic.kernel.Default (self-tuning)’> <<WLS Kernel>> <> <> <1637894744672> <BEA-149205> <Failed to initialize the application ‘EBSDataSource’ due to error weblogic.application.ModuleException:
at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:327)
at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:199)
at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:517)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:159)
at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:45)
at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:648)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:52)
at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191)
at weblogic.application.internal.SingleModuleDeployment.prepare(SingleModuleDeployment.java:44)
at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:154)
at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61)
at weblogic.deploy.internal.targetserver.SystemResourceDeployment.prepare(SystemResourceDeployment.java:55)
at weblogic.management.deploy.internal.DeploymentAdapter$1.doPrepare(DeploymentAdapter.java:39)
at weblogic.management.deploy.internal.DeploymentAdapter.prepare(DeploymentAdapter.java:191)
at weblogic.management.deploy.internal.AppTransition$1.transitionApp(AppTransition.java:21)
at weblogic.management.deploy.internal.ConfiguredDeployments.transitionApps(ConfiguredDeployments.java:240)
at weblogic.management.deploy.internal.ConfiguredDeployments.prepare(ConfiguredDeployments.java:165)
at weblogic.management.deploy.internal.ConfiguredDeployments.deploy(ConfiguredDeployments.java:122)
at weblogic.management.deploy.internal.DeploymentServerService.resume(DeploymentServerService.java:180)
at weblogic.management.deploy.internal.DeploymentServerService.start(DeploymentServerService.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:263)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
Caused By: weblogic.common.resourcepool.ResourceSystemException:
Could not connect to ‘oracle.jdbc.OracleDriver’.

The returned message is: ORA-01017: invalid username/password; logon denied

It is likely that the login or password is not valid.
It is also possible that something else is invalid in
the configuration or that the database is not available.
at weblogic.jdbc.common.internal.JDBCUtil.parseException(JDBCUtil.java:301)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:383)
at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:241)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1322)
at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1239)
at weblogic.common.resourcepool.ResourcePoolImpl.start(ResourcePoolImpl.java:250)The


The customer confirmed followings.

  – The initial parameter SEC_CASE_SENSITIVE_LOGON is set to FALSE.
  – They can connect to Database using sqlplus by password both in upper and lower case.

Solution

Reset the password of EBSDataSource as follows.

(1) Login to WLS Console and proceed as follows.

      Domain Structure > Services > Data Sources > EBSDataSource > Configuration TAB > Connection Pool Sub-TAB

(2) Push “Lock & Edit” button in Change Center.
     Then set APPS schema’s password for “Password” & “Confirm Password” fields and push “Save” button.

(3) Push “Activate Chang” button in Change Center.

(4) Stop oacore_server1 and forms_server1 as follows.

$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh stop oacore_server2
$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh stop oacore_server3
$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh stop oacore_server4
$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh stop forms_server1


(5) Start  oacore_server1 and forms_server1 as follows.

$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start oacore_server2
$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start oacore_server3
$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start oacore_server4
$ADMIN_SCRIPTS_HOME/admanagedsrvctl.sh start forms_server1


(6) Check if the status of “oacore_server1” and “forms_server1” has been changed to “RUNNING”.

Reference: Status of “oacore_server1” And “forms_sever1” Is “ADMIN” Not “RUNNING” on EBS Created by Rapidclone (Doc ID 2824612.1)

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s