1
Interpreting Error Messages

This chapter provides general information and helpful tips about using this guide for interpreting Oracle Enterprise Manager error messages. The following topics are discussed in this chapter:

• Sorting Oracle Enterprise Manager messages
• Calling Oracle Support Services

Important:

For information on the specific Oracle server releases supported by Oracle Enterprise Manager and its components, see the Oracle Enterprise Manager Configuration Guide.

Sorting Oracle Enterprise Manager Messages

This manual discusses specific messages for the Oracle Enterprise Manager Console, its common services, and integrated applications. This manual also covers messages for the separately licensable Management Packs.

Message Prefixes

In this manual, messages are sorted in alphabetical order by message prefix, and each chapter covers messages of one or more types of prefixes. The prefix of a message indicates the Oracle Enterprise Manager facility that generated the message. The following table lists these facilities.

Table 1-1 Message Prefixes

Prefixes Beginning With:	Facility
EmSDK	Software Developer Kit (SDK) Messages
EPC	Oracle Trace Messages
OMO	Oracle Management Object Messages
ODG	Oracle Data Collection Service Messages (Second Tier)
SDO	Spatial Index Analyzer Messages
VD. . .	Oracle Enterprise Manager Framework Messages
VDKBITW	Index Tuning Wizard Messages
VMS	Oracle Top Sessions Messages
VNI	Agent Gateway Messages
VTC. . .	Console Messages
VTD	Oracle Data Collection Service Messages (Client Tier)
VTK	Oracle Management Server Messages (Client Tier)
VTM	Oracle Performance Manager Messages
VTP	Oracle Capacity Planner Messages
VTZCLI	Change Management Pack Command Line Interface Messages
VXA	Oracle Management Server Messages
VXN	Naming Service Messages

Other Oracle Message Prefixes

There are other Oracle messages that you may encounter when using Oracle Enterprise Manager. When you see prefixes that are not listed in this manual, check the specific manuals that discuss messages with those prefixes, as follows:

Table 1-2 Other Oracle Message Prefixes

Prefixes	Manuals
TNS	The error message is generated by an Oracle network product. These errors are documented in the Oracle9i Database Error Messages manual.
NMC	The 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 the Oracle9i Database Error Messages manual.
NNO	The error messages are generated by a Names server. The prefix "NNC" is for error messages generated by an Oracle Names client and for error messages 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 the Oracle9i Database Error Messages manual.
NMP	The error messages are 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 the Oracle9i Database Error Messages manual.
ORA	This generic prefix is returned by all Oracle applications. These errors are documented in the Oracle9i Database Error Messages manual.

Contacting Oracle Support Services

Some error message actions recommend contacting Oracle Support Services to report an error. When contacting Oracle Support Services, prepare the following:

• Have at hand the hardware, operating system, and release number of the operating system on which your application(s) is running.
• Have at hand the release numbers of all the Oracle Enterprise Manager products involved in the current problem.
• If you encountered one or more error codes or messages, have ready the exact message prefixes and numbers and message texts in the order they appeared.
• Provide a number representing the severity of the problem 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.

• Provide a description of the problem, including any unusual conditions.
• You will also be asked for your:

  Name

  Company name

  Company's Oracle customer support ID (CSI) number

  Phone number

Table 1-3 Preparation Checklist

Information Needed	Fill In
Applications	Hardware: Operating system: Release number of the operating system:
Oracle Enterprise Manager	Release numbers:
Messages	Message prefixes: Message numbers: Order they appeared:
Severity of the Problem	Number representing the severity: 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.
Problem Description
Customer Information	Name: Company name: Company's Oracle customer support ID (CSI) number: Phone number: