Oracle7 Server Messages Go to Product Documentation Library
Go to books for this product
Go to Contents for this book
Go to Index

Go to previous file in sequence Go to next file in sequence

Using Messages

This chapter gives you general information and helpful tips about messages. The following topics are covered:

Locating Message Documentation

Oracle Server

These messages are generated by the Oracle Server when running any Oracle program. This manual documents messages that are common across Oracle products and tools.

Product Specific

These messages are specific to one product and are documented in manuals for that product. For example, if you work on a Macintosh and use SQL*Net, you would need to refer to the messages contained in the SQL*Net for Macintosh Manual.

Operating System-Specific

These messages are specific to one operating system. A range of message code numbers is reserved for each operating system. For example, the range 7500 - 7999 is for DEC VAX/VMS messages; these messages are listed in the appropriate operating system-specific documentation.

The prefix of the message indicates where to find information about the message. For example, some messages in this manual have the prefix "ORA". If you encounter a message without a prefix, first check the manuals for the product you are using, then check this manual.

Accuracy of Messages

The accuracy of the messages in this manual is our primary concern. Occasionally, an enhancement to a message is not incorporated into the Oracle software. Should you encounter a message generated on your system that differs from the message in this book, be assured the improved message text is usually incorporated in the next release of the software. If you should encounter a discrepancy, please contact us using the information contained in the Reader Comment Form at the back of this manual.

Message Format

All messages you see displayed are prefixed by text that indicates which program issued the message. For example, the prefix "ORA" shows that the message was generated by the Oracle Server. The location of messages in this book depends on the prefix of the message. The following table lists the prefixes of messages that you may encounter and the location of the message in this book.

All messages are listed in order by the message code number. To look up a message, use the message code number.

Message Prefixes Listed in this manual

The following messages per prefix are listed in this manual:

Prefix Type of Message Location

DBA SQL*DBA Chapter 5

EXP Export utility Chapter 6

IMP Import utility Chapter 6

LCC Parameter file Chapter 6

MOD SQL*Module Chapter 8

ORA Generic Oracle Server Chapter 2

PCC Precompiler Chapter 4

PLS PL/SQL Chapter 3

SQL Precompiler Runtime Chapter 4

SQL*Loader SQL*Loader Chapter 7

Message Prefixes of Oracle Products Not Listed in this manual

The following message per prefix are not listed in this manual:

Prefix Type of Product

ACF File Access

ACG Oracle Access

ACI IAC Access

ACM Mail Access

ACS SQL Access

ACT Text Retrieval Access


ADM Office Administration

APP Applications

ASY SQL*Net Driver (Async Manager)

BLD VM Install

BRW Data Browser




CPR CASE*Project

Prefix Type of Product

CRM CASE*Repository

CPY Oracle Tools


DIR Directory Services

DLN Datalens


GC* Oracle Charting Library

GO* Oracle Graphics

GWP Oracle Procedural Gateway

GWT Oracle Transparent Gateway Developer Kit

GTW Gateway and Connect Kit


IDM SQL*Connect to IDMS


IMS SQL*Connect to IMS

INS Install

KNT SQL*Net Driver (Knet TCP/IP)

MAI Oracle Mail

MGR Server Manager

MBC Multi-byte CASE Library

MOD SQL*Module

MPA SQL*Net Driver (LU6.2/APPC)

MPI SQL*Net Driver (DECNet)


MPV SQL*Net Driver (VTAM)

MST VM Network Master (listener)


NBD VM net install

NSM SQL*Net (VTAMaster)

Prefix Type of Product

NSS VM-specific shared segment/memory Configurator

OAP SQL*Net Driver (APPC/LU62 Manager)


ODM Document Manager

OFC Oracle Office

OFF Oracle Office

OG* Oracle Graphics



ONS SQL*Net Driver (VTAM)


OPW Oracle Password

OSN SQL*Net Driver (VTAM)

OXA Oracle XA Interface

OXQ Office Automation Query Builder

PDE PL/SQL Development Environment

RDB SQL*Connect to RDB

RMS SQL*Connect to RMS

RXS Pro*Rexx

SCH Office Scheduler

SDS Source Control

SP1 Oracle Tools

SP2 Oracle Tools

SRV VM server (child process)

TST Ora*Tst

