ORA-12700 to ORA-19399
ORA-12700 invalid NLS parameter value (string)
Cause: An invalid NLS initialization parameter was specified.
Action: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.
ORA-12701 CREATE DATABASE character set is not known
Cause: The character set specified in the CREATE DATABASE command does not exist on the system.
Action: Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.
ORA-12702 invalid NLS parameter string used in SQL function
Cause: An invalid parameter or value was entered in the NLS parameter string in a SQL function.
Action: Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.
ORA-12703 this character set conversion is not supported
Cause: An attempt was made to use the CONVERT function to convert between two character sets, and the requested conversion is not possible due to unavailability of one or both character sets.
Action: Use character sets available on the system in the CONVERT function.
ORA-12704 character set mismatch
Cause: One of the following:
The string operands (other than an NLSPARAMS argument) to an operator or built-in function do not have the same character set.
An NLSPARAMS operand is not in the database character set.
String data with character set other than the database character set is passed to a built-in function not expecting it.
The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS.
A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the
column into which the value would be inserted.
A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column.
An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter.
Action: Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other.
ORA-12705 invalid or unknown NLS parameter value specified
Cause: There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set.
Action: Check the syntax of the ALTER SESSION statement and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION statement, see the Oracle9i SQL Reference.
ORA-12706 this CREATE DATABASE character set is not allowed
Cause: An attempt was made to create a database on an ASCII-based machine using an EBCDIC-based character set or vice versa. This is not permitted.
Action: Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported.
ORA-12707 error while getting create database NLS parameter string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12708 error while loading create database NLS parameter string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12709 error while loading create database character set
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12710 CREATE CONTROLFILE character set is not known
Cause: The character set specified when creating the control file is unknown.
Action: Specify a known character set.
ORA-12711 this CREATE CONTROLFILE character set is not allowed
Cause: It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.
Action: Create the correct control file for machine and character set.
ORA-12712 new character set must be a superset of old character set
Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set must be a superset of the old character set. For example, WE8ISO8859P1 is not a superset of the WE8DEC.
Action: Specify a superset character set.
ORA-12713 Character data loss in NCHAR/CHAR conversion
Cause: When character set conversion happens between CHAR and NCHAR either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.
Action: Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to false.
ORA-12714 invalid national character set specified
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set.
Action: Ensure that the specified national character set is valid.
ORA-12715 invalid character set specified
Cause: The character set specified is not allowed for this operation or is invalid.
Action: Ensure that the specified character set is valid.
ORA-12716 Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
Cause: CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.
Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated by methods such as export/import.
ORA-12717 Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists
Cause: NCLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.
Action: Remove NCLOB data as listed in the alert file. NCLOB data can be migrated by methods such as export/import.
ORA-12718 operation requires connection as SYS
Cause: This command can only be run when connecting as user SYS.
Action: Connect as user SYS to run this command.
ORA-12719 operation requires database is in RESTRICTED mode
Cause: This command can only be run when the database is in RESTRICTED mode.
Action: Ensure that the system is in RESTRICTED mode.
ORA-12720 operation requires database is in EXCLUSIVE mode
Cause: This command can only be run when the database is in EXCLUSIVE mode.
Action: Ensure that the system is in EXCLUSIVE mode.
ORA-12721 operation cannot execute when other sessions are active
Cause: This command can only be run when there are no other sessions active.
Action: Ensure there are no other connections to the database.
ORA-12800 system appears too busy for parallel query execution
Cause: Load on the system is too high to perform parallel queries.
Action: Re-execute serially or wait until the system load is reduced.
ORA-12801 error signaled in parallel query server string
Cause: A parallel query server reached an exception condition.
Action: Check the following error message for the cause.
ORA-12802 parallel query server lost contact with coordinator
Cause: A parallel query server lost contact with the foreground (coordinator) process/thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12803 parallel query server lost contact with another server
Cause: A parallel query server lost contact with another server.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12804 parallel query server appears to have died
Cause: Cannot find process information for a parallel query server thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12805 parallel query server died unexpectedly
Cause: A parallel query server died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services. See trace file for more details.
ORA-12806 could not get background process to hold enqueue
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
ORA-12807 process queue could not receive parallel query message
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
ORA-12808 cannot set string_INSTANCES greater than number of instances string
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement to a value larger than the number of available instances.
Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.
ORA-12809 cannot set string_INSTANCES when mounted in exclusive mode
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement while the database was mounted in exclusive mode.
Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle9i Real Application Clusters mounted in CLUSTER_DATABASE mode.
ORA-12810 PARALLEL_MAX_SERVERS must be less than or equal to string
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.
Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry.
ORA-12811 PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.
Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.
ORA-12812 only one 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 a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.
ORA-12813 value for PARALLEL or DEGREE must be greater than 0
Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.
Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.
ORA-12814 only one CACHE or NOCACHE clause may be specified
Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement.
Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.
ORA-12815 value for INSTANCES must be greater than 0
Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT.
Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.
ORA-12816 parallel create index fastpath operation
Cause: The parallel create index fastpath operation event has been set.
Action: Set this event only under the supervision Oracle development.
ORA-12817 parallel query option must be enabled
Cause: A parallel query option feature has been invoked but this option has not been enabled.
Action: Enable the parallel query option.
ORA-12818 invalid option in PARALLEL clause
Cause: An unrecognized option was used within a PARALLEL clause.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
ORA-12819 missing options in PARALLEL clause
Cause: PARALLEL clause cannot be empty.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
ORA-12820 invalid value for DEGREE
Cause: Invalid value for DEGREE was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause.
ORA-12821 invalid value for INSTANCES
Cause: An invalid value for INSTANCES was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause.
ORA-12822 duplicate option in PARALLEL clause
Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.
Action: Specify each desired PARALLEL clause option only once.
ORA-12823 default degree of parallelism may not be specified here
Cause: The PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER statement.
Action: Respecify with an explicit degree of parallelism.
ORA-12824 INSTANCES DEFAULT may not be specified here
Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.
ORA-12825 explicit degree of parallelism must be specified here
Cause: The DEGREE option was omitted from an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit degree of parallelism.
ORA-12826 hung parallel query server was killed
Cause: The parallel query server was hung and subsequently killed.
Action: Re-execute the query and report suspicious events in the trace file to Oracle Support Services if the error persists.
ORA-12827 insufficient parallel query slaves available
Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired.
Action: Either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves.
ORA-12828 Can't start parallel transaction at a remote site
Cause: PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction.
Action: Do not use PDML at remote sites.
ORA-12829 Deadlock - itls occupied by siblings at block string of file string
Cause: A parallel statement failed because all ITLS in the current block are occupied by siblings of the same transaction.
Action: Increase the value of MAXTRANS of the block or reduce the degree of parallelism for the statement. Re-execute the statement. Report suspicious events in the trace file to Oracle Support Services if the error persists.
ORA-12830 Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12831 Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
Cause: After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12832 Could not allocate slaves on all specified instances
Cause: After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query.
Action: To allow results to be returned by successfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances.
ORA-12833 Coordinator's instance not a member of parallel_instance_group
Cause: The coordinator's instance must be a member of the PARALLEL_INSTANCE_GROUP in which this operation will be run.
Action: Either add the coordinator's instance to the current PARALLEL_INSTANCE_GROUP or change PARALLEL_INSTANCE_GROUP.
ORA-12834 Instance group name, 'string', too long, must be less than string characters
Cause: The instance group name is too long.
Action: Either shorten the name or get rid of the instance group.
ORA-12835 No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to execute a query on global views.
Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP.
ORA-12838 cannot read/modify an object after modifying it in parallel
Cause: Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted.
Action: Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation.
ORA-12839 cannot modify an object in parallel after modifying it
Cause: Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted.
Action: Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation.
ORA-12840 cannot access a remote table after parallel/insert direct load txn
Cause: Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued.
Action: Commit/roll back the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction.
ORA-12841 Cannot alter the session parallel DML state within a transaction
Cause: Transaction in progress.
Action: Commit or roll back the transaction and then re-execute.
ORA-12842 schema modified during parallel execution
Cause: Schema modified during the parse phase of parallel processing.
Action: No action required.
ORA-12843 pdml lock not held properly on the table
Cause: The coodinator crashed or released the lock on the partition which the slave is trying to aquire.
Action: Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the PDML again.
ORA-12900 must specify a default temporary tablespace for a locally managed database
Cause: A locally managed database must have a temporary tablespace other than SYSTEM tablespace.
Action: Specify the default temporary tablespace when creating a locally managed database.
ORA-12901 Default temporary tablespace must be of TEMPORARY type
Cause: In a locally managed database, default temporary tablespace must be TEMPORARY type.
Action:
ORA-12902 default temporary tablespace must be SYSTEM or of TEMPORARY type
Cause: In a dictionary-managed database, default temporary tablespace must be SYSTEM or TEMPORARY type.
Action:
ORA-12903 default temporary tablespace must be an ONLINE tablespace
ORA-12904 default temporary tablespace cannot be altered to PERMANENT type
ORA-12905 default temporary tablespace cannot be brought OFFLINE
ORA-12906 cannot drop default temporary tablespace
ORA-12907 tablespace string is already the default temporary tablespace
ORA-12908 cannot specify SYSTEM as default temporary tablespace when creating database
ORA-12909 TEMPORARY keyword expected
ORA-12910 cannot specify temporary tablespace as default tablespace
Cause: An attempt was made to assign a temporary tablespace to be a user's default tablespace.
Action: Assign a permanent tablespace to be the default tablespace.
ORA-12911 permanent tablespace cannot be temporary tablespace
Cause: An attempt was made to assign a permanent tablespace to be a user's temporary tablespace.
Action: Assign a temporary tablespace to be user's temporary tablespace.
ORA-12912 Dictionary managed tablespace specified as temporary tablespace
Cause: An attempt was made to assign a dictionary managed tablespace to be a user's temporary tablespace.
Action: Assign a locally managed temporary tablespace to be the user's temporary tablespace.
ORA-12913 Cannot create dictionary managed tablespace
Cause: An attempt was made to create a dictionary managed tablespace in a database whose SYSTEM tablespace is locally managed.
Action: Create a locally managed tablespace.
ORA-12914 Cannot migrate tablespace to dictionary managed type
Cause: An attempt was made to migrate a locally managed tablespace to dictionary managed type when the database has a locally managed SYSTEM tablespace.
Action: Such an operation cannot be issued.
ORA-12915 Cannot alter dictionary managed tablespace to read write
Cause: An attempt was made to alter a dictionary managed tablespace to read write in a database whose SYSTEM tablespace is locally managed. This tablespace can only be dropped.
Action: Such an operation cannot be issued.
ORA-12920 database is already in force logging mode
Cause: The ALTER DATABASE FORCE LOGGING statement failed because the database is already in force logging mode.
Action: No action required.
ORA-12921 database is not in force logging mode
Cause: The ALTER DATABASE NO FORCE LOGGING statement failed because the database is not in force logging mode.
Action: No action required.
ORA-12922 concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING statement running in the system.
Action: Contact the database administrator who is responsible for the concurrent statement.
ORA-12923 tablespace string is in force logging mode
Cause: An attempt to alter the specified temporary tablespace failed because the tablespace is in force logging mode.
Action: Put the tablespace out of force logging mode by issuing an ALTER TABLESPACE NO FORCE LOGGING statement.
ORA-12924 tablespace string is already in force logging mode
Cause: An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode.
Action: No action required.
ORA-12925 tablespace string is not in force logging mode
Cause: An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode.
Action: No action required.
ORA-12926 FORCE LOGGING option already specified
Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once.
Action: Remove all but one of the FORCE LOGGING options.
ORA-12980 checkpoint option not allowed with SET UNUSED
Cause: An attempt was made to specify checkpoint option with SET UNUSED.
Action: Remove the checkpoint option.
ORA-12981 cannot drop column from an object type table
Cause: An attempt was made to drop a column from an object type table.
Action: This action is not allowed.
ORA-12982 cannot drop column from a nested table
Cause: An attempt was made to drop a column from a nested table.
Action: This action is not allowed.
ORA-12983 cannot drop all columns in a table
Cause: An attempt was made to drop all columns in a table.
Action: Make sure at least one column remains in the table after the drop column operation.
ORA-12984 cannot drop partitioning column
Cause: An attempt was made to drop a column used as the partitioning key.
Action: This action is not allowed.
ORA-12985 tablespace 'string' is read only, cannot drop column
Cause: An attempt was made to drop column from a partition/subpartition on a read-only tablespace.
Action: Set the tablespace to read write and resubmit statement.
ORA-12986 columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE
Cause: An attempt was made to access a table with columns in partially dropped state (that is, drop column operation was interrupted).
Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table.
ORA-12987 cannot combine drop column with other operations
Cause: An attempt was made to combine drop column with other ALTER TABLE operations.
Action: Ensure that drop column is the sole operation specified in ALTER TABLE.
ORA-12988 cannot drop column from table owned by SYS
Cause: An attempt was made to drop a column from a system table.
Action: This action is not allowed.
ORA-12989 invalid value for checkpoint interval
Cause: An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1).
Action: Correct checkpoint interval and resubmit statement.
ORA-12990 duplicate option specified
Cause: Duplicate option specified in statement.
Action: Remove the duplicate option and resubmit statement.
ORA-12991 column is referenced in a multi-column constraint
Cause: An attempt was made to drop a column referenced by some constraints.
Action: Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement.
ORA-12992 cannot drop parent key column
Cause: An attempt was made to drop a parent key column.
Action: Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement.
ORA-12993 tablespace 'string' is offline, cannot drop column
Cause: An attempt was made to drop a column from a partition/subpartition on an offline tablespace.
Action: Bring the tablespace online and resubmit statement.
ORA-12994 drop column option only allowed once in statement
Cause: An attempt was made to repeat the drop column option in a single statement.
Action: Separate drop column options into different statements and resubmit statements.
ORA-12995 no columns in partially dropped state
Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns.
Action: Cannot submit this statement.
ORA-12996 cannot drop system-generated virtual column
Cause: An attempt was made to drop a virtual column generated by the system.
Action: This action is not allowed.
ORA-12997 cannot drop primary key column from an index-organized table
Cause: An attempt was made to drop a primary key column from an index- organized table.
Action: This action is not allowed.
ORA-13000 dimension number is out of range
Cause: The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.
Action: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.
ORA-13001 dimensions mismatch error
Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match.
Action: Make sure that the number of dimensions in the HHCODEs match.
ORA-13002 specified level is out of range
Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.
Action: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE.
ORA-13003 the specified range for a dimension is invalid
Cause: The specified range for a dimension is invalid.
Action: Make sure that the lower bound (lb) is less than the upper bound (ub).
ORA-13004 the specified buffer size is invalid
Cause: The buffer size for a function is not valid.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13005 recursive HHCODE function error
Cause: An error occurred in a recursively called HHCODE function.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13006 the specified cell number is invalid
Cause: The cell identifier is either less than 0 or greater than (2^ndim - 1).
Action: Make sure that the cell identifier is between 0 and (2^ndim - 1).
ORA-13007 an invalid HEX character was detected
Cause: A character that is not in the range [0-9] or [A-Fa-f] was detected.
Action: Verify that all characters in a string are in the range [0-9] or [A-Fa-f].
ORA-13008 the specified date format has an invalid component
Cause: Part of the specified date format is invalid.
Action: Verify that the date format is valid.
ORA-13009 the specified date string is invalid
Cause: The specified date string has a bad component or does not match the specified format string.
Action: Make sure that the components of the date string are valid and that the date and format strings match.
ORA-13010 an invalid number of arguments has been specified
Cause: An invalid number of arguments was specified for an SDO function.
Action: Verify the syntax of the function call.
ORA-13011 value is out of range
Cause: A specified dimension value is outside the range defined for that dimension.
Action: Make sure that all values to be encoded are within the defined dimension range.
ORA-13012 an invalid window type was specified
Cause: An invalid window type was specified.
Action: Valid window types are RANGE, PROXIMITY, POLYGON.
ORA-13013 the specified topology was not INTERIOR or BOUNDARY
Cause: A topology was specified that was not INTERIOR or BOUNDARY.
Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE's topology.
ORA-13014 a topology identifier outside the range of 1 to 8 was specified
Cause: A topology identifier outside the range of 1 to 8 was specified.
Action: Specify a topology in the range of 1 to 8.
ORA-13015 the window definition is not valid
Cause: The number of values used to define the window does not correspond to the window type.
Action: Verify that the number of values used to define the window is correct for the window type and number of dimensions.
ORA-13016 bad partition definition
Cause: The partition common code was not correctly decoded.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13017 unrecognized line partition shape
Cause: The shape of a 2-D line partition could not be determined.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13018 bad distance type
Cause: The specified distance type is invalid.
Action: The only supported distance functions are EUCLID and MANHATTAN.
ORA-13019 coordinates out of bounds
Cause: Vertex coordinates lie outside the valid range for the specified dimension.
Action: Re-define vertex coordinates within specified boundaries.
ORA-13020 coordinate is NULL
Cause: A vertex coordinate has a NULL value.
Action: Re-define vertex coordinate to have a non-NULL value.
ORA-13021 element not continuous
Cause: The coordinates defining a geometric element are not connected.
Action: Re-define coordinates for the geometric element.
ORA-13022 polygon crosses itself
Cause: The coordinates defining a polygonal geometric element represent crossing segments.
Action: Re-define the coordinates for the polygon.
ORA-13023 interior element interacts with exterior element
Cause: An interior element of a geometric object interacts with the exterior element of that object.
Action: Re-define coordinates for the geometric elements.
ORA-13024 polygon has less than three segments
Cause: The coordinates defining a polygonal geometric element represent less than three segments.
Action: Re-define the coordinates for the polygon.
ORA-13025 polygon does not close
Cause: The coordinates defining a polygonal geometric element represent an open polygon.
Action: Re-define the coordinates of the polygon.
ORA-13026 unknown element type for element string.string.string
Cause: The SDO_ETYPE column in the layer_SDOGEOM table contains an invalid geometric element type value.
Action: Re-define the geometric element type in the layer_SDOGEOM table for the specified geometric element using one of the supported SDO_ETYPE values. See the Oracle Spatial User's Guide and Reference for an explanation of SDO_ETYPE and its possible values.
ORA-13027 unable to read dimension definition from string
Cause: There was a problem reading the dimension definition from the layer_SDODIM table.
Action: Verify that the layer_SDODIM table exists and that the appropriate privileges exist on the table. Address any other errors that might appear with the message.
ORA-13028 Invalid Gtype in the SDO_GEOMETRY object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid gtypes.
ORA-13029 Invalid SRID in the SDO_GEOMETRY object
Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range.
Action: Verify that the geometries have valid SRIDs.
ORA-13030 Invalid dimension for the SDO_GEOMETRY object
Cause: There is a mismatch between the dimension in the SDO_GTYPE and the dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.
Action: Verify that the geometries have valid dimensionality.
ORA-13031 Invalid Gtype in the SDO_GEOMETRY object for point object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are NULL but the SDO_GTYPE is not of type POINT.
Action: Verify that the geometries have valid gtypes.
ORA-13032 Invalid NULL SDO_GEOMETRY object
Cause: There are invalid SDO_POINT_TYPE, SDO_ELEM_INFO_ARRAY, or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid fields. To specify a NULL Geometry, specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL.
ORA-13033 Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. The triplets in this field do not make up a valid geometry.
Action: Verify that the geometries have valid data.
ORA-13034 Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the SDO_GEOMETRY object. The coordinates in this field do not make up a valid geometry. There may be NULL values for X, Y, or both.
Action: Verify that the geometries have valid data.
ORA-13035 Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates.
Action: Verify that the geometries have valid data.
ORA-13036 Operation [string] not supported for Point Data
Cause: The specified geometry function is not supported for Point data.
Action: Make sure that the specified geometry function is not called on point data.
ORA-13037 SRIDs do not match for the two geometries
Cause: A Spatial operation is invoked with two geometries where one geometry has an SRID and the other geometry does not have an SRID.
Action: Make sure that the spatial operations are invoked between two geometries with compatible SRIDs.
ORA-13039 failed to update spatial index for element string.string.string
Cause: Another error will accompany this message that will indicate the problem.
Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.
ORA-13040 failed to subdivide tile
Cause: This is an internal error.
Action: Note any accompanying errors and contact Oracle Support Services.
ORA-13041 failed to compare tile with element string.string.string
Cause: The spatial relationship between a generated tile and the specified element could not be determined.
Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any errors which accompany ORA-13041 and contact Oracle Support Services.
ORA-13042 invalid SDO_LEVEL and SDO_NUMTILES combination
Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the layer_SDOLAYER table. The most likely cause is that the columns are NULL.
Action: Verify that the SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial User's Guide and Reference. Retry the operation.
ORA-13043 failed to read meta data from the layer_SDOLAYER table
Cause: An error was encountered reading the layer meta data from the layer_SDOLAYER table.
Action: This error is usually the result of an earlier error which should also have been reported. Address this accompanying error and retry the current operation. If no accompanying error was reported, then contact Oracle Support Services.
ORA-13044 the specified tile size exceeds the maximum resolution
Cause: The tile size specified for fixed size tessellation exceeds the maximum resolution as computed from the layer meta data.
Action: See the Oracle Spatial User's Guide and Reference for an explanation of tiling levels, tile size, and tiling resolution. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. This can be achieved by using a fewer number of tiles per geometric object or specifying a lesser tile size value than the current one.
ORA-13045 invalid compatibility flag
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13046 invalid number of arguments
Cause: An invalid number of arguments was specified for an SDO_GEOM function.
Action: Refer to the Oracle Spatial User's Guide and Reference for a description of the syntax and semantics of the relevant SDO_GEOM function.
ORA-13047 unable to determine ordinate count from table layer_SDOLAYER
Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer layer.
Action: Verify that the layer_SDOLAYER table has a valid value for the column SDO_ORDCNT. Retry the operation.
ORA-13048 recursive SQL fetch error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13049 unable to determine tolerance value from table layer_SDODIM
Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer layer.
Action: Verify that the layer_SDODIM table has a valid value for the column SDO_TOLERANCE.
ORA-13050 unable to construct spatial object
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13051 failed to initialize spatial object
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13052 unsupported geometric type for geometry string.string
Cause: The geometry type for a specific instance in a layer_SDOGEOM table is not among the set of geometry types supported by the Oracle Spatial Cartridge.
Action: Check the Oracle Spatial User's Guide and Reference for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema.
ORA-13053 maximum number of geometric elements in argument list exceeded
Cause: The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded.
Action: Check the Oracle Spatial User's Guide and Reference for the syntax of the SDO_GEOM function and use fewer arguments to describe the geometry, or check the description of the SDO_WINDOW package for a workaround that permits storing the object in a table and then using it as an argument in a call to the SDO_GEOM function.
ORA-13054 recursive SQL parse error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13055 Oracle object string does not exist in specified table
Cause: The requested object is not present in the specified table.
Action: Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Retry the operation.
ORA-13108 spatial table string not found
Cause: The specified spatial table does not exist.
Action: Check the Spatial Data option data dictionary to make sure that the table is registered.
ORA-13109 spatial table string exists
Cause: The specified spatial table is registered in the Spatial Data option data dictionary.
Action: Remove the existing table from the Spatial Data option data dictionary or use a different name.
ORA-13110 spatial table string is not partitioned
Cause: The specified spatial table is not partitioned.
Action: Check the Spatial Data option data dictionary and make sure that a high water mark is set.
ORA-13111 spatial table string has no partition key defined
Cause: The specified spatial table does not have a partition key defined.
Action: Check the Spatial Data option data dictionary and make sure that the table is partitioned.
ORA-13112 invalid count mode string
Cause: The specified count mode is not valid.
Action: Alter the count mode. Valid count modes are ESTIMATE or EXACT.
ORA-13113 Oracle table string does not exist
Cause: The specified Oracle table does not exist.
Action: Check the Oracle7 data dictionary and make sure that the table exists.
ORA-13114 tablespace string not found
Cause: The specified tablespace does not exist.
Action: Check the Oracle7 data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it.
ORA-13115 tablespace string is already allocated
Cause: The specified tablespace is already allocated to the spatial table.
Action: Allocate another tablespace name to the table.
ORA-13116 tablespace string is not allocated to table string
Cause: The specified tablespace is not allocated to the specified spatial table.
Action: Allocate the tablespace to the spatial table.
ORA-13117 partition string not found
Cause: The specified partition does not exist.
Action: Verify the name of the partition by checking the Spatial Data option data dictionary.
ORA-13119 source and target tablespaces are identical
Cause: Identical source and target tablespaces were specified when trying to move partition.
Action: Specify different source and target tablespaces if you wish to move a partition.
ORA-13121 failed to create child partition
Cause: The creation of a child partition failed.
Action: Check for other errors that accompany this error and correct them first.
ORA-13122 child partition string not found
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13123 column string is already defined
Cause: The specified column is already defined for the spatial table.
Action: Use a different column name.
ORA-13124 unable to determine column id for column string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13125 partition key is already set
Cause: A partition key is already set for the spatial table.
Action: Only one partition key can be specified per spatial table.
ORA-13126 unable to determine class for spatial table string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13127 failed to generate target partition
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13128 current tiling level exceeds user specified tiling level
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13129 HHCODE column string not found
Cause: The specified spatial column does not exist.
Action: Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary.
ORA-13135 failed to alter spatial table
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13136 null common code generated
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13137 failed to generate tablespace sequence number
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13138 could not determine name of object string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13139 could not obtain column definition for string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13140 invalid target type
Cause: The specified target type is not valid.
Action: Substitute a valid target type. Valid target types are TABLE or VIEW.
ORA-13141 invalid RANGE window definition
Cause: The RANGE window specified is not correctly defined.
Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (for example, such as: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values.
ORA-13142 invalid PROXIMITY window definition
Cause: The PROXIMITY window specified is not correctly defined.
Action: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values.
ORA-13143 invalid POLYGON window definition
Cause: The POLYGON window specified is not correctly defined.
Action: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values.
ORA-13144 target table string not found
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13145 failed to generate range list
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13146 could not find table substitution variable string
Cause: The partition name substitution variable string was not found in the SQL filter.
Action: The substitution variable string must be in the SQL filter to indicate where that partition name should be placed.
ORA-13147 failed to generate MBR
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13148 failed to generate SQL filter
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13149 failed to generate next sequence number for spatial table string
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13150 failed to insert exception record
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
ORA-13151 failed to remove exception record
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
ORA-13152 invalid HHCODE type
Cause: The specified HHCODE type is not valid.
Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.
ORA-13153 invalid high water mark specified
Cause: The highwater mark must be greater than or equal to zero.
Action: Make sure that the highwater mark is an integer greater than or equal to zero.
ORA-13154 invalid precision specified
Cause: The precision specified is out of range.
Action: The precision must be an integer greater than or equal to zero.
ORA-13155 invalid number of dimensions specified
Cause: The number of dimensions specified is out of range.
Action: The number of dimensions must be between 1 and 32.
ORA-13156 table to be registered string.string is not empty
Cause: The specified table has rows in it.
Action: Make sure that the table to be registered is empty.
ORA-13157 Oracle error ORAstring encountered while string
Cause: The specified Oracle error was encountered.
Action: Correct the Oracle error.
ORA-13158 Oracle object string does not exist
Cause: The specified object does not exist.
Action: Verify that the specified object exists.
ORA-13159 Oracle table string already exists
Cause: The specified table already exists.
Action: Drop the specified table.
ORA-13181 unable to determine length of column string_SDOINDEX.SDO_CODE
Cause: The length of the SDO_CODE column in the layer_SDOINDEX table could not be determined.
Action: Make sure that the layer_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Retry the operation.
ORA-13182 failed to read element string.string.string
Cause: The specified element could not be read from the layer_SDOGEOM table.
Action: Verify that the specified element exists in the table. Retry the operation.
ORA-13183 unsupported geometric type for geometry string.string
Cause: The geometry type in the layer_SDOGEOM table is unsupported.
Action: Modify the geometry type to be one of the supported types.
ORA-13184 failed to initialize tessellation package
Cause: Initialization of the tessellation package failed.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13185 failed to generate initial HHCODE
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13186 fixed tile size tessellation failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13187 subdivision failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13188 cell decode failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13189 recursive SQL parse failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13190 recursive SQL fetch failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13191 failed to read SDO_ORDCNT value
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13192 failed to read number of element rows
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13193 failed to allocate space for geometry
Cause: There was insufficient memory to read the geometry from the database.
Action: Validate the geometry. Record the error messages that are returned and contact Oracle Support Services.
ORA-13194 failed to decode supercell
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13195 failed to generate maximum tile value
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13196 failed to compute supercell for element string.string.string
Cause: The system was unable to compute the minimum bounding HHCODE or supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
ORA-13197 element string.string.string is out of range
Cause: Tessellation did not generate any tiles for this element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the layer_SDODIM table.
Action: Verify that the geometry is valid and within the defined domain.
ORA-13198 Spatial Cartridge error: string
Cause: Internal error in some Spatial Cartridge stored procedure.
Action: Record the sequence of procedure calls or events that preceeded this error and contact Oracle Support Services if the error message text does not clearly specify the cause of the error.
ORA-13199 string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13200 internal error [string] in spatial indexing.
Cause: This is an internal error.
Action: Contact Oracle Support Services with the exact error text.
ORA-13201 invalid parameters supplied in CREATE INDEX statement
Cause: An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement.
Action: Check the Spatial Cartridge User Guide for the number, syntax, and semantics of expected parameters for spatial index creation.
ORA-13202 failed to create or insert into the SDO_INDEX_METADATA table
Cause: An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it.
Action: Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace.
ORA-13203 failed to read USER_SDO_GEOM_METADATA table
Cause: An error was encountered while trying to read USER_SDO_GEOM_METADATA table.
Action: Check that USER_SDO_GEOM_METADATA has an entry for the current geometry table.
ORA-13204 failed to create spatial index table
Cause: An error was encountered while trying to create the index table.
Action: Check that user has create table privilege in the current schema and that the user has sufficient quota in the default or specified tablespace.
ORA-13205 internal error while parsing spatial parameters
Cause: An internal error was encountered while parsing the spatial parameters.
Action: Check to make sure that the parameters passed in the parameter string are all valid.
ORA-13206 internal error [string] while creating the spatial index
Cause: An internal error was encountered while creating the spatial index.
Action: Contact Oracle Support Services with the exact error text.
ORA-13207 incorrect use of the [string] operator
Cause: An error was encountered while evaluating the specified operator.
Action: Check the parameters and the return type of the specified operator.
ORA-13208 internal error while evaluating [string] operator
Cause: An internal error was encountered.
Action: Contact Oracle Support Services with the exact error text.
ORA-13209 internal error while reading SDO_INDEX_METADATA table
Cause: An internal error was encountered while trying to read SDO_INDEX_METADATA table.
Action: Contact Oracle Support Services. Note this and accompanying error numbers.
ORA-13210 error inserting data into the index table
Cause: An error was encountered while trying to insert data into the index table. Likely causes are:
Insufficient quota in the current tablespace
User does not appropriate privileges
Action: Check the accompanying error messages.
ORA-13211 failed to tessellate the window object
Cause: An internal error was encountered while trying to tessellate the window object.
Action: Verify the geometric integrity of the window object using the VALIDATE_GEOMETRY procedure.
ORA-13212 failed to compare tile with the window object
Cause: The spatial relationship between a generated tile and the specified window object could not be determined.
Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any accompanying errors and contact Oracle Support Services.
ORA-13213 failed to generate spatial index for window object
Cause: Another error, indicating the real cause of the problem, should accompany this error.
Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.
ORA-13214 failed to compute supercell for window object
Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
ORA-13215 window object is out of range
Cause: Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the USER_SDO_GEOM_METADATA view.
Action: Verify that the geometry is valid and within the defined domain.
ORA-13216 failed to update spatial index
Cause: Another error will accompany this message that will indicate the problem.
Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.
ORA-13217 invalid parameters supplied in ALTER INDEX statement
Cause: An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement.
Action: Check the Oracle Spatial User's Guide and Reference for the number, syntax, and semantics of expected parameters for spatial alter index command.
ORA-13218 max number of supported index tables reached for [string] index
Cause: An add_index parameter is passed to ALTER INDEX when the number of existing index tables is already at maximum.
Action: Delete one of the index tables before adding another index table.
ORA-13219 failed to create spatial index table [string]
Cause: An error was encountered while trying to create the index table.
Action: There is a table in the index's schema with the specified name. The create index will try to create an index table with this name. Either rename this table or change the name of the index.
ORA-13220 failed to compare tile with the geometry
Cause: The spatial relationship between a generated tile and the specified geometry could not be determined.
Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any errors which accompany ORA-13220 and contact Oracle Support Services.
ORA-13221 unknown geometry type in the geometry object
Cause: The SDO_GTYPE attribute in the geometry object contains an invalid value.
Action: Re-define the geometric type in the geometry table using one of the supported SDO_GTYPE values. See the Oracle Spatial User's Guide and Reference for an explanation of SDO_GTYPE and its possible values.
ORA-13222 failed to compute supercell for geometry in string
Cause: The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
ORA-13223 duplicate entry for string in SDO_GEOM_METADATA table
Cause: There are duplicate entries for the given table and column value pair in the SDO_GEOM_METADATA table
Action: Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the SDO_GEOME_METADATA table.
ORA-13224 specified index name is too long for a spatial index
Cause: An index name was specified which is longer than the supported length of the spatial index name.
Action: Check the supported size of the index name and reduce the size of the index name.
ORA-13225 specified index table name is too long for a spatial index
Cause: An index table name was specified which is longer than the supported length of the spatial index table name.
Action: Check the supported size of the index table name and reduce the size of the index name.
ORA-13226 interface not supported without a spatial index
Cause: The geometry table does not have a spatial index.
Action: Verify that the geometry table referenced in the spatial operator has a spatial index on it.
ORA-13227 SDO_LEVEL values for the two index tables do not match
Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match.
Action: Verify that two compatible indexes are used for the spatial join operator. Indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values.
ORA-13228 Spatial index create failed due to invalid type
Cause: An Attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY.
Action: Make sure that the index is created on a column of type SDO_GEOMETRY.
ORA-13230 failed to create temporary table [string] during R-tree creation
Cause: The specified temporary table either already exists or there is not enough tablespace.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.
ORA-13231 failed to create index table [string] during R-tree creation
Cause: The specified index table either already exists or there is not enough tablespace. Otherwise, contact Oracle Support Services.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.
ORA-13232 failed to allocate memory during R-tree creation
Cause: This feature assumes a minimum of 64 KB memory for bulk creation.
Action: Create the index for a small subset of the data. Then, use transactional inserts for the rest.
ORA-13233 failed to create sequence number [string] for R-tree
Cause: The specified sequence number exists.
Action: Delete the sequence object or contact Oracle Support Services.
ORA-13234 failed to access R-tree-index table [string]
Cause: The index table is either deleted or corrupted.
Action: Rebuild the index or contact Oracle Support Services with accompanying error messages.
ORA-13236 internal error in R-tree processing: [string]
Cause: An internal error occurred in R-tree processing.
Action: Contact Oracle Support Services with message text.
ORA-13237 internal error during R-tree concurrent updates: [string]
Cause: An inconsistency was encountered during concurrent updates possibly due to the use of serializable isolation level.
Action: Change the isolation level to "read committed" using alter session or contact Oracle Support Services with the message text.
ORA-13239 sdo_dimensionality not specified during n-d R-tree creation
Cause: An error occurred in reading the dimensionality parameter.
Action: Check the documentation for a valid range and specify the dimensionality as a parameter.
ORA-13240 specified dimensionality greater than that of the query mbr
Cause: An error occurred because of too few values in query mbr.
Action: Omit the dimensionality or use the dimensionality of the query.
ORA-13241 specified dimensionality does not match that of the data
Cause: An error occurred because the dimensionality specified in the CREATE INDEX does not match that of the data.
Action: Change it to the data dimensionality.
ORA-13242 failed to read tolerance values for n-d R-tree
Cause: An error occurred in reading the information for the specified table and column in USER_SDO_GEOM_METADATA table.
Action: Insert appropriate row specifying the tolerance.
ORA-13243 specified operator is not supported for n-d R-tree: [string]
Cause: Currently, an n-d R-tree only supports sdo_filter operator.
Action: Check the documentation for querytype parameters for sdo_filter or contact Oracle Support Services.
ORA-13249 string
Cause: An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component.
Action: Contact Oracle Support Services with the exact error text.
ORA-13250 insufficient privileges to modify metadata table entries
Cause: The user requesting the operation does not have the appropriate privileges on the referenced tables.
Action: Check that the specified feature and geometry table names are correct and then verify that the current user has at least SELECT privilege on those tables.
ORA-13251 duplicate entry string in metadata table
Cause: The specified entry already exists in the metadata table.
Action: Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once.
ORA-13260 layer table string does not exist
Cause: Data migration source table layer_SDOGEOM does not exist.
Action: Ensure that the specified layername is correct and that the corresponding spatial layer tables exist in the current schema.
ORA-13261 geometry table string does not exist
Cause: The specified geometry table does not exist in the current schema.
Action: Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values.
ORA-13262 geometry column string does not exist in table string
Cause: The specified table does not have a column of type SDO_GEOMETRY.
Action: Alter or recreate the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER.
ORA-13263 column string in table string is not of type SDO_GEOMETRY
Cause: The column intended for storing the geometry is not of type SDO_GEOMETRY.
Action: Alter the column definition to be of type SDO_GEOMETRY.
ORA-13264 geometry identifier column string does not exist in table string
Cause: The specified table does not contain a GID column.
Action: Confirm that the GID columnname was correctly specified and that it exists in the specified table.
ORA-13265 geometry identifier column string in table string is not of type NUMBER.
Cause: GID column is not of type NUMBER.
Action: Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER.
ORA-13266 error inserting data into table string
Cause: An OCI error occurred or the user has insufficient quota in the active tablespace or the rollback segments are too small.
Action: There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem.
ORA-13267 error reading data from layer table string
Cause: There was an error reading the geometry data from the layer_SDOGEOM table.
Action: Verify that layer_SDOGEOM and layer_SDODIM exist. If they do exist, then run VALIDATE_GEOMETRY on the specified layer.
ORA-13268 error obtaining dimension from USER_SDO_GEOM_METADATA
Cause: There is no entry in USER_SDO_GEOM_METADATA for the specified geometry table.
Action: Insert an entry for the destination geometry table with the dimension information obtained from the source layer_SDODIM table.
ORA-13269 internal error [string] encountered when processing geometry table
Cause: An internal error occurred.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13270 OCI error string
Cause: An OCI error occurred while processing the layer or geometry tables.
Action: Take the appropriate steps to correct the OCI specific error.
ORA-13271 error allocating memory for geometry object
Cause: Insufficient memory.
Action: Make more memory available to the current session/process.
ORA-13272 geometric object string in table string is invalid
Cause: The specified object failed the geometric integrity checks performed by VALIDATE_GEOMETRY.
Action: Consult the Oracle Spatial User's Guide and Reference for information on the geometric integrity checks performed by VALIDATE_GEOMETRY and correct the geometry definition if required.
ORA-13273 dimension metadata table string does not exist
Cause: The layer_SDODIM table does not exist.
Action: Verify that the specified layer name is correct and that the layer_SDODIM table exists in the current schema.
ORA-13274 Operator invoked with non compatible SRIDs
Cause: A Spatial operator was invoked with a window geometry with an SRID and the layer without an SRID or window has no SRID and the layer has an SRID.
Action: Make sure that the layer and window both have an SRID or they both do not have an SRID.
ORA-13275 Spatial index creation failure on unsupported type
Cause: A spatial index create was invoked on a column that is not of type SDO_GEOMETRY.
Action: Spatial index can only be created on a column of type SDO_GEOMETRY. Make sure the indexed column has SDO_GEOMETRY type.
ORA-13276 internal error [string] in coordinate transformation
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13278 failure to convert SRID to native format
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13281 failure in execution of sql statement to retrieve WKT
Cause: OCI internal error or SRID does not match a table entry.
Action: Check that a valid SRID is being used.
ORA-13282 failure on initialization of coordinate transformation
Cause: Parsing error on source or destination coordinate system WKT or incompatible coordinate systems.
Action: Check validity of WKT for table entries and the legitimacy of the requested transformation.
ORA-13283 failure to get new geometry object for conversion in place
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13284 failure to copy geometry object for conversion in place
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13285 Geometry coordinate transformation error
Cause: A coordinate pair was out of valid range for a conversion/projection.
Action: Check that data to be transformed is consistent with the desired conversion/projection.
ORA-13287 can't transform unknown gtype
Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed.
Action:
ORA-13288 Point coordinate transformation error
Cause: An internal error while transforming points.
Action: Check the accompanying error messages.
ORA-13290 The specified unit is not supported
Cause: Spatial function called with an unknown UNIT.
Action: Check the supported units by Spatial and call the spatial function with the correct UNIT parameter.
ORA-13291 Conversion error between the specified unit and standard unit
Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.
Action: Check unit specification and respecify it.
ORA-13292 Incorrect ARC_TOLERANCE specification
Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a Geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be specified and it should not be less than the tolerance specified for the geometry.
Action: Check ARC_TOLERANCE specification and make sure it is correct.
ORA-13293 Cannot specify unit for geometry without a georeferenced SRID
Cause: A Spatial function with unit parameter is called on a geometry without a georeferenced SRID.
Action: Make sure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs.
ORA-13294 Cannot transform geometry containing circular arcs
Cause: It is impossible to transform a 3-point representation of a circular arc without distortion.
Action: Make sure a geometry does not contain circular arcs.
ORA-13295 Geometry objects are in different coordinate systems
Cause: A Spatial function is called with two geometries with two different SRIDs.
Action: Transform geometry objects to be in the same coordinate system and call the spatial function.
ORA-13296 Incorrect Coordinate System Specification
Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID.
Action: Check WKT in CS_SRS table for Earth radius and inverse flattening.
ORA-13300 Single point transform error
Cause: Low level coordinate transformation error trap.
Action: Check the accompanying error messages.
ORA-13303 failure to retrieve a geometry object from a table
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13304 failure to insert a transformed geometry object in a table
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13330 invalid MASK
Cause: The MASK you passed to RELATE function is not valid.
Action: Verify that the mask is not NULL. See the Oracle Spatial User's Guide and Reference for a list of supported masks.
ORA-13331 invalid LRS segment
Cause: The given LRS segment was not a valid linestring.
Action: A valid LRS geometric segment is a line string geometry in Oracle Spatial. It could be a simple or compound line string (made of lines or arcs, or both). The dimension information must include the measure dimension as the last element in Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or latitude/longitude plus measure).
ORA-13332 invalid LRS point
Cause: Given LRS point was not a point-geometry with measure information.
Action: Check the given point geometry.A valid LRS point is a point geometry in Oracle Spatial with additional measure dimension.
ORA-13333 invalid LRS measure
Cause: The given measure for linear referencing was out of range.
Action: Re-define the given measure.
ORA-13334 LRS segments not connected
Cause: The given geometric segments were not connected.
Action: Check the start/end points of the given geometric segments.
ORA-13335 LRS measure information not defined
Cause: The measure information of a given geometric segments was not assigned (IS NULL).
Action: Assign/define the measure information. An LRS geometric segment is defined if its start and end measure are assigned (non-null).
ORA-13336 Failure in converting standard diminfo/geometry to LRS dim/geom
Cause: No room for measure dimension in the given diminfo or the given standard geometry is not a point a linestring.
Action: Check if the diminfo dimensions are less than 3 or given geometry type is point or linestring.
ORA-13337 failure in concatenating LRS polygons
Cause: LRS concatenation involving LRS polygons is not supported.
Action: Check geometry and element type to make sure the concatenate operation is not called with a polygon type.
ORA-13338 failure in reversing LRS polygon/collection geometry
Cause: Reversing an LRS polygon/collection geometry produces an invalid geometry as this operation is not well defined for polygon geometry.
Action: Check the geometry type to make sure this operation is called on non polygon type geometry.
ORA-13339 LRS Polygon clipping across multiple rings
Cause: Clipping (dynseg) a polygon across multiple rings.
Action: Polygon clipping only allowed for a single ring.
ORA-13340 a point geometry has more than one coordinate
Cause: A geometry, specified as being a point, has more than one coordinate in its definition.
Action: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, then set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, then remove the extraneous coordinates from its definition.
ORA-13341 a line geometry has less than two coordinates
Cause: A geometry, specified as being a line, has less than two coordinates in its definition.
Action: A line must consist of at least two distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13342 an arc geometry has less than three coordinates
Cause: A geometry, specified as being an arc, has less than three coordinates in its definition.
Action: An arc must consist of at least three distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13343 a polygon geometry has less than four coordinates
Cause: A geometry, specified as being a polygon, has less than four coordinates in its definition.
Action: A polygon must consist of at least four distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13344 an arcpolygon geometry has less than five coordinates
Cause: A geometry, specified as being an arcpolygon, has less than six coordinates in its definition.
Action: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected, the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13345 a compound polygon geometry has less than five coordinates
Cause: A geometry, specified as being a compound polygon, has less than five coordinates in its definition.
Action: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line, each of which must be described using three and at least two distinct coordinates, respectively. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13346 the coordinates defining an arc are collinear
Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates.
Action: Alter the definition or the arc or set the SDO_ETYPE or SDO_GTYPE to the line type.
ORA-13347 the coordinates defining an arc are not distinct
Cause: Two or more of the three points defining an arc are the same.
Action: Alter the definition of the arc, ensuring that three distinct coordinate values are used.
ORA-13348 polygon boundary is not closed
Cause: The boundary of a polygon does not close.
Action: Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry.
ORA-13349 polygon boundary crosses itself
Cause: The boundary of a polygon intersects itself.
Action: Correct the geometric definition of the object.
ORA-13350 two or more rings of a complex polygon touch
Cause: The inner or outer rings of a complex polygon touch.
Action: All rings of a complex polygon must be disjoint. Correct the geometric description of the object.
ORA-13351 two or more rings of a complex polygon overlap
Cause: The inner or outer rings of a complex polygon overlap.
Action: All rings of a complex polygon must be disjoint. Correct the geometric description of the object.
ORA-13352 the coordinates do not describe a circle
Cause: The set of coordinates used to describe a circle are incorrect.
Action: Confirm that the set of coordinates actually represent points on the circumference of a circle.
ORA-13353 ELEM_INFO_ARRAY not grouped in threes
Cause: The ELEM_INFO_ARRAY in SDO_GEOMETRY has more or fewer elements than expected.
Action: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3.
ORA-13354 incorrect offset in ELEM_INFO_ARRAY
Cause: The offset field in ELEM_INFO_ARRAY of SDO_GEOMETRY references an invalid array subscript in SDO_ORDINATE_ARRAY.
Action: Confirm that the offset is a valid array subscript in SDO_ORDINATE_ARRAY.
ORA-13355 SDO_ORDINATE_ARRAY not grouped by number of dimensions specified
Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user.
Action: Confirm that the number of dimensions is consistent with data representation in SDO_ORDINATE_ARRAY.
ORA-13356 adjacent points in a geometry are redundant
Cause: There are repeated points in the sequence of coordinates.
Action: Remove the redundant point.
ORA-13357 extent type does not contain 2 points
Cause: Extent type should be represented by 2 points: lower left and upper right.
Action: Confirm that there are only 2 points for extent type.
ORA-13358 circle type does not contain 3 points
Cause: Circle type should be represented by 3 distinct points on the circumference.
Action: Confirm that there are only 3 points for circle type.
ORA-13359 extent does not have an area
Cause: The 2 points representing the extent are identical.
Action: Confirm that the 2 points describing the extent type are distinct.
ORA-13360 invalid subtype in a compound type
Cause: This subtype is not allowed within the ETYPE specified.
Action: Refer to Oracle Spatial User's Guide and Reference for type definitions.
ORA-13361 not enough sub-elements within a compound ETYPE
Cause: The compound type declare more sub-elements than actually defined.
Action: Confirm that the number of sub-elements is consistent with the compound type declaration.
ORA-13362 disjoint sub-element in a compound polygon
Cause: Compound polygon must describe an enclosed area.
Action: Confirm that all sub-elements are connected.
ORA-13363 no valid ETYPE in the geometry
Cause: None of the ETYPEs within the geometry is supported.
Action: Confirm that there is at least one valid ETYPE.
ORA-13364 Layer Dimensionality does not match geometry dimensions
Cause: Spatial layer has a geometry with a different dimensions than the dimensions specified for the layer.
Action: Make sure that all geometries in a layer have the same dimensions and they match the dimensions in the SDO_DIM_ARRAY object for the layer in USER_SDO_GEOM_METADATA.
ORA-13365 Layer SRID does not match geometry SRID
Cause: Spatial layer has a geometry with a different SRID than the SRID specified for the layer.
Action: Make sure that all geometries in a layer have the same SRID and the SRIDs match the SRID in USER_SDO_GEOM_METADATA for the layer.
ORA-13366 Invalid combination of interior exterior rings
Cause: In the Spatial geometry, interior and exterior rings are not used consistently.
Action: Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array.
ORA-13367 Wrong orientation for interior/exterior rings
Cause: In a spatial geometry, the exterior and/or interior rings are not oriented correctly.
Action: The exterior rings should be oriented counter clock-wise and interior rings should be oriented clock wise.
ORA-13368 Simple Polygon type has more than one exterior ring
Cause: In a polygon type geometry, there is more than one exterior ring.
Action: Set the type to be multi-polygon if more than one exterior is present in the geometry.
ORA-13369 Invalid value for etype in the 4 digit format
Cause: A 4 digit etype for non polygon type element is used or the orientation is not a valid orientation for interior/exterior rings of the polygon.
ORA-13370 failure in applying 3D LRS functions
Cause: Only Non-geodetic 3D linestring geometry (made of line segments) are supported for 3D LRS package.
Action: Check the geometry and element types and SRID.
ORA-13371 invalid position of measure dimension
Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in dim_info_array.
Action: Check geometry gtype and its dim_info_array.
ORA-13372 failure in modifying metadata for a table with spatial index
Cause: Modifying the metadata after the index is created will cause inconsistency between geometry gtype and diminfo.
Action: Modify(or Prepare) metadata before creating index on sdo_geometry column.
ORA-13373 Element of type Extent is not supported for Geodetic data
Cause: Element type extent for a polygon geometry is not supported for geodetic data.
Action: Convert the extent type polygon to a regular 5 point polygon and set etype accordingly.
ORA-13374 SDO_MBR not supported for geodetic data
Cause: The SDO_MBR functionality is not supported for geodetic data.
Action: Find an alternative function that can be used in this context.
ORA-13375 The layer is of type [string] while geometry inserted has type [string]
Cause: The layer has a type that is different or inconsistent with the type of the current geometry.
Action: Change the geometry type to agree with the layer type or change the layer type to agree with the geometry type.
ORA-13376 Invalid type name specified for layer_gtype parameter
Cause: An invalid type name is specified for the layer gtype constraint.
Action: Consult the Oracle Spatial User's Guide and Reference to get a list of valid layer gtypes that can be used in defining a layer gtype constraint.
ORA-13377 Invalid combination of elements with orientation
Cause: An element of the geometry has orientation specified while some other element has no orientation specified (4 digit etype).
Action: Make sure all the polygon elements have orientation specified using the 4 digit etype notation.
ORA-13378 Invalid index for element to be extracted
Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the given geometry.
ORA-13379 Invalid index for sub-element to be extracted
Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the given geometry.
ORA-13400 Oracle GeoImage internal error, arguments: [string], [string], [string], [string], [string]
Cause: This is an internal Oracle GeoImage error.
Action: Contact Oracle Support Services.
ORA-13401 unsupported geoimage format
Cause: The GeoImage format is not supported.
Action: Confirm that the GeoImage format is valid and supported.
ORA-13402 NULL destination
Cause: The object specified as the destination is NULL.
Action: Confirm that the object specified as the destination is not NULL.
ORA-13403 NULL source geometry
Cause: The source GeoImage has a NULL geometry.
Action: Verify that the geometry of the source GeoImage is not NULL.
ORA-13404 not a local source
Cause: An attempt has been made to modify a GeoImage which is not stored in the database.
Action: Import the GeoImage in order to modify it.
ORA-13405 NULL source
Cause: The object specified as the source is NULL.
Action: Confirm that the object specified as the source is not NULL.
ORA-13406 unsupported image processing command [string]
Cause: The image processing command specified is not supported for a GeoImage.
Action: Consult the Oracle interMedia User's Guide and Reference to verify which image processing commands are supported within an Oracle GeoImage method.
ORA-13407 unrecognized space type qualifier [string]
Cause: The GeoImage space type qualifier is invalid.
Action: Use a valid space type qualifier (RASTER or MODEL).
ORA-13408 NULL table name
Cause: The table name parameter is NULL.
Action: Verify that the parameter used for the table name is not NULL.
ORA-13409 Oracle table "string" does not exist.
Cause: The table specified does not exist.
Action: Verify that the table name used is valid and the table exists.
ORA-13410 NULL column name
Cause: The column name parameter is NULL.
Action: Verify that the parameter used for the column name is not NULL.
ORA-13411 Oracle column "string" does not exist.
Cause: The column specified does not exist.
Action: Verify that the column name used is valid and the column exists.
ORA-13412 invalid ROWID
Cause: The ROWID value used is not valid.
Action: Verify that the ROWID value used is valid.
ORA-13413 could not select the GeoImage for initialization
Cause: The GeoImage in the table could not be selected.
Action: Verify that the GeoIMage is present in the table and the supplied parameters are valid.
ORA-13414 could not update the table containing the GeoImage
Cause: The table containing the GeoImage could not be updated.
Action: Verify that the table exists and is valid.
ORA-13415 invalid domain
Cause: The SDO_DIMINFO value used is not valid or the SDO_GEOMETRY supplied is not defined in the domain.
Action: Verify that the SDO_DIMINFO value is valid, and that the SDO_GEOMETRY is defined within the domain specified.
ORA-13416 invalid geometry, arguments [string]
Cause: The SDO_GEOMETRY value used is not valid.
Action: Verify that the SDO_GEOMETRY is valid. Consult the Oracle Spatial User's Guide and Reference for a list of valid geometries.
ORA-13417 undefined raster to model space transformation
Cause: The raster to model space transformation associated with a GeoImage is undefined.
Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format.
ORA-13418 undefined model to raster space transformation
Cause: The model to raster space transformation associated with a GeoImage is undefined.
Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format.
ORA-13419 invalid latitude value
Cause: A latitude value outside the valid range [-90,90] has been used.
Action: Verify that the GeoImage geometry definition is within the domain.
ORA-13420 invalid model to raster space transformation
Cause: The model to raster space transformation associated with a GeoImage is not valid or cannot be calculated.
Action: Verify that the transformation is supported and that the GeoImage format is valid.
ORA-13421 invalid raster to model space transformation
Cause: The raster to model space transformation associated with a GeoImage is not valid or cannot be calculated.
Action: Verify that the transformation is supported and that the GeoImage format is valid.
ORA-13422 uninitialized source
Cause: The LOB used for the source is not initialized.
Action: Verify that the source is properly initialized.
ORA-13423 empty source
Cause: The LOB used for the source is empty.
Action: Verify that the source is properly initialized and data has been imported into it.
ORA-13424 uninitialized destination
Cause: The LOB used for the destination is not initialized.
Action: Verify that the destination is properly initialized.
ORA-13425 empty destination
Cause: The LOB used for the destination is empty.
Action: Verify that the destination is properly initialized and data has been imported into it.
ORA-13426 unsupported raster origin
Cause: The raster origin specified is not supported.
Action: Verify that the origin specified is supported.
ORA-13427 unknown raster origin
Cause: The value specified for the raster origin is invalid.
Action: Verify that the value used to specify the raster origin is valid and supported.
ORA-13428 source does not exist
Cause: The source does not exist or cannot be accessed.
Action: Verify that the source specification is correct and accessible.
ORA-13429 operation "string" not supported on GeoImage type "string"
Cause: The specified operation is not supported on the particular geoimage type.
Action: Verify that the operation is supported.
ORA-13430 model coordinate system not supported
Cause: The model specified for the definition of the coordinate system is not supported.
Action: Verify that the model value is correct.
ORA-13433 NULL crop geometry
Cause: The geometry used to crop a GeoImage is NULL.
Action: Verify that the geometry used for the crop operation is not NULL.
ORA-13442 invalid scaling parameters [string] [string]
Cause: The parameters used in the scale operation are invalid.
Action: Verify that the scaling parameters are greater than zero.
ORA-13443 unrecognized scale mode [string]
Cause: The scale mode used in the scale operation is invalid.
Action: Consult the Oracle interMedia User's Guide and Reference for a list of valid scale mode qualifiers.
ORA-13451 unsupported conversion format [string]
Cause: The format specified for conversion is invalid or unsupported.
Action: Verify that the conversion format specified is valid.
ORA-13461 invalid tag/key [string]
Cause: The tag or key is invalid.
Action: Verify that the format version is supported or the format is valid.
ORA-13462 invalid tie point
Cause: One of the tie points is invalid.
Action: Verify that the tie points used are valid (for example all raster tie points are >= 0).
ORA-13463 unsupported GeoTIFF geometry definition
Cause: The combination of keys/tags used to define the geometry footprint of the GeoImage is not supported.
Action: Verify that the GeoTIFF format version is supported and the format is valid.
ORA-13464 unsupported conversion
Cause: The format specified for conversion is not supported. In GeoTIFF, only a limited number of tags/keys combinations are supported for conversion.
Action: Verify that the GeoTIFF format version is supported and conversion to the desired format is available.
ORA-13465 invalid destination window
Cause: The window specified as destination in the command is not valid.
Action: Verify that the window definition is correct.
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 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 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 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 missing PARTITION keyword
Cause: Keyword PARTITION missing.
Action: Supply missing keyword.
ORA-14005 missing RANGE keyword
Cause: Keyword RANGE missing.
Action: Supply missing keyword.
ORA-14006 invalid partition name
Cause: A partition name of the form identifier is expected but not present.
Action: Enter an appropriate partition name.
ORA-14007 missing LESS keyword
Cause: Keyword LESS missing.
Action: Supply missing keyword.
ORA-14008 missing THAN keyword
Cause: Keyword THAN missing.
Action: Supply missing keyword.
Skip Headers
Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01
Go To Documentation Library
Home Go To Product List
Book List Go To Table Of Contents
Contents Go To Index
Index
Master Index
Feedback
Go to previous page Go to next page
13
ORA-24280 to ORA-29249
ORA-24280 invalid input value for parameter string
Cause: The parameter has been provided a negative, out of range, or NULL input value.
Action: Correct the input value such that it is valid, and is within the range as specified in the documentation.
ORA-24281 invalid access past the maximum size of LOB parameter string
Cause: The value of positional or size parameters exceeds the maximum allowed LOB size of 4 Gigabytes.
Action: Correct the input values for amount and offset such that their sum is less than or equal to 4 Gigabytes. If error occurs in a read or write loop, check the looping conditions and/or offset increments.
ORA-24300 bad value for mode
Cause: An undefined mode value was specified.
Action: Check that the correct mode is selected and that an allowed value for that mode is specified.
ORA-24301 null host specified in thread-safe logon
Cause: An HDA was not specified in the logon call while running in a thread safe environment.
Action: Make sure that HDA is not NULL when calling the logon routine.
ORA-24302 host connection in use by another thread
Cause: An attempt was made to use the host connection while it was in use by another thread.
Action: Wait for another thread to finish before using this connection.
ORA-24303 call not supported in non-deferred linkage
Cause: One of the calls that is supported in deferred mode linkage exclusively was invoked when the client was linked non-deferred.
Action: Use this call in deferred mode of linkage.
ORA-24304 datatype not allowed for this call
Cause: Data of this datatype cannot be sent or fetched in pieces.
Action: Use other bind or define calls for this datatype.
ORA-24305 bad bind or define context
Cause: The call was executed on a cursor for which this is invalid.
Action: Verify that this call is valid for this cursor. For example, Get piece information and set piece information are valid on a cursor if appropriate binds and defines have been done on this cursor.
ORA-24306 bad buffer for piece
Cause: A zero length buffer or a null buffer pointer was provided.
Action: Verify that the buffer pointing to this piece or its length is non-zero. The buffer pointer for the next piece or its length can be zero if it is the last piece to be inserted and there are no more data for the column.
ORA-24307 invalid length for piece
Cause: The length of the piece exceeded the maximum possible size.
Action: Verify that the length of this piece and the cumulative length of all the previous pieces is not more than the desired value supplied by the application.
ORA-24308 illegal define position
Cause: Call to modify attributes was done for a non-existent position.
Action: Verify that a define has been done for this position.
ORA-24309 already connected to a server
Cause: This server handle is already attached to a server.
Action: Disconnect from the server and then retry the call to establish a connection.
ORA-24310 length specified for null connect string
Cause: The connect string is null, but a length was specified for it.
Action: Set length to zero if connect string is null.
ORA-24311 memory initialization failed
Cause: Cannot initialize user memory.
Action: Contact Oracle Support Services.
ORA-24312 illegal parameters specified for allocating user memory
Cause: An illegal size or null pointer was specified for user memory.
Action: Specify a legal size and a valid pointer for user memory.
ORA-24313 user already authenticated
Cause: A user has already been authenticated on this service handle.
Action: Terminate the service context before using it for another user.
ORA-24314 service handle not initialized
Cause: The server context does not done exist.
Action: Establish the server context in the service context.
ORA-24315 illegal attribute type
Cause: An illegal attribute type was specified for the handle.
Action: Consult the Oracle Call Interface Programmer's Guide to specify an attribute valid for this handle.
ORA-24316 illegal handle type
Cause: An illegal handle type was specified.
Action: Consult the Oracle Call Interface Programmer's Guide to specify a valid handle type.
ORA-24317 define handle used in a different position
Cause: A define was done with an existing handle on a different position.
Action: Specify the same position as before on a redefine.
ORA-24318 call not allowed for scalar data types
Cause: This call is valid only for object types.
Action: Verify that the data-type for this variable is an object type.
ORA-24319 unable to allocate memory
Cause: Process was unable to allocate memory to store diagnostics.
Action: Terminate other processes in order to reclaim needed memory.
ORA-24320 unable to initialize a mutex
Cause: An attempt to initialize a MUTEX failed.
Action: Contact Oracle Support Services.
ORA-24321 inconsistent parameters passed
Cause: One of the three memory function pointers is null or non-null.
Action: Verify that either all the memory functions are null or non-null.
ORA-24322 unable to delete an initialized mutex
Cause: An attempt to delete an initialized MUTEX failed.
Action: Contact Oracle Support Services.
ORA-24323 value not allowed
Cause: A null or invalid value was passed in for a mandatory parameter.
Action: Verify that all mandatory parameters are properly initialized.
ORA-24324 service handle not initialized
Cause: An attempt was made to use an improper service context handle.
Action: Verify that the service context handle has all the parameters initialized prior to this call.
ORA-24325 this OCI operation is not currently allowed
Cause: An attempt was made to use a context handle outside its scope.
Action: Verify that the context handle is set to a service context handle that has been converted to a logon data area for other OCI calls. The logon data area must be converted back to a service context before it can be used.
ORA-24326 handle passed in is already initialized
Cause: An attempt was made to pass an initialized handle.
Action: Verify that the parameter passed in to retrieve a handle does not already point to a handle.
ORA-24327 need explicit attach before authenticating a user
Cause: A server context must be initialized before creating a session.
Action: Create and initialize a server handle.
ORA-24328 illegal attribute value
Cause: The attribute value passed in is illegal.
Action: Consult the Oracle Call Interface Programmer's Guide and specify a legal attribute value for the handle.
ORA-24329 invalid character set identifier
Cause: The character set identifier specified is invalid.
Action: Specify a valid character set identifier in the OCI call.
ORA-24330 internal OCI error
Cause: An internal OCI error has occurred.
Action: Contact Oracle Support Services.
ORA-24331 user buffer too small
Cause: The user buffer to contain the output data is too small.
Action: Specify a bigger buffer.
ORA-24332 invalid object type
Cause: An invalid object type is requested for the describe call.
Action: Specify a valid object type to the describe call.
ORA-24333 zero iteration count
Cause: An iteration count of zero was specified for the statement.
Action: Specify the number of times this statement must be executed.
ORA-24334 no descriptor for this position
Cause: The application is trying to get a descriptor from a handle for an illegal position.
Action: Check the position number.
ORA-24335 cannot support more than 1000 columns
Cause: The number of columns exceeds the maximum number supported.
Action: Specify a number of columns less than 1000.
ORA-24336 invalid result set descriptor
Cause: The result set descriptor should have valid data fetched into it before it can be converted to a statement handle.
Action: Fetch valid data into the descriptor before attempting to convert it into a statement handle.
ORA-24337 statement handle not prepared
Cause: A statement cannot be executed before making preparing a request.
Action: Prepare a statement before attempting to execute it.
ORA-24338 statement handle not executed
Cause: A fetch or describe was attempted before executing a statement handle.
Action: Execute a statement and then fetch or describe the data.
ORA-24339 cannot set server group name after connecting to server
Cause: An attempt was made to set the server group in a server handle after connecting to the server. However, once the connection is established to a server, the server group name cannot be set anymore.
Action: Attach to the server after setting the server group name in the server handle.
ORA-24340 cannot support more than 255 columns
Cause: The number of columns exceeds maximum supported by the server.
Action: Limit your operation to 255 columns.
ORA-24341 bad mode specified
Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client.
Action: OCI_ENV_NO_MUTEX may be specified when OCI_THREADED had been specified at process initialization.
ORA-24342 unable to destroy a mutex
Cause: An attempt to destroy a MUTEX failed.
Action: Contact Oracle Support Services.
ORA-24343 user defined callback error
Cause: The only valid return value for a user defined callback function is OCI_CONTINUE. Any other value will cause this error.
Action: Make sure that OCI_CONTINUE is returned from the user-defined callback function.
ORA-24344 success with compilation error
Cause: A SQL or PL/SQL compilation error occurred.
Action: Return OCI_SUCCESS_WITH_INFO along with the error code.
ORA-24345 A Truncation or null fetch error occurred
Cause: A truncation or a null fetch error.
Action: Make sure that the buffer size is long enough to store the returned data.
ORA-24346 cannot execute without binding variables
Cause: None of the bind variables in the SQL statement are bound.
Action: Bind all the variables before the execute is done.
ORA-24347 Warning of a NULL column in an aggregate function
Cause: A null column was processed by an aggregate function.
Action: An OCI_SUCCESS_WITH_INFO is returned.
ORA-24348 Update or Delete without Where
Cause: An UPDATE or DELETE was executed without a WHERE clause.
Action: An OCI_SUCCESS_WITH_INFO is returned.
ORA-24350 OCI call not allowed
Cause: OCI used is not permitted from external procedures.
Action: Refer to the Oracle Call Interface Programmer's Guide for usage restrictions.
ORA-24351 invalid date passed into OCI call
Cause: A bad date was passed into one of the OCI calls.
Action: Check your date bind values and correct them.
ORA-24352 invalid COBOL display type passed into OCI call
Cause: A bad COBOL display type was passed into one of the OCI calls.
Action: Check your COBOL display type bind values and correct them.
ORA-24353 user buffer too small to accommodate COBOL display type
Cause: User supplied buffer for a COBOL display type was too small to accommodate fetched number.
Action: Increase the allocation for COBOL display type buffer.
ORA-24354 number fetched too large to fit in COBOL display type buffer.
Cause: The number fetched was beyond the range that can be displayed.
Action: Check the number in the database.
ORA-24355 attempt to store a negative number in an Unsigned Display type.
Cause: An attempt was made to convert a negative number into an unsigned display type.
Action: Check the number in the database or change the defined datatype.
ORA-24356 internal error while converting from to COBOL display type.
Cause: An internal error was encountered during conversion to COBOL display type.
Action: Contact Oracle Support Services.
ORA-24357 internal error while converting from to OCIDate.
Cause: An internal error was encountered during conversion to OCIDate type.
Action: Contact Oracle Support Services.
ORA-24358 OCIBindObject not invoked for a Object type or Reference
Cause: OCIBindObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference.
Action: Invoke the OCIBindObject call for all Object Types and References.
ORA-24359 OCIDefineObject not invoked for a Object type or Reference
Cause: OCIDefineObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference.
Action: Invoke the OCIDefineObject call for all Object Types and References.
ORA-24360 Type Descriptor Object not specified for Object Bind/Define
Cause: Type Descriptor Object is a mandatory parameter for Object Types Binds and Defines.
Action: Invoke the OCIBindObject() or OCIDefineObject() call with a valid Type Descriptor Object.
ORA-24361 basic bind call not invoked before invoking advanced bind call
Cause: One of the basic bind calls was not invoked on this bind handle before performing an advanced bind call.
Action: Invoke the advanced bind call on this bind handle only after performing a basic bind call.
ORA-24362 improper use of the character count flag
Cause: When the character count flag is set, then the maximum size of the buffer in the server should be specified as a non-zero value.
Action: Use a non-zero value for the maximum size of the buffer in the server.
ORA-24363 measurements in characters illegal here
Cause: Measurements in characters instead of bytes are illegal if either the server's or client's character set is varying width.
Action: If either the client's or server's character set is varying width then do not use the OCI_ATTR_CHAR_COUNT attribute for the bind handle. Use OCI_ATTR_MAXDATA_SIZE instead.
ORA-24364 internal error while padding blanks
Cause: An internal error has occurred while attempting to blank pad string data. This error should not occur normally.
Action: Contact Oracle Support Services.
ORA-24365 error in character conversion
Cause: This usually occurs during conversion of a multibyte character data when the source data is abnormally terminated in the middle of a multibyte character.
Action: Make sure that all multibyte character data is properly terminated.
ORA-24366 migratable user handle is set in service handle
Cause: This occurs during user authentication, a migratable user handle has been set in the service handle.
Action: Service handle must not be set with migratable user handle when it is used to authenticate another user.
ORA-24367 user handle has not been set in service handle
Cause: This occurs during authentication of a migratable user. the service handle has not been set with non-migratable user handle.
Action: Service handle must be set with non-migratable user handle when it is used to authenticate a migratable user.
ORA-24368 OCI mutex counter non-zero when freeing a handle
Cause: This is an internal OCI error.
Action: Contact Oracle Support Services.
ORA-24369 required callbacks not registered for one or more bind handles
Cause: No callbacks have been registered for one or more of the bind handles which are part of the RETURNING clause.
Action: The bind handles which are to receive data in a DML statement with a RETURNING clause must have their mode set as DATA_AT_EXEC and callback functions must be registered for these bind handles using OCIBindDynamic.
ORA-24370 illegal piecewise operation attempted
Cause: Data of a certain datatype that does not support piecewise operation is being sent or fetched in pieces.
Action: Always set the piece value to OCI_ONE_PIECE for datatypes that does not support piecewise operation.
ORA-24371 data would not fit in current prefetch buffer
Cause: An internal OCI error has occurred.
Action: Contact Oracle Support Services.
ORA-24372 invalid object for describe
Cause: The object to be described is not valid. It either has compilation or authorization errors.
Action: The object to be described must be valid.
ORA-24373 invalid length specified for statement
Cause: The length specified for the statement is either 0 or too large.
Action: Specify a valid length for the statement.
ORA-24374 define not done before fetch or execute and fetch
Cause: The application did not define output variables for data being fetched before issuing a fetch call or invoking a fetch by specifying a non-zero row count in an execute call.
Action: Issue OCI define calls for the columns to be fetched.
ORA-24375 Cannot use V6 syntax when talking to a V8 server
Cause: V6 syntax is no longer supported in V8 server.
Action: Change syntax to V7 syntax or higher.
ORA-24376 cannot register/get user callback for non-environment handle
Cause: A user callback registration or get was attempted on a handle which is not an environment handle.
Action: Pass the environment handle to register/get user callback.
ORA-24377 invalid OCI function code
Cause: An invalid function code was used to register or get user callback.
Action: Use a valid OCI function code.
ORA-24378 user callbacks not allowed for this call
Cause: An attempt was made to register a user callback for an OCI call for which it not allowed to register user callbacks.
Action: Do not register user callback for this OCI call.
ORA-24379 invalid user callback type
Cause: An invalid type of user callback was specified.
Action: Specify a valid user callback type.
ORA-24380 invalid mode specification
Cause: The mode parameter in an OCIU* call is invalid.
Action: Use only a valid mode parameter.
ORA-24381 error(s) in array DML
Cause: One or more rows failed in the DML.
Action: Refer to the error stack in the error handle.
ORA-24382 statement handled already executed or described
Cause: The statement handle was executed or described successfully before.
Action: Perform a OCIStmtPrepare again before OCI_PARSE_ONLY.
ORA-24383 Overflow segment of an IOT cannot be described
Cause: The name specified in the OCIDescribeAny call referred to an IOT overflow segment.
Action: Use OCIDescribeAny to describe only documented objects.
ORA-24384 Application context size is not initialized
Cause: The size of the application context must be initialized before populating each context element.
Action: Issue OCIAttrSet with OCI_ATTR_CTX_SIZE to initialize context size.
ORA-24385 Application context size or index is not valid
Cause: The size or index of the application context must be non-zero and non-negative.
Action: Use an appropriate value for the size.
ORA-24386 statement/server handle is in use when being freed
Cause: This is an internal OCI error.
Action: The user should reset in-use flag in statement handle before freeing the handle.
ORA-24387 Invalid attach driver
Cause: Trying to attach using the wrong driver.
Action: Relink the application in the correct mode.
ORA-24388 Unsupported functionality in fast path mode
Cause: Feature not supported in fast path mode.
Action: Avoid using the functionality in this mode.
ORA-24389 Invalid scrollable fetch parameters
Cause: All the requested rows in this fetch could not be received.
Action: Check the fetch orientation, scroll offset, OCI_ATTR_CURRENT_POSITION, and the number of rows in the OCIStmtFetch2 call. If required, change some of the above parameters and fetch again.
ORA-24390 Unsupported scrollable cursor operation
Cause: The scrollable cursor execute or fetch has failed.
Action: Check the documentation for supported types, and other restrictions while using scrollable cursors.
ORA-24391 invalid fetch operation
Cause: Scrollable cursor operation requested with non-scrollable cursor.
Action: Check if the statement was executed in the scrollable mode. The only acceptable orientation is OCI_FETCH_NEXT that ignores the scroll offset parameter.
ORA-24392 no connection pool to associate server handle
Cause: OCIServerAttach was called in OCI_POOL mode but no connection pool was found to associate the server handle.
Action: 1) Verify that OCIConnectionPoolCreate is called before calling OCIServerAttach. 2) Verify that the database link specified in OCIServerAttach matches with that of the connection pool database link.
ORA-24393 invalid mode for creating connection pool
Cause: The mode specified in OCIConnectionPoolCreate is invalid.
Action: Use a valid mode.
ORA-24394 invalid mode for destroying connection pool
Cause: The mode specified in OCIConnectionPoolDestroy is invalid.
Action: Use a valid mode.
ORA-24395 cannot reinitialize non-existent pool
Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.
Action: Create a connection pool prior to reinitializing it.
ORA-24396 invalid attribute set in server handle
Cause: Attribute OCI_ATTR_NONBLOCKING_MODE has been set on the server handle and attached in OCI_POOL mode. Connection pooling does not support non blocking mode.
Action: Do not set the OCI_ATTR_NONBLOCKING_MODE attribute on the server handle while attaching in OCI_POOL mode.
ORA-24397 error occurred while trying to free connections
Cause: An internal error occurred while trying to free connections.
Action: Contact Oracle Support Services.
ORA-24398 connection pool already exists
Cause: A connection pool has already been created for the specified pool handle.
Action: 1) Specify a different pool handle to create a new connection pool. 2) If you wish to modify the pool parameters, call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode.
ORA-24399 invalid number of connections specified
Cause: An invalid combination of minimum, maximum and increment number of connections was specified in the OCIConnectionPoolCreate call.
Action: Specify a valid combination of parameters.
ORA-24400 error occurred while creating connections in the pool
Cause: The database link specified in OCIConnectionPoolCreate might be invalid.
Action: Specify a valid database link.
ORA-24401 cannot open further connections
Cause: Sufficient number of connections are not present in the pool to execute the call. No new connections can be opened as the connMax parameter supplied in OCIConnectionPoolCreate has been reached.
Action: Call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode and increase the value of the connMax parameter.
ORA-24402 error occurred while creating connections in the pool
Cause: The username and password specified in OCIConnectionPoolCreate might be invalid.
Action: Specify a valid username and password.
ORA-24403 error occurred while trying to destroy the connection pool
Cause: Some connections in the pool were busy when an attempt to destroy the connection pool was made.
Action: Ensure no connections from the pool are being used.
ORA-24404 connection pool does not exist
Cause: An attempt was made to use the connection pool before it was created.
Action: Create the connection pool.
ORA-24405 error occurred while trying to create connections in the pool
Cause: An internal error occurred while creating connections in the pool.
Action: Contact Oracle Support Services.
ORA-24406 API mode switch is disallowed when a call is in progress.
Cause: A mode switch from OCI8 to OCI7 was attempted in a callback.
Action: The user should perform the API mode switch either prior to initiating the top call or after the main call has completed.
ORA-24407 connection pool already exists
Cause: A connection pool has already been created for the specified pool name.
Action: Specify a different pool name to create a new connection pool.
ORA-24408 could not generate unique server group name
Cause: An internal error occurred while generating unique server group name.
Action: Contact Oracle Support Services.
ORA-24409 client cannot understand the object
Cause: The client cannot process all the new features in the object.
Action: Upgrade the client so that features like inheritance and SQLJ objects can be used.
ORA-24410 scrollable cursor max size exceeded
Cause: Result set size exceeded the max limits.
Action: Check the documentation for allowable maximum result set size for scrollable cursors. Re-execute with a smaller expected result set size or make the cursor non-scrollable.
ORA-24411 Session pool already exists.
Cause: A session pool has already been created for the specified pool handle.
Action:
Specify a different pool handle to create a new session pool.
If you wish to modify the pool parameters, then call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode.
ORA-24412 Cannot reinitialize non-existent pool
Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.
Action: Create a session pool prior to reinitializing it.
ORA-24413 Invalid number of sessions specified
Cause: An invalid combination of minimum, maximum, and increment number of sessions was specified in the OCISessionPoolCreate call.
Action: Specify a valid combination of parameters.
ORA-24414 Only number sessions could be started.
Cause: The number of sessions specified by the minSess parameter of OCISessionPoolCreate could not be started, possibly because the value supplied was larger than that supported by the server.
Action: This is a warning. Check the maximum number of sessions allowed on the server.
ORA-24415 Missing or null username.
Cause: Username and password must be specified when pool is created in this mode.
Action: Specify a valid username and password.
ORA-24416 Invalid session Poolname was specified.
Cause: An attempt was made to use a Session Pool that does not exist.
Action: Create a Session Pool before using it.
ORA-24417 Session pool size has exceeded the maximum limit
Cause: The number of sessions has exceeded the maximum size of the Session Pool.
Action: This is a warning. You can tune the session pool with appropriate minimum and maximum parameters.
ORA-24418 Cannot open further sessions.
Cause: Sufficient number of sessions are not present in the pool to execute the call. No new sessions can be opened as the sessMax parameter supplied in OCISessionPoolCreate has been reached.
Action: Call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode and increase the value of the sessMax parameter.
ORA-24419 Proxy sessions are not supported in this mode.
Cause: A proxy session was requested from a Session Pool which does not support proxy sessions.
Action: Do not specify mode OCI_CRED_PROXY.
ORA-24420 OCISessionRelease must be used to release this session.
Cause: The session was retrieved using OCISessionGet, and an attempt has been made to release it using a call other than OCISessionRelease.
Action: Call OCISessionRelease.
ORA-24421 OCISessionRelease cannot be used to release this session.
Cause: The session was not retrieved using OCISessionGet, and an attempt has been made to release it using OCISessionRelease.
Action: Release the session using an appropriate call.
ORA-24422 error occurred while trying to destroy the Session Pool
Cause: An attempt was made to destroy the session pool while some sessions in the pool were busy.
Action: Ensure that no sessions from the pool are being used OR call OCISessionPoolDestroy with mode set to OCI_SPD_FORCE.
ORA-24430 Null values for sqltext and key were specified.
Cause: An attempt was made to call OCIStmtPrepare2 and neither sqltext nor key were specified.
Action: Specify valid values for sqltext, key, or both.
ORA-24431 Statement does not exist in the cache
Cause: The statement that was requested does not exist in the statement cache.
Action: Request a valid statement.
ORA-24432 The statement that was returned is not tagged.
Cause: A tagged statement was requested, but an untagged statement has been returned.
Action: This is a warning. Please modify and tag the statement as desired.
ORA-24433 This statement has already been prepared using OCIStmtPrepare2.
Cause: A statement that was earlier prepared using OCIStmtPrepare2 is now being reprepared using OCIStmtPrepare.
Action: Use a different statement handle.
ORA-24434 OCIStmtRelease called before OCIStmtPrepare2.
Cause: An attempt was made to release a statement without first preparing it using OCIStmtPrepare2.
Action: Call OCIStmtPrepare2 before OCIStmtRelease.
ORA-24435 Invalid Service Context specified.
Cause: The statement was prepared using a service context that is different from the one specified in OCIStmtExecute.
Action: Please specify the same service context that the statement was prepared with.
ORA-24436 Invalid statement Handle.
Cause: OCIHandleFree called on a statement that was prepared using OCIstmtPrepare2.
Action: Release the statement using OCIStmtRelease.
ORA-24437 OCIStmtExecute called before OCIStmtPrepare2.
Cause: An attempt was made to execute a statement without first preparing it using OCIStmtPrepare2.
Action: Call OCIStmtPrepare2 before OCIStmtExecute.
ORA-24438 Invalid Authentication Handle specified.
Cause: The statement was prepared using an authentication handle that is different from the one specified in OCIStmtExecute.
ORA-24500 invalid UTF16 mode
Cause: UTF16 mode is allowed only at environment handle creation time.
Action: Remove UTF16 mode for functions other than OCIEnvCreate().
ORA-24501 invalid UTF16 string passed in
Cause: Non-UTF16 string is passed in while UTF16 string is expected.
Action: Check the parameter which is actually a string.
ORA-24502 codepoint length overflows
Cause: Returned buffer has more codepoints than allowed.
Action: Set OCI_MAXCHAR_SIZE large enough to accommodate.
ORA-24503 codepoint length overflows for piecewise operation
Cause: Accumulated codepoint length exceeds allowed codepoint length.
Action: Set OCI_MAXCHAR_SIZE large enough to accommodate.
ORA-24504 data length larger than expected
Cause: Incoming data larger than receiving buffer.
Action: Set OCI_MAXDATA/OCI_MAXCHAR_SIZE appropriately or remove the setting.
ORA-24505 cannot change character set id on the handle
Cause: An attempt was made to change character set id on non-environment handles.
Action: Only try to change character set id on environment handles.
ORA-24506 invalid attempt to change character set id on env handle
Cause: An attempt was made to change character set id after other handles have been allocated from the env handle.
Action: Change character set id after creating environment handle but before allocating any handles from it.
ORA-24507 invalid combination of character set ids
Cause: Attempts to set one character set id as zero.
Action: Set both charset and ncharset as zero or non-zero in OCIEnvNlsCreate()
ORA-24750 incorrect size of attribute
Cause: Transaction ID attribute size is incorrect.
Action: Verify that the size parameter is correct.
ORA-24752 OCI_TRANS_NEW flag must be specified for local transactions
Cause: Application attempted to start a local transaction without using OCI_TRANS_NEW.
Action: Use OCI_TRANS_NEW when starting local transactions.
ORA-24753 local transactions cannot be detached
Cause: An attempt to detach a local transaction was made.
Action: Local transactions may only be committed or rolled back.
ORA-24754 cannot start new transaction with an active transaction
Cause: An attempt to start a new transaction was made when there was an active transaction.
Action: Commit, rollback or detach the existing transaction before starting a new transaction.
ORA-24755 OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
Cause: These flags are currently not supported.
Action: No action required.
ORA-24756 transaction does not exist
Cause: An invalid transaction identifier or context was used or the transaction has completed.
Action: Supply a valid identifier if the transaction has not completed and retry the call.
ORA-24757 duplicate transaction identifier
Cause: An attempt was made to start a new transaction with an identifier already in use by an existing transaction.
Action: Verify that the identifier is not in use.
ORA-24758 not attached to the requested transaction
Cause: An attempt was made to detach or complete a transaction that is not the current transaction.
Action: Verify that the transaction context refers to the current transaction.
ORA-24759 invalid transaction start flags
Cause: An invalid transaction start flag was passed.
Action: Verify that one of the values OCI_TRANS_NEW, OCI_TRANS_JOIN, or OCI_TRANS_RESUME was specified.
ORA-24760 invalid isolation level flags
Cause: An invalid isolation level flag was passed.
Action: Verify that only one of following values - OCI_TRANS_READONLY, OCI_TRANS_READWRITE, OCI_TRANS_SERIALIZABLE is used.
ORA-24761 transaction rolled back
Cause: The application tried to commit a transaction and the server rolled it back.
Action: No action required.
ORA-24762 server failed due to unspecified error
Cause: An internal error has occurred in the server commit protocol.
Action: Contact Oracle Support Services.
ORA-24763 transaction operation cannot be completed now
Cause: The commit or rollback cannot be performed now because the session cannot switch to the specified transaction.
Action: Retry the operation later.
ORA-24764 transaction branch has been heuristically committed
Cause: This is an informational message.
Action: No action required.
ORA-24765 transaction branch has been heuristically rolled back
Cause: This is an informational message.
Action: No action required.
ORA-24766 transaction branch has been partly committed and aborted
Cause: This is an informational message.
Action: No action required.
ORA-24767 transaction was read-only and has been committed
Cause: This is an informational message.
Action: No action required.
ORA-24768 commit protocol error occured in the server
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-24769 cannot forget an active transaction
Cause: Transaction identifier refers to an active transaction.
Action: Verify that the identifier of an active transaction was not passed as an argument.
ORA-24770 cannot forget a prepared transaction
Cause: Transaction identifier refers to a prepared transaction.
Action: Verify that the identifier of a prepared transaction was not passed as an argument.
ORA-24771 cannot detach, prepare or forget a local transaction
Cause: Service handle contains a local transaction context.
Action: Verify that the transaction context does not refer to a local transaction.
ORA-24772 Cannot mix tightly-coupled and loosely-coupled branches
Cause: Application attempted to start a transaction with a global transaction identifier and a wrong option.
Action: Verify that all branches of a global transaction are started with either OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the application is correct and uses distributed updates, contact Oracle Support Services.
ORA-24773 invalid transaction type flags
Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified.
Action: Verify that the right parameters are being used.
ORA-24774 cannot switch to specified transaction
Cause: The transaction specified in the call refers to a transaction created by a different user.
Action: Create transactions with the same authentication so that they can be switched.
ORA-24775 cannot prepare or commit transaction with non-zero lock value
Cause: An attempt was made to detach the transaction with a non-zero lock value.
Action: Detach the transaction with lock value set to zero and then try to prepare or commit the transaction.
ORA-24776 cannot start a new transaction
Cause: An attempt was made to start a new transaction when session was already attached to an existing transaction.
Action: End the current transaction before creating a new transaction.
ORA-24777 use of non-migratable database link not allowed
Cause: The transaction, which needs to be migratable between sessions, tried to access a remote database from a non-multithreaded server process.
Action: Perform the work in the local database or open a connection to the remote database from the client. If the multithreaded server option is installed, connect to the Oracle instance through the dispatcher.
ORA-24778 cannot open connections
Cause: The migratable transaction tried to access a remote database when the session itself had opened connections to remote database(s).
Action: Close the connection(s) in the session and then try to access the remote database from the migratable transaction. If the error still occurs, contact Oracle Support Services.
ORA-24779 detach not allowed with open remote cursor
Cause: The migratable transaction tried to detach from the current session while an open remote cursor exists.
Action: Close any open remote cursor prior to detach.
ORA-24780 cannot recover a transaction while in an existing transaction
Cause: An attempt was made to commit or roll back a transaction while in a different transaction, and the transaction for which the action is requested is in a recovery state (this happens if it is idle too long).
Action: Detach from the current transaction and retry the operation.
ORA-24781 branches don't belong to the same global transaction
Cause: The list of xids passed into kpotxmp() do not have the same gtrid
ORA-24782 Cannot detach from a non-migratable transaction
Cause: An attempt was made to detach from a non-migrateable transaction.
Action: Either commit or rollback the transaction.
ORA-24783 Cannot switch non-migratable transactions
Cause: An attempt was made to prepare/commit a txn different from current.
ORA-24784 Transaction exists
Cause: An attempt was made to start a transaction, while attached to a non-migrateable transaction.
ORA-24785 Cannot resume a non-migratable transaction
Cause: An attempt was made to resume a non-migrateable transaction.
ORA-24786 separated transaction has been completed
Cause: The current transaction has been completed by another process.
Action: Start a new transaction.
ORA-24787 remote cursors must be closed before a call completes
Cause: The previous operation did not close all the remote cursors it opened. Since separated transactions are enabled, this is not allowed.
Action: Close all remote cursors in each call, or start a regular (non-separated) transaction.
ORA-24788 cannot switch to specified transaction (server type)
Cause: The transaction specified was created by a shared server and the requestor is a dedicated server, or the transaction was created by a dedicated server and the requestor is a shared server.
Action: All parts of this application should connect as dedicated or as shared.
ORA-24790 cannot mix OCI_TRANS_RESUME and transaction isolation flags
Cause: An attempt was made to change the isolation level of an existing transaction.
Action: No action required.
ORA-24801 illegal parameter value in OCI lob function
Cause: One of the parameter values in the OCI LOB function is illegal.
Action: Check every parameter in the OCI Lob function call to make sure they are correct. Offsets should be greater than or equal to one.
ORA-24802 user defined lob read callback error
Cause: The only valid return value for a user defined LOB read callback function is OCI_CONTINUE. Any other value will cause this error.
Action: Verify that OCI_CONTINUE is returned from the user defined LOB read callback function.
ORA-24803 illegal parameter value in lob read function
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
ORA-24804 illegal parameter value in lob write function
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
ORA-24805 LOB type mismatch
Cause: When copying or appending LOB locators, both source and destination LOB locators should be of the same type.
Action: Pass the same type of LOB locators for copying or appending.
ORA-24806 LOB form mismatch
Cause: When reading from or writing into LOBs, the character set form of the user buffer should be same as that of the LOB.
Action: Make sure that the buffer you are using to read or write has the same form as that of the LOB.
ORA-24807 LOB form mismatch
Cause: When copying or appending LOBs, both source and destination LOB locators should have the same character set form.
Action: Pass locators of the same character set form for copying or appending LOBs.
ORA-24808 streaming of lob data is not allowed when using lob buffering
Cause: An attempt was made to stream LOB data via the polling mode or a callback when LOB buffering was enabled for the input LOB locator.
Action: Lob buffering is useful when reading/writing small amounts of LOB data so streaming should not be necessary. Rewrite the OCILobRead/OCILobWrite call so that it does not use streaming. If streaming of data is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the OCILobRead/OCILobWrite call.
ORA-24809 amount specified will not fit in the lob buffers
Cause: LOB buffering is enabled for the input LOB locator so buffering will be used. However, the amount of LOB data to read or write is larger than what the LOB buffers can hold.
Action: Either disable buffering on the input LOB locator and reissue the command or pass a smaller amount.
ORA-24810 attempting to write more data than indicated
Cause: While writing into a LOB, more data was supplied than indicated.
Action: If data is written in pieces, then make sure that you do not provide more data in the pieces (cumulatively), than you indicated.
ORA-24811 less data provided for writing than indicated
Cause: While writing into a LOB, less data was provided than indicated.
Action: If writing data in single pieces, then make sure that the buffer length specified is big enough to accommodate the data being provided. If data is written in pieces, then make sure that all the data has been provided before specifying OCI_LAST_PIECE.
ORA-24812 character set conversion to or from UCS2 failed
Cause: If the database character set is varying-width, the CLOB/NCLOB value is implicitly converted to or from UCS2. This implicit conversion failed.
Action: Contact Oracle Support Services.
ORA-24813 cannot send or receive an unsupported LOB
Cause: An attempt was made to send a LOB across the network, but either the server does not support the LOB sent by the client, or the client does not support the LOB sent by the server. This error usually occurs when the client and server are running different versions of Oracle.
Action: Use a version of the Oracle that supports the LOB on both the client and the server.
ORA-24814 operation not allowed for temporary LOBs
Cause: Temporary LOB locators are not allowed in the operation. For example, OCILobAssign only takes persistent LOB locators as parameters, not temporary LOBs.
Action: Use OCILobLocatorAssign for temporary LOBs instead. Note that OCILobLocatorAssign can also be used for persistent LOBs, in which case it will behave the same as OCILobAssign.
ORA-24850 failed to startup shared subsystem
Cause: While attempting to initialize OCI in shared mode, a problem was encountered in starting the shared subsystem.
Action: Contact Oracle Support Services.
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 Support Services.
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 Support Services.
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 Support Services.
ORA-24900 invalid or unsupported mode paramater passed in call
Cause: The mode parameter passed into the OCI Client Notification call is incorrect.
Action: Correct the mode parameter passed into OCI.
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: Make sure that the handle parameters in the call to come from the same OCI Environment.
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: Set the name and name-length attributes using the OCIAttrSet() 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: Set the NAMESPACE attribute using the OCIAttrSet() 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: Set the callback attribute using the OCIAttrSet() 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: Set the recepient protocol attribute using the OCIAttrSet() 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: Set the recepient attribute using the OCIAttrSet() call.
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: Set the appropriate callback and recepient protocol attributes using the OCIAttrSet() call.
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-24950 unregister failed, registeration not found
Cause: The registeration that was asked to be unregistered could not be found.
Action: Check the callback function name and the subscription name in the unregister call.
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/old).column_name.
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-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-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-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-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-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-25007 functions or methods not allowed in WHEN clause
Cause: PL/SQL 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-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-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-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-25012 PARENT and NEW values cannot be identical
Cause: The referencing clause specifies identical values for PARENT and OLD.
Action: Respecify either the PARENT or NEW referencing value.
ORA-25013 OLD and PARENT values cannot be identical
Cause: The referencing clause specifies identical values for OLD and PARENT.
Action: Respecify either the OLD or PARENT referencing value.
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-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-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-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-25018 conflicting trigger string already exists
Cause: Conflicting instead of DDL trigger on schema/database already exists.
Action: Remove the old trigger.
ORA-25019 too much concurrency
Cause: Cannot pin the database/schema because of too much concurrency.
Action: Try the operation later.
ORA-25020 renaming system triggers is not allowed
Cause: renaming system triggers is not allowed.
Action: Drop the trigger and create a new one.
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-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-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-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-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-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-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-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-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-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-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-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-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-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 add a LOCAL partition descriptor if the table is partitioned.
ORA-25114 invalid file number specified in the DUMP DATAFILE/TEMPFILE command
Cause: An invalid file number was used in dumping a datafile or temporary file.
Action: Specify a valid file number.
ORA-25115 duplicate BLOCK option specification
Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE command.
Action: Specify only one BLOCK option.
ORA-25116 invalid block number specified in the DUMP DATAFILE/TEMPFILE command
Cause: An invalid block number was used in dumping a datafile or temporary file.
Action: Specify a valid block number.
ORA-25117 MIN/MAX/Block Number expected
Cause: A value other than MIN/MAX, or a block number was entered in the DUMP DATAFILE/TEMPFILE command.
Action: Correct the syntax.
ORA-25118 invalid DUMP DATAFILE/TEMPFILE option
Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command.
Action: Correct the syntax.
ORA-25119 LOGGING/NOLOGGING option already specified
Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were specified more than once.
Action: Remove all but one of the logging specifications.
ORA-25120 MINIMUM EXTENT option already specified
Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was specified more than once.
Action: Remove all but one of the MINIMUM EXTENT specifications.
ORA-25121 MINIMUM EXTENT value greater than maximum extent size
Cause: In CREATE/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.
ORA-25122 Only LOCAL bitmap indexes are permitted on partitioned tables
Cause: An attempt was made to create a global bitmap index on a partitioned table.
Action: Create a local bitmap index instead.
ORA-25123 Too many components specified in the name.
Cause: More components per name than is allowed were specified.
Action: Check the name specified for the operation.
ORA-25124 Database link name not allowed.
Cause: A database link name was specified when it is not permitted.
Action: Check the name specified for the operation.
ORA-25125 BUFFER_POOL storage option not allowed
Cause: An attempt was made to specify the BUFFER_POOL storage option. This option may only be specified during CREATE/ALTER TABLE/CLUSTER/INDEX.
Action: Remove this option and retry the statement.
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-25127 RELY not allowed in NOT NULL constraint
Cause: An attempt was made to set RELY on for NOT NULL constraint.
Action: Only NORELY may be specified for a NOT NULL constraint.
ORA-25128 No insert/update/delete on table with constraint (string.string) disabled and validated
Cause: An attempt was made to insert/update/delete on table with DISABLE VALIDATE constraint.
Action: Change the constraint's states.
ORA-25129 cannot modify constraint (string) - no such constraint
Cause: The named constraint does not exist for this table.
Action: Try again with a constraint that does exist for this table.
ORA-25130 cannot modify primary key - primary key not defined for table
Cause: An attempt was made to modify a primary key that is not defined for the table.
Action: No action required.
ORA-25131 cannot modify unique(string) - unique key not defined for table
Cause: An attempt was made to modify a unique key that is not defined for the table.
Action: No action required.
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 partition is not mutually exclusive from the rest of the table.
Action: Change the constraint's status.
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-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-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-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-25137 Data value out of range
Cause: Value from cast operand is larger than cast target size.
Action: Increase size of cast target.
ORA-25138 string 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-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-25140 string 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-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-25142 default storage clause specified twice
Cause: Default storage clause was specified twice for create tablespace.
Action: Specify it once.
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-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-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-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-25147 UNIFORM SIZE value greater than maximum extent size
Cause: In CREATE/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-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-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-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-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-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-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-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-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-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-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 either the standard blocksize or one of (2k, 4k, 8k, 16k, 32k) subject to the maximum and minimum blocksizes supported by the platform.
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-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-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-25178 duplicate PCTTHRESHOLD storage option specification
Cause: The storage option PCTTHRESHOLD is specified more than once.
Action: Specify storage options at most once.
ORA-25179 invalid PCTTHRESHOLD storage option value
Cause: The specified value must be a positive integer.
Action: Specify an appropriate value.
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-25181 missing ON keyword for NESTED INDEX
Cause: The ON keyword is required to specify nested index column nest.
Action: Add ON keyword.
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/BFILE/VARRAY columns
partitioning/PARALLEL/CREATE TABLE AS SELECT options
ALTER TABLE with ADD/MODIFY column options
CREATE INDEX
Action: Do not use the disallowed feature(s) in this release.
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-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-25185 index column other than last can not be specified for INCLUDE clause
Cause: An index column name other than the last was 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-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-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-25188 cannot drop/disable/defer the primary key constraint for index-organized tables
Cause: An attempt was made to DROP, DISABLE, or DEFER the primary key constraint for an index-only table. This is not allowed.
Action: Do not DROP, DISABLE, or DEFER the primary key constraint for an index-only 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/DEALLOCATE EXTENT, PCTFREE/PCTUSED for IOT top index segment
Action: Remove the illegal option(s).
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 (for example, changing physical attributes) with some other operation (for example, ADD constraint) which is illegal
Action: Ensure that a index-organized table maintenance operation is the sole operation specified in ALTER TABLE statement.
ORA-25191 cannot reference overflow table of an index-organized table
Cause: An attempt was made 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-25192 invalid option for an index-organized table
Cause: An attempt was made 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-25193 cannot use COMPRESS option for a single column key
Cause: An attempt was made to use COMPRESS option on single column key.
Action: Remove the COMPRESS option.
ORA-25194 invalid COMPRESS prefix length value
Cause: The specified value must be a positive integer less than the number of key columns.
Action: Specify an appropriate value.
ORA-25195 invalid option for index on an index-organized table
Cause: An attempt was made to specify one or more of the following options for index on an IOT: BITMAP, REVERSE, PCTUSED.
Action: Specify an appropriate option.
ORA-25196 keyword MOVE in ALTER TABLE MOVE must immediately follow table_name
Cause: MOVE specified after one/more other ALTER options.
Action: Change order of options, MOVE should be first or remove the illegal option(s).
ORA-25197 an overflow segment already exists for the indexed-organized table
Cause: An attempt was made to ADD OVERFLOW segment on an index-organized table that already has an overflow segment.
Action: No action required.
ORA-25198 only range and hash partitioning are supported for index-organized table
Cause: System or composite partitioning schemes are not supported.
Action: Select a different partitioning scheme.
ORA-25199 partitioning key of a index-organized table must be a subset of the primary key
Cause: An attempt was made to specify a partitioning key which is not a prefix of the primary key of the index-organized table.
Action: Select a different partitioning key.
ORA-25200 invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
Cause: A NULL parameter was specified for QUEUE_NAME.
Action: Specify a non-NULL queue name.
ORA-25201 invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
Cause: An invalid value specified for parameter VISIBILITY.
Action: Specify either ON_COMMIT or IMMEDIATE.
ORA-25202 invalid value NULL, string should be non-NULL
Cause: A NULL value was specified for the parameter.
Action: Specify a non-NULL value.
ORA-25203 invalid value string, DELAY should be non-negative
Cause: A negative value or NULL was specified for DELAY.
Action: Specify a non-negative integer for DELAY.
ORA-25204 invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
Cause: An invalid SEQUENCE_DEVIATION was specified.
Action: Specify either the option 'BEFORE' or 'TOP'.
ORA-25205 the QUEUE string.string does not exist
Cause: The specified queue does not exist.
Action: Create the queue first before specifying it for enqueue or dequeue.
ORA-25206 enqueue failed, enqueue to exception queue string.string not permitted
Cause: An attempt was made to enqueue to an exception queue.
Action: Try enqueueing to another queue.
ORA-25207 enqueue failed, queue string.string is disabled from enqueueing
Cause: The queue has been stopped to prevent any further enqueueing.
Action: Enable the queue first by using an administrative operation.
ORA-25208 RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE
Cause: A relative message identifier should be specified if sequence deviation is specified as BEFORE.
Action: Either specify an existing relative message identifier or do not specify sequence deviation as BEFORE.
ORA-25209 invalid value string, EXPIRATION should be non-negative or NEVER
Cause: The expiration is less than zero or NULL.
Action: Specify a valid value for EXPIRE_AFTER which should be greater than or equal to zero or NEVER.
ORA-25210 invalid value for RELATIVE_MSGID, no message in queue with that msgid
Cause: No message in the queue with the MSGID equal to the specified RELATIVE_MSGID.
Action: Try again with a valid RELATIVE_MSGID.
ORA-25211 invalid DELAY specified when using sequence deviation
Cause: The DELAY specified in the enqueue is greater than the delay of the message with the given relative message ID.
Action: Set the DELAY to be less than or equal to the delay of the message with the given relative message ID. If the TOP option is used the delay must be less than or equal to the delay of all the messages in the queue.
ORA-25212 invalid PRIORITY specified when using sequence deviation
Cause: The PRIORITY specified in the enqueue is less than the priority of the message with the given relative message ID.
Action: Set the PRIORITY to be less than the delay of the message with the given relative message ID. If the TOP option is used the priority must be greater than or equal to the priority of all the messages in the queue.
ORA-25213 message with specified RELATIVE_MSGID has been dequeued
Cause: The message specified by the RELATIVE_MSGID field in the sequence deviation BEFORE option has been dequeued.
Action: No action required. This is an informational message only.
ORA-25214 cannot specify delay or expiration for enqueue to exception queue
Cause: A message was enqueued to the exception queue with either delay or expiration specified.
Action: Enqueue a message without delay or expiration.
ORA-25215 user_data type and queue type do not match
Cause: A user tries to enqueue an object to a queue that was created for objects of different type.
Action: Try enqueue again with an object of the right type.
ORA-25216 invalid recipient, either NAME or ADDRESS must be specified
Cause: Both attributes, NAME and ADDRESS, were specified null for one of the recipients in the recipient list.
Action: Specify a non-null NAME or ADDRESS for the recipient.
ORA-25217 enqueue failed, visibility must be IMMEDIATE for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue without setting visibility to IMMEDIATE.
Action: Set visibility to IMMEDIATE.
ORA-25218 enqueue failed, delay must be zero for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue with delay greater than zero seconds.
Action: Set delay to zero.
ORA-25219 enqueue failed, sequence deviation not allowed for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue with sequence deviation specified.
Action: Do not specify sequence deviation.
ORA-25220 enqueue failed, signature not specified for a non-repudiable queue
Cause: An attempt was made to enqueue to a non-repudiable queue without specifying the signature.
Action: Specify the signature.
ORA-25221 enqueue failed, signature specified queue not supporting non-repudiation
Cause: An attempt was made to enqueue to a queue specifying the signature for a queue not supporting non-repudiation.
Action: Remove the signature.
ORA-25222 enqueue failed, complete sender info. not provided for a queue supporting non-repudiation
Cause: An attempt was made to enqueue to a queue without giving the complete sender information (name) for a queue supporting non-repudiation.
Action: Provide the sender information.
ORA-25223 user_data type used is not supported
Cause: An attempt was made to enqueue data into a non persistent queue that is of a type other than the supported raw or object type.
Action: Enqueue the message again with data of raw or object type.
ORA-25224 sender name must be specified for enqueue into secure queues
Cause: An attempt was made to enqueue into a secure queue without specifying a sender name.
Action: Enqueue the message with sender name specified.
ORA-25225 invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
Cause: An invalid parameter has been specified for DEQUEUE_MODE.
Action: Specify either REMOVE, BROWSE or LOCKED.
ORA-25226 dequeue failed, queue string.string is not enabled for dequeue
Cause: The queue has not been enabled for dequeue.
Action: Enable the queue using START_QUEUE.
ORA-25228 timeout or end-of-fetch during message dequeue from string.string
Cause: User-specified dequeue wait time has passed or the end of the queue has been reached but no message has been retrieved.
Action: Try dequeue again with the appropriate WAIT_TIME or the FIRST_MESSAGE option.
ORA-25229 error on transformation of message string string
Cause: There was an error when transforming a message at enqueue, dequeue, or propagation time.
Action: Correct the transformation function.
ORA-25230 invalid value string, WAIT should be non-negative
Cause: A negative value has been specified for WAIT.
Action: Specify a non-negative value or FOREVER.
ORA-25231 cannot dequeue because CONSUMER_NAME not specified
Cause: A user tried to dequeue from a queue that has been created for multiple consumers but a CONSUMER_NAME was not been specified in the dequeue options.
Action: Specify the CONSUMER_NAME in the dequeue options.
ORA-25232 duplicate recipients specified for message
Cause: An enqueue was performed with duplicate queue agents in the recipients parameter.
Action: Remove the duplicate queue agent and retry the call.
ORA-25233 invalid parameter specified for NAVIGATION
Cause: An invalid parameter has been specified for NAVIGATION.
Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE or NEXT_TRANSACTION. Use FIRST_MESSAGE for dequeuing the first message that satisfies the criterion, NEXT_MESSAGE for dequeuing the next message that satisfies the criterion and NEXT_TRANSACTION for moving to a set of messages enqueued by another transaction.
ORA-25234 NEXT_TRANSACTION navigation option invalid for queue table string.string
Cause: The NEXT_TRANSACTION navigation option was used in a dequeue from a queue in a queue table that was not created for transactional grouping.
Action: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation option. If you want to dequeue messages using transactional grouping create the queue in a queue table that has transactional grouping enabled.
ORA-25235 fetched all messages in current transaction
Cause: The NEXT_TRANSACTION navigation option was used in a dequeue when there were no more messages that belong to the same transaction.
Action: Use the NEXT_TRANSACTION navigation option to move to the next also use the FIRST_MESSAGE option to start from the head of the queue again.
ORA-25236 buffer too small for user data
Cause: The variable or buffer used for the out parameter payload is too small for the user data dequeued.
Action: Increase the size of the buffer or the size of the variable. Maximum size allowed is 32K.
ORA-25237 navigation option used out of sequence
Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after dequeuing all the messages.
Action: Reset the dequeuing position using the FIRST_MESSAGE navigation option and then specify the NEXT_MESSAGE or NEXT_TRANSACTION option.
ORA-25238 too many recipients specified for message destination string
Cause: An ENQUEUE was performed with more than 32 recipients for the given destination (address).
Action: Reduce the number of recipients to 32 or less, and retry the call.
ORA-25239 message ID not supplied when dequeuing from exception queue string.string
Cause: An attempt was made to dequeue from a release 8.0-compatible exception queue without including a message ID in the dequeue options.
Action: Check the application to ensure that the queue name has been specified correctly. If the queue name is correct supply a message ID when dequeuing from a release 8.0-compatible exception queue. Otherwise, upgrade the QUEUE_TABLE containing the queue to release 8.1-compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
ORA-25240 message ID and dequeue condition/correlation ID specified in dequeue options
Cause: An attempt was made to dequeue by including both a message ID and a dequeue condition/correlation ID in the dequeue options. In the dequeue options, you are permitted to specify either a message ID or a dequeue condition/correlation ID, or neither.
Action: To dequeue a message, specify a message ID or a dequeue condition/correlation ID in the dequeue options, but do not specify both. If you want to dequeue in the queue's sort order, then do not specify either the message ID or dequeue condition/correlation ID in the dequeue options.
ORA-25241 cannot change correlation ID from string to string without FIRST_MESSAGE option
Cause: An attempt was made to change the correlation ID while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
Action: To use a correlation ID that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.
ORA-25242 cannot change subscriber name from string to string without FIRST_MESSAGE option
Cause: An attempt was made to change the subscriber name while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
Action: To use a subscriber name that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.
ORA-25243 CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
Cause: An attempt was made to dequeue from an exception queue by specifying the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be specified when dequeuing from a normal queue created for multiple consumers.
Action: Specify only the message ID in the dequeue options to dequeue a message from an exception queue.
ORA-25244 dequeue index key not found, QUEUE string, rowid string
Cause: An internal error was encountered. There may be an inconsistency in the queue table index.
Action: Contact Oracle Support Services. You may need to provide the trace file and information about reproducing the error.
ORA-25245 agent name cannot be specified if address is a single-consumer queue or an exception queue
Cause: The agent name for the agent in the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue.
Action: Do not specify the agent name.
ORA-25246 listen failed, the address string is an 8.0 style exception queue
Cause: An 8.0 style exception queue was specified in the agent-list for the LISTEN call.
Action: Specify a normal 8.0 style queue or an 8.1 style queue in the agent-list.
ORA-25247 string is not a recipient of specified message
Cause: The consumer name specified in the dequeue options is not a recipient of the message specified by the message ID.
Action: Ensure that the agent specified by the consumer name is a recipient of the message specified by the message ID.
ORA-25248 duplicate agent specified in the agent list
Cause: An agent was specified more than once in the agent list of the LISTEN call.
Action: Remove the duplicate agent specification(s), and retry the call.
ORA-25249 dequeue failed, dequeue not allowed for queue string.string
Cause: An attempt was made to dequeue from a non-persistent queue.
Action: Dequeue from a different queue.
ORA-25250 Cannot specify a remote recipient for the message
Cause: A recipient for the message enqueued to a non-persistent queue had a non-local address.
Action: Do not specify the address field or specify the queue which is the target of the enqueue
ORA-25251 exceeded maximum number of recipients for message
Cause: An attempt was made to issue an ENQUEUE call that exceeded the maximum number (1024) of recipients per message.
Action: Reduce the number of recipients to 1024 or less, and retry the call.
ORA-25252 listen failed, the address string is a non-persistent queue
Cause: A non-persistent queue was specified as an address for an agent in the LISTEN call.
Action: Specify a normal queue as address for the agent, and retry the LISTEN call.
ORA-25253 listen failed, queue string.string is not enabled for dequeue
Cause: An attempt was made to specify a queue that is not enabled for dequeue in a LISTEN call.
Action: Enable the queue for dequeue using START_QUEUE, and retry the LISTEN call.
ORA-25254 time-out in LISTEN while waiting for a message
Cause: The specified wait time has elapsed and there were no messages for any of the agents in the agent-list.
Action: Try the LISTEN call with an appropriate time-out.
ORA-25255 incorrect subscription string string
Cause: An incorrect subscription string was specified with OCIRegister.
Action: Specify a subscription string using the [CONSUMER:]SCHEMA.QUEUE form.
ORA-25256 consumer cannot be specified with a single-consumer queue or an exception queue
Cause: An attempt was made to specify a consumer in the subscription string when registering for notification on a single-consumer queue or an exception queue.
Action: Do not specify the consumer in the subscription string.
ORA-25257 consumer must be specified with a multi-consumer queue
Cause: An attempt was made to register on a multi-consumer queue without specifying a consumer in the subscription string.
Action: Specify a consumer in the subscription string.
ORA-25258 cannot register for notifications on an 8.0 style exception queue
Cause: An attempt was made to specify an 8.0 style exception queue in the subscription string of OCIRegister.
Action: Specify a normal queue or a non-persistent queue.
ORA-25259 cannot specify protocol for agent
Cause: The user specified the protocol attribute for an agent in the agent list.
Action: Do not specify the protocol attribute of the agent object type.
ORA-25261 JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
Cause: AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that is insufficient for AQ propagation.
Action: Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ propagation.
ORA-25262 agent name cannot be NULL if address is a multi-consumer queue
Cause: The name for the agent in the LISTEN call was not specified when the agent address was a multi-consumer queue.
Action: Specify a non-NULL name for the agent.
ORA-25263 no message in queue string.string with message ID string
Cause: An attempt was made to dequeue a message with a specific message ID, but no such message exists in the queue.
Action: Try dequeue again with a valid message ID.
ORA-25264 can't get signature for this queue
Cause: An attempt was made to dequeue the signature from this queue, which is not reciever non-repidiable.
Action: Try dequeue again without the get signature option.
ORA-25265 specified signature for a queue which does not support reciever non-repudiation
Cause: An attempt was made to dequeue the message from a queue which does not support reciever non-repudiation, but the signature was specified for verification.
Action: Try dequeue again without the signature.
ORA-25266 didn't try to dequeue by message id with the signature
Cause: The signature was specified for a queue, but the dequeue was not done by message id.
Action: Try dequeue again by message id.
ORA-25267 didn't specify the signature for a reciever non-repudiable queue
Cause: The signature was not specified for a reciever non-repudiable queue.
Action: Try dequeue again along with the signature.
ORA-25268 didn't dequeue in browse mode with get signature option
Cause: The dequeue was not performed in browse mode with get signature option.
Action: Try dequeue again in browse mode.
ORA-25269 can't specify signature with get signature option
Cause: The signature is not required for the dequeue with get signature option.
Action: Try dequeue again without the signature in dequeue options.
ORA-25270 sender info does not match with the actual sender of the message
Cause: The sender info and the message id do not match.
Action: Provide the correct sender info or try dequeue again without the signature in dequeue options.
ORA-25271 queue table not found for the given queue
Cause: The queue table does not exist for the given queue.
Action: Provide the correct queue name.
ORA-25272 Signature does not exist for the given reciever and message id
Cause: Signature does not exist for the given reciever and message id.
Action: Check the message id and the reciever's information.
ORA-25276 table specified is not a queue table
Cause: An invalid queue table name is specified.
Action: Check the dictionary views to see if the table is a queue table.
ORA-25277 cannot grant or revoke object privilege on release 8.0 compatible queues
Cause: An attempt was made to grant or revoke object privilege on release 8.0 style queues.
Action: Convert the release 8.0 compatible queue table to release 8.1 compatible using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting or revoking object privilege.
ORA-25278 grantee name cannot be NULL
Cause: An attempt was made to specify NULL for the grantee parameter.
Action: Specify a valid grantee parameter.
ORA-25279 dequeue as select not supported before 9.0.0
Cause: Dequeue as select not supported before 9.0.0.
Action: Don't use select condition while dequeuing.
ORA-25280 complete sender information not provided to non-repudiate sender
Cause: Complete sender information not provided to non-repudiate sender.
Action: Provide the complete sender information.
ORA-25281 complete reciever information not provided to non-repudiate reciever
Cause: Complete reciever information not provided to non-repudiate reciever.
Action: Provide the complete reciever information.
ORA-25282 message id not provided for non-repudiation
Cause: Message id was not provided.
Action: Provide the message id.
ORA-25283 either agent's name or address needed for non-repudiation
Cause: neither agent's name nor address provided for non-repudiation.
Action: Provide the agent info.
ORA-25284 Invalid value string for string
Cause: An Invalid value or NULL was specified for the parameter.
Action: Check the documentation for valid values.
ORA-25285 Invalid value string for array_mode
Cause: An Invalid value or NULL was specified for the array_mode.
Action: Check the documentation for valid values.
ORA-25286 Invalid number of elements in the message properties array
Cause: Number of elements in the message properties array does not match the number of elements in the payload array.
Action: Create a message property array with one element (that applies for all the elements in the payload array) or create a message property array with the same number of elements as there are in the payload array.
ORA-25287 Invalid value string, string should be non-negative
Cause: An Invalid value or NULL was specified for the parameter.
Action: Specify a non negative integer.
ORA-25288 AQ HTTP propagation encountered error, status-code number, string
Cause: AQ propagation's HTTP request to the propagation servlet at the specified address encountered an error.
Action: Specify a valid address in the connect string of the propagation destination dblink, make sure the dblink user has the correct permissions, and check if the AQ propagation servlet was properly installed.
ORA-25289 Buffer Already Exists
Cause: Buffer already exists for the specified queue.
Action: No action required.
ORA-25290 Cannot complete operation on queue string with existing messages
Cause: Queue already has messages. Cannot complete operation.
Action: Truncate the queue before adding/dropping a buffer.
ORA-25291 Buffer does not exist for the specified queue
Cause: Buffer does not exist for the specified queue.
Action: Operation on the buffer cannot be performed. create the buffer.
ORA-25292 Cannot add buffer on the specified queue
Cause: Buffer cannot be added on the Specified Queue.
Action: Can only add buffers to 8.1 style non-exception multi-consumer queues, which do not have priority, non_repudiation, message_grouping, max_retries, and retention.
ORA-25293 Remote Recipient Subscribers and buffered operations not possible for Queue string
Cause: Specified Queue has remote recipient subscribers.
Action: Cannot add buffers/add buffered subscribers to queues with remote recipient subscribers.
ORA-25294 Queue string has a buffer
Cause: Specified Queue has a buffer.
Action: Drop the buffer first.
ORA-25295 Subscriber is not allowed to dequeue buffered messages
Cause: Subscriber is only allowed to dequeue persistent messages.
Action: Drop the subscriber and re-create it.
ORA-25296 Queue Table string has a buffered queue string
Cause: Cannot downgrade the queue table because it has a buffered queue.
Action: Drop the buffer or the buffered queue.
ORA-25297 The message options only make sense for buffered messages
Cause: The message options only make sense for buffered messages.
Action: Check the enqueue/dequeue options.
ORA-25298 The memory threshold for a queue cannot be negative
Cause: The memory threshold for a queue cannot be negative.
Action: Correct the memory threshold.
ORA-25299 Cannot add buffered subscriber for a non-buffered queue
Cause: Cannot add buffered subscriber for a non-buffered queue.
Action: Either add buffer to the queue, or make the subscriber non-buffered.
ORA-25300 Cannot drop buffer for queue with buffered subscribers
Cause: Cannot drop buffer for queue with buffered subscribers.
Action: Either drop buffered subscribers or forcibly drop the buffer.
ORA-25301 cannot specify recipient list during enqueue
Cause: Recipient list for buffered queue not supported.
Action: Don't specify recipient list for buffered enqueues.
ORA-25302 Operation not possible for non-buffered queue string
Cause: Last enqd/ackd message is only supported for buffered queues.
Action: The operation is not supported.
ORA-25350 maximum number of concurrent transaction branches exceeded
Cause: The limit on the number of concurrent transaction branches has been reached.
Action: Increase the initialization parameter TRANSACTIONS and restart the system.
ORA-25351 transaction is currently in use
Cause: The transaction is currently used by a different session.
Action: Do not switch to a transaction attached to some other session.
ORA-25352 no current transaction
Cause: The user session is not attached to any transaction.
Action: Do not attempt to detach when there is no current transaction.
ORA-25353 branch marked for deletion
Cause: The branch specified cannot be killed immediately because another session is using the branch, but it has been marked for kill. This means it will be deleted as soon as possible after the current uninterruptable operation is completed.
Action: No action is required for the branch to be deleted.
ORA-25400 must replay fetch
Cause: A failure occurred since the last fetch on this statement. Failover was able to bring the statement to its original state to allow continued fetches.
Action: This is an internally used error message and should not be seen by the user.
ORA-25401 can not continue fetches
Cause: A failure occurred since the last fetch on this statement. Failover was unable to bring the statement to its original state to allow continued fetches.
Action: Re-execute the statement and start fetching from the beginning.
ORA-25402 transaction must roll back
Cause: A failure occurred while a transaction was active on this connection.
Action: The client must roll back.
ORA-25403 could not reconnect
Cause: The connection to the database has been lost, and attempts to reconnect have failed.
Action: Manually reconnect.
ORA-25404 lost instance
Cause: The primary instance has died.
Action: This is an internally used error message and should not be seen by the user.
ORA-25405 transaction status unknown
Cause: A failure occurred while a transaction was attempting to commit. Failover could not automatically determine instance status.
Action: The user must determine the transaction's status manually.
ORA-25406 could not generate a connect address
Cause: Failover was unable to generate an address for a backup instance.
Action: Contact Oracle Support Services.
ORA-25407 connection terminated
Cause: The connection was lost while doing a fetch.
Action: This is an internally used error message and should not be seen by the user.
ORA-25408 can not safely replay call
Cause: The connection was lost while doing this call. It may not be safe to replay it after failover.
Action: Check to see if the results of the call have taken place, and then replay it if desired.
ORA-25425 connection lost during rollback
Cause: The connection was lost while issuing a rollback.
Action: If the transaction is not externally coordinated, then Oracle implicitly rolled back, so no action is required. Otherwise examine PENDING_TRANS$ to determine if ROLLBACK FORCE is required.
ORA-25426 remote instance does not support shared dblinks
Cause: A shared database link is being used to connect to a remote instance that does not support this feature because it is an older version.
Action: Use a normal database link if you need to connect to this instance.
ORA-25436 invalid table alias: string
Cause: An attempt to evaluate was made, which failed because one of the table values specified had an invalid alias.
Action: Check the valid table aliases in the evaluation context, and try again with a valid alias.
ORA-25437 duplicate table value for table alias: string
Cause: An attempt to evaluate was made, which failed because some of the table values specified had the same table alias.
Action: Check the table values specified, and try again with only one value per table.
ORA-25438 invalid variable name: string
Cause: An attempt to evaluate was made, which failed because one of the variable values specified had an invalid name.
Action: Check the valid variable names in the evaluation context, and try again with a valid name.
ORA-25439 duplicate variable value for variable: string
Cause: An attempt to evaluate was made, which failed because some of the variable values specified had the same variable name.
Action: Check the variable names specified, and try again with only one value per variable.
ORA-25440 invalid table alias: string
Cause: An attempt to evaluate was made, which failed because one of the column values specified had an invalid table alias.
Action: Check the valid table aliases in the evaluation context, and try again with a valid name.
ORA-25441 duplicate column value for table alias: string
Cause: An attempt to evaluate was made, which failed because one of the column values supplied a value for a table alias, which already had a table value supplied.
Action: Check the table and column values specified, and try again with either a table value or column values for each table alias.
ORA-25442 too many column values for table alias: string
Cause: An attempt to evaluate was made, which failed because too many column values were supplied for the specified table alias.
Action: Check the column values specified, and try again with the right number of column values.
ORA-25443 duplicate column value for table alias: string, column number: string
Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column number.
Action: Check the column values specified, and try again with only one column value for each table alias and column number.
ORA-25444 invalid ROWID: string for table alias: string
Cause: An attempt to evaluate was made, which failed because an invalid ROWID was supplied for the specified table alias.
Action: Check the column values specified, and try again with only one column value for each table alias and column number.
ORA-25445 invalid column number: string for table alias: string
Cause: An attempt to evaluate was made, which failed because an invalid column number was supplied for the specified table alias as a part of a column value.
Action: Check the column values specified, and try again with a valid column number.
ORA-25446 duplicate column value for table alias: string, column: string
Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column name.
Action: Check the specified column values, and try again with only one column value for each table alias and column name.
ORA-25447 encountered errors during evaluation of rule string.string
Cause: An attempt to evaluate was made, which failed during the evaluation of the specified rule.
Action: Check the rule and the values passed to evaluate, and try again with valid values.
ORA-25448 rule string.string has errors
Cause: An attempt to load the specified rule failed due to errors in the rule.
Action: Check the rule and retry the operation.
ORA-25461 rule set not specified
Cause: An attempt to evaluate was made, which failed because the ruleset name specified was null.
Action: Check the rule set name, and try again with a valid name.
ORA-25462 evaluation context not specified
Cause: An attempt to evaluate was made, which failed because the evaluation context specified was null.
Action: Check the evaluation context name, and try again with a valid name.
ORA-25463 table alias not specified
Cause: An attempt to evaluate was made, which failed because one of the table values specified had a NULL alias name.
Action: Check the list of table values, and try again with a valid alias name.
ORA-25464 ROWID not specified for table alias: string
Cause: An attempt to evaluate was made, which failed because the table value for the specified table alias had a NULL ROWID.
Action: Check the list of table values, and try again with a valid ROWID.
ORA-25465 variable name not specified
Cause: An attempt to evaluate was made, which failed because one of the variable values specified had a NULL variable name.
Action: Check the list of variable values, and try again with a valid variable name.
ORA-25466 data not specified for variable name: string
Cause: An attempt to evaluate was made, which failed because the variable value for the specified variable name had NULL data.
Action: Check the list of variable values, and try again with valid data.
ORA-25467 table alias not specified
Cause: An attempt to evaluate was made, which failed because one of the column values specified had a NULL alias name.
Action: Check the list of column values, and try again with a valid alias name.
ORA-25468 column name not specified for alias: string
Cause: An attempt to evaluate was made, which failed because one of the column values for the specified alias name had a NULL column name.
Action: Check the list of column values, and try again with a valid column name.
ORA-25469 data not specified for alias: string column name: string
Cause: An attempt to evaluate was made, which failed because the column value for the specified alias and column name had NULL data.
Action: Check the list of column values, and try again with valid data.
ORA-25500 database is not open
Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED command.
Action: Open the database and retry this command.
ORA-25501 ALTER SYSTEM QUIESCE RESTRICTED command failed
Cause: Database resource manager failed to change plan.
Action: Look at the alert logs to see a detailed description of the error.
ORA-25502 concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
Cause: There is a concurrent ALTER SYSTEM QUIESCE RESTRICTED or ALTER SYSTEM UNQUIESCE command running in the system.
Action: Contact the database administrator who is responsible for the concurrent command.
ORA-25503 cannot open database because the database is being quiesced
Cause: Database cannot be opened because the system is being or has been quiesced.
Action: Open the database after the system has been quiesced.
ORA-25504 the system is already in quiesced state
Cause: Cannot quiesce the system because the system is already quiesced.
ORA-25505 the system is not in quiesced state
Cause: Cannot unquiesce the system because the system is not in quiesced state.
ORA-25506 resource manager has not been continuously on in some instances
Cause: Cannot quiesce the system because resource manager has not been continuously on since startup in this or some other instances.
ORA-25507 resource manager has not been continuously on
Cause: Cannot quiesce the system because resource manager has not been continuously on since startup.
ORA-25508 database is not mounted
Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE command.
Action: Mount the database and retry this command.
ORA-25509 operation on "string"."string".string not allowed
Cause: A column has been added to a replicated table, but replication support processing has not completed.
Action: Wait until replication support processing has completed before updating the column.
ORA-25526 bad format of _DB_MTTR_SIM_TARGET: string
Cause: One value in _DB_MTTR_SIM_TARGET is not a valid MTTR.
Action: Alter the value of _DB_MTTR_SIM_TARGET.
ORA-25527 bad format of _DB_MTTR_SIM_TARGET
Cause: One value in _DB_MTTR_SIM_TARGET is empty.
Action: Set the value of _DB_MTTR_SIM_TARGET properly.
ORA-25528 too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET
Cause: Too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET.
Action: Alter the value of _DB_MTTR_SIM_TARGET.
ORA-25530 FAST_START_MTTR_TARGET is not specified
Cause: An attempt to start MTTR advisory was made, which failed because FAST_START_MTTR_TARGET was not specified.
Action: Set FAST_START_MTTR_TARGET.
ORA-25531 MTTR specified is too small: number
Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too small for MTTR advisory.
Action: Set a larger FAST_START_MTTR_TARGET or candidate MTTR.
ORA-25532 MTTR specified is too large: number
Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too large for MTTR advisory.
Action: Set a smaller FAST_START_MTTR_TARGET or candidate MTTR.
ORA-25950 missing where clause in join index specification
Cause: An attempt to create a join index was made, which failed because no valid where clause was found.
Action: Ensure that a where clause with valid join conditions is specified in the create index statement.
ORA-25951 join index where clause cannot contain OR condition
Cause: An attempt to create a join index was made, which failed because there was an OR branch in the where clause.
Action: Reformulate the where clause without using ORs.
ORA-25952 join index must only contain inner equi-joins
Cause: An attempt to create a join index was made, which failed because it included a predicate which wasn't an equi-inner join.
Action: Remove the inappropriate predicate.
ORA-25953 join index cannot be a functional index
Cause: An attempt to create a join index was made, which failed because a functional index was requested or necessary (such as is the case for indexing columns using timezone).
Action: Remove any functional indexing columns.
ORA-25954 missing primary key or unique constraint on dimension
Cause: An attempt to create a join index was made, which failed because one or more dimensions did not have an appropriate constraint matching the join conditions.
Action: Ensure that the where clause is correct (contains all of the constraint columns) and that an enforced constraint is on each dimension table.
ORA-25955 all tables must be joined in the where clause
Cause: An attempt to create a join index was made, which failed because one of the tables in the from clause did not appear in the where clause.
Action: Ensure that the where clause contains all from clause tables.
ORA-25956 join index cannot be created on tables owned by SYS
Cause: An attempt to create a join index was made, which failed because one of the tables was owned by SYS.
Action: Ensure that no join index related table is owned by SYS.
ORA-25957 join index where clause cannot contain cycles
Cause: An attempt to create a join index was made, which failed because the where clause contains a cycle.
Action: Ensure that the where clause is in the form of a star or snowflake schema.
ORA-25958 join index where clause predicate may only contain column references
Cause: An attempt to create a join index was made, which failed because a predicate in the where clause contained something other than a simple column.
Action: Ensure that the where clause only contains columns.
ORA-25959 join index must be of the bitmap type
Cause: An attempt to create a join index was made, which failed because no bitmap keyword was used.
Action: Make the index a bitmap index.
ORA-25960 join index cannot be based on a temporary table
Cause: An attempt to create a join index was made, which failed because one of the tables was temporary.
Action: Ensure no underlying tables are temporary.
ORA-25961 join index prevents dml cascade constraint operation
Cause: An attempt to execute dml resulted in the need to perform dml on another table because of a cascade constraint. The join index only allows one of its underlying tables to me modified at a time.
Action: Drop the join index or remove the constraint.
ORA-25962 join index prevents multitable insert or merge
Cause: An attempt to execute an merge or multitable insert on a table that was used to create a bitmap join index was made. Merge and multitable inserts are not supported on tables that were used to create a bitmap join index.
Action: Drop the join index.
ORA-25963 join index must be created on tables
Cause: An attempt to create a join index was made, which failed because the from clause contains non table object.
Action: Ensure that the from clause only contains tables.
ORA-25964 column type incompatible with join column type
Cause: The datatype of the join column is incompatible with the datatype of the joined column.
Action: Select a compatible datatype for the join column.
ORA-26000 partition load specified but table string is not partitioned
Cause: The Loader control file contains a PARTITION clause but the table being loaded is not partitioned.
Action: Remove the partition specification from the SQL*Loader control file and retry the load.
ORA-26001 Index string specified in SORTED INDEXES does not exist on table string
Cause: A non-existent index was specified in the SORTED INDEXES clause.
Action: Do not specify as a SORTED INDEX.
ORA-26002 Table string has index defined upon it.
Cause: Parallel load was specified into a table which has index defined upon it.
Action: Drop index(es) defined upon table, or do not use parallel load, or use SKIP_INDEX_MAINTENANCE option.
ORA-26003 parallel load not supported for index-organized table string
Cause: Parallel load is not supported for index-organized tables.
Action: Load the index-organized table without the PARALLEL option.
ORA-26004 Tables loaded through the direct path may not be clustered
Cause: An attempt was made to load a clustered table via the direct path.
Action: Use the conventional path.
ORA-26005 Invalid handle for direct path load
Cause: In direct path load, the handle passed in does not match the type listed.
Action: Verify the handle and type are correct.
ORA-26006 Incorrect bind variable in column string's sql expression - string
Cause: In direct path load, the bind variables listed in the sql expression do not match the input argument column names.
Action: Verify all the input arguments are listed in the expression as bind variables, and all the bind variables are listed as input arguments to the expression. Or verify that there were no errors in executing the OCI statements when getting the bind variable list.
ORA-26007 For INSERT option, table must be empty. Error on table string
Cause: The user tried to use the INSERT option on a non-empty table.
Action: Empty the table from SQL*Plus, or use the REPLACE option.
ORA-26008 NOT NULL column string has a nullif clause
Cause: A column which is NOT NULL in the database has a SQL*Loader NULLIF clause on it.
Action: Remove the NULLIF clause in the SQL*Loader control file.
ORA-26009 NOT NULL column string has a defaultif clause which may evaluate to null
Cause: A column which is NOT NULL in the database has a SQL*Loader DEFAULTIF clause which may evaluate to null.
Action: Remove the DEFAULTIF clause in the SQL*Loader control file.
ORA-26010 Column string in table string is NOT NULL and is not being loaded
Cause: A column which is NOT NULL in the database is not being loaded and will cause every row to be rejected.
Action: Load the column by specifying the NOT NULL column in the INTO TABLE clause in the SQL*Loader control file.
ORA-26011 Cannot load type string into column string in table string
Cause: A column can only store data of type declared for that column and a substitutable column can only store data of valid subtypes of the supertype declared for that column.
Action: Check that the type or subtype specified is valid for that column.
ORA-26012 No data found while executing sql statement string for column string - check input for: string
Cause: Executing sql statement against the data dictionary tables returned "ORA-01403: no data found".
Action: No data retrieved when selecting against the data dictionary tables most likely means that there's an error in user input. Check that the input listed is correct.
ORA-26013 List allocated may not be big enough
Cause: There seems to be a discrepancy between the size for a list or buffer allocated by direct path api and the size needed.
Action: Contact Oracle Support Services.
ORA-26014 OCI_ATTR_DIRPATH_SUBST_OBJ_TBL is set for non-final object table string
Cause: Client set OCI_ATTR_DIRPATH_SUBST_OBJ_TBL for either a non-object table or for a final object table. This attribute can only be, and must be, set for non-final object tables.
Action: Check the type of the loading table. Do not set this attribute if the table is not a non-final object table.
ORA-26015 Array column string in table string is not supported by direct path
Cause: User attempted to load an array column via the direct path.
Action: Use the conventional path.
ORA-26016 Record string: Rejected - Error on table string, partition string
Cause: The record indicated caused an Oracle error on insert.
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
ORA-26017 Global indexes not allowed on direct path partition load, table string
Cause: Global indexes are defined on a table when direct path loading a single partition of the table.
Action: Remove the global index from the named table and retry the operation.
ORA-26018 Column string in table string does not exist
Cause: Column specified in the loader control file does not exist.
Action: Make sure the column exists and that you have privileges on it. Correct the loader control file if it is wrong.
ORA-26019 Column string in table string of type string not supported by direct path
Cause: The specified column of SQL column type string is not supported by the direct path loader.
Action: If the column is NULLable, remove it from the control file description. Then it will be loaded as a NULL.
ORA-26020 index string.string loaded successfully with string keys
Cause: Non-partitioned index information put to loader log file.
Action: No action required. This is an informational message.
ORA-26021 index string.string partition string loaded successfully with string keys
Cause: Partitioned index information put to loader log file.
Action: No action required. This is an informational message.
ORA-26022 index string.string was made unusable due to:
Cause: A non-partitioned index was made index unusable due to the error displayed below this error.
Action: Depending on the error, either rebuild the index, or drop and re-create it.
ORA-26023 index string.string partition string was made unusable due to:
Cause: A partition of a partitioned index was made index unusable due to error displayed below this error.
Action: Depending on the error, either rebuild the index partition, or drop and re-create the entire index.
ORA-26024 SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
Cause: User requested SKIP_UNUSABLE_INDEXES option, and the index segment was in unusable state prior to the beginning of the load.
Action: Informational only. User will need to either rebuild the index or index partition, or re-create the index.
ORA-26025 SKIP_INDEX_MAINTENANCE option requested
Cause: A request was made that index maintenance be skipped on a direct path load.
Action: The listed index was put into Index Unusable state due to the user requesting that index maintenance be skipped. Either rebuild the index or index partitions, or drop and re-create the index.
ORA-26026 unique index string.string initially in unusable state
Cause: A unique index is in IU state (a unique index cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).
Action: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
ORA-26027 unique index string.string partition string initially in unusable state
Cause: A partition of a unique index is in IU state (a unique index cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).
Action: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
ORA-26028 index string.string initially in unusable state
Cause: An index is in IU state prior to the beginning of a direct path load, it cannot be maintained by the loader.
Action: Either rebuild the index, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only).
ORA-26029 index string.string partition string initially in unusable state
Cause: A partition of an index is in IU state prior to the beginning of a direct path load, it cannot be maintained by the loader.
Action: Either rebuild index partition, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only).
ORA-26030 index string.string had string partitions made unusable due to:
Cause: A logical index error occurred on a partitioned index which affected one or more index partitions, which are listed below this message.
Action: The affected index partitions will have to be rebuilt, or, the entire index dropped and re-created.
ORA-26031 index maintenance error, the load cannot continue
Cause: A index error occurred during the index maintenance phase of a direct path load. The load cannot continue. See error message below this message.
Action: See action for the error message which follows this one.
ORA-26032 index string.string loading aborted after string keys
Cause: An index error occurred during direct-load of an index-organized table. Loading had to be aborted. No rows were loaded.
Action: Check the key just following the number of keys mentioned above. This key caused the index problem mentioned in an earlier message.
ORA-26033 error while evaluating index string.string, row string due to:
Cause: An index error occurred while attempting to evaluate an expression on a functional index.
Action: Verify that the input data is valid for the functional index.
ORA-26034 end of logical record found when reading length of varying length field
Cause: While attempting to read the length portion of a varying length field, then end of the logical record was reached.
Action: Verify that the control file describes the data correctly and that the data in the datafile matches the description in the control file
ORA-26035 Record string: Rejected - Error on table string, subpartition string
Cause: The record indicated caused an Oracle error on insert.
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
ORA-26036 subpartition load specified but table string is not subpartitioned
Cause: The Loader control file contains a PARTITION clause but the table being loaded is not subpartitioned.
Action: Remove the subpartition specification from the SQL*Loader control file and retry the load.
ORA-26037 Record string: Rejected - Error on table string, subpartition string
Cause: The record indicated caused an Oracle error on insert.
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
ORA-26038 error converting character length field to a number
Cause: An error occurred while attempting to convert the characters containing the count portion of a VARCHARC or VARRAWC field.
Action: Verify that the count portion for the field has the correct value.
ORA-26039 Table string has domain index defined upon it
Cause: Direct path load was specified for a table which has a domain index defined upon it.
Action: Drop domain index(es) defined on the table or use the conventional path.
ORA-26040 Data block was loaded using the NOLOGGING option
Cause: An attempt was made to access data in a block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option.
Action: Drop the object containing the block.
ORA-26041 DATETIME/INTERVAL datatype conversion error
Cause: The column could not be converted from DATETIME datatype to internal DATETIME/CHARACTER datatype.
Action: Contact Oracle Support Services.
ORA-26042 unable to convert format string into internal form
Cause: An attempt to convert a DATETIME format string into internal format in preparation for DATETIME datatype processing failed.
Action: Contact Oracle Support Services.
ORA-26043 unable to convert time zone for DATETIME/INTERVAL processing
Cause: An attempt to convert the time zone specified by the ORA_STDZ environment variable to internal format failed.
Action: Verify that the setting for ORA_STDZ is valid.
ORA-26044 unable to to get DATETIME/INTERVAL reference date
Cause: An attempt to retrieve the system reference date for DATETIME/INTERVAL datatypes failed.
Action: Contact Oracle Support Services.
ORA-26045 REF column string expects string arguments; found string.
Cause: The number of arguments for the REF column is incorrect.
Action: Specify the correct number of input arguments for REFs.
Unscoped system-generated REFs can have exactly 1 or 2 input arguments.
It has exactly 1 input argument (one for the OID value) if a fixed table name was specified through OCI_DIRPATH_EXPR_REF_TBLNAME.
It has exactly 2 input arguments (one for the table name and one for the OID value) if a fixed table name was not specified through OCI_DIRPATH_EXPR_REF_TBLNAME.
Scoped system-generated REFs can have 1 or 2 input arguments.
Because a table name argument is not needed for a scoped ref, only 1 argument (OID value) is expected. But if the table name argument is given, it's still accepted.
Scoped primary-key REFs with N columns in its primary-key OID can have N or N+1 input arguments.
Because a table name argument is not needed for a scoped ref, only N arguments (making up the OID value) is expected. But if the table name argument is given, it's still accepted.
ORA-26046 REF column string expects scoped table name string; user passed in string.
Cause: The scoped table name passed in by the user does not match the name in the schema.
Action: Specify the correct table name for the scoped REF column.
ORA-26047 REF column has invalid value for system generated oid
Cause: The value passed in by the user for the system generated oid does not consist of valid hexadecimal digits.
Action: Specify a valid oid value for the REF column.
ORA-26048 Scoped REF column has wrong table name.
Cause: The scoped table name passed in by the user does not match the name in the schema.
Action: Specify the correct table name for the scoped REF column.
ORA-26049 Unscoped REF column has non-existent table name.
Cause: The table name passed in by the user does not exist in the schema.
Action: Specify a valid table name for the unscoped REF column.
ORA-26050 Direct path load of domain index is not supported for this column type.
Cause: Direct path can not load a domain index of that column type.
Action: Drop the index and try again or load using conventional path.
ORA-26051 internal error parsing packed decimal format string
Cause: A packed decimal field with a nonzero scale factor is mapped to a character column. In order to perform the datatype conversion, a numeric format string must be created based on the input field's precision and scale specifications. Direct path loader encountered an error in creating this format string.
Action: Examine the packed decimal field's precision and scale specifications and make sure that they contain valid values.
ORA-26052 Unsupported type number for SQL expression on column string.
Cause: The direct path api does not support a SQL expression on a column of that type.
Action: Make sure the types are correct.
ORA-26076 cannot set or reset value after direct path structure is allocated
Cause: Client attempted to set or reset the number of rows in a direct path structure after it has already been allocated and initialized. Attributes used is one of the following:
OCI_ATTR_NUM_ROWS: to set # of rows in a direct path column array
OCI_ATTR_DIRPATH_DCACHE_SIZE: to set size of a date cache (default is 0)
OCI_ATTR_DIRPATH_DCACHE_DISABLE: to set whether date cache will be disabled on overflow (default is FALSE)
Action: Set the following attributes before:
OCI_ATTR_NUM_ROWS: before calling OCIHandleAlloc for column array
OCI_ATTR_DIRPATH_DCACHE_SIZE: before calling OCIDirPathPrepare
OCI_ATTR_DIRPATH_DCACHE_DISABLE: before calling OCIDirPathPrepare
ORA-26077 direct path column array is not initialized
Cause: Client attempted to allocate a column array for a direct path function context before allocating a column array for the table-level direct path context.
Action: Allocate the table-level direct path context's column array via OCIHandleAlloc before allocating column arrays for direct path function contexts.
ORA-26078 file string is not part of database being loaded
Cause: A parallel load file was specified which is not part of the database.
Action: Check filename and pathname for correctness.
ORA-26079 file string is not part of table string.string
Cause: A parallel load file was specified which is not in the tablespace of the table being loaded.
Action: Check to make sure that the specified parallel load file is in the tablespace of the table being loaded.
ORA-26080 file string is not part of table string.string partition string
Cause: A parallel load file was specified which is not in the tablespace of the table (partition, subpartition) being loaded. When a partitioned table is being loaded, the file must be in the tablespace of every partition or subpartition (that is, each (sub)partition must be in the same tablespace).
Action: Specify a different parallel load file, or no file at all.
ORA-26081 load stream synchronization error
Cause: The row header flag byte contains an unexpected value, this indicates that an error has occurred in either the generation of, or the pushing of the load stream from the client to the server.
Action: Usually due to an application programming error when dealing with error handling, or not resetting the stream state.
ORA-26082 load of overlapping segments on table string.string is not allowed
Cause: Client application is attempting to do multiple direct path load operations on the same table, but the segments overlap.
Action: Check the partition names (subname attribute of the direct path context) being loaded. Make sure you are not loading a table and a partition of the same table. Make sure you are not loading a partition, and a sub-partition within the same partition.
ORA-26084 direct path context already finished
Cause: An OCIDirPathLoadStream operation was attempted after OCIDirPathFinish was called. Once a direct path operation has been finished, no more data can be loaded.
Action: Check program logic to make sure OCIDirPathLoadStream is not called after OCIDirPathFinish.
ORA-26085 direct path operation must start its own transaction
Cause: A direct path operation is being attempted within a transaction that has already been started.
Action: Commit the transaction and Prepare the direct path operation again.
ORA-26086 direct path does not support triggers
Cause: A direct path operation is being attempted on a table which has enabled triggers.
Action: Disable the triggers on the table and try again.
ORA-26087 direct path does not support referential constraints
Cause: A direct path operation was attempted on a table which has enabled referential integrity constraints.
Action: Disable the referential integrity constraints on the table and try again.
ORA-26088 scalar column 'string' must be specified prior to LOB columns
Cause: All scalar columns (that is, non-LOB and non-LONG columns) must be specified by the client of the direct path API prior to specifying any LOB columns.
Action: Specify all scalar columns prior to specifying any LOB columns.
ORA-26089 LONG column 'string' must be specified last
Cause: A client of the direct path API specified a LONG column to be loaded, but the LONG column was not the last column to be specified.
Action: Specify the LONG column last.
ORA-26090 row is in partial state
Cause: A direct path operation is being finished or a data save request has been made, but the table for which the request is being made on has a row in partial state. The row must be completed before the segment high water marks can be moved.
Action: Either complete the row, or abort the direct path operation.
ORA-26091 requested direct path operation not supported
Cause: A direct path operation was requested that is not supported
Action: Do not use that operation. Currently, UNLOAD is not supported.
ORA-26092 only LONG or LOB types can be partial
Cause: A column which is not a LONG or LOB had the OCI_DIRPATH_COL_PARTIAL flag associated with it. Only LONG or LOB type columns can be loaded in pieces.
Action: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column.
ORA-26093 stream offset does not map to a column array
Cause: The ROW_COUNT attribute was being read from a direct path stream handle and it was found that the stream offset for the last processed row did not map to a column array offset.
Action: Make sure the stream was sourced from a column array.
ORA-26094 stream format error: input column overflow
Cause: An input stream contained data for more input columns than specified by the client of the direct path API.
Action: Make sure that the stream being loaded is for the correct table. Check initialization sequence.
ORA-26095 unprocessed stream data exists
Cause: Either a OCIDirPathLoadStream call was made which provided more stream data prior to the server being able to fully process the stream data that it already has, or a OCIDirPathFinish call was made when the server had unprocessed stream data.
Action: Most likely an application misuse of the direct path API. Make sure that the stream is not being reset inadvertently prior to any previous stream data being processed, or, that OCIDirPathFinish is not being called prematurely (that is, stream pushed, error encountered and LoadStream not called to process the remainder of the stream before Finish is called).
ORA-26096 transfer size too small for row data (number bytes required)
Cause: Either the transfer buffer size specified, or the default transfer buffer size (if you did not specify a size), is too small to contain a single row of the converted row data.
Action: Set the transfer buffer size attribute of the direct path context to be larger.
ORA-26097 unsupported conversion for column string (from type number to type number)
Cause: The direct path API does not support the required conversion.
Action: Make sure the types are correct.
ORA-26098 direct path context is not prepared
Cause: A direct path API function was called with a direct path context which has not been prepared.
Action: Make sure all necessary attributes in the direct path context have been set, and the context is prepared via OCIDirPathPrepare.
ORA-26099 direct path context is already prepared
Cause: OCIDirPathPrepare was called with a context that has already been prepared.
Action: Free the direct path context, set necessary attributes, and call OCIDirPathPrepare.
ORA-26100: unused error
Cause: This error is not used.
Action: No action required.
ORA-26101 tablespace # in file header is string rather than string for file string
Cause: The tablespace number in the file header is inconsistent with that in the control file.
Action: Check if the control file has been migrated correctly. Retry with the correct control file and datafile.
ORA-26102 relative file # in file header is string rather than string for file string
Cause: The relative file number in the file header is inconsistent with that in the control file.
Action: Check if the control file has been migrated correctly. Retry with the correct control file and datafile.
ORA-26103 V6 or V7 data file used to create control file
Cause: The file header of the referenced file is in V6 or V7 format.
Action: Either remove the file from the create control file command, or somehow migrate the file header to V8 format.
ORA-26500 error on caching "string"."string"
Cause: Attempt to cache the replication information which is unavailable in the catalog for the object.
Action: Use DBMS_REPUTIL.SYNC_UP_REP to validate the replication catalog, or use DBMS_REPUTIL.MAKE_INTERNAL_PKG to validate internal package.
ORA-26501 RepAPI operation failure
Cause: An external RepAPI operation failed.
Action: Consult detail error message.
ORA-26502 error resignal
Cause: An internal service failed and signalled an error.
Action: Consult detail error message.
ORA-26503 internal RepAPI operation failure on object string.string
Cause: An unexpected internal RepAPI failure was detected.
Action: Contact Oracle Support Services.
ORA-26504 operation not implemented
Cause: The caller requested a RepAPI operation that was not implemented.
Action: Do not issue this call.
ORA-26505 unexpected internal null
Cause: An internal buffer control structure was NULL.
Action: Verify that sufficient memory resources are available to RepAPI.
ORA-26506 null global context
Cause: An internal buffer control structure was NULL.
Action: Verify that sufficient memory resources are available to RepAPI.
ORA-26507 null master connection
Cause: The master connection handle was or became invalid.
Action: Verify that the master connection is valid.
ORA-26508 null materialized view connection
Cause: The client connection handle was or became invalid.
Action: Verify that the client connection is valid.
ORA-26509 null materialized view control structure
Cause: An internal materialized view control structure could not be obtained.
Action: Check that the owner and users provided are correct.
ORA-26510 materialized view name: 'string' is greater than max. allowed length of string bytes
Cause: The specified materialized view name was too long.
Action: Shorten the materialized view name.
ORA-26511 master table 'string.string' not found
Cause: A RepAPI operation was attempted against a non-existent or invalid master table.
Action: Verify that the master table object exists.
ORA-26512 error pushing transaction to def$error
Cause: An unexpected error occurred while sending an DEF$ERROR RPC to the master site.
Action: Verify that the DBMS_DEFER package is valid and executable by the RepAPI client. Contact the local or master site administrator, if necessary.
ORA-26513 push error: master proc. string$RP.string failed for trans:string seq:string
Cause: A conflict/error occurred at the master site while executing a $RP.rep_insert(), rep_update(), or rep_delete() function which was not handled by conflict resolution logic at the master.
Action: Notify master site system administrator or database administrator.
ORA-26514 object 'string.string' not found
Cause: The specified object was expected but not found.
Action: Verify that the specified object exists and is valid.
ORA-26515 no master log available for 'string.string'
Cause: The specified master log was not found or available for the named table.
Action: Create the master log at the master site or correct any problems that may exist with the log.
ORA-26516 no push transaction acknowledgement
Cause: RepAPI was unable to confirm that the last pushed transaction was successfully committed by the master site.
Action: Verify that the communications link between the local site and the master site is still valid. If the transaction has not been committed at the master, repush the transaction.
ORA-26517 materialized view control entry for 'string.string' was not found
Cause: The specified materialized view catalog control record was not found.
Action: Verify that the local materialized view catalog is valid and that the local materialized view is properly defined.
ORA-26518 push queue synchronization error detected
Cause: Client tried to repush a transaction has already been committed at the master site. A common cause of this problem is an error at the local site in initializing or updating the local site transaction sequence mechanism.
Action: Verify that transaction data that RepAPI was attempting to repushed to the master site exists at the master table and is valid and consistent with the local site. If this error occurs, redundantly identified transactions are ignored and then purged from the local updatable materialized view logs. Check that the local site is correctly assigning new transaction IDs and is not accidently generating non-unique values.
ORA-26519 no memory available to allocate
Cause: There was no memory left for the RepAPI process. This error may occur when RepAPI is trying to allocate a new table buffer area.
Action: Shut down one or more local applications to attempt to free heap memory and retry the RepAPI operation.
ORA-26520 internal memory failure
Cause: An internal memory error was detected.
Action: Check if other errors have occurred or determine if any local application may have corrupted the memory subsystem.
ORA-26521 rpc initialization error
Cause: An error occurred during the initialization of a PL/SQL RPC.
Action: Verify that the procedure to be invoked exists and is valid at the master site and is executable by the RepAPI user.
ORA-26522 rpc execution error
Cause: An error occurred during the execution of a PL/SQL RPC.
Action: Check the error messages from the remote procedure and fix any remote site problems that may be preventing the execution of the invoked RPC.
ORA-26523 rpc termination error
Cause: An error occurred during the termination of a PL/SQL RPC. This is usually caused by master site being unable to close an opened cursor or if RepAPI cannot deallocate internal memory.
Action: Fix any server side problems first, determine if the RepAPI memory subsystem has been corrupted.
ORA-26524 nls subsystem initialization failure for product=string, facility=string
Cause: The NLS product/facility error message file could not be located or properly initialized.
Action: Check that the error message directory and file(s) have been properly installed.
ORA-26525 session connection attempt failed for string (@string)
Cause: A connection could not be established to the specified database using the provided connection string.
Action: Check that the user, password, connect string, names services, network, and any remote site listener process are properly installed and working.
ORA-26526 materialized view sql ddl parse/expansion failed for string.string
Cause: The client SQL materialized view definition query could not be properly parsed by the master Oracle site.
Action: Check that materialized view DDL SQL is compatible with the currently connected version of Oracle and does not violate any of the RepAPI SQL limitations or restrictions.
ORA-26527 local store callback init phase failed for 'string.string'
Cause: The client callback failed during its INIT phase for the named object.
Action: Verify that the objects referenced by the client callback exist and are valid. Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Support Services.
ORA-26528 local store callback proc phase failed for 'string.string'
Cause: The client callback failed during its PROC phase for the named object.
Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Support Services.
ORA-26529 local store callback term phase failed for 'string.string'
Cause: The client callback failed during its TERM phase for the named object.
Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Support Services.
ORA-26530 unable to build materialized view refresh control list
Cause: The materialized view control list could not be constructed. This is generally the result of an error while accessing the local materialized view catalog.
Action: Verify that the named materialized view(s) are properly defined and valid.
ORA-26532 replication parallel push simulated site failure
Cause: A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site.
Action: Do not enable the event for normal operation.
ORA-26534 collision: tranID number ignored and purged
Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.
Action: See the action section for E_QUEUESYNC (26518).
ORA-26535 number byte row cache insufficient for table with rowsize=number
Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.
Action: Increase the RepAPI row buffer size or reduce the width of the replicated tables.
ORA-26536 refresh was aborted because of conflicts caused by deferred transactions
Cause: There are outstanding conflicts logged in the DEFERROR table at the materialized view's master site.
Action: Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master's DEFERROR table. Proceeding despite conflicts can result in an updatable materialized view's changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved.
ORA-26563 renaming this table is not allowed
Cause: Attempt to rename a replicated table, an updatable materialized view table or the master table of a materialized view for which a materialized view log has been created.
Action: If desired, unregister the replicated table with DBMS_REPCAT.DROP_MASTER_REPOBJECT, or use the recommended procedure to rename the master table of a materialized view.
ORA-26564 string argument is not of specified type
Cause: User passed type of the given argument number does not match with the type of the argument in the stored arguments.
Action: Invoke correct type procedure (that is, get_XXX_arg).
ORA-26565 Call to type_arg made before calling dbms_defer.call
Cause: User invoked type_arg procedure before starting a deferred call.
Action: Invoke various procedures in the correct order.
ORA-26566 Couldn't open connect to string
Cause: Failed to open connection using given database link.
Action: Make sure that the database link is valid and remote m/c is up.
ORA-26571 string.string.string: number of arguments (string) does not match replication catalog
Cause: The number of arguments does not match the replication catalog.
Action: Examine the total number of arguments for the RPC call.
ORA-26572 string.string.string: argument string does not match replication catalog
Cause: The (RPC) call is corrupted.
Action: Examine total number of arguments and each argument for the RPC call.
ORA-26575 remote database does not support replication parallel propagation
Cause: The remote database has a version lower than Oracle 8.0 and hence does not understand replication parallel propagation.
Action: Use serial propagation or upgrade the remote database to Oracle 8.0 or above.
ORA-26650 string background process string might not be started successfully
Cause: An error occurred during creation of a capture or apply background process.
Action: Review V$Capture and V$Apply_coordinator views for the status of these processes. Also check the trace file for more information.
ORA-26660 Invalid action context value for string
Cause: The value specified in the action context is invalid for use in STREAMS.
Action: Check that the type and value are correct.
ORA-26665 STREAMS process string already exists
Cause: An attempt was made to create a STREAMS process that already exists.
Action: Either specify another STREAMS process or remove the existing STREAMS process.
ORA-26666 cannot alter STREAMS process string
Cause: An attempt was made to alter a STREAMS process that is currently running.
Action: Stop the STREAMS process and re-issue the command.
ORA-26667 invalid STREAMS parameter string
Cause: An attempt was made to specify an invalid parameter.
Action: Check the documentation for valid parameters.
ORA-26669 parameter string inconsistent with parameter string
Cause: An attempt was made to specify a subprogram parameter value that is inconsistent with another parameter value.
Action: Check the documentation for valid parameter values.
ORA-26670 STREAMS option requires COMPATIBLE parameter to be string or higher
Cause: Streams requires compatibility to be 9.2.0 or higher.
Action: Shut down and restart with an appropriate compatibility setting.
ORA-26671 maximum number of STREAMS processes exceeded
Cause: Cannot create additional STREAMS processes since the maximum number of STREAMS processes has been reached.
Action: Remove existing STREAMS processes and retry the operation.
ORA-26672 timeout occurred while stopping STREAMS process string
Cause: Timeout occurred while waiting for a STREAMS process to shut down.
Action: Retry the operation. If the error persists, then try stopping the process with the FORCE option, or contact Oracle Support Services.
ORA-26680 object type not supported
Cause: The specified object type is not supported.
Action: Retry with a supported object type.
ORA-26681 command type not supported
Cause: The specified command type is not supported.
Action: Retry with a supported command type.
ORA-26682 invalid value for publication_on
Cause: The publication_on parameter should be either 'Y' or 'N'.
Action: Retry with a proper value for publication_on.
ORA-26683 invalid value for value_type
Cause: The value_type parameter should be either 'OLD' or 'NEW'.
Action: Retry with proper value_type.
ORA-26684 invalid value for value_type
Cause: The value_type parameter should be one of 'OLD', 'NEW', or '*'.
Action: Retry with proper value_type.
ORA-26685 cannot apply transactions from multiple sources
Cause: Transactions from multiple sources were sent to the same apply process.
Action: Create multiple apply processes and create appropriate rules so that transactions from only one source reach an apply process.
ORA-26686 cannot capture from specified SCN
Cause: An attempt was made to specify an invalid SCN.
Action: Retry with a valid SCN.
ORA-26687 no instantiation SCN provided
Cause: Object SCN has not been set.
Action: Set the SCN by calling DBMS_APPLY_ADM.SET_INSTANTIATION_SCN.
ORA-26688 missing key in LCR
Cause: Metadata mismatch, or not enough information in the user generated LCR.
Action: Alter the database object, or provide all defined keys in the LCR.
ORA-26689 column datatype mismatch in LCR
Cause: The datatypes of columns in the LCR are not the same as the datatypes in the database object.
Action: Alter the database object.
ORA-26690 datatype not supported at non-Oracle system
Cause: One of the columns of the LCR being applied was of a datatype not supported by either the target non-Oracle system or by the Oracle transparent gateway through which the apply is being done.
Action: Do not apply data of this type. If possible, filter out columns containing such datatypes before applying.
ORA-26691 operation not supported at non-Oracle system
Cause: The apply process attempted an operation that is either not supported by the non-Oracle system or by the Oracle transparent gateway through which the apply is being done. Some kinds of DML (like procedure and function calls) and all DDL will cause this error to be raised.
Action: Do not attempt to apply such LCRs to non-Oracle systems. If possible, filter out such LCRs before applying.
ORA-26701 STREAMS process string does not exist
Cause: An attempt was made to access a STREAMS process which does not exist.
Action: Check with the relevant security views for the correct name of the object.
ORA-27000 skgfqsbi: failed to initialize storage subsystem (SBT) layer
Cause: SBTINIT returned an error, additional information indicates error.
Action: Verify that vendor's storage subsystem product is operating correctly.
ORA-27001 unsupported device type
Cause: The specified device type is supported on this platform.
Action: Check V$BACKUP_DEVICE for supported device types.
ORA-27002 function called with invalid device structure
Cause: An internal error occurred. Additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27003 cannot open file on device allocated with NOIO option
Cause: An internal error occurred. A file is being created/retrieved on a device allocated with NOIO option, additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27004 invalid blocksize specified
Cause: An internal error occurred. The block size specified is incorrect for the device on which file is being created, additional information indicates block size specified, and the function that encountered the error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27005 cannot open file for async I/O on device not supporting async
Cause: An internal error occurred. A file is being opened for asynchronous I/O on a device that does not support asynchronous I/O, additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27006 sbtremove returned error
Cause: Additional information indicates error returned by SBTREMOVE, and the function that encountered the error.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27007 failed to open file
Cause: SBTOPEN returned error, additional information indicates error returned from SBTOPEN, and the function that encountered the error.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27008 function called with invalid file structure
Cause: An internal error occurred. Additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27009 skgfwrt: cannot write to file opened for read
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27010 skgfwrt: write to file failed
Cause: SBTWRITE returned error, additional information indicates error returned from SBTWRITE.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27011 skgfrd: cannot read from file opened for write
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27012 skgfrd: read from file failed
Cause: SBTREAD returned error, additional information indicates error returned from SBTREAD.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27013 skgfqdel: cannot delete an open file
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27014 skgfqpini: translation error while expanding SS_UDMPDIR
Cause: Failure of SLTLN in SKGFQPINI.
Action: Check additional return error for more information.
ORA-27015 skgfcls: failed to close the file
Cause: SBTCLOSE returned an error. Additional information indicates error returned from SBTCLOSE.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27016 skgfcls: sbtinfo returned error
Cause: Additional information indicates error returned from SBTINFO.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27017 skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)
Cause: Media handle string length exceeds SSTMXQMH.
Action: Verify that the vendor's storage subsystem product is operating correctly, and that the platform limit (SSTMXQMH) is at least 64 (the limit specified for SBTINFO). additional information indicates the media handle string length returned by SBTINFO, and the limit (SSTMXQMH).
ORA-27018 BLKSIZE is not a multiple of the minimum physical block size
Cause: User-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size that is permitted on this platform.
Action: Two ADDITIONAL INFORMATION messages are displayed which show the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integral multiple of the minimum block size.
ORA-27019 tape filename length exceeds limit (SBTOPMXF)
Cause: The length of the tape file name provided to sequential I/O OSD functions is too long.
Action: Additional information indicates in which function this error is encountered, the length of file name provided, and the limit on file name.
ORA-27020 named devices not supported
Cause: The platform or the specified device type does not support named devices.
Action: Do not specify device name or use a device type that supports named devices. Use V$BACKUP_DEVICE view to see what device types and names (if any) are available.
ORA-27021 sequential file handle must be specified
Cause: The file name which will be passed to SBTOPEN was not specified.
Action: Specify a file name and continue. If this is a backup set being created via Recovery Manager, use the 'format' option to specify the backup piece handle name.
ORA-27022 skgfqsbi: could not allocate memory for media manager
Cause: Oracle could not allocate memory required by the media management software which is linked with Oracle to provide backup/restore services.
Action: Increase the amount of memory available to the Oracle process and retry the backup/restore.
ORA-27023 skgfqsbi: media manager protocol error
Cause: The media management software which is linked with Oracle to provide backup/restore services did not provide its function pointer structure to Oracle. This is an internal error in the media management product.
Action: Contact the media management vendor.
ORA-27024 skgfqsbi: sbtinit2 returned error
Cause: SBTINIT2 returned an error. This happens during a backup or restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27025 skgfqsbi: invalid media manager context area size
Cause: The media management software requested a context area size which is greater than the maximum allowable size. This is an internal error in the media management product.
Action: Contact the media management vendor.
ORA-27026 skgfrls: sbtend returned error
Cause: SBTEND returned an error. This happens during a backup or restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27027 sbtremove2 returned error
Cause: SBTREMOVE2 returned an error. This happens when deleting a backup file.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27028 skgfqcre: sbtbackup returned error
Cause: SBTBACKUP returned an error. This happens when creating a backup file during a backup operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27029 skgfrtrv: sbtrestore returned error
Cause: SBTRESTORE returned an error. This happens when retrieving a backup file during a restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27030 skgfwrt: sbtwrite2 returned error
Cause: SBTWRITE2 returned an error. This happens while writing a backup file during a backup operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27031 mirror resilvering functions not supported
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27032 skgfrpini: failed to obtain file size limit
Cause: GETRLIMIT system call returned an error.
Action: Check errno.
ORA-27033 skgfrpini: failed to obtain file size limit
Cause: ULIMIT system call returned an error.
Action: Check errno.
ORA-27034 skgfrcre: maximum length of ORACLE_SID exceeded
Cause: Too many characters in the ORACLE_SID string.
Action: Rename the ORACLE_SID to a string of up to the maximum number of characters specified for your system.
ORA-27035 logical block size is invalid
Cause: Logical block size for Oracle files must be a multiple of the physical block size, and less than the maximum.
Action: Block size specified is returned as additional information, check initialization parameters, additional information also indicates which function encountered the error.
ORA-27036 translation error, unable to expand file name
Cause: Additional information indicates SLTLN/SLNRM error, and also indicates which function encountered the error.
Action: Check additional information.
ORA-27037 unable to obtain file status
Cause: STAT system call returned an error, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27038 skgfrcre: file exists
Cause: Trying to create a database file, but file by that name already exists.
Action: Verify that name is correct, specify reuse if necessary.
ORA-27039 create file failed, file size limit reached
Cause: An attempt was made to create a file that exceeds the process' file size limit, additional information indicates which function encountered the error.
Action: Raise the file size limit.
ORA-27040 skgfrcre: create error, unable to create file
Cause: Create system call returned an error, unable to create file.
Action: Verify the file name and permissions.
ORA-27041 unable to open file
Cause: Open system call returned an error, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27042 not enough space on raw partition to fullfill request
Cause: This is an internal error. The file is too large for the raw partition. Additional information indicates which function encountered the error.
Action: Check for trace file and contact Oracle Support Services.
ORA-27043 unable to seek to beginning of file
Cause: Seek system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27044 unable to write the header block of file
Cause: Write system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27045 unable to close the file
Cause: Close system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27046 file size is not a multiple of logical block size
Cause: File size as indicated by STAT is not correct, additional information indicates which function encountered the error.
Action: Verify that the file has not been overwritten or truncated.
ORA-27047 unable to read the header block of file
Cause: Read system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27048 skgfifi: file header information is invalid
Cause: Possibly trying to use a non-database file as a database file.
Action: Verify that file is a database file.
ORA-27049 unable to seek to and read the last block
Cause: An attempt was made to seek to and read the last block in file, additional information indicates which function encountered error.
Action: Check errno.
ORA-27050 function called with invalid FIB/IOV structure
Cause: This is an internal error. Additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27052 unable to flush file data
Cause: FSYNC system call returned error, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27053 skgfifi: blocksize in file header not a multiple of logical block size
Cause: The logical block size is invalid, additional information indicates the logical block size and the block size in the file header.
Action: Use a different logical block size, or do not reuse file.
ORA-27056 skgfrdel: could not delete file
Cause: Unlink system call returned error.
Action: Check errno.
ORA-27057 skgfask: cannot perform async I/O to file
Cause: This is an internal error. The query is being asked about asynchronous vector I/O when the file does not support asynchronous I/O.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27058 skgfask: question parameter is invalid
Cause: This is an internal error. An invalid query is being asked.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27059 skgfrsz: could not reduce file size
Cause: FTRUNCATE system call returned error.
Action: Check errno.
ORA-27060 skgfofi: could not set close-on-exec bit on file
Cause: FCNTL system call returned error.
Action: Check errno.
ORA-27061 skgfospo: waiting for async I/Os failed
Cause: AIOWAIT function returned error.
Action: Check errno.
ORA-27062 skgfospo: could not find pending async I/Os
Cause: There should have been some asynchronous I/Os in the system but a blocking aiowait indicates that there are no more I/Os. It could be due to an Oracle bug, a vendor OS bug, or an NFS server not responding.
Action: Check the Oracle trace file, OS message files, and contact Oracle Support Services.
ORA-27063 skgfospo: number of bytes read/written is incorrect
Cause: The number of bytes read/written as returned by AIOWAIT does not match the original number, additional information indicates both these numbers.
Action: Check errno.
ORA-27064 skgfdisp: cannot perform async I/O to file
Cause: This is an internal error. A request was made to perform asynchronous I/O when IOV indicates that it cannot be performed on the file.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27065 skgfdisp: cannot perform async vector I/O to file
Cause: This is an internal error. A request was made to perform asynchronous vector I/O when it cannot be performed on the file.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27066 skgfdisp: number of buffers in vector I/O exceeds maximum
Cause: This is an internal error. The number of buffers in vector I/O exceeds maximum allowed by the OSD, additional information indicates both these numbers.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27067 skgfdisp: size of buffer is invalid
Cause: This is an internal error. The buffer size is either 0, or greater than SSTIOMAX or not a multiple of logical block size, additional information indicates where in function the error was encountered and the buffer size.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27068 skgfdisp: buffer is not aligned properly
Cause: This is an internal error. The buffer is not aligned to SSIOALIGN boundary, additional information indicates where in function the error was encountered and the buffer pointer.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27069 skgfdisp: attempt to do I/O beyond the range of the file
Cause: This is an internal error. The range of blocks being read or written is outside the range of the file, additional information indicates the starting block number, number of blocks in I/O, and the last valid block in the file.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27070 skgfdisp: async read/write failed
Cause: AIOREAD/AIOWRITE system call returned error, additional information indicates starting block number of I/O.
Action: Check errno.
ORA-27071 skgfdisp: unable to seek to desired position in file
Cause: LSEEK system call returned error, additional information indicates block number in file to which seek was attempted.
Action: Check errno.
ORA-27072 skgfdisp: I/O error
Cause: READ/WRITE/READV/WRITEV system call returned error, additional information indicates starting block number of I/O.
Action: Check errno.
ORA-27073 skgfcfi: async I/Os remaining to be dequeued for this file
Cause: This is an internal error. The file is being closed but not all asynchronous I/Os to the file have been dequeued, additional information indicates number of I/Os pending on the file.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27074 skgfrofl: unable to determine limit for open files
Cause: GETRLIMIT system call returned error.
Action: Check errno.
ORA-27075 skgfrofl: SSTMOFRC constant too large
Cause: This is an internal error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27076 skgfrofl: unable to set limit for open files
Cause: SETRLIMIT system call returned error.
Action: Check errno.
ORA-27077 skgfofi: too many files open
Cause: This is an internal error. The number of files opened through SKGFOFI has reached the limit.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27080 skgfrdup: too many files open
Cause: the number of files opened has reached system limit.
Action: check error, and set system configuration values.
ORA-27084 skgfqio: unable to get/set file status flags
Cause: System call FCNTL with F_GETFL/F_SETFL flag returned error.
Action: Check errno.
ORA-27086 skgfglk: unable to lock file - already in use
Cause: The file is locked by another process, indicating that it is currently in use by a database instance.
Action: Determine which database instance legitimately owns this file.
ORA-27087 skgfglk: unable to get share lock - file not readable
Cause: Share lock request was made on a file not open for read access.
Action: File must be open read-only or read-write to get a share lock.
ORA-27088 skgfglk: unable to get file status
Cause: The file is not open or the file descriptor is invalid.
Action: Make sure the file is open and the descriptor is valid.
ORA-27089 skgfrlk: unable to release advisory lock
Cause: The file lock release failed.
Cause: See the errno.
ORA-27091 skgfqio: unable to queue I/O
Cause: A read/write/readv/writev system call returned error. Additional information indicates the starting block number of the I/O.
Action: Check the errno.
ORA-27092 skgfofi: size of file exceeds file size limit of the process
Cause: An attempt was made to open a file that exceeds the process's file size limit (ulimit), additional information shows the current limit (logical blocks) and the size of the file (logical blocks).
Action: increase the processes file size limit (ulimit) and retry.
ORA-27100 shared memory realm already exists
Cause: An attempt was made to start duplicate instances, or tried to restart an instance that had not been properly shut down.
Action: Use a different instance name, or cleanup the failed instance's SGA.
ORA-27101 shared memory realm does not exist
Cause: Unable to locate shared memory realm.
Action: Verify that the realm is accessible.
ORA-27102 out of memory
Cause: Out of memory.
Action: Consult the trace file for details.
ORA-27103 internal error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-27120 unable to removed shared memory segment
Cause: SHMCTL() call failed.
Action: check permissions on segment, contact Oracle Support Services.
ORA-27121 unable to determine size of shared memory segment
Cause: SHMCTL() call failed.
Action: check permissions on segment, contact Oracle Support Services.
ORA-27122 unable to protect memory
Cause: MPROTECT() call failed.
Action: Contact Oracle Support Services.
ORA-27123 unable to attach to shared memory segment
Cause: SHMAT() call failed.
Action: Check permissions on segment, contact Oracle Support Services.
ORA-27124 unable to detach from shared memory segment
Cause: SHMDT() call failed.
Action: Contact Oracle Support Services.
ORA-27125 unable to create shared memory segment
Cause: SHMGET() call failed.
Action: Contact Oracle Support Services.
ORA-27126 unable to lock shared memory segment in core
Cause: Insufficient privileges to lock shared memory segment in core.
Action: Make sure the process is running with the necessary privileges.
ORA-27127 unable to unlock shared memory segment
Cause: Insufficient privileges to unlock shared memory segment.
Action: Make sure the process is running with the necessary privileges.
ORA-27128 unable to determine pagesize
Cause: SYSCONF() call failed.
Action: Contact Oracle Support Services.
ORA-27141 invalid process ID
Cause: Process operation attempted using invalid process ID.
Action: Contact Oracle Support Services.
ORA-27142 could not create new process
Cause: Operating system call error.
Action: Check errno and if possible increase the number of processes.
ORA-27143 OS system call failure
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27144 attempt to kill process failed
Cause: Operating system call error.
Action: Check errno and contact Oracle Support Services.
ORA-27145 insufficient resources for requested number of processes
Cause: Operating system call error.
Action: Check errno and contact Oracle Support Services.
ORA-27146 post/wait initialization failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27147 post/wait reset failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27148 spawn wait error
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27149 assignment out of range
Cause: This is an internal error. A request was made for a conversion too large for the type.
Action: Contact Oracle Support Services.
ORA-27150 attempt to notify process of pending oradebug call failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27151 buffer not large enough to hold process ID string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-27152 attempt to post process failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27153 wait operation failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27154 post/wait create failed
Cause: This is an internal error. Multiple post/wait creates were attempted simultaneously.
Action: Check errno and contact Oracle Support Services.
ORA-27155 could not execute file
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27156 request for process information failed
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-27157 OS post/wait facility removed
Cause: The post/wait facility for which the calling process is awaiting action was removed from the system.
Action: Check errno and contact Oracle Support Services.
ORA-27190 skgfrd: sbtread2 returned error
Cause: SBTREAD2 returned an error. This happens while reading a backup file during a restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27191 sbtinfo2 returned error
Cause: SBTINFO2 returned an error. This happens while retrieving backup file information from the media manager's catalog.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27192 skgfcls: sbtclose2 returned error - failed to close file
Cause: SBTCLOSE2 returned an error. This happens while closing a backup file during a backup or restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27193 sbtinfo2 did not return volume label
Cause: SBTINFO2 did not return the volume label information for the backup file that was just created. This is an internal error in the media management product.
Action: Contact the media management vendor.
ORA-27194 skgfdvcmd: sbtcommand returned error
Cause: SBTCOMMAND returned an error. This happens when an RMAN SEND command is issued.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27195 proxy copy not supported
Cause: An attempt was made to do a proxy backup or restore, but the media management software installed with Oracle does not support proxy copy.
Action: Rerun the backup in non-proxy mode, or contact the media management vendor if the software is supposed to support proxy copy.
ORA-27196 skgfpbk: sbtpcbackup returned error
Cause: SBTPCBACKUP returned an error. This happens when a proxy backup is begun.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27197 skgfprs: sbtpcrestore returned error
Cause: SBTPCRESTORE returned an error. This happens when a proxy restore is begun.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27198 skgfpvl: sbtpcvalidate returned error
Cause: SBTPCVALIDATE returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27199 skgfpst: sbtpcstatus returned error
Cause: SBTPCSTATUS returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27200 skgfpgo: sbtpcstart returned error
Cause: SBTPCSTART returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27201 skgfpcm: sbtpccommit returned error
Cause: SBTPCCOMMIT returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27202 skgfpen: sbtpcend returned error
Cause: SBTPCEND returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27203 skgfpqb: sbtpcquerybackup returned error
Cause: SBTPCQUERYBACKUP returned an error. This happens during a proxy backup.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27204 skgfpqr: sbtpcqueryrestore returned error
Cause: SBTPCQUERYRESTORE returned an error. This happens during a proxy restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27205 skgfpcn: sbtpccancel returned error
Cause: SBTPCCANCEL returned an error. This happens during a proxy restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27206 requested file not found in media management catalog
Cause: A backup file used in a recovery manager catalog maintenance command was not found in the media management catalog.
Action: Retry the command with a different file.
ORA-27207 syntax error in device PARMS - parentheses mismatch or missing
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn
ORA-27208 syntax error in device PARMS - environment variable value missing
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with the correct syntax: ENV=(var1=val1,var2=val2,..)
ORA-27209 syntax error in device PARMS - unknown keyword or missing =
Cause: User-supplied PARMS value has incorrect syntax. The server expected to find ENV or BLKSIZE, but found an unknown keyword.
Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn
ORA-27210 syntax error in device PARMS
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn
ORA-27211 Failed to load Media Management Library
Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call to dlopen for media library returned error. See Additional information for the error code.
Action: Retry the command with proper media library. Or re-install Media management module for Oracle.
ORA-27212 some entrypoints in Media Management Library are missing
Cause: Media library does not have one of the following entrypoints : sbtinfo, sbtread, sbtwrite, sbtremove, sbtopen, sbtclose, or sbtinit.
Action: Retry the command with proper media library.
ORA-27213 failed to unload Media Management Library
Cause: The dlclose for media library returned an error. See Additional information for the error code.
Action: Contact Oracle Support Services.
ORA-27300 OS system dependent operation:string failed with status: string
Cause: Operating system call error.
Action: Contact Oracle Support Services.
ORA-27301 OS failure message: string
Cause: Operating system call error.
Action: Contact Oracle Support Services.
ORA-27302 failure occurred at: string
Cause: Operating system call error.
Action: Contact Oracle Support Services.
ORA-27303 additional information: string
Cause: Operating system call error.
Action: Contact Oracle Support Services.
ORA-27500 inter-instance IPC error
Cause: This is an operating system/cluster interconnect error.
Action: Check the extra information and contact Oracle Support Services.
ORA-27501 IPC error creating a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27502 IPC error deleting OSD context
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27505 IPC error destroying a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27506 IPC error connecting to a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27507 IPC error disconnecting from a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27508 IPC error sending a message
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27509 IPC error receiving a message
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27510 IPC error waiting for a request to complete
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27512 IPC error posting a process
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27542 Failed to unprepare a buffer prepared for remote update
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27543 Failed to cancel outstanding IPC request
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27544 Failed to map memory region for export
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27545 Fail to prepare buffer for remote update
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27546 Oracle compiled against IPC interface version string.string found version string.string
Cause: A misconfiguration or installation error occurred.
Action: Install the IPC library for this release of Oracle.
ORA-27547 Unable to query IPC OSD attribute string
Cause: This is an operating system-dependent IPC error.
Action: Contact Oracle Support Services.
ORA-27548 Unable to unprepare IPC buffer
Cause: This is an operating system-dependent IPC error.
Action: Contact Oracle Support Services.
ORA-28000 the account is locked
Cause: The user has entered wrong password consequently for maximum number of times specified by the user's profile parameter FAILED_LOGIN_ATTEMPTS, or the database administrator has locked the account.
Action: Wait for PASSWORD_LOCK_TIME or contact the database administrator.
ORA-28001 the password has expired
Cause: The user's account has expired and the password needs to be changed.
Action: Change the password or contact the database administrator.
ORA-28002 the password will expire within string days
Cause: The user's account is about to about to expire and the password needs to be changed.
Action: Change the password or contact the database administrator.
ORA-28003 password verification for the specified password failed
Cause: The new password did not meet the necessary complexity specifications and the PASSWORD_VERIFY_FUNCTION failed.
Action: Enter a different password. Contact the database administrator to find out the rules for choosing the new password.
ORA-28004 invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
Cause: The password verification function does not have the required number and type of input/output arguments and/or the return argument.
Action: Check the Oracle9i Security Overview to find out the format of the password verification function.
ORA-28005 invalid logon flags
Cause: The flags are not properly set or conflicting flags are set in making calls.
Action: Call the function with appropriate flags set.
ORA-28006 conflicting values for parameters string and string
Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX cannot both be set. One parameter should be unlimited while other is set.
Action: Set one value to UNLIMITED explicitly.
ORA-28007 the password cannot be reused
Cause: The password cannot be reused for the specified number of days or for the specified number of password changes.
Action: Try the password that you have not used for the specified number of days or the specified number of password changes Refer to the password parameters in the CREATE PROFILE statement.
ORA-28008 invalid old password
Cause: Old password supplied is wrong; Hence user cannot be authenticated using old password.
Action: Supply the correct old password for authentication.
ORA-28009 connection to sys should be as sysdba or sysoper
Cause: Connect sys/password is no longer a valid syntax.
Action: Try connect sys/password as sysdba or connect sys/password as sysoper.
ORA-28010 cannot expire external or global accounts
Cause: If a user account is created as IDENTIFIED EXTERNALLY, or IDENTIFIED GLOBALLY, this account cannot be expired.
Action: Try to expire the password of the user that has database password.
ORA-28011 the account will expire soon; change your password now
Cause: The user's account is marked for expire; the expiry period is unlimited.
Action: Change the password or contact the DBA.
ORA-28020 IDENTIFIED GLOBALLY already specified
Cause: The IDENTIFIED GLOBALLY clause was specified twice.
Action: Use only one IDENTIFIED GLOBALLY clause.
ORA-28021 cannot grant global roles
Cause: A role granted was IDENTIFIED GLOBALLY. Global roles can only be granted via a central authority for the domain.
Action: Use ALTER ROLE to change the type of role (from IDENTIFIED GLOBALLY to other, such as IDENTIFIED BY password), or allocate it to a global user via the central authority.
ORA-28022 cannot grant external roles to global user or role
Cause: A role granted was IDENTIFIED EXTERNALLY. External roles cannot be granted to global users or global roles.
Action: Use ALTER ROLE to change the type of the role being granted (from IDENTIFIED EXTERNALLY to other, such as IDENTIFIED BY password), or use ALTER ROLE or ALTER USER to change the type of the user or role that is the grantee.
ORA-28023 must revoke grants of this role to other user(s) first
Cause: The role altered to IDENTIFIED GLOBALLY was granted to one or more other users and/or roles. Global roles cannot be granted to any user or role.
Action: Use REVOKE to revoke the role from other users or roles first.
ORA-28024 must revoke grants of external roles to this role/user
Cause: The user or role altered to IDENTIFIED GLOBALLY has external roles directly granted; these must be revoked, since external roles cannot be granted to global users or roles.
Action: Use REVOKE to revoke the external roles from the user or role to be ALTERed.
ORA-28025 missing or null external name
Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name.
Action: Provide a valid external name.
ORA-28026 user with same external name already exists
Cause: The external name specified for the user being created or altered already exists for another user.
Action: External names must be unique among users. Specify another.
ORA-28027 privileged database links may be used by global users
Cause: Only users IDENTIFIED GLOBALLY may use a privileged database link.
Action: Either change the user to a global user or try to use a different database link.
ORA-28028 could not authenticate remote server
Cause: During the course of opening a privileged database link, the remote server was not securely identified using the network security service. Additional errors should follow.
Action: Consult the network security service documentation on how to properly configure the remote server.
ORA-28029 could not authorize remote server for user string
Cause: During the course of opening a privileged database link, the remote server was found to lack the necessary authorizations to connect as the current global user. This may be because the server was not authorized by the network security service. Or it may be because the local server is restricting access by the remote server using the DBMS_SECURITY_DOMAINS_ADMIN package.
Action: Grant the remote server the proper authorization to connect as the given global user, and check that the local server is not restricting access.
ORA-28030 Server encountered problems accessing LDAP directory service
Cause: Unable to access LDAP directory service.
Action: Contact your system administrator.
ORA-28035 Cannot Get Session Key for Authentication
Cause: Client and server cannot negotiate shared secret during logon.
Action: Contact your system administrator.
ORA-28100 policy function schema string is invalid
Cause: The schema was dropped after the policy associated with the function had been added to the object.
Action: Drop the policy and re-create it with a policy function owned by a valid user. Or re-create the user and the policy function under the new user.
ORA-28101 policy already exists
Cause: A policy with the same name for the same object already exists.
Action: Check if the policy has already been added or use a different policy name.
ORA-28102 policy does not exist
Cause: Try to drop/enable/refresh a non-existent policy.
Action: Correct the policy name argument.
ORA-28103 adding a policy to an object owned by SYS is not allowed
Cause: Try to add a policy to a table or a view owned by SYS.
Action: You cannot perform this operation.
ORA-28104 policy function or package is invalid
Cause: The function or package implementing a policy does not exist or was created with errors.
Action: Correct the function or package.
ORA-28106 input value for argument #string is not valid
Cause: Input values for the argument is missing or invalid.
Action: Correct the input values.
ORA-28107 policy was disabled
Cause: Try to flush a disabled policy.
Action: If the policy is supposed to be enforced, it must be enabled.
ORA-28108 circular security policies detected
Cause: Policies for the same object reference each other.
Action: Drop the policies.
ORA-28109 the number of related policies has exceeded the limit of 16
Cause: Too many policies are involved in the same objects.
Action: Drop one or more policies. Or combine a few of them into one.
ORA-28110 policy function or package string.string has error
Cause: The policy function may have been dropped, or is no longer valid.
Action: Check the status of the function and correct the problem. Or re-create the policy with a valid function.
ORA-28111 insufficient privilege to evaluate policy predicate
Cause: Predicate has a subquery which contains objects that the owner of policy function does not have privilege to access.
Action: Grant appropriate privileges to the policy function owner.
ORA-28112 failed to execute policy function
Cause: The policy function has one or more error during execution.
Action: Check the trace file and correct the errors.
ORA-28113 policy predicate has error
Cause: Policy function generates invalid predicate.
Action: Review the trace file for detailed error information.
ORA-28115 policy with check option violation
Cause: Policy predicate was evaluated to FALSE with the updated values.
Action: Check the trace file and correct the errors.
ORA-28116 insufficient privileges to do direct path access
Cause: Users with insufficient privileges attempting to do direct path access of tables with fine grain access control policies.
Action: Ask the database administrator to do the operation. Note that users can work with security administrator to temporarily drop/disable the policies at time of export, import, or load, but this has security implication, and thus access of the database must be controlled carefully.
ORA-28117 integrity constraint violated - parent record not found
Cause: tried to update/insert a child record with new foreign key values, but the corresponding parent row was not visible because of fine-grained security in the parent.
Action: make sure that the updated foreign key values are visible in the parent.
ORA-28118 policy group already exists
Cause: tried to create a policy group that already exists.
ORA-28119 policy group does not exist
Cause: tried to drop a policy group that does not exist.
ORA-28120 driving context already exists
Cause: tried to create a driving context that already exists.
ORA-28121 driving context does not exist
Cause: tried to drop a driving context that does not exist.
ORA-28132 Merge into syntax does not support security policies.
Cause: Merge into syntax currently does not support a security policy on the destination table.
Action: use the insert / update DML stmts on the table that has a security policy defined on it.
ORA-28133 full table access is restricted by fine-grained security
Cause: The user is not SYS and doesn't have full table access due to VPD policies. This only happens for internal DML/query under a DDL.
Action: Grant the appropriate privilege or contact Oracle Support Services if this is too restrictive.
ORA-28134 object cannot have fine-grained access control policy
Cause: Only tables, views, or synonyms of tables or views may have VPD policies.
Action: No action required.
ORA-28150 proxy not authorized to connect as client
Cause: A proxy user attempted to connect as a client, but the proxy was not authorized to act on behalf of the client.
Action: Grant the proxy user permission to perform actions on behalf of the client by using the ALTER USER... GRANT CONNECT command.
ORA-28151 more than one user name specified for command
Cause: More than one user name was specified for an ALTER USER command.
Action: Try the command again with only one user name.
ORA-28152 proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
Cause: A proxy user attempted to specify an initial role for a client, but the client does not possess the role.
Action: Change the proxy user so that it does not specify the role or grant the role to the client.
ORA-28153 Invalid client initial role specified: 'string'
Cause: A role specified by a proxy user as an initial role to be activated upon connecting on behalf of a client is invalid.
Action: Connect again as the client specifying a valid role.
ORA-28154 Proxy user may not act as client 'string'
Cause: A proxy user cannot assume the identity of a privileged user in order to limit the privileges that a proxy can possess.
Action: Execute the statement again, specifying a client other than a privileged user.
ORA-28155 user 'string' specified as a proxy is actually a role
Cause: A user specified in an AUDIT operation BY proxy ON BEHALF OF client is actually a role.
Action: Execute the statement again with a valid proxy user.
ORA-28156 Proxy user 'string' not authorized to set role 'string' for client 'string'
Cause: A proxy user has not been granted the right to use a role on behalf of a client.
Action: Execute the command ALTER USER client GRANT CONNECT THROUGH PROXY proxy to grant the needed role.
ORA-28157 Proxy user 'string' forbidden to set role 'string' for client 'string'
Cause: A proxy user was forbidden to use a role on behalf of a client through the command ALTER USER client GRANT CONNECT THROUGH proxy WITH ALL ROLES EXCEPT role.
Action: Execute the command ALTER USER client GRANT CONNECT THROUGH PROXY proxy to grant the needed role.
ORA-28158 missing ALL keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28159 missing BEHALF keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28160 missing EXCEPT keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28161 missing ROLES keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28162 missing THROUGH keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28163 GRANT already specified
Cause: The GRANT clause was specified twice.
Action: Use only one GRANT clause.
ORA-28164 REVOKE already specified
Cause: The REVOKE clause was specified twice.
Action: Use only one REVOKE clause.
ORA-28165 proxy 'string' may not specify password-protected role 'string' for client 'string'
Cause: A proxy user attempted to activate a role on behalf of a client which has a password associated with it. Since the proxy does not have a password, this activation cannot be allowed.
Action: Attempt to activate a different role or change the role administratively so that there is no password.
ORA-28166 duplicate rolename in list
Cause: The name of a role was specified more than once in a list.
Action: Repeat the command specifying the role once.
ORA-28168 attempted to grant password-protected role
Cause: An ALTER USER ... GRANT CONNECT command was attempted specifying a role that is protected by a password as a role which the proxy may execute on behalf of a client.
Action: Either specify a role that does not have a password or alter the role so that a password is not required.
ORA-28169 unsupported certificate type
Cause: The type of certificate from which the server is to extract the credentials of the client is not supported.
Action: Specify a supported type.
ORA-28170 unsupported certificate version
Cause: The version of the certificate from which the server is to extract the credentials of the client is not supported.
Action: Specify a supported version.
ORA-28171 unsupported Kerberos version
Cause: The version of the Kerberos ticket which the server is to use to validate the identity of the client is not supported.
Action: Specify a supported version.
ORA-28172 distinguished name not provided by proxy
Cause: A client user is to be identified using a distinguished name, but none was provided by the proxy user.
Action: Provide a distinguished name.
ORA-28173 certificate not provided by proxy
Cause: A client user is to be identified using a certificate but none was provided by the proxy user.
Action: Provide a certificate.
ORA-28174 Kerberos ticket not provided by proxy
Cause: A client user is to be authenticated using a Kerberos ticket but none was provided by the proxy user.
Action: Provide a Kerberos ticket.
ORA-28175 incorrect certificate type
Cause: the type of certificate provided by the proxy user to identify a client user does not match the type that is required.
Action: Provide a certificate of the correct type.
ORA-28176 incorrect certificate version
Cause: The version of the certificate provided by the proxy user to identify a client user does not match the version that is required.
Action: Provide a certificate of the correct version.
ORA-28177 incorrect Kerberos ticket version
Cause: the version of the Kerberos ticket provided by the proxy user to authenticate a client user does not match the version that is required.
Action: Provide a Kerberos ticket of the correct version.
ORA-28178 password not provided by proxy
Cause: A client user is to be authenticated using a database password but none was provided by the proxy user.
Action: Provide a password.
ORA-28179 client user name not provided by proxy
Cause: No user name was provided by the proxy user for the client user.
Action: Either specify a client database user name, a distinguished name or an X.509 certificate.
ORA-28180 multiple authentication methods provided by proxy
Cause: More than one authentication method was specified by the proxy user for the client user.
Action: Specify only one of the following:
A client database user name
A distinguished name
An X.509 certificate.
ORA-28200 IDENTIFIED USING already specified
Cause: The IDENTIFIED USING clause was specified twice.
Action: Use only one IDENTIFIED USING clause.
ORA-28201 Not enough privileges to enable application role 'string'
Cause: An attempt to enable application role outside the scope of the designated package.
Action: Enable the role directly or indirectly using the designated package.
ORA-12700 invalid NLS parameter value (string)
Cause: An invalid NLS initialization parameter was specified.
Action: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.
ORA-12701 CREATE DATABASE character set is not known
Cause: The character set specified in the CREATE DATABASE command does not exist on the system.
Action: Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.
ORA-12702 invalid NLS parameter string used in SQL function
Cause: An invalid parameter or value was entered in the NLS parameter string in a SQL function.
Action: Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.
ORA-12703 this character set conversion is not supported
Cause: An attempt was made to use the CONVERT function to convert between two character sets, and the requested conversion is not possible due to unavailability of one or both character sets.
Action: Use character sets available on the system in the CONVERT function.
ORA-12704 character set mismatch
Cause: One of the following:
The string operands (other than an NLSPARAMS argument) to an operator or built-in function do not have the same character set.
An NLSPARAMS operand is not in the database character set.
String data with character set other than the database character set is passed to a built-in function not expecting it.
The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS.
A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the
column into which the value would be inserted.
A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column.
An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter.
Action: Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other.
ORA-12705 invalid or unknown NLS parameter value specified
Cause: There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set.
Action: Check the syntax of the ALTER SESSION statement and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION statement, see the Oracle9i SQL Reference.
ORA-12706 this CREATE DATABASE character set is not allowed
Cause: An attempt was made to create a database on an ASCII-based machine using an EBCDIC-based character set or vice versa. This is not permitted.
Action: Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported.
ORA-12707 error while getting create database NLS parameter string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12708 error while loading create database NLS parameter string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12709 error while loading create database character set
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-12710 CREATE CONTROLFILE character set is not known
Cause: The character set specified when creating the control file is unknown.
Action: Specify a known character set.
ORA-12711 this CREATE CONTROLFILE character set is not allowed
Cause: It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.
Action: Create the correct control file for machine and character set.
ORA-12712 new character set must be a superset of old character set
Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set must be a superset of the old character set. For example, WE8ISO8859P1 is not a superset of the WE8DEC.
Action: Specify a superset character set.
ORA-12713 Character data loss in NCHAR/CHAR conversion
Cause: When character set conversion happens between CHAR and NCHAR either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.
Action: Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to false.
ORA-12714 invalid national character set specified
Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set.
Action: Ensure that the specified national character set is valid.
ORA-12715 invalid character set specified
Cause: The character set specified is not allowed for this operation or is invalid.
Action: Ensure that the specified character set is valid.
ORA-12716 Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
Cause: CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.
Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated by methods such as export/import.
ORA-12717 Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists
Cause: NCLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.
Action: Remove NCLOB data as listed in the alert file. NCLOB data can be migrated by methods such as export/import.
ORA-12718 operation requires connection as SYS
Cause: This command can only be run when connecting as user SYS.
Action: Connect as user SYS to run this command.
ORA-12719 operation requires database is in RESTRICTED mode
Cause: This command can only be run when the database is in RESTRICTED mode.
Action: Ensure that the system is in RESTRICTED mode.
ORA-12720 operation requires database is in EXCLUSIVE mode
Cause: This command can only be run when the database is in EXCLUSIVE mode.
Action: Ensure that the system is in EXCLUSIVE mode.
ORA-12721 operation cannot execute when other sessions are active
Cause: This command can only be run when there are no other sessions active.
Action: Ensure there are no other connections to the database.
ORA-12800 system appears too busy for parallel query execution
Cause: Load on the system is too high to perform parallel queries.
Action: Re-execute serially or wait until the system load is reduced.
ORA-12801 error signaled in parallel query server string
Cause: A parallel query server reached an exception condition.
Action: Check the following error message for the cause.
ORA-12802 parallel query server lost contact with coordinator
Cause: A parallel query server lost contact with the foreground (coordinator) process/thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12803 parallel query server lost contact with another server
Cause: A parallel query server lost contact with another server.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12804 parallel query server appears to have died
Cause: Cannot find process information for a parallel query server thread.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.
ORA-12805 parallel query server died unexpectedly
Cause: A parallel query server died unexpectedly, PMON cleaning up the process.
Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services. See trace file for more details.
ORA-12806 could not get background process to hold enqueue
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
ORA-12807 process queue could not receive parallel query message
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
ORA-12808 cannot set string_INSTANCES greater than number of instances string
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement to a value larger than the number of available instances.
Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.
ORA-12809 cannot set string_INSTANCES when mounted in exclusive mode
Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement while the database was mounted in exclusive mode.
Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle9i Real Application Clusters mounted in CLUSTER_DATABASE mode.
ORA-12810 PARALLEL_MAX_SERVERS must be less than or equal to string
Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.
Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry.
ORA-12811 PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.
Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.
ORA-12812 only one 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 a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.
ORA-12813 value for PARALLEL or DEGREE must be greater than 0
Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.
Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.
ORA-12814 only one CACHE or NOCACHE clause may be specified
Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement.
Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.
ORA-12815 value for INSTANCES must be greater than 0
Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT.
Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.
ORA-12816 parallel create index fastpath operation
Cause: The parallel create index fastpath operation event has been set.
Action: Set this event only under the supervision Oracle development.
ORA-12817 parallel query option must be enabled
Cause: A parallel query option feature has been invoked but this option has not been enabled.
Action: Enable the parallel query option.
ORA-12818 invalid option in PARALLEL clause
Cause: An unrecognized option was used within a PARALLEL clause.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
ORA-12819 missing options in PARALLEL clause
Cause: PARALLEL clause cannot be empty.
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
ORA-12820 invalid value for DEGREE
Cause: Invalid value for DEGREE was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause.
ORA-12821 invalid value for INSTANCES
Cause: An invalid value for INSTANCES was specified within a PARALLEL clause.
Action: Specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause.
ORA-12822 duplicate option in PARALLEL clause
Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.
Action: Specify each desired PARALLEL clause option only once.
ORA-12823 default degree of parallelism may not be specified here
Cause: The PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER statement.
Action: Respecify with an explicit degree of parallelism.
ORA-12824 INSTANCES DEFAULT may not be specified here
Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.
ORA-12825 explicit degree of parallelism must be specified here
Cause: The DEGREE option was omitted from an ALTER DATABASE RECOVER command.
Action: Respecify with an explicit degree of parallelism.
ORA-12826 hung parallel query server was killed
Cause: The parallel query server was hung and subsequently killed.
Action: Re-execute the query and report suspicious events in the trace file to Oracle Support Services if the error persists.
ORA-12827 insufficient parallel query slaves available
Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired.
Action: Either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves.
ORA-12828 Can't start parallel transaction at a remote site
Cause: PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction.
Action: Do not use PDML at remote sites.
ORA-12829 Deadlock - itls occupied by siblings at block string of file string
Cause: A parallel statement failed because all ITLS in the current block are occupied by siblings of the same transaction.
Action: Increase the value of MAXTRANS of the block or reduce the degree of parallelism for the statement. Re-execute the statement. Report suspicious events in the trace file to Oracle Support Services if the error persists.
ORA-12830 Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12831 Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
Cause: After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued.
Action: Execute COMMIT or ROLLBACK before issuing another SQL command.
ORA-12832 Could not allocate slaves on all specified instances
Cause: After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query.
Action: To allow results to be returned by successfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances.
ORA-12833 Coordinator's instance not a member of parallel_instance_group
Cause: The coordinator's instance must be a member of the PARALLEL_INSTANCE_GROUP in which this operation will be run.
Action: Either add the coordinator's instance to the current PARALLEL_INSTANCE_GROUP or change PARALLEL_INSTANCE_GROUP.
ORA-12834 Instance group name, 'string', too long, must be less than string characters
Cause: The instance group name is too long.
Action: Either shorten the name or get rid of the instance group.
ORA-12835 No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to execute a query on global views.
Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP.
ORA-12838 cannot read/modify an object after modifying it in parallel
Cause: Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted.
Action: Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation.
ORA-12839 cannot modify an object in parallel after modifying it
Cause: Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted.
Action: Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation.
ORA-12840 cannot access a remote table after parallel/insert direct load txn
Cause: Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued.
Action: Commit/roll back the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction.
ORA-12841 Cannot alter the session parallel DML state within a transaction
Cause: Transaction in progress.
Action: Commit or roll back the transaction and then re-execute.
ORA-12842 schema modified during parallel execution
Cause: Schema modified during the parse phase of parallel processing.
Action: No action required.
ORA-12843 pdml lock not held properly on the table
Cause: The coodinator crashed or released the lock on the partition which the slave is trying to aquire.
Action: Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the PDML again.
ORA-12900 must specify a default temporary tablespace for a locally managed database
Cause: A locally managed database must have a temporary tablespace other than SYSTEM tablespace.
Action: Specify the default temporary tablespace when creating a locally managed database.
ORA-12901 Default temporary tablespace must be of TEMPORARY type
Cause: In a locally managed database, default temporary tablespace must be TEMPORARY type.
Action:
ORA-12902 default temporary tablespace must be SYSTEM or of TEMPORARY type
Cause: In a dictionary-managed database, default temporary tablespace must be SYSTEM or TEMPORARY type.
Action:
ORA-12903 default temporary tablespace must be an ONLINE tablespace
ORA-12904 default temporary tablespace cannot be altered to PERMANENT type
ORA-12905 default temporary tablespace cannot be brought OFFLINE
ORA-12906 cannot drop default temporary tablespace
ORA-12907 tablespace string is already the default temporary tablespace
ORA-12908 cannot specify SYSTEM as default temporary tablespace when creating database
ORA-12909 TEMPORARY keyword expected
ORA-12910 cannot specify temporary tablespace as default tablespace
Cause: An attempt was made to assign a temporary tablespace to be a user's default tablespace.
Action: Assign a permanent tablespace to be the default tablespace.
ORA-12911 permanent tablespace cannot be temporary tablespace
Cause: An attempt was made to assign a permanent tablespace to be a user's temporary tablespace.
Action: Assign a temporary tablespace to be user's temporary tablespace.
ORA-12912 Dictionary managed tablespace specified as temporary tablespace
Cause: An attempt was made to assign a dictionary managed tablespace to be a user's temporary tablespace.
Action: Assign a locally managed temporary tablespace to be the user's temporary tablespace.
ORA-12913 Cannot create dictionary managed tablespace
Cause: An attempt was made to create a dictionary managed tablespace in a database whose SYSTEM tablespace is locally managed.
Action: Create a locally managed tablespace.
ORA-12914 Cannot migrate tablespace to dictionary managed type
Cause: An attempt was made to migrate a locally managed tablespace to dictionary managed type when the database has a locally managed SYSTEM tablespace.
Action: Such an operation cannot be issued.
ORA-12915 Cannot alter dictionary managed tablespace to read write
Cause: An attempt was made to alter a dictionary managed tablespace to read write in a database whose SYSTEM tablespace is locally managed. This tablespace can only be dropped.
Action: Such an operation cannot be issued.
ORA-12920 database is already in force logging mode
Cause: The ALTER DATABASE FORCE LOGGING statement failed because the database is already in force logging mode.
Action: No action required.
ORA-12921 database is not in force logging mode
Cause: The ALTER DATABASE NO FORCE LOGGING statement failed because the database is not in force logging mode.
Action: No action required.
ORA-12922 concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING statement running in the system.
Action: Contact the database administrator who is responsible for the concurrent statement.
ORA-12923 tablespace string is in force logging mode
Cause: An attempt to alter the specified temporary tablespace failed because the tablespace is in force logging mode.
Action: Put the tablespace out of force logging mode by issuing an ALTER TABLESPACE NO FORCE LOGGING statement.
ORA-12924 tablespace string is already in force logging mode
Cause: An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode.
Action: No action required.
ORA-12925 tablespace string is not in force logging mode
Cause: An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode.
Action: No action required.
ORA-12926 FORCE LOGGING option already specified
Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once.
Action: Remove all but one of the FORCE LOGGING options.
ORA-12980 checkpoint option not allowed with SET UNUSED
Cause: An attempt was made to specify checkpoint option with SET UNUSED.
Action: Remove the checkpoint option.
ORA-12981 cannot drop column from an object type table
Cause: An attempt was made to drop a column from an object type table.
Action: This action is not allowed.
ORA-12982 cannot drop column from a nested table
Cause: An attempt was made to drop a column from a nested table.
Action: This action is not allowed.
ORA-12983 cannot drop all columns in a table
Cause: An attempt was made to drop all columns in a table.
Action: Make sure at least one column remains in the table after the drop column operation.
ORA-12984 cannot drop partitioning column
Cause: An attempt was made to drop a column used as the partitioning key.
Action: This action is not allowed.
ORA-12985 tablespace 'string' is read only, cannot drop column
Cause: An attempt was made to drop column from a partition/subpartition on a read-only tablespace.
Action: Set the tablespace to read write and resubmit statement.
ORA-12986 columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE
Cause: An attempt was made to access a table with columns in partially dropped state (that is, drop column operation was interrupted).
Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table.
ORA-12987 cannot combine drop column with other operations
Cause: An attempt was made to combine drop column with other ALTER TABLE operations.
Action: Ensure that drop column is the sole operation specified in ALTER TABLE.
ORA-12988 cannot drop column from table owned by SYS
Cause: An attempt was made to drop a column from a system table.
Action: This action is not allowed.
ORA-12989 invalid value for checkpoint interval
Cause: An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1).
Action: Correct checkpoint interval and resubmit statement.
ORA-12990 duplicate option specified
Cause: Duplicate option specified in statement.
Action: Remove the duplicate option and resubmit statement.
ORA-12991 column is referenced in a multi-column constraint
Cause: An attempt was made to drop a column referenced by some constraints.
Action: Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement.
ORA-12992 cannot drop parent key column
Cause: An attempt was made to drop a parent key column.
Action: Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement.
ORA-12993 tablespace 'string' is offline, cannot drop column
Cause: An attempt was made to drop a column from a partition/subpartition on an offline tablespace.
Action: Bring the tablespace online and resubmit statement.
ORA-12994 drop column option only allowed once in statement
Cause: An attempt was made to repeat the drop column option in a single statement.
Action: Separate drop column options into different statements and resubmit statements.
ORA-12995 no columns in partially dropped state
Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns.
Action: Cannot submit this statement.
ORA-12996 cannot drop system-generated virtual column
Cause: An attempt was made to drop a virtual column generated by the system.
Action: This action is not allowed.
ORA-12997 cannot drop primary key column from an index-organized table
Cause: An attempt was made to drop a primary key column from an index- organized table.
Action: This action is not allowed.
ORA-13000 dimension number is out of range
Cause: The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.
Action: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.
ORA-13001 dimensions mismatch error
Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match.
Action: Make sure that the number of dimensions in the HHCODEs match.
ORA-13002 specified level is out of range
Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.
Action: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE.
ORA-13003 the specified range for a dimension is invalid
Cause: The specified range for a dimension is invalid.
Action: Make sure that the lower bound (lb) is less than the upper bound (ub).
ORA-13004 the specified buffer size is invalid
Cause: The buffer size for a function is not valid.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13005 recursive HHCODE function error
Cause: An error occurred in a recursively called HHCODE function.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13006 the specified cell number is invalid
Cause: The cell identifier is either less than 0 or greater than (2^ndim - 1).
Action: Make sure that the cell identifier is between 0 and (2^ndim - 1).
ORA-13007 an invalid HEX character was detected
Cause: A character that is not in the range [0-9] or [A-Fa-f] was detected.
Action: Verify that all characters in a string are in the range [0-9] or [A-Fa-f].
ORA-13008 the specified date format has an invalid component
Cause: Part of the specified date format is invalid.
Action: Verify that the date format is valid.
ORA-13009 the specified date string is invalid
Cause: The specified date string has a bad component or does not match the specified format string.
Action: Make sure that the components of the date string are valid and that the date and format strings match.
ORA-13010 an invalid number of arguments has been specified
Cause: An invalid number of arguments was specified for an SDO function.
Action: Verify the syntax of the function call.
ORA-13011 value is out of range
Cause: A specified dimension value is outside the range defined for that dimension.
Action: Make sure that all values to be encoded are within the defined dimension range.
ORA-13012 an invalid window type was specified
Cause: An invalid window type was specified.
Action: Valid window types are RANGE, PROXIMITY, POLYGON.
ORA-13013 the specified topology was not INTERIOR or BOUNDARY
Cause: A topology was specified that was not INTERIOR or BOUNDARY.
Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE's topology.
ORA-13014 a topology identifier outside the range of 1 to 8 was specified
Cause: A topology identifier outside the range of 1 to 8 was specified.
Action: Specify a topology in the range of 1 to 8.
ORA-13015 the window definition is not valid
Cause: The number of values used to define the window does not correspond to the window type.
Action: Verify that the number of values used to define the window is correct for the window type and number of dimensions.
ORA-13016 bad partition definition
Cause: The partition common code was not correctly decoded.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13017 unrecognized line partition shape
Cause: The shape of a 2-D line partition could not be determined.
Action: This is an internal error. Contact Oracle Support Services.
ORA-13018 bad distance type
Cause: The specified distance type is invalid.
Action: The only supported distance functions are EUCLID and MANHATTAN.
ORA-13019 coordinates out of bounds
Cause: Vertex coordinates lie outside the valid range for the specified dimension.
Action: Re-define vertex coordinates within specified boundaries.
ORA-13020 coordinate is NULL
Cause: A vertex coordinate has a NULL value.
Action: Re-define vertex coordinate to have a non-NULL value.
ORA-13021 element not continuous
Cause: The coordinates defining a geometric element are not connected.
Action: Re-define coordinates for the geometric element.
ORA-13022 polygon crosses itself
Cause: The coordinates defining a polygonal geometric element represent crossing segments.
Action: Re-define the coordinates for the polygon.
ORA-13023 interior element interacts with exterior element
Cause: An interior element of a geometric object interacts with the exterior element of that object.
Action: Re-define coordinates for the geometric elements.
ORA-13024 polygon has less than three segments
Cause: The coordinates defining a polygonal geometric element represent less than three segments.
Action: Re-define the coordinates for the polygon.
ORA-13025 polygon does not close
Cause: The coordinates defining a polygonal geometric element represent an open polygon.
Action: Re-define the coordinates of the polygon.
ORA-13026 unknown element type for element string.string.string
Cause: The SDO_ETYPE column in the layer_SDOGEOM table contains an invalid geometric element type value.
Action: Re-define the geometric element type in the layer_SDOGEOM table for the specified geometric element using one of the supported SDO_ETYPE values. See the Oracle Spatial User's Guide and Reference for an explanation of SDO_ETYPE and its possible values.
ORA-13027 unable to read dimension definition from string
Cause: There was a problem reading the dimension definition from the layer_SDODIM table.
Action: Verify that the layer_SDODIM table exists and that the appropriate privileges exist on the table. Address any other errors that might appear with the message.
ORA-13028 Invalid Gtype in the SDO_GEOMETRY object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid gtypes.
ORA-13029 Invalid SRID in the SDO_GEOMETRY object
Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range.
Action: Verify that the geometries have valid SRIDs.
ORA-13030 Invalid dimension for the SDO_GEOMETRY object
Cause: There is a mismatch between the dimension in the SDO_GTYPE and the dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.
Action: Verify that the geometries have valid dimensionality.
ORA-13031 Invalid Gtype in the SDO_GEOMETRY object for point object
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are NULL but the SDO_GTYPE is not of type POINT.
Action: Verify that the geometries have valid gtypes.
ORA-13032 Invalid NULL SDO_GEOMETRY object
Cause: There are invalid SDO_POINT_TYPE, SDO_ELEM_INFO_ARRAY, or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.
Action: Verify that the geometries have valid fields. To specify a NULL Geometry, specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL.
ORA-13033 Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. The triplets in this field do not make up a valid geometry.
Action: Verify that the geometries have valid data.
ORA-13034 Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the SDO_GEOMETRY object. The coordinates in this field do not make up a valid geometry. There may be NULL values for X, Y, or both.
Action: Verify that the geometries have valid data.
ORA-13035 Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates.
Action: Verify that the geometries have valid data.
ORA-13036 Operation [string] not supported for Point Data
Cause: The specified geometry function is not supported for Point data.
Action: Make sure that the specified geometry function is not called on point data.
ORA-13037 SRIDs do not match for the two geometries
Cause: A Spatial operation is invoked with two geometries where one geometry has an SRID and the other geometry does not have an SRID.
Action: Make sure that the spatial operations are invoked between two geometries with compatible SRIDs.
ORA-13039 failed to update spatial index for element string.string.string
Cause: Another error will accompany this message that will indicate the problem.
Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.
ORA-13040 failed to subdivide tile
Cause: This is an internal error.
Action: Note any accompanying errors and contact Oracle Support Services.
ORA-13041 failed to compare tile with element string.string.string
Cause: The spatial relationship between a generated tile and the specified element could not be determined.
Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any errors which accompany ORA-13041 and contact Oracle Support Services.
ORA-13042 invalid SDO_LEVEL and SDO_NUMTILES combination
Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the layer_SDOLAYER table. The most likely cause is that the columns are NULL.
Action: Verify that the SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial User's Guide and Reference. Retry the operation.
ORA-13043 failed to read meta data from the layer_SDOLAYER table
Cause: An error was encountered reading the layer meta data from the layer_SDOLAYER table.
Action: This error is usually the result of an earlier error which should also have been reported. Address this accompanying error and retry the current operation. If no accompanying error was reported, then contact Oracle Support Services.
ORA-13044 the specified tile size exceeds the maximum resolution
Cause: The tile size specified for fixed size tessellation exceeds the maximum resolution as computed from the layer meta data.
Action: See the Oracle Spatial User's Guide and Reference for an explanation of tiling levels, tile size, and tiling resolution. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. This can be achieved by using a fewer number of tiles per geometric object or specifying a lesser tile size value than the current one.
ORA-13045 invalid compatibility flag
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13046 invalid number of arguments
Cause: An invalid number of arguments was specified for an SDO_GEOM function.
Action: Refer to the Oracle Spatial User's Guide and Reference for a description of the syntax and semantics of the relevant SDO_GEOM function.
ORA-13047 unable to determine ordinate count from table layer_SDOLAYER
Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer layer.
Action: Verify that the layer_SDOLAYER table has a valid value for the column SDO_ORDCNT. Retry the operation.
ORA-13048 recursive SQL fetch error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13049 unable to determine tolerance value from table layer_SDODIM
Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer layer.
Action: Verify that the layer_SDODIM table has a valid value for the column SDO_TOLERANCE.
ORA-13050 unable to construct spatial object
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13051 failed to initialize spatial object
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13052 unsupported geometric type for geometry string.string
Cause: The geometry type for a specific instance in a layer_SDOGEOM table is not among the set of geometry types supported by the Oracle Spatial Cartridge.
Action: Check the Oracle Spatial User's Guide and Reference for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema.
ORA-13053 maximum number of geometric elements in argument list exceeded
Cause: The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded.
Action: Check the Oracle Spatial User's Guide and Reference for the syntax of the SDO_GEOM function and use fewer arguments to describe the geometry, or check the description of the SDO_WINDOW package for a workaround that permits storing the object in a table and then using it as an argument in a call to the SDO_GEOM function.
ORA-13054 recursive SQL parse error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13055 Oracle object string does not exist in specified table
Cause: The requested object is not present in the specified table.
Action: Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Retry the operation.
ORA-13108 spatial table string not found
Cause: The specified spatial table does not exist.
Action: Check the Spatial Data option data dictionary to make sure that the table is registered.
ORA-13109 spatial table string exists
Cause: The specified spatial table is registered in the Spatial Data option data dictionary.
Action: Remove the existing table from the Spatial Data option data dictionary or use a different name.
ORA-13110 spatial table string is not partitioned
Cause: The specified spatial table is not partitioned.
Action: Check the Spatial Data option data dictionary and make sure that a high water mark is set.
ORA-13111 spatial table string has no partition key defined
Cause: The specified spatial table does not have a partition key defined.
Action: Check the Spatial Data option data dictionary and make sure that the table is partitioned.
ORA-13112 invalid count mode string
Cause: The specified count mode is not valid.
Action: Alter the count mode. Valid count modes are ESTIMATE or EXACT.
ORA-13113 Oracle table string does not exist
Cause: The specified Oracle table does not exist.
Action: Check the Oracle7 data dictionary and make sure that the table exists.
ORA-13114 tablespace string not found
Cause: The specified tablespace does not exist.
Action: Check the Oracle7 data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it.
ORA-13115 tablespace string is already allocated
Cause: The specified tablespace is already allocated to the spatial table.
Action: Allocate another tablespace name to the table.
ORA-13116 tablespace string is not allocated to table string
Cause: The specified tablespace is not allocated to the specified spatial table.
Action: Allocate the tablespace to the spatial table.
ORA-13117 partition string not found
Cause: The specified partition does not exist.
Action: Verify the name of the partition by checking the Spatial Data option data dictionary.
ORA-13119 source and target tablespaces are identical
Cause: Identical source and target tablespaces were specified when trying to move partition.
Action: Specify different source and target tablespaces if you wish to move a partition.
ORA-13121 failed to create child partition
Cause: The creation of a child partition failed.
Action: Check for other errors that accompany this error and correct them first.
ORA-13122 child partition string not found
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13123 column string is already defined
Cause: The specified column is already defined for the spatial table.
Action: Use a different column name.
ORA-13124 unable to determine column id for column string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13125 partition key is already set
Cause: A partition key is already set for the spatial table.
Action: Only one partition key can be specified per spatial table.
ORA-13126 unable to determine class for spatial table string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13127 failed to generate target partition
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13128 current tiling level exceeds user specified tiling level
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13129 HHCODE column string not found
Cause: The specified spatial column does not exist.
Action: Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary.
ORA-13135 failed to alter spatial table
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13136 null common code generated
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13137 failed to generate tablespace sequence number
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13138 could not determine name of object string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13139 could not obtain column definition for string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13140 invalid target type
Cause: The specified target type is not valid.
Action: Substitute a valid target type. Valid target types are TABLE or VIEW.
ORA-13141 invalid RANGE window definition
Cause: The RANGE window specified is not correctly defined.
Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (for example, such as: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values.
ORA-13142 invalid PROXIMITY window definition
Cause: The PROXIMITY window specified is not correctly defined.
Action: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values.
ORA-13143 invalid POLYGON window definition
Cause: The POLYGON window specified is not correctly defined.
Action: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values.
ORA-13144 target table string not found
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13145 failed to generate range list
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13146 could not find table substitution variable string
Cause: The partition name substitution variable string was not found in the SQL filter.
Action: The substitution variable string must be in the SQL filter to indicate where that partition name should be placed.
ORA-13147 failed to generate MBR
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13148 failed to generate SQL filter
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13149 failed to generate next sequence number for spatial table string
Cause: This is an internal error.
Action: Document messages and contact Oracle Support Services.
ORA-13150 failed to insert exception record
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
ORA-13151 failed to remove exception record
Cause: Operation failed to insert a record into the exception table.
Action: Fix any other errors reported.
ORA-13152 invalid HHCODE type
Cause: The specified HHCODE type is not valid.
Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.
ORA-13153 invalid high water mark specified
Cause: The highwater mark must be greater than or equal to zero.
Action: Make sure that the highwater mark is an integer greater than or equal to zero.
ORA-13154 invalid precision specified
Cause: The precision specified is out of range.
Action: The precision must be an integer greater than or equal to zero.
ORA-13155 invalid number of dimensions specified
Cause: The number of dimensions specified is out of range.
Action: The number of dimensions must be between 1 and 32.
ORA-13156 table to be registered string.string is not empty
Cause: The specified table has rows in it.
Action: Make sure that the table to be registered is empty.
ORA-13157 Oracle error ORAstring encountered while string
Cause: The specified Oracle error was encountered.
Action: Correct the Oracle error.
ORA-13158 Oracle object string does not exist
Cause: The specified object does not exist.
Action: Verify that the specified object exists.
ORA-13159 Oracle table string already exists
Cause: The specified table already exists.
Action: Drop the specified table.
ORA-13181 unable to determine length of column string_SDOINDEX.SDO_CODE
Cause: The length of the SDO_CODE column in the layer_SDOINDEX table could not be determined.
Action: Make sure that the layer_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Retry the operation.
ORA-13182 failed to read element string.string.string
Cause: The specified element could not be read from the layer_SDOGEOM table.
Action: Verify that the specified element exists in the table. Retry the operation.
ORA-13183 unsupported geometric type for geometry string.string
Cause: The geometry type in the layer_SDOGEOM table is unsupported.
Action: Modify the geometry type to be one of the supported types.
ORA-13184 failed to initialize tessellation package
Cause: Initialization of the tessellation package failed.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13185 failed to generate initial HHCODE
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13186 fixed tile size tessellation failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13187 subdivision failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13188 cell decode failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13189 recursive SQL parse failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13190 recursive SQL fetch failed
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13191 failed to read SDO_ORDCNT value
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13192 failed to read number of element rows
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13193 failed to allocate space for geometry
Cause: There was insufficient memory to read the geometry from the database.
Action: Validate the geometry. Record the error messages that are returned and contact Oracle Support Services.
ORA-13194 failed to decode supercell
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13195 failed to generate maximum tile value
Cause: This is an internal error.
Action: Record the error messages that are returned and contact Oracle Support Services.
ORA-13196 failed to compute supercell for element string.string.string
Cause: The system was unable to compute the minimum bounding HHCODE or supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
ORA-13197 element string.string.string is out of range
Cause: Tessellation did not generate any tiles for this element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the layer_SDODIM table.
Action: Verify that the geometry is valid and within the defined domain.
ORA-13198 Spatial Cartridge error: string
Cause: Internal error in some Spatial Cartridge stored procedure.
Action: Record the sequence of procedure calls or events that preceeded this error and contact Oracle Support Services if the error message text does not clearly specify the cause of the error.
ORA-13199 string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-13200 internal error [string] in spatial indexing.
Cause: This is an internal error.
Action: Contact Oracle Support Services with the exact error text.
ORA-13201 invalid parameters supplied in CREATE INDEX statement
Cause: An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement.
Action: Check the Spatial Cartridge User Guide for the number, syntax, and semantics of expected parameters for spatial index creation.
ORA-13202 failed to create or insert into the SDO_INDEX_METADATA table
Cause: An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it.
Action: Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace.
ORA-13203 failed to read USER_SDO_GEOM_METADATA table
Cause: An error was encountered while trying to read USER_SDO_GEOM_METADATA table.
Action: Check that USER_SDO_GEOM_METADATA has an entry for the current geometry table.
ORA-13204 failed to create spatial index table
Cause: An error was encountered while trying to create the index table.
Action: Check that user has create table privilege in the current schema and that the user has sufficient quota in the default or specified tablespace.
ORA-13205 internal error while parsing spatial parameters
Cause: An internal error was encountered while parsing the spatial parameters.
Action: Check to make sure that the parameters passed in the parameter string are all valid.
ORA-13206 internal error [string] while creating the spatial index
Cause: An internal error was encountered while creating the spatial index.
Action: Contact Oracle Support Services with the exact error text.
ORA-13207 incorrect use of the [string] operator
Cause: An error was encountered while evaluating the specified operator.
Action: Check the parameters and the return type of the specified operator.
ORA-13208 internal error while evaluating [string] operator
Cause: An internal error was encountered.
Action: Contact Oracle Support Services with the exact error text.
ORA-13209 internal error while reading SDO_INDEX_METADATA table
Cause: An internal error was encountered while trying to read SDO_INDEX_METADATA table.
Action: Contact Oracle Support Services. Note this and accompanying error numbers.
ORA-13210 error inserting data into the index table
Cause: An error was encountered while trying to insert data into the index table. Likely causes are:
Insufficient quota in the current tablespace
User does not appropriate privileges
Action: Check the accompanying error messages.
ORA-13211 failed to tessellate the window object
Cause: An internal error was encountered while trying to tessellate the window object.
Action: Verify the geometric integrity of the window object using the VALIDATE_GEOMETRY procedure.
ORA-13212 failed to compare tile with the window object
Cause: The spatial relationship between a generated tile and the specified window object could not be determined.
Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any accompanying errors and contact Oracle Support Services.
ORA-13213 failed to generate spatial index for window object
Cause: Another error, indicating the real cause of the problem, should accompany this error.
Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.
ORA-13214 failed to compute supercell for window object
Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
ORA-13215 window object is out of range
Cause: Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the USER_SDO_GEOM_METADATA view.
Action: Verify that the geometry is valid and within the defined domain.
ORA-13216 failed to update spatial index
Cause: Another error will accompany this message that will indicate the problem.
Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.
ORA-13217 invalid parameters supplied in ALTER INDEX statement
Cause: An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement.
Action: Check the Oracle Spatial User's Guide and Reference for the number, syntax, and semantics of expected parameters for spatial alter index command.
ORA-13218 max number of supported index tables reached for [string] index
Cause: An add_index parameter is passed to ALTER INDEX when the number of existing index tables is already at maximum.
Action: Delete one of the index tables before adding another index table.
ORA-13219 failed to create spatial index table [string]
Cause: An error was encountered while trying to create the index table.
Action: There is a table in the index's schema with the specified name. The create index will try to create an index table with this name. Either rename this table or change the name of the index.
ORA-13220 failed to compare tile with the geometry
Cause: The spatial relationship between a generated tile and the specified geometry could not be determined.
Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any errors which accompany ORA-13220 and contact Oracle Support Services.
ORA-13221 unknown geometry type in the geometry object
Cause: The SDO_GTYPE attribute in the geometry object contains an invalid value.
Action: Re-define the geometric type in the geometry table using one of the supported SDO_GTYPE values. See the Oracle Spatial User's Guide and Reference for an explanation of SDO_GTYPE and its possible values.
ORA-13222 failed to compute supercell for geometry in string
Cause: The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table.
Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.
ORA-13223 duplicate entry for string in SDO_GEOM_METADATA table
Cause: There are duplicate entries for the given table and column value pair in the SDO_GEOM_METADATA table
Action: Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the SDO_GEOME_METADATA table.
ORA-13224 specified index name is too long for a spatial index
Cause: An index name was specified which is longer than the supported length of the spatial index name.
Action: Check the supported size of the index name and reduce the size of the index name.
ORA-13225 specified index table name is too long for a spatial index
Cause: An index table name was specified which is longer than the supported length of the spatial index table name.
Action: Check the supported size of the index table name and reduce the size of the index name.
ORA-13226 interface not supported without a spatial index
Cause: The geometry table does not have a spatial index.
Action: Verify that the geometry table referenced in the spatial operator has a spatial index on it.
ORA-13227 SDO_LEVEL values for the two index tables do not match
Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match.
Action: Verify that two compatible indexes are used for the spatial join operator. Indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values.
ORA-13228 Spatial index create failed due to invalid type
Cause: An Attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY.
Action: Make sure that the index is created on a column of type SDO_GEOMETRY.
ORA-13230 failed to create temporary table [string] during R-tree creation
Cause: The specified temporary table either already exists or there is not enough tablespace.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.
ORA-13231 failed to create index table [string] during R-tree creation
Cause: The specified index table either already exists or there is not enough tablespace. Otherwise, contact Oracle Support Services.
Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.
ORA-13232 failed to allocate memory during R-tree creation
Cause: This feature assumes a minimum of 64 KB memory for bulk creation.
Action: Create the index for a small subset of the data. Then, use transactional inserts for the rest.
ORA-13233 failed to create sequence number [string] for R-tree
Cause: The specified sequence number exists.
Action: Delete the sequence object or contact Oracle Support Services.
ORA-13234 failed to access R-tree-index table [string]
Cause: The index table is either deleted or corrupted.
Action: Rebuild the index or contact Oracle Support Services with accompanying error messages.
ORA-13236 internal error in R-tree processing: [string]
Cause: An internal error occurred in R-tree processing.
Action: Contact Oracle Support Services with message text.
ORA-13237 internal error during R-tree concurrent updates: [string]
Cause: An inconsistency was encountered during concurrent updates possibly due to the use of serializable isolation level.
Action: Change the isolation level to "read committed" using alter session or contact Oracle Support Services with the message text.
ORA-13239 sdo_dimensionality not specified during n-d R-tree creation
Cause: An error occurred in reading the dimensionality parameter.
Action: Check the documentation for a valid range and specify the dimensionality as a parameter.
ORA-13240 specified dimensionality greater than that of the query mbr
Cause: An error occurred because of too few values in query mbr.
Action: Omit the dimensionality or use the dimensionality of the query.
ORA-13241 specified dimensionality does not match that of the data
Cause: An error occurred because the dimensionality specified in the CREATE INDEX does not match that of the data.
Action: Change it to the data dimensionality.
ORA-13242 failed to read tolerance values for n-d R-tree
Cause: An error occurred in reading the information for the specified table and column in USER_SDO_GEOM_METADATA table.
Action: Insert appropriate row specifying the tolerance.
ORA-13243 specified operator is not supported for n-d R-tree: [string]
Cause: Currently, an n-d R-tree only supports sdo_filter operator.
Action: Check the documentation for querytype parameters for sdo_filter or contact Oracle Support Services.
ORA-13249 string
Cause: An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component.
Action: Contact Oracle Support Services with the exact error text.
ORA-13250 insufficient privileges to modify metadata table entries
Cause: The user requesting the operation does not have the appropriate privileges on the referenced tables.
Action: Check that the specified feature and geometry table names are correct and then verify that the current user has at least SELECT privilege on those tables.
ORA-13251 duplicate entry string in metadata table
Cause: The specified entry already exists in the metadata table.
Action: Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once.
ORA-13260 layer table string does not exist
Cause: Data migration source table layer_SDOGEOM does not exist.
Action: Ensure that the specified layername is correct and that the corresponding spatial layer tables exist in the current schema.
ORA-13261 geometry table string does not exist
Cause: The specified geometry table does not exist in the current schema.
Action: Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values.
ORA-13262 geometry column string does not exist in table string
Cause: The specified table does not have a column of type SDO_GEOMETRY.
Action: Alter or recreate the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER.
ORA-13263 column string in table string is not of type SDO_GEOMETRY
Cause: The column intended for storing the geometry is not of type SDO_GEOMETRY.
Action: Alter the column definition to be of type SDO_GEOMETRY.
ORA-13264 geometry identifier column string does not exist in table string
Cause: The specified table does not contain a GID column.
Action: Confirm that the GID columnname was correctly specified and that it exists in the specified table.
ORA-13265 geometry identifier column string in table string is not of type NUMBER.
Cause: GID column is not of type NUMBER.
Action: Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER.
ORA-13266 error inserting data into table string
Cause: An OCI error occurred or the user has insufficient quota in the active tablespace or the rollback segments are too small.
Action: There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem.
ORA-13267 error reading data from layer table string
Cause: There was an error reading the geometry data from the layer_SDOGEOM table.
Action: Verify that layer_SDOGEOM and layer_SDODIM exist. If they do exist, then run VALIDATE_GEOMETRY on the specified layer.
ORA-13268 error obtaining dimension from USER_SDO_GEOM_METADATA
Cause: There is no entry in USER_SDO_GEOM_METADATA for the specified geometry table.
Action: Insert an entry for the destination geometry table with the dimension information obtained from the source layer_SDODIM table.
ORA-13269 internal error [string] encountered when processing geometry table
Cause: An internal error occurred.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13270 OCI error string
Cause: An OCI error occurred while processing the layer or geometry tables.
Action: Take the appropriate steps to correct the OCI specific error.
ORA-13271 error allocating memory for geometry object
Cause: Insufficient memory.
Action: Make more memory available to the current session/process.
ORA-13272 geometric object string in table string is invalid
Cause: The specified object failed the geometric integrity checks performed by VALIDATE_GEOMETRY.
Action: Consult the Oracle Spatial User's Guide and Reference for information on the geometric integrity checks performed by VALIDATE_GEOMETRY and correct the geometry definition if required.
ORA-13273 dimension metadata table string does not exist
Cause: The layer_SDODIM table does not exist.
Action: Verify that the specified layer name is correct and that the layer_SDODIM table exists in the current schema.
ORA-13274 Operator invoked with non compatible SRIDs
Cause: A Spatial operator was invoked with a window geometry with an SRID and the layer without an SRID or window has no SRID and the layer has an SRID.
Action: Make sure that the layer and window both have an SRID or they both do not have an SRID.
ORA-13275 Spatial index creation failure on unsupported type
Cause: A spatial index create was invoked on a column that is not of type SDO_GEOMETRY.
Action: Spatial index can only be created on a column of type SDO_GEOMETRY. Make sure the indexed column has SDO_GEOMETRY type.
ORA-13276 internal error [string] in coordinate transformation
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13278 failure to convert SRID to native format
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13281 failure in execution of sql statement to retrieve WKT
Cause: OCI internal error or SRID does not match a table entry.
Action: Check that a valid SRID is being used.
ORA-13282 failure on initialization of coordinate transformation
Cause: Parsing error on source or destination coordinate system WKT or incompatible coordinate systems.
Action: Check validity of WKT for table entries and the legitimacy of the requested transformation.
ORA-13283 failure to get new geometry object for conversion in place
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13284 failure to copy geometry object for conversion in place
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13285 Geometry coordinate transformation error
Cause: A coordinate pair was out of valid range for a conversion/projection.
Action: Check that data to be transformed is consistent with the desired conversion/projection.
ORA-13287 can't transform unknown gtype
Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed.
Action:
ORA-13288 Point coordinate transformation error
Cause: An internal error while transforming points.
Action: Check the accompanying error messages.
ORA-13290 The specified unit is not supported
Cause: Spatial function called with an unknown UNIT.
Action: Check the supported units by Spatial and call the spatial function with the correct UNIT parameter.
ORA-13291 Conversion error between the specified unit and standard unit
Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.
Action: Check unit specification and respecify it.
ORA-13292 Incorrect ARC_TOLERANCE specification
Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a Geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be specified and it should not be less than the tolerance specified for the geometry.
Action: Check ARC_TOLERANCE specification and make sure it is correct.
ORA-13293 Cannot specify unit for geometry without a georeferenced SRID
Cause: A Spatial function with unit parameter is called on a geometry without a georeferenced SRID.
Action: Make sure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs.
ORA-13294 Cannot transform geometry containing circular arcs
Cause: It is impossible to transform a 3-point representation of a circular arc without distortion.
Action: Make sure a geometry does not contain circular arcs.
ORA-13295 Geometry objects are in different coordinate systems
Cause: A Spatial function is called with two geometries with two different SRIDs.
Action: Transform geometry objects to be in the same coordinate system and call the spatial function.
ORA-13296 Incorrect Coordinate System Specification
Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID.
Action: Check WKT in CS_SRS table for Earth radius and inverse flattening.
ORA-13300 Single point transform error
Cause: Low level coordinate transformation error trap.
Action: Check the accompanying error messages.
ORA-13303 failure to retrieve a geometry object from a table
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13304 failure to insert a transformed geometry object in a table
Cause: OCI internal error.
Action: Contact Oracle Support Services with the exact error message text.
ORA-13330 invalid MASK
Cause: The MASK you passed to RELATE function is not valid.
Action: Verify that the mask is not NULL. See the Oracle Spatial User's Guide and Reference for a list of supported masks.
ORA-13331 invalid LRS segment
Cause: The given LRS segment was not a valid linestring.
Action: A valid LRS geometric segment is a line string geometry in Oracle Spatial. It could be a simple or compound line string (made of lines or arcs, or both). The dimension information must include the measure dimension as the last element in Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or latitude/longitude plus measure).
ORA-13332 invalid LRS point
Cause: Given LRS point was not a point-geometry with measure information.
Action: Check the given point geometry.A valid LRS point is a point geometry in Oracle Spatial with additional measure dimension.
ORA-13333 invalid LRS measure
Cause: The given measure for linear referencing was out of range.
Action: Re-define the given measure.
ORA-13334 LRS segments not connected
Cause: The given geometric segments were not connected.
Action: Check the start/end points of the given geometric segments.
ORA-13335 LRS measure information not defined
Cause: The measure information of a given geometric segments was not assigned (IS NULL).
Action: Assign/define the measure information. An LRS geometric segment is defined if its start and end measure are assigned (non-null).
ORA-13336 Failure in converting standard diminfo/geometry to LRS dim/geom
Cause: No room for measure dimension in the given diminfo or the given standard geometry is not a point a linestring.
Action: Check if the diminfo dimensions are less than 3 or given geometry type is point or linestring.
ORA-13337 failure in concatenating LRS polygons
Cause: LRS concatenation involving LRS polygons is not supported.
Action: Check geometry and element type to make sure the concatenate operation is not called with a polygon type.
ORA-13338 failure in reversing LRS polygon/collection geometry
Cause: Reversing an LRS polygon/collection geometry produces an invalid geometry as this operation is not well defined for polygon geometry.
Action: Check the geometry type to make sure this operation is called on non polygon type geometry.
ORA-13339 LRS Polygon clipping across multiple rings
Cause: Clipping (dynseg) a polygon across multiple rings.
Action: Polygon clipping only allowed for a single ring.
ORA-13340 a point geometry has more than one coordinate
Cause: A geometry, specified as being a point, has more than one coordinate in its definition.
Action: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, then set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, then remove the extraneous coordinates from its definition.
ORA-13341 a line geometry has less than two coordinates
Cause: A geometry, specified as being a line, has less than two coordinates in its definition.
Action: A line must consist of at least two distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13342 an arc geometry has less than three coordinates
Cause: A geometry, specified as being an arc, has less than three coordinates in its definition.
Action: An arc must consist of at least three distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13343 a polygon geometry has less than four coordinates
Cause: A geometry, specified as being a polygon, has less than four coordinates in its definition.
Action: A polygon must consist of at least four distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13344 an arcpolygon geometry has less than five coordinates
Cause: A geometry, specified as being an arcpolygon, has less than six coordinates in its definition.
Action: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected, the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13345 a compound polygon geometry has less than five coordinates
Cause: A geometry, specified as being a compound polygon, has less than five coordinates in its definition.
Action: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line, each of which must be described using three and at least two distinct coordinates, respectively. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.
ORA-13346 the coordinates defining an arc are collinear
Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates.
Action: Alter the definition or the arc or set the SDO_ETYPE or SDO_GTYPE to the line type.
ORA-13347 the coordinates defining an arc are not distinct
Cause: Two or more of the three points defining an arc are the same.
Action: Alter the definition of the arc, ensuring that three distinct coordinate values are used.
ORA-13348 polygon boundary is not closed
Cause: The boundary of a polygon does not close.
Action: Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry.
ORA-13349 polygon boundary crosses itself
Cause: The boundary of a polygon intersects itself.
Action: Correct the geometric definition of the object.
ORA-13350 two or more rings of a complex polygon touch
Cause: The inner or outer rings of a complex polygon touch.
Action: All rings of a complex polygon must be disjoint. Correct the geometric description of the object.
ORA-13351 two or more rings of a complex polygon overlap
Cause: The inner or outer rings of a complex polygon overlap.
Action: All rings of a complex polygon must be disjoint. Correct the geometric description of the object.
ORA-13352 the coordinates do not describe a circle
Cause: The set of coordinates used to describe a circle are incorrect.
Action: Confirm that the set of coordinates actually represent points on the circumference of a circle.
ORA-13353 ELEM_INFO_ARRAY not grouped in threes
Cause: The ELEM_INFO_ARRAY in SDO_GEOMETRY has more or fewer elements than expected.
Action: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3.
ORA-13354 incorrect offset in ELEM_INFO_ARRAY
Cause: The offset field in ELEM_INFO_ARRAY of SDO_GEOMETRY references an invalid array subscript in SDO_ORDINATE_ARRAY.
Action: Confirm that the offset is a valid array subscript in SDO_ORDINATE_ARRAY.
ORA-13355 SDO_ORDINATE_ARRAY not grouped by number of dimensions specified
Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user.
Action: Confirm that the number of dimensions is consistent with data representation in SDO_ORDINATE_ARRAY.
ORA-13356 adjacent points in a geometry are redundant
Cause: There are repeated points in the sequence of coordinates.
Action: Remove the redundant point.
ORA-13357 extent type does not contain 2 points
Cause: Extent type should be represented by 2 points: lower left and upper right.
Action: Confirm that there are only 2 points for extent type.
ORA-13358 circle type does not contain 3 points
Cause: Circle type should be represented by 3 distinct points on the circumference.
Action: Confirm that there are only 3 points for circle type.
ORA-13359 extent does not have an area
Cause: The 2 points representing the extent are identical.
Action: Confirm that the 2 points describing the extent type are distinct.
ORA-13360 invalid subtype in a compound type
Cause: This subtype is not allowed within the ETYPE specified.
Action: Refer to Oracle Spatial User's Guide and Reference for type definitions.
ORA-13361 not enough sub-elements within a compound ETYPE
Cause: The compound type declare more sub-elements than actually defined.
Action: Confirm that the number of sub-elements is consistent with the compound type declaration.
ORA-13362 disjoint sub-element in a compound polygon
Cause: Compound polygon must describe an enclosed area.
Action: Confirm that all sub-elements are connected.
ORA-13363 no valid ETYPE in the geometry
Cause: None of the ETYPEs within the geometry is supported.
Action: Confirm that there is at least one valid ETYPE.
ORA-13364 Layer Dimensionality does not match geometry dimensions
Cause: Spatial layer has a geometry with a different dimensions than the dimensions specified for the layer.
Action: Make sure that all geometries in a layer have the same dimensions and they match the dimensions in the SDO_DIM_ARRAY object for the layer in USER_SDO_GEOM_METADATA.
ORA-13365 Layer SRID does not match geometry SRID
Cause: Spatial layer has a geometry with a different SRID than the SRID specified for the layer.
Action: Make sure that all geometries in a layer have the same SRID and the SRIDs match the SRID in USER_SDO_GEOM_METADATA for the layer.
ORA-13366 Invalid combination of interior exterior rings
Cause: In the Spatial geometry, interior and exterior rings are not used consistently.
Action: Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array.
ORA-13367 Wrong orientation for interior/exterior rings
Cause: In a spatial geometry, the exterior and/or interior rings are not oriented correctly.
Action: The exterior rings should be oriented counter clock-wise and interior rings should be oriented clock wise.
ORA-13368 Simple Polygon type has more than one exterior ring
Cause: In a polygon type geometry, there is more than one exterior ring.
Action: Set the type to be multi-polygon if more than one exterior is present in the geometry.
ORA-13369 Invalid value for etype in the 4 digit format
Cause: A 4 digit etype for non polygon type element is used or the orientation is not a valid orientation for interior/exterior rings of the polygon.
ORA-13370 failure in applying 3D LRS functions
Cause: Only Non-geodetic 3D linestring geometry (made of line segments) are supported for 3D LRS package.
Action: Check the geometry and element types and SRID.
ORA-13371 invalid position of measure dimension
Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in dim_info_array.
Action: Check geometry gtype and its dim_info_array.
ORA-13372 failure in modifying metadata for a table with spatial index
Cause: Modifying the metadata after the index is created will cause inconsistency between geometry gtype and diminfo.
Action: Modify(or Prepare) metadata before creating index on sdo_geometry column.
ORA-13373 Element of type Extent is not supported for Geodetic data
Cause: Element type extent for a polygon geometry is not supported for geodetic data.
Action: Convert the extent type polygon to a regular 5 point polygon and set etype accordingly.
ORA-13374 SDO_MBR not supported for geodetic data
Cause: The SDO_MBR functionality is not supported for geodetic data.
Action: Find an alternative function that can be used in this context.
ORA-13375 The layer is of type [string] while geometry inserted has type [string]
Cause: The layer has a type that is different or inconsistent with the type of the current geometry.
Action: Change the geometry type to agree with the layer type or change the layer type to agree with the geometry type.
ORA-13376 Invalid type name specified for layer_gtype parameter
Cause: An invalid type name is specified for the layer gtype constraint.
Action: Consult the Oracle Spatial User's Guide and Reference to get a list of valid layer gtypes that can be used in defining a layer gtype constraint.
ORA-13377 Invalid combination of elements with orientation
Cause: An element of the geometry has orientation specified while some other element has no orientation specified (4 digit etype).
Action: Make sure all the polygon elements have orientation specified using the 4 digit etype notation.
ORA-13378 Invalid index for element to be extracted
Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the given geometry.
ORA-13379 Invalid index for sub-element to be extracted
Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.
Action: Make sure the parameters to the extract function are in the valid range for the given geometry.
ORA-13400 Oracle GeoImage internal error, arguments: [string], [string], [string], [string], [string]
Cause: This is an internal Oracle GeoImage error.
Action: Contact Oracle Support Services.
ORA-13401 unsupported geoimage format
Cause: The GeoImage format is not supported.
Action: Confirm that the GeoImage format is valid and supported.
ORA-13402 NULL destination
Cause: The object specified as the destination is NULL.
Action: Confirm that the object specified as the destination is not NULL.
ORA-13403 NULL source geometry
Cause: The source GeoImage has a NULL geometry.
Action: Verify that the geometry of the source GeoImage is not NULL.
ORA-13404 not a local source
Cause: An attempt has been made to modify a GeoImage which is not stored in the database.
Action: Import the GeoImage in order to modify it.
ORA-13405 NULL source
Cause: The object specified as the source is NULL.
Action: Confirm that the object specified as the source is not NULL.
ORA-13406 unsupported image processing command [string]
Cause: The image processing command specified is not supported for a GeoImage.
Action: Consult the Oracle interMedia User's Guide and Reference to verify which image processing commands are supported within an Oracle GeoImage method.
ORA-13407 unrecognized space type qualifier [string]
Cause: The GeoImage space type qualifier is invalid.
Action: Use a valid space type qualifier (RASTER or MODEL).
ORA-13408 NULL table name
Cause: The table name parameter is NULL.
Action: Verify that the parameter used for the table name is not NULL.
ORA-13409 Oracle table "string" does not exist.
Cause: The table specified does not exist.
Action: Verify that the table name used is valid and the table exists.
ORA-13410 NULL column name
Cause: The column name parameter is NULL.
Action: Verify that the parameter used for the column name is not NULL.
ORA-13411 Oracle column "string" does not exist.
Cause: The column specified does not exist.
Action: Verify that the column name used is valid and the column exists.
ORA-13412 invalid ROWID
Cause: The ROWID value used is not valid.
Action: Verify that the ROWID value used is valid.
ORA-13413 could not select the GeoImage for initialization
Cause: The GeoImage in the table could not be selected.
Action: Verify that the GeoIMage is present in the table and the supplied parameters are valid.
ORA-13414 could not update the table containing the GeoImage
Cause: The table containing the GeoImage could not be updated.
Action: Verify that the table exists and is valid.
ORA-13415 invalid domain
Cause: The SDO_DIMINFO value used is not valid or the SDO_GEOMETRY supplied is not defined in the domain.
Action: Verify that the SDO_DIMINFO value is valid, and that the SDO_GEOMETRY is defined within the domain specified.
ORA-13416 invalid geometry, arguments [string]
Cause: The SDO_GEOMETRY value used is not valid.
Action: Verify that the SDO_GEOMETRY is valid. Consult the Oracle Spatial User's Guide and Reference for a list of valid geometries.
ORA-13417 undefined raster to model space transformation
Cause: The raster to model space transformation associated with a GeoImage is undefined.
Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format.
ORA-13418 undefined model to raster space transformation
Cause: The model to raster space transformation associated with a GeoImage is undefined.
Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format.
ORA-13419 invalid latitude value
Cause: A latitude value outside the valid range [-90,90] has been used.
Action: Verify that the GeoImage geometry definition is within the domain.
ORA-13420 invalid model to raster space transformation
Cause: The model to raster space transformation associated with a GeoImage is not valid or cannot be calculated.
Action: Verify that the transformation is supported and that the GeoImage format is valid.
ORA-13421 invalid raster to model space transformation
Cause: The raster to model space transformation associated with a GeoImage is not valid or cannot be calculated.
Action: Verify that the transformation is supported and that the GeoImage format is valid.
ORA-13422 uninitialized source
Cause: The LOB used for the source is not initialized.
Action: Verify that the source is properly initialized.
ORA-13423 empty source
Cause: The LOB used for the source is empty.
Action: Verify that the source is properly initialized and data has been imported into it.
ORA-13424 uninitialized destination
Cause: The LOB used for the destination is not initialized.
Action: Verify that the destination is properly initialized.
ORA-13425 empty destination
Cause: The LOB used for the destination is empty.
Action: Verify that the destination is properly initialized and data has been imported into it.
ORA-13426 unsupported raster origin
Cause: The raster origin specified is not supported.
Action: Verify that the origin specified is supported.
ORA-13427 unknown raster origin
Cause: The value specified for the raster origin is invalid.
Action: Verify that the value used to specify the raster origin is valid and supported.
ORA-13428 source does not exist
Cause: The source does not exist or cannot be accessed.
Action: Verify that the source specification is correct and accessible.
ORA-13429 operation "string" not supported on GeoImage type "string"
Cause: The specified operation is not supported on the particular geoimage type.
Action: Verify that the operation is supported.
ORA-13430 model coordinate system not supported
Cause: The model specified for the definition of the coordinate system is not supported.
Action: Verify that the model value is correct.
ORA-13433 NULL crop geometry
Cause: The geometry used to crop a GeoImage is NULL.
Action: Verify that the geometry used for the crop operation is not NULL.
ORA-13442 invalid scaling parameters [string] [string]
Cause: The parameters used in the scale operation are invalid.
Action: Verify that the scaling parameters are greater than zero.
ORA-13443 unrecognized scale mode [string]
Cause: The scale mode used in the scale operation is invalid.
Action: Consult the Oracle interMedia User's Guide and Reference for a list of valid scale mode qualifiers.
ORA-13451 unsupported conversion format [string]
Cause: The format specified for conversion is invalid or unsupported.
Action: Verify that the conversion format specified is valid.
ORA-13461 invalid tag/key [string]
Cause: The tag or key is invalid.
Action: Verify that the format version is supported or the format is valid.
ORA-13462 invalid tie point
Cause: One of the tie points is invalid.
Action: Verify that the tie points used are valid (for example all raster tie points are >= 0).
ORA-13463 unsupported GeoTIFF geometry definition
Cause: The combination of keys/tags used to define the geometry footprint of the GeoImage is not supported.
Action: Verify that the GeoTIFF format version is supported and the format is valid.
ORA-13464 unsupported conversion
Cause: The format specified for conversion is not supported. In GeoTIFF, only a limited number of tags/keys combinations are supported for conversion.
Action: Verify that the GeoTIFF format version is supported and conversion to the desired format is available.
ORA-13465 invalid destination window
Cause: The window specified as destination in the command is not valid.
Action: Verify that the window definition is correct.
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 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 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 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 missing PARTITION keyword
Cause: Keyword PARTITION missing.
Action: Supply missing keyword.
ORA-14005 missing RANGE keyword
Cause: Keyword RANGE missing.
Action: Supply missing keyword.
ORA-14006 invalid partition name
Cause: A partition name of the form identifier is expected but not present.
Action: Enter an appropriate partition name.
ORA-14007 missing LESS keyword
Cause: Keyword LESS missing.
Action: Supply missing keyword.
ORA-14008 missing THAN keyword
Cause: Keyword THAN missing.
Action: Supply missing keyword.
Skip Headers
Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01
Go To Documentation Library
Home Go To Product List
Book List Go To Table Of Contents
Contents Go To Index
Index
Master Index
Feedback
Go to previous page Go to next page
13
ORA-24280 to ORA-29249
ORA-24280 invalid input value for parameter string
Cause: The parameter has been provided a negative, out of range, or NULL input value.
Action: Correct the input value such that it is valid, and is within the range as specified in the documentation.
ORA-24281 invalid access past the maximum size of LOB parameter string
Cause: The value of positional or size parameters exceeds the maximum allowed LOB size of 4 Gigabytes.
Action: Correct the input values for amount and offset such that their sum is less than or equal to 4 Gigabytes. If error occurs in a read or write loop, check the looping conditions and/or offset increments.
ORA-24300 bad value for mode
Cause: An undefined mode value was specified.
Action: Check that the correct mode is selected and that an allowed value for that mode is specified.
ORA-24301 null host specified in thread-safe logon
Cause: An HDA was not specified in the logon call while running in a thread safe environment.
Action: Make sure that HDA is not NULL when calling the logon routine.
ORA-24302 host connection in use by another thread
Cause: An attempt was made to use the host connection while it was in use by another thread.
Action: Wait for another thread to finish before using this connection.
ORA-24303 call not supported in non-deferred linkage
Cause: One of the calls that is supported in deferred mode linkage exclusively was invoked when the client was linked non-deferred.
Action: Use this call in deferred mode of linkage.
ORA-24304 datatype not allowed for this call
Cause: Data of this datatype cannot be sent or fetched in pieces.
Action: Use other bind or define calls for this datatype.
ORA-24305 bad bind or define context
Cause: The call was executed on a cursor for which this is invalid.
Action: Verify that this call is valid for this cursor. For example, Get piece information and set piece information are valid on a cursor if appropriate binds and defines have been done on this cursor.
ORA-24306 bad buffer for piece
Cause: A zero length buffer or a null buffer pointer was provided.
Action: Verify that the buffer pointing to this piece or its length is non-zero. The buffer pointer for the next piece or its length can be zero if it is the last piece to be inserted and there are no more data for the column.
ORA-24307 invalid length for piece
Cause: The length of the piece exceeded the maximum possible size.
Action: Verify that the length of this piece and the cumulative length of all the previous pieces is not more than the desired value supplied by the application.
ORA-24308 illegal define position
Cause: Call to modify attributes was done for a non-existent position.
Action: Verify that a define has been done for this position.
ORA-24309 already connected to a server
Cause: This server handle is already attached to a server.
Action: Disconnect from the server and then retry the call to establish a connection.
ORA-24310 length specified for null connect string
Cause: The connect string is null, but a length was specified for it.
Action: Set length to zero if connect string is null.
ORA-24311 memory initialization failed
Cause: Cannot initialize user memory.
Action: Contact Oracle Support Services.
ORA-24312 illegal parameters specified for allocating user memory
Cause: An illegal size or null pointer was specified for user memory.
Action: Specify a legal size and a valid pointer for user memory.
ORA-24313 user already authenticated
Cause: A user has already been authenticated on this service handle.
Action: Terminate the service context before using it for another user.
ORA-24314 service handle not initialized
Cause: The server context does not done exist.
Action: Establish the server context in the service context.
ORA-24315 illegal attribute type
Cause: An illegal attribute type was specified for the handle.
Action: Consult the Oracle Call Interface Programmer's Guide to specify an attribute valid for this handle.
ORA-24316 illegal handle type
Cause: An illegal handle type was specified.
Action: Consult the Oracle Call Interface Programmer's Guide to specify a valid handle type.
ORA-24317 define handle used in a different position
Cause: A define was done with an existing handle on a different position.
Action: Specify the same position as before on a redefine.
ORA-24318 call not allowed for scalar data types
Cause: This call is valid only for object types.
Action: Verify that the data-type for this variable is an object type.
ORA-24319 unable to allocate memory
Cause: Process was unable to allocate memory to store diagnostics.
Action: Terminate other processes in order to reclaim needed memory.
ORA-24320 unable to initialize a mutex
Cause: An attempt to initialize a MUTEX failed.
Action: Contact Oracle Support Services.
ORA-24321 inconsistent parameters passed
Cause: One of the three memory function pointers is null or non-null.
Action: Verify that either all the memory functions are null or non-null.
ORA-24322 unable to delete an initialized mutex
Cause: An attempt to delete an initialized MUTEX failed.
Action: Contact Oracle Support Services.
ORA-24323 value not allowed
Cause: A null or invalid value was passed in for a mandatory parameter.
Action: Verify that all mandatory parameters are properly initialized.
ORA-24324 service handle not initialized
Cause: An attempt was made to use an improper service context handle.
Action: Verify that the service context handle has all the parameters initialized prior to this call.
ORA-24325 this OCI operation is not currently allowed
Cause: An attempt was made to use a context handle outside its scope.
Action: Verify that the context handle is set to a service context handle that has been converted to a logon data area for other OCI calls. The logon data area must be converted back to a service context before it can be used.
ORA-24326 handle passed in is already initialized
Cause: An attempt was made to pass an initialized handle.
Action: Verify that the parameter passed in to retrieve a handle does not already point to a handle.
ORA-24327 need explicit attach before authenticating a user
Cause: A server context must be initialized before creating a session.
Action: Create and initialize a server handle.
ORA-24328 illegal attribute value
Cause: The attribute value passed in is illegal.
Action: Consult the Oracle Call Interface Programmer's Guide and specify a legal attribute value for the handle.
ORA-24329 invalid character set identifier
Cause: The character set identifier specified is invalid.
Action: Specify a valid character set identifier in the OCI call.
ORA-24330 internal OCI error
Cause: An internal OCI error has occurred.
Action: Contact Oracle Support Services.
ORA-24331 user buffer too small
Cause: The user buffer to contain the output data is too small.
Action: Specify a bigger buffer.
ORA-24332 invalid object type
Cause: An invalid object type is requested for the describe call.
Action: Specify a valid object type to the describe call.
ORA-24333 zero iteration count
Cause: An iteration count of zero was specified for the statement.
Action: Specify the number of times this statement must be executed.
ORA-24334 no descriptor for this position
Cause: The application is trying to get a descriptor from a handle for an illegal position.
Action: Check the position number.
ORA-24335 cannot support more than 1000 columns
Cause: The number of columns exceeds the maximum number supported.
Action: Specify a number of columns less than 1000.
ORA-24336 invalid result set descriptor
Cause: The result set descriptor should have valid data fetched into it before it can be converted to a statement handle.
Action: Fetch valid data into the descriptor before attempting to convert it into a statement handle.
ORA-24337 statement handle not prepared
Cause: A statement cannot be executed before making preparing a request.
Action: Prepare a statement before attempting to execute it.
ORA-24338 statement handle not executed
Cause: A fetch or describe was attempted before executing a statement handle.
Action: Execute a statement and then fetch or describe the data.
ORA-24339 cannot set server group name after connecting to server
Cause: An attempt was made to set the server group in a server handle after connecting to the server. However, once the connection is established to a server, the server group name cannot be set anymore.
Action: Attach to the server after setting the server group name in the server handle.
ORA-24340 cannot support more than 255 columns
Cause: The number of columns exceeds maximum supported by the server.
Action: Limit your operation to 255 columns.
ORA-24341 bad mode specified
Cause: OCI_ENV_NO_MUTEX mode was specified for a non-threaded client.
Action: OCI_ENV_NO_MUTEX may be specified when OCI_THREADED had been specified at process initialization.
ORA-24342 unable to destroy a mutex
Cause: An attempt to destroy a MUTEX failed.
Action: Contact Oracle Support Services.
ORA-24343 user defined callback error
Cause: The only valid return value for a user defined callback function is OCI_CONTINUE. Any other value will cause this error.
Action: Make sure that OCI_CONTINUE is returned from the user-defined callback function.
ORA-24344 success with compilation error
Cause: A SQL or PL/SQL compilation error occurred.
Action: Return OCI_SUCCESS_WITH_INFO along with the error code.
ORA-24345 A Truncation or null fetch error occurred
Cause: A truncation or a null fetch error.
Action: Make sure that the buffer size is long enough to store the returned data.
ORA-24346 cannot execute without binding variables
Cause: None of the bind variables in the SQL statement are bound.
Action: Bind all the variables before the execute is done.
ORA-24347 Warning of a NULL column in an aggregate function
Cause: A null column was processed by an aggregate function.
Action: An OCI_SUCCESS_WITH_INFO is returned.
ORA-24348 Update or Delete without Where
Cause: An UPDATE or DELETE was executed without a WHERE clause.
Action: An OCI_SUCCESS_WITH_INFO is returned.
ORA-24350 OCI call not allowed
Cause: OCI used is not permitted from external procedures.
Action: Refer to the Oracle Call Interface Programmer's Guide for usage restrictions.
ORA-24351 invalid date passed into OCI call
Cause: A bad date was passed into one of the OCI calls.
Action: Check your date bind values and correct them.
ORA-24352 invalid COBOL display type passed into OCI call
Cause: A bad COBOL display type was passed into one of the OCI calls.
Action: Check your COBOL display type bind values and correct them.
ORA-24353 user buffer too small to accommodate COBOL display type
Cause: User supplied buffer for a COBOL display type was too small to accommodate fetched number.
Action: Increase the allocation for COBOL display type buffer.
ORA-24354 number fetched too large to fit in COBOL display type buffer.
Cause: The number fetched was beyond the range that can be displayed.
Action: Check the number in the database.
ORA-24355 attempt to store a negative number in an Unsigned Display type.
Cause: An attempt was made to convert a negative number into an unsigned display type.
Action: Check the number in the database or change the defined datatype.
ORA-24356 internal error while converting from to COBOL display type.
Cause: An internal error was encountered during conversion to COBOL display type.
Action: Contact Oracle Support Services.
ORA-24357 internal error while converting from to OCIDate.
Cause: An internal error was encountered during conversion to OCIDate type.
Action: Contact Oracle Support Services.
ORA-24358 OCIBindObject not invoked for a Object type or Reference
Cause: OCIBindObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference.
Action: Invoke the OCIBindObject call for all Object Types and References.
ORA-24359 OCIDefineObject not invoked for a Object type or Reference
Cause: OCIDefineObject was not invoked resulting in an incomplete bind specification for a Object Type or Reference.
Action: Invoke the OCIDefineObject call for all Object Types and References.
ORA-24360 Type Descriptor Object not specified for Object Bind/Define
Cause: Type Descriptor Object is a mandatory parameter for Object Types Binds and Defines.
Action: Invoke the OCIBindObject() or OCIDefineObject() call with a valid Type Descriptor Object.
ORA-24361 basic bind call not invoked before invoking advanced bind call
Cause: One of the basic bind calls was not invoked on this bind handle before performing an advanced bind call.
Action: Invoke the advanced bind call on this bind handle only after performing a basic bind call.
ORA-24362 improper use of the character count flag
Cause: When the character count flag is set, then the maximum size of the buffer in the server should be specified as a non-zero value.
Action: Use a non-zero value for the maximum size of the buffer in the server.
ORA-24363 measurements in characters illegal here
Cause: Measurements in characters instead of bytes are illegal if either the server's or client's character set is varying width.
Action: If either the client's or server's character set is varying width then do not use the OCI_ATTR_CHAR_COUNT attribute for the bind handle. Use OCI_ATTR_MAXDATA_SIZE instead.
ORA-24364 internal error while padding blanks
Cause: An internal error has occurred while attempting to blank pad string data. This error should not occur normally.
Action: Contact Oracle Support Services.
ORA-24365 error in character conversion
Cause: This usually occurs during conversion of a multibyte character data when the source data is abnormally terminated in the middle of a multibyte character.
Action: Make sure that all multibyte character data is properly terminated.
ORA-24366 migratable user handle is set in service handle
Cause: This occurs during user authentication, a migratable user handle has been set in the service handle.
Action: Service handle must not be set with migratable user handle when it is used to authenticate another user.
ORA-24367 user handle has not been set in service handle
Cause: This occurs during authentication of a migratable user. the service handle has not been set with non-migratable user handle.
Action: Service handle must be set with non-migratable user handle when it is used to authenticate a migratable user.
ORA-24368 OCI mutex counter non-zero when freeing a handle
Cause: This is an internal OCI error.
Action: Contact Oracle Support Services.
ORA-24369 required callbacks not registered for one or more bind handles
Cause: No callbacks have been registered for one or more of the bind handles which are part of the RETURNING clause.
Action: The bind handles which are to receive data in a DML statement with a RETURNING clause must have their mode set as DATA_AT_EXEC and callback functions must be registered for these bind handles using OCIBindDynamic.
ORA-24370 illegal piecewise operation attempted
Cause: Data of a certain datatype that does not support piecewise operation is being sent or fetched in pieces.
Action: Always set the piece value to OCI_ONE_PIECE for datatypes that does not support piecewise operation.
ORA-24371 data would not fit in current prefetch buffer
Cause: An internal OCI error has occurred.
Action: Contact Oracle Support Services.
ORA-24372 invalid object for describe
Cause: The object to be described is not valid. It either has compilation or authorization errors.
Action: The object to be described must be valid.
ORA-24373 invalid length specified for statement
Cause: The length specified for the statement is either 0 or too large.
Action: Specify a valid length for the statement.
ORA-24374 define not done before fetch or execute and fetch
Cause: The application did not define output variables for data being fetched before issuing a fetch call or invoking a fetch by specifying a non-zero row count in an execute call.
Action: Issue OCI define calls for the columns to be fetched.
ORA-24375 Cannot use V6 syntax when talking to a V8 server
Cause: V6 syntax is no longer supported in V8 server.
Action: Change syntax to V7 syntax or higher.
ORA-24376 cannot register/get user callback for non-environment handle
Cause: A user callback registration or get was attempted on a handle which is not an environment handle.
Action: Pass the environment handle to register/get user callback.
ORA-24377 invalid OCI function code
Cause: An invalid function code was used to register or get user callback.
Action: Use a valid OCI function code.
ORA-24378 user callbacks not allowed for this call
Cause: An attempt was made to register a user callback for an OCI call for which it not allowed to register user callbacks.
Action: Do not register user callback for this OCI call.
ORA-24379 invalid user callback type
Cause: An invalid type of user callback was specified.
Action: Specify a valid user callback type.
ORA-24380 invalid mode specification
Cause: The mode parameter in an OCIU* call is invalid.
Action: Use only a valid mode parameter.
ORA-24381 error(s) in array DML
Cause: One or more rows failed in the DML.
Action: Refer to the error stack in the error handle.
ORA-24382 statement handled already executed or described
Cause: The statement handle was executed or described successfully before.
Action: Perform a OCIStmtPrepare again before OCI_PARSE_ONLY.
ORA-24383 Overflow segment of an IOT cannot be described
Cause: The name specified in the OCIDescribeAny call referred to an IOT overflow segment.
Action: Use OCIDescribeAny to describe only documented objects.
ORA-24384 Application context size is not initialized
Cause: The size of the application context must be initialized before populating each context element.
Action: Issue OCIAttrSet with OCI_ATTR_CTX_SIZE to initialize context size.
ORA-24385 Application context size or index is not valid
Cause: The size or index of the application context must be non-zero and non-negative.
Action: Use an appropriate value for the size.
ORA-24386 statement/server handle is in use when being freed
Cause: This is an internal OCI error.
Action: The user should reset in-use flag in statement handle before freeing the handle.
ORA-24387 Invalid attach driver
Cause: Trying to attach using the wrong driver.
Action: Relink the application in the correct mode.
ORA-24388 Unsupported functionality in fast path mode
Cause: Feature not supported in fast path mode.
Action: Avoid using the functionality in this mode.
ORA-24389 Invalid scrollable fetch parameters
Cause: All the requested rows in this fetch could not be received.
Action: Check the fetch orientation, scroll offset, OCI_ATTR_CURRENT_POSITION, and the number of rows in the OCIStmtFetch2 call. If required, change some of the above parameters and fetch again.
ORA-24390 Unsupported scrollable cursor operation
Cause: The scrollable cursor execute or fetch has failed.
Action: Check the documentation for supported types, and other restrictions while using scrollable cursors.
ORA-24391 invalid fetch operation
Cause: Scrollable cursor operation requested with non-scrollable cursor.
Action: Check if the statement was executed in the scrollable mode. The only acceptable orientation is OCI_FETCH_NEXT that ignores the scroll offset parameter.
ORA-24392 no connection pool to associate server handle
Cause: OCIServerAttach was called in OCI_POOL mode but no connection pool was found to associate the server handle.
Action: 1) Verify that OCIConnectionPoolCreate is called before calling OCIServerAttach. 2) Verify that the database link specified in OCIServerAttach matches with that of the connection pool database link.
ORA-24393 invalid mode for creating connection pool
Cause: The mode specified in OCIConnectionPoolCreate is invalid.
Action: Use a valid mode.
ORA-24394 invalid mode for destroying connection pool
Cause: The mode specified in OCIConnectionPoolDestroy is invalid.
Action: Use a valid mode.
ORA-24395 cannot reinitialize non-existent pool
Cause: OCIConnectionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.
Action: Create a connection pool prior to reinitializing it.
ORA-24396 invalid attribute set in server handle
Cause: Attribute OCI_ATTR_NONBLOCKING_MODE has been set on the server handle and attached in OCI_POOL mode. Connection pooling does not support non blocking mode.
Action: Do not set the OCI_ATTR_NONBLOCKING_MODE attribute on the server handle while attaching in OCI_POOL mode.
ORA-24397 error occurred while trying to free connections
Cause: An internal error occurred while trying to free connections.
Action: Contact Oracle Support Services.
ORA-24398 connection pool already exists
Cause: A connection pool has already been created for the specified pool handle.
Action: 1) Specify a different pool handle to create a new connection pool. 2) If you wish to modify the pool parameters, call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode.
ORA-24399 invalid number of connections specified
Cause: An invalid combination of minimum, maximum and increment number of connections was specified in the OCIConnectionPoolCreate call.
Action: Specify a valid combination of parameters.
ORA-24400 error occurred while creating connections in the pool
Cause: The database link specified in OCIConnectionPoolCreate might be invalid.
Action: Specify a valid database link.
ORA-24401 cannot open further connections
Cause: Sufficient number of connections are not present in the pool to execute the call. No new connections can be opened as the connMax parameter supplied in OCIConnectionPoolCreate has been reached.
Action: Call OCIConnectionPoolCreate in OCI_CPOOL_REINITIALIZE mode and increase the value of the connMax parameter.
ORA-24402 error occurred while creating connections in the pool
Cause: The username and password specified in OCIConnectionPoolCreate might be invalid.
Action: Specify a valid username and password.
ORA-24403 error occurred while trying to destroy the connection pool
Cause: Some connections in the pool were busy when an attempt to destroy the connection pool was made.
Action: Ensure no connections from the pool are being used.
ORA-24404 connection pool does not exist
Cause: An attempt was made to use the connection pool before it was created.
Action: Create the connection pool.
ORA-24405 error occurred while trying to create connections in the pool
Cause: An internal error occurred while creating connections in the pool.
Action: Contact Oracle Support Services.
ORA-24406 API mode switch is disallowed when a call is in progress.
Cause: A mode switch from OCI8 to OCI7 was attempted in a callback.
Action: The user should perform the API mode switch either prior to initiating the top call or after the main call has completed.
ORA-24407 connection pool already exists
Cause: A connection pool has already been created for the specified pool name.
Action: Specify a different pool name to create a new connection pool.
ORA-24408 could not generate unique server group name
Cause: An internal error occurred while generating unique server group name.
Action: Contact Oracle Support Services.
ORA-24409 client cannot understand the object
Cause: The client cannot process all the new features in the object.
Action: Upgrade the client so that features like inheritance and SQLJ objects can be used.
ORA-24410 scrollable cursor max size exceeded
Cause: Result set size exceeded the max limits.
Action: Check the documentation for allowable maximum result set size for scrollable cursors. Re-execute with a smaller expected result set size or make the cursor non-scrollable.
ORA-24411 Session pool already exists.
Cause: A session pool has already been created for the specified pool handle.
Action:
Specify a different pool handle to create a new session pool.
If you wish to modify the pool parameters, then call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode.
ORA-24412 Cannot reinitialize non-existent pool
Cause: OCISessionPoolCreate was not called in OCI_DEFAULT mode for this pool handle.
Action: Create a session pool prior to reinitializing it.
ORA-24413 Invalid number of sessions specified
Cause: An invalid combination of minimum, maximum, and increment number of sessions was specified in the OCISessionPoolCreate call.
Action: Specify a valid combination of parameters.
ORA-24414 Only number sessions could be started.
Cause: The number of sessions specified by the minSess parameter of OCISessionPoolCreate could not be started, possibly because the value supplied was larger than that supported by the server.
Action: This is a warning. Check the maximum number of sessions allowed on the server.
ORA-24415 Missing or null username.
Cause: Username and password must be specified when pool is created in this mode.
Action: Specify a valid username and password.
ORA-24416 Invalid session Poolname was specified.
Cause: An attempt was made to use a Session Pool that does not exist.
Action: Create a Session Pool before using it.
ORA-24417 Session pool size has exceeded the maximum limit
Cause: The number of sessions has exceeded the maximum size of the Session Pool.
Action: This is a warning. You can tune the session pool with appropriate minimum and maximum parameters.
ORA-24418 Cannot open further sessions.
Cause: Sufficient number of sessions are not present in the pool to execute the call. No new sessions can be opened as the sessMax parameter supplied in OCISessionPoolCreate has been reached.
Action: Call OCISessionPoolCreate in OCI_SPOOL_REINITIALIZE mode and increase the value of the sessMax parameter.
ORA-24419 Proxy sessions are not supported in this mode.
Cause: A proxy session was requested from a Session Pool which does not support proxy sessions.
Action: Do not specify mode OCI_CRED_PROXY.
ORA-24420 OCISessionRelease must be used to release this session.
Cause: The session was retrieved using OCISessionGet, and an attempt has been made to release it using a call other than OCISessionRelease.
Action: Call OCISessionRelease.
ORA-24421 OCISessionRelease cannot be used to release this session.
Cause: The session was not retrieved using OCISessionGet, and an attempt has been made to release it using OCISessionRelease.
Action: Release the session using an appropriate call.
ORA-24422 error occurred while trying to destroy the Session Pool
Cause: An attempt was made to destroy the session pool while some sessions in the pool were busy.
Action: Ensure that no sessions from the pool are being used OR call OCISessionPoolDestroy with mode set to OCI_SPD_FORCE.
ORA-24430 Null values for sqltext and key were specified.
Cause: An attempt was made to call OCIStmtPrepare2 and neither sqltext nor key were specified.
Action: Specify valid values for sqltext, key, or both.
ORA-24431 Statement does not exist in the cache
Cause: The statement that was requested does not exist in the statement cache.
Action: Request a valid statement.
ORA-24432 The statement that was returned is not tagged.
Cause: A tagged statement was requested, but an untagged statement has been returned.
Action: This is a warning. Please modify and tag the statement as desired.
ORA-24433 This statement has already been prepared using OCIStmtPrepare2.
Cause: A statement that was earlier prepared using OCIStmtPrepare2 is now being reprepared using OCIStmtPrepare.
Action: Use a different statement handle.
ORA-24434 OCIStmtRelease called before OCIStmtPrepare2.
Cause: An attempt was made to release a statement without first preparing it using OCIStmtPrepare2.
Action: Call OCIStmtPrepare2 before OCIStmtRelease.
ORA-24435 Invalid Service Context specified.
Cause: The statement was prepared using a service context that is different from the one specified in OCIStmtExecute.
Action: Please specify the same service context that the statement was prepared with.
ORA-24436 Invalid statement Handle.
Cause: OCIHandleFree called on a statement that was prepared using OCIstmtPrepare2.
Action: Release the statement using OCIStmtRelease.
ORA-24437 OCIStmtExecute called before OCIStmtPrepare2.
Cause: An attempt was made to execute a statement without first preparing it using OCIStmtPrepare2.
Action: Call OCIStmtPrepare2 before OCIStmtExecute.
ORA-24438 Invalid Authentication Handle specified.
Cause: The statement was prepared using an authentication handle that is different from the one specified in OCIStmtExecute.
ORA-24500 invalid UTF16 mode
Cause: UTF16 mode is allowed only at environment handle creation time.
Action: Remove UTF16 mode for functions other than OCIEnvCreate().
ORA-24501 invalid UTF16 string passed in
Cause: Non-UTF16 string is passed in while UTF16 string is expected.
Action: Check the parameter which is actually a string.
ORA-24502 codepoint length overflows
Cause: Returned buffer has more codepoints than allowed.
Action: Set OCI_MAXCHAR_SIZE large enough to accommodate.
ORA-24503 codepoint length overflows for piecewise operation
Cause: Accumulated codepoint length exceeds allowed codepoint length.
Action: Set OCI_MAXCHAR_SIZE large enough to accommodate.
ORA-24504 data length larger than expected
Cause: Incoming data larger than receiving buffer.
Action: Set OCI_MAXDATA/OCI_MAXCHAR_SIZE appropriately or remove the setting.
ORA-24505 cannot change character set id on the handle
Cause: An attempt was made to change character set id on non-environment handles.
Action: Only try to change character set id on environment handles.
ORA-24506 invalid attempt to change character set id on env handle
Cause: An attempt was made to change character set id after other handles have been allocated from the env handle.
Action: Change character set id after creating environment handle but before allocating any handles from it.
ORA-24507 invalid combination of character set ids
Cause: Attempts to set one character set id as zero.
Action: Set both charset and ncharset as zero or non-zero in OCIEnvNlsCreate()
ORA-24750 incorrect size of attribute
Cause: Transaction ID attribute size is incorrect.
Action: Verify that the size parameter is correct.
ORA-24752 OCI_TRANS_NEW flag must be specified for local transactions
Cause: Application attempted to start a local transaction without using OCI_TRANS_NEW.
Action: Use OCI_TRANS_NEW when starting local transactions.
ORA-24753 local transactions cannot be detached
Cause: An attempt to detach a local transaction was made.
Action: Local transactions may only be committed or rolled back.
ORA-24754 cannot start new transaction with an active transaction
Cause: An attempt to start a new transaction was made when there was an active transaction.
Action: Commit, rollback or detach the existing transaction before starting a new transaction.
ORA-24755 OCI_TRANS_NOMIGRATE, OCI_TRANS_JOIN options are not supported
Cause: These flags are currently not supported.
Action: No action required.
ORA-24756 transaction does not exist
Cause: An invalid transaction identifier or context was used or the transaction has completed.
Action: Supply a valid identifier if the transaction has not completed and retry the call.
ORA-24757 duplicate transaction identifier
Cause: An attempt was made to start a new transaction with an identifier already in use by an existing transaction.
Action: Verify that the identifier is not in use.
ORA-24758 not attached to the requested transaction
Cause: An attempt was made to detach or complete a transaction that is not the current transaction.
Action: Verify that the transaction context refers to the current transaction.
ORA-24759 invalid transaction start flags
Cause: An invalid transaction start flag was passed.
Action: Verify that one of the values OCI_TRANS_NEW, OCI_TRANS_JOIN, or OCI_TRANS_RESUME was specified.
ORA-24760 invalid isolation level flags
Cause: An invalid isolation level flag was passed.
Action: Verify that only one of following values - OCI_TRANS_READONLY, OCI_TRANS_READWRITE, OCI_TRANS_SERIALIZABLE is used.
ORA-24761 transaction rolled back
Cause: The application tried to commit a transaction and the server rolled it back.
Action: No action required.
ORA-24762 server failed due to unspecified error
Cause: An internal error has occurred in the server commit protocol.
Action: Contact Oracle Support Services.
ORA-24763 transaction operation cannot be completed now
Cause: The commit or rollback cannot be performed now because the session cannot switch to the specified transaction.
Action: Retry the operation later.
ORA-24764 transaction branch has been heuristically committed
Cause: This is an informational message.
Action: No action required.
ORA-24765 transaction branch has been heuristically rolled back
Cause: This is an informational message.
Action: No action required.
ORA-24766 transaction branch has been partly committed and aborted
Cause: This is an informational message.
Action: No action required.
ORA-24767 transaction was read-only and has been committed
Cause: This is an informational message.
Action: No action required.
ORA-24768 commit protocol error occured in the server
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-24769 cannot forget an active transaction
Cause: Transaction identifier refers to an active transaction.
Action: Verify that the identifier of an active transaction was not passed as an argument.
ORA-24770 cannot forget a prepared transaction
Cause: Transaction identifier refers to a prepared transaction.
Action: Verify that the identifier of a prepared transaction was not passed as an argument.
ORA-24771 cannot detach, prepare or forget a local transaction
Cause: Service handle contains a local transaction context.
Action: Verify that the transaction context does not refer to a local transaction.
ORA-24772 Cannot mix tightly-coupled and loosely-coupled branches
Cause: Application attempted to start a transaction with a global transaction identifier and a wrong option.
Action: Verify that all branches of a global transaction are started with either OCI_TRANS_TIGHT or OCI_TRANS_LOOSE option. If the application is correct and uses distributed updates, contact Oracle Support Services.
ORA-24773 invalid transaction type flags
Cause: OCI_TRANS_TIGHT or OCI_TRANS_LOOSE mode was not specified.
Action: Verify that the right parameters are being used.
ORA-24774 cannot switch to specified transaction
Cause: The transaction specified in the call refers to a transaction created by a different user.
Action: Create transactions with the same authentication so that they can be switched.
ORA-24775 cannot prepare or commit transaction with non-zero lock value
Cause: An attempt was made to detach the transaction with a non-zero lock value.
Action: Detach the transaction with lock value set to zero and then try to prepare or commit the transaction.
ORA-24776 cannot start a new transaction
Cause: An attempt was made to start a new transaction when session was already attached to an existing transaction.
Action: End the current transaction before creating a new transaction.
ORA-24777 use of non-migratable database link not allowed
Cause: The transaction, which needs to be migratable between sessions, tried to access a remote database from a non-multithreaded server process.
Action: Perform the work in the local database or open a connection to the remote database from the client. If the multithreaded server option is installed, connect to the Oracle instance through the dispatcher.
ORA-24778 cannot open connections
Cause: The migratable transaction tried to access a remote database when the session itself had opened connections to remote database(s).
Action: Close the connection(s) in the session and then try to access the remote database from the migratable transaction. If the error still occurs, contact Oracle Support Services.
ORA-24779 detach not allowed with open remote cursor
Cause: The migratable transaction tried to detach from the current session while an open remote cursor exists.
Action: Close any open remote cursor prior to detach.
ORA-24780 cannot recover a transaction while in an existing transaction
Cause: An attempt was made to commit or roll back a transaction while in a different transaction, and the transaction for which the action is requested is in a recovery state (this happens if it is idle too long).
Action: Detach from the current transaction and retry the operation.
ORA-24781 branches don't belong to the same global transaction
Cause: The list of xids passed into kpotxmp() do not have the same gtrid
ORA-24782 Cannot detach from a non-migratable transaction
Cause: An attempt was made to detach from a non-migrateable transaction.
Action: Either commit or rollback the transaction.
ORA-24783 Cannot switch non-migratable transactions
Cause: An attempt was made to prepare/commit a txn different from current.
ORA-24784 Transaction exists
Cause: An attempt was made to start a transaction, while attached to a non-migrateable transaction.
ORA-24785 Cannot resume a non-migratable transaction
Cause: An attempt was made to resume a non-migrateable transaction.
ORA-24786 separated transaction has been completed
Cause: The current transaction has been completed by another process.
Action: Start a new transaction.
ORA-24787 remote cursors must be closed before a call completes
Cause: The previous operation did not close all the remote cursors it opened. Since separated transactions are enabled, this is not allowed.
Action: Close all remote cursors in each call, or start a regular (non-separated) transaction.
ORA-24788 cannot switch to specified transaction (server type)
Cause: The transaction specified was created by a shared server and the requestor is a dedicated server, or the transaction was created by a dedicated server and the requestor is a shared server.
Action: All parts of this application should connect as dedicated or as shared.
ORA-24790 cannot mix OCI_TRANS_RESUME and transaction isolation flags
Cause: An attempt was made to change the isolation level of an existing transaction.
Action: No action required.
ORA-24801 illegal parameter value in OCI lob function
Cause: One of the parameter values in the OCI LOB function is illegal.
Action: Check every parameter in the OCI Lob function call to make sure they are correct. Offsets should be greater than or equal to one.
ORA-24802 user defined lob read callback error
Cause: The only valid return value for a user defined LOB read callback function is OCI_CONTINUE. Any other value will cause this error.
Action: Verify that OCI_CONTINUE is returned from the user defined LOB read callback function.
ORA-24803 illegal parameter value in lob read function
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
ORA-24804 illegal parameter value in lob write function
Cause: This is an internal error.
Action: This error should not normally occur. If it persists, contact Oracle Support Services.
ORA-24805 LOB type mismatch
Cause: When copying or appending LOB locators, both source and destination LOB locators should be of the same type.
Action: Pass the same type of LOB locators for copying or appending.
ORA-24806 LOB form mismatch
Cause: When reading from or writing into LOBs, the character set form of the user buffer should be same as that of the LOB.
Action: Make sure that the buffer you are using to read or write has the same form as that of the LOB.
ORA-24807 LOB form mismatch
Cause: When copying or appending LOBs, both source and destination LOB locators should have the same character set form.
Action: Pass locators of the same character set form for copying or appending LOBs.
ORA-24808 streaming of lob data is not allowed when using lob buffering
Cause: An attempt was made to stream LOB data via the polling mode or a callback when LOB buffering was enabled for the input LOB locator.
Action: Lob buffering is useful when reading/writing small amounts of LOB data so streaming should not be necessary. Rewrite the OCILobRead/OCILobWrite call so that it does not use streaming. If streaming of data is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the OCILobRead/OCILobWrite call.
ORA-24809 amount specified will not fit in the lob buffers
Cause: LOB buffering is enabled for the input LOB locator so buffering will be used. However, the amount of LOB data to read or write is larger than what the LOB buffers can hold.
Action: Either disable buffering on the input LOB locator and reissue the command or pass a smaller amount.
ORA-24810 attempting to write more data than indicated
Cause: While writing into a LOB, more data was supplied than indicated.
Action: If data is written in pieces, then make sure that you do not provide more data in the pieces (cumulatively), than you indicated.
ORA-24811 less data provided for writing than indicated
Cause: While writing into a LOB, less data was provided than indicated.
Action: If writing data in single pieces, then make sure that the buffer length specified is big enough to accommodate the data being provided. If data is written in pieces, then make sure that all the data has been provided before specifying OCI_LAST_PIECE.
ORA-24812 character set conversion to or from UCS2 failed
Cause: If the database character set is varying-width, the CLOB/NCLOB value is implicitly converted to or from UCS2. This implicit conversion failed.
Action: Contact Oracle Support Services.
ORA-24813 cannot send or receive an unsupported LOB
Cause: An attempt was made to send a LOB across the network, but either the server does not support the LOB sent by the client, or the client does not support the LOB sent by the server. This error usually occurs when the client and server are running different versions of Oracle.
Action: Use a version of the Oracle that supports the LOB on both the client and the server.
ORA-24814 operation not allowed for temporary LOBs
Cause: Temporary LOB locators are not allowed in the operation. For example, OCILobAssign only takes persistent LOB locators as parameters, not temporary LOBs.
Action: Use OCILobLocatorAssign for temporary LOBs instead. Note that OCILobLocatorAssign can also be used for persistent LOBs, in which case it will behave the same as OCILobAssign.
ORA-24850 failed to startup shared subsystem
Cause: While attempting to initialize OCI in shared mode, a problem was encountered in starting the shared subsystem.
Action: Contact Oracle Support Services.
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 Support Services.
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 Support Services.
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 Support Services.
ORA-24900 invalid or unsupported mode paramater passed in call
Cause: The mode parameter passed into the OCI Client Notification call is incorrect.
Action: Correct the mode parameter passed into OCI.
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: Make sure that the handle parameters in the call to come from the same OCI Environment.
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: Set the name and name-length attributes using the OCIAttrSet() 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: Set the NAMESPACE attribute using the OCIAttrSet() 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: Set the callback attribute using the OCIAttrSet() 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: Set the recepient protocol attribute using the OCIAttrSet() 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: Set the recepient attribute using the OCIAttrSet() call.
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: Set the appropriate callback and recepient protocol attributes using the OCIAttrSet() call.
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-24950 unregister failed, registeration not found
Cause: The registeration that was asked to be unregistered could not be found.
Action: Check the callback function name and the subscription name in the unregister call.
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/old).column_name.
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-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-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-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-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-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-25007 functions or methods not allowed in WHEN clause
Cause: PL/SQL 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-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-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-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-25012 PARENT and NEW values cannot be identical
Cause: The referencing clause specifies identical values for PARENT and OLD.
Action: Respecify either the PARENT or NEW referencing value.
ORA-25013 OLD and PARENT values cannot be identical
Cause: The referencing clause specifies identical values for OLD and PARENT.
Action: Respecify either the OLD or PARENT referencing value.
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-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-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-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-25018 conflicting trigger string already exists
Cause: Conflicting instead of DDL trigger on schema/database already exists.
Action: Remove the old trigger.
ORA-25019 too much concurrency
Cause: Cannot pin the database/schema because of too much concurrency.
Action: Try the operation later.
ORA-25020 renaming system triggers is not allowed
Cause: renaming system triggers is not allowed.
Action: Drop the trigger and create a new one.
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-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-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-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-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-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-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-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-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-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-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-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-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-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 add a LOCAL partition descriptor if the table is partitioned.
ORA-25114 invalid file number specified in the DUMP DATAFILE/TEMPFILE command
Cause: An invalid file number was used in dumping a datafile or temporary file.
Action: Specify a valid file number.
ORA-25115 duplicate BLOCK option specification
Cause: BLOCK (MIN/MAX) was specified more than once in the DUMP DATAFILE/TEMPFILE command.
Action: Specify only one BLOCK option.
ORA-25116 invalid block number specified in the DUMP DATAFILE/TEMPFILE command
Cause: An invalid block number was used in dumping a datafile or temporary file.
Action: Specify a valid block number.
ORA-25117 MIN/MAX/Block Number expected
Cause: A value other than MIN/MAX, or a block number was entered in the DUMP DATAFILE/TEMPFILE command.
Action: Correct the syntax.
ORA-25118 invalid DUMP DATAFILE/TEMPFILE option
Cause: An invalid option was specified for the DUMP DATAFILE/TEMPFILE command.
Action: Correct the syntax.
ORA-25119 LOGGING/NOLOGGING option already specified
Cause: In CREATE TABLESPACE, the LOGGING and/or NOLOGGING options were specified more than once.
Action: Remove all but one of the logging specifications.
ORA-25120 MINIMUM EXTENT option already specified
Cause: In CREATE TABLESPACE, the MINIMUM EXTENT option was specified more than once.
Action: Remove all but one of the MINIMUM EXTENT specifications.
ORA-25121 MINIMUM EXTENT value greater than maximum extent size
Cause: In CREATE/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.
ORA-25122 Only LOCAL bitmap indexes are permitted on partitioned tables
Cause: An attempt was made to create a global bitmap index on a partitioned table.
Action: Create a local bitmap index instead.
ORA-25123 Too many components specified in the name.
Cause: More components per name than is allowed were specified.
Action: Check the name specified for the operation.
ORA-25124 Database link name not allowed.
Cause: A database link name was specified when it is not permitted.
Action: Check the name specified for the operation.
ORA-25125 BUFFER_POOL storage option not allowed
Cause: An attempt was made to specify the BUFFER_POOL storage option. This option may only be specified during CREATE/ALTER TABLE/CLUSTER/INDEX.
Action: Remove this option and retry the statement.
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-25127 RELY not allowed in NOT NULL constraint
Cause: An attempt was made to set RELY on for NOT NULL constraint.
Action: Only NORELY may be specified for a NOT NULL constraint.
ORA-25128 No insert/update/delete on table with constraint (string.string) disabled and validated
Cause: An attempt was made to insert/update/delete on table with DISABLE VALIDATE constraint.
Action: Change the constraint's states.
ORA-25129 cannot modify constraint (string) - no such constraint
Cause: The named constraint does not exist for this table.
Action: Try again with a constraint that does exist for this table.
ORA-25130 cannot modify primary key - primary key not defined for table
Cause: An attempt was made to modify a primary key that is not defined for the table.
Action: No action required.
ORA-25131 cannot modify unique(string) - unique key not defined for table
Cause: An attempt was made to modify a unique key that is not defined for the table.
Action: No action required.
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 partition is not mutually exclusive from the rest of the table.
Action: Change the constraint's status.
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-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-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-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-25137 Data value out of range
Cause: Value from cast operand is larger than cast target size.
Action: Increase size of cast target.
ORA-25138 string 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-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-25140 string 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-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-25142 default storage clause specified twice
Cause: Default storage clause was specified twice for create tablespace.
Action: Specify it once.
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-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-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-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-25147 UNIFORM SIZE value greater than maximum extent size
Cause: In CREATE/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-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-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-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-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-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-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-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-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-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-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 either the standard blocksize or one of (2k, 4k, 8k, 16k, 32k) subject to the maximum and minimum blocksizes supported by the platform.
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-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-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-25178 duplicate PCTTHRESHOLD storage option specification
Cause: The storage option PCTTHRESHOLD is specified more than once.
Action: Specify storage options at most once.
ORA-25179 invalid PCTTHRESHOLD storage option value
Cause: The specified value must be a positive integer.
Action: Specify an appropriate value.
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-25181 missing ON keyword for NESTED INDEX
Cause: The ON keyword is required to specify nested index column nest.
Action: Add ON keyword.
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/BFILE/VARRAY columns
partitioning/PARALLEL/CREATE TABLE AS SELECT options
ALTER TABLE with ADD/MODIFY column options
CREATE INDEX
Action: Do not use the disallowed feature(s) in this release.
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-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-25185 index column other than last can not be specified for INCLUDE clause
Cause: An index column name other than the last was 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-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-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-25188 cannot drop/disable/defer the primary key constraint for index-organized tables
Cause: An attempt was made to DROP, DISABLE, or DEFER the primary key constraint for an index-only table. This is not allowed.
Action: Do not DROP, DISABLE, or DEFER the primary key constraint for an index-only 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/DEALLOCATE EXTENT, PCTFREE/PCTUSED for IOT top index segment
Action: Remove the illegal option(s).
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 (for example, changing physical attributes) with some other operation (for example, ADD constraint) which is illegal
Action: Ensure that a index-organized table maintenance operation is the sole operation specified in ALTER TABLE statement.
ORA-25191 cannot reference overflow table of an index-organized table
Cause: An attempt was made 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-25192 invalid option for an index-organized table
Cause: An attempt was made 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-25193 cannot use COMPRESS option for a single column key
Cause: An attempt was made to use COMPRESS option on single column key.
Action: Remove the COMPRESS option.
ORA-25194 invalid COMPRESS prefix length value
Cause: The specified value must be a positive integer less than the number of key columns.
Action: Specify an appropriate value.
ORA-25195 invalid option for index on an index-organized table
Cause: An attempt was made to specify one or more of the following options for index on an IOT: BITMAP, REVERSE, PCTUSED.
Action: Specify an appropriate option.
ORA-25196 keyword MOVE in ALTER TABLE MOVE must immediately follow table_name
Cause: MOVE specified after one/more other ALTER options.
Action: Change order of options, MOVE should be first or remove the illegal option(s).
ORA-25197 an overflow segment already exists for the indexed-organized table
Cause: An attempt was made to ADD OVERFLOW segment on an index-organized table that already has an overflow segment.
Action: No action required.
ORA-25198 only range and hash partitioning are supported for index-organized table
Cause: System or composite partitioning schemes are not supported.
Action: Select a different partitioning scheme.
ORA-25199 partitioning key of a index-organized table must be a subset of the primary key
Cause: An attempt was made to specify a partitioning key which is not a prefix of the primary key of the index-organized table.
Action: Select a different partitioning key.
ORA-25200 invalid value string, QUEUE_NAME should be [SCHEMA.]NAME
Cause: A NULL parameter was specified for QUEUE_NAME.
Action: Specify a non-NULL queue name.
ORA-25201 invalid value, VISIBILITY should be ON_COMMIT or IMMEDIATE
Cause: An invalid value specified for parameter VISIBILITY.
Action: Specify either ON_COMMIT or IMMEDIATE.
ORA-25202 invalid value NULL, string should be non-NULL
Cause: A NULL value was specified for the parameter.
Action: Specify a non-NULL value.
ORA-25203 invalid value string, DELAY should be non-negative
Cause: A negative value or NULL was specified for DELAY.
Action: Specify a non-negative integer for DELAY.
ORA-25204 invalid value, SEQUENCE_DEVIATION should be BEFORE or TOP
Cause: An invalid SEQUENCE_DEVIATION was specified.
Action: Specify either the option 'BEFORE' or 'TOP'.
ORA-25205 the QUEUE string.string does not exist
Cause: The specified queue does not exist.
Action: Create the queue first before specifying it for enqueue or dequeue.
ORA-25206 enqueue failed, enqueue to exception queue string.string not permitted
Cause: An attempt was made to enqueue to an exception queue.
Action: Try enqueueing to another queue.
ORA-25207 enqueue failed, queue string.string is disabled from enqueueing
Cause: The queue has been stopped to prevent any further enqueueing.
Action: Enable the queue first by using an administrative operation.
ORA-25208 RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE
Cause: A relative message identifier should be specified if sequence deviation is specified as BEFORE.
Action: Either specify an existing relative message identifier or do not specify sequence deviation as BEFORE.
ORA-25209 invalid value string, EXPIRATION should be non-negative or NEVER
Cause: The expiration is less than zero or NULL.
Action: Specify a valid value for EXPIRE_AFTER which should be greater than or equal to zero or NEVER.
ORA-25210 invalid value for RELATIVE_MSGID, no message in queue with that msgid
Cause: No message in the queue with the MSGID equal to the specified RELATIVE_MSGID.
Action: Try again with a valid RELATIVE_MSGID.
ORA-25211 invalid DELAY specified when using sequence deviation
Cause: The DELAY specified in the enqueue is greater than the delay of the message with the given relative message ID.
Action: Set the DELAY to be less than or equal to the delay of the message with the given relative message ID. If the TOP option is used the delay must be less than or equal to the delay of all the messages in the queue.
ORA-25212 invalid PRIORITY specified when using sequence deviation
Cause: The PRIORITY specified in the enqueue is less than the priority of the message with the given relative message ID.
Action: Set the PRIORITY to be less than the delay of the message with the given relative message ID. If the TOP option is used the priority must be greater than or equal to the priority of all the messages in the queue.
ORA-25213 message with specified RELATIVE_MSGID has been dequeued
Cause: The message specified by the RELATIVE_MSGID field in the sequence deviation BEFORE option has been dequeued.
Action: No action required. This is an informational message only.
ORA-25214 cannot specify delay or expiration for enqueue to exception queue
Cause: A message was enqueued to the exception queue with either delay or expiration specified.
Action: Enqueue a message without delay or expiration.
ORA-25215 user_data type and queue type do not match
Cause: A user tries to enqueue an object to a queue that was created for objects of different type.
Action: Try enqueue again with an object of the right type.
ORA-25216 invalid recipient, either NAME or ADDRESS must be specified
Cause: Both attributes, NAME and ADDRESS, were specified null for one of the recipients in the recipient list.
Action: Specify a non-null NAME or ADDRESS for the recipient.
ORA-25217 enqueue failed, visibility must be IMMEDIATE for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue without setting visibility to IMMEDIATE.
Action: Set visibility to IMMEDIATE.
ORA-25218 enqueue failed, delay must be zero for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue with delay greater than zero seconds.
Action: Set delay to zero.
ORA-25219 enqueue failed, sequence deviation not allowed for queue string.string
Cause: An attempt was made to enqueue to a non-persistent queue with sequence deviation specified.
Action: Do not specify sequence deviation.
ORA-25220 enqueue failed, signature not specified for a non-repudiable queue
Cause: An attempt was made to enqueue to a non-repudiable queue without specifying the signature.
Action: Specify the signature.
ORA-25221 enqueue failed, signature specified queue not supporting non-repudiation
Cause: An attempt was made to enqueue to a queue specifying the signature for a queue not supporting non-repudiation.
Action: Remove the signature.
ORA-25222 enqueue failed, complete sender info. not provided for a queue supporting non-repudiation
Cause: An attempt was made to enqueue to a queue without giving the complete sender information (name) for a queue supporting non-repudiation.
Action: Provide the sender information.
ORA-25223 user_data type used is not supported
Cause: An attempt was made to enqueue data into a non persistent queue that is of a type other than the supported raw or object type.
Action: Enqueue the message again with data of raw or object type.
ORA-25224 sender name must be specified for enqueue into secure queues
Cause: An attempt was made to enqueue into a secure queue without specifying a sender name.
Action: Enqueue the message with sender name specified.
ORA-25225 invalid value string, DEQUEUE_MODE should be REMOVE or BROWSE or LOCKED
Cause: An invalid parameter has been specified for DEQUEUE_MODE.
Action: Specify either REMOVE, BROWSE or LOCKED.
ORA-25226 dequeue failed, queue string.string is not enabled for dequeue
Cause: The queue has not been enabled for dequeue.
Action: Enable the queue using START_QUEUE.
ORA-25228 timeout or end-of-fetch during message dequeue from string.string
Cause: User-specified dequeue wait time has passed or the end of the queue has been reached but no message has been retrieved.
Action: Try dequeue again with the appropriate WAIT_TIME or the FIRST_MESSAGE option.
ORA-25229 error on transformation of message string string
Cause: There was an error when transforming a message at enqueue, dequeue, or propagation time.
Action: Correct the transformation function.
ORA-25230 invalid value string, WAIT should be non-negative
Cause: A negative value has been specified for WAIT.
Action: Specify a non-negative value or FOREVER.
ORA-25231 cannot dequeue because CONSUMER_NAME not specified
Cause: A user tried to dequeue from a queue that has been created for multiple consumers but a CONSUMER_NAME was not been specified in the dequeue options.
Action: Specify the CONSUMER_NAME in the dequeue options.
ORA-25232 duplicate recipients specified for message
Cause: An enqueue was performed with duplicate queue agents in the recipients parameter.
Action: Remove the duplicate queue agent and retry the call.
ORA-25233 invalid parameter specified for NAVIGATION
Cause: An invalid parameter has been specified for NAVIGATION.
Action: Choose one of FIRST_MESSAGE, NEXT_MESSAGE or NEXT_TRANSACTION. Use FIRST_MESSAGE for dequeuing the first message that satisfies the criterion, NEXT_MESSAGE for dequeuing the next message that satisfies the criterion and NEXT_TRANSACTION for moving to a set of messages enqueued by another transaction.
ORA-25234 NEXT_TRANSACTION navigation option invalid for queue table string.string
Cause: The NEXT_TRANSACTION navigation option was used in a dequeue from a queue in a queue table that was not created for transactional grouping.
Action: Specify either FIRST_MESSAGE or NEXT_MESSAGE as the navigation option. If you want to dequeue messages using transactional grouping create the queue in a queue table that has transactional grouping enabled.
ORA-25235 fetched all messages in current transaction
Cause: The NEXT_TRANSACTION navigation option was used in a dequeue when there were no more messages that belong to the same transaction.
Action: Use the NEXT_TRANSACTION navigation option to move to the next also use the FIRST_MESSAGE option to start from the head of the queue again.
ORA-25236 buffer too small for user data
Cause: The variable or buffer used for the out parameter payload is too small for the user data dequeued.
Action: Increase the size of the buffer or the size of the variable. Maximum size allowed is 32K.
ORA-25237 navigation option used out of sequence
Cause: The NEXT_MESSAGE or NEXT_TRANSACTION option was specified after dequeuing all the messages.
Action: Reset the dequeuing position using the FIRST_MESSAGE navigation option and then specify the NEXT_MESSAGE or NEXT_TRANSACTION option.
ORA-25238 too many recipients specified for message destination string
Cause: An ENQUEUE was performed with more than 32 recipients for the given destination (address).
Action: Reduce the number of recipients to 32 or less, and retry the call.
ORA-25239 message ID not supplied when dequeuing from exception queue string.string
Cause: An attempt was made to dequeue from a release 8.0-compatible exception queue without including a message ID in the dequeue options.
Action: Check the application to ensure that the queue name has been specified correctly. If the queue name is correct supply a message ID when dequeuing from a release 8.0-compatible exception queue. Otherwise, upgrade the QUEUE_TABLE containing the queue to release 8.1-compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
ORA-25240 message ID and dequeue condition/correlation ID specified in dequeue options
Cause: An attempt was made to dequeue by including both a message ID and a dequeue condition/correlation ID in the dequeue options. In the dequeue options, you are permitted to specify either a message ID or a dequeue condition/correlation ID, or neither.
Action: To dequeue a message, specify a message ID or a dequeue condition/correlation ID in the dequeue options, but do not specify both. If you want to dequeue in the queue's sort order, then do not specify either the message ID or dequeue condition/correlation ID in the dequeue options.
ORA-25241 cannot change correlation ID from string to string without FIRST_MESSAGE option
Cause: An attempt was made to change the correlation ID while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
Action: To use a correlation ID that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.
ORA-25242 cannot change subscriber name from string to string without FIRST_MESSAGE option
Cause: An attempt was made to change the subscriber name while using the NEXT_MESSAGE or NEXT_TRANSACTION option for dequeuing.
Action: To use a subscriber name that is different from the previous dequeue call, reset the dequeuing position by using the FIRST_MESSAGE navigation option.
ORA-25243 CONSUMER_NAME cannot be specified when dequeuing from exception queue string.string
Cause: An attempt was made to dequeue from an exception queue by specifying the CONSUMER_NAME in the dequeue options. CONSUMER_NAME can only be specified when dequeuing from a normal queue created for multiple consumers.
Action: Specify only the message ID in the dequeue options to dequeue a message from an exception queue.
ORA-25244 dequeue index key not found, QUEUE string, rowid string
Cause: An internal error was encountered. There may be an inconsistency in the queue table index.
Action: Contact Oracle Support Services. You may need to provide the trace file and information about reproducing the error.
ORA-25245 agent name cannot be specified if address is a single-consumer queue or an exception queue
Cause: The agent name for the agent in the LISTEN call was specified when the agent address was a single-consumer queue or an exception queue.
Action: Do not specify the agent name.
ORA-25246 listen failed, the address string is an 8.0 style exception queue
Cause: An 8.0 style exception queue was specified in the agent-list for the LISTEN call.
Action: Specify a normal 8.0 style queue or an 8.1 style queue in the agent-list.
ORA-25247 string is not a recipient of specified message
Cause: The consumer name specified in the dequeue options is not a recipient of the message specified by the message ID.
Action: Ensure that the agent specified by the consumer name is a recipient of the message specified by the message ID.
ORA-25248 duplicate agent specified in the agent list
Cause: An agent was specified more than once in the agent list of the LISTEN call.
Action: Remove the duplicate agent specification(s), and retry the call.
ORA-25249 dequeue failed, dequeue not allowed for queue string.string
Cause: An attempt was made to dequeue from a non-persistent queue.
Action: Dequeue from a different queue.
ORA-25250 Cannot specify a remote recipient for the message
Cause: A recipient for the message enqueued to a non-persistent queue had a non-local address.
Action: Do not specify the address field or specify the queue which is the target of the enqueue
ORA-25251 exceeded maximum number of recipients for message
Cause: An attempt was made to issue an ENQUEUE call that exceeded the maximum number (1024) of recipients per message.
Action: Reduce the number of recipients to 1024 or less, and retry the call.
ORA-25252 listen failed, the address string is a non-persistent queue
Cause: A non-persistent queue was specified as an address for an agent in the LISTEN call.
Action: Specify a normal queue as address for the agent, and retry the LISTEN call.
ORA-25253 listen failed, queue string.string is not enabled for dequeue
Cause: An attempt was made to specify a queue that is not enabled for dequeue in a LISTEN call.
Action: Enable the queue for dequeue using START_QUEUE, and retry the LISTEN call.
ORA-25254 time-out in LISTEN while waiting for a message
Cause: The specified wait time has elapsed and there were no messages for any of the agents in the agent-list.
Action: Try the LISTEN call with an appropriate time-out.
ORA-25255 incorrect subscription string string
Cause: An incorrect subscription string was specified with OCIRegister.
Action: Specify a subscription string using the [CONSUMER:]SCHEMA.QUEUE form.
ORA-25256 consumer cannot be specified with a single-consumer queue or an exception queue
Cause: An attempt was made to specify a consumer in the subscription string when registering for notification on a single-consumer queue or an exception queue.
Action: Do not specify the consumer in the subscription string.
ORA-25257 consumer must be specified with a multi-consumer queue
Cause: An attempt was made to register on a multi-consumer queue without specifying a consumer in the subscription string.
Action: Specify a consumer in the subscription string.
ORA-25258 cannot register for notifications on an 8.0 style exception queue
Cause: An attempt was made to specify an 8.0 style exception queue in the subscription string of OCIRegister.
Action: Specify a normal queue or a non-persistent queue.
ORA-25259 cannot specify protocol for agent
Cause: The user specified the protocol attribute for an agent in the agent list.
Action: Do not specify the protocol attribute of the agent object type.
ORA-25261 JOB_QUEUE_PROCESSES must be at least 2 for AQ propagation
Cause: AQ Propagator encountered a setting for JOB_QUEUE_PROCESSES that is insufficient for AQ propagation.
Action: Set the number of JOB_QUEUE_PROCESSES to at least 2 for AQ propagation.
ORA-25262 agent name cannot be NULL if address is a multi-consumer queue
Cause: The name for the agent in the LISTEN call was not specified when the agent address was a multi-consumer queue.
Action: Specify a non-NULL name for the agent.
ORA-25263 no message in queue string.string with message ID string
Cause: An attempt was made to dequeue a message with a specific message ID, but no such message exists in the queue.
Action: Try dequeue again with a valid message ID.
ORA-25264 can't get signature for this queue
Cause: An attempt was made to dequeue the signature from this queue, which is not reciever non-repidiable.
Action: Try dequeue again without the get signature option.
ORA-25265 specified signature for a queue which does not support reciever non-repudiation
Cause: An attempt was made to dequeue the message from a queue which does not support reciever non-repudiation, but the signature was specified for verification.
Action: Try dequeue again without the signature.
ORA-25266 didn't try to dequeue by message id with the signature
Cause: The signature was specified for a queue, but the dequeue was not done by message id.
Action: Try dequeue again by message id.
ORA-25267 didn't specify the signature for a reciever non-repudiable queue
Cause: The signature was not specified for a reciever non-repudiable queue.
Action: Try dequeue again along with the signature.
ORA-25268 didn't dequeue in browse mode with get signature option
Cause: The dequeue was not performed in browse mode with get signature option.
Action: Try dequeue again in browse mode.
ORA-25269 can't specify signature with get signature option
Cause: The signature is not required for the dequeue with get signature option.
Action: Try dequeue again without the signature in dequeue options.
ORA-25270 sender info does not match with the actual sender of the message
Cause: The sender info and the message id do not match.
Action: Provide the correct sender info or try dequeue again without the signature in dequeue options.
ORA-25271 queue table not found for the given queue
Cause: The queue table does not exist for the given queue.
Action: Provide the correct queue name.
ORA-25272 Signature does not exist for the given reciever and message id
Cause: Signature does not exist for the given reciever and message id.
Action: Check the message id and the reciever's information.
ORA-25276 table specified is not a queue table
Cause: An invalid queue table name is specified.
Action: Check the dictionary views to see if the table is a queue table.
ORA-25277 cannot grant or revoke object privilege on release 8.0 compatible queues
Cause: An attempt was made to grant or revoke object privilege on release 8.0 style queues.
Action: Convert the release 8.0 compatible queue table to release 8.1 compatible using DBMS_AQADM.MIGRATE_QUEUE_TABLE before granting or revoking object privilege.
ORA-25278 grantee name cannot be NULL
Cause: An attempt was made to specify NULL for the grantee parameter.
Action: Specify a valid grantee parameter.
ORA-25279 dequeue as select not supported before 9.0.0
Cause: Dequeue as select not supported before 9.0.0.
Action: Don't use select condition while dequeuing.
ORA-25280 complete sender information not provided to non-repudiate sender
Cause: Complete sender information not provided to non-repudiate sender.
Action: Provide the complete sender information.
ORA-25281 complete reciever information not provided to non-repudiate reciever
Cause: Complete reciever information not provided to non-repudiate reciever.
Action: Provide the complete reciever information.
ORA-25282 message id not provided for non-repudiation
Cause: Message id was not provided.
Action: Provide the message id.
ORA-25283 either agent's name or address needed for non-repudiation
Cause: neither agent's name nor address provided for non-repudiation.
Action: Provide the agent info.
ORA-25284 Invalid value string for string
Cause: An Invalid value or NULL was specified for the parameter.
Action: Check the documentation for valid values.
ORA-25285 Invalid value string for array_mode
Cause: An Invalid value or NULL was specified for the array_mode.
Action: Check the documentation for valid values.
ORA-25286 Invalid number of elements in the message properties array
Cause: Number of elements in the message properties array does not match the number of elements in the payload array.
Action: Create a message property array with one element (that applies for all the elements in the payload array) or create a message property array with the same number of elements as there are in the payload array.
ORA-25287 Invalid value string, string should be non-negative
Cause: An Invalid value or NULL was specified for the parameter.
Action: Specify a non negative integer.
ORA-25288 AQ HTTP propagation encountered error, status-code number, string
Cause: AQ propagation's HTTP request to the propagation servlet at the specified address encountered an error.
Action: Specify a valid address in the connect string of the propagation destination dblink, make sure the dblink user has the correct permissions, and check if the AQ propagation servlet was properly installed.
ORA-25289 Buffer Already Exists
Cause: Buffer already exists for the specified queue.
Action: No action required.
ORA-25290 Cannot complete operation on queue string with existing messages
Cause: Queue already has messages. Cannot complete operation.
Action: Truncate the queue before adding/dropping a buffer.
ORA-25291 Buffer does not exist for the specified queue
Cause: Buffer does not exist for the specified queue.
Action: Operation on the buffer cannot be performed. create the buffer.
ORA-25292 Cannot add buffer on the specified queue
Cause: Buffer cannot be added on the Specified Queue.
Action: Can only add buffers to 8.1 style non-exception multi-consumer queues, which do not have priority, non_repudiation, message_grouping, max_retries, and retention.
ORA-25293 Remote Recipient Subscribers and buffered operations not possible for Queue string
Cause: Specified Queue has remote recipient subscribers.
Action: Cannot add buffers/add buffered subscribers to queues with remote recipient subscribers.
ORA-25294 Queue string has a buffer
Cause: Specified Queue has a buffer.
Action: Drop the buffer first.
ORA-25295 Subscriber is not allowed to dequeue buffered messages
Cause: Subscriber is only allowed to dequeue persistent messages.
Action: Drop the subscriber and re-create it.
ORA-25296 Queue Table string has a buffered queue string
Cause: Cannot downgrade the queue table because it has a buffered queue.
Action: Drop the buffer or the buffered queue.
ORA-25297 The message options only make sense for buffered messages
Cause: The message options only make sense for buffered messages.
Action: Check the enqueue/dequeue options.
ORA-25298 The memory threshold for a queue cannot be negative
Cause: The memory threshold for a queue cannot be negative.
Action: Correct the memory threshold.
ORA-25299 Cannot add buffered subscriber for a non-buffered queue
Cause: Cannot add buffered subscriber for a non-buffered queue.
Action: Either add buffer to the queue, or make the subscriber non-buffered.
ORA-25300 Cannot drop buffer for queue with buffered subscribers
Cause: Cannot drop buffer for queue with buffered subscribers.
Action: Either drop buffered subscribers or forcibly drop the buffer.
ORA-25301 cannot specify recipient list during enqueue
Cause: Recipient list for buffered queue not supported.
Action: Don't specify recipient list for buffered enqueues.
ORA-25302 Operation not possible for non-buffered queue string
Cause: Last enqd/ackd message is only supported for buffered queues.
Action: The operation is not supported.
ORA-25350 maximum number of concurrent transaction branches exceeded
Cause: The limit on the number of concurrent transaction branches has been reached.
Action: Increase the initialization parameter TRANSACTIONS and restart the system.
ORA-25351 transaction is currently in use
Cause: The transaction is currently used by a different session.
Action: Do not switch to a transaction attached to some other session.
ORA-25352 no current transaction
Cause: The user session is not attached to any transaction.
Action: Do not attempt to detach when there is no current transaction.
ORA-25353 branch marked for deletion
Cause: The branch specified cannot be killed immediately because another session is using the branch, but it has been marked for kill. This means it will be deleted as soon as possible after the current uninterruptable operation is completed.
Action: No action is required for the branch to be deleted.
ORA-25400 must replay fetch
Cause: A failure occurred since the last fetch on this statement. Failover was able to bring the statement to its original state to allow continued fetches.
Action: This is an internally used error message and should not be seen by the user.
ORA-25401 can not continue fetches
Cause: A failure occurred since the last fetch on this statement. Failover was unable to bring the statement to its original state to allow continued fetches.
Action: Re-execute the statement and start fetching from the beginning.
ORA-25402 transaction must roll back
Cause: A failure occurred while a transaction was active on this connection.
Action: The client must roll back.
ORA-25403 could not reconnect
Cause: The connection to the database has been lost, and attempts to reconnect have failed.
Action: Manually reconnect.
ORA-25404 lost instance
Cause: The primary instance has died.
Action: This is an internally used error message and should not be seen by the user.
ORA-25405 transaction status unknown
Cause: A failure occurred while a transaction was attempting to commit. Failover could not automatically determine instance status.
Action: The user must determine the transaction's status manually.
ORA-25406 could not generate a connect address
Cause: Failover was unable to generate an address for a backup instance.
Action: Contact Oracle Support Services.
ORA-25407 connection terminated
Cause: The connection was lost while doing a fetch.
Action: This is an internally used error message and should not be seen by the user.
ORA-25408 can not safely replay call
Cause: The connection was lost while doing this call. It may not be safe to replay it after failover.
Action: Check to see if the results of the call have taken place, and then replay it if desired.
ORA-25425 connection lost during rollback
Cause: The connection was lost while issuing a rollback.
Action: If the transaction is not externally coordinated, then Oracle implicitly rolled back, so no action is required. Otherwise examine PENDING_TRANS$ to determine if ROLLBACK FORCE is required.
ORA-25426 remote instance does not support shared dblinks
Cause: A shared database link is being used to connect to a remote instance that does not support this feature because it is an older version.
Action: Use a normal database link if you need to connect to this instance.
ORA-25436 invalid table alias: string
Cause: An attempt to evaluate was made, which failed because one of the table values specified had an invalid alias.
Action: Check the valid table aliases in the evaluation context, and try again with a valid alias.
ORA-25437 duplicate table value for table alias: string
Cause: An attempt to evaluate was made, which failed because some of the table values specified had the same table alias.
Action: Check the table values specified, and try again with only one value per table.
ORA-25438 invalid variable name: string
Cause: An attempt to evaluate was made, which failed because one of the variable values specified had an invalid name.
Action: Check the valid variable names in the evaluation context, and try again with a valid name.
ORA-25439 duplicate variable value for variable: string
Cause: An attempt to evaluate was made, which failed because some of the variable values specified had the same variable name.
Action: Check the variable names specified, and try again with only one value per variable.
ORA-25440 invalid table alias: string
Cause: An attempt to evaluate was made, which failed because one of the column values specified had an invalid table alias.
Action: Check the valid table aliases in the evaluation context, and try again with a valid name.
ORA-25441 duplicate column value for table alias: string
Cause: An attempt to evaluate was made, which failed because one of the column values supplied a value for a table alias, which already had a table value supplied.
Action: Check the table and column values specified, and try again with either a table value or column values for each table alias.
ORA-25442 too many column values for table alias: string
Cause: An attempt to evaluate was made, which failed because too many column values were supplied for the specified table alias.
Action: Check the column values specified, and try again with the right number of column values.
ORA-25443 duplicate column value for table alias: string, column number: string
Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column number.
Action: Check the column values specified, and try again with only one column value for each table alias and column number.
ORA-25444 invalid ROWID: string for table alias: string
Cause: An attempt to evaluate was made, which failed because an invalid ROWID was supplied for the specified table alias.
Action: Check the column values specified, and try again with only one column value for each table alias and column number.
ORA-25445 invalid column number: string for table alias: string
Cause: An attempt to evaluate was made, which failed because an invalid column number was supplied for the specified table alias as a part of a column value.
Action: Check the column values specified, and try again with a valid column number.
ORA-25446 duplicate column value for table alias: string, column: string
Cause: An attempt to evaluate was made, which failed because duplicate column values were supplied for the specified table alias and column name.
Action: Check the specified column values, and try again with only one column value for each table alias and column name.
ORA-25447 encountered errors during evaluation of rule string.string
Cause: An attempt to evaluate was made, which failed during the evaluation of the specified rule.
Action: Check the rule and the values passed to evaluate, and try again with valid values.
ORA-25448 rule string.string has errors
Cause: An attempt to load the specified rule failed due to errors in the rule.
Action: Check the rule and retry the operation.
ORA-25461 rule set not specified
Cause: An attempt to evaluate was made, which failed because the ruleset name specified was null.
Action: Check the rule set name, and try again with a valid name.
ORA-25462 evaluation context not specified
Cause: An attempt to evaluate was made, which failed because the evaluation context specified was null.
Action: Check the evaluation context name, and try again with a valid name.
ORA-25463 table alias not specified
Cause: An attempt to evaluate was made, which failed because one of the table values specified had a NULL alias name.
Action: Check the list of table values, and try again with a valid alias name.
ORA-25464 ROWID not specified for table alias: string
Cause: An attempt to evaluate was made, which failed because the table value for the specified table alias had a NULL ROWID.
Action: Check the list of table values, and try again with a valid ROWID.
ORA-25465 variable name not specified
Cause: An attempt to evaluate was made, which failed because one of the variable values specified had a NULL variable name.
Action: Check the list of variable values, and try again with a valid variable name.
ORA-25466 data not specified for variable name: string
Cause: An attempt to evaluate was made, which failed because the variable value for the specified variable name had NULL data.
Action: Check the list of variable values, and try again with valid data.
ORA-25467 table alias not specified
Cause: An attempt to evaluate was made, which failed because one of the column values specified had a NULL alias name.
Action: Check the list of column values, and try again with a valid alias name.
ORA-25468 column name not specified for alias: string
Cause: An attempt to evaluate was made, which failed because one of the column values for the specified alias name had a NULL column name.
Action: Check the list of column values, and try again with a valid column name.
ORA-25469 data not specified for alias: string column name: string
Cause: An attempt to evaluate was made, which failed because the column value for the specified alias and column name had NULL data.
Action: Check the list of column values, and try again with valid data.
ORA-25500 database is not open
Cause: Database must be open to perform ALTER SYSTEM QUIESCE RESTRICTED command.
Action: Open the database and retry this command.
ORA-25501 ALTER SYSTEM QUIESCE RESTRICTED command failed
Cause: Database resource manager failed to change plan.
Action: Look at the alert logs to see a detailed description of the error.
ORA-25502 concurrent ALTER SYSTEM QUIESCE/UNQUIESCE command is running
Cause: There is a concurrent ALTER SYSTEM QUIESCE RESTRICTED or ALTER SYSTEM UNQUIESCE command running in the system.
Action: Contact the database administrator who is responsible for the concurrent command.
ORA-25503 cannot open database because the database is being quiesced
Cause: Database cannot be opened because the system is being or has been quiesced.
Action: Open the database after the system has been quiesced.
ORA-25504 the system is already in quiesced state
Cause: Cannot quiesce the system because the system is already quiesced.
ORA-25505 the system is not in quiesced state
Cause: Cannot unquiesce the system because the system is not in quiesced state.
ORA-25506 resource manager has not been continuously on in some instances
Cause: Cannot quiesce the system because resource manager has not been continuously on since startup in this or some other instances.
ORA-25507 resource manager has not been continuously on
Cause: Cannot quiesce the system because resource manager has not been continuously on since startup.
ORA-25508 database is not mounted
Cause: Database must be mounted to perform ALTER SYSTEM UNQUIESCE command.
Action: Mount the database and retry this command.
ORA-25509 operation on "string"."string".string not allowed
Cause: A column has been added to a replicated table, but replication support processing has not completed.
Action: Wait until replication support processing has completed before updating the column.
ORA-25526 bad format of _DB_MTTR_SIM_TARGET: string
Cause: One value in _DB_MTTR_SIM_TARGET is not a valid MTTR.
Action: Alter the value of _DB_MTTR_SIM_TARGET.
ORA-25527 bad format of _DB_MTTR_SIM_TARGET
Cause: One value in _DB_MTTR_SIM_TARGET is empty.
Action: Set the value of _DB_MTTR_SIM_TARGET properly.
ORA-25528 too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET
Cause: Too many candidate MTTRs are specified in _DB_MTTR_SIM_TARGET.
Action: Alter the value of _DB_MTTR_SIM_TARGET.
ORA-25530 FAST_START_MTTR_TARGET is not specified
Cause: An attempt to start MTTR advisory was made, which failed because FAST_START_MTTR_TARGET was not specified.
Action: Set FAST_START_MTTR_TARGET.
ORA-25531 MTTR specified is too small: number
Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too small for MTTR advisory.
Action: Set a larger FAST_START_MTTR_TARGET or candidate MTTR.
ORA-25532 MTTR specified is too large: number
Cause: The current FAST_START_MTTR_TARGET setting or a candidate MTTR setting is too large for MTTR advisory.
Action: Set a smaller FAST_START_MTTR_TARGET or candidate MTTR.
ORA-25950 missing where clause in join index specification
Cause: An attempt to create a join index was made, which failed because no valid where clause was found.
Action: Ensure that a where clause with valid join conditions is specified in the create index statement.
ORA-25951 join index where clause cannot contain OR condition
Cause: An attempt to create a join index was made, which failed because there was an OR branch in the where clause.
Action: Reformulate the where clause without using ORs.
ORA-25952 join index must only contain inner equi-joins
Cause: An attempt to create a join index was made, which failed because it included a predicate which wasn't an equi-inner join.
Action: Remove the inappropriate predicate.
ORA-25953 join index cannot be a functional index
Cause: An attempt to create a join index was made, which failed because a functional index was requested or necessary (such as is the case for indexing columns using timezone).
Action: Remove any functional indexing columns.
ORA-25954 missing primary key or unique constraint on dimension
Cause: An attempt to create a join index was made, which failed because one or more dimensions did not have an appropriate constraint matching the join conditions.
Action: Ensure that the where clause is correct (contains all of the constraint columns) and that an enforced constraint is on each dimension table.
ORA-25955 all tables must be joined in the where clause
Cause: An attempt to create a join index was made, which failed because one of the tables in the from clause did not appear in the where clause.
Action: Ensure that the where clause contains all from clause tables.
ORA-25956 join index cannot be created on tables owned by SYS
Cause: An attempt to create a join index was made, which failed because one of the tables was owned by SYS.
Action: Ensure that no join index related table is owned by SYS.
ORA-25957 join index where clause cannot contain cycles
Cause: An attempt to create a join index was made, which failed because the where clause contains a cycle.
Action: Ensure that the where clause is in the form of a star or snowflake schema.
ORA-25958 join index where clause predicate may only contain column references
Cause: An attempt to create a join index was made, which failed because a predicate in the where clause contained something other than a simple column.
Action: Ensure that the where clause only contains columns.
ORA-25959 join index must be of the bitmap type
Cause: An attempt to create a join index was made, which failed because no bitmap keyword was used.
Action: Make the index a bitmap index.
ORA-25960 join index cannot be based on a temporary table
Cause: An attempt to create a join index was made, which failed because one of the tables was temporary.
Action: Ensure no underlying tables are temporary.
ORA-25961 join index prevents dml cascade constraint operation
Cause: An attempt to execute dml resulted in the need to perform dml on another table because of a cascade constraint. The join index only allows one of its underlying tables to me modified at a time.
Action: Drop the join index or remove the constraint.
ORA-25962 join index prevents multitable insert or merge
Cause: An attempt to execute an merge or multitable insert on a table that was used to create a bitmap join index was made. Merge and multitable inserts are not supported on tables that were used to create a bitmap join index.
Action: Drop the join index.
ORA-25963 join index must be created on tables
Cause: An attempt to create a join index was made, which failed because the from clause contains non table object.
Action: Ensure that the from clause only contains tables.
ORA-25964 column type incompatible with join column type
Cause: The datatype of the join column is incompatible with the datatype of the joined column.
Action: Select a compatible datatype for the join column.
ORA-26000 partition load specified but table string is not partitioned
Cause: The Loader control file contains a PARTITION clause but the table being loaded is not partitioned.
Action: Remove the partition specification from the SQL*Loader control file and retry the load.
ORA-26001 Index string specified in SORTED INDEXES does not exist on table string
Cause: A non-existent index was specified in the SORTED INDEXES clause.
Action: Do not specify as a SORTED INDEX.
ORA-26002 Table string has index defined upon it.
Cause: Parallel load was specified into a table which has index defined upon it.
Action: Drop index(es) defined upon table, or do not use parallel load, or use SKIP_INDEX_MAINTENANCE option.
ORA-26003 parallel load not supported for index-organized table string
Cause: Parallel load is not supported for index-organized tables.
Action: Load the index-organized table without the PARALLEL option.
ORA-26004 Tables loaded through the direct path may not be clustered
Cause: An attempt was made to load a clustered table via the direct path.
Action: Use the conventional path.
ORA-26005 Invalid handle for direct path load
Cause: In direct path load, the handle passed in does not match the type listed.
Action: Verify the handle and type are correct.
ORA-26006 Incorrect bind variable in column string's sql expression - string
Cause: In direct path load, the bind variables listed in the sql expression do not match the input argument column names.
Action: Verify all the input arguments are listed in the expression as bind variables, and all the bind variables are listed as input arguments to the expression. Or verify that there were no errors in executing the OCI statements when getting the bind variable list.
ORA-26007 For INSERT option, table must be empty. Error on table string
Cause: The user tried to use the INSERT option on a non-empty table.
Action: Empty the table from SQL*Plus, or use the REPLACE option.
ORA-26008 NOT NULL column string has a nullif clause
Cause: A column which is NOT NULL in the database has a SQL*Loader NULLIF clause on it.
Action: Remove the NULLIF clause in the SQL*Loader control file.
ORA-26009 NOT NULL column string has a defaultif clause which may evaluate to null
Cause: A column which is NOT NULL in the database has a SQL*Loader DEFAULTIF clause which may evaluate to null.
Action: Remove the DEFAULTIF clause in the SQL*Loader control file.
ORA-26010 Column string in table string is NOT NULL and is not being loaded
Cause: A column which is NOT NULL in the database is not being loaded and will cause every row to be rejected.
Action: Load the column by specifying the NOT NULL column in the INTO TABLE clause in the SQL*Loader control file.
ORA-26011 Cannot load type string into column string in table string
Cause: A column can only store data of type declared for that column and a substitutable column can only store data of valid subtypes of the supertype declared for that column.
Action: Check that the type or subtype specified is valid for that column.
ORA-26012 No data found while executing sql statement string for column string - check input for: string
Cause: Executing sql statement against the data dictionary tables returned "ORA-01403: no data found".
Action: No data retrieved when selecting against the data dictionary tables most likely means that there's an error in user input. Check that the input listed is correct.
ORA-26013 List allocated may not be big enough
Cause: There seems to be a discrepancy between the size for a list or buffer allocated by direct path api and the size needed.
Action: Contact Oracle Support Services.
ORA-26014 OCI_ATTR_DIRPATH_SUBST_OBJ_TBL is set for non-final object table string
Cause: Client set OCI_ATTR_DIRPATH_SUBST_OBJ_TBL for either a non-object table or for a final object table. This attribute can only be, and must be, set for non-final object tables.
Action: Check the type of the loading table. Do not set this attribute if the table is not a non-final object table.
ORA-26015 Array column string in table string is not supported by direct path
Cause: User attempted to load an array column via the direct path.
Action: Use the conventional path.
ORA-26016 Record string: Rejected - Error on table string, partition string
Cause: The record indicated caused an Oracle error on insert.
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
ORA-26017 Global indexes not allowed on direct path partition load, table string
Cause: Global indexes are defined on a table when direct path loading a single partition of the table.
Action: Remove the global index from the named table and retry the operation.
ORA-26018 Column string in table string does not exist
Cause: Column specified in the loader control file does not exist.
Action: Make sure the column exists and that you have privileges on it. Correct the loader control file if it is wrong.
ORA-26019 Column string in table string of type string not supported by direct path
Cause: The specified column of SQL column type string is not supported by the direct path loader.
Action: If the column is NULLable, remove it from the control file description. Then it will be loaded as a NULL.
ORA-26020 index string.string loaded successfully with string keys
Cause: Non-partitioned index information put to loader log file.
Action: No action required. This is an informational message.
ORA-26021 index string.string partition string loaded successfully with string keys
Cause: Partitioned index information put to loader log file.
Action: No action required. This is an informational message.
ORA-26022 index string.string was made unusable due to:
Cause: A non-partitioned index was made index unusable due to the error displayed below this error.
Action: Depending on the error, either rebuild the index, or drop and re-create it.
ORA-26023 index string.string partition string was made unusable due to:
Cause: A partition of a partitioned index was made index unusable due to error displayed below this error.
Action: Depending on the error, either rebuild the index partition, or drop and re-create the entire index.
ORA-26024 SKIP_UNUSABLE_INDEXES requested and index segment was initially unusable
Cause: User requested SKIP_UNUSABLE_INDEXES option, and the index segment was in unusable state prior to the beginning of the load.
Action: Informational only. User will need to either rebuild the index or index partition, or re-create the index.
ORA-26025 SKIP_INDEX_MAINTENANCE option requested
Cause: A request was made that index maintenance be skipped on a direct path load.
Action: The listed index was put into Index Unusable state due to the user requesting that index maintenance be skipped. Either rebuild the index or index partitions, or drop and re-create the index.
ORA-26026 unique index string.string initially in unusable state
Cause: A unique index is in IU state (a unique index cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).
Action: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
ORA-26027 unique index string.string partition string initially in unusable state
Cause: A partition of a unique index is in IU state (a unique index cannot have index maintenance skipped via SKIP_UNUSABLE_INDEXES).
Action: Either rebuild the index or index partition, or use SKIP_INDEX_MAINTENANCE if the client is SQL*Loader.
ORA-26028 index string.string initially in unusable state
Cause: An index is in IU state prior to the beginning of a direct path load, it cannot be maintained by the loader.
Action: Either rebuild the index, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only).
ORA-26029 index string.string partition string initially in unusable state
Cause: A partition of an index is in IU state prior to the beginning of a direct path load, it cannot be maintained by the loader.
Action: Either rebuild index partition, re-create the index, or use either SKIP_UNUSABLE_INDEXES or SKIP_INDEX_MAINTENANCE (SQL*Loader only).
ORA-26030 index string.string had string partitions made unusable due to:
Cause: A logical index error occurred on a partitioned index which affected one or more index partitions, which are listed below this message.
Action: The affected index partitions will have to be rebuilt, or, the entire index dropped and re-created.
ORA-26031 index maintenance error, the load cannot continue
Cause: A index error occurred during the index maintenance phase of a direct path load. The load cannot continue. See error message below this message.
Action: See action for the error message which follows this one.
ORA-26032 index string.string loading aborted after string keys
Cause: An index error occurred during direct-load of an index-organized table. Loading had to be aborted. No rows were loaded.
Action: Check the key just following the number of keys mentioned above. This key caused the index problem mentioned in an earlier message.
ORA-26033 error while evaluating index string.string, row string due to:
Cause: An index error occurred while attempting to evaluate an expression on a functional index.
Action: Verify that the input data is valid for the functional index.
ORA-26034 end of logical record found when reading length of varying length field
Cause: While attempting to read the length portion of a varying length field, then end of the logical record was reached.
Action: Verify that the control file describes the data correctly and that the data in the datafile matches the description in the control file
ORA-26035 Record string: Rejected - Error on table string, subpartition string
Cause: The record indicated caused an Oracle error on insert.
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
ORA-26036 subpartition load specified but table string is not subpartitioned
Cause: The Loader control file contains a PARTITION clause but the table being loaded is not subpartitioned.
Action: Remove the subpartition specification from the SQL*Loader control file and retry the load.
ORA-26037 Record string: Rejected - Error on table string, subpartition string
Cause: The record indicated caused an Oracle error on insert.
Action: Determine the Oracle error and correct the record. The offending column(s) are not known.
ORA-26038 error converting character length field to a number
Cause: An error occurred while attempting to convert the characters containing the count portion of a VARCHARC or VARRAWC field.
Action: Verify that the count portion for the field has the correct value.
ORA-26039 Table string has domain index defined upon it
Cause: Direct path load was specified for a table which has a domain index defined upon it.
Action: Drop domain index(es) defined on the table or use the conventional path.
ORA-26040 Data block was loaded using the NOLOGGING option
Cause: An attempt was made to access data in a block that was loaded without redo generation using the NOLOGGING/UNRECOVERABLE option.
Action: Drop the object containing the block.
ORA-26041 DATETIME/INTERVAL datatype conversion error
Cause: The column could not be converted from DATETIME datatype to internal DATETIME/CHARACTER datatype.
Action: Contact Oracle Support Services.
ORA-26042 unable to convert format string into internal form
Cause: An attempt to convert a DATETIME format string into internal format in preparation for DATETIME datatype processing failed.
Action: Contact Oracle Support Services.
ORA-26043 unable to convert time zone for DATETIME/INTERVAL processing
Cause: An attempt to convert the time zone specified by the ORA_STDZ environment variable to internal format failed.
Action: Verify that the setting for ORA_STDZ is valid.
ORA-26044 unable to to get DATETIME/INTERVAL reference date
Cause: An attempt to retrieve the system reference date for DATETIME/INTERVAL datatypes failed.
Action: Contact Oracle Support Services.
ORA-26045 REF column string expects string arguments; found string.
Cause: The number of arguments for the REF column is incorrect.
Action: Specify the correct number of input arguments for REFs.
Unscoped system-generated REFs can have exactly 1 or 2 input arguments.
It has exactly 1 input argument (one for the OID value) if a fixed table name was specified through OCI_DIRPATH_EXPR_REF_TBLNAME.
It has exactly 2 input arguments (one for the table name and one for the OID value) if a fixed table name was not specified through OCI_DIRPATH_EXPR_REF_TBLNAME.
Scoped system-generated REFs can have 1 or 2 input arguments.
Because a table name argument is not needed for a scoped ref, only 1 argument (OID value) is expected. But if the table name argument is given, it's still accepted.
Scoped primary-key REFs with N columns in its primary-key OID can have N or N+1 input arguments.
Because a table name argument is not needed for a scoped ref, only N arguments (making up the OID value) is expected. But if the table name argument is given, it's still accepted.
ORA-26046 REF column string expects scoped table name string; user passed in string.
Cause: The scoped table name passed in by the user does not match the name in the schema.
Action: Specify the correct table name for the scoped REF column.
ORA-26047 REF column has invalid value for system generated oid
Cause: The value passed in by the user for the system generated oid does not consist of valid hexadecimal digits.
Action: Specify a valid oid value for the REF column.
ORA-26048 Scoped REF column has wrong table name.
Cause: The scoped table name passed in by the user does not match the name in the schema.
Action: Specify the correct table name for the scoped REF column.
ORA-26049 Unscoped REF column has non-existent table name.
Cause: The table name passed in by the user does not exist in the schema.
Action: Specify a valid table name for the unscoped REF column.
ORA-26050 Direct path load of domain index is not supported for this column type.
Cause: Direct path can not load a domain index of that column type.
Action: Drop the index and try again or load using conventional path.
ORA-26051 internal error parsing packed decimal format string
Cause: A packed decimal field with a nonzero scale factor is mapped to a character column. In order to perform the datatype conversion, a numeric format string must be created based on the input field's precision and scale specifications. Direct path loader encountered an error in creating this format string.
Action: Examine the packed decimal field's precision and scale specifications and make sure that they contain valid values.
ORA-26052 Unsupported type number for SQL expression on column string.
Cause: The direct path api does not support a SQL expression on a column of that type.
Action: Make sure the types are correct.
ORA-26076 cannot set or reset value after direct path structure is allocated
Cause: Client attempted to set or reset the number of rows in a direct path structure after it has already been allocated and initialized. Attributes used is one of the following:
OCI_ATTR_NUM_ROWS: to set # of rows in a direct path column array
OCI_ATTR_DIRPATH_DCACHE_SIZE: to set size of a date cache (default is 0)
OCI_ATTR_DIRPATH_DCACHE_DISABLE: to set whether date cache will be disabled on overflow (default is FALSE)
Action: Set the following attributes before:
OCI_ATTR_NUM_ROWS: before calling OCIHandleAlloc for column array
OCI_ATTR_DIRPATH_DCACHE_SIZE: before calling OCIDirPathPrepare
OCI_ATTR_DIRPATH_DCACHE_DISABLE: before calling OCIDirPathPrepare
ORA-26077 direct path column array is not initialized
Cause: Client attempted to allocate a column array for a direct path function context before allocating a column array for the table-level direct path context.
Action: Allocate the table-level direct path context's column array via OCIHandleAlloc before allocating column arrays for direct path function contexts.
ORA-26078 file string is not part of database being loaded
Cause: A parallel load file was specified which is not part of the database.
Action: Check filename and pathname for correctness.
ORA-26079 file string is not part of table string.string
Cause: A parallel load file was specified which is not in the tablespace of the table being loaded.
Action: Check to make sure that the specified parallel load file is in the tablespace of the table being loaded.
ORA-26080 file string is not part of table string.string partition string
Cause: A parallel load file was specified which is not in the tablespace of the table (partition, subpartition) being loaded. When a partitioned table is being loaded, the file must be in the tablespace of every partition or subpartition (that is, each (sub)partition must be in the same tablespace).
Action: Specify a different parallel load file, or no file at all.
ORA-26081 load stream synchronization error
Cause: The row header flag byte contains an unexpected value, this indicates that an error has occurred in either the generation of, or the pushing of the load stream from the client to the server.
Action: Usually due to an application programming error when dealing with error handling, or not resetting the stream state.
ORA-26082 load of overlapping segments on table string.string is not allowed
Cause: Client application is attempting to do multiple direct path load operations on the same table, but the segments overlap.
Action: Check the partition names (subname attribute of the direct path context) being loaded. Make sure you are not loading a table and a partition of the same table. Make sure you are not loading a partition, and a sub-partition within the same partition.
ORA-26084 direct path context already finished
Cause: An OCIDirPathLoadStream operation was attempted after OCIDirPathFinish was called. Once a direct path operation has been finished, no more data can be loaded.
Action: Check program logic to make sure OCIDirPathLoadStream is not called after OCIDirPathFinish.
ORA-26085 direct path operation must start its own transaction
Cause: A direct path operation is being attempted within a transaction that has already been started.
Action: Commit the transaction and Prepare the direct path operation again.
ORA-26086 direct path does not support triggers
Cause: A direct path operation is being attempted on a table which has enabled triggers.
Action: Disable the triggers on the table and try again.
ORA-26087 direct path does not support referential constraints
Cause: A direct path operation was attempted on a table which has enabled referential integrity constraints.
Action: Disable the referential integrity constraints on the table and try again.
ORA-26088 scalar column 'string' must be specified prior to LOB columns
Cause: All scalar columns (that is, non-LOB and non-LONG columns) must be specified by the client of the direct path API prior to specifying any LOB columns.
Action: Specify all scalar columns prior to specifying any LOB columns.
ORA-26089 LONG column 'string' must be specified last
Cause: A client of the direct path API specified a LONG column to be loaded, but the LONG column was not the last column to be specified.
Action: Specify the LONG column last.
ORA-26090 row is in partial state
Cause: A direct path operation is being finished or a data save request has been made, but the table for which the request is being made on has a row in partial state. The row must be completed before the segment high water marks can be moved.
Action: Either complete the row, or abort the direct path operation.
ORA-26091 requested direct path operation not supported
Cause: A direct path operation was requested that is not supported
Action: Do not use that operation. Currently, UNLOAD is not supported.
ORA-26092 only LONG or LOB types can be partial
Cause: A column which is not a LONG or LOB had the OCI_DIRPATH_COL_PARTIAL flag associated with it. Only LONG or LOB type columns can be loaded in pieces.
Action: Do not use the OCI_DIRPATH_COL_PARTIAL flag for the column.
ORA-26093 stream offset does not map to a column array
Cause: The ROW_COUNT attribute was being read from a direct path stream handle and it was found that the stream offset for the last processed row did not map to a column array offset.
Action: Make sure the stream was sourced from a column array.
ORA-26094 stream format error: input column overflow
Cause: An input stream contained data for more input columns than specified by the client of the direct path API.
Action: Make sure that the stream being loaded is for the correct table. Check initialization sequence.
ORA-26095 unprocessed stream data exists
Cause: Either a OCIDirPathLoadStream call was made which provided more stream data prior to the server being able to fully process the stream data that it already has, or a OCIDirPathFinish call was made when the server had unprocessed stream data.
Action: Most likely an application misuse of the direct path API. Make sure that the stream is not being reset inadvertently prior to any previous stream data being processed, or, that OCIDirPathFinish is not being called prematurely (that is, stream pushed, error encountered and LoadStream not called to process the remainder of the stream before Finish is called).
ORA-26096 transfer size too small for row data (number bytes required)
Cause: Either the transfer buffer size specified, or the default transfer buffer size (if you did not specify a size), is too small to contain a single row of the converted row data.
Action: Set the transfer buffer size attribute of the direct path context to be larger.
ORA-26097 unsupported conversion for column string (from type number to type number)
Cause: The direct path API does not support the required conversion.
Action: Make sure the types are correct.
ORA-26098 direct path context is not prepared
Cause: A direct path API function was called with a direct path context which has not been prepared.
Action: Make sure all necessary attributes in the direct path context have been set, and the context is prepared via OCIDirPathPrepare.
ORA-26099 direct path context is already prepared
Cause: OCIDirPathPrepare was called with a context that has already been prepared.
Action: Free the direct path context, set necessary attributes, and call OCIDirPathPrepare.
ORA-26100: unused error
Cause: This error is not used.
Action: No action required.
ORA-26101 tablespace # in file header is string rather than string for file string
Cause: The tablespace number in the file header is inconsistent with that in the control file.
Action: Check if the control file has been migrated correctly. Retry with the correct control file and datafile.
ORA-26102 relative file # in file header is string rather than string for file string
Cause: The relative file number in the file header is inconsistent with that in the control file.
Action: Check if the control file has been migrated correctly. Retry with the correct control file and datafile.
ORA-26103 V6 or V7 data file used to create control file
Cause: The file header of the referenced file is in V6 or V7 format.
Action: Either remove the file from the create control file command, or somehow migrate the file header to V8 format.
ORA-26500 error on caching "string"."string"
Cause: Attempt to cache the replication information which is unavailable in the catalog for the object.
Action: Use DBMS_REPUTIL.SYNC_UP_REP to validate the replication catalog, or use DBMS_REPUTIL.MAKE_INTERNAL_PKG to validate internal package.
ORA-26501 RepAPI operation failure
Cause: An external RepAPI operation failed.
Action: Consult detail error message.
ORA-26502 error resignal
Cause: An internal service failed and signalled an error.
Action: Consult detail error message.
ORA-26503 internal RepAPI operation failure on object string.string
Cause: An unexpected internal RepAPI failure was detected.
Action: Contact Oracle Support Services.
ORA-26504 operation not implemented
Cause: The caller requested a RepAPI operation that was not implemented.
Action: Do not issue this call.
ORA-26505 unexpected internal null
Cause: An internal buffer control structure was NULL.
Action: Verify that sufficient memory resources are available to RepAPI.
ORA-26506 null global context
Cause: An internal buffer control structure was NULL.
Action: Verify that sufficient memory resources are available to RepAPI.
ORA-26507 null master connection
Cause: The master connection handle was or became invalid.
Action: Verify that the master connection is valid.
ORA-26508 null materialized view connection
Cause: The client connection handle was or became invalid.
Action: Verify that the client connection is valid.
ORA-26509 null materialized view control structure
Cause: An internal materialized view control structure could not be obtained.
Action: Check that the owner and users provided are correct.
ORA-26510 materialized view name: 'string' is greater than max. allowed length of string bytes
Cause: The specified materialized view name was too long.
Action: Shorten the materialized view name.
ORA-26511 master table 'string.string' not found
Cause: A RepAPI operation was attempted against a non-existent or invalid master table.
Action: Verify that the master table object exists.
ORA-26512 error pushing transaction to def$error
Cause: An unexpected error occurred while sending an DEF$ERROR RPC to the master site.
Action: Verify that the DBMS_DEFER package is valid and executable by the RepAPI client. Contact the local or master site administrator, if necessary.
ORA-26513 push error: master proc. string$RP.string failed for trans:string seq:string
Cause: A conflict/error occurred at the master site while executing a $RP.rep_insert(), rep_update(), or rep_delete() function which was not handled by conflict resolution logic at the master.
Action: Notify master site system administrator or database administrator.
ORA-26514 object 'string.string' not found
Cause: The specified object was expected but not found.
Action: Verify that the specified object exists and is valid.
ORA-26515 no master log available for 'string.string'
Cause: The specified master log was not found or available for the named table.
Action: Create the master log at the master site or correct any problems that may exist with the log.
ORA-26516 no push transaction acknowledgement
Cause: RepAPI was unable to confirm that the last pushed transaction was successfully committed by the master site.
Action: Verify that the communications link between the local site and the master site is still valid. If the transaction has not been committed at the master, repush the transaction.
ORA-26517 materialized view control entry for 'string.string' was not found
Cause: The specified materialized view catalog control record was not found.
Action: Verify that the local materialized view catalog is valid and that the local materialized view is properly defined.
ORA-26518 push queue synchronization error detected
Cause: Client tried to repush a transaction has already been committed at the master site. A common cause of this problem is an error at the local site in initializing or updating the local site transaction sequence mechanism.
Action: Verify that transaction data that RepAPI was attempting to repushed to the master site exists at the master table and is valid and consistent with the local site. If this error occurs, redundantly identified transactions are ignored and then purged from the local updatable materialized view logs. Check that the local site is correctly assigning new transaction IDs and is not accidently generating non-unique values.
ORA-26519 no memory available to allocate
Cause: There was no memory left for the RepAPI process. This error may occur when RepAPI is trying to allocate a new table buffer area.
Action: Shut down one or more local applications to attempt to free heap memory and retry the RepAPI operation.
ORA-26520 internal memory failure
Cause: An internal memory error was detected.
Action: Check if other errors have occurred or determine if any local application may have corrupted the memory subsystem.
ORA-26521 rpc initialization error
Cause: An error occurred during the initialization of a PL/SQL RPC.
Action: Verify that the procedure to be invoked exists and is valid at the master site and is executable by the RepAPI user.
ORA-26522 rpc execution error
Cause: An error occurred during the execution of a PL/SQL RPC.
Action: Check the error messages from the remote procedure and fix any remote site problems that may be preventing the execution of the invoked RPC.
ORA-26523 rpc termination error
Cause: An error occurred during the termination of a PL/SQL RPC. This is usually caused by master site being unable to close an opened cursor or if RepAPI cannot deallocate internal memory.
Action: Fix any server side problems first, determine if the RepAPI memory subsystem has been corrupted.
ORA-26524 nls subsystem initialization failure for product=string, facility=string
Cause: The NLS product/facility error message file could not be located or properly initialized.
Action: Check that the error message directory and file(s) have been properly installed.
ORA-26525 session connection attempt failed for string (@string)
Cause: A connection could not be established to the specified database using the provided connection string.
Action: Check that the user, password, connect string, names services, network, and any remote site listener process are properly installed and working.
ORA-26526 materialized view sql ddl parse/expansion failed for string.string
Cause: The client SQL materialized view definition query could not be properly parsed by the master Oracle site.
Action: Check that materialized view DDL SQL is compatible with the currently connected version of Oracle and does not violate any of the RepAPI SQL limitations or restrictions.
ORA-26527 local store callback init phase failed for 'string.string'
Cause: The client callback failed during its INIT phase for the named object.
Action: Verify that the objects referenced by the client callback exist and are valid. Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Support Services.
ORA-26528 local store callback proc phase failed for 'string.string'
Cause: The client callback failed during its PROC phase for the named object.
Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Support Services.
ORA-26529 local store callback term phase failed for 'string.string'
Cause: The client callback failed during its TERM phase for the named object.
Action: Refer to the vendor-specific callback error code reference to diagnose the local problem. Record all error states and notify Oracle Support Services.
ORA-26530 unable to build materialized view refresh control list
Cause: The materialized view control list could not be constructed. This is generally the result of an error while accessing the local materialized view catalog.
Action: Verify that the named materialized view(s) are properly defined and valid.
ORA-26532 replication parallel push simulated site failure
Cause: A parallel push executed with event 26531 enabled raises this error to simulation failure of network or destination site.
Action: Do not enable the event for normal operation.
ORA-26534 collision: tranID number ignored and purged
Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.
Action: See the action section for E_QUEUESYNC (26518).
ORA-26535 number byte row cache insufficient for table with rowsize=number
Cause: A transaction that was pushed had a transaction ID that collided with a transaction that was previously pushed and committed at the master site.
Action: Increase the RepAPI row buffer size or reduce the width of the replicated tables.
ORA-26536 refresh was aborted because of conflicts caused by deferred transactions
Cause: There are outstanding conflicts logged in the DEFERROR table at the materialized view's master site.
Action: Resolve the conflicts in the master DEFERROR table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS, even if there are conflicts in the master's DEFERROR table. Proceeding despite conflicts can result in an updatable materialized view's changes appearing to be temporarily lost, until a refresh succeeds after the conflicts are resolved.
ORA-26563 renaming this table is not allowed
Cause: Attempt to rename a replicated table, an updatable materialized view table or the master table of a materialized view for which a materialized view log has been created.
Action: If desired, unregister the replicated table with DBMS_REPCAT.DROP_MASTER_REPOBJECT, or use the recommended procedure to rename the master table of a materialized view.
ORA-26564 string argument is not of specified type
Cause: User passed type of the given argument number does not match with the type of the argument in the stored arguments.
Action: Invoke correct type procedure (that is, get_XXX_arg).
ORA-26565 Call to type_arg made before calling dbms_defer.call
Cause: User invoked type_arg procedure before starting a deferred call.
Action: Invoke various procedures in the correct order.
ORA-26566 Couldn't open connect to string
Cause: Failed to open connection using given database link.
Action: Make sure that the database link is valid and remote m/c is up.
ORA-26571 string.string.string: number of arguments (string) does not match replication catalog
Cause: The number of arguments does not match the replication catalog.
Action: Examine the total number of arguments for the RPC call.
ORA-26572 string.string.string: argument string does not match replication catalog
Cause: The (RPC) call is corrupted.
Action: Examine total number of arguments and each argument for the RPC call.
ORA-26575 remote database does not support replication parallel propagation
Cause: The remote database has a version lower than Oracle 8.0 and hence does not understand replication parallel propagation.
Action: Use serial propagation or upgrade the remote database to Oracle 8.0 or above.
ORA-26650 string background process string might not be started successfully
Cause: An error occurred during creation of a capture or apply background process.
Action: Review V$Capture and V$Apply_coordinator views for the status of these processes. Also check the trace file for more information.
ORA-26660 Invalid action context value for string
Cause: The value specified in the action context is invalid for use in STREAMS.
Action: Check that the type and value are correct.
ORA-26665 STREAMS process string already exists
Cause: An attempt was made to create a STREAMS process that already exists.
Action: Either specify another STREAMS process or remove the existing STREAMS process.
ORA-26666 cannot alter STREAMS process string
Cause: An attempt was made to alter a STREAMS process that is currently running.
Action: Stop the STREAMS process and re-issue the command.
ORA-26667 invalid STREAMS parameter string
Cause: An attempt was made to specify an invalid parameter.
Action: Check the documentation for valid parameters.
ORA-26669 parameter string inconsistent with parameter string
Cause: An attempt was made to specify a subprogram parameter value that is inconsistent with another parameter value.
Action: Check the documentation for valid parameter values.
ORA-26670 STREAMS option requires COMPATIBLE parameter to be string or higher
Cause: Streams requires compatibility to be 9.2.0 or higher.
Action: Shut down and restart with an appropriate compatibility setting.
ORA-26671 maximum number of STREAMS processes exceeded
Cause: Cannot create additional STREAMS processes since the maximum number of STREAMS processes has been reached.
Action: Remove existing STREAMS processes and retry the operation.
ORA-26672 timeout occurred while stopping STREAMS process string
Cause: Timeout occurred while waiting for a STREAMS process to shut down.
Action: Retry the operation. If the error persists, then try stopping the process with the FORCE option, or contact Oracle Support Services.
ORA-26680 object type not supported
Cause: The specified object type is not supported.
Action: Retry with a supported object type.
ORA-26681 command type not supported
Cause: The specified command type is not supported.
Action: Retry with a supported command type.
ORA-26682 invalid value for publication_on
Cause: The publication_on parameter should be either 'Y' or 'N'.
Action: Retry with a proper value for publication_on.
ORA-26683 invalid value for value_type
Cause: The value_type parameter should be either 'OLD' or 'NEW'.
Action: Retry with proper value_type.
ORA-26684 invalid value for value_type
Cause: The value_type parameter should be one of 'OLD', 'NEW', or '*'.
Action: Retry with proper value_type.
ORA-26685 cannot apply transactions from multiple sources
Cause: Transactions from multiple sources were sent to the same apply process.
Action: Create multiple apply processes and create appropriate rules so that transactions from only one source reach an apply process.
ORA-26686 cannot capture from specified SCN
Cause: An attempt was made to specify an invalid SCN.
Action: Retry with a valid SCN.
ORA-26687 no instantiation SCN provided
Cause: Object SCN has not been set.
Action: Set the SCN by calling DBMS_APPLY_ADM.SET_INSTANTIATION_SCN.
ORA-26688 missing key in LCR
Cause: Metadata mismatch, or not enough information in the user generated LCR.
Action: Alter the database object, or provide all defined keys in the LCR.
ORA-26689 column datatype mismatch in LCR
Cause: The datatypes of columns in the LCR are not the same as the datatypes in the database object.
Action: Alter the database object.
ORA-26690 datatype not supported at non-Oracle system
Cause: One of the columns of the LCR being applied was of a datatype not supported by either the target non-Oracle system or by the Oracle transparent gateway through which the apply is being done.
Action: Do not apply data of this type. If possible, filter out columns containing such datatypes before applying.
ORA-26691 operation not supported at non-Oracle system
Cause: The apply process attempted an operation that is either not supported by the non-Oracle system or by the Oracle transparent gateway through which the apply is being done. Some kinds of DML (like procedure and function calls) and all DDL will cause this error to be raised.
Action: Do not attempt to apply such LCRs to non-Oracle systems. If possible, filter out such LCRs before applying.
ORA-26701 STREAMS process string does not exist
Cause: An attempt was made to access a STREAMS process which does not exist.
Action: Check with the relevant security views for the correct name of the object.
ORA-27000 skgfqsbi: failed to initialize storage subsystem (SBT) layer
Cause: SBTINIT returned an error, additional information indicates error.
Action: Verify that vendor's storage subsystem product is operating correctly.
ORA-27001 unsupported device type
Cause: The specified device type is supported on this platform.
Action: Check V$BACKUP_DEVICE for supported device types.
ORA-27002 function called with invalid device structure
Cause: An internal error occurred. Additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27003 cannot open file on device allocated with NOIO option
Cause: An internal error occurred. A file is being created/retrieved on a device allocated with NOIO option, additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27004 invalid blocksize specified
Cause: An internal error occurred. The block size specified is incorrect for the device on which file is being created, additional information indicates block size specified, and the function that encountered the error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27005 cannot open file for async I/O on device not supporting async
Cause: An internal error occurred. A file is being opened for asynchronous I/O on a device that does not support asynchronous I/O, additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27006 sbtremove returned error
Cause: Additional information indicates error returned by SBTREMOVE, and the function that encountered the error.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27007 failed to open file
Cause: SBTOPEN returned error, additional information indicates error returned from SBTOPEN, and the function that encountered the error.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27008 function called with invalid file structure
Cause: An internal error occurred. Additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27009 skgfwrt: cannot write to file opened for read
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27010 skgfwrt: write to file failed
Cause: SBTWRITE returned error, additional information indicates error returned from SBTWRITE.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27011 skgfrd: cannot read from file opened for write
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27012 skgfrd: read from file failed
Cause: SBTREAD returned error, additional information indicates error returned from SBTREAD.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27013 skgfqdel: cannot delete an open file
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27014 skgfqpini: translation error while expanding SS_UDMPDIR
Cause: Failure of SLTLN in SKGFQPINI.
Action: Check additional return error for more information.
ORA-27015 skgfcls: failed to close the file
Cause: SBTCLOSE returned an error. Additional information indicates error returned from SBTCLOSE.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27016 skgfcls: sbtinfo returned error
Cause: Additional information indicates error returned from SBTINFO.
Action: Verify that the vendor's storage subsystem product is operating correctly.
ORA-27017 skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)
Cause: Media handle string length exceeds SSTMXQMH.
Action: Verify that the vendor's storage subsystem product is operating correctly, and that the platform limit (SSTMXQMH) is at least 64 (the limit specified for SBTINFO). additional information indicates the media handle string length returned by SBTINFO, and the limit (SSTMXQMH).
ORA-27018 BLKSIZE is not a multiple of the minimum physical block size
Cause: User-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size that is permitted on this platform.
Action: Two ADDITIONAL INFORMATION messages are displayed which show the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integral multiple of the minimum block size.
ORA-27019 tape filename length exceeds limit (SBTOPMXF)
Cause: The length of the tape file name provided to sequential I/O OSD functions is too long.
Action: Additional information indicates in which function this error is encountered, the length of file name provided, and the limit on file name.
ORA-27020 named devices not supported
Cause: The platform or the specified device type does not support named devices.
Action: Do not specify device name or use a device type that supports named devices. Use V$BACKUP_DEVICE view to see what device types and names (if any) are available.
ORA-27021 sequential file handle must be specified
Cause: The file name which will be passed to SBTOPEN was not specified.
Action: Specify a file name and continue. If this is a backup set being created via Recovery Manager, use the 'format' option to specify the backup piece handle name.
ORA-27022 skgfqsbi: could not allocate memory for media manager
Cause: Oracle could not allocate memory required by the media management software which is linked with Oracle to provide backup/restore services.
Action: Increase the amount of memory available to the Oracle process and retry the backup/restore.
ORA-27023 skgfqsbi: media manager protocol error
Cause: The media management software which is linked with Oracle to provide backup/restore services did not provide its function pointer structure to Oracle. This is an internal error in the media management product.
Action: Contact the media management vendor.
ORA-27024 skgfqsbi: sbtinit2 returned error
Cause: SBTINIT2 returned an error. This happens during a backup or restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27025 skgfqsbi: invalid media manager context area size
Cause: The media management software requested a context area size which is greater than the maximum allowable size. This is an internal error in the media management product.
Action: Contact the media management vendor.
ORA-27026 skgfrls: sbtend returned error
Cause: SBTEND returned an error. This happens during a backup or restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27027 sbtremove2 returned error
Cause: SBTREMOVE2 returned an error. This happens when deleting a backup file.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27028 skgfqcre: sbtbackup returned error
Cause: SBTBACKUP returned an error. This happens when creating a backup file during a backup operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27029 skgfrtrv: sbtrestore returned error
Cause: SBTRESTORE returned an error. This happens when retrieving a backup file during a restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27030 skgfwrt: sbtwrite2 returned error
Cause: SBTWRITE2 returned an error. This happens while writing a backup file during a backup operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27031 mirror resilvering functions not supported
Cause: An internal error occurred.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27032 skgfrpini: failed to obtain file size limit
Cause: GETRLIMIT system call returned an error.
Action: Check errno.
ORA-27033 skgfrpini: failed to obtain file size limit
Cause: ULIMIT system call returned an error.
Action: Check errno.
ORA-27034 skgfrcre: maximum length of ORACLE_SID exceeded
Cause: Too many characters in the ORACLE_SID string.
Action: Rename the ORACLE_SID to a string of up to the maximum number of characters specified for your system.
ORA-27035 logical block size is invalid
Cause: Logical block size for Oracle files must be a multiple of the physical block size, and less than the maximum.
Action: Block size specified is returned as additional information, check initialization parameters, additional information also indicates which function encountered the error.
ORA-27036 translation error, unable to expand file name
Cause: Additional information indicates SLTLN/SLNRM error, and also indicates which function encountered the error.
Action: Check additional information.
ORA-27037 unable to obtain file status
Cause: STAT system call returned an error, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27038 skgfrcre: file exists
Cause: Trying to create a database file, but file by that name already exists.
Action: Verify that name is correct, specify reuse if necessary.
ORA-27039 create file failed, file size limit reached
Cause: An attempt was made to create a file that exceeds the process' file size limit, additional information indicates which function encountered the error.
Action: Raise the file size limit.
ORA-27040 skgfrcre: create error, unable to create file
Cause: Create system call returned an error, unable to create file.
Action: Verify the file name and permissions.
ORA-27041 unable to open file
Cause: Open system call returned an error, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27042 not enough space on raw partition to fullfill request
Cause: This is an internal error. The file is too large for the raw partition. Additional information indicates which function encountered the error.
Action: Check for trace file and contact Oracle Support Services.
ORA-27043 unable to seek to beginning of file
Cause: Seek system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27044 unable to write the header block of file
Cause: Write system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27045 unable to close the file
Cause: Close system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27046 file size is not a multiple of logical block size
Cause: File size as indicated by STAT is not correct, additional information indicates which function encountered the error.
Action: Verify that the file has not been overwritten or truncated.
ORA-27047 unable to read the header block of file
Cause: Read system call failed, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27048 skgfifi: file header information is invalid
Cause: Possibly trying to use a non-database file as a database file.
Action: Verify that file is a database file.
ORA-27049 unable to seek to and read the last block
Cause: An attempt was made to seek to and read the last block in file, additional information indicates which function encountered error.
Action: Check errno.
ORA-27050 function called with invalid FIB/IOV structure
Cause: This is an internal error. Additional information indicates which function encountered error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27052 unable to flush file data
Cause: FSYNC system call returned error, additional information indicates which function encountered the error.
Action: Check errno.
ORA-27053 skgfifi: blocksize in file header not a multiple of logical block size
Cause: The logical block size is invalid, additional information indicates the logical block size and the block size in the file header.
Action: Use a different logical block size, or do not reuse file.
ORA-27056 skgfrdel: could not delete file
Cause: Unlink system call returned error.
Action: Check errno.
ORA-27057 skgfask: cannot perform async I/O to file
Cause: This is an internal error. The query is being asked about asynchronous vector I/O when the file does not support asynchronous I/O.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27058 skgfask: question parameter is invalid
Cause: This is an internal error. An invalid query is being asked.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27059 skgfrsz: could not reduce file size
Cause: FTRUNCATE system call returned error.
Action: Check errno.
ORA-27060 skgfofi: could not set close-on-exec bit on file
Cause: FCNTL system call returned error.
Action: Check errno.
ORA-27061 skgfospo: waiting for async I/Os failed
Cause: AIOWAIT function returned error.
Action: Check errno.
ORA-27062 skgfospo: could not find pending async I/Os
Cause: There should have been some asynchronous I/Os in the system but a blocking aiowait indicates that there are no more I/Os. It could be due to an Oracle bug, a vendor OS bug, or an NFS server not responding.
Action: Check the Oracle trace file, OS message files, and contact Oracle Support Services.
ORA-27063 skgfospo: number of bytes read/written is incorrect
Cause: The number of bytes read/written as returned by AIOWAIT does not match the original number, additional information indicates both these numbers.
Action: Check errno.
ORA-27064 skgfdisp: cannot perform async I/O to file
Cause: This is an internal error. A request was made to perform asynchronous I/O when IOV indicates that it cannot be performed on the file.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27065 skgfdisp: cannot perform async vector I/O to file
Cause: This is an internal error. A request was made to perform asynchronous vector I/O when it cannot be performed on the file.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27066 skgfdisp: number of buffers in vector I/O exceeds maximum
Cause: This is an internal error. The number of buffers in vector I/O exceeds maximum allowed by the OSD, additional information indicates both these numbers.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27067 skgfdisp: size of buffer is invalid
Cause: This is an internal error. The buffer size is either 0, or greater than SSTIOMAX or not a multiple of logical block size, additional information indicates where in function the error was encountered and the buffer size.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27068 skgfdisp: buffer is not aligned properly
Cause: This is an internal error. The buffer is not aligned to SSIOALIGN boundary, additional information indicates where in function the error was encountered and the buffer pointer.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27069 skgfdisp: attempt to do I/O beyond the range of the file
Cause: This is an internal error. The range of blocks being read or written is outside the range of the file, additional information indicates the starting block number, number of blocks in I/O, and the last valid block in the file.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27070 skgfdisp: async read/write failed
Cause: AIOREAD/AIOWRITE system call returned error, additional information indicates starting block number of I/O.
Action: Check errno.
ORA-27071 skgfdisp: unable to seek to desired position in file
Cause: LSEEK system call returned error, additional information indicates block number in file to which seek was attempted.
Action: Check errno.
ORA-27072 skgfdisp: I/O error
Cause: READ/WRITE/READV/WRITEV system call returned error, additional information indicates starting block number of I/O.
Action: Check errno.
ORA-27073 skgfcfi: async I/Os remaining to be dequeued for this file
Cause: This is an internal error. The file is being closed but not all asynchronous I/Os to the file have been dequeued, additional information indicates number of I/Os pending on the file.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27074 skgfrofl: unable to determine limit for open files
Cause: GETRLIMIT system call returned error.
Action: Check errno.
ORA-27075 skgfrofl: SSTMOFRC constant too large
Cause: This is an internal error.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27076 skgfrofl: unable to set limit for open files
Cause: SETRLIMIT system call returned error.
Action: Check errno.
ORA-27077 skgfofi: too many files open
Cause: This is an internal error. The number of files opened through SKGFOFI has reached the limit.
Action: Check for a trace file and contact Oracle Support Services.
ORA-27080 skgfrdup: too many files open
Cause: the number of files opened has reached system limit.
Action: check error, and set system configuration values.
ORA-27084 skgfqio: unable to get/set file status flags
Cause: System call FCNTL with F_GETFL/F_SETFL flag returned error.
Action: Check errno.
ORA-27086 skgfglk: unable to lock file - already in use
Cause: The file is locked by another process, indicating that it is currently in use by a database instance.
Action: Determine which database instance legitimately owns this file.
ORA-27087 skgfglk: unable to get share lock - file not readable
Cause: Share lock request was made on a file not open for read access.
Action: File must be open read-only or read-write to get a share lock.
ORA-27088 skgfglk: unable to get file status
Cause: The file is not open or the file descriptor is invalid.
Action: Make sure the file is open and the descriptor is valid.
ORA-27089 skgfrlk: unable to release advisory lock
Cause: The file lock release failed.
Cause: See the errno.
ORA-27091 skgfqio: unable to queue I/O
Cause: A read/write/readv/writev system call returned error. Additional information indicates the starting block number of the I/O.
Action: Check the errno.
ORA-27092 skgfofi: size of file exceeds file size limit of the process
Cause: An attempt was made to open a file that exceeds the process's file size limit (ulimit), additional information shows the current limit (logical blocks) and the size of the file (logical blocks).
Action: increase the processes file size limit (ulimit) and retry.
ORA-27100 shared memory realm already exists
Cause: An attempt was made to start duplicate instances, or tried to restart an instance that had not been properly shut down.
Action: Use a different instance name, or cleanup the failed instance's SGA.
ORA-27101 shared memory realm does not exist
Cause: Unable to locate shared memory realm.
Action: Verify that the realm is accessible.
ORA-27102 out of memory
Cause: Out of memory.
Action: Consult the trace file for details.
ORA-27103 internal error
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-27120 unable to removed shared memory segment
Cause: SHMCTL() call failed.
Action: check permissions on segment, contact Oracle Support Services.
ORA-27121 unable to determine size of shared memory segment
Cause: SHMCTL() call failed.
Action: check permissions on segment, contact Oracle Support Services.
ORA-27122 unable to protect memory
Cause: MPROTECT() call failed.
Action: Contact Oracle Support Services.
ORA-27123 unable to attach to shared memory segment
Cause: SHMAT() call failed.
Action: Check permissions on segment, contact Oracle Support Services.
ORA-27124 unable to detach from shared memory segment
Cause: SHMDT() call failed.
Action: Contact Oracle Support Services.
ORA-27125 unable to create shared memory segment
Cause: SHMGET() call failed.
Action: Contact Oracle Support Services.
ORA-27126 unable to lock shared memory segment in core
Cause: Insufficient privileges to lock shared memory segment in core.
Action: Make sure the process is running with the necessary privileges.
ORA-27127 unable to unlock shared memory segment
Cause: Insufficient privileges to unlock shared memory segment.
Action: Make sure the process is running with the necessary privileges.
ORA-27128 unable to determine pagesize
Cause: SYSCONF() call failed.
Action: Contact Oracle Support Services.
ORA-27141 invalid process ID
Cause: Process operation attempted using invalid process ID.
Action: Contact Oracle Support Services.
ORA-27142 could not create new process
Cause: Operating system call error.
Action: Check errno and if possible increase the number of processes.
ORA-27143 OS system call failure
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27144 attempt to kill process failed
Cause: Operating system call error.
Action: Check errno and contact Oracle Support Services.
ORA-27145 insufficient resources for requested number of processes
Cause: Operating system call error.
Action: Check errno and contact Oracle Support Services.
ORA-27146 post/wait initialization failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27147 post/wait reset failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27148 spawn wait error
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27149 assignment out of range
Cause: This is an internal error. A request was made for a conversion too large for the type.
Action: Contact Oracle Support Services.
ORA-27150 attempt to notify process of pending oradebug call failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27151 buffer not large enough to hold process ID string
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-27152 attempt to post process failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27153 wait operation failed
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27154 post/wait create failed
Cause: This is an internal error. Multiple post/wait creates were attempted simultaneously.
Action: Check errno and contact Oracle Support Services.
ORA-27155 could not execute file
Cause: Operating system call failed.
Action: Check errno and contact Oracle Support Services.
ORA-27156 request for process information failed
Cause: This is an internal error.
Action: Contact Oracle Support Services.
ORA-27157 OS post/wait facility removed
Cause: The post/wait facility for which the calling process is awaiting action was removed from the system.
Action: Check errno and contact Oracle Support Services.
ORA-27190 skgfrd: sbtread2 returned error
Cause: SBTREAD2 returned an error. This happens while reading a backup file during a restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27191 sbtinfo2 returned error
Cause: SBTINFO2 returned an error. This happens while retrieving backup file information from the media manager's catalog.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27192 skgfcls: sbtclose2 returned error - failed to close file
Cause: SBTCLOSE2 returned an error. This happens while closing a backup file during a backup or restore operation.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27193 sbtinfo2 did not return volume label
Cause: SBTINFO2 did not return the volume label information for the backup file that was just created. This is an internal error in the media management product.
Action: Contact the media management vendor.
ORA-27194 skgfdvcmd: sbtcommand returned error
Cause: SBTCOMMAND returned an error. This happens when an RMAN SEND command is issued.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27195 proxy copy not supported
Cause: An attempt was made to do a proxy backup or restore, but the media management software installed with Oracle does not support proxy copy.
Action: Rerun the backup in non-proxy mode, or contact the media management vendor if the software is supposed to support proxy copy.
ORA-27196 skgfpbk: sbtpcbackup returned error
Cause: SBTPCBACKUP returned an error. This happens when a proxy backup is begun.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27197 skgfprs: sbtpcrestore returned error
Cause: SBTPCRESTORE returned an error. This happens when a proxy restore is begun.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27198 skgfpvl: sbtpcvalidate returned error
Cause: SBTPCVALIDATE returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27199 skgfpst: sbtpcstatus returned error
Cause: SBTPCSTATUS returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27200 skgfpgo: sbtpcstart returned error
Cause: SBTPCSTART returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27201 skgfpcm: sbtpccommit returned error
Cause: SBTPCCOMMIT returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27202 skgfpen: sbtpcend returned error
Cause: SBTPCEND returned an error. This happens during a proxy backup or restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27203 skgfpqb: sbtpcquerybackup returned error
Cause: SBTPCQUERYBACKUP returned an error. This happens during a proxy backup.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27204 skgfpqr: sbtpcqueryrestore returned error
Cause: SBTPCQUERYRESTORE returned an error. This happens during a proxy restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27205 skgfpcn: sbtpccancel returned error
Cause: SBTPCCANCEL returned an error. This happens during a proxy restore.
Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.
ORA-27206 requested file not found in media management catalog
Cause: A backup file used in a recovery manager catalog maintenance command was not found in the media management catalog.
Action: Retry the command with a different file.
ORA-27207 syntax error in device PARMS - parentheses mismatch or missing
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn
ORA-27208 syntax error in device PARMS - environment variable value missing
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with the correct syntax: ENV=(var1=val1,var2=val2,..)
ORA-27209 syntax error in device PARMS - unknown keyword or missing =
Cause: User-supplied PARMS value has incorrect syntax. The server expected to find ENV or BLKSIZE, but found an unknown keyword.
Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn
ORA-27210 syntax error in device PARMS
Cause: User-supplied PARMS value has incorrect syntax.
Action: Retry the command with the correct syntax: ENV=(..) BLKSIZE=nnnn
ORA-27211 Failed to load Media Management Library
Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call to dlopen for media library returned error. See Additional information for the error code.
Action: Retry the command with proper media library. Or re-install Media management module for Oracle.
ORA-27212 some entrypoints in Media Management Library are missing
Cause: Media library does not have one of the following entrypoints : sbtinfo, sbtread, sbtwrite, sbtremove, sbtopen, sbtclose, or sbtinit.
Action: Retry the command with proper media library.
ORA-27213 failed to unload Media Management Library
Cause: The dlclose for media library returned an error. See Additional information for the error code.
Action: Contact Oracle Support Services.
ORA-27300 OS system dependent operation:string failed with status: string
Cause: Operating system call error.
Action: Contact Oracle Support Services.
ORA-27301 OS failure message: string
Cause: Operating system call error.
Action: Contact Oracle Support Services.
ORA-27302 failure occurred at: string
Cause: Operating system call error.
Action: Contact Oracle Support Services.
ORA-27303 additional information: string
Cause: Operating system call error.
Action: Contact Oracle Support Services.
ORA-27500 inter-instance IPC error
Cause: This is an operating system/cluster interconnect error.
Action: Check the extra information and contact Oracle Support Services.
ORA-27501 IPC error creating a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27502 IPC error deleting OSD context
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27505 IPC error destroying a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27506 IPC error connecting to a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27507 IPC error disconnecting from a port
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27508 IPC error sending a message
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27509 IPC error receiving a message
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27510 IPC error waiting for a request to complete
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27512 IPC error posting a process
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27542 Failed to unprepare a buffer prepared for remote update
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27543 Failed to cancel outstanding IPC request
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27544 Failed to map memory region for export
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27545 Fail to prepare buffer for remote update
Cause: This is an operating system/cluster interconnect error.
Action: Check the value of errno and contact Oracle Support Services.
ORA-27546 Oracle compiled against IPC interface version string.string found version string.string
Cause: A misconfiguration or installation error occurred.
Action: Install the IPC library for this release of Oracle.
ORA-27547 Unable to query IPC OSD attribute string
Cause: This is an operating system-dependent IPC error.
Action: Contact Oracle Support Services.
ORA-27548 Unable to unprepare IPC buffer
Cause: This is an operating system-dependent IPC error.
Action: Contact Oracle Support Services.
ORA-28000 the account is locked
Cause: The user has entered wrong password consequently for maximum number of times specified by the user's profile parameter FAILED_LOGIN_ATTEMPTS, or the database administrator has locked the account.
Action: Wait for PASSWORD_LOCK_TIME or contact the database administrator.
ORA-28001 the password has expired
Cause: The user's account has expired and the password needs to be changed.
Action: Change the password or contact the database administrator.
ORA-28002 the password will expire within string days
Cause: The user's account is about to about to expire and the password needs to be changed.
Action: Change the password or contact the database administrator.
ORA-28003 password verification for the specified password failed
Cause: The new password did not meet the necessary complexity specifications and the PASSWORD_VERIFY_FUNCTION failed.
Action: Enter a different password. Contact the database administrator to find out the rules for choosing the new password.
ORA-28004 invalid argument for function specified in PASSWORD_VERIFY_FUNCTION string
Cause: The password verification function does not have the required number and type of input/output arguments and/or the return argument.
Action: Check the Oracle9i Security Overview to find out the format of the password verification function.
ORA-28005 invalid logon flags
Cause: The flags are not properly set or conflicting flags are set in making calls.
Action: Call the function with appropriate flags set.
ORA-28006 conflicting values for parameters string and string
Cause: The parameters PASSWORD_REUSE_TIME and PASSWORD_REUSE_MAX cannot both be set. One parameter should be unlimited while other is set.
Action: Set one value to UNLIMITED explicitly.
ORA-28007 the password cannot be reused
Cause: The password cannot be reused for the specified number of days or for the specified number of password changes.
Action: Try the password that you have not used for the specified number of days or the specified number of password changes Refer to the password parameters in the CREATE PROFILE statement.
ORA-28008 invalid old password
Cause: Old password supplied is wrong; Hence user cannot be authenticated using old password.
Action: Supply the correct old password for authentication.
ORA-28009 connection to sys should be as sysdba or sysoper
Cause: Connect sys/password is no longer a valid syntax.
Action: Try connect sys/password as sysdba or connect sys/password as sysoper.
ORA-28010 cannot expire external or global accounts
Cause: If a user account is created as IDENTIFIED EXTERNALLY, or IDENTIFIED GLOBALLY, this account cannot be expired.
Action: Try to expire the password of the user that has database password.
ORA-28011 the account will expire soon; change your password now
Cause: The user's account is marked for expire; the expiry period is unlimited.
Action: Change the password or contact the DBA.
ORA-28020 IDENTIFIED GLOBALLY already specified
Cause: The IDENTIFIED GLOBALLY clause was specified twice.
Action: Use only one IDENTIFIED GLOBALLY clause.
ORA-28021 cannot grant global roles
Cause: A role granted was IDENTIFIED GLOBALLY. Global roles can only be granted via a central authority for the domain.
Action: Use ALTER ROLE to change the type of role (from IDENTIFIED GLOBALLY to other, such as IDENTIFIED BY password), or allocate it to a global user via the central authority.
ORA-28022 cannot grant external roles to global user or role
Cause: A role granted was IDENTIFIED EXTERNALLY. External roles cannot be granted to global users or global roles.
Action: Use ALTER ROLE to change the type of the role being granted (from IDENTIFIED EXTERNALLY to other, such as IDENTIFIED BY password), or use ALTER ROLE or ALTER USER to change the type of the user or role that is the grantee.
ORA-28023 must revoke grants of this role to other user(s) first
Cause: The role altered to IDENTIFIED GLOBALLY was granted to one or more other users and/or roles. Global roles cannot be granted to any user or role.
Action: Use REVOKE to revoke the role from other users or roles first.
ORA-28024 must revoke grants of external roles to this role/user
Cause: The user or role altered to IDENTIFIED GLOBALLY has external roles directly granted; these must be revoked, since external roles cannot be granted to global users or roles.
Action: Use REVOKE to revoke the external roles from the user or role to be ALTERed.
ORA-28025 missing or null external name
Cause: The IDENTIFIED EXTERNALLY AS or IDENTIFIED GLOBALLY AS clause was specified with a valid external name.
Action: Provide a valid external name.
ORA-28026 user with same external name already exists
Cause: The external name specified for the user being created or altered already exists for another user.
Action: External names must be unique among users. Specify another.
ORA-28027 privileged database links may be used by global users
Cause: Only users IDENTIFIED GLOBALLY may use a privileged database link.
Action: Either change the user to a global user or try to use a different database link.
ORA-28028 could not authenticate remote server
Cause: During the course of opening a privileged database link, the remote server was not securely identified using the network security service. Additional errors should follow.
Action: Consult the network security service documentation on how to properly configure the remote server.
ORA-28029 could not authorize remote server for user string
Cause: During the course of opening a privileged database link, the remote server was found to lack the necessary authorizations to connect as the current global user. This may be because the server was not authorized by the network security service. Or it may be because the local server is restricting access by the remote server using the DBMS_SECURITY_DOMAINS_ADMIN package.
Action: Grant the remote server the proper authorization to connect as the given global user, and check that the local server is not restricting access.
ORA-28030 Server encountered problems accessing LDAP directory service
Cause: Unable to access LDAP directory service.
Action: Contact your system administrator.
ORA-28035 Cannot Get Session Key for Authentication
Cause: Client and server cannot negotiate shared secret during logon.
Action: Contact your system administrator.
ORA-28100 policy function schema string is invalid
Cause: The schema was dropped after the policy associated with the function had been added to the object.
Action: Drop the policy and re-create it with a policy function owned by a valid user. Or re-create the user and the policy function under the new user.
ORA-28101 policy already exists
Cause: A policy with the same name for the same object already exists.
Action: Check if the policy has already been added or use a different policy name.
ORA-28102 policy does not exist
Cause: Try to drop/enable/refresh a non-existent policy.
Action: Correct the policy name argument.
ORA-28103 adding a policy to an object owned by SYS is not allowed
Cause: Try to add a policy to a table or a view owned by SYS.
Action: You cannot perform this operation.
ORA-28104 policy function or package is invalid
Cause: The function or package implementing a policy does not exist or was created with errors.
Action: Correct the function or package.
ORA-28106 input value for argument #string is not valid
Cause: Input values for the argument is missing or invalid.
Action: Correct the input values.
ORA-28107 policy was disabled
Cause: Try to flush a disabled policy.
Action: If the policy is supposed to be enforced, it must be enabled.
ORA-28108 circular security policies detected
Cause: Policies for the same object reference each other.
Action: Drop the policies.
ORA-28109 the number of related policies has exceeded the limit of 16
Cause: Too many policies are involved in the same objects.
Action: Drop one or more policies. Or combine a few of them into one.
ORA-28110 policy function or package string.string has error
Cause: The policy function may have been dropped, or is no longer valid.
Action: Check the status of the function and correct the problem. Or re-create the policy with a valid function.
ORA-28111 insufficient privilege to evaluate policy predicate
Cause: Predicate has a subquery which contains objects that the owner of policy function does not have privilege to access.
Action: Grant appropriate privileges to the policy function owner.
ORA-28112 failed to execute policy function
Cause: The policy function has one or more error during execution.
Action: Check the trace file and correct the errors.
ORA-28113 policy predicate has error
Cause: Policy function generates invalid predicate.
Action: Review the trace file for detailed error information.
ORA-28115 policy with check option violation
Cause: Policy predicate was evaluated to FALSE with the updated values.
Action: Check the trace file and correct the errors.
ORA-28116 insufficient privileges to do direct path access
Cause: Users with insufficient privileges attempting to do direct path access of tables with fine grain access control policies.
Action: Ask the database administrator to do the operation. Note that users can work with security administrator to temporarily drop/disable the policies at time of export, import, or load, but this has security implication, and thus access of the database must be controlled carefully.
ORA-28117 integrity constraint violated - parent record not found
Cause: tried to update/insert a child record with new foreign key values, but the corresponding parent row was not visible because of fine-grained security in the parent.
Action: make sure that the updated foreign key values are visible in the parent.
ORA-28118 policy group already exists
Cause: tried to create a policy group that already exists.
ORA-28119 policy group does not exist
Cause: tried to drop a policy group that does not exist.
ORA-28120 driving context already exists
Cause: tried to create a driving context that already exists.
ORA-28121 driving context does not exist
Cause: tried to drop a driving context that does not exist.
ORA-28132 Merge into syntax does not support security policies.
Cause: Merge into syntax currently does not support a security policy on the destination table.
Action: use the insert / update DML stmts on the table that has a security policy defined on it.
ORA-28133 full table access is restricted by fine-grained security
Cause: The user is not SYS and doesn't have full table access due to VPD policies. This only happens for internal DML/query under a DDL.
Action: Grant the appropriate privilege or contact Oracle Support Services if this is too restrictive.
ORA-28134 object cannot have fine-grained access control policy
Cause: Only tables, views, or synonyms of tables or views may have VPD policies.
Action: No action required.
ORA-28150 proxy not authorized to connect as client
Cause: A proxy user attempted to connect as a client, but the proxy was not authorized to act on behalf of the client.
Action: Grant the proxy user permission to perform actions on behalf of the client by using the ALTER USER... GRANT CONNECT command.
ORA-28151 more than one user name specified for command
Cause: More than one user name was specified for an ALTER USER command.
Action: Try the command again with only one user name.
ORA-28152 proxy user 'string' may not specify initial role 'string' on behalf of client 'string'
Cause: A proxy user attempted to specify an initial role for a client, but the client does not possess the role.
Action: Change the proxy user so that it does not specify the role or grant the role to the client.
ORA-28153 Invalid client initial role specified: 'string'
Cause: A role specified by a proxy user as an initial role to be activated upon connecting on behalf of a client is invalid.
Action: Connect again as the client specifying a valid role.
ORA-28154 Proxy user may not act as client 'string'
Cause: A proxy user cannot assume the identity of a privileged user in order to limit the privileges that a proxy can possess.
Action: Execute the statement again, specifying a client other than a privileged user.
ORA-28155 user 'string' specified as a proxy is actually a role
Cause: A user specified in an AUDIT operation BY proxy ON BEHALF OF client is actually a role.
Action: Execute the statement again with a valid proxy user.
ORA-28156 Proxy user 'string' not authorized to set role 'string' for client 'string'
Cause: A proxy user has not been granted the right to use a role on behalf of a client.
Action: Execute the command ALTER USER client GRANT CONNECT THROUGH PROXY proxy to grant the needed role.
ORA-28157 Proxy user 'string' forbidden to set role 'string' for client 'string'
Cause: A proxy user was forbidden to use a role on behalf of a client through the command ALTER USER client GRANT CONNECT THROUGH proxy WITH ALL ROLES EXCEPT role.
Action: Execute the command ALTER USER client GRANT CONNECT THROUGH PROXY proxy to grant the needed role.
ORA-28158 missing ALL keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28159 missing BEHALF keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28160 missing EXCEPT keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28161 missing ROLES keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28162 missing THROUGH keyword
Cause: Keyword missing.
Action: Provide missing keyword.
ORA-28163 GRANT already specified
Cause: The GRANT clause was specified twice.
Action: Use only one GRANT clause.
ORA-28164 REVOKE already specified
Cause: The REVOKE clause was specified twice.
Action: Use only one REVOKE clause.
ORA-28165 proxy 'string' may not specify password-protected role 'string' for client 'string'
Cause: A proxy user attempted to activate a role on behalf of a client which has a password associated with it. Since the proxy does not have a password, this activation cannot be allowed.
Action: Attempt to activate a different role or change the role administratively so that there is no password.
ORA-28166 duplicate rolename in list
Cause: The name of a role was specified more than once in a list.
Action: Repeat the command specifying the role once.
ORA-28168 attempted to grant password-protected role
Cause: An ALTER USER ... GRANT CONNECT command was attempted specifying a role that is protected by a password as a role which the proxy may execute on behalf of a client.
Action: Either specify a role that does not have a password or alter the role so that a password is not required.
ORA-28169 unsupported certificate type
Cause: The type of certificate from which the server is to extract the credentials of the client is not supported.
Action: Specify a supported type.
ORA-28170 unsupported certificate version
Cause: The version of the certificate from which the server is to extract the credentials of the client is not supported.
Action: Specify a supported version.
ORA-28171 unsupported Kerberos version
Cause: The version of the Kerberos ticket which the server is to use to validate the identity of the client is not supported.
Action: Specify a supported version.
ORA-28172 distinguished name not provided by proxy
Cause: A client user is to be identified using a distinguished name, but none was provided by the proxy user.
Action: Provide a distinguished name.
ORA-28173 certificate not provided by proxy
Cause: A client user is to be identified using a certificate but none was provided by the proxy user.
Action: Provide a certificate.
ORA-28174 Kerberos ticket not provided by proxy
Cause: A client user is to be authenticated using a Kerberos ticket but none was provided by the proxy user.
Action: Provide a Kerberos ticket.
ORA-28175 incorrect certificate type
Cause: the type of certificate provided by the proxy user to identify a client user does not match the type that is required.
Action: Provide a certificate of the correct type.
ORA-28176 incorrect certificate version
Cause: The version of the certificate provided by the proxy user to identify a client user does not match the version that is required.
Action: Provide a certificate of the correct version.
ORA-28177 incorrect Kerberos ticket version
Cause: the version of the Kerberos ticket provided by the proxy user to authenticate a client user does not match the version that is required.
Action: Provide a Kerberos ticket of the correct version.
ORA-28178 password not provided by proxy
Cause: A client user is to be authenticated using a database password but none was provided by the proxy user.
Action: Provide a password.
ORA-28179 client user name not provided by proxy
Cause: No user name was provided by the proxy user for the client user.
Action: Either specify a client database user name, a distinguished name or an X.509 certificate.
ORA-28180 multiple authentication methods provided by proxy
Cause: More than one authentication method was specified by the proxy user for the client user.
Action: Specify only one of the following:
A client database user name
A distinguished name
An X.509 certificate.
ORA-28200 IDENTIFIED USING already specified
Cause: The IDENTIFIED USING clause was specified twice.
Action: Use only one IDENTIFIED USING clause.
ORA-28201 Not enough privileges to enable application role 'string'
Cause: An attempt to enable application role outside the scope of the designated package.
Action: Enable the role directly or indirectly using the designated package.
No comments:
Post a Comment