Introduction:
Managing EBS environments effectively requires attention to detail, especially after upgrades like AD-TXK 15. One critical aspect is ensuring password synchronization for seamless ADOP cycles.
Understanding the Issue :
After upgrading the AD-TXK components to version 15 in an Oracle EBS environment, running an ADOP cycle can fail if the passwords for the ebs_system and system database users are not identical. During the patching process, ADOP validates the database user credentials and relies on the ebs_system user, which serves as a proxy for the system user in specific operations.
If these passwords are not the same, the ADOP cycle fails with an error message resembling:
The ebs_system password and the system password should be the same.
Root Cause:
The root cause of this issue is a design requirement introduced with AD-TXK version 15. The ebs_system user must have the same password as the system user for compatibility with the ADOP framework. This is because the patching utilities use ebs_system as a proxy to perform privileged database operations, and a mismatch in credentials leads to authentication errors.
Resolution:
To resolve this issue, ensure that the passwords for the ebs_system and system database users are synchronized. Below are the steps:
Update the Password for ebs_system: Use SQL*Plus or a similar tool to update the password for the ebs_system user to match the system user:
ALTER USER ebs_system IDENTIFIED BY <system_password>;
Validate the Change: Test the connectivity for both system and ebs_system users:
sqlplus ebs_system/<password>@<DB_SID>
sqlplus system/<password>@<DB_SID>
Retry the ADOP Cycle: After synchronizing the passwords, rerun the ADOP command:
adop phase=fs_clone
The process should now proceed without errors.
Conclusion:
Synchronizing the ebs_system and system passwords is crucial for successful ADOP cycles post AD-TXK 15 upgrade. Ensure this alignment to avoid patching disruptions.
Thank you for visiting our blog!
