Server Manager Messages and Codes
This chapter lists the messages generated by Server Manager. For each message, the probable cause and corrective action are given.
00100-00199: Server Manager Line Mode Parsing Messages
MGR-00100 invalid SPOOL file name
| Cause: | When using the SPOOL command, you entered an invalid file specification or the name of a file that already exists. | |
| Action: | Specify a valid name for a file that does not currently exist. | |
MGR-00101 extraneous text at end of command
| Cause: | There were unrecognized commands or other text on the command line. | |
| Action: | Issue the command without the extraneous text. | |
MGR-00102 missing LOG keyword
| Cause: | The LOG keyword was missing from the ARCHIVE LOG command. | |
| Action: | Correct the syntax of the command, then issue the command again. | |
MGR-00103 illegal ARCHIVE LOG option
| Cause: | An option specified was not LIST, STOP, START, NEXT, ALL, a number, or a filename in the ARCHIVE LOG command. | |
| Action: | Correct the syntax of the command, then issue the command again. | |
MGR-00104 illegal RECOVER option
| Cause: | You specified an invalid option. Valid options for the RECOVER command are DATABASE, MANUAL, UNTIL, TABLESPACE, or DATAFILE. | |
| Action: | Correct the syntax of the command, then issue the command again. | |
MGR-00105 invalid INSTANCE name
| Cause: | An invalid SQL*Net service name was specified for the instance name. | |
| Action: | Refer to your Oracle platform-specific documentation for a complete description of specifying SQL*Net service names. | |
MGR-00106 invalid ECHO switch
| Cause: | An invalid option for the SET ECHO command was specified. | |
| Action: | Use either ON or OFF as an option for the SET ECHO command. | |
MGR-00107 invalid TERMOUT switch
| Cause: | An invalid option for the SET TERMOUT command was specified. | |
| Action: | Use either ON or OFF as an option for the SET TERMOUT command. | |
MGR-00108 invalid TIMING switch
| Cause: | An invalid option for the SET TIMING command was specified. | |
| Action: | Use either ON or OFF as an option for the SET TIMING command. | |
MGR-00109 invalid CYCLE value
| Cause: | An invalid value for the SET CYCLE command was specified. | |
| Action: | The SET CYCLE command requires a value between 15 seconds and 99:99 (min:sec), inclusive. | |
MGR-00110 illegal SET option
| Cause: | An invalid option for the SET command was specified. | |
| Action: | Correct the syntax of the SET command and issue the command again. See the Oracle Server Manager User's Guide for the correct syntax. | |
MGR-00111 illegal SHOW option
| Cause: | An invalid option for the SHOW command was specified. | |
| Action: | Correct the syntax of the SHOW command and issue the command again. See the Oracle Server Manager User's Guide for the correct syntax. | |
MGR-00113 invalid PFILE name
| Cause: | Server Manager does not recognize the file specified by the PFILE option. | |
| Action: | Specify a legal parameter file. | |
MGR-00114 invalid database name
| Cause: | The specified database name is not recognized. | |
| Action: | Specify a legal database name. | |
MGR-00115 unexpected end of command
| Cause: | An option was specified without any arguments. | |
| Action: | Correct the syntax of the command and enter the command again with the appropriate arguments for options that require values. | |
MGR-00116 illegal SHUTDOWN option
| Cause: | An option was specified that was not NORMAL, IMMEDIATE, or ABORT for the SHUTDOWN command. | |
| Action: | Correct the syntax of the command, then issue the command again. | |
MGR-00117 invalid tablespace name
| Cause: | The specified tablespace name was not recognized. | |
| Action: | Specify a legal tablespace name. | |
MGR-00118 invalid process identifier or statistics class
| Cause: | Something other than a number for a process identifier, or an invalid class was specified after the MONITOR STATISTICS command. | |
| Action: | Specify only numbers as process identifiers, or specify a valid class for the MONITOR STATISTICS command. | |
MGR-00119 illegal STARTUP option
| Cause: | An option was specified that was not DBA, PFILE, EXCLUSIVE, SHARED, MOUNT, OPEN, RECOVER, or NOMOUNT for the STARTUP command. | |
| Action: | Correct the syntax of the command, then issue the command again. | |
MGR-00120 invalid STOPONERROR switch
| Cause: | An invalid option was specified for the SET STOPONERROR command. | |
| Action: | Use either ON or OFF as an option for the SET STOPONERROR command. | |
MGR-00121 illegal MONITOR option
| Cause: | An illegal option was specified for the MONITOR command. | |
| Action: | Correct the syntax of the MONITOR command in the Oracle Server Manager User's Guide and issue the command again. | |
MGR-00122 invalid SET numeric parameter
| Cause: | A character or an invalid value was specified when a number was expected as a value for a SET command option. | |
| Action: | Correct the syntax of the command, use an appropriate number for the option and issue the command again. | |
MGR-00123 invalid tablespace name list
| Cause: | An invalid string was specified as one of the values in the list of tablespaces in the ARCHIVE LOG command. For example, an empty string is an invalid string. | |
| Action: | Correct the syntax of the command, use valid tablespace names for all names in the list, then enter the command again. | |
MGR-00124 invalid ARCHIVE destination
| Cause: | The specified ARCHIVE destination was not recognized. | |
| Action: | Specify a legal ARCHIVE destination. See the Oracle Server Manager User's Guide for the correct syntax. | |
MGR-00125 integer value overflow
| Cause: | A numeric value was specified that was too large. | |
| Action: | Use a smaller number. | |
MGR-00127 invalid combination of STARTUP options
| Cause: | The specified options of the STARTUP command cannot be used simultaneously. | |
| Action: | Correct the syntax of the STARTUP command and issue the command again. See the Oracle Server Manager User's Guide for options that can be used with STARTUP. | |
MGR-00128 invalid DEBUG switch
| Cause: | The DEBUG switch was not recognized. | |
| Action: | Specify a legal DEBUG switch. See the Oracle Server Manager User's Guide for the correct syntax. | |
MGR-00129 value out of range (1 - num)
| Cause: | The specified value was out of range. The valid range is given by the error message. | |
| Action: | Use a number within the range specified by this error. | |
MGR-00131 invalid ARCHIVE TO device
| Cause: | The specified ARCHIVE TO device was not recognized. | |
| Action: | Specify a legal ARCHIVE TO device. See the Oracle Server Manager User's Guide for the correct syntax. | |
MGR-00132 null hostname/password specified
| Cause: | "hostname/password" was not specified. | |
| Action: | Specify the correct "hostname/password". | |
MGR-00133 invalid datafile list
| Cause: | An invalid string was entered as one of the values in the list of datafiles in the ARCHIVE LOG command. For example, an empty string is an invalid string. | |
| Action: | Correct the syntax of the command, use valid datafile names for all names in the list, then enter the command again. | |
MGR-00134 invalid AUTORECOVERY switch
| Cause: | An invalid option was specified for the SET AUTORECOVERY command. | |
| Action: | Use either ON or OFF as options for the SET AUTORECOVERY command. | |
MGR-00136 bad variable specification
| Cause: | A variable was incorrectly specified using the VARIABLE command. | |
| Action: | Correct the syntax of the command, then issue the command again. | |
MGR-00137 syntax error in PL/SQL Block
| Cause: | The PL/SQL block contains a syntax error. | |
| Action: | Correct the syntax error. | |
MGR-00139 invalid ALTER DATABASE option
| Cause: | The specified ALTER DATABASE option was not recognized. | |
| Action: | Specify a legal option. See the Oracle Server Manager User's Guide for the correct syntax. | |
MGR-00140 invalid COMPATIBILITY switch
| Cause: | The specified COMPATIBILITY switch was not recognized. | |
| Action: | Specify a legal COMPATIBILITY switch. See the Oracle Server Manager User's Guide for the correct syntax. | |
MGR-00141 invalid RETRIES value
| Cause: | The specified RETRIES value was not recognized. | |
| Action: | Specify a legal RETRIES value. See the Oracle Server Manager User's Guide for the correct syntax. | |
MGR-00142 cannot recognize object type, owner, or name
| Cause: | The specified object type, owner, or name was not recognized. | |
| Action: | Specify a legal object type, owner, or name. | |
MGR-00143 variable "name" has not been defined
| Cause: | The specified variable was not recognized. | |
| Action: | Specify an existing variable. You can use the PRINT command to display currently defined variables. | |
MGR-00144 invalid object type for DESCRIBE
| Cause: | The specified object type was not TABLE, VIEW, or PROCEDURE. | |
| Action: | Check that the object is a table, view, or procedure. If so, check that you specified the correct name and try again. If not, you cannot DESCRIBE the object. | |
MGR-00145 invalid object name for DESCRIBE
| Cause: | The specified table, view, stored procedure, or function was not recognized. | |
| Action: | Check your spelling and be sure to specify an existing table, view, stored procedure, or function. | |
MGR-00146 invalid HISTORY value
| Cause: | The specified HISTORY value was not recognized. | |
| Action: | Specify a legal HISTORY value. See the Oracle Server Manager User's Guide for the correct syntax. | |
MGR-00147 invalid LINES value
| Cause: | The specified LINES value was not recognized. | |
| Action: | Specify a legal LINES value. See the Oracle Server Manager User's Guide for the correct syntax. | |
00300-00399: Server Manager Line Mode Execution Messages
MGR-00300 internal error code, argument: [num]
| Cause: | You have encountered an internal error in Server Manager. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-00301 cannot SET INSTANCE while connected to a database
| Cause: | You used SET INSTANCE while you were connected to a database. | |
| Action: | Disconnect from the database before using SET INSTANCE if you wish to change the current instance. | |
MGR-00302 not connected to a database
| Cause: | You must be connected to the database for the requested operation. | |
| Action: | Connect to the database using a valid username and password before retrying the operation. | |
MGR-00304 input file I/O error [num]; input aborted
| Cause: | A command file used as input to Server Manager is corrupted or invalid. | |
| Action: | Check the file before trying the operation again. | |
MGR-00305 command size exceeds internal buffer size (num)
| Cause: | The SQL statement size exceeds Server Manager's buffer size. | |
| Action: | Shorten the SQL statement by removing extra blanks or by converting intermediate statements to views. | |
MGR-00306 monitor cycle interval time out of range (1 - num)
| Cause: | You entered an invalid number for the cycle interval. | |
| Action: | Enter a value between 15 seconds and 99:99 (min:sec), inclusive, for the cycle interval. | |
MGR-00307 cannot open spool file "name"
| Cause: | Server Manager tried to open a spool file after you entered SPOOL <filename>, but could not open the file. Possible causes are a lack of disk space or inadequate privileges to create a file. | |
| Action: | Determine why Server Manager could not create a new file and try the operation again. | |
MGR-00308 no spool file opened
| Cause: | You entered SPOOL OFF, but you were not spooling at the time, so there was no file to close. | |
| Action: | If you wish to capture session output, first use the SPOOL command to open a file, then enter your commands before closing the file with SPOOL OFF. | |
MGR-00309 cannot close spool file "name"
| Cause: | SPOOL OFF could not close the currently open spool file. | |
| Action: | Check for operating system circumstances that are preventing the file from being closed. | |
MGR-00310 cannot open parameter file "name"
| Cause: | Server Manager cannot locate or open the file specified by the PFILE option, either because the file does not exist or because Server Manager has insufficient privileges to open the file. | |
| Action: | Make sure the file exists in a location expected by Server Manager and can be opened. | |
MGR-00311 data exceeds internal buffer size
| Cause: | The results returned by a SQL query exceed the size of Server Manager's internal buffer. | |
| Action: | Use the SET command to increase MAXDATA or decrease ARRAYSIZE. | |
MGR-00312 invalid pid range num num
| Cause: | You entered an invalid range. Ranges must be specified using the lower number first. Note: If a valid range includes any currently active process identification numbers, the range will be accepted. | |
| Action: | Enter a valid range. | |
MGR-00313 no active processes to monitor
| Cause: | You specified process identification numbers that do not correspond to any currently active processes. | |
| Action: | Try again by entering process identification numbers that you know to be currently active. | |
MGR-00314 unable to attach to default host
| Cause: | The default host has not been set up correctly. | |
| Action: | Use the SET INSTANCE command with a valid host specification to set up a default host. | |
MGR-00315 cannot open command file "name"
| Cause: | Server Manager cannot locate the specified command file. | |
| Action: | Verify the file's name and Server Manager's access to it before retrying. | |
MGR-00318 Server Manager command line error [num]
| Cause: | You made a syntax or typing error while entering a Server Manager command. | |
| Action: | Correct the syntax and try again. | |
MGR-00321 instance name too long
| Cause: | You specified an instance name that may or may not be valid, but is too long (exceeds 127 characters). | |
| Action: | Verify the name of the desired instance and try again. | |
MGR-00322 total size of command line parameters exceeds buffer size
| Cause: | You entered too many command line arguments and the size of the Server Manager buffer was exceeded. | |
| Action: | Reduce the number of command line arguments. | |
MGR-00323 invalid date specification; use DD-MON-YY:HH:MM:SS
| Cause: | You entered an improper date specification in the RECOVER DATABASE command. | |
| Action: | Use a valid date specification. For example: 24-DEC-1988:12:33:26. | |
MGR-00324 maximum number of tablespaces (num) exceeded; last num ignored
| Cause: | You specified too many tablespace names in the RECOVER TABLESPACE command. You may only specify up to 16 tablespace names. | |
| Action: | Reduce the number of tablespaces. If you want to recover more than 16 tablespaces, use the RECOVER command multiple times. | |
MGR-00325 read error on parameter file "filename"
| Cause: | The file you specified using the PFILE option of the STARTUP command is too large (exceeds 8K), the file contains a line that is too long, or another file system error occurred. | |
| Action: | Reduce the size of the parameter file before specifying it again or shorten extremely long lines in the file. | |
MGR-00326 currently no statistics belong to the specified class
| Cause: | At this time no statistics exist in the class you specified. | |
MGR-00327 command not available in this mode
| Cause: | You have specified a command that is not available in this mode. | |
| Action: | Do not specify the command in the current mode. | |
MGR-00328 insufficient privileges for this display
| Cause: | You do not have sufficient privileges to view the monitor you requested. | |
| Action: | Contact your database administrator to obtain the required privileges. | |
MGR-00329 insufficient privileges for SHOW SGA
| Cause: | You attempted to use SHOW SGA without sufficient privileges. | |
| Action: | Contact your database administrator to obtain the required privileges. | |
MGR-00330 logsource name too long
| Cause: | You specified a logsource name that may or may not be valid, but is too long (exceeds 127 characters). | |
| Action: | Verify the logsource name and try again. | |
MGR-00336 insufficient privileges for SHOW PARAMETERS
| Cause: | You attempted to use SHOW PARAMETERS without sufficient privileges. | |
| Action: | Contact your database administrator to obtain the required privileges. | |
MGR-00337 missing instance name
| Cause: | Instance name or service name not specified in the CONNECT statement. | |
| Action: | Use CONNECT username/password@instance. | |
MGR-00340 display size exceeded; extra lines truncated
| Cause: | The monitor display retrieved too many lines. | |
| Action: | Increase the granularity of your selection. | |
MGR-00341 the bind variable name is undefined
| Cause: | The SQL statement refers to an undefined bind variable. | |
| Action: | Use the VARIABLE command to define the bind variable and execute the query again. | |
MGR-00342 unable to complete internal login
| Cause: | An attempt was made to complete an internal connection to a database. This connection attempt has failed as a result of the indicated database error. | |
| Action: | Correct the database error and try again. | |
MGR-00343 no such parameter
| Cause: | SHOW PARAMETER was given a parameter name that does not exist. | |
| Action: | Use a different argument with SHOW PARAMETER. | |
MGR-00360 object to be described does not exist
| Cause: | The object in a DESCRIBE FUNCTION/PROCEDURE/PACKAGE statement does not exist. | |
| Action: | Check that the object name and owner are correct and that the object exists. | |
MGR-00361 no privilege to describe this object
| Cause: | You do not have sufficient privileges to describe the object. | |
| Action: | The object owner must grant privileges on the object. | |
MGR-00362 text too long for DESCRIBE
| Cause: | The object's text is too long for the DESCRIBE command. | |
| Action: | The object cannot be used with the DESCRIBE command. | |
MGR-00363 logic error in DESCRIBE
| Cause: | You have encountered an internal error in Server Manager. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-00364 out of space for identifier in DESCRIBE
| Cause: | You have encountered an internal error in Server Manager. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-00365 DESCRIBE PACKAGE BODY is not supported
| Cause: | Only a package's specification can be described. The keyword BODY cannot be used with DESCRIBE PACKAGE. | |
| Action: | Remove the BODY keyword. | |
01500-01599: Server Manager Internal Messages
MGR-01501 Server Manager has run out of memory
| Cause: | Server Manager was unable to obtain the memory it required. | |
| Action: | Close some windows or exit and restart Server Manager. | |
MGR-01503 an invalid argument was sent to a function
| Cause: | An internal Server Manager function was called incorrectly. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-01505 user requested cancel
| Cause: | You cancelled out of the middle of a process. | |
MGR-01506 unknown error
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-01507 unable to open file "filename"
| Cause: | Server Manager was unable to open an existing file or create a new one. | |
| Action: | Check that the file exists and Server Manager can locate the file. Or make sure there is enough free disk space and you have sufficient privileges to create a file. | |
MGR-01508 unable to close the current file
| Cause: | Server Manager was unable to close a file. | |
| Action: | Check for operating system circumstances that are preventing the file from being closed. | |
MGR-01509 unexpected EOF encountered
| Cause: | Server Manager encountered an unexpected End-Of-File marker. | |
| Action: | Examine the script(s) to determine the problem. | |
MGR-01523 invalid monitor name: name
| Cause: | The entered monitor name is not a valid monitor type. | |
| Action: | Enter a different monitor name. | |
02000-02009: Server Manager About Box Messages
MGR-02001 unable to destroy a timer
MGR-02002 unable to create a timer
| Cause: | You have encountered an internal error in Server Manager. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-02003 unable to load a window from a resource file
MGR-02004 unable to find a needed resource: masplash.tif
| Cause: | A resource file is missing or corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
02010-02019: Server Manager Administration Window Internal Messages
Most messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-02011 a control is missing from a resource
MGR-02016 an error occurred while loading a window from the resource file
MGR-02017 unable to get subview
| Cause: | A resource file is corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-02019 an error occurred while accessing help
| Cause: | An error occurred in Oracle Help. | |
| Action: | Examine subsequent messages. | |
02020-02029: Server Manager Event Handler Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
02030-02039: Server Manager Connection List Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
02040-02069: Server Manager Startup Messages
Most messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-02042 unable to open resource file: name
MGR-02046 unable to get a resource
MGR-02047 unable to load window system resources
MGR-02051 an error occurred while initializing Multimedia
| Cause: | The multimedia resource file (mmmwm.res) may be missing or corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-02056 unable to load the splash screen from the resource file
MGR-02057 unable to find a necessary resource file
| Cause: | A resource file is corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-02059 unable to open .msb file for product name, facility name
| Cause: | The message file for the specified product and facility cannot be found. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
02070-02089: Server Manager Window and Menu Handler Messages
Most messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-02073 an error occurred while connecting to a database
| Cause: | An error occurred while connecting to a database. | |
| Action: | Examine subsequent messages. | |
MGR-02076 an error occurred while disconnecting from a database
| Cause: | An error occurred while disconnecting from a database. | |
| Action: | Examine subsequent messages. | |
MGR-02083 unable to load the Connect dialog box
| Cause: | A resource file is corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
02090-02099: Server Manager Utility Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
02100-02109: Server Manager Window Handler Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
02110-02119: Server Manager Root Window Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
02130-02139: Server Manager Administration Window Button and Folder Tab Messages
Most messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-02134 tab "name" failed; maybe catsvrmg.sql not run or not a DBA
MGR-02135 tab "name" failed; maybe insufficient privileges
| Cause: | Either Server Manager was not installed fully, or you do not have access to this information. | |
| Action: | Run the CATSVRMG.SQL script as SYS, if necessary. Then connect as a user with the DBA role as a default role. | |
MGR-02136 tab "name" failed, maybe utlxplan.sql not run
| Cause: | The table sys.plan_table does not exist. | |
| Action: | Run the script UTLXPLAN.SQL as SYS. | |
MGR-02137 tab "name" failed, maybe catrepad.sql not run or not a DBA
| Cause: | Either Server Manager was not installed fully, or you do not have access to this information. | |
| Action: | Run the catrepad.sql script as SYS, if necessary. Then connect as a user with the DBA role as a default role. | |
02140-02149: Server Manager Administration Window Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
02150-02159: Server Manager Administration Window SQL Interface Messages
Most messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-02150 an unrecognized database version was encountered
| Cause: | You have tried to administer a database version that Server Manager does not support. | |
| Action: | Consider upgrading your database. | |
MGR-02151 a specification for action string could not be found
| Cause: | A resource file is corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-02156 Server Manager could not perform action string
MGR-02157 action string failed; maybe catsvrmg.sql not run or not a DBA
MGR-02158 action string failed; maybe insufficient privileges
| Cause: | Either Server Manager was not installed fully, or you do not have access to this information. | |
| Action: | Run the CATSVRMG.SQL script as SYS, if necessary. Then connect as a user with the DBA role as a default role. | |
02160-02169: Server Manager Administration Window Menu Handler Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
02170-02179: Server Manager Administration Window Lower Pane Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
02180-02189: Server Manager Administration Window Object List Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
02190-02199: Server Manager Administration Window Database Banner Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
03000-03499: Server Manager Monitor Messages
Most messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-03006 the monitor_name could not enable its child views
MGR-03007 the monitor_name could not disable its child views
| Cause: | A monitor resource is corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-03008 the monitor_name could not be resized
| Cause: | The monitor was not able to be resized. | |
| Action: | Examine subsequent messages. A Toolkit error should follow this message. | |
MGR-03009 the monitor_name could not sort on the selected column
MGR-03010 the monitor_name cannot set its Cycle radio button
MGR-03011 the monitor_name cannot set its Sample on Demand radio button
MGR-03012 the monitor_name cannot reset a button
| Cause: | A monitor resource is corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-03013 the monitor_name cannot complete the filter operation
| Cause: | Text in the Filter field is invalid. | |
| Action: | Enter valid text in the Filter field. | |
MGR-03016 a monitor_name is closing because its SQL command failed
| Cause: | Connection to the database has been lost during the execution of a SQL command. | |
| Action: | Verify that the database is still running and that the network is functioning properly. Attempt to reconnect. | |
MGR-03017 a monitor_name is closing because its Interval pop-up menu failed
| Cause: | An error was generated when the Interval pop-up menu was used. | |
| Action: | Examine subsequent messages. | |
MGR-03018 the monitor_name is in an unknown state and could not be removed
| Cause: | The monitor failed to shut down properly. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-03019 the monitor_name was not found
| Cause: | A monitor resource is corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-03020 the following title was too long: "name"
| Cause: | You attempted to create a monitor with a connection name longer than 80 characters. | |
| Action: | Shorten your SQL*Net service names. | |
MGR-03021 a monitor_name is closing because of an error finishing a SQL command
| Cause: | The monitor lost connection with the database while a SQL command was running. | |
| Action: | Verify that the database is still running and that the network is functioning properly. Attempt to reconnect. A more specific error message will follow, probably indicating that the connection state has changed. | |
MGR-03022 select a monitor from the scrolling list and click OK
| Cause: | A resource file is missing or corrupted. | |
| Action: | Check your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-03023 monitor selection failed
| Cause: | An error occurred during the selection of a monitor. | |
| Action: | Examine subsequent messages. | |
MGR-03024 interval must be at least 15 seconds
| Cause: | User entered an interval less than 15 seconds. | |
| Action: | Enter a valid interval of 15 seconds or more. | |
MGR-03025 numeric filter fields must contain numeric values
| Cause: | User entered a non-numeric value for a numeric filter field. | |
| Action: | Enter a valid number in the filter field and click filter again. | |
MGR-03050 a monitor_name is closing because of an error in parse/bind/define
| Cause: | An error was encountered when attempting to parse, bind, or define a SQL statement for the monitor. | |
| Action: | Verify that the database is still running and that the network is functioning properly. Attempt to reconnect. A more specific error message will follow, probably indicating that the connection state has changed. | |
MGR-03051 an error occurred while executing a monitor query
MGR-03052 the query for the monitor_name failed to execute
| Cause: | An error occurred when the monitor was interacting with the SQL engine. | |
| Action: | Verify that the database is still running and that the network is functioning properly. Attempt to reconnect. A more specific error message will follow, probably indicating that the connection state has changed. | |
MGR-03053 an error occurred after completing a monitor query
MGR-03054 one or more monitors are closing due to a connection problem
| Cause: | The state of the monitor connection has changed as a result of actions taken outside of the monitor subsystem. | |
| Action: | Verify that the database is still running and that the network is functioning properly. Attempt to reconnect. A more specific error message will follow, probably indicating that the connection state has changed. | |
03500-03536: Server Manager SQL Engine Messages
MGR-03500 encountered an unterminated quote
| Cause: | The last command contained an open quote without a matching close quote. | |
| Action: | Correct the quoting and issue the command again. | |
MGR-03501 unable to process so many nested scripts
| Cause: | You have attempted to run a script that in turn tries to run too many nested levels of scripts. | |
| Action: | Restructure your scripts so the nesting depth decreases. | |
MGR-03502 the @@ operator is only allowed within SQL scripts
| Cause: | You attempted to use the @@ operator from the interactive mode. | |
| Action: | The @@ operator is only allowed from within a script. In the interactive mode, use the @ operator to run a SQL script. | |
MGR-03503 could not resolve the symbols in "filename"
| Cause: | The filename you provided for the parameter file contained undefined symbols. | |
| Action: | Check the text of the parameter filename you provided. | |
MGR-03504 CYCLE is no longer a valid global property
| Cause: | You attempted to set the CYCLE property. | |
| Action: | Set the interval in the monitor(s) you are running. | |
MGR-03505 ARRAYSIZE is no longer a valid global property
| Cause: | You attempted to set the ARRAYSIZE property. | |
| Action: | None. Server Manager will fetch as many rows as possible given the current size of the MAXDATA buffer. | |
MGR-03506 expected a number (num-999999), not "string"
| Cause: | You attempted to set a property (NUMWIDTH, CHARWIDTH, and so on) to a non-numeric value or a number outside of the legal range. | |
| Action: | Use a value within the specified range. | |
MGR-03509 corrupted internal Oracle number representation
| Cause: | You attempted to use a bind variable that appears to have been corrupted. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-03510 corrupted bind variable type [type]
| Cause: | You attempted to use a bind variable that appears to have been corrupted. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-03511 the HOST command is not supported in graphical mode
| Cause: | You tried to use the HOST command from within a SQL Worksheet. | |
| Action: | Scripts that make use of the HOST command must be run from Server Manager line mode. | |
MGR-03512 spool file "name" is already open
| Cause: | You attempted to open a second spool file. | |
| Action: | Use SPOOL OFF to close the existing spool file. | |
MGR-03514 unable to start the database
| Cause: | The cause is listed in subsequent error messages. | |
| Action: | Examine the subsequent errors. | |
MGR-03515 invalid SERVEROUTPUT switch
| Cause: | You attempted to set SERVEROUTPUT to something other than ON or OFF. | |
| Action: | Use ON or OFF as arguments with SET SERVEROUTPUT. | |
MGR-03523 no parameter for SHOW ERRORS and no object has been compiled
| Cause: | You issued a SHOW ERRORS command, but have yet to compile a PL/SQL object. | |
| Action: | You can find error information for a specific object by selecting from the ALL_ERRORS view where NAME = <object>. | |
MGR-03524 unable to shutdown the database
| Cause: | You attempted to shut down the database without sufficient privileges. | |
| Action: | Enable the privileges required for shutdown. | |
MGR-03525 expected SYSDBA or SYSOPER, not "string"
| Cause: | You attempted to use the CONNECT AS syntax and specified something other than SYSDBA or SYSOPER. | |
| Action: | Correct the syntax and issue the command again. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-03534 invalid AUTOPRINT switch
| Cause: | You attempted to set AUTOPRINT to something other than ON or OFF | |
| Action: | Use ON or OFF as arguments with SET AUTOPRINT. | |
MGR-03536 variable type REFCURSOR not available
| Cause: | You tried to declare a REFCURSOR variable against a version of server manager which which does not support this variable type. | |
| Action: | The version of Server Manager you are running against does not support the REFCURSOR feature. It was most likely compiled against a pre-7.2 database. | |
04000-04008: Server Manager Worksheet Command Messages
Messages in this range indicate that a SQL Worksheet command failed to execute properly. Other messages will follow the SQL Worksheet command messages. Examine the subsequent messages to determine the proper action.
04009-04099: Server Manager Worksheet Messages
MGR-04017 the attempted font change did not succeed
| Cause: | This action is not available to you. | |
| Action: | Do not change the font. | |
MGR-04022 the Write Selection menu item was chosen without a text selection
| Cause: | You chose Write Selection from the Worksheet menu without having any text selected in the input or output panes of a SQL Worksheet. | |
| Action: | Attempt the command with text selected. | |
MGR-04024 unable to open specified file: "name"
| Cause: | A specified file could not be opened. | |
| Action: | The file is either invalid or in an unexpected format. Verify the filename and replace the file with a usable file, if necessary. | |
MGR-04025 the Get File option of the Recover dialog box failed
| Cause: | You specified a filename which was invalid. | |
| Action: | Specify a valid filename. | |
MGR-04026 the Apply Recovery Archives dialog box failed
| Cause: | An error occurred in the operation of the Worksheet's Apply Recovery Archives dialog box. | |
| Action: | Examine subsequent messages. | |
MGR-04027 the database is not available
| Cause: | The Oracle database is not accessible from your system. | |
| Action: | Verify that the database is available and that you have the ability to connect to the database from the current location. | |
04501-04549: Server Manager Line Mode Messages
MGR-04501 monitors are not available from the line mode Server Manager
| Cause: | You attempted the MONITOR command from Server Manager line mode. | |
| Action: | Start Server Manager in graphical mode to run monitors. | |
MGR-04544 invalid parameter format
| Cause: | You gave an invalid command line argument. | |
| Action: | Start Line mode with the correct arguments. These should be of the format command="command". Note that the command should be in quotes. | |
MGR-04545 too many parameters
| Cause: | You gave too many parameters on the command line, or your command line parameters may have been parsed separately. | |
| Action: | Pass in only the supported number of arguments. Make sure they are of the format command="command". Note that the command should be in quotes. | |
MGR-04546 invalid connect string
| Cause: | Your connect string contained invalid information. | |
| Action: | Check the syntax of your connect string. It should be "[username] [/password] [@instance path]". | |
MGR-04547 duplicate password
| Cause: | Your connect string contained either a null password or multiple password strings. | |
| Action: | Make sure your connect string only gives a single password. It should be of the form "/password". | |
MGR-04548 null username/password not valid with connection name
| Cause: | A connect string with a null username/password and a non-null connection name is invalid. | |
| Action: | You must explicitly specify a null username/password using the "/" designator when giving a connection name in the user string. For example: "/@t:lorax:E". | |
MGR-04549 null or invalid connection name
| Cause: | Your connect string contained either a null or invalid host string. | |
| Action: | Check the syntax of your connect string. | |
05500-05509: Server Manager User Program Interface Messages
MGR-05500 out of unique ids for asynchronous connections
| Cause: | You have too many outstanding asynchronous connections. | |
| Action: | Close some less important windows or restart Server Manager. | |
MGR-05501 user string overflow
| Cause: | You have tried to connect using a username that is greater than 30 characters in length. | |
| Action: | Specify a shorter username. | |
MGR-05502 password string overflow
| Cause: | You have tried to connect using a password that is greater than 30 characters in length. | |
| Action: | Specify a shorter password. | |
MGR-05503 host string overflow
| Cause: | You have tried to connect using a hostname that is greater than 80 characters in length. | |
| Action: | Use a shorter service name. | |
MGR-05504 cannot connect to an Oracle version_num instance
| Cause: | You have attempted to connect to an old version of Oracle. | |
| Action: | Server Manager can only run against Version 7 or later. You can upgrade the instance, or use the SQL*DBA included with your release of Oracle. | |
MGR-05505 cannot perform a CONNECT usr/pswd AS name to an ORACLE 7.0 instance
| Cause: | You tried to connect to a version 7.0 database AS SYSDBA or AS SYSOPER. | |
| Action: | In Version 7.0 you must CONNECT INTERNAL [/password]. | |
MGR-05506 unable to release an allocated connection
| Cause: | You attempted to close a window which could not be closed. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-05507 the list of connections has been corrupted
| Cause: | You have encountered an internal error in Server Manager. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
06500-06529: Server Manager Oracle Toolkit II Messages
Most messages in this range indicate that you have encountered an internal error. Call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-06512 Oracle Toolkit II has run out of memory
| Cause: | There is not enough memory. | |
| Action: | Free up or add memory. | |
MGR-06513 Oracle Toolkit II's client has run out of memory
| Cause: | There is not enough memory. | |
| Action: | Free up or add memory. | |
MGR-06518 Oracle Toolkit II's connection to the window system was refused
| Cause: | The windowing system (usually X Windows) denied permission to connect. | |
| Action: | On X Windows, set the DISPLAY to a server that will allow connections. | |
06600-06699: Server Manager Oracle Help Messages
Most messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-06602 the Oracle Help book is in a format not recognized by object store
| Cause: | The Oracle Help book has not been installed properly or is corrupted. | |
| Action: | Reinstall the help book(s) or the entire product. | |
MGR-06603 Oracle Help has run out of memory
| Cause: | There is not enough memory. | |
| Action: | Free up or add memory. | |
MGR-06606 Oracle Help could not find a help target
| Cause: | The program tried to access an Oracle Help target not contained in the help book(s). | |
| Action: | Reinstall the help book(s) or the entire product. If this does not solve the problem, contact Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-06607 Oracle Help could not find the specified word
| Cause: | The find operation could not locate the specified word. | |
| Action: | The word does not exist in the Help document. Try another word. | |
MGR-06608 Oracle Help could not link to external document
| Cause: | External document is either damaged, non-existent, or is not an Oracle Book document. | |
| Action: | Replace the document or link to a valid document. | |
MGR-06610 the document is not an Oracle Help document
| Cause: | The Oracle Help book has not been installed properly or has become corrupted. | |
| Action: | Reinstall the help book(s) or the entire product. | |
MGR-06611 the document is newer than Oracle Help
| Cause: | The Oracle Help book has not been installed properly or has become corrupted. | |
| Action: | Reinstall the help book(s) or the entire product. If this does not solve the problem, contact Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-06614 Oracle Help encountered an invalid link
| Cause: | The program tried to follow an Oracle Help link not contained in the help book(s). | |
| Action: | Reinstall the help book(s) or the entire product. If this does not solve the problem, contact Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-06618 the string begins with a percent sign
| Cause: | An entered string begins with a percent sign. | |
| Action: | Remove the percent sign from the beginning of the string. | |
07001-08529: Server Manager DRUID Messages
MGR-07368 the Username field must contain a valid Oracle username
| Cause: | The text you entered in the Username field is not a valid Oracle username. | |
| Action: | Check to make sure the value entered conforms to the guidelines for Oracle usernames given in Chapter 2 of the Oracle7 Server SQL Reference. | |
MGR-07369 the Password field must contain a password string
| Cause: | You selected Password in the Create/Alter User property sheet, but did not specify a password. | |
| Action: | Select another password option or assign a password to the user. | |
MGR-07401 the Composite Limit field must contain a valid number
MGR-07402 the Private SGA field must contain a valid number
MGR-07403 the Reads per Call field must contain a valid number
MGR-07404 the Reads per Session field must contain a valid number
MGR-07405 the Idle Time field must contain a valid number
MGR-07406 the Connect Time field must contain a valid number
MGR-07407 the CPU per Call field must contain a valid number
MGR-07408 the CPU per Session field must contain a valid number
MGR-07409 the Sessions per User field must contain a valid number
| Cause: | The number entered in the indicated field is not valid. | |
| Action: | Check to make sure there are no extraneous alphabetic or punctuation characters in the field. Make sure the value entered is within the range of valid values. | |
MGR-07410 the Profile Name field must contain a valid Oracle identifier
| Cause: | The value entered in the Profile Name field is not an Oracle identifier. | |
| Action: | Check to make sure the value entered conforms to the guidelines for Oracle identifiers given in Chapter 2 of the Oracle7 Server SQL Reference. | |
MGR-07537 the System Change Number field must contain a positive number
| Cause: | The value you have entered in the field is not a valid SCN. | |
| Action: | In general, you should allow Oracle to determine the SCN, so try committing the transaction without specifying an SCN. | |
MGR-07539 the Group Number field must contain a valid number
| Cause: | The value in the field is not a number. | |
| Action: | The group number must be a positive number that is not the number of an existing group. When the dialog box appears, Server Manager initializes this field to be one greater than the greatest log file group number. | |
MGR-07540 the New File Size field must contain a valid number
| Cause: | The value in this field is not a number. | |
| Action: | Provide a valid positive number. | |
MGR-07541 at least one file must be specified
| Cause: | You have not specified the name of at least one file. | |
| Action: | Use the New button to bring up the file specification dialog box from which you can select a file. | |
MGR-07542 the Filename field must contain a valid filename
| Cause: | The field is empty or contains an invalid file. | |
| Action: | Provide a valid filename. | |
MGR-07543 you must select a log file group in which to place the log file
| Cause: | You have not selected the group into which this log file will be placed. | |
| Action: | Choose one of the provided groups. | |
MGR-07544 the To field must contain a valid filename
| Cause: | The field is empty or contains an invalid file. | |
| Action: | Provide a valid filename. | |
MGR-07547 the Name field must contain a valid Oracle identifier
| Cause: | The Name field is empty or contains a value that is not a valid Oracle identifier. | |
| Action: | Check to make sure the value entered conforms to the guidelines for Oracle identifiers given in Chapter 2 of the Oracle7 Server SQL Reference. | |
MGR-07548 you must specify at least one datafile
| Cause: | There are no entries in the list of datafiles. | |
| Action: | Use the New button to bring up a dialog box that will allow you to specify a datafile. | |
MGR-07549 the Initial Extent field must be empty or contain a valid number
MGR-07550 the Next Extent field must be empty or contain a valid number
MGR-07551 the Minimum Extents field must be empty or contain a valid number
MGR-07552 the Maximum Extents field must be empty or contain a valid number
MGR-07553 the Percentage Increase field must be empty or contain a valid number
| Cause: | The value is not a positive number. | |
| Action: | Specify a positive number or leave the field empty. | |
MGR-07555 unable to find tablespace information for "name"
| Cause: | Server Manager was unable to find the default storage settings for the chosen tablespace. | |
| Action: | Refresh the Tablespaces object list and try to alter the tablespace again. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-07556 the Rollback Segment field must contain a valid Oracle identifier
| Cause: | The Rollback Segment field is empty or contains a value that is not a valid Oracle identifier. | |
| Action: | Check to make sure the value entered conforms to the guidelines for Oracle identifiers given in Chapter 2 of the Oracle7 Server SQL Reference.. | |
MGR-07557 the Optimal field must be empty or contain a valid number
| Cause: | The value is not a positive number. | |
| Action: | Specify a positive number or leave the field empty. | |
MGR-08049 the Role Name field must contain a valid Oracle identifier
| Cause: | The text you entered in the Role Name field is not a valid Oracle identifier. | |
| Action: | Check to make sure the value entered conforms to the guidelines for Oracle usernames given in Chapter 2 of the Oracle7 Server SQL Reference. | |
MGR-08050 with Password selected, a password must be specified
| Cause: | You selected Password in the Create/Alter Role property sheet, but did not specify a password. | |
| Action: | Select another password option or assign a password to the role. | |
MGR-08051 a user or role must be specified
| Cause: | No user or role was specified in the Grant/Revoke Role dialog box. | |
| Action: | Select a user or role from the scrolling list. | |
MGR-08052 with the Role privilege type selected, a role must be chosen
| Cause: | With the Role privilege type selected, you clicked the OK button in the Add Privilege to Role dialog box before selecting a role from the Defined Roles scrolling list. | |
| Action: | Select a role from the Defined Roles scrolling list or click the Cancel button to exit the dialog box. | |
MGR-08053 with the System privilege type selected, a privilege must be chosen
| Cause: | With the System Privileges privilege type selected, you clicked the OK button in the Add Privilege to Role dialog box before selecting a system privilege from the System Privileges scrolling list. | |
| Action: | Select a privilege from the System Privileges scrolling list or click the Cancel button to exit the dialog box. | |
MGR-08054 with the Object privilege type selected, an object must be specified
| Cause: | With the Object privilege type selected, you clicked the OK button in the Add Privilege to Role dialog box before entering an object in the Object Name field. | |
| Action: | Enter an object into the Object Name field or click the Cancel button to exit the dialog box. | |
MGR-08055 a schema must be chosen
| Cause: | You clicked the OK button in the Find Schema Object dialog box without selecting a schema from the Schema scrolling list. | |
| Action: | Select a schema from the Schema scrolling list or click the Cancel button to exit the dialog box. | |
MGR-08056 an object must be chosen
| Cause: | You clicked the OK button in the Find Schema Object dialog box without selecting an object from the Object scrolling list. | |
| Action: | Select an object from the Object scrolling list or click the Cancel button to exit the dialog box. | |
MGR-08504 the tablespace "name" is not offline so this datafile cannot be renamed
| Cause: | You tried to rename a datafile in an online tablespace. | |
| Action: | Take the corresponding tablespace offline and then rename the datafile. | |
MGR-08505 the tablespace "name" is invalid so this datafile cannot be renamed
| Cause: | You tried to rename a datafile in an invalid tablespace. | |
| Action: | Repair the tablespace to make it valid and then rename the datafile. | |
MGR-08507 the Quota Size field must contain a valid number
| Cause: | A negative number or a non-numeric character was entered in the Quota Size field of the Add/Edit Quota dialog box. | |
| Action: | Enter a valid quota size. | |
MGR-08510 a user must be specified
| Cause: | No user was specified in the Users scrolling list of the Assign Profile dialog box. | |
MGR-08515 this datafile has already been added to the database and cannot be removed
| Cause: | You tried to remove from a tablespace a datafile which belongs to a tablespace. | |
| Action: | None. A previously added datafile cannot be removed. | |
MGR-08517 the Object Name field does not contain a valid schema object
| Cause: | You entered a schema object that does not follow proper naming or quoting conventions. | |
| Action: | Enter a valid schema object name. | |
MGR-08524 a privilege or role must be specified
| Cause: | A Privilege or Role was not specified in the Remove Privilege from User/Role dialog box. | |
| Action: | Select a privilege or role from the list before clicking the Remove button. | |
09500-09999: Server Manager Help System Messages
Most messages in this range indicate that you have encountered an internal error. Call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-09501 help is not available for the active window
| Cause: | The active window does not have a help target. This is probably because it is a system window rather than a Server Manager window. | |
| Action: | None. Refer to your documentation for the information about which you were looking for help. | |
MGR-09502 Oracle Help returned an error
| Action: | A second message will include the Oracle Help error. This number should be looked up in the Oracle Help documentation. | |
MGR-09506 Oracle Help was not able to respond to the user request
| Cause: | Multiple causes; to be clarified by additional error messages. | |
| Action: | Examine subsequent messages. | |
MGR-09507 Oracle Help text was not found
| Cause: | The Oracle Help book, mahelp.obd, is not properly installed or slfindfile() cannot find it. | |
| Action: | Reinstall Oracle Book or verify the response of slfindfile() for your platform. | |
MGR-09508 the text for target "string" was not found
| Cause: | The context string in the maht (help table) did not have a corresponding string in the mahelp.obd book. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. The file mahelp.obd or the maht will need to be modified. | |
10000-10099: Server Manager National Language Support Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
10500-10599: Server Manager Oracle Toolkit II Resource Manager Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
11000-11499: Server Manager Core Messages
Messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-11401 input error, unable to read input line
| Cause: | An error in reading from the input source occurred. This is most likely because the input line is too long. | |
| Action: | Try breaking the input line into multiple lines of no more than 1024 bytes per line. | |
MGR-11402 error while writing output to a file
| Cause: | An error in writing to the output file occurred. This is most likely because the output line is too long. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-11403 error while writing output
| Cause: | An error in writing to the output source (generally stdout) occurred. This is most likely because the output line is too long. | |
| Action: | If this occurred in Server Manager Line Mode, try executing the query in the Server Manager Worksheet. | |
MGR-11404 error formatting output
| Cause: | An error occurred during the CORE sprintf routine. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
11500-11999: Server Manager Replication Messages
Most messages in this range indicate that you have encountered an internal error. For these messages, call Customer Support with the circumstances and complete set of messages leading to the error.
For other messages in this range, specific actions can be taken. These messages are listed below:
MGR-11500 you must quiesce the replicated schema before performing the operation
| Cause: | You attempted to alter a master repschema that has not been quiesced. | |
| Action: | First Suspend Master Activity on the replicated schema, then try again. | |
MGR-11502 the current operation is only valid for master definition sites
| Cause: | You attempted to use an operation that is only valid for master definition sites. | |
| Action: | Perform operation on a master definition site. | |
MGR-11505 the Remote Master field must contain a valid remote database
| Cause: | The operation needs a list of one or more remote masters on which to operate. | |
| Action: | Specify a list of masters in the Server Manager dialog using multi-select. | |
MGR-11506 the DDL Text field must contain a valid DDL statement
| Cause: | The operation needs a DDL statement. | |
| Action: | Enter a DDL statement in the Server Manager dialog. | |
MGR-11517 the selected Destination Database has no transactions queued for remote execution
| Cause: | You attempted an operation on a Destination Database which has no transactions queued for remote execution. | |
| Action: | Retry this operation when there are transactions queued for remote execution. | |
MGR-11519 the Transaction Count field must contain a positive integer
| Cause: | The number entered in the indicated field is not valid. | |
| Action: | Check to make sure there are no extraneous alphabetic or punctuation characters in the field. Make sure the value entered is within the range of valid values. | |
MGR-11520 the Execution Seconds field must contain a positive integer
| Cause: | The number entered in the indicated field is not valid. | |
| Action: | Check to make sure there are no extraneous alphabetic or punctuation characters in the field. Make sure the value entered is within the range of valid values. | |
MGR-11521 the selected deferred transaction has no associated calls
| Cause: | A deferred transaction was queued for execution, but the transaction does not contain any operations (i.e. a null transaction) | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-11523 the deferred call arguments could not be extracted
| Cause: | An error occurred while trying to extract and store the arguments for a call in a deferred transaction. | |
| Action: | Call Customer Support with the circumstances and complete set of messages leading to the error. | |
MGR-11525 the local database is not a master site
| Cause: | An operation originating from a remote database or locally assumes that the local database is a master site for replication. | |
| Action: | No action can be taken in this case. | |
MGR-11528 all objects in the chosen schema are already replicated
| Cause: | All the objects in the chosen schema are replicated. | |
| Action: | Choose a different schema or add some more objects to this schema. | |
MGR-11530 you must select at least one Remote Master from the list
| Cause: | The operation needs a list of one or more remote masters on which to operate. | |
| Action: | Specify a list of masters in the Server Manager dialog using multi-select. | |
MGR-11531 cannot generate replication support for name. Table has no PRIMARY KEY.
| Cause: | Replication will not work for tables without a PRIMARY KEY. | |
| Action: | Recreate table with a PRIMARY KEY or call procedure DBMS_REPCAT.SET_COLUMNS after CREATE_MASTER_REPOBJECT but before GENERATE_REPLICATION_SUPPORT. | |
MGR-11532 you must select at least one Master Database from the list
| Cause: | The operation needs a list of one or more remote masters on which to operate. | |
| Action: | Specify a list of masters in the Server Manager dialog using multi-select. | |
MGR-11533 cannot execute package SYS.DBMS_DEFER_PRINT. Maybe CATREPAD.SQL not run or no EXECUTE privilege
| Cause: | Server manager cannot execute DBMS_DEFER_PRINT. | |
| Action: | Make sure CATREPAD.SQL has been run and the current user has execute privileges on DBMS_DEFER_PRINT. | |
MGR-11534 cannot display call arguments for a remote procedure from a snapshot site
| Cause: | Cannot get the call arguments for remote procedure. | |
| Action: | No action is available from a snapshot site. | |
