Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8
Error Messages Release 8.0 A54625_01 |
|
Cause: An I/O error occurred on the named online redo log file, probably because the file was not accessible or because it was corrupted.
Action: Restore access to the file or restore the file from a backup.
Cause: The internal information in an online redo log file does not match the control file information.
Action: Refer to the Oracle8 Server Administrator's Guide for recovery procedures.
Cause: Recovery was given a log that was created before the last ALTER DATABASE OPEN RESETLOGS command. There should be another log created since then that contains the correct redo.
Action: Find and install the correct archived redo log file, then retry the operation.
Cause: The maximum number of errors on this log member has been exceeded. Other messages will accompany this message.
Action: Correct the underlying problems mentioned in the other messages.
Cause: An I/O failure occurred when attempting to recreate an online log as part of either an ALTER DATABASE OPEN RESETLOGS or ALTER DATABASE CLEAR log file command.
Action: Check the accompanying messages. Check that the file is accessible.
Cause: An I/O error has occurred while writing the log, probably because the file was not accessible, or a device failed.
Action: Make the file accessible or restore the device, then restart the system. If the log is lost, apply media or incomplete recovery.
Cause: A redo log file member is no longer complete. Other messages will accompany this message.
Action: Correct the underlying problem mentioned in the other messages.
Cause: During online recovery, the block size specified in the control file did not match the block size indicated in the redo log file.
Action: Restore the correct redo log file from a backup or reset the online redo log files.
Cause: A failure occurred during a single-process redo log operation. This error does not occur during normal multi-process operations.
Action: Shut down and restart the database.
Cause: The operating system was unable to determine the block size for the named file.
Action: Check the accompanying messages, then restore the device or specify another file.
Cause: Media recovery is enabled and the specified log was not archived.
Action: Archive the redo log file or disable media recovery. If the command supports the UNARCHIVED option, then it can be used. However, this may result in making backups unusable and forcing some offline files to be dropped.
Cause: The time specified in a RECOVER DATABASE... UNTIL is before January 1, 1988.
Action: Specify a time after January 1, 1988.
Cause: An attempt was made to enable a thread when all of the online redo log files in the thread needed to be archived, and media recovery has been enabled. There is no online redo log file that can be made the new current log for the thread.
Action: Archive a redo log file for the thread.
Cause: Some type of redo log file corruption has been discovered. This message describes the location of the corruption. Other messages will accompany this message and describe the type of corruption.
Action: Perform recovery with a good version of the redo log file or perform incomplete recovery up to the indicated change or time. For more information about recovery and incomplete recovery, see the index entries on "recovery, incomplete" and on "redo log files" in Oracle8 Server Concepts.
Cause: The block header on the block in the redo log file is not valid. The block number and time-stamp are given in an accompanying message.
Action: Perform recovery with a good version of the redo log file or perform cancel-based recovery up to, but not including, the corrupted redo log file.
Cause: A change number found in the redo log file is lower than a previously encountered change number. The redo log file is corrupted in some way. The corruption may be at the earlier change number or at this one. The block number and time-stamp are given in an accompanying message.
Action: Perform recovery with a good version of the redo log file or perform time-based recovery up to the indicated time.
Cause: A change record in the redo log file contains lengths that do not add up to a consistent value. The redo log file is corrupted in some way.
Action: Perform recovery with a good version of the redo log file or perform time-based recovery up to the indicated time.
Cause: An attempt was made to add a redo log group or add a redo log group member that would result in a set of online redo logs with too many members. The maximum number of members is set when the database is created.
Action: Use fewer redo log group members or use the CREATE CONTROLFILE command and set the parameter MAXLOGMEMBERS to a larger value.
Cause: A CREATE or ALTER statement specified too many members in the file list.
Action: Specify a number of files that is within the given limit or use the CREATE CONTROLFILE command and set the parameter MAXLOGMEMBERS to a larger value.
Cause: An attempt to add or drop a redo log group member specified a redo log file group number that does not exist.
Action: Check the configuration of the redo log files and retry the command with a valid group number.
Cause: An invalid filename was given to drop a redo log group member. Either the file is not a part of the database, or it is a datafile.
Action: Specify a valid member name and retry the command.
Cause: An attempt was made to remove the last member of a redo log group.
Action: If desired, delete the entire log by using the DROP log file command.
Cause: A request to drop a redo log group member was denied because it would remove data required to form a complete online redo log group.
Action: If desired, delete the entire log after archiving, if required, using the DROP log file command.
Cause: The log given for recovery is a backup of the online version from the time it was the current log. The archived version of the log would not be marked as the end of the thread. This message can also be caused by failing to list the current log of an enabled thread in a CREATE CONTROLFILE command.
Action: Find the archived version of the log and specify its name. If this is media recovery immediately following a CREATE CONTROLFILE, be sure the current log for this thread was included.
Cause: An I/O error occurred when attempting to write the header to a redo log group member that is being added to an existing group.
Action: See accompanying messages. Fix the problem or use another file.
Cause: The specified log failed to pass checks to ensure it corresponds to the log that was generated against a cold backup image of the database.
Action: Find the log that was generated by this copy of the database and give that filename to recover.
Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted
Action: Find and install correct version of log or reset logs.
Cause: The file header for the redo log contains a checksum that does not match the value calculated from the file header as read from disk. This means the file header is corrupted
Action: Find the correct file and try again.
Cause: The redo block indicated by the accompanying error, is not valid. It has a checksum that does not match the block contents.
Action: Do recovery with a good version of the log or do time based recovery up to the indicated time. If this happens when archiving, archiving of the problem log can be skipped by clearing the log with the UNARCHIVED option. This must be followed by a backup of every datafile to insure recoverability of the database.
Cause: Attempt to open thread failed because it is necessary to switch redo generation to another online log, but all the other logs are being cleared or need to be archived before they can be used.
Action: If the ALTER DATABASE CLEAR log file command is still active then wait for it to complete. Otherwise, re-enter the CLEAR command. If there are other online logs for the thread that are not being cleared, then archive the logs.
Cause: The value of the initialization parameter DB_HANDLES is too small.
Action: Shut down the instance, increase the value of DB_HANDLES in the initialization parameter file, and then restart the instance. Under normal circumstances, let DB_HANDLES take its default value by omitting the parameter from the initialization parameter file.
Cause: An attempt was made to access a file being taken off line, or the database may be closing.
Action: Access the file after it is taken off line. Attempts will either succeed because the datafile is back online or fail with a message describing which file is off line. Repeat until successful.
Cause: The online log was written by an incompatible version of Oracle. This can occur when the redo log file was created by either a newer or older version of Oracle.
Action: Recover the database using a compatible version, shut it down cleanly; then restart with the current software.
Cause: An invalid value has been used for the DB_BLOCK_SIZE initialization parameter.
Action: Adjust the parameter and restart the instance.
Cause: The system was unable to determine the default DB_BLOCK_SIZE.
Action: See the corresponding operating system-specific message. As a work-around, specify the block size with the parameter DB_BLOCK_SIZE in the initialization parameter file. See also your operating system-specific Oracle documentation.
Cause: An attempt was made to read from a file that is not readable. The most likely cause is that the file is off line.
Action: Check the state of the file. Bring the file online, if necessary.
Cause: Backups are occurring too frequently on this file. Each time a new backup is started for a file, any writes which have been previously issued (but not completed) have to be re-issued. If hot backups are started very, very frequently, it is possible that some writes will be re-issued repeatedly and never complete.
Action: Increase the interval between begin hot-backup commands for this file.
Cause: Either the number of buffers or the number of LRU latches is too small to satisfy the specified buffer pool configuration.
Action: Either increase the number of buffers and/or number of LRU latches or configure smaller buffer pools.
This section lists messages concerning the redo log file.
Cause: An attempt to switch to a new online log for the redo thread failed because no reusable log could be found. This log is being cleared and will be useable when the clearing completes. The command that began the clearing may have terminated without completing the clearing.
Action: If the clear command is still executing, then wait for its completion. If it terminated, then re-enter the clear command or drop the log.
Cause: An attempt to switch the current log of a single thread is not allowed because the compatibility requirements force a new log format version number. When changing log formats, all threads must switch to the new format at the same time.
Action: Open the database to cause the coordinated log switch. If that is not possible, then return to the same software version and compatibility setting last used to open the database.
Cause: An operation encountered this online log in the middle of being cleared. The command that began the clearing may have terminated without completing the clearing.
Action: If the clear command is still executing, then wait for its completion. If it terminated, then re-enter the clear command or drop the log.
Cause: Log cannot be cleared because the redo in it is needed to recover offline datafiles. It has not been archived so there is no other copy available. If the log is cleared, the tablespaces containing the files will have to be dropped.
Action: Archive the log, then repeat the clear command. If archiving is not possible and dropping the tablespaces is acceptable, then add the clause UNRECOVERABLE DATAFILE at the end of the clear command.
Cause: An attempt was made to reuse an online log file that is being archived.
Action: The online logfile has been overwritten; it cannot be archived.
This section lists messages generated when different versions of Oracle communicate.
Cause: The release level given for the specified initialization parameter is invalid.
Action: Correct the parameter value in the initialization parameter file and retry.
Cause: The value specified cannot be supported by this release of the software.
Action: Choose an appropriate value or remove the initialization parameter value to use the default value.
Cause: Changes have been made to the database that require a newer software release or that violate the open compatibility initialization parameters.
Action: Use a version of the software that can understand the changes or relax the compatibility requirements in the initialization parameter file.
Cause: The recovery compatible, or recovery not compatible, initialization parameters were changed for another running instance.
Action: Change the initialization parameters of the current instance to match other instances already running.
Cause: The file used for converting the database from V7 to V8 could not be found.
Action: Verify that the migration process has been started on this database and that the convert file name is accessable.
Cause: Reporting a type associated with another message.
Action: See accompanying message.
Cause: The specification for the initialization parameter COMPATIBLE is too low to allow the requested operation.
Action: Shut down and specify a higher COMPATIBLE value, then restart.
Cause: Another instance has the database mounted and that instance is for a different release of Oracle than you are using.
Action: Shut down and start up all instances with the new release of Oracle.
Cause: Reporting the parameter that resulted in the compatibility error.
Action: Shutdown and startup with a higher compatibility setting.
This section lists messages generated when the installed Oracle product discovers a discrepancy in licensing codes.
Cause: This installed Oracle software is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes.
Action: Check that Oracle is installed correctly. Then contact customer support.
Cause: This installed Oracle feature is not licensed to run on this CPU. This can also occur if Oracle software has been installed incorrectly, for example, with the wrong licensing codes.
Action: Check that Oracle is installed correctly. Then contact customer support.
This section lists messages generated when background processes of the Oracle Server are started or shut down.
Cause: The specified process did not start.
Action: Check that the executable image is in the correct place with the correct protections and that there is enough memory.
Cause: This message is usually caused by a faulty or non-existent background process image.
Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages or obtain a proper background process image, then retry the operation.
Cause: The specified process did not start.
Action: Check and, if necessary, correct problems indicated by one or more of the following:
See also your operating system-specific Oracle documentation.
Cause: A background process started after Oracle was already running.
Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. If no user on site started the process, report the message to customer support.
Cause: One of the background processes completed unexpectedly.
Action: Restart the system. Check and, if necessary, correct the problem indicated by the background trace file in BACKGROUND_DUMP_DEST.
Cause: One of the background processes completed normally as requested by the user.
Action: If you are solving a problem, check for other messages and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart Oracle.
Cause: A foreground process needing service from a background process has discovered the background process died.
Action: Refer to the message code given in the message and the trace file for the foreground and the background processes.
Cause: The log writer process terminated abnormally.
Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process errors, check the trace file for the mentioned process until the root error is found.
Cause: The Database Writer process terminated abnormally.
Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
Cause: The Process Monitor process terminated abnormally.
Action: Check the accompanying messages, and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
Cause: The Archiver process terminated abnormally.
Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
Cause: The System Monitor process terminated abnormally.
Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
Cause: The system tracing process died.
Cause: The distributed transaction, two-phase commit, recovery process died.
Cause: A snapshot refresh process died.
Action: Restart the instance.
Cause: One Lock process terminated abnormally.
Action: Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
Cause: The lock manager monitor process terminated.
Cause: A lock manager daemon process terminated.
Cause: One of the background processes did not exit normally when the instance shut down.
Action: Use the SHUTDOWN ABORT command. Check the accompanying messages, if any, and the background process trace file. Correct the problem mentioned in the other messages. Then restart the instance. If the trace file mentions any other background process messages, check the trace file for the mentioned process until the root message is found.
Cause: The number of registered interrupt handling routines for when the break key is entered exceeds the maximum allowed.
Action: Reduce the number of registered interrupt handlers.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
This section lists messages generated when an internal exception is generated within Oracle.
Cause: This is a catchall internal error message for Oracle program exceptions. It indicates that a process has met a low-level, unexpected condition. Various causes of this message include:
The first argument is the internal message number. Other arguments are various numbers, names, and character strings. See "Calling Customer Support" on page -3 for more information. The numbers may change meanings between different versions of the Oracle Server.
Action: Report this error to customer support after gathering the following information:
NOTE: The cause of this message may manifest itself as different errors at different times. Be aware of the history of errors that occurred before this internal error.
Cause: The Process Monitor process encountered a lock conflict while trying to recover processes. This is an internal error message not usually issued.
Action: Contact customer support.
Cause: An internal programming exception has occurred.
Action: Report this error as a program bug to customer support.
Cause: An Oracle Server session is in an unrecoverable state.
Action: Log in to Oracle again so a new server session will be created automatically. Examine the session trace file for more information.
Cause: An error occurred while processing a recursive SQL statement. A recursive SQL statement is one that applies to internal dictionary tables.
Action: If the situation described in the next message on the stack can be corrected, do so; otherwise, contact customer support.
Cause: A call to deferred UPI functions was made in non-deferred mode.
Action: Contact customer support.
The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.
This section lists messages generated when the Oracle dictionary cache is accessed. Note that row cache is a synonym for dictionary cache.
Cause: An attempt was made to alter or drop a table, cluster, or index defined in the control file's bootstrap segment and needed to warm start the database.
Action: Correct the spelling of the object name or remove it from the ALTER or DROP statement.
Cause: The version of the bootstrap data in a file is incompatible with the current version of the software.
Action: Restore a version of the software that is compatible with the datafiles.
Cause: An operation requested a resource that was unavailable. The maximum number of dictionary cache instance locks is specified by the ROW_CACHE_INSTANCE_LOCKS parameter in the initialization parameter file. When this maximum is reached, no more requests are processed.
Action: Try the operation again in a few minutes. If this error occurs often, contact customer support.
Cause: An error occurred when processing bootstrap data. Refer to the accompanying messages for more information about the cause of the problem.
Action: Correct the problems mentioned in the other messages. If the problem persists, contact customer support.
Cause: A previous attempt to start an instance was terminated.
Action: Shut down the instance completely, then restart it.
Cause: There is an internal error where a routine was unable to translate a message code.
Action: Contact customer support.
This section lists some of the messages generated when SQL statements are parsed by the Oracle Server. Most, but not all, messages in this section indicate incorrect SQL syntax. For SQL syntax, refer to Oracle8 Server SQL Reference.
If you are using Trusted Oracle, see the Trusted Oracle documentation for information about error messages in that environment.
Cause: The statement is not recognized as a valid SQL statement. This error can occur if the Procedural Option is not installed and a SQL statement is issued that requires this option; for example, a CREATE PROCEDURE statement. You can determine if the Procedural Option is installed by starting SQL*Plus. If the PL/SQL banner is not displayed, then the option is not installed.
Action: Correct the syntax or install the Procedural Option.
Cause: The CREATE command was not followed by a valid CREATE option.
Action: Correct the syntax.
Cause: The datatype entered in the CREATE or ALTER TABLE statement is not valid.
Cause: A table or cluster name is invalid or does not exist. This message is also issued if an invalid cluster name or no cluster name is specified in an ALTER CLUSTER or DROP CLUSTER statement.
Action: Check spelling. A valid table name or cluster name must begin with a letter and may contain only alphanumeric characters and the special characters $, _, and #. The name must be less than or equal to 30 characters and cannot be a reserved word.
Cause: The column name entered is either missing or invalid.
Action: Enter a valid column name. A valid column name must begin with a letter, be less than or equal to 30 characters, and consist of only alphanumeric characters and the special characters $, _, and #. If it contains other characters, it must be enclosed in double quotation marks. It may not be a reserved word.
Cause: A required keyword is missing.
Action: Correct the syntax.
Cause: A required left parenthesis has been omitted. Certain commands, such as CREATE TABLE, CREATE CLUSTER, and INSERT, require a list of items enclosed in parentheses. Parentheses also are required around subqueries in WHERE clauses and in UPDATE table SET column = (SELECT...) statements.
Action: Correct the syntax, inserting a left parenthesis where required, and retry the statement.
Cause: A left parenthesis has been entered without a closing right parenthesis, or extra information was contained in the parentheses. All parentheses must be entered in pairs.
Action: Correct the syntax and retry the statement.
Cause: Either of the following: In a CREATE TABLE or ALTER TABLE statement, NOT was entered to specify that no null values are allowed in that column, but the keyword NULL was omitted. In the IS [NOT] NULL logical operator, the keyword NULL was not found. For example, the following statement generates this message:
SELECT * FROM EMP WHERE DEPTNO IS NOT;
The keyword NULL must follow the keywords IS NOT.
Cause: An Oracle function was referenced with an incorrect number of arguments. All Oracle functions, except for SYSDATE, require at least one argument.
Action: Correct the syntax of the function by entering the required number of arguments.
Cause: No size was specified for a character field or the size was invalid. A maximum length must be specified for each character column. The maximum value for this length varies for each character datatype, such as CHAR or VARCHAR2.
Action: Enter a maximum length for the field.
Cause: Special characters are valid only in certain places. If special characters other than $, _, and # are used in a name and the name is not enclosed in double quotation marks ("), this message will be issued. One exception to this rule is for database names; in this case, double quotes are stripped out and ignored.
Action: Remove the invalid character from the statement or enclose the object name in double quotation marks.
Cause: The SQL statement requires two sets of values equal in number. This error occurs when the second set contains more items than the first set. For example, the subquery in a WHERE or HAVING clause may return too many columns, or a VALUES or SELECT clause may return more columns than are listed in the INSERT.
Action: Check the number of items in each set and change the SQL statement to make them equal.
Cause: The keyword ADD does not precede one of the following:
Action: Specify the keyword ADD in the ALTER statement.
Cause: This is an internal error message not usually issued.
Action: Contact customer support.
Cause: A required comma has been omitted from a list of columns or values in an INSERT statement or a list of the form ((C,D),(E,F), ...).
Cause: A column name used in a join exists in more than one table and is thus referenced ambiguously. In a join, any column name that occurs in more than one of the tables must be prefixed by its table name when referenced. The column should be referenced as TABLE.COLUMN or TABLE_ALIAS.COLUMN. For example, if tables EMP and DEPT are being joined and both contain the column DEPTNO, then all references to DEPTNO should be prefixed with the table name, as in EMP.DEPTNO or E.DEPTNO.
Action: Prefix references to column names that exist in multiple tables with either the table name or a table alias and a period (.), as in the examples above.
Cause: An entry was formatted like a function call, but it is not recognizable as an Oracle function.
Cause: A search condition was entered with an invalid or missing relational operator.
Action: Include a valid relational operator such as =, !=, ^=, <>, >, <, >=, <=, ALL, ANY, [NOT] BETWEEN, EXISTS, [NOT] IN, IS [NOT] NULL, or [NOT] LIKE in the condition.
Cause: The SQL command was not complete. Part of a valid command was entered, but at least one major component was omitted.
Cause: An invalid option was specified in defining a column or storage clause. The valid option in specifying a column is NOT NULL to specify that the column cannot contain any NULL values. Only constraints may follow the datatype. Specifying a maximum length on a DATE or LONG datatype also causes this error.
Action: Correct the syntax. Remove the erroneous option or length specification from the column or storage specification.
Cause: In a SELECT or REVOKE statement, the keyword FROM was either missing, misplaced, or misspelled. The keyword FROM must follow the last selected item in a SELECT statement or the privileges in a REVOKE statement.
Action: Correct the syntax. Insert the keyword FROM where appropriate. The SELECT list itself also may be in error. If quotation marks were used in an alias, check that double quotation marks enclose the alias. Also, check to see if a reserved word was used as an alias.
Cause: The keyword BY was omitted in a GROUP BY, ORDER BY, or CONNECT BY clause. In a GRANT statement, the keyword IDENTIFIED must also be followed by the keyword BY.
Action: Correct the syntax. Insert the keyword BY where required and then retry the statement.
Cause: An INSERT statement has been entered without the keyword INTO.
Action: Correct the syntax. Insert the keyword INTO where required and then retry the statement.
Cause: An INSERT statement has been entered without the keyword VALUES or SELECT. Either a VALUES clause or a SELECT subquery must follow the INSERT INTO clause.
Action: Correct the syntax. Enter either a VALUES clause or a subquery after the INSERT INTO clause.
Cause: An equal sign has been omitted in one of the following places:
Action: Correct the syntax. Insert the equal sign where required and retry the statement.
Cause: A SELECT subquery must be included in a CREATE VIEW statement.
Action: Correct the syntax. Insert the required SELECT clause after the CREATE VIEW clause and then retry the statement.
Cause: This is an internal error message not usually issued.
Action: Contact customer support.
Cause: This is an internal error message not usually issued.
Action: Contact customer support.
Cause: This is an internal error message not usually issued.
Action: Contact customer support.
Cause: Either
Action: If the cause is
Cause: The SQL statement ends with an inappropriate clause. For example, an ORDER BY clause may have been included in a CREATE VIEW or INSERT statement. ORDER BY cannot be used to create an ordered view or to insert in a certain order. Also, an improper SQL ending occurs if IN clause is used with only one argument (IN(X), for example). An IN clause must have two or more arguments.
Action: Correct the syntax by removing the inappropriate clauses. It may be possible to duplicate the removed clause with another SQL statement. For example, to order the rows of a view, do so when querying the view and not when creating it. This error can also occur in SQL*Forms applications if a continuation line is indented. Check for indented lines and delete these spaces.
Cause: One of the group functions, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used in a WHERE or GROUP BY clause.
Action: Remove the group function from the WHERE or GROUP BY clause. The desired result may be achieved by including the function in a subquery or HAVING clause.
Cause: This is an internal error message not usually issued.
Action: Contact customer support.
Cause: A required part of a clause or expression has been omitted. For example, a SELECT statement may have been entered without a list of columns or expressions or with an incomplete expression. This message is also issued in cases where a reserved word is misused, as in SELECT TABLE.
Action: Check the statement syntax and specify the missing component.
Cause: A SELECT list cannot include both a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, and an individual column expression, unless the individual column expression is included in a GROUP BY clause.
Action: Drop either the group function or the individual column expression from the SELECT list or add a GROUP BY clause that includes all individual column expressions listed.
Cause: The function was referenced with too few arguments.
Action: Check the function syntax and specify the required number of arguments.
Cause: The function was referenced with too many arguments.
Action: Check the function syntax and specify only the required number of arguments.
Cause: An invalid ALTER option was specified.
Cause: The cluster name was either missing or invalid.
Action: Specify a valid cluster name. A valid cluster name must start with a letter, be less than or equal to 30 characters, and contain only alphanumeric characters or the special characters $, _, and #. It may not be a reserved word. The name must be specified immediately following the keywords CREATE CLUSTER.
Cause: The table or view entered does not exist, a synonym that is not allowed here was used, or a view was referenced where a table is required. Existing user tables and views can be listed by querying the data dictionary. Certain privileges may be required to access the table. If an application returned this message, the table the application tried to access does not exist in the database, or the application does not have access to it.
Action: Check each of the following:
Contact the database administrator if the table needs to be created or if user or application privileges are required to access the table.
Also, if attempting to access a table or view in another schema, make certain the correct schema is referenced and that access to the object is granted.
Cause: The current user owns no cluster by the specified name.
Action: Specify a valid cluster name following the keyword CLUSTER, then retry the statement.
Cause: An attempt was made to create a table with fewer cluster columns than were specified in the CREATE CLUSTER statement. The CLUSTER clause of a CREATE TABLE statement must specify all cluster columns that were defined when the cluster was created.
Action: Specify all cluster columns in the CREATE TABLE statement, then retry it.
Cause: A column specified in the cluster clause of a CREATE TABLE statement is not a column in this table.
Action: Re-execute the statement, using the names of columns defined for the table.
Cause: A GRANT statement was specified without the keyword TO, or an invalid form of the GRANT command was entered.
Action: Check the syntax for the GRANT command, insert the keyword TO where required, and retry the statement.
Cause: This error occurs when a SQL statement requires two sets of values equal in number, but the second set contains fewer items than the first set. This can occur in a WHERE or HAVING clause in which a nested SELECT returns too few columns as in:
WHERE (A,B) IN (SELECT C FROM ...)
Another common cause of this error is an INSERT statement in which the VALUES or SELECT clause does not contain enough values needed for the INSERT, as in
INSERT INTO EMP(EMPNO,ENAME) VALUES('JONES')
Action: Check the number of items in each set and change the SQL statement to make them equal.
Cause: The ALTER CLUSTER statement has been withdrawn.
Action: To add data to a cluster from an existing table, use the following series of SQL statements:
CREATE TABLE newtable SELECT * FROM oldtable CLUSTER clustername; DROP oldtable; RENAME TABLE newtable oldtable;
Cause: This is an internal error message not usually issued.
Action: Contact customer support.
Cause: A DROP command was not followed by a valid DROP option, such as CLUSTER, DATABASE LINK, INDEX, ROLLBACK SEGMENT, SEQUENCE, SYNONYM, TABLE, TABLESPACE, or VIEW.
Action: Check the command syntax, specify a valid DROP option, then retry the statement.
Cause: A DROP CLUSTER statement specified a cluster that is not empty. A cluster may not be dropped if it contains any tables, unless the optional INCLUDING TABLES clause is specified. Tables may also be removed from a cluster by using the DROP TABLE command.
Action: Either specify the INCLUDING TABLES clause in the DROP CLUSTER statement or remove all tables from the cluster with the DROP TABLE command before issuing the DROP CLUSTER command.
Cause: Groups are not currently implemented.
Action: No user action required.
Cause: In a CREATE INDEX, DROP INDEX, or VALIDATE INDEX statement, the index name was missing or invalid.
Action: Specify a valid index name after the keyword INDEX. To drop or validate an existing index, check the name by querying the data dictionary. To create a new index, check the syntax before retrying.
Cause: A GRANT CONNECT statement was issued without the keyword IDENTIFIED.
Action: Check the syntax and insert the keyword IDENTIFIED after the last username. The format is
GRANT CONNECT TO user-list IDENTIFIED BY password-list;
Cause: An attempt was made to create a database object (such as a table, view, cluster, index, or synonym) that already exists. A user's database objects must have distinct names.
Action: Enter a unique name for the database object or modify or drop the existing object so it can be reused.
Cause: An AUDIT or NOAUDIT command was not followed by a valid option or the keyword ALL. For example, when AUDITing tables an option such as ALTER, AUDIT, COMMENT, DELETE, GRANT, INDEX, INSERT, LOCK, RENAME, SELECT, or UPDATE must be specified.
Cause: A column name was specified twice in a CREATE or INSERT statement. Column names must be unique within a table, view, or cluster.
Action: In a CREATE statement, change one of the column names to a new, unique column name. In an INSERT statement, remove one of the duplicate names.
Cause: The keyword CHECK should follow the keyword WITH in the WITH OPTION clause of the CREATE VIEW statement.
Action: Check the statement syntax and insert the keyword CHECK where required. Then retry the statement.
Cause: A statement specified the name of a tablespace that does not exist.
Action: Enter the name of an existing tablespace. For a list of tablespace names, query the data dictionary. If a tablespace is dropped and re-created with the same name, use ALTER USER to reset the default or temporary tablespace name, because the new tablespace is not the same as the dropped tablespace, even though they have the same name.
Cause: A column name in the order-by list matches more than one select list column.
Action: Remove the duplicate column naming in the select list.
Cause: The group-by or order-by column list contains more than 255 expressions.
Action: Use no more than 255 expressions in the group-by or order-by list.
Cause: A table specified in a query's SELECT list is not named in the FROM clause list.
Action: Check spelling of the table names, check that each table name in the SELECT list matches a table name in the FROM list, and then retry the statement.
Cause: An alias was used with the return-all-columns function (*) in the SELECT list. For example:
SELECT * COL_ALIAS FROM EMP;
Action: Either specify individual columns or do not specify an alias with a "*".
Cause: A LOCK statement was specified and the keyword TABLE was missing, misspelled, or misplaced. A LOCK statement must begin with LOCK TABLE tablename.
Cause: The keyword WHERE in a SELECT statement was missing, misspelled, or misplaced.
Cause: The keyword INDEX in a CREATE UNIQUE INDEX or VALIDATE INDEX statement was missing, misspelled, or misplaced.
Cause: The keyword ON in a GRANT, REVOKE, or CREATE INDEX statement was missing, misspelled, or misplaced.
Action: Check syntax and spelling, and use the keyword ON where required.
Cause: The keyword START was specified without the keyword WITH. Both keywords are necessary if a START WITH clause is desired in a tree-structured query.
Action: Change the keyword START to the keywords START WITH. Then retry the statement.
Cause: The keyword SET in an UPDATE statement is missing, misspelled, or misplaced.
Action: Check syntax and spelling, and use the keyword SET after the name of the table to be updated.
Cause: The name of a schema object exceeds 30 characters. Schema objects are tables, clusters, views, indexes, synonyms, tablespaces, and usernames.
Action: Shorten the name to 30 characters or less.
Cause: The percentage of free space specified in a CREATE INDEX statement is not between 0 and 100. A PCTFREE value of 0 means the entire block is available. The value 100 is not useful because it means that no data may be inserted. The default is 10.
Action: Specify a PCTFREE value between 0 and 100. Then retry the statement.
Cause: An attempt was made to add two date fields together. Dates may be added only to numeric fields, not to other dates.
Action: Use the Oracle function TO_NUMBER to convert one of the date fields to a numeric field before adding it to the other date field.
Cause: The use of the PRIOR clause, the pseudo-column LEVEL, or ROWNUM is incorrect in this context.
Action: Check the syntax for the SQL statement. Then remove or relocate the keyword PRIOR, LEVEL, or ROWNUM.
Cause: An AUDIT or NOAUDIT statement specified the same option more than once.
Action: Either specify ALL without other auditing options or remove the duplicate auditing specifications.
Cause: A group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, was used within another group function, as in MAX(COUNT(*)), without a corresponding GROUP BY clause.
Action: Either add a GROUP BY clause or remove the extra level of nesting.
Cause: The GROUP BY clause does not contain all the expressions in the SELECT clause. SELECT expressions that are not included in a group function, such as AVG, COUNT, MAX, MIN, SUM, STDDEV, or VARIANCE, must be listed in the GROUP BY clause.
Action: Include in the GROUP BY clause all SELECT expressions that are not group function arguments.
Cause: The synonym used is based on a table, view, or synonym that no longer exists.
Action: Replace the synonym with the name of the object it references or re-create the synonym so that it refers to a valid table, view, or synonym.
Cause: Both table-wide and system-wide options were specified within a single AUDIT statement.
Action: Check the AUDIT command syntax. Then retry one or more AUDIT statements.
Cause: A left parenthesis appeared in a join condition, but a plus sign (+) did not follow. A left parenthesis in a join condition usually signals an outer-join specification and so a plus sign is expected to follow. To specify an outer join on a column in a join operation, follow the column reference in the join condition with a plus sign (+) enclosed in parentheses.
Action: Correct the SQL syntax and retry the statement.
Cause: A column name was used in an expression where it is not permitted, such as in the VALUES clause of an INSERT statement.
Action: Check the syntax of the statement and use column names only where appropriate.
Cause: Probably a syntax error.
Cause: Probably a syntax error.
Cause: No username was specified in a GRANT statement or one of the specified usernames is invalid. Valid usernames must be specified following the keyword TO in a GRANT statement to define a user. A username must begin with a letter, consist only of alphanumeric characters and the special characters $, _, and #, and be less than or equal to 30 characters. If it contains other characters, it must be enclosed in double quotation marks. It may not be a reserved word.
Action: Specify a valid username, or list of usernames, following the keyword TO in the GRANT statement.
Cause: More usernames than passwords were specified in a GRANT statement. A valid password must be specified for each username listed in the GRANT statement.
Action: Enter a valid password for each username.
Cause: More passwords than usernames were specified in a GRANT statement. Only one password may be entered for each username listed in the GRANT statement.
Action: Enter an equal number of usernames and passwords.
Cause: No privileges were specified in a GRANT privilege statement, or one of the specified privileges is invalid.
Action: Enter one or more valid privileges such as SELECT, INSERT, DELETE, UPDATE, ALTER, INDEX, REFERENCES, or ALL. More than one privilege may be granted by entering the privileges in a list separated by commas (,) or by specifying the keyword ALL to grant all privileges.
Cause: An invalid form of the REVOKE command was entered. There are two forms of the REVOKE command. The first form is used to revoke a user's database access privileges. The second form is used to revoke a user's object privileges.
Action: Check the command syntax and retry the statement.
Cause: The keyword WITH was specified at the end of a GRANT statement without the keyword GRANT. To grant privileges to a user and the permission to grant those privileges to another user, you must specify the keywords WITH GRANT OPTION at the end of the GRANT statement.
Action: Change the keyword WITH to the keywords WITH GRANT OPTION, then retry the statement.
Cause: The keywords WITH GRANT were specified at the end of a GRANT statement without the keyword OPTION.
Action: Change the keywords WITH GRANT to the keywords WITH GRANT OPTION. Then retry the statement.
Cause: In a CREATE or DROP SYNONYM statement, the synonym name was either missing or invalid.
Action: Check syntax and spelling. A valid synonym name must be specified immediately following the keyword SYNONYM in both statements. Valid synonym names must begin with a letter, consist of alphanumeric characters and the special characters $, _, and #, and be less than or equal to 30 characters. They may not be reserved words.
Cause: A single bar (|) was interpreted as an attempt to specify concatenation, but the concatenation operator is a double bar (||).
Action: Enter a double bar (||) for concatenation or remove the single bar (|) if concatenation was not intended.
Cause: A value of datatype LONG was used in a function or in a DISTINCT, WHERE, CONNECT BY, GROUP BY, or ORDER BY clause. A LONG value can only be used in a SELECT clause.
Action: Remove the LONG value from the function or clause.
Cause: An expression or function was used in a CREATE VIEW statement, but no corresponding column name was specified. When expressions or functions are used in a view, all column names for the view must be explicitly specified in the CREATE VIEW statement.
Action: Enter a column name for each column in the view in parentheses after the view name.
Cause: In a CREATE VIEW statement, the view name was missing or invalid.
Action: Enter a valid view name following CREATE VIEW. Valid view names must begin with a letter, consist of only alphanumeric characters and the special characters $, _, and #, be less than or equal to 30 characters, and may not be reserved words. If the view name contains other characters, it must be enclosed in double quotation marks.
|
 Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|
