User`s guide

A-2 Oracle Database Installation and Administration Guide
ORA-05004: Fatal error: stack overflow, extension failed
Cause: A call to a function required an extension of the current call stack segment.
This extension failed and the corresponding ILCS routine returned the error.
Action: Ensure that the user address space is large enough in the JOIN entry and
that there is no temporary memory saturation. Then re-run the program. If you
need further help, then contact the Oracle Support Services Representative.
ORA-05005: Error: IT0INITS called in PROLOD
Cause: This is an internal error and should not occur.
Action: Contact the Oracle Support Services Representative.
ORA-05006: sltga already initialized
Cause: The initialization routine for the sltga is called more than one time.
Action: Check if more than one stub modules ( PROSTUB , XAOSTUB ) are linked to the
application.
ORA-05007: failed to load OSNTAB
Cause: This message is usually be preceded by a BS2000 BLS-nnnn message. The
most likely reason is that the
ORALOAD library cannot be found.
Action: Contact the Database Administrator about the ORALOAD library. If you
cannot identify the cause of the problem, then contact the Oracle Support Services
Representative.
ORA-05008: failed to load requested network driver
Cause: This message is usually be preceded by a BS2000 BLS-nnnn message. The
most likely reason is that the
ORALOAD library cannot be found.
Action: Contact the Database Administrator about the ORALOAD library. If you
cannot identify the cause of the problem, then contact the Oracle Support Services
Representative.
ORA-05009: osnsgl: user connects invalid in kernel
Cause: A database link was set up using the single-task driver (S:). This is invalid,
as the single-task driver can only be used for call connections on the user side.
Action: Select a different network driver for the database link.
ORA-05010: bad filename length
Cause: Buffer overflow while building/translating a file name. This could be
caused by specifying an excessively long file name in the
ORAENV file.
Action: If you cannot identify the cause of the problem, then contact the Oracle
Support Services Representative.
ORA-05011: bad file size
Cause: This is an internal error and should not normally occur.
Action: Contact the Oracle Support Services Representative.
ORA-05012: bad block size
Cause: This is an internal error and should not normally occur.
Action: Contact the Oracle Support Services Representative.
ORA-05013: bad filename parse
Cause: A file name being analyzed is not well-formed for Oracle Database
purposes.