AutoPatch error: The worker should not have status ‘Running’ or ‘Restarted’ at this point.

ERROR:

R12.2 ADOP:

AutoPatch error:
The worker should not have status ‘Running’ or ‘Restarted’ at this point.

CAUSE:

SOLUTION:

Step 1: Launch Adctrl and check the status of the workers. Are the workers currently running or have they been started?

Select the following options in Adctrl: 
   Option 1 to Show Worker Status then
   Option 4 to Tell manager that a worker failed its job

Step 2. Restart the ADOP patch from the following given OPTIONS.

• If you wish to restart a failed patch from the beginning, specify the following option

• If you wish to restart a failed patch from where it left off, simply specify the following option

adop phase=apply patches=<Patch_Number> restart=yes abandon=no

OPMNCTL startall Fails with unexpected exit: status 4200

FIX:

Once the new wallet is in place, OPMN and OHS should be able to initiate successfully.

To verify the startup of only OPMN and OHS, you can utilize the commands adopmnctl.sh start and adapcctl.sh start.

Alternatively, you have the option to execute adstrtal.sh, which will attempt to start all components simultaneously.

Steps to change password for APPS in EBS R12.2

Today, we will delve into the process of changing the EBS APPS password in Oracle E-Business Suite R12.2. While this is a routine and fundamental task for every appsdba, it is essential to perform the steps cautiously to avoid any potential risks or unforeseen complications.

What is the Apps Schema?

The Apps schema refers to a schema that does not contain any tables of its own. It serves as the shared runtime schema for all E-Business Suite products. It includes synonyms for all tables in Oracle apps and also consists of packages, functions, and procedures. The default password for this schema is “apps.”

What is the Applsys Schema?

The Applsys schema comprises all the necessary tables for administrative purposes. The default password for this schema is also “apps.” It consolidates the database objects of various technical products into a single schema called Applsys.

What is the Applsyspub Schema?

The Applsyspub schema primarily handles password checking. Its default password is “pub.” Applsyspub is utilized for authentication through read-only views.

Why should the Apps and Applsys passwords always be the same?

The requirement for having the same password for both the Apps and Applsys schemas is due to the authentication process. When signing on to Apps, it initially connects to a public schema named APPLSYSPUB. This schema validates the AOL username and password entered, typically using the guest user account (operations/welcome). Once this authentication is confirmed, selecting a responsibility triggers validation by the APPLSYS schema, followed by the connection to the APPS schema.

Step 7: Modifying the Password in WebLogic

A) If your EBS R12.2 AD TXK Delta is 7 or higher, you should follow the subsequent steps.

[applmgr@ebslive scripts] $perl $FND_TOP/patch/115/bin/txkManageDBConnectionPool.pl
Please select from list of valid options
        updateDSPassword - Update WebLogic Datasource Password
        updateDSJdbcUrl  - Update WebLogic Datasource Connection String
Enter Your Choice : updateDSPassword
Enter the full path of Applications Context File [DEFAULT -]:
Enter weblogic admin server password: <enter Weblogic Password>
Enter the APPS user password: <enter New APPS Password>

B) If your EBS R12.2 AD TXK Delta is lower than 7, you should utilize the following steps.

1. Access the WebLogic console through a web browser.
2. Click on the “Lock and Edit” button.
3. Navigate to the “Domain structure” section and select “Services” -> “Data Sources.”
4. Locate and select the “EBSDataSource” entry.
5. In the “Settings of EBSDataSource” page, go to the connection pool section.
6. Enter the updated password for the apps user and save the changes.
7. Finally, click on “Activate changes” to apply the modifications.

Step 8 . Start the application services.

[applmgr@ebslive appl]$ pwd

  /u01/app/PROD/fs2/EBSapps/appl

[applmgr@ebslive appl]$ adstrtal.sh

 You are running adstrtal.sh version 120.24.12020000.6

 Enter the APPS username: apps 

 Enter the APPS password:

 Enter the WebLogic Server password:

 All enabled services for this node are started.

 adstrtal.sh: Exiting with status 0

Step 9: Validate WLS Datastore Modifications by Following These Steps

1. Access the WLS Administration Console and log in.
2. In the Domain Structure tree, expand the “Services” section, then choose “Data Sources.”
3. Locate and select “EBSDataSource” on the “Summary of JDBC Data Sources” page.
4. Navigate to the “Settings for EBSDataSource” page and select “Monitoring” followed by “Testing.”
5. Select “oacore_server1” from the available options.
6. Click on “Test DataSource.”
7. Look for the confirmation message stating “Test of EBSDataSource on server oacore_server1 was successful.”
8. If Integrated SOA Gateway (ISG) is implemented, repeat the steps for “OAEADataSource”. Verify “oafm_cluster*” managed servers are started successfully.