// Copyright (c) 1991, 1997, 1998, 1999 by the Oracle Corporation.  All rights reserved.
/
/
/ $Header: nmsus.msg 19-aug-99.13:51:47 xxu Exp $
/
/
/ NAME                                          
/   nmsus.msg                                            
/                                                     
/
/ FUNCTION
/   SNMP error message file, American English version.  This file contains
/   both generic SNMP messages, for any Oracle SNMP-manageable service,
/   and messages specific to the RDBMS subagent.
/
/
/ NOTES
/       Message text should be limited to a maximum of 76 characters.
/       Messages containing embedded % directives should not overrun
/       the 76 character limit unless they signal unusual errors
/       which do not occur as part of user applications.  For example,
/       startup errors and system-dependent errors can probably get
/       away with longer message text.
/
/
/       '/' at beginning-of-line for comments.
/       '//' at beginning-of-line for *Cause: And *Action: fields.
/
/       In all explanations below, the words "specified service" refer
/       to either the database subagent, OR other SNMP-capable service.
/
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
/
/
/ 
/ OWNER
/   Network Products Division
/
/ MODIFIED
/    xxu        09/15/99 - modify message 1018
/    xxu        08/19/99 - added message 1083
/    aholser    07/29/99 - bug 368311
/    syetchin   07/16/99 - Added the tag NLS_DO_NOT_TRANSLATE
/    syetchin   07/13/99 - Adding new messages
/    dnakos     06/14/99 - added message 1008
/    syetchin   04/07/98 - The message 01078 was broken. So correcting the brok
/    syetchin   03/16/98 -
/    syetchin   03/16/98 - Conform to new message format, for release 8.0.5
/    syetchin   03/16/98 - Added new messages for new events
/    dnakos     08/25/97 - add mesg 1014
/    dnakos     05/20/97 - add message 1013
/    dnakos     05/20/97 - add 'not in archivelog mode' message
/    jaysmith   04/17/97 - reinstate (again...) messages 315 & 316

/
///////////////////////////////////////////////////////////////////////////
/
///////////////////////////////////////////////////////////////////////////
///////////////////////////////////////////////////////////////////////////
// UI[00000,0050]
/ 0 - 50   Configuration and startup errors
/
/
///////////////////////////////////////////////////////////////////////////
/

00001, 00000, "Warning: %s unable to connect to SNMP master agent"
// *Cause: The specified service could not contact the SNMP master agent.
//  The master agent supported by Oracle
//  for this platform is not installed, or has not been started.  Messages
//  specific to this platform follow.  This is only a warning, and does
//  not prevent the agent from communicating with the console.
// *Action: consult Oracle documentation for your platform, and then make sure
//    that the correct SNMP master agent is installed and started.
/ 
00002, 00000, "%s failed to allocate memory for snmp.ora parameters" 
// *Cause: The specified service was unable to allocate enough memory to hold all
//    all the snmp.ora parameters.  This may indicate that the parameters
//    are too big, but more likely is a system error.
// *Action: Check system configuration and if possible, reduce the number of
//    the processes running.  If this does not fix the problem, report as a bug.
/
00003, 00000, "%s could not find snmp.ora file, or it was malformed"
// *Cause: The snmp.ora file could not be opened and read by the specified
//    service.  The location of this
//    file varies by platform, but normally it must be in the same directory as
//    other SQL*Net paramter files.
//    Detailed error messages may follow this one, if the problem could be
//    traced to a specific parameter.
// *Action: Consult the documentation for your platform, then create the file
//    in the proper location, and restart the program.
/
00004, 00000, "%s unable to register MIB or MIB row"
// *Cause: The specified service was unable to register its MIB or MIB row
//     with the master agent.
//    Detailed, platform-specific messages follow.
// *Action: Consult the documentation for SNMP on your platform.  If the messages
//    indicate that another program already has that MIB or MIB row registered,
//    you may want to terminate that program, then retry.
/
00005, 00000, "snmp.visibleservices parameter in snmp.ora is missing or empty"
// *Cause: The snmp.ora file does not contain a filled-in 
//     snmp.visibleservices parameter, or it's empty.
// *Action:  Edit or create the snmp.ora file and try again.
/
00006, 00000, "Required parameter %s was not found in snmp.ora"
// *Cause: The snmp.ora file did not contain the indicated parameter,
//   which was required.  Normally this would happen because one of the
//   services mentioned in snmp.visibleservices required one or more
//   detail parameters to be supplied, such as the one indicated.
// *Action: Edit or create the snmp.ora file and try again.
/
00007, 00000, "%s failed to allocate memory"
// *Cause: The specified service was unable to allocate memory.
// *Action:  Check system configuration and if possible, reduce the number of
//    the processes running.  If this does not fix the problem, report as a bug.
/
00008, 00000, "Environment variable %s is not set"
// *Cause: The specified environement variable is not found.
// *Action:  Make this environement variable available to the agent.
/
///////////////////////////////////////////////////////////////////////////
/
/ 51 - 75  Logging messages (these do not indicate an error)
/
/
///////////////////////////////////////////////////////////////////////////
/
00051, 00000,  "%s connected successfully to master agent" 
// *Cause: The subagent successfully to the master agent
// *Action: (none)
/
00052, 00000,  "Disconnected successfully from master agent"
// *Cause:  The subagent successfully logged off from the master agent.
//    This would normally be a part of the shutdown process.
// *Action: (none)
/
00053, 00000,  "Successfully registered all MIBs"
// *Cause: The subagent has completed its MIB or MIB row registrations
// *Action: (none)
/
00054, 00000, "Successfully deregistered all MIBs"
// *Cause: The subagent has completed its MIB or MIB row deregistrations.
//    This is normally part of the shutdown process
// *Action: (none)
/
00055, 00000, "Optional parameter %s was not found in snmp.ora; using default"
// *Cause: The snmp.ora file did not contain the indicated parameter,
//   which was optional.  The service used its default value for that
//   parameter, instead.
// *Action: If a value other than the default is desired, edit or create
//   the snmp.ora file and try again.
/
///////////////////////////////////////////////////////////////////////////
/
/ 200 - 250  Database subagent errors
/
/
///////////////////////////////////////////////////////////////////////////
00202, 00000, "Failure to connect to the database"
// *Cause: The database subagent was unable to connect to the database.
//    The detailed error message, which is documented in Oracle7 Server
//    manuals, follows.
// *Action: Consult Oracle7 Server documentation for the detailed error
//    message.
/

00203, 00000, "Error %s disconnecting from the database: %s"
// *Cause: The database subagent was unable to connect to the database,
//    and received the specified error number and text message.
//    The detailed error message, which is documented in Oracle7 Server
//    manuals, follows.
// *Action: Consult Oracle7 Server documentation for the detailed error
//    message.
/

00204, 00000, "Failure to listen on address %s"
// *Cause: The database subagent was unable to listen on the specified
//    TNS address, possibly because another instance of the database agent
//    has already claimed the address.  If more information is
//    available, it will appear under this error.
// *Action: If another instance of the database agent is already
//    running, either allow it to continue running or bring it down
//    and try again.  Otherwise, see "Actions" for the other TNS errors.
/

00205, 00000, "Failure to connect to database %s with username/password %s"
// *Cause: Connection to the specified database failed because either the
//    listener could not resolve the database name or the database user
//    credentials failed authentication.
// *Action: Verify the database SID is correctly specified and configured
//    for the listener, and that the database username and password are
//    valid.	
/

00206, 00000, "Failure to retrieve characterset information from database %s"
// *Cause: the characterset information is not available
// *Action: check if nls_database_parameters table exists.
/

///////////////////////////////////////////////////////////////////////////
/
/ 250 - 275  Database subagent log messages
/    (these are informational only, and do not indicate an error)
/
///////////////////////////////////////////////////////////////////////////
00250, 00000,  "Database subagent started"
// *Cause: The database subagent started successfully.
// *Action:  (none)
/
00251, 00000,  "Database subagent beginning shutdown process" 
// *Cause: The database subagent has received the shutdown command,
//    and is processing it.
// *Action:  (none)
/
00252, 00000,  "Database subagent shutting down now"
// *Cause: The shutdown process has completed.  This should be the last
//    message output.
// *Action: (none)
/
00253, 00000, "Connected successfully to database %s"
// *Cause: The subagent successfully logged on to the specified database.
//   This message may also be output if the database goes down and comes
//   back up.
// *Action:  (none)
/
00254, 00000,  "Disconnected successfully from database %s"
// *Cause:  The subagent successfully logged off from the specified database.
//    This would normally be a part of the shutdown process.
// *Action: (none)
/
00255, 00000,  "Database %s became unreachable; trap sent"
// *Cause: The specified database became inaccessible, and the subagent
//    then sent an SNMP trap.  This may not indicate a problem, since the database
//    may have been shut down deliberately (the subagent is unable to distinguish
//    the cause of the inaccessibility).  
//    The destination(s) of the trap are normally set as part of
//    master agent configuration.  Consult the SNMP documentation for your platform.
// *Action: Consult the Oracle7 Server documentation, if the shutdown was not
//    deliberate.  If traps are not being received at your management station(s),
//    consult the platform SNMP documentation and ensure that the management
//    station's address is configured properly for the master agent.
/
///////////////////////////////////////////////////////////////////////////
/
/ 301 - 350   errors in operation of the agent
/
/
///////////////////////////////////////////////////////////////////////////
00301, 00000,  "Failed to initialize MIB file"
// *Cause:  The text files which describe the SNMP MIBs were not found
//    in the correct location
// *Action: Check the agent's installation and install the correct files.
/
00302, 00000,  "Failed to initialize user queue"
// *Cause:  The agent was unable to initialize the file which holds
//   data about users.  Following messages may provide more details.
// *Action: Check detail messages and call Customer Support if a
//    solution cannot be found.
/
00303, 00000,  "Failed to initialize event registration queue"
// *Cause:  The agent was unable to initialize the file which holds
//   data about event registrations.  
//   Following messages may provide more details.
// *Action: Check detail messages and call Customer Support if a
//    solution cannot be found. 
/
00304, 00000,  "Failed to initialize job queue"
// *Cause:  The agent was unable to initialize the file which holds
//   data about jobs..  Following messages may provide more details.
// *Action: Check detail messages  and call Customer Support if a
//    solution cannot be found.
/
00305, 00000,  "Failed to initialize event occurrence queue"
// *Cause:  The agent was unable to initialize the file which holds
//   data about event occurrences.  
//   Following messages may provide more details.
// *Action: Check detail messages  and call Customer Support if a
//    solution cannot be found.
/
00306, 00000,  "Failed to initialize job status queue"
// *Cause:  The agent was unable to initialize the file which holds
//   data about job statuses.  Following messages may provide more details.
// *Action: Check detail messages  and call Customer Support if a
//    solution cannot be found.
/
00307, 00000,  "Failed to initialize RPC layer"
// *Cause:  The Remote Procedure Call layer could not be initialized.
//    Following messages may provide more details.
// *Action: Check detail messages and call Customer Support if a
//    solution cannot be found.
/
00308, 00000,  "Failed to listen on address:  another agent may be running"
// *Cause:  The agent's connection cache could not be initialized.
//    This is frequently caused by having the agent already running
//     (only one copy can be running at a time)
// *Action: If another agent is running, bring it down first.
/
00309, 00000,  "Failed to initialize internal address"
// *Cause:  The agent's address for internal RPC's could not be
//    initialized.  This may be because another copy of the agent
//     is already running.
// *Action: if another copy of the agent is already running, kill
//   both agents and try again.
/
00310, 00000,  "Failed to initialize auxiliary address"
// *Cause: The agent's address for file transfer RPC's could not be
//    initialized.  This may be because another copy of the agent
//     is already running
// *Action: if another copy of the agent is already running, kill
//   both agents and try again.
/
00311, 00000,  "Failed to initialize language ID"
// *Cause:  The agent's language ID could not be initialized.
// *Action: Make sure the language id environment variable is correct 
//     for the agent.
/
00312, 00000,  "Error opening file %s"
// *Cause:  The agent was unable to open the specified file
// *Action: Check that the directory exists, and that the agent has
//   the required permissions to write the file.
/
00313, 00000,  "Unable to access directory %s "
// *Cause:  The agent was unable to access the specified directory,
//    or it does not exist
// *Action: Check that the directory exists, and that the agent has
//   the required permissions to write into it.
/
00314, 00000,  "dbsnmp.spawnaddress parameter in snmp.ora missing"
// *Cause: The dbsnmp.spawnaddress parameter is required from 7.3.2 1
//    onward.  This must be a different address from dbsnmp.address,
//    and is used for file transfer and Oracle Software Manager
// *Action: Add the parameter.
/
00315, 00000,  "Failed to create tcl package index"
// *Cause:  The tcl package index could not be created"
// *Action: Make sure all the share libraries in the directory
//   $ORACLE_HOME/network/agent/library are correct.
/
00316, 00000,  "Failed to initialize init.tcl"
// *Cause:  The tcl7.5 init.tcl file could not be initialized"
// *Action: Make sure you have a correct version of init.tcl in
//   $ORACLE_HOME/network/agent/tcl.
/

