After Clone Some Custom Managers Remains with Status Error System Hold, Fix Manager Before Resetting Counters (Doc ID 3024811.1)

Last updated on MAY 27, 2024

Applies to:

Symptoms

After cloning in the Concurrent manager Administration page we see for some custom managers with ERROR : System Hold, Fix Manager before resetting counters when the application is set to secondary node(xxxxxx02)

ERROR in the Concurrent manager Administration page
-----------------------
ERROR: System Hold, Fix Manager before resetting counters.

ICM log error

----------------------

Starting CustomManager  Concurrent Manager           
usdsop: exec failed during spawnrsh: No such file or directory

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Start the managers

2.Point the managers to the secondary node xxxxx02

3. Error appears

Changes

Cause

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