We can display the cause of an error that we received and troubleshooting suggestions, with the OERR Utility.
It is located under the $ORACLE_HOME/bin directory. We can use the OERR utility after setting the variables.
If you are not familiar with the error, OERR can quickly provide information on identifying the problem.
|
1 2 3 4 5 6 7 8 9 10 11 |
-bash-4.3$ . oraenv ORACLE_SID = [oracle] ? TESTDB1 The Oracle base remains unchanged with value /u01/app/oracle -bash-4.3$ oerr Usage: oerr facility error Facility is identified by the prefix string in the error message. For example, if you get ORA-7300, "ora" is the facility and "7300" is the error. So you should type "oerr ora 7300". If you get LCD-111, type "oerr lcd 111", and so on. |
The use is as follows:
For ORA-03113 error;
|
1 2 3 4 5 6 7 8 |
-bash-4.3$ oerr ora 3113 03113, 00000, "end-of-file on communication channel" // *Cause: The connection between Client and Server process was broken. // *Action: There was a communication error that requires further investigation. // First, check for network problems and review the SQL*Net setup. // Also, look in the alert.log file for any errors. Finally, test to // see whether the server process is dead and whether a trace file // was generated at failure time. |
For ORA-01555 error;
|
1 2 3 4 5 6 |
-bash-4.3$ oerr ora 1555 01555, 00000, "snapshot too old: rollback segment number %s with name \"%s\" too small" // *Cause: rollback records needed by a reader for consistent read are // overwritten by other writers // *Action: If in Automatic Undo Management mode, increase undo_retention // setting. Otherwise, use larger rollback segments |
For RMAN-01009 error;
|
1 2 3 4 |
-bash-4.3$ oerr rman 01009 1009, 1, "syntax error: found \"%s\": expecting one of: \"%s\"" // *Cause: A syntax error was signaled during parsing. // *Action: Correct the input. |
For CRS-00215 error;
|
1 2 3 4 |
-bash-4.3$ oerr crs 215 215, 1, "Could not start resource '%s'." // *Cause: There was an internal error while starting the resource. // *Action: Check the CRS daemon log file. |
