73 ORA-02100 to ORA-04099
- ORA-02100: PCC: out of memory (i.e., could not allocate)
-
- ORA-02101: PCC: inconsistent cursor cache (uce/cuc mismatch)
-
- ORA-02102: PCC: inconsistent cursor cache (no cuc entry for this uce)
-
- ORA-02103: PCC: inconsistent cursor cache (out-of-range cuc ref)
-
- ORA-02104: PCC: inconsistent host cache (no cuc available)
-
- ORA-02105: PCC: inconsistent cursor cache (no cuc entry in cache)
-
- ORA-02106: PCC: inconsistent cursor cache (OraCursor nr is bad)
-
- ORA-02107: PCC: this pgm too old for run-time library: please re-PCC it
-
- ORA-02108: PCC: invalid descriptor passed to run-time library
-
- ORA-02109: PCC: inconsistent host cache (out-of-range sit ref)
-
- ORA-02110: PCC: inconsistent host cache (invalid sqi type)
-
- ORA-02111: PCC: heap consistency error
-
- ORA-02112: PCC: SELECT..INTO returns too many rows
-
- ORA-02140: invalid tablespace name
-
Cause: An identifier does not follow ALTER TABLESPACE.
- ORA-02141: invalid OFFLINE option
-
Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE.
- ORA-02142: missing or invalid ALTER TABLESPACE option
-
Cause: A valid option was not present.
- ORA-02143: invalid STORAGE option
-
Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause.
- ORA-02144: no option specified for ALTER CLUSTER
-
Cause: No ALTER CLUSTER options are specified.
- ORA-02145: missing STORAGE option
-
Cause: No STORAGE options were specified following STORAGE (
- ORA-02146: SHARED specified multiple times
-
Cause: The SHARED option was specified in a CREATE DATABASE statement multiple times.
- ORA-02147: conflicting SHARED/EXCLUSIVE options
-
Cause: Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement.
- ORA-02148: EXCLUSIVE specified multiple times
-
Cause: The EXCLUSIVE option was specified in a CREATE DATABASE statement multiple times.
- ORA-02149: Specified partition does not exist
-
Cause: Partition not found for the object.
- ORA-02150: invalid new tablespace name
-
Cause: The new tablespace name specified in ALTER TABLESPACE RENAME TO statement was invalid.
- ORA-02151: invalid tablespace name: string
-
Cause: Oracle cannot create a tablespace whose name starts with '_$deleted$'.
- ORA-02152: Invalid ALTER TABLESPACE ... RENAME option
-
Cause: An option other than DATAFILE or TO follows by ALTER TABLESPACE ... RENAME.
- ORA-02153: invalid VALUES password string
-
Cause: An encoded password string does not follow the VALUES clause.
- ORA-02154: a tablespace with the name 'string' is found
-
Cause: An attempt to rename a tablespace to a new name failed because the new name is already used by some other tablespace.
- ORA-02155: invalid DEFAULT tablespace identifier
-
Cause: An identifier does not follow DEFAULT TABLESPACE.
- ORA-02156: invalid TEMPORARY tablespace identifier
-
Cause: An identifier does not follow TEMPORARY TABLESPACE.
- ORA-02157: no options specified for ALTER USER
-
Cause: No options were specified.
- ORA-02158: invalid CREATE INDEX option
-
Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified.
- ORA-02159: installed DLM does not support releasable locking mode
-
Cause: The parameter file specified gc_* parameters that allow locks to be release by the LCK process when not in use. This mode requires additional support from the DLM that is not available.
- ORA-02160: index-organized table can not contain columns of type LONG
-
Cause: A column of type LONG defined for index-organized table.
- ORA-02161: invalid value for MAXLOGFILES
-
Cause: A number does not follow MAXLOGFILES.
- ORA-02162: invalid value for MAXDATAFILES
-
Cause: A number does not follow MAXDATAFILES.
- ORA-02163: invalid value for FREELIST GROUPS
-
Cause: A number does not follow FREELIST GROUPS.
- ORA-02164: DATAFILE clause specified more than once
-
Cause: The CREATE DATABASE command contains more than one DATAFILE clause.
- ORA-02165: invalid option for CREATE DATABASE
-
Cause: An invalid CREATE DATABASE option is present.
- ORA-02166: ARCHIVELOG and NOARCHIVELOG specified
-
Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement.
- ORA-02167: LOGFILE clause specified more than once
-
Cause: The CREATE DATABASE command contains more than one LOGFILE clause.
- ORA-02168: invalid value for FREELISTS
-
Cause: A number does not follow FREELISTS
- ORA-02169: FREELISTS storage option not allowed
-
Cause: The user attempted to specify the FREELISTS storage option. This option may only be specified during create table or create index.
- ORA-02170: FREELIST GROUPS storage option not allowed
-
Cause: The user attempted to specify the FREELIST GROUPS storage option. This option may only be specified during create table and when allow_freelist_groups INIT.ORA is specified.
- ORA-02171: invalid value for MAXLOGHISTORY
-
Cause: A number does not follow MAXLOGHISTORY
- ORA-02172: The PUBLIC keyword is not appropriate for a disable thread
-
Cause: The PUBLIC keyword was specified for a disable.
- ORA-02173: invalid option for DROP TABLESPACE
-
Cause: Either a token other than INCLUDING was found following the tablespace name or some text was found following INCLUDING CONTENTS.
- ORA-02174: Missing required thread number
-
Cause: Must specify thread number after THREAD keyword
- ORA-02175: invalid rollback segment name
-
Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier was not found following ROLLBACK SEGMENT.
- ORA-02176: invalid option for CREATE ROLLBACK SEGMENT
-
Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.
- ORA-02177: Missing required group number
-
Cause: Must specify group number after GROUP keyword
- ORA-02178: correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
-
Cause: There is a syntax error in the user's statement.
- ORA-02179: valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
-
Cause: There is a syntax error in the user's statement.
- ORA-02180: invalid option for CREATE TABLESPACE
-
Cause: An invalid option appeared.
- ORA-02181: invalid option to ROLLBACK WORK
-
Cause: A token other than TO follows ROLLBACK [WORK].
- ORA-02182: savepoint name expected
-
Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT].
- ORA-02183: valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }
-
Cause: There is a syntax error in the user's statement.
- ORA-02184: resource quotas are not allowed in REVOKE
-
Cause: In a revoke statement, a resource quota was specified.
- ORA-02185: a token other than WORK follows COMMIT
-
Cause: A token other than WORK follows COMMIT.
- ORA-02186: tablespace resource privilege may not appear with other privileges
-
Cause: An attempt was made to grant or revoke a resource quota in the same statement in which other privileges are granted or revoked.
- ORA-02187: invalid quota specification
-
Cause: The user attempted to grant a tablespace quota above the upper limit.
- ORA-02188: Cannot enable instance publicly
-
Cause: An attempt was made to publicly enable a thread associated with an instance.
- ORA-02189: ON tablespace required
-
Cause: In a grant or revoke statement, the user specified a tablespace quota but did not follow it with the ON tablespace clause.
- ORA-02190: keyword TABLES expected
-
Cause: The keyword TABLES is expected following DROP CLUSTER name INCLUDING.
- ORA-02191: correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT rbs
-
Cause: There is a syntax error in the user's statement.
- ORA-02192: PCTINCREASE not allowed for rollback segment storage clauses
-
Cause: pctincrease was specified in a create or alter rollback segment
- ORA-02194: event specification syntax error string (minor error string) near 'string'
-
Cause: There is a syntax error in an event specification.
- ORA-02195: Attempt to create string object in a string tablespace
-
Cause: The object type is inconsistent with a tablespace contents.
- ORA-02196: PERMANENT/TEMPORARY option already specified
-
Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once.
- ORA-02197: file list already specified
-
Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was specified.
- ORA-02198: ONLINE/OFFLINE option already specified
-
Cause: In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were specified more than once.
- ORA-02199: missing DATAFILE/TEMPFILE clause
-
Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.
- ORA-02200: WITH GRANT OPTION not allowed for PUBLIC
-
Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.
- ORA-02201: sequence not allowed here
-
Cause: An attempt was made to reference a sequence in a from-list.
- ORA-02202: no more tables permitted in this cluster
-
Cause: An attempt was made to create a table in a cluster which already contains 32 tables.
- ORA-02203: INITIAL storage options not allowed
-
Cause: The user attempted to alter the INITIAL storage option of a table, cluster, index, or rollback segment. These options may only be specified when the object is created.
- ORA-02204: ALTER, INDEX and EXECUTE not allowed for views
-
Cause: An attempt was made to grant or revoke an invalid privilege on a view.
- ORA-02205: only SELECT and ALTER privileges are valid for sequences
-
Cause: An attempt was made to grant or revoke an invalid privilege on a sequence.
- ORA-02206: duplicate INITRANS option specification
-
Cause: INITRANS is specified more than once.
- ORA-02207: invalid INITRANS option value
-
Cause: The INITRANS value is not an integer between 1 and 255 and less than or equal to the MAXTRANS value.
- ORA-02208: duplicate MAXTRANS option specification
-
Cause: MAXTRANS is specified more than once.
- ORA-02209: invalid MAXTRANS option value
-
Cause: The MAXTRANS value is not an integer between 1 and 255 and greater than or equal to the INITRANS value.
- ORA-02210: no options specified for ALTER TABLE
-
Cause: No ALTER TABLE option was specified.
- ORA-02211: invalid value for PCTFREE or PCTUSED
-
Cause: The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100.
- ORA-02212: duplicate PCTFREE option specification
-
Cause: PCTFREE option specified more than once.
- ORA-02213: duplicate PCTUSED option specification
-
Cause: PCTUSED option specified more than once.
- ORA-02214: duplicate BACKUP option specification
-
Cause: The BACKUP option to ALTER TABLE is specified more than once.
- ORA-02215: duplicate tablespace name clause
-
Cause: There is more than one TABLESPACE clause in the CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT statement.
- ORA-02216: tablespace name expected
-
Cause: A tablespace name was not present where required by the syntax for the failing statement.
- ORA-02217: duplicate storage option specification
-
Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE) is specified more than once.
- ORA-02218: invalid INITIAL storage option value
-
Cause: The specified value must be an integer.
- ORA-02219: invalid NEXT storage option value
-
Cause: The specified value must be an integer.
- ORA-02220: invalid MINEXTENTS storage option value
-
Cause: The specified value must be a positive integer less than or equal to MAXEXTENTS.
- ORA-02221: invalid MAXEXTENTS storage option value
-
Cause: The specified value must be a positive integer greater than or equal to MINEXTENTS.
- ORA-02222: invalid PCTINCREASE storage option value
-
Cause: The specified value must be a positive integer.
- ORA-02223: invalid OPTIMAL storage option value
-
Cause: The specified value must be an integer.
- ORA-02224: EXECUTE privilege not allowed for tables
-
Cause: An attempt was made to grant or revoke an invalid privilege on a table.
- ORA-02225: only EXECUTE and DEBUG privileges are valid for procedures
-
Cause: An attempt was made to grant or revoke an invalid privilege on a procedure, function or package.
- ORA-02226: invalid MAXEXTENTS value (max allowed: string)
-
Cause: The MAXEXTENTS specified is too large for the database block size. This applies only to SYSTEM rollback segment.
- ORA-02227: invalid cluster name
-
Cause: A cluster name of the form [ identifier . ] identifier is expected but not present.
- ORA-02228: duplicate SIZE specification
-
Cause: The SIZE option is specified more than once.
- ORA-02229: invalid SIZE option value
-
Cause: The specified value must be an integer number of bytes.
- ORA-02230: invalid ALTER CLUSTER option
-
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE is specified in an ALTER CLUSTER statement.
- ORA-02231: missing or invalid option to ALTER DATABASE
-
Cause: An option other than ADD, DROP, RENAME, ARCHIVELOG, NOARCHIVELOG, MOUNT, DISMOUNT, OPEN, or CLOSE is specified in the statement.
- ORA-02232: invalid MOUNT mode
-
Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword in an ALTER DATABASE statement.
- ORA-02233: invalid CLOSE mode
-
Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword in an ALTER DATABASE statement.
- ORA-02234: changes to this table are already logged
-
Cause: the log table to be added is a duplicate of another
- ORA-02235: this table logs changes to another table already
-
Cause: the table to be altered is already a change log for another table
- ORA-02236: invalid file name
-
Cause: A character string literal was not used in the filename list of a LOGFILE, DATAFILE, or RENAME clause.
- ORA-02237: invalid file size
-
Cause: A non-integer value was specified in the SIZE or RESIZE clause.
- ORA-02238: filename lists have different numbers of files
-
Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the the number of existing filenames does not equal the number of new filenames.
- ORA-02239: there are objects which reference this sequence
-
Cause: the sequence to be dropped is still referenced
- ORA-02240: invalid value for OBJNO or TABNO
-
Cause: A number does not follow either OBJNO or TABNO.
- ORA-02241: must of form EXTENTS (FILE n BLOCK n SIZE n, ...)
-
Cause: bad extent storage clause
- ORA-02242: no options specified for ALTER INDEX
-
Cause: No options specified.
- ORA-02243: invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
-
Cause: An option other than INITRANS, MAXTRANS,or STORAGE is specified in an ALTER INDEX statement or in the USING INDEX clause of an ALTER MATERIALIZED VIEW statement.
- ORA-02244: invalid ALTER ROLLBACK SEGMENT option
-
Cause: The STORAGE option is expected but not found.
- ORA-02245: invalid ROLLBACK SEGMENT name
-
Cause: An identifier was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT.
- ORA-02246: missing EVENTS text
-
Cause: A character string literal was expected, but not found, following ALTER SESSION SET EVENTS.
- ORA-02247: no option specified for ALTER SESSION
-
Cause: The option SET EVENTS was expected, but not found, following ALTER SESSION.
- ORA-02248: invalid option for ALTER SESSION
-
Cause: Obvious.
- ORA-02249: missing or invalid value for MAXLOGMEMBERS
-
Cause: A valid number does not follow MAXLOGMEMBERS. The value specified must be between 1 and the port-specific maximum number of log file members.
- ORA-02250: missing or invalid constraint name
-
Cause: The constraint name is missing or invalid.
- ORA-02251: subquery not allowed here
-
Cause: Subquery is not allowed here in the statement.
- ORA-02252: check constraint condition not properly ended
-
Cause: The specified search condition for the check constraint is not properly ended.
- ORA-02253: constraint specification not allowed here
-
Cause: Constraint specification is not allowed here in the statement.
- ORA-02254: DEFAULT expression not allowed here
-
Cause: Default value expression is not allowed for the column here in the statement.
- ORA-02255: obsolete 7.1.5
-
Cause: Was that defaults must not conflict with not null constraints
- ORA-02256: number of referencing columns must match referenced columns
-
Cause: The number of columns in the foreign-key referencing list is not equal to the number of columns in the referenced list.
- ORA-02257: maximum number of columns exceeded
-
Cause: The number of columns in the key list exceeds the maximum number.
- ORA-02258: duplicate or conflicting NULL and/or NOT NULL specifications
-
Cause: Self-evident.
- ORA-02259: duplicate UNIQUE/PRIMARY KEY specifications
-
Cause: Self-evident.
- ORA-02260: table can have only one primary key
-
Cause: Self-evident.
- ORA-02261: such unique or primary key already exists in the table
-
Cause: Self-evident.
- ORA-02262: ORA-string occurs while type-checking column default value expression
-
Cause: New column datatype causes type-checking error for existing column default value expression.
- ORA-02263: need to specify the datatype for this column
-
Cause: The required datatype for the column is missing.
- ORA-02264: name already used by an existing constraint
-
Cause: The specified constraint name has to be unique.
- ORA-02265: cannot derive the datatype of the referencing column
-
Cause: The datatype of the referenced column is not defined as yet.
- ORA-02266: unique/primary keys in table referenced by enabled foreign keys
-
Cause: An attempt was made to truncate a table with unique or primary keys referenced by foreign keys enabled in another table. Other operations not allowed are dropping/truncating a partition of a partitioned table or an ALTER TABLE EXCHANGE PARTITION.
- ORA-02267: column type incompatible with referenced column type
-
Cause: The data type or collation of the referencing column was incompatible with the data type or collation of the referenced column.
- ORA-02268: referenced table does not have a primary key
-
Cause: The referenced table does not have a primary key.
- ORA-02269: key column cannot be of LONG datatype
-
Cause: Self-evident.
- ORA-02270: no matching unique or primary key for this column-list
-
Cause: A REFERENCES clause in a CREATE/ALTER TABLE statement gives a column-list for which there is no matching unique or primary key constraint in the referenced table.
- ORA-02271: table does not have such constraint
-
Cause: Self-evident.
- ORA-02272: constrained column cannot be of LONG datatype
-
Cause: Self-evident.
- ORA-02273: this unique/primary key is referenced by some foreign keys
-
Cause: Self-evident.
- ORA-02274: duplicate referential constraint specifications
-
Cause: Self-evident.
- ORA-02275: such a referential constraint already exists in the table
-
Cause: Self-evident.
- ORA-02276: default value type incompatible with column type
-
Cause: The type of the evaluated default expression is incompatible with the datatype of the column.
- ORA-02277: invalid sequence name
-
Cause: The specified sequence name is not a valid identifier name.
- ORA-02278: duplicate or conflicting MAXVALUE/NOMAXVALUE specifications
-
Cause: Self-evident.
- ORA-02279: duplicate or conflicting MINVALUE/NOMINVALUE specifications
-
Cause: Self-evident.
- ORA-02280: duplicate or conflicting CYCLE/NOCYCLE specifications
-
Cause: Self-evident.
- ORA-02281: duplicate or conflicting CACHE/NOCACHE specifications
-
Cause: Self-evident.
- ORA-02282: duplicate or conflicting ORDER/NOORDER specifications
-
Cause: Self-evident.
- ORA-02283: cannot alter starting sequence number
-
Cause: Self-evident.
- ORA-02284: duplicate INCREMENT BY specifications
-
Cause: Self-evident.
- ORA-02285: duplicate START WITH specifications
-
Cause: Self-evident.
- ORA-02286: no options specified for ALTER SEQUENCE
-
Cause: Self-evident.
- ORA-02287: sequence number not allowed here
-
Cause: The specified sequence number (CURRVAL or NEXTVAL) is inappropriate here in the statement.
- ORA-02288: invalid OPEN mode
-
Cause: A token other than RESETLOGS appears following ALTER DATABASE name OPEN.
- ORA-02289: sequence does not exist
-
Cause: The specified sequence does not exist, or the user does not have the required privilege to perform this operation.
- ORA-02290: check constraint (string.string) violated
-
Cause: The values being inserted do not satisfy the named check constraint.
- ORA-02291: integrity constraint (string.string) violated - parent key not found
-
Cause: A foreign key value has no matching primary key value.
- ORA-02292: integrity constraint (string.string) violated - child record found
-
Cause: attempted to delete a parent key value that had a foreign key dependency.
- ORA-02293: cannot validate (string.string) - check constraint violated
-
Cause: an alter table operation tried to validate a check constraint to a populated table that had nocomplying values.
- ORA-02294: cannot enable (string.string) - constraint changed during validation
-
Cause: While one DDL statement was attempting to enable this constraint, another DDL changed this same constraint.
- ORA-02295: found more than one enable/disable clause for constraint
-
Cause: a create or alter table specified more than one enable and/or disable clause for a given constraint.
- ORA-02296: cannot enable (string.string) - null values found
-
Cause: an alter table enable constraint failed because the table contains values that do not satisfy the constraint.
- ORA-02297: cannot disable constraint (string.string) - dependencies exist
-
Cause: an alter table disable constraint failed becuase the table has foriegn keys that are dpendent on this constraint.
- ORA-02298: cannot validate (string.string) - parent keys not found
-
Cause: an alter table validating constraint failed because the table has orphaned child records.
- ORA-02299: cannot validate (string.string) - duplicate keys found
-
Cause: an alter table validating constraint failed because the table has duplicate key values.
- ORA-02300: invalid value for OIDGENERATORS
-
Cause: A number was not specified for the value of OIDGENERATORS.
- ORA-02301: maximum number of OIDGENERATORS is 255
-
Cause: A number greater than 255 was specified for the value of OIDGENERATORS.
- ORA-02302: invalid or missing type name
-
Cause: An invalid or missing type name was entered in a statement.
- ORA-02303: cannot drop or replace a type with type or table dependents
-
Cause: An attempt was made to drop or replace a type that has type or table dependents.
- ORA-02304: invalid object identifier literal
-
Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is either: - not a string of 32 hexadecimal characters - an object identifier that already identifies an existing object - an object identifier different from the original object identifier already assigned to the type
- ORA-02305: only EXECUTE, DEBUG, and UNDER privileges are valid for types
-
Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not EXECUTE, DEBUG, or UNDER) on a type.
- ORA-02306: cannot create a type that already has valid dependent(s)
-
Cause: An attempt was made to create a type that already has some valid dependent(s) (these dependents depend on the fact that the type does not exist).
- ORA-02307: cannot alter with REPLACE option a type that is not valid
-
Cause: An attempt was made to ALTER with REPLACE option a type that is not valid.
- ORA-02308: invalid option string for object type column
-
Cause: An attempt was made to specify an invalid option, such as PACKED or UNPACKED, for the object type column.
- ORA-02309: atomic NULL violation
-
Cause: An attempt was made to acess the attributes of a NULL object instance.
- ORA-02310: exceeded maximum number of allowable columns in table
-
Cause: The attributes in the object type column exceeded the maximum number of columns allowed in a table.
- ORA-02311: cannot alter with COMPILE option a valid type with type or table dependents
-
Cause: An attempt was made to ALTER with COMPILE option a type that is valid and has type or table dependents.
- ORA-02313: object type contains non-queryable type string attribute
-
Cause: The specified object type contains a nested attribute whose type is non-queryable.
- ORA-02314: illegal use of type constructor
-
Cause: The statement contains an illegal use of a type constructor.
- ORA-02315: incorrect number of arguments for default constructor
-
Cause: The number of arguments specified for the default constructor doesn't match the number of attributes of the object type.
- ORA-02320: failure in creating storage table for nested table column string
-
Cause: An error occurred while creating the storage table for the specified nested table column.
- ORA-02322: failure in accessing storage table of the nested table column
-
Cause: An error occured while performing DML on the storage table of the nested table column.
- ORA-02324: more than one column in the SELECT list of THE subquery
-
Cause: More than one column was selected in the THE subquery.
- ORA-02327: cannot create index on expression with datatype string
-
Cause: An attempt was made to create an index on a non-indexable expression.
- ORA-02329: column of datatype string cannot be unique or a primary key
-
Cause: An attempt was made to place a UNIQUE or a PRIMARY KEY constraint on a column of datatype VARRAY, nested table, object, LOB, FILE or REF.
- ORA-02330: datatype specification not allowed
-
Cause: An attempt was made to specify the data type in the column constraint specification of an object table.
- ORA-02331: cannot create constraint on column of datatype string
-
Cause: An attempt was made to create a constraint on a column posessing a non-constrainable datatype -- VARRAY, nested table, object, LOB, FILE, or REF.
- ORA-02332: cannot create index on attributes of this column
-
Cause: An attempt was made to create an index on an attributes of an object type column.
- ORA-02333: cannot create constraints on attributes of this column
-
Cause: An attempt was made to create a constraint on an attribute of an object type column.
- ORA-02334: cannot infer type for column
-
Cause: A datatype was not declared for this column (in the CREATE TABLE) and an attempt was made to create a constraint on an attribute of this column.
- ORA-02335: invalid datatype for cluster column
-
Cause: An attempt was made to declare a CLUSTER column of datatype object, REF, nested table, VARRAY, LOB, or FILE.
- ORA-02336: column attribute cannot be accessed
-
Cause: An attempt was made to extract an attribute of an object type column.
- ORA-02337: not an object type column
-
Cause: An attempt was made to use dotted notation on a non-ADT column; that is, "a.b.c" where "a" is not an object type.
- ORA-02338: missing or invalid column constraint specification
-
Cause: A column constraint was not specified.
- ORA-02339: invalid column specification
-
Cause: An attempt was made to specify the PACKED or UNPACKED keyword for a non-object type column.
- ORA-02340: invalid column specification
-
Cause: An attempt was made to specify an UNPACKED column within a packed table.
- ORA-02342: replacement type has compilation errors
-
Cause: The use of the ALTER...REPLACE statement on a valid type caused a compilation error.
- ORA-02344: cannot revoke execute on a type with table dependents
-
Cause: An attempt was made to revoke execute on a type that has dependents.
- ORA-02345: cannot create a view with column based on CURSOR operator
-
Cause: A CURSOR operator was used as one of the SELECT elements in the subquery of a CREATE VIEW or CREATE TABLE ... AS SELECT statement.
- ORA-02347: cannot grant privileges on columns of an object table
-
Cause: An attempt was made to grant privileges on the columns of an object table.
- ORA-02348: cannot create VARRAY column with embedded LOB
-
Cause: An attempt was made to create a column of a VARRAY type which has an embedded LOB attribute. The LOB could be an attribute of a subtype of the declared type of VARRAY's element.
- ORA-02349: invalid user-defined type - type is incomplete
-
Cause: An attempt was made to use an incomplete type definition as a column or table datatype.
- ORA-02351: internal error: string\n
-
Cause: An unexpected error condition was detected.
- ORA-02352: error setting an OCI attribute: string\n
-
Cause: An OCI error has occurred.
- ORA-02353: error fetching an OCI attribute: string\n
-
Cause: An OCI error has occurred.
- ORA-02354: error in exporting/importing data\nstring
-
Cause: An error has occurred in a stream export or import operation. This message will be followed by another message giving more details about this error.
- ORA-02355: error opening file: string\n
-
Cause: An attempt to open the specified file for data export/import failed.
- ORA-02356: The database is out of space. The load cannot continue
-
Cause: The load was discontinued due to space exhaustion in the database.
- ORA-02357: header in file string may not contain correct information\n
-
Cause: The header may be corrupted.
- ORA-02358: error in exporting or importing data\n
-
Cause: An error has occurred in a stream export or import operation.
- ORA-02359: database version in file string is not valid\n
-
Cause: The specified file could not be used for this load because its database version was not compatible with the database version in the other files in the DUMPFILE clause.
- ORA-02360: fatal error during data export/import initialization\n
-
Cause: An unexpected error occurred during initialization for data export/import.
- ORA-02361: error while attempting to allocate number bytes of memory\n
-
Cause: An error occurred while trying to allocate memory. This is likely caused by insufficient memory.
- ORA-02362: error closing file: string\n
-
Cause: An attempt to close the specified file for data export/import failed.
- ORA-02363: error reading from file: string\n
-
Cause: An attempt to read from the specified file for data export/import failed.
- ORA-02364: error writing to file: string\n
-
Cause: An attempt to write to the specified file for data export or import failed.
- ORA-02365: error seeking in file: string\n
-
Cause: An attempt to seek to the specified position in file failed.
- ORA-02366: The following index(es) on table string were processed:
-
Cause: The table had some indexes which were loaded if there were no errors.
- ORA-02367: read ended but had expected more data from file string\n
-
Cause: A truncated or incomplete file was used for the load operation.
- ORA-02368: the following file is not valid for this load operation\n
-
Cause: A file could not be used for this load. See the following message for more information.
- ORA-02369: internal number in header in file string is not valid\n
-
Cause: The specified file could not be used for this load because the internal number in the header was not valid.
- ORA-02370: internal metadata in file string is not valid\n
-
Cause: The specified file could not be used for this load because the internal metadata stored in this file does not match the metadata stored in the first file piece set.
- ORA-02371: Loader must be at least version string.string.string.string.string for direct path
-
Cause: The loader being used is incompatible with this version of the kernel.
- ORA-02372: data for row: string \n
-
Cause: A conversion error occurred while loading data into a table. The message shows values for the field in the row that had the conversion error.
- ORA-02373: Error parsing insert statement for table string.
-
Cause: self-evident.
- ORA-02374: conversion error loading table string.string
-
Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.
- ORA-02375: conversion error loading table string.string partition string
-
Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.
- ORA-02376: invalid or redundant resource
-
Cause: a create, or alter profile command which names a resource not yet defined, or try to specify same resource twice.
- ORA-02377: invalid profile limit string
-
Cause: A value of 0 or lower was specified for the limit.
- ORA-02378: duplicate resource name string
-
- ORA-02379: profile string already exists
-
Cause: Try to create a profile which already exist
- ORA-02380: profile string does not exist
-
Cause: Try to assign a user to a non-existant profile
- ORA-02381: cannot drop PUBLIC_DEFAULT profile
-
Cause: Try to drop PUBLIC_DEFAULT profile
- ORA-02382: profile string has users assigned, cannot drop without CASCADE
-
- ORA-02383: illegal cost factor
-
Cause: Negative or UNLIMITED cost for this resourc
- ORA-02390: exceeded COMPOSITE_LIMIT, you are being logged off
-
- ORA-02391: exceeded simultaneous SESSIONS_PER_USER limit
-
Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSION_PER_USER clause of the user profile.
- ORA-02392: exceeded session limit on CPU usage, you are being logged off
-
- ORA-02393: exceeded call limit on CPU usage
-
- ORA-02394: exceeded session limit on IO usage, you are being logged off
-
- ORA-02395: exceeded call limit on IO usage
-
- ORA-02396: exceeded maximum idle time, please connect again
-
Cause: as stated
- ORA-02397: exceeded PRIVATE_SGA limit, you are being logged off
-
Cause: Only when using TP monitor
- ORA-02398: exceeded procedure space usage
-
Cause: Stored procedured used up too much space in SYSTEM Tablespace
- ORA-02399: exceeded maximum connect time, you are being logged off
-
Cause: As stated
- ORA-02401: cannot EXPLAIN view owned by another user
-
Cause: The view specified in the SQL statement belongs to another user and cannot be explained.
- ORA-02402: PLAN_TABLE not found
-
Cause: The table used by EXPLAIN to store row source information does not exist in the current schema.
- ORA-02403: plan table does not have correct format
-
Cause: The explicit plan table does not have the appropriate field definitions.
- ORA-02404: specified plan table not found
-
Cause: The specified plan table does cannot be found.
- ORA-02405: invalid sql plan object provided
-
Cause: The user provided a NULL, empty, or malformed object of type SQL_PLAN_TABLE_TYPE
- ORA-02420: missing schema authorization clause
-
Cause: the AUTHORIZATION clause is missing from a create schema statement.
- ORA-02421: missing or invalid schema authorization identifier
-
Cause: the schema name is missing or is incorrect in an authorization clause of a create schema statement.
- ORA-02422: missing or invalid schema element
-
Cause: A statement other than a create table, create view, or grant privilege appears in a create schema statement.
- ORA-02423: schema name does not match schema authorization identifier
-
Cause: a table definition with a schema name prepended to the table name does not match the schema name provided in the authorization clause of a create schema statement.
- ORA-02424: potential circular view references or unknown referenced tables
-
Cause: the create schema statement contains views that depend on other views in the containing create schema statement or they contain references to unknown tables.
- ORA-02425: create table failed
-
Cause: a create table statement failed in the create schema statement.
- ORA-02426: privilege grant failed
-
Cause: a grant privilege statement failed inthe create schema statement.
- ORA-02427: create view failed
-
Cause: a create view statement failed in the create schema statement.
- ORA-02428: could not add foreign key reference
-
Cause: could not add a foreign key reference because of error in declaration. Either referenced table does not exist or table does not have an unique key.
- ORA-02429: cannot drop index used for enforcement of unique/primary key
-
Cause: user attempted to drop an index that is being used as the enforcement mechanism for unique or primary key.
- ORA-02430: cannot enable constraint (string) - no such constraint
-
Cause: the named constraint does not exist for this table.
- ORA-02431: cannot disable constraint (string) - no such constraint
-
Cause: the named constraint does not exist for this table.
- ORA-02432: cannot enable primary key - primary key not defined for table
-
Cause: Attempted to enable a primary key that is not defined for the table.
- ORA-02433: cannot disable primary key - primary key not defined for table
-
Cause: Attempted to disable a primary key tht is not defined for the table.
- ORA-02434: cannot enable unique(string) - unique key not defined for table
-
Cause: attempted to enable a unique key that is not defined for the table.
- ORA-02435: cannot disable unique(string) - unique key not defined for table
-
Cause: attempted to disable a unique key that is not deined for the table.
- ORA-02436: date or system variable wrongly specified in CHECK constraint
-
Cause: An attempt was made to use a date constant or system variable, such as USER, in a check constraint that was not completely specified in a CREATE TABLE or ALTER TABLE statement. For example, a date was specified without the century.
- ORA-02437: cannot validate (string.string) - primary key violated
-
Cause: attempted to validate a primary key with duplicate values or null values.
- ORA-02438: Column check constraint cannot reference other columns
-
Cause: attempted to define a column check constraint that references another column.
- ORA-02439: Unique index on a deferrable constraint is not allowed
-
Cause: attempted to enable a deferrable primary key/unique constraint that has an existing unique index on the constraint columns.
- ORA-02440: Create as select with referential constraints not allowed
-
Cause: create table foo (... ref. con. ...) as select ...;
- ORA-02441: Cannot drop nonexistent primary key
-
Cause: alter table drop primary key - primary key does not exist.
- ORA-02442: Cannot drop nonexistent unique key
-
Cause: alter table drop unique (col list) - unique specification does not exist.
- ORA-02443: Cannot drop constraint - nonexistent constraint
-
Cause: alter table drop constraint <constraint_name>
- ORA-02444: Cannot resolve referenced object in referential constraints
-
Cause: attempted to define foreign key referencing an object which cannot be resolved to a base table reference
- ORA-02445: Exceptions table not found
-
Cause: the explicity or implicity declared exceptions table does not exist.
- ORA-02446: CREATE TABLE ... AS SELECT failed - check constraint violated
-
Cause: An attempt was made to use a CREATE TABLE ... AS SELECT statement when some rows violated one or more CHECK constraints.
- ORA-02447: cannot defer a constraint that is not deferrable
-
Cause: An attempt was made to defer a nondeferrable constraint
- ORA-02448: constraint does not exist
-
Cause: The named constraint does not exist
- ORA-02449: unique/primary keys in table referenced by foreign keys
-
Cause: An attempt was made to drop a table with unique or primary keys referenced by foreign keys in another table.
- ORA-02450: Invalid hash option - missing keyword IS
-
Cause: Missing IS keyword.
- ORA-02451: duplicate HASHKEYS specification
-
Cause: The HASHKEYS option is specified more than once.
- ORA-02452: invalid HASHKEYS option value
-
Cause: The specified HASHKEYS option must be an integer value.
- ORA-02453: duplicate HASH IS specification
-
Cause: The HASH IS option is specified more than once.
- ORA-02454: Number of hash keys per block (string) exceeds maximum of string
-
Cause: The SIZE argument is too small.
- ORA-02455: The number of cluster key column must be 1
-
Cause: When specifing the HASH IS option, the number of key columns must be 1.
- ORA-02456: The HASH IS column specification must be NUMBER(*,0)
-
Cause: The column specification must specify an integer.
- ORA-02457: The HASH IS option must specify a valid column
-
Cause: The HASH IS column name is not specified in the cluster definition.
- ORA-02458: HASHKEYS must be specified for a HASH CLUSTER
-
Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER.
- ORA-02459: Hashkey value must be a positive integer
-
Cause: The value of the hash key was not a positive number.
- ORA-02460: Inappropriate index operation on a hash cluster
-
Cause: An attempt to create a cluster index was issued on a hash cluster.
- ORA-02461: Inappropriate use of the INDEX option
-
Cause: This option is only valid for non hash clusters.
- ORA-02462: Duplicate INDEX option specified
-
Cause: The INDEX option is specified more than once.
- ORA-02463: Duplicate HASH IS option specified
-
Cause: The HASH IS option is specified more than once.
- ORA-02464: Cluster definition can not be both HASH and INDEX
-
Cause: The cluster can either be a hash or indexed cluster - not both.
- ORA-02465: Inappropriate use of the HASH IS option
-
Cause: This option is only valid for clusters
- ORA-02466: The SIZE and INITRANS options cannot be altered for HASH CLUSTERS.
-
Cause: An attempt was made to change the SIZE and INITRANS options after the hash cluster was created.
- ORA-02467: Column referenced in expression not found in cluster definition
-
Cause: A column in the hash is expression was not present in cluster definition.
- ORA-02468: Constant or system variable wrongly specified in expression
-
Cause: A constant or system variable was specified in the hash expression.
- ORA-02469: Hash expression does not return an Oracle Number.
-
Cause: Result of evaluating hash expression is not an Oracle Number.
- ORA-02470: TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
-
Cause: An attempt was made to specify SYSDATE, UID, USER, ROWNUM, or LEVEL in hash expression.
- ORA-02471: SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression.
-
Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expressions.
- ORA-02472: PL/SQL functions not allowed in hash expressions
-
Cause: A PL/SQL function was used in the hash expression.
- ORA-02473: Error while evaluating the cluster's hash expression.
-
Cause: An error occurred while evaluating the clusters hash expression.
- ORA-02474: Fixed hash area extents used (string) exceeds maximum allowed (string)
-
Cause: The number of extents required for creating the fixed hash area exceeds the maximum number allowed.
- ORA-02475: maximum cluster chain block count of string has been exceeded
-
Cause: The number of blocks in a cluster chain exceeds the maximum number allowed.
- ORA-02476: can not create index due to parallel direct load on table
-
Cause: A parallel direct load is occurring to the specified table.
- ORA-02477: can not perform parallel direct load on object string
-
Cause: A parallel direct load is not possible because an index is is being created on the table.
- ORA-02478: merge into base segment would overflow MAXEXTENTS limit
-
Cause: Merge of temporary segment into base segment failed because MAXEXTENTS was larger than the total in the temp and base segments
- ORA-02479: error while translating file name for parallel load
-
Cause: An invalid file name was specified to load data into.
- ORA-02481: Too many processes specified for events (max string)
-
Cause: Too many processes specified than allowed per event.
- ORA-02482: Syntax error in event specification (string)
-
Cause: Illegal event string
- ORA-02483: Syntax error in process specification (string)
-
Cause: Illegal process string
- ORA-02484: Invalid _trace_buffers parameter specification (string)
-
Cause: Bad process or size in _trace_buffers INIT.ORA parameter.
- ORA-02485: Invalid _trace_options parameter specification (string)
-
Cause: Bad syntax for _trace_options INIT.ORA parameter.
- ORA-02486: Error in writing trace file string
-
Cause: Error occurred in creating/writing the file.
- ORA-02487: Error in converting trace data
-
Cause: Incompatible binary trace data was specified.
- ORA-02488: Error encountered when accessing file [string] for trace conversion
-
Cause: An attempt was made to open or access the trace file during a trace conversion.
- ORA-02490: missing required file size in RESIZE clause
-
Cause: No value was specified for the RESIZE clause.
- ORA-02491: missing required keyword ON or OFF in AUTOEXTEND clause
-
Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause.
- ORA-02492: missing required file block increment size in NEXT clause
-
Cause: No value was specified for the NEXT clause.
- ORA-02493: invalid file increment size in NEXT clause
-
Cause: A non-integer value was used for the NEXT clause of the DATAFILE list.
- ORA-02494: invalid or missing maximum file size in MAXSIZE clause
-
Cause: UNLIMITED was not specified, or an invalid integer value was specified, for the MAXSIZE clause in the DATAFILE file list. The MAXSIZE value cannot be smaller than the SIZE value.
- ORA-02495: cannot resize file string, tablespace string is read only
-
Cause: An attempt was made to resize a data file in a tablespace that is read only.
- ORA-02496: cannot alter or drop an individual chunk tablespace
-
Cause: An attempt was made to alter or drop an individual chunk tablespace which is part of a tablespace set.
- ORA-02500: IN SHARD option already specified
-
Cause: In the CREATE TABLESPACE, the IN SHARD option was specified more than once.
- ORA-02501: invalid option for CREATE TABLESPACE SET
-
Cause: An invalid option IN SHARD was specified for the CREATE TABLESPACE SET statement.
- ORA-02502: USING TEMPLATE can only be used in CREATE TABLESPACE SET
-
Cause: An attempt to specify the TEMPLATE option without the CREATE TABLESPACE SET statement failed.
- ORA-02503: USING TEMPLATE option already specified
-
Cause: In the CREATE TABLESPACE SET, the USING TEMPLATE option was specified more than once.
- ORA-02504: SHARDSPACE string does not exist
-
Cause: A nonexistent SHARDSPACE was specified in the CREATE TABLESPACE or CREATE TABLESPACE SET statement.
- ORA-02505: IN SHARDSPACE option already specified
-
Cause: In the CREATE TABLESPACE SET, the IN SHARDSPACE option was specified more than once.
- ORA-02506: CREATE TABLESPACE SET statement requires the SHARDSPACE keyword
-
Cause: The SHARDSPACE option was not specified in the CREATE TABLESPACE SET statement.
- ORA-02507: missing SHARDSPACE keyword
-
Cause: The SHARDSPACE keyword was omitted in the IN SHARDSPACE option.
- ORA-02508: attempted to create a shard tablespace in a non-shard database
-
Cause: An attempt was made to create a shard tablespace in a non-shard database.
- ORA-02509: A SHARDSPACE cannot handle several PARTITIONSETS.
-
Cause: An attempt was made to define multiple PARTITIONSETS in the SHARDSPACE.
- ORA-02510: A tablespace set cannot be referenced at the table level.
-
Cause: An attempt was made to reference a tablespace set at the table level.
- ORA-02511: SQL query not allowed; the shard DDL is disabled.
-
Cause: An attempt was made to run a shard DDL on a nondeployed shard or with the shard DDL option disabled.
- ORA-02512: only one PARTITIONSET option may be specified
-
Cause: The CREATE TABLE statement contained more than one PARTITIONSET option.
- ORA-02513: invalid sharded table PARTITIONSET method
-
Cause: An invalid PARTITIONSET method was specified in the CREATE TABLE statement. A table may be partitioned by RANGE or LIST.
- ORA-02514: list PARTITIONSET method expects a single partitioning column
-
Cause: The number of columns in a PARTITIONSET column list exceeded the legal limit of one for list partitioned tables.
- ORA-02515: cannot interval partition set a sharded table
-
Cause: Interval PARTITIONSET was not supported for a sharded table.
- ORA-02516: invalid SHARDED type specified
-
Cause: Only tables can have the SHARDED type.
- ORA-02517: PARTITIONSET and CLUSTER clauses are mutually exclusive
-
Cause: definition of a table with both PARTITIONSET and CLUSTER clauses which is illegal.
- ORA-02518: invalid PARTITIONSET clause specified in a non sharded table
-
Cause: definition of a non sharded table with PARTITIONSET clause is illegal.
- ORA-02519: cannot perform cross-shard operation. Chunk "string" is unavailable
-
Cause: All shards where this chunk is stored were unavailable.
- ORA-02520: Shard data object number exceeds UB4MAXVAL
-
Cause: All shards where this chunk is stored were unavailable.
- ORA-02521: attempted to enable shard DDL in a non-shard database
-
Cause: An attempt was made to enable shard DDL in a non-shard database.
- ORA-02522: cannot get a new data object number range from the Global Data Services (GDS) catalog
-
Cause: An attempt was made to get a new range of data object numbers which resulted in a failure.
- ORA-02523: The table being created is not SHARDED.
-
Cause: PARENT clause was specified on a non-sharded table.
- ORA-02524: Invalid parent table specified.
-
Cause: The parent table specified was not a valid identifier.
- ORA-02525: child and parent table owner mismatch.
-
Cause: The child and parent tables did not have the same owner.
- ORA-02526: child and parent table sharding method mismatch.
-
Cause: The child and parent tables did not have the same sharding method.
- ORA-02527: child and parent table shard key columns mismatch.
-
Cause: The child and parent tables did not have the same shard key columns.
- ORA-02528: child and table partition set key columns mismatch.
-
Cause: The child and parent tables did not have the same partition set key columns.
- ORA-02529: invalid parent table.
-
Cause: The table name specified was not the one of the root table.
- ORA-02530: parent table not specified
-
Cause: An attempt was made to create a child table without specifying the PARENT clause.
- ORA-02531: shard name not found
-
Cause: An attempt was made to create a sharded table on a non-sharded database.
- ORA-02532: sharding columns must form a subset key of key columns of a UNIQUE index
-
Cause: An attempt was made to create a primary key constaint on non-sharding columns.
- ORA-02533: missing PARTITION clause
-
Cause: The PARTITION clause was expected but was not supplied.
- ORA-02534: invalid PARTITION clause
-
Cause: The PARTITION clause was supplied with CONSISTENT HASH sharding.
- ORA-02535: missing TABLESPACE SET clause
-
Cause: The TABLESPACE SET clause was expected but was not supplied.
- ORA-02536: invalid TABLESPACE SET name: string
-
Cause: The TABLESPACE SET supplied did not exist.
- ORA-02537: Data file name specified but not supported by tablespace set template
-
Cause: Data file explicit name was specified as part of the tablespace set template. Only Oracle Managed Files are supported by a tablespace set.
- ORA-02538: invalid TABLESPACE SET clause
-
Cause: The TABLESPACE SET clause was not expected.
- ORA-02539: the operation is not supported across shards
-
Cause: An attempt was made to perform an operation with shard DDL enabled, which is not supported for propagation from catalog to shards.
- ORA-02540: global indexes are not supported for sharded tables
-
Cause: An attempt was made to create a global index on a sharded table, which is not supported.
- ORA-02541: TABLESPACE SET is required
-
Cause: The TABLESPACE SET clause was not supplied when creating an index on a system-managed sharded table.
- ORA-02542: invalid partitioning method specified with user-defined sharding
-
Cause: The partitioning method specified was not compatible with user-defined sharding.
- ORA-02543: invalid partitioning method specified with system-managed or composite sharding
-
Cause: The partitioning method specified was not compatible with system-managed or composite sharding.
- ORA-02544: sharding or partition set column datatype is not supported
-
Cause: Supported data types were not used for the sharding or partition set columns.
- ORA-02545: sharding or partition set column can not be a virtual column
-
Cause: Virtual column was used in the sharding or partition set key, which is not supported.
- ORA-02546: The LONG data type is not supported for duplicated tables.
-
Cause: An invalid option was specified while creating duplicated tables.
- ORA-02547: Option string is not supported for duplicated tables
-
Cause: An invalid option was specified while creating duplicated tables.
- ORA-02548: Option string is not supported for duplicated tables
-
Cause: An invalid option was specified while altering duplicated tables.
- ORA-02549: cannot create a sharded table with index organization
-
Cause: An attempt was made to create an index-organized sharded table under system-managed sharding or composite sharding, which is not supported.
- ORA-02550: Creating duplicated table not allowed when shard DDL is disabled
-
Cause: Duplicated tables were created when shard DDL was disabled.
- ORA-02551: Truncate table for duplicated tables is not supported
-
Cause: Invalid operation was specified on a duplicated table.
- ORA-02552: invalid shard name
-
Cause: The shard name specified was not valid.
- ORA-02553: TABLESPACE is required
-
Cause: The TABLESPACE clause was not supplied when specifying a partition of a user-defined sharded table.
- ORA-02554: invalid DROP TABLESPACE SET
-
Cause: The DROP TABLESPACE SET command was not compatible with user-defined sharding.
- ORA-02555: Online redefinition is not supported for sharded and duplicated tables.
-
Cause: An attempt was made to perform online redefinition on a sharded table or a duplicated table for sharding, which is not supported.
- ORA-02556: Only sharded or duplicated tables are supported across shards.
-
Cause: An attempt was made to create a non-sharded, non-duplicated table across shards, which is not supported.
- ORA-02557: cannot operate on sharded objects when shard DDL is disabled
-
Cause: An attempt was made to operate on a sharded or a duplicated object across shards when the shard DDL was not enabled.
- ORA-02558: cannot operate on non-sharded objects when shard DDL is enabled
-
Cause: An attempt was made to ALTER or DROP a non-sharded object when the shard DDL was enabled.
- ORA-02559: The TABLESPACE SET string does not belong to the shardspace of the table.
-
Cause: The TABLESPACE SET supplied existed in a different shardspace from the one to which the table belonged.
- ORA-02560: cannot modify partitions for system-managed or composite sharded tables.
-
Cause: An attempt was made to modify partitions on system-managed or composite sharded tables.
- ORA-02561: maximum number of columns in a duplicated table without primary key is 999
-
Cause: An attempt was made to create a duplicated table with 1000 columns when there was no primary key defined. Note that unused columns in the table are counted toward the 1000 column limit.
- ORA-02562: cannot create a duplicated table in a non-shard schema
-
Cause: An attempt was made to create a duplicated table in a non-shard schema.
- ORA-02563: XMLType column in a duplicated table cannot be used in non-ASSM tablespace "string"
-
Cause: XMLType column in a duplicated table required an automatic segment space management (ASSM) tablespace.
- ORA-02564: rebuild outline is not supported across shards.
-
Cause: An attempt was made to rebuild an outline with shard DDL enabled, which is not supported.
- ORA-02565: cannot use individual chunk tablespace
-
Cause: An individual chunk tablespace which was part of a tablespace set was used.
- ORA-02566: cannot create duplicated table - insufficient privileges
-
Cause: An attempt was made to create a duplicated table when the user did not have sufficient privileges.
- ORA-02567: cannot create a sharded table with empty columns
-
Cause: An attempt was made to create a sharded table without any columns.
- ORA-02568: cannot create an identity column in a sharded table
-
Cause: An attempt was made to create a sharded table with an identity column.
- ORA-02569: cannot drop a system tablespace string when sharding environment is deployed
-
Cause: An attempt was made to drop a system tablespace part of the sharding environment when the sharding environment was deployed.
- ORA-02570: cannot alter user password - insufficient privileges
-
Cause: An attempt was made to alter the password for a user who created duplicated tables but did not have the privilege to execute the ALTER DATABASE LINK statement.
- ORA-02571: ALTER TABLE TRUNCATE PARTITION for duplicated tables is not supported
-
Cause: An invalid operation was specified on a duplicated table.
- ORA-02572: A non all-shard user cannot operate on schema objects that are sharded or duplicated on all shards.
-
Cause: An attempt was made to operate on a sharded or duplicated schema object by a non all-shard user.
- ORA-02573: cannot enable shard DDL when current_schema has been changed
-
Cause: Shard DDL is not supported after a session's current schema has been altered.
- ORA-02574: Sharded table cannot be a nested table.
-
Cause: An attempt was made to create a nested sharded table, which is not supported.
- ORA-02575: Invalid sharding method for a deployed sharded database
-
Cause: An invalid sharding method was set for a sharded database.
- ORA-02576: number of partition set specifications is not equal to the number of shardspaces
-
Cause: Fewer or more number of partition set specifications were specified than the number of shardspaces in the composite sharding environment.
- ORA-02577: cannot specify PARTITIONSET in a non-composite sharding environment
-
Cause: PARTITIONSETS were specified while creating a sharded table in non-composite sharding environment.
- ORA-02578: missing PARTITIONSET specification
-
Cause: PARTITIONSET specifications were missing.
- ORA-02579: cannot create a tablespace set with SMALLFILE option
-
Cause: An attempt was made to create a tablespace set with the SMALLFILE option.
- ORA-02580: cannot add or drop data files from a tablespace set
-
Cause: An attempt was made to add or drop a data file from a tablespace set.
- ORA-02581: cannot create foreign key constraints on columns referencing a duplicated table
-
Cause: An attempt was made to create a foreign key constraint in a sharded table on a column referencing a duplicated table.
- ORA-02582: invalid tablespace set name specified for the partition set
-
Cause: The tablespace set name specified for the partition set was either invalid or belonged to a different shardspace.
- ORA-02583: option PARALLEL not supported when creating duplicated table as select from another table
-
Cause: An attempt was made to create a duplicated table as select from another table in parallel mode.
- ORA-02584: INMEMORY options not supported for duplicated tables
-
Cause: An attempt was made to create or alter a duplicated table by enabling INMEMORY options.
- ORA-02585: create tablepsace set failure, one of its tablespaces not created
-
Cause: One of the tablespaces in the tablespace set was not created.
- ORA-02586: cannot change duplicated table refresh rate in a non-catalog database
-
Cause: An attempt was made to change the dupl_table_refresh_rate in the non-catalog database.
- ORA-02587: create duplicated table of Object Type is not supported
-
Cause: An attempt was made to create a duplicated table of object type.
- ORA-02588: minimum refresh rate for duplicated table is 20 seconds
-
Cause: An attempt was made to change the dupl_table_refresh_rate to less than 20 seconds.
- ORA-02589: invalid partition set name
-
Cause: An invalid partition set name was specified.
- ORA-02590: invalid sequence of partition sets
-
Cause: The sequence used to specify partition sets was invalid.
- ORA-02591: cannot specify a common tablespace set for indexes on a sharded table in composite sharding
-
Cause: An attempt was made to specify a common tablespace set for indexes on a sharded table in a composite sharding environment which is not supported.
- ORA-02592: cannot drop user until all shard databases are up and all gsm_requests are completed
-
Cause: An attempt was made to drop a user who owns a duplicated table when the shard database was down or the gsm_requests were pending execution.
- ORA-02593: cannot drop duplicated table until all shard databases are up and all gsm_requests are completed
-
Cause: An attempt was made to drop a duplicated table when the shard database was down or the gsm_requests were pending execution.
- ORA-02594: cannot alter shard user password until all shard databases are up and all gsm_requests are completed
-
Cause: An attempt was made to alter shard user password when the shard database was down or the gsm_requests were pending execution.
- ORA-02595: Abstract data type is not supported for duplicated tables.
-
Cause: An invalid option was specified while creating duplicated tables.
- ORA-02596: cannot truncate duplicated table on a shard database
-
Cause: An attempt was made to truncate a duplicated table on a shard database.
- ORA-02597: The read-only option is not supported for sharded tables.
-
Cause: An invalid option was specified while creating a sharded table.
- ORA-02598: tablespace specified in the SQL command does not exist in the shard
-
Cause: A DROP or ALTER TABLESPACE operation was attempted on a shard where the tablespace does not exist.
- ORA-02599: cannot drop partitionset column
-
Cause: An attempt was made to drop a column used as the super-partitioning key for a sharded table.
- ORA-02600: credential name is invalid: string
-
Cause: An invalid credential name was specified.
- ORA-02601: credential already exists: string
-
Cause: Credential name specified already used by an existing object.
- ORA-02602: credential does not exist: string
-
Cause: The specified credential does not exist.
- ORA-02603: file name is invalid: string
-
Cause: An invalid file name was specified.
- ORA-02604: file already exists: string
-
Cause: File name specified already used by an existing object.
- ORA-02605: file does not exist: string
-
Cause: The specified file does not exist.
- ORA-02606: destination name is invalid: string
-
Cause: An invalid destination name was specified.
- ORA-02607: destination not specified
-
Cause: A destination must be specified in the command.
- ORA-02608: destination does not exist: string
-
Cause: The specified destination does not exist.
- ORA-02609: remote scheduler agent not running
-
Cause: The specified remote scheduler agent cannot be contacted.
- ORA-02610: Remote job failed with error: string
-
Cause: Unable to successfully run specified job.
- ORA-02611: shardgroup name is invalid: string
-
Cause: An invalid shardgroup name was specified.
- ORA-02612: shardgroup does not exist: string
-
Cause: The specified shardgroup did not exist.
- ORA-02613: shardspace name is invalid: string
-
Cause: An invalid shardspace name was specified.
- ORA-02614: shardspace does not exist: string
-
Cause: The specified shardspace did not exist.
- ORA-02615: Neither a shardgroup nor a shardspace name was specified.
-
Cause: A shardgroup or shardspace name was not specified.
- ORA-02616: Both a shardgroup and a shardspace name were specified.
-
Cause: A shardgroup and a shardspace name were both specified. For this command, either a shardgroup or shardspace name may be specified, but not both.
- ORA-02617: Neither a credential nor login information was specified
-
Cause: Either a credential or login information must be specified.
- ORA-02618: Both a credential and login information was specified
-
Cause: For this command, either a credential or login information may be specified, not both.
- ORA-02619: Both a file name and file contents were specified.
-
Cause: A file name and file contents were both specified.
- ORA-02620: db_domain value too long: string
-
Cause: The value specified for db_domain exceeded the 128 character limit.
- ORA-02621: file in use by shard 'string'
-
Cause: The specified file was in use by an undeployed shard.
- ORA-02622: Shard is not open in write mode.
-
Cause: The shard was not opened in the correct mode.
- ORA-02623: Failed to create broker configuration with error string.
-
Cause: A request to create the broker configuration failed.
- ORA-02624: Failed to enable broker configuration with error string.
-
Cause: A request to enable the broker configuration failed.
- ORA-02625: Failed to add standby shard string to the broker configuration with error string.
-
Cause: A request to add the shard to the broker configuration failed.
- ORA-02626: Failed to enable standby shard string for the broker configuration with error string.
-
Cause: A request to enable the shard for the broker configuration failed.
- ORA-02627: Shardspace 'string' does not exist.
-
Cause: The requested shardspace did not exist.
- ORA-02628: invalid shardgroup name 'string'
-
Cause: The shardgroup name was invalid.
- ORA-02629: cannot modify deployed shardgroup string
-
Cause: The shardgroup was already deployed and could no longer be modified.
- ORA-02630: cannot modify primary or standby status of shardgroup string
-
Cause: The shardgroup already contained a shard and could not be converted from a primary shard to a standby shard or from a standby shard to a primary shard.
- ORA-02631: The shardspace name 'string' is invalid.
-
Cause: An invalid shardspace name was provided.
- ORA-02632: cannot modify deployed shardspace 'string'
-
Cause: The shardspace was already deployed and could no longer be modified.
- ORA-02633: The shardspace 'string' is invalid.
-
Cause: An invalid shardpsace name was provided.
- ORA-02634: Oracle XML DB is not installed.
-
Cause: Oracle XML DB was required for remote scheduler agent configuration but was not installed.
- ORA-02635: The value of chunks must be greater than one.
-
Cause: An invalid value of chunks was passed.
- ORA-02636: Shard is already in shardspace string.
-
Cause: The shard was already in a shardspace.
- ORA-02637: The source and target shards are in different shardgroups.
-
Cause: The source and target shards for a chunk move operation were in different shardgroups.
- ORA-02638: The shardgroup string is not deployed.
-
Cause: The containing shardgroup for the source and target shards was not yet deployed.
- ORA-02639: Source and target shards are the same.
-
Cause: The source and target shards for a chunk move were the same.
- ORA-02640: Shardspace already has a primary shardgroup.
-
Cause: An attempt was made to add a primary shardgroup to a shardspace that already had a primary shardgroup. When Oracle Data Guard replication is used, only one primary shardgroup is allowed in each shardspace.
- ORA-02641: Shard string was not deployed because it does not contain a corresponding shard in all shardgroups.
-
Cause: The shard did not have a corresponding shard in all shardgroups in an Oracle Data Guard configuration, therefore it was not deployed.
- ORA-02642: There were no new shards to deploy.
-
Cause: The 'deploy' command was issued, but there were no new shards to deploy.
- ORA-02643: failed to enable fast-start failover with error string
-
Cause: A request to enable fast-start failover failed.
- ORA-02644: Shard 'string' already exists in specified rack 'string'.
-
Cause: The specified rack already contained another shard in the same Oracle Data Guard configuration.
- ORA-02645: only one primary shard allowed per shardspace
-
Cause: The specified shardspace already contained a primary shard.
- ORA-02646: Standby shards not allowed in Oracle GoldenGate configurations.
-
Cause: The Oracle GoldenGate configurations contained standby shards.
- ORA-02647: The rack name 'string' is invalid.
-
Cause: An invalid rack name was provided.
- ORA-02648: Password for SYS account was not specified.
-
Cause: A SYS password was not specified when creating a new shard using Oracle Database Configuration Assistant (DBCA).
- ORA-02649: cannot change region for a system-managed or composite shard
-
Cause: An attempt was made to change the region value for a system-managed or composite shard.
- ORA-02650: remote scheduler agent error: string
-
Cause: An operation failed when performed using the remote scheduler agent.
- ORA-02651: The specified pool 'string' is not sharded.
-
Cause: The specified pool was not sharded.
- ORA-02652: The maximum number of sharded GDS pools has been reached.
-
Cause: The maximum number of Global Data Services (GDS) sharded pools had been reached.
- ORA-02653: shardgroup already exists: string
-
Cause: The specified shardgroup was already in existence.
- ORA-02654: Shards and shardgroups cannot exist in the same database pool.
-
Cause: The specified database pool already contained either a conflicting shard or shardgroup.
- ORA-02655: not a sharded catalog
-
Cause: The catalog was not enabled for sharding and a sharding command was executed.
- ORA-02656: shardspace already exists: string
-
Cause: The specified shardspace was already in existence.
- ORA-02657: too few chunks specified for shardspace
-
Cause: The number of chunks in the specified shardspace was less than twice the number of shards in one of its shardgroups.
- ORA-02658: shardspace already exists: string
-
Cause: The specified shardspace was already in existence.
- ORA-02659: cannot remove a shard which contains chunks
-
Cause: An attempt was made to remove a shard which currently contains chunks.
- ORA-02660: Shard 'string' was also removed.
-
Cause: When a shard was removed, all other shards in the same Oracle Data Guard configuration were also removed.
- ORA-02661: shardspace and shardgroup parameters are mutually exclusive
-
Cause: A command was issued that included both the shardspace and and shardgroup parameters.
- ORA-02662: Chunk number 'string' does not exist on the source database.
-
Cause: An invalid chunk number or source database was provided.
- ORA-02663: Remote scheduler agents may be listening on previously specified port.
-
Cause: The '-agent_port' parameter specified a new agent port value. The already registered scheduler agents must re-register with the catalog database to use this new value.
- ORA-02664: Specified port may be in use.
-
Cause: The '-agent_port' parameter specified a new agent port value. The port specified may already have been in use by another process in the system.
- ORA-02665: shardspace not specified
-
Cause: A command was issued that did not include shardspace".
- ORA-02666: Tablespace set required to perform this operation was not found.
-
Cause: An attempt was made to perform a chunk management operation before creating a tablespace set.
- ORA-02667: Root table required to perform this operation was not found.
-
Cause: An attempt was made to perform a chunk management operation before creating a sharded table.
- ORA-02668: Observer cannot be started for database "string"
-
Cause: One or more conditions required by Data Guard observer were not met.
- ORA-02669: data type or length of a partitionset column in a sharded table cannot be changed
-
Cause: An attempt was made to issue an ALTER TABLE statement to modify the data type or length of a column used to super-partition the specified sharded table.
- ORA-02670: unsupported SQL construct: string
-
Cause: The query had a construct that was not supported for inter shard query.
- ORA-02671: DML are not allowed on more than one shard
-
Cause: The DML was applied to more than one shard.
- ORA-02672: cannot update sharding key
-
Cause: An attempt was made to update the sharding key value using the UPDATE command.
- ORA-02673: string maps to multiple shards
-
Cause: The aggregate, group by, semi-join, or anti-join subquery was mapped to multiple shards.
- ORA-02674: illegal join predicate on sharding key
-
Cause: The query had illegal or no join predicate on the sharding key.
- ORA-02675: sharded table string outer joined with replicated table string
-
Cause: The query had a sharded table outer joined to the replicated table.
- ORA-02676: non-equality join on sharding key
-
Cause: The query had a non-equality join on the sharding key.
- ORA-02677: queries not supported on objects with user-specified sharding
-
Cause: The query had an object defined by user-specified sharding.
- ORA-02678: cross shard queries not supported on composite sharding
-
Cause: The query had an object defined under composite sharding.
- ORA-02679: queries involving private and sharded tables not supported
-
Cause: The query referenced a private and a sharded table.
- ORA-02680: unsupported construct referred in the query
-
Cause: The query referenced unsupported constructs which could not be fetched from the shard.
- ORA-02681: array DML not supported on a sharded table
-
Cause: The statement attempts an array DML operation on a sharded table.
- ORA-02682: shard key missing in INSERT statement
-
Cause: The INSERT statement was used to insert a row in the sharded table without inserting a value for the shard column.
- ORA-02683: inconsistent shard schema
-
Cause: The schema definition on the shard and the coordinator did not match.
- ORA-02684: invalid partition for the chunk string
-
Cause: A valid partition was not found for the chunk number passed to the shard database.
- ORA-02685: cannot rename a duplicated table on a shard database
-
Cause: An attempt was made to rename a duplicated table on a shard database.
- ORA-02686: query returned data from string percent of total chunks
-
Cause: Some of the chunks were not accessible in the system.
- ORA-02687: target partition key does not map to any partition
-
Cause: An attempt was made to update or delete a record of a range or list-based sharded table with a partition key that did not belong to any of the partition.
- ORA-02688: sharded table string does not exist
-
Cause: An attempt was made to add a partition set to a sharded table that did not exist.
- ORA-02689: cannot alter duplicated table until GSM_REQUEST to CREATE DUPLICATED TABLE are completed on all shards
-
Cause: An attempt was made to alter a duplicated table when the GSM_REQUEST to create duplicated table materialized view was pending execution.
- ORA-02690: cannot add existing value to partition sets
-
Cause: The value added to the list partition set already existed for the table.
- ORA-02691: duplicate partition set name
-
Cause: The name of a partition set of a sharded table being created was not unique.
- ORA-02692: cannot perform cross-shard operation. Some shards are unavailable.
-
Cause: One or more shards were unavailable during the cross-shard operation.
- ORA-02700: osnoraenv: error translating ORACLE_SID
-
Cause: Two-task driver could not find the value of ORACLE_SID in the environment.
- ORA-02701: osnoraenv: error translating oracle image name
-
Cause: ORACLE_HOME environment variable not set.
- ORA-02702: osnoraenv: error translating orapop image name
-
Cause: ORACLE_HOME environment variable not set.
- ORA-02703: osnpopipe: pipe creation failed
-
Cause: The pipe driver failed to create pipes for communications with the orapop process.
- ORA-02704: osndopop: fork failed
-
Cause: The two-task driver could not fork orapop.
- ORA-02705: osnpol: polling of communication channel failed
-
Cause: The pipe driver failed while polling the communications channel.
- ORA-02706: osnshs: host name too long
-
Cause: The length of your host-string specified by the TWO_TASK environment variable exceeds the ORACLE system-imposed limit.
- ORA-02707: osnacx: cannot allocate context area
-
Cause: The invoked Unix two-task driver could not allocate heap space for the context area.
- ORA-02708: osnrntab: connect to host failed, unknown ORACLE_SID
-
Cause: The invoked Unix two-task driver failed to find an entry in oratab for the sid you supplied.
- ORA-02709: osnpop: pipe creation failed
-
Cause: The pipe driver failed to create pipes for two-task communications with the oracle shadow process.
- ORA-02710: osnpop: fork failed
-
Cause: The pipe driver could not fork the oracle shadow process.
- ORA-02711: osnpvalid: write to validation channel failed
-
Cause: The pipe driver failed to write to the orapop process.
- ORA-02712: osnpop: malloc failed
-
Cause: The pipe driver failed to allocate enough heap space for its context area buffers.
- ORA-02713: osnprd: message receive failure
-
Cause: The pipe driver failed to read a message from the communications channel.
- ORA-02714: osnpwr: message send failure
-
Cause: The pipe driver failed to write a message to the communications channel.
- ORA-02715: osnpgetbrkmsg: message from host had incorrect message type
-
Cause: The pipe driver received a message having an unrecognizable message type.
- ORA-02716: osnpgetdatmsg: message from host had incorrect message type
-
Cause: The Pipe driver received a message having an unrecognizable message type.
- ORA-02717: osnpfs: incorrect number of bytes written
-
Cause: The Pipe driver sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes furnished to the driver.
- ORA-02718: osnprs: reset protocol error
-
Cause: The two-task driver could not reset the connection.
- ORA-02719: osnfop: fork failed
-
Cause: The fast driver could not fork the oracle shadow process.
- ORA-02720: osnfop: shmat failed
-
Cause: When the fast driver was invoked, processes failed to attach to the shared memory buffer. You probably supplied an illegal shared memory attach address, or the system ran out of data space to accomodate the buffer.
- ORA-02721: osnseminit: cannot create semaphore set
-
Cause: The Fast driver failed to get a semaphore set.
- ORA-02722: osnpui: cannot send break message to orapop
-
Cause: The Pipe driver could not send a break message to orapop.
- ORA-02723: osnpui: cannot send break signal
-
Cause: The Pipe driver could not send a break message to the ORACLE shadow process.
- ORA-02724: osnpbr: cannot send break message to orapop
-
Cause: The Pipe driver could not send a break message to orapop.
- ORA-02725: osnpbr: cannot send break signal
-
Cause: The Pipe driver could not send a break message to the ORACLE shadow process.
- ORA-02726: osnpop: access error on oracle executable
-
Cause: The Pipe driver could not access the oracle executable.
- ORA-02727: osnpop: access error on orapop executable
-
Cause: The Pipe driver could not access the orapop executable.
- ORA-02728: osnfop: access error on oracle executable
-
Cause: The Fast driver could not access the oracle executable.
- ORA-02729: osncon: driver not in osntab
-
Cause: The driver you have specified is not supported.
- ORA-02730: osnrnf: cannot find user logon directory
-
Cause: The driver you have specified could not find your logon directory while searching for your local .sqlnet file.
- ORA-02731: osnrnf: malloc of buffer failed
-
Cause: The specified driver could not find enough heap space to malloc a buffer.
- ORA-02732: osnrnf: cannot find a matching database alias
-
Cause: Database alias specified was not identified in either $HOME/.sqlnet or /etc/sqlnet.
- ORA-02733: osnsnf: database string too long
-
Cause: While converting a database alias to a database ID, the resulting database ID string exceeded the ORACLE system-imposed limit.
- ORA-02734: osnftt: cannot reset shared memory permission
-
Cause: The Fast driver was unable to reset shared memory permissions.
- ORA-02735: osnfpm: cannot create shared memory segment
-
Cause: The Fast driver failed to create a shared memory segment for two-task communication.
- ORA-02736: osnfpm: illegal default shared memory address
-
Cause: The Fast driver failed to establish a default shared memory address.
- ORA-02737: osnpcl: cannot tell orapop to exit
-
Cause: The Pipe driver failed to send orapop the command to exit.
- ORA-02738: osnpwrtbrkmsg: incorrect number of bytes written
-
Cause: The pipe driver apparently sent an imcomplete break message.
- ORA-02739: osncon: host alias is too long
-
Cause: The alias used for a sqlnet host is longer than 161 characters.
- ORA-02750: osnfsmmap: cannot open shared memory file ?/dbs/ftt_pid.dbf
-
Cause: The Fast driver failed to create a shared memory file for two-task communication.
- ORA-02751: osnfsmmap: cannot map shared memory file
-
Cause: The Fast driver failed to map a shared memory file for two-task communication.
- ORA-02752: osnfsmmap: illegal shared memory address
-
Cause: The Fast driver failed to attach shared memory at the expected location.
- ORA-02753: osnfsmmap: cannot close shared memory file
-
Cause: The Fast driver cannot close the shared memory file.
- ORA-02754: osnfsmmap: cannot change shared memory inheritence
-
Cause: The Fast driver could not alter the inheritence attributes of the shared memory.
- ORA-02755: osnfsmcre: cannot create chared memory file ?/dbs/ftt_pid.dbf
-
Cause: The Fast driver failed to create a file for shared memory.
- ORA-02756: osnfsmnam: name translation failure
-
Cause: The Fast driver encountered an error translating the shared memory filename ?/dbs/ftt_pid.dbf.
- ORA-02757: osnfop: fork_and_bind failed
-
Cause: The Fast driver failed to fork a process onto the desired cluster and node number.
- ORA-02758: Allocation of internal array failed
-
Cause: The package was unable to allocate memory for an array because the system ran out of memory.
- ORA-02759: Not enough request descriptors available
-
Cause: All of the package's request descriptors are in use performing other requests.
- ORA-02760: Client close of file failed.
-
Cause: The client was unable to close a file after forking the servers.
- ORA-02761: File number to be canceled is negative.
-
Cause: The file number contained with the sfiov structure is less than zero.
- ORA-02762: file number to be cancelled is greater than the maximum.
-
Cause: The file number contained with the sfiov structure is greater than the maximum.
- ORA-02763: Unable to cancel at least one request
-
Cause: No requests were found that could be cancelled.
- ORA-02764: Invalid package mode
-
Cause: The mode of the package can only be parallel or duplex.
- ORA-02765: Invalid maximum number of servers
-
Cause: The number of servers given was less than or equal to zero.
- ORA-02766: Invalid maximum of request descriptors
-
Cause: The number of request descriptors was less than or equal to zero.
- ORA-02767: Less than one request descriptor was allocated per server
-
Cause: The package requires that the number of request descriptors be greater than or equal to the number of servers used.
- ORA-02768: Maximum number of files is invalid
-
Cause: The maximum number of files to be used by the package was less than or equal to zero.
- ORA-02769: Setting of handler for SIGTERM failed
-
Cause: The package was unable to set up handling by the server for the termination signal. This is an internal error.
- ORA-02770: Total number of blocks is invalid
-
Cause: The total number of blocks to be allocated for use by the package was not greater than zero.
- ORA-02771: Illegal request time out value
-
Cause: The number was not a positive number.
- ORA-02772: Invalid maximum server idle time
-
Cause: The time given was not a positive number.
- ORA-02773: Invalid maximum client wait time
-
Cause: The time given was not a positive number.
- ORA-02774: Invalid request list latch time out value
-
Cause: The time given was not a positive number.
- ORA-02775: Invalid request done signal
-
Cause: The signal number was not a positive number.
- ORA-02776: Value for request done signal exceeds maximum
-
Cause: The value sent to the package for use as the "request done" signal exceeds the maximum allowed by the operating system.
- ORA-02777: Stat failed on log directory
-
Cause: The package was unable to get information about the directory in which the log files are to reside.
- ORA-02778: Name given for the log directory is invalid
-
Cause: The name given for the directory in which the logs are to be kept does not correspond to a directory.
- ORA-02779: Stat failed on core dump directory
-
Cause: The package was unable to get information about the directory into which the servers are to dump core in the event of an exception.
- ORA-02780: Name given for the core dump directory is invalid
-
Cause: The name given for the directory in which the server processes are to dump core in the event of an exception does not correspond to a directory.
- ORA-02781: Invalid value given for the timing wanted flag
-
Cause: The value given was not TRUE or FALSE.
- ORA-02782: Both read and write functions were not specified
-
Cause: To ensure that the functions act symmetrically, pointers to both the read and write functions must be given.
- ORA-02783: Both post and wait functions were not specified
-
Cause: To ensure that the functions act symmetrically, pointers to both the posting and waiting functions must be given.
- ORA-02784: Invalid shared memory ID specified
-
Cause: The ID of the segment specified for use as the shared buffer region was invalid.
- ORA-02785: Invalid shared memory buffer size
-
Cause: The size given for the shared memory segment to be used as the shared buffer region was less than or equal to zero.
- ORA-02786: Size needed for shared region is greater than segment size
-
Cause: The size of the shared segment that was specified for the shared buffer region is less than the number of bytes required. The first field of the "additional information" field is the size needed. The second is the size of the segment.
- ORA-02787: Unable to allocate memory for segment list
-
Cause: The package cannot allocate memory for an internal segment list because the system has run out of memory. The "additional information" field is the amount of memory that the package attempted to allocate.
- ORA-02788: Unable to find kernel process pointer in async process array
-
Cause: Internal error - Contact ORACLE support.
- ORA-02789: Maximum number of files reached
-
Cause: The maximum number of files that can be used for asynchronous I/O has been reached.
- ORA-02790: File name is too long
-
Cause: The length of the name of a file that is being opened for asynchronous I/O is longer than the maximum. The "additional information" field is the maximum length.
- ORA-02791: Unable to open file for use with asynchronous I/O
-
Cause: The package could not open file for some reason.
- ORA-02792: Unable to fstat() a file being used for asynchronous I/O.
-
Cause: The fstat(2) call on a file being used for asynchronous I/O failed.
- ORA-02793: Close of asynchronous I/O failed.
-
Cause: The client was unable to close a file being used for asynchronous I/O.
- ORA-02794: Client unable to get key for shared memory
-
Cause: The client was unable to get a key so that it obtain shared memory for use with shared memory.
- ORA-02795: Request list is empty
-
Cause: The client was signalled by a server that it was done with a request but the "done" list was empty.
- ORA-02796: Done request is not in correct state
-
Cause: A request is not in the right state.
- ORA-02797: No requests available
-
Cause: No free request descriptors are available.
- ORA-02798: Invalid number of requests
-
Cause: The number of operations sent to either sfard() or sfawrite() is less than zero.
- ORA-02799: Unable to arm signal handler
-
Cause: The arming of a signal handler for the "done" signal failed.
- ORA-02800: Requests timed out
-
Cause: Some of the requests for asynchronous input or output were not serviced in the required amount of time.
- ORA-02801: Operations timed out
-
Cause: Some asynchronous operations timed out in kernel mode.
- ORA-02802: No idle servers available in parallel mode
-
Cause: Internal error.
- ORA-02803: Retrieval of current time failed
-
Cause: Internal error.
- ORA-02804: Allocation of memory failed for log file name
-
Cause: The client was unable to allocated a buffer for the name of the log file.
- ORA-02805: Unable to set handler for SIGTPA
-
Cause: Internal error.
- ORA-02806: Unable to set handler for SIGALRM
-
Cause: Internal error.
- ORA-02807: Allocation of memory for I/O vectors failed.
-
Cause: The client was unable to allocate memory for the array of I/O vectors that the servers are to use.
- ORA-02808: Allocation of memory of open files array failed.
-
Cause: The client was unable to allocate memory for an array of flags that the servers are to use.
- ORA-02809: Jump buffer not valid
-
Cause: Internal error.
- ORA-02810: Unable to make temporary file name for memory mapped file
-
- ORA-02811: Unable to attach shared memory segment
-
- ORA-02812: Bad attach address
-
- ORA-02813: Unable to make temporary file name in order to get key
-
Cause: Internal error.
- ORA-02814: Unable to get shared memory
-
Cause: Shmget(2) failed.
- ORA-02815: Unable to attach shared memory
-
Cause: Shmat(2) failed.
- ORA-02816: Unable to kill a process
-
Cause: A server did not die after being sent a kill signal.
- ORA-02817: Read failed
-
Cause: A server could not read a requested amount of data.
- ORA-02818: Less than the number of blocks requested was read in
-
Cause: A server could not read in the request amount of data. The first number in the "additional information" field is the block number being read in. The second is the actual number of bytes that was read in.
- ORA-02819: Write failed
-
Cause: A server was unable to perform a write. The number in the "additional information" field is the starting block number of the data segment being written out. The first number in the "additional information" field is the block number being written out. The second is the actual number of bytes that was written out. The disk may have filled up.
- ORA-02820: Unable to write the requested number of blocks
-
Cause: A server could not write the requested amount of data out to disk. The disk may have run out of space.
- ORA-02821: Unable to read the requested number of blocks.
-
Cause: A server could not read the number of blocks that was requested. The end of the file may have been read.
- ORA-02822: Invalid block offset
-
Cause: A server was unable to seek to the designated block.
- ORA-02823: Buffer is not aligned.
-
Cause: The buffer on which an I/O is being done is not on the correct boundary.
- ORA-02824: Request free list is empty
-
Cause: The list from which the package allocates request descriptors is empty because all of the descriptors is in use.
- ORA-02825: Request on free list was not free
-
Cause: Internal error.
- ORA-02826: Illegal block size
-
Cause: A negative number was given for the I/O block size to be used by the asynchronous I/O package.
- ORA-02827: Invalid file number
-
Cause: The file number upon which an operation is to done is either less than zero or greater than the maximum number of files than can be open.
- ORA-02828: Segment free list is empty
-
Cause: No segments are available to allocated.
- ORA-02829: No segment of the proper size is available
-
Cause: No segment of the proper size is ready for use by the caller.
- ORA-02830: Segment could not be split - no free segments available
-
Cause: A segment that is larger than that desired could not be split because no free segment was available.
- ORA-02831: Segment deallocation failed - empty segment list
-
Cause: The caller attempted to deallocate a segment but the "in use" list was empty. This is a programming error.
- ORA-02832: Segment deallocation failed - segment not on list
-
Cause: The caller attempted to deallocate a segment that was not on the "in use" list. This is a programming error.
- ORA-02833: Server was unable to close file
-
Cause: A server was unable to close a file being used for asynchronous I/O.
- ORA-02834: Server unable to open file
-
Cause: The server was unable to open a file for use with asynchronous I/O.
- ORA-02835: Server unable to send signal to client
-
Cause: Internal error.
- ORA-02836: Unable to create temporary key file
-
Cause: Internal error.
- ORA-02837: Unable to unlink temporary file
-
Cause: Internal error.
- ORA-02838: Unable to arm signal handler for the alarm signal
-
Cause: The arming of a signal handler for the alarmsignal failed.
- ORA-02839: Sync of blocks to disk failed.
-
Cause: The server was unable to flush its writes out to disk.
- ORA-02840: Open of log file by client failed
-
Cause: The client process was unable to open its log file.
- ORA-02841: Server died on start up
-
Cause: A server exited during its initialization process.
- ORA-02842: Client unable to fork a server
-
Cause: The client could not spawn a server. A possible reason is that the operating system has reached its limit on the number of processes that it can spawn.
- ORA-02843: Invalid value for kernel flag
-
Cause: An illegal value was given for the kernel flag in the information structure. Only TRUE and FALSE are permitted.
- ORA-02844: Invalid value for the leave open flag
-
Cause: A value was given for the flag that determines whether a file is to be left open after the client checks it to see if the servers can use it. Only TRUE and FALSE are supported.
- ORA-02845: Invalid value for the timing wanted flag
-
Cause: A value was given for the flag that indicates that operations are to be timed out. Only TRUE and FALSE are supported.
- ORA-02846: Unkillable server
-
Cause: A server would not respond to the termination signal. The first number is the number of the server. The second is its UNIX process number. This is an internal problem.
- ORA-02847: Server did not terminate when posted
-
Cause: A server did not respond to a posted request to shutdown. The first number is the number of the server. The second is its UNIX process number. This is an internal problem.
- ORA-02848: Asynchronous I/O package is not running
-
Cause: An operation using the asynchronous I/O package was attempted without first initializing the package using sfainit().
- ORA-02849: Read failed because of an error
-
Cause: A server could not read the requested amount of data from disk.
- ORA-02850: File is closed
-
Cause: A file upon which an asynchronous I/O operation is to be performed has already been closed by the package.
- ORA-02851: Request list is empty when it should not be
-
Cause: This is an internal problem.
- ORA-02852: Invalid critical-section time out value
-
Cause: The time given was not a positive number.
- ORA-02853: Invalid server list latch time out value
-
Cause: The time given was not a positive number.
- ORA-02854: Invalid number of request buffers
-
Cause: The value given for "db_slave_buffers" in your INIT.ORA file is less than 0.
- ORA-02855: Number of requests is less than the number of slaves
-
Cause: The value given for 'db_slave_buffers' in the initialization parameter file was less than the number specified for the number of slaves, 'db_slaves.'
- ORA-02875: smpini: Unable to get shared memory for PGA
-
Cause: Stated in errno.
- ORA-02876: smpini: Unable to attach to shared memory for PGA
-
Cause: Stated in errno.
- ORA-02877: smpini: Unable to initialize memory protection
-
Cause: The adspcinit program has not been executed.
- ORA-02878: sou2o: Variable smpdidini overwritten
-
Cause: The variable smpdidini was overwritten, probably by client code.
- ORA-02879: sou2o: Could not gain access to protected memory
-
Cause: This is an internal error, note error code in errno.
- ORA-02880: smpini: Could not register PGA for protection
-
Cause: This is an internal error, note error code in errno.
- ORA-02881: sou2o: Could not revoke access to protected memory
-
Cause: This is an internal error, note error code in errno.
- ORA-02882: sou2o: Could not register SGA for protection
-
Cause: This is an internal error, note error code in errno.
- ORA-02899: smscre: Cannot create SGA with Extended Shared Memory feature
-
Cause: The environment variable EXTSHM was set before starting oracle.
- ORA-03001: unimplemented feature
-
Cause: This feature is not implemented.
- ORA-03002: operator not implemented
-
Cause: This is an internal error.
- ORA-03007: obsolete feature
-
Cause: User attempted to use a feature which is no longer supported.
- ORA-03009: Incompatible OCI function call
-
Cause: An incompatible OCI function call was issued for new functionality.
- ORA-03100: communication area cannot be allocated; insufficient memory
-
- ORA-03101: invalid input data for string
-
Cause: Invalid input data was detected for the specified data type.
- ORA-03102: TTC detects an invalid character set.
-
Cause: A malformed TTC (Two-Task Common) packet was received.
- ORA-03103: malformed TTC packet from client rejected for TTC RPC (string): Reason: number
-
Cause: An invalid input was detected for the specified Two-Task Common (TTC) remote procedural call (RPC).
- ORA-03105: internal protocol error
-
- ORA-03106: fatal two-task communication protocol error
-
- ORA-03107: oranet buffer underflow
-
- ORA-03108: oranet: ORACLE does not support this interface version
-
- ORA-03109: oranet buffer overflow
-
- ORA-03110: oranet: ORACLE does not support this SQL version
-
- ORA-03111: break received on communication channel
-
- ORA-03112: a server linked as single-task cannot use SQL*Net
-
Cause: A statement containing a SQL*Net connect string was issued to the single-task server. For example, a database link was used in a SQL statement.
- ORA-03113: end-of-file on communication channel
-
Cause: The connection between Client and Server process was broken.
- ORA-03114: not connected to ORACLE
-
- ORA-03115: unsupported network datatype or representation
-
- ORA-03116: invalid buffer length passed to a conversion routine
-
- ORA-03117: two-task save area overflow
-
- ORA-03118: two-task coroutine has invalid state
-
- ORA-03119: two-task detected inconsistent datatype specification
-
Cause: There was both a datatype, and an anonymous datatype declaration found.
- ORA-03120: two-task conversion routine: integer overflow
-
- ORA-03121: no interface driver connected - function not performed
-
- ORA-03122: attempt to close ORACLE-side window on user side
-
Cause: This is an internal error.
- ORA-03123: operation would block
-
Cause: This is a status code that indicates that the operation cannot complete now.
- ORA-03124: two-task internal error
-
Cause: Internal error.
- ORA-03125: client-server protocol violation
-
Cause: The application received a bad escape sequence from the server and may indicate a problem with the client application user code.
- ORA-03126: network driver does not support non-blocking operations
-
Cause: A non-blocking operation was attempted and the network driver does not support non-blocking operations.
- ORA-03127: no new operations allowed until the active operation ends
-
Cause: An attempt was made to execute a new operation before the active non-blocking operation completed or a new operation was attempted before all the pieces of a column were inserted or fetched.
- ORA-03128: connection is in blocking mode
-
Cause: The OCI test for non-blocking mode on a connection indicates that the connection is in blocking mode.
- ORA-03129: the next piece to be inserted is required
-
Cause: The application performed a piecewise bind on a column.
- ORA-03130: the buffer for the next piece to be fetched is required
-
Cause: The application performed a piecewise define on the column.
- ORA-03131: an invalid buffer was provided for the next piece
-
Cause: The application either provided the length of the buffer for the next piece to be zero or provided a null pointer.
- ORA-03132: two-task default value overflow
-
Cause: The default value specified for a record field was too large.
- ORA-03134: Connections to this server version are no longer supported.
-
Cause: An attempt was made to connect to an Oracle server of older version.
- ORA-03135: connection lost contact
-
Cause: 1) Server unexpectedly terminated or was forced to terminate. 2) Server timed out the connection.
- ORA-03136: inbound connection timed out
-
Cause: 1) The inbound connection was timed out by the server because user authentication was not completed within the given time specified by SQLNET.INBOUND_CONNECT_TIMEOUT or its default value.
- ORA-03137: malformed TTC packet from client rejected: [string] [string] [string] [string] [string] [string] [string] [string]
-
Cause: A malformed TTC (Two-Task Common) packet was received from the client.
- ORA-03138: Connection terminated due to security policy violation
-
Cause: Connection was terminated due to a security policy violation.
- ORA-03139: This OCI call has been disabled by the DBA
-
Cause: The SEC_DISABLE_OLDER_ORACLE_RPCS initialization parameter was enabled.
- ORA-03140: I/O operation in progress
-
Cause: The current I/O operation was not complete. The error is typically returned from vectored and/or asynchronous I/O calls.
- ORA-03141: I/O request queue full
-
Cause: The I/O request queue was full and no more requests could be queued.
- ORA-03142: Session ID: number Serial number: number
-
Cause: Connection was lost for the specified session and serial number. This is either due to session being killed or network problems.
- ORA-03143: Process ID: string Thread ID: string
-
Cause: Connection was lost for the specified process ID and thread ID. This is either due to session being killed or network problems.
- ORA-03144: Process ID: string
-
Cause: Connection was lost for the specified process ID. This is either due to session being killed or network problems.
- ORA-03145: I/O streaming direction error
-
Cause: Attempted to PUT data when GET streaming was in progress or attempted to GET data when PUT streaming was in progress.
- ORA-03146: invalid buffer length for TTC field
-
Cause: A malformed TTC (Two-Task Common) packet was received.
- ORA-03147: missing mandatory TTC field
-
Cause: A malformed TTC (Two-Task Common) packet was received.
- ORA-03148: OCI_ATTR_ROW_COUNT cannot return a row count exceeding UB4MAXVAL. The actual row count is [string]
-
Cause: The row count was larger than UB4MAXVAL. OCI clients using OCI_ATTR_ROW_COUNT cannot see row counts larger than UB4MAXVAL.
- ORA-03149: invalid Oracle error code
-
Cause: An invalid Oracle error code was received by the server.
- ORA-03150: end-of-file on communication channel for database link
-
Cause: The connection between the client and the remote server process was broken.
- ORA-03151: schema name length exceeding UB1MAXVAL
-
Cause: The schema name length was larger than UB1MAXVAL, and clients older than Release 12.2 were unable to process longer names.
- ORA-03152: object name length exceeding UB1MAXVAL
-
Cause: The object name length was larger than UB1MAXVAL, and clients older than Release 12.2 wree unable to process longer names.
- ORA-03153: column name length exceeding UB1MAXVAL
-
Cause: The column name length was larger than UB1MAXVAL, and clients older than Release 12.2 were unable to process longer names.
- ORA-03154: Deprecated TTC operation is disallowed.
-
Cause: A Deprecated Two-Task Common (TTC) remote procedural call (RPC) was invoked.
- ORA-03155: SQL statement not supported for remote execution
-
Cause: Statement execution could not proceed because the rewritten statement that was issued to the remote had a different ordering (or number) of bind variables as compared to the original statement issued locally.
- ORA-03156: OCI call timed out
-
Cause: The OCI call was timed out because it was not completed within the timeout specified by OCI_ATTR_CALL_TIMEOUT.
- ORA-03160: An invalid client operation was requested by the server
-
Cause: You are using an Oracle client application linked with libraries with lower version than the current server version.
- ORA-03170: deadlocked on readable physical standby (undo segment string)
-
Cause: A new undo segment was added. A query can occasionally deadlock when issued around the time an undo segment is added and used immediately on the primary.
- ORA-03171: Recovery was terminated during query execution
-
Cause: Recovery was terminated. A query can ocassionally deadlock when recovery is terminated because it needs a block with changes that are made after the point at which recovery was terminated.
- ORA-03172: STANDBY_MAX_DATA_DELAY of string seconds exceeded
-
Cause: Standby recovery fell behind the STANDBY_MAX_DATA_DELAY requirement.
- ORA-03173: Standby may not be synced with primary
-
Cause: ALTER SESSION SYNC WITH PRIMARY did not work because either the standby was not synchronous or in a data-loss mode with regard to the primary, or the standby recovery was terminated.
- ORA-03174: STANDBY_MAX_DATA_DELAY does not apply to SYS users
-
Cause: ALTER SESSION SET STANDBY_MAX_DATA_DELAY did not work for SYS users.
- ORA-03175: parameter string mismatch
-
Cause: The value of the %s parameter was not the same in all instances.
- ORA-03176: string only works on an open physical standby database
-
Cause: The database was not an open physical standby database.
- ORA-03177: enable read-only violation logging
-
- ORA-03178: duplicate SESSION or GLOBAL specifications
-
Cause: Duplicate SESSION or GLOBAL specifications were specified.
- ORA-03179: NOCACHE or ORDER sequences cannot be accessed from Active Data Guard standby
-
Cause: NOCACHE or ORDER sequences were not supported for Active Data Guard standby.
- ORA-03180: Sequence values cannot be allocated for Oracle Active Data Guard standby.
-
Cause: Connection to the corresponding primary database failed. The primary database might be down.
- ORA-03181: Sequence object no longer exists for Oracle Active Data Guard standby.
-
Cause: The sequence object might have been dropped by the primary database.
- ORA-03182: The sequence object is no longer a global sequence for Oracle Active Data Guard standby database.
-
Cause: The sequence object might have been altered by the primary database.
- ORA-03183: Parameter string value change failed.
-
Cause: The parameter could not be changed during Oracle Active Data Guard (Oracle ADG) recovery.
- ORA-03185: The value change failed for parameter string.
-
Cause: An attempt was made to enable the parameter on a non-Engineered system or it was not on a Platform as a Service.
- ORA-03186: Cannot start Oracle ADG recovery on a non-Oracle Cloud database on a server that is not a primary server.
-
Cause: An attempt was made to start Oracle Active Data Guard (Oracle ADG) recovery on a non-Oracle Cloud database that was not on the primary server.
- ORA-03187: Preplugin recovery cannot start from a backup belonging to a prior PDB incarnation.
-
Cause: An attempt was made to start preplugin recovery from a backup prior to the current pluggable database (PDB) incarnation.
- ORA-03200: the segment type specification is invalid
-
Cause: segment type is not TABLE, INDEX, or CLUSTER
- ORA-03201: the group number specification is invalid
-
Cause: the freelist group number was either negative or larger than the the number of freelist groups in the segment
- ORA-03202: the scan limit specification is invalid
-
Cause: the scan limit did not have a positive integer value the number of freelist groups in the segment
- ORA-03203: concurrent update activity makes space analysis impossible
-
Cause: high volume of user updates interfere with the space analysis
- ORA-03204: the segment type specification should indicate partitioning
-
Cause: partition name is specified for the space analysis, but the object type does not indicate parttitioning
- ORA-03205: partition name is required when partitioned type is specified
-
Cause: partition name is not specified for the space analysis, but the object type indicates parttitioning
- ORA-03206: maximum file size of (string) blocks in AUTOEXTEND clause is out of range
-
Cause: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed.
- ORA-03207: subpartitioned type must be specified for composite object
-
Cause: partition type is specified for the space analysis, but the object type indicates composite partitioning
- ORA-03208: partitioned type must be specified for a non-composite object
-
Cause: subpartition type is specified for the space analysis, but the object type indicates non-composite partitioning
- ORA-03209: DBMS_ADMIN_PACKAGE invalid file/block specification
-
Cause: The value of file number or block number is outside of limits or inconsistent
- ORA-03210: DBMS_ADMIN_PACKAGE invalid option specification
-
Cause: The value of one of the option parameters is incorrect
- ORA-03211: The segment does not exist or is not in a valid state
-
Cause: The segment specified in the DBMS_SPACE_ADMIN or DBMS_SPACE operation does not exist or is not in a state appropriate for this operation
- ORA-03212: Temporary Segment cannot be created in locally-managed tablespace
-
Cause: Attempt to create a temporary segment for sort/hash/lobs in in permanent tablespace of kind locally-managed
- ORA-03213: Invalid Lob Segment Name for DBMS_SPACE package
-
Cause: The Lob Segment specified in the DBMS_SPACE operation does not exist.
- ORA-03214: File Size specified is smaller than minimum required
-
Cause: File Size specified for add/resize datafile/tempfile does not allow for the minimum required of one allocation unit.
- ORA-03215: File Size specified for resize is too small
-
Cause: File Size specified for resize datafile/tempfile causes bitmap control structures to overlap
- ORA-03216: Tablespace/Segment Verification cannot proceed
-
Cause: Corruptions detected during verification whch cannot be dealt with
- ORA-03217: invalid option for alter of TEMPORARY TABLESPACE
-
Cause: invalid option for alter of temporary tablespace was specified
- ORA-03218: invalid option for CREATE/ALTER TABLESPACE
-
Cause: invalid option for create/alter tablespace of type locally-managed
- ORA-03219: Tablespace 'string' is dictionary-managed, offline or temporary
-
Cause: Operation which is only applicable to permanent, online, locally-managed tablespaces is specified for a tablespace which is either dictionary-managed, offline or temporary
- ORA-03220: DBMS_ADMIN_PACKAGE required parameter is NULL or missing
-
Cause: Some of the procedures was called with missing or NULL parameters
- ORA-03221: Temporary tablespaces and temporary segments must have standard block size
-
Cause: An attempt was made to do one of the following : (1) create a temporary tablespace with a non-standard block size or, (2) alter an existing permanent tablespace of non-standard block size to a temporary tablespace or, (3) issue a DDL statement that would result in the creation of a temporary segment in a tablespace of non-standard block size.
- ORA-03222: average row size and row count must be greater than zero
-
Cause: Either a bad value passed to dbms_space.create_table_cost() or explain plan did not pass through size information.
- ORA-03223: Bitmap index block addressable limitation reached
-
Cause: The limitation of addressability of BMIB (Bitmap Index Block) was reached for the current blocksize.
- ORA-03230: segment only contains string blocks of unused space above high water mark
-
Cause: Attempt to preserve too many blocks.
- ORA-03231: the INITIAL extent may not be deallocated
-
Cause: Attempt to deallocate space from the segment which was truncated prior to the 7.3 release.
- ORA-03233: unable to extend table string.string subpartition string by string in tablespace string
-
Cause: Failed to allocate an extent for table subpartition segment in tablespace.
- ORA-03234: unable to extend index string.string subpartition string by string in tablespace string
-
Cause: Failed to allocate an extent for index subpartition segment in tablespace.
- ORA-03235: max # extents (string) reached in table string.string subpartition string
-
Cause: A table subpartition tried to extend past maxextents
- ORA-03236: max # extents (string) reached in index string.string subpartition string
-
Cause: An index subpartition tried to extend past maxextents
- ORA-03237: Initial Extent of specified size cannot be allocated in tablespace (string)
-
Cause: Too large a size for an initial extent due to freelist group specification
- ORA-03238: unable to extend LOB segment string.string subpartition string by string in tablespace string
-
Cause: An attempt was made to allocate an extent for LOB subpartition segment in tablespace, but the extent could not be allocated because there is not enough space in the tablespace indicated.
- ORA-03239: maxextents (string) reached in LOB segment string.string subpartition string
-
Cause: A LOB subpartition segment tried to extend past maxextents.
- ORA-03240: User's temporary tablespace same as tablespace being migrated
-
Cause: Users default temporary tablespace must be different from the tablespace being migrated.
- ORA-03241: Invalid unit size
-
Cause: User specified an invalid unit size for the tablespace
- ORA-03242: Tablespace migration retried 500 times
-
Cause: For migration to complete, temporary segments should not be present in the tablespace at the time of migration.
- ORA-03243: destination dba overlaps with existing control information
-
Cause: Cannot overlap control information during relocation
- ORA-03244: No free space found to place the control information
-
Cause: During migration of tablespace found no place to put the control information. If during bitmaps relocation, found no space at the specified destination.
- ORA-03245: Tablespace has to be dictionary managed, online and permanent to be able to migrate
-
Cause: Tablespace was not dictionary managed or online or permanent.
- ORA-03246: Invalid block number specified
-
Cause: Control information cannot be placed at the specified dba either because the block number specified is beyond the file end or the file is not large enough to accomodate the control information at that location
- ORA-03247: Invalid block number specified
-
Cause: Relocation of bitmaps to the said destination will make the tablespace self descriptive
- ORA-03248: Too much of segment creation activity during migration
-
Cause: Temporary segments were attempted to be created during migration
- ORA-03249: Uniform size for auto segment space managed tablespace should have atleast string blocks
-
Cause: For the given blocksize, uniform size specified is insufficient
- ORA-03250: Cannot mark this segment corrupt
-
Cause: This segment cannot be marked corrupt because it contains data dictionary objects
- ORA-03251: Cannot issue this command on SYSTEM tablespace
-
Cause: It is not permitted to migrate SYSTEM tablespace from locally managed format to dictionary managed format or relocate bitmaps.
- ORA-03252: initial extent size not enough for LOB segment
-
Cause: Fatblock size of LOB segment is too big to fit into the initial extent.
- ORA-03254: unable to execute the sql in read only database
-
Cause: Unable to create a consistent snapshot of the object in a read only database. Transaction recovery must be performed before opening the database read only.
- ORA-03261: the tablespace string has only one file
-
Cause: Dropping file from ts which has a single file extent.
- ORA-03262: the file is non-empty
-
Cause: Trying to drop a non-empty datafile
- ORA-03263: cannot drop the first file of tablespace string
-
Cause: Trying to drop the first datafile with which ts is created
- ORA-03264: cannot drop offline datafile of locally managed tablespace
-
Cause: Trying to drop offline datafile in lmts
- ORA-03274: both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified
-
Cause: The DEALLOCATE option and the ALLOCATE option are specified in the same command.
- ORA-03275: duplicate DEALLOCATE option specification
-
Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is specified more than once.
- ORA-03276: duplicate ALLOCATE EXTENT option specification
-
Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once.
- ORA-03277: invalid SIZE specified
-
Cause: The specified value must be an integer.
- ORA-03278: duplicate ALLOCATE EXTENT option specification
-
Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more than once.
- ORA-03279: invalid INSTANCE specified
-
Cause: The specified value is not recognized as a valid instance name.
- ORA-03280: invalid DATAFILE filename specified
-
Cause: A character string literal is expected, but not found.
- ORA-03281: invalid ALLOCATE EXTENT option
-
Cause: An option other than DATAFILE, SIZE or INSTANCE was specified.
- ORA-03282: missing ALLOCATE EXTENT option
-
Cause: No ALLOCATE EXTENT options were specified.
- ORA-03283: specified datafile string does not exist
-
Cause: The datafile does not exist
- ORA-03284: datafile or tempfile string is not a member of tablespace string
-
Cause: The specified datafile or tempfile did not belong to the tablespace that the object resides in.
- ORA-03286: ALLOCATE EXTENT not valid for HASH CLUSTERS
-
Cause: The cluster is a hash cluster, and can not use the allcoate extent option.
- ORA-03287: invalid FREELIST GROUP specified
-
Cause: The specified FREELIST GROUP number is invalid
- ORA-03288: both FREELIST GROUP and INSTANCE parameters may not be specified
-
Cause: Both FREELIST GROUP and INSTANCE were specified in clause
- ORA-03289: partition name and segment type do not match
-
Cause: Partition name and segment type specified for space analysis do not match
- ORA-03290: Invalid truncate command - missing CLUSTER or TABLE keyword
-
Cause: Invalid object specification given.
- ORA-03291: Invalid truncate option - missing STORAGE keyword
-
Cause: Expected STORAGE keyword
- ORA-03292: Table to be truncated is part of a cluster
-
Cause: The table being truncated is a member of a cluster.
- ORA-03293: Cluster to be truncated is a HASH CLUSTER
-
Cause: Only INDEX CLUSTERS can be truncated.
- ORA-03296: cannot resize datafile - file string not found
-
Cause: The specified datafile is not available for resizing.
- ORA-03297: file contains used data beyond requested RESIZE value
-
Cause: Some portion of the file in the region to be trimmed is currently in use by a database object
- ORA-03298: cannot shrink datafile - file string is under hot backup
-
Cause: Attempt to shrink a datafile while it is under hot backup. This is not allowed.
- ORA-03299: cannot create dictionary table string
-
Cause: A dictionary table is created upon the first execution of the command 'alter database datafile autoextend on' for a database. This operation did not succeed. The most probable cause for this is insufficient space in the system tablespace.
- ORA-03700: More than one shardspace not allowed with system-managed sharding.
-
Cause: An attempt to add a shardspace to the catalog was attempted when a shardspace already existed.
- ORA-03701: invalid parameter combination: string and string
-
Cause: Mutually exclusive parameters were specified in a command.
- ORA-03702: reserved word used as object name: string
-
Cause: A reserved word was used as the name of an object.
- ORA-03703: no sharded database pools exist
-
Cause: A command was issued which required a sharded database pool, but none existed.
- ORA-03704: too many sharded database pools exist
-
Cause: A command was issued which required a sharded database pool, but more than one existed.
- ORA-03705: must explicitly specify shardgroup name because there could be multiple candidates
-
Cause: A command was issued without specifying a shardgroup and a default shardgroup could not be determined.
- ORA-03706: must explicitly specify shardspace name because there could be multiple candidates
-
Cause: A command was issued without specifying a shardspace and a default shardspace could not be determined.
- ORA-03707: mandatory environment variable not set at destination: string
-
Cause: An environment variable required for the operation was not set at the specified destination.
- ORA-03708: shard 'string' does not exist
-
Cause: The requested shard did not exist.
- ORA-03709: invalid format for input parameter file
-
Cause: The input file contained a parameter that was too long or the input file was not in the correct format.
- ORA-03710: directory does not exist or is not writeable at destination: string
-
Cause: A directory required for successful operation did not exist or was not writeable at the destination.
- ORA-03711: A shard with the same database identifier is a member of a different shardgroup.
-
Cause: A shard with the same database identifier was a member of a shardgroup in another shardspace.
- ORA-03712: A shard with the same database identifier is already in the shardgroup.
-
Cause: A shard with the same database identifier was a member of the specified shardgroup.
- ORA-03713: Shard 'string' contained string chunks.
-
Cause: A shard that contained chunks was removed from the catalog. Those chunks are no longer available.
- ORA-03714: errors found during chunk recovery
-
Cause: The chunk recovery procedure was not able to automatically recover corrupted chunks.
- ORA-03715: invalid user string
-
Cause: The specified user did not exist on this shard.
- ORA-03716: statement too long
-
Cause: The statement was too long.
- ORA-03717: Shard string does not exist in the shard pool.
-
Cause: A nonexistent shard was provided for execution.
- ORA-03718: Service management is not available at this time because broker configuration string does not have a registered primary database.
-
Cause: The primary database was not registered. Service management requires registration of all primary databases.
- ORA-03719: Shard character set does not match catalog character set.
-
Cause: The specified shard character set did not match the catalog character set.
- ORA-03720: Shard national character set does not match catalog national character set.
-
Cause: The specified shard national character set did not match the catalog national character set.
- ORA-03736: Database string is not a part of the sharded schema.
-
Cause: The specified database was not in the sharded schema.
- ORA-03737: cannot suspend move for chunk number string
-
Cause: The specified chunk move could not be suspended.
- ORA-03738: cannot remove chunk number string from the move queue
-
Cause: The specified chunk could not be removed from the queue.
- ORA-03739: The specified database is not configured to be a catalog.
-
Cause: The specified database was not configured to be a catalog.
- ORA-03740: Deployment failed with error: string
-
Cause: Unable to successfully complete shard deployment.
- ORA-03741: Could not retrieve default template from shard.
-
Cause: Unable to retrieve default Oracle Database Configuration Assistant (DBCA) template from shard.
- ORA-03742: Move chunk conditions are not met.
-
Cause: Chunk migration pre-check failed because one of the transporting tablespaces was either read-only or in hot backup mode.
- ORA-03743: cannot create service, sharded services must use preferred_all option
-
Cause: An attempt was made to create a service in a sharded pool that specified preferred and available databases.
- ORA-03744: Shard DDL state is not up-to-date.
-
Cause: The requested operation required one or more involved shards to be up-to-date with the DDL state of the sharded system.
- ORA-03745: global service manager not running
-
Cause: The master global service manager was no longer connected to the catalog.
- ORA-03746: The GSMUSER account does not have SYSDG and SYSBACKUP privileges.
-
Cause: The GSMUSER account was not granted SYSDG and SYSBACKUP privileges.
- ORA-03747: root table already exists
-
Cause: New shardspaces could not be added because a root table already existed in the sharded database.
- ORA-03748: A deploy operation is already in progress.
-
Cause: A previous request for deploy operation was still in progress.
- ORA-03749: Chunk move cannot be performed at this time.
-
Cause: A database condition that prevents chunk move was detected.
- ORA-03750: flashback database not enabled
-
Cause: The flashback database was not enabled on the database being configured.
- ORA-03751: user-defined sharding not supported
-
Cause: User-defined sharding was not supported on the database being configured.
- ORA-03752: specified VNCR in use
-
Cause: The specified valid node check for registration (VNCR) was in use by at least one database or shard.
- ORA-03753: The procedure cannot be propagated.
-
Cause: SYS.EXEC_SHARD_PLSQL can only execute a limited set of PL/SQL procedures.
- ORA-03754: shardgroups not allowed with user-defined or private sharding
-
Cause: An attempt was made to create a shardgroup with user-defined or private sharding.
- ORA-03755: current database role is incorrect: string
-
Cause: An attempt was made to create a primary shard from a standby database or a standby shard from a primary database.
- ORA-03756: The chunk string is already being split.
-
Cause: There was an incomplete split operation on the same chunk ID.
- ORA-03757: cannot skip or ignore shard DDL
-
Cause: An attempt was made to skip a system DDL request such as SPLITCHUNK.
- ORA-03758: cannot schedule split during an ongoing move
-
Cause: There was an incomplete move operation.
- ORA-03759: This procedure cannot be used to set database parameter string.
-
Cause: An attempt was made to set a database parameter that cannot be set using this procedure.
- ORA-03760: Oracle RAC affinity is supported only on a non-sharded Oracle RAC database.
-
Cause: An attempt to enable affinity was made on an Oracle database that was either non-RAC, or shard, or shard catalog.
- ORA-03761: Table is not found.
-
Cause: The table specification was not correct.
- ORA-03762: Partitioned table with this name does not exist.
-
Cause: The specified table was not partitioned.
- ORA-03763: Partitioned type 'string' is not supported.
-
Cause: The specified table was not partitioned by either RANGE, LIST or HASH.
- ORA-03764: Affinity is already enabled for a different table or service.
-
Cause: A table affinity was already specified. Multiple table affinities are currently not supported.
- ORA-03765: Service string has already been deleted by another session.
-
Cause: An attempt was made to delete a service that was already deleted.
- ORA-03766: Cannot modify service string because it is being deleted.
-
Cause: An attempt was made to modify a service that was already deleted.
- ORA-03767: The database to be replaced is not deployed: string
-
Cause: An attempt was made to replace a database that was not deployed.
- ORA-03768: The database to be replaced is still up: string
-
Cause: An attempt was made to replace a database that was still running.
- ORA-03769: job_queue_processes setting must be greater than one
-
Cause: The job_queue_processes initialization parameter was set to zero or one.
- ORA-03770: incorrect shard is given for replace: string
-
Cause: An attempt was made to replace a shard with another shard that did not have the same data as the original shard.
- ORA-03771: parameter parsing failed with error: string
-
Cause: The parameter values passed to SET DATAGUARD_PROPERTY were invalid.
- ORA-03772: attempt to set Oracle Data Guard property failed with error: string
-
Cause: The values passed to SET DATAGUARD_PROPERTY were invalid.
- ORA-03773: SPLIT CHUNK is not supported on a user-defined sharding environment.
-
Cause: A SPLIT CHUNK command was attempted on a user-defined sharding environment.
- ORA-03774: Cannot replace shard with OGG replication setup: string
-
Cause: An attempt was made to replace a shard with Oracle GoldenGate (OGG) as replication setup.
- ORA-03775: The new DBID of the standby database does not match the old DBID.
-
Cause: An attempt was made to replace a standby database shard having a different database identifier (DBID) than the original shard. All members of the Oracle Data Guard configuration must have same DBID.
- ORA-03776: maximum number of shards exceeded
-
Cause: A maximum of three primary shards are supported on this platform.
- ORA-03777: A move operation is already in progress.
-
Cause: A move was already in progress. Multiple concurrent user-requested move operations are not permitted.
- ORA-03778: Chunk string was already being moved to or from another location.
-
Cause: The chunk was already being moved. The current move request cannot be superceded.
- ORA-03779: failed to update broker configuration with error: string
-
Cause: A request to update the broker configuration failed.
- ORA-03780: failed to stop fast-start failover observers with error: string
-
Cause: A request to stop observers failed during an attempt to modify the Oracle Data Guard broker configuration.
- ORA-03781: error, 'error while executing some of the DDL statements'
-
Cause: There was an error while executing some of the DDL statements.
- ORA-03782: error, 'time out while waiting for the DDL statement execution'
-
Cause: The specified timeout was reached while waiting for the completion of the DDL statement execution.
- ORA-03783: no new shard to deploy
-
Cause: No new shard was added to deploy.
- ORA-03784: failed to disable fast-start failover with error: string
-
Cause: A request to disable fast-start failover failed.
- ORA-03785: database not open
-
Cause: An operation was attempted that requires the database to be open.
- ORA-03786: failed to replace primary database shard: string
-
Cause: An attempt was made to replace a primary database shard when standby databases are alive. This is now allowed.
- ORA-03787: failed to remove standby shard string from the broker configuration with error: string
-
Cause: A request to remove the shard from the broker configuration failed.
- ORA-03788: Shardspace 'string' does not contain a primary shard group.
-
Cause: An attempt was made to add a standby shard group or modify an existing shard group resulting in no primary shard groups being present.
- ORA-03789: cannot move chunk when sharded tables are in inconsistent state
-
Cause: An attempt was made to move chunk when one or more of the sharded tables are in inconsistent state.
- ORA-03790: multitenant container database (CDB) already exists: string
-
Cause: The specified multitenant container database (CDB) was already in existence.
- ORA-03791: CDB for this PDB is not found
-
Cause: An attempt was made to add a pluggable database (PDB) shard, but its container database (CDB) was not part of the sharding configuration or did not match the database identifier (DBID).
- ORA-03792: CDB already has one of the PDBs as a shard
-
Cause: One of the pluggable databases (PDB) in a container database (CDB) was already added as a shard.
- ORA-03793: CDB name is invalid: string
-
Cause: An invalid multitenant container database (CDB) name was specified.
- ORA-03794: CDB does not exist: string
-
Cause: The specified multitenant container database (CDB) did not exist.
- ORA-03795: The tablespace set string is read-only or offline.
-
Cause: Chunk operation was requested while the tablespace set was not online.
- ORA-03796: database already contains sharding metadata
-
Cause: The specified database already contained sharding metadata and could not be added as a new shard.
- ORA-03797: cannot deploy this shard for user-defined sharding because database version is not compatible
-
Cause: The database version was older than version 18.0 and did not support user-defined sharding.
- ORA-03798: Source and target database versions are different.
-
Cause: Target database was a different version than the source database.
- ORA-03799: invalid table family name specified: string
-
Cause: The table family name specified for the service was invalid.
- ORA-03800: cannot drop values from partitions and subpartitions of a user-defined sharded table
-
Cause: An attempt was made to modify a partition or a subpartition of a user-defined sharded table to drop one or more values.
- ORA-03801: incomplete PARTITION or SUBPARTITION maintenance command
-
Cause: The ALTER TABLE ... SPLIT or MERGE PARTITION or SUBPARTITION command did not contain an UPDATE INDEXES clause for a user-defined sharded table.
- ORA-03803: Only REFRESH COMPLETE ON DEMAND USING TRUSTED CONSTRAINTS option is supported for materialized views on sharded tables created on the catalog.
-
Cause: An attempt was made to create a materialized view on a sharded table on the shard catalog using the unsupported REFRESH options.
- ORA-03804: cannot alter the root table when there are child tables in inconsistent state
-
Cause: An attempt was made to alter a root table when one or more of its child tables were in inconsistent state.
- ORA-03805: missing tablespace clause for LOB column or columns in one or more partitions
-
Cause: An attempt was made to split a table partition with LOB columns without specifying tablespaces for all LOB columns in each resulting partition after the split.
- ORA-03807: An all shard GRANT command cannot contain any local objects.
-
Cause: A GRANT command that contained local objects was issued with shard DDL enabled.
- ORA-03808: shard key or partition set key columns cannot be columns that accept NULL values
-
Cause: An attempt was made to create a sharded table with shard key or partition set key columns that accept NULL values.
- ORA-03812: cannot specify NULL as partition bound or partitionset bound in sharding
-
Cause: An attempt was made to create a sharded table partition or partitionset with NULL value bound.
- ORA-03813: list partition method expects a single partitioning column in user-defined sharding
-
Cause: An attempt was made to create a sharded table with multiple columns as partitioning key.
- ORA-03814: cannot set a column as UNUSED in sharded tables
-
Cause: An attempt was made to alter a sharded table and set a column as UNUSED.
- ORA-03816: cannot drop the parent of a sharded child table
-
Cause: An attempt was made to drop the parent of a sharded child table.
- ORA-03817: cannot merge partitions that belong to different shardspaces
-
Cause: An attempt was made to merge partitions that are created in different shardspaces.
- ORA-03818: DML operations are not supported on the catalog for private sharding tables.
-
Cause: An attempt was made to perform a data manipulation languate (DML) operation on a private sharding table in the catalog.
- ORA-03819: cannot alter or drop private sharding tables in the catalog while shard DDL is enabled
-
Cause: An attempt was made to alter or drop a private sharding table in the catalog while shard DDL was enabled.
- ORA-03820: ALTER TABLE PRIVATELY cannot be performed on non-private sharding tables.
-
Cause: An attempt was made to alter a non-private sharding table to privately sharded or duplicated.
- ORA-03822: WARNING: DDL failed on string shards( offline: string, skipped: string, errors: string)
-
Cause: DDL was not propagated to offline shards and skipped shards with past DDL errors. DLL errors show the number of shards with errors.
- ORA-03823: Asynchronous propagation of DDL is timed out.
-
Cause: DDL statement propagation was not finished within one hour.
- ORA-03824: Error on string shard(s): string
-
Cause: DDL statement propagation errored out on one or more shards.
- ORA-03825: DDL statement cannot be executed due to shard unavailability.
-
Cause: DDL statement could not be executed synchronously because some shards were offline. The DLL STRICT execution mode requires all primary shards to be online.
- ORA-03828: cannot operate on privately sharded objects on the catalog
-
Cause: An attempt was made to create or modify a privately sharded object on the catalog.
- ORA-03850: The tablespace set string is already associated with a table family.
-
Cause: The specified tablespace set could not be used for this command because it was already associated with another table family.
- ORA-03851: operation not supported in private sharding
-
Cause: An attempt was made to perform an operation that was not supported with private sharding method.
- ORA-03852: user already exists on the catalog: string
-
Cause: A schema name was specified for creation that already exists on the catalog.
- ORA-03853: no schema provided
-
Cause: No schemas were specified for this command.
- ORA-03854: A CDB must be specified when adding a PDB shard.
-
Cause: An attempt was made to add a pluggable database (PDB) shard to the configuration without specifying its multitenant container database (CDB).
- ORA-03855: root container (CDB$ROOT) cannot be used as a shard
-
Cause: An attempt was made to add the root container (CDB$ROOT) to the configuration.
- ORA-03856: root container (CDB$ROOT) must be specified when adding a CDB
-
Cause: An attempt was made to add a pluggable database (PDB) as a multitenant container database (CDB).
- ORA-03857: A listener.ora file already exists in the shard host Oracle home.
-
Cause: An attempt was made to create a new TNS listener on the shard host, but a listener.ora file already existed in the $ORACLE_HOME/network/admin directory.
- ORA-03858: The specified CDB already contains a PDB shard from the current sharded database.
-
Cause: An attempt was made to add a pluggable database (PDB) shard to a multitenant container database (CDB) that already contained a PDB shard from the same sharded database.
- ORA-03859: Moving all chunks is not allowed in user-defined sharding.
-
Cause: An attempt was made to move all chunks from a source database. This operation is not allowed for user defined sharding.
- ORA-03860: Creating a shard catalog is not allowed in the root of a multitenant container database (CDB).
-
Cause: An attempt was made to create a shard catalog in the root of a CDB.
- ORA-03861: Pluggable database (PDB) name cannot be modified for a service.
-
Cause: An attempt was made to modify the pluggable database (PDB) name for a service.
- ORA-03862: A common user cannot run sharded DDL statements.
-
Cause: An attempt was made to run sharded DDL statements as a common user.
- ORA-03863: There is no deployed database named string.
-
Cause: The named database either did not exist or was not deployed.
- ORA-03864: cannot move chunk when there are no partition sets
-
Cause: Move chunk operation was attempted in a shardspace that did not have any partition set for sharded tables.
- ORA-03866: The GSMROOTUSER account does not have SYSDG and SYSBACKUP privileges.
-
Cause: The GSMROOTUSER account was not granted SYSDG and SYSBACKUP privileges.
- ORA-03867: maximum number of table families reached
-
Cause: An attempt was made to create a new table family when the maximum supported number of table families was reached.
- ORA-03868: shardspace does not contain a primary shard
-
Cause: The specified shardspace did not contain a primary shard.
- ORA-03869: The specified shard is already configured as a catalog.
-
Cause: An attempt was made to add a shard that was already configured as a catalog.
- ORA-03870: Parameter string passed to function string has invalid value string.
-
Cause: A sharding function was called with an invalid value.
- ORA-03871: Some DDL statements are yet to be applied on the catalog.
-
Cause: GDSCTL command 'sync ddl' was executed before all of the existing DDL statements were applied.
- ORA-03872: unable to create shard wallet at string with error string
-
Cause: Oracle was unable to create the shard wallet at the specified location.
- ORA-03873: unable to encrypt DDL statement with error string
-
Cause: The system was unable to encrypt the DDL statement.
- ORA-03874: unable to encrypt GSMUSER password with error string
-
Cause: Oracle was unable encrypt the Global Service Manager GSMUSER password.
- ORA-03875: The database parameter WALLET_ROOT is already set.
-
Cause: A new WALLET_ROOT value was used to create the catalog, but the database parameter WALLET_ROOT was already set.
- ORA-03876: error string when attempting to generate a temporary key to add new shards
-
Cause: The system was unable to generate a new key to add shards.
- ORA-03877: Chunk is put online on migration destination shard
-
Cause: Chunk migration information message.
- ORA-03878: The specified VNCR or VNCR group does not exist.
-
Cause: The specified valid node check for registration (VNCR) or VNCR group did not exist in the catalog.
- ORA-03900: shard internal database link cannot be altered or dropped
-
Cause: An attempt was made to directly alter or drop an internal database link for sharding, which is not allowed.
- ORA-03901: shard key or partition set key column cannot be renamed
-
Cause: An attempt was made to rename a shard key column or a partition set key column of a sharded table, which is not allowed.
- ORA-03902: cannot shrink a system-managed or composite sharded table with primary key or any sharded table with functional index
-
Cause: An attempt was made to shrink a system-managed or composite sharded table with primary key or a sharded table with functional index, which is not allowed.
- ORA-03903: The Flashback Table operation is not supported on sharded or duplicated tables.
-
Cause: An attempt was made to perform the Flashback Table operation on a sharded or duplicated table, which is not allowed.
- ORA-03904: The sharding virtual colummn cannot be modified.
-
Cause: An attempt was made to modify the sharding virtual column, SYS_HASHVAL, which is not allowed.
- ORA-03905: cannot use the same tablespace for multiple partitions of a user-defined sharded table
-
Cause: An attempt was made to use a tablespace for multiple partitions of a user-defined sharded table.
- ORA-03906: invalid tablespace name string specified for the partition string
-
Cause: An attempt was made to specify a tablespace name for a partition, subpartition, or LOBs that did not belong to the shardspace.
- ORA-03907: REF data type is not supported for duplicated tables.
-
Cause: An invalid option was specified while creating duplicated tables.
- ORA-03908: cannot drop duplicated table materialized views on shards
-
Cause: An attempt was made to manually drop materialized views of a duplicated table on shard databases.
- ORA-03909: cannot set parameter SHRD_DUPL_TABLE_REFRESH_RATE in SPFILE
-
Cause: An attempt was made to set parameter SHRD_DUPL_TABLE_REFRESH_RATE in SPFILE.
- ORA-03910: cannot drop duplicated table materialized view log
-
Cause: An attempt was made to drop materialized view logs created on duplicated tables.
- ORA-03911: column string is not supported for duplicated tables
-
Cause: An invalid option was specified while creating duplicated tables.
- ORA-03912: option string is not supported for duplicated tables
-
Cause: An invalid option was specified while creating duplicated tables.
- ORA-03913: A tablespace cannot be referenced at the table level.
-
Cause: An attempt was made to reference a tablespace at the table level.
- ORA-03914: cannot use tablespace string for partition string
-
Cause: At attempt was made to specify a tablespace that was used for a different chunk or partition in the tables already created.
- ORA-03915: cannot purge an individual chunk tablespace
-
Cause: An attempt was made to purge an individual chunk tablespace which is a part of a tablespace set.
- ORA-03916: The creation of Information Lifecycle Management (ILM) policy is not supported for duplicated tables.
-
Cause: An invalid option was specified while creating duplicated tables.
- ORA-03917: invalid partition set value
-
Cause: The attempt to update or insert into a partition set column failed.
- ORA-03918: invalid number of partitions specified for the child table
-
Cause: An attempt was made to create a child table with a number of partitions not equal to the number of partitions in the parent table.
- ORA-03919: invalid list value or values specified for the partition string
-
Cause: The list values specified for a partition of the table could not exactly be matched with the list values of the corresponding partition of the parent table.
- ORA-03920: invalid range value specified for the partition string
-
Cause: The range value specified for a partition of the table could not be matched with the range value of the corresponding partition of the parent table.
- ORA-03921: invalid number of list values specified for the partition string
-
Cause: The number of list values specified for a partition of the table was not equal to the number of list values specified for the corresponding partition of the parent table.
- ORA-03922: invalid range or list value specified for the partitionset string
-
Cause: The value specified for the range or list of the partitionset did not exactly match the value specified for the partitionset in the parent table.
- ORA-03923: cannot drop a tablespace set used for a composite sharded table
-
Cause: The tablespace was used for a composite sharded table and cannot be dropped unless the contents are dropped manually.
- ORA-03924: cannot alter a user-defined sharded table directly in the shard database
-
Cause: An attempt was made to alter a user-defined sharded table directly on the shard database.
- ORA-03925: duplicate partitionset name
-
Cause: Name of a partitionset of a table being created is not unique.
- ORA-03926: DEFAULT tablespace is not supported for sharded tables or indexes.
-
Cause: An attempt was made to use DEFAULT tablespaces for sharded tables or indexes.
- ORA-03927: invalid use of STORE IN clause for a sharded table or index
-
Cause: The STORE IN (tablespace list) clause was used to specify tablespaces for partitions of a sharded table or for partitions of an index where the sharded table did not have subpartitions or the subpartition method was not hash.
- ORA-03929: CREATE TABLE...AS SELECT statement is not supported for sharded tables.
-
Cause: An attempt was made to create a sharded table AS SELECT from another table, which is not supported.
- ORA-03930: Editions are not supported for sharded tables.
-
Cause: An attempt was made to create a sharded table using editions, which is not supported.
- ORA-03931: maximum number of sharding columns for consistent hash is 15.
-
Cause: The number of columns in a sharding key column list exceeded the legal limit of 15.
- ORA-03932: cannot create the default shard tablespace on the catalog when shard DDL is enabled
-
Cause: An attempt was made to create a tablespace in the catalog which is created on the shards by default in user-defined sharding.
- ORA-03933: An all-shard object cannot depend on any local objects.
-
Cause: An attempt was made to create or alter an all-shard object to depend on a local user object, which is not allowed.
- ORA-03934: An all-shard index cannot be created on local tables.
-
Cause: An attempt was made to create an all-shard index on a local user table, which is not allowed.
- ORA-03935: A sharded table cannot have columns that depend on local objects.
-
Cause: An attempt was made to create or alter a sharded table to contain columns that depend on local objects, which is not allowed.
- ORA-03936: cannot use a sharded tablespace for non-sharding purposes
-
Cause: An attempt was made to use a sharded tablespace for non-sharding purposes.
- ORA-03937: The creation of Information Lifecycle Management (ILM) policy is not supported for duplicated tables.
-
Cause: An invalid option was specified while altering duplicated tables.
- ORA-03938: cannot create duplicated tables on a shard database
-
Cause: An attempt was made to create a duplicated table on a shard database, which is not supported.
- ORA-03939: cannot specify a data file name for a tablespace in a sharding setup
-
Cause: The data file name was specified during creation of the tablespace. Only Oracle Managed Files are supported by a tablespace used in a sharding setup.
- ORA-03940: A trigger cannot be created on any sharded table.
-
Cause: An attempt was made to create a trigger on a sharded table, which is not allowed.
- ORA-03941: A shard key or partition set key column cannot be a sequence.
-
Cause: An attempt was made to create a sharded table having a shard key or a partition set key column based on a sequence, which is not allowed.
- ORA-03942: cannot create temporary tablespace sets
-
Cause: An attempt was made to create a temporary tablespace set, which is not allowed.
- ORA-03943: zone maps are not supported on sharded tables
-
Cause: An attempt was made to create a materialized zone map on a sharded table, which is not supported.
- ORA-03944: cannot specify PARENT clause for duplicated tables
-
Cause: An invalid option was specified while creating duplicated tables.
- ORA-03945: Cannot perform the operation on the child table before performing the same operation on the root table
-
Cause: An attempt was made to alter the child table to add or drop or split a partition whose root partition has not been added or dropped or split yet.
- ORA-03946: Operation is not supported on a user-defined sharded table
-
Cause: An attempt was made to perform an unsupported partition operation on a user-defined sharded table.
- ORA-03947: cannot create an autolist or interval partitioned sharded table
-
Cause: An attempt was made to create an autolist or interval partitioned sharded table.
- ORA-03948: A DEFAULT partition or partition set cannot be specified for a sharded table.
-
Cause: An attempt was made to create a partition or partition set with a DEFAULT high value on a sharded table.
- ORA-03949: password is required for encypted columns in a sharded table
-
Cause: An attempt was made to create a sharded table containing an encrypted column without specifying a password.
- ORA-03950: GoldenGate error: string
-
Cause: An operation failed when performed using Oracle GoldenGate.
- ORA-03951: Invalid OGG service descriptor - OGG message: string
-
Cause: One or more components of the Oracle GoldenGate (OGG) service descriptor could not be verified.
- ORA-03952: OGG string URI: string is not reachable - HTTP message: string
-
Cause: Oracle GoldenGate (OGG) AdminService or DistributionService could not be reached.
- ORA-03953: OGG string URI: string failed to string string: string - OGG message: string
-
Cause: Oracle GoldenGate (OGG) AdminService or DistributionService operation failed.
- ORA-03954: OGG sharding function called in an invalid context: string function called in string
-
Cause: Internal error. An Oracle GoldenGate (OGG) sharding functionality was called in an invalid context, for example, catalog function in shard or vice versa.
- ORA-03955: Invalid combination of OGG deployment parameters specified for shardgroup: string (S=string, C=string, R=string)
-
Cause: The values specified for Oracle GoldenGate (OGG) deployment parameters (number of shards - S, number of chunks - C and replication factor - R) for the shardgroup were not compatible with each other.
- ORA-03956: Invalid entry in the OGG command payload: string
-
Cause: Internal error. The payload for Oracle GoldenGate (OGG) command sent from the sharding catalog to the shard database contained an invalid entry.
- ORA-03957: Sharding configuration parameter 'string' is not set in the shard database.
-
Cause: Internal error. A database initialization parameter required by the shard database was not set during deployment.
- ORA-03958: Failure to remove shard: string - string
-
Cause: A request to remove a shard database failed.
- ORA-03959: chunk allocation error in shardgroup: string - string
-
Cause: Internal error. Chunk allocation algorithm for Oracle GoldenGate (OGG) detected inconsistencies in the sharding configuration.
- ORA-03960: Chunk number 'string' already exists on the target shard.
-
Cause: An invalid chunk number or target shard name was provided.
- ORA-03961: A move chunk request already exists for chunk number 'string' from the source shard.
-
Cause: An invalid chunk number or source shard name was provided.
- ORA-03962: invalid SPLIT PARTITION command for a user-defined sharded object
-
Cause: Tablespaces for resulting partitions in a SPLIT PARTITION command were either unspecified or in use.
- ORA-03964: updated or deleted row of duplicated table is not synchronized with catalog
-
Cause: An attempt was made to update or delete the row of a duplicated table that was recently inserted on this shard database. This table did not have primary key; therefore, any modifications of the inserted row cannot be performed until after the next duplicated table refresh (the default timeout is 1 minute).
- ORA-03965: updated or deleted row of duplicated table is not found on catalog
-
Cause: An attempt was made to update or delete the row of a materialized view on a shard database but the materialized view was not synchronized with the catalog and the affected rows were already deleted from the catalog by another shard database.
- ORA-03966: cannot alter duplicated table materialized views on shards
-
Cause: An attempt was made to manually alter materialized views of a duplicated table on shard databases.
- ORA-03967: failed to rename the materialized view log when renaming duplicated table
-
Cause: An attempt was made to rename the duplicated table, and the internal statement to rename the materialized view log failed.
- ORA-03968: Invisible column is not supported for duplicated tables.
-
Cause: An invalid option was specified while creating duplicated tables.
- ORA-04000: the sum of PCTUSED and PCTFREE cannot exceed 100
-
Cause: the sum of PCTUSED and PCTFREE for a cluster or table exceeds 100
- ORA-04001: sequence parameter string must be an integer
-
Cause: %s (a sequence parameter) specified was not an integer
- ORA-04002: INCREMENT must be a non-zero integer
-
Cause: a sequence increment was specified to be zero
- ORA-04003: sequence parameter string exceeds maximum size allowed (string digits)
-
Cause: %s (a sequencer parameter) had too many digits
- ORA-04004: MINVALUE must be less than MAXVALUE
-
Cause: MINVALUE was specified to be greater than or equal to MAXVALUE
- ORA-04005: INCREMENT must be less than MAXVALUE minus MINVALUE
-
Cause: the INCREMENT specified is >= MAXVALUE-MINVALUE
- ORA-04006: START WITH cannot be less than MINVALUE
-
Cause: the given starting value is less than MINVALUE
- ORA-04007: MINVALUE cannot be made to exceed the current value
-
Cause: the given MINVALUE would be greater than the current value
- ORA-04008: START WITH cannot be more than MAXVALUE
-
Cause: the starting value would be larger than MAXVALUE
- ORA-04009: MAXVALUE cannot be made to be less than the current value
-
Cause: the current value exceeds the given MAXVALUE
- ORA-04010: the number of values to CACHE must be greater than 1
-
Cause: the value in the CACHE clause was one
- ORA-04011: sequence string must range between string and string
-
Cause: the value specified for one of the sequence parameters exceeds limits
- ORA-04012: object is not a sequence
-
Cause: the object specified cannot have sequence ddl's performed on it
- ORA-04013: number to CACHE must be less than one cycle
-
Cause: number to CACHE given is larger than values in a cycle
- ORA-04014: descending sequences that CYCLE must specify MINVALUE
-
Cause: sequences that cycle must have their wrap-wrap specified
- ORA-04015: ascending sequences that CYCLE must specify MAXVALUE
-
Cause: sequences that cycle must have their wrap-wrap specified
- ORA-04016: sequence string no longer exists
-
Cause: sequence was dropped while processing its next value.
- ORA-04017: invalid value string (length = string) for parameter MAX_DUMP_FILE_SIZE
-
Cause: The string supplied for the parameter MAX_DUMP_FILE_SIZE was not an integer, an integer followed by 'K', 'M', or 'G', nor the special value UNLIMITED.
- ORA-04018: The 'string' parameter cannot be altered in Oracle Database Standard Edition or Oracle Database Express Edition.
-
Cause: An attempt was made to alter the specified parameter in the Standard Edition or Express Edition.
- ORA-04020: deadlock detected while trying to lock object stringstringstringstringstring
-
Cause: While trying to lock a library object, a deadlock is detected.
- ORA-04021: timeout occurred while waiting to lock object stringstringstringstringstring
-
Cause: While waiting to lock a library object, a timeout occurred.
- ORA-04022: nowait requested, but had to wait to lock dictionary object
-
Cause: Had to wait to lock a library object during a nowait request.
- ORA-04023: Object stringstringstringstringstring could not be validated or authorized
-
Cause: A number of attempts were made to validate or authorize an object but failed.
- ORA-04024: self-deadlock detected while trying to mutex pin cursor string
-
Cause: While trying to mutex pin a cursor, a self-deadlock is detected.
- ORA-04025: maximum allowed library object lock allocated for stringstringstringstringstring
-
Cause: Too many active locks for the object has been allocated. This error can be a result of too many cursors kept open per session.
- ORA-04027: self-deadlock during automatic validation for object string.string
-
Cause: An attempt was made to validate an invalidated object but it failed because of a self-deadlock.
- ORA-04028: cannot generate diana for object stringstringstringstringstring
-
Cause: Cannot generate diana for an object because of lock conflict.
- ORA-04029: error ORA-string occurred when querying stringstringstring
-
Cause: The table or view being queried might be missing. The error number indicates the error.
- ORA-04030: out of process memory when trying to allocate string bytes (string,string)
-
Cause: Operating system process private memory was exhausted.
- ORA-04031: unable to allocate string bytes of shared memory ("string","string","string","string")
-
Cause: More shared memory is needed than was allocated in the shared pool or Streams pool.
- ORA-04032: pga_aggregate_target must be set before switching to auto mode
-
Cause: attempt to set workarea_size_policy to AUTO while pga_aggregate_target is not specified
- ORA-04033: Insufficient memory to grow pool
-
Cause: The system had insufficient memory to grow the pool to the specified size.
- ORA-04034: unable to shrink pool to specified size
-
Cause: The pool could not shrink to the specified size as it could not free memory.
- ORA-04035: unable to allocate string bytes of shared memory in shared object cache "string" of size "string"
-
Cause: More shared memory is needed than was allocated in the shared object cache.
- ORA-04036: PGA memory used by the instance exceeds PGA_AGGREGATE_LIMIT
-
Cause: Private memory across the instance exceeded the limit specified in the PGA_AGGREGATE_LIMIT initialization parameter. The largest sessions using Program Global Area (PGA) memory were interrupted to get under the limit.
- ORA-04037: unable to allocate memory on another instance in the cluster
-
Cause: The instance ran out of memory as its allocated memory was less than the required memory.
- ORA-04039: insufficient HugePages to grow System Global Area (SGA)
-
Cause: The number of system configured HugePages was insufficient to grow the database System Global Area (SGA) to the specified size.
- ORA-04041: package specification must be created first before creating package body
-
Cause: Attempt to create a package body before creating its package specification.
- ORA-04042: procedure, function, package, or package body does not exist
-
Cause: Attempt to access a procedure, function, package, or package body that does not exist.
- ORA-04043: object string does not exist
-
Cause: An object name was specified that was not recognized by the system. There are several possible causes: - An invalid name for a table, view, sequence, procedure, function, package, or package body was entered. Since the system could not recognize the invalid name, it responded with the message that the named object does not exist. - An attempt was made to rename an index or a cluster, or some other object that cannot be renamed.
- ORA-04044: procedure, function, package, or type is not allowed here
-
Cause: A procedure, function, or package was specified in an inappropriate place in a statement.
- ORA-04045: errors during recompilation/revalidation of string.string
-
Cause: This message indicates the object to which the following errors apply. The errors occurred during implicit recompilation/revalidation of the object.
- ORA-04046: results of compilation are too large to support
-
Cause: Attempt to compile and store a large stored procedure that results in compilation data that is too large for the system to support or store.
- ORA-04047: object specified is incompatible with the flag specified
-
Cause: The object type implied by the flag does not match the type of object specified.
- ORA-04050: invalid or missing procedure, function, or package name
-
Cause: The required procedure, function, or package name is invalid or missing.
- ORA-04051: user string cannot use database link string.string
-
Cause: During forwarding of a remote object access, an attempt was made to use a non-existent database link or one owned by a user other than the logon user or PUBLIC.
- ORA-04052: error occurred when looking up remote object stringstringstringstringstring
-
Cause: An error occurred when trying to look up a remote object.
- ORA-04053: error occurred when validating remote object stringstringstringstringstring
-
Cause: An error occurred when trying to validate a remote object.
- ORA-04054: database link string does not exist
-
Cause: During compilation of a PL/SQL block, an attempt was made to use a non-existent database link.
- ORA-04055: Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
-
Cause: This compilation was aborted because the library unit that was compiled would have formed a non-REF mutually-dependent cycle with some other library units. This happens when an attempt is made to compile types that have attributes of other types that may participate in a cycle with this type. Example: create type t1; create type t2 (a t1); create type t1 (a t2);
- ORA-04060: insufficient privileges to execute string
-
Cause: Attempt to execute a stored procedure without sufficient privileges.
- ORA-04061: existing state of string has been invalidated
-
Cause: Attempt to resume the execution of a stored procedure using the existing state which has become invalid or inconsistent with the stored procedure because the procedure has been altered or dropped.
- ORA-04062: string of string has been changed
-
Cause: Attempt to execute a stored procedure to serve an RPC stub which specifies a timestamp or signature that is different from the current timestamp/signature of the procedure.
- ORA-04063: string has errors
-
Cause: Attempt to execute a stored procedure or use a view that has errors. For stored procedures, the problem could be syntax errors or references to other, non-existent procedures. For views, the problem could be a reference in the view's defining query to a non-existent table. Can also be a table which has references to non-existent or inaccessible types.
- ORA-04064: not executed, invalidated string
-
Cause: Attempt to execute a stored procedure that has been invalidated.
- ORA-04065: not executed, altered or dropped string
-
Cause: Attempt to execute a stored procedure that has been altered or dropped thus making it not callable from the calling procedure.
- ORA-04066: non-executable object, string
-
Cause: Attempt to execute a non-procedure.
- ORA-04067: not executed, string does not exist
-
Cause: Attempt to execute a non-existent stored procedure.
- ORA-04068: existing state of packagesstringstringstring has been discarded
-
Cause: One of errors 4060 - 4067 when attempt to execute a stored procedure.
- ORA-04069: cannot drop or replace a library with table dependents
-
Cause: An attempt was made to drop or replace a library that has dependents. There could be a table which depends on type which depends on the library being dropped.
- ORA-04070: invalid trigger name
-
Cause: An invalid trigger name was specified.
- ORA-04071: missing BEFORE, AFTER or INSTEAD OF keyword
-
Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause.
- ORA-04072: invalid trigger type
-
Cause: An invalid trigger type was given.
- ORA-04073: column list not valid for this trigger type
-
Cause: A column list was specified for a non-update trigger type.
- ORA-04074: invalid REFERENCING name
-
Cause: An invalid name was given in the referencing clause.
- ORA-04075: invalid trigger action
-
Cause: An statement was given for the trigger action.
- ORA-04076: invalid NEW or OLD specification
-
Cause: An invalid NEW or OLD specification was given for a column.
- ORA-04077: WHEN clause cannot be used with table level triggers
-
Cause: The when clause can only be specified for row level triggers.
- ORA-04078: OLD and NEW values cannot be identical
-
Cause: The referencing clause specifies identical values for NEW and OLD.
- ORA-04079: invalid trigger specification
-
Cause: The create TRIGGER statement is invalid.
- ORA-04080: trigger 'string' does not exist
-
Cause: The TRIGGER name is invalid.
- ORA-04081: trigger 'string' already exists
-
Cause: The TRIGGER name or type already exists.
- ORA-04082: NEW or OLD references not allowed in table level triggers
-
Cause: The trigger is accessing "new" or "old" values in a table trigger.
- ORA-04083: invalid trigger variable 'string'
-
Cause: The variable referenced in the trigger body is invalid.
- ORA-04084: cannot change NEW values for this trigger type
-
Cause: New trigger variables can only be changed in before row insert or update triggers.
- ORA-04085: cannot change the value of an OLD reference variable
-
Cause: Old values can only be read and not changed.
- ORA-04086: trigger description too long, move comments into triggering code
-
Cause: The trigger description is limited to 2000 characters (for dictionary storage reasons). The description does not include the text of the "when" clause or the text of the pl/sql code executed for the trigger.
- ORA-04087: cannot change the value of ROWID reference variable
-
Cause: Rowid's can only be read and not changed.
- ORA-04088: error during execution of trigger 'string.string'
-
Cause: A runtime error occurred during execution of a trigger.
- ORA-04089: cannot create triggers on objects owned by SYS
-
Cause: An attempt was made to create a trigger on an object owned by SYS.
- ORA-04090: 'string' specifies same table, event and trigger time as 'string'
-
Cause: Trigger is of duplicate event and trigger time.
- ORA-04091: table string.string is mutating, trigger/function may not see it
-
Cause: A trigger (or a user defined plsql function that is referenced in this statement) attempted to look at (or modify) a table that was in the middle of being modified by the statement which fired it.
- ORA-04092: cannot string in a trigger
-
Cause: A trigger attempted to commit or rollback.
- ORA-04093: references to columns of type LONG are not allowed in triggers
-
Cause: A trigger attempted to reference a long column in the triggering table.
- ORA-04094: table string.string is constraining, trigger may not modify it
-
Cause: A trigger attempted to modify a table that was constraining for some referential constraint of a parent SQL statement.
- ORA-04095: trigger 'string' already exists on another table, cannot replace it
-
Cause: Cannot replace a trigger which already exists on a different table than the one being replaced.
- ORA-04096: trigger 'string' has a WHEN clause which is too large, limit 2K
-
Cause: A trigger's 'when' clause is limited to 2K for dictionary storage reasons. The trigger being created exceeded that size.
- ORA-04097: DDL conflict while trying to drop or alter a trigger
-
Cause: An attempt was made to concurrently perform two DDL operations on a trigger or trigger table.
- ORA-04098: trigger 'string.string' is invalid and failed re-validation
-
Cause: A trigger was attempted to be retrieved for execution and was found to be invalid. This also means that compilation/authorization failed for the trigger.
- ORA-04099: trigger 'string' is valid but not stored in compiled form
-
Cause: A trigger was attempted to be retrieved for execution and was found to be valid, but not stored. This may mean the an upgrade was done improperly from a non-stored trigger release.