Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
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.
Action: Correct the syntax.
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, then 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.
Action: Correct the syntax.
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 Oracle Support Services.
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), ...).
Action: Correct the syntax.
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.
Action: Correct the syntax.
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.
Action: Correct the syntax.
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 Oracle Support Services.
Cause: This is an internal error message not usually issued.
Action: Contact Oracle Support Services.
Cause: The specified string does not contain an identifier.
Action: Correct the string argument.
Cause: One of the following:
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.
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 Oracle Support Services.
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.
Action: Correct the syntax.
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 Oracle Support Services.
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.
Action: Correct the syntax.
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.
Cause: A column name in the order-by list matches more than one select list columns.
Action: Remove duplicate column naming in select list.
Cause: The group-by or order-by column list contain more than 1000 expressions.
Action: Use no more than 1000 expressions in the group-by or order-by list.
Cause: An unsupported interval type was encountered.
Action: Use a valid interval type.
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.
Action: Correct the syntax.
Cause: The keyword WHERE in a SELECT statement was missing, misspelled, or misplaced.
Action: Correct the syntax.
Cause: The keyword INDEX in a CREATE UNIQUE INDEX or VALIDATE INDEX statement was missing, misspelled, or misplaced.
Action: Correct the syntax.
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.
Action: Correct syntax.
Cause: Probably a syntax error.
Action: Correct syntax.
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: Object privileges or non-MAC system privileges were granted to the procedure.
Action: Only grant MAC privileges using the PROCEDURE clause.
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.
Cause: A host language program attempted to open too many cursors. The initialization parameter OPEN_CURSORS determines the maximum number of cursors per user.
Action: Modify the program to use fewer cursors. If this error occurs often, shut down Oracle, increase the value of OPEN_CURSORS, and then restart Oracle.
Cause: Either a host language program call specified an invalid cursor or the value of the MAXOPENCURSORS option in the precompiler command were too small. All cursors must be opened using the OOPEN call before being referenced in any of the following calls: SQL, DESCRIBE, NAME, DEFINE, BIND, EXEC, FETCH, and CLOSE. The Logon Data Area (LDA) must be defined by using OLON or OLOGON. If the LDA is not defined, this message is issued for the following calls: OPEN, COM, CON, ROL, and LOGOFF.
Action: Check the erroneous call statement. Specify a correct LDA area or open the cursor as required. If there is no problem with the cursor, it may be necessary to increase the MAXOPENCURSORS option value before precompiling.
Cause: In a host language program, a FETCH call was issued out of sequence. A successful parse-and-execute call must be issued before a fetch. This can occur if an attempt was made to FETCH from an active set after all records have been fetched. This may be caused by fetching from a SELECT FOR UPDATE cursor after a commit. A PL/SQL cursor loop implicitly does fetches and may also cause this error.
Action: Parse and execute a SQL statement before attempting to fetch the data.
Cause: A host language program call referenced a cursor with no associated parsed SQL statement. A SQL call (for example, OSQL3) must be used to pass a SQL statement to Oracle and to associate the statement with an open cursor. A cursor must already have an associated SQL statement if referenced in any of the following calls: DESCRIBE, NAME, DEFINE, BIND, EXECUTE, and FETCH.
Action: Do the SQL call, for example, OSQL, to pass the required SQL statement before referencing the cursor.
Cause: An attempt was made to use automatic logon on a system not supporting this feature.
Action: Provide the complete username and password to log on to Oracle.
Cause: An invalid password was given when logging on.
Action: Provide a valid password.
Cause: A program issued a BIND call for a variable not listed in the associated SQL statement. Only those variables prefixed by either a colon (:) or ampersand (&) in the SQL statement may be referenced in a BIND call, OBIND or OBINDN. This error may also be caused by a mismatch between a Precompiler program and the related library, SQLLIB.
Action: Modify the BIND call to reference one of the substitute variables specified in the associated SQL statement.
Cause: A reference was made to a variable not listed in the SELECT clause. In OCI, this can occur if the number passed for the position parameter is less than one or greater than the number of variables in the SELECT clause in any of the following calls: DESCRIBE, NAME, or DEFINE. In SQL*Forms or SQL*Report, specifying more variables in an INTO clause than in the SELECT clause also causes this error.
Action: Determine which of the problems listed caused the problem and take appropriate action.
Cause: A SQL statement containing substitution variables was executed without all variables bound. All substitution variables must have a substituted value before the SQL statement is executed.
Action: In OCI, use an OBIND or OBINDN call to substitute the required values.
Cause: A host language program call did not pass all required parameters.
Action: Check the syntax for the call and enter all required parameters.
Cause: One of the following:
DBLINK_ENCRYPT_LOGIN initialization parameter is set to TRUE, and you attempted to use a database link pointing to a release 7.0 (or lower) Oracle database server.Action: For the above causes:
DBLINK_ENCRYPT_LOGIN to FALSE. If you wish to use encrypted database links, then you must upgrade all Oracle database servers to release 7.1 (or higher).Cause: An attempt was made to use Oracle7 compatibility mode when accessing Oracle version 6.
Action: Use V6 SQL language type. You may need to use the SET COMPATIBILITY V6 command.
Cause: A host language program issued an Oracle call, other than OLON or OLOGON, without being logged on to Oracle. This can occur when a user process attempts to access the database after the instance it is connected to terminates, forcing the process to disconnect.
Action: Log on to Oracle, by calling OLON or OLOGON, before issuing any Oracle calls. When the instance has been restarted, retry the action.
Cause: The user interrupted an Oracle operation by entering CTRL-C, Control-C, or another canceling operation. This forces the current operation to end. This is an informational message only.
Action: Continue with the next operation.
Cause: A user tried to log on to Oracle while an instance shutdown was in progress. Oracle logons are disabled while Oracle is being shut down.
Action: Wait until Oracle is brought back up before attempting to log on.
Cause: This is an internal error message not usually issued.
Action: Contact Oracle Support Services.
Cause: The cursor is in an invalid state.
Action: Ensure the appropriate OCI/UPI function is called after the fetch and before the offending function.
Cause: An invalid username or password was entered in an attempt to log on to Oracle. The username and password must be the same as was specified in a GRANT CONNECT statement. If the username and password are entered together, the format is: username/password.
Action: Enter a valid username and password combination in the correct format.
Cause: An attempt was made to fetch data using the LONG fetch option, but the specified column was not LONG.
Action: Re-execute the fetch without the LONG fetch option or create the table with a LONG column.
Cause: The user side memory allocator returned an error.
Action: Increase the size of the process heap or switch to the old set of calls.
Cause: This is an internal error message not usually issued.
Action: Contact Oracle Support Services.
Cause: This is an internal error message not usually issued.
Action: Contact Oracle Support Services.
Cause: The attempted database operation does not conform to the user programming interface (UPI) for the two communicating Oracle servers.
Action: You may need to upgrade one or more of your Oracle servers or re-link your user side application with new libraries. Report the problem to Oracle Support Services.
Cause: The cursor number is not a valid open cursor.
Action: Make sure that the cursor is open.
Cause: An OCI program call specified an invalid datatype. In OCI calls, Oracle datatypes are specified as numbers between 1 and 7.
Action: Check the datatype description and enter the correct number for the datatype.
Cause: An integer parameter to a UPI function is out of range.
Action: This usually indicates an error in a tool built on top of the Oracle DBMS. Report the error to Oracle Support Services.
Cause: More than one long buffer in the bind list.
Action: Change the buffer size to be less than 4000 for the bind variable bound to a normal column.
Cause: An attempt was made to use a bind variable in a SQL data definition operation.
Action: Such bind variables are not allowed.
Cause: Received send long message but do not have the cursor context.
Action: Contact Oracle Support Services.
Cause: Received a request to send the long again when there is no long
Action: Contact Oracle Support Services.
Cause: The SELECT... INTO specified in the bind call does not correspond to a variable in the SQL statement.
Action: If it is not possible to correct the statement, then contact Oracle Support Services.
Cause: An attempt was made to change the current username or password without the appropriate privilege. This error also occurs if attempting to install a database without the necessary operating system privileges.
Action: Ask the database administrator to perform the operation or grant the required privileges.
Cause: This is an internal error message related to Export/Import.
Action: Contact Oracle Support Services.
Cause: An attempt was made to log on while Oracle is being started or shut down.
Action: Wait a few minutes. Then retry the operation.
Cause: Oracle was not started. Possible causes include the following:
Action: Refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. If Oracle has been initialized, then on some operating systems, verify that Oracle was linked correctly. See the platform-specific Oracle documentation.
Cause: Logins are disallowed because an instance started in restricted mode. Only users with RESTRICTED SESSION system privilege can log on.
Action: Request that Oracle be restarted without the restricted option or obtain the RESTRICTED SESSION system privilege.
Cause: Unable to find bind context on user side.
Action: Make sure that the variable being bound is in the SQL statement.
Cause: An attempt was made to process a complex SQL statement which consumed all available memory of the cursor.
Action: Simplify the complex SQL statement. Alternatively, you can use the NO_EXPAND hint which prevents the cost-based optimizer from considering OR-expansion for queries having OR conditions or INLISTS in the WHERE clause. Usually, the optimizer considers using OR expansion and uses this method if it decides the cost is lower than not using it. Refer to the Oracle9i Database Performance Tuning Guide and Reference for information about using hints.
Cause: An attempt was made to write datafile headers in an old format. The new format cannot be used until after the database has been verified as being compatible with this software version.
Action: Open the database to advance to the new file formats, then repeat the operation. If the operation is required before the database can be opened, then use the previous software release to do the operation.
Cause: An attempt was made to explain plan on other people's view without the necessary privileges on the underlying objects of the view.
Action: Get necessary privileges or do not perform the offending operation.
Cause: There are multibyte characters in the password or some characters in the password are not in US7ASCII range.
Action: Resubmit the password with valid characters.
Cause: Pointer to HSTDEF extension in HSTDEF is null.
Action: Contact Oracle Support Services.
Cause: An attempt was made to detach a session which had open cursors.
Action: Close all the cursors before detaching the session.
Cause: The application code corrupted some of the user memory used by Oracle.
Action: Make sure that the application code is not overwriting memory.
Cause: An attempt was made to bind a buffer whose total size would exceed the maximum size allowed. Total array size for arrays is calculated as:
(element_size)*(number of elements)
Action: Reduce the buffer size.
Cause: A connect was attempted to a userid which does not have create session privilege.
Action: Grant the user CREATE SESSION privilege.
Cause: Oracle could not extend the current area any further because the operating system would not supply any more space. A system-specific message should appear following this message.
Action: Close some cursors and try again or check operating system quotas to use more virtual memory. See your operating system-specific Oracle documentation.
Cause: This message is displayed after a previous message to provide more specific information.
Action: See the cause and action for the previous message.
Cause: The procedure user specified in deferred RPC does not exist.
Action: Check to make sure that the procedure exists and is visible to the replication process.
Cause: This error occurs when a newer server version requests from an older server version an operation that is not supported.
Action: You may need to upgrade one or more of your Oracle servers or relink your user application with new libraries.
Cause: Oracle could not open a new context area because the operating system would not supply any more space. A system-specific message should appear following this message.
Action: Close some cursors and try again or check operating system quotas to use more virtual memory. See your operating system-specific Oracle documentation.
Cause: The deferred RPC data in SYS.DEF$_CALL is corrupted.
Action: Contact Oracle Support Services.
Cause: A valid destination for parameter LOG_ARCHIVE_DUPLEX_DEST was not specified when parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was set to 2.
Action: Either specify a value for parameter LOG_ARCHIVE_DUPLEX_DEST, or reduce the value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to 1.
Cause: A bind variable or other user area could not be read by Oracle.
Action: Check that binds are done correctly on valid user buffers, then retry the operation.
Cause: A define, FETCH... INTO or SELECT... INTO, variable or other user area could not be written to by Oracle.
Action: Check that INTO variables and indicators are correctly specified. Then retry the operation.
Cause: The reference to a block.field identifier in a user exit is incorrect or ambiguous, probably because it is misspelled or incomplete.
Action: Check syntax and identifier spelling. Then correct the reference.
Cause: Attempt to delete non-existent HSTDEF extension.
Action: Contact Oracle Support Services.
Cause: The client application attempted to bind a variable or execute a cursor opened in a PL/SQL block before the statement was parsed.
Action: Ensure the statement is parsed before a bind or execute.
Cause: The client application attempted to bind an array of cursors or attempted to repeatedly execute against a PL/SQL block with a bind variable of type cursor.
Action: Bind a single cursor or execute the PL/SQL block once.
Cause: You are using an Oracle client application linked with version 7 (or lower) libraries and you attempted to start up a V8 (or higher) server.
Action: Use a client application linked with V8 (or higher) libraries.
Cause: Exceeded the maximum buffer size for current platform.
Action: Use piecewise fetch with a smaller buffer size.
Cause: An attempt was made to run an older, obsolete Oracle Server.
Action: Upgrade the server.
Cause: An attempt was made to perform an operation before Oracle was started.
Action: Start Oracle. Then retry the operation.
Cause: An attempt was made to stop Oracle, but Oracle was not running.
Action: No action required.
Cause: An illegal internal operation was attempted.
Action: Contact Oracle Support Services.
Cause: An attempt was made to shut down Oracle inside a logon session.
Action: Log off before shutting down Oracle.
Cause: An attempt was made to log on while already logged on.
Action: No action required.
Cause: Oracle does not support multiple logons per process.
Action: No action required.
Cause: A failure occurred during initialization of the background processes.
Action: Refer to the diagnostic information in the accompanying message stack or in the trace file and take appropriate action.
Cause: Failure during processing of initialization parameters during system startup.
Action: Further diagnostic information should be in the error stack.
Cause: There was an error when the database or control file was created.
Action: Check what error was signaled when the database was first created or when the control file was re-created. Take appropriate actions to re-create the database or a new control file.
Cause: A failure occurred during system shutdown.
Action: Refer to the diagnostic information in the accompanying message stack and take appropriate action.
Cause: An attempt was made to start Oracle while it was already running.
Action: Shut down Oracle first, if you want to restart it.
Cause: "row_locking = always" is specified in the INIT.ORA file. This feature is not supported by ORACLE without the transaction processing option.
Action: Remove it from INIT.ORA file or set it to "default" or "intent".
Cause: The value of the given initialization parameter is required to be the same for all instances in the cluster database configuration.
Action: Change the value of the initialization parameter in the initialization parameter file to match that of other cluster database instances.
Cause: The failing OCI call contains an argument with an invalid value.
Action: Use valid argument values. For more information, see the Oracle Call Interface Programmer's Guide and the appropriate programming language supplement.
Cause: Errors were encountered when the named procedure was executed as a deferred remote procedure call.
Action: Correct the cause of the preceding errors.
Cause: An attempt was made to roll back to a savepoint that was never established.
Action: No action is required.
Cause: An attempt was made to start up Oracle by a user who is currently logged on.
Action: Log off. Then issue the STARTUP command.
Cause: Users are still logged into the instance.
Action: Either wait for all users to logoff or use SHUTDOWN IMMEDIATE.
Cause: The SHUTDOWN IMMEDIATE command was used to shut down a running Oracle instance, terminating any active operations.
Action: Wait for the instance to be restarted or contact the database administrator.
Cause: The SHUTDOWN command was used to shut down a running Oracle instance, disallowing any connects to Oracle.
Action: Wait for the instance to restart or contact the database administrator.
Cause: Unable to destroy the old SGA.
Action: Manually remove the old SGA. See your operating system-specific Oracle documentation for instructions. Then retry the STARTUP command.
Cause: The instance connected to was terminated abnormally, probably due to a SHUTDOWN ABORT. The current process was forced to disconnect from the instance.
Action: Examine the alert log for more details. Contact the database administrator to determine when the instance is restarted. Attempt to reconnect after the instance is running again.
Cause: There is at least one more session, other than the current one, logged in to the instance. ALTER DATABASE CLOSE is not permitted when other sessions are active.
Action: Find the other sessions and disconnect them. Then reissue the ALTER DATABASE CLOSE statement. Also, issue the SHUTDOWN IMMEDIATE command to force users off the system, or issue the SHUTDOWN ABORT command to shut down the database without waiting for users to be forced off.
Cause: An attempt was made to connect while the database is being closed with the ALTER DATABASE CLOSE statement.
Action: Attempt to connect again when the database is open. Contact the database administrator to find out when the database will be open.
Cause: A DML cursor from the OTEX() call processed 0 rows when executed.
Action: Caller can either do a rollback or ignore the message and execute the rest of the cursors in the cursor array.
Cause: The program was linked with a different version of the server than the instance to which it is attempting to connect.
Action: Relink the program against the same version of Oracle as the instance or restart (startup force) the database using the program's version of the SERVER.
Cause: An attempt was made to shut down the database while a transaction was in progress.
Action: Either commit or rollback the current transaction and then attempt to shut down the database.
Cause: The application program interface could not insert or update a LONG column because of an internal error when a TTCGETV call fails. For example, a network read error or one of the parameters passed to the call is invalid.
Action: Retry the insert or update.
Cause: An attempt was made to mount a database in parallel mode with the initialization parameter SINGLE_PROCESS set to TRUE.
Action: Either mount the database in EXCLUSIVE mode or set the initialization parameter SINGLE_PROCESS to FALSE before starting the instance in parallel (shared) mode.
Cause: An attempt was made to mount a database with the name of a currently mounted database.
Action: No action is required.
Cause: Some other instance has the database of same name currently mounted and you are trying to create it.
Action: Either change the database name or shut down the other instance.
Cause: Some other instance has the database mounted exclusive or shared.
Action: Shut down the other instance or mount in a compatible mode.
Cause: The database name in the control file does not match your database name.
Action: Either find the correct control file or change your database name.
Cause: The number of control files used by this instance disagrees with the number of control files in an existing instance.
Action: Check to make sure that all control files are listed.
Cause: An attempt to mount the database discovered that another instance mounted a database by the same name, but the mount is not compatible. Additional errors are reported explaining why.
Action: See accompanying errors.
Cause: An attempt was made to dismount a database before it was closed.
Action: Close the database, then retry the operation.
Cause: An attempt to perform media recovery was made but the database is not mounted.
Action: Mount the database.
Cause: Either media recovery is actively being applied to the file, or it is being backed up while the database is in NOARCHIVELOG mode. It cannot be used for normal database access or crash recovery.
Action: Complete or cancel the media recovery session or backup.
Cause: A command was attempted that requires the database to be open.
Action: Open the database and try the command again.
Cause: This message reports the file name involved with other messages.
Action: See the associated messages for a description of the problem.
Cause: The datafile was missing from a CREATE CONTROLFILE command or BACKUP CONTROLFILE RECOVERY was done with a control file that was saved before the file was created.
Action: Rename the MISSING file to the name of the real file.
Cause: An attempt to continue media recovery is being made but media recovery was not started.
Action: No action is required.
Cause: An attempt was made to open a datafile that is in need of media recovery.
Action: First apply media recovery to the datafile identified in the message, then retry the operation.
Cause: The device on which the file resides is probably offline. If the file is a temporary file, then it is also possible that the device has run out of space. This could happen because disk space of temporary files is not necessarily allocated at file creation time.
Action: Restore access to the device or remove unnecessary files to free up space.
Cause: The device on which the file resides is probably off line.
Action: Restore access to the device, then retry the operation.
Cause: Usually the file is not accessible.
Action: Make sure the datafile is in the expected location and can be accessed properly, then retry the operation.
Cause: An attempt was made to add a datafile with a block size that is greater than the maximum block size allowed.
Action: Retry the operation with a smaller block size.
Cause: An attempt to add a datafile failed because the limit for such files had already been reached.
Action: If more database space is required, export the database and re-create it with a higher limit for datafiles and perhaps increased file size.
Cause: Insufficient space on device.
Action: Decrease the size of the requested file or allocate a file on another device with more available space. If a file size was not specified in the statement, then specify a file size smaller than the available space on the device.
Cause: An attempt was made to drop a datafile when it is online.
Action: Take file offline before dropping.
Cause: An attempt was made to use ALTER DATABASE RENAME to rename a datafile that is online in an open instance or is being recovered.
Action: Close database in all instances and end all recovery sessions.
Cause: The information in this file is inconsistent with information from the control file. See accompanying message for reason.
Action: Make certain that the database files and control files are the correct files for this database.
Cause: An attempt to start backup of an online tablespace failed because media recovery is not enabled.
Action: Enable media recovery and retry this operation.
Cause: An attempt to do media recovery found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is currently doing media recovery on the file.
Action: Do not do media recovery.
Cause: An attempt to disable media recovery found that an online backup is still in progress.
Action: End the backup of the offending tablespace and retry this command.
Cause: An operation failed because the database was not mounted in exclusive mode.
Action: Shut down Oracle and mount the database in exclusive mode.
Cause: The specified database name is too long.
Action: Shorten the database name to eight characters or fewer, then retry the operation.
Cause: An attempt to start an online backup found that one of the files is offline.
Action: Bring the offending files online and retry this command or do a cold backup.
Cause: The user's default or temporary tablespace was dropped.
Action: Reassign the default or temporary tablespace.
Cause: The named datafile was created under an incompatible version of Oracle, or the file is invalid or non-existent.
Action: Shut down and restart the correct version of Oracle or check the references to the datafile and make sure it exists.
Cause: The specified value of the initialization parameter DB_FILES is too large.
Action: Reduce the value of the DB_FILES parameter and retry the operation.
Cause: The specified datafile name is too long.
Action: Shorten the file name and retry the operation.
Cause: The specified redo log file name is too long.
Action: Shorten the file name and retry the operation.
Cause: An attempt to access a database failed because it is mounted in exclusive mode by another instance.
Action: Either shut down the other instance or wait for the other instance to either close the database or mount it in parallel mode, before retrying the operation.
Cause: An attempt was made to access a datafile that is offline.
Action: Bring the datafile back online.
Cause: A file size was specified in the AS clause of the ALTER DATABASE CREATE DATAFILE statement, and the size was smaller than the size needed.
Action: Create the file with a larger size.
Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline.
Action: Wait for the other instance to release the lock on the file.
Cause: The requested operation cannot be done when the database is mounted but not open in this instance, and another instance has the database open.
Action: Execute the operation in an open instance, open the database in this instance, or close the database in the other instances.
Cause: The RESETLOGS option was given in ALTER DATABASE OPEN, but there has been no incomplete recovery session.
Action: Reissue the ALTER DATABASE OPEN statement without specifying '.
Cause: All the files were found to be offline when attempting to end an online backup.
Action: No action required. Online backup does not need to be ended for this tablespace.
Cause: An attempt to change a datafile's name in the control file failed because no file was found with the new name.
Action: Make sure that the datafile has been properly renamed by the operating system and retry.
Cause: None of the files were found to be in online backup when attempting to end an online backup.
Action: No action required. Online backup does not need to be ended for this tablespace.
Cause: An attempt to disable media recovery found a file that needs media recovery, thus media recovery cannot be disabled.
Action: Recover the offending file or drop the tablespace it belongs to and retry this command.
Cause: Specified file size is larger than maximum allowable size value.
Action: Specify a smaller size.
Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if the database is in ARCHIVELOG mode.
Action: Take the tablespace offline as usual or do a shutdown abort before attempting the required operation. It is worthwhile reconsidering the backup strategy for the database. The attempted operations can be done if ARCHIVEREDO LOG mode is enabled.
Cause: An attempt was made to start an online backup, but an online backup was already started for one of the datafiles.
Action: End the first backup before beginning another.
Cause: A file belonging to the SYSTEM tablespace has been marked offline by the database administrator. The database cannot be started until all SYSTEM tablespace files are online and can be opened.
Action: Bring the file online.
Cause: An attempt was made to mount the database PARALLEL without the existence of a Lock Manager.
Action: Mount the database in EXCLUSIVE mode.
Cause: An attempt to shut down normally found that an online backup is still in progress.
Action: End the backup of the offending tablespace and retry this command.
Cause: Tablespace cannot be taken offline or made read-only when online backup is running. Ending the backup entails writing the file header, which this operation, were it permitted, would prevent.
Action: End the online backup and then take the tablespace offline or make it read-only.
Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery. This message is usually accompanied by ORA-01172.
Action: There is additional information for ORA-01172. Perform a RECOVER datafile for the file containing the block. If this does not resolve the problem, restore the file from a backup and recover it again.
Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery.
Action: Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery.
Cause: Attempted to start an incompatible media recovery or open resetlogs during media recovery or RMAN backup . Media recovery sessions are incompatible if they attempt to recover the same data file. Incomplete media recovery or open resetlogs is incompatible with any media recovery. Backup or restore by RMAN is incompatible with open resetlogs.
Action: Complete or cancel the other media recovery session or RMAN backup.
Cause: Some operation is in progress that expects the state of the instance to remain open or mounted.
Action: Wait for the operation to complete and try again. If attempting a normal database shutdown, try SHUTDOWN ABORT.
Cause: The attempted operation will not succeed while the instance is in one of the states mentioned in the message.
Action: Wait for the open, close, mount, or dismount to complete and try again. If attempting a normal database shutdown, try SHUTDOWN ABORT.
Cause: Either media or instance recovery is in progress. The recovery may need access to the files that the attempted operation tried to use.
Action: Wait for the recovery to complete and try again.
Cause: The background process was either unable to find one of the data files or failed to lock it because the file was already in use. The database will prohibit access to this file but other files will be unaffected. However, the first instance to open the database will need to access all online data files. The accompanying error from the operating system describes why the file could not be identified.
Action: At the operating system level, make the file available to the database. Then either open the database or do an ALTER SYSTEM CHECK DATAFILES.
Cause: Another instance has a database by this name mounted.
Action: Find which instance is still running. Perhaps you have not lost the control files after all.
Cause: Not all of the files specified in CREATE CONTROLFILE are from the same database. The database ID of this file does not match that from the first file specified.
Action: Check the list of files provided to the CREATE.
Cause: The named file in the DATAFILE or LOGFILE section of the CREATE CONTROLFILE command does not appear to be as stated.
Action: Check the mentioned file.
Cause: The database name given at the command line does not match the database name found in the file header.
Action: Chance are good that the database name specified at the command line is incorrect. Resolve the discrepancy, and resubmit the command. If you are attempting to change the database name, be sure to use the SET DATABASE option.
Cause: CREATE CONTROLFILE discovered that the block size for this file is incompatible with any of the configured cache blocksizes in the initialization parameter file.
Action: Configure the appropriate cache for this block size using one of the (DB_2K_cache_size, DB_4K_cache_size, DB_8K_cache_size, DB_16K_cache_size, DB_32K_cache_size) parameters.
Cause: The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header.
Action: Specify the correct file name and size (in bytes).
Cause: MAXLOGFILES specified on the command line too large.
Action: Resubmit the command with a smaller value for MAXLOGFILES.
Cause: MAXDATAFILES specified on the command line too large.
Action: Resubmit the command with a smaller value for MAXDATAFILES.
Cause: File mentioned in CREATE CONTROLFILE has a file number which is larger than that specified for MAXDATAFILES or MAXLOGFILES.
Action: Increase the maximum specified on the command line.
Cause: There is an overlap of file numbers in the files specified on the command line or the same file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same log they must be specified together in a group file specification. This message will also appear if the same control file appears more than once in the CONTROL_FILES parameter in the INIT.ORA file. If this happens, check for additional error messages.
Action: Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files then omit the earlier backup. If they are members of the same log, insure they are in the same group file specification. If this message appears because of a duplicate control file, check the CONTROL_FILES parameter in the INIT.ORA file and see if a file is specified more than once. If all files names appear to be unique, check to make sure that the actual control files themselves are unique. For example, in UNIX check for a symbolic or a hard link to another control file in the list.
Cause: The file is located on a device with a different physical block size than the other members in the group.
Action: Use a physical device with matching block size.
Cause: Datafile number 1 was not specified in a CREATE CONTROLFILE command.
Action: Locate datafile number 1 and resubmit the CREATE CONTROLFILE command.
Cause: A file specified in the CREATE CONTROLFILE statement was not found. All datafiles and all redo log files, if NORESETLOGS was used, must be accessible by the process that issues the CREATE CONTROLFILE statement.
Action: Check the statement for a typing mistake in the file name and check for the existence of all files. Then issue the statement again after correcting the file names.
Cause: The checkpoint in the file header could not be advanced. See accompanying errors for the reason. The datafile will be taken offline the same as for a write error of a data block.
Action: See accompanying errors for details. Restore access to the file, do media recovery, and bring it back online.
Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery.
Action: Do a RECOVER DATAFILE for the file containing the block. If this does not resolve the problem, then restore the file from a backup and recover it.
Cause: One of the following:
Action: One of the following:
Cause: The maximum number of database files supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.
Action: Change the value of the DB_FILES parameter to be compatible.
Cause: The data dictionary is found to have more files than that which can be supported by this instance.
Action: Shut down the instance and restart with a larger value for DB_FILES.
Cause: After a CREATE CONTROLFILE, the data dictionary was found to have more datafiles than that supported by the control file.
Action: Re-create the control file with a larger value for MAXDATAFILES.
Cause: When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile.
Action: Do a CREATE CONTROLFILE with the correct file or none at all.
Cause: An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a datafile that existed at the last CREATE CONTROL file command. The information needed to re-create the file was lost with the control file that existed when the file was added to the database.
Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.
Cause: During datafile recovery, a file was listed that was not part of the database.
Action: Recheck the file name. Remember to use single quotation marks at the SQL*DBA command line. Remember also that the file name is translated in the operating environment of SQL*DBA.
Cause: An attempt was made to create datafile 1 using ALTER DATABASE CREATE DATAFILE.
Action: Recover file from a backup or re-create the database.
Cause: An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a datafile that existed at the last RESETLOGS database open.
Action: Find a backup of the file, and recover it. Do incomplete recovery to time before file was originally created.
Cause: An attempt was made to use ALTER DATABASE CREATE DATAFILE to re-create a datafile that is online in an open instance or is being recovered.
Action: Close database in all instances and end all recovery sessions.
Cause: Some other instance has the database mounted exclusive.
Action: Shut down the other instance and then mount shared.
Cause: An ALTER DATABASE ADD LOGFILE statement specified a log number for the new log which is already in use.
Action: Specify a different log file number, or let the database choose an unused value.
Cause: An ALTER DATABASE ADD LOGFILE statement specified a log number for the new log which is too large.
Action: Specify a correct log file number.
Cause: The datafile did not pass the checks to insure it is part of the database. See the accompanying error messages for the reason the verification failed.
Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.
Cause: The datafile did not pass the checks to insure it is part of the database. Reads are not allowed until it is verified.
Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.
Cause: A log file member given to CREATE CONTROLFILE is on a physical device that has a different block size than the device originally used to create the log.
Action: Move the file to a device with the correct block size or use the RESETLOGS option to CREATE CONTROLFILE.
Cause: In a CREATE CONTROLFILE command, either this file or all previous files were backups from before the last RESETLOGS. This may also occur if this is a file that is offline and has been offline since before the last RESETLOGS.
Action: If the file was taken offline normal before the last RESETLOGS, and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise find the version of the mentioned file consistent with the rest of the datafiles and resubmit the command.
Cause: An attempt was made to use a datafile when the log reset information in the file does not match the control file. Either the datafile or the control file is a backup that was made before the most recent ALTER DATABASE OPEN RESETLOGS.
Action: Restore file from a more recent backup.
Cause: When attempting to do a normal tablespace offline, it was discovered that one of the files in the tablespace was already offline.
Action: Either bring the datafile online first, or use another tablespace offline option.
Cause: At least two redo log files from at least one thread must be specified in the CREATE CONTROLFILE command line.
Action: Find the missing redo log files and retry the command with the newly found redo log files included in the command line.
Cause: A different copy of the file was accessed the last time media recovery looked at the file header. A backup of the file was restored or the meaning of the file name changed during recovery.
Action: Ensure the correct file is available, and then retry recovery.
Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file was not closed cleanly when it was last opened by the database. It must be recovered to a time when it was not being updated. The most likely cause of this error is forgetting to restore the file from a backup before doing incomplete recovery.
Action: Either apply more logs until the file is consistent or restore the file from an older backup and repeat recovery.
Cause: An incomplete recovery session was started, but an insufficient number of logs were applied to make the file consistent. The reported file is an online backup which must be recovered to the time the backup ended.
Action: Either apply more logs until the file is consistent or restore the database files from an older backup and repeat recovery.
Cause: The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file.
Action: Either apply more logs until the file is consistent or restore the backup again and repeat recovery.
Cause: During CREATE CONTROLFILE all threads represented in the logs must be represented by at least two logs. A "last log" and a second log. The named thread does not contain two such logs.
Action: Either find more logs from the named thread. Or use the RESETLOGS option to CREATE CONTROLFILE.
Cause: File sizes must be given for all log files if doing a CREATE CONTROLFILE with the RESETLOGS option.
Action: Resubmit the command with the appropriate log file size.
Cause: An attempt was made to end an online backup for a file that is not in online backup.
Action: Do not enter command since it is not needed.
Cause: The size of the file as returned by the operating system is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated. Maybe it is the result of a half completed copy.
Action: Restore a good copy of the datafile and do recovery as needed.
Cause: An I/O error was reported for the file header. The error was trapped and a second attempt will be made.
Action: The file probably will require recovery. Further error messages will indicate what is needed.
Cause: The creation time in the file header is not the same as the creation time in the control file. This is probably a copy of a file that was dropped.
Action: Restore a current copy of the datafile and do recovery as needed.
Cause: The creation SCN in the file header is not the same as the creation SCN in the control file. This is probably a copy of a file that was dropped.
Action: Restore a current copy of the datafile and do recovery as needed.
Cause: The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database.
Action: Restore a copy of the correct datafile and do recovery as needed.
Cause: The file type in the header is not correct for a datafile. This is probably a log file or control file. If the type is not a small non-zero positive number then the header is corrupted.
Action: Restore a copy of the correct datafile and do recovery as needed.
Cause: The database ID in the file header does not match the database ID in the control file. The file may be from a different database, or it may not be a database file at all. If the database was rebuilt, this may be a file from before the rebuild. Note that if you see this error when the file is supposed to be plugged in from another database via the Transportable Tablespace feature, it means the database ID in the file header does not match the one expected.
Action: Restore a copy of the correct datafile and do recovery as needed.
Cause: The control file change sequence number in the datafile is greater than the number in the control file. This implies that the wrong control file is being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.
Action: Use the current control file or do BACKUP CONTROLFILE RECOVERY to make the control file current. Be sure to follow all restrictions on doing a BACKUP CONTROLFILE RECOVERY.
Cause: The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.
Action: Make the correct file available to the database. Then, either open the database, or execute ALTER SYSTEM CHECK DATAFILES.
Cause: The reset log data in the file header does not match the control file. If the database is closed or the file is offline, the backup is old because it was taken before the last ALTER DATABASE OPEN RESETLOGS statement. If opening a database that is open already by another instance, or if another instance just brought this file online, the file accessed by this instance is probably a different version. Otherwise, a backup of the file probably was restored while the file was in use.
Action: Make the correct file available to the database. Then, either open the database or execute ALTER SYSTEM CHECK DATAFILES.
Cause: The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistency of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database.
Action: Have operating system make correct file available to database. If the trace file dump indicates that only the checksum is wrong, restore from a backup and do media recovery.
Cause: The file is not a copy of the file LAST used under Oracle7. This datafile is either a backup taken from before the migration, or the database was opened by Oracle7 after the migration utility was run. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database under Oracle7. Only the datafiles that were current when the migration was done may be accessed by Oracle8.
Action: Have operating system make correct datafile available to database, or repeat the Oracle7 to Oracle8 migration. Make sure that database is NOT opened after migration utility is run.
Cause: MAXLOGMEMBERS specified on the command line too large.
Action: Resubmit the command with a smaller value for MAXLOGMEMBERS.
Cause: MAXINSTANCES specified on the command line too large.
Action: Resubmit the command with a smaller value for MAXINSTANCES.
Cause: MAXLOGHISTORY specified on the command line too large.
Action: Resubmit the command with a smaller value for MAXLOGHISTORY.
Cause: A CREATE CONTROLFILE statement was given which did not list all the enabled threads for the database.
Action: Reissue the CREATE CONTROLFILE statement, including all enabled threads.
Cause: A thread that was given during CREATE CONTROLFILE is enabled, but the datafiles indicate that it should be disabled. This is probably because the logs supplied to the CREATE CONTROLFILE are old (from before the disabling of the thread).
Action: This thread is not required to run the database. The CREATE CONTROLFILE statement can be reissued without the problem thread, and, if desired, the thread can be re-created after the database is open.
Cause: A member of a multiple-member log file group specified in a CREATE CONTROLFILE is not part of the same group as previous members.
Action: Group together the correct members for the CREATE CONTROLFILE command.
Cause: A member of a multiple-member log file group is from a different point in time. One of the members specified may be an older (backup) copy of the log.
Action: Find the correct version of the log, or leave it out of the CREATE CONTROLFILE command.
Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database has been opened.
Action: Re-phrase the query to include only fixed objects, or open the database.
Cause: A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open.
Action: Re-phrase the query to avoid a large sort, increase the values of the SORT_AREA_SIZE and/or SORT_AREA_RETAINED_SIZE initialization parameters to enable the sort to be done in memory.
Cause: When the database writer opens the datafile, it is accessing a different physical file than the foreground doing the recovery. The timestamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all.
Action: Look in the DBWR trace file for the error it received when attempting to read the file header. Reconfigure the operating system as needed to have the file name successfully access the same file when opened by a background process.
Cause: An attempt was made to create a database or control file that does not have room for at least two logs per thread of redo. A thread of redo must have two online logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.
Action: Either reduce the MAXINSTANCES argument or increase the value of MAXLOGFILES.
Cause: The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS.
Action: Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE.
Cause: Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong.
Action: Omit the GROUP option or give the correct one.
Cause: The log is for a thread greater than the MAXINSTANCES argument.
Action: Increase the value for MAXINSTANCES and resubmit the command.
Cause: The log file member in the accompanying error is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted log.
Action: Find the correct log member or omit this member from the command.
Cause: The log file in the accompanying error is inconsistent with the contents of other logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the log listed since all that can be detected is that there is an inconsistency. All log files listed in the command must be the current versions of the online logs.
Action: Find the correct online logs or use the RESETLOGS option.
Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database id. Both the SET DATABASE and RESETLOGS options must be specified to create the control file for this database.
Action: Resubmit command with the SET DATABASE and RESETLOGS options.
Cause: The datafile in the accompanying error is inconsistent with the contents of the logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online logs was missing from the command. It is also possible that one or more of the logs is an old copy rather than the current version. All online log files must be listed in the command and must be the current versions of the online logs.
Action: Find the correct online logs or use the RESETLOGS option.
Cause: An attempt to make a tablespace read only found that one of its files is offline.
Action: Bring the file online and retry this command.
Cause: An attempt to make a tablespace read write found that one of its files is offline.
Action: Bring the file online and retry this command.
Cause: An attempt to start an online backup found that one of the files is marked read only. Read-only files do not need to be set into online backup mode.
Action: Make the backup without the begin backup command.
Cause: An attempt to do media recovery using a backup control file found that one of the files is marked read only. Read-only files do not normally need to be recovered, but recovery with a backup control file must recover all online files.
Action: If the file really is read only, take it offline before the recovery, and bring the read-only tablespace online after the database is open. If the file does need recovery use a control file from the time the file was read-write. If the correct control file is not available, use CREATE CONTROLFILE to make one.
Cause: An attempt was made to end an online backup of file when the file is busy. Some operation such as recovery or rename may be active, or there may still be some instance that has the database open with this file online.
Action: If there is an instance with the database open then the backup can be ended there by using the ALTER TABLESPACE command. Otherwise wait for the completion of the other operation.
Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded.
Action: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful.
Cause: The indicated error occurred while doing initialization processing of file headers.
Action: The error indicated should be corrected. An attempt is made to recover from this error by using a slower access algorithm.
Cause: An operating system error occurred during the resize.
Action: Fix the cause of the operating system error and retry the command.
Cause: An operating system error occurred during the resize.
Action: The error is ignored, operation continues normally.
Cause: An online file uses an external cache, but the database is in NOARCHIVELOG mode. Since an external cache may require media recovery this cannot be allowed.
Action: Change database to be in ARCHIVELOG mode or do not use an external cache.
Cause: The command specifies adding more datafiles than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large.
Action: If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If this is an ADD DATAFILE command, break it up into multiple commands.
Cause: The external cache may have been restarted.
Action: Take the file mentioned in the error stack offline, perform media recovery, bring the file online, and retry the attempted operation. You may also restart all instances to make sure they access all datafiles through consistent external caches.
Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure.
Action: Restore accessibility to the file mentioned in the error stack and restart the instance.
Cause: A system tablespace file was detected as inaccessible due to media failure.
Action: Restore accessibility to the file mentioned in the error stack and restart the instance.
Cause: Media recovery with a backup control file or a control file that was rebuilt, encountered the creation of a datafile that was not in the control file. An entry has been added to the control file for the new datafiles, but with the file name UNNAMEDnnnn, where nnnn is the file number. Attached errors describe the file names that were originally used to create the files.
Action: Rename the files to valid file names and resume recovery. If necessary the ALTER DATABASE CREATE DATAFILE statement may be used to create a file suitable for recovery and do the rename. If the file is not going to be recovered then take it offline with the FOR DROP option.
Cause: An attempt was made to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option.
Action: Either bring the file online and recover it, or take it offline with the FOR DROP option.
Cause: The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery.
Action: Restore more recent backups and recover them.
Cause: Recovery of the whole database encountered redo indicating there was a point in time recovery of the tablespace. The new version of the files in the tablespace should be included in the recovery, but that was not done.
Action: If the tablespace should not be recovered, take its file offline for drop. If it should be recovered, then restore or rename as needed and restart the recovery.
Cause: An attempt was made to do a RESETLOGS open with a file entry in the control file that was originally created after the UNTIL time of the incomplete recovery. Allowing such an entry may hide the version of the file that is needed at this time. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed.
Action: If more recovery is desired then apply redo until the creation time of the file is reached. If the file is not wanted and the same file number is not in use at the stop time of the recovery, then the file can be taken offline with the FOR DROP option. Otherwise a different control file is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a control file can be created via CREATE CONTROLFILE.
Cause: An attempt was made to archive an online redo log or enable archiving for a clone database.
Action: Do not attempt to archive from a clone. The archive log destination could easily be the same as the primary database destroying its archived logs. If archiving is needed, then re-create the database not as a clone.
Cause: The indicated error occurred while terminating the processing of file headers. The error was other than a write error.
Action: The indicated error should be corrected.
Cause: Read of the file header returned a record but its version cannot be identified. Either the header has been corrupted, or the file is not a valid database file.
Action: Have the operating system make the correct file available to the database, or recover the file.
Cause: An attempt to make a tablespace read only or offline normal found that a recovery manager proxy backup is in progress. If the file is made offline or read only, then the file header cannot be updated when the backup is complete.
Action: Wait for the Recovery Manager backup to complete and retry this command.
Cause: The specified file is being backed up by Recovery Manager.
Action: Wait for the Recovery Manager proxy backup to complete before starting another backup.
Cause: The specified file is being backed up by Recovery Manager.
Action: Wait for the Recovery Manager proxy backup to complete. Recovery Manager backup mode cannot be initiated or terminated manually.
Cause: An attempt to shut down normally found that a Recovery Manager backup is still in progress.
Action: Wait for the Recovery Manager proxy backup to complete and retry this command.
Cause: The file is in use by another database instance.
Action: Determine which database instance legitimately owns the file.
Cause: The size of the raw partion cannot be determined.
Action: Add the datafile/logfile by specifying the size parameter.
Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES or ALTER DATABASE TEMPFILE DROP INCLUDING DATAFILES operation was not able to delete a temporary file in the database.
Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.
Cause: A DROP TABLESPACE INCLUDING CONTENTS AND DATAFILES operation was not able to delete a datafile in the tablespace.
Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.
Cause: ALTER DATABASE END BACKUP was issued while the database was open.
Action: Either use ALTER DATABASE DATAFILE <filename> END BACKUP to end backup for specific files, or ALTER TABLESPACE <name> END BACKUP if backup is complete for all files in a tablespace.
Cause: The value for the specified parameter contained a destination string that could not be translated.
Action: Use a valid destination string in the specified parameter.
Cause: Unable to get information about an Oracle Managed Files destination directory.
Action: Check the permissions on the directory or use a different directory name.
Cause: The name given for an Oracle Managed Files destination does not correspond to a directory.
Action: Use a different name.
Cause: Unable to create an Oracle Managed Files name for a datafile, logfile or control file.
Action: Check previous error messages for the reason Oracle was unable to create the file name. Take corrective action, if possible, and retry the command.
Cause: An error prevented the file from being deleted.
Action: Subsequent errors describe the operating system error that prevented the file deletion. Fix the problem, if possible, and manually purge the file.
Cause: Unable to create a unique file name for an Oracle Managed Files datafile, logfile, or control file. Oracle tried several names but each file name was already in use in the default destination directory for the file type.
Action: Retry the operation. If that fails, it may be necessary to change the default destination directory for the file type and then retry.
Cause: Could not get date/time when trying to create unique file name.
Action: Internal error - contact Oracle Support Services.
Cause: A TEMPFILE clause was specified for an ALTER TABLESPACE for a permanent tablespace.
Action: Retry with a DATAFILE clause.
Cause: The value for DB_CREATE_FILE_DEST or DB_CREATE_ONLINE_LOG_DEST_n parameter is too long.
Action: Replace the destination value for the specified parameter with a shorter character string.
Cause: An operation that renames or adds/drops a file was attempted at a standby database and STANDBY_PRESERVES_NAMES is true.
Action: Set STANDBY_PRESERVES_NAMES to false if the operation must be performed.
Cause: During standby database recovery an error occurred when trying to create a new file name for the indicated file.
Action: Use the ALTER DATABASE CREATE DATAFILE command with a new unique name and then resume the standby database recovery.
Cause: The REUSE parameter was specified in a command without a file name.
Action: Either supply a file name or remove the REUSE parameter.
Cause: The COMPATIBLE initialization parameter was not set to the correct value for setting STANDBY_FILE_MANAGEMENT to AUTO.
Action: Restart the instance with COMPATIBLE set to the correct release.
Cause: Automated standby file management was enabled but an added file could not automatically be created on the standby. The error from the creation attempt is displayed in another message. The controlfile file entry for the file will be 'UNNAMEDnnnnn'.
Action: Temporarily set STANDBY_FILE_MANAGEMENT to MANUAL and use the ALTER DATABASE CREATE DATAFILE statement to create the file. Then set STANDBY_FILE_MANAGEMENT to AUTO and restart standby recovery.
Cause: An operation that renames, adds, or drops a file was attempted at a standby database and STANDBY_FILE_MANAGEMENT was set to AUTO.
Action: Set STANDBY_FILE_MANAGEMENT to MANUAL if the operation must be performed.
Cause: An attempt was made to add to the database a datafile, log file, or control file with an Oracle Managed Files file name.
Action: Retry the operation with a new file name.
Cause: An ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename' statement specified a file name which is already in use.
Action: Either specify a different file name or add the REUSE parameter to the statement to overwrite the existing file.
Cause: An operating system error occurred while attempting to create a trace file specified in the ALTER DATABASE BACKUP CONTROLFILE TO TRACE AS 'filename' statement.
Action: Check the error stack for more detailed information.
Cause: DB_FILES has been set too high to be supported by the system.
Action: Decrease the value of DB_FILES.
Cause: On of the following:
Action: Check to see whether the input parameters are valid. The V$LOGMNR_LOGS view can be queried to see the SCN ranges that are valid for the set of log files specified, and the DB_ID of the database that generated the log files.
Cause: StartSCN may be greater than EndSCN, or the SCN specified may be invalid.
Action: Specify a valid SCN range.
Cause: The specified Date value is invalid for the log file.
Action: Specify a valid date range.
Cause: The specified Options is invalid for the procedure.
Action: Specify valid Options.
Cause: The specified file cannot be opened.
Action: Check to make sure the file or directory exists and is accessible.
Cause: The file or directory may not exist or is inaccessible.
Action: Specify valid file or directory. Make sure that file and directory are accessible.
Cause: The log file is produced by a different database than other log files already added to the list.
Action: Specify a log file produced by the same database.
Cause: The logfile was produced by a different incarnation of the database.
Action: Add a logfile that is produced by the same incarnation.
Cause: The logfile is produced by a different incarnation of the database.
Action: Add a logfile that is produced by the same incarnation.
Cause: The log file specified has already been added to the list of log files.
Action: Specify a different log file.
Cause: The user attempted to remove a log file that is not present in the list.
Action: Specify a valid logfile.
Cause: Not all logfiles corresponding to the data or scn range specified have been added to the list.
Action: Check the v$logmnr_logs view to determine the missing scn range, and add the relevant logfiles.
Cause: No log file has been specified for the LogMiner session.
Action: Specify at least one log file.
Cause: The input date/SCN range is not fully contained within the log files specified for the session.
Action: Select out of V$LOGMNR_LOGS view to check the date or SCN range covered by the log files specified for the LogMiner session, and reissue the procedure with appropriate date or SCN range.
Cause: The dictionary file is corrupt.
Action: Get a new dictionary file.
Cause: The dictionary file is produced by a database that is different from that produced the log files.
Action: Specify a compatible dictionary file.
Cause: The character set of the database that produced the dictionary file is different from the character set of the database that produced the log files.
Action: Specify a dictionary file with the same character set.
Cause: The redo version of the database generating the dictionary is different from the one generating the logfiles.
Cause: The dictionary materialized view was taken at a SCN that does not correspond to the creation SCN of the earliest logfile.
Action: Get a correct dictionary materialized view.
Cause: The dictionary file was extracted from a different incarnation of the database.
Action: Specify a dictionary file extracted from the correct database incarnation.
Cause: DBMS_LOGMNR.USE_COLMAP can only be used with a valid dictionary.
Action: Specify the dictionary file in DBMS_LOGMNR.START_LOGMNR().
Cause: A syntax error was detected in the logmnr.opt file.
Action: Use correct syntax.
Cause: The schema specified does not exist.
Action: Specify a correct schema or a compatible dictionary file.
Cause: The table specified in the logmnr.opt file does not exist in the dictionary provided to LogMiner.
Action: Make sure that the table specified is valid.
Cause: The column specified in the logmnr.opt file does not exist for the table definition in the dictionary provided for LogMiner.
Action: Make sure that the column specified is valid.
Cause: A select was issued from V$LOGMNR_CONTENTS without first invoking the DBMS_LOGMNR.START_LOGMNR() procedure.
Action: Invoke the DBMS_LOGMNR.START_LOGMNR() procedure before issuing a select from the V$LOGMNR_CONTENTS view.
Cause: A select was issued from V$LOGMNR_CONTENTS without first invoking the DBMS_LOGMNR.START_LOGMNR() procedure. Otherwise, DBMS_LOGMNR.END_LOGMNR() was called without a prior call to DBMS_LOGMNR.START_LOGMNR() or DBMS_LOGMNR.ADD_LOGFILE()
Action: Invoke the DBMS_LOGMNR.START_LOGMNR() procedure before issuing a select from the V$LOGMNR_CONTENTS view.
Cause: UTL_FILE_DIR is not set in the initialization parameter file.
Action: Set UTL_FILE_DIR to the appropriate directory.
Cause: The specified Logminer session ID or session handle is invalid.
Action: Use a valid Logminer session ID or session handle.
Cause: The return type requested by the user is not supported by LCR_MINE.
Action: Pick a return type supported by the LCR_MINE function.
Cause: An attempt was made to use the MINE_VALUE function on a column other than redo_value or undo_value columns of SYS.V$LOGMNR_CONTENTS fixed table/view.
Action: Rewrite the SQL statement with a legal invocation of MINE_VALUE.
Cause: The table/column specified in the LCR_MINE call does not exist at the the specified SCN. The table/column definition has to exist at the start SCN specified for lcr_mine to be able to identify the table/column correctly.
Action: Create a LogMiner session at a start SCN at which the table definition is available.
Cause: The return type specified for the column in the LCR_MINE call is different from the actual type of the column.
Action: Rewrite the LCR_MINE invocation with the right return type.
Cause: The fully qualified name of the column to be mined by the LogMiner functions should be string literal.
Action: If the fully qualified name of the column to be mined is a.b.c.d, enclose the column name in quotes as in 'a.b.c.d'.
Cause: A redo log file has been added or removed while selecting on the v$logmnr_logs fixed view.
Action: Re-issue the SQL select statement on the v$logmnr_logs view.
Cause: A Logminer attach session was issued while already attached to a Logminer session.
Action: Detach from the current Logminer session and attach to the requested session.
Cause: A command or procedure was issued which requires an attached Logminer session.
Action: Attach to a Logminer session before issuing the command or procedure.
Cause: Logminer activate session was called before prepare session.
Cause: A session attribute was supplied which is invalid.
Action: Re-issue with a valid session attribute.
Cause: A Logminer dictionary attribute was supplied which is invalid.
Action: Re-issue with a valid dictionary attribute.
Cause: The input date/SCN range is not fully contained within the logfiles specified for the session.
Action: select out of v$logmnr_logs view to check the date or SCN range covered by the logfiles specified for the LogMiner session , and reissue the procedure with appropriate date or SCN range.
Cause: An non-existent table was supplied to Logminer include_src_tbl() or exclude_src_table().
Action: Re-issue with a valid table name.
Cause: A Logminer routine was called from the wrong state.
Cause: The logfile was produced by a different database than other logfiles already added to the list.
Action: Specify a logfile produced by the same database.
Cause: The database does not have archivelog mode enabled.
Action: Ensure that initialization parameters enabling archivelog mode are set. For example:
log_archive_start=true log_archive_dest="ORACLE_HOME/dbs" log_archive_format="archstring.log"
Mount the database and issue commands to enable archivelog mode.
startup pfile=initsid.ora mount ALTER DATABASE ARCHIVELOG ALTER DATABASE OPEN
Cause: The COMPATIBLE initialization parameter is set to some value less than 9.0.0.
Action: Ensure that the COMPATIBLE initialization parameter is set to 9.0.0 or higher. For example:
COMPATIBLE = 9.0.0.0.0
Cause: Other users are performing DDL operations.
Cause: Another process is simultaneously attempting to run build().
Action: Wait until the other process completes.
Cause: The table may be missing or locked by another user.
Action: This error should not occur. If it does occur and there is reason to believe that required tables are missing, then as a last resort the package dbmslmd.sql may be reinstalled. Doing so will delete all existing Logminer Dictionary data.
Cause: Unexpected error condition.
Action: Check the trace file.
Cause: No previously established Logminer Dictionary is available and a complete gather of a source system data dictionary was not found in the logstream. build() may not have been run to force the gathering of a source system data dictionary, or add_log_file() may not have been called to add all log files which contain the complete gathered system data dictionary.
Action: If build() was not employed prior to this mining session, the Logminer Ad Hoc user may elect to employ an alternate dictionary such as the current system catalog or a previously built flat file dictionary. Other Logminer clients must run build() prior to mining. If build() has been run, ensure that all logfiles which comprise the gathered system dictionary have been added. The following query, run on the system which build() was run, can be helpful in identifying the required files.
select DICTIONARY_BEGIN, DICTIONARY_END, name from v$archived_log;
Minimally a set of files starting with one which has DICTIONARY_BEGIN = 'YES' and all subsequent log files through one which has DICTIONARY_END = \qYESmustbeadded.'
Cause: The dictionary file or directory does not exist or is inaccessible.
Action: Make sure that the dictionary file and directory exist and are accessible.
Cause: The logfile has a different compatibility version than the rest of the logfiles in the session.
Action: Make sure that all logfiles in the session have the same compatibility version.
Cause: Can not do this when other process is attached to LogMiner session.
Cause: An attempt was made to add an already processed logfile.
Cause: Could not load NLS package.
Cause: The logfiles to be analyzed in the current LogMiner session require more system resources than what is currently available.
Action: Reduce the number of logfiles to be analyzed for a given LogMiner session and try again.
Cause: Logminer can not resume session because there is not enough SGA memory available to read in checkpointed data. Logminer periodically checkpoints data to enable faster crash recovery.
Action: Specify a bigger max_sga for the given LogMiner session and try again.
Cause: A coordinator process is already attached to the specified logminer context.
Action: Detach from the active coordinator session and retry the attach.
Cause: Supplemental log data must be enabled on this database instance.
Action: Enable supplemental log data.
Cause: LogMiner sessions exist on this database instance which rely on the existence of supplemental log data.
Action: Destroy all LogMiner sessions on this instance which are mining log files from this same instance. Then reissue the command.
Cause: The source database instance producing log files for this LogMiner session was altered to no longer log supplemental data.
Action: Destroy this Logminer session. Re-enable supplemental log data on the source system and create a new LogMiner session.
Cause: Invocation failed to specify either a dictionary tablespace or a spill tablespace.
Action: Reformat invocation of DBMS_LOGMNR_D.SET_TABLESPACE to include the name of one or more tablespaces.
NEW_TABLESPACE - A string naming an existing tablespace.
Supply only this parameter to recreate all Logminer tables to employ this tablespace.
DICTIONARY_TABLESPACE - A string naming an existing tablespace.
Supply this parameter when it is desired to place Logminer Dictionary data in a tablespace different from that where Logminer spill data is to be written. This parameter overrides the new_tablespace parameter with respect to Logminer Dictionary tables.
SPILL_TABLESPACE - a string naming an existing tablespace.
Supply this parameter when it is desired to place Logminer spill data in a tablespace different from that where Logminer Dictionary data is to be written. This parameter overrides the new_tablespace parameter with respect to Logminer spill tables.
Cause: The tablespace name given as either the NEW_TABLESPACE or the DICTIONARY_TABLESPACE parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.
Action: Check the spelling of the tablespace name. If the spelling is correct, then verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE will not create a tablespace.
Cause: The tablespace name given as either the NEW_TABLESPACE or the SPILL_TABLESPACE parameter to DBMS_LOGMNR_D.SET_TABLESPACE does not exist.
Action: Check the spelling of the tablespace name. If the spelling is correct, then verify that the named tablespace has already been created. DBMS_LOGMNR_D.SET_TABLESPACE will not create a tablespace.
Cause: An attempt was made to execute DBMS_LOGMNR_D.SET_TABLESPACE while Logminer sessions existed. In general DBMS_LOGMNR_D.SET_TABLESPACE should be run before any Logminer activity has begun. If this error occurs, then this procedure has not been followed.
Action: First cause all Logminer sessions to be destroyed. A Logminer session can exist as a result of executing DBMS_LOGMNR.START_LOGMNR or as the result of running a product such as Logical Standby or Streams which uses Logminer. Next, execute DBMS_LOGMNR_D.SET_TABLESPACE.
Cause: The specified restart scn is too old and Logminer could not find a proper checkpoint.
Action: Specify a bigger restart SCN to try again.
Cause: One or more log files containing the LogMiner dictionary was not found.
Action: Add into LogMiner all log files containing the dictionary.
Cause: The number of processes requested by the caller can not be allocated.
Action: Increase the number of parallel servers allocated to the instance.
Cause: The maximum number of concurrent persistent LogMiner sessions allowed is limited by the LOGMNR_MAX_PERSISTENT_SESSIONS parameter. Not enough memory has been set aside at instance startup to allocate the new LogMiner session.
Action: Increase LOGMNR_MAX_PERSISTENT_SESSIONS and restart the instance.
Cause: LogMiner does not mine redo records generated with LOG_PARALLELISM set to a value greater than 1.
Cause: An attempt was made to insert a NULL into the column "USER"."TABLE"."COLUMN".
For example, if you enter:
connect scott/tiger create table a (a1 number not null); insert into a values (null);
Oracle returns:
ORA-01400 cannot insert NULL into ("SCOTT"."A"."A1") : which means you cannot insert NULL into "SCOTT"."A"."A1".
Action: Retry the operation with a value other than NULL.
Cause: The value entered is larger than the maximum width defined for the column.
Action: Enter a value smaller than the column width or use the MODIFY option with ALTER TABLE to expand the column width.
Cause: An INSERT or UPDATE statement was attempted on a view created with the CHECK OPTION. This would have resulted in the creation of a row that would not satisfy the view's WHERE clause.
Action: Examine the view's WHERE clause in the dictionary table VIEWS. If the current view does not have the CHECK OPTION, then its FROM clause must reference a second view that is defined using the CHECK OPTION. The second view's WHERE clause must also be satisfied by any INSERT or UPDATE statements. To insert the row, it may be necessary to insert it directly into the underlying table, rather than through the view.
Cause: In a host language program, all records have been fetched. The return code from the fetch was +4, indicating that all records have been returned from the SQL query.
Action: Terminate processing for the SELECT statement.
Cause: Increasing the length of a column would cause the combined length of the columns specified in a previous CREATE INDEX statement to exceed the maximum index length (255). The total index length is computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields are calculated as a length of 7, character fields are calculated at their defined width, and numeric fields are length 22.
Action: The only way to alter the column is to drop the affected index. The index cannot be re-created if to do so would exceed the maximum index width.
Cause: The INTO clause of a FETCH operation contained a NULL value, and no indicator was used. The column buffer in the program remained unchanged, and the cursor return code was +2. This is an error unless you are running Oracle with DBMS=6, emulating version 6, in which case it is only a warning.
Action: You may do any of the following:
Cause: In a host language program, a FETCH operation was forced to truncate a character string. The program buffer area for this column was not large enough to contain the entire string. The cursor return code from the fetch was +3.
Action: Increase the column buffer area to hold the largest column value or perform other appropriate processing.
Cause: An attempt was made to update a table column "USER"."TABLE"."COLUMN" with a NULL value.
For example, if you enter:
connect scott/tiger update table a (a1 number not null); insert into a values (null);
Oracle returns:
ORA-01407 cannot update ("SCOTT"."A"."A1") to NULL
which means you cannot update the column "SCOTT"."A"."A1" to NULL.
Action: Retry the operation with a value other than NULL.
Cause: A CREATE INDEX statement specified a column that is already indexed. A single column may be indexed only once. Additional indexes may be created on the column if it is used as a portion of a concatenated index, that is, if the index consists of multiple columns.
Action: Do not attempt to re-index the column, as it is unnecessary. To create a concatenated key, specify one or more additional columns in the CREATE INDEX statement.
Cause: Creation of index with NOSORT option when rows were not ascending. The NOSORT option may only be used for indexes on groups of rows that already are in ascending order.
For non-unique indexes the ROWID is considered part of the index key. This means that two rows that appear to be stored in ascending order may not be. If you create an index NOSORT, and two of the rows in the table have the same index values, but get split across two extents, the data block address of the first block in the second extent can be less than the data block address of the last block in the first extent. If these addresses are not in ascending order, the ROWIDs are not either. Since these ROWIDs are considered part of the index key, the index key is not in ascending order, and the create index NOSORT fails.
Action: Create the index without the NOSORT option or ensure that the table is stored in one extent.
Cause: A ROWID was entered incorrectly. ROWIDs must be entered as formatted hexadecimal strings using only numbers and the characters A through F. A typical ROWID format is '000001F8.0001.0006'.
Action: Check the format, then enter the ROWID using the correct format. ROWID format: block ID, row in block, file ID.
Cause: An attempt was made to fetch a column of size more than 64K and could not store the length of the column in the given indicator of size 2 bytes.
Action: Use the new bind type with call backs to fetch the long column.
Cause: The length for type 97 is 0.
Action: Specify the correct length.
Cause: The user buffer bound by the user as packed decimal number contained an illegal value.
Action: Use a legal value.
Cause: An attempt was made to bind an array without either a current array length pointer or a zero maximum array length.
Action: Specify a valid length.
Cause: The query contains more distinct aggregates than can be processed. The current limit is 255.
Action: Reduce the number of distinct aggregate functions in the query.
Cause: Two tables in a join operation specified an outer join with respect to each other. If an outer join is specified on one of the tables in a join condition, it may not be specified on the other table.
Action: Remove the outer join specification (+) from one of the tables, then retry the operation.
Cause: a.b (+) = b.b and a.c (+) = c.c is not allowed.
Action: Check that this is really what you want, then join b and c first in a view.
Cause: An ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement specified the name of an index that does not exist. Only existing indexes can be altered, dropped, or validated. Existing indexes may be listed by querying the data dictionary.
Action: Specify the name of an existing index in the ALTER INDEX, DROP INDEX, or VALIDATE INDEX statement.
Cause: An attempt was made to use an incorrect format.
Action: Inspect the format, correct it if necessary, then retry the operation.
Cause: An attempt was made to use an invalid format.
Action: Inspect the format, correct it if necessary, then retry the operation.
Cause: An attempt was made to use an invalid precision specifier.
Action: Inspect the precision specifier, correct it if necessary, then retry the operation.
Cause: The number specified in exact fetch is less than the rows returned.
Action: Rewrite the query or change number of rows requested.
Cause: An error was encountered during the execution of an exact fetch. This message will be followed by more descriptive messages.
Action: See the accompanying messages and take appropriate action.
Cause: The character following the escape character in LIKE pattern is missing or not one of the escape character, '%', or '_'.
Action: Remove the escape character or specify the missing character.
Cause: Given escape character for LIKE is not a character string of length 1.
Action: Change it to a character string of length 1.
Cause: Evaluation of an value expression causes an overflow/underflow.
Action: Reduce the operands.
Cause: The outer query must use one of the keywords ANY, ALL, IN, or NOT IN to specify values to compare because the subquery returned more than one row.
Action: Use ANY, ALL, IN, or NOT IN to specify which values to compare or reword the query so only one row is retrieved.
Cause: An illegal value for a mathematical function argument was specified. For example
SELECT SQRT(-1) "Square Root" FROM DUAL;
Action: See the Oracle9i SQL Reference for valid input and ranges of the mathematical functions.
Cause: No overflow segment defined.
Action: Add overflow segment.
Cause: An ALTER TABLE ADD statement specified the name of a column that is already in the table. All column names must be unique within a table.
Action: Specify a unique name for the new column, then re-execute the statement.
Cause: An internal error occurred while attempting to execute a GRANT statement.
Action: Contact Oracle Support Services.
Cause: The synonym specified in DROP PUBLIC SYNONYM is not a valid public synonym. It may be a private synonym.
Action: Correct the synonym name or use DROP SYNONYM if the synonym is not public.
Cause: A CREATE SYNONYM statement specified a synonym name that is the same as an existing synonym, table, view, or cluster. Synonyms may not have the same name as any other synonym, table, view, or cluster available to the user creating the synonym.
Action: Specify a unique name for the synonym, then re-execute the statement.
Cause: A DROP SYNONYM statement specified a synonym that does not exist. Existing synonym names may be listed by querying the data dictionary.
Action: Specify the name of an existing synonym in the DROP SYNONYM statement.
Cause: This message is caused by any reference to a non-existent user. For example, it occurs if a SELECT, GRANT, or REVOKE statement specifies a username that does not exist. Only a GRANT CONNECT statement may specify a new username. All other GRANT and REVOKE statements must specify existing usernames. If specified in a SELECT statement, usernames must already exist.
Action: Specify only existing usernames in the SELECT, GRANT, or REVOKE statement or ask the database administrator to define the new username.
Cause: The condition specified in a CONNECT BY clause caused a loop in the query, where the next record to be selected is a descendent of itself. When this happens, there can be no end to the query.
Action: Check the CONNECT BY clause and remove the circular reference.
Cause: A join operation was specified with a CONNECT BY clause. If a CONNECT BY clause is used in a SELECT statement for a tree-structured query, only one table may be referenced in the query.
Action: Remove either the CONNECT BY clause or the join operation from the SQL statement.
Cause: When inserting or updating records, a numeric value was entered that exceeded the precision defined for the column.
Action: Enter a value that complies with the numeric column's precision, or use the MODIFY option with the ALTER TABLE command to expand the precision.
Cause: An ALTER TABLE MODIFY statement attempted to change the datatype of a column containing data. A column whose datatype is to be altered must contain only NULL values.
Action: To alter the datatype, first set all values in the column to NULL.
Cause: An ALTER TABLE MODIFY statement attempted to decrease the scale or precision of a numeric column containing data. In order to decrease either of these values, the column must contain only NULL values. An attempt to increase the scale without also increasing the precision will also cause this message.
Action: Set all values in the column to NULL before decreasing the numeric precision or scale. If attempting to increase the scale, increase the precision in accordance with the scale or set all values in the column to NULL first.
Cause: An ALTER TABLE MODIFY statement attempted to decrease the size of a character field containing data. A column whose maximum size is to be decreased must contain only NULL values.
Action: Set all values in column to NULL before decreasing the maximum size.
Cause: An ALTER TABLE MODIFY statement attempted to change a column specification unnecessarily, from NOT NULL to NOT NULL.
Action: No action required.
Cause: An internal error occurred in referencing a view.
Action: Contact Oracle Support Services.
Cause: This is an internal error message not normally issued.
Action: Contact Oracle Support Services.
Cause: A SELECT statement attempted to select ROWIDs from a view derived from a join operation. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned.
Action: Remove ROWID from the view selection clause, then re-execute the statement.
Cause: A SELECT statement attempted to select ROWIDs from a view containing columns derived from functions or expressions. Because the rows selected in the view do not correspond to underlying physical records, no ROWIDs can be returned.
Action: Remove ROWID from the view selection clause, then re-execute the statement.
Cause: An ALTER TABLE MODIFY statement specified a column used to cluster the table. Clustered columns may not be altered.
Action: To alter the column, first re-create the table in non-clustered form. The column's size can be increased at the same time.
Cause: An ALTER TABLE MODIFY statement attempted to change an indexed character column to a LONG column. Columns with the datatype LONG may not be indexed, so the index must be dropped before the modification.
Action: Drop all indexes referencing the column before changing its datatype to LONG.
Cause: An ALTER TABLE MODIFY statement attempted to change the definition of a column containing NULL values to NOT NULL. The column may not currently contain any NULL values if it is to be altered to NOT NULL.
Action: Set all NULL values in the column to values other than NULL before ALTERING the column to NOT NULL.
Cause: The combined length of all the columns specified in a CREATE INDEX statement exceeded the maximum index length. The maximum index length varies by operating system. The total index length is computed as the sum of the width of all indexed columns plus the number of indexed columns. Date fields have a length of 7, character fields have their defined length, and numeric fields have a length of 22. Numeric length = (precision/2) + 1. If negative, add +1.
Action: Select columns to be indexed so the total index length does not exceed the maximum index length for the operating system. See also your operating system-specific Oracle documentation.
Cause: The column may already allow NULL values, the NOT NULL constraint is part of a primary key or check constraint, or an ALTER TABLE MODIFY statement attempted to change a column specification unnecessarily, from NULL to NULL.
Action: If a primary key or check constraint is enforcing the NOT NULL constraint, then drop that constraint.
Cause: A CREATE UNIQUE INDEX statement specified one or more columns that currently contain duplicate values. All values in the indexed columns must be unique by row to create a UNIQUE INDEX.
Action: If the entries need not be unique, remove the keyword UNIQUE from the CREATE INDEX statement, then re-execute the statement. If the entries must be unique, as in a primary key, then remove duplicate values before creating the UNIQUE index.
Cause: A transaction was not processed properly because the SET TRANSACTION statement was not the first statement.
Action: Commit or roll back the current transaction before using the statement SET TRANSACTION.
Cause: A non-numeric value could not be converted into a number value.
Action: Check the value to make sure it contains only numbers, a sign, a decimal point, and the character "E" or "e", then retry the operation.
Cause: The converted form of the specified expression was too large for the specified datatype.
Action: Define a larger datatype or correct the data.
Cause: A non-DDL insert/delete/update or select for update operation was attempted.
Action: Commit (or roll back) the transaction, and then re-execute.
Cause: The converted form of the specified expression was too large for the specified type. The problem also occurs in COBOL programs when using COMP-3 in the picture clause, which is acceptable to the Pro*COBOL Precompiler and to COBOL but results in this error.
Action: Define a larger datatype or correct the data.
Cause: An attempt was made to bind or define a variable character string with a buffer length less than the minimum requirement.
Action: Increase the buffer size or use a different type.
Cause: The buffer length was less than the minimum required or greater than its length at bind time minus two bytes.
Action: Make sure the string size is long enough to hold the buffer.
Cause: The requested format conversion is not supported.
Action: Remove the requested conversion from the SQL statement. Check the syntax for the TO_CHAR, TO_DATE, and TO_NUMBER functions to see which conversions are supported.
Cause: An attempt was made to insert a value from a LONG datatype into another datatype. This is not allowed.
Action: Do not try to insert LONG datatypes into other types of columns.
Cause: The longest literal supported by Oracle consists of 2000 characters.
Action: Reduce the number of characters in the literal to 2000 characters or fewer or use the VARCHAR2 or LONG datatype to insert strings exceeding 2000 characters.
Cause: An attempt was made to modify the datatype of column which has referential constraints; or has check constraints which only allows changing the datatype from CHAR to VARCHAR or vise versa.
Action: Remove the constraint(s) or do not perform the offending operation.
Cause: The user in the TO clause of the GRANT statement has already been GRANTed privileges on this table.
Action: Do not GRANT privileges on a table to the user who originally GRANTed privileges on that table. The statement in error is probably unnecessary.
Cause: In an UPDATE statement following a SELECT FOR UPDATE, part of the ROWID contains invalid characters. ROWID must be expressed in the proper and expected format for ROWID and within quotes.
Action: Enter the ROWID just as it was returned in the SELECT FOR UPDATE.
Cause: This is a time-based read consistency error for a database object, such as a table or index. Either of the following may have happened:
Action: If the cause is:
If the object creation time-stamp is still greater than the system time, then export the object's data, drop the object, re-create the object so it has a new creation time-stamp, import the object's data, and resume work.
Cause: A DISTINCT, GROUP BY, ORDER BY, or SET operation requires a sort key longer than that supported by Oracle. Either too many columns or too many group functions were specified in the SELECT statement.
Action: Reduce the number of columns or group functions involved in the operation.
Cause: A predicate in the WHERE clause has two columns from different tables with "(+)".
Action: Change the WHERE clause so that each predicate has a maximum of one outer-join table.
Cause: An invalid column name was specified after the PRIOR keyword.
Action: Check syntax, spelling, use a valid column name, and try again.
Cause: Constants of different types are specified in an in-list.
Action: Use constants of same type for in-lists.
Cause: An attempt was made to create a private synonym with the same name as the object to which it refers. This error typically occurs when a user attempts to create a private synonym with the same name as one of their objects.
Action: Choose a different synonym name or create the synonym under a different username.
Cause: CONNECT BY cannot be used on a view where there is not a correspondence between output rows and rows of the underlying table.
Action: Remove the DISTINCT or GROUP BY from the view or move the CONNECT BY clause into the view.
Cause: Subqueries cannot be used in a CONNECT BY clause.
Action: Remove the subquery or move it to the WHERE clause.
Cause: START WITH and PRIOR are meaningful only in connection with CONNECT BY.
Action: Check the syntax for the SQL statement and add a CONNECT BY clause, if necessary.
Cause: After executing a statement, an attempt was made to rebind a bind variable with a datatype different from that of the original bind.
Action: Re-parse the cursor before rebinding with a different datatype.
Cause: An expression attempted to divide by zero.
Action: Correct the expression, then retry the operation.
Cause: This is an internal error message not normally issued.
Action: Contact Oracle Support Services.
Cause: User is performing an array bind with a bind variable whose maximum size is greater than 2000 bytes.
Action: Such bind variables cannot participate in array binds. Use an ordinary bind operation instead.
Cause: A bind variable of type 97 does not contain null at the last position.
Action: Make the last character null.
Cause: A bind variable of type 5 (null-terminated string) does not contain the terminating null in its buffer.
Action: Terminate the string with a null character.
Cause: An invalid format parameter was used with the TO_CHAR or TO_NUMBER function.
Action: Correct the syntax, then retry the operation.
Cause: The character set used to perform the operation, such as the CONVERT function, is not a supported character set.
Action: Use one of the supported character sets.
Cause: At attempt was made to bind an array to a non-PL/SQL statement.
Action: Rewrite the offending code being careful to bind arrays only to PL/SQL statements.
Cause: You bound a buffer of type DTYVCS (VARCHAR with the two byte length in front) and at execute time the length in the first two bytes is more than the maximum buffer length, given in the bind call. The number of elements in the array and the current number of elements in the array cannot be more than the maximum size of the array.
Action: Ensure that the buffer size is sufficiently large to contain the array plus two bytes for the buffer length.
Cause: An attempt was made to bind a data value that was either too large for the datatype, for example, NUMBER, or was greater than 2000 bytes, for example, VARCHAR or LONG.
Action: Find a way to convert or truncate the data value so that its length is acceptable.
Cause: A conversion request cannot be performed because the buffer is too small to hold the result.
Action: Increase the size of the buffer.
Cause: A conversion request cannot be performed because a digit was invalid.
Action: Fix the number and retry.
Cause: String concatenation result is more than the maximum size.
Action: Make sure that the result is less than the maximum size.
Cause: The syntax of the ANALYZE command was incorrect.
Action: Check the syntax and enter the command using the correct syntax.
Cause: The CASCADE option should be used only for tables or clusters.
Action: Do not use the CASCADE option in this manner. Check the syntax of the statement and then retry.
Cause: The LIST option can be used only for tables or clusters.
Action: Do not use the LIST option in this manner. Check the syntax of the statement and then retry.
Cause: The specified SAMPLE size is out of range
Action: Specify a value within the proper range.
Cause: The specified histogram SIZE value was out of range.
Action: Specify a value within the proper range.
Cause: The specified table either does not exist or user does not have the proper privileges.
Action: Specify the correct table to use.
Cause: The specified table does not have the proper field definitions.
Action: Specify the correct table to use.
Cause: The FOR COLUMNS column_list clause cannot be used with ANALYZE CLUSTER.
Action: Retry with a legal syntax.
For more information about ANALYZE CLUSTER, see the Oracle9i SQL Reference.
Cause: An error occurred while checking a block with the ANALYZE command.
Action: Check the trace file for more descriptive messages about the problem. Correct these errors. The name of the trace file is operating system-specific, for example, ORAxxxx.TRC. It is found in the directory specified by the initialization parameter USER_DUMP_DEST. If USER_DUMP_DEST is not set, trace files are not created. It may be necessary to re-create the object. See also your operating system-specific Oracle documentation.
Cause: An error occurred when validating an index or a table using the ANALYZE command. One or more entries does not point to the appropriate cross-reference.
Action: Check the trace file for more descriptive messages about the problem. Correct these errors. The name of the trace file is operating system-specific, for example, ORAxxxx.TRC. It is found in the directory specified by the USER_DUMP_DEST initialization parameter. If USER_DUMP_DEST is not set, trace files are not created. It may be necessary to re-create the object. See also your operating system-specific Oracle documentation.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|