///////////////////////////////////////////////////////////////////////////
/
/ 351 - 360  Messages related to encryption of the agent's files
/
/
///////////////////////////////////////////////////////////////////////////

00351, 00000,  "Encryption key supplied is not the one used to encrypt file"
// *Cause:  If a key was given at startup, it does not match the key that
//    was last used.  If no key was given at startup, then the file was
//    encrypted with a non-default key, and that key must be supplied.
// *Action:  There is no way for Oracle to recover the key, i.e. it is not
//   hidden anywhere.  If the user cannot remember it, then he should save
//   the files in hopes that the key will be remembered later.
/
00352, 00000,  "Password file not found or not readable"
// *Cause:  This message appears on startup if a "password_file="
//    argument was typed on the command line, but the indicated file
//    was not found, could not be read, or did not contain a line of
//    text. (for security reasons, the name of the password
//    file is not echoed)
// *Action: Enter the correct file name and ensure that it has at least
//    one text line of at least 6 characters.
/
00355, 00000,  "Password must be at least 6 characters"
// *Cause: (see 352) The user has typed in a key that is too short.
// *Action: Enter between 6 and 8 characters
/
///////////////////////////////////////////////////////////////////////////
// UI[0361,0370]
/ 361 - 370   errors in operation of the unsolicited event executable
/
/
///////////////////////////////////////////////////////////////////////////
00361, 00000,  "oemevent invoked with insufficient arguments"
// *Cause:  oemevent was called with too few arguments.
//   It should be invoked as
//        oemevent <event name> <object> <severity> <message> [<result>...]
//   where <event name> is a legal OEM event name,
//         <object> is the name  of the service or resource to which the
//                  event applies,
//         <severity> is one of "alert", "warning", or "clear",
//         <message> is the text of the error message to be conveyed to
//                  the OEM console, and
//         <result> is zero or more strings to be returned as the "results"
//                  of the event.
// *Action:  Invoke oemevent with appropriate arguments.
/
00362, 00000,  "Event name not valid"
// *Cause:  The first argument passed to oemevent is not a valid
//    OEM event name.
// *Action:  Invoke oemevent with a legal OEM event name.
/
00363, 00000,  "Severity level not valid"
// *Cause:  The third argument passed to oemevent is not a valid
//    OEM event severity level (one of "alert", "warning", or "clear")
// *Action:  Invoke oemevent with a legal OEM event severity level.
/
00364, 00000,  "oemevent failed to contact agent"
// *Cause:  oemevent was unable to establish a connection with the
//    agent's Comm process.
// *Action:  Check that the agent Comm process is up.
//           Check that the agent Comm process is acceping connections.
//           Check that the agent's address in snmp.ora is correct.
/
00365, 00000,  "ReportEvent RPC to agent failed"
// *Cause:  oemevent was unable to send the ReportEvent RPC to the
//    agent's Comm process.
// *Action:  Check that the agent Comm process is up.
//           Try running oemevent again.
/

