Oracle Error Messages: 04/25/12

Wednesday 25 April 2012

ORA-25193: cannot use COMPRESS option for a single column key

ORA-25193: cannot use COMPRESS option for a single column key

Cause: An attempt to use COMPRESS option on single column key

Action: Remove the COMPRESS option.

ORA-25192: invalid option for an index-organized table

ORA-25192: invalid option for an index-organized table

Cause: An attempt to specify one or more of the following options for an index-organized table: (NO(CACHE, NO LOGGING, CLUSTER

Action: Remove the illegal option(s)

ORA-25191: cannot reference overflow table of an index-organized table

ORA-25191: cannot reference overflow table of an index-organized table

Cause: An attempt to directly access the overflow table of an index-organized table

Action: Issue the statement against the parent index-organized table containing the specified overflow table.

ORA-25190: an index-organized table maintenance operation may not be combined with other operations

ORA-25190: an index-organized table maintenance operation may not be combined with other operations

Cause: ALTER TABLE statement attempted to combine an index-organized table maintenance operation (e.g. changing physical attributes) with some other operation (e.g. ADD constraint) which is illegal

Action: Ensure that a index-organized table maintenance operation is the sole operation specified in ALTER TABLE statement;

ORA-25189: illegal ALTER TABLE option for an index-organized table

ORA-25189: illegal ALTER TABLE option for an index-organized table

Cause: During ALTER of a index-organized table, the user attempted to enter one or more of the following options: TABLESPACE, ALLOCATE or DEALLOCATE EXTENT, PCTFREE or PCTUSED for IOT top index segment

Action: Remove the illegal option(s).

ORA-25187: specified exceptions table form incorrect

ORA-25187: specified exceptions table form incorrect

Cause: The specified table does not have the proper field definitions.

Action: Specify the correct table to use.

ORA-25186: INCLUDING clause specified for index-organized table without OVERFLOW

ORA-25186: INCLUDING clause specified for index-organized table without OVERFLOW

Cause: INCLUDING clause of a CREATE TABLE is an valid option only for index-organized tables with OVERFLOW clause (at creation time) or if an OVERFLOW segment already exists (at ALTER time).

Action: Specify OVERFLOW clause for the index-organized table : For ALTER, perform ADD OVERFLOW first.

ORA-25185: index column other than last can not be specified for INCLUDE clause

ORA-25185: index column other than last can not be specified for INCLUDE clause

Cause: An index column name other than the last is specified as including column

Action: Specify either a column name which is not part of index-organized table primary key index , or the last key column of the primary key for the INCLUDING clause.

ORA-25184: column name expected

ORA-25184: column name expected

Cause: A column name is not present where required by the CREATE TABLE for specifying last column to be included in the index segment of the index-organized table

Action: Specify a column name where required by the syntax.

ORA-25183: index-organized table top index segment is in a different tablespace

ORA-25183: index-organized table top index segment is in a different tablespace

Cause: An attempt was made to drop a tablespace which contains an index only table s overflow segment but not the top index segment

Action: find index-organized tables which span the tablespace being dropped and some other tablespace(s). Drop these tables.

ORA-25182: feature not currently available for index-organized tables

ORA-25182: feature not currently available for index-organized tables

Cause: An attempt was made to use one or more of the following feature(s) not currently supported for index-organized tables: CREATE TABLE with LOB or BFILE or VARRAY columns, partitioning or PARALLEL or CREATE TABLE AS SELECT options, ALTER TABLE with ADD or MODIFY column options, CREATE INDEX

Action: Do not use the disallowed feature(s) in this release.

ORA-25181: missing ON keyword for NESTED INDEX

ORA-25181: missing ON keyword for NESTED INDEX

Cause: ON keyword required to specify nested index column nest

Action: Add ON keyword

ORA-25180: PCTTHRESHOLD only valid for certain table organizations

ORA-25180: PCTTHRESHOLD only valid for certain table organizations

Cause: PCTTHRESHOLD can only be specified for tables with certain organizations.

Action: Remove the PCTTHRESHOLD option.

ORA-25179: invalid PCTTHRESHOLD storage option value

ORA-25179: invalid PCTTHRESHOLD storage option value

Cause: The specified value must be a positive integer.

Action: Specify an appropriate value.

ORA-25178: duplicate PCTTHRESHOLD storage option specification

ORA-25178: duplicate PCTTHRESHOLD storage option specification

Cause: The storage option PCTTHRESHOLD is specified more than once.

Action: Specify storage options at most once.

ORA-25177: UNRECOVERABLE option not permitted

ORA-25177: UNRECOVERABLE option not permitted

Cause: The UNRECOVERABLE option may not be specified for a primary key for a table with this organization

Action: Remove UNRECOVERABLE option for primary key

ORA-25176: storage specification not permitted for primary key

ORA-25176: storage specification not permitted for primary key

Cause: Storage parameters cannot be defined for a PRIMARY KEY constraint for a table with this organization

Action: Remove storage specification for primary key

ORA-25175: no PRIMARY KEY constraint found

ORA-25175: no PRIMARY KEY constraint found

Cause: A PRIMARY KEY constraint must be defined for a table with this organization

Action: Define a PRIMARY KEY

ORA-25158: Cannot specify RELY for foreign key if the associated primary key is NORELY

ORA-25158: Cannot specify RELY for foreign key if the associated primary key is NORELY

Cause: RELY is specified for the foreign key contraint, when the associated primary key constraint is NORELY.

Action: Change the option of the primary key also to RELY.

ORA-25157: Specified block size string is not valid

ORA-25157: Specified block size string is not valid

Cause: An attempt was made to create a tablespace with a block size which is not supported.

Action: Specify one of the valid blocksizes i.e the standard blocksize or one of (2k, 4k, 8k, 16k, 32k) subject to the maximum and minimum blocksizes supported by the platform.

ORA-25156: old style outer join (+) cannot be used with ANSI joins

ORA-25156: old style outer join (+) cannot be used with ANSI joins

Cause: When a query block uses ANSI style joins, the old notation for specifying outer joins (+) cannot be used.

Action: Use ANSI style for specifying outer joins also.

ORA-25155: column used in NATURAL join cannot have qualifier

ORA-25155: column used in NATURAL join cannot have qualifier

Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier.

Action: Remove the qualifier.

ORA-25154: column part of USING clause cannot have qualifier

ORA-25154: column part of USING clause cannot have qualifier

Cause: Columns that are used for a named-join (either a NATURAL join or a join with a USING clause) cannot have an explicit qualifier.

Action: Remove the qualifier.

ORA-25153: Temporary Tablespace is Empty

ORA-25153: Temporary Tablespace is Empty

Cause: An attempt was made to use space in a temporary tablespace with no files.

Action: Add files to the tablespace using ADD TEMPFILE command.

ORA-25152: TEMPFILE cannot be dropped at this time

ORA-25152: TEMPFILE cannot be dropped at this time

Cause: An attempt was made to drop a TEMPFILE being used by online users

Action: The TEMPFILE has been taken offline. Try again, later.

ORA-25151: Rollback Segment cannot be created in this tablespace

ORA-25151: Rollback Segment cannot be created in this tablespace

Cause: An attempt was made to create a rollback segment in a tablespace with autoallocate extent allocation policy.

Action: Specify a different tablespace for the rollback segment

ORA-25150: ALTERING of extent parameters not permitted

ORA-25150: ALTERING of extent parameters not permitted

Cause: An attempt was made to alter the extent parameters for a segment in a tablespace with autoallocate or uniform extent allocation policy.

Action: Remove the appropriate extent parameters from the command.

ORA-25149: Columns of UROWID type may not be indexed

ORA-25149: Columns of UROWID type may not be indexed

Cause: An attempt was made to create an index on a column of UROWID type

Action: Remove the column from the list of indexed columns

ORA-25148: ONLINE option not permitted

ORA-25148: ONLINE option not permitted

Cause: An attempt was made to specify ONLINE for ALTER TABLE MOVE on a table that is not index-organized. The ONLINE option is currently supported only for index-organized tables.

Action: Remove the ONLINE option from the command.

ORA-25147: UNIFORM SIZE value greater than maximum extent size

ORA-25147: UNIFORM SIZE value greater than maximum extent size

Cause: In CREATE or ALTER TABLESPACE, the value specified for the UNIFORM SIZE option was greater than the maximum extent size.

Action: Choose a lower value for the UNIFORM SIZE option.

ORA-25146: EXTENT MANAGEMENT option already specified

ORA-25146: EXTENT MANAGEMENT option already specified

Cause: In CREATE TABLESPACE, the EXTENT MANAGEMENT option was specified more than once.

Action: Remove all but one of the EXTENT MANAGEMENT specifications.

ORA-25145: allocation policy already specified

ORA-25145: allocation policy already specified

Cause: In CREATE TABLESPACE, the allocation policy was specified more than once, for example, AUTOALLOCATE and UNIFORM.

Action: Remove all but one of the allocation policy specifications.

ORA-25144: invalid option for CREATE TABLESPACE with TEMPORARY contents

ORA-25144: invalid option for CREATE TABLESPACE with TEMPORARY contents

Cause: An invalid option appears.

Action: Specify one of the valid options: EXTENT MANAGEMENT DICTIONARY, USER

ORA-25143: default storage clause is not compatible with allocation policy

ORA-25143: default storage clause is not compatible with allocation policy

Cause: default storage clause was specified for a tablespace with AUTOALLOCATE or UNIFORM policy

Action: Omit the storage clause

ORA-25142: default storage clause specified twice

ORA-25142: default storage clause specified twice

Cause: default storage clause was specified twice for create tablespace

Action: Specify it once.

ORA-25141: invalid EXTENT MANAGEMENT clause

ORA-25141: invalid EXTENT MANAGEMENT clause

Cause: An invalid option appears for EXTENT MANAGEMENT clause

Action: Specify one of the valid options: UNIFORM SIZE, AUTOALLOCATE

ORA-25140: %s space policy cannot be specified for the string extent management

ORA-25140: %s space policy cannot be specified for the string extent management

Cause: An invalid option appears.

Action: Make sure that for LOCAL extent management UNIFORM or AUTOALLOCATE is specified, and for DICTIONARY extent management UNIFORM or AUTOALLOCATE are not specified

ORA-25139: invalid option for CREATE TEMPORARY TABLESPACE

ORA-25139: invalid option for CREATE TEMPORARY TABLESPACE

Cause: An invalid option appears.

Action: Specify one of the valid options: TEMPFILE, EXTENT MANAGEMENT LOCAL, UNIFORM

ORA-25138: %s initialization parameter has been made obsolete

ORA-25138: %s initialization parameter has been made obsolete

Cause: An obsolete initialization parameter has been specified

Action: The system will come up, but parameters must be examined

ORA-25137: Data value out of range

ORA-25137: Data value out of range

Cause: Value from cast operand is larger than cast target size.

Action: Increase size of cast target.

ORA-25136: this cluster can contain only one table

ORA-25136: this cluster can contain only one table

Cause: An attempt was made to store more than one table in a cluster that was created with the SINGLE TABLE option.

Action: Do not attempt to store more than one table in the cluster.

ORA-25135: cannot use the SINGLE TABLE option

ORA-25135: cannot use the SINGLE TABLE option

Cause: The SINGLE TABLE option is only valid for hash clusters.

Action: Do not specify the SINGLE TABLE option.

ORA-25134: keyword TABLE expected

ORA-25134: keyword TABLE expected

Cause: The keyword TABLE is missing from the SINGLE TABLE option.

Action: Place the keyword TABLE after the keyword SINGLE in the command.

ORA-25133: duplicate SINGLE TABLE option specified

ORA-25133: duplicate SINGLE TABLE option specified

Cause: The SINGLE TABLE option was specified more than once.

Action: Specify the SINGLE TABLE option only once.

ORA-25132: UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION

ORA-25132: UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION

Cause: cannot ALTER TABLE EXCHANGE PARTITION when the partition and the table have a disabled and validated unique constraints AND the unique keys in the partion is not mutually exclusive from the rest of the table.

Action: Change the constraint s status.

ORA-25131: cannot modify unique(string) - unique key not defined for table

ORA-25131: cannot modify unique(string) - unique key not defined for table

Cause: attempted to modify a unique key that is not deined for the table.

Action: None

ORA-25130: cannot modify primary key - primary key not defined for table

ORA-25130: cannot modify primary key - primary key not defined for table

Cause: Attempted to modify a primary key that is not defined for the table.

Action: None

ORA-25129: cannot modify constraint (string) - no such constraint

ORA-25129: cannot modify constraint (string) - no such constraint

Cause: the named constraint does not exist for this table.

Action: Obvious

ORA-25128: No insert or update or delete on table with constraint (string.string) disabled and validated

ORA-25128: No insert or update or delete on table with constraint (string.string) disabled and validated

Cause: Try to insert or update or delete on table with DISABLE VALIDATE constraint.

Action: Change the constraint s states.

ORA-25127: RELY not allowed in NOT NULL constraint

ORA-25127: RELY not allowed in NOT NULL constraint

Cause: An attempt to set RELY on for NOT NULL constraint.

Action: only NORELY may be specified for a NOT NULL constraint.

ORA-25126: Invalid name specified for BUFFER_POOL

ORA-25126: Invalid name specified for BUFFER_POOL

Cause: The name of the buffer pool specified by the user is invalid. The only valid names are KEEP, RECYCLE and DEFAULT.

Action: Use a valid name or remove the BUFFER_POOL clause.

ORA-25125: BUFFER_POOL storage option not allowed

ORA-25125: BUFFER_POOL storage option not allowed

Cause: The user attempted to specify the BUFFER_POOL storage option. This option may only be specified during CREATE or ALTER TABLE or CLUSTER or INDEX.

Action: Remove this option and retry the statement.

ORA-25124: Database link name not allowed.

ORA-25124: Database link name not allowed.

Cause: Specifying a database link name when it is not permitted.

Action: Check the name specified for the operation.

ORA-25123: Too many components specified in the name.

ORA-25123: Too many components specified in the name.

Cause: Specifying more components to a name than allowed.

Action: Check the name specified for the operation.

ORA-25122: Only LOCAL bitmap indexes are permitted on partitioned tables

ORA-25122: Only LOCAL bitmap indexes are permitted on partitioned tables

Cause: An attempt was made to create a global bitmap index on a partioned table.

Action: create a local bitmap index instead.

ORA-25121: MINIMUM EXTENT value greater than maximum extent size

ORA-25121: MINIMUM EXTENT value greater than maximum extent size

Cause: In CREATE or ALTER TABLESPACE, the value specified for the MINIMUM EXTENT option was greater than the maximum extent size.

Action: Choose a lower value for the MINIMUM EXTENT option.