Release 8.0
A54625_01
 Library |
 Product |
 Contents |
| Oracle8
Error Messages Release 8.0 A54625_01 |
|
Cause: A CREATE INDEX statement was issued that contained more than one LOCAL clause.
Action: Specify the LOCAL option at most once. Then retry the operation.
Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause.
Action: Specify either a LOCAL or a GLOBAL clause, but not both. Then retry the operation.
Cause: A CREATE INDEX statement contained more than one GLOBAL clause.
Action: Specify the GLOBAL option at most once. Then retry the operation.
Cause: A CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause.
Action: Specify a GLOBAL or a LOCAL clause, but not both. Then retry the operation.
Cause: A statement was issued which was missing the keyword PARTITION.
Action: Supply the missing keyword and retry the operation.
Cause: A statement was issued which was missing the keyword RANGE.
Action: Supply the missing keyword and retry the operation.
Cause: A partition name of the form name is expected but not present.
Action: Enter an appropriate partition name. Then retry the operation.
Cause: A statement was issued which was missing the keyword LESS.
Action: Supply the missing keyword. Then retry the operation.
Cause: A statement was issued which was missing the keyword THAN.
Action: Supply the missing keyword. Then retry the operation.
Cause: While parsing a CREATE INDEX statement to create a LOCAL partitioned index, one of partitions was found to contain a VALUES LESS THAN clause which is illegal since a LOCAL index inherits partition bounds from its base table.
Action: Remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions.
Cause: An unexpected option was encountered while parsing physical attributes of an index partition; valid options are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE. This message could also have resulted from omission of a terminating (right) parenthesis following the list of partition descriptions.
Action: Remove invalid option(s) from the list of physical attributes of an index partition.
Cause: The names given to partitions resulting from the splitting of an existing table or index partition were not distinct.
Action: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.
Cause: Name of a partition resulting from splitting of an existing table or index partition was given a name identical to that of some other existing partition of that table or index.
Action: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.
Cause: Name given to a partition of a table or index being created was not unique.
Action: Rename partition(s) to ensure that their names are unique among partitions of the table or index being created.
Cause: The number of columns in a partitioning column list exceeded the legal limit of 16.
Action: Modify the partitioning column list so that it consists of at most 16 columns.
Cause: CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 2**32-1 (65535).
Action: Reduce the number of partitions so that they do not exceed 2**32-1 (65535).
Cause: An attempt was made to create a LOCAL partitioned index on a non-partitioned table. Only GLOBAL indices (partitioned or otherwise) can be created on a non-partitioned table.
Action: Correct the statement and retry the operation.
Cause: A partition bound list contained more elements than there are partitioning columns.
Action: Ensure that the number of elements in the partition bound list is equal to the number of partitioning columns of the table or index. Then retry the operation.
Cause: Partition bound list contained fewer elements than there are partitioning columns.
Action: Ensure that the number of elements in the partition bound list is equal to the number of partitioning columns of the table or index.
Cause: Partition bound list contained an element of invalid type (that is, not a number, non-empty string literal, or MAXVALUE).
Action: Ensure that all elements of partition bound list are of valid type.
Cause: An unexpected option was encountered while parsing physical attributes of a table partition; valid options are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED. This error also could have resulted from the omission of a terminating (right) parenthesis following the list of partition descriptions.
Action: Remove invalid option(s) from the list of physical attributes of a table partition.
Cause: In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE was not specified for all columns.
Action: Ensure that the VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns.
Cause: An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal.
Action: Remove LOCAL along with partition descriptions, if any, from the CREATE INDEX statement.
Cause: An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal.
Action: Remove PARTITION BY RANGE clause along with partition descriptions from the CREATE INDEX statement.
Cause: An attempt was made to create a LOCAL partitioned index with a number of partitions which is different from that of the underlying table.
Action: Correct the CREATE INDEX statement to specify a correct number of partitions and retry the operation.
Cause: PARTITION option was encountered while parsing a definition of a snapshot or a snapshot log.
Action: Ensure that the definition of a SNAPSHOT does not include invalid options and retry the operation.
Cause: The definition of a table contained both PARTITION and CLUSTER clauses which is illegal.
Action: Remove one of the conflicting clauses and retry the operation.
Cause: A CREATE TABLE statement contained more than one PARTITION clause.
Action: Specify the PARTITION option at most once and retry the operation.
Cause: A statement was issued that was missing the keyword AT.
Action: Supply the missing keyword and retry the operation.
Cause: The partitioning columns of a global partitioned index did not contain a prefix of the index's key columns.
Action: Ensure that the GLOBAL partitioned index being created is prefixed and retry the operation.
Cause: The partitioning column specified in the CREATE TABLE statement is not one of columns of the table being created.
Action: Ensure that all columns in the partitioning column list are columns of the table being created. Then retry the operation.
Cause: The partitioning column specified was of type LONG or LONG RAW, which is illegal.
Action: Ensure that no partitioning column is of type LONG or LONG RAW. Then retry the operation.
Cause: High bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message did not collate lower than that of the following partition, which is illegal.
Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition. Then retry the operation.
Cause: Length of partition bound value is longer than that of the corresponding partitioning column.
Action: Ensure that lengths of the high bound values do not exceed those of corresponding partitioning columns. Then retry the operation.
Cause: High bound of the partition whose name (explicitly specified by the user) is displayed in this message did not collate lower than that of the following partition, which is illegal.
Action: Ensure that the high bound of every partition (except for the last one) collates lower than that of a following partition.
Cause: An attempt was made to create a GLOBAL non-prefixed partitioned index which is illegal.
Action: If a non-prefixed index is desired, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed. Then retry the operation.
Cause: An attempt was made to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns.
Action: If an index whose partitioning columns do not form a subset of its key columns is indeed desired, it must be created as non-UNIQUE; otherwise, correct the list of key and/or partitioning columns to ensure that the index's partitioning columns form a subset of its key columns. Then retry the operation.
Cause: While parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, a resulting partition was found to contain a VALUES LESS THAN clause which is illegal.
Action: Remove the VALUES LESS THAN clause from the description(s) of partitions which result from splitting an existing table or index partition. Then retry the operation.
Cause: While parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement, the description of new physical attributes of the partition being moved, modified, or rebuilt was found to contain VALUES LESS THAN clause which is illegal.
Action: Remove the VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt. Then retry the operation.
Cause: The ALTER TABLE ADD PARTITION statement contained descriptions of more than one partition to be added.
Action: Ensure that the statement contains exactly one partition definition and that it does not contain any commas. Then retry the operation.
Cause: The ALTER TABLE MOVE PARTITION statement contained descriptions of more than one partition to be moved.
Action: Ensure that the statement describes exactly one partition to be moved and that it does not contain any commas. Then retry the operation.
Cause: The ALTER TABLE|INDEX MODIFY PARTITION statement contained descriptions of more than one partition to be modified.
Action: Ensure that the statement describes exactly one partition to be modified and that it does not contain any commas.
Cause: The ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two new partitions into which an existing table or index partition was to be split.
Action: Ensure that the statement describes exactly two partition into which an existing partition is to be split. Then retry the operation.
Cause: The ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation, which is illegal.
Action: Ensure that RENAME operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement. Then retry the operation.
Cause: The ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (for example, MOVE PARTITION) with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.
Action: Ensure that a partition maintenance operation is the sole operation specified in an ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices, or specifying that a table be renamed (ALTER TABLE RENAME) can be combined.
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was specified in an ALTER TABLE MODIFY PARTITION statement.
Action: Specify only legal options, then retry the operation.
Cause: An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY PARTITION statement.
Action: Specify only legal options, then retry the operation.
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER SNAPSHOT statement.
Action: Specify only legal options, then retry the operation.
Cause: An attempt was made to use partition-extended table name syntax in illegal context (that is, not in a FROM-clause or INSERT, DELETE, or UPDATE statement).
Action: Avoid use of partition-extended table name in contexts other than those mentioned above.
Cause: An attempt was made to modify an attribute (for example, a table) with the ALTER statement at creation time.
Action: Ensure that ALTER statement specifies new values only for attributes which can be changed after an object has been created.
Cause: An attempt was made to specify an invalid option following the partition name in the ALTER TABLE TRUNCATE PARTITION statement. The name of the partition to be truncated can be followed only by DROP STORAGE or REUSE STORAGE.
Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION.
Cause: The ALTER INDEX statement contained the REBUILD keyword following an index attribute (for example, INITRANS).
Action: Ensure that the keyword REBUILD immediately follows the name of the index being altered.
Cause: The sum of PCTUSED and PCTFREE for a partition whose number (partitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used.
Action: Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100. Then retry the operation.
Cause: The sum of PCTUSED and PCTFREE for a partition whose name is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used.
Action: Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100. Then retry the operation.
Cause: The value of INITRANS was found to be greater than that of MAXTRANS for a partition whose number (partitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used.
Action: Ensure that value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS. Then retry the operation.
Cause: The value of INITRANS was found to be greater than that of MAXTRANS for a partition whose name is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used.
Action: Ensure that value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS.
Cause: An attempt was made to use the ALTER TABLE statement to modify data type and/or length of a column used to partition the table named in the ALTER TABLE statement.
Action: Avoid modifying data type and/or length of table partitioning column(s).
Cause: An attempt was made to use the ALTER TABLE statement to modify data type and/or length of a column used to partition some index defined on the table named in the ALTER TABLE statement.
Action: Avoid modifying the data type and/or length of index partitioning column(s).
Cause: An attempt was made to use the ALTER TABLE statement modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table that has one or more partitions residing in read-only tablespaces.
Action: Avoid performing these operations on a partitioned table that has one or more partitions residing in read-only tablespaces.
Cause: An attempt was made to add or enable a primary key/unique constraint on column(s) of a table that has an index marked Index Unusable.
Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD.
Cause: An attempt was made to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index that has one or more partitions marked Index Unusable.
Action: Drop the existing index or rebuild unusable partitions it using ALTER INDEX REBUILD PARTITION.
Cause: An attempt was made to specify an ALLOCATE STORAGE clause in an ALTER TABLE statement issued against a partitioned table.
Action: Remove the ALLOCATE STORAGE option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION statement.
Cause: An attempt was made to issue an ALTER TABLE statement containing an option (such as TABLESPACE and INITIAL, FREELISTS, and FREELIST GROUPS inside STORAGE clauses) for a non-partitioned table. These options are permitted only for partitioned tables.
Action: Remove the illegal option(s) and retry the operation.
Cause: A TABLESPACE_NUMBER clause was specified more than once for an index or an index partition.
Action: Correct the code generating text of the CREATE INDEX statement sent to the slaves, then retry the operation.
Cause: An attempt was made to specify both TABLESPACE and TABLESPACE_NUMBER clauses for an index or an index partition.
Action: Correct the code generating text of the CREATE INDEX statement sent to the slaves, then retry the operation.
Cause: An attempt was made to specify a TABLESPACE_NUMBER value which is not an integer between 0 and 0x7FFFFFFF.
Action: Correct the code generating text of the CREATE INDEX statement sent to the slaves, then retry the operation.
Cause: An attempt was made to issue an ALTER INDEX statement containing an option (such as PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS, and FREELIST GROUPS inside STORAGE clause) which are permitted only for partitioned indices or in conjunction with REBUILD.
Action: Remove illegal option(s) and retry the operation.
Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified for an index used to enforce a constraint.
Action: Choose one of the valid index options and retry the operation.
Cause: An attempt was made to truncate a fixed table. Fixed tables cannot be truncated.
Action: Ensure that the table being truncated is not a fixed table.
Cause: An attempt was made to truncate a bootstrap table or cluster. Bootstrap tables or clusters cannot be truncated.
Action: Ensure that the table (or cluster) being truncated is not a bootstrap table (or cluster).
Cause: Partition bound for SPLIT or ADD partition operation did not collate higher than the partition bound of previous partition.
Action: Ensure that the partition bound of every partition (except the first one) collates higher than that of the previous partition.
Cause: The index named in the ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation meaningless.
Action: Ensure that the index named in the ALTER INDEX statement specifying a partition maintenance operation is partitioned.
Cause: An attempt was made to drop or split a partition of a LOCAL index.
Action: Ensure that the index named in the DROP/SPLIT PARTITION statement is a GLOBAL partitioned index.
Cause: An attempt was made to perform a partition maintenance operation involving a non-existent partition.
Action: Ensure that the partitioned object (table or index) named in the ALTER TABLE/INDEX statement contains a specified partition.
Cause: An attempt was made to drop highest partition of a GLOBAL index.
Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is not the highest partition of the index.
Cause: The ALTER INDEX MODIFY PARTITION statement issued against an index partition marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses.
Action: Ensure that only valid options are specified, then retry the operation.
Cause: An attempt was made to split a partition along a bound which either collates higher than that of the partition to be split, or lower than that of a partition immediately preceding the one to be split.
Action: Ensure that the bound along which a partition is to be split collates lower than that of the partition to be split and higher than that of a partition immediately preceding the one to be split.
Cause: An attempt was made to enter a ALTER TABLE/INDEX RENAME PARTITION statement specifying a partition name identical to the name of the partition being renamed.
Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index.
Cause: An attempt was made to enter a ALTER TABLE/INDEX RENAME PARTITION statement specifying a partition name identical to the name of some existing partition of the object.
Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index.
Cause: A drop partition command was executed when there is only one partition in the table.
Action: Ensure that there is more than one partition. Drop the table to remove all partitions.
Cause: An attempt was made to specify TABLESPACE DEFAULT for an object other than a LOCAL index.
Action: Reenter the statement without the TABLESPACE DEFAULT clause.
Cause: An attempt was made either to create a partitioned table with a LONG datatype or to add a LONG datatype column to a partitioned table.
Action: LONG data types are not supported with partitioned tables. Create a table without the LONG column or change the table to not-partitioned. If adding a column, do not use the LONG datatype. If modifying attributes of a column to change data type to LONG, it has to be a non-partitioned table.
Cause: An attempt was made to rebuild a partitioned index using the ALTER INDEX REBUILD statement.
Action: Rebuild the index one partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and recreate the entire index.
Cause: Name of the table to be EXCHANGED was not followed by the [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION] statement.
Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE PARTITION.
Cause: An attempt was made to perform the EXCHANGE operation on a clustered or partitioned table.
Action: Ensure that the table being exchanged with the partition is not partitioned or clustered.
Cause: The two tables specified in the EXCHANGE statement have a different number of columns.
Action: Ensure that the two tables have the same number of columns with the same type and size.
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION are of different type or size.
Action: Ensure that the two tables have the same number of columns with the same type and size.
Cause: The two tables specified in the EXCHANGE statement have indexes which are not equivalent.
Action: Ensure that the indexes for the two tables have indexes which follow this rule: for every non-partitioned index for the non-partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same.
Cause: It was detected that at least one row in the non-partitioned table does not qualify for the partition specified in the ALTER TABLE EXCHANGE PARTITION.
Action: Ensure that all the rows in the segment qualify for the partition. Perform the ALTER TABLE operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that partition to find out the invalid rows and delete them.
Cause: An attempt was made to use partition-extended table name syntax in conjunction with a remote object name.
Action: Correct the statement and retry the operation.
Cause: An attempt was made to use partition-extended table name syntax in conjunction with a synonym name.
Action: Correct the statement and retry the operation.
Cause: LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified.
Action: Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement.
Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is not allowed.
Action: Remove one of the offending clauses. [UN]RECOVERABLE is being deprecated in V8. To duplicate the semantics of the UNRECOVERABLE clause, create an object with the NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with the LOGGING option.
Cause: The CREATE TABLE/INDEX statement used to create a partitioned table/index contained a RECOVERABLE or UNRECOVERABLE clause.
Action: Remove the offending clause. [UN]RECOVERABLE is being deprecated in V8. To duplicate the semantics of the UNRECOVERABLE clause, create an object with the NOLOGGING option and then ALTER it specifying LOGGING. To duplicate the semantics of the RECOVERABLE clause, create an object with the LOGGING option.
Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.
Action: Remove the offending clause. RECOVERABLE/UNRECOVERABLE may only be specified in CREATE TABLE/INDEX statement describing a non-partitioned table or index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being deprecated in V8. To duplicate the semantics of the UNRECOVERABLE clause, create an object with the NOLOGGING option and then ALTER it specifying LOGGING. To duplicate the semantics of the RECOVERABLE clause, create an object with the LOGGING option.
Cause: An attempt was made to specify a LOGGING or NOLOGGING clause in a CREATE TABLE or ALTER TABLE statement involving a clustered table.
Action: Remove offending clause and retry the operation.
Cause: A parameter which supplies the partition name was not entered. This parameter is optional for non-partitioned objects, but is required for partitioned objects.
Action: Supply the missing parameter and retry the operation.
Cause: An attempt was made to use a partition number or a bind variable. A partition to be accessed can only be specified using its name.
Action: Modify the statement so that the partition is referred to by its name.
Cause: An attempt was made to use a partition-extended object name with an object which is not a table.
Action: Avoid using partition-extended name syntax with objects which are not tables.
Cause: The specified partitioning column was of type ROWID.
Action: Ensure that no partitioning column is of type ROWID, then retry the operation.
Cause: An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal.
Action: Remove PARTITION BY RANGE() clause along with the partition-list to create a GLOBAL non-partitioned index on a clustered table.
Cause: Description of a partition found in CREATE TABLE/INDEX statement contained a RECOVERABLE or UNRECOVERABLE clause.
Action: Remove the offending clause. Use LOGGING or NOLOGGING instead and retry the operation.
Cause: An attempt was made either to create a partitioned table with a LOB datatype or to add a LOB datatype column to a partitioned table.
Action: LOB data types are not supported with partitioned tables. Create table without the LOB column or change the table to non-partitioned. If adding a column, do not use LOB datatype. If modifying attributes of a column to change data type to LOB, it has to be a non-partitioned table.
Cause: An attempt was made either to create a partitioned table with an OBJECT datatype (ADT, REF, nested table, array) or to add an OBJECT datatype column to a partitioned table.
Action: Object data types are not supported with partitioned tables. Create the table without the Object column or change the table to non-partitioned. If adding a column, do not use OBJECT datatypes. If modifying attributes of a column to change data type to OBJECT, it has to be a non-partitioned table.
Cause: Length of linear key representation of a high bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message exceeded the legal limit (4K).
Action: Change representation of a partition high bound to bring its length within legal limit.
Cause: Length of linear key representation of a high bound of the partition whose name (explicitly specified by the user) is displayed in this message exceeded the legal limit (4K).
Action: Change representation of a partition high bound to bring its length within legal limit.
Cause: User attempted an operation requiring that we access data in a partition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.
Action: Bring tablespace online before attempting the operation.
Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION have different CHECK constraint.
Action: Ensure that the two tables do not have CHECK constraint defined on any column.
Cause: Length of a linear key representation of a high bound of a table partition being added or along which an existing table or index partition is being split exceeded the legal limit (4K).
Action: Change representation of a partition high bound to bring its length within legal limit.
Cause: An attempt was made to use a date expression whose format does not fully (i.e. day, month, and year (including century)) specify a date as a partition bound for a DATE column. The format may have been specified explicitly (using TO_DATE() function) or implicitly (NLS_DATE_FORMAT).
Action: Ensure that date format used in a partition bound for a DATE column supports complete specification of a date (i.e. day, month, and year (including century)). If NLS_DATE_FORMAT does not support complete (i.e. including the century) specification of the year, use TO_DATE() (e.g. TO_DATE('01-01-1999', 'MM-DD-YYYY') to fully express the desired date.
Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.
Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices, or specifying that a table be renamed (ALTER TABLE RENAME) may be combined.
Cause: Both REVERSE and NOREVERSE were specified in CREATE INDEX statement..
Action: Remove all but one of the REVERSE or NOREVERSE clauses and reissue the statement.
Cause: NOREVERSE was specified more than once in ALTER INDEX statement.
Action: Remove all but one of the NOREVERSE clauses and reissue the statement.
Cause: REVERSE was specified more than once in ALTER INDEX or CREATE INDEX statements.
Action: Remove all but one of the REVERSE clauses and reissue the statement.
Cause: REVERSE/NOREVERSE clause is not allowed in this context.
Action: Remove offending clause. REVERSE may be specified as an attribute of an index (not of an individual partition, if creating a partitioned index) in CREATE INDEX statement and ALTER INDEX REBUILD statement. NOREVERSE may be specified only in ALTER INDEX REBUILD statement.
Cause: The concatenated partition key of an inserted record was found to be beyond the concatenated partition bound list of the last partition.
Action: Either do not insert the key or add a partition capable of accepting the key.
Cause: The concatenated partition key of an inserted record was found to be outside the ranges of the two concatenated partition bound lists that delimit the partition named in the INSERT statement.
Action: Either do not insert the key or else insert it in another partition.
Cause: An UPDATE statement attempted to change the value of a partition key column.
Action: Either do not attempt to update a partition key column or else make sure that the new column value is equal to the old column value.
Cause: Cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement. This error is never returned to user, because is caught in opiexe() and the DML statement is retried.
Action: Nothing need be done, error should never be returned to user.
Cause: An attempt was made to drop a tablespace which contains tables whose partitions are not completely contained in this tablespace.
Action: Find tables with partitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move partitions to a different tablespace.
Cause: An attempt was made to drop a tablespace which contains indexes whose partitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace.
Action: Find indexes with partitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them.
Cause: Incorrect syntax was specified for the LOCAL option.
Action: Enter a partition name for the LOCAL option and retry the command.
Cause: The table or index was not partitioned. Invalid syntax.
Action: Retry the command with correct syntax.
Cause: An attempt was made to specify a partition which does not exist for the object.
Action: Specify a valid partition name and retry the operation.
Cause: More than one partition name has been specified for the ANALYZE option.
Action: Specify one partition name and retry the operation.
Cause: A partition number or bind variable has been used for the ANALYZE option.
Action: Specify a valid partition name.
Cause: Incorrect syntax was specified for the LOCAL option.
Action: Correct the syntax by specifying a partitioned index and retry the command.
Cause: Incorrect syntax was specified for the partitioned index.
Action: Correct the syntax by specifying the LOCAL option and retry the command.
Cause: The partition contained rows which should be in some other partition. This was possibly due to an exchange partition without validation.
Action: Delete rows in partition which fall outside the partition bounds.
Cause: The specified table either does not exist or the user does not have the proper privileges.
Action: Specify the correct table to use or obtain the proper privileges.
Cause: The specified table does not have the proper field definitions.
Action: Specify the correct table to use and retry the operation.
Cause: The VALIDATE INTO has been specified for a non-partitioned table, cluster or index.
Action: Use the VALIDATE INTO clause only for a partitioned table and retry the operation.
Cause: The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error.
Action: In order to modify the database, it must first be shut down and re-opened for read-write access.
Cause: The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance.
Action: This instance must be opened for read-write access, or all other instances must first be shut down and re-opened for read-only access.
Cause: The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance.
Action: This instance must be opened for read-only access, or all other instances must first be shut down and re-opened for read-write access.
Cause: The device block size returned by sequential I/O OSD is invalid.
Action: Correct the block size and retry the operation.
Cause: A read error was detected on the input file.
Action: Check that the file is not corrupt and retry the operation.
Cause: A write error was detected on the output file.
Action: Check that the file is not corrupt and retry the operation.
Cause: A call to get device information returned an error. Most likely one or more of the following was entered incorrectly: device name, type, parameters.
Action: Check that the device name, type, and parameters are correct and retry the operation.
Cause: A call to create file returned an error.
Action: Check additional messages and access permissions, make the necessary corrections, then retry the operation.
Cause: A call to identify the file returned an error. Most likely the filename was entered incorrectly or the file does not exist.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Check if the file exists, then retry the operation.
Cause: A call to create the sequential file returned an error. Most likely the access permissions were set incorrectly.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Check access permissions and correct if necessary. Then retry the operation.
Cause: A call to retrieve the sequential file returned an error. Most likely the filename was entered incorrectly or the file does not exist.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Check if the filename was entered correctly and that the file exists. Then retry the operation.
Cause: A call to delete the file returned an error. Most likely the filename was entered incorrectly or the file does not exist.
Action: One or more other messages should be displayed to help pinpoint the cause of the error.
Cause: A call to delete the sequential file returned an error.
Action: One or more other messages should be displayed to help pinpoint the cause of the error.
Cause: A call to resize the file returned an error.
Action: One or more other messages should be displayed to help pinpoint the cause of the error.
Cause: Attempted to use BACKUP/RESTORE functions while connected to the dispatcher in a multi-threaded server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.
Action: Connect directly to the instance then re-execute the BACKUP or RESTORE function.
Cause: The indicated device could not be allocated because it is allocated to another session, or no device was named, or all devices of the requested type are busy.
Action: Either attempt to allocate another device or wait until the required device is no longer busy.
Cause: The device type indicated is invalid.
Action: Supply a correct device type and retry the allocation.
Cause: The device name indicated is invalid.
Action: Supply a correct device name and retry the allocation.
Cause: The specified device could not be allocated.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
Cause: The initialization parameter LOG_ARCHIVE_MIN_SUCCEED_DEST is not within the valid range.
Action: Specify a correct value. If the database is in ARCHIVELOG mode with automatic archiving enabled, LOG_ARCHIVE_MIN_SUCCEED_DEST should be either 1 or 2.
Cause: LOG_ARCHIVE_DUPLEX_DEST has been disabled possibly due to failure to archive to that destination.
Action: Either
Cause: An error occurred in the platform-specific device code.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
Cause: The specified device could not be de-allocated.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
Cause: An error occurred while sending the indicated command to the session device.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.
Cause: An invalid type of device limit was specified in a call to X$DBMS_BACKUP_RESTORE.SETLIMIT.
Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL.
Cause: The attempted datafile, archivelog, or controlfile copy requires that a null device be allocated to the session, but a non-null device was found.
Action: Deallocate the current device and allocate a null device to the session, then retry the copy.
Cause: The indicated file, which is an archivelog, controlfile, or datafile was found to be empty during a copy, scan, or backup operation.
Action: Ensure that the correct files are being specified for the copy or backup operation.
Cause: When opening the file to be placed in a copy or backup set, or to be inspected, the header was not recognized as a valid file header for a file of the indicated type (datafile, archivelog, or controlfile), belonging to the current database, or perhaps the file does belong to the current database but has been changed since it was specified for inclusion in the backup set.
Action: Ensure that the correct files are being specified for the copy or backup operation.
Cause: An error occurred while writing to a file.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation.
Cause: The user-specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup.
Action: None. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt.
Cause: An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied.
Action: Retry the resize after the backup or copy is complete.
Cause: An attempt was made to allocate a device to a session while another device is already allocated.
Action: Deallocate the current device and retry the operation.
Cause: An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated.
Action: Allocate a device then retry the operation.
Cause: A file number used in a COPY, BACKUP, or RESTORE operation is not valid for the current database.
Action: Specify a valid file number and retry the operation.
Cause: The input file specified for a COPY or BACKUP operation could not be opened because the record describing the file is not found in the controlfile.
Action: Specify a correct recid/stamp and retry the copy or backup.
Cause: The input file specified for a COPY or BACKUP operation could not be opened because the file is being resized.
Action: Wait for the resize to complete then retry the copy or backup.
Cause: The file access enqueue could not be obtained for a file specified in a COPY or BACKUP operation. If the enqueue type shown is "shared", then the file is the input file for a backup or copy. If the type is "exclusive", then the file is the output file for a datafile copy or restore which is attempting to overwrite the currently active version of that file. In this case, the file must be offline or the database must be closed.
Action: Wait until the conflicting operation is complete, then retry the COPY or BACKUP.
Cause: This type of COPY or RESTORE requires an output file name.
Action: Specify an output filename and retry the operation.
Cause: During a BACKUP, RESTORE, COPY or SCAN operation, the indicated file did not contain as many blocks as were indicated in the file header.
Action: The input copy or backup piece is probably corrupt. If another backup or copy of the file that is being restored exists, then the corrupt file can be deleted from the recovery catalog and the operation can be restarted.
Cause: The specified file number was not found in the control file.
Action: Specify a correct file number and retry the operation.
Cause: A copyDataFileCopy or restoreDataFileTo function specified a file number but no output file name, indicating that the output filename should be taken from the controlfile. However, the controlfile entry for this file indicates that it was created for a file that was present in the data dictionary but not named during the last CREATE CONTROLFILE statement, so the name in the controlfile cannot be used for restoration.
Action: Either specify an output filename or issue a SQL RENAME command to enter a valid name for this file in the controlfile.
Cause: A BACKUP or RESTORE operation was attempted before a conversation was started.
Action: Start a conversation then retry the operation.
Cause: An attempt was made to proceed from the file naming phase to the piece processing phase of a BACKUP or RESTORE conversation before any files have been specified for BACKUP or RESTORE.
Action: Specify some files then retry the operation.
Cause: An error occurred which forced the termination of the current BACKUP or RESTORE conversation.
Action: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation.
Cause: The indicated file, which was specified as the target for a COPY or RESTORE operation is already in use by the database.
Action: Specify a different name and retry the COPY or RESTORE operation.
Cause: While creating the indicated backup piece, an end-of-volume condition was encountered before all of the backup set control data was written to the backup piece. This is most likely a media error, because the amount of backup set control data is very small in relation to the total amount of data in a backup set.
Action: Retry the piece with a larger piece of output media.
Cause: The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data.
Action: Use the SETLIMIT procedure to increase the k-byte limit and retry the operation.
Cause: An error occurred while reading from a file.
Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the COPY, BACKUP, or RESTORE operation.
Cause: The indicated record has been marked as deleted. This indicates that the corresponding file has either been overwritten by another copy or restore, or that the copy was "consumed" by a switchToCopy operation.
Action: If you know the name of the file you want to copy, then inspect it and then retry the copy specifying the new recid.
Cause: The controlfile that is the source for a backup or copy operation is not a SNAPSHOT or BACKUP controlfile.
Action: Specify the name of a SNAPSHOT or BACKUP controlfile.
Cause: You tried to begin a BACKUP or RESTORE conversation, but another conversation is already active in this session.
Action: Either continue the current conversation, or call backupCancel or restoreCancel to end the current conversation before starting a new one.
Cause: An attempt was made to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, an attempt was made to specify an archived log to be included in a datafile backup set. The specified file will not be included in the BACKUP or RESTORE operation.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: This datafile is already specified for inclusion in this BACKUP or RESTORE conversation. A BACKUP or RESTORE conversation may process only a single instance of a datafile.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: The controlfile is already specified for inclusion in this BACKUP or RESTORE conversation. A BACKUP or RESTORE conversation may process only a single instance of the controlfile.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: The indicated archivelog has already been specified for inclusion in this backup conversation. A backup conversation may process only one copy of any archivelog.
Action: No action required - the conversation is still active, and more files can be specified.
Cause: An attempt was made to request that the snapshot controlfile be included in the backup set, but no snapshot controlfile has been created for this instance.
Action: Specify a different controlfile name, or call cfileMakeAndUseSnapshot to create the snapshot controlfile.
Cause: A file was specified for inclusion in a backup set but it has a logical block size different from the rest of the files in the backup set. All files in a backup set must have the same logical block size.
Action: Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified.
Cause: No starting SCN was specified to backupDataFile or backupDataFileCopy, but the current backup conversation is for an incremental backup, which requires that a non-zero SCN be specified for all datafiles.
Action: The conversation is still active. Re-specify the datafile with a non-zero SCN.
Cause: A corrupt block was found in a controlfile, archivelog, or backup piece that is being read for a backup or copy. Corruption is not allowed in controlfiles, archivelogs, or backup pieces.
Action: None. The COPY or BACKUP operation fails. Note that in the case of a backup set, the conversation is still active and the piece may be retried.
Cause: This message identifies the input file for a failed copy operation. Both the file number and name (if the name has been determined) are shown.
Action: Other messages should display to help pinpoint the cause and the solution.
|
 Copyright © 1997 Oracle Corporation. All Rights Reserved. |
|
