Oracle Server Manager User's Guide

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.

Action: None.
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: Only a package's specification can be described. The keyword BODY cannot be used with DESCRIBE PACKAGE.

Action: Remove the BODY keyword.