D Troubleshooting

D.1.1 Problems Creating a Database

You should always use INSTALL.P.SUPER or INSTALL.P.DBA to create a new database, because this is the easiest way to get a correct instance. If you encounter problems during this process, then study the diagnostic output, correct, and run the respective part manually, or remove the partially-created database, and re-run the whole process. All files belonging to a specific database are prefixed with the system identifier (ORASID) for that database, except for log files which have an extra prefix.

Also, check the following:

• Does the BS2000 user ID have an adequate PUBLIC-SPACE-LIMIT for the corresponding pubset?

• Is enough disk space available on the pubset or disks used to create the databases?

• Is disk space fragmentation too high?

D.2.1 Problems Starting a Database

This section lists information related to problems encountered when starting a database.

• 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.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:

• Does the file exist?

• Is the file accessible to the program which is trying to open it?

• Is there a hardware problem?

• Did you specify the correct block size?

If you specified the ORAENV environment variable, SF_PBLKSIZE, at database creation, then you must continue to use the same specification whenever you run an ALTER DATABASE statement.

D.3.2 Oracle Database 11g Trace Files

Whenever Oracle Database 11g encounters an exception, it writes a trace (or dump) file. You may need to send the file to the Oracle Support Services Representative if any unusual problem occurs.

These files are created at database startup with a standard header and are modified for the last time at database shutdown. If no problems have occurred, then you may want to remove these files after a successful shutdown.

D.3.3 Oracle Database-Level Error Information

When you get an Oracle Database message, the ORA-xxxx message may sometimes be followed by a message like the following:

SOSD error 8xxxyyyy from mmmmmmmm : text

This indicates that the error originated in operating system code or low-level Oracle Database code interfacing with the operating system. The SOSD error code provides important diagnostic information, and when contacting the Oracle Support Services Representative you should always supply this code, if present, in addition to the Oracle Database error number.

The error code is displayed in hexadecimal, and is structured as follows:

• xxx identifies the function reporting the error. This information is useful to the Oracle Support Services Representative.

• yyyy details the error. It is either an internal code of the function, or a compacted return code of a BS2000 system macro (see subsequent section).

• mmmmmmmm is the name of the Oracle Database internal function. Text, if present, explains the error code. Often it says "RC FROM zzzzz MACRO".

A BS2000 system macro return code is condensed into the 2-byte value yyyy as follows:

• For system macros that return a code bb0000aa, yyyy is bbaa

• For I/O calls, yyyy is the DMS error code

In all other cases, yyyy contains the right halfword of the return code of the BS2000 macro.