|Oracle8i Server Installation and Database Administration Guide
Release 3 (8.1.7) for Fujitsu Siemens Computers BS2000/OSD
Part Number A95466-01
This section describes problems that you may encounter when using the Oracle Server release 8.1.7 on BS2000, and provides you with information on how to diagnose and overcome such problems.
To solve a problem, identify the type of the problem and locate the relevant information in this appendix. Examine each of the listed points to find the cause of the problem. Carry out the suggested solution, and try again. The event log file described in this document may help you to diagnose the problem.
Refer to the appendix "Oracle Messages" in this guide and to Oracle8i Server Messages and Codes Manual for information about specific messages.
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, 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:
When you attempt to start up a database and the startup fails, you sometimes get an ORA-5032 message and not much other information. This indicates that a problem occurred in a very early stage of the startup, when the Oracle8i error stack and backtracking mechanism was not yet active. If this is the case, you should check the following:
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 your System Administrator to find out how the subsystems are arranged. Then change the corresponding xxx_BASE environment variables in your ORAENV file to relocate the Oracle8i areas to suitable address ranges.
A small address space allowance in the JOIN file may not leave enough room for Oracle8i requirements.
If the Oracle8i database has not been shut down properly, old background, server, or single-task users 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. It may be difficult to find out about cross-userid single-task users. Exit SVRMGRL (this is required to release the old kernel as well) and retry.
If you get a timeout message when starting the background tasks, check the following points:
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 BS2000 JOIN entry. Cancel any background tasks that have already started.
If you have problems opening, closing, reading, or writing a database or log file, check the following points:
If you specified the ORAENV environment variable, SF_PBLKSIZE, at database creation, you must continue to use the same specification whenever you execute an ALTER DATABASE statement.
Whenever the Oracle8i Server encounters an exception condition, it writes a trace (or dump) file. You may need to send the file to your Oracle Customer Support Representative if any unusual problem should occur.
Note that 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, you may wish to remove these files after a successful shutdown.
Trace files are created by Server Manager, the background and the network server tasks. A user (client) task creates a trace file, only if an error is encountered in a single-task connection.
A trace filename is constructed using the pattern defined by the ORADUMP environment variable in the ORAENV file.
When you get an Oracle Server message, the OER-xxxx message may sometimes be followed by a message like the following:
This indicates that the error originated in operating system code or low-level Oracle Server code interfacing with the operating system. The SOSD error code provides important diagnostic information, and when contacting your Oracle Customer Support Representative you should always supply this code, if present, in addition to the Oracle Server error number.
The error code is displayed in hexadecimal, and is structured as follows:
A BS2000 system macro return code is condensed into the 2-byte value yyyy as follows: