User`s guide

A-16 Oracle Database Installation and Administration Guide
Cause: The user-side stub module could not load the PRO/OCI module. In this
case, the message is usually preceded by a BS2000 BLS-
nnnn message, or the
loaded module is incompatible with the version of the stub module.
Action: Ensure that the ORALOAD link name exists and points to the current
ORALOAD library. Re-link the application with the current link libraries.
ORA-05191: symbol translation error for kernel memory pool
Cause: The logical name translation for the kernel memory pool failed. Normally,
this indicates an invalid system id,
ORASID in the ORAENV file.
Action: Ensure that the ORAENV file definition is correct. Otherwise, contact the
Oracle Support Services Representative.
ORA-05192: cannot create/attach kernel memory pool
Cause: The memory pool for the Oracle Database kernel code could not be
enabled. In a user program, a possible cause is that the user program already
allocates part of the address range needed for the memory pool.
Action: Ensure that the user program does not request storage excessively, and
that any
SGA_BASE and KNL_BASE parameters in the ORAENV file are consistent. If
you cannot identify the cause of the problem, then contact the Oracle Support
Services Representative.
ORA-05193: Symbol translation error for kernel module or load library
Cause: The logical-name translation for the kernel module or load library failed.
This is an internal error and should not normally occur.
Action: Contact the Oracle Support Services Representative.
ORA-05194: cannot load kernel
Cause: The kernel could not be loaded into the kernel memory pool. In most
cases, this message is preceded by a
BLS - nnn message from the operating system.
Action: Ensure that the ORALOAD link name identifies the correct ORALOAD library,
and that the
ORAENV variable, KNL_MODULE , names one of the possible kernels. Then
re-issue the
STARTUP command. If you cannot identify the cause of the problem,
then contact the Oracle Support Services Representative.
ORA-05195: bad or missing kernel connector
Cause: The loaded kernel could not verify its user-side connector module. This
can occur if you use an incorrect kernel version.
Action: If you cannot identify the cause of the problem, then contact the Oracle
Support Services Representative.
ORA-05198: associated internal OSD error code %d
Cause: This message precedes ORA-05199, if there is more information available.
The first 4 hexadecimal digits can often identify the module, and the last 4
hexadecimal digits are usually a condensed version of an associated system macro
code. This code can be helpful in diagnosing the problem.
Action: If you cannot identify the cause of the problem, then contact the Oracle
Support Services Representative.
ORA-05199: ORACLE ABNORMAL EXIT
Cause: A fatal error occurred, which prevents continuation of execution. In many
cases, a preceding message explains the error. The system causes the program
execution to stop (
TERM ABNORMAL with DUMP is displayed).