Erreurs ORA 13900 à 14099 Cause et Action
LISTE CODE ERREURS ORACLE.
|
ORA-13900
|
ORA-13900: missing or invalid parameter string
|
|
Cause
|
A call to SET_THRESHOLD procedure was either missing a parameter, or the parameter was invalid.
|
|
Action
|
Specify a valid value for this parameter.
|
|
ORA-13901
|
ORA-13901: Object string was not found.
|
|
Cause
|
An object name was passed to SET_THRESHOLD procedure that did not map to a valid object.
|
|
Action
|
Specify a valid object name.
|
|
ORA-13902
|
ORA-13902: The specified file string is not a data file.
|
|
Cause
|
The object name was passed to a SET_THRESHOLD procedure that did not map to a valid data file.
|
|
Action
|
Specify a valid data file name.
|
|
ORA-13903
|
ORA-13903: Invalid combination of string threshold value and operator.
|
|
Cause
|
A non-positive number was used for "Blocked User Session Count" metrics while operator contains equal.
|
|
Action
|
Use a positive number for the threshold value or use "greater than" operator.
|
|
ORA-13904
|
ORA-13904: The file has been dropped and recreated during the procedure call.
|
|
Cause
|
The file on which threshold is specified was dropped and recreated during the procedure call.
|
|
Action
|
Retry this operation.
|
|
ORA-13905
|
ORA-13905: Critical or warning threshold have incorrect values
|
|
Cause
|
The tablespace threshold values can be in the range 0 to 100 only.
|
|
Action
|
Check the threshold values
|
|
ORA-13906
|
ORA-13906: The tablepace is not of the right type.
|
|
Cause
|
An attempt was made to set a threshold on dictionary-managed tablespaces.
|
|
Action
|
Check the tablespace type and reissue the command.
|
|
ORA-13907
|
ORA-13907: Threshold value is invalid.
|
|
Cause
|
An attempt was made to specify an invalid value for critical or warning thresholds.
|
|
Action
|
Use non-negative integers only for threshold values.
|
|
ORA-13908
|
ORA-13908: Invalid combination of metrics id and object type parameters.
|
|
Cause
|
An attempt was made to specify an invalid combination of metrics id // and object type parameters.
|
|
Action
|
Specify a valid combination of metrics id and object type parameters.
|
|
ORA-13909
|
ORA-13909: Invalid combination of threshold value and operator.
|
|
Cause
|
An attempt was made to specify an invalid combination of threshold value and operator.
|
|
Action
|
Check the operator and threshold values and reissue statement.
|
|
ORA-13910
|
ORA-13910: Parameter string cannot be NULL.
|
|
Cause
|
An attempt was made to call GET_THRESHOLD procedure without a required parameter.
|
|
Action
|
Specify a valid value for this parameter.
|
|
ORA-13911
|
ORA-13911: Threshold not found
|
|
Cause
|
The threshold did not exist with the specified threshold key.
|
|
Action
|
No action required.
|
|
ORA-13912
|
ORA-13912: Critical threshold value is less than warning threshold value.
|
|
Cause
|
An attempt was made to call SET_THRESHOLD procedure with the critical threshold value less than the warning threshold value.
|
|
Action
|
Check the threshold values and reissue the statement.
|
|
ORA-13913
|
ORA-13913: The threshold cannot be set when SYSAUX is offline.
|
|
Cause
|
SET_THRESHOLD procedure was called when SYSAUX tablespace was offline.
|
|
Action
|
Call SET_THRESHOLD procedure when SYSAUX is online.
|
|
ORA-13914
|
ORA-13914: Threshold notification failed.
|
|
Cause
|
An error occurred when sending notification for this threshold.
|
|
Action
|
Make sure you have enough space on SYSAUX tablespace and retry this operation.
|
|
ORA-13915
|
ORA-13915: Critical byte based free space threshold value is greater than warning threshold value.
|
|
Cause
|
An attempt was made to call SET_THRESHOLD procedure with the bytes based critical threshold value greater than the warning threshold value.
|
|
Action
|
Check the threshold values and reissue the statement.
|
|
ORA-13916
|
ORA-13916: Invalid value "string" specified for parameter "string"
|
|
Cause
|
An invalid value was specified for the the given parameter.
|
|
Action
|
Correct the value being specified for the parameter.
|
|
ORA-13917
|
ORA-13917: Posting system alert with reason_id string failed with code [string] [string]
|
|
Cause
|
Connection to the database is dead, or invalid parameter to alert routine.
|
|
Action
|
If this condition repeats, please contact Oracle Support.
|
|
ORA-13918
|
ORA-13918: Updating system alert with reason_id string failed; previous alert not found
|
|
Cause
|
System Error: An attempt to update a system alert failed. The alert was improperly cleared from WRI$_ALERT_OUTSTANDING.
|
|
Action
|
Do not delete from WRI$_ALERT_OUTSTANDING. If this condition repeats, please contact Oracle Support.
|
|
ORA-13919
|
ORA-13919: Cannot specify values for parameter "string" and for parameter "string"
|
|
Cause
|
Can only specify a value for one or the other.
|
|
Action
|
Pass just one of the parameters.
|
|
ORA-13951
|
ORA-13951: MMON sub-action time limit exceeded
|
|
Cause
|
This is an internal Server Manageability Error
|
|
Action
|
Contact Oracle Support Services
|
|
ORA-14000
|
ORA-14000: only one LOCAL clause may be specified
|
|
Cause
|
CREATE INDEX statement contained more than one LOCAL clause
|
|
Action
|
Specify LOCAL option at most once
|
|
ORA-14001
|
ORA-14001: LOCAL clause contradicts previosly specified GLOBAL clause
|
|
Cause
|
CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause
|
|
Action
|
Specify LOCAL or GLOBAL clause, but not both
|
|
ORA-14002
|
ORA-14002: only one GLOBAL clause may be specified
|
|
Cause
|
CREATE INDEX statement contained more than one GLOBAL clause
|
|
Action
|
Specify GLOBAL option at most once
|
|
ORA-14003
|
ORA-14003: GLOBAL clause contradicts previosly specified LOCAL clause
|
|
Cause
|
CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause
|
|
Action
|
Specify GLOBAL or LOCAL clause, but not both
|
|
ORA-14004
|
ORA-14004: missing PARTITION keyword
|
|
Cause
|
keyword PARTITION missing
|
|
Action
|
supply missing keyword
|
|
ORA-14005
|
ORA-14005: missing RANGE keyword
|
|
Cause
|
keyword RANGE missing
|
|
Action
|
supply missing keyword
|
|
ORA-14006
|
ORA-14006: invalid partition name
|
|
Cause
|
a partition name of the form is expected but not present.
|
|
Action
|
enter an appropriate partition name.
|
|
ORA-14007
|
ORA-14007: missing LESS keyword
|
|
Cause
|
keyword LESS missing
|
|
Action
|
supply missing keyword
|
|
ORA-14008
|
ORA-14008: missing THAN keyword
|
|
Cause
|
keyword THAN missing
|
|
Action
|
supply missing keyword
|
|
ORA-14009
|
ORA-14009: partition bound may not be specified for a LOCAL index partition
|
|
Cause
|
while parsing a CREATE INDEX statement to create a LOCAL partitioned index, of one of partitions was found to contain 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
|
|
ORA-14010
|
ORA-14010: this physical attribute may not be specified for an index partition
|
|
Cause
|
unexpected option was encountered while parsing physical attributes of an index partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE,
STORAGE, PCTFREE; only TABLESPACE may be specified for Hash partitions
|
|
Action
|
remove invalid option(s) from the list of physical attributes of an index partition
|
|
ORA-14011
|
ORA-14011: names assigned to resulting partitions must be distinct
|
|
Cause
|
Names of partitions resulting from splitting of an existing table or index partition are 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
|
|
ORA-14012
|
ORA-14012: resulting partition name conflicts with that of an existing partition
|
|
Cause
|
Name of a partition resulting from splitting of an existing table or index partition is 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
|
|
ORA-14013
|
ORA-14013: duplicate partition name
|
|
Cause
|
Name of a partition of a table or index being created is not unique
|
|
Action
|
rename partition(s) to ensure that their names are unique among partitions of the table or index being created
|
|
ORA-14014
|
ORA-14014: maximum number of partitioning columns is 16
|
|
Cause
|
number of columns in a partitioning column list exceeded the legal limit of 16
|
|
Action
|
modify partitioning column list so that it consists of at most 16 columns
|
|
ORA-14015
|
ORA-14015: too many partition descriptions
|
|
Cause
|
CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 1048575 (1024K-1).
|
|
Action
|
Reduce number of partitions to not exceed 1048575 (1024K -1).
|
|
ORA-14016
|
ORA-14016: underlying table of a LOCAL partitioned index must be partitioned
|
|
Cause
|
User attempted to create a LOCAL partitioned index on a non-partitioned table which is illegal. Only GLOBAL indices (partitioned or otherwise) may be created on a non-partitioned
table.
|
|
Action
|
Correct the statement and reenter
|
|
ORA-14017
|
ORA-14017: partition bound list contains too many elements
|
|
Cause
|
Partition bound list contained more elements than there are partitioning columns
|
|
Action
|
Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index
|
|
ORA-14018
|
ORA-14018: partition bound list contains too few elements
|
|
Cause
|
Partition bound list contained fewer elements than there are partitioning columns
|
|
Action
|
Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index
|
|
ORA-14019
|
ORA-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
|
|
Cause
|
Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or MAXVALUE)
|
|
Action
|
Ensure that all elements of partition bound list are of valid type
|
|
ORA-14020
|
ORA-14020: this physical attribute may not be specified for a table partition
|
|
Cause
|
unexpected option was encountered while parsing physical attributes of a table partition; valid options for Range or Composite Range partitions are INITRANS, MAXTRANS, TABLESPACE,
STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified for Hash partitions
|
|
Action
|
remove invalid option(s) from the list of physical attributes of a table partition
|
|
ORA-14021
|
ORA-14021: MAXVALUE must be specified for all columns
|
|
Cause
|
In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE must be specified for all columns
|
|
Action
|
Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns
|
|
ORA-14022
|
ORA-14022: creation of LOCAL partitioned cluster indices is not supported
|
|
Cause
|
An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal
|
|
Action
|
Remove LOCAL along with s, if any, from the CREATE INDEX statement.
|
|
ORA-14023
|
ORA-14023: creation of GLOBAL partitioned cluster indices is not supported
|
|
Cause
|
An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal
|
|
Action
|
Remove PARTITION BY RANGE clause along with s from the CREATE INDEX statement.
|
|
ORA-14024
|
ORA-14024: number of partitions of LOCAL index must equal that of the underlying table
|
|
Cause
|
User attempted 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
|
|
ORA-14025
|
ORA-14025: PARTITION may not be specified for a materialized view or a materialized view log
|
|
Cause
|
PARTITION option was encountered while parsing a definition of a materialized view or a materialized view log
|
|
Action
|
Ensure that a definition of a MATERIALIZED VIEW does not include invalid options
|
|
ORA-14026
|
ORA-14026: PARTITION and CLUSTER clauses are mutually exclusive
|
|
Cause
|
definition of a table contained both PARTITION and CLUSTER clauses which is illegal
|
|
Action
|
Remove one of the conflicting clauses
|
|
ORA-14027
|
ORA-14027: only one PARTITION clause may be specified
|
|
Cause
|
CREATE TABLE statement contained more than one PARTITION clause
|
|
Action
|
Specify PARTITION option at most once
|
|
ORA-14028
|
ORA-14028: missing AT or VALUES keyword
|
|
Cause
|
keyword AT or VALUES missing
|
|
Action
|
supply missing keyword
|
|
ORA-14029
|
ORA-14029: GLOBAL partitioned index must be prefixed
|
|
Cause
|
partitioning columns of a global partitioned index must form a prefix of the index" key columns
|
|
Action
|
Ensure that the GLOBAL partitioned index being created is prefixed
|
|
ORA-14030
|
ORA-14030: non-existent partitioning column in CREATE TABLE statement
|
|
Cause
|
Partitioning column specified in 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.
|
|
ORA-14031
|
ORA-14031: partitioning column may not be of type LONG or LONG RAW
|
|
Cause
|
Partitioning column specified by the user was of type LONG or LONG RAW, which is illegal.
|
|
Action
|
Ensure that no partitioning column is of type LONG or LONG RAW.
|
|
ORA-14032
|
ORA-14032: partition bound of partition number string is too high
|
|
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.
|
|
ORA-14036
|
ORA-14036: partition bound value too large for column
|
|
Cause
|
Length of partition bound value is longer than that of the corresponding partitioning column.
|
|
Action
|
Ensure that lengths of high bound values do not exceed those of corresponding partitioning columns
|
|
ORA-14037
|
ORA-14037: partition bound of partition "string" is too high
|
|
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 high bound of every partition (except for the last one) collates lower than that of a following partition.
|
|
ORA-14038
|
ORA-14038: GLOBAL partitioned index must be prefixed
|
|
Cause
|
User attempted to create a GLOBAL non-prefixed partitioned index which is illegal
|
|
Action
|
If the user, indeed, desired to create a non-prefixed index, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is
prefixed
|
|
ORA-14039
|
ORA-14039: partitioning columns must form a subset of key columns of a UNIQUE index
|
|
Cause
|
User attempted to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns which is illegal
|
|
Action
|
If the user, indeed, desired to create an index whose partitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of
key and/or partitioning columns to ensure that the index" partitioning columns form a subset of its key columns
|
|
ORA-14041
|
ORA-14041: partition bound may not be specified for resulting partitions
|
|
Cause
|
while parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, of a resulting partition was found to contain VALUES LESS THAN clause which is illegal
|
|
Action
|
remove VALUES LESS THAN clause from the description(s) of partitions resulting from splitting an existing table or index partition
|
|
ORA-14042
|
ORA-14042: partition bound may not be specified for a partition being moved, modified or rebuilt
|
|
Cause
|
while parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement, 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 VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt
|
|
ORA-14043
|
ORA-14043: only one partition may be added
|
|
Cause
|
ALTER TABLE ADD PARTITION 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
|
|
ORA-14044
|
ORA-14044: only one partition may be moved
|
|
Cause
|
ALTER TABLE MOVE PARTITION 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
|
|
ORA-14045
|
ORA-14045: only one partition may be modified
|
|
Cause
|
ALTER TABLE|INDEX MODIFY PARTITION 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
|
|
ORA-14046
|
ORA-14046: a partition may be split into exactly two new partitions
|
|
Cause
|
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
|
|
ORA-14047
|
ORA-14047: ALTER TABLE|INDEX RENAME may not be combined with other operations
|
|
Cause
|
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;
|
|
ORA-14048
|
ORA-14048: a partition maintenance operation may not be combined with other operations
|
|
Cause
|
ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (e.g. MOVE PARTITION) with some other operation (e.g. ADD PARTITION or PCTFREE which is
illegal
|
|
Action
|
Ensure that a partition maintenance operation 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-14049
|
ORA-14049: invalid ALTER TABLE MODIFY PARTITION option
|
|
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 for a
Range or Composite Range partition.
|
|
Action
|
Specify only legal options.
|
|
ORA-14050
|
ORA-14050: invalid ALTER INDEX MODIFY PARTITION option
|
|
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.
|
|
ORA-14051
|
ORA-14051: invalid ALTER MATERIALIZED VIEW option
|
|
Cause
|
An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER MATERIALIZED VIEW statement.
|
|
Action
|
Specify only legal options.
|
|
ORA-14052
|
ORA-14052: partition-extended table name syntax is disallowed in this context
|
|
Cause
|
User attempted to use partition-extended table name syntax in illegal context (i.e. not in FROM-clause or INSERT, DELETE, or UPDATE statement)
|
|
Action
|
Avoid use of partition-extended table name in contexts other those mentioned above.
|
|
ORA-14053
|
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
|
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
|
ORA-14055: keyword REBUILD in ALTER INDEX REBUILD must immediately follow
|
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
ORA-14081: new partition name must differ from the old partition name
|
|
Cause
|
User entered ALTER TABLE/INDEX RENAME PARTITION specifying 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
|
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 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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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
|
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.
|