User`s guide

Oracle Error Messages for BS2000/OSD A-7
ORA-05053: invalid or missing PGA_BASE
Cause: An invalid value for the PGA_BASE parameter has been specified in the
DBA
ORAENV file.
Action: Specify a correct value.
ORA-05054: invalid or missing PGA_SIZE
Cause: An invalid value for the PGA_SIZE environment variable has been specified
in the DBA
ORAENV file. You should never change the default value for the PGA_
SIZE
environment variable.
Action: Use the default value for the PGA_SIZE environment variable. If this does
not solve the problem, then contact your Oracle Support Services Representative.
ORA-05055: address range for PGA (fixed part) is not free
Cause: The address range described by the PGA_BASE and PGA_SIZE ORAENV
variables is not available for allocation. This may be due to overlapping
PGA , SGA ,
and
KERNEL areas, or to an application program which has occupied memory in
this area. If you did not specify a value for
PGA_BASE , then the default may be
inappropriate for your case.
Action: Refer to the section "Address Space Planning" in the "Oracle Database
System Architecture and Implementation" chapter of the Oracle Database
Installation and Administration Guide for Fujitsu BS2000/OSD for further
information.
ORA-05056: no more context space
Cause: During processing of a SQL request, dynamic memory could not be
allocated. This could happen when very complex requests are being processed and
there is not enough memory available.
Action: Verify that the user address space is large enough and that your
application program (if the error occurred when you were using an application
program) is not using excessive memory. Otherwise, contact your Oracle Support
Services Representative.
ORA-05058: assert failed: SGA not mapped
Cause: This is an internal error and should not normally occur.
Action: Contact your Oracle Support Services Representative.
ORA-05059: assert failed: not in kernel
Cause: This is an internal error and should not normally occur.
Action: Contact your Oracle Support Services Representative.
ORA-05060: SGA not created
Cause: After you issued the STARTUP command, the SGA shared memory pool
could not be created.
Action: Verify that you are not trying to start the database while it is running and
that the database system identification is not being used for two different
databases. Otherwise, contact your Oracle Support Services Representative.
ORA-05061: SGA attach failed
Cause: Connection to the SGA shared memory pool could not be established. This
may have happened if you used the wrong system identification, or if the database
you expected to be running is not running.