Release 9.2
Part Number A90842-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| SQL*Plus User's Guide and Reference Release 9.2 Part Number A90842-01 |
|
This appendix lists error messages with prefixes SP2- and CPY- generated by SQL*Plus and iSQL*Plus.
This chapter contains information about:
For error messages with prefixes such as ORA-, TNS- and PLS- generated by Oracle, refer to the Oracle9i Database Error Messages.
Cause: Required variable name was missing after the ACCEPT command.
Action: Re-enter the ACCEPT command with a variable argument to store the input value.
Cause: An invalid option was used in the ACCEPT command.
Action: Check the syntax of the ACCEPT command for the correct option.
Cause: There was no specified text entered after the APPEND command.
Action: Re-enter the APPEND command with the specified text.
Cause: Unable to allocate memory to format computations.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: There was no break defined.
Action: Define a break. Check the syntax of the BREAK command for the correct options.
Cause: An invalid option was used in the BREAK command.
Action: Check the syntax of the BREAK command for the correct options.
Cause: There was no column name after the specified keyword.
Action: Enter a column name after the specified keyword.
Cause: An invalid numeric argument was used in the specified option.
Action: Correct the argument and try again.
Cause: An error has occurred. SQL*Plus was unable to allocate memory for a BREAK command.
Action: Allocate more memory by closing some applications.
Cause: An internal error occurred.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: The search string specified was not found.
Action: Check the search string to make sure that it is valid.
Cause: There was nothing in the SQL buffer when using the CHANGE command.
Action: Make sure the SQL buffer is not empty before using the CHANGE command.
Cause: An invalid option was used in the CHANGE command.
Action: Check the syntax of the CHANGE command for the correct options.
Cause: There was nothing in the SQL buffer when using the DEL command.
Action: Make sure the SQL buffer is not empty before using the DEL command.
Cause: The input value specified was too long.
Action: Re-enter with fewer characters.
Cause: An internal error occurred.
Action: Note the message and number, and contact Oracle Support Services.
Cause: A large SQL or PL/SQL script is being executed from SQL*Plus.
Action: Reduce the size of the SQL statement or PL/SQL block by one of the following:
Cause: The maximum number of lines in a SQL statement or PL/SQL block has been exceeded.
Action: Reduce the number of lines and try again.
Cause: The specified command entered was too long.
Action: Check the command syntax for the limitation.
Cause: The maximum length of the command-line has been exceeded.
Action: Reduce the length of the data in the substitution variables used in the command.
Cause: The command entered was not valid.
Action: Check the syntax of the command you used for the correct options.
Cause: An unknown command was entered.
Action: Check the syntax of the command you used for the correct options.
Cause: No columns have been defined.
Action: No action required.
Cause: The column name specified was not defined.
Action: Retry again with a valid column name.
Cause: An invalid number was used for this option.
Action: Re-try the operation with a valid number.
Cause: An internal error occurred.
Action: Note the message and number, and contact Oracle Support Services.
Cause: The column which the format is based on was not defined.
Action: Use the COLUMN command to make sure the column the format is based on is defined first.
Cause: The column name specified was not defined.
Action: Retry again with a valid column name.
Cause: Unable to allocate memory to process the COLUMN command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: Unable to allocate memory to store the new definition.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: No COMPUTE definition.
Action: Define a COMPUTE. Check the syntax of the COMPUTE command for the correct options.
Cause: The maximum number of COMPUTE functions has been exceeded.
Action: Reduce the number of COMPUTE functions.
Cause: No COMPUTE functions requested.
Action: No action required.
Cause: A label or a function was specified more than once.
Action: Remove the unnecessary labels or functions.
Cause: The ON keyword was specified more than once.
Action: Specify the ON keyword once in the command.
Cause: The OF keyword was specified more than once.
Action: Specify the OF keyword once in the command.
Cause: Unable to allocate memory to process the COMPUTE command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: Missing a keyword in the statement.
Action: Check the syntax of the command you used for the correct options, and use the keyword in the appropriate place.
Cause: The column name was not specified for the keyword.
Action: Specify the column name and try again.
Cause: Unable to allocate memory to process the COMPUTE command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: Unable to allocate memory to process the COMPUTE command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: Unable to allocate memory to process the COMPUTE command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: Nothing was in the SQL buffer to run.
Action: Enter a valid SQL command.
Cause: File name was not specified in the GET or SAVE commands.
Action: Specify a file name and try again.
Cause: Nothing in the SQL buffer when attempting to save the content to a file.
Action: Enter a SQL command to save.
Cause: The file name specified was the word "file".
Action: Put the name in single quotes.
Cause: An attempt was made to append the content of the SQL buffer to a file and the file could not be written. Possible causes:
Action: Take the following actions
Cause: An attempt was made to save the content of the SQL buffer to a file and the file could not be written. Possible causes:
Action: Take the following actions:
Cause: The file was in use.
Action: Release the file from the other process.
Cause: An invalid option was used in the SAVE command.
Action: Check the syntax of the SAVE command for the correct options.
Cause: No DEFINE symbols were defined.
Action: No action required.
Cause: The specified symbol was undefined.
Action: Re-enter the DEFINE command with an assignment clause or a valid symbol or variable name.
Cause: Expecting an equal sign after a symbol or variable name in the DEFINE command.
Action: Specify an equal sign after the symbol or variable name.
Cause: There was no value for the variable or symbol. SQL*Plus expected a value to be assigned to a symbol or variable name after the equal sign.
Action: Specify a value for the symbol or variable.
Cause: Maximum number of variables that can be defined in a SQL*Plus session was exceeded.
Action: UNDEFINE any unused variables to make room for this variable and re-run the command.
Action: The SQL*Plus executable is not linked correctly.
Action: Make a note of the message and the number, then contact the System Administrator to re-link SQL*Plus.
Cause: An internal error occurred.
Action: Note the message and number, and contact the System Administrator.
Cause: Unable to initialize a session to the Oracle instance.
Action: Make a note of the message and the number, then contact the Database Administrator.
Cause: Unable to connect to Oracle after three attempts.
Action: Validate login details and re-try.
Cause: An invalid option was specified for the given command.
Action: Check the syntax of the command you used for the correct options.
Cause: Possible causes:
Action: Take the following actions:
Cause: The line in the file was too long.
Action: No action required or reduce the length of the line.
Cause: Unable to close the specified file as it was being used.
Action: Release the file from the other process.
Cause: On-line SQL*Plus help is not installed in this Oracle instance.
Action: Contact the Database Administrator to install the on-line help.
Cause: There is no help information available for the specified command.
Action: Enter HELP INDEX for a list of topics.
Cause: The option ? is not valid in this command.
Action: Check the syntax of the command you used for the correct options.
Cause: The assignment for the specified variable was incorrect.
Action: Check the syntax of the ACCEPT command for the correct options.
Cause: There are no lines stored in the buffer.
Action: Enter SQL statements into the buffer.
Cause: The line number specified was incorrect.
Action: Check that the line number is correct and try again.
Cause: The line number specified was incorrect.
Action: Check that the line number is correct and try again.
Cause: Invalid line number was specified.
Action: Re-enter with a valid line number.
Cause: The input value was too long.
Action: Reduce the size of the value and re-enter.
Cause: SQL*Plus was unable to login after three attempts.
Action: Make sure the userid and password is correct and try again.
Cause: SQL*Plus was unable to find a value for a substitution variable.
Action: Enter a value for the substitution variable at the prompt.
Cause: Unable to allocate memory for the symbol.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: The PRINT command is not allowed within a PAGE break.
Action: Check the syntax of the PRINT command for the correct options.
Cause: Unable to allocate temporary storage for printing.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: An invalid format was specified for the column.
Action: Specify a valid format for the column.
Cause: The specified variable is not valid for printing.
Action: Check the variable type before re-typing the command.
Cause: The current line size setting is too small to fit the specified data item on a line.
Action: Increase the line size so that the item can be displayed.
Cause: The specified variable could not be created for column - internal error or out of memory.
Action: Check memory usage.
Cause: The specified variable could not be created.
Action: Check the syntax of the command you used for the correct options.
Cause: The specified column was not uniquely qualified in the statement.
Action: Check the syntax of the command you used for the correct options.
Cause: An internal memory error occurred.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: Insufficient memory allocated to the COMPUTE block.
Action: Allocate more memory by closing other applications.
Cause: An invalid SET option name was specified.
Action: Re-enter with either ON or OFF as one of the SET options.
Cause: An internal error occurred.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: A value for a parameter was out of the specified range.
Action: Check the limits of the parameter and enter a value that is within the range.
Cause: Non-numeric value (integer) was entered for a parameter.
Action: Enter a valid numeric value (integer).
Cause: An unknown error occurred in the SET command.
Action: Make a note of the message, then contact Oracle Support Services.
Cause: The specified variable was not defined as a buffer.
Action: Make sure that the buffer variable name is correct and try again.
Cause: The specified character in the SET command cannot be alphanumeric or white-space.
Action: Check the syntax of the command you used for the correct options.
Cause: The value entered was incorrect.
Action: Re-enter with a valid value.
Cause: SET option was missing in the command.
Action: Check the syntax of the command you used for the correct options.
Cause: Invalid option was specified for the command.
Action: Check the syntax of the command you used for the correct options.
Cause: The file is currently being used.
Action: Release the file from the other process.
Cause: Maximum number of nested procedures or scripts was reached.
Action: Reduce the number of nested procedures or scripts.
Cause: Unable to open the specified file.
Action: Check and make sure the file name is valid.
Cause: SQL*Plus was expecting a string at the end of the command, but could not find it.
Action: Retry the command with a valid string. Check the syntax of the command you used for the correct options.
Cause: The DESCRIBE command schema or object did not have a terminating quote.
Action: Close the opening quotation mark with the corresponding closing quotation mark.
Cause: SQL*Plus was expecting a symbol, but it was not specified.
Action: Check the syntax of the command you used for the correct options.
Cause: Specified variable name exceeded the maximum name length.
Action: Reduce the size of the symbol name and re-enter.
Cause: Unable to allocate memory while trying to run the TIMING command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: The TIMING command failed to initialize due to a possible operating system error.
Action: Resolve the operating system error and try again.
Cause: There are no timers recorded to SHOW or STOP.
Action: Check that timers were created with the TIMING command.
Cause: Unable to allocate memory while trying to run the TTITLE or BTITLE command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: An attempt was made to use SPOOL OUT where it is not supported.
Action: No action possible. SPOOL OUT has been disabled possibly because of lack of printing support at the operating system level.
Cause: Possible causes:
Action: Take the following actions:
Cause: An invalid filename was entered in the SPOOL command.
Action: Correct the filename and re-enter.
Cause: The maximum number of characters was exceeded in the SQL buffer after the substitution variable was expanded.
Action: Reduce the length in the substitution variable and try again.
Cause: Unable to allocate memory while trying to run the command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: Unable to allocate memory while trying to run the command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: The command specified is not implemented.
Action: Use the appropriate SQL*Plus command. See the documentation for a list of commands and their correct syntax.
Cause: The command was not recognized, or it is disabled. This occurs if it is a command that does not have any meaning in SQL*Plus (such as a SQL buffer editing command), or it is not allowed for security reasons.
Action: Remove the command from the script. See the documentation for a list of commands and their correct syntax.
Cause: The current edit buffer cannot be undefined.
Action: No action required.
Cause: An buffer name contained an illegal character, for example hyphen (-).
Action: Correct and remove the illegal character from the buffer name.
Cause: A SQL*Plus command option was invalid.
Action: Check the syntax for "The SQLPLUS Command" for the correct usage.
Cause: An invalid option was used in the GET command.
Action: Check the syntax of the command you used for the correct options.
Cause: The value entered in the ACCEPT command was not a number.
Action: Enter a valid number.
Cause: There was no carriage return at the last line of the SQL statement.
Action: Insert a carriage return.
Cause: An option to WHENEVER SQLERROR was invalid in SQL*Plus.
Action: Specify a valid option.
Cause: An option to WHENEVER OSERROR was invalid in SQL*Plus.
Action: Specify a valid option.
Cause: Usage for COPY command was specified incorrectly.
Action: Specify a valid option.
Cause: The FROM and TO clauses were missing from the COPY statement.
Action: Specify at least one clause. Check the syntax of the command you used for the correct options.
Cause: The FROM keyword was in the wrong position in the COPY command.
Action: Check the syntax of the COPY command for the correct options.
Cause: The TO keyword was in the wrong position in the COPY command.
Action: Check the syntax of the COPY command for the correct options.
Cause: A parenthetical list was missing in the column list or the USING keyword is missing in the COPY command.
Action: Check the syntax of the COPY command for the correct options.
Cause: The APPEND keyword was in the wrong position in the COPY command.
Action: Check the syntax of the COPY command for the correct options.
Cause: Invalid SELECT statement found in the COPY command.
Action: Check the syntax of the COPY command for the correct options.
Cause: The CREATE keyword was in the wrong position in the COPY command.
Action: Check the syntax of the COPY command for the correct options.
Cause: The REPLACE keyword was in the wrong position in the COPY command.
Action: Check the syntax of the COPY command for the correct options.
Cause: The maximum number of columns was exceeded in the COPY command.
Action: Reduce the number of columns and try again.
Cause: An invalid or null column name was specified in either the COLUMN or the ATTRIBUTE command.
Action: Retry the operation with a valid column name.
Cause: A missing right parenthesis was identified in the COPY command.
Action: Retry the operation with a comma or right parenthesis.
Cause: USING keyword is missing in the USING clause of the COPY command.
Action: Specify the USING keyword before the USING clause of the COPY command.
Cause: Missing connect string for the database that contains the data to be copied from in the COPY command.
Action: Include a FROM clause to specify a source database other than the default.
Cause: Missing connect string for the database containing the destination table in the COPY command.
Action: Include a TO clause to specify a source database other than the default.
Cause: The INSERT keyword was misplaced in the COPY command.
Action: Check the syntax of the COPY command for the correct options.
Cause: The file specified already exists.
Action: Use the REPLACE option to overwrite the existing file, or specify another file name.
Cause: An attempt was made to use a command that has been explicitly disabled for your schema in this database.
Action: Ask your System Administrator why the Product User Profile (PUP) table has been set to disable this command for your schema.
Cause: An argument was missing in the SET command.
Action: Check the syntax of the SET command for the correct options.
Cause: Either end-of-file was reached, or CTRL-C was entered to cancel the process.
Action: No action required.
Cause: The specified SET option was out of range.
Action: Enter a value within the SET option range and re-try the SET command.
Cause: Incorrect syntax for the VARIABLE command was entered.
Action: Check the syntax of the VARIABLE command for the correct usage.
Cause: Incorrect syntax for the PRINT command was entered.
Action: Check the syntax of the PRINT command for the correct usage.
Cause: Incorrect syntax for the SHOW ERRORS command was entered.
Action: Check the syntax of the SHOW ERRORS command for the correct options.
Cause: The specified bind variable was not declared.
Action: Run the VARIABLE command to check that the bind variables you used in your SQL statement exist. Before running a SQL statement with bind variables, you must use the VARIABLE command to declare each variable.
Cause: Missing file name or an invalid file name specified.
Action: Make sure that a file name was specified.
Cause: Incorrect syntax for the EXECUTE command was entered.
Action: Check the syntax of the EXECUTE command for the correct usage.
Cause: Incorrect syntax for the DESCRIBE command was entered.
Action: Check the syntax of the DESCRIBE command for the correct usage.
Cause: The specified object you tried to DESCRIBE does not exist in the database.
Action: Retry the command with a valid object name.
Cause: The specified object you tried to DESCRIBE does not exist in the package.
Action: Check and make sure that the object name is correct.
Cause: The specified object you tried to DESCRIBE is invalid.
Action: Re-validate the object.
Cause: An invalid character was used in the DESCRIBE command.
Action: Correct the character and try again.
Cause: Invalid sub-object specification in the DESCRIBE command.
Action: Correct the subject specification and try again.
Cause: A column was described within an object in the DESCRIBE command.
Action: Remove the column specification in the DESCRIBE command and try again.
Cause: There are no bind variables declared.
Action: No action required.
Cause: An invalid option was used in the SET SERVEROUTPUT command.
Action: Specify a valid option.
Cause: A SQL statement was attempted that is not FIPS compliant. This error may also occur if a SQL*Plus feature, for example SET AUTOTRACE, that uses SQL specific to Oracle was turned on when using FIPS flagging.
Action: Use SET FLAGGER, and turn FIPS compliance checking OFF, or rewrite the statement.
Cause: An invalid option was specified in the SET FLAGGER command.
Action: Specify a valid option.
Cause: A attempt was made to describe a package as stand-alone, no sub-object such as a procedure was supplied.
Action: Use the DESCRIBE command to describe a sub-object within a package.
Cause: An option to EXIT was invalid in SQL*Plus.
Action: Specify a valid option.
Cause: The specified EXIT variable is non-numeric.
Action: Check the syntax of the EXIT command for the correct usage.
Cause: The function COMPUTE must appear before each LABEL keyword.
Action: Check the syntax of the COMPUTE command for the correct usage.
Cause: Unable to allocate memory to process the command.
Action: Free up additional memory by: closing applications not required; reducing the size of the command, or statement; or by recoding the query to select fewer records.
Cause: Missing label text about the LABEL keyword in the COMPUTE command.
Action: Check the syntax of the COMPUTE command for the correct options.
Cause: An invalid option was used in the SET COLSEP command.
Action: Specify a valid option.
Cause: An invalid option was used in the SET AUTO[COMMIT] command.
Action: Check the syntax of the SET AUTOCOMMIT command for the correct options.
Cause: The value entered in the ACCEPT command was not in the specified datatype.
Action: Correct the datatype and re-enter.
Cause: The value entered in the ACCEPT command was not in the specified format.
Action: Correct the format and try again.
Cause: Required filename was missing after the SET EDITFILE command.
Action: Check the syntax of the SET EDITFILE command for the correct options.
Cause: An invalid option was used in the STORE command.
Action: Check the syntax of the STORE command for the correct options.
Cause: The file specified in the STORE command already exists.
Action: Use the REPLACE option to overwrite the existing file, or specify another file name.
Cause: The STORE command was unable to create the specified file. There may be insufficient disk space, too many open files, or read-only protection on the output directory.
Action: Check that there is sufficient disk space and that the protection on the directory allows file creation.
Cause: The STORE command was unable to close the specified file. Another resource may have locked the file.
Action: Check that the file is not locked before closing it.
Cause: Unable to DESCRIBE the remote object.
Action: No action required.
Cause: An invalid option was used in the SET AUTOTRACE command.
Action: Check the syntax of the SET AUTOTRACE command for the correct options.
Cause: Not enough memory to enable this feature.
Action: Free up additional memory by closing applications not required, or reduce the size of the command, statement or query output.
Cause: Unable to generate the report using AUTOTRACE.
Action: Make a note of the message and the number, then contact the Database Administrator.
Cause: An AUTOTRACE command was issued by a user with insufficient privileges, or who did not have a PLAN_TABLE.
Action: Make sure the user has been granted the PLUSTRACE role, and that a PLAN_TABLE has been created for the user.
Cause: The current version of the Oracle Server is too low for this feature.
Action: Use a higher version of the Oracle Server.
Cause: Unable to construct a unique statement ID in AUTOTRACE.
Action: Check that AUTOTRACE is configured and that you have the PLUSTRACE role enabled.
Cause: Unable to find the session identifier.
Action: Check that the PLUSTRACE role has been granted.
Cause: An error occurred while AUTOTRACE attempted to make a second connection to the database instance.
Action: Check that the database limit on number of active sessions has not been exceeded.
Cause: An error occurred while AUTOTRACE attempted to disconnect from the database instance.
Action: Check that the database is still available.
Cause: No data was found in the PLAN_TABLE while gathering statistics using AUTOTRACE.
Action: Refer to the Oracle9i Database Error Messages for the specified ORA error message.
Cause: The starting line number specified is larger than the ending number.
Action: Re-enter the starting line number with a smaller line number.
Cause: These error messages are warnings that the PRODUCT_USER_PROFILE table has not been built in the SYSTEM account.
Action: The exact format of the file extension and location of the file are system dependent. See the SQL*Plus installation guide provided for your operating system. The script must be run as user SYSTEM.
Cause: Error encountered while printing the specified variable.
Action: Check that the specified variable is correct and try again.
Cause: This message is followed by a successful login to the Oracle Server. The DBMS_APPLICATION package is used to maintain on-line information about a particular application logged onto Oracle. SET APPINFO could not be initialized.
Action: This package is created during the running of the CATPROC.SQL and should be available on all databases from Oracle 7.2. Check that your database is correctly installed.
Cause: The string specified was too long.
Action: Reduce the size of the specified string and re-try the operation.
Cause: The PASSWORD command was issued when there was no connection to the Oracle instance.
Action: Connect to the Oracle database before re-issuing the PASSWORD command.
Cause: SQL*Plus was unable to execute the command because there was no connection to a database.
Action: Connect to a database and re-try the operation.
Cause: An internal error occurred.
Action: Make a note of the message, then contact Oracle Support Services.
Cause: An operating system error occurred with the EDIT command.
Action: Check that the file was created successfully, and verify that the device you are writing to is still available.
Cause: The new passwords entered did not match.
Action: Re-issue the PASSWORD command and make sure that the new passwords are entered correctly.
Cause: The PASSWORD command failed to change passwords because:
Action: Re-issue the PASSWORD command and make sure that the new passwords are entered correctly.
Cause: The NLS character set used in this session does not contain shift sensitive characters. The SET SHIFTINOUT command is unnecessary.
Action: No action required.
Cause: The SP1, SP2, or CPY message file could not be found. SQL*Plus cannot run.
Action: Check the Oracle platform specific documentation to make sure SQL*Plus is installed correctly. This may occur because the ORACLE_HOME environment variable or registry equivalent is not set to the location of the Oracle software. Make sure this value is set correctly. Check that the SQL*Plus binary message files exist in the SQL*Plus message directory, for example $ORACLE_HOME/sqlplus/mesg. Check the value of NLS_LANG environment variable or registry equivalent is correct.
Cause: An invalid character was specified as part of the variable name.
Action: Specify the variable with valid characters.
Cause: An invalid character was specified as part of the variable name.
Action: Specify the variable with alphanumeric characters and '_'.
Cause: A conversion request could not be performed because the string contained alphanumeric characters.
Action: Make sure that the string only contains numeric digits.
Cause: The COPY command is not available in this version of SQL*Plus.
Action: Make a note of the message and the number, then contact Oracle Support Services.
Cause: The length of the bind variable datatype was exceeded.
Action: Reduce the length of the bind variable datatype.
Cause: The type specified is not supported.
Action: Rewrite the query to select the data with types that SQL*Plus supports.
Cause: An invalid date was entered or does not match the format.
Action: Enter a valid date or a date in the required format.
Cause: An invalid option was used in the DESCRIBE command.
Action: Check the syntax of the DESCRIBE command for the correct options.
Cause: Attempted to use the CONNECT AS syntax and specified something other than SYSDBA or SYSOPER.
Action: Correct the syntax and issue the CONNECT command again.
Cause: An invalid option was entered for the SQL*Plus CONNECT command.
Action: Check the syntax for the CONNECT command for the correct usage.
Cause: The specified options of the STARTUP command cannot be used simultaneously.
Action: Check the syntax of the STARTUP command for the correct usage.
Cause: The specified options of the SHUTDOWN command cannot be used simultaneously.
Action: Check the syntax of the SHUTDOWN command for the correct usage.
Cause: The specified options of the ARCHIVE LOG command cannot be used simultaneously.
Action: Check the syntax of the ARCHIVE LOG command for the correct usage.
Cause: An invalid option was used in the SHUTDOWN command.
Action: Check the syntax of the SHUTDOWN command for the correct options.
Cause: An invalid option was used in the ARCHIVE LOG command.
Action: Check the syntax of the ARCHIVE LOG command for the correct options.
Cause: This is a RECOVER DATABASE command prompt, prompting for the redo log files to be applied.
Action: Enter one of the redo log file options.
Cause: There was a problem with the connection instance while issuing the SET INSTANCE command.
Action: Disconnect from the instance before re-issuing the command.
Cause: An invalid connect string was specified.
Action: Check that the connect string is correct.
Cause: The command entered was invalid.
Action: Check the syntax of the command you used for the correct options.
Cause: An invalid option was specified for a given command.
Action: Check the syntax of the command you used for the correct options.
Cause: The maximum length of the command-line was exceeded.
Action: Reduce the length of the data in the substitution variables used in the command.
Cause: An invalid option was used in the SET DESCRIBE command.
Action: Check the syntax of the SET DESCRIBE command for the correct options.
Cause: For security reasons, the command was restricted by the -RESTRICT command-line option.
Action: Ask your Database Administrator why SQL*Plus should be run with a -RESTRICT option.
Cause: An invalid option was used in the SET SQLPLUSCOMPAT[IBLITY] command.
Action: Check the syntax of the SET SQLPLUSCOMPATIBLITY command for the correct options.
Cause: The specified value was not in the range.
Action: Specify a value in the range.
Cause: The PAGESIZE setting was too small to display the specified LINESIZE.
Action: Increase the PAGESIZE to at least match the specified LINESIZE.
Cause: An attempt was made to use a synonym to point to an object that no longer exists where the synonym had the same name as the base object, or an attempt was made to use a synonym that has a circular path that points back to itself.
Action: Make sure that the last synonym in the synonym path points to an object that exists, and that it doesn't point back to itself.
Cause: SQL*Plus was unable to find a message file during program initialization, and could not display error messages or text required for normal operation. The most common cause is that ORACLE_HOME has not been set. Other possible causes are a corrupt or unreadable message file. This message is hard coded (in English) in the SQL*Plus source code so it can be displayed on message file error. It could never be read from this message file because the error occurs only when the message files cannot be opened. This entry in the message file is for documentation purposes only.
Action: Make sure that all environment variables or registry entries needed to run SQL*Plus are set. The variables are platform specific but may include ORACLE_HOME, ORACLE_SID, NLS_LANG, and LD_LIBRARY_PATH. Also check that the file sp1XX.msb is in the $ORACLE_HOME/sqlplus/mesg or %ORACLE_HOME%\sqlplus\mesg directory. The "XX" stands for the country prefix associated with your NLS_LANG environment variable. SQL*Plus reads only one of the sp1XX.msb files. For example sp1ja.msb is read if NLS_LANG is JAPANESE_JAPAN.JA16EUC. If NLS_LANG is not set, then the default (English language) sp1us.msb is used. Check that the appropriate file is of non-zero size and that the file permissions allow it to be read. Note that ".msb" files are binary. The contents may be meaningless when viewed or printed. If you are unsure which language file is being used, unset NLS_LANG and run SQL*Plus to verify it can read the sp1us.msb file.
Cause: No connection to an Oracle server could be made.
Action: Normally occurs after other errors showing that the database is not running, or that the username and password were invalid.
Cause: STARTUP MIGRATE was used to try to startup an Oracle server for a release prior to 9.2.
Action: Check the platform specific environment to verify that you are connecting to an Oracle server that is at least release 9.2.
Cause: The command was not recognized by the SQL*Plus engine, or it is disabled in iSQL*Plus. This occurs if it is a command that does not have any meaning in iSQL*Plus (such as a SQL buffer editing command), or it is not allowed for security reasons, or it is an obsolete command.
Action: Remove the command from your script. If you used a disabled command, check the documentation for a replacement command.
Cause: The command was not recognized or it is disabled in iSQL*Plus. This occurs if it is a command that does not have any meaning in iSQL*Plus (such as a SQL buffer editing command), it is not allowed for security reasons, or it is an obsolete command.
Action: Remove the command from the script. If you used a disabled command, check the documentation for a replacement command.
Cause: The command option is not available in iSQL*Plus. This error usually occurs after SP2-158 or SP2-735. Some options are disabled in a web based context because they have no meaning, they prevent proper operation, or because they pose a security risk.
Action: Remove the option from the command.
Cause: The Username field of the iSQL*Plus Login screen was empty.
Action: Enter a username before attempting to log in.
Cause: An error occurred while parsing the Username and Password fields of the iSQL*Plus Login screen.
Action: Check that you haven't specified a password as part of the username (for example "scott/tiger") and simultaneously put the password in the Password field of the Login screen. The password should appear once only. This error occurs when iSQL*Plus can't determine what password you intended to use.
Cause: An error occurred while trying to read the connection identifier in the Connection Identifier field of the iSQL*Plus Login screen.
Action: If the full connection syntax is used in the Username field (for example "username/password@connect_identifier") then the Connection Identifier field must be empty.
Cause: iSQL*Plus was unable to connect to an Oracle instance, or the username and password were incorrect. An incomplete or incorrect CONNECT command was specified in an iSQL*Plus script.
Action: All authentication information must be included in the CONNECT command in iSQL*Plus. Make sure that both a username and password are used.
Cause: Either the web server (Oracle HTTP server) handling your request has timed out and your session has expired, or the web server has halted. In either case session information (for example, current database connection, values of SET variables) is not available.
Action: Restart the web server (if necessary) and re-login to iSQL*Plus.
Cause: An invalid option to SET MARKUP was entered in iSQL*Plus.
Action: Remove the invalid option.
Cause: An invalid command sequence was entered.
Action: Use the HELP command to show the syntax of SQL*Plus commands.
Cause: All commands in the iSQL*Plus input script have been executed with no explicit output.
Action: No action required.
Cause: The iSQL*Plus session was idle for too long and the context has been removed to free resources for other connections.
Action: Reconnect to iSQL*Plus. The System Administrator configures the time-out period.
Cause: An attempt was made to execute a query from iSQL*Plus when a previous query was still processing. This condition occurs when the browser back button, or stop button is pressed during query processing.
Action: Reconnect to iSQL*Plus.
Cause: The Execute button was clicked when there were no statements in the input area to execute.
Action: Enter statements to run in the input area and click Execute again.
Cause: Save Script was clicked when there were no statements in the input area to save.
Action: Enter statements to save in the input area and click Save Script again.
Cause: An attempt was made to execute a script and output the results to a file when there were no statements in the script to execute.
Action: Make sure the script contains statements to execute and execute the script again.
Cause: Attempted to load a script into the input area with a format the web server cannot understand.
Action: Make sure the script is in a text file and the MIME type settings needed by the browser to recognize the file are set correctly. Typically if you are loading a file with the extension .SQL, make sure the browser has a SQL MIME type.
Cause: This is an informational message. You successfully exited out of iSQL*Plus.
Action: No action required.
Cause: Clicked Load Script but either no file name was specified, or the specified file name did not exist, or if it existed, it was empty.
Action: Enter the name of an existing file into the field and try again, or if the specified file existed but was empty, no action is required.
Cause: Attempted to use the interactive mode of the RECOVER command in iSQL*Plus. Use the autorecovery mode in iSQL*Plus.
Action: Switch SET AUTORECOVERY ON and rerun the RECOVER command.
Cause: A quote was found in the middle of the value portion of a keyword/value pair.
Action: Check for and remove the extra quote.
Cause: No keyword was found in a keyword/value pair of a URL argument.
Action: Check for a missing keyword or a missing equals sign.
Cause: The value for a keyword was missing in a keyword/value pair of a URL.
Action: Check for a missing value or perhaps a missing equals sign.
Cause: Could not find the end quote to match an open quote in a keyword/value pair of a URL.
Action: Check for and insert the matching end quote.
Cause: Already have a keyword/value pair where the value is quoted but extra characters were still found in a URL argument.
Action: Remove the extra characters.
Cause: The keyword was already specified in a previous parameter of a URL argument.
Action: Remove one of the keyword occurrences.
Cause: The script keyword was not specified in the URL.
Action: Add a script keyword/value pair to the URL argument.
Cause: No connection string was supplied in the URL argument for a dynamic report. That is, the userid keyword was not specified.
Action: Login via the interactive login page.
Cause: Incorrect syntax was used for the iSQL*Plus username in the connection string. No AS SYSDBA or AS SYSOPER clause can be included.
Action: Correct the syntax. Use the AS SYSDBA or AS SYSOPER field of the login page for privileged connections.
Cause: The password field of the iSQL*Plus Login screen was empty.
Action: Enter your password before attempting to log in.
Cause: The width or height specified for the input area size was either not a numeric value, or was not in the range 1 to 999.
Action: Re-enter valid numeric values for the input area size.
Cause: An attempt was made to connect to a database that SQL*Plus has not been configured to allow connections to.
Action: If this occurred with the CONNECT command in iSQL*Plus, the "iSQLPlusConnectIdList" configuration parameter in the isqlplus.conf file does not include the connection identifier used. For example, when the command "CONNECT username/password@connect_identifier" is entered, the "connect_identifier" must match a connection identifier in the parameter list. The connection identifier is not case sensitive.
Cause: An attempt was made to enter a value other than a username or '/' in the iSQL*Plus Login screen Username field.
Action: Only a username is allowed in the iSQL*Plus Login screen Username field. A username, or "/" is allowed in the iSQL*Plus DBA Login screen.
Cause: No scripts are available in the history list because no scripts have yet been executed in this session.
Action: Scripts are only made available in the history list after they have been executed in the session.
Cause: The history size specified was either not a numeric value, or was not in the range 0 to 100.
Action: Re-enter a numeric value in the range 0 to 100 for the history size.
Cause: Attempted to use a keyword or variable in an iSQL*Plus URL argument that was not recognized by iSQL*Plus, or that is only available through an iSQL*Plus DBA connection.
Action: Remove the keyword or variable argument, or use the iSQL*Plus DBA URL instead of the iSQL*Plus URL.
Cause: The value entered for the specified keyword was invalid.
Action: Re-enter the command using a valid value for the specified keyword. Valid values for the keyword "type" are "URL" or "TEXT".
Cause: No connect identifier or database instance was specified for the connect command or the SET INSTANCE command.
Action: Re-enter the command and specify a valid connect identifier or database instance.
Cause: iSQL*Plus could not log in to the server because there was no URL "userid" argument, or the information supplied was insufficient or incorrect.
Action: Log in via the Login screen to load the script into the Work Screen.
Cause: iSQL*Plus could not close the timed out session identified by the user session Id.
Action: No action required. This is a debugging message.
Cause: iSQL*Plus has expired the timed out session identified by the user session Id.
Cause: No action required. This is a debugging message.
Cause: iSQL*Plus failed to log in user with the given username, URL and connect identifier.
Action: No action required. This is a debugging message.
Cause: iSQL*Plus logged in user with the given user session Id, username, URL and connect identifier.
Action: No action required. This is a debugging message.
Cause: iSQL*Plus failed to log out user with given user session Id.
Action: No action required. This is a debugging message.
Cause: iSQL*Plus logged out user with given user session Id.
Action: No action required. This is a debugging message.
Cause: Number of active iSQL*Plus sessions is displayed.
Action: No action required. This is a debugging message.
Cause: Displays the number of sessions that have timed out and are to be expired, and the resulting number of active sessions.
Action: No action required. This is a debugging message.
Cause: Displays iSQL*Plus log in details: username, password, connection identifier and privilege.
Action: No action required. This is a debugging message.
Cause: Displays iSQL*Plus log in details: username, password and connection identifier.
Action: No action required. This is a debugging message.
Cause: Displays the complete syntax of the iSQL*Plus connect string: username/password@sid [AS {SYSDBA|SYSOPER}] as produced by the SQL*Plus connect API.
Action: No action required. This is a debugging message.
Cause: An attempt was made to enter a value other than a password in the iSQL*Plus Login screen Password field.
Action: Only a valid password is allowed in the Password field.
Cause: An attempt was made to enter a value other than a valid connection identifier in the iSQL*Plus Login screen Connection Identifier field.
Action: Only a valid connection identifier or a valid alias is allowed in the Connection Identifier field.
Cause: An attempt was made to request a service from iSQL*Plus by manually typing the URL, but no keywords were recognized.
Action: Refer to the iSQL*Plus documentation for the syntax, and types of service that can be manually entered in a URL.
Cause: An attempt was made to request a service from iSQL*Plus by manually typing the URL, but the value specified for a keyword was not recognized.
Action: Refer to the iSQL*Plus documentation for the syntax, and types of service that can be manually entered in a URL.
Cause: After logging in, iSQL*Plus can only process further requests if cookies are enabled on your browser.
Action: Enable cookies on your browser and log in again.
Cause: iSQL*Plus only supports HTTP, HTTPS and FTP.
Action: Change the scheme to one that is supported.
Cause: The iSQL*Plus script that was running has been cancelled by the user. It may have been cancelled by clicking the Cancel button, by re-executing the script, or by clicking any other button or link on the Work screen.
Action: No action required.
Cause: An HTTP error occurred while attempting to fetch the contents of a URL. The URL may have been renamed, removed or be temporarily unavailable.
Action: Check that the URL is spelled correctly and that it is available from the requested server.
Cause: Cannot determine the operating system platform from the retrieved OS version information.
Action: No action required.
Cause: An HTTP error occurred while attempting to fetch the contents of a URL. The URL may have been renamed, removed or be temporarily unavailable.
Action: Check that the URL is spelled correctly and that it is available from the requested server.
Cause: The value entered for the specified keyword was invalid.
Action: Re-enter the command using a valid value for the specified keyword. Valid values for the keyword "action" are "EXECUTE" or "LOAD".
Cause: Cannot determine version of Windows using the get version API.
Action: No action required.
Cause: An attempt was made to log in through the iSQL*Plus URL with AS SYSDBA or AS SYSOPER privilege.
Action: AS SYSDBA or AS SYSOPER privileged login is only permitted through the iSQL*Plus DBA URL. Remove the AS SYSDBA or AS SYSOPER arguments from the login request, or log in through the iSQL*Plus DBA URL.
Cause: The login details supplied in the connect string may contain a duplicate keyword, an incorrect keyword or an out of sequence keyword.
Action: Check the syntax of the connect string and fix or remove the incorrect content.
Cause: In the Script History page, no scripts were selected for loading or deleting from the history list.
Action: Click the checkbox of each script to be loaded or deleted and then click the Load or Delete button.
Cause: An internal error has occurred in iSQL*Plus.
Action: Make a note of the message, then contact Oracle Support Services.
Cause: An internal COPY function has invoked COPY with a create option (flag) value that is out of range.
Action: Please contact Oracle Worldwide Customer Support Services.
Cause: An internal COPY function has been invoked with a logical host number value that is out of range.
Action: Please contact Oracle Worldwide Customer Support Services.
Cause: On an APPEND operation or an INSERT (when the table exists), at least one column name in the destination table does not match the corresponding column name in the optional column name list or in the SELECT command.
Action: Re-specify the COPY command, making sure that the column names and their respective order in the destination table match the column names and column order in the optional column list or in the SELECT command
Cause: On an APPEND operation or an INSERT (when the table exists), at least one column in the destination table does not have the same datatype as the corresponding column in the SELECT command.
Action: Re-specify the COPY command, making sure that the data types for items being selected agree with the destination. Use TO_DATE, TO_CHAR, and TO_NUMBER to make conversions.
Cause: On an APPEND operation or an INSERT (when the table exists), the number of columns in the SELECT command is greater than the number of columns in the destination table.
Action: Re-specify the COPY command, making sure that the number of columns being selected agrees with the number in the destination table.
Cause: On an APPEND operation or INSERT (when the table exists), the number of columns in the SELECT command is less than the number of columns in the destination table.
Action: Re-specify the COPY command, making sure that the number of columns being selected agrees with the number in the destination table.
Cause: On an APPEND operation or an INSERT (when the table exists), the number of columns in the column name list is greater than the number of columns in the destination table.
Action: Re-specify the COPY command, making sure that the number of columns in the column list agrees with the number in the destination table.
Cause: On an APPEND operation or an INSERT (when the table exists), the number of columns in the column name list is less than the number of columns in the destination table.
Action: Re-specify the COPY command, making sure that the number of columns in the column list agrees with the number in the destination table.
Cause: An attempt was made to copy an object datatype that is not supported in the COPY command. Datatypes supported by the COPY command are CHAR, DATE, LONG, NUMBER and VARCHAR2.
Action: Re-specify the COPY command, making sure that the unsupported datatype column is removed. For more information, see the "COPY" command.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