VG* Virtual Graphics System

VSA SQL*Connect to VSAM

Recognizing Variable Text in Messages

To help you find and fix errors, Oracle embeds object names, numbers, and character strings in some messages. These embedded variables are represented by name, num, str and so on. For example, the message

ORA-00020: maximum number of processes (num) exceeded 

might actually appear as follows:

ORA-00020: maximum number of processes (50) exceeded 

Message Stacks

Occasionally, you may see a "message stack." This is simply a series of related messages issued at different levels of Oracle.

The following message stack is a generic example:

ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "SCOTT.VALUE_ERR", line 1
ORA-06512: at line 1 

The following message stack is a VAX/VMS example:

ORA-01034: Oracle not available
ORA-07625: smsget: $MGBLSC failure
%SYSTEM-W-NOSUCHSEC, no such (global) section 

In this example, notice that the message at the bottom of the stack is issued by the VMS operating system. Seeing the messages at each level in the system may help you trace the originating event. For example, in this case, Oracle may not be available simply because it has not been started, and consequently there is no system global area (SGA). If you need the help of customer support, be sure to report all the messages in the stack.

Message Ranges

Oracle7 Server messages, which are found in Chapter 2 are grouped into specific ranges indicating the type or cause of event that generated the message. Most of these messages are listed in this manual. Because Oracle runs on many different platforms, operating system-specific messages are listed in the appropriate Oracle manual for each platform.

The following list shows all current Oracle7 Server message ranges. Ranges highlighted in bold type are operating system-specific messages that are not listed in this manual. For information about operating system-specific documents, see "Related Publications" in the Preface.

00000-00100: Oracle Server

00101-00149: Multi-Threaded Server

00150-00159: Oracle*XA

00200-00249: Control Files

00250-00299: Archiving and Recovery

00300-00369: Redo Log Files

00370-00389: KCB External

00390-00399: Redo Log Files

00400-00420: Oracle Compatibility

00436-00437: Licensing

00440-00460: Detached Process Startup

00470-00485: Detached Process Death

00486-00569: Interrupt Handlers

00570-00599: SQL*Connect Opening & Reading Files

00600-00639: Oracle Exceptions

00640-00699: SQL*Connect

00700-00709: Dictionary Cache

00816-00816: Message Translation

00900-00999: SQL Parsing

01000-01099: User Program Interface

01100-01250: Oracle Files

01400-01489: SQL Execution

01490-01499: Miscellaneous, ANALYZE, SQL Parsing, Execution

01500-01699: Oracle Commands

01700-01799: SQL Parsing

01800-01899: The Date Function

01900-02039: SQL Parsing

02040-02099: Distributed Transactions

02100-02139: Oracle Runtime Library SQL Messages

02140-02299: SQL Parsing

02351-02375: SQL*Loader in Direct Path Mode

02376-02399: Oracle Resources

02400-02419: EXPLAIN PLAN Command

02420-02429: Schemas

02430-02449: Constraint Enabling and Disabling

02450-02475: Hash Cluster Commands

02476-02479: Parallel Direct Loader

02480-02489: Trace Facility

02490-02499: Resizeable Datafiles

02500-02699: CTOS

02700-02757: UNIX Two Task

02875-02899: IBM RS/6000

03000-03099: Features Not Implemented

03100-03199: Two-Task Interface

03200-03289: Extent Allocation and Other Space Management Errors

03290-03295: TRUNCATE Command

03296-03299: Resizeable Datafiles

03300-03499: Meiko

03500-03699: Macintosh

03700-03999: AOS/VS

04000-04109: Command Parameters

04020-04029: Library Object Locks

04030-04039: System Memory

04040-04069: Stored Procedures

04070-04099: Triggers

04500-04899: CMS

04900-09429: ICL DRS6000

05000-05899: OEM

05900-05999: Wang

06000-06429: SQL*Net

06430-06499: NCR System 3000

06500-06599: PL/SQL

06581-06591: European OEM Ports

06600-06699: SQL*Net

06700-06899: SQL*Net TLI

06900-06939: CMX

06950-06999: SQL*Net AppleTalk

07000-07099: SQL*Connect for DB2

07100-07199: SQL*Connect for IMS

07200-07499: UNIX

07500-07999: VAX/VMS

