1
Interpreting Error Messages

This chapter provides general information and helpful tips about error and informational messages generated by the Oracle Enterprise Manager that can require action on your part. For each message, the probable cause and corrective action are provided. The following topics are discussed:

• Sorting Out Oracle Enterprise Manager Error Messages

• Calling Worldwide Customer Support

Attention:

For information on the specific Oracle server releases supported by Oracle Enterprise Manager and its components, see the compatibility matrix in the Oracle Enterprise Manager Documentation Release Note.

Sorting Out Oracle Enterprise Manager Error Messages

The chapters in this manual discuss specific messages for the Console, its internal services, its integrated applications, Oracle Performance Manager, Oracle TopSessions, Oracle Tablespace Manager, Oracle Expert, and Oracle Trace.

Enterprise Manager Prefixes

The Oracle Enterprise Manager messages are listed alphabetically by message prefix. The prefix of the message indicates the Oracle Enterprise Manager facility that generated the message. The following table lists these prefixes and the associated Oracle Enterprise Manager facilities.

Table 1-1

Code	Facility
EPC	Oracle Trace
XP	Oracle Expert Services
MGR	SQL Engine and Line Mode
NMS	Agent
VAR	Backup and Recovery Manager
VAC	Security Manager
VAG	Storage Manager
VAI	Instance Manager
VAS	Schema Manager
VAX	Generic
VMM	Oracle Performance Manager
VMS	Oracle TopSessions
VMT	Oracle Tablespace Manager
VOC	Console
VOD	Daemon
VOJ	Job System

Message Prefixes and the Associated Facility

Note:

Error messages that are generated from the SQL Worksheet generally appear with the MGR prefix.

Other Oracle Error Prefixes

There are other Oracle product error messages that you may encounter. When you see prefixes that are not listed in the Oracle Enterprise Manager Messages Manual, you need to see the specific manual that discusses error messages with that prefix, as follows.

• The prefix "TNS" means that the error message is generated by an Oracle network product. These errors are documented in Oracle Network Products Messages Manual.

• The prefix "NMC" indicates that an error message is generated by the Oracle Network Manager. The prefix "NMO" indicates error messages generated by the network object layer of the Network Manager. The prefix "NMR" is for messages generated from the ROS file level of the Network Manager. These errors are documented in Oracle Network Products Messages Manual.

• The prefix "NNO" precedes error messages generated by a Names server. The prefix "NNC" is for error messages generated by an Oracle Names client, and those common to both server and client. The prefix "NNL" is for error messages generated by the Oracle Names Control utility. These errors are documented in Oracle Network Products Messages Manual.

• The "NMP" prefix is for error messages generated by the Network Management Protocol, the part of the Names server that handles SNMP queries. The "NPL" prefix precedes error messages generated by the Network Presentation Layer component of the Names server. Network Management Protocol and Network Presentation Layer error messages are typically not visible to the user. These errors are documented in Oracle Network Products Messages Manual.

• The prefix "ORA" is the generic prefix returned by all Oracle applications. These errors are documented in Oracle Server Messages.

Calling Worldwide Customer Support

Some error messages recommend calling Worldwide Customer Support to report the error. When you call Worldwide Customer Support, please have the following information at hand:

• The hardware, operating system, and release number of the operating system on which your application(s) are running.

  Example: "My client application runs on a Windows NT workstation running SUN OS4.1.3 and the server application runs on a SUN workstation machine running SUN OS4.1.3. The protocol is TCP/IP."

• The release numbers of all the Oracle Enterprise Manager products involved in the current problem.

  Example: "We are running Oracle Enterprise Manager release 1.0 at the client and the server, with release 2.0.14 Oracle TCP/IP Adapters."

• If you encountered one or more error codes or messages, the exact code numbers and message texts in the order they appeared.

• The problem severity according to the following codes:

  1 = Program not usable. Critical impact on operations.

  2 = Program usable. Operations severely restricted.

  3 = Program usable with limited functions. Not critical to overall operations.

  4 = Problem circumvented by customer. Minimal effect, if any, on operations.

• A description of the problem, including any unusual conditions.

• You will also be expected to provide your:
  • name
  • company's name
  • company's Oracle customer support ID (CSI) number
  • phone number

---