///////////////////////////////////////////////////////////////////////////
// UI[0600,0799]
/ 600-799   Job and event errors.  These can be sent back to the console
/   when users run jobs or register events..
/
///////////////////////////////////////////////////////////////////////////
/
00600, 00000, "Insufficient or incorrect arguments"
// *Cause:  A predefined event or job was invoked with fewer arguments
//    than required, or with the wrong types of arguments.
// *Action: Check the documentation and try again.  If problem continues,
//   check that the installed versions of agent and console match.
/
00601, 00000, "Job failed due to agent restart while it was running"
// *Cause:  The job was running when the agent was shut down.  The job
//    was not completed.
// *Action: None.  If the job was an immediate job, resubmit it.
/
00602, 00000, "Job failed because a required file could not be opened."
// *Cause:  The job tried to open a file but was unable to do so.
// *Action: Check available space and permissions of the ORACLE_HOME\net80\agent
//    directory and correct any problems discovered.
/
00603, 00000, "The job did not write any output."
// *Cause:  There was no output from the job.
// *Action: Check available space and permissions of the ORACLE_HOME\net80\agent
//    directory and the directories pointed to by TEMP and TMP, and correct any
//    problems discovered.
/
00604, 00000, "Could not access agent queue file."
// *Cause:  An agent queue file could not be accessed.
// *Action: Check available space and permissions of the ORACLE_HOME\net80\agent
//    directory and correct any problems discovered.
/
00605, 00000, "Could not fork or create job process."
// *Cause:  The job process could not be created.
// *Action: Check the user authentication and system resource limitations.
/
00606, 00000, "User authentication failed."
// *Cause:  The user failed authentication.
// *Action: Check user name, password and permissions.
/
00607, 00000, "Out of memory."
// *Cause:  The system is out of memory.
// *Action: Decrease system memory usage by shutting down unnecessary programs
//     or services. Check system for programs that are consuming system memory
//     without releasing it.
/
00608, 00000, "Operating system resource shortage."
// *Cause:  The system is running short of a critical resource.
// *Action: Decrease system workload.
/
00609, 00000, "Output truncated"
// *Cause:  The job output exceeded maximum allowed.
// *Action: No action required.
/



///////////////////////////////////////////////////////////////////////////
/
/ 900 - 999  Log messages.  These appear only in the agent's log file and do not
/   necessarily indicate an error.  Messages that appear in the user interface
/   are listed separately in other messages files.
/
///////////////////////////////////////////////////////////////////////////
/
00900, 00000, "Registered event %s for %s on %s;  id=%s"
// *Cause: Indicates that the agent has registered the specified event
//    for the user on the service, and its internal id number is as given.
// *Action: none
/

00901, 00000, "Event %s duplicates existing registration;  rejected"
// *Cause:  The Registration was rejected because it was identical to an existing one.
// *Action: none
/

00902, 00000, "Cancelling event registration, id %s"
// *Cause: The agent is about to cancel an event registration.
// *Action: none
/

00903, 00000, "Delivered an occurrence of event %s to %s"
// *Cause: The agent delivered a report of an event occurring, which
//    was registered by the specified user.
// *Action: none
/

00904, 00000, "Job %s has expired"
// *Cause: The specified job number's schedule has expired
// *Action: none
/

00905, 00000, "Executing job %s"
// *Cause: The specified job number is being executed by the agent
// *Action: none
/

00906, 00000, "Cancelling job %s"
// *Cause: the specified job is being cancelled at the console's request
// *Action: none
/

00907, 00000, "Running fixup job %s for event %s"
// *Cause: The specified fixup job is being run, since its event occurred
// *Action:
/

00908, 00000, "Shutting down normally"
// *Cause: a dbsnmp_stop command was received from lsnrctl
// *Action: none
/

00909, 00000, "Restarting Comm process"
// *Cause: The Worker process has detected no response from the Comm
//     process for the timeout period, and has restarted it.
//     This may or may indicate an error.  If it happens 
//     repeatedly, it may indicate communications problems with the 
//     the console
// *Action:  Inspect trace file for the Comm process, if tracing is on.
//     If not, and this appears repeatedly, stop agent, turn on tracing,
//     and restart it.
/

00910, 00000, "Scheduled job %s for %s with schedule %s; id=%s"
// *Cause: Indicates that a request to schedule the specified job was
//   received from the console and the job was scheduled, with an 
//   an internal id as given.
// *Action:  none
/

00911, 00000, "Cancelling job %s for user %s"
// *Cause: The specified job id was cancelled by the console
// *Action: none
/

00912, 00000, "Delivered status for job %s to user %s"
// *Cause: The status of a completed job was delivered to the console
// *Action: none
/

00913, 00000, "Registered user %s with address %s, language %s; id=%s"
// *Cause: The user was registered with the specified parameters.  The
//   internal id of the user is also given.
// *Action: none
/

