Oracle Enterprise Manager Messages Manual Release 1.5.0 A57693-01 |
|
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.
Cause: There were unrecognized commands or other text on the command line.
Action: Check the command syntax and/or issue the command without the extraneous text.
Cause: The LOG keyword was missing from the ARCHIVE LOG command.
Action: Correct the syntax of the command, and then issue the command again.
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, and then issue the command again.
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.
Cause: An invalid Net8 service name was specified for the instance name.
Action: Refer to your Oracle platform-specific documentation for a complete description of specifying Net8 service names.
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.
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.
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.
Cause: An invalid value was specified for the SET CYCLE command.
Action: Specify a SET CYCLE value between 5 seconds and 99:99 (min:sec) inclusive.
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 Enterprise Manager Administrator's Guide for the correct syntax.
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 Enterprise Manager Administrator's Guide for the correct syntax.
Cause: The specified PFILE name is not recognized.
Action: Specify a legal PFILE name.
Cause: The specified database name is not recognized.
Action: Specify a legal database name.
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.
Cause: An option other than NORMAL, IMMEDIATE, or ABORT was specified for the SHUTDOWN command.
Action: Correct the syntax of the command, and then issue the command again.
Cause: The specified tablespace name was not recognized.
Action: Specify a legal tablespace name.
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.
Cause: An option other than DBA, PFILE, EXCLUSIVE, SHARED, MOUNT, OPEN, RECOVER, or NOMOUNT was specified for the STARTUP command.
Action: Correct the syntax of the command, and then issue the command again.
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.
Cause: An illegal option was specified for the MONITOR command.
Action: Correct the syntax of the MONITOR command and issue the command again. See the Oracle Server Manager User's Guide for the correct syntax.
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, using an appropriate number for the option, and then issue the command again.
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, using valid tablespace names for all names in the list, and then enter the command again.
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.
Cause: A numeric value that was too large was specified.
Action: Use a smaller number.
Cause: The VERIFY switch was not recognized.
Action: Specify a legal VERIFY switch.
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.
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.
Cause: The specified value was out of range. The error message includes the valid range.
Action: Use a number within the range specified by the error message.
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.
Cause: The "hostname/password" was not specified.
Action: Specify the correct "hostname/password."
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, using valid datafile names for all names in the list, and then enter the command again.
Cause: An invalid option was specified for the SET AUTORECOVERY command.
Action: Use either ON or OFF as options for the SET AUTORECOVERY command.
Cause: A variable was incorrectly specified using the VARIABLE command.
Action: Correct the syntax of the command, and then issue the command again.
Cause: The PL/SQL block contains a syntax error.
Action: Correct the syntax error.
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.
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.
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.
Cause: The specified object type, owner, or name was not recognized.
Action: Specify a legal object type, owner, or name.
Cause: The specified variable was not recognized.
Action: Specify an existing variable. You can use the PRINT command to display currently defined variables.
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.
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.
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.
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.
Cause: An invalid option for the SET APPINFO command was specified.
Action: Use either ON, OFF or user text as an option for the SET APPINFO command.
Cause: You have encountered an internal error.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You used SET INSTANCE while you were connected to a database.
Action: If you want to change the current instance, disconnect from the database before using SET INSTANCE.
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.
Cause: The .CRT file is invalid or could not be found. The Server Manager requires the .CRT file in order to display monitors.
Action: Make sure the Server Manager can access the desired .CRT file.
Cause: A command file used as input to Server Manager is corrupted or invalid.
Action: Check the file before trying the operation again.
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.
Cause: You entered an invalid number for the cycle interval.
Action: Enter a value between 5 seconds and 99:99 (min:sec) inclusive.
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.
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, and then enter your commands before closing the file with SPOOL OFF.
Cause: SPOOL OFF could not close the currently opened spool file.
Action: Check for operating system circumstances that are preventing the file from being closed.
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 that the file can be opened.
Cause: A SQL query returned results exceeding the size of Server Manager's internal buffer.
Action: Use the SET command to increase MAXDATA or decrease ARRAYSIZE.
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.
Cause: You specified process identification numbers that do not correspond to any currently active processes.
Action: Enter the process identification numbers that you know to be currently active.
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.
Cause: Server Manager cannot locate the specified command file.
Action: Verify the file name and Server Manager's access to it before retrying.
Cause: You attempted to start up an instance while you were connected to a database.
Action: If you want to start up an instance, you must DISCONNECT from the database you are currently connected to.
Cause: You attempted to shutdown an instance while you were connected to a database.
Action: If you want to shutdown an instance, you must DISCONNECT from the database you are currently connected to.
Cause: You made a syntax or typing error while entering a Server Manager command.
Action: Correct the syntax and try again.
Cause: Server Manager cannot open the file specified by the ORA_SVRMGRINIT variable, 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.
Cause: You specified a terminal name that is too long, exceeding 64 characters. The name may or may not be valid.
Action: Verify the name of the desired terminal and try again.
Cause: You specified an instance name that may or may not be valid, but is too long (exceeding 127 characters).
Action: Verify the name of the desired instance and try again.
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.
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.
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.
Cause: The file you specified using the PFILE option of the STARTUP command is too large (exceeding 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.
Cause: At this time no statistics exist in the class you specified.
Action: None.
Cause: You have specified a command that is not available in this mode.
Action: Do not specify the command in the current mode.
Cause: You do not have sufficient privileges to view the monitor you requested.
Action: Contact your database administrator to obtain the required privileges.
Cause: You attempted to use SHOW SGA without sufficient privileges.
Action: Contact your database administrator to obtain the required privileges.
Cause: You specified a logsource name that may or may not be valid, but is too long (exceeding 127 characters).
Action: Verify the logsource name and try again.
Cause: There is not enough memory for the current SQL buffer.
Action: Use the SET command to reduce the value of MAXDATA.
Cause: Since executing the MONITOR FILEIO command, a database file has been added, invalidating the contents of the monitor.
Action: Execute the MONITOR FILEIO command again.
Cause: Since executing the MONITOR FILEIO command, a database file has been dropped, invalidating the contents of the monitor.
Action: Execute the MONITOR FILEIO command again.
Cause: You attempted to use SHOW PARAMETERS without sufficient privileges.
Action: Contact your database administrator to obtain the required privileges.
Cause: Instance name or service name not specified in the CONNECT statement.
Action: Use CONNECT username/password@instance.
Cause: The monitor display retrieved too many lines.
Action: Increase the granularity of your selection.
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.
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.
Cause: SHOW PARAMETER was given a parameter name that does not exist.
Action: Use a different argument with SHOW PARAMETER.
Cause: A mandatory scrolling list in a dialog box contained 0 elements.
Action: None.
Cause: The scrolling list for kill user session operation contain no elements.
Action: None.
Cause: The scrolling list for recover in-doubt transactions operation contained no elements.
Action: None
Cause: The scrolling list for set tablespace offline operation contained no elements.
Action: None
Cause: The scrolling list for set tablespace online operation contained no elements.
Action: None
Cause: The scrolling list for drop rollback segment operation contained no elements.
Action: None
Cause: The scrolling list for set rollback segment online operation contained no elements.
Action: None
Cause: The scrolling list for set rollback segment offline operation contained no elements.
Action: None
Cause: The scrolling list for begin online tablespace backup operation contained no elements.
Action: None
Cause: The scrolling list for end online tablespace backup operation contained no elements.
Action: None
Cause: The scrolling list for recover tablespace operation contained no elements.
Action: None
Cause: The scrolling list for recover datafiles operation contained no elements.
Action: None
Cause: The scrolling list for alter user or drop user operation contained no elements.
Action: None
Cause: The scrolling list for alter role or drop role operation contained no elements.
Action: None
Cause: The scrolling list for grant to or revoke from operation contained no elements.
Action: None
Cause: The monitor is already active.
Action: Cycle through the windows until the monitor becomes visible.
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.
Cause: You do not have sufficient privileges to describe the object.
Action: The object owner must grant privileges on the object.
Cause: The object's text is too long for the DESCRIBE command.
Action: The object cannot be used with the DESCRIBE command.
Cause: You have encountered an internal error in Server Manager.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error in Server Manager.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: Only a package's specification can be described. The keyword BODY cannot be used with DESCRIBE PACKAGE.
Action: Remove the BODY keyword.
Cause: You tried to execute the dialog box before specifying all required values.
Action: Specify all required values and try again.
Cause: You tried to move to another control before filling in a mandatory field.
Action: Fill in the current field.
Cause: You tried to move to another control before selecting a mandatory list item.
Action: Select an item from the scrolling list.
Cause: You have attempted to use a feature that has not been implemented.
Action: If this is a documented Server Manager feature, call World Wide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: Server Manager was unable to obtain the memory it required.
Action: Close some windows or exit and restart Server Manager.
Cause: An internal Sever Manager function was called incorrectly.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You cancelled out of the middle of a process.
Action: None.
Cause: Unknown.
Action: Call Oracle Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: Server Manager was unable to open an existing file or create a new one.
Action: Check that the file exists and that Server Manager can locate the file. Or make sure there is enough free disk space and you have sufficient privileges to create a file.
Cause: Server Manager was unable to close a file.
Action: Check for operating system circumstances that are preventing the file from being closed.
Cause: Server Manager encountered an unexpected End-Of-File marker.
Action: Examine the script(s) to determine the problem.
Cause: The entered monitor name is not a valid monitor type.
Action: Enter a different monitor name.
Messages in this range indicate that you have encountered an internal error. For these messages, contact Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: An error occurred in Oracle Help.
Action: Examine subsequent messages.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: An error occurred while connecting to a database.
Action: Examine subsequent messages.
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.
Cause: You have encountered an internal error in Server Manager.
Action: Try closing one or more SQL Worksheet windows. If problem persists, call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: An error occurred while disconnecting from a database.
Action: Examine subsequent messages.
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.
Cause: You have encountered an internal error in Server Manager.
Action: Try closing one or more monitor windows. If problem persists, call Customer Support with the circumstances and complete set of messages leading to the error.
Action: You have encountered an internal error in Server Manager.
Action: Try closing one or more Admin Worksheets or try closing one or more SQL Worksheets or close all monitor windows. If problem persists, call Customer Support with the circumstances and complete set of messages leading to the error.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: The table sys.plan_table does not exist.
Action: Run the script utlxplan.sql as SYS.
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.
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.
Cause: Your version of Server Manager is out of date.
Action: Obtain an updated copy of Server Manager.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Cause: A monitor resource 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.
Cause: A monitor resource 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.
Cause: The monitor was not able to be resized.
Action: Examine subsequent messages. A Toolkit error should follow this message.
Cause: A monitor resource 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.
Cause: A monitor resource 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.
Cause: A monitor resource 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.
Cause: A monitor resource 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.
Cause: Text in the Filter field is invalid.
Action: Enter valid text in the Filter field.
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.
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. A more specific error message will follow, probably indicating that the connection state has changed.
Cause: An error was generated when the Interval pop-up menu was used.
Action: Examine subsequent messages.
Cause: The monitor failed to shut down properly.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: A monitor resource 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.
Cause: You attempted to create a monitor with a connection name longer than 80 characters.
Action: Shorten your Net8 service names.
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.
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.
Cause: An error occurred during the selection of a monitor.
Action: Examine subsequent messages. If the problem persists, call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: User entered an interval less than 5 seconds.
Action: Enter a valid interval of 5 seconds or more.
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..
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.
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.
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.
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.
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.
Cause: An error occurred while the monitor was manipulating data for display purposes.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: A monitor type was internally specified for which a data manipulation action is invalid.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: A number which should be in an internal Oracle format did not have a format which could be recognized as an Oracle number.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: A number had an integer portion which was out of the valid range.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: A number which should be in an internal Oracle format did not have a format which could be recognized as an Oracle number.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: A monitor failed because it attempted to divide by zero when it was manipulating data.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The last command contained an opening quote without a matching closing quote.
Action: Correct the quotes and issue the command again.
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.
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.
Cause: The filename you provided for the parameter file contained undefined symbols.
Action: Check the text of the parameter filename you provided.
Cause: You attempted to set the CYCLE property.
Action: Set the interval in the monitor(s) you are running.
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.
Cause: You attempted to set a property (NUMWIDTH, CHARWIDTH, and so on) to a non-numeric value or a number outside the legal range.
Action: Use a value within the specified range.
Cause: You attempted to use a bind variable that appears to have been corrupted.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You attempted to use a bind variable that appears to have been corrupted.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
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.
Cause: You attempted to open a second spool file.
Action: Use SPOOL OFF to close the existing spool file.
Cause: You may be using an incorrect init.ora file (which may not have the correct syntax) or an invalid configuration. Incorrect values may have been set for one or more parameters in the stored configuration.
Action: You should use a correct init.ora file or use a stored configuration which you have been able to use successfully for startup or you can fix the problems in the current init.ora file. If you are using a stored configuration, you can export it into a file and then fix the problem in the init.ora file.
Cause: You attempted to set SERVEROUTPUT to something other than ON or OFF.
Action: Use ON or OFF as arguments with SET SERVEROUTPUT.
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.
Cause: You attempted to shut down the database without sufficient privileges.
Action: Enable the privileges required for shutdown.
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, contact Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You attempted to set AUTOPRINT to something other than ON or OFF
Action: Use ON or OFF as arguments with SET AUTOPRINT.
Cause: You tried to declare a REFCURSOR variable against a version of Server Manager 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.
Cause: The package SYS.DBMS_APPLICATION_INFO cannot be accessed.
Action: Check if SYS.DBMS_APPLICATION_INFO exists. Make sure the user has the required privileges to run the package. Ensure that the database is OPEN.
Cause: You attempted to set FETCHROWS to a non-numeric value or a number outside of the legal range.
Action: Use a value from 1 to 999,999.
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.
Cause: A SQL Worksheet command failed to execute properly.
Action: Examine subsequent messages.
Cause: A SQL Worksheet command failed to execute properly.
Action: Examine subsequent messages.
Cause: A SQL Worksheet command failed to execute properly.
Action: Examine subsequent messages.
Cause: A SQL Worksheet command failed to execute properly.
Action: Examine subsequent messages.
Cause: A SQL Worksheet command failed to execute properly.
Action: Examine subsequent messages.
Cause: A SQL Worksheet command failed to execute properly.
Action: Examine subsequent messages.
Cause: A SQL Worksheet command failed to execute properly.
Action: Examine subsequent messages.
Cause: A SQL Worksheet command failed to execute properly.
Action: Examine subsequent messages.
Cause: A SQL Worksheet command failed to execute properly.
Action: Examine subsequent messages.
Cause: An error occurred when you attempted to resize a SQL Worksheet window.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: An error occurred when you attempted to use a SQL Worksheet's split bar.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: An error occurred when you attempted to select text in a SQL Worksheet's History text field.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: An error occurred when you attempted to use the Up and Down buttons in a SQL Worksheet's Command History dialog box.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error in Server Manager.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error in Server Manager.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: The action is not available to you.
Action: Do not change the font.
Cause: You chose either Previous Command or Next Command from the Worksheet menu, and the command did not complete successfully.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: The Server Manager shows the command history as having more commands than are actually present. The command history is corrupted.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You chose the Write Selection from the Worksheet menu without having any text selected in the input or output panes of a SQL Worksheet.
Action: Select text and choose the Write Selection again.
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.
Cause: You specified a filename which was invalid.
Action: Specify a valid filename.
Cause: An error occurred while trying to apply one or more log files from the SQL Worksheet's Recovery dialog box.
Action: Examine subsequent messages.
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.
Cause: You attempted to invoke the MONITOR command from Server Manager line mode. The MONITOR command is no longer available in the Oracle Enterprise Manager version of line mode Server Manager.
Action: Start Oracle Performance Manager to graphically display database performance statistics.
Cause: You gave an invalid command line argument.
Action: Start Server Manager line mode with the correct arguments. These should be of the format command="command". Note that the command should be in quotes.
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.
Cause: Your connect string contained invalid information.
Action: Check the syntax of your connect string. It should be
"[username] [/password] [@instance path]".
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".
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".
Cause: Your connect string contained either a null or invalid host string.
Action: Check the syntax of your connect string.
Cause: Your password has expired or will expire.
Action: Use the "change_passwd" command to change your password.
Cause: You have too many outstanding asynchronous connections.
Action: Close some less important windows or restart Server Manager.
Cause: You have tried to connect using a username that is greater than 30 characters in length.
Action: Specify a shorter username.
Cause: You have tried to connect using a password that is greater than 30 characters in length.
Action: Specify a shorter password.
Cause: You have tried to connect using a hostname that is greater than 80 characters in length.
Action: Use a shorter service name.
Cause: You have attempted to connect to an old version of Oracle.
Action: Server Manager can only run against Version 7.0 or later. You can upgrade the instance, or use the SQL*DBA included with your release of the Oracle database.
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].
Cause: You attempted to close a window which could not be closed.
Action: Call Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error in Server Manager.
Action: Contact Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Messages in this range indicate that you have encountered an internal error. For these messages, contact Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: There is not enough memory.
Action: Free up or add memory.
Cause: There is not enough memory.
Action: Free up or add memory.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The windowing system (usually X Windows) denied permission to connect.
Action: On X Windows, set the DISPLAY to a server which will allow connections.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: An external icon file was not in the expected place.
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.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Messages in this range indicate that you have encountered an internal error. For these messages, contact Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The Oracle Help book has not been installed properly or is corrupted.
Action: Reinstall the help book(s) or the entire product.
Cause: There is not enough memory.
Action: Free up or add memory.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
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.
Cause: The find operation could not locate the specified word.
Action: The word does not exist in the Help document. Try another word.
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.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The Oracle Help book has not been installed properly or has become corrupted.
Action: Reinstall the help book(s) or the entire product.
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.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
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.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: A help request was invalid.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: An entered string begins with a percent sign.
Action: Remove the percent sign from the beginning of the string.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Help.
Action: Call Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The binary resource file could not be opened. It may be in the wrong directory or missing.
Action: Refer to your Oracle platform-specific documentation to make sure Server Manager is installed correctly. Reinstall if necessary. If the problem is not resolved, contact Worldwide Customer Support, specifying the circumstances and complete set of messages leading to the error.
Cause: The text you entered in the Username field is not a valid Oracle username.
Action: Check that the username you entered conforms to the guidelines for Oracle usernames in Chapter 2 of the Oracle8 Server SQL Language Reference Manual.
Cause: You have 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.
Cause: The number entered in the Composite Limit field is not valid.
Action: Make sure there are no extraneous alphabetic or punctuation characters in the Composite Limit field and that the number entered is within the range of valid values.
Cause: The number entered in the Private SGA field is not valid.
Action: Make sure there are no extraneous alphabetic or punctuation characters in the Private SGA field and that the value entered is within the range of valid values.
Cause: The number entered in the Reads per Call field is not valid.
Action: Make sure there are no extraneous alphabetic or punctuation characters in the Reads per Call field and that the value entered is within the range of valid values.
Cause: The number entered in the Reads per Session field is not valid.
Action: Make sure there are no extraneous alphabetic or punctuation characters in the Reads per Session field and that the value entered is within the range of valid values.
Cause: The number entered in the Idle Time field is not valid.
Action: Make sure there are no extraneous alphabetic or punctuation characters in the Idle Time field and that the value entered is within the range of valid values.
Cause: The number entered in the Connect Time field is not valid.
Action: Make sure there are no extraneous alphabetic or punctuation characters in the Connect Time field and that the value entered is within the range of valid values.
Cause: The number entered in the CPU per Call field is not valid.
Action: Make sure there are no extraneous alphabetic or punctuation characters in the CPU per Call field and that the value entered is within the range of valid values.
Cause: The number entered in the CPU per Session field is not valid.
Action: Make sure there are no extraneous alphabetic or punctuation characters in the CPU per Session field and that the value entered is within the range of valid values.
Cause: The number entered in the Session per User field is not valid.
Action: Make sure there are no extraneous alphabetic or punctuation characters in the Sessions per User field and that the value entered is within the range of valid values.
Cause: The value entered in the Profile Name field is not an Oracle identifier.
Action: Make sure the value entered conforms to the guidelines for Oracle identifiers in Chapter 2 of the Oracle8 Server SQL Language Reference Manual.
Cause: The value you have entered in the field is not a valid System Change Number.
Action: In general, you should allow Oracle to determine the System Change Number. Execute the transaction without specifying an System Change Number.
Cause: The value you have entered in the Group Number field is not a number.
Action: The group number must be a positive number, which is not the number of an existing group. When the dialog box appears, Server Manager initializes the Group Number field to be one greater than the greatest log file group number.
Cause: The value you have entered in this New File Size field is not a number.
Action: Type a valid positive number in the New File Size field.
Cause: You have not specified the name of at least one file in the file specification dialog box.
Action: To select a file, use the New button to access the file specification dialog box.
Cause: The Filename field is empty or contains an invalid file.
Action: Enter a valid filename in the field.
Cause: You have not selected the group into which this log file will be placed.
Action: Choose one of the provided groups.
Cause: The To field is empty or contains an invalid file.
Action: Enter a valid filename in the To field.
Cause: The Name field is empty or contains a value that is not a valid Oracle identifier.
Action: Make sure the value you entered conforms to the guidelines for Oracle identifiers in Chapter 2 of the Oracle8 Server SQL Language Reference Manual.
Cause: The list of datafiles does not contain any entries.
Action: Use the New button to access a dialog box to specify a datafile.
Cause: The value you entered in the field is not a positive number.
Action: Either type in a positive number or leave the field empty.
Cause: The value you entered in the field is not a positive number.
Action: Either type in a positive number or leave the field empty.
Cause: The value you entered in the field is not a positive number.
Action: Either type in a positive number or leave the field empty.
Cause: The value you entered in the field is not a positive number.
Action: Either type in a positive number or leave the field empty.
Cause: The value you entered in the field is not a positive number.
Action: Either type in a positive number or leave the field empty.
Cause: The Server Manager could not find the default storage settings for the chosen tablespace.
Action: Refresh the Tablespaces object list and try changing the tablespace again. If the problem persists, contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The Rollback Segment field is empty or contains a value that is not a valid Oracle identifier.
Action: Make sure the value you entered conforms to the guidelines for Oracle identifiers in Chapter 2 of the Oracle8 Server SQL Language Reference Manual.
Cause: The value you entered in the field is not a positive number.
Action: Either enter a positive number or leave the field empty.
Cause: The Maximum Extents value is less than Minimum Extents value.
Action: Change one or both of the values so that the Maximum Extents is greater than or equal to the Minimum Extents.
Cause: You have entered an invalid Oracle identifier in the Role Name field.
Action: Make sure the value entered conforms to the guidelines for Oracle usernames in Chapter 2 of the Oracle8 Server SQL Language Reference Manual.
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.
Cause: You have not specified a user or role in the Grant/Revoke Role dialog box.
Action: Select a user or role from the scrolling list.
Cause: You selected the Role privilege type, clicked OK in the Add Privilege to Role dialog box before you have selected 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.
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.
Cause: With the Object privilege type selected, you clicked the OK button in the Add Privilege to Role dialog box before selecting 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.
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.
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.
Cause: You tried to rename a datafile in an online tablespace.
Action: Take the corresponding tablespace offline and then rename the datafile.
Cause: You tried to rename a datafile in an invalid tablespace.
Action: Repair the tablespace to make it valid and then rename the datafile.
Cause: You entered a negative number or a non-numeric character in the Quota Size field of the Add/Edit Quota dialog box.
Action: Enter a valid quota size in the Quota Size field of the Add/Edit Quota dialog box.
Cause: You did not specify a user in the Users scrolling list of the Assign Profile dialog box.
Action: Specify a user in the Users scrolling list of the Assign Profile dialog box.
Cause: You tried to remove from a tablespace a datafile which belongs to a tablespace.
Action: None. A previously added datafile cannot be removed.
Cause: You entered a schema object that does not follow proper naming or quoting conventions.
Action: Enter a valid schema object name.
Cause: You did not specify a Privilege or Role in the Remove Privilege from the User/Role dialog box.
Action: Select a privilege or role from the list before you click the Remove button.
Cause: The active window does not have a help target. The window is probably a system window rather than a Server Manager window.
Action: None. Refer to your documentation for help.
Cause: Unknown
Action: A second message will include the Oracle Help error. Check the number up in the Oracle Help documentation.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving Oracle Toolkit II.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: Unknown
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: Multiple causes. Additional error messages should clarify the situation.
Action: Examine subsequent messages.
Cause: The Oracle Help book, mahelp.obd, is not properly installed or slfindfile() cannot find it.
Action: Install Oracle Book again or verify the response of slfindfile() for your platform.
Cause: The context string in the maht (help table) did not have a corresponding string in the mahelp.obd book.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error. The file mahelp.obd or the maht must be modified.
Cause: You have encountered an internal error involving the international string support library.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You have encountered an internal error involving the Oracle Toolkit II Resource Manager.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: There was an error in reading from the input source. The input line may be too long.
Action: Break the input line into multiple lines of no more than 1024 bytes per line.
Cause: There was an error in writing to the output file. The output line may be too long.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: There was an error in writing to the output source (generally stdout). The output line may be too long.
Action: If the error occurred in Server Manager Line Mode, execute the query in the Server Manager Worksheet.
Cause: An error occurred during the CORE sprintf routine.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: You attempted to alter a master object group that has not been quiesced.
Action: First Suspend Master Activity on the object group, then try again.
Cause: You attempted to operate on a snapshot object group which has no snapshot repobjects (refresh object group).
Action: Create snapshot repobjects.
Cause: You attempted to use an operation that is only valid for master definition sites.
Action: Perform operation on a master definition site.
Cause: You did not specify an object group on which to operate for the command.
Action: Specify an object group in the Server Manager dialog.
Cause: Each snapshot object group needs a remote refresh master which contains the object group with the same name.
Action: Specify a replication object group in the Server Manager dialog.
Cause: The operation needs a list of one or more remote masters on which to operate.
Action: Using multi-select, specify a list of masters in the Server Manager dialog.
Cause: The operation needs a DDL statement.
Action: Enter a DDL statement in the Server Manager dialog.
Cause: You have attempted a consistent refresh without specifying which snapshots to refresh.
Action: Select one or more snapshots in the Server Manager dialog.
Cause: You have attempted a consistent refresh with the option to specify the refresh method for each snapshot, but you have not specified the refresh methods.
Action: Enter the string of the refresh methods in the Server Manager dialog.
Cause: Multiple object groups were specified for an operation which accepts only one object group.
Action: Select only one object group in the Server Manager dialog.
Cause: The operation needs a list of one or more database links on which to operate.
Action: Using multi-select, specify a list of database links in the Server Manager dialog.
Cause: A surrogate administrator for a replication environment must be specified for the operation.
Action: Specify the surrogate administrator in the Server Manager dialog.
Cause: You must specify a name for the link in order to create a database link.
Action: Specify the name of the remote database to which to form the link.
Cause: You attempted to relocate the master definition site without specifying the new master definition site.
Action: Specify the name of the new master definition site in the Server Manager dialog.
Cause: You attempted to switch the snapshot master without specifying the new master.
Action: Specify the name of the new master in the Server Manager dialog.
Cause: You attempted an operation, such as Execute, which requires deferred transactions to be queued for remote site(s).
Action: No action can be taken in this case.
Cause: You attempted an operation which requires a master site.
Action: Try the operation at a master site for the object group again.
Cause: You attempted an operation on a Destination Database which has no transactions queued for remote execution.
Action: Try this operation again when there are transactions queued for remote execution.
Cause: You attempted an operation which requires deferred transactions to be queued for a specified link.
Action: No action can be taken in this case.
Cause: The number you entered in the indicated field is not valid.
Action: 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.
Cause: The number entered in the indicated field is not valid.
Action: 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.
Cause: A deferred transaction was queued for execution, but the transaction does not contain any operations (i.e. a null transaction).
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: The SQL-actions which generates a timestamp based on SYSDATE could not perform its function.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: An error occurred during the process to extract and store the arguments for a call in a deferred transaction.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: A call, which was queued as part of a deferred transaction, does not have any associated arguments.
Action: Contact Worldwide Customer Support with the circumstances and complete set of messages leading to the error.
Cause: An operation, which was originated 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.
Cause: The operation needs a interval value.
Action: Enter an interval based on SYSDATE in the Server Manager dialog.
Cause: The operation needs a valid date value.
Action: Enter a valid date string, such as "29-MAY-95" or a function of SYSDATE in the Server Manager dialog.
Cause: All the objects in the chosen schema are replicated.
Action: Choose a different schema or add objects to this schema.
Cause: At least one object must be selected from the multi-select list.
Action: Select at least one object in the Server Manager dialog box or click Cancel.
Cause: The operation needs a list of one or more remote masters on which to operate.
Action: Using multi-select, specify a list of masters in the Server Manager dialog.
Cause: You attempted to generate replication support for a table with no PRIMARY KEY without specifying column(s) to act as the PRIMARY KEY.
Action: Choose one or more columns from the Column(s) for Primary Key multi-select list or deselect Generate Replication Support.
Cause: The operation needs a list of one or more remote masters on which to operate.
Action: Using multi-select, specify a list of masters in the Server Manager dialog.
Cause: Server manager cant execute DBMS_DEFER_PRINT.
Action: Make sure CATREPAD.SQL has been run and the current user has execute privileges on DBMS_DEFER_PRINT.
Cause: Cannot get the call arguments for remote procedur.e
Action: No action is available from a snapshot site.
Cause: You did not specify a schema for the object you want to replicate.
Action: Specify a valid schema in the first Object Name field or click the Find Object Button.
Cause: You did not specify a name for the object you want to replicate.
Action: Specify a valid object name in the second Object Name field or click the Find Object Button.
Cause: You specified an object which is already replicated at this site. Objects can only be in one Replication Object Group.
Action: Specify a different object or click the Find Object Button.