After Step 6.2.7 in Note 1070033.1, Internal Monitor Couldn't Be Started (Doc ID 2064992.1)

Last updated on OCTOBER 12, 2015

Applies to:

Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
Information in this document applies to any platform.

Symptoms

Following <Note 1070033.1>, after run 6.2.7 complete the database configuration step successfully, the Internal Monitor of Standby environment couldn't be started because the work shift of Internal Monitor was gone.

Changes

Execute the following SQL:

SQL>exec fnd_net_services.remove_system(<SID>);
SQL>commit;
SQL>exec fnd_conc_clone.setup_clean;

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms