ORA-14053: illegal attempt to modify string
in string statement
Cause:
Certain attributes of objects (e.g. tables) may be specified at creation time,
but may not be modified using ALTER statement. Unfortunately, user specified
one of such attributes.
Action:
Ensure that ALTER statement specifies new values only for attributes which may
be changed once an object has been created
ORA-14054: invalid ALTER TABLE TRUNCATE PARTITION
option
Cause:
Name of the partition to be truncated may be followed by DROP STORAGE or REUSE
STORAGE
Action:
Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with
ALTER TABLE TRUNCATE PARTITION
ORA-14055: keyword REBUILD in ALTER INDEX REBUILD
must immediately follow <index name>
Cause:
ALTER INDEX statement contained REBUILD keyword following some index attributes
(e.g. INITRANS.)
Action:
Ensure that keyword REBUILD immediately follows the name of the index being
altered
ORA-14056: partition number string: sum of
PCTUSED and PCTFREE may not exceed 100
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
ORA-14057: partition "string": sum
of PCTUSED and PCTFREE may not exceed 100
Cause:
the sum of PCTUSED and PCTFREE for a partition whose name (explicitly specified
by the user) 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
ORA-14058: partition number string: INITRANS
value must be less than MAXTRANS value
Cause:
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 explcitly or derived from the
default value for the partitioned table or index) is no greater than that of
MAXTRANS
ORA-14059: partition "string":
INITRANS value must be less than MAXTRANS value
Cause:
Value of INITRANS was found to be greater than that of MAXTRANS for a partition
whose name (explicitly specified by the user) 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 explcitly or derived from the
default value for the partitioned table or index) is no greater than that of
MAXTRANS
ORA-14060: data type or length of a table
partitioning column may not be changed
Cause:
User issued ALTER TABLE statement attempting to modify data type and/or length
of a column used to partition the table named in ALTER TABLE statement, which
is illegal
Action:
Avoid modifying data type and/or length of table partitioning column(s)
ORA-14061: data type or length of an index
partitioning column may not be changed
Cause:
User issued ALTER TABLE statement attempting to modify data type and/or length
of a column used to partition some index defined on the table named in ALTER
TABLE statement, which is illegal
Action:
Avoid modifying data type and/or length of index partitioning column(s)
ORA-14062: one or more of table's partitions reside
in a read-only tablespace
Cause:
User issued ALTER TABLE statement attempting to 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 one or more partitions of which reside in read-only
tablespaces, which is illegal
Action:
Avoid performing aformentioned operations on a partitioned table one or more
partitions of which reside in read-only tablespaces
ORA-14063: Unusable index exists on unique/primary
constraint key
Cause:
User attempted to add or enable a primary key/unique constraint on column(s) of
a table on which there exists an index marked Index Unusable.
Action:
Drop the existing index or rebuild it using ALTER INDEX REBUILD
ORA-14064: Index with Unusable partition exists on
unique/primary constraint key
Cause:
User attempted to add or enable a primary key/unique constraint on column(s) of
a table on which there exists an index one or more partitions of which are
marked Index Unusable.
Action:
Drop the existing index or rebuild unusable partitions it using ALTER INDEX
REBUILD PARTITION
ORA-14065: ALLOCATE STORAGE may not be specified
for a partitioned table
Cause:
User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against
a partitioned table which is illegal.
Action:
Remove the illegal option. If it is desired to add storage to individual
partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY
PARTITION statement.
ORA-14066: illegal option for a non-partitioned index-organized
table
Cause:
An attempt was made to issue a CREATE or ALTER TABLE command on a
non-partitioned IOT, but the command contains an option that is legal only for
partitioned index-organized tables. Such options are: ENABLE ROW MOVEMENT and
DISABLE ROW MOVEMENT.
Action:
Remove the illegal option(s) from the command.
ORA-14067: duplicate TABLESPACE_NUMBER
specification
Cause:
TABLESPACE_NUMBER clause was specified more than once for an table, index or an
index partition
Action:
Correct the code generating text of CREATE INDEX statement sent to the slaves
ORA-14068: TABLESPACE and TABLESPACE_NUMBER may not
be both specified
Cause:
Both TABLESPACE and TABLESPACE_NUMBER clauses were specified for a table, index
or an index partition
Action:
Correct the code generating text of CREATE INDEX statement sent to the slaves
ORA-14069: invalid TABLESPACE_NUMBER value
Cause:
The TABLESPACE_NUMBER value is not an integer between 0 and 0x7FFFFFFF
Action:
Correct the code generating text of CREATE INDEX statement sent to the slaves
ORA-14070: option may be specified only for
partitioned indices or with REBUILD
Cause:
User issued ALTER INDEX statament containing an option which is legal only for
partitioned indices or in conjunction with REBUILD against a non-partitioned
index. Such options are: PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL,
FREELISTS, and FREELIST GROUPS inside STORAGE clause
Action:
Remove illegal option(s).
ORA-14071: invalid option for an index used to
enforce a constraint
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.
ORA-14072: fixed table may not be truncated
Cause:
User attempted to truncate a fixed table which is illegal.
Action:
Ensure that the table being truncated is not a fixed table.
ORA-14073: bootstrap table or cluster may not be
truncated
Cause:
User attempted to truncate a bootstrap table or cluster which is illegal
Action:
Ensure that the table (or cluster) being truncated is not a bootstrap table (or
cluster)
ORA-14074: partition bound must collate higher than
that of the last partition
Cause:
Partition bound specified in ALTER TABLE ADD PARTITION statement did not
collate higher than that of the table's last partition, which is illegal.
Action:
Ensure that the partition bound of the partition to be added collates higher
than that of the table's last partition.
ORA-14075: partition maintenance operations may
only be performed on partitioned indices
Cause:
Index named in ALTER INDEX partition maintenance operation is not partitioned,
making a partition maintenance operation, at best, meaningless
Action:
Ensure that the index named in ALTER INDEX statement specifying a partition
maintenance operation is, indeed, partitioned
ORA-14076: submitted alter index
partition/subpartition operation is not valid for local partitioned index
Cause:
User attempted to either drop, split, add or coalesce a partition or a
subpartition of a local index which is illegal.
Action:
Ensure that the index named in such statement is a global partitioned index.
ORA-14078: you may not drop the highest partition
of a GLOBAL index
Cause:
User attempted to drop highest partition of a GLOBAL index, which is illegal.
Action:
Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is
not the highest partition of the index.
ORA-14079: illegal option for a partition marked
Index Unusable
Cause:
ALTER INDEX MODIFY PARTITION statement against an index partition marked Index
Unusable contained STORAGE and/or DEALLOCATE SPACE clauses which is illegal
Action:
Ensure that only valid optins are specified
ORA-14080: partition cannot be split along the
specified high bound
Cause:
User attempted 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 that that of a partition
immediately preceding the one to be split
ORA-14081: new partition name must differ from the
old partition name
Cause:
User entered ALTER TABLE/INDEX RENAME PARTITION specifying
<new-partition-name> which is 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
ORA-14082: new partition name must differ from that
of any other partition of the object
Cause:
User entered ALTER TABLE/INDEX RENAME PARTITION specifying <new-partition-name>
which is 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
ORA-14083: cannot drop the only partition of a
partitioned table
Cause:
A drop partition command is being executed when there is only one partition in
the table
Action:
Ensure that there is at least one partition. Drop table to remove all
partitions
ORA-14084: you may specify TABLESPACE DEFAULT only
for a LOCAL index
Cause:
User attempted to specify TABLESPACE DEFAULT for an object other than a LOCAL
index, which is illegal.
Action:
Reenter the statement without TABLESPACE DEFAULT clause.
ORA-14085: partitioned table cannot have column
with LONG datatype
Cause:
User tried to create a partitioned table with a LONG datatype or tried to add a
LONG datatype column to a partitioned table.
Action:
LONG data types are not supported with partitioned tables. Create table without
LONG column or change table to not partitioned. If adding column, do not use
LONG datatype. If modifying attributes of a column to change data type to LONG,
it has to be a non partitioned table.
ORA-14086: a partitioned index may not be rebuilt
as a whole
Cause:
User attempted to rebuild a partitioned index using ALTER INDEX REBUILD
statement, which is illegal
Action:
Rebuild the index a partition at a time (using ALTER INDEX REBUILD PARTITION)
or drop and recreate the entire index
ORA-14094: invalid ALTER TABLE EXCHANGE PARTITION
option
Cause:
Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING}
INDEX][{WITH|WITHOUT} VALIDATION]
Action:
Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified
with ALTER TABLE EXCHANGE PARTITION
ORA-14095: ALTER TABLE EXCHANGE requires a
non-partitioned, non-clustered table
Cause:
The table in the EXCHANGE operation is either clustered or partitioned
Action:
Ensure that the table with which the partition is being exchanged for is not
partitioned or clustered.
ORA-14096: tables in ALTER TABLE EXCHANGE PARTITION
must have the same number of columns
Cause:
The two tables specified in the EXCHANGE have different number of columns
Action:
Ensure that the two tables have the same number of columns with the same type
and size.
ORA-14097: column type or size mismatch in ALTER
TABLE EXCHANGE PARTITION
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.
ORA-14098: index mismatch for tables in ALTER TABLE
EXCHANGE PARTITION
Cause:
The two tables specified in the EXCHANGE 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.
ORA-14099: all rows in table do not qualify for
specified partition
Cause:
There is at least one row in the non partitioned table which 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.
ORA-14100: partition extended table name cannot
refer to a remote object
Cause:
User attempted to use partition-extended table name syntax in conjunction with
remote object name which is illegal
Action:
Correct the statement and reenter
ORA-14101: partition extended table name cannot
refer to a synonym
Cause:
User attempted to use partition-extended table name syntax in conjunction with
synonym name which is illegal
Action:
Correct the statement and reenter
ORA-14102: only one LOGGING or NOLOGGING clause may
be specified
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.
ORA-14103: LOGGING/NOLOGGING may not be combined
with RECOVERABLE/UNRECOVERABLE
Cause:
A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is
disallowed.
Action:
Remove one of the offending clauses. [UN]RECOVERABLE is being deprecated in V8
and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause,
create an object with NOLOGGING option and then ALTER it specifying LOGGING. To
duplicate semantics of RECOVERABLE clause, create an object with LOGGING
option.
ORA-14104: RECOVERABLE/UNRECOVERABLE may not be
specified for partitioned tables/indices
Cause:
CREATE TABLE/INDEX statement used to create a partitioned table/index contained
RECOVERABLE or UNRECOVERABLE clause which is illegal
Action:
Remove offending clause. [UN]RECOVERABLE is being deprecated in V8 and will be
obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an
object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate
semantics of RECOVERABLE clause, create an object with LOGGING option.
ORA-14105: RECOVERABLE/UNRECOVERABLE may not be
specified in this context
Cause:
RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.
Action:
Remove 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 and
will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create
an object with NOLOGGING option and then ALTER it specifying LOGGING. To
duplicate semantics of RECOVERABLE clause, create an object with LOGGING
option.
ORA-14106: LOGGING/NOLOGGING may not be specified
for a clustered table
Cause:
User attempted to specify LOGGING or NOLOGGING clausein CREATE TABLE or ALTER
TABLE statement involving a clustered table
Action:
Remove offending clause.
ORA-14107: partition specification is required for
a partitioned object
Cause:
parameter which supplies partition name is missing. This parameter is optional
for non-partitioned objects, but is required for partitioned objects.
Action:
supply missing parameter
ORA-14108: illegal partition-extended table name
syntax
Cause:
Partition to be accessed may only be specified using its name. User attempted
to use a partition number or a bind variable.
Action:
Modify statement to refer to a partition using its name
ORA-14109: partition-extended object names may only
be used with tables
Cause:
User attempted 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
ORA-14110: partitioning column may not be of type
ROWID
Cause:
Partitioning column specified by the user was of type ROWID, which is illegal.
Action:
Ensure that no partitioning column is of type ROWID.
ORA-14111: creation of a GLOBAL partitioned index
on clustered tables is not supported
Cause:
An attempt was made to create a GLOBAL partitioned index on a clustered table
which is currently illegal.
Action:
Remove PARTITION BY RANGE/HASH clause along with any partition descriptions to
create a GLOBAL non-partitioned index on a clustered table
ORA-14112: RECOVERABLE/UNRECOVERABLE may not be
specified for a partition or subpartition
Cause:
Description of a partition or subpartition found in CREATE TABLE/INDEX
statement contained RECOVERABLE or UNRECOVERABLE clause which is illegal
Action:
Remove offending clause. Use LOGGING or NOLOGGING instead.
ORA-14113: partitioned table cannot have column
with LOB datatype
Cause:
User tried to create a partitioned table with a LOB datatype or tried to add a
LOB datatype column to a partitioned table.
Action:
LOB data types are not supported with partitioned tables. Create table without
LOB column or change table to not partitioned. If adding 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.
ORA-14114: partitioned table cannot have column
with object, REF, nested table, array datatype
Cause:
User tried to create a partitioned table with a object datatype (object, REF,
nested table, array) or tried to add a object datatype column to a partitioned
table.
Action:
object data types are not supported with partitioned tables. Create table
without object column or change table to not partitioned. If adding 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.
ORA-14115: partition bound of partition number string
is too long
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.
ORA-14116: partition bound of partition "string"
is too long
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.
ORA-14117: partition resides in offlined tablespace
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.
ORA-14118: CHECK constraint mismatch in ALTER TABLE
EXCHANGE PARTITION
Cause:
The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE
PARTITION statement have CHECK constraint defined on them.
Action:
Ensure that the two tables do not have CHECK constraint defined on any column
ORA-14119: specified partition bound is too long
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.
ORA-14120: incompletely specified partition bound
for a DATE column
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.
ORA-14121: MODIFY DEFAULT ATTRIBUTES may not be
combined with other operations
Cause:
ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT
ATTRIBUTES with some other operation (e.g. 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 at will
ORA-14122: only one REVERSE or NOREVERSE clause may
be specified
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.
ORA-14123: duplicate NOREVERSE clause
Cause:
NOREVERSE was specified more than once in ALTER INDEX statement.
Action:
Remove all but one of the NOREVERSE clauses and reissue the statement.
ORA-14124: duplicate REVERSE clause
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.
ORA-14125: REVERSE/NOREVERSE may not be specified
in this context
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.
ORA-14126: only a <parallel clause> may
follow description(s) of resulting partitions
Cause:
Descriptions of partition(s) resulting from splitting of a table or index
partition may be followed by an optional <parallel clause> which applies
to the entire statement and which, in turn, may not be followed by any other
clause.
Action:
Ensure that all partition attributes appear within the parenthesized list of
descriptions of resulting partitions in ALTER TABLE/INDEX SPLIT PARTITION
statement.
ORA-14128: FOREIGN KEY constraint mismatch in ALTER
TABLE EXCHANGE PARTITION
Cause:
The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE
PARTITION statement have different FOREIGN KEY constraints.
Action:
Ensure that the two tables do not have FOREIGN KEY constraints defined on any
column or disable all FOREIGN KEY constraints on both tables. Then retry the
operation.
ORA-14129: INCLUDING INDEXES must be specified as
tables have enabled UNIQUE constraints
Cause:
Matching UNIQUE constraints in both table are enabled and validated but
INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE
PARTITION|SUBPARTITION command.
Action:
Disable currently enabled matching UNIQUE constraints on both tables or ensure
that INCLUDING INDEXES option is used.
ORA-14130: UNIQUE constraints mismatch in ALTER
TABLE EXCHANGE PARTITION
Cause:
One of the tables named in the ALTER TABLE EXCHANGE PARTITION command has a
UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is
defined on the other table or a matching constraint is defined on the other
table, but it differs from that defined on the first table vis-a-vis being enabled
and/or validated.
Action:
Ensure that for every UNIQUE constraint defined on one of the tables named in
the ALTER TABLE EXCHANGE PARTITION statement there is a matching (vis-a-vis key
columns and being enabled and/or validated) UNIQUE constraint defined on the
other table. If UNIQUE constrains are enabled, UNIQUE constraints on the
partitioned table should be enforced using local indexes.
ORA-14131: enabled UNIQUE constraint exists on one
of the tables
Cause:
One of the tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION
statement has enabled UNIQUE constraint(s) defined on it, which prevents
EXCHANGE from proceeding.
Action:
Disable constraints defined on tables referenced in the ALTER TABLE EXCHANGE
PARTITION|SUBPARTITION statement and retry the statement.
ORA-14132: table cannot be used in EXCHANGE
Cause:
An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION
command, but the non-partitioned table cannot be used in the EXCHANGE because
one or more of the following apply:
- it is a typed
table
- it is a
temporary table
- it contains
ADT columns
- it contains
nested-table columns
- it contains
REF columns
- it contains
array columns
- it is an
index-organized table
- it contains
LOB columns
- it is a nested
table
- it is created
with row dependency and the partitioned table is not
- it is created
without row dependency and the partitioned table is
Action:
Make sure the non-partitioned table does not violate any of the above
restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command.
ORA-14133: ALTER TABLE MOVE cannot be combined with
other operations
Cause:
An attempt was made to combine an ALTER TABLE MOVE statement with another
operation, such as MODIFY.
Action:
Make sure that MOVE is the only operation specified in ALTER TABLE statement;
ORA-14134: indexes cannot use both DESC and REVERSE
Cause:
An attempt was made to make a reverse index with some index columns marked
DESC.
Action:
Do not use DESC in reverse indexes. The rule-based optimizer can scan indexes
backwards, which allows a normal reverse index to simulate a reverse index with
columns marked DESC.
ORA-14135: a LOB column cannot serve as a
partitioning column
Cause:
An attempt was made to specify a column of type BLOB or CLOB as a partitioning
or subpartitioning column.
Action:
Ensure that no partitioning or subpartitioning column is of type BLOB or CLOB.
ORA-14136: ALTER TABLE EXCHANGE restricted by
fine-grained security
Cause:
User doing exchange does not have full table access due to VPD policies.
Action:
Grant exempt priviliges to this user.
ORA-14137: Table in partially dropped state, submit
DROP TABLE PURGE
Cause:
An attempt was made to access a partitioned table in a partially dropped state.
Action:
Submit DROP TABLE <table> PURGE to drop the table.
ORA-14138: An unexpected error encountered during
drop table operation
Cause:
Drop table encountered an unexpected error.
Action:
a. Submit drop table <table> purge, or b. If the situation described in
the next error on the stack can be corrected, do so. c. Contact Oracle Support.
ORA-14139: table string.string is
already in read-only mode
Cause:
an attempt was made to set a read-only table in read-only mode
Action:
this DDL can only be executed on a read/write table
ORA-14140: table string.string is
already in read/write mode
Cause:
an attempt was made to set a read/write table in read/write mode
Action:
this DDL can only be executed on a read-only table
ORA-14141: ALTER INDEX VISIBLE|INVISIBLE may not be
combined with other operations
Cause:
ALTER INDEX statement attempted to combine a VISIBLE|INVISIBLE operation with
some other operation which is illegal
Action:
Ensure that VISIBLE|INVISIBLE operation is the sole operation specified in
ALTER INDEX statement
ORA-14142: ALTER INDEX VISIBLE|INVISIBLE may not be
used with certain types of index
Cause:
Using the ALTER INDEX VISIBLE|INVISIBLE statement on certain types of indexes
(IOT-TOP, Cluster indexes) is illegal.
Action:
Remove the option VISIBLE|INVISIBLE.
ORA-14143: CREATE INDEX INVISIBLE may not be used
with this type of index
Cause:
Certain types of indexes (IOT-TOP, Cluster indexes) cannot be created
invisible.
Action:
Remove the option INVISIBLE
ORA-14150: missing SUBPARTITION keyword
Cause:
keyword SUBPARTITION missing
Action:
supply missing keyword
ORA-14151: invalid table partitioning method
Cause:
Invalid partitioning method was specified in CREATE TABLE statement. A table
may be partitioned by RANGE, HASH, LIST, SYSTEM, or Composite
Range-Hash/List/Range (R+H/L/R).
Action:
Specify one of valid partitioning methods
ORA-14152: invalid number of partitions specified
in PARTITIONS clause
Cause:
number-of-partitions clause contained in CREATE TABLE or CREATE INDEX statement
specified a number of partitions outside of legal range (1-1048575)
Action:
Specify a number between 1 and 1024K-1 in the number-of-partitions clause
No hay comentarios:
Publicar un comentario