SQL*Plus Error Messages

This appendix lists error messages with prefixes SP2- and CPY- generated by SQL*Plus and iSQL*Plus:

For error messages with prefixes such as ORA-, TNS- and PLS- generated by Oracle Database, see the Oracle Database Error Messages guide.

SQL*Plus Error Messages

SP2-0002 ACCEPT statement must specify a variable name
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.
SP2-0003 Ill-formed ACCEPT command starting as command_string
Cause: 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 append
Cause: 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 format computations
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.
SP2-0015 no break(s) defined
Cause: There was no break defined.
Action: Define a break. Check the syntax of the BREAK command for the correct options.
SP2-0016 break specification must start with ON/BY or ACROSS keyword
Cause: 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 after keyword_name keyword
Cause: There was no column name after the specified keyword.
Action: Enter a column name after the specified keyword.
SP2-0019 invalid numeric argument to option_name option
Cause: An invalid numeric argument was used in the specified option.
Action: Correct the argument and try again.
SP2-0020 no storage available for column_name
Cause: 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 to modify the buffer_name buffer variable
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-0023 String not found
Cause: The search string specified was not found.
Action: Check the search string to make sure that it is valid.
SP2-0024 Nothing to change
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.
SP2-0025 Invalid change string
Cause: 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 delete
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.
SP2-0027 Input is too long (> max_characters characters) - line ignored
Cause: The input value specified was too long.
Action: Re-enter with fewer characters.
SP2-0029 command buffer space exhausted
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:

  • 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 line
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.
SP2-0038 Command too long. (max_characters characters)
Cause: The specified command entered was too long.
Action: Check the command syntax for the limitation.
SP2-0039 command-line overflow while substituting into command_name
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.
SP2-0042 unknown command command_name - rest of line ignored
Cause: 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 commands enter HELP and to leave enter EXIT
Cause: An unknown command was entered.
Action: Check the syntax of the command you used for the correct options.
SP2-0045 no column_name defined
Cause: No columns have been defined.
Action: No action required.
SP2-0046 column_name not defined
Cause: The column name specified was not defined.
Action: Retry with a valid column name.
SP2-0047 Invalid number for option_name option
Cause: An invalid number was used for this option.
Action: Re-try the operation with a valid number.
SP2-0052 like column_name, column_name not defined
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.
SP2-0054 no room to allocate definition_name definition. Ignored
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.
SP2-0055 out of room while allocating portion of new definition_name. Old definition (if any) retained
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.
SP2-0080 no COMPUTES currently defined
Cause: No COMPUTE definition.
Action: Define a COMPUTE. Check the syntax of the COMPUTE command for the correct options.
SP2-0081 maximum of number COMPUTE functions allowed at a time
Cause: The maximum number of COMPUTE functions has been exceeded.
Action: Reduce the number of COMPUTE functions.
SP2-0082 no COMPUTE functions requested
Cause: No COMPUTE functions requested.
Action: No action required.
SP2-0083 warning: COMPUTE option function_name specified number times
Cause: A label or a function was specified more than once.
Action: Remove the unnecessary labels or functions.
SP2-0084 COMPUTE ON keyword specified already
Cause: The ON keyword was specified more than once.
Action: Specify the ON keyword once in the command.
SP2-0085 COMPUTE OF keyword specified already
Cause: The OF keyword was specified more than once.
Action: Specify the OF keyword once in the command.
SP2-0087 no room to allocate COMPUTE control block for column_name
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.
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 appropriate place.
SP2-0092 missing columns for keyword_name keyword
Cause: The column name was not specified for the keyword.
Action: Specify the column name and try again.
SP2-0096 no more room to allocate INTO variable variable_name
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.
SP2-0097 no storage to allocate ON column column_name
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.
SP2-0098 no storage to allocate COMPUTE block for column_name
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.
SP2-0103 Nothing in SQL buffer to run
Cause: 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, entity name
Cause: File name was not specified in the GET or SAVE commands.
Action: Specify a file name and try again.
SP2-0107 Nothing to save
Cause: 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 used
Cause: 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 SET

To 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_name
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:

  • 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 file file_name
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:

  • 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 file file_name
