User`s guide

Problems Accessing the Database
D-2 Oracle Database Installation and Administration Guide
■ Did you get an ORA-05032 error with no extra information?
When you attempt to start a database and the startup fails, you sometimes get an
ORA-05032 message and not much other information. This indicates that a
problem occurred in a very early stage of the startup, when Oracle Database 11g
error stack and backtracking mechanism was not yet active. If this is the case, then
you should check the following:
– Did you call the ORAENV procedure prior to calling SQL*Plus?
– Did you specify a correct and unique ORASID value in the ORAENV file?
– Are there potential address range conflicts?
The address ranges assigned to the kernel memory pool, the SGA, and the
PGA, in each task, could be partially occupied by shared subsystems also used
in the instance. Contact the System Administrator to find out how the
subsystems are arranged. Then change the corresponding
xxx_BASE
environment variables in the
ORAENV file to relocate the Oracle Database 11g
areas to suitable address ranges.
– Is the user address space large enough?
A small address space limit may not leave enough room for Oracle Database
11g requirements.
– Has a previous startup attempt failed, leaving invalid background, database,
or user tasks?
If the Oracle Database 11g has not been shut down properly, then old
background or database tasks may hang and still be connected to the SGA of
the old instance. This inhibits the creation of a new SGA. You may get a
message indicating
shutdown in progress .
Cancel the remaining background, server, and user tasks. Exit SQL*Plus (this
is required to release shared memory pools of the old instance) and retry.
D.2.2 Problems with Tasks
If you get a time out message when starting the background tasks, then check the
following points:
■ Are the background tasks blocked in the BS2000 job queue? This may occur due to
system overload or insufficient task priority.
The background tasks should always be started with the IMMEDIATE option and
preferably in a reserved
Jobclass . Check the ORAENV BGJPAR environment variable
and the user attributes of the BS2000 user ID. Cancel any background tasks that
have already started.
■ If no background task can be found using the /STATUS command, then the jobs
have probably aborted. Check the job outputs.
D.3 Problems Accessing the Database
Refer to this section if you are facing issues accessing the database.
D.3.1 Problems with Database and Log files
If you have problems opening, closing, reading, or writing a database or log file, then
check the following points: