Database Error Messages

Release
toggle
  • 23ai
  • 21c
  • 19c
Updated
Jun 24, 2024

PRKO-02090

OC4J could not be disabled

Cause

OC4J instance could not be disabled.


Action

Make sure that Node name is correct and that OC4J instance exists and is not already disabled. The current state of the OC4J instance can be found using the command 'srvctl status oc4j'. To check if OC4J instance is configured or not use the command 'srvctl config oc4j'.