00914, 00000, "Job %s succeeded"
// *Cause:  the specified job id has been run and reported success
// *Action: none
/

00915, 00000, "Job %s failed, error code=%s"
// *Cause: the specified job id failed with the error code given.  
//   Complete output is returned to the console
// *Action: none
/

00916, 00000, "File transfer request for %s from %s"
// *Cause: The specified file was fetched from the specified address
// *Action: none
/


///////////////////////////////////////////////////////////////////////////
// UI[1000,1099]
/ 1000 - 1099  Errors. All of these may appear on the console as error
/    messages from the agent.
/ 
/    These may or may not indicate a bug in the software;
/    in certain cases user actions may be able to clear the problem
/
/
///////////////////////////////////////////////////////////////////////////
/

01001, 00000, "Event file does not exist"
// *Cause: The specified event could not be registered because the
//    .tcl file that implements it does not exist on the agent.
// *Action: Check the installation of the agent, and if necessary
//   reinstall the correct version.
/
01002, 00000, "Invalid service name"
// *Cause: On an event registration, a database or service name was
//    specified which the agent does not monitor.
// *Action: Check configuration files on the console, and snmp.ora
//    file on the agent.
/
01003, 00000, "Failed to lookup user data"
// *Cause: For an event, a user was specified who has
//   not been registered with the agent.  Possibly the user registration
//   file has been inadvertently deleted.
// *Action:  Logging off from the console and logging back in may fix
//   the problem.
/
01004, 00000, "Invalid user language"
// *Cause:  For an event registration, the language string which was
//   registered for the user was invalid.  The language comes from the
//   the NLS_LANG environment variable on the console machine.
// *Action: Check the setting of NLS_LANG.  If necessary, correct, log off
//   from the console and log back in.
/
01005, 00000, "Event script %s evaluation failed"
// *Cause:  The Tcl script for the specified event failed to evaluate.
//    The specific error found by Tcl is returned to the console.
// *Action: Check the results returned to the console;  it may be that
//    incorrect arguments were provided to the event, or the catsnmp.sql
//    script that gives the agent permission to execute the predefined
//    events has not been run.
/
01006, 00000, "Job file %s does not exist"
// *Cause: The specified job could not be registered because the
//    .tcl file that implements it does not exist on the agent.
// *Action: Check the installation of the agent, and if necessary
//   reinstall the correct version.
/
01007, 00000, "No segment was found that satisified specified event parameters"
// *Cause: The specified segment could not be found in the database.
// *Action: Check the sql statement, and if necessary correct the 
//   event or job parameters.
/
01008, 00000, "Parameter does not exist"
// *Cause: The specified parameter could not be found in the v$sysstat table.
// *Action: Check the sql statement, and if necessary correct the 
//   event or job parameters.
/
01009, 00000, "Failed to execute the user defined program"
// *Cause: The specified user defined program could not be executed on the
//     agent.
// *Action: Make sure the user defined program exists and can be executed 
//     by the agent.
/
01010, 00000, "svrmgrl or sqldba does not exist"
// *Cause: The svrmgrl or sqldba executable does not exist.
// *Action: Make sure either svrmgrl or sqldba can be invoked by the agent.
/
01011, 00000, "Invalid date format"
// *Cause: The date format is not in mm/dd/yy format.
// *Action: Make sure the date format is in mm/dd/yy.
/
01012, 00000, "Database is operating in NOARCHIVELOG mode.\nAs a result, this event will not be executed."
// *Cause: The database is operating in NOARCHIVELOG mode.
// *Action: Alter the database archive log mode to on.
/
01013, 00000, "sqlplus does not exist"
// *Cause: The sqlplus executable does not exist.
// *Action: Make sure either svrmgrl or sqldba can be invoked by the agent.
/
01014, 00000, "Tablespace does not exist or has no free extents"
// *Cause: No free extents were found for the specified tablespace.
// *Action: Check the sql statement, and if necessary correct the 
//   event or job parameters.
/
01015, 00000, "Select unexpectedly returned no rows"
// *Cause: The sql statement returned no rows
// *Action: Check the sql statement
/
01016, 00000, "DML_LOCKS is set to 0.  As a result, this event\nwill not be executed."
// *Cause: DML_LOCKS equalled 0.
// *Action: Check the sql statement
/
01017, 00000, "Automatic archiving has been disabled.  As a\nresult, this event will not be executed."
// *Cause: LOG_ARCHIVE_START equalled FALSE.
// *Action: Check the sql statement
/
01018, 00000, "View sys.dba_blockers does not exist.  Please verify catblock.sql has been run."
// *Cause: View SYS.DBA_BLOCKS does not exist.
// *Action: Verify $ORACLE_HOME\rdbms\admin\catblock.sql has been run.
/
01019, 00000, "The partitions for index %s.%s could not be found"
// *Cause: The index partitions associated with a particular indexed partition could not be found.
// *Action: Check the sql statement
/
01020, 00000, "Tablespace does not exist or at least one of\nits datafiles has been defined with autoextend enabled."
// *Cause: At least one of the tablespace's datafiles has autoextend enabled.
// *Action:
/
01021, 00000, "SQL Statement returned more than one row or column."
// *Cause: The SQL statement specified for collecting the data point does not return a single value as it is expected.
// *Action: Check the sql statement
/