Cause: The file was in use.
Action: Release the file from the other process.
SP2-0116 Illegal SAVE command
Cause: 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 defined
Cause: No DEFINE symbols were defined.
Action: No action required.
SP2-0135 Symbol symbol_name is UNDEFINED
Cause: 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 equal sign (=)
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 value following equal sign
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.
SP2-0138 no room to add substitution variable 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.
SP2-0146 Unable to allocate dynamic space needed (number_of_bytes bytes) - exiting
Cause: An internal error occurred.
Action: Note the message and number, and contact the System Administrator.
SP2-0152 ORACLE may not be functioning properly
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.
SP2-0157 unable to CONNECT to ORACLE after 3 attempts, exiting SQL*Plus
Cause: 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_name
Cause: 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 truncated
Cause: 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_name
Cause: Unable to close the specified file as it was being used.
Action: Release the file from the other process.
SP2-0171 HELP system not available
Cause: 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.sql script to install HELP on this database: 
sqlplus system @hlpbld.sql helpus.sql
SP2-0172 No HELP matching this topic was 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 invalid
Cause: 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 assignment
Cause: 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_name buffer
Cause: There are no lines stored in the buffer.
Action: Enter SQL statements into the buffer.
SP2-0224 invalid starting line number
Cause: The line number specified was incorrect.
Action: Check that the line number is correct and try again.
SP2-0225 invalid ending line number
Cause: The line number specified was incorrect.
Action: Check that the line number is correct and try again.
SP2-0226 Invalid line number current_line_number
Cause: Invalid line number was specified.
Action: Re-enter with a valid line number.
SP2-0232 Input too long. Must be less than number_of_characters characters
Cause: The input value was too long.
Action: Reduce the size of the value and re-enter.
SP2-0233 Unable to obtain userid after number_of_attempts attempts. Retry command
Cause: 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 command within a PAGE break
Cause: 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 temporary storage for printing
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.
SP2-0246 Illegal FORMAT string column_ format_name
Cause: An invalid format was specified for the column.
Action: Specify a valid format for the column.
SP2-0249 variable_name not a valid variable type for printing
Cause: 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 line
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.
SP2-0258 could not create variable variable_name for column column_name
Cause: The specified variable could not be created for column – internal error or out of memory.
Action: Check memory usage.
SP2-0259 could not create variable variable_name for COMPUTE INTO
Cause: The specified variable could not be created.
Action: Check the syntax of the command you used for the correct options.
SP2-0260 computation for column column_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 CCBDEF pointer array
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.
SP2-0263 no room to allocate COMPUTE block for column_name ON page/report/column_name
Cause: Insufficient memory allocated to the COMPUTE block.
Action: Allocate more memory by closing other applications.
SP2-0265 option_name must be set ON or OFF
Cause: 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_number out 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 not a valid number
Cause: Non-numeric value (integer) was entered for a parameter.
Action: Enter a valid numeric value (integer).
SP2-0271 variable_name is not a buffer variable
Cause: 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 character cannot be alphanumeric or white-space
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.
SP2-0277 entered_value value not valid
Cause: The value entered was incorrect.
Action: Re-enter with a valid value.
SP2-0281 option_name missing set option 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 file
Cause: The file is currently being used.
Action: Release the file from the other process.
SP2-0309 SQL*Plus command procedures may only be nested to a depth of number_of_nested_procedures
Cause: 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_name
Cause: Unable to open the specified file.
Action: Check and make sure the file name is valid.
SP2-0311 string expected but not found
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.
SP2-0312 missing terminating quote (quote_type)
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.
SP2-0317 expected symbol name is missing
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.
SP2-0318 symbol name beginning variable_name.. is too long (max max_name_length) Illegal variable name variable_name
Cause: 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 denied
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.
SP2-0324 operating system timing error error_option_number - request denied
Cause: 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_name
Cause: 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 title buffer
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.
SP2-0331 SPOOL OUT disabled
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.
SP2-0332 Cannot create spool file
Cause: 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 variable substitution (>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 storage
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.
SP2-0359 memory exhausted
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.
SP2-0381 command_name is not available
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.
SP2-0382 The command_name command is not available
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.
SP2-0392 Cannot UNDEFINE the current edit buffer
Cause: The current edit buffer cannot be undefined.
Action: No action required.
SP2-0394 Illegal buffer name: buffer_name
Cause: 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 command
Cause: 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 datatype
Cause: 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_characters characters
Cause: There was no carriage return at the last line of the SQL statement.
Action: Insert a carriage return.
SP2-0495 FROM and TO clauses both missing; specify at least one
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.
SP2-0496 Misplaced FROM clause
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.
SP2-0497 Misplaced TO clause
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.
SP2-0498 Missing parenthetical column list or USING keyword
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.
SP2-0499 Misplaced APPEND keyword
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.
SP2-0501 Error in SELECT statement: Oracle_database_error_message
Cause: Invalid SELECT statement found in the COPY command.
Action: Check the syntax of the COPY command for the correct options.
SP2-0513 Misplaced CREATE keyword
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.
SP2-0514 Misplaced REPLACE keyword
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.
SP2-0515 Maximum number of columns (max_num_columns) exceeded
Cause: 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 name NULL encountered
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.
SP2-0517 Missing comma or right parenthesis
Cause: A missing right parenthesis was identified in the COPY command.
Action: Retry the operation with a comma or right parenthesis.
SP2-0518 Missing USING clause
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.
SP2-0519 FROM string missing Oracle Net @database specification
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.
SP2-0520 TO string missing Oracle Net @database specification
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.
SP2-0526 Misplaced INSERT keyword
Cause: 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 already exists. Use SAVE filename[.ext] REPLACE
Cause: 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 disabled in Product User Profile
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.
SP2-0545 SET command requires an argument
Cause: An argument was missing in the SET command.
Action: Check the syntax of the SET command for the correct options.
SP2-0546 User requested Interrupt or EOF detected
Cause: Either end-of-file was reached, or CTRL-C was entered to cancel the process.
Action: No action required.
SP2-0547 option_name option value out 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_name not declared
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.
SP2-0556 Invalid file name Usage: STORE {SET} filename[.ext] [CRE[ATE]|REP[LACE]|APP[END]]or Unable to complete EDIT command
Cause: Missing file name or an invalid file name specified.
Action: Make sure that a file name was specified.
SP2-0559 Usage: EXEC[UTE] statement
Cause: 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 exist
Cause: 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 in package
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.
SP2-0564 Object object_name is INVALID, it may not be described
Cause: The specified object you tried to DESCRIBE is invalid.
Action: Re-validate the object.
SP2-0565 Illegal identifier
Cause: An invalid character was used in the DESCRIBE command.
Action: Correct the character and try again.
SP2-0566 Illegal sub-object specification
Cause: Invalid sub-object specification in the DESCRIBE command.
Action: Correct the subject specification and try again.
SP2-0567 Illegal column specification for PL/SQL object
Cause: 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 declared
Cause: 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 feature not in SQL92 Entry |Intermediate|Full Level
Cause: A SQL statement was attempted that is not FIPS compliant. May also occur if a SQL*Plus feature, for example SET 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 a package; 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_name was non-numeric
Cause: The specified EXIT variable is non-numeric.
Action: Check the syntax of the EXIT command for the correct usage.
SP2-0590 A COMPUTE function must appear before each LABEL keyword
Cause: 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 dynamic space needed (number_of_bytes bytes) Try reducing ARRAYSIZE or the number of columns selected
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.
SP2-0593 Label text must follow the LABEL keyword
Cause: 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 a valid datatype _name format
Cause: 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 match input 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 already exists. Use another name or STORE {SET} filename[.ext] REPLACE
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.
SP2-0606 Cannot create file_name file
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 enables file creation.
SP2-0607 Cannot close file_name file
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.
SP2-0608 Object object_name is a remote object, cannot further describe
Cause: 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_name
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.
SP2-0612 Error generating report_name report
Cause: 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_TABLE format or existence Error enabling autotrace_report report
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.
SP2-0614 Server version too low for this feature
Cause: 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 unique STATEMENT_ID
Cause: 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 Session Identifier. Check PLUSTRACE role is enabled Error enabling autotrace_report report
Cause: Unable to find the session identifier.
Action: Check that the PLUSTRACE role has been granted.
SP2-0619 Error while connecting
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.
SP2-0620 Error while disconnecting
Cause: 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_number while gathering statistics
Cause: 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 must be less than ending line number
Cause: 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 SYSTEM
Cause: 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.
SP2-0625 Error printing variable variable_name
Cause: Error encountered while printing the specified variable.
Action: Check that the specified variable is correct and try again.
SP2-0626 Error accessing package DBMS_APPLICATION_INFO You may need to install the Oracle Procedural option SET APPINFO requires Oracle Server Release 7.2 or later
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.
SP2-0631 String beginning string_name is too long. Maximum size is 1 characteror Maximum size is string_length characters
Cause: 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 connection to server
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.
SP2-0642 SQL*Plus internal error state error_state context error_number. Unsafe to proceedor Unable to proceed
Cause: An internal error occurred.
Action: Make a note of the message, then contact Oracle Support Services.
SP2-0645 Operating System error occurred Unable to complete EDIT command
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.
SP2-0650 New passwords do not match
Cause: 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 unchanged
Cause: 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 only affects shift sensitive character sets
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.
SP2-0667 Message file facility<lang>.msb not found
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.
SP2-0668 Invalid variable name
Cause: An invalid character was specified as part of the variable name.
Action: Specify the variable with valid characters.
SP2-0669 Valid characters are alphanumerics and '_'
Cause: An invalid character was specified as part of the variable name.
Action: Specify the variable with alphanumeric characters and '_'.
SP2-0670 Internal number conversion failed
Cause: 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 available
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.
SP2-0676 Bind variable length cannot exceed variable_length units_of_variable
Cause: The length of the bind variable datatype was exceeded.
Action: Reduce the length of the bind variable datatype.
SP2-0678 Column or attribute type can not be displayed by SQL*Plus
Cause: 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_variable is invalid or format mismatched format
Cause: 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 of STARTUP options
Cause: 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 of SHUTDOWN options
Cause: 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 of ARCHIVE LOG options
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.
SP2-0717 Illegal SHUTDOWN option
Cause: 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 option
Cause: 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 while connected to a database
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.
SP2-0733 Invalid connect string
Cause: An invalid connect string was specified.
Action: Check that the connect string is correct.
SP2-0734 Unknown command beginning command_name ... - rest of line ignored
Cause: The command entered was invalid.
Action: Check the syntax of the command you used for the correct options.
SP2-0735 Unknown command_name option beginning option_name
Cause: 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 while substituting into line beginning string_name
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.
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_name not available
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.
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 out of 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 least max_page_size to run this query with LINESIZE line_size
Cause: 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 circular path of synonym synonym_name
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.
SP2-0750 ORACLE_HOME may not be set
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. 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 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.

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 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.

SP2-0751 Unable to connect to Oracle. Exiting SQL*Plus
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.
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 only valid with Oracle 9.2 or greater
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.
SP2-0754 FROM clause cannot contain AS SYSDBA or AS SYSOPER
Cause: 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 contain AS SYSDBA or AS SYSOPER
Cause: 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_len bytes exceeds maximum length max_len
Cause: The FROM clause is too long.
Action: Reduce the string specified in the FROM clause.
SP2-0757 TO clause length clause_len bytes exceeds maximum length max_len
Cause: The TO clause is too long.
Action: Reduce the string specified in the TO clause.
SP2-0758 FROM clause missing username or connection identifier
Cause: 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 username or connection identifier
Cause: 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 SHOW ERRORS [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 the schema and object components separately.
SP2-0768 Illegal SPOOL command
Cause: 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 Manager instance started
Cause: Document: Feedback message
Action:
SP2-0773 Automatic Storage Manager diskgroups mounted
Cause: Document: Feedback message
Action:
SP2-0774 Automatic Storage Manager instance shutdown
Cause: Document: Feedback message
Action:
SP2-0775 Automatic Storage Manager diskgroups dismounted
Cause: Document: Feedback message
Action:
SP2-0776 Invalid schema and object separator 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 in SHOW 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 arguments too long
Cause: 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 a valid datatype
Cause: 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_name out 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 established
Cause: Document: Feedback message
Action:
SP2-0783 Cannot SET variable while connected to a database
Cause: 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 character beginning byte returned
Cause: 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 with compilation warnings
Cause: The PL/SQL procedure has been created, but has one or more warnings, informational messages or performance messages 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 with compilation warnings
Cause: The PL/SQL procedure has been altered, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL function has been created, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL function has been altered, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL package has been created, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL package has been altered, but has one or more warnings, informational messages or performance messages 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 with compilation warnings
Cause: The PL/SQL package body has been created, but has one or more warnings, informational messages or performance messages 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 with compilation warnings
Cause: The PL/SQL package body has been altered, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL view has been created, but has one or more warnings, informational messages or performance messages that 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 compilation warnings
Cause: The PL/SQL view has been altered, but has one or more warnings, informational messages or performance messages that 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 compilation warnings
Cause: The PL/SQL trigger has been created, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL trigger has been altered, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL type has been created, but has one or more warnings, informational messages or performance messages that 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 compilation warnings
Cause: The PL/SQL type has been altered, but has one or more warnings, informational messages or performance messages that 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 with compilation warnings
Cause: The PL/SQL type body has been created, but has one or more warnings, informational messages or performance messages 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 with compilation warnings
Cause: The PL/SQL type body has been altered, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL library has been created, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL library has been altered, but has one or more warnings, informational messages or performance messages 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 compilation warnings
Cause: The PL/SQL java has been created, but has one or more warnings, informational messages or performance messages that 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 compilation warnings
Cause: The PL/SQL java has been altered, but has one or more warnings, informational messages or performance messages that 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 warnings
Cause: The PL/SQL block has been created, but has one or more warnings, informational messages or performance messages that 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 with compilation warnings
Cause: The PL/SQL dimension has been created, but has one or more warnings, informational messages or performance messages 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 with compilation warnings
Cause: The PL/SQL dimension has been altered, but has one or more warnings, informational messages or performance messages 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 compilation errors
Cause: 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 with compilation errors
Cause: 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 compilation errors
Cause: 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 compilation errors
Cause: 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 compilation errors
Cause: 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 compilation errors
Cause: 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 with compilation errors
Cause: 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 with compilation errors
Cause: 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 compilation errors
Cause: 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 compilation errors
Cause: 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 compilation errors
Cause: 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 compilation errors
Cause: 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 compilation errors
Cause: 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 compilation errors
Cause: 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 with compilation errors
Cause: 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 with compilation errors
Cause: 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 compilation errors
Cause: 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 compilation errors
Cause: 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 compilation error
Cause: 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 compilation errors
Cause: 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 errors
Cause: 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 with compilation errors
Cause: 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 with compilation errors
Cause: 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 only valid with Oracle 9.2 or greater
Cause: 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 at least release 9.2.
SP2-1501 STARTUP with DOWNGRADE only valid with Oracle 9.2 or greater
Cause: 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 at least release 9.2.
SP2-1502 The HTTP proxy server specified by http_proxy is not accessible
Cause: The HTTP proxy server used by SQL*Plus cannot be accessed. SQL*Plus will be unable to run scripts located on a web server.
Action: Check that the proxy setting has the correct value, or unset it if no proxy is needed. SQL*Plus may get the 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 proxy and verify that web pages can still be loaded.
SP2-1503 Unable to initialize Oracle call interface
Cause: 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*Plus Instant 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 uninitialized LOB variable
Cause: 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 position entered
Cause: The BTITLE, TTITLE, REPHEADER or REPFOOTER command you entered attempts to use a COL or TAB value greater than 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 or less, or uses a COL or TAB value of LINESIZE or less if LINESIZE is greater than 240.

iSQL*Plus Error Messages

SP2-0850 Command command_name is not available in iSQL*Plus
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.
SP2-0851 Command beginning command_name... is not available in iSQL*Plus
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.
SP2-0852 Option not available in iSQL*Plus
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, because they prevent proper operation, or because they pose a security risk.
Action: Remove the option from the command.
SP2-0853 Empty username field
Cause: 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 entered twice
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.
SP2-0855 Connect identifier cannot be entered twice
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.
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 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.
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 commands enter HELP
Cause: An invalid command sequence was entered.
Action: Use the HELP command to show the syntax of SQL*Plus commands.
SP2-0863 iSQL*Plus processing completed
Cause: All commands in the iSQL*Plus input script have been executed with no explicit output.
Action: No action required.
SP2-0864 Session has expired. Please log in again
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 timeout period.
SP2-0865 Session is blocked. Please log in again
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.
SP2-0866 Please enter statements in the Input area
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.
SP2-0867 No script to be saved
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.
SP2-0868 No script to execute
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.
SP2-0869 Invalid file content
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 your browser to recognize the file 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 load
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.
SP2-0872 SET AUTORECOVERY ON must be used in iSQL*Plus
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.
SP2-0873 An unexpected quote was found in the URL argument
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.
SP2-0874 URL argument is missing a keyword
Cause: 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 a keyword but no value
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.
SP2-0876 URL argument is missing an end quote
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.
SP2-0877 Found an unexpected character in a URL argument
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.
SP2-0878 Duplicate keyword keyword specified
Cause: 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 for dynamic reports to execute
Cause: The script keyword was not specified in the URL.
Action: Add a script keyword/value pair to the URL argument.
SP2-0880 Enter connection details to run script script_url
Cause: 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 field
Cause: 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 size specified
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.
SP2-0884 Connection to database connect_identifier is not allowed
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 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 parameter list. The connection identifier is not case sensitive.
SP2-0885 Only a valid username or '/' is allowed in the username field
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.
SP2-0886 No scripts in history
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.
SP2-0887 History size specified is 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 for the keyword type must be either URL or TEXT
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".
SP2-0890 Instance not set, or connect identifier not specified
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.
SP2-0892 Error expiring session
Cause: iSQL*Plus could not close the timed out session identified by the user session Id.
Action: No action required.
SP2-0893 Expired session
Cause: iSQL*Plus has expired the timed out session identified by the user session Id.
Action: No action required.
SP2-0894 Unsuccessful log in for username from URL to connect_id
Cause: 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 username
Cause: iSQL*Plus failed to log out user with given user session Id.
Action: No action required.
SP2-0911 Only a password is allowed in the password field
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.
SP2-0912 Only a connect identifier is allowed in the connection identifier 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.
SP2-0913 No keywords recognised by iSQL*Plus
Cause: An attempt was made to request a service from iSQL*Plus by manually typing in the URL, but no keywords could be recognized.
Action: Refer to the iSQL*Plus documentation for the syntax, and types of service that can be manually entered in a URL.
SP2-0914 Value "value" for keyword "keyword" not recognised by iSQL*Plus
Cause: An attempt was made to request a service from iSQL*Plus by manually typing in 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.
SP2-0915 Cookies may have been disabled
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.
SP2-0916 Scheme scheme not supported
Cause: iSQL*Plus only supports HTTP, HTTPS and FTP.
Action: Change the scheme to one that is supported.
SP2-0917 User requested cancel
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 Workspace.
Action: No action required.
SP2-0918 HTTP error number on attempt to open URL
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.
SP2-00920 HTTP error message on attempt to open URL
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.
SP2-0921 The value specified for the keyword action must be either EXECUTE or LOAD
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".
SP2-0923 AS SYSDBA or AS SYSOPER login not allowed through the iSQL*Plus URL
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.
SP2-0924 Supplied connect string has duplicate or incorrect keyword
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.
SP2-0925 No scripts selected to load or delete
Cause: 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*Plus internal error: state = number, message = message
Cause: 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 AS SYSOPER not allowed through iSQL*Plus URL
Cause: An attempt was made to CONNECT with AS SYSDBA or AS SYSOPER privileges through the iSQL*Plus URL.
Action: CONNECT with AS SYSDBA or AS SYSOPER privileges is only permitted through the iSQL*Plus DBA 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 reconfigure iSQLPlusAllowUserMarkup in the iSQL*Plus Server
Cause: The iSQL*Plus Server has been configured to prevent the use of SET MARKUP HTML ENTMAP and COLUMN ENTMAP.
Action: The System Administrator can change the value of iSQLPlusAllowUserMarkup in the iSQL*Plus Server configuration to allow use of the ENTMAP option.
SP2-0930 Enter a URL or a path and file name, not both
Cause: In the iSQL*Plus Load Script screen, the location of a script to load into the Workspace 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 contains an illegal parameter
Cause: When attempting to login to iSQL*Plus, an illegal parameter was found in the Connection Identifier string.
Action: Modify the Connection Identifier string to remove the illegal parameter and attempt to log in again.
SP2-0932 Size specified for script width 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 script height 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*Plus Server currently has insufficient memory to complete this script
Cause: The iSQL*Plus Server could not completely execute the script because there was not 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 report URL
Cause: Either required parameters are missing from the dynamic report URL or there are special characters in the URL that are not HTML encoded.
Action: Check that all parameters are correct and that any special characters are HTML encoded before submitting the dynamic report URL again.
SP2-0936 URL access is disabled in iSQL*Plus
Cause: @, @@ or START was used with a URL, or a dynamic report referenced a URL. The iSQL*Plus Administrator has disabled this functionality.
Action: Contact your iSQL*Plus Administrator.

COPY Command Messages

CPY-0002 Illegal or missing APPEND, CREATE, INSERT, or REPLACE option
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.
CPY-0003 Internal Error: logical host number out of range
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.
CPY-0004 Source and destination table and column names don't match
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
CPY-0005 Source and destination column attributes don't match
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.
CPY-0006 Select list has more columns than destination table
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.
CPY-0007 Select list has fewer columns than 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.
CPY-0008 More column list names than columns 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.
CPY-0009 Fewer column list names than columns 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.
CPY-0012 Datatype cannot be copied
Cause: An attempt was made to copy a 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 SQL*Plus COPY Command.

你可能感兴趣的:(message)

  • 基于websocket实现Web群聊 一杯雪花勇闯天涯 音视频技术websocket前端javascript
    安装node中ws模块npminstallwsNode中处理代码constWebSocket=require("ws");constwsServer=newWebSocket.Server({port:3000});varmaps=newMap();varnumber=0;varsendMessage={};wsServer.on('connection',(socket)=>{console.l
  • Python——pyqt5——消息框（QMessageBox） 少年痴北城 python
    一、提供的类型QMessageBox.information信息框QMessageBox.question问答框QMessageBox.warning警告QMessageBox.ctitical危险QMessageBox.about关于二、引用fromPyQt5.QtWidgetsimportQMessageBox三、代码示例#消息框#self当前窗口的夫窗口#消息：信息QMessageBox.i
  • PyQT5 QMessageBox对话框设置 自动驾驶探索站 python开发语言qt5
    PyQT5QMessageBox对话框设置1介绍2演示3代码1介绍  QMessageBox是一种通用的弹出式对话框，用于显示消息，允许用户通过单击不同的标准按钮对消息进行反馈。提供了许多常用的弹出式对话框，如提示、警告、错误、询问、关于等对话框。这些不同类型的QMessageBox对话框只是显示时的图标不同，其他功能是一样的。  QMessageBox类中的常用方法如下：方法描述QMessage
  • Pyqt5_QMessageBox weixin_33850890 c/c++
    QMessageBoxheader:会话窗标题info：会话窗内容#弹出5种不同类型的消息框reply1=QMessageBox.information(self,"title","infocontent",QMessageBox.Yes|QMessageBox.No,QMessageBox.Yes)reply2=QMessageBox.question(self,"title","questio
  • 回调 函数解决异步，promise解决异步 css趣多多 java前端javascript
    created(){//===============================================回调函数解决异步//this.getList((res)=>{//this.$message.success("获取数据成功");//constfirstData=res.data;////再次获取数据，需要依赖于第一次获取的数据//this.getList2((finalData
  • Python PyQt5 QMessageBox 教程 蜡笔小新星 PyQt5pythonqt开发语言经验分享学习前端
    文章目录前言导入必要的模块基本用法显示信息框显示警告框显示错误框显示询问框显示关于框自定义QMessageBox自定义按钮和图标完整示例前言在PyQt5中，QMessageBox是一个常用的对话框类，用于向用户显示信息、警告、询问、错误等消息，并允许用户通过点击按钮来响应。本教程将详细介绍QMessageBox的基本用法，并提供丰富的案例示例。导入必要的模块首先，我们需要从PyQt5.QtWidg
  • HTML5 通信方式及应用 天涯学馆 大前端&移动端全栈架构html5前端html
    目录postMessageAPIWebSocketsServer-SentEvents(SSE)FetchAPI/XMLHttpRequest(XHR)WebWorkers&ServiceWorkersHTML5提供了多种通信方式，使得浏览器中的Web应用能够实现页面间、窗口间、甚至与外部服务的有效通信。这些通信方式大大提升了Web应用的交互性和复杂性，为构建现代、富客户端Web应用奠定了基础。以
  • C++学习——引用变量中易出现的错误 Ricky_One 学习c++笔记
    在C++学习中容易出现变量引用不恰当导致编译错误，先来看一段代码：#includeusingnamespacestd;voidprintMessage(string&message){cout<
  • 低版本impala多次去重UDAF 路边草随风 大数据c++hadoopimpalaUDAF大数据C++
    使用低版本的impala在进行去重统计count(distinct字段)操作的时候会遇到很大的限制，就是一条sql只能对一个字段进行去重统计，多于一个字段使用count(distinct字段)则会提示如下报错：”errorMessage:AnalysisException:allDISTINCTaggregatefunctionsneedtohavethesamesetofparametersas
  • 程序代码篇---Numpy&assert&迭代器 Ronin-Lotus 程序代码篇numpypython学习assert迭代器
    文章目录前言第一部分：Numpy1.创建数组2.数组索引和切片3.数组形状操作4.数组运算5.数学函数6.随机数生成7.数组排序第二部分：assert基本语法1.condition2.error_message示例注意事项断言的用途第三部分：迭代器迭代器协议1.__iter__()2.__next__()迭代器的特点1.惰性求值2.一次性3.内存效率创建迭代器使用迭代器迭代器和可迭代对象可迭代对象
  • Kafka 实现之消息及消息格式 流华追梦 KafkakafkaKafka消息Kafka消息格式消息批次控制批次RecordHeader旧消息格式
    目录一.前言二.Kafka消息（Messages）三.Kafka消息格式（MessageFormat）3.1.消息批次（RecordBatch）3.1.1.控制批次（ControlBatches）3.2.记录（Record）3.2.1.记录的Header（RecordHeader）3.3.旧消息格式（OldMessageFormat）一.前言Kafka的消息格式是由消息的键和值组成的。每条消息都有
  • 计算机编程中的事件驱动架构在提升应用程序响应性方面的作用与实现 借口 热点资讯
    博客主页：借口的CSDN主页⏩文章专栏：《热点资讯》计算机编程中的事件驱动架构在提升应用程序响应性方面的作用与实现计算机编程中的事件驱动架构在提升应用程序响应性方面的作用与实现计算机编程中的事件驱动架构在提升应用程序响应性方面的作用与实现引言事件驱动架构概述定义历史背景核心组件事件源（EventSource）事件处理器（EventHandler）中介者（Mediator）消息队列（MessageQ
  • 被怼了：acks=all消息也会丢失？ java
    消息队列是面试中一定会被问到的技术模块，虽然它在面试题占比不及并发编程和数据库，但也属于面试中的关键性问题。所以今天我们就来看一道，MQ中高频，但可能会打破你以往认知的一道面试题。所谓的关键问题指的是这道面试题会影响你整体面试结果。我们在面试消息队列（MessageQueue，MQ）时，尤其是面试Kafka时，经常会被问到：如何保证消息不丢失？那么，我们的回答会分为以下3部分：保证生产者消息不丢失
  • 初学可视化PyQt5系列--主要类 万金油笑匠 PyQt5小白学做四旋翼无人机Python数据分析与可视化qt开发语言pythonuipyqt
    【初学可视化PyQt5系列】第1章PyQt5简介第2章PyQt5新增功能第3章Hellomyfourrotordrone第4章PyQt5主要类第5章PyQt5使用Qt设计器第6章PyQt5信号与插槽第7章PyQt5布局与管理第8章PyQt5基本小部件第9章PyQt5QDialog类第10章PyQt5QMessageBox类第11章PyQt5多文档界面第12章PyQt5拖放第13章PyQt5数据库处
  • 【转载】通过 GetMessageExtraInfo 方法判断当前收到的鼠标消息是否来自触控板和 Pen 涟幽516 windowsmicrosoft
    大家都知道，在不开启WM_Pointer的情况下，无论是走WM_Touch或者是RealTimeStylus等方式，默认下触摸都会提升为鼠标消息从而更好兼容应用程序的逻辑如果此时应用程序想要根据消息循环里面接收到的Win32消息判断一个鼠标消息的来源是否来自于触摸框触摸屏或者是Pen笔等，可以通过GetMessageExtraInfo方法获取更多的信息根据GetMessageExtraInfo方法
  • Unity中关于游戏制作的代码架构书写 我叫_小Z unityunity3dc#
    本代码架构一个由四篇代码组成，用于单机小游戏的开发首先是Message脚本用于消息的存放，代码如下:usingSystem.Collections;usingSystem.Collections.Generic;usingUnityEngine;publicclassMessage{//类型publicbyteType;//命令publicintCommand;//参数publicobjectCo
  • [Unity技术] Unity3D高级编程网络层剖析数据协议原理 王 银 UnityUnity辅助拓展json
    协议包的格式，json,msgpack,protobuf以及自定义格式项目的网路层在建设中，除了选择传输协议TCP，UDP，以及应用层协议HTTP方式外，还需要选择在传输过程中的业务层协议格式。前面我们分析了TCP，UDP，HTTP的原理与应用，这里我们来了解下在传输层和应用层之上的业务层中，网络数据传输格式的选择以及它们的利弊。我们将在这里剖析JSON，MessagePack，Protobuf的
  • Python 如何使用访问Windows共享文件夹 蜡笔小新星 pythonwindows开发语言经验分享
    文章目录引言前置条件步骤一：导入必要的模块步骤二：配置连接参数步骤三：实例化SMB连接对象并尝试连接步骤四：列出共享文件夹中的文件与文件夹步骤五：下载与上传文件（可选）步骤六：处理连接错误错误排查指南结论引言本教程旨在帮助您使用pysmb库，通过SMB（ServerMessageBlock）协议，轻松连接到Windows共享文件夹，并列举其中的文件与文件夹。此外，我们还将简要介绍如何下载和上传文件
  • Android10 高通平台 softap热点基本流程2 VaderZhang Android系统WIFI开发softaphotspot热点Android
    上一篇讲到SoftApManager.IdleState状态中处理CMD_START消息，这个消息用来打开热点功能。我们从这里继续看热点功能基本流程。publicbooleanprocessMessage(Messagemessage){switch(message.what){caseCMD_START:WifiConfigurationconfig=(WifiConfiguration)mes
  • 【RocketMQ 存储】- broker 端存储批量消息的逻辑 月幻星影 源码分析RocketMQjava-rocketmqrocketmq消息存储
    文章目录1.前言2.DefaultMessageStore#asyncPutMessages批量新增消息2.1Commit#asyncPutMessages2.2Commit#encode批量编码消息2.3MappedFile#appendMessages添加批量消息2.4MappedFile#appendMessagesInner添加批量消息2.5CommitLog#doAppend3.小结本文
  • 用PYTHON Tkinter 做四子棋游戏(1) Flash The Dash PythonTkinter四子棋游戏游戏python
    之前，总在想，既然有五子棋，有三子棋，为何不做一四子棋游戏呢？今天，就来尝试用PYTHON来开发一个四子棋游戏。首先，想好如何设置棋盘：10*10，读者也能自行调整。随后就设置好了网页的初始长宽，背景颜色等等。代码如下：importtkinterastkfromtkinterimportmessageboximporttimeimportrandomclassTicTacToe:def__init
  • Rollup：专注类库和框架打包 时解之 JS专区RollupRollup打包大前端Javascript
    文章内容输出来源：拉勾大前端高薪训练营-概述-也是一款ESModules打包器-也可以将项目中的一些散落的细小模块打包为整块代码-rollup与webpack作用类似-rollup更为小巧，仅仅是一款ESM打包器-rollup中并不支持类似HMR这种高级特性-rollup并不是要与webpack全面竞争-目标是提供一个充分利用ESM各项特性的高效打包器-快速上手-准备代码-src/message.
  • Vue对话式前端界面 WUJI02 裁判文书大模型vue.js前端javascript
    一.对话样式的实现用一个messages数组来存放对话信息，信息有两种类型user和botthis.messages.push({type:'user',content:this.userMessage});this.messages.push({type:'bot',content:response.data.reply});模版部分使用:class="['message-content',me
  • 2024年Python最新python之protobuf使用案例_python protobuf 使用案例(1) 2401_84557849 程序员python网络java
    enumPhoneType{MOBILE=0;HOME=1;WORK=2;}messagePhoneNumber{requiredstringnumber=1;optionalPhoneTypetype=2[default=HOME];}repeatedPhoneNumberphones=4;//repeate类似数组，里面可以存放多个PhoneNumber可自定义类型}messageAddres
  • python+selenium定位网页 动态元素 + 定位非select（即input）的下拉列表 + 返回上一个函数进行保存操作 心田婷 python定位seleniumpython
    1、python+selenium定位网页动态元素这个折磨我快一天的小东西，磨的我都快想睡觉了网上大佬门的经验啥的都看遍了，或许是看到不够多，找了一天都没解决，然后现在终于找到了解决的办法！！！报错：selenium.common.exceptions.NoSuchElementException:Message:nosuchelement:Unabletolocateelement:{“meth
  • 支持selenium的chromedriver更新到125.0.6422.60 代码的乐趣 selenium测试工具
    最近chrome释放新版本：125.0.6422.60如果运行selenium自动化测试出现以下问题是，是需要升级chromedriver才可以解决的。selenium.common.exceptions.SessionNotCreatedException:Message:sessionnotcreated:ThisversionofChromeDriveronlysupportsChromev
  • Kafka常见问题之 org.apache.kafka.common.errors.RecordTooLargeException 王多鱼的梦想～ Kafka修炼手册kafkaapache分布式运维
    文章目录Kafka常见问题之org.apache.kafka.common.errors.RecordTooLargeException:Themessageis1,048,576byteswhenserializedwhichislargerthanthemaximumrequestsize.1.错误解析2.错误原因3.错误复现案例3.1生产者发送超大消息4.解决方案4.1方法1：调整Kafka
  • 搭建 PostgreSQL 阿杰技术 数据库数据库postgresql
    端口：5432代理备份端口：6432下载postgresql-15.0-1-windows-x64乱码显示配置环境变量PGDATA=数据目录位置找到postgresql.conf文件，修改参数lc_messages='UTF8'max_connections=1000shared_buffers=4GBwork_mem=8MB问题：远程易掉线方案：修改配置信息tcp_keepalives_idle
  • 【Python进阶】assert 使用 | assert触发条件，使用实践示例 Qodicat Python学习python开发语言
    文章目录1基本介绍2其他实践示例2.1检查函数参数2.2检查输入数据是否合规2.3检查操作是否合规1基本介绍assert是Python中的一个关键字，用于在代码中进行断言检查。它的作用是在条件为False的情况下触发AssertionError异常，用于帮助开发者在程序中捕获和处理错误。assert的语法如下：assertexpression,message其中expression是要进行断言检查
  • MFC常用操作 我爱_编程 UG二次开发mfc
    1，获取STATIC控件的值CStringstr;m_STATIC2.GetWindowText(str);//获取STATIC控件的值MessageBox(str);2.设置EDIT控件的值m_EDIT2.SetWindowText(str);//设置EDIT控件的值GetDlgItem(IDC_EDIT1)->SetWindowText("Leave");//设置EDIT控件的值3.移动控件m
  • JAVA中的Enum 周凡杨 javaenum枚举
    Enum是计算机编程语言中的一种数据类型---枚举类型。 在实际问题中，有些变量的取值被限定在一个有限的范围内。     例如，一个星期内只有七天 我们通常这样实现上面的定义： public String monday; public String tuesday; public String wensday; public String thursday
  • 赶集网mysql开发36条军规 Bill_chen mysql业务架构设计mysql调优mysql性能优化
    (一)核心军规 (1)不在数据库做运算    cpu计算务必移至业务层； (2)控制单表数据量    int型不超过1000w，含char则不超过500w；    合理分表；    限制单库表数量在300以内； (3)控制列数量    字段少而精，字段数建议在20以内
  • Shell test命令 daizj shell字符串test数字文件比较
    Shell test命令 Shell中的 test 命令用于检查某个条件是否成立，它可以进行数值、字符和文件三个方面的测试。 数值测试 参数 说明 -eq 等于则为真 -ne 不等于则为真 -gt 大于则为真 -ge 大于等于则为真 -lt 小于则为真 -le 小于等于则为真 实例演示： num1=100 num2=100if test $[num1]
  • XFire框架实现WebService(二) 周凡杨 javawebservice
       有了XFire框架实现WebService(一)，就可以继续开发WebService的简单应用。 Webservice的服务端(WEB工程)： 两个java bean类： Course.java    package cn.com.bean; public class Course {     private
  • 重绘之画图板 朱辉辉33 画图板
           上次博客讲的五子棋重绘比较简单，因为只要在重写系统重绘方法paint（）时加入棋盘和棋子的绘制。这次我想说说画图板的重绘。        画图板重绘难在需要重绘的类型很多，比如说里面有矩形，园，直线之类的，所以我们要想办法将里面的图形加入一个队列中，这样在重绘时就
  • Java的IO流 西蜀石兰 java
    刚学Java的IO流时，被各种inputStream流弄的很迷糊，看老罗视频时说想象成插在文件上的一根管道，当初听时觉得自己很明白，可到自己用时，有不知道怎么代码了。。。 每当遇到这种问题时，我习惯性的从头开始理逻辑，会问自己一些很简单的问题，把这些简单的问题想明白了，再看代码时才不会迷糊。 IO流作用是什么？ 答：实现对文件的读写，这里的文件是广义的； Java如何实现程序到文件
  • No matching PlatformTransactionManager bean found for qualifier 'add' - neither 林鹤霄
    java.lang.IllegalStateException: No matching PlatformTransactionManager bean found for qualifier 'add' - neither qualifier match nor bean name match!   网上找了好多的资料没能解决，后来发现：项目中使用的是xml配置的方式配置事务，但是
  • Row size too large (> 8126). Changing some columns to TEXT or BLOB aigo column
    原文：http://stackoverflow.com/questions/15585602/change-limit-for-mysql-row-size-too-large   异常信息： Row size too large (> 8126). Changing some columns to TEXT or BLOB or using ROW_FORMAT=DYNAM
  • JS 格式化时间 alxw4616 JavaScript
    /** * 格式化时间 2013/6/13 by 半仙 [email protected] * 需要 pad 函数 * 接收可用的时间值. * 返回替换时间占位符后的字符串 * * 时间占位符:年 Y 月 M 日 D 小时 h 分 m 秒 s 重复次数表示占位数 * 如 YYYY 4占4位 YY 占2位<p></p> * MM DD hh mm
  • 队列中数据的移除问题 百合不是茶 队列移除
         队列的移除一般都是使用的remov();都可以移除的,但是在昨天做线程移除的时候出现了点问题,没有将遍历出来的全部移除,  代码如下;      // package com.Thread0715.com; import java.util.ArrayList; public class Threa
  • Runnable接口使用实例 bijian1013 javathreadRunnablejava多线程
    Runnable接口 a.       该接口只有一个方法：public void run(); b.       实现该接口的类必须覆盖该run方法 c.       实现了Runnable接口的类并不具有任何天
  • oracle里的extend详解 bijian1013 oracle数据库extend
    扩展已知的数组空间，例： DECLARE TYPE CourseList IS TABLE OF VARCHAR2(10); courses CourseList; BEGIN -- 初始化数组元素，大小为3 courses := CourseList('Biol 4412 ', 'Psyc 3112 ', 'Anth 3001 '); --
  • 【httpclient】httpclient发送表单POST请求 bit1129 httpclient
    浏览器Form Post请求 浏览器可以通过提交表单的方式向服务器发起POST请求，这种形式的POST请求不同于一般的POST请求 1. 一般的POST请求，将请求数据放置于请求体中，服务器端以二进制流的方式读取数据，HttpServletRequest.getInputStream()。这种方式的请求可以处理任意数据形式的POST请求，比如请求数据是字符串或者是二进制数据 2. Form
  • 【Hive十三】Hive读写Avro格式的数据 bit1129 hive
     1. 原始数据 hive> select * from word; OK 1 MSN 10 QQ 100 Gtalk 1000 Skype      2. 创建avro格式的数据表   hive> CREATE TABLE avro_table(age INT, name STRING)STORE
  • nginx+lua+redis自动识别封解禁频繁访问IP ronin47
    在站点遇到攻击且无明显攻击特征，造成站点访问慢，nginx不断返回502等错误时，可利用nginx+lua+redis实现在指定的时间段 内，若单IP的请求量达到指定的数量后对该IP进行封禁，nginx返回403禁止访问。利用redis的expire命令设置封禁IP的过期时间达到在 指定的封禁时间后实行自动解封的目的。 一、安装环境： CentOS x64 release 6.4(Fin
  • java-二叉树的遍历-先序、中序、后序（递归和非递归）、层次遍历 bylijinnan java
    import java.util.LinkedList; import java.util.List; import java.util.Stack; public class BinTreeTraverse { //private int[] array={ 1, 2, 3, 4, 5, 6, 7, 8, 9 }; private int[] array={ 10,6,
  • Spring源码学习-XML 配置方式的IoC容器启动过程分析 bylijinnan javaspringIOC
    以FileSystemXmlApplicationContext为例，把Spring IoC容器的初始化流程走一遍： ApplicationContext context = new FileSystemXmlApplicationContext ("C:/Users/ZARA/workspace/HelloSpring/src/Beans.xml&q
  • [科研与项目]民营企业请慎重参与军事科技工程 comsci 企业
         军事科研工程和项目 并非要用最先进，最时髦的技术，而是要做到“万无一失”    而民营科技企业在搞科技创新工程的时候，往往考虑的是技术的先进性，而对先进技术带来的风险考虑得不够，在今天提倡军民融合发展的大环境下，这种“万无一失”和“时髦性”的矛盾会日益凸显。。。。。。所以请大家在参与任何重大的军事和政府项目之前，对
  • spring 定时器-两种方式 cuityang springquartz定时器
    方式一： 间隔一定时间 运行 <bean id="updateSessionIdTask" class="com.yang.iprms.common.UpdateSessionTask" autowire="byName" /> <bean id="updateSessionIdSchedule
  • 简述一下关于BroadView站点的相关设计 damoqiongqiu view
    终于弄上线了，累趴，戳这里http://www.broadview.com.cn   简述一下相关的技术点   前端：jQuery+BootStrap3.2+HandleBars，全站Ajax（貌似对SEO的影响很大啊！怎么破？），用Grunt对全部JS做了压缩处理，对部分JS和CSS做了合并（模块间存在很多依赖，全部合并比较繁琐，待完善）。   后端：U
  • 运维 PHP问题汇总 dcj3sjt126com windows2003
    1、Dede(织梦)发表文章时,内容自动添加关键字显示空白页 解决方法： 后台>系统>系统基本参数>核心设置>关键字替换（是/否），这里选择“是”。 后台>系统>系统基本参数>其他选项>自动提取关键字，这里选择“是”。   2、解决PHP168超级管理员上传图片提示你的空间不足 网站是用PHP168做的，反映使用管理员在后台无法
  • mac 下 安装php扩展 - mcrypt dcj3sjt126com PHP
    MCrypt是一个功能强大的加密算法扩展库，它包括有22种算法，phpMyAdmin依赖这个PHP扩展，具体如下： 下载并解压libmcrypt-2.5.8.tar.gz。 在终端执行如下命令： tar zxvf libmcrypt-2.5.8.tar.gz cd libmcrypt-2.5.8/ ./configure --disable-posix-threads --
  • MongoDB更新文档 [四] eksliang mongodbMongodb更新文档
    MongoDB更新文档 转载请出自出处：http://eksliang.iteye.com/blog/2174104 MongoDB对文档的CURD，前面的博客简单介绍了，但是对文档更新篇幅比较大，所以这里单独拿出来。 语法结构如下： db.collection.update( criteria, objNew, upsert, multi) 参数含义 参数   
  • Linux下的解压，移除，复制，查看tomcat命令 y806839048 tomcat
    重复myeclipse生成webservice有问题删除以前的，干净 1、先切换到：cd usr/local/tomcat5/logs 2、tail -f catalina.out 3、这样运行时就可以实时查看运行日志了 Ctrl+c 是退出tail命令。 有问题不明的先注掉   cp /opt/tomcat-6.0.44/webapps/g
  • Spring之使用事务缘由(3-XML实现) ihuning spring
      用事务通知声明式地管理事务   事务管理是一种横切关注点。为了在 Spring 2.x 中启用声明式事务管理，可以通过 tx Schema 中定义的 <tx:advice> 元素声明事务通知，为此必须事先将这个 Schema 定义添加到 <beans> 根元素中去。声明了事务通知后，就需要将它与切入点关联起来。由于事务通知是在 <aop:
  • GCD使用经验与技巧浅谈 啸笑天 GC
    前言 GCD(Grand Central Dispatch)可以说是Mac、iOS开发中的一大“利器”，本文就总结一些有关使用GCD的经验与技巧。 dispatch_once_t必须是全局或static变量 这一条算是“老生常谈”了，但我认为还是有必要强调一次，毕竟非全局或非static的dispatch_once_t变量在使用时会导致非常不好排查的bug，正确的如下： 1
  • linux（Ubuntu）下常用命令备忘录1 macroli linux工作ubuntu
    在使用下面的命令是可以通过--help来获取更多的信息1,查询当前目录文件列表：ls ls命令默认状态下将按首字母升序列出你当前文件夹下面的所有内容，但这样直接运行所得到的信息也是比较少的，通常它可以结合以下这些参数运行以查询更多的信息：  ls / 显示/.下的所有文件和目录  ls -l 给出文件或者文件夹的详细信息 ls -a 显示所有文件，包括隐藏文
  • nodejs同步操作mysql qiaolevip 学习永无止境每天进步一点点mysqlnodejs
    // db-util.js var mysql = require('mysql'); var pool = mysql.createPool({ connectionLimit : 10, host: 'localhost', user: 'root', password: '', database: 'test', port: 3306 });
  • 一起学Hive系列文章 superlxw1234 hiveHive入门
      [一起学Hive]系列文章 目录贴，入门Hive，持续更新中。   [一起学Hive]之一—Hive概述，Hive是什么 [一起学Hive]之二—Hive函数大全-完整版 [一起学Hive]之三—Hive中的数据库(Database)和表(Table) [一起学Hive]之四-Hive的安装配置 [一起学Hive]之五-Hive的视图和分区 [一起学Hive
  • Spring开发利器：Spring Tool Suite 3.7.0 发布 wiselyman spring
    Spring Tool Suite(简称STS)是基于Eclipse，专门针对Spring开发者提供大量的便捷功能的优秀开发工具。   在3.7.0版本主要做了如下的更新：   将eclipse版本更新至Eclipse Mars 4.5 GA Spring Boot(JavaEE开发的颠覆者集大成者，推荐大家学习)的配置语言YAML编辑器的支持(包含自动提示，
按字母分类： ABCDEFGHIJKLMNOPQRSTUVWXYZ其他