The most common cause is an unsynced or corrupted opmn.xml file. This XML file is the brain of OPMN. It lists every component OPMN is supposed to manage.
If you are using a stateful orchestrator (like Terraform), run a refresh:
Ensure the srvctl binary you are using belongs to the correct Grid Infrastructure or Database home. How to Fix PRCR-1001 prcr-1001 resource does not exist
If the resource exists via the native tool but not via the controller, you likely have a permission or state mismatch. If it doesn't exist anywhere, you need to recreate it.
Did this happen after an ?
Restart the Oracle High Availability Services (OHAS) on the affected node.
If you believe this resource is critical and should exist, please open a support ticket with the following information: The most common cause is an unsynced or corrupted opmn
Are you working on a environment or Restart (Standalone) ?