| Oracle7 Server Messages |  Library |
 Product |
 Contents |
 Index |
| Oracle7 Server Messages | Library |
Product |
Contents |
Index |
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.
All messages are listed in order by the message code number. To look up a message, use the message code number.
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
Prefix Type of Product
ACF File Access
ACG Oracle Access
ACI IAC Access
ACM Mail Access
ACS SQL Access
ACT Text Retrieval Access
ADA SQL*Connect to ADABAS
ADM Office Administration
APP Applications
ASY SQL*Net Driver (Async Manager)
BLD VM Install
BRW Data Browser
CAL SQL*Calc
CCC CASE*Core
CIC CICS Attach
CPR CASE*Project
Prefix Type of Product
CRM CASE*Repository
CPY Oracle Tools
DBU DBU
DIR Directory Services
DLN Datalens
FRM SQL*Forms
GC* Oracle Charting Library
GO* Oracle Graphics
GWP Oracle Procedural Gateway
GWT Oracle Transparent Gateway Developer Kit
GTW Gateway and Connect Kit
IAP SQL*Forms
IDM SQL*Connect to IDMS
IMP IMPORT
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)
MPM MPM
MPV SQL*Net Driver (VTAM)
MST VM Network Master (listener)
MTC SQL*Net Driver (IBM TCP/IP)
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)
OCL ORAINST
ODM Document Manager
OFC Oracle Office
OFF Oracle Office
OG* Oracle Graphics
OIN VM ORAINST
OIT SQL*Net Driver (SNS TCP/IP)
ONS SQL*Net Driver (VTAM)
ONT SQL*Net Driver (NCR TCP/IP)
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
ORA-00020: maximum number of processes (num) exceeded
might actually appear as follows:
ORA-00020: maximum number of processes (50) exceeded
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.
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.
00101-00149: Multi-Threaded Server
00250-00299: Archiving and Recovery
00400-00420: Oracle Compatibility
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
00816-00816: Message Translation
01000-01099: User Program Interface
01490-01499: Miscellaneous, ANALYZE, SQL Parsing, Execution
01800-01899: The Date Function
02040-02099: Distributed Transactions
02100-02139: Oracle Runtime Library SQL Messages
02351-02375: SQL*Loader in Direct Path Mode
02400-02419: EXPLAIN PLAN Command
02430-02449: Constraint Enabling and Disabling
02450-02475: Hash Cluster Commands
02476-02479: Parallel Direct Loader
02490-02499: Resizeable Datafiles
03000-03099: Features Not Implemented
03100-03199: Two-Task Interface
03200-03289: Extent Allocation and Other Space Management Errors
03296-03299: Resizeable Datafiles
04000-04109: Command Parameters
04020-04029: Library Object Locks
04040-04069: Stored Procedures
06581-06591: European OEM Ports
06950-06999: SQL*Net AppleTalk
07000-07099: SQL*Connect for DB2
07100-07199: SQL*Connect for IMS
08175-08190: Discrete Transactions
08401-08499: PL/SQL Utility Packages for Procedural Gateway
09200-09499: DOS, OS/2, and Novell
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
25200-25699: Advanced Queueing
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.
Two initialization parameters specify where the trace files are stored:
BACKGROUND_DUMP_DES
Specifies the location for trace files created by the Oracle background processes PMON, DBWR, LGWR, and SMON.
USER_DUMP_DEST
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 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.
|
Prev Next |
 Copyright © 1996 Oracle Corporation. All Rights Reserved. |
Library |
Product |
Contents |
Index |