Oracle Error Message Facility
Contents |
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 sqlerrm in oracle example server releases supported by Oracle Enterprise Manager and its components, see the Oracle
How Do You See Virtual Memory Statistics In Linux?
Enterprise Manager Configuration Guide. Sorting Oracle Enterprise Manager Messages This manual discusses specific messages for the Oracle Enterprise Manager Console, oerr command 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
Oerr Ora
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 oerr utility windows 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
Improper standard input connection from the terminal. Action: Normally not visible to the user. Start the INTCTL program again.
Oerr Railroad
If the error persists, contact Oracle Support Services. TNS-00002 INTCTL:
Sqlerrcode
error while starting the Interchange Cause: The Interchange could not be started. Action: Check the Interchange oracle sql error message configuration files (INTCHG.ORA, TNSNET.ORA and TNSNAV.ORA) for errors and confirm that no other programs are using the ADDRESS(es) specified. If the error continues, turn on tracing in https://docs.oracle.com/cd/B10501_01/em.920/a96671/interp.htm the Interchange components and examine the trace files to determine the cause of the problem. Be sure to turn tracing off when the problem has been resolved. TNS-00003 INTCTL: error while sending request to the Interchange Cause: Improper command sent to the Interchange or the Interchange is not responding. This message is not normally http://docs.oracle.com/cd/B10500_01/server.920/a96525/tnsus.htm visible to the user. Action: Verify that the command sent to the Interchange is valid. Also check that the Interchange is running by using the INTCTL STATUS command. If necessary, start the Interchange using the INTCTL START command. TNS-00004 INTCTL: error while starting the Navigator Cause: The Navigator could not be started. Action: Check to make sure that executables for the Navigator (NAVGATR) are present in the Oracle executable directory on your platform. Check the configuration files TNSNET.ORA and TNSNAV.ORA for errors. If the error continues, turn on tracing in the Interchange components and examine the trace files to determine the cause of the problem. Be sure to turn tracing off when the problem has been resolved. TNS-00005 INTCTL: error while sending request to the Navigator Cause: The Navigator is not responding. Either the Navigator is not running or another process is responding. Action: Check that the Navigator is running by using the STATUS command of the Interchange Contr
SQL TuningSecurityOracle UNIXOracle LinuxMonitoringRemote supportRemote plansRemote servicesApplication Server ApplicationsOracle FormsOracle PortalApp UpgradesSQL ServerOracle ConceptsSoftware SupportRemote Support Development Implementation Consulting StaffConsulting PricesHelp Wanted! http://www.dba-oracle.com/t_create_custom_oracle_error_message.htm Oracle PostersOracle Books Oracle Scripts Ion Excel-DB Don Burleson Blog
Make a custom Oracle error message Oracle Database Tips by Burleson ConsultingDecember 12, 2015 Question: I want to make fully documented custom error messages in my PL/SQL application and integrate the error error message messages the same as any other ORA-xxxx message. How do you document a new error and make it work with the oerr utility? Answer: Adding custom Oracle error messages is not difficult. Any PL/SQL programmers know that they can create any custom ZZZ-1234 error number to be returned by their code.You can use oracle error message utl_file.put_line to write to the alert log , and you can use this same approach to write customized error messages. Here we write a ZZZ-1234 custom error message to the Oracle alert log: -- ****************************************************** -- Set the utl_file_dir -- ****************************************************** alter system set utl_file_dir = ?:alert_loc?); -- ****************************************************** -- Open the alert log file for write access -- ****************************************************** utl_file.fopen(':alert_loc',?alertprod.log?,'W'); -- ****************************************************** -- Write the custom message to the alert log file-- ****************************************************** dbms_output.put_line('ZZZ-1234 This guy has bad credit'); But writing s custom alert message is only half the story, you must also document the error cause and error action within the Oracle error message utility (oerr).The oerr messages are placed into groups based on the prefix for the files. The facility information is read from the facility file located in $ORACLE_HOME/lib/facility.lis. zzz:custom:*:tns:rdbms:*: ora:rdbms:*: Mapping the facility files to the error messages In the case above the customized message zzz:custom points to a message file located at: $ORACLE_HOM