ORA-14031: partitioning column may not be of type LONG or LONG RAW

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-14030: non-existent partitioning column in CREATE TABLE statement

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-14029: GLOBAL partitioned index must be prefixed

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-14028: missing AT or VALUES keyword

ORA-14028: missing AT or VALUES keyword

Cause: keyword AT or VALUES missing

Action: supply missing keyword

ORA-14027: only one PARTITION clause may be specified

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-14026: PARTITION and CLUSTER clauses are mutually exclusive

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-14025: PARTITION may not be specified for a materialized view or a materialized view log

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-14024: number of partitions of LOCAL index must equal that of the underlying table

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-14023: creation of GLOBAL partitioned cluster indices is not supported

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 lamp;lt;lamp;nbsp;partition descriptionlamp;gt;s from the CREATE INDEX statement.

ORA-14022: creation of LOCAL partitioned cluster indices is not supported

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 lamp;lt;lamp;nbsp;partition descriptionlamp;gt;s, if any, from the CREATE INDEX statement.

ORA-14021: MAXVALUE must be specified for all columns

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-14020: this physical attribute may not be specified for a table partition

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-14019: partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE

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-14018: partition bound list contains too few elements

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-14017: partition bound list contains too many elements

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-14016: underlying table of a LOCAL partitioned index must be partitioned

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-14015: too many partition descriptions

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-14014: maximum number of partitioning columns is 16

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-14013: duplicate partition name

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-14012: resulting partition name conflicts with that of an existing partition

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-14011: names assigned to resulting partitions must be distinct

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-14010: this physical attribute may not be specified for an index partition

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-14009: partition bound may not be specified for a LOCAL index partition

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, lamp;lt;lamp;nbsp;partition-descriptionlamp;gt; 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-14008: missing THAN keyword

ORA-14008: missing THAN keyword

Cause: keyword THAN missing

Action: supply missing keyword

ORA-14007: missing LESS keyword

ORA-14007: missing LESS keyword

Cause: keyword LESS missing

Action: supply missing keyword

ORA-14006: invalid partition name

ORA-14006: invalid partition name

Cause: a partition name of the form lamp;lt;lamp;nbsp;identifierlamp;gt; is expected but not present.

Action: enter an appropriate partition name.

ORA-14005: missing RANGE keyword

ORA-14005: missing RANGE keyword

Cause: keyword RANGE missing

Action: supply missing keyword

ORA-14004: missing PARTITION keyword

ORA-14004: missing PARTITION keyword

Cause: keyword PARTITION missing

Action: supply missing keyword

ORA-14003: GLOBAL clause contradicts previosly specified LOCAL clause

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-14002: only one GLOBAL clause may be specified

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-14001: LOCAL clause contradicts previosly specified GLOBAL clause

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-14000: only one LOCAL clause may be specified

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-13951: MMON sub-action time limit exceeded

ORA-13951: MMON sub-action time limit exceeded

Cause: This is an internal Server Manageability Error

Action: Contact Oracle Support Services

ORA-13919: Cannot specify values for parameter string and for parameter string

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-13918: Updating system alert with reason_id string failed; previous alert not found

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-13917: Posting system alert with reason_id string failed with code (string( (string(

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-13916: Invalid value string specified for parameter string

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-13915: Critical byte based free space threshold value is greater than warning threshold value.

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-13914: Threshold notification failed.

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-13913: The threshold cannot be set when SYSAUX is offline.

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-13912: Critical threshold value is less than warning threshold value.

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-13911: Threshold not found

ORA-13911: Threshold not found

Cause: The threshold did not exist with the specified threshold key.

Action: No action required.

ORA-13910: Parameter string cannot be NULL.

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-13909: Invalid combination of threshold value and operator.

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-13908: Invalid combination of metrics id and object type parameters.

ORA-13908: Invalid combination of metrics id and object type parameters.

Cause: An attempt was made to specify an invalid combination of metrics id or or and object type parameters.

Action: Specify a valid combination of metrics id and object type parameters.

ORA-13907: Threshold value is invalid.

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-13906: The tablepace is not of the right type.

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-13905: Critical or warning threshold have incorrect values

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-13904: The file has been dropped and recreated during the procedure call.

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-13903: Invalid combination of string threshold value and operator.

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-13902: The specified file string is not a data file.

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-13901: Object string was not found.

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-13900: missing or invalid parameter string

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-13871: Invalid instance name

ORA-13871: Invalid instance name

Cause: Instance name is too long (exceeding 16 characters)

Action: Supply correct name

ORA-13870: Database-wide SQL tracing is not enabled

ORA-13870: Database-wide SQL tracing is not enabled

Cause: Attempt to disable a database-level tracing which was never enabled

Action: No action required

ORA-13869: Instance-wide SQL tracing on instance string is already enabled

ORA-13869: Instance-wide SQL tracing on instance string is already enabled

Cause: Attempt to enable an instance-level tracing which has been already enabled on a specific instance

Action: Disable and re-enable tracing with different bind or wait options

ORA-13868: Instance-wide SQL tracing on instance string is not enabled

ORA-13868: Instance-wide SQL tracing on instance string is not enabled

Cause: Attempt to disable a service-level tracing which was never explicitly enabled on a specific instance

Action: No action required

ORA-13867: Database-wide SQL tracing is already enabled

ORA-13867: Database-wide SQL tracing is already enabled

Cause: Attempt to enable a database-level tracing which has been already enabled

Action: Disable and re-enable tracing with different bind or wait options

ORA-13866: Client identifier must be specified

ORA-13866: Client identifier must be specified

Cause: Omitting client identifier while enabling or disabling tracing or aggregation

Action: Supply the client identifier

ORA-13865: Module name must be specified

ORA-13865: Module name must be specified

Cause: Attempt to enable or disable a service-level statistics aggregation without a module specification

Action: Supply module name