User`s guide

A-8 Oracle Database User's Guide
Action: Verify that it is not one of the preceding causes (check with your database
administrator). Otherwise, contact your Oracle Support Services Representative.
ORA-05063: SGA base invalid
Cause: An invalid value has been specified for the SGA_BASE parameter in the
ORAENV file.
Action: This value is not normally needed. If specified, it must be a hexadecimal
value giving the full virtual address for the
SGA memory pool. Correct the value
and re-issue the
STARTUP command.
ORA-05064: cannot allocate SGA
Cause: After creating the memory pool, the REQMP to allocate the space failed.
Probable operating system error.
Action: If you cannot identify the cause of the problem, then contact your Oracle
Support Services Representative.
ORA-05065: SGA not deleted
Cause: When attempting to detach from the SGA, the DISMP system macro
returned an error.
Action: If you cannot identify the cause of the problem, then contact your Oracle
Support Services Representative.
ORA-05066: SGA address space conflict
Cause: The SGA cannot be placed at the requested address range, because the
range is already partly used. The SGA start address is defined by the
ORAENV
variable,
SGA_BASE ; its size is determined by various initialization file parameters
such as processes, buffers, and so on.
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 variables. Inspect the JOIN entry for your
address space limit. Contact your System Administrator to find out about shared
subsystems and their placement in the address space. Make sure that you do not
overlap with the Oracle Database kernel.
ORA-05067: SGA: address space saturation
Cause: When the SGA is being allocated, the operating system reported that the
virtual address space is saturated.
Action: Contact your System Administrator about paging area size and current
overall system load.
ORA-05068 SGA still active, should not be
Cause: When the SGA is being created during startup, it is found that the SGA
memory pool is still in use (although the databases should be shut down). This
may be caused by a hanging single-task, user task or a network server task.
Action: Check for such hanging tasks. Cancel these tasks, then restart the
database.
ORA-05069: Unexpected SGA memory pool problem
Cause: The ENAMP macro returned an unexpected error code.
Action: Contact your Oracle Support Services Representative.
ORA-05070: cannot enable TPA ser.item