Database Error Messages

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

PRKO-02075

OC4J could not be removed

Cause

OC4J instance could not be removed because it does not exist.


Action

The current OC4J configuration can be checked using the command 'srvctl config oc4j'. Make sure that OC4J instance is running on that port. If there are other underlying messages printed then check the cause/action for the underlying errors shown with this.