OCI-00625
internal error code within PDB: (string)(string)(string)(string)(string)(string)(string)(string)(string)(string)(string)(string)
Cause
This is a generic PDB-specific internal error number for Oracle program exceptions. It indicates that a process encountered an unexpected condition within the PDB that led to the closing of the PDB. The first argument in the message is the internal message. This argument and the database version number are critical in identifying the root cause and the potential impact. to your system.
Action
Visit My Oracle Support to access the ORA-00600 Lookup tool (reference Note 600.1) for more information regarding the specific ORA-00625 error encountered. An Incident is created for this error in the Automatic Diagnostic Repository (ADR). When logging a service request, use the Incident Packaging Service (IPS) from the Support Workbench or the ADR Command Interpreter (ADRCI) to automatically package the relevant trace information (reference My Oracle Support Note 411.1). The following information should be gathered to determine the root cause:
- changes that led to the error
- events or unusual circumstances that led to the error
- operations attempted prior to the error
- conditions of the operating system and databases at the time of the error
Note: The cause of this message may manifest itself as different errors at different times. Consider the history of the errors that occurred before this internal error.
OCI-00625
Internal error code within PDB: [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string]
Cause
This is the generic PDB-specific internal error number for Oracle program exceptions. It indicates that a process encountered a low-level, unexpected condition within a PDB. The PDB was closed (abort). The first argument in the message is the internal message. This argument and the database version number are critical in identifying the root cause and the potential impact to your system.
Action
Visit My Oracle Support to access the ORA-00600 Lookup tool (reference Note 600.1) for more information regarding the specific ORA-00625 error encountered.
An Incident is created for this error in the Automatic Diagnostic Repository (ADR). When logging a service request, use the Incident Packaging Service (IPS) from the Support Workbench or the ADR Command Interpreter (ADRCI) to automatically package the relevant trace information (reference My Oracle Support Note 411.1).
The following information should also be gathered to help determine the root cause:
- changes leading up to the error
- events or unusual circumstances leading up to the error
- operations attempted prior to the error
- conditions of the operating system and databases at the time of the error
Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.
OCI-00625
Internal error code within PDB: [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string], [string]
Cause
This is the generic PDB-specific internal error number for Oracle program exceptions. It indicates that a process encountered a low-level, unexpected condition within a PDB. The PDB was closed (abort). The first argument in the message is the internal message. This argument and the database version number are critical in identifying the root cause and the potential impact to your system.
Action
Visit My Oracle Support to access the ORA-00600 Lookup tool (reference Note 600.1) for more information regarding the specific ORA-00625 error encountered.
An Incident is created for this error in the Automatic Diagnostic Repository (ADR). When logging a service request, use the Incident Packaging Service (IPS) from the Support Workbench or the ADR Command Interpreter (ADRCI) to automatically package the relevant trace information (reference My Oracle Support Note 411.1).
The following information should also be gathered to help determine the root cause:
- changes leading up to the error
- events or unusual circumstances leading up to the error
- operations attempted prior to the error
- conditions of the operating system and databases at the time of the error
Note: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.
