Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: An internal error was encountered.
Action: Contact customer support with the circumstances leading to the error and the complete set of error messages.
Cause: SET INSTANCE was used while currently connected to a database.
Action: To change the current instance, DISCONNECT from the database before using SET INSTANCE.
Cause: The requested operation required being connected to the database.
Action: CONNECT to the database using a valid username and password before retrying the operation.
Cause: A command file used as input to SQL*DBA is corrupt or invalid.
Action: Check the file before retrying the operation.
Cause: The size of the SQL statement exceeds SQL*DBA's buffer size.
Action: Shorten the SQL statement by removing extra blanks or by using intermediate statements or views, if necessary.
Cause: An invalid number was specified for the cycle interval.
Action: Enter a number between 1 and 3600 for the cycle interval. The number indicates seconds.
Cause: SQL*DBA tried to open a spool file after the SPOOL filename was specified, but could not open the file. Possible causes are not enough disk space or inadequate privileges to create a file.
Action: Determine why SQL*DBA could not create a new file and retry.
Cause: SPOOL OFF was entered when not currently spooling.
Action: To capture session output, use the SPOOL command to open a file, enter the required commands, and close the file with SPOOL OFF.
Cause: SPOOL OFF could not close the currently open spool file.
Action: Check for an operating system reason that the spool file could not be closed.
Cause: SQL*DBA cannot locate or open the file specified by the PFILE option, because either the file does not exist or SQL*DBA has insufficient privileges to open the file.
Action: Check that the file exists in a location expected by SQL*DBA and can be opened.
Cause: The results returned by a SQL query exceed the internal SQL*DBA buffer.
Action: Use the SET command to increase MAXDATA or decrease ARRAYSIZE.
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: SQL*DBA cannot locate the specified command file.
Action: Check the file's name and SQL*DBA's access to it before retrying.
Cause: An attempt was made to start up an instance while connected to a database.
Action: To start up an instance, first DISCONNECT from the current database.
Cause: A syntax or typing error was made while entering a SQL*DBA command line.
Action: Check the syntax and try again.
Cause: SQL*DBA cannot open the file specified by the ORA_SQLDBAINIT variable, because either the file does not exist or SQL*DBA has insufficient privilege to open the file.
Action: Check that the specified file exists and can be opened.
Cause: File mentioned cannot be opened.
Action: Check that the specified file exists and can be opened.
Cause: An instance name was specified that may be valid, but is too long (exceeds 64 characters).
Action: Check the name of the desired instance and try again.
Cause: Too many command-line arguments were specified to fit in the SQL*DBA buffer.
Action: Specify the arguments over several command lines.
Cause: The file specified using PFILE is too large (exceeds 8K).
Action: Reduce the size of the parameter file before specifying it again using PFILE.
Cause: A command was specified that is not available in this mode.
Action: Switch to a mode where the command is allowed.
Cause: An attempt was made to display a MONITOR display without sufficient privileges for the underlying V$ tables.
Action: Contact the database administrator to obtain the required privileges.
Cause: An attempt was made to use SHOW SGA without sufficient privileges.
Action: Contact the database administrator to obtain the required privileges.
Cause: The specified name may be valid, but is too long (exceeds 127 characters).
Action: Use a shorter name. For example, relocate the file so that its path name is shorter.
Cause: There is not enough memory for the current SQL buffer.
Action: Use the SET command to reduce MAXDATA. Re-invoke MONITOR FILEIO.
Cause: An attempt was made to use SHOW PARAMETERS without sufficient privileges.
Action: Contact the database administrator to obtain the required privileges.
Cause: The instance name was not specified in the CONNECT statement.
Action: Issue the CONNECT statement again, using the proper instance name.
Cause: The SQL statement refers to an undefined bind variable.
Action: Use the VARIABLE statement to define the bind variable and re-execute the query.
Cause: Some database error occurred that prevented a successful CONNECT INTERNAL. For example, a SHUTDOWN ABORT command was issued. This message is usually followed by another message that indicates the problem.
Action: Ensure that the instance is started correctly before trying to CONNECT INTERNAL. You may need to use the STARTUP FORCE command.
Cause: SHOW PARAMETER was given a parameter name that does not exist.
Action: Use a different argument to SHOW PARAMETER.
Cause: A mandatory list element in a dialog contained zero (0) elements.
Action: No action required.
Cause: An attempt was made to see if users were connected, but no users were connected.
Action: No action required.
Cause: There were no in-doubt transactions to resolve.
Action: No action required.
Cause: There were no offline tablespaces to bring online.
Action: No action required.
Cause: There were no tablespaces to take offline. You cannot take the SYSTEM tablespace offline.
Action: No action required.
Cause: There were no offline rollback segments to drop.
Action: No action required.
Cause: There were no offline or partly available rollback segments to bring online.
Action: No action required.
Cause: There were no online rollback segments to take offline.
Action: No action required.
Cause: There were no online tablespaces to backup.
Action: No action required.
Cause: An attempt was made to end an online tablespace backup, but no tables are being backed up.
Action: No action required.
Cause: There were no offline tablespaces to recover.
Action: No action required.
Cause: There were no offline datafiles to recover.
Action: No action required.
Cause: There were no named users to alter or drop.
Action: No action required.
Cause: There were no roles to alter or drop.
Action: No action required.
Cause: There were no users or roles to grant privileges and roles to or to revoke privileges and roles from.
Action: Create some users before granting roles or privileges.
Cause: An instantiation of this monitor was already active.
Action: Cycle through the monitor windows until the monitor becomes visible.
