SQL*Plus Error Messages
-
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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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-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.
COPY Command Messages
-
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