//  Secondary additional script failure messages
//

01075, 00000, "getcpuutil failed"
// *Cause: A call to getcpuutil failed unexpectedly
// *Action: none
/
01076, 00000, "getpaging failed"
// *Cause: A call to getpaging failed unexpectedly
// *Action: none
/
01077, 00000, "Invalid disk name"
// *Cause: On an event registration, it was discovered an invalid disk
//    name was specified; for example, a disk name of '*'.
// *Action: Make sure an explicit disk name was specified for the event.
/
01078, 00000, "diskusage  failed"
// *Cause: A call to diskusage failed unexpectedly
// *Action: none
/
01079, 00000, "getlsnrstatus failed"
// *Cause: A call to getlsnrstatus failed unexpectedly
// *Action: none
/
01080, 00000, "There were %s numbers in ORA-01578"
// *Cause: Discovered more numbers in error message than expected
// *Action: none
/
01081, 00000, "Duration not greater than 0"
// *Cause: Duration was found not to be greater than 0
// *Action: none
/
01082, 00000,  " The Agent does not have this service in it's SERVICES.ORA"
// *Cause: The Console and Agent services are out of sync.
// *Action: Drop the Agent node from the Navigator Pane and re-discover the node.
/
01083, 00000,  "No priamry archive destinations.\nAs a result, this event will not be executed."
// *Cause: Oracle 8i supports standby databases as archive destinations.
//         If all valid archive destinations are standby databases,
//         event registration will fail.
// *Action: None
/

