User`s guide

Problems Accessing the Database
Troubleshooting D-3
■ Does the file exist?
■ Is the file accessible to the program which is trying to open it?
■ Is there a hardware problem?
■ Did you specify the correct block size?
If you specified the ORAENV environment variable, SF_PBLKSIZE , at database creation,
then you must continue to use the same specification whenever you run an
ALTER
DATABASE
statement.
D.3.2 Oracle Database 11g Trace Files
Whenever Oracle Database 11g encounters an exception, it writes a trace (or dump)
file. You may need to send the file to the Oracle Support Services Representative if any
unusual problem occurs.
These files are created at database startup with a standard header and are modified for
the last time at database shutdown. If no problems have occurred, then you may want
to remove these files after a successful shutdown.
D.3.3 Oracle Database-Level Error Information
When you get an Oracle Database message, the ORA-xxxx message may sometimes be
followed by a message like the following:
SOSD error 8xxxyyyy from mmmmmmmm : text
This indicates that the error originated in operating system code or low-level Oracle
Database code interfacing with the operating system. The
SOSD error code provides
important diagnostic information, and when contacting the Oracle Support Services
Representative you should always supply this code, if present, in addition to the
Oracle Database error number.
The error code is displayed in hexadecimal, and is structured as follows:
■ xxx identifies the function reporting the error. This information is useful to the
Oracle Support Services Representative.
■ yyyy details the error. It is either an internal code of the function, or a compacted
return code of a BS2000 system macro (see subsequent section).
■ mmmmmmmm is the name of the Oracle Database internal function. Text, if
present, explains the error code. Often it says "
RC FROM zzzzz MACRO ".
A BS2000 system macro return code is condensed into the 2-byte value yyyy as
follows:
■ For system macros that return a code bb0000aa , yyyy is bbaa
■ For I/O calls, yyyy is the DMS error code
In all other cases, yyyy contains the right halfword of the return code of the BS2000
macro.