User`s guide
Oracle Error Messages for BS2000/OSD A-15
Cause: An invalid value for the
KNL_SIZE
parameter has been specified in the
ORAENV
file.
Action: You should not normally specify this variable, as the default value will be
correct. Contact your Oracle Support Services Representative.
ORA-05174: bad kernel base
Cause: An invalid value for the
KNL_BASE
parameter has been specified in the
ORAENV
file.
Action: If this value is specified, then it must be a hexadecimal value giving the
full virtual address for the kernel memory pool. Correct the value and restart the
database.
ORA-05175: Kernel address space conflict
Cause: The Oracle Database kernel cannot be placed at the requested address
range, because the range is already used. The kernel start address is defined by the
ORAENV
parameter,
KNL_BASE
.
Action: Refer to the section on "Address Space Planning" in the chapter "Oracle
Database System Architecture and Implementation" of the Oracle Database
Installation and Administration Guide for Fujitsu BS2000/OSD, and adjust the
relevant initialization file and
ORAENV
parameters. Inspect the
JOIN
entry for your
address space limit. Contact your System Administrator to learn about shared
subsystems and their placement in the address space.
ORA-05176: Kernel: address space saturation
Cause: When the Oracle Database kernel memory pool was being allocated, the
operating system signalled that the virtual address space is currently saturated.
Action: Contact your System Administrator about paging area size and current
overall system load.
ORA-05177: Unexpected Kernel memory pool problem
Cause: The
ENAMP
macro returned an unexpected error code.
Action: This problem can be caused when you run a program in 24-bit mode and
try to connect a single-task to a kernel residing above the 16MB line (because the
database itself is running in 31-bit mode). If this is the cause of the error, then you
must access the database in two-task mode (through SQL*Net). Refer to the
ENAMP macro description in the BS2000 documentation for other possible reasons.
If you cannot identify the cause of the problem, then contact your Oracle Support
Services Representative.
ORA-05178: Kernel module not yet initialized
Cause: The current task is trying to attach to an Oracle Database kernel which is
not yet completely initialized. This can only happen if you try to connect to a
database which is just being started.
Action: Retry after a while. Remember that it may take a few minutes until a
database is fully running and ready for the users. If the error persists, then contact
your database administrator.
ORA-05180: Cannot load character set table
Cause: One of the modules containing character set tables cannot be loaded.
Action: Verify that the
ORALOAD
library is accessible through
LINK=ORALOAD
. For
further information about link names and the
ORALOAD
library, Refer to Chapter 1,
"Getting Started" in this manual. If you cannot identify the cause of the problem,
then contact your Oracle Support Services Representative.