08000-08174: Accessing Data

08175-08190: Discrete Transactions

08200-08399: nCUBE

08401-08499: PL/SQL Utility Packages for Procedural Gateway

08500-08799: SQL*Connect

09100-09199: Oracle Gateways

09200-09499: DOS, OS/2, and Novell

09500-09699: MPE/XL

09700-09999: UNIX

10000-10999: Internal

11000-11999: SQL*Net MVS

12000-12019: Table Snapshots

12100-12299: SQL*Net

12300-12399: Multiple Mount

12400-12499: Trusted Oracle

12500-12699: SQL*Net

12700-12799: National Language Support

12800-12849: Parallel Query/Index Creation

13000-13199: Spatial Data Option

14000-14099: Partitioned Objects - Parsing

14400-14499: Partitioned Objects - Execution

14500-14999: Partitioned Objects - Analyze

19999-21000: Stored Procedures

21100-21299: Internal Messages

23300-24299: DBMS PL/SQL Packages

24300-24999: UPI/OCI Messages

25000-25099: Trigger Errors

25100-25199: Parsing Errors

25200-25699: Advanced Queueing

Calling Customer Support

Some messages recommend calling Oracle's customer support to report a problem. When you call customer support, please have the following information at hand:

Also, you will be expected to give your

Oracle Exception Messages

Oracle's extensive self-checking helps detect internal errors. Rather than frustrate you with cryptic messages, Oracle uses the following catchall message for Oracle internal exceptions:

ORA-00600: internal error code, arguments: [num], [], [],[],[],[] 

An actual message might appear as follows:

ORA-00600: internal error code, arguments: [1042], [3],[upilam], [], [],[] 

Notice that the message text is followed by up to six arguments, which indicate the origin and attributes of the error. The first argument is the internal error number. Other arguments are various numbers, names, and character strings. Empty brackets may be ignored.

In addition to being returned to the user, internal errors are also written to the Alert file along with additional information about the event causing the message. The Alert file also lists any trace files that may have been generated because of an internal error. See the following sections for descriptions of the trace and alert files.

If you receive an ORA-00600 message, report it as a software bug to customer support.

Trace Files

A trace file is created each time an Oracle instance starts or an unexpected event occurs in a user process or background process. The name of the trace file includes the instance name, the process name, and the Oracle process number. The file extension or file type is usually TRC, and, if different, is noted in your operating system-specific Oracle documentation. The contents of the trace file may include dumps of the system global area, process global area, supervisor stack, and registers.

Two initialization parameters specify where the trace files are stored:


Specifies the location for trace files created by the Oracle background processes PMON, DBWR, LGWR, and SMON.


Specifies the location for trace files created by user processes such as SQL*DBA, SQL*Plus, or Pro*C.

The Alert file also describes the location of trace files generated when internal errors occur. See the next section for a description of the Alert file.

You may need to format the trace file before using it to diagnose problems. To format a trace file, use the DUMPFMT utility, which is available on most systems and is described in your operating system-specific Oracle documentation. Customer support may ask you for a formatted trace file to help solve a problem.

For more information about trace files, see the Oracle7 Server Administrator's Guide.

The Alert File

The Alert file is a log file that records information about internal errors and administrative activities, such as backups. When an internal error occurs, the message is sent to the terminal screen as well as written to the Alert file. Oracle also writes additional information about internal errors to the Alert file, such as the location and name of any trace files generated because of the error and so forth.

The name of the Alert file is operating system-specific. The location of the Alert file is the same as the location of the background process trace files. This location is specified by the BACKGROUND_DUMP_DEST initialization parameter. For more information, see your Oracle7 operating system-specific documentation.

If your system uses an operator's console, some messages from Oracle may appear on the console. All important messages are written to the Alert file as well as the operator's console. Because non-Oracle messages also appear on this console, the Alert file is a better record for tracing all Oracle administrative activity and errors than the console log.

The Alert file also records information about administrative activities, such as backups and archiving online redo log files. For more information about the Alert file, see the Oracle7 Server Administrator's Guide.

Go to previous file in sequence Go to next file in sequence
Prev Next
Copyright © 1996 Oracle Corporation.
All Rights Reserved.
Go to Product Documentation Library
Go to books for this product
Go to Contents for this book
Go to Index