///////////////////////////////////////////////////////////////////////////
// UI[1100,1199]
/ 1100 - 1199  Confirmation messages. All of these may appear on the console 
/    as confirmation messages or job report.
/ 
/    These do not indicate a bug in the software.
/
/
///////////////////////////////////////////////////////////////////////////
/
01101, 00000, "The job completed successfully"
// *Cause: The specified job has been executed successfully
// *Action: None.
/
01102, 00000, "Database Statistics Daily Report"
// *Cause: Database historical job report
// *Action: None.
/
01103, 00000, "System Statistics"
// *Cause: Database historical job report
// *Action: None.
/
01104, 00000, "Library Cache Miss Ratio"
// *Cause: Database historical job report
// *Action: None.
/
01105, 00000, "Data Dictionary Miss Ratio"
// *Cause: Database historical job report
// *Action: None.
/
01106, 00000, "Buffer Cache Hit Ratio"
// *Cause: Database historical job report
// *Action: None.
/
01107, 00000, "Physical I/O"
// *Cause: Database historical job report
// *Action: None.
/
01108, 00000, "Sort (memory vs disk)"
// *Cause: Database historical job report
// *Action: None.
/
01109, 00000, "Table Scan (long vs short)"
// *Cause: Database historical job report
// *Action: None.
/
01110, 00000, "Users logged on"
// *Cause: Database historical job report
// *Action: None.
/
01111, 00000, "Active Users"
// *Cause: Database historical job report
// *Action: None.
/
01112, 00000, "SGA Size (in Kbytes)"
// *Cause: Database historical job report
// *Action: None.
/
01113, 00000, "UGA Size (in Kbytes)"
// *Cause: Database historical job report
// *Action: None.
/
01114, 00000, "Tablespace Statistics"
// *Cause: Database historical job report
// *Action: None.
/
01115, 00000, "Allocated (in Kbytes)"
// *Cause: Database historical job report
// *Action: None.
/
01116, 00000, "Used (in Kbytes)"
// *Cause: Database historical job report
// *Action: None.
/
01117, 00000, "Biggest Chunk (in Kbytes)"
// *Cause: Database historical job report
// *Action: None.
/
01118, 00000, "No of I/O"
// *Cause: Database historical job report
// *Action: None.
/
01119, 00000, "Historical data was loaded into database"
// *Cause: Database historical job report
// *Action: None.
/
01120, 00000, "The max extent size was changed for %s %s."
// *Cause: Database change max extent fixit job
// *Action: None.
/
01121, 00000, "The next extent size was changed for %s %s."
// *Cause: Database change next extent fixit job
// *Action: None.
/
///////////////////////////////////////////////////////////////////////////
//NLS_DO_NOT_TRANSLATE [1200,1999]
/ 1200 - 1999  Internal errors.  Report as a bug.
/
/
///////////////////////////////////////////////////////////////////////////
/
01200, 00000, "Failed to locate user %s. Deleting an occurrence of event %s"
// *Cause: 
// *Action:  Report to Oracle Worldwide Support.
/
01201, 00000, "Could not create Tcl interpreter"
// *Cause: On an event registration, the agent was unable to create the
//   the Tcl interpreter to process the event.
// *Action: Report to Oracle Worldwide Support.
/
///////////////////////////////////////////////////////////////////////////
// UI[5000,5999]
/ 5000 - 5999  Errors reserved for the console group.
/
/
///////////////////////////////////////////////////////////////////////////
/
05001, 00000, "Unable to Start Hot Backup"
// *Cause: Call to a SQL statement failed 
// *Action:
/
05002, 00000, "An offline backup is in progress"
// *Cause: An offline backup is in progress
// *Action:
/
05003, 00000, "Tablespace is offline"
// *Cause: Tablespace is offline
// *Action:
/
05004, 00000, "Unable to End Hot Backup"
// *Cause: Call to a SQL statement failed 
// *Action:
/
05005, 00000, "Unable to Start Cold Backup"
// *Cause: Call to a SQL statement failed
// *Action:
/
05006, 00000, "Offline backup about to take place"
// *Cause: Offline backup about to take place 
// *Action:
/
05007, 00000, "Unable to End Cold Backup"
// *Cause: Call to a SQL statement failed
// *Action:
/
05008, 00000, "Database not started"
// *Cause: Database not started 
// *Action:
/
05009, 00000, "Logon Failed"
// *Cause: Unable to logon 
// *Action:
/
05010, 00000, "Database is running - please shutdown"
// *Cause: Database is running and needs to be shutdown 
// *Action:
/
05011, 00000, "Database is not running - please start it"
// *Cause: Database is not running and needs to be started
// *Action:
/
05012, 00000, "Backing up Tablespace %s"
// *Cause: User information 
// *Action:
/
05013, 00000, "Start: Backing up Tablespace %s"
// *Cause: User information
// *Action: 
/
05014, 00000, "Done: Backing up Tablespace %s"
// *Cause: User information
// *Action: 
/
05015, 00000,  "Start of main script"
// *Cause: User information
// *Action: 
/
05016, 00000,  " Connect str.	=  %s"
// *Cause: User information
// *Action:
/ 
05017, 00000,  " Tablespaces	= %s"
// *Cause: User information
// *Action: 
/
05018, 00000,  " Datafile#	= %s"
// *Cause: User information
// *Action: 
/
05019, 00000,  " Datafiles	= %s"
// *Cause: User information
// *Action: 
/
05020, 00000,  " Destination	=  %s"
// *Cause: User information
// *Action: 
/
05021, 00000,  " Tablespace state =  %s"
// *Cause: User information
// *Action: 
/
05022, 00000,  " Database state	=  %s"
// *Cause: User information
// *Action: ls
/
05023, 00000,  " JobID		=  %s"
// *Cause: User information
// *Action: ls
/


