ORA-25116: invalid block number specified in the DUMP DATAFILE or TEMPFILE command

ORA-25116: invalid block number specified in the DUMP DATAFILE or TEMPFILE command

Cause: An invalid block number was used in dumping a datafile or tempfile.

Action: Specify a valid block number.

ORA-25115: duplicate BLOCK option specification

ORA-25115: duplicate BLOCK option specification

Cause: BLOCK (MIN or MAX) was specified more than once in the DUMP DATAFILE or TEMPFILE command.

Action: Specify only one BLOCK option.

ORA-25114: invalid file number specified in the DUMP DATAFILE or TEMPFILE command

ORA-25114: invalid file number specified in the DUMP DATAFILE or TEMPFILE command

Cause: An invalid file number was used in dumping a datafile or tempfile.

Action: Specify a valid file number.

ORA-25113: GLOBAL may not be used with a bitmap index

ORA-25113: GLOBAL may not be used with a bitmap index

Cause: An attempt was made to create a bitmap index using the GLOBAL option.

Action: Remove GLOBAL from the CREATE BITMAP INDEX statement, and or or add a LOCAL partition descriptor if the table is partitioned.

ORA-25112: maximum number of BITMAP index columns is 30

ORA-25112: maximum number of BITMAP index columns is 30

Cause: Too many columns were specified for the index.

Action: Create an index on fewer columns.

ORA-25111: creation of BITMAP cluster indices is not supported

ORA-25111: creation of BITMAP cluster indices is not supported

Cause: An attempt was made to create a cluster index with the BITMAP attribute.

Action: Remove BITMAP from the CREATE INDEX statement.

ORA-25110: NOSORT may not be used with a bitmap index

ORA-25110: NOSORT may not be used with a bitmap index

Cause: An attempt was made to create a bitmap index using the NOSORT option.

Action: Remove NOSORT from the CREATE BITMAP INDEX statement.

ORA-25109: standby lock name space has illegal character string

ORA-25109: standby lock name space has illegal character string

Cause: An invalid lock name space was specified for the standby database. The lock name space for the standby database can only contain A-Z, 0-9, _ , # , $ , . and characters.

Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a valid character string.

ORA-25108: standby lock name space exceeds size limit of string characters

ORA-25108: standby lock name space exceeds size limit of string characters

Cause: The lock name space for the standby database exceeded the maximum string length.

Action: Change initialization parameter _STANDBY_LOCK_NAME_SPACE to a character string of less than the specified characters.

ORA-25107: duplicate TABLESPACE option specification

ORA-25107: duplicate TABLESPACE option specification

Cause: the TABLESPACE was specified more than once in an ALTER INDEX REBUILD statement.

Action: Remove all but one of the TABLESPACE clauses.

ORA-25106: only one of PARALLEL or NOPARALLEL clause may be specified

ORA-25106: only one of PARALLEL or NOPARALLEL clause may be specified

Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in an ALTER INDEX REBUILD statement.

Action: Remove all but one of the PARALLEL or NOPARALLEL clauses.

ORA-25105: RECOVERABLE option can only be used with ALTER INDEX REBUILD

ORA-25105: RECOVERABLE option can only be used with ALTER INDEX REBUILD

Cause: The RECOVERABLE option to ALTER INDEX was used without the REBUILD option.

Action: Use ALTER INDEX REBUILD.

ORA-25104: UNRECOVERABLE option can only be used with ALTER INDEX REBUILD

ORA-25104: UNRECOVERABLE option can only be used with ALTER INDEX REBUILD

Cause: The UNRECOVERABLE option to ALTER INDEX was used without the REBUILD option.

Action: Use ALTER INDEX REBUILD.

ORA-25103: NOPARALLEL option can only be used with ALTER INDEX REBUILD

ORA-25103: NOPARALLEL option can only be used with ALTER INDEX REBUILD

Cause: The NOPARALLEL option to ALTER INDEX was used without the REBUILD option.

Action: Use ALTER INDEX REBUILD.

ORA-25102: PARALLEL option can only be used with ALTER INDEX REBUILD

