ADOP Cutover Fails, Timeout While Starting Services On Secondary Node
Last updated on JUNE 20, 2018
Applies to:Oracle Applications DBA - Version 12.2.5 to 12.2.5 [Release 12.2]
Information in this document applies to any platform.
Other causes of CUTOVER are possible, review symptoms carefully. Raise a Service Request to verify if any doubt!
After applying a patch with adop: (prepare/apply/finalize), the cutover failed.
The services on primary node possibly up, but services down on the secondary node.
-> Confirm CUTOVER_STATUS past step 4 [ FS CUTOVER COMPLETED ]
Performed normal adop patching, issued cutover.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms