ADOP Patch Fails, Status Shows as 'Not Started' on Secondary Nodes
(Doc ID 2951785.1)
Last updated on SEPTEMBER 11, 2024
Applies to:
Oracle Applications DBA - Version 12.2.4 and laterInformation in this document applies to any platform.
Symptoms
While applying any patch using Adop, it gets applied successfully on the primary node but the patch application is 'Not Started' on the secondary nodes.
The adop.log shows the below apply status for secondary node. No errors found.
ADOP patch should be completed successfully on the secondary node as well after applying it on primary node.
The issue can be reproduced at will with the following steps:
1. Run adop phase=prepare
2. adop phase=apply patches=<patch_no>
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 |