ORA-25102: PARALLEL option can only be used with ALTER INDEX REBUILD

Cause: The PARALLEL option to ALTER INDEX was used without the REBUILD option.

Action: Use ALTER INDEX REBUILD.

ORA-25101: duplicate REBUILD option specification

ORA-25101: duplicate REBUILD option specification

Cause: The REBUILD option to ALTER INDEX is specified more than once.

Action: Specify the option at most once.

ORA-25100: TABLESPACE option can only be used with ALTER INDEX REBUILD

ORA-25100: TABLESPACE option can only be used with ALTER INDEX REBUILD

Cause: The TABLESPACE option to ALTER INDEX was used without the REBUILD option.

Action: Use ALTER INDEX REBUILD TABLESPACE tablespace name.

ORA-25020: renaming system triggers is not allowed

ORA-25020: renaming system triggers is not allowed

Cause: renaming system triggers is not allowed

Action: Drop the trigger, and create a new one for the same

ORA-25019: too much concurreny

ORA-25019: too much concurreny

Cause: cannot pin the database or schema because of too much concurrency

Action: try the operation later

ORA-25018: conflicting trigger string already exists

ORA-25018: conflicting trigger string already exists

Cause: Conflicting instead of DDL trigger on schema or database already exists.

Action: Remove the old trigger

ORA-25017: cannot reference NEW ROWID for movable rows in before triggers

ORA-25017: cannot reference NEW ROWID for movable rows in before triggers

Cause: NEW ROWID was referenced in a before row trigger which is defined on an index-organized table, or a partitioned table with enabled movement of rows. The ROWID cannot be computed in a before row update trigger because it depends on the actual values of the row

Action: Remove references to NEW ROWID from the trigger definition.

ORA-25016: cannot specify column list for insert into nested table view column

ORA-25016: cannot specify column list for insert into nested table view column

Cause: A column list cannot be specified for inserts into the nested table view column.

Action: Specify all the columns for insert into the nested table.

ORA-25015: cannot perform DML on this nested table view column

ORA-25015: cannot perform DML on this nested table view column

Cause: DML cannot be performed on a nested table view column except through an INSTEAD OF trigger

Action: Create an INSTEAD OF trigger over the nested table view column and then perform the DML.

ORA-25014: cannot change the value of a PARENT reference variable

ORA-25014: cannot change the value of a PARENT reference variable

Cause: Parent values can only be read and not changed.

Action: Do not attempt to change a Parent variable.

ORA-25013: OLD and PARENT values cannot be identical

ORA-25013: OLD and PARENT values cannot be identical

Cause: The referencing clause specifies identical values for OLD and PARENT.

Action: Re-specify either the OLD or PARENT referencing value.

ORA-25012: PARENT and NEW values cannot be identical

ORA-25012: PARENT and NEW values cannot be identical

Cause: The referencing clause specifies identical values for PARENT and OLD.

Action: Re-specify either the PARENT or NEW referencing value.

ORA-25011: cannot create trigger on internal AQ table

ORA-25011: cannot create trigger on internal AQ table

Cause: An attempt was made to try to create a trigger on a table that is used internally to support the Advanced Queueing (AQ) feature.

Action: Do not create the trigger.

ORA-25010: Invalid nested table column name in nested table clause

ORA-25010: Invalid nested table column name in nested table clause

Cause: The column name specified in the nested table clause of an INSTEAD OF trigger does not correspond to a nested table column.

Action: Specify a nested table column on which the trigger is to be defined.

ORA-25009: Nested table clause allowed only for INSTEAD OF triggers

ORA-25009: Nested table clause allowed only for INSTEAD OF triggers

Cause: Triggers on nested tables can only be created on view columns using INSTEAD OF triggers.

Action: Use view nested table columns for defining nested table triggers.

ORA-25008: no implicit conversion to LOB datatype in instead-of trigger

ORA-25008: no implicit conversion to LOB datatype in instead-of trigger

Cause: When inserting or updating a view using instead-of trigger, the new value for a LOB view column is of a different datatype.

Action: Specified a LOB value as the new value for the LOB view column.

