Skip Headers

Oracle8i Server Installation and Database Administration Guide
Release 3 (8.1.7) for Fujitsu Siemens Computers BS2000/OSD

Part Number A95466-01
Go To Table Of Contents
Go To Index

Go to previous page Go to next page

Problem Solving

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.

Problems Installing Oracle8i

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, 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:

Problems Starting a Database

Problems Starting the Database

Problems with Tasks

If you get a timeout message when starting the background tasks, check the following points:

Problems Accessing the Database

Problems with Database and Log files

If you have problems opening, closing, reading, or writing a database or log file, check the following points:

Oracle8i Trace Files

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.

Trace Filenames

A trace filename is constructed using the pattern defined by the ORADUMP environment variable in the ORAENV file.

OS-Level Error Information

When you get an Oracle Server message, the OER-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 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:

identifies the function reporting the error. This information is useful to your Oracle Customer Support Representative.

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

is the name of the Oracle Server 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:

Go to previous page Go to next page
Copyright © 2001 Oracle Corporation.

All Rights Reserved.
Go To Table Of Contents
Go To Index