My Oracle Support Banner

ADOP Cutover Fails, Timeout While Starting Services On Secondary Node (Doc ID 2411800.1)

Last updated on SEPTEMBER 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!

Symptoms

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 ]

Changes

Performed normal adop patching, issued cutover.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.