ORA-25007: functions or methods not allowed in WHEN clause

ORA-25007: functions or methods not allowed in WHEN clause

Cause: PLSQL function call or method invocation is not allowed in the WHEN clause when creating a trigger.

Action: Remove the function call or method invocation from the WHEN clause.

ORA-25006: cannot specify this column in UPDATE OF clause

ORA-25006: cannot specify this column in UPDATE OF clause

Cause: Attempt to create a trigger on update of a column whose datatype is disallowed in the clause, such as LOB and nested table.

Action: Remove the UPDATE OF clause.

ORA-25005: cannot CREATE INSTEAD OF trigger on a read-only view

ORA-25005: cannot CREATE INSTEAD OF trigger on a read-only view

Cause: attempt to create an INSTEAD OF trigger on a view created with read-only option. The view cannot be updated using INSTEAD OF triggers.

Action: Do not create the trigger.

ORA-25004: WHEN clause is not allowed in INSTEAD OF triggers

ORA-25004: WHEN clause is not allowed in INSTEAD OF triggers

Cause: WHEN clause is specified in an INSTEAD OF trigger.

Action: Remove the WHEN clause when creating an INSTEAD OF trigger.

ORA-25003: cannot change NEW values for this column type in trigger

ORA-25003: cannot change NEW values for this column type in trigger

Cause: Attempt to change NEW trigger variables of datatype object, REF, nested table, VARRAY or LOB datatype which is not supported.

Action: Do not change the NEW trigger variables in the trigger body.

ORA-25002: cannot create INSTEAD OF triggers on tables

ORA-25002: cannot create INSTEAD OF triggers on tables

Cause: Only BEFORE or AFTER triggers can be created on a table.

Action: Change the trigger type to BEFORE or AFTER.

ORA-25001: cannot create this trigger type on views

ORA-25001: cannot create this trigger type on views

Cause: Only INSTEAD OF triggers can be created on a view.

Action: Change the trigger type to INSTEAD OF.

ORA-25000: invalid use of bind variable in trigger WHEN clause

ORA-25000: invalid use of bind variable in trigger WHEN clause

Cause: A bind variable was used in the when clause of a trigger.

Action: Remove the bind variable. To access the table columns use (new or old).column_name.

ORA-24960: the attribute string is greater than the maximum allowable length of number

ORA-24960: the attribute string is greater than the maximum allowable length of number

Cause: The user attempted to pass an attribute that is too long

Action: Shorten the specified attribute and retry the operation.

ORA-24952: register, unregister or post has incorrect collection count

ORA-24952: register, unregister or post has incorrect collection count

Cause: The register, unregister or post function was invoked with a collection that was smaller than the size specified by the parameter to the function.

Action: Please check the function s use and ensure that the size parameter is correct.

ORA-24950: unregister failed, registeration not found

ORA-24950: unregister failed, registeration not found

Cause: The registeration that was asked to be unregistered could not be found.

Action: Please check the callback function name and the subscription name in the unregister call.

ORA-24912: Listener thread failed. string

ORA-24912: Listener thread failed. string

Cause: Thread listening for event notification exited because of an error. The error encountered is appended to the error message.

Action: The client needs to be restarted.

ORA-24911: Cannot start listener thread at specified port

ORA-24911: Cannot start listener thread at specified port

Cause: Thread already running at a different port.

Action: Set the correct port in the environment handle or let the system choose the port.

ORA-24909: call in progress. Current operation cancelled

ORA-24909: call in progress. Current operation cancelled

Cause: The OCI call was invoked when another call on the connection was in progress.

