Oracle Utilities - Using Hidden
Programs, Import/Export, SQL Loader, oradebug, Dbverify, Tkprof and
More
Using the facility name that was entered on the command line, oerr
retrieves the component for that facility (as displayed in Figure 3.3).
In the example above (oerr ora 04030), oerr will use the rdbms
component. Once the component is retrieved, oerr can derive the full
path and file name for the appropriate message file:
Following the example through, the line above equates to the following
directory and file:
$ORACLE_HOME/rdbms/mesg/oraus.msg
Once the path and filename are determined, the contents of the file will
provide the cause and action for each error in the facility:
01058, 00000, "internal New Upi interface error"
// *Cause: Attempt to delete non existant hstdef extension.
// *Action: Report as a bug.
01059, 00000, "parse expected before a bind or execute"
// *Cause: The client application attempted to bind a variable or
execute
// a cursor opened in a PL/SQL block before the statement was parsed.
// *Action: Ensure the statement is parsed before a bind or execute.
01060, 00000, "array binds or executes not allowed"
// *Cause: The client application attempted to bind an array of cursors
or
// attempted to repeatedly execute against a PL/SQL block with a bind
// variable of type cursor.
// *Action: Bind a single cursor or execute the PL/SQL block once.
All of the “ORA” error messages are contained in this file. oerr will
find the error number in this file utilizing awk commands and display
the results back to the terminal.
The above is an excerpt from Oracle Utilities - Using
Hidden Programs, Import/Export, SQL Loader, oradebug, Dbverify, Tkprof
and More by Rampant TechPress.
For more details on Oracle
utilities, see the book "Advanced
Oracle Utilities" by Bert Scalzo, Donald K. Burleson, and Steve Callan.
You can buy it direct from the publisher
for 30% off directly from
Rampant TechPress.
