SQL*Plus SP2错误信息

SQL*Plus ErrorMessages

SP2-0002 ACCEPT statement must specifya variable nameCause: Required variable name was missing after the ACCEPT command.Action: Re-enter the ACCEPT command with a variable argument to store the input value.SP2-0003 Ill-formed ACCEPT commandstarting as command_stringCause: An invalid option was used in the ACCEPT command.Action: Check the syntax of the ACCEPT command for the correct option.SP2-0004 Nothing to appendCause: There was no specified text entered after the APPEND command.Action: Re-enter the APPEND command with the specified text.SP2-0006 not enough room to formatcomputationsCause: 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.SP2-0015 no break(s) definedCause: There was no break defined.Action: Define a break. Check the syntax of the BREAK command for the correct options.SP2-0016 break specification muststart with ON/BY or ACROSS keywordCause: An invalid option was used in the BREAK command.Action: Check the syntax of the BREAK command for the correct options.SP2-0017 missing column name afterkeyword_name keywordCause: There was no column name after the specified keyword.Action: Enter a column name after the specified keyword.SP2-0019 invalid numeric argumentto option_name optionCause: An invalid numeric argument was used in the specified option.Action: Correct the argument and try again.SP2-0020 no storage available forcolumn_nameCause: An error has occurred. SQL*Plus was unable to allocate memory for a BREAK command.Action: Allocate more memory by closing some applications.SP2-0022 cannot allocate space tomodify the buffer_name buffer variableCause: 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.SP2-0023 String not foundCause: The search string specified was not found.Action: Check the search string to make sure that it is valid.SP2-0024 Nothing to changeCause: 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.SP2-0025 Invalid change stringCause: An invalid option was used in the CHANGE command.Action: Check the syntax of the CHANGE command for the correct options.SP2-0026 No lines to deleteCause: 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.SP2-0027 Input is too long (> max_characterscharacters) - line ignoredCause: The input value specified was too long.Action: Re-enter with fewer characters.SP2-0029 command buffer space exhaustedCause: 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:Remove extra white space and comments.Re-code to use fewer commands and/or shorter variable names.Place sections of the block into stored (or packaged) procedures, and then call these procedures from the block.SP2-0030 no room for another lineCause: 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.SP2-0038 Command too long. (max_characterscharacters)Cause: The specified command entered was too long.Action: Check the command syntax for the limitation.SP2-0039 command-line overflow whilesubstituting into command_nameCause: 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.SP2-0042 unknown command command_name- rest of line ignoredCause: The command entered was not valid.Action: Check the syntax of the command you used for the correct options.SP2-0044 For a list of known commandsenter HELP and to leave enter EXITCause: An unknown command was entered.Action: Check the syntax of the command you used for the correct options.SP2-0045 no column_name definedCause: No columns have been defined.Action: No action required.SP2-0046 column_name not definedCause: The column name specified was not defined.Action: Retry with a valid column name.SP2-0047 Invalid number for option_nameoptionCause: An invalid number was used for this option.Action: Re-try the operation with a valid number.SP2-0052 like column_name, column_namenot definedCause: 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.SP2-0054 no room to allocate definition_namedefinition. IgnoredCause: 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.SP2-0055 out of room while allocatingportion of new definition_name. Old definition (if any) retainedCause: 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.SP2-0080 no COMPUTES currently definedCause: No COMPUTE definition.Action: Define a COMPUTE. Check the syntax of the COMPUTE command for the correct options.SP2-0081 maximum of number COMPUTEfunctions allowed at a timeCause: The maximum number of COMPUTE functions has been exceeded.Action: Reduce the number of COMPUTE functions.SP2-0082 no COMPUTE functions requestedCause: No COMPUTE functions requested.Action: No action required.SP2-0083 warning: COMPUTE optionfunction_name specified number timesCause: A label or a function was specified more than once.Action: Remove the unnecessary labels or functions.SP2-0084 COMPUTE ON keyword specifiedalreadyCause: The ON keyword was specified more than once.Action: Specify the ON keyword once in the command.SP2-0085 COMPUTE OF keyword specifiedalreadyCause: The OF keyword was specified more than once.Action: Specify the OF keyword once in the command.SP2-0087 no room to allocate COMPUTEcontrol block for column_nameCause: 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.SP2-0088 missing keyword_name keyword.Usage: STORE {SET} filename[.ext] [CRE[ATE]|REP[LACE]|APP[END]]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 appropriateplace.SP2-0092 missing columns for keyword_namekeywordCause: The column name was not specified for the keyword.Action: Specify the column name and try again.SP2-0096 no more room to allocateINTO variable variable_nameCause: 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.SP2-0097 no storage to allocateON column column_nameCause: 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.SP2-0098 no storage to allocateCOMPUTE block for column_nameCause: 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.SP2-0103 Nothing in SQL buffer torunCause: Nothing was in the SQL buffer to run.Action: Enter a valid SQL command. SQL*Plus commands are not stored in the SQL buffer.SP2-0105 Illegal, or missing, entitynameCause: File name was not specified in the GET or SAVE commands.Action: Specify a file name and try again.SP2-0107 Nothing to saveCause: Nothing in the SQL buffer when attempting to save the content to a file.Action: Enter a SQL command to save. SQL*Plus commands are not stored in the SQL buffer.SP2-0108 The filenames CREATE, REPLACE,APPEND, FILE and abbreviations may not be usedCause: An attempt was made to enter a filename using the word FILE, or one of the command keywords CREATE, REPLACE,APPEND, or one of their abbreviations. The filename specified in the command was not permitted.Action: Check the following command syntax and enter a valid filename:command filename[.ext] [CR[EATE]|REP[LACE]|AP[PEND]]where command can be SAVE, SPOOL or STORE SETTo use the command keywords CREATE, REPLACE, APPEND or one of their abbreviations as the filename, or to use the word FILE as the filename, you must enclose it in single quotes.SP2-0109 Cannot append to file file_nameCause: An attempt was made to append the content of the SQL buffer to a file and the file could not be written.Possible causes:An error was encountered when creating the destination file.A directory name specified in the SAVE statement was not found.A system error made it impossible to open the file.Action: Take the following actions:Check that the destination is valid and that there is sufficient space on the destination device.Check the statement for a typing mistake in the directory name. Then issue the statement again after correcting the directory name.SP2-0110 Cannot create save filefile_nameCause: An attempt was made to save the content of the SQL buffer to a file and the file could not be written. Possiblecauses:An error was encountered when creating the destination file.A directory name specified in the SAVE statement was not found.A system error made it impossible to open the file.Action: Take the following actions:Check that the destination is valid and that there is sufficient space on the destination device.Check the statement for a typing mistake in the directory name. Then issue the statement again after correcting the directory name.SP2-0111 Cannot close save filefile_nameCause: The file was in use.Action: Release the file from the other process.SP2-0116 Illegal SAVE commandCause: An invalid option was used in the SAVE command.Action: Check the syntax of the SAVE command for the correct options.SP2-0134 no symbols currently definedCause: No DEFINE symbols were defined.Action: No action required.SP2-0135 Symbol symbol_name is UNDEFINEDCause: The specified symbol was undefined.Action: Re-enter the DEFINE command with an assignment clause or a valid symbol or variable name.SP2-0136 DEFINE requires an equalsign (=)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.SP2-0137 DEFINE requires a valuefollowing equal signCause: There was no value for the variable or symbol. SQL*Plus expected a value to be assigned to a symbol or variablename after the equal sign.Action: Specify a value for the symbol or variable.SP2-0138 no room to add substitutionvariable variableCause: 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.SP2-0146 Unable to allocate dynamicspace needed (number_of_bytes bytes) - exitingCause: An internal error occurred.Action: Note the message and number, and contact the System Administrator.SP2-0152 ORACLE may not be functioningproperlyCause: Unable to initialize a session to the Oracle instance.Action: Make a note of the message and the number, then contact the Database Administrator.SP2-0157 unable to CONNECT to ORACLEafter 3 attempts, exiting SQL*PlusCause: Unable to connect to Oracle after three attempts.Action: Validate login details and re-try.SP2-0158 unknown command_name option"option_name"Cause: An invalid option was specified for the given command.Action: Check the syntax of the command you used for the correct options.SP2-0160 Unable to open file_nameCause: Possible causes:The file was not found under the specified name in the specified location.File lacked the necessary privileges to open the file.A system error made it impossible to open the file.Action: Take the following actions:Make sure the file name specified is stored in the appropriate directory.Make sure that the file has the privileges necessary for access. If it does not then change privileges accordingly.Consult operating system documentation or contact the System Administrator.SP2-0161 line line_number truncatedCause: The line in the file was too long.Action: No action required or reduce the length of the line.SP2-0162 unable to close file_nameCause: Unable to close the specified file as it was being used.Action: Release the file from the other process.SP2-0171 HELP system not availableCause: Command-line SQL*Plus help is not installed in this Oracle instance.Action: Command-line SQL*Plus help is not installed in this Oracle instance. Use the sqlplus/admin/help/hlpbld.sqlscript to install HELP on this database:

sqlplus system @hlpbld.sql helpus.sql

SP2-0172 No HELP matching this topicwas found.Cause: There is no help information available for the specified command.Action: Enter HELP INDEX for a list of topics.SP2-0176 Option ? Is invalidCause: The option ? is not valid in this command.Action: Check the syntax of the command you used for the correct options.SP2-0187 error in variable assignmentCause: The assignment for the specified variable was incorrect.Action: Check the syntax of the ACCEPT command for the correct options.SP2-0223 No lines in buffer_namebufferCause: There are no lines stored in the buffer.Action: Enter SQL statements into the buffer.SP2-0224 invalid starting line numberCause: The line number specified was incorrect.Action: Check that the line number is correct and try again.SP2-0225 invalid ending line numberCause: The line number specified was incorrect.Action: Check that the line number is correct and try again.SP2-0226 Invalid line number current_line_numberCause: Invalid line number was specified.Action: Re-enter with a valid line number.SP2-0232 Input too long. Must beless than number_of_characters charactersCause: The input value was too long.Action: Reduce the size of the value and re-enter.SP2-0233 Unable to obtain useridafter number_of_attempts attempts. Retry commandCause: SQL*Plus was unable to login after three attempts.Action: Make sure the userid and password is correct and try again.SP2-0240 Enter value for variable_name:Cause: SQL*Plus was unable to find a value for a substitution variable.Action: Enter a value for the substitution variable at the prompt.SP2-0241 No room for symbol symbol_name(not defined)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.SP2-0244 Cannot issue a PRINT commandwithin a PAGE breakCause: The PRINT command is not allowed within a PAGE break.Action: Check the syntax of the PRINT command for the correct options.SP2-0245 Unable to allocate temporarystorage for printingCause: 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.SP2-0246 Illegal FORMAT string column_format_nameCause: An invalid format was specified for the column.Action: Specify a valid format for the column.SP2-0249 variable_name not a validvariable type for printingCause: The specified variable is not valid for printing.Action: Check the variable type before re-typing the command.SP2-0253 data item line_number (data_item_name)will not fit on lineCause: 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.SP2-0258 could not create variablevariable_name for column column_nameCause: The specified variable could not be created for column – internal error or out of memory.Action: Check memory usage.SP2-0259 could not create variablevariable_name for COMPUTE INTOCause: The specified variable could not be created.Action: Check the syntax of the command you used for the correct options.SP2-0260 computation for columncolumn_name not uniquely qualified. could be for table table_name or table_name. computation ignored.Cause: The specified column was not uniquely qualified in the statement.Action: Check the syntax of the command you used for the correct options.SP2-0262 no room to allocate CCBDEFpointer arrayCause: 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.SP2-0263 no room to allocate COMPUTEblock for column_name ON page/report/column_nameCause: Insufficient memory allocated to the COMPUTE block.Action: Allocate more memory by closing other applications.SP2-0265 option_name must be setON or OFFCause: An invalid SET option name was specified.Action: Re-enter with either ON or OFF as one of the SET options.SP2-0266 internal error: buffer(buffer_size) smaller than l (buffer_limit)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.SP2-0267 option_name option parameter_numberout of range (lower_range through upper_range)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.SP2-0268 option_name option nota valid numberCause: Non-numeric value (integer) was entered for a parameter.Action: Enter a valid numeric value (integer).SP2-0271 variable_name is not abuffer variableCause: The specified variable was not defined as a buffer.Action: Make sure that the buffer variable name is correct and try again.SP2-0272 character_name charactercannot be alphanumeric or white-spaceCause: 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.SP2-0277 entered_value value notvalidCause: The value entered was incorrect.Action: Re-enter with a valid value.SP2-0281 option_name missing setoption Usage: SET SHIFT[INOUT] [VIS[IBLE|INV[ISIBLE]]or Usage: SET MARKUP HTML [ON|OFF] [HEAD text] [BODY text] [TABLE text] [ENTMAP [ON|OFF]] [SPOOL [ON|OFF]] [PRE[FORMAT] [ON|OFF]][-M[ARKUP] \"HTML [ON|OFF] [HEAD text] [BODY text]Cause: SET option was missing in the command.Action: Check the syntax of the command you used for the correct options.SP2-0306 Invalid option Usage: CONN[ECT][login] [AS {SYSDBA|SYSOPER}]Where <login> ::= <username>[/<password>][@<connect_string>] | /or Usage: CONN[ECT] username/password[@connect_identifier] [AS {SYSOPER|SYSDBA}]or: CONN[ECT] /[@connect_identifier]AS {SYSOPER|SYSDBA}Cause: Invalid option was specified for the command.Action: Check the syntax of the command you used for the correct options.SP2-0308 cannot close spool fileCause: The file is currently being used.Action: Release the file from the other process.SP2-0309 SQL*Plus command proceduresmay only be nested to a depth of number_of_nested_proceduresCause: Maximum number of nested procedures or scripts was reached.Action: Reduce the number of nested procedures or scripts.SP2-0310 unable to open file file_nameCause: Unable to open the specified file.Action: Check and make sure the file name is valid.SP2-0311 string expected but notfoundCause: 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.SP2-0312 missing terminating quote(quote_type)Cause: The DESCRIBE command schemaor object did not have a terminating quote.Action: Close the opening quotation mark with the corresponding closing quotation mark.SP2-0317 expected symbol name ismissingCause: SQL*Plus was expecting a symbol, but it was not specified.Action: Check the syntax of the command you used for the correct options.SP2-0318 symbol name beginning variable_name..is too long (max max_name_length) Illegal variable name variable_nameCause: Specified variable name exceeded the maximum name length.Action: Reduce the size of the symbol name and re-enter.SP2-0323 no room to add timing element- request deniedCause: 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.SP2-0324 operating system timingerror error_option_number - request deniedCause: The TIMING command failed to initialize due to a possible operating system error.Action: Resolve the operating system error and try again.SP2-0325 no timing elements to option_nameCause: There are no timers recorded to SHOW or STOP.Action: Check that timers were created with the TIMING command.SP2-0328 no room to allocate titlebufferCause: 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.SP2-0331 SPOOL OUT disabledCause: 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 operatingsystem level.SP2-0332 Cannot create spool fileCause: Possible causes:Insufficient privileges to create a file.A system error made it impossible to create a file.Action: Take the following actions:Change privileges to allow creation of the file.Consult the operating system documentation or contact the System Administrator.SP2-0333 Illegal spool file name:spool_name (bad character: 'character_name')Cause: An invalid filename was entered in the SPOOL command.Action: Correct the filename and re-enter.SP2-0341 line overflow during variablesubstitution (>number_of_characters characters at line line_number)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.SP2-0357 Out of temporary storageCause: 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.SP2-0359 memory exhaustedCause: 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.SP2-0381 command_name is not availableCause: 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.SP2-0382 The command_name commandis not availableCause: The command was not recognized, or it is disabled. This occurs if it is a command that does not have anymeaning 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.SP2-0392 Cannot UNDEFINE the currentedit bufferCause: The current edit buffer cannot be undefined.Action: No action required.SP2-0394 Illegal buffer name: buffer_nameCause: A buffer name contained an illegal character, for example hyphen (-).Action: Correct and remove the illegal character from the buffer name.SP2-0423 Illegal GET commandCause: An invalid option was used in the GET command.Action: Check the syntax of the command you used for the correct options.SP2-0425 value is not a valid datatypeCause: The value entered in the ACCEPT command was not valid for the specified datatype.Action: Enter a valid value, e.g. 123 for a NUMBER variable.SP2-0426 Input truncated to number_of_characterscharactersCause: There was no carriage return at the last line of the SQL statement.Action: Insert a carriage return.SP2-0495 FROM and TO clauses bothmissing; specify at least oneCause: 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.SP2-0496 Misplaced FROM clauseCause: The FROM keyword was in the wrong position in the COPY command.Action: Check the syntax of the COPY command for the correct options.SP2-0497 Misplaced TO clauseCause: The TO keyword was in the wrong position in the COPY command.Action: Check the syntax of the COPY command for the correct options.SP2-0498 Missing parenthetical columnlist or USING keywordCause: 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.SP2-0499 Misplaced APPEND keywordCause: The APPEND keyword was in the wrong position in the COPY command.Action: Check the syntax of the COPY command for the correct options.SP2-0501 Error in SELECT statement:Oracle_database_error_messageCause: Invalid SELECT statement found in the COPY command.Action: Check the syntax of the COPY command for the correct options.SP2-0513 Misplaced CREATE keywordCause: The CREATE keyword was in the wrong position in the COPY command.Action: Check the syntax of the COPY command for the correct options.SP2-0514 Misplaced REPLACE keywordCause: The REPLACE keyword was in the wrong position in the COPY command.Action: Check the syntax of the COPY command for the correct options.SP2-0515 Maximum number of columns(max_num_columns) exceededCause: The maximum number of columns was exceeded in the COPY command.Action: Reduce the number of columns and try again.SP2-0516 Invalid command_name nameNULL encounteredCause: 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.SP2-0517 Missing comma or rightparenthesisCause: A missing right parenthesis was identified in the COPY command.Action: Retry the operation with a comma or right parenthesis.SP2-0518 Missing USING clauseCause: 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.SP2-0519 FROM string missing OracleNet @database specificationCause: 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.SP2-0520 TO string missing OracleNet @database specificationCause: 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.SP2-0526 Misplaced INSERT keywordCause: The INSERT keyword was misplaced in the COPY command.Action: Check the syntax of the COPY command for the correct options.SP2-0540 File file_name alreadyexists. Use SAVE filename[.ext] REPLACECause: The file specified already exists.Action: Use the REPLACE option to overwrite the existing file, or specify another file name.SP2-0544 Command command_name disabledin Product User ProfileCause: An attempt was made to use a command that has been explicitly disabled for your schemain this database.Action: Ask your System Administrator why the Product User Profile (PUP) table has been set to disable this commandfor your schema.SP2-0545 SET command requires anargumentCause: An argument was missing in the SET command.Action: Check the syntax of the SET command for the correct options.SP2-0546 User requested Interruptor EOF detectedCause: Either end-of-file was reached, or CTRL-C was entered to cancel the process.Action: No action required.SP2-0547 option_name option valueout of range (lower_value through upper_value)Cause: The specified SET option was out of range.Action: Enter a value within the SET option range and re-try the SET command.SP2-0548 Usage: VAR[IABLE] [<variable>[NUMBER | CHAR | CHAR (n [CHAR|BYTE]) |VARCHAR2 (n [CHAR|BYTE]) | NCHAR | NCHAR (n) |NVARCHAR2 (n) | CLOB | NCLOB | REFCURSOR |BINARY_FLOAT | BINARY_DOUBLE]]Cause: Incorrect syntax for the VARIABLE command was entered.Action: Check the syntax of the VARIABLE command for the correct usage.SP2-0549 Usage: PRINT [:<variable>...]Cause: Incorrect syntax for the PRINT command was entered.Action: Check the syntax of the PRINT command for the correct usage.SP2-0550 Usage: SHOW ERRORS [{FUNCTION| PROCEDURE | PACKAGE | PACKAGE BODY | TRIGGER | VIEW | TYPE | TYPE BODY | DIMENSION| JAVA SOURCE | JAVA CLASS} [schema.]name]Cause: Incorrect syntax for the SHOW ERRORS command was entered.Action: Check the syntax of the SHOW ERRORS command for the correct options.SP2-0552 Bind variable variable_namenot declaredCause: 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. Beforerunning a SQL statement with bind variables, you must use the VARIABLE command to declare each variable.SP2-0556 Invalid file name Usage:STORE {SET} filename[.ext] [CRE[ATE]|REP[LACE]|APP[END]]or Unable to complete EDIT commandCause: Missing file name or an invalid file name specified.Action: Make sure that a file name was specified.SP2-0559 Usage: EXEC[UTE] statementCause: Incorrect syntax for the EXECUTE command was entered.Action: Check the syntax of the EXECUTE command for the correct usage.SP2-0560 Usage: DESCRIBE [schema.]object[.subobject|@db_link][column]Cause: Incorrect syntax for the DESCRIBE command was entered.Action: Check the syntax of the DESCRIBE command for the correct usage.SP2-0561 Object does not existCause: The specified object you tried to DESCRIBE does not exist in the database.Action: Retry the command with a valid object name.SP2-0562 Object does not exist inpackageCause: The specified object you tried to DESCRIBE does not exist in the package.Action: Check and make sure that the object name is correct.SP2-0564 Object object_name is INVALID,it may not be describedCause: The specified object you tried to DESCRIBE is invalid.Action: Re-validate the object.SP2-0565 Illegal identifierCause: An invalid character was used in the DESCRIBE command.Action: Correct the character and try again.SP2-0566 Illegal sub-object specificationCause: Invalid sub-object specification in the DESCRIBE command.Action: Correct the subject specification and try again.SP2-0567 Illegal column specificationfor PL/SQL objectCause: A column was described within an object in the DESCRIBE command.Action: Remove the column specification in the DESCRIBE command and try again.SP2-0568 No bind variables declaredCause: There are no bind variables declared.Action: No action required.SP2-0570 Usage: SET SERVEROUTPUT{ON | OFF} [SIZE {n | UNL[IMITED]} ] [FOR[MAT] {WRA[PPED] | WOR[D_WRAPPED] | TRU[NCATED] } ]Cause: An invalid option was used in the SET SERVEROUTPUT command.Action: Specify a valid option.SP2-0575 Use of Oracle SQL featurenot in SQL92 Entry |Intermediate|Full LevelCause: A SQL statement was attempted that is not FIPS compliant. May also occur if a SQL*Plus feature, for exampleSET AUTOTRACE, that uses Oracle-specific SQL was turned on when you are using FIPS flagging.Action: Use SET FLAGGER, and turn FIPS compliance checking OFF, or rewrite the statement.SP2-0577 Usage: SET FLAGGER {OFF| ENTRY | INTERMEDIATE | FULL}Cause: An invalid option was specified in the SET FLAGGER command.Action: Specify a valid option.SP2-0581 Object object_name is apackage; use 'DESCRIBE <package>.<procedure>'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.SP2-0582 Usage: {EXIT | QUIT} [SUCCESS| FAILURE | WARNING | n |<variable> | :<bindvariable>] [COMMIT | ROLLBACK]Cause: An option to EXIT was invalid in SQL*Plus.Action: Specify a valid option.SP2-0584 EXIT variable variable_namewas non-numericCause: The specified EXIT variable is non-numeric.Action: Check the syntax of the EXIT command for the correct usage.SP2-0590 A COMPUTE function mustappear before each LABEL keywordCause: The function COMPUTE must appear before each LABEL keyword.Action: Check the syntax of the COMPUTE command for the correct usage.SP2-0591 Unable to allocate dynamicspace needed (number_of_bytes bytes) Try reducing ARRAYSIZE or the number of columns selectedCause: 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.SP2-0593 Label text must followthe LABEL keywordCause: Missing label text about the LABEL keyword in the COMPUTE command.Action: Check the syntax of the COMPUTE command for the correct options.SP2-0594 Usage: SET COLSEP {" "| text}Cause: An invalid option was used in the SET COLSEP command.Action: Specify a valid option.SP2-0596 Usage: SET AUTO[COMMIT]{OFF | ON | IMM[EDIATE] | n}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.SP2-0597 datatype _name is not avalid datatype _name formatCause: The value entered in the ACCEPT command was not in the specified datatype.Action: Correct the datatype and re-enter.SP2-0598 value_name does not matchinput format "format_name"Cause: The value entered in the ACCEPT command was not in the specified format.Action: Correct the format and try again.SP2-0599 Usage: SET EDITF[ILE] filename[.ext]Cause: Required filename was missing after the SET EDITFILE command.Action: Check the syntax of the SET EDITFILE command for the correct options.SP2-0603 Usage: Illegal STORE command.Usage: STORE {SET} filename[.ext] [CRE[ATE]|REP[LACE]|APP[END]]Cause: An invalid option was used in the STORE command.Action: Check the syntax of the STORE command for the correct options.SP2-0605 File file_name alreadyexists. Use another name or STORE {SET} filename[.ext] REPLACECause: The file specified in the STORE command already exists.Action: Use the REPLACE option to overwrite the existing file, or specify another file name.SP2-0606 Cannot create file_namefileCause: The STORE command was unable to create the specified file. There may be insufficient disk space, too manyopen files, or read-only protection on the output directory.Action: Check that there is sufficient disk space and that the protection on the directory enables file creation.SP2-0607 Cannot close file_namefileCause: 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.SP2-0608 Object object_name is aremote object, cannot further describeCause: Unable to DESCRIBE the remote object.Action: No action required.SP2-0609 Usage: SET AUTOT[RACE]{OFF | ON | TRACE[ONLY] } [EXP[LAIN]] [STAT[ISTICS] ]Cause: An invalid option was used in the SET AUTOTRACE command.Action: Check the syntax of the SET AUTOTRACE command for the correct options.SP2-0610 Error initializing feature_nameCause: Not enough memory to enable this feature.Action: Free up additional memory by closing applications not required, or reduce the size of the command, statementor query output.SP2-0612 Error generating report_namereportCause: Unable to generate the report using AUTOTRACE.Action: Make a note of the message and the number, then contact the Database Administrator.SP2-0613 Unable to verify PLAN_TABLEformat or existence Error enabling autotrace_report reportCause: 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 theuser.SP2-0614 Server version too lowfor this featureCause: The current version of the Oracle Server is too low for this feature.Action: Use a higher version of the Oracle Server.SP2-0617 Cannot construct a uniqueSTATEMENT_IDCause: Unable to construct a unique statement ID in AUTOTRACE.Action: Check that AUTOTRACE is configured and that you have the PLUSTRACE role enabled.SP2-0618 Cannot find the SessionIdentifier. Check PLUSTRACE role is enabled Error enabling autotrace_report reportCause: Unable to find the session identifier.Action: Check that the PLUSTRACE role has been granted.SP2-0619 Error while connectingCause: 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.SP2-0620 Error while disconnectingCause: An error occurred while AUTOTRACE attempted to disconnect from the database instance.Action: Check that the database is still available.SP2-0621 Error ORA -error_numberwhile gathering statisticsCause: No data was found in the PLAN_TABLE while gathering statistics using AUTOTRACE.Action: Refer to the Oracle Database Error Messages for the specified ORA error message.SP2-0622 Starting line number mustbe less than ending line numberCause: The starting line number specified is larger than the ending number.Action: Re-enter the starting line number with a smaller line number.SP2-0623 Error accessing PRODUCT_USER_PROFILE.Warning: Product user profile information not loaded! You may need to run PUPBLD.SQL as SYSTEMCause: 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*Plusinstallation guide provided for your operating system. The script must be run as user SYSTEM.SP2-0625 Error printing variablevariable_nameCause: Error encountered while printing the specified variable.Action: Check that the specified variable is correct and try again.SP2-0626 Error accessing packageDBMS_APPLICATION_INFO You may need to install the Oracle Procedural option SET APPINFO requires Oracle Server Release 7.2 or laterCause: This message is followed by a successful login to the Oracle Server. The DBMS_APPLICATION package is usedto 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 databasesfrom Oracle 7.2. Check that your database is correctly installed.SP2-0631 String beginning string_nameis too long. Maximum size is 1 characteror Maximum size is string_length charactersCause: The string specified was too long.Action: Reduce the size of the specified string and re-try the operation.SP2-0640 Not connected.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.SP2-0641 command_name requires connectionto serverCause: 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.SP2-0642 SQL*Plus internal errorstate error_state context error_number. Unsafe to proceedor Unable to proceedCause: An internal error occurred.Action: Make a note of the message, then contact Oracle Support Services.SP2-0645 Operating System erroroccurred Unable to complete EDIT commandCause: 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.SP2-0650 New passwords do not matchCause: The new passwords entered did not match.Action: Re-issue the PASSWORD command and make sure that the new passwords are entered correctly.SP2-0659 Password unchangedCause: The PASSWORD command failed to change passwords because:No passwords were given.The new passwords did not match.Action: Re-issue the PASSWORD command and make sure that the new passwords are entered correctly.SP2-0666 WARNING: SHIFTINOUT onlyaffects shift sensitive character setsCause: The NLS character set used in this session does not contain shift sensitive characters. The SET SHIFTINOUTcommand is unnecessary.Action: No action required.SP2-0667 Message file facility<lang>.msbnot foundCause: 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 mayoccur 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.SP2-0668 Invalid variable nameCause: An invalid character was specified as part of the variable name.Action: Specify the variable with valid characters.SP2-0669 Valid characters are alphanumericsand '_'Cause: An invalid character was specified as part of the variable name.Action: Specify the variable with alphanumeric characters and '_'.SP2-0670 Internal number conversionfailedCause: A conversion request could not be performed because the string contained alphanumeric characters.Action: Make sure that the string only contains numeric digits.SP2-0675 COPY command not availableCause: 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.SP2-0676 Bind variable length cannotexceed variable_length units_of_variableCause: The length of the bind variable datatype was exceeded.Action: Reduce the length of the bind variable datatype.SP2-0678 Column or attribute typecan not be displayed by SQL*PlusCause: The type specified is not supported.Action: Rewrite the query to select the data with types that SQL*Plus supports.SP2-0685 The date entered_variableis invalid or format mismatched formatCause: An invalid date was entered or does not match the format.Action: Enter a valid date or a date in the required format.SP2-0686 Usage: DESCRIBE [schema.]object[@db_link]Cause: An invalid option was used in the DESCRIBE command.Action: Check the syntax of the DESCRIBE command for the correct options.SP2-0692 Usage: CONN[ECT] [logon][AS {SYSDBA|SYSOPER}]Where <logon> ::= <username>[/<password>][@<connect_string>] | /Cause: An invalid option was entered for the SQL*Plus CONNECT command.Action: Check the syntax for the CONNECT command for the correct usage.SP2-0714 Invalid combination ofSTARTUP optionsCause: The specified options of the STARTUP command cannot be used simultaneously.Action: Check the syntax of the STARTUP command for the correct usage.SP2-0715 Invalid combination ofSHUTDOWN optionsCause: The specified options of the SHUTDOWN command cannot be used simultaneously.Action: Check the syntax of the SHUTDOWN command for the correct usage.SP2-0716 Invalid combination ofARCHIVE LOG optionsCause: 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.SP2-0717 Illegal SHUTDOWN optionCause: An invalid option was used in the SHUTDOWN command.Action: Check the syntax of the SHUTDOWN command for the correct options.SP2-0718 Illegal ARCHIVE LOG optionCause: An invalid option was used in the ARCHIVE LOG command.Action: Check the syntax of the ARCHIVE LOG command for the correct options.SP2-0728 Specify log: {<RET>=suggested| filename | AUTO | CANCEL}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.SP2-0729 Cannot SET INSTANCE whileconnected to a databaseCause: There was a problem with the connection instance while issuing the SET INSTANCE command.Action: Disconnect from the instance before re-issuing the command.SP2-0733 Invalid connect stringCause: An invalid connect string was specified.Action: Check that the connect string is correct.SP2-0734 Unknown command beginningcommand_name ... - rest of line ignoredCause: The command entered was invalid.Action: Check the syntax of the command you used for the correct options.SP2-0735 Unknown command_name optionbeginning option_nameCause: An invalid option was specified for a given command.Action: Check the syntax of the command you used for the correct options.SP2-0736 Command line overflow whilesubstituting into line beginning string_nameCause: The maximum length of the command line was exceeded.Action: Reduce the length of the data in the substitution variables used in the command.SP2-0737 Usage: SET DESCRIBE [DEPTH{1|n|ALL}] [LINENUM {ON|OFF}] [INDENT {ON|OFF}]Cause: An invalid option was used in the SET DESCRIBE command.Action: Check the syntax of the SET DESCRIBE command for the correct options.SP2-0738 Restricted command command_namenot availableCause: 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.SP2-0745 Usage: SET SQLPLUSCOMPAT[IBILITY]version.release.[update]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.SP2-0746 command_option option outof range (lower through upper )Cause: The specified value was not in the range.Action: Specify a value in the range.SP2-0747 PAGESIZE must be at leastmax_page_size to run this query with LINESIZE line_sizeCause: The PAGESIZE setting was too small to display the specified LINESIZE.Action: Increase the PAGESIZE to at least match the specified LINESIZE.SP2-0749 Cannot resolve circularpath of synonym synonym_nameCause: An attempt was made to use a synonym to point to an object that no longer exists where the synonym had thesame 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'tpoint back to itself.SP2-0750 ORACLE_HOME may not besetCause: SQL*Plus was unable to find a message file during program initialization, and could not display error messagesor 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. On Windows the SQLPLUS registry entry may be invalid.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 themessage 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 variablesare platform specific but may include ORACLE_HOME, ORACLE_SID, NLS_LANG, and LD_LIBRARY_PATH.On Windows if the environment variable called SQLPLUS is set, it must contain the directory name of the SQL*Plus message files, for example %ORACLE_HOME%\sqlplus\mesg.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 thatthe 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.SP2-0751 Unable to connect to Oracle.Exiting SQL*PlusCause: 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 passwordwere invalid.SP2-0752 Usage: -C[OMPATIBILITY]version.release.[update]Cause: An invalid option was used in the -C[OMPATIBILITY] command option.Action: Check the syntax of the SQL*Plus executable for the correct options.SP2-0753 STARTUP with MIGRATE onlyvalid with Oracle 9.2 or greaterCause: 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 atleast release 9.2.SP2-0754 FROM clause cannot containAS SYSDBA or AS SYSOPERCause: The COPY command does not support AS SYSDBA or AS SYSOPER connections.Action: Remove AS SYSDBA or AS SYSOPER from the FROM clause.SP2-0755 TO clause cannot containAS SYSDBA or AS SYSOPERCause: The COPY command does not support AS SYSDBA or AS SYSOPER connections.Action: Remove AS SYSDBA or AS SYSOPER from the TO clause.SP2-0756 FROM clause length clause_lenbytes exceeds maximum length max_lenCause: The FROM clause is too long.Action: Reduce the string specified in the FROM clause.SP2-0757 TO clause length clause_lenbytes exceeds maximum length max_lenCause: The TO clause is too long.Action: Reduce the string specified in the TO clause.SP2-0758 FROM clause missing usernameor connection identifierCause: The COPY command FROM clause must include a username and a connection identifier.Action: Specify a username and a connection identifier in the FROM clause.SP2-0759 TO clause missing usernameor connection identifierCause: The COPY command TO clause must include a username and a connection identifier.Action: Specify a username and a connection identifier in the TO clause.SP2-0762 Mismatched quotes in SHOWERRORS [object]Cause: Invalid syntax was found in the object name submitted as an argument to SHOW ERRORS.Action: If quotes are used, check that they are correctly matched. Either quote the whole argument, or quote theschema and object components separately.SP2-0768 Illegal SPOOL commandCause: An invalid option was used in the SPOOL command.Action: Check the syntax of the SPOOL command for the correct options.SP2-0769 Usage: SPOOL { <file> |OFF | OUT }where <file> is file_name[.ext] [CRE[ATE]|REP[LACE]|APP[END]]Cause: Incorrect syntax for the SPOOL command was entered.Action: Check the syntax of the SPOOL command for the correct usage.SP2-0771 File filename already exists.Use another name or "SPOOL filename[.ext] REPLACE"Cause: The file specified in the SPOOL command already exists.Action: Use the REPLACE option to overwrite the existing file, or specify another file name.SP2-0772 Automatic Storage Managerinstance startedCause: Document: Feedback messageAction:SP2-0773 Automatic Storage Managerdiskgroups mountedCause: Document: Feedback messageAction:SP2-0774 Automatic Storage Managerinstance shutdownCause: Document: Feedback messageAction:SP2-0775 Automatic Storage Managerdiskgroups dismountedCause: Document: Feedback messageAction:SP2-0776 Invalid schema and objectseparator in SHOW ERRORS [object]Cause: Invalid syntax was found in the object name submitted as an argument to SHOW ERRORS.Action: If a schema is specified, check that the schema and object names are separated by a period.SP2-0777 Invalid single quotes inSHOW ERRORS [object]Cause: Invalid syntax was found in the object name submitted as an argument to SHOW ERRORS.Action: If the SHOW ERRORs argument is quoted, check that only double quotes are used. Either quote the whole argument,or quote the schema and object components separately.SP2-0778 Script filename and argumentstoo longCause: The combined length of the script filename and script arguments is too long for SQL*Plus.Action: Reduce the length of the script name and path. Reduce the number and/or size of the script arguments.SP2-0780 Value entered is not avalid datatypeCause: The value entered in the ACCEPT command was not valid for the specified datatype.Action: Enter a valid number within a valid range for the datatype.SP2-0781 command option option_nameout of range (min through max)Cause: Attempted to enter a value outside the allowed range for the command option.Action: Check the limits for the command option and enter a value within the allowed range.SP2-0782 Prelim connection establishedCause: Document: Feedback messageAction:SP2-0783 Cannot SET variable whileconnected to a databaseCause: Attempted to set a system variable that cannot be set while still connected to a database instance.Action: Disconnect from the database instance before attempting to set the system variable.SP2-0784 Invalid or incomplete characterbeginning byte returnedCause: Attempted to return a string from the database that contained an invalid or incomplete character.Action: Replace the invalid or incomplete string in the database with a valid or complete string.SP2-0804 Procedure created withcompilation warningsCause: The PL/SQL procedure has been created, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL procedure.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0805 Procedure altered withcompilation warningsCause: The PL/SQL procedure has been altered, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL procedure.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0806 Function created with compilationwarningsCause: The PL/SQL function has been created, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL function.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0807 Function altered with compilationwarningsCause: The PL/SQL function has been altered, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL function.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0808 Package created with compilationwarningsCause: The PL/SQL package has been created, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL package.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0809 Package altered with compilationwarningsCause: The PL/SQL package has been altered, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL package.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0810 Package Body created withcompilation warningsCause: The PL/SQL package body has been created, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL package body.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0811 Package Body altered withcompilation warningsCause: The PL/SQL package body has been altered, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL package body.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0812 View created with compilationwarningsCause: The PL/SQL view has been created, but has one or more warnings, informational messages or performance messagesthat may help you to improve your PL/SQL view.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0813 View altered with compilationwarningsCause: The PL/SQL view has been altered, but has one or more warnings, informational messages or performance messagesthat may help you to improve your PL/SQL view.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0814 Trigger created with compilationwarningsCause: The PL/SQL trigger has been created, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL trigger.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0815 Trigger altered with compilationwarningsCause: The PL/SQL trigger has been altered, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL trigger.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0816 Type created with compilationwarningsCause: The PL/SQL type has been created, but has one or more warnings, informational messages or performance messagesthat may help you to improve your PL/SQL type.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0817 Type altered with compilationwarningsCause: The PL/SQL type has been altered, but has one or more warnings, informational messages or performance messagesthat may help you to improve your PL/SQL type.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0818 Type Body created withcompilation warningsCause: The PL/SQL type body has been created, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL type body.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0819 Type Body altered withcompilation warningsCause: The PL/SQL type body has been altered, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL type body.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0820 Library created with compilationwarningsCause: The PL/SQL library has been created, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL library.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0821 Library altered with compilationwarningsCause: The PL/SQL library has been altered, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL library.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0822 Java created with compilationwarningsCause: The PL/SQL java has been created, but has one or more warnings, informational messages or performance messagesthat may help you to improve your PL/SQL java.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0823 Java altered with compilationwarningsCause: The PL/SQL java has been altered, but has one or more warnings, informational messages or performance messagesthat may help you to improve your PL/SQL java.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0824 PL/SQL compilation warningsCause: The PL/SQL block has been created, but has one or more warnings, informational messages or performance messagesthat may help you to improve your PL/SQL block.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0825 Dimension created withcompilation warningsCause: The PL/SQL dimension has been created, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL dimension.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0826 Dimension altered withcompilation warningsCause: The PL/SQL dimension has been altered, but has one or more warnings, informational messages or performancemessages that may help you to improve your PL/SQL dimension.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0827 Procedure created with compilationerrorsCause: The PL/SQL procedure has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0828 Procedure altered withcompilation errorsCause: The PL/SQL procedure has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0829 Function created with compilationerrorsCause: The PL/SQL function has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0830 Function altered with compilationerrorsCause: The PL/SQL function has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0831 Package created with compilationerrorsCause: The PL/SQL package has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0832 Package altered with compilationerrorsCause: The PL/SQL package has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0833 Package Body created withcompilation errorsCause: The PL/SQL package body has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0834 Package Body altered withcompilation errorsCause: The PL/SQL package body has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0835 View created with compilationerrorsCause: The PL/SQL view has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0836 View altered with compilationerrorsCause: The PL/SQL view has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0837 Trigger created with compilationerrorsCause: The PL/SQL trigger has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0838 Trigger altered with compilationerrorsCause: The PL/SQL trigger has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0839 Type created with compilationerrorsCause: The PL/SQL type has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0840 Type altered with compilationerrorsCause: The PL/SQL type has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0841 Type Body created withcompilation errorsCause: The PL/SQL type body has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0842 Type Body altered withcompilation errorsCause: The PL/SQL type body has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0843 Library created with compilationerrorsCause: The PL/SQL library has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0844 Library altered with compilationerrorsCause: The PL/SQL library has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0845 Java created with compilationerrorCause: The PL/SQL java has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0846 Java altered with compilationerrorsCause: The PL/SQL java has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0847 PL/SQL compilation errorsCause: The PL/SQL block has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0848 Dimension created withcompilation errorsCause: The PL/SQL dimension has been created, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-0849 Dimension altered withcompilation errorsCause: The PL/SQL dimension has been altered, but has one or more error messages.Action: Use the SQL*Plus SHOW ERR[ORS] command to display the warnings and messages.SP2-1500 STARTUP with UPGRADE onlyvalid with Oracle 9.2 or greaterCause: STARTUP UPGRADE 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 atleast release 9.2.SP2-1501 STARTUP with DOWNGRADEonly valid with Oracle 9.2 or greaterCause: STARTUP DOWNGRADE 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 atleast release 9.2.SP2-1502 The HTTP proxy server specifiedby http_proxy is not accessibleCause: The HTTP proxy server used by SQL*Plus cannot be accessed. SQL*Plus will be unable to run scripts locatedon a web server.Action: Check that the proxy setting has the correct value, or unset it if no proxy is needed. SQL*Plus may getthe proxy name from the environment variable http_proxy, or the value may be set in another way on your system. Check that the given proxy server is operational. Most web browsers can be configured to use a proxy. Configure a browser to use the desired proxyand verify that web pages can still be loaded.SP2-1503 Unable to initialize Oraclecall interfaceCause: Indicates a library used by SQL*Plus to communicate with the database failed to initialize correctly.Action: Check that the Oracle environment or registry entries are consistent and correct. If using the SQL*PlusInstant Client make sure the SQL*Plus and Oracle libraries are from the same release. Make sure you have read access to the libraries.SP2-1504 Cannot print uninitializedLOB variableCause: The specified LOB variable should be initialized before printing.Action: Check that the specified variable is initialized and try again.SP2-1505 Invalid COL or TAB positionenteredCause: The BTITLE, TTITLE, REPHEADER or REPFOOTER command you entered attempts to use a COL or TAB value greaterthan 240, or a COL or TAB value greater than LINESIZE if LINESIZE is greater than 240.Action: Make sure the BTITLE, TTITLE, REPHEADER or REPFOOTER command you enter uses a COL or TAB value of 240 orless, or uses a COL or TAB value of LINESIZE or less if LINESIZE is greater than 240.

iSQL*Plus ErrorMessages

SP2-0850 Command command_name isnot available in iSQL*PlusCause: The command was not recognized by the SQL*Plus engine, or it is disabled iniSQL*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 replacementcommand.SP2-0851 Command beginning command_name...is not available in iSQL*PlusCause: The command was not recognized by the SQL*Plus engine, or it is disabled iniSQL*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 replacementcommand.SP2-0852 Option not available in iSQL*PlusCause: The command option is not available in iSQL*Plus. This error usually occursafter SP2-158 or SP2-735. Some options are disabled in a web based context because they have no meaning, because they prevent proper operation, or because they pose a security risk.Action: Remove the option from the command.SP2-0853 Empty username fieldCause: The Username field of the iSQL*Plus Login screen was empty.Action: Enter a username before attempting to log in.SP2-0854 Password cannot be enteredtwiceCause: An error occurred while parsing the Username and Password fields of the iSQL*PlusLogin screen.Action: Check that you haven't specified a password as part of the username (for example "scott/tiger") and simultaneouslyput 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.SP2-0855 Connect identifier cannotbe entered twiceCause: An error occurred while trying to read the connection identifier in the Connection Identifier field of the iSQL*PlusLogin 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.SP2-0856 Usage: CONN[ECT] username/password[@connect_identifier][AS {SYSOPER|SYSDBA}]or: CONN[ECT] /[@connect_identifier] AS {SYSOPER|SYSDBA}Cause: iSQL*Plus was unable to connect to an Oracle instance, or the username and passwordwere 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.SP2-0858 Usage: SET MARKUP HTML[ON] [HEAD text] [BODY text] [TABLE text] [PRE[FORMAT] {ON|OFF}]Cause: An invalid option to SET MARKUP was entered in iSQL*Plus.Action: Remove the invalid option.SP2-0860 For a list of known commandsenter HELPCause: An invalid command sequence was entered.Action: Use the HELP command to show the syntax of SQL*Plus commands.SP2-0863 iSQL*Plusprocessing completedCause: All commands in the iSQL*Plus input script have been executed with no explicitoutput.Action: No action required.SP2-0864 Session has expired. Pleaselog in againCause: The iSQL*Plus session was idle for too long and the context has been removedto free resources for other connections.Action: Reconnect to iSQL*Plus. The System Administrator configures the timeout period.SP2-0865 Session is blocked. Pleaselog in againCause: An attempt was made to execute a query from iSQL*Plus when a previous querywas still processing. This condition occurs when the browser Back button, or Stop button is pressed during query processing.Action: Reconnect to iSQL*Plus.SP2-0866 Please enter statementsin the Input areaCause: 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.SP2-0867 No script to be savedCause: 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.SP2-0868 No script to executeCause: An attempt was made to execute a script and output the results to a file when there were no statements inthe script to execute.Action: Make sure the script contains statements to execute and execute the script again.SP2-0869 Invalid file contentCause: 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 your browser to recognize thefile are set correctly. Typically if you are loading a file with the extension .SQL then make sure the browser has a "SQL" MIME type.SP2-0871 No script to loadCause: Clicked Load Script but either no file name was specified, or the specified file name did not exist, orif 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 wasempty, no action is required.SP2-0872 SET AUTORECOVERY ON mustbe used in iSQL*PlusCause: Attempted to use the interactive mode of the RECOVER command in iSQL*Plus. Usethe autorecovery mode in iSQL*Plus.Action: Switch SET AUTORECOVERY ON and rerun the RECOVER command.SP2-0873 An unexpected quote wasfound in the URL argumentCause: A quote was found in the middle of the value portion of a keyword/value pair.Action: Check for and remove the extra quote.SP2-0874 URL argument is missinga keywordCause: No keyword was found in a keyword/value pair of a URL argument.Action: Check for a missing keyword or perhaps a missing equals sign.SP2-0875 URL argument contains akeyword but no valueCause: 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.SP2-0876 URL argument is missingan end quoteCause: 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.SP2-0877 Found an unexpected characterin a URL argumentCause: Already have a keyword/value pair where the value is quoted but extra characters were still found in a URLargument.Action: Remove the extra characters.SP2-0878 Duplicate keyword keywordspecifiedCause: The keyword was already specified in a previous parameter of a URL argument.Action: Remove one of the keyword occurrences.SP2-0879 Must specify a script fordynamic reports to executeCause: The script keyword was not specified in the URL.Action: Add a script keyword/value pair to the URL argument.SP2-0880 Enter connection detailsto run script script_urlCause: iSQL*Plus could not log in to the server because there was not URL "userid"argument, or the information supplied was insufficient or incorrect.Action: Log in through the Login screen to execute the Dynamic Report script.SP2-0882 Empty password fieldCause: The password field of the iSQL*Plus Login screen was empty.Action: Enter your password before attempting to log in.SP2-0883 Invalid Input area sizespecifiedCause: The width or height specified for the Input area size was either not a numeric value, or was not in therange 1 to 999.Action: Re-enter valid numeric values for the Input area size.SP2-0884 Connection to databaseconnect_identifier is not allowedCause: An attempt was made to connect to a database that SQL*Plus has not been configured to allow connectionsto.Action: If this occurred with the CONNECT command in iSQL*Plus, the "iSQLPlusConnectIdList"configuration parameter in the web.xml 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 parameterlist. The connection identifier is not case sensitive.SP2-0885 Only a valid username or'/' is allowed in the username fieldCause: An attempt was made to enter a value other than a username or '/' in the iSQL*PlusLogin screen Username field.Action: Only a username is allowed in the iSQL*Plus Login screen Username field. Ausername, or "/" is allowed in the iSQL*Plus DBA Login screen.SP2-0886 No scripts in historyCause: 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.SP2-0887 History size specifiedis non numeric or outside the range [0 -100]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.SP2-0889 The value specified forthe keyword type must be either URL or TEXTCause: 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".SP2-0890 Instance not set, or connectidentifier not specifiedCause: 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.SP2-0892 Error expiring sessionCause: iSQL*Plus could not close the timed out session identified by the user sessionId.Action: No action required.SP2-0893 Expired sessionCause: iSQL*Plus has expired the timed out session identified by the user session Id.Action: No action required.SP2-0894 Unsuccessful log in forusername from URL to connect_idCause: iSQL*Plus failed to log in user with the given username, URL and connect identifier.Action: No action required.SP2-0896 Failed to log out usernameCause: iSQL*Plus failed to log out user with given user session Id.Action: No action required.SP2-0911 Only a password is allowedin the password fieldCause: An attempt was made to enter a value other than a password in the iSQL*PlusLogin screen Password field.Action: Only a valid password is allowed in the Password field.SP2-0912 Only a connect identifieris allowed in the connection identifier fieldCause: An attempt was made to enter a value other than a valid connection identifier in the iSQL*PlusLogin screen Connection Identifier field.Action: Only a valid connection identifier or a valid alias is allowed in the Connection Identifier field.SP2-0913 No keywords recognisedby iSQL*PlusCause: An attempt was made to request a service from iSQL*Plus by manually typing inthe URL, but no keywords could be recognized.Action: Refer to the iSQL*Plus documentation for the syntax, and types of service thatcan be manually entered in a URL.SP2-0914 Value "value" for keyword"keyword" not recognised by iSQL*PlusCause: An attempt was made to request a service from iSQL*Plus by manually typing inthe 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 thatcan be manually entered in a URL.SP2-0915 Cookies may have been disabledCause: After logging in, iSQL*Plus can only process further requests if cookies areenabled on your browser.Action: Enable cookies on your browser and log in again.SP2-0916 Scheme scheme notsupportedCause: iSQL*Plus only supports HTTP, HTTPS and FTP.Action: Change the scheme to one that is supported.SP2-0917 User requested cancelCause: The iSQL*Plus script that was running has been cancelled by the user. It mayhave been cancelled by clicking the Cancel button, by re-executing the script, or by clicking any other button or link on the Workspace.Action: No action required.SP2-0918 HTTP error number onattempt to open URLCause: An HTTP error occurred while attempting to fetch the contents of a URL. The URL may have been renamed, removedor be temporarily unavailable.Action: Check that the URL is spelled correctly and that it is available from the requested server.SP2-00920 HTTP error message onattempt to open URLCause: An HTTP error occurred while attempting to fetch the contents of a URL. The URL may have been renamed, removedor be temporarily unavailable.Action: Check that the URL is spelled correctly and that it is available from the requested server.SP2-0921 The value specified forthe keyword action must be either EXECUTE or LOADCause: 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".SP2-0923 AS SYSDBA or AS SYSOPERlogin not allowed through the iSQL*Plus URLCause: An attempt was made to log in through the iSQL*Plus URL with AS SYSDBA or ASSYSOPER privilege.Action: AS SYSDBA or AS SYSOPER privileged login is only permitted through the iSQL*PlusDBA URL. Remove the AS SYSDBA or AS SYSOPER arguments from the login request, or log in through the iSQL*Plus DBA URL.SP2-0924 Supplied connect stringhas duplicate or incorrect keywordCause: The login details supplied in the connect string may contain a duplicate keyword, an incorrect keyword oran out of sequence keyword.Action: Check the syntax of the connect string and fix or remove the incorrect content.SP2-0925 No scripts selected toload or deleteCause: In the 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.SP2-0926 iSQL*Plusinternal error: state = number, message = messageCause: An internal error has occurred in iSQL*Plus.Action: Make a note of the message, then contact Oracle Support Services.SP2-0927 CONNECT AS SYSDBA or ASSYSOPER not allowed through iSQL*Plus URLCause: An attempt was made to CONNECT with AS SYSDBA or AS SYSOPER privileges through the iSQL*PlusURL.Action: CONNECT with AS SYSDBA or AS SYSOPER privileges is only permitted through the iSQL*PlusDBA URL. Remove the AS SYSDBA or AS SYSOPER arguments from the CONNECT request, or CONNECT through the iSQL*Plus DBA URL.SP2-0929 To use ENTMAP reconfigureiSQLPlusAllowUserMarkup in the iSQL*Plus ServerCause: The iSQL*Plus Server has been configured to prevent the use of SET MARKUP HTMLENTMAP and COLUMN ENTMAP.Action: The System Administrator can change the value of iSQLPlusAllowUserMarkup in the iSQL*PlusServer configuration to allow use of the ENTMAP option.SP2-0930 Enter a URL or a path andfile name, not bothCause: In the iSQL*Plus Load Script screen, the location of a script to load into theWorkspace was specified in both the URL and File fields. A script can be loaded from a URL, or from the local file system, but not from both at the same time.Action: Enter either a URL, or a path and file name.SP2-0931 Connection Identifier containsan illegal parameterCause: When attempting to login to iSQL*Plus, an illegal parameter was found in theConnection Identifier string.Action: Modify the Connection Identifier string to remove the illegal parameter and attempt to log in again.SP2-0932 Size specified for scriptwidth is non numeric or outside the range [1 -500]Cause: The size specified for the script width was either not a numeric value, or was not in the range 1 to 500.Action: Re-enter a numeric value in the range 1 to 500 for the script width.SP2-0933 Size specified for scriptheight is non numeric or outside the range [1 - 300]Cause: The size specified for the script height was either not a numeric value, or was not in the range 1 to 300.Action: Re-enter a numeric value in the range 1 to 300 for the script height.SP2-0934 iSQL*PlusServer currently has insufficient memory to complete this scriptCause: The iSQL*Plus Server could not completely execute the script because there wasnot enough memory available. Part of the script may have executed. Some specific causes are:1. The Java VM heap grew too large due to executing scripts with large output or with too many concurrent sessions.2. Insufficient physical memory available for the Java VM.Action: One or more of the following may help:1. Edit queries to reduce the number of rows returned.2. Turn iSQL*Plus multi page output on to reduce the number of rows cached.3. Schedule large scripts sequentially.4. Use Oracle Resource Manager to limit user queries.5. Modify the iSQL*Plus OC4J startup script. Increase the -Xmx and -Xms values to allocate more memory to iSQL*Plus.6. Review DDL and DCL that may have been executed prior to the memory shortage. Reexecute the script.SP2-0935 Invalid dynamic reportURLCause: Either required parameters are missing from the dynamic report URL or there are special characters in theURL that are not HTML encoded.Action: Check that all parameters are correct and that any special characters are HTML encoded before submittingthe dynamic report URL again.SP2-0936 URL access is disabledin iSQL*PlusCause: @, @@ or START was used with a URL, or a dynamic report referenced a URL. The iSQL*PlusAdministrator has disabled this functionality.Action: Contact your iSQL*Plus Administrator.

COPY CommandMessages

CPY-0002 Illegal or missing APPEND,CREATE, INSERT, or REPLACE optionCause: 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.CPY-0003 Internal Error: logicalhost number out of rangeCause: 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.CPY-0004 Source and destinationtable and column names don't matchCause: On an APPEND operation or an INSERT (when the table exists), at least one column name in the destinationtable 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 destinationtable match the column names and column order in the optional column list or in the SELECT commandCPY-0005 Source and destinationcolumn attributes don't matchCause: On an APPEND operation or an INSERT (when the table exists), at least one column in the destination tabledoes 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.CPY-0006 Select list has more columnsthan destination tableCause: On an APPEND operation or an INSERT (when the table exists), the number of columns in the SELECT commandis 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 numberin the destination table.CPY-0007 Select list has fewer columnsthan destination tableCause: On an APPEND operation or INSERT (when the table exists), the number of columns in the SELECT command isless 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 numberin the destination table.CPY-0008 More column list namesthan columns in the destination tableCause: On an APPEND operation or an INSERT (when the table exists), the number of columns in the column name listis 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 thenumber in the destination table.CPY-0009 Fewer column list namesthan columns in the destination tableCause: On an APPEND operation or an INSERT (when the table exists), the number of columns in the column name listis 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 thenumber in the destination table.CPY-0012 Datatype cannot be copiedCause: An attempt was made to copy a datatype that is not supported in the COPY command. Datatypes supported bythe 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 SQL*Plus COPY Command.转：http://www.360doc.com/content/11/1104/11/111514_161583508.shtml