Action: Check if the OCI call is supported when the call is in progress under special conditions; for example, if it is being used by a signal handler. NLS_DO_ NOT_TRANSLATE (24910,24910(

ORA-24908: invalid recipient presentation attribute

ORA-24908: invalid recipient presentation attribute

Cause: The subscription handle passed into the OCI call does not have a valid recipient presentation attribute.

Action: Set the recipient presentation attribute using the OCIAttrSet() call

ORA-24907: invalid pair of callback and recepient protocol attributes

ORA-24907: invalid pair of callback and recepient protocol attributes

Cause: The subscription handle passed into the OCI call can t have both the callback defined and a recepient protocol other than OCI_SUBSCR_PROTO_OCI at the same time.

Action: Please set the appropriate callback and recepient protocol attributes using the OCIAttrSet() call.

ORA-24906: invalid recepient attribute passed into OCI call

ORA-24906: invalid recepient attribute passed into OCI call

Cause: The subscription handle passed into the OCI call does not have a proper recepient attribute.

Action: Please set the recepient attribute using the OCIAttrSet() call.

ORA-24905: invalid recepient protocol attribute passed into OCI call

ORA-24905: invalid recepient protocol attribute passed into OCI call

Cause: The subscription handle passed into the OCI call does not have a proper recepient protocol attribute.

Action: Please set the recepient protocol attribute using the OCIAttrSet() call.

ORA-24904: invalid callback attribute passed into OCI call

ORA-24904: invalid callback attribute passed into OCI call

Cause: The subscription handle passed into the OCI call does not have a proper callback attribute.

Action: Please set the callback attribute using the OCIAttrSet() call.

ORA-24903: invalid namespace attribute passed into OCI call

ORA-24903: invalid namespace attribute passed into OCI call

Cause: The subscription handle passed into the OCI call does not have a proper namespace attribute.

Action: Please set the namespace attribute using the OCIAttrSet() call.

ORA-24902: invalid subscription name or name-length in subscription handle

ORA-24902: invalid subscription name or name-length in subscription handle

Cause: The subscription handle passed into the OCI call does not have a proper name or name-length attribute.

Action: Please set the name and name-length attributes using the OCIAttrSet() call.

ORA-24901: handles belonging to different environments passed into an OCI call

ORA-24901: handles belonging to different environments passed into an OCI call

Cause: All handles passed into an OCI call should belong to the same environment. In the call that returned this error, handles belonging to different environments were passed in.

Action: Please ensure that the handle parameters in the call to come from the same OCI Environment.

ORA-24900: invalid or unsupported mode paramater passed in call

ORA-24900: invalid or unsupported mode paramater passed in call

Cause: The mode parameter passed into the OCI Client Notification call is incorrect.

Action: Please correct the mode parameter passed into OCI.

ORA-24853: failed to connect thread to shared subsystem

ORA-24853: failed to connect thread to shared subsystem

Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the thread to the shared subsystem.

Action: Contact Oracle Customer Support.

ORA-24852: protocol error during statement execution

ORA-24852: protocol error during statement execution

Cause: An internal protocol error occurred while receiving describe data from the server during execution of a statement.

Action: Contact Oracle Customer Support.

ORA-24851: failed to connect to shared subsystem

ORA-24851: failed to connect to shared subsystem

Cause: While attempting to initialize OCI in shared mode, a problem was encountered in connecting the process to the shared subsystem.

Action: Contact Oracle Customer Support.

ORA-24850: failed to startup shared subsystem

ORA-24850: failed to startup shared subsystem

Cause: While attempting to initialize OCI in shared mode, a problem was encountered in starting up the shared subsystem.

Action: Contact Oracle Customer support.

ORA-24817: Unable to allocate the given chunk for current lob operation

ORA-24817: Unable to allocate the given chunk for current lob operation

Cause: The given size is increased to accomodate the number of bytes from server due to varying width db char or nchar set.

Action: Use smaller chunk sizes when you have character set conversion between client or server or perform piece-wise read or write.

ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column

ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column

Cause: A Bind value of length potentially lamp;gt; 4000 bytes follows binding for LOB or LONG.

Action: Re-order the binds so that the LONG bind or LOB binds are all at the end of the bind list.

ORA-24815: Invalid character set form

ORA-24815: Invalid character set form

Cause: An invalid character set form was passed into an OCI LOB function. For example, the only valid cs form for OCILobCreateTemporary() is OCI_ DEFAULT(0), SQLCS_IMPLICIT(1) or SQLCS_NCHAR(2).

Action: Specify a valid character set form.