Oracle Database Server Messages(二) .

 

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)

Part Number A96525-01
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback

Go to previous page Go to next page

5
ORA-02100 to ORA-04099


ORA-02100 PCC: out of memory (i.e., could not allocate)

Cause: SQLLIB was unable to allocate enough memory to execute the program.

Action: Allocate more memory to the user session and then rerun the program. If the error persists, contact Oracle Support Services for assistance.


ORA-02101 PCC: inconsistent cursor cache (uce/cuc mismatch)

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02102 PCC: inconsistent cursor cache (no cuc entry for this uce)

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02103 PCC: inconsistent cursor cache (out-of-range cuc ref)

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02104 PCC: inconsistent host cache (no cuc available)

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02105 PCC: inconsistent cursor cache (no cuc entry in cache)

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02106 PCC: inconsistent cursor cache (OraCursor nr is bad)

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02107 PCC: this pgm too old for run-time library: please re-PCC it

Cause: The program was precompiled by an older version of the Oracle Precompilers, which is incompatible with this release of SQLLIB.

Action: Precompile the program with a newer version of the Oracle Precompilers.


ORA-02108 PCC: invalid descriptor passed to run-time library

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02109 PCC: inconsistent host cache (out-of-range sit ref)

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02110 PCC: inconsistent host cache (invalid sqi type)

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02111 PCC: heap consistency error

Cause: This internal error typically indicates a memory-related error.

Action: Check the program for memory-related errors, such as invalid pointers or array-bounds violations.


ORA-02112 PCC: SELECT..INTO returns too many rows

Cause: A SELECT...INTO statement returned more rows than can be stored in the host variable provided.

Action: There are three possible solutions:

  1. Use the precompiler option SELECT_ERROR=NO.
  2. Declare a host variable with a larger array dimension.
  3. Declare a cursor or cursor variable for the select statement.

ORA-02140 invalid tablespace name

Cause: An identifier does not follow ALTER TABLESPACE.

Action: Specify a tablespace name following ALTER TABLESPACE.


ORA-02141 invalid OFFLINE option

Cause: An option other than NORMAL or IMMEDIATE follows OFFLINE.

Action: The user must either specify no option following OFFLINE or one of the options NORMAL or IMMEDIATE.


ORA-02142 missing or invalid ALTER TABLESPACE option

Cause: A valid option is not present.

Action: Use one of the valid options: add, rename, default, online, offline, read only, read write, begin, end, no, or force.


ORA-02143 invalid STORAGE option

Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause.

Action: Specify only valid options.


ORA-02144 no option specified for ALTER CLUSTER

Cause: No ALTER CLUSTER options are specified.

Action: Specify one or more of the following options: PCTFREE, PCTUSED, SIZE, STORAGE.


ORA-02145 missing STORAGE option

Cause: No STORAGE options were specified following STORAGE (.

Action: Specify one or more STORAGE option between the parentheses.


ORA-02146 SHARED specified multiple times

Cause: The SHARED option was specified in a CREATE DATABASE statement multiple times.

Action: Only specify the SHARED option once.


ORA-02147 conflicting SHARED/EXCLUSIVE options

Cause: Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement.

Action: Specify SHARED or EXCLUSIVE, but not both.


ORA-02148 EXCLUSIVE specified multiple times

Cause: The EXCLUSIVE option was specified in a CREATE DATABASE statement multiple times.

Action: Only specify the EXCLUSIVE option once.


ORA-02149 Specified partition does not exist

Cause: Partition not found for the object.

Action: Retry with correct partition name.


ORA-02153 invalid VALUES password string

Cause: An encoded password string does not follow the VALUES clause.

Action: Place a proper encoded password string after the VALUES clause.


ORA-02155 invalid DEFAULT tablespace identifier

Cause: An identifier does not follow DEFAULT TABLESPACE.

Action: Place a tablespace name after DEFAULT TABLESPACE.


ORA-02156 invalid TEMPORARY tablespace identifier

Cause: An identifier does not follow TEMPORARY TABLESPACE.

Action: Place a tablespace name after TEMPORARY TABLESPACE.


ORA-02157 no options specified for ALTER USER

Cause: No options were specified.

Action: Specify at least one ALTER USER option.


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.

Action: Choose one of the valid CREATE INDEX options.


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.

Action: Specify configuration parameters that do not require the additional function.


ORA-02160 index-organized table can not contain columns of type LONG

Cause: A column of type LONG defined for index-organized table.

Action: Do not use columns of type LONG in index-organized tables.


ORA-02161 invalid value for MAXLOGFILES

Cause: A number does not follow MAXLOGFILES.

Action: Specify a number after MAXLOGFILES.


ORA-02162 invalid value for MAXDATAFILES

Cause: A number does not follow MAXDATAFILES.

Action: Specify a number after MAXDATAFILES.


ORA-02163 invalid value for FREELIST GROUPS

Cause: A number does not follow FREELIST GROUPS.

Action: Specify a number after FREELIST GROUPS.


ORA-02164 DATAFILE clause specified more than once

Cause: The CREATE DATABASE command contains more than one DATAFILE clause.

Action: Specify at most one DATAFILE clause.


ORA-02165 invalid option for CREATE DATABASE

Cause: An invalid CREATE DATABASE option is present.

Action: Specify only valid CREATE DATABASE options.


ORA-02166 ARCHIVELOG and NOARCHIVELOG specified

Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement.

Action: Specify at most one of these two options.


ORA-02167 LOGFILE clause specified more than once

Cause: The CREATE DATABASE command contains more than one LOGFILE clause.

Action: Specify at most one LOGFILE clause.


ORA-02168 invalid value for FREELISTS

Cause: A number does not follow FREELISTS.

Action: Specify a number after FREELISTS.


ORA-02169 FREELISTS storage option not allowed

Cause: An attempt was made to specify the FREELISTS storage option. This option may only be specified during create table or create index.

Action: Remove these options and retry the statement.


ORA-02170 FREELIST GROUPS storage option not allowed

Cause: An attempt was made to specify the FREELIST GROUPS storage option. This option may be specified only when using the CREATE TABLE command and when the ALLOW_FREELIST_GROUPS parameter is specified in the initialization parameter file.

Action: Retry the statement without the FREELIST GROUPS storage option or set the ALLOW_FREELIST_GROUPS parameter in the initialization parameter file.


ORA-02171 invalid value for MAXLOGHISTORY

Cause: A number does not follow MAXLOGHISTORY.

Action: Specify a number after MAXLOGHISTORY.


ORA-02172 The PUBLIC keyword is not appropriate for a disable thread

Cause: The PUBLIC keyword was specified for a disable.

Action: Remove the keyword and resubmit.


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.

Action: Place nothing or only INCLUDING CONTENTS after the tablespace name.


ORA-02174 Missing required thread number

Cause: A thread number must be specified after THREAD keyword.

Action: Use correct syntax.


ORA-02175 invalid rollback segment name

Cause: In the CREATE or DROP ROLLBACK SEGMENT statements, an identifier was not found following ROLLBACK SEGMENT.

Action: Place the segment name following ROLLBACK SEGMENT.


ORA-02176 invalid option for CREATE ROLLBACK SEGMENT

Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.

Action: Specify one of the valid options: TABLESPACE and STORAGE.


ORA-02177 Missing required group number

Cause: A group number must be specified after GROUP keyword.

Action: Check the syntax of the command, specify a group number after GROUP, and retry it.


ORA-02178 correct syntax is: SET TRANSACTION READ { ONLY | WRITE }

Cause: There is a syntax error in the user's statement.

Action: Correct the syntax as indicated.


ORA-02179 valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }

Cause: There is a syntax error in the user's statement.

Action: Correct the syntax as indicated.


ORA-02180 invalid option for CREATE TABLESPACE

Cause: An invalid option appears.

Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE, OFFLINE, or FORCE.


ORA-02181 invalid option to ROLLBACK WORK

Cause: A token other than TO follows ROLLBACK [WORK].

Action: Place nothing or TO SAVEPOINT name after ROLLBACK [WORK].


ORA-02182 savepoint name expected

Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT].

Action: Place a savepoint name following TO [SAVEPOINT].


ORA-02183 valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }

Cause: There is a syntax error in the user's statement.

Action: Correct the syntax as indicated.


ORA-02184 resource quotas are not allowed in REVOKE

Cause: In a revoke statement, a resource quota was specified.

Action: Specify resource privilege without the quota.


ORA-02185 a token other than WORK follows COMMIT

Cause: A token other than WORK follows COMMIT.

Action: Place either nothing or WORK after 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.

Action: Use a separate grant or revoke statement for the resource quota privilege.


ORA-02187 invalid quota specification

Cause: In a grant or revoke statement, an attempt was made to grant a tablespace quota above the upper limit.

Action: Grant a smaller tablespace quota.


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.

Action: Specify the tablespace on which the quota is to be applied with the ON tablespace clause.


ORA-02190 keyword TABLES expected

Cause: The keyword TABLES is expected following DROP CLUSTER name INCLUDING.

Action: Place TABLES after INCLUDING.


ORA-02191 correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT rbs

Cause: There is a syntax error in the user's statement.

Action: Correct the syntax as indicated.


ORA-02192 PCTINCREASE not allowed for rollback segment storage clauses

Cause: The storage parameter PCTINCREASE was specified in a CREATE or ALTER ROLLBACK SEGMENT command.

Action: Retry the command without the PCTINCREASE clause.


ORA-02194 event specification syntax error string (minor error string) near 'string'

Cause: There is a syntax error in an event specification.

Action: Check syntax and spelling and try again.


ORA-02195 Attempt to create string object in a string tablespace

Cause: The object type is inconsistent with a tablespace contents.

Action: Create an object in a different tablespace, or change the user defaults.


ORA-02196 PERMANENT/TEMPORARY option already specified

Cause: In CREATE TABLESPACE, the PERMANENT and/or TEMPORARY options were specified more than once.

Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.

For more information about the parameters of CREATE TABLESPACE, see the Oracle9i SQL Reference.


ORA-02197 file list already specified

Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was specified.

Action: Merge the DATAFILE/TEMPFILE clauses into a single clause.


ORA-02198 ONLINE/OFFLINE option already specified

Cause: In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were specified more than once.

Action: Specify at most one of ONLINE or OFFLINE.


ORA-02199 missing DATAFILE/TEMPFILE clause

Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.

Action: Specify a DATAFILE/TEMPFILE clause.


ORA-02200 WITH GRANT OPTION not allowed for PUBLIC

Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.

Action: Remove the WITH GRANT OPTION clause.


ORA-02201 sequence not allowed here

Cause: An attempt was made to reference a sequence in a from-list.

Action: A sequence can only be referenced in a select-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.

Action: Up to 32 tables may be stored per cluster.


ORA-02203 INITIAL storage options not allowed

Cause: An attempt was made 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.

Action: Remove these options and retry the statement.


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.

Action: Do not attempt to grant or revoke any of ALTER, INDEX, or EXECUTE privileges on views.


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.

Action: Do not attempt to grant or revoke DELETE, INDEX, INSERT, UPDATE, REFERENCES or EXECUTE privilege on sequences.


ORA-02206 duplicate INITRANS option specification

Cause: INITRANS is specified more than once.

Action: Specify INITRANS at most 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.

Action: Choose a valid INITRANS value.


ORA-02208 duplicate MAXTRANS option specification

Cause: MAXTRANS is specified more than once.

Action: Specify MAXTRANS at most 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.

Action: Choose a valid MAXTRANS value.


ORA-02210 no options specified for ALTER TABLE

Cause: No ALTER TABLE option was specified.

Action: Specify at least one alter table option.


ORA-02211 invalid value for PCTFREE or PCTUSED

Cause: The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100.

Action: Choose an appropriate value for the option.


ORA-02212 duplicate PCTFREE option specification

Cause: PCTFREE option specified more than once.

Action: Specify PCTFREE at most once.


ORA-02213 duplicate PCTUSED option specification

Cause: PCTUSED option specified more than once.

Action: Specify PCTUSED at most once.


ORA-02214 duplicate BACKUP option specification

Cause: The BACKUP option to ALTER TABLE is specified more than once.

Action: Specify the option at most 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.

Action: Specify at most one TABLESPACE clause.


ORA-02216 tablespace name expected

Cause: A tablespace name is not present where required by the syntax for one of the following statements: CREATE/DROP TABLESPACE, CREATE TABLE, CREATE INDEX, or CREATE ROLLBACK SEGMENT.

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


ORA-02217 duplicate storage option specification

Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE) is specified more than once.

Action: Specify all storage options at most once.


ORA-02218 invalid INITIAL storage option value

Cause: The specified value must be an integer.

Action: Choose an appropriate integer value.


ORA-02219 invalid NEXT storage option value

Cause: The specified value must be an integer.

Action: Choose an appropriate integer value.


ORA-02220 invalid MINEXTENTS storage option value

Cause: The specified value must be a positive integer less than or equal to MAXEXTENTS.

Action: Specify an appropriate value.


ORA-02221 invalid MAXEXTENTS storage option value

Cause: The specified value must be a positive integer greater than or equal to MINEXTENTS.

Action: Specify an appropriate value.


ORA-02222 invalid PCTINCREASE storage option value

Cause: The specified value must be a positive integer.

Action: Specify an appropriate value.


ORA-02223 invalid OPTIMAL storage option value

Cause: The specified value must be an integer.

Action: Choose an appropriate integer value.


ORA-02224 EXECUTE privilege not allowed for tables

Cause: An attempt was made to grant or revoke an invalid privilege on a table.

Action: Do not attempt to grant or revoke EXECUTE privilege on tables.


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.

Action: Do not attempt to grant or revoke any privilege besides EXECUTE or DEBUG on procedures, functions or packages.


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.

Action: Specify a smaller value.


ORA-02227 invalid cluster name

Cause: A cluster name was not properly formed.

Action: Check the rules for forming object names and enter an appropriate cluster name.


ORA-02228 duplicate SIZE specification

Cause: The SIZE option is specified more than once.

Action: Specify the SIZE option at most once.


ORA-02229 invalid SIZE option value

Cause: The specified value must be an integer number of bytes.

Action: Specify an appropriate value.


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.

Action: Specify only legal options.


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.

Action: Specify only legal options.


ORA-02232 invalid MOUNT mode

Cause: A mode other than SHARED or EXCLUSIVE follows the MOUNT keyword in an ALTER DATABASE statement.

Action: Specify either SHARED, EXCLUSIVE, or nothing following MOUNT.


ORA-02233 invalid CLOSE mode

Cause: A mode other than NORMAL or IMMEDIATE follows the CLOSE keyword in an ALTER DATABASE statement.

Action: Specify either NORMAL, IMMEDIATE, or nothing following CLOSE.


ORA-02234 changes to this table are already logged

Cause: The log table to be added is a duplicate of another.

Action: Do not add this change log to the system; check that the replication product's system tables are consistent.


ORA-02235 this table logs changes to another table already

Cause: The table to be altered is already a change log for another table.

Action: Do not log changes to the specified base table to this table; check that the replication product's system tables are consistent.


ORA-02236 invalid file name

Cause: A character string literal was not used in the file name list of a LOGFILE, DATAFILE, or RENAME clause.

Action: Use correct syntax.


ORA-02237 invalid file size

Cause: A non-integer value was specified in the SIZE or RESIZE clause.

Action: Use correct syntax.


ORA-02238 filename lists have different numbers of files

Cause: In a RENAME clause in ALTER DATABASE or TABLESPACE, the number of existing file names does not equal the number of new file names.

Action: Make sure there is a new file name to correspond to each existing file name.


ORA-02239 there are objects which reference this sequence

Cause: The sequence to be dropped is still referenced by other objects.

Action: Make sure the sequence name is correct or drop the constraint or object that references the sequence.


ORA-02240 invalid value for OBJNO or TABNO

Cause: A number does not follow either OBJNO or TABNO.

Action: Specify a number after OBJNO or TABNO.


ORA-02241 must of form EXTENTS (FILE n BLOCK n SIZE n, ...)

Cause: There was an error in the extent storage clause.

Action: Respecify the storage clause using the correct syntax and retry the command.


ORA-02242 no options specified for ALTER INDEX

Cause: No options specified.

Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.


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.

Action: Specify only legal options.


ORA-02244 invalid ALTER ROLLBACK SEGMENT option

Cause: The STORAGE option is expected but not found.

Action: Specify the STORAGE option.


ORA-02245 invalid ROLLBACK SEGMENT name

Cause: An identifier was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT.

Action: Place a rollback segment name following SEGMENT.


ORA-02246 missing EVENTS text

Cause: A character string literal was expected, but not found, following ALTER SESSION SET EVENTS.

Action: Place the string literal containing the events text after EVENTS.


ORA-02247 no option specified for ALTER SESSION

Cause: The option SET EVENTS was expected, but not found, following ALTER SESSION.

Action: Place the SET EVENTS option after ALTER SESSION.


ORA-02248 invalid option for ALTER SESSION

Cause: An option other than SET EVENTS was found following the ALTER SESSION command.

Action: Specify the SET EVENTS option after the ALTER SESSION command and try again.


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.

Action: Specify a valid number after MAXLOGMEMBERS.


ORA-02250 missing or invalid constraint name

Cause: The constraint name is missing or invalid.

Action: Specify a valid identifier name for the constraint name.


ORA-02251 subquery not allowed here

Cause: Subquery is not allowed here in the statement.

Action: Remove the subquery from the statement.


ORA-02252 check constraint condition not properly ended

Cause: The specified search condition for the check constraint is not properly ended.

Action: End the condition properly.


ORA-02253 constraint specification not allowed here

Cause: Constraint specification is not allowed here in the statement.

Action: Remove the constraint specification from the statement.


ORA-02254 DEFAULT expression not allowed here

Cause: Default value expression is not allowed for the column here in the statement.

Action: Remove the default value expression from the statement.


ORA-02255: NOT NULL not allowed after DEFAULT NULL

Cause: A NOT NULL specification conflicts with the NULL default value.

Action: Remove either the NOT NULL or the DEFAULT NULL specification and try again.


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.

Action: Make sure that the referencing columns match the referenced columns.


ORA-02257 maximum number of columns exceeded

Cause: The number of columns in the key list exceeds the maximum number.

Action: Reduce the number columns in the list.


ORA-02258 duplicate or conflicting NULL and/or NOT NULL specifications

Cause: A duplicate or conflicting NULL and/or NOT NULL was specified.

Action: Remove one of the conflicting specifications and try again.


ORA-02259 duplicate UNIQUE/PRIMARY KEY specifications

Cause: A duplicate unique or primary key was specified.

Action: Remove the duplicate specification and try again.


ORA-02260 table can have only one primary key

Cause: Two or more primary keys were specified for the same table.

Action: Remove the extra primary keys and try again.


ORA-02261 such unique or primary key already exists in the table

Cause: A unique or primary key was specified that already exists for the table.

Action: Remove the extra key and try again.


ORA-02262 ORA-string occurs while type-checking column default value expressionexpression

Cause: New column datatype causes type-checking error for existing column default value expression.

Action: Remove the default value expression or do not alter the column datatype.


ORA-02263 need to specify the datatype for this column

Cause: The required datatype for the column is missing.

Action: Specify the required datatype.


ORA-02264 name already used by an existing constraint

Cause: The specified constraint name has to be unique.

Action: Specify a unique constraint name for the constraint.


ORA-02265 cannot derive the datatype of the referencing column

Cause: The datatype of the referenced column is not defined as yet.

Action: Make sure that the datatype of the referenced column is defined before referencing it.


ORA-02266 unique/primary keys in table referenced by enabled foreign keys

Cause: An attempt was made to drop or truncate a table with unique or primary keys referenced by foreign keys enabled in another table.

Action: Before dropping or truncating the table, disable the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command:

select constraint_name, table_name, status
from user_constraints
where r_constraint_name in (
select constraint_name from user_constraints where table_name 
='tabnam');


ORA-02267 column type incompatible with referenced column type

Cause: The datatype of the referencing column is incompatible with the datatype of the referenced column.

Action: Select a compatible datatype for the referencing column.


ORA-02268 referenced table does not have a primary key

Cause: The referenced table does not have a primary key.

Action: Specify explicitly the referenced table unique key.


ORA-02269 key column cannot be of LONG datatype

Cause: An attempt was made to define a key column of datatype LONG. This is not allowed.

Action: Change the datatype of the column or remove the LONG column from the key, and try again.


ORA-02270 no matching unique or primary key for this column-list

Cause: An attempt was made to reference a unique or primary key in a table with a CREATE or ALTER TABLE statement when no such key exists in the referenced table.

Action: Add the unique or primary key to the table or find the correct names of the columns with the primary or unique key, and try again.


ORA-02271 table does not have such constraint

Cause: An attempt was made to reference a table using a constraint that does not exist.

Action: Check the spelling of the constraint name or add the constraint to the table, and try again.


ORA-02272 constrained column cannot be of LONG datatype

Cause: A constrained column cannot be defined as datatype LONG. This is not allowed.

Action: Change the datatype of the column or remove the constraint on the column, and try again.


ORA-02273 this unique/primary key is referenced by some foreign keys

Cause: A unique or primary key referenced by foreign keys cannot be dropped.

Action: Remove all references to the key before dropping it.


ORA-02274 duplicate referential constraint specifications

Cause: A referential constraint was specified more than once. This is not allowed.

Action: Remove the duplicate specification.


ORA-02275 such a referential constraint already exists in the table

Cause: An attempt was made to specify a referential constraint that already exists. This would result in duplicate specifications and so is not allowed.

Action: Be sure to specify a constraint only once.


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.

Action: Change the type of the column, or modify the default expression.


ORA-02277 invalid sequence name

Cause: The specified sequence name is not a valid identifier name.

Action: Specify a valid identifier name for the sequence name.


ORA-02278 duplicate or conflicting MAXVALUE/NOMAXVALUE specifications

Cause: Duplicate or conflicting MAXVALUE and/or NOMAXVALUE specifications.

Action: Remove one of the conflicting specifications and try again.


ORA-02279 duplicate or conflicting MINVALUE/NOMINVALUE specifications

Cause: Duplicate or conflicting MINVALUE and/or NOMINVALUE clauses were specified.

Action: Remove one of the conflicting specifications and try again.


ORA-02280 duplicate or conflicting CYCLE/NOCYCLE specifications

Cause: Duplicate or conflicting CYCLE and/or NOCYCLE clauses were specified.

Action: Remove one of the conflicting specifications and try again.


ORA-02281 duplicate or conflicting CACHE/NOCACHE specifications

Cause: Duplicate or conflicting CACHE and/or NOCACHE clauses were specified.

Action: Remove one of the conflicting specifications and try again.


ORA-02282 duplicate or conflicting ORDER/NOORDER specifications

Cause: Duplicate or conflicting ORDER and/or NOORDER clauses were specified.

Action: Remove one of the conflicting specifications and try again.


ORA-02283 cannot alter starting sequence number

Cause: An attempt was made to alter a starting sequence number. This is not allowed.

Action: Do not try to alter a starting sequence number.


ORA-02284 duplicate INCREMENT BY specifications

Cause: A duplicate INCREMENT BY clause was specified.

Action: Remove the duplicate specification and try again.


ORA-02285 duplicate START WITH specifications

Cause: A duplicate START WITH clause was specified.

Action: Remove the duplicate specification and try again.


ORA-02286 no options specified for ALTER SEQUENCE

Cause: No ALTER SEQUENCE option was specified.

Action: Check the syntax. Then specify at least one ALTER SEQUENCE option.


ORA-02287 sequence number not allowed here

Cause: The specified sequence number reference, CURRVAL or NEXTVAL, is inappropriate at this point in the statement.

Action: Check the syntax. Then remove or relocate the sequence number.


ORA-02288 invalid OPEN mode

Cause: A mode other than RESETLOGS was specified in an ALTER DATABASE OPEN statement. RESETLOGS is the only valid OPEN mode.

Action: Remove the invalid mode from the statement or replace it with the keyword RESETLOGS, and try again.


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.

Action: Make sure the sequence name is correct, and that you have the right to perform the desired operation on this sequence.


ORA-02290 check constraint (string.string) violated

Cause: The value or values attempted to be entered in a field or fields violate a defined check constraint.

Action: Enter values that satisfy the constraint.


ORA-02291 integrity constraint (string.string) violated - parent key not found

Cause: A foreign key value has no matching primary key value.

Action: Delete the foreign key or add a matching primary key.


ORA-02292 integrity constraint (string.string) violated - child record found

Cause: An attempt was made to delete a row that is referenced by a foreign key.

Action: It is necessary to DELETE or UPDATE the foreign key before changing this row.


ORA-02293 cannot validate (string.string) - check constraint violated

Cause: An attempt was made via an ALTERTABLE statement to add a check constraint to a populated table that had no complying values.

Action: Retry the ALTER TABLE statement, specifying a check constraint on a table containing complying values. For more information about ALTER TABLE, see the Oracle9i SQL Reference.


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.

Action: Try again, with only one DDL changing the constraint this time.


ORA-02295 found more than one enable/disable clause for constraint

Cause: An attempt was made via a CREATE or ALTER TABLE statement to specify more than one ENABLE and/or DISABLE clause for a given constraint.

Action: Only one ENABLE or DISABLE clause may be specified for a given constraint.


ORA-02296 cannot enable (string.string) - null values found

Cause: An ALTER TABLE command with an ENABLE CONSTRAINT clause failed because the table contains values that do not satisfy the constraint.

Action: Make sure that all values in the table satisfy the constraint before issuing an ALTER TABLE command with an ENABLE CONSTRAINT clause. For more information about ALTER TABLE and ENABLE CONSTRAINT, see the Oracle9i SQL Reference.


ORA-02297 cannot disable constraint (string.string) - dependencies exist

Cause: An alter table disable constraint failed because the table has foreign keys that are dependent on the constraint.

Action: Either disable the foreign key constraints or use a DISABLE CASCADE command.


ORA-02298 cannot validate (string.string) - parent keys not found

Cause: An ALTER TABLE ENABLE CONSTRAINT command failed because the table has orphaned child records.

Action: Make sure that the table has no orphaned child records before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see the Oracle9i SQL Reference.


ORA-02299 cannot validate (string.string) - duplicate keys found

Cause: An ALTER TABLE ENABLE CONSTRAINT command failed because the table has duplicate key values.

Action: Make sure that the table has no duplicate key values before issuing an ALTER TABLE ENABLE CONSTRAINT command. For more information about ALTER TABLE and ENABLE CONSTRAINT, see the Oracle9i SQL Reference.


ORA-02300 invalid value for OIDGENERATORS

Cause: A number was not specified for the value of OIDGENERATORS.

Action: Specify a number for OIDGENERATORS.


ORA-02301 maximum number of OIDGENERATORS is 255

Cause: A number greater than 255 was specified for the value of OIDGENERATORS.

Action: Make sure the number specified for OIDGENERATORS does not exceed 255.


ORA-02302 invalid or missing type name

Cause: An invalid or missing type name was entered in a statement.

Action: Enter a valid type name in the statement and retry the operation.


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 dependents. There could be a substitutable column of a supertype of the type being dropped.

Action: Drop all types and tables depending on the type, then retry the operation using the VALIDATE option, or use the FORCE option.


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

Action: Do not specify the object identifier clause or specify a 32 hexadecimal-character object identifier literal that is unique or identical to the originally assigned object identifier. Then retry the operation.


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.

Action: GRANT or REVOKE only the EXECUTE, DEBUG, or UNDER privilege on types.


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).

Action: Drop the dependents first before creating the type, or do not create the type.


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.

Action: Use the CREATE OR REPLACE TYPE command to modify the type.


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.

Action: Remove the invalid option from column specification and retry the operation.


ORA-02309 atomic NULL violation

Cause: An attempt was made to access the attributes of a NULL object instance.

Action: Ensure that the object instance is non-NULL before accessing.


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.

Action: Specify fewer attributes for the object type and retry the operation.


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.

Action: No need to perform this operation.


ORA-02313 object type contains non-queryable type string attribute

Cause: The specified object type contains a nested attribute whose type is non-queryable.

Action: Use an object type with queryable attribute types.


ORA-02315 incorrect number of arguments for default constructor

Cause: The number of arguments specified for the default constructor does not match the number of attributes of the object type.

Action: Specify the correct number of arguments for the default constructor and retry the operation.


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.

Action: See the messages that follow for more details. If the situation they describe can be corrected, do so; otherwise contact Oracle Support Services.


ORA-02322 failure in accessing storage table of the nested table column

Cause: An error occurred while performing DML on the storage table of the nested table column.

Action: If the situation described in the following messages can be corrected, do so; otherwise contact Oracle Support Services.


ORA-02324 more than one column in the SELECT list of THE subquery

Cause: More than one column was selected in the THE subquery.

Action: Specify only one column in the SELECT list of the THE subquery and retry the operation.


ORA-02327 cannot create index on expression with datatype string

Cause: An attempt was made to create an index on a non-indexable expression.

Action: Change the column datatype or do not create the index on an expression whose datatype is one of VARRAY, nested table, object, LOB, or REF.


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.

Action: Change the column datatype or remove the constraint. Then retry the operation.


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.

Action: Remove data type specification and retry the operation.


ORA-02331 cannot create constraint on column of datatype string

Cause: An attempt was made to create a constraint on a column possessing a non-constrainable datatype: VARRAY, nested table, object, LOB, FILE, or REF.

Action: Change the column datatype, or remove the constraint.


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.

Action: Do not specify the index on the attribute.


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.

Action: Remove the constraint or change the object type.


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.

Action: Declare a datatype for the 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.

Action: Remove the CLUSTER column or change the datatype of the column.


ORA-02336 column attribute cannot be accessed

Cause: An attempt was made to extract an attribute of an object type column.

Action: Change the object type for the column and retry the operation.


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.

Action: Either change the column type to an object type or do not perform this operation.


ORA-02338 missing or invalid column constraint specification

Cause: A column constraint was not specified.

Action: Remove the column specification or specify a column constraint. Then retry the operation.


ORA-02339 invalid column specification

Cause: An attempt was made to specify the PACKED or UNPACKED keyword for a non-object type column.

Action: Remove the PACKED or UNPACKED keyword in the column specification and retry the operation.


ORA-02340 invalid column specification

Cause: An attempt was made to specify an UNPACKED column within a packed table.

Action: Remove the UNPACKED keyword in the column specification.


ORA-02342 replacement type has compilation errors

Cause: The use of the ALTER...REPLACE statement on a valid type caused a compilation error.

Action: Use the ALTER...REPLACE statement to replace the type with a valid type which does not cause compilation errors.


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.

Action: Drop all table(s) depending on the type, then retry the operation, or use the FORCE option.


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.

Action: Remove the CURSOR operator and replace it with the CAST operator.


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.

Action: Choose another table. Privileges cannot be granted on 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.

Action: Remove the offending attribute from the type. If it is a subtype attribute then declare the VARRAY column NOT SUBSTITUTABLE.


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.

Action: Complete the type definition and retry the operation.


ORA-02351 Record string: Rejected - Error on table string, column string

Cause: The record indicated caused an Oracle error on insert.

Action: Determine the Oracle error and correct the record.


ORA-02352 Direct path connection must be homogeneous

Cause: The user-side to kernel-side connection is heterogeneous.

Action: In versions prior to 9.0.0, the connection must be between identical hardware and operating systems. In addition, the SQL*Loader and RDBMS versions must be the same.


ORA-02353 Multibyte character error

Cause: Text specified by POSITION or terminated by newlines is invalid.

Action: Edit the control file or the datafile to fix alignment of column.


ORA-02354 Conversion initialization error occurred on field string

Cause: An error occurred during conversion initialization for a field. This is an internal error.

Action: Contact Oracle Support Services.


ORA-02355 Conversion error occurred on CONSTANT field string

Cause: A CONSTANT field caused an Oracle error; all rows will be rejected.

Action: Determine the Oracle error and correct the record.


ORA-02356 The database is out of space. The load cannot continue

Cause: The load was discontinued due to space exhaustion in the database.

Action: Add space for the specified table.


ORA-02357 Packed Decimal conversion error

Cause: The column could not be converted from packed decimal to character.

Action: Check the column and make it conform to packed decimal format.


ORA-02358 Zoned Decimal conversion error

Cause: The column could not be converted from packed decimal to character.

Action: Check the column and make it conform to packed decimal format.


ORA-02359 Field in data file exceeded maximum specified length

Cause: The field is too long for the specified column.

Action: Shorten the field so that its length is less than or equal to the column length.


ORA-02360 Column not found before end of logical record (use TRAILING NULLCOLS)

Cause: A column started after the end of the logical record had been reached.

Action: Use the TRAILING NULLCOLS option or supply data for the column.


ORA-02361 Initial enclosing character not found

Cause: The initial enclosing character of an enclosed field was not found.

Action: Supply the character before the start of the field.


ORA-02362 Logical record ended - second enclosing character not present

Cause: The second enclosing character of an enclosed field was not found.

Action: Supply the character after the end of the field.


ORA-02363 No terminator found after TERMINATED and ENCLOSED field

Cause: No terminator was found after a terminated and enclosed field.

Action: Supply the character after the end of the field.


ORA-02364 Record string: Discarded - failed all WHEN clauses

Cause: The record was not loaded because it failed the WHEN clauses of all the tables.

Action: No action required.


ORA-02365 Index string was made Index Unusable due to

Cause: The index was not loaded. The cause of the error is stated after the message.

Action: Correct the cause of the error, then reload.


ORA-02366 The following index(es) on table string were processed:

Cause: The indexes listed for the named table were loaded.

Action: No action required.


ORA-02367 Index string was loaded.

Cause: The index specified in the message was loaded.

Action: No action required.


ORA-02368 Record string: Discarded - all columns null.

Cause: The record was not loaded because all of the columns in the table were null for that record.

Action: No action required.


ORA-02369 Warning: Variable length field was truncated.

Cause: A variable length field was truncated by the end of the logical record.

Action: This is just a warning, but since a variable length field has the length embedded in the data for each row, you may want to check your data.


ORA-02370 Record string - Warning on table string, column string

Cause: The record indicated caused an warning.

Action: Determine the warning and correct the record if necessary.


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.

Action: Upgrade your loader to at least the specified version or use the conventional path.


ORA-02372 Relative start position > absolute field end position.

Cause: A field specified as POSITION(*+n:y) had its relative start occur after the absolute position y.

Action: Check that you are not missing a delimiter and that the values of n and y are correct.


ORA-02373 Error parsing insert statement for table string.

Cause: A parsing error occurred.

Action: Check the message following this parsing error message.


ORA-02374 No more slots for read buffer queue.

Cause: There are no free read buffers.

Action: Use the READBUFFERS keyword in the loader to increase the number of read buffers.


ORA-02375 Record string: Rejected - Error on table string

Cause: The record indicated caused an Oracle error on insert.

Action: Determine the Oracle error and correct the record. The offending column(s) are not known.


ORA-02376 invalid or redundant resource

Cause: A resource that is not defined or that is specified twice appears in the CREATE or ALTER PROFILE statement.

Action: Define the resource before issuing a CREATE or ALTER PROFILE command. Also check the statement to see that each resource is listed only once.


ORA-02377 invalid resource limit

Cause: An invalid resource limit of 0 was specified.

Action: Specify a resource limit greater than 0.


ORA-02378 duplicate resource name string

Cause: The same resource was specified twice in a CREATE or ALTER PROFILE statement.

Action: Issue the statement again, carefully checking that each resource is used only once.


ORA-02379 profile string already exists

Cause: An attempt was made to create a profile that already exists.

Action: Create the profile with a name not already used by another profile.


ORA-02380 profile string does not exist

Cause: An attempt was made to assign a user to a non-existent profile.

Action: Assign the user to an existing profile.


ORA-02381 cannot drop PUBLIC_DEFAULT profile

Cause: An attempt was made to drop the PUBLIC_DEFAULT profile.

Action: The PUBLIC_DEFAULT profile cannot be dropped.


ORA-02382 profile string has users assigned, cannot drop without CASCADE

Cause: An attempt was made to drop a profile that had users assigned to it without using the CASCADE option of the DROP PROFILE statement. A profile that has users assigned to it cannot be dropped, unless the CASCADE option is specified. CASCADE reassigns users to the PUBLIC_DEFAULT profile before dropping the profile.

Action: To reassign all users to the PUBLIC_DEFAULT profile, issue the DROP PROFILE statement with the CASCADE option.


ORA-02383 illegal cost factor

Cause: A negative value or UNLIMITED cost was specified for this resource in the ALTER RESOURCE COST statement.

Action: Only positive integer values can be specified for resources in the ALTER RESOURCE COST statement. Issue the statement again, using a positive integer value for each resource specified.


ORA-02390 exceeded COMPOSITE_LIMIT, you are being logged off

Cause: The COMPOSITE_LIMIT for the profile is exceeded. That is, the weighted sum of the connection time, logical reads per session, CPU usage per session, and private SGA space used during the session exceeded the limit set by the COMPOSITE_LIMIT clause set in the user profile.

Action: If this happens often, ask the database administrator to raise the COMPOSITE_LIMIT of the user profile, or determine which resource is used the most and raise the limit on that resource.


ORA-02391 exceeded simultaneous SESSIONS_PER_USER limit

Cause: An attempt was made to exceed the maximum number of concurrent sessions allowed by the SESSIONS_PER_USER clause of the user profile.

Action: End one or more concurrent sessions or ask the database administrator to increase the SESSIONS_PER_USER limit of the user profile. For more information about SESSIONS_PER_USER and the database administrator's specific tasks of adjusting concurrent sessions, see the Oracle9i SQL Reference and the Oracle9i Database Administrator's Guide.


ORA-02392 exceeded session limit on CPU usage, you are being logged off

Cause: An attempt was made to exceed the maximum CPU usage allowed by the CPU_PER_SESSION clause of the user profile.

Action: If this happens often, ask the database administrator to increase the CPU_PER_SESSION limit of the user profile.


ORA-02393 exceeded call limit on CPU usage

Cause: An attempt was made to exceed the maximum CPU time for a call, a parse, execute, or fetch, allowed by the CPU_PER_CALL clause of the user profile.

Action: If this happens often, ask the database administrator to increase the CPU_PER_CALL limit of the user profile.


ORA-02394 exceeded session limit on IO usage, you are being logged off

Cause: An attempt was made to exceed the maximum I/O allowed by the LOGICAL_READS_PER_SESSION clause of the user profile.

Action: If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_SESSION limit of the user profile.


ORA-02395 exceeded call limit on IO usage

Cause: An attempt was made to exceed the maximum I/O for a call, a parse, execute, or fetch, allowed by the LOGICAL_READS_PER_CALL clause of the user profile.

Action: If this happens often, ask the database administrator to increase the LOGICAL_READS_PER_CALL limit of the user profile.


ORA-02396 exceeded maximum idle time, please connect again

Cause: A user has exceeded the maximum time allowed to remain idle.

Action: The user must reconnect to the database.


ORA-02397 exceeded PRIVATE_SGA limit, you are being logged off

Cause: This error occurs only when using a multi-threaded server.

Action: Contact the database administrator to expand the PRIVATE_SGA limit.


ORA-02398 exceeded procedure space usage

Cause: Stored procedures used up too much space in the SYSTEM tablespace.

Action: Use fewer stored procedures or add an additional file to the system tablespace.


ORA-02399 exceeded maximum connect time, you are being logged off

Cause: A user has exceeded the maximum time allowed to be connected to the database.

Action: The user must reconnect to the database.


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.

Action: Create a view with the same definition that belongs to current user.


ORA-02402 PLAN_TABLE not found

Cause: The table used by EXPLAIN to store row source information does not exist in the current schema.

Action: Create a plan table in the current schema or use the INTO clause of the statement to put the results of the explain command in an existing plan table.


ORA-02403 plan table does not have correct format

Cause: The explicit plan table does not have the appropriate field definitions.

Action: Redefine the plan table to have the appropriate field definitions.


ORA-02404 specified plan table not found

Cause: The specified plan table does cannot be found.

Action: Create the specified plan table or use an existing plan table.


ORA-02420 missing schema authorization clause

Cause: The AUTHORIZATION clause is missing from a create schema statement.

Action: Proceed the schema authorization identifier with the AUTHORIZATION keyword.


ORA-02421 missing or invalid schema authorization identifier

Cause: One of the following:

  • The schema authorization identifier is not recognized.
  • An attempt was made to use a schema authorization identifier for a user while not connected as that user.

Action: If the cause is

  • an unrecognized identifier, then use an existing identifier.
  • connected with a different user name, then disconnect and connect to the correct user name.

ORA-02422 missing or invalid schema element

Cause: A statement other than a CREATE TABLE, CREATE VIEW, or GRANT appears in a CREATE SCHEMA statement.

Action: See the Oracle9i SQL Reference or the valid elements of the 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.

Action: Check that the schema names match the one given in the CREATE SCHEMA statement.


ORA-02424 potential circular view references or unknown referenced tables

Cause: The CREATE SCHEMA statement contains a view that depends on other views contained in the CREATE SCHEMA statement, or they contain references to non-existing tables.

Action: Create the dependent views in a separate CREATE SCHEMA statement and ensure that all referenced tables are either defined in the CREATE SCHEMA statement or exist outside the statement.


ORA-02425 create table failed

Cause: A CREATE TABLE statement failed in the CREATE SCHEMA statement.

Action: The cause for failure will be presented below this message. Follow the appropriate actions as suggested by the subsequent messages.


ORA-02426 privilege grant failed

Cause: A GRANT statement failed in the CREATE SCHEMA statement.

Action: The cause for failure will be presented below this message. Follow appropriate actions, as suggested by the subsequent messages.


ORA-02427 create view failed

Cause: A CREATE VIEW statement failed in the CREATE SCHEMA statement.

Action: The cause for failure will be presented below this message. Follow appropriate actions, as suggested by the subsequent messages.


ORA-02428 could not add foreign key reference

Cause: Oracle could not add a foreign key reference because of an error in the declaration. Either the referenced table does not exist or the table does not have a unique key.

Action: Check that the referenced table exists and/or has a unique key.


ORA-02429 cannot drop index used for enforcement of unique/primary key

Cause: An attempt was made to drop an index that is being used as the enforcement mechanism for a unique or primary key.

Action: Drop the integrity constraint instead of dropping the index.


ORA-02430 cannot enable constraint (string) - no such constraint

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

Action: Check that a constraint exists before trying to enable it.


ORA-02431 cannot disable constraint (string) - no such constraint

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

Action: Check that a constraint exists before trying to disable it.


ORA-02432 cannot enable primary key - primary key not defined for table

Cause: An attempt was made to enable a primary key that is not defined for the table.

Action: Add a primary key definition for the table.


ORA-02433 cannot disable primary key - primary key not defined for table

Cause: An attempt was made to disable a primary key that is not defined for the table.

Action: Check that a primary key exists before trying to disable it.


ORA-02434 cannot enable unique(string) - unique key not defined for table

Cause: An attempt was made to enable a unique key that is not defined for the table.

Action: Check that a unique key exists before trying to enable it.


ORA-02435 cannot disable unique(string) - unique key not defined for table

Cause: An attempt was made to disable a unique key that is not defined for the table.

Action: Check that a unique key exists before trying to disable it.


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.

Action: Completely specify the date constant or system variable.


ORA-02437 cannot validate (string.string) - primary key violated

Cause: An attempt was made to validate a primary key with duplicate values or null values.

Action: Remove the duplicates and null values before enabling a primary key.


ORA-02438 Column check constraint cannot reference other columns

Cause: An attempt was made to define a column check constraint that references another column.

Action: Define it as a table check constraint.


ORA-02439 Unique index on a deferrable constraint is not allowed

Cause: An attempt was made to enable a deferrable primary key/unique constraint that has an existing unique index on the constraint columns.

Action: Drop the index on the constraint columns or make the constraint not deferrable.


ORA-02440 Create as select with referential constraints not allowed

Cause: Integrity constraints on a table cannot be created when creating the table using the CREATE TABLE... AS SELECT... form.

Action: First, create the table, and then alter the table to add the desired integrity constraints.


ORA-02441 Cannot drop nonexistent primary key

Cause: An attempt was made to drop the primary key constraint on a table, but there is no primary key constraint on this table.

Action: Ensure the correct table name is entered in the statement. Otherwise, no action required.


ORA-02442 Cannot drop nonexistent unique key

Cause: An attempt was made to drop a unique key constraint for a column that does not have a unique key constraint.

Action: Make certain the correct column name was entered. Otherwise, no action required.


ORA-02443 Cannot drop constraint - nonexistent constraint

Cause: An attempt was made to drop a constraint that does not exist.

Action: Make certain the constraint and table name are correct and attempt the procedure again.


ORA-02444 Cannot resolve referenced object in referential constraints

Cause: An attempt was made to define a foreign key with a reference to a schema object that cannot be resolved to a base table reference.

Action: Define referential constraints only with schema objects resolving to a base table.


ORA-02445 Exceptions table not found

Cause: The explicitly or implicitly declared exceptions table does not exist.

Action: If the correct exceptions table name was used, then create the table and retry the enable command.


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.

Action: Do not select rows that violate constraints.


ORA-02447 cannot defer a constraint that is not deferrable

Cause: An attempt was made to defer a nondeferrable constraint.

Action: Drop the constraint and create a new one that is deferrable.


ORA-02448 constraint does not exist

Cause: The named constraint does not exist.

Action: Choose a constraint that does exist or do not perform this operation.


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.

Action: Before performing the above operations the table, drop the foreign key constraints in other tables. You can see what constraints are referencing a table by issuing the following command:

SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = "tabnam";


ORA-02450 Invalid hash option - missing keyword IS

Cause: Missing IS keyword.

Action: Specify HASH IS option.


ORA-02451 duplicate HASHKEYS specification

Cause: The HASHKEYS option is specified more than once.

Action: Only specify the HASHKEYS option once.


ORA-02452 invalid HASHKEYS option value

Cause: The specified HASHKEYS option must be an integer value.

Action: Specify an appropriate value.


ORA-02453 duplicate HASH IS specification

Cause: The HASH IS option is specified more than once.

Action: only specify the HASH IS option once.


ORA-02454 Number of hash keys per block (string) exceeds maximum of string

Cause: The SIZE argument is too small.

Action: Increase the SIZE argument.


ORA-02455 The number of cluster key column must be 1

Cause: When specifying the HASH IS option, the number of key columns must be 1.

Action: Either do not specify the HASH IS option or reduce the number of key columns.


ORA-02456 The HASH IS column specification must be NUMBER(*,0)

Cause: The column specification must specify an integer.

Action: Specify the column definition as type NUMBER(precision, 0).


ORA-02457 The HASH IS option must specify a valid column

Cause: The HASH IS column name is not specified in the cluster definition.

Action: Specify a valid column name.


ORA-02458 HASHKEYS must be specified for a HASH CLUSTER

Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER.

Action: Specify the HASHKEYS option.


ORA-02459 Hashkey value must be a positive integer

Cause: The value of the hash key was not a positive number.

Action: Specify a positive integer.


ORA-02460 Inappropriate index operation on a hash cluster

Cause: An attempt to create a cluster index was issued on a hash cluster.

Action: Do not attempt to create such an index.


ORA-02461 Inappropriate use of the INDEX option

Cause: This option is only valid for non hash clusters.

Action: Do not specify this option.


ORA-02462 Duplicate INDEX option specified

Cause: The INDEX option is specified more than once.

Action: Only specify the INDEX option once.


ORA-02463 Duplicate HASH IS option specified

Cause: The HASH IS option is specified more than once.

Action: Only specify the HASH IS option 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.

Action: Remove either the HASH IS or INDEX options.


ORA-02465 Inappropriate use of the HASH IS option

Cause: This option is only valid for clusters.

Action: Do not specify this option.


ORA-02466 The SIZE option is not allow to be altered for HASH CLUSTERS

Cause: The SIZE cannot be changed once the hash cluster has been created.

Action: Do not specify this option.


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.

Action: Re-create the cluster and correct the error in hash expression.


ORA-02468 Constant or system variable wrongly specified in expression

Cause: A constant or system variable was specified in the hash expression.

Action: Re-create the cluster and correct the error in hash expression.


ORA-02469 Hash expression does not return an Oracle Number.

Cause: Result of evaluating hash expression is not an Oracle Number.

Action: Re-create the cluster and correct the error in hash expression.


ORA-02470 TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.

Cause: TO_DATE, USERENV and SYSDATE are not allowed in hash expressions.

Action: Re-create the cluster and correct the error 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.

Action: Re-create the cluster and remove the offending keywords.


ORA-02472 PL/SQL functions not allowed in hash expressions

Cause: A PL/SQL function was used in the hash expression.

Action: Re-create the cluster and remove the PL/SQL function.


ORA-02473 Error while evaluating the cluster's hash expression.

Cause: An error occurred while evaluating the clusters hash expression.

Action: Correct the query and retry.


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.

Action: Reduce the number of extents required by increasing the extent allocation sizes within the STORAGE clause.


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.

Action: Increase SIZE parameter in CREATE CLUSTER statement or reconsider suitability of cluster key.


ORA-02476 can not create index due to parallel direct load on table

Cause: A parallel direct load is occurring to the specified table.

Action: Retry statement after load is complete.


ORA-02477 can not perform parallel direct load on object string

Cause: A parallel direct load is not possible because an index is being created on the table.

Action: Retry load after index creation is complete.


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 temporary and base segments.

Action: Use a larger value for MAXEXTENTS on the base segment or make the extents in the temporary segments larger.


ORA-02479 error while translating file name for parallel load

Cause: An invalid file name was specified to load data into.

Action: Specify a valid database file.


ORA-02481 Too many processes specified for events (max string)

Cause: Too many processes specified than allowed per event.

Action: Enter fewer processes by using ranges or wildcards if possible.


ORA-02482 Syntax error in event specification (string)

Cause: Illegal event string.

Action: Enter a legal event string.


ORA-02483 Syntax error in process specification (string)

Cause: Illegal process string.

Action: Enter a legal process string.


ORA-02486 Error in writing trace file string

Cause: Error occurred in creating/writing the file.

Action: Check the file name and make sure it is constructed properly. Also, check permissions for directories.


ORA-02490 missing required file size in RESIZE clause

Cause: No value was specified for the RESIZE clause.

Action: Use the correct syntax.


ORA-02491 missing required keyword ON or OFF in AUTOEXTEND clause

Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause.

Action: Use the correct syntax.


ORA-02492 missing required file block increment size in NEXT clause

Cause: No value was specified for the NEXT clause.

Action: Use the correct syntax.


ORA-02493 invalid file increment size in NEXT clause

Cause: A non-integer value was used for the NEXT clause of the DATAFILE list.

Action: Use the correct syntax.


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.

Action: Use the correct syntax.


ORA-02495 cannot resize file string, tablespace string is read only

Cause: An attempt was made to resize a datafile in a tablespace that is read only.

Action: Change the tablespace to read/write and retry the resize operation.


ORA-02700 osnoraenv: error translating ORACLE_SID

Cause: Two-task driver could not find the value of ORACLE_SID in the environment.

Action: Make sure that the ORACLE_SID environment variable has been properly set and exported.


ORA-02701 osnoraenv: error translating oracle image name

Cause: ORACLE_HOME environment variable not set.

Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.


ORA-02702 osnoraenv: error translating orapop image name

Cause: ORACLE_HOME environment variable not set.

Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.


ORA-02703 osnpopipe: pipe creation failed

Cause: The pipe driver failed to create pipes for communications with the ORAPOP process.

Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator.


ORA-02704 osndopop: fork failed

Cause: The two-task driver could not fork ORAPOP.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.


ORA-02705 osnpol: polling of communication channel failed

Cause: The pipe driver failed while polling the communications channel.

Action: Contact Oracle Support Services.


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.

Action: Contact Oracle Support Services.


ORA-02707 osnacx: cannot allocate context area

Cause: The invoked UNIX two-task driver could not allocate heap space for the context area.

Action: Contact Oracle Support Services.


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.

Action: First, check whether you have read access to ORATAB, and see if the desired sid is there. Add an entry to ORATAB for the desired SID, if necessary.


ORA-02709 osnpop: pipe creation failed

Cause: The pipe driver failed to create pipes for two-task communications with the Oracle shadow process.

Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator.


ORA-02710 osnpop: fork failed

Cause: The pipe driver could not fork the Oracle shadow process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.


ORA-02711 osnpvalid: write to validation channel failed

Cause: The pipe driver failed to write to the ORAPOP process.

Action: Contact Oracle Support Services.


ORA-02712 osnpop: malloc failed

Cause: The pipe driver failed to allocate enough heap space for its context area buffers.

Action: Contact Oracle Support Services.


ORA-02713 osnprd: message receive failure

Cause: The pipe driver failed to read a message from the communications channel.

Action: Contact Oracle Support Services.


ORA-02714 osnpwr: message send failure

Cause: The pipe driver failed to write a message to the communications channel.

Action: Contact Oracle Support Services.


ORA-02715 osnpgetbrkmsg: message from host had incorrect message type

Cause: The pipe driver received a message having an unrecognizable message type.

Action: Contact Oracle Support Services.


ORA-02716 osnpgetdatmsg: message from host had incorrect message type

Cause: The Pipe driver received a message having an unrecognizable message type.

Action: Contact Oracle Support Services.


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.

Action: Contact Oracle Support Services.


ORA-02718 osnprs: reset protocol error

Cause: The two-task driver could not reset the connection.

Action: Contact Oracle Support Services.


ORA-02719 osnfop: fork failed

Cause: The fast driver could not fork the Oracle shadow process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.


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 accommodate the buffer.

Action: Try invoking the Fast driver later, or use the default attach address.


ORA-02721 osnseminit: cannot create semaphore set

Cause: The Fast driver failed to get a semaphore set.

Action: The system-imposed limit on semaphores or semaphore identifiers may have been exceeded. Read the returned operating system error code and check with your system administrator.


ORA-02722 osnpui: cannot send break message to orapop

Cause: The Pipe driver could not send a break message to ORAPOP.

Action: Contact Oracle Support Services.


ORA-02723 osnpui: cannot send break signal

Cause: The Pipe driver could not send a break message to the Oracle shadow process.

Action: Contact Oracle Support Services.


ORA-02724 osnpbr: cannot send break message to orapop

Cause: The Pipe driver could not send a break message to ORAPOP.

Action: Contact Oracle Support Services.


ORA-02725 osnpbr: cannot send break signal

Cause: The Pipe driver could not send a break message to the Oracle shadow process.

Action: Kill system call failed. Check the error code (errno) and contact Oracle Support Services.


ORA-02726 osnpop: access error on oracle executable

Cause: The Pipe driver could not access the Oracle executable.

Action: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path.


ORA-02727 osnpop: access error on orapop executable

Cause: The Pipe driver could not access the ORAPOP executable.

Action: Check the permissions on the ORAPOP executable and each component of the ORACLE_HOME/bin path.


ORA-02728 osnfop: access error on oracle executable

Cause: The Fast driver could not access the Oracle executable.

Action: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path.


ORA-02729 osncon: driver not in osntab

Cause: The driver you have specified is not supported.

Action: Check with your database administrator which drivers are 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.

Action: Set and export the HOME environment variable to identify your home directory. Check with your system administrator to make sure that your UID and home directory are correct in the /etc/passwd file.


ORA-02731 osnrnf: malloc of buffer failed

Cause: The specified driver could not find enough heap space to MALLOC a buffer.

Action: Contact Oracle Support Services.


ORA-02732 osnrnf: cannot find a matching database alias

Cause: Database alias specified was not identified in either $HOME/.sqlnet or /etc/sqlnet.

Action: Create the alias in a file called .sqlnet in the home directory for personal use, or have system administrator create the alias in /etc/sqlnet for system-wide use.


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.

Action: Contact Oracle Support Services.


ORA-02734 osnftt: cannot reset shared memory permission

Cause: The Fast driver was unable to reset shared memory permissions.

Action: Contact Oracle Support Services.


ORA-02735 osnfpm: cannot create shared memory segment

Cause: The Fast driver failed to create a shared memory segment for two-task communication.

Action: Check whether the system-imposed limit on shared memory identifiers has already been reached for your system.


ORA-02736 osnfpm: illegal default shared memory address

Cause: The Fast driver failed to establish a default shared memory address.

Action: Contact Oracle Support Services.


ORA-02737 osnpcl: cannot tell orapop to exit

Cause: The Pipe driver failed to send ORAPOP the command to exit.

Action: Contact Oracle Support Services.


ORA-02738 osnpwrtbrkmsg: incorrect number of bytes written

Cause: The pipe driver apparently sent an incomplete break message.

Action: Contact Oracle Support Services.


ORA-02739 osncon: host alias is too long

Cause: The alias used for a SQLNET host is longer than 161 characters.

Action: Use a shorter alias.


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.

Action: Check the permissions on the directory ?/dbs.


ORA-02751 osnfsmmap: cannot map shared memory file

Cause: The Fast driver failed to map a shared memory file for two-task communication.

Action: Contact Oracle Support Services.


ORA-02752 osnfsmmap: illegal shared memory address

Cause: The Fast driver failed to attach shared memory at the expected location.

Action: Contact Oracle Support Services.


ORA-02753 osnfsmmap: cannot close shared memory file

Cause: The Fast driver cannot close the shared memory file.

Action: Contact Oracle Support Services.


ORA-02754 osnfsmmap: cannot change shared memory inheritence

Cause: The Fast driver could not alter the inheritance attributes of the shared memory.

Action: Contact Oracle Support Services.


ORA-02755 osnfsmcre: cannot create chared memory file ?/dbs/ftt_pid.dbf

Cause: The Fast driver failed to create a file for shared memory.

Action: Check the permissions on the directory ?/dbs.


ORA-02756 osnfsmnam: name translation failure

Cause: The Fast driver encountered an error translating the shared memory file name ?/dbs/ftt_pid.dbf.

Action: Contact Oracle Support Services.


ORA-02757 osnfop: fork_and_bind failed

Cause: The Fast driver failed to fork a process onto the desired cluster and node number.

Action: Check the desired node number in sercose[0] and cluster ID in sercose[1]. If these seem valid, contact Oracle Support Services.


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.

Action: Either reclaim memory by killing other processes or restart the machine with more memory.


ORA-02759 Not enough request descriptors available

Cause: All of the package's request descriptors are in use performing other requests.

Action: Either wait until enough requests are done, or shut the package down and re-initialize it with more request descriptors.


ORA-02760 Client close of file failed.

Cause: The client was unable to close a file after forking the servers.

Action: This is a system problem; contact your System Administrator.


ORA-02761 File number to be canceled is negative.

Cause: The file number contained with the SFIOV structure is less than zero.

Action: This may be a programming error. If it is not, contact Oracle Support Services.


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.

Action: This may be a programming error. If it is not, contact Oracle Support Services.


ORA-02763 Unable to cancel at least one request

Cause: No requests were found that could be cancelled.

Action: This error can occur if all the requests dealing with that file number have already been filled.


ORA-02764 Invalid package mode

Cause: The mode of the package can only be parallel or duplex.

Action: See SFA.H for the correct values.


ORA-02765 Invalid maximum number of servers

Cause: The number of servers given was less than or equal to zero.

Action: Use a number greater than zero.


ORA-02766 Invalid maximum of request descriptors

Cause: The number of request descriptors was less than or equal to zero.

Action: Use a number greater than 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.

Action: Use a higher number


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.

Action: Use a positive number.


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.

Action: Contact Oracle Support Services.


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.

Action: Use a positive number.


ORA-02771 Illegal request time out value

Cause: The number was not a positive number.

Action: Use a positive number.


ORA-02772 Invalid maximum server idle time

Cause: The time given was not a positive number.

Action: Use a positive number.


ORA-02773 Invalid maximum client wait time

Cause: The time given was not a positive number.

Action: Use a positive number.


ORA-02774 Invalid request list latch time out value

Cause: The time given was not a positive number.

Action: Use a positive number.


ORA-02775 Invalid request done signal

Cause: The signal number was not a positive number.

Action: Use 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.

Action: Contact your system administrator.


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.

Action: Check the permissions on the directory or use a different directory name.


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.

Action: Use a different name.


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.

Action: Check the permissions on the directory or use a different directory name.


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.

Action: Use a different name.


ORA-02781 Invalid value given for the timing wanted flag

Cause: The value given was not TRUE or FALSE.

Action: Specify TRUE or FALSE for the timing wanted flag.


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.

Action: Either specify both functions or specify neither. The package will supply its own functions.


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.

Action: Either specify both functions or specify neither. The package will supply its own functions.


ORA-02784 Invalid shared memory ID specified

Cause: The ID of the segment specified for use as the shared buffer region was invalid.

Action: Use a different ID, or let the package specify its own.


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.

Action: Use a positive number.


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.

Action: Use a larger size segment or let the package allocate its own.


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.

Action: Close some processes or contact your system administrator.


ORA-02788 Unable to find kernel process pointer in async process array

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02789 Maximum number of files reached

Cause: The maximum number of files that can be used for asynchronous I/O has been reached.

Action: Shut down the servers and re-initialize the package with a higher number.


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.

Action: Use a shorter name.


ORA-02791 Unable to open file for use with asynchronous I/O

Cause: The package could not open file for some reason.

Action: Check the file name.


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.

Action: Check the file name.


ORA-02793 Close of asynchronous I/O failed.

Cause: The client was unable to close a file being used for asynchronous I/O.

Action: Contact Oracle Support Services.


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. This is an internal error.

Action: Contact Oracle Support Services.


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. This is an internal error.

Action: Contact Oracle Support Services.


ORA-02796 Done request is not in correct state

Cause: A request is not in the right state. This is an internal error.

Action: Contact Oracle Support Services.


ORA-02797 No requests available

Cause: No free request descriptors are available.

Action: Wait until some requests are filled and then retry the request, or shut down the servers and initialize the package with a higher number of requests.


ORA-02798 Invalid number of requests

Cause: The number of operations sent to either SFARD() or SFAWRITE() is less than zero. This is a user programming error.

Action: Check the calling program.


ORA-02799 Unable to arm signal handler

Cause: The arming of a signal handler for the "done" signal failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-02800 Requests timed out

Cause: Some of the requests for asynchronous input or output were not serviced in the required amount of time.

Action: If the load on the system is high, it is possible that the timeout limit is too low. Reset it with SFAINIT(). If the server processes are dying due to unexpected signals, this is an internal error, and Oracle Support Services should be contacted.


ORA-02801 Operations timed out

Cause: Some asynchronous operations timed out in kernel mode. This is an internal error.

Action: Contact Oracle Support Services.


ORA-02802 No idle servers available in parallel mode

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02803 Retrieval of current time failed

Cause: This is an internal error.

Action: Contact Oracle Support Services.


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.

Action: Contact your system administrator.


ORA-02805 Unable to set handler for SIGTPA

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02806 Unable to set handler for SIGALRM

Cause: This is an internal error.

Action: Contact Oracle Support Services.


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.

Action: Contact your system administrator.


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.

Action: Contact your system administrator.


ORA-02809 Jump buffer not valid

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02810 Unable to make temporary file name for memory mapped file

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02811 Unable to attach shared memory segment

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02812 Bad attach address

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02813 Unable to make temporary file name in order to get key

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02814 Unable to get shared memory

Cause: SHMGET(2) failed.

Action: Check the UNIX number. If you are unsure about what it means, contact Oracle Support Services.


ORA-02815 Unable to attach shared memory

Cause: SHMAT(2) failed.

Action: Check the UNIX number. If you are unsure about what it means, contact Oracle Support Services.


ORA-02816 Unable to kill a process

Cause: A server did not die after being sent a kill signal.

Action: The process may be a runaway; contact Oracle Support Services.


ORA-02817 Read failed

Cause: A server could not read a requested amount of data.

Action: Check the call to SFARD(). An incorrect file descriptor may have been sent to SFARD(). The number in the "additional information" field is the starting block number of the data segment being read in.


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. This is a programming error.

Action: Check the calling program.


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.

Action: Check the UNIX error number.


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.

Action: Check the UNIX error number.


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.

Action: Check the file on disk.


ORA-02822 Invalid block offset

Cause: A server was unable to seek to the designated block.

Action: Check the UNIX error number.


ORA-02823 Buffer is not aligned.

Cause: The buffer on which an I/O is being done is not on the correct boundary.

Action: Check the calling program.


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.

Action: Wait until some become free, or initialize the package with a higher number of request descriptors.


ORA-02825 Request on free list was not free

Cause: This is an internal error.

Action: Contact Oracle Support Services.


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. This is a programming error.

Action: Use either a positive number or zero to get the default value.


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.

Action: Since the calling program should not touch this number, this is a programming error.


ORA-02828 Segment free list is empty

Cause: No segments are available to allocated.

Action: Free some segments or shut down the package and re-initialize it with a higher number of segments.


ORA-02829 No segment of the proper size is available

Cause: No segment of the proper size is ready for use by the caller.

Action: Free some segments and try again.


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.

Action: Free some segments and try again.


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.

Action: Check the calling program.


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.

Action: Check the calling program.


ORA-02833 Server was unable to close file

Cause: A server was unable to close a file being used for asynchronous I/O.

Action: See the UNIX error number for more information.


ORA-02834 Server unable to open file

Cause: The server was unable to open a file for use with asynchronous I/O.

Action: Check the UNIX error number for more information.


ORA-02835 Server unable to send signal to client

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02836 Unable to create temporary key file

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02837 Unable to unlink temporary file

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02838 Unable to arm signal handler for the alarm signal

Cause: The arming of a signal handler for the alarm signal failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-02839 Sync of blocks to disk failed.

Cause: The server was unable to flush its writes out to disk.

Action: Check the UNIX error number.


ORA-02840 Open of log file by client failed

Cause: The client process was unable to open its log file.

Action: Check the UNIX error number for more information.


ORA-02841 Server died on start up

Cause: A server exited during its initialization process.

Action: Check the servers' logs for more information.


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.

Action: Either reduce the number of servers that are to be used, or reconfigure the operating system so that it can handle more processes.


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. This is a programming error.

Action: Check the calling routine.


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. This is a programming error.

Action: Check the calling routine.


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. This is a programming error.

Action: Check the calling routine.


ORA-02846 Unkillable server

Cause: A server failed to 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.

Action: Contact Oracle Support Services.


ORA-02847 Server did not terminate when posted

Cause: A server did not respond to a posted request to shut down. The first number is the number of the server. The second is its UNIX process number. This is an internal problem.

Action: Contact Oracle Support Services.


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().

Action: Call SFAINIT() before using the package.


ORA-02849 Read failed because of an error

Cause: A server could not read the requested amount of data from disk.

Action: Check the UNIX error number.


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. This is a programming error.

Action: Check the calling program.


ORA-02851 Request list is empty when it should not be

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-02852 Invalid critical-section time out value

Cause: The time given was not a positive number.

Action: Use a positive number.


ORA-02853 Invalid server list latch time out value

Cause: The time given was not a positive number.

Action: Use 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.

Action: Use a number that is greater than or equal to 0.


ORA-02855 Number of requests is less than the number of slaves

Cause: The value given for DB_SLAVE_BUFFERS in your INIT.ORA file is less than the number specified for the number of slaves, DB_SLAVES.

Action: Specify a number that is greater than that given for DB_SLAVES Alternatively, specify 0. The kernel will supply the appropriate number.


ORA-02875 smpini: Unable to get shared memory for PGA

Cause: Stated in error code (errno).

Action: Resolve the problem.


ORA-02876 smpini: Unable to attach to shared memory for PGA

Cause: Stated in error code (errno).

Action: Resolve the problem.


ORA-02877 smpini: Unable to initialize memory protection

Cause: The ADSPCINIT program has not been executed.

Action: Execute the ADSCPINIT program as shown in your Installation and Users' Guide. If the problem persists, try restarting your computer.


ORA-02878 sou2o: Variable smpdidini overwritten

Cause: The variable SMPDIDINI was overwritten, probably by client code.

Action: Verify client code (for example, in Pro*C check for illegal memory access). If the problem occurs outside Single Task operation, contact Oracle Support Services.


ORA-02879 sou2o: Could not gain access to protected memory

Cause: This is an internal error, note error code in errno.

Action: Restarting your application or your computer may cure the problem. If not, report the error to Oracle Support Services.


ORA-02880 smpini: Could not register PGA for protection

Cause: This is an internal error, note error code in errno.

Action: Restarting your application or your computer may cure the problem. If not, report the error to Oracle Support Services.


ORA-02881 sou2o: Could not revoke access to protected memory

Cause: This is an internal error, note error code in errno.

Action: Restarting your application or your computer may cure the problem. If not, report the error to Oracle Support Services.


ORA-02882 sou2o: Could not register SGA for protection

Cause: This is an internal error, note error code in errno.

Action: Restarting your application or your computer may cure the problem. If not, report the error to Oracle Support Services.


ORA-02899 smscre: Cannot create SGA with Extended Shared Memory feature

Cause: The environment variable EXTSHM was set before starting Oracle.

Action: Unset the environment variable EXTSHM and restart Oracle.


ORA-03001 unimplemented feature

Cause: At attempt was made to use a feature that is not currently implemented.

Action: Do not attempt to use this feature at this time.


ORA-03002 operator not implemented

Cause: At attempt was made to use an operator that is not currently implemented.

Action: Do not attempt to use this operator at this time.


ORA-03007 obsolete feature

Cause: An attempt was made to use a feature that is no longer supported.

Action: No action required.


ORA-03008 parameter COMPATIBLE >= string needed for string

Cause: An attempt was made to use a feature for a later Oracle version than the setting of the initialization parameter, COMPATIBLE.

Action: Set COMPATIBLE to the value in the message (or higher), and retry the command, but be aware that this will limit your downgrade options.


ORA-03100 communication area cannot be allocated; insufficient memory

Cause: An attempt to allocate stack space for communication purposes failed. This is an internal error message not usually issued.

Action: Contact Oracle Support Services.


ORA-03105 internal protocol error

ORA-03106 fatal two-task communication protocol error

Cause: The communication path between Oracle and the user task has stopped. This is an internal error message not usually issued.

Action: Contact Oracle Support Services.


ORA-03107 oranet buffer underflow

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.


ORA-03108 oranet: ORACLE does not support this interface version

Cause: The version of Oracle connected to via Net8 does not support this version of the Net8 protocol.

Action: Upgrade the older version of Oracle and try again.


ORA-03109 oranet buffer overflow

Cause: Data being transferred between the user program and Oracle overflowed the buffer space available. This is an internal error message not usually issued.

Action: Contact Oracle Support Services.


ORA-03110 oranet: ORACLE does not support this SQL version

Cause: The version of Oracle connected to via Net8 does not support the version of the Net8 protocol.

Action: Upgrade the older version of Oracle and try again.


ORA-03111 break received on communication channel

Cause: A break was processed on the communications channel, but was not properly handled by Net8 software. This is an internal error message not usually issued.

Action: Contact Oracle Support Services.


ORA-03112 a server linked as single-task cannot use SQL*Net

Cause: A statement containing a Net8t connect string was issued to the single-task server. For example, a database link was used in a SQL statement.

Action: Do not use Net8t connect strings in a single-task environment.


ORA-03113 end-of-file on communication channel

Cause: An unexpected end-of-file was processed on the communication channel. The problem could not be handled by the Net8 two-task software. This message could occur if the shadow two-task process associated with a Net8 connect has terminated abnormally, or if there is a physical failure of the interprocess communication vehicle, that is, the network or server machine went down.

In addition, this message could occur when any of the following statements/commands have been issued:

  • ALTER SYSTEM KILL SESSION ... IMMEDIATE
  • ALTER SYSTEM DISCONNECT SESSION ... IMMEDIATE
  • SHUTDOWN ABORT/IMMEDIATE/TRANSACTIONAL

Action: If this message occurs during a connection attempt, check the setup files for the appropriate Net8 driver and confirm Net8 software is correctly installed on the server. If the message occurs after a connection is well established, and the error is not due to a physical failure, check if a trace file was generated on the server at failure time. Existence of a trace file may suggest an Oracle internal error that requires the assistance of Oracle Support Services.


ORA-03114 not connected to ORACLE

Cause: A call to Oracle was attempted when no connection was established. Usually this happens because a user-written program has not logged on. It may happen if communication trouble causes a disconnection. In addition, this message could occur when ALTER SYSTEM KILL SESSION or ALTER SYSTEM DISCONNECT SESSION were issued with the IMMEDIATE qualifier because, in those cases, the client's connection to the database is terminated without waiting for the client to issue a request.

Action: Try again. If the message recurs and the program is user written, check the program.


ORA-03115 unsupported network datatype or representation

Cause: A user bind or define, or an Oracle function, is not supported by this heterogeneous Net8 connection.

Action: Upgrade the older version of Oracle and try again.


ORA-03116 invalid buffer length passed to a conversion routine

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.


ORA-03117 two-task save area overflow

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.


ORA-03118 two-task coroutine has invalid state

Cause: This is an internal error message not usually issued.

Action: Contact Oracle Support Services.


ORA-03119 two-task detected inconsistent datatype specification

Cause: Found both a datatype, and an anonymous datatype, declaration.

Action: Correct the specification.


ORA-03120 two-task conversion routine: integer overflow

Cause: An integer value in an internal Oracle structure overflowed when being sent or received over a heterogeneous connection. This can happen when an invalid buffer length or too great a row count is specified. It usually indicates a bug in the user application.

Action: Check parameters to Oracle calls. If the problem recurs, reduce all integer parameters, column values not included, to less than 32767.


ORA-03121 no interface driver connected - function not performed

Cause: This message occurs usually because the Net8 driver is not loaded into memory or there is a mismatch of the version of the driver. A user program linked with an obsolete library may also cause this message. Only programs provided by Oracle Corporation should use this interface.

Action: If the message occurred during use of a program provided by Oracle Corporation, contact Oracle Support Services. If a user program caused the message, relink the program with current versions of the Oracle libraries.


ORA-03122 attempt to close ORACLE-side window on user side

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-03123 operation would block

Cause: The attempted operation cannot complete now.

Action: Retry the operation later.


ORA-03124 two-task internal error

Cause: This is an internal error.

Action: Contact Oracle Support Services.


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.

Action: Contact Oracle Support Services.


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.

Action: Use default blocking operations or use a driver supporting 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.

Action: Execute the new operation after the non-blocking operation completes. If piecewise binds/defines were done, execute the new operation after all the pieces have been 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.

Action: If non-blocking mode is required use appropriate OCI calls to change the mode.


ORA-03129 the next piece to be inserted is required

Cause: The application performed a piecewise bind on a column.

Action: Provide the next piece of this bind variable.


ORA-03130 the buffer for the next piece to be fetched is required

Cause: The application performed a piecewise define on the column.

Action: Provide the next buffer for the next piece to be retrieved.


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.

Action: Verify if the buffer pointer for the next piece is null or if the length is zero.


ORA-03132 two-task default value overflow

Cause: The default value specified for a record field was too large.

Action: Change the default value to fit the field size.


ORA-03200 the segment type specification is invalid

Cause: The segment type is not TABLE, INDEX, or CLUSTER.

Action: Use a correct segment type.


ORA-03201 the group number specification is invalid

Cause: The freelist group number is either negative or larger than the number of freelist groups in the segment.

Action: Use a correct group number.


ORA-03202 the scan limit specification is invalid

Cause: The scan limit does not have a positive integer value greater than the number of freelist groups in the segment.

Action: Use a correct scan limit.


ORA-03203 concurrent update activity makes space analysis impossible

Cause: High volume of user updates interfere with the space analysis.

Action: Retry the command or lock the underlying objects.


ORA-03204 the segment type specification should indicate partitioning

Cause: A partition name was specified for the space analysis, but the object type does not indicate partitioning.

Action: Specify PARTITION in the segment type if the object is partitioned, Otherwise, omit the partition name.


ORA-03205 partition name is required when partitioned type is specified

Cause: A partition name was not specified for the space analysis, but the object type indicates partitioning.

Action: Specify a partition name if the object is partitioned. Otherwise, specify a non-partitioned type.


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.

Action: Reduce the size and retry.


ORA-03207 subpartitioned type must be specified for composite object

Cause: A partition type is specified for the space analysis, but the object type indicates composite partitioning.

Action: Specify a subpartition name and a subpartition type.


ORA-03208 partitioned type must be specified for a non-composite object

Cause: A subpartition type is specified for the space analysis, but the object type indicates non-composite partitioning.

Action: Specify a partition name and a partition type.


ORA-03209 DBMS_ADMIN_PACKAGE invalid file/block specification

Cause: The value of file number or block number is outside of limits or inconsistent.

Action: Fix the file number/block number value.


ORA-03210 DBMS_ADMIN_PACKAGE invalid option specification

Cause: The value of one of the option parameters is incorrect.

Action: Fix the option value.


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.

Action: Fix the segment specification, or put the segment in the appropriate state.


ORA-03212 Temporary Segment cannot be created in locally-managed tablespace

Cause: An attempt was made to create a temporary segment for SORT/HASH/LOBS in a locally-managed permanent tablespace.

Action: Alter temporary tablespace of user to a temporary tablespace or a dictionary-managed permanent tablespace.


ORA-03213 Invalid Lob Segment Name for DBMS_SPACE package

Cause: The LOB segment specified in the DBMS_SPACE operation does not exist.

Action: Fix the segment specification.


ORA-03214 File Size specified is smaller than minimum required

Cause: File size specified for add/resize datafile/temporary file does not allow for the minimum required of one allocation unit.

Action: Increase the specification for the file size.


ORA-03215 File Size specified for resize is too small

Cause: File size specified for resize datafile/temporary file causes bitmap control structures to overlap.

Action: Increase the specification for the file size.


ORA-03216 Tablespace/Segment Verification cannot proceed

Cause: Corruption was detected during verification which cannot be dealt with

Action: Do manual verification.


ORA-03217 invalid option for alter of TEMPORARY TABLESPACE

Cause: Invalid option for alter of temporary tablespace was specified.

Action: Specify one of the valid options: ADD TEMPFILE, TEMPFILE ONLINE, TEMPFILE OFFLINE.


ORA-03218 invalid option for CREATE/ALTER TABLESPACE

Cause: Invalid option for create/alter tablespace of type locally-managed.

Action: Specify one of the valid options.


ORA-03219 Tablespace 'string' is dictionary managed, offline, or temporary.

Cause: An operation which is only applicable to permanent, online, locally managed tablespaces is specified for a tablespace that is either dictionary managed, offline, or temporary.

Action: Reissue the operation for a different tablespace, mount the tablespace, or do not issue it at all since it does not apply for the given tablespace.


ORA-03220 DBMS_ADMIN_PACKAGE required parameter is NULL or missing

Cause: Some of the procedures were called with missing or NULL parameters.

Action: Specify the missing parameter.


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
  2. Alter an existing permanent tablespace of non-standard block size to a temporary tablespace
  3. Issue a DDL statement that would result in the creation of a temporary segment in a tablespace of non-standard block size

Action: There are three possible solutions:

If creating a temporary tablespace, do not specify a block size different from the standard block size.
  1. If altering an existing permanent tablespace to a temporary tablespace, ensure that it is of standard block size.
  2. Ensure that the user's temporary tablespace is a tablespace having the standard block size.

ORA-03230 segment only contains string blocks of unused space above high water mark

Cause: Attempt to preserve too many blocks.

Action: Reduce the KEEP amount.


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.

Action: Increase the KEEP amount, or truncate the segment, and reissue the command.


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.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.


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.

Action: Use ALTER TABLESPACE ADD DATAFILE statement to add one or more files to the tablespace indicated.


ORA-03235 max # extents (string) reached in table string.string subpartition string

Cause: A table subpartition tried to extend past MAXEXTENTS.

Action: If the value of MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.


ORA-03236 max # extents (string) reached in index string.string subpartition string

Cause: An index subpartition tried to extend past MAXEXTENTS.

Action: If the value of MAXEXTENTS is less than the system maximum, raise it. Otherwise, you must re-create with larger initial, next or PCTINCREASE parameters.


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.

Action: Reduce number of freelist groups specified for the segment.


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.

Action: Use the ALTER TABLESPACE ADD DATAFILE statement to add one or more files to 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.

Action: If the value of MAXEXTENTS is less than the system maximum, raise it. Otherwise, re-create the subpartition with larger INITIAL, NEXT, or PCTINCREASE parameters.


ORA-03240 User's temporary tablespace same as tablespace being migrated

Cause: Users default temporary tablespace must be different from the tablespace being migrated.

Action: alter users default temporary tablespace to be different.


ORA-03241 Invalid unit size

Cause: User specified an invalid unit size for the tablespace.

Action: Specify the correct unit size. To estimate unit size, refer to the Oracle9i Database Administrator's Guide.


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.

Action: Avoid migrating the tablespace when there is heavy temporary segment creation going on as with object drops.


ORA-03243 destination dba overlaps with existing control information

Cause: Cannot overlap control information during relocation.

Action: Choose another destination address.


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.

Action: If during migration, add more space to the tablespace and retry migration. If during bitmaps relocation, specify a destination address where there is enough free space.


ORA-03245 Tablespace has to be dictionary managed, online and permanent to be able to migrate

Cause: Tablespace was not dictionary managed, online, or permanent.

Action: Make sure the tablespace is online, permanent, or dictionary managed.


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.

Action: specify a correct block number.


ORA-03247 Invalid block number specified

Cause: Relocation of bitmaps to the said destination will make the tablespace self descriptive.

Action: Choose another destination DBA.


ORA-03248 Too much of segment creation activity during migration

Cause: Temporary segments were attempted to be created during migration.

Action: The error is signalled after retrying migration for 500 times. Run migration when there is less segment creation activity going on.


ORA-03249 Uniform size for auto segment space managed tablespace should have atleast string blocks.

Cause: For the given blocksize, the specified uniform size is insufficient.

Action: Specify a larger extent size and retry.


ORA-03250 Cannot mark this segment corrupt

Cause: This segment cannot be marked corrupt because it contains data dictionary objects.

Action: Check the segment information and re-issue the command.


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.

Action: Check the tablespace name and procedure name.


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.

Action: Choose one of the options or issue two separate commands.


ORA-03275 duplicate DEALLOCATE option specification

Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is specified more than once.

Action: Specify the option at most once.


ORA-03276 duplicate ALLOCATE EXTENT option specification

Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once.

Action: Specify the option at most once.


ORA-03277 invalid SIZE specified

Cause: The specified value must be an integer.

Action: Choose an appropriate integer value.


ORA-03278 duplicate ALLOCATE EXTENT option specification

Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more than once.

Action: Specify each option at most once.


ORA-03279 invalid INSTANCE specified

Cause: The specified value is not recognized as a valid instance name.

Action: Use a valid name.


ORA-03280 invalid DATAFILE filename specified

Cause: A character string literal is expected, but not found.

Action: Specify file names using character string literals.


ORA-03281 invalid ALLOCATE EXTENT option

Cause: An option other than DATAFILE, SIZE or INSTANCE was specified.

Action: Remove invalid option and retry the command.


ORA-03282 missing ALLOCATE EXTENT option

Cause: No ALLOCATE EXTENT options were specified.

Action: Specified one or more of the following options: DATAFILE, SIZE or INSTANCE.


ORA-03283 specified datafile string does not exist

Cause: The datafile does not exist.

Action: Retry the option with the correct datafile.


ORA-03284 datafile string is not a member of tablespace string

Cause: The specified datafile does not belong to the tablespace that the object resides in.

Action: Retry the option with the correct datafile.


ORA-03286 ALLOCATE EXTENT not valid for HASH CLUSTERS

Cause: The cluster cannot use the allocate extent option because it is a hash cluster.

Action: Do not use this command on a hash cluster.


ORA-03287 invalid FREELIST GROUP specified

Cause: The specified FREELIST GROUP number is invalid.

Action: Choose a number between 1 and the number of freelist groups for this object.


ORA-03288 both FREELIST GROUP and INSTANCE parameters may not be specified

Cause: Both FREELIST GROUP and INSTANCE were specified in clause.

Action: Remove one of the two parameters.


ORA-03289 partition name and segment type do not match

Cause: Partition name and segment type specified for space analysis do not match.

Action: Specify type PARTITION if the object is partitioned, specify SUBPARTITION if the object is composite.


ORA-03290 Invalid truncate command - missing CLUSTER or TABLE keyword

Cause: Invalid object specification given.

Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE.


ORA-03291 Invalid truncate option - missing STORAGE keyword

Cause: Expected STORAGE keyword.

Action: Either specify DROP STORAGE or REUSE STORAGE.


ORA-03292 Table to be truncated is part of a cluster

Cause: The table being truncated is a member of a cluster.

Action: Either use TRUNCATE CLUSTER or DROP TABLE.


ORA-03293 Cluster to be truncated is a HASH CLUSTER

Cause: Only INDEX CLUSTERS can be truncated.

Action: Drop and re-create the HASH CLUSTER instead of using truncate.


ORA-03296 cannot resize datafile - file string not found

Cause: The specified datafile is not available for resizing.

Action: Ensure that the datafile name is valid, and if so, ensure the file is accessible.


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.

Action: Drop or move segments containing extents in this region prior to resizing the file, or choose a resize value such that only free space is in the trimmed.


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.

Action: Retry shrinking the file after the hot backup completes.


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.

Action: See action for next error message in error stack.


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.

Action: Create the table/cluster specifying values whose sum is less than or equal to 100.


ORA-04001 sequence parameter string must be an integer

Cause: string (a sequence parameter) specified was not an integer.

Action: Create the sequence, giving the specified parameter an integer value.


ORA-04002 INCREMENT must be a non-zero integer

Cause: A sequence increment was specified to be zero.

Action: Specify the increment to be a non-zero value.


ORA-04003 sequence parameter string exceeds maximum size allowed (string digits)

Cause: string (a sequencer parameter) had too many digits.

Action: Specify the parameter with the allowed number of digits.


ORA-04004 MINVALUE must be less than MAXVALUE

Cause: MINVALUE was specified to be greater than or equal to MAXVALUE.

Action: Specify a MINVALUE that is less than MAXVALUE.


ORA-04005 INCREMENT must be less than MAXVALUE minus MINVALUE

Cause: The INCREMENT specified is greater than or equal to MAXVALUE-MINVALUE.

Action: Specify an INCREMENT that is less than MAXVALUE-MINVALUE.


ORA-04006 START WITH cannot be less than MINVALUE

Cause: The given starting value is less than MINVALUE.

Action: Make sure that the starting value is greater than or equal to MINVALUE.


ORA-04007 MINVALUE cannot be made to exceed the current value

Cause: The given MINVALUE would be greater than the current value.

Action: Always make sure that MINVALUE is less than or equal to the current value.


ORA-04008 START WITH cannot be more than MAXVALUE

Cause: The starting value would be larger than MAXVALUE.

Action: Make sure that the starting value is less than MAXVALUE.


ORA-04009 MAXVALUE cannot be made to be less than the current value

Cause: The current value exceeds the given MAXVALUE.

Action: Make sure that the new MAXVALUE is larger than the current value.


ORA-04010 the number of values to CACHE must be greater than 1

Cause: The value in the CACHE clause was one.

Action: Specify NOCACHE, or a value larger than one.


ORA-04011 sequence string must range between string and string

Cause: The value specified for one of the sequence parameters exceeds limits.

Action: Specify a parameter within these limits.


ORA-04012 object is not a sequence

Cause: The object specified cannot have sequence DDLs performed on it.

Action: Re-enter the statement being careful with the spelling of the name.


ORA-04013 number to CACHE must be less than one cycle

Cause: The number to CACHE specified in a CREATE SEQUENCE statement exceeds the number of values in a cycle.

Action: Enlarge the cycle or cache fewer values, and try again.


ORA-04014 descending sequences that CYCLE must specify MINVALUE

Cause: A value was not specified in the CREATE SEQUENCE statement. Sequences that cycle must specify a value at which to begin again.

Action: Re-create the sequence, specifying the value at which it is to begin.


ORA-04015 ascending sequences that CYCLE must specify MAXVALUE

Cause: A value was not specified in the CREATE SEQUENCE statement. Sequences that cycle must specify a value at which to begin again.

Action: Recreate the sequence, specifying the value at which it is to begin.


ORA-04016 sequence string no longer exists

Cause: Sequence was dropped while processing its next value.

Action: Re-create the sequence.


ORA-04017 invalid value string (length = string) for parameter max_dump_file_ size

Cause: Neither did the string supplied for MAX_DUMP_FILE_SIZE parameter match the "UNLIMITED" string value nor did it represent a base 10 integer.

Action: Reassign a proper value to this parameter.


ORA-04018 invalid value string for parameter _scn_scheme

Cause: The value specified for initialization parameter _SCN_SCHEME is not recognized as one of the defined schemes.

Action: Reassign a proper value.


ORA-04019 SCN scheme incompatible with other instances

Cause: Either different instances are running incompatible Oracle releases or different values have been assigned to the _SCN_SCHEME initialization parameter on different instances.

Action: Make sure the _SCN_SCHEME initialization parameter is set to the same value on all instances.


ORA-04020 deadlock detected while trying to lock object stringstringstringstringstring

Cause: While trying to lock a library object, a deadlock is detected.

Action: Retry the operation later.


ORA-04021 timeout occurred while waiting to lock object stringstringstringstringstring

Cause: While waiting to lock a library object, a timeout is occurred.

Action: Retry the operation later.


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.

Action: Retry the operation later.


ORA-04028 cannot generate diana for object stringstringstringstringstring

Cause: Cannot generate diana for an object because of lock conflict.

Action: Report this error to your support representative.


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.

Action: Fix the error.


ORA-04030 out of process memory when trying to allocate string bytes (string,string)

Cause: Operating system process private memory has been exhausted.

Action: See the database administrator or operating system administrator to increase process memory quota. There may be a bug in the application that causes excessive allocations of process memory space.


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.

Action: If the shared pool is out of memory, either use the DBMS_SHARED_ POOL package to pin large packages, reduce your use of shared memory, or increase the amount of available shared memory by increasing the value of the initialization parameters SHARED_POOL_RESERVED_SIZE and SHARED_ POOL_SIZE. If the large pool is out of memory, increase the initialization parameter LARGE_POOL_SIZE.


ORA-04032 pga_aggregate_target must be set before switching to auto mode

Cause: An attempt was made to set WORKAREA_SIZE_POLICY to AUTO while PGA_AGGREGATE_TARGET is not specified.

Action: Before setting WORKAREA_SIZE_POLICY, set PGA_AGGREGATE_TARGET to a value representing the total private memory available to the instance. This total is generally the total physical memory available in the system minus what is needed for the SGA minus what is needed for the operating system (for example, such as 500 MB).


ORA-04033 insufficient memory to grow pool

Cause: The system had insufficient memory to grow the pool to the specified size.

Action: Specify a smaller value to grow the pool.


ORA-04041 package specification must be created first before creating package body

Cause: Attempt to create a package body before creating its package specification.

Action: Create the package specification first before creating the package body.


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.

Action: Make sure the name is correct.


ORA-04043 object string does not exist

Cause: An object name was specified that was not recognized by the system. Following are 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.

Action: Check the spelling of the named object and rerun the code. (Valid names of tables, views, functions, etc. can be listed by querying the data dictionary.)


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.

Action: Make sure the name is correct or remove it.


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.

Action: Check the following errors for more information, and make the necessary corrections to 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.

Action: Reduce the size of the store procedure by splitting it into smaller stored procedures.


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.

Action: Specify the correct object, or use the appropriate flag.


ORA-04050 invalid or missing procedure, function, or package name

Cause: The required procedure, function, or package name is invalid or missing.

Action: Specify a valid name.


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.

Action: Change your database link structure so that all indirect remote accesses are done from the same userid that originates the request.


ORA-04052 error occurred when looking up remote object stringstringstringstringstring

Cause: An error has occurred when trying to look up a remote object.

Action: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying/looking up objects stored in the database.


ORA-04053 error occurred when validating remote object stringstringstringstringstring

Cause: An error has occurred when trying to validate a remote object.

Action: Fix the error. Make sure the remote database system has run KGLR.SQL to create necessary views used for querying/looking up objects stored in the database.


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.

Action: Either use a different database link or create the 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);

Action: Break the cycle (possibly by adding a REF or by using another type).


ORA-04060 insufficient privileges to execute string

Cause: Attempt to execute a stored procedure without sufficient privileges.

Action: Get necessary 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.

Action: Try again; this error should have caused the existing state of all packages to be re-initialized.


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.

Action: Recompile the caller in order to pick up the new timestamp.


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.

Action: Fix the errors and/or create referenced objects as necessary.


ORA-04064 not executed, invalidated string

Cause: Attempt to execute a stored procedure that has been invalidated.

Action: Recompile the stored procedure.


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.

Action: Recompile its dependents.


ORA-04066 non-executable object, string

Cause: Attempt to execute a non-procedure.

Action: Make sure that a correct name is given.


ORA-04067 not executed, string does not exist

Cause: Attempt to execute a non-existent stored procedure.

Action: Make sure that a correct name is given.


ORA-04068 existing state of packagesstringstringstring has been discarded

Cause: An error occurred when attempting to execute a stored procedure.

Action: Refer to the accompanying messages and fix the error mentioned. Try the procedure again after proper reinitialization of any application's state.


ORA-04070 invalid trigger name

Cause: An invalid trigger name was specified.

Action: Verify that trigger name is not a reserved keyword.


ORA-04071 missing BEFORE, AFTER or INSTEAD OF keyword

Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause.

Action: Specify either BEFORE, AFTER or INSTEAD OF.


ORA-04072 invalid trigger type

Cause: An invalid trigger type was given.

Action: Specify either INSERT, UPDATE or DELETE.


ORA-04073 column list not valid for this trigger type

Cause: A column list was specified for a non-update trigger type.

Action: Remove the column list.


ORA-04074 invalid REFERENCING name

Cause: An invalid name was given in the referencing clause.

Action: Verify the referencing name is not a reserved word.


ORA-04075 invalid trigger action

Cause: An statement was given for the trigger action.

Action: Re-specify the trigger action.


ORA-04076 invalid NEW or OLD specification

Cause: An invalid NEW or OLD specification was given for a column.

Action: Re-specify the column using the correct NEW or OLD specification.


ORA-04077 WHEN clause cannot be used with table level triggers

Cause: The when clause can only be specified for row level triggers.

Action: Remove the when clause or specify for each row.


ORA-04078 OLD and NEW values cannot be identical

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

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


ORA-04079 invalid trigger specification

Cause: The create TRIGGER statement is invalid.

Action: Check the statement for correct syntax.


ORA-04080 trigger 'string' does not exist

Cause: The TRIGGER name is invalid.

Action: Check the trigger name.


ORA-04081 trigger 'string' already exists

Cause: The TRIGGER name or type already exists.

Action: Use a different trigger name or drop the trigger which is of the same name.


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.

Action: Remove any new or old references.


ORA-04083 invalid trigger variable 'string'

Cause: The variable referenced in the trigger body is invalid.

Action: See the Oracle9i SQL Reference for valid trigger variable types.


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.

Action: Change the trigger type or remove the variable reference.


ORA-04085 cannot change the value of an OLD reference variable

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

Action: Do not attempt to change an old variable.


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.

Action: If the trigger description contains a large comment, move that comment into the PL/SQL code for the trigger.


ORA-04087 cannot change the value of ROWID reference variable

Cause: ROWIDs can only be read and not changed.

Action: Do not attempt to change an ROWID value.


ORA-04088 error during execution of trigger 'string.string'

Cause: A runtime error occurred during execution of a trigger.

Action: Check the triggers which were involved in the operation.


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.

Action: Do not create triggers on objects owned by SYS.


ORA-04090 'string' specifies same table, event and trigger time as 'string'

Cause: Trigger is of duplicate event and trigger time.

Action: Combine the triggering information into one trigger which is fired at the given time.


ORA-04091 table string.string is mutating, trigger/function may not see it

Cause: A trigger (or a user defined PL/SQL 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.

Action: Rewrite the trigger (or function) so it does not read that table.


ORA-04092 cannot string in a trigger

Cause: A trigger attempted to commit or roll back.

Action: Rewrite the trigger so it does not commit or roll back.


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.

Action: Do not reference the long column.


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.

Action: Rewrite the trigger so that it does not modify that table.


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.

Action: Drop the trigger with the same name and re-create it.


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.

Action: Use a smaller WHEN clause. Note, the trigger body could be used to perform the same limiting action as the WHEN clause.


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.

Action: Investigate the new state of the trigger and retry the DDL operation, if still appropriate.


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.

Action: Options are to resolve the compilation/authorization errors, disable the trigger, or drop 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.

Action: Alter compile the trigger to create the trigger in stored form. Also, you may want to review that a proper upgrade was done.

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)

Part Number A96525-01
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback

Go to previous page Go to next page

6
ORA-04100 to ORA-07499


ORA-04930 open sequence number failed or initial state is valid

Cause: Either Shared Sequence Number operating system component was not installed properly, or an MC hardware failure may have occurred or a previous instance was not shut down properly.

Action: Verify that there are no background or foreground Oracle processes from a previous instance on this node using the operating system command ps -ef | grep instance_name. Verify that there are no shared memory segments belonging to the user which owns the Oracle installation by issuing the ipcs -b operating system command. If there are shared memory segments or processes still on the system, use SVRMGRL to shut down the instance with the abort option. If the instance is not up, verify that the cluster software and/or the hardware is installed and working. Log in as superuser and issue the CNXSHOW command. Are all of the nodes in the cluster listed? Are they members of the cluster? Is the communications between nodes okay? If the answer to any of these questions is false, contact Digital's customer support organization.


ORA-04931 unable to set initial sequence number value

Cause: A call to the SSN failed to set the sequence number to its initial value, possibly caused by an MC hardware problem.

Action: Verify that the MC hardware is functioning properly. If it is not, contact Digital's customer support organization. If it is, contact Oracle Support Services.


ORA-04932 increment or adjust of sequence number failed

Cause: A call to the SSN failed to increment the sequence number.

Action: Verify that the MC hardware is functioning properly. If it is not, contact Digital's customer support organization. If it is, contact Oracle Support Services.


ORA-04933 initial service identifier is non-zero

Cause: A valid service identifier existed before the sequence number service was opened.

Action: Verify that the instance is completely shut down.


ORA-04934 unable to obtain the current sequence number

Cause: A call to the SSN failed to return its current value. Either there are many errors occurring on the MC hardware, or the sequence number has become invalid and cannot be validated.

Action: Verify that the MC hardware is functioning properly. If it is, contact Oracle Support Services.


ORA-04935 unable to get/convert SCN recovery lock

Cause: A process has timed out trying to get or convert the SCN recovery lock. Another process probably has the lock in EX or SHR mode, but is not releasing it.

Action: Contact Oracle Support Services.


ORA-04940 unsupported optimization of Oracle binary, check alert log for more info

Cause: ORACLE binary has been optimized with unsupported options or a required option has not been used.

Action: Check the documentation for a list of supported and required flags for the optimizing utility that you used to optimize ORACLE. Shutdown the instance, optimize ORACLE again with a supported combination of options, and restart the instance.


ORA-06000 NETASY: port open failure

Cause: Autologin unable to open port.

Action: Check log file for operating system-specific error code.


ORA-06001 NETASY: port set-up failure

Cause: Autologin unable to change port attributes.

Action: Check log file for operating system-specific error code.


ORA-06002 NETASY: port read failure

Cause: Autologin unable to read from port.

Action: Check log file for operating system-specific error code.


ORA-06003 NETASY: port write failure

Cause: Autologin unable to write to port.

Action: Check log file for operating system-specific error code.


ORA-06004 NETASY: dialogue file open failure

Cause: Autologin unable to open dialogue file.

Action: Check connect string for accuracy/typos.


ORA-06005 NETASY: dialogue file read failure

Cause: Autologin unable to read dialogue file.

Action: Check log file for operating system-specific error code.


ORA-06006 NETASY: dialogue execute failure

Cause: Expected response never received.

Action: Check log file for operating system-specific error code.


ORA-06007 NETASY: bad dialogue format

Cause: Dialogue file contains syntax error.

Action: Correct the dialogue file.


ORA-06009 NETASY: dialogue filename too long

Cause: Full file specification for dialogue file exceeds 64 bytes.

Action: Amend connect string accordingly.


ORA-06010 NETASY: dialogue file too long

Cause: Dialogue file exceeds 768 bytes in length.

Action: Simplify dialogue (for example, such as remove comments, redundant white space), or split into two and link with the MORE command.


ORA-06011 NETASY: dialogue too long

Cause: One of the following:

  • Dialogue contains more than 24 exchange blocks
  • Dialogue send string exceeds 84 bytes in length

Action: Simplify dialogue or split into two and link with the MORE command.


ORA-06017 NETASY: message receive failure

Cause: Asynchronous driver gets I/O error while doing network read operation.

Action: Check log file for operating system-specific error code and contact Oracle Support Services.


ORA-06018 NETASY: message send failure

Cause: Asynchronous driver gets I/O error while doing network write operation.

Action: Check log file for operating system-specific error code and contact Oracle Support Services.


ORA-06019 NETASY: invalid login (connect) string

Cause: Syntax error in login string.

Action: Resubmit with correct string.


ORA-06020 NETASY: initialisation failure

Cause: Asynchronous driver unable to complete initialization.

Action: Check log file for operating system-specific error code.


ORA-06021 NETASY: connect failed

Cause: Asynchronous driver unable to establish connection with partner.

Action: Check log file for operating system-specific error code.


ORA-06022 NETASY: channel open failure

Cause: No free channel.

Action: Contact Oracle Support Services.


ORA-06023 NETASY: port open failure

Cause: Asynchronous driver unable to open port.

Action: Check log file for operating system-specific error code.


ORA-06024 NETASY: VTM error

Cause: Virtual Terminal Manager unable to read/write to port.

Action: Check log file for operating system-specific error code.


ORA-06025 NETASY: Configuration error

Cause: Asynchronous driver generated for server-only, but client service requested.

Action: Contact Oracle Support Services.


ORA-06026 NETASY: port close failure

Cause: Asynchronous driver unable to close port.

Action: Check log file for operating system-specific error code.


ORA-06027 NETASY: channel close failure

Cause: Asynchronous driver unable to close channel.

Action: Check log file for operating system-specific error code.


ORA-06028 NETASY: unable to intialise for logging

Cause: Asynchronous driver unable to initialize for logging I/O.

Action: Contact Oracle Support Services.


ORA-06029 NETASY: port assignment failure

Cause: Asynchronous driver unable to assign port to channel.

Action: Contact Oracle Support Services.


ORA-06030 NETDNT: connect failed, unrecognized node name

Cause: Node name specified in host string is unknown (probably misspelled).

Action: Retry with correct node name.


ORA-06031 NETDNT: connect failed, unrecognized object name

Cause: Host string contains reference to object (which does not exist):

@d:node-obj => object is ORDNobj;

  • When node is VMS, the object is ORDNobj.COM
  • When node is UNIX, the object is ORDNobj @d:node::"task=obj" => object is obj;
  • When node is VMS, the object is obj.COM
  • When node is UNIX, the object is obj

Action: Retry with correct object name or create the required object on host node.


ORA-06032 NETDNT: connect failed, access control data rejected

Cause: Host string contains invalid username/password.

Action: Retry with correct username/password.


ORA-06033 NETDNT: connect failed, partner rejected connection

Cause: Connection with partner was made but was rejected.

Action: Contact your network administrator.


ORA-06034 NETDNT: connect failed, partner exited unexpectedly

Cause: Connection with host node was made but partner aborted.

Action: Make sure object (see 06031, above) is working (for VMS run the command file and make sure that the Oracle server process starts up); sometimes happens when the network/node is under stress; in this case, a retry often works.


ORA-06035 NETDNT: connect failed, insufficient resources

Cause: Insufficient system resources are available to complete the connection; for example, all DECnet channels are in use.

Action: Contact your network administrator.


ORA-06037 NETDNT: connect failed, node unreachable

Cause: Host node is down.

Action: Contact your network administrator.


ORA-06039 NETDNT: connect failed

Cause: Connect failed for unexpected reason (see OSD error).

Action: Contact Oracle Support Services.


ORA-06040 NETDNT: invalid login (connect) string

Cause: Syntax error in login string.

Action: Resubmit with correct string.


ORA-06041 NETDNT: disconnect failed

Cause: Driver gets error while doing network close operation.

Action: Contact Oracle Support Services.


ORA-06042 NETDNT: message receive failure

Cause: Driver gets I/O error while doing network read operation.

Action: Contact Oracle Support Services.


ORA-06043 NETDNT: message send failure

Cause: Driver gets I/O error while doing network write operation.

Action: Contact Oracle Support Services.


ORA-06044 NETDNT: connect failed, byte count quota exceeded

Cause: Connect failed because of insufficient byte count quota.

Action: Increase byte count quota.


ORA-06102 NETTCP: cannot allocate context area

Cause: Insufficient dynamic memory available for connection context area.

Action: Contact Oracle Support Services.


ORA-06105 NETTCP: remote host is unknown

Cause: Host name specified in the login (connect) string is unknown.

Action: Check spelling; make sure name is in the TCP/IP HOST file.


ORA-06106 NETTCP: socket creation failure

Cause: Process open file quota probably exceeded.

Action: Contact Oracle Support Services.


ORA-06107 NETTCP: ORACLE network server not found

Cause: No entry in SERVICES file for Oracle server.

Action: Add (ORASRV) entry to the TCP/IP SERVICES file.


ORA-06108 NETTCP: connect to host failed

Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net TCP/IP server on the remote host is not up, or the host itself is not up (check the latter by targeting it with Telnet).

Action: Start the SQL*Net TCP/IP server process on the remote host.


ORA-06109 NETTCP: message receive failure

Cause: I/O error occurred while attempting network read operation.

Action: Contact Oracle Support Services.


ORA-06110 NETTCP: message send failure

Cause: I/O error occurred while attempting network write operation.

Action: Contact Oracle Support Services.


ORA-06111 NETTCP: disconnect failure

Cause: Error occurred while closing a socket.

Action: Contact Oracle Support Services.


ORA-06112 NETTCP: invalid buffer size

Cause: The buffer size specified in the login string exceeds the allowed maximum (of 4096).

Action: Re-submit with valid buffer size.


ORA-06113 NETTCP: Too many connections

Cause: The maximum no. of concurrently open connections has been reached.

Action: Exit an application with an open connection which is no longer required.


ORA-06114 NETTCP: SID lookup failure

Cause: From the remote host's SQL*Net TCP/IP server: the database SID, specified in the login (connect) string, was not recognized.

Action: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net TCP/IP server).


ORA-06115 NETTCP: unable to create ORACLE logicals

Cause: The host's SQL*Net TCP/IP server was unable to create the necessary logical names required by the Oracle server process. See the SQL*Net TCP/IP server log file for more details.

Action: Contact your system administrator.


ORA-06116 NETTCP: unable to create ORASRV process

Cause: The host's SQL*Net TCP/IP server was unable to create the Oracle server process. See the SQL*Net TCP/IP server log file for more details.

Action: Contact your system administrator.


ORA-06117 NETTCP: unable to create ORASRV: quota exceeded

Cause: The host's SQL*Net TCP/IP server was unable to create the Oracle server process because of quota depletion.

Action: Increase quota allocations to the SQL*Net TCP/IP server process.


ORA-06118 NETTCP: unable to complete handshake with ORASRV

Cause: The Oracle server process was started but failed to complete its initialization.

Action: Contact Oracle Support Services.


ORA-06119 NETTCP: spurious client request

Cause: The host's SQL*Net TCP/IP server was unable to recognize this connection request. See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06120 NETTCP: network driver not loaded

Cause: The TCP/IP network driver is not loaded.

Action: Check that the TCP/IP driver is loaded correctly.


ORA-06121 NETTCP: access failure

Cause: The host's SQL*Net TCP/IP server was unable to test the accessibility of the SID mapping file (specified in CONFIG.ORA) associated with this connection request. See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06122 NETTCP: setup failure

Cause: The host's SQL*Net TCP/IP server was unable to set up the appropriate environment to service this connection request. See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06123 NETTCP: cannot set KEEPALIVE

Cause: The host's SQL*Net TCP/IP server was unable to set the socket KEEPLIVE option. See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06124 NETTCP: timeout waiting for ORASRV

Cause: The Oracle server process was started but failed to respond after N seconds.

Action: For heavily loaded systems this is not an uncommon occurrence. Increase the value of N (the default is 30) by placing the following entry in the CONFIG.ORA file: SQLNET ORASRV_WAIT = no_of_secs which will come into effect the next time the SQL*Net TCP/IP server is started.


ORA-06125 NETTCP: ORASRV exited unexpectedly

Cause: The Oracle server process was started but exited unexpectedly. Possible causes:

  1. Insufficient quotas to run ORASRV
  2. Oracle is not installed See the ORASRV output file for more details; the file will be in the ORA_SQLNET directory and will have a name of the form: ORA_SRVTnn_sid.OUT

Action: If appropriate action is not obvious from the ORASRV output file, then contact Oracle Support Services.


ORA-06126 NETTCP: ORASRV unable to open network connection

Cause: The Oracle server process was started but was unable to open the socket passed to it by ORASRV.

Action: Contact Oracle Support Services.


ORA-06127 NETTCP: unable to change username

Cause: The host's SQL*Net TCP/IP server could not establish a PROXY LOGIN connection because the client username is unknown (to the host operating system).

Action: Create new user account on host.


ORA-06128 NETTCP: unable to create mailbox

Cause: The host's SQL*Net TCP/IP server was unable to create a mailbox (needed for IPC communication with the Oracle server process). See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06129 NETTCP: unable to transfer socket ownership to ORASRV

Cause: The host's SQL*Net TCP/IP server was unable to transfer the network communication handle to the Oracle server process. See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06130 NETTCP: host access denied

Cause: The host's SQL*Net TCP/IP server rejected this connection request because the client node does not have access privilege - as determined by the contents of the Valid Node Table (VNT), a component of the host's CONFIG.ORA.

Action: To grant access, add appropriate entry to the host's VNT.


ORA-06131 NETTCP: user access denied

Cause: The host's SQL*Net TCP/IP server rejected this connection request because the client user(name) does not have access privilege, as determined by the contents of the Username Mapping Table (UMT), a component of the host's CONFIG.ORA.

Action: To grant access, add appropriate entry to the host's UMT.


ORA-06132 NETTCP: access denied, wrong password

Cause: The host SQL*Net TCP/IP server rejected this connection request because the client password did not match the host password.

Action: To grant access, get passwords in sync.


ORA-06133 NETTCP: file not found

Cause: The host's SQL*Net TCP/IP server could not find the SID mapping file (specified in CONFIG.ORA) associated with this connection request.

Action: Check CONFIG.ORA for spelling; make correct entry.


ORA-06134 NETTCP: file access privilege violation

Cause: The host's SQL*Net TCP/IP server did not have READ/ EXECUTE permission for the SID mapping file (specified in CONFIG.ORA) associated with this connection request.

Action: Change protection on SID mapping file.


ORA-06135 NETTCP: connection rejected; server is stopping

Cause: The host's SQL*Net TCP/IP server rejected this connection request because it is in the process of stopping.

Action: Restart SQL*Net TCP/IP server.


ORA-06136 NETTCP: error during connection handshake

Cause: Network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06137 NETTCP: error during connection handshake

Cause: Network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06138 NETTCP: error during connection handshake

Cause: Network I/O failure occurred while communicating with the host's SQL*Net TCP/IP server. See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06140 NETTCP: no such user

Cause: A proxy login connect attempt failed because the client username has no counterpart on the host.

Action: Try again with a user that has a counterpart on the host.


ORA-06141 NETTCP: no privilege for user

Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server had insufficient privileges to access the proxy account.

Action: Change account protection; change server privileges.


ORA-06142 NETTCP: error getting user information

Cause: A proxy login connect attempt failed because the SQL*Net TCP/IP server was unable to access the proxy account. See the SQL*Net TCP/IP server log file for more details.

Action: Contact Oracle Support Services.


ORA-06143 NETTCP: maximum connections exceeded

Cause: The connect failed because the maximum concurrent connections supported by the host's SQL*Net TCP/IP server has already been reached.

Action: Wait for a short period and retry.


ORA-06144 NETTCP: SID (database) is unavailable

Cause: The database administrator on the host has varied the SID offline.

Action: Wait for it to be varied back online.


ORA-06145 NETTCP: unable to start ORASRV: images not installed

Cause: The host's SQL*Net TCP/IP server was unable to start the Oracle server process because the Oracle protected images were not installed.

Action: Install the images.


ORA-06200 TWOTASK: connect failed, can't create mailbox

ORA-06201 TWOTASK: connect failed, can't attach to mailbox

ORA-06202 TWOTASK: connect failed, can't spawn ORASRV process

ORA-06203 TWOTASK: connect failed, handshake failure

ORA-06204 TWOTASK: connect failed, can't access ORASRV2.COM

ORA-06205 TWOTASK: connect failed, can't create logical name

ORA-06206 TWOTASK: message receive failure

ORA-06207 TWOTASK: message send failure

ORA-06208 TWOTASK: invalid login (connect) string

ORA-06209 TWOTASK: connect failed, mailbox already exists

ORA-06210 TWOTASK: connect failed, ORASRV exited unexpectedly

ORA-06211 TWOTASK: connect failed, timeout waiting for ORASRV

ORA-06212 TWOTASK: connect failed, logical name table is full

ORA-06213 TWOTASK: connect failed

ORA-06214 TWOTASK: connect failed, insufficient quotas to create ORASRV

ORA-06215 TWOTASK: connect failed, ORASRV protected image not installed

ORA-06216 TWOTASK: connect failed, can't find ORASRV image file

ORA-06250 NETNTT: cannot allocate send and receive buffers

Cause: Two-task driver could not allocate data buffers.

Action: There is insufficient memory to run your program. Kill off other processes to free up memory.


ORA-06251 NETNTT: cannot translate address file name

Cause: ORACLE_HOME environment variable not set.

Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.


ORA-06252 NETNTT: cannot open address file

Cause: The NTT two-task driver could not open a file containing address information.

Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.


ORA-06253 NETNTT: cannot read arguments from address file

Cause: The NTT two-task driver could not read addressing information from its addressing file.

Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.


ORA-06254 NETNTT: cannot share connection to cube

Cause: The NTT two-task driver could not share a connection to the cube.

Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported. Make sure the instance you are attempting to connect to is actually up and running.


ORA-06255 NETNTT: cannot read pid of remote process

Cause: An error occurred while reading the NTT communications link.

Action: Contact Oracle Support Services.


ORA-06256 NETNTT: remote fork failed

Cause: The Oracle listener process on the cube could not fork off a shadow process.

Action: The instance you are trying to connect to probably does not have enough memory to run another shadow process. Ask someone else to log off, or connect to a different instance.


ORA-06257 NETNTT: cannot send command line to shadow process

Cause: An error occurred while writing the NTT communications link.

Action: Contact Oracle Support Services.


ORA-06258 NETNTT: cannot allocate context area

Cause: Two-task driver could not allocate data buffers.

Action: There is insufficient memory to run your program. Kill off other processes to free up memory.


ORA-06259 NETNTT: cannot read from remote process

Cause: An error occurred while reading the NTT communications link.

Action: Contact Oracle Support Services.


ORA-06260 NETNTT: cannot write to remote process

Cause: An error occurred while writing the NTT communications link.

Action: Contact Oracle Support Services.


ORA-06261 NETNTT: nrange() failed

Cause: The call to NRANGE() failed while attempting to establish a connection.

Action: Contact Oracle Support Services.


ORA-06262 NETNTT: nfconn() failed

Cause: The call to NFCONN() failed while attempting to establish a connection.

Action: Contact Oracle Support Services.


ORA-06263 NETNTT: out of memory in pi_connect

Cause: Two-task driver could not allocate data buffers.

Action: There is insufficient memory to run your program. Kill off other processes to free up memory.


ORA-06264 NETNTT: data protocol error

Cause: The NTT two-task driver received an unexpected message type.

Action: Contact Oracle Support Services.


ORA-06265 NETNTT: break protocol error

Cause: The NTT two-task driver received an unexpected message type.

Action: Contact Oracle Support Services.


ORA-06266 NETNTT: bad write length

Cause: The NTT two-task driver failed on an internal consistency check.

Action: Contact Oracle Support Services.


ORA-06267 NETNTT: bad state

Cause: The NTT two-task driver failed on an internal consistency check.

Action: Contact Oracle Support Services.


ORA-06268 NETNTT: cannot read /etc/oratab

Cause: The NTT two-task driver could not read configuration information from /etc/oratab.

Action: Make sure /etc/oratab exists and is readable. This error may occur if the file is incorrectly formatted. It also may occur if the driver has run out of memory.


ORA-06300 IPA: Disconnect failure

Cause: A fatal error occurred during the disconnect from the server. This was probably caused by inaccessible message queues.

Action: If there is no message queue, restart the SQL*Net IPA servers using IPACTL. Otherwise contact Oracle Support Services.


ORA-06301 IPA: Cannot allocate driver context

Cause: The memory pool is exhausted.

Action: Check the circumstances and try to allocate less memory in your program or adjust the parameters in your initialization parameter file and retry.


ORA-06302 IPA: Cannot connect to remote host

Cause: One of the following:

  • There is no ADI server defined to reflect a connection to the specified host.
  • The remote host is not known by the local system.
  • The Oracle kernel on the remote host is not generated with the IPA driver

Action: Check sequentially for the above causes and eliminate the actual cause found.


ORA-06303 IPA: Message send error

Cause: The SQL*Net IPA driver could not write the message into the message queue.

Action: Make sure that the message queue exists and is accessible. If necessary rerun IPACTL.


ORA-06304 IPA: Message receive error

Cause: The SQL*Net IPA driver could not read a message from the message queue.

Action: Make sure that the message queue exists and is accessible. If necessary rerun IPACTL.


ORA-06305 IPA: Illegal message type

Cause: The communication between user and Oracle is out of synchronization. This message should not normally be issued.

Action: Contact Oracle Support Services.


ORA-06306 IPA: Message write length error

Cause: The IPA driver tried to write a message in the queue that was too big for the queue.

Action: Contact Oracle Support Services.


ORA-06307 IPA: Cannot reset connection

Cause: A fatal error occurred during the resetting of the connection.

Action: Contact Oracle Support Services.


ORA-06308 IPA: No more connections available

Cause: You have exhausted all your connections.

Action: Try again when some of the current users have logged off.


ORA-06309 IPA: No message queue available

Cause: The SQL*Net IPA servers have not been started.

Action: Run IPACTL.


ORA-06310 IPA: Environment variable(s) not set

Cause: Environment variable(s) not set correctly.

Action: Check and correct.


ORA-06311 IPA: Maximum number of servers reached

Cause: Maximum number of servers reached.

Action: Shut down and restart with an increased maximum number of servers. Note that database links consume one server per link. Be sure to start enough servers to support database links.


ORA-06312 IPA: Incorrect outgoing service name supplied

Cause: Incorrect outgoing service name supplied.

Action: Check and correct the service name.


ORA-06313 IPA: Shared memory failed to initialise

Cause: The shared memory has not been set up correctly.

Action: Contact your system administrator.


ORA-06314 IPA: Event set up failure

Cause: Fatal interprocess communication error.

Action: Contact your system administrator.


ORA-06315 IPA: Invalid connect string

Cause: The connect string is malformed.

Action: Check and correct.


ORA-06316 IPA: Invalid database SID

Cause: The SID is unknown at the remote side.

Action: Either the database does not exist, is not running, or there are no reserved servers for that SID.


ORA-06317 IPA: Local maximum number of users exceeded

Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the local side.

Action: Wait for free connections to become available. If the problem persists, contact your system administrator.


ORA-06318 IPA: Local maximum number of connections exceeded

Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle to different hosts has been exceeded on the local side.

Action: Wait for free connections to become available. If the problem persists, contact your system administrator.


ORA-06319 IPA: Remote maximum number of users exceeded

Cause: The maximum number of simultaneous users of SQL*Net IPA has been exceeded on the remote side.

Action: Wait for free connections to become available. If the problem persists, contact your system administrator.


ORA-06320 IPA: Remote maximum number of connections exceeded

Cause: The maximum number of simultaneous connections that SQL*Net IPA can handle from different hosts has been exceeded on the remote side.

Action: Wait for free connections to become available. If the problem persists, contact your system administrator.


ORA-06321 IPA: Cannot reach the remote side

Cause: There has been a timeout on an attempt to connect to a remote server the reason for which is most likely to be the remote SQL*Net IPA software is not running. An alternative reason could be that the remote initiator service name is incorrect.

Action: Check and start the remote SQL*Net software. Check that it is started with the correct service names supplied.


ORA-06322 IPA: Fatal shared memory error

Cause: An internal error has occurred in the shared memory handling.

Action: Contact Oracle Support Services.


ORA-06323 IPA: Cause event error

Cause: Fatal interprocess communication error.

Action: Contact your system administrator.


ORA-06400 NETCMN: No default host string specified

Cause: There was no default host string specified in the configuration and the user did not specify any explicit connect string.

Action: Either reconfigure the system specifying a default connect string or use an explicit connect string.


ORA-06401 NETCMN: invalid driver designator

Cause: The login (connect) string contains an invalid driver designator.

Action: Correct the string and re-submit.


ORA-06402 NETCMN: error receiving break message

Cause: Error occurred while attempting to read a break message.

Action: Contact Oracle Support Services.


ORA-06403 Unable to allocate memory.

Cause: System unable to allocate needed virtual memory.

Action: Configure more memory, reduce load, or try again.


ORA-06404 NETCMN: invalid login (connect) string

Cause: Syntax error in login string.

Action: Correct string and re-submit.


ORA-06405 NETCMN: reset protocol error

Cause: Unable to reset out of break state.

Action: Contact Oracle Support Services.


ORA-06406 NETCMN: error sending break message

Cause: Error occurred while attempting to send a break message.

Action: Contact Oracle Support Services.


ORA-06407 NETCMN: unable to set up break handling environment

Cause: Error occurred while attempting to set up asynchronous handlers for in-coming, out-of-band break messages.

Action: Contact Oracle Support Services.


ORA-06408 NETCMN: incorrect message format

Cause: Message from partner contains bad header.

Action: Contact Oracle Support Services.


ORA-06413 Connection not open.

Cause: Unable to establish connection.

Action: Use diagnostic procedures to ascertain exact problem.


ORA-06416 NETCMN: error on test

Cause: Error occurred while testing I/O status of the network connection.

Action: Contact Oracle Support Services.


ORA-06419 NETCMN: server can not start oracle

Cause: The remote server was unable to start an Oracle process on behalf of the client.

Action: Make sure permissions on the remote Oracle program are correctly set. Contact your system administrator.


ORA-06420 NETCMN: SID lookup failure

Cause: From the remote host's server: the database SID, specified in the login (connect) string, was not recognized.

Action: Add the appropriate SID entry to the CONFIG.ORA or ORATAB file on the remote host (restarting the remote server may be needed).


ORA-06421 NETCMN: Error detected in the read-in data

Cause: Error found during recomputation of checksum or CRC.

Action: Possible hardware failures of communication nodes. Contact system administrator immediately.


ORA-06422 NETCMN: Error in sending data

Cause: Unable to transmit data to remote host.

Action: Try reconnect to remote host, and contact your system administrator.


ORA-06423 NETCMN: Error in receiving data

Cause: Unable to receive data from remote host.

Action: Try reconnect to remote host, and contact your system administrator.


ORA-06430 ssaio: Seals do not match

Cause: A function was called with an invalid argument.

Action: Contact Oracle Support Services.


ORA-06431 ssaio: Invalid Block number

Cause: The file block number is out of range of the file. The additional information returns the block number.

Action: Verify that the block number is correct. Run DBFSIZE and check if the block number is in that range. Contact Oracle Support Services.


ORA-06432 ssaio: Buffer Not Aligned

Cause: The I/O buffer was not aligned on a 2K boundary.

Action: Contact Oracle Support Services.


ORA-06433 ssaio: LSEEK error, unable to seek to requested block.

Cause: The additional information returns the block number.

Action: Look up the additional information returned in your operating system reference manual. Verify that the block number is correct.


ORA-06434 ssaio: read error, unable to read requested block from database file.

Cause: The read system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.


ORA-06435 ssaio: write error, unable to write requested block to database file.

Cause: The write system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.


ORA-06436 ssaio: asynchronous I/O failed due to incorrect parameters.

Cause: The Asynchronous I/O system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.


ORA-06437 ssaio: the asynchronous write was unable to write to the database file.

Cause: The Asynchronous I/O system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.


ORA-06438 ssaio: the asynchronous read was unable to read from the database file.

Cause: The Asynchronous I/O system call returned an error.

Action: The additional information indicates the block number. Look up the additional information returned in your operating system manual.


ORA-06439 ssaio: the asynchronous write returned incorrect number of bytes

Cause: This write call may have been truncated. The additional information returns the block number and number of bytes.

Action: Verify that the block number and the number of bytes written are correct.


ORA-06440 ssaio: the asynchronous read returned incorrect number of bytes

Cause: This read call may have been truncated. The additional information returns the block number and number of bytes.

Action: Verify that the block number and the number of bytes read are correct.


ORA-06441 ssvwatev: Incorrect parameter passed to function call

Cause: Either the Oracle process ID, or wait time or event ID is invalid.

Action: The additional information indicates the process ID, time and event ID.


ORA-06442 ssvwatev: Failed with unexpected error number.

Cause: Some system problems may exist on your system; check the error logs.

Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.


ORA-06443 ssvpstev: Incorrect parameter passed to function call

Cause: An invalid event ID is passed in to this routine.

Action: The additional information indicates the event ID.


ORA-06444 ssvpstev: Failed with unexpected error number.

Cause: Some system problems may exist on your system; check the error logs.

Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.


ORA-06445 ssvpstevrg: Incorrect parameters passed to function call

Cause: An invalid event ID, or the low and high event ID do not exist.

Action: The additional information indicates the error number. It also contains the event ID, low boundary and high boundary.


ORA-06446 ssvpstevrg: Failed with unexpected error number.

Cause: Some system problems may exist on your system; check the error logs.

Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.


ORA-06447 ssvpstp: Incorrect parameter passed to function call

Cause: Invalid Oracle process ID is passed in to this routine.

Action: The additional information indicates the process ID.


ORA-06448 ssvpstp: Failed with unexpected error number.

Cause: Some system problems may exist on your system; check the error logs.

Action: The additional information indicates the error number. Look up the additional information returned in your operating system manual.


ORA-06449 The list IO or the sysvendor is not installed.

Cause: Oracle tries to use the SYSVENDOR interface (INIT.ORA parameter USE_SYSVENDOR=TRUE) but the UNIX kernel does not have the Oracle SYSVENDOR interface linked in.

Action: Set USE_SYSVENDOR=FALSE in INIT.ORA, if you do not want to use this interface or link the UNIX kernel with this interface so that Oracle can use it.


ORA-06500 PL/SQL: storage error

Cause: This is a rare internal error message. Memory has been exhausted or corrupted.

Action: Contact Oracle Support Services.


ORA-06501 PL/SQL: program error

Cause: This is an internal error message. An error has been detected in a PL/SQL program.

Action: Contact Oracle Support Services.


ORA-06502 PL/SQL: numeric or value error string

Cause: An arithmetic, numeric, string, conversion, or constraint error occurred. For example, this error occurs if an attempt is made to assign the value NULL to a variable declared NOT NULL, or if an attempt is made to assign an integer larger than 99 to a variable declared NUMBER(2).

Action: Change the data, how it is manipulated, or how it is declared so that values do not violate constraints.


ORA-06503 PL/SQL: Function returned without value

Cause: A call to PL/SQL function completed, but no RETURN statement was executed.

Action: Rewrite PL/SQL function, making sure that it always returns a value of a proper type.


ORA-06504 PL/SQL: Return types of Result Set variables or query do not match

Cause: Number and/or types of columns in a query does not match declared return type of a result set variable, or declared types of two Result Set variables do not match.

Action: Change the program statement or declaration. Verify what query the variable actually refers to during execution.


ORA-06505 PL/SQL: variable requires more than 32767 bytes of contiguous memory

Cause: A PL/SQL variable was declared with a constraint which required more than 32767 bytes of memory. PL/SQL does not currently support allocations of contiguous memory greater than 32767 bytes.

Action: Consider reducing the constraint in the variable declaration. If that is not possible, try changing the database or national character set to such, that requires less memory for the same constraint. Note: changing the character set will impact execution of all PL/SQL code.


ORA-06508 PL/SQL: could not find program unit being called

Cause: An attempt was made to call a stored program that could not be found. The program may have been dropped or incompatibly modified, or have compiled with errors.

Action: Check that all referenced programs, including their package bodies, exist and are compatible.


ORA-06509 PL/SQL: ICD vector missing for this package

Cause: This indicates a version clash between some package distributed with an Oracle product and the product executable.

Action: Contact Oracle Support Services.


ORA-06510 PL/SQL: unhandled user-defined exception

Cause: A user-defined exception was raised by PL/SQL code, but not handled.

Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or database administrator.


ORA-06511 PL/SQL: cursor already open

Cause: An attempt was made to open a cursor that was already open.

Action: Close cursor first before reopening.


ORA-06512 at string line string

Cause: Backtrace message as the stack is unwound by unhandled exceptions.

Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or database administrator.


ORA-06513 PL/SQL: index for PL/SQL table out of range for host language array

Cause: An attempt is being made to copy a PL/SQL table to a host language array. But an index in the table is either less than one or greater than the maximum size of the host language array. When copying PL/SQL tables to host language arrays, the table entry at index 1 is placed in the first element of the array, the entry at index 2 is placed in the second element of the array, etc. If an table entry has not been assigned then the corresponding element in the host language array is set to null.

Action: Increase size of host language array, or decrease size of PL/SQL table. Also make sure that you do not use index values less than 1.


ORA-06514 PL/SQL: The remote call cannot be handled by the server

Cause: The remote call has parameters that are cursor variables or lob variables. This cannot be handled by stored procedures on your server.

Action: Avoid using cursor variables or lob variables as parameters for stored procedures on this server or upgrade your server to a release that supports this.


ORA-06515 PL/SQL: unhandled exception string

Cause: An exception was raised by PL/SQL code, but not handled. The exception number is outside the legal range of Oracle errors.

Action: Fix the problem causing the exception or write an exception handler for this condition. Or you may need to contact your application administrator or database administrator.


ORA-06516 PL/SQL: the Probe packages do not exist or are invalid

Cause: A Probe operation, probably an attempt to initialize the Oracle server to debug PL/SQL, could not be completed because the Probe packages were not loaded or have become invalid.

Action: DBA should load the Probe packages. This can be done by running the PBLOAD.SQL script supplied with the RDBMS.


ORA-06517 PL/SQL: Probe error - string

Cause: An error occurred while passing a Probe operation to the server for execution.

Action: Refer to the entry for the embedded error message.


ORA-06518 PL/SQL: Probe version string incompatible with version string

Cause: The current version of Probe is incompatible with the version on the Oracle server.

Action: Refer to the documentation to ensure that this degree of compatibility is supported.


ORA-06519 active autonomous transaction detected and rolled back

Cause: Before returning from an autonomous PL/SQL block, all autonomous transactions started within the block must be completed (either committed or rolled back). If not, the active autonomous transaction is implicitly rolled back and this error is raised.

Action: Ensure that before returning from an autonomous PL/SQL block, any active autonomous transactions are explicitly committed or rolled back.


ORA-06520 PL/SQL: Error loading external library

Cause: An error was detected by PL/SQL trying to load the external library dynamically.

Action: Check the stacked error (if any) for more details.


ORA-06521 PL/SQL: Error mapping function

Cause: An error was detected by PL/SQL trying to map the mentioned function dynamically.

Action: Check the stacked error (if any) for more details.


ORA-06522 string

Cause: ORA-06520 or ORA-06521could stack this error with a system-specific error string.

Action: This error string should give the cause for errors ORA-06520 or ORA-06521


ORA-06523 Maximum number of arguments exceeded

Cause: There is an upper limit on the number of arguments that one can pass to the external function.

Action: Check the port-specific documentation on how to calculate the upper limit.


ORA-06524 Unsupported option : string

Cause: The option specified is an unsupported feature for external procedures.

Action: Correct the syntax in the external specification.


ORA-06525 Length Mismatch for CHAR or RAW data

Cause: The length specified in the length variable has an illegal value. This can happen if you have requested a PL/SQL INOUT, OUT or RETURN raw variable to be passed as a RAW with no corresponding length variable. This error can also happen if there is a mismatch in the length value set in the length variable and the length in the ORLVSTR or ORLRAW.

Action: Correct the external procedure code and set the length variable correctly.


ORA-06526 Unable to load PL/SQL library

Cause: PL/SQL was unable to instantiate the library referenced by this referenced in the EXTERNAL syntax. This is a serious error and should normally not happen.

Action: Report this problem to Oracle Support Services.


ORA-06527 External procedure SQLLIB error: string

Cause: An error occurred in SQLLIB during execution of a Pro* external procedure.

Action: The message text indicates the actual SQLLIB error that occurred.


ORA-06528 Error executing PL/SQL profiler

Cause: An error occurred during execution of a PL/SQL profiler procedure.

Action: Check the stacked errors for more details.


ORA-06529 Version mismatch - PL/SQL profiler

Cause: The PL/SQL profiler package (DBMSPB.SQL, PRVTPBP.PLB) does not match the version of the code in the server implementing the profiler.

Action: Run the package PROFLOAD.SQL in $ORACLE_HOME/rdbms/admin to load the correct version of the PL/SQL profiler packages.


ORA-06530 Reference to uninitialized composite

Cause: An object, LOB, or other composite was referenced as a left hand side without having been initialized.

Action: Initialize the composite with an appropriate constructor or whole-object assignment.


ORA-06531 Reference to uninitialized collection

Cause: An element or member function of a nested table or VARRAY was referenced (where an initialized collection is needed) without the collection having been initialized.

Action: Initialize the collection with an appropriate constructor or whole-object assignment.


ORA-06532 Subscript outside of limit

Cause: A subscript was greater than the limit of a VARRAY or non-positive for a VARRAY or nested table.

Action: Check the program logic and increase the VARRAY limit if necessary.


ORA-06533 Subscript beyond count

Cause: An in-limit subscript was greater than the count of a VARRAY or too large for a nested table.

Action: Check the program logic and explicitly extend if necessary.


ORA-06534 cannot access Serially Reusable package string in the context of a trigger

Cause: The program attempted to access a Serially Reusable package in the context of a trigger. Such an access is currently unsupported.

Action: Check the program logic and remove any references to Serially Reusable packages (procedure, function or variable references) which might happen in the context of a trigger.


ORA-06535 statement string in string is NULL or 0 length

Cause: The program attempted to use a dynamic statement string that was either NULL or 0 length.

Action: Check the program logic and ensure that the dynamic statement string is properly initialized.


ORA-06536 IN bind variable bound to an OUT position

Cause: The program attempted to bind an IN bind variable to a statement that was expecting an OUT bind variable at that position.

Action: Make sure that an OUT or IN OUT bind mode is specified for the bind argument.


ORA-06537 OUT bind variable bound to an IN position

Cause: The program attempted to bind an OUT bind variable to a statement that was expecting an IN bind variable at that position.

Action: Make sure that an IN or IN OUT bind mode is specified for the bind argument.


ORA-06538 statement violates string RESTRICT_REFERENCES pragma

Cause: The program attempted to execute a dynamic statement which does not meet the purity level specified (in the pragma RESTRICT_REFERENCES directive) for the module executing the statement.

Action: Ensure that the dynamic statement meets the purity level specified for the module executing the statement.


ORA-06539 target of OPEN must be a query

Cause: The program attempted to perform an OPEN cursor operation on a dynamic statement that was not a query.

Action: Ensure that the OPEN cursor operation is done on a dynamic query statement.


ORA-06540 PL/SQL: compilation error

Cause: A PL/SQL compilation error occurred. However, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages.

Action: See accompanying PLS-nnnnn error messages.


ORA-06541 PL/SQL: compilation error - compilation aborted

Cause: A PL/SQL compilation error occurred and the compilation was aborted; but the compilation unit was written out to the backing store. However, unlike ORA-06545, the user generally will not see this error message. Instead, there will be accompanying PLS-nnnnn error messages.

Action: See accompanying PLS-nnnnn error messages.


ORA-06544 PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

Cause: A PL/SQL internal error occurred.

Action: Report as a bug; the first argument is the internal error number.


ORA-06545 PL/SQL: compilation error - compilation aborted

Cause: A PL/SQL compilation error occurred and the compilation was aborted completely without the compilation unit being written out to the backing store. Unlike ORA-06541, the user will always see this error along with the accompanying PLS-nnnnn error messages.

Action: See accompanying PLS-nnnnn error messages.


ORA-06546 DDL statement is executed in an illegal context

Cause: DDL statement is executed dynamically in illegal PL/SQL context.

  • Dynamic OPEN cursor for a DDL in PL/SQL
  • Bind variables used in the USING clause to EXECUTE IMMEDIATE a DDL
  • Define variables used in the INTO clause to EXECUTE IMMEDIATE a DDL

Action: Use EXECUTE IMMEDIATE without USING and INTO clauses to execute the DDL statement.


ORA-06547 RETURNING clause must be used with INSERT, UPDATE, or DELETE statements

Cause: EXECUTE IMMEDIATE with a RETURNING clause is used to execute dynamic UPDATE, INSERT, or DELETE statements only.

Action: Use the RETURNING clause in EXECUTE IMMEDIATE for INSERT, UPDATE, or DELETE statements only. For other statements, use the USING clause instead.


ORA-06548 no more rows needed

Cause: The caller of a pipelined function does not need more rows to be produced by the pipelined function.

Action: Catch the NO_DATA_NEEDED exception is an exception handling block.


ORA-06549 PL/SQL: failed to dynamically open shared object (DLL): string

Cause: One possible cause might be that there are too many DLLs open at the same time.


ORA-06550 line string, column string:string

Cause: A PL/SQL compilation error has occurred. The numbers given for line and column are the location in the PL/SQL block where the error occurred.

Action: Refer to the following PL/SQL messages for more information about the error.


ORA-06551 PL/SQL: Unhandled exception

ORA-06552 PL/SQL: string

ORA-06553 PLS-string: string

ORA-06554 package DBMS_STANDARD must be created before using PL/SQL

Cause: The DBMS-specific extensions to PL/SQL's package STANDARD are in package DBMS_STANDARD. This package must be created before using PL/SQL.

Action: Create package DBMS_STANDARD. The source for this PL/SQL stored package is provided with the distribution.


ORA-06555 this name is currently reserved for use by user SYS

Cause: An attempt was made to create a package named STANDARD, DBMS_STANDARD or DEBUG_IO. These are currently reserved for use by user SYS.

Action: Choose another name for your package.


ORA-06556 the pipe is empty, cannot fulfill the unpack_message request

Cause: There are no more items in the pipe.

Action: Check that the sender and receiver agree on the number and types of items placed on the pipe.


ORA-06557 null values are not allowed for any parameters to pipe icd's

Cause: Internal error from the DBMS_PIPE package.

Action: Contact Oracle Support Services.


ORA-06558 buffer in dbms_pipe package is full. No more items allowed

Cause: The pipe buffer size has been exceeded.

Action: Inspect the program to analyze the rate of input and output to the pipe. You might need to take items out of the pipe by executing RECEIVE_MESSAGE, or empty the entire pipe by executing PURGE on the pipe.


ORA-06559 wrong datatype requested, string, actual datatype is string

Cause: The sender put different datatype on the pipe than that being requested (package DBMS_PIPE). The numbers are:

  • 6 - number
  • 9 - char
  • 12 - date

Action: Check that the sender and receiver agree on the number and types of items placed on the pipe.


ORA-06560 pos, string, is negative or larger than the buffer size, string

Cause: Internal error from the DBMS_PIPE package.

Action: Contact Oracle Support Services.


ORA-06561 given statement is not supported by package DBMS_SQL

Cause: An attempt was made to parse an unsupported statement using procedure PARSE provided by package DBMS_SQL.

Action: Only statements which begin with SELECT, DELETE, INSERT, UPDATE, LOCK, BEGIN, DECLARE, or << (PL/SQL label delimiter) are supported.


ORA-06562 type of out argument must match type of column or bind variable

Cause: An attempt was made to get the value of a column or a bind variable by calling procedure COLUMN_VALUE or VARIABLE_VALUE of package DBMS_SQL but the type of the given out argument where to place the value is different from the type of the column or bind variable that was previously defined by calling procedure DEFINE_COLUMN (for defining a column) or BIND_VARIABLE (for binding a bind variable) of package DBMS_SQL.

Action: Pass in an out argument of the correct type when calling procedure COLUMN_VALUE or VARIABLE_VALUE. The right type is the type that was provided when defining the column or binding the bind variable.


ORA-06563 top level procedure/function specified, cannot have subparts

Cause: The name to be resolved was specified with three parts (a.b.c) but the a.b part resolves to a top level procedure or function (which do not have nested procedures). This can also happen with a two-part name, a.b, where a is a synonym for a top level package or procedure.

Action: Specify a procedure/function within a package, or a top level procedure/function.


ORA-06564 object string does not exist

Cause: The named object could not be found. Either it does not exist or you do not have permission to access it.

Action: Create the object or get permission to access it.


ORA-06565 cannot execute string from within stored procedure

Cause: The named procedure cannot be executed from within a stored procedure, function or package. This function can only be used from PL/SQL anonymous blocks.

Action: Remove the procedure from the calling stored procedure.


ORA-06566 invalid number of rows specified

Cause: An invalid number of rows was specified in a call to the procedure DEFINE_COLUMN in the package DBMS_SQL. For a given parsed statement in a given cursor, all columns must be defined to have the same number of rows, so all the calls to DEFINE_COLUMN must specify the same number of rows.

Action: Specify a number that matches that for previously defined columns.


ORA-06567 invalid number of values specified

Cause: An invalid number of values to be bound was specified in a call to the procedure BIND_VARIABLE in the package DBMS_SQL. In order to execute a given parsed statement in a given cursor, the same number of values must have been bound for all bind variables, so when EXECUTE is called, the latest calls to BIND_VARIABLE must have specified the same number of values to be bound for all bind variables.

Action: Make sure that the same number of values have been bound for all of the bind variables.


ORA-06568 obsolete ICD procedure called

Cause: An obsolete ICD procedure was called by a PL/SQL program. The PL/SQL program was probably written for an earlier release of RDBMS.

Action: Make sure that all PL/SQL programs have been upgraded to the latest release of the RDBMS. This can be accomplished by following upgrade instructions in the README file, or by running the CATPROC.SQL script supplied with the RDBMS.


ORA-06569 Collection bound by bind_array contains no elements

Cause: A collection with zero elements was bound to a bind variable in a call to procedure BIND_ARRAY in the package DBMS_SQL. In order to execute a bind of a collection, the collection must contain at least one element. If no elements are present, at execute time, there will be no value for this bind and the statement is meaningless.

Action: Fill the collection with the elements you want to bind and try the bind call again.


ORA-06570 shared pool object does not exist, cannot be pinned

Cause: The specified shared pool shared cursor could not be found, therefore it cannot be pinned.

Action: Make sure that a correct shared cursor name is given. Names are a string of the form 'HHHHHHHH,SDDDDDDDDDD' where the H's are an 8 digit hex number from the 'address' column of V$SQLAREA, and the D's are a 1 to 10 digit decimal number with an optional leading sign (from the HASH_VALUE column) Remove the procedure from the calling stored procedure.


ORA-06571 Function string does not guarantee not to update database

Cause: One of the following:

  • A SQL statement references a packaged, PL/SQL function that does not contain a pragma that prevents the database from being updated.
  • A SQL statement references a standalone, PL/SQL function that contains an instruction to update the database.

Action: If the referenced function is a packaged, PL/SQL function, re-create the PL/SQL function with the required pragma; be certain to include the 'Write No Database State' (WNDS) argument in the argument list of the pragma. If the referenced function is standalone, PL/SQL function, do not use the function.


ORA-06572 Function string has out arguments

Cause: A SQL statement references either a packaged or standalone PL/SQL function that contains an OUT parameter in its argument list. PL/SQL functions referenced by SQL statements must not contain the OUT parameter.

Action: Re-create the PL/SQL function without the OUT parameter in the argument list.


ORA-06573 Function string modifies package state, cannot be used here

Cause: One of the following:

  • A SQL statement references a packaged, PL/SQL function that does not contain a pragma containing the 'Write no Package State' (WNPS).
  • A SQL statement references a standalone, PL/SQL function that modifies a package state. A standalone, PL/SQL function referenced by a SQL statement cannot modify a package state.

Action: If the function is a packaged, PL/SQL function: Re-create the function and include a pragma containing the 'Write no Package State' (WNPS). If the function is standalone PL/SQL function, delete the function from the SQL statement.


ORA-06574 Function string references package state, cannot execute remotely

Cause: One of the following:

  • A remote, packaged function or a remote-mapped, local, packaged function that does not contain a pragma with the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments references a package state.
  • A remote, standalone function or a remote-mapped, local, standalone function contains a reference to a package state (reads or writes a package variable). Only local functions that are referenced in a SELECT list, VALUES clause of an INSERT statement, or SET clause of an UPDATE statement can modify a package state.

Action: If the function is a packaged function: Re-create the function and include a pragma containing the 'Write no Package State' (WNPS) and 'Read no Package State' (RNPS) arguments. If the function is a standalone function: Do not call the function.


ORA-06575 Package or function string is in an invalid state

Cause: A SQL statement references a PL/SQL function that is in an invalid state. Oracle attempted to compile the function, but detected errors.

Action: Check the SQL statement and the PL/SQL function for syntax errors or incorrectly assigned, or missing, privileges for a referenced object.


ORA-06576 not a valid function or procedure name

Cause: Could not find a function (if an INTO clause was present) or a procedure (if the statement did not have an INTO clause) to call.

Action: Change the statement to invoke a function or procedure.


ORA-06577 output parameter not a bind variable

Cause: The argument corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement must be a bind variable.

Action: Change the argument to a bind variable.


ORA-06578 output parameter cannot be a duplicate bind

Cause: The bind variable corresponding to an IN/OUT or OUT parameter for a function or a procedure or a function return value in a CALL statement cannot be a duplicate bind variable.

Action: Change the bind variable to be unique.


ORA-06580 Hash Join ran out of memory while keeping large rows in memory

Cause: Hash Join reserves 3 slots (each slot size = DB_BLOCK_SIZE * HASH_MULTIBLOCK_IO_COUNT) for a row. If a row is larger than that, this error will be raised.

Action: Increase HASH_MULTIBLOCK_IO_COUNT so that each joined row fits in a slot. HASH_AREA_SIZE may also need to be increased.


ORA-06592 CASE not found while executing CASE statement

Cause: A CASE statement must either list all possible cases or have an else clause.

Action: Add all missing cases or an ELSE clause.


ORA-06593 string is not supported with natively compiled PL/SQL modules

Cause: The specified feature is not yet supported for natively compiled PL/SQL modules.

Action: Recompile the relevant PL/SQL modules in non-native mode by setting the PLSQL_COMPILER_FLAGS parameter to INTERPRETED.


ORA-06600 LU6.2 Driver: SNA software is not loaded

Cause: The SNA software is not running.

Action: Start the SNA software and try again.


ORA-06601 LU6.2 Driver: Invalid database ID string

Cause: The database string in the connect was invalid.

Action: Provide a valid database string, as defined in documentation.


ORA-06602 LU6.2 Driver: Error allocating context area

Cause: Context area failure.

Action: Contact Oracle Support Services.


ORA-06603 LU6.2 Driver: Error allocating memory

Cause: Operating system refused request for memory.

Action: Contact Oracle Support Services.


ORA-06604 LU6.2 Driver: Unable to allocate session with remote LU

Cause: Allocate system call failed.

Action: Ensure that the SNA software is running and that sessions are free. If this is the case, then check your SNA configuration data for errors. You may have entered an incorrect parameter.


ORA-06605 LU6.2 Driver: Unexpected line turnaround

Cause: SNA software switched from send to receive unexpectedly.

Action: Check the SNA configuration data, particularly parameters associated with a session.


ORA-06606 LU6.2 Driver: Unexpected response from SNA

Cause: A parameter in an SNA call returned an unexpected value.

Action: Attempt to reproduce problem, debug and record the value of the 'what' data parameter at the time of error. Then contact your service representative.


ORA-06607 LU6.2 Driver: Reset occurred in send state

Cause: A reset was issued while in send state.

Action: Check the SNA LOG data, if relevant, for further information.


ORA-06608 LU6.2 Driver: Reset occurred in receive state

Cause: A reset was received from the partner while in receive state. This may be because the partner deallocated.

Action: Check the SNA LOG data, if relevant, for further information.


ORA-06610 LU6.2 Driver: Failed during deallocation

Cause: LU6.2 driver was unable to deallocate gracefully.

Action: Check the reason for deallocation. Consult the SNA LOG data.


ORA-06611 LU6.2 Driver: Request to send error

ORA-06612 LU6.2 Driver: Send data error

ORA-06613 LU6.2 Driver: Receive and wait error

ORA-06614 LU6.2 Driver: Receive Immediate error

ORA-06615 LU6.2 Driver: Send error

ORA-06616 LU6.2 Driver: Attach to LU failed

Cause: The SQL*Net LU6.2 driver was unable to attach to the LU specified in the connect string, or was unable to attach to the default LU.

Action: Check that the LU name specified in the connect string, or the default LU name if no LU was specified, is correctly configured and operational.


ORA-06617 LU6.2 Driver: Attach to PU failed

ORA-06618 LU6.2 Driver: Activation of subnetwork failed

ORA-06619 LU6.2 Driver: Unable to activate remote partner

ORA-06620 LU6.2 Driver: Invalid remote partner

ORA-06621 LU6.2 Driver: Allocation error

ORA-06622 LU6.2 Driver: Unable to attach to SNA

Cause: The SQL*Net LU6.2 driver could not attach to the SNA software on your machine. The most likely cause is that the SNA software is not operational.

Action: Check the status of the SNA software, ensure that it is operational and then try again.


ORA-06700 TLI Driver: incorrect message type from host

Cause: TLI received a message with an unrecognizable message type.

Action: Contact Oracle Support Services.


ORA-06701 TLI Driver: incorrect number of bytes written

Cause: TLI sent a message that was apparently successful, but the number of bytes transmitted did not match the number of bytes supplied to the driver.

Action: Contact Oracle Support Services.


ORA-06702 TLI Driver: cannot allocate context area

Cause: TLI could not allocate heap space for the context area.

Action: Contact Oracle Support Services.


ORA-06703 TLI Driver: send break message failed

Cause: TLI failed to send a break message across the connection.

Action: Contact Oracle Support Services.


ORA-06704 TLI Driver: receive break message failed

Cause: TLI failed to receive an expected break message.

Action: Contact Oracle Support Services.


ORA-06705 TLI Driver: remote node is unknown

Cause: TLI could not find your remote host information.

Action: Make sure you specified the host name correctly on the command line. (Also, check your capitalization and spelling.)


ORA-06706 TLI Driver: service not found

Cause: TLI could not find service information for the specified service name.

Action: If you specified the service name on the command line or with the environment variable TLI_SERVER, make sure you specified it correctly. If the service name is not in the SERVICES file for your protocol, ask your system administrator to add it.


ORA-06707 TLI Driver: connection failed

Cause: TLI failed to establish the connection to a SQL*Net TCP/IP server due to an error encountered by the remote server, which has supplied a string describing the remote error.

Action: See the SQL*Net TCP/IP User's Guide or the Oracle9i Net Services Administrator's Guide for the specific cause and action.


ORA-06708 TLI Driver: message receive failure

Cause: TLI encountered an error receiving a message from the communication channel.

Action: Contact Oracle Support Services.


ORA-06709 TLI Driver: message send failure

Cause: TLI encountered an error sending a message across the communication channel.

Action: Contact Oracle Support Services.


ORA-06710 TLI Driver: send interrupt break message failed

Cause: TLI failed to send a break message while handling an interrupt signal from the user.

Action: Contact Oracle Support Services.


ORA-06711 TLI Driver: error on bind

Cause: TLI failed to assign a network address to the communication channel.

Action: Contact Oracle Support Services.


ORA-06712 TLI Driver: error on accept

Cause: TLI failed to accept a connection request from the client.

Action: Contact Oracle Support Services.


ORA-06713 TLI Driver: error on connect

Cause: TLI failed to connect the client to the remote server. The network line to the remote host may be down.

Action: Use other network login programs to make sure that the remote host is accessible.


ORA-06720 TLI Driver: SID lookup failure

Cause: The database SID supplied in the database login string was not recognized by the remote host.

Action: Ask your system administrator to add the appropriate SID entry to ORATAB on the remote host.


ORA-06721 TLI Driver: spurious client req

Cause: The remote TLI server received an undefined request.

Action: Contact Oracle Support Services.


ORA-06722 TLI Driver: connection setup failure

Cause: The remote TLI server rejected the connection request, and the client was unable to retrieve an error code or message.

Action: Contact Oracle Support Services.


ORA-06730 TLI Driver: unable to open clone device

Cause: TLI failed to open the Streams clone device associated with the transport provider.

Action: Contact Oracle Support Services.


ORA-06731 TLI Driver: cannot alloc t_call

Cause: TLI cannot allocate space for the client's connection information.

Action: Contact Oracle Support Services.


ORA-06732 TLI Driver: cannot alloc t_discon

Cause: TLI cannot allocate space for the client's disconnection information.

Action: Contact Oracle Support Services.


ORA-06733 TLI Driver: failed to receive disconnect

Cause: TLI failed to receive an expected disconnection message during connection release.

Action: Contact Oracle Support Services.


ORA-06734 TLI Driver: cannot connect

Cause: TLI failed to connect the client to the remote server.

Action: Check that the remote TLI server is running.


ORA-06735 TLI Driver: client failed to close error conn

Cause: TLI failed to properly close a connection after an error was received.

Action: Contact Oracle Support Services.


ORA-06736 TLI Driver: server not running

Cause: TLI timed out while attempting to connect to the remote TLI server.

Action: Check that the remote TLI server is running with the status utility for the transport provider you are using. If it is not, ask your system administrator to start it.


ORA-06737 TLI Driver: connection failed

Cause: TLI could not establish a connection to the remote TLI server.

Action: Check that the remote TLI server is running with the status utility for the transport provider you are using.


ORA-06741 TLI Driver: unable to open protocol device

Cause: The TLI server failed to open the Streams device associated with the transport provider.

Action: Contact Oracle Support Services.


ORA-06742 TLI Driver: cannot alloc t_bind

Cause: The TLI server cannot allocate space for its requested network address.

Action: Contact Oracle Support Services.


ORA-06743 TLI Driver: cannot alloc t_bind

Cause: The TLI server cannot allocate space for its actual network address.

Action: Contact Oracle Support Services.


ORA-06744 TLI Driver: listener cannot bind

Cause: The TLI server failed to assign the correct network address on which to listen for connections.

Action: Contact Oracle Support Services.


ORA-06745 TLI Driver: listener already running

Cause: The network address on which the TLI server awaits connection requests is in use, possibly because the server is already running.

Action: Ensure that the TLI server is not already running. If it is not running and this error message recurs, contact Oracle Support Services.


ORA-06746 TLI Driver: cannot alloc t_call

Cause: TLI cannot allocate space for the TLI server's connection information.

Action: Contact Oracle Support Services.


ORA-06747 TLI Driver: error in listen

Cause: The TLI server encountered an error while listening for connection requests.

Action: Contact Oracle Support Services.


ORA-06748 TLI Driver: cannot allocate t_discon

Cause: TLI cannot allocate space for the TLI server's disconnection information.

Action: Contact Oracle Support Services.


ORA-06749 TLI Driver: option not allowed across network

Cause: The requested TLI server command must be issued from the same host on which the server is running.

Action: Log in to the remote host and try again.


ORA-06750 TLI Driver: sync failed

Cause: The Oracle process started by the TLI server was unable to synchronize its inherited connection.

Action: Contact Oracle Support Services.


ORA-06751 TLI Driver: bound addresses unequal

Cause: The OSN check server address failed. The bound server address was not the same as the requested binding address.

Action: Contact Oracle Support Services.


ORA-06752 TLI: error in signal setup

Cause: A call to SIGACTION() returned with a system error.

Action: Contact Oracle Support Services.


ORA-06753 TLI Driver: name-to-address mapping failed

Cause: For SVR4, the NETDIR_GETBYNAME() call failed for some unknown reason.

Action: Contact Oracle Support Services.


ORA-06754 TLI Driver: unable to get local host address

Cause: The name of the remote host to connect to was not specified, and the name of the local host cannot be retrieved from the HOSTS file.

Action: Contact your system administrator.


ORA-06755 TLI Driver: cannot close transport endpoint

Cause: The TLI server was unable to close a connection after passing it to an Oracle process.

Action: Contact Oracle Support Services.


ORA-06756 TLI Driver: cannot open oratab

Cause: The TLI server could not open the file used to define the locations of remotely accessible databases.

Action: Ask your system administrator to check that the file exists and has the correct permissions.


ORA-06757 TLI Driver: server got bad command

Cause: The TLI server received an invalid command.

Action: Contact Oracle Support Services.


ORA-06760 TLI Driver: timeout reading orderly release

Cause: TLI was not able to retrieve an expected disconnect message while closing the communication channel.

Action: Contact Oracle Support Services.


ORA-06761 TLI Driver: error sending orderly release

Cause: TLI encountered an error sending a disconnect message closing the communication channel.

Action: Contact Oracle Support Services.


ORA-06762 TLI Driver: error reading orderly release

Cause: TLI encountered an error receiving an expected disconnect message while closing the communication channel.

Action: Contact Oracle Support Services.


ORA-06763 TLI Driver: error sending disconnect

Cause: TLI encountered an error sending a disconnect message closing the communication channel.

Action: Contact Oracle Support Services.


ORA-06764 TLI Driver: error reading disconnect

Cause: TLI was not able to retrieve an expected disconnect message while closing the communication channel.

Action: Contact Oracle Support Services.


ORA-06765 TLI Driver: error awaiting orderly release

Cause: TLI encountered an error awaiting a disconnect message while closing the communication channel.

Action: Contact Oracle Support Services.


ORA-06766 TLI Driver: close failed during release

Cause: TLI failed to close the communication channel after receiving a disconnect message.

Action: Contact Oracle Support Services.


ORA-06767 TLI Driver: alloc failed during release

Cause: TLI cannot allocate space for disconnection information while closing the communication channel.

Action: Contact Oracle Support Services.


ORA-06770 TLI Driver: error sending version

Cause: TLI encountered an error while sending its version information during connection establishment.

Action: Contact Oracle Support Services.


ORA-06771 TLI Driver: error reading version

Cause: TLI encountered an error while awaiting the expected version information during connection establishment.

Action: Contact Oracle Support Services.


ORA-06772 TLI Driver: error sending command

Cause: TLI encountered an error while sending a command message during connection establishment.

Action: Contact Oracle Support Services.


ORA-06773 TLI Driver: error reading command

Cause: TLI encountered an error while awaiting the expected command message during connection establishment.

Action: Contact Oracle Support Services.


ORA-06774 TLI Driver: error sending break mode

Cause: TLI encountered an error while sending break-mode message during connection establishment.

Action: Contact Oracle Support Services.


ORA-06775 TLI Driver: error reading break mode

Cause: TLI encountered an error while awaiting the expected break-mode message during connection establishment.

Action: Contact Oracle Support Services.


ORA-06776 TLI Driver: error sending parms

Cause: TLI encountered an error while sending the connection parameters during connection establishment.

Action: Contact Oracle Support Services.


ORA-06777 TLI Driver: error reading parms

Cause: TLI encountered an error while awaiting the expected connection parameter message during connection establishment.

Action: Contact Oracle Support Services.


ORA-06778 TLI Driver: error sending ccode

Cause: TLI encountered an error while sending the completion status message during connection establishment.

Action: Contact Oracle Support Services.


ORA-06779 TLI Driver: error reading ccode

Cause: TLI encountered an error while awaiting the expected completion status message during connection establishment.

Action: Contact Oracle Support Services.


ORA-06780 TLI Driver: recv error code failed

Cause: TLI encountered an error while awaiting an expected error message during connection establishment.

Action: Contact Oracle Support Services.


ORA-06781 TLI Driver: error reading negotation string

Cause: TLI encountered an error while awaiting the expected negotiation message during connection establishment.

Action: Contact Oracle Support Services.


ORA-06790 TLI Driver: poll failed

Cause: TLI was unable to poll the communication channel for possible incoming messages.

Action: Contact Oracle Support Services.


ORA-06791 TLI Driver: poll returned error event

Cause: TLI received an unexpected event while polling the communication channel for possible incoming messages.

Action: Contact Oracle Support Services.


ORA-06792 TLI Driver: server cannot exec oracle

Cause: The remote TLI server was unable to start an Oracle process on behalf of the client.

Action: Note the operating system error message or number and contact your system administrator. The permissions on the remote Oracle program may be set incorrectly.


ORA-06793 TLI Driver: server cannot create new process

Cause: The remote TLI server was unable to start an Oracle process on behalf of the client.

Action: Note the operating system error message or number and contact your system administrator. The remote host may be unable to create any new processes due to a full process table.


ORA-06794 TLI Driver: shadow process could not retrieve protocol info

Cause: The Oracle process either failed to allocate memory to store the protocol information record, or the protocol rejected the request for some unknown reason.

Action: Contact Oracle Support Services.


ORA-06800 TLI Driver: SQL*Net SPX client went away during reconnect

Cause: The client process was aborted by the system or the user, and was unable to complete the connection establishment with the server listener process.

Action: Determine the cause of the client exit, and reattempt the connection.


ORA-06801 TLI Driver: listen for SPX server reconnect failed

Cause: An unknown event occurred on the client's listening socket.

Action: Contact Oracle Support Services.


ORA-06802 TLI Driver: could not open the /etc/netware/yellowpages file

Cause: The /etc/netware/yellowpages file does not exist, or is not readable by the TLI listener process.

Action: Insure the file exists and is readable. Make sure that the server machine's node name, network number, ethernet address, and listening socket number are encoded in the file.


ORA-06803 TLI Driver: the IPX device file could not be opened

Cause: The /dev/ipx file does not exist, or the driver has not been installed in the kernel correctly.

Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.


ORA-06804 TLI Driver: could not bind an IPX address at initialization

Cause: The IPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.


ORA-06805 TLI Driver: could not send datagram SAP packet for SPX

Cause: The socket endpoint for sending SAP packet was corrupted for some unknown reason.

Action: Contact Oracle Support Services.


ORA-06806 TLI Driver: could not complete protocol initialization for SPX

Cause: A step in the SPX/IPX protocol initialization failed.

Action: Check the previous error reported, and follow corrective action.


ORA-06807 TLI Driver: could not open ethernet device driver file

Cause: The file /dev/eth does not exist, or the driver it references could not be opened.

Action: The system's real ethernet device file, for example /dev/wd, for the Western Digital ethernet driver, should be linked to the file /dev/eth. If this has been done, insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact Oracle Support Services for a list of supported ethernet drivers.


ORA-06808 TLI Driver: could not link IPX and ethernet streams

Cause: Either the ethernet driver has not been installed in the system correctly, or the ethernet driver is not supported.

Action: Insure that the ethernet driver has been installed by completing the TCP/IP installation on your system, and testing a connection. If problem continues, contact Oracle Support Services for a list of supported ethernet drivers.


ORA-06809 TLI Driver: could not clear the IPX ethernet SAP at init

Cause: The IPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.


ORA-06810 TLI Driver: could not set the IPX ethernet SAP at init

Cause: The IPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.


ORA-06811 TLI Driver: could not set the IPX network number at init

Cause: The IPX driver has not been correctly installed, or the network number encoded in the /etc/netware/yellowpages file is invalid.

Action: The network number in the yellowpages file should match the four-byte network number of your Novell file server. If this is configured correctly, reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.


ORA-06812 TLI Driver: could not read the ethernet driver's node address

Cause: The ethernet driver is not installed correctly, or does not support this operation.

Action: Contact Oracle Support Services for a list of supported ethernet drivers.


ORA-06813 TLI Driver: the configured ethernet address is incorrect

Cause: The node address read from the ethernet driver does not match the value encoded in the /etc/netware/yellowpages file for this server.

Action: Confirm the correct ethernet node address for your LAN card, and enter this value in the yellowpages file.


ORA-06814 TLI Driver: the SPX device file could not be opened

Cause: The /dev/nspxd file does not exist, or the driver has not been installed in the kernel correctly.

Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.


ORA-06815 TLI Driver: could not link SPX and IPX streams

Cause: The SPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.


ORA-06816 TLI Driver: could not set the SPX SAP address

Cause: The SPX driver has not been correctly installed.

Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.


ORA-06817 TLI Driver: could not read the Novell network address

Cause: The file $ORACLE_HOME/spx/address could not be opened for reading and writing.

Action: Make sure ORACLE_HOME is set, and the permissions on the ORACLE_HOME are read, write. If this file has been unintentionally deleted, run SPXCTL (net option) to reset the configured Novell network number for SQL*Net SPX.


ORA-06900 CMX: cannot read tns directory

Cause: CMX is not started on your system.

Action: Install and/or start CMX on your system.


ORA-06901 CMX: no local name assigned to local application

Cause: Local application ORACMX has no local name assigned.

Action: Enter unique local name for ORACMX in the TNS directory.


ORA-06902 CMX: cannot attach to cmx subsystem

Cause: CCP-xxxx is not started.

Action: Start your CCP software on the communication controller.


ORA-06903 CMX: cannot read transport address of remote application

Cause: Remote application not entered in TNS directory.

Action: Enter remote application in TNS directory.


ORA-06904 CMX: no transport address available for remote application

Cause: No local name assigned to remote application.

Action: Assign local name to remote application.


ORA-06905 CMX: connect error

Cause: Remote partner not listening.

Action: Make sure remote node has CMX installed and running make sure ORACMX is running on remote host.


ORA-06906 CMX: cannot get maximum packet size from CMX

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06907 CMX: error during connect confirmation

Cause: Remote partner aborted.

Action: Contact Oracle Support Services.


ORA-06908 CMX: error during transfer of ORACLE_SID

Cause: Remote partner aborted.

Action: Contact Oracle Support Services.


ORA-06909 CMX: error during acknowledge of ORACLE_SID

Cause: Remote partner aborted.

Action: Contact Oracle Support Services.


ORA-06910 CMX: Cannot start oracle process on remote machine

Cause: Oracle process not found or wrong mode (should be 4751).

Action: Change /etc/oratab or set mode to 4751.


ORA-06911 CMX: t_event returns ERROR

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06912 CMX: write error in datarq

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06913 CMX: error during redirection of connection

Cause: ORACMX has been stopped, or user process has been aborted.

Action: Contact Oracle Support Services.


ORA-06914 CMX: unexepected event during start of oracle

Cause: Connect sequence out of sync.

Action: Contact Oracle Support Services.


ORA-06915 CMX: unknown t_event in datarq

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06916 CMX: error in data read (t_datain)

Cause: Remote partner aborted.

Action: Contact Oracle Support Services.


ORA-06917 CMX: error in data read (too many bytes read)

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06918 CMX: T_NOEVENT during wait for read event

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06919 CMX: error during write request (unknown event)

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06920 CMX: getbrkmsg illegal datatype

Cause: Received packets are corrupted.

Action: Contact Oracle Support Services.


ORA-06921 CMX: getdatmsg illegal datatype

Cause: Received packets are corrupted.

Action: Contact Oracle Support Services.


ORA-06922 CMX: bad write length

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06923 CMX: illegal break condition

Cause: Break handling out of sync.

Action: Contact Oracle Support Services.


ORA-06924 CMX: wrong break message length

Cause: Received packets are corrupted.

Action: Contact Oracle Support Services.


ORA-06925 CMX: disconnect during connect request

Cause: Partner is not responding.

Action: Make sure partner is up and running and reachable.


ORA-06926 CMX: T_ERROR during read data

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06927 CMX: T_DATAIN received before all data written

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06928 CMX: wrong ORACLE_SID

Cause: ORACLE_SID is not entered in remote ORATAB.

Action: Add ORACLE_SID to remote ORATAB.


ORA-06929 CMX: error when sending ORACLE_SID

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06930 CMX: error when checking ORACLE_SID

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06931 CMX: error during read_properties for server

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06932 CMX: error in local name

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06933 CMX: error during attach

Cause: Internal error in CMX.

Action: Contact Oracle Support Services.


ORA-06950 No error

Cause: SQL*Net AppleTalk error codes base. This is not an error.

Action: No action required.


ORA-06951 Operating system call error

Cause: AppleTalk API received error in VMS system service.

Action: Contact Oracle Support Services.


ORA-06952 Remote end of the communication issued a forward-reset packet.

Cause: Peer program may have aborted.

Action: Investigate network problems and try again.


ORA-06953 Not enough virtual memory

Cause: Not enough memory available.

Action: Check VMS process quotas and/or SYSGEN parameters.


ORA-06954 Illegal file name

Cause: Erroneous file name.

Action: Check path name for server output file, or SQL*Net Appletalk Logical names and symbols.


ORA-06955 Number of database servers exceed limit

Cause: Too many database connections.

Action: Check ATKSRV_MAXCON parameter in configuration file.


ORA-06956 Failed to get local host name

Cause: Unable to get Appletalk host name.

Action: Check Appletalk configuration.


ORA-06957 No SID is currently available

Cause: Incoming SQL*Net connection specified invalid SID name.

Action: Specify correct SID in connect string and retry.


ORA-06958 Failed to access configuration file

Cause: Unable to access CONFIG.ATK.

Action: Check file protections.


ORA-06959 Buffer I/O quota is too small

Cause: Buffered I/O quota exceeded.

Action: Increase BIOLM using AUTHORIZE utility and retry.


ORA-06960 Failed to access log file

Cause: SQL*Net Appletalk listener could not create log file.

Action: Check directory path and protections.


ORA-06961 Insufficient privilege for attempted operation

Cause: You do not have sufficient privileges for the attempted operation.

Action: Check process privileges and retry.


ORA-06970 X.25 Driver: remote host is unknown

Cause: Host name specified in the login (connect string) is unknown.

Action: Check spelling; make sure name is in the X.25 HOST file.


ORA-06971 X.25 Driver: error while receiving data

ORA-06972 X.25 Driver: error while sending data

ORA-06973 X.25 Driver: invalid buffer size

Cause: The buffer size specified in the login string must be between 5 and 4096.

Action: Re-submit with valid buffer size.


ORA-06974 X.25 Driver: SID lookup failure

Cause: From the remote host's SQL*Net X.25 server: the database SID, specified in the login (connect) string, was not recognized.

Action: Add the appropriate SID entry to the CONFIG.ORA file on the remote host (and restart the SQL*Net X.25 server).


ORA-06975 X.25 Driver: connect to host failed

Cause: Connection attempt to remote host has failed. Probably means that the SQL*Net X.25 server on the remote host is not up, or the host itself is not up.

Action: Start the SQL*Net X.25 server process on the remote host.


ORA-06976 X.25 Driver: endpoint creation failure

Cause: Process open file quota probably exceeded.

Action: Contact Oracle Support Services.


ORA-06977 X.25 Driver: X.25 Level 2 failure

Cause: X.25 level 2 is down. X.25 link is not working.

Action: Run system checks to verify functioning of X.25 software. Contact your hardware vendor.


ORA-06978 X.25 Driver: Too many callback tries

Cause: Call back address probably same as called address.

Action: Verify that the callback address and called address are different.


ORA-06979 X.25 Driver: server cannot start oracle

Cause: The remote X.25 server was unable to start an Oracle process on behalf of the client.

Action: Make sure permissions on the remote Oracle program are correctly set. Contact your system administrator.


ORA-07200 slsid: oracle_sid not set.

Cause: The environment variable $(ORACLE_SID) is not set.

Action: Set ORACLE_SID environment variable.


ORA-07201 slhom: oracle_home variable not set in environment.

Cause: $(ORACLE_HOME) environment variable not set.

Action: Set ORACLE_HOME.


ORA-07202 sltln: invalid parameter to sltln.

Cause: The SLTLN name translation routine was called with invalid arguments. The input, or output stings were either NULL or 0 length.

Action: Probable internal Oracle error. Contact Oracle Support Services.


ORA-07203 sltln: attempt to translate a long environment variable.

Cause: A string was passed to SLTLN containing a long environment variable. SLTLN accepts environment names of 30 or less characters.

Action: Shorten environment variable name to less than 30 characters.


ORA-07204 sltln: name translation failed due to lack of output buffer space.

Cause: The SLTLN routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred.

Action: Possible internal error. Check output buffer length stored in sercose[0]. Path names are limited to 255 characters.


ORA-07205 slgtd: time error, unable to obtain time.

Cause: Time() system call returned an error. Possible operating system error.

Action: Check additional information returned. Contact Oracle Support Services.


ORA-07206 slgtd: gettimeofday error, unable to obtain time.

Cause: GETTIMEOFDAY() system call returned an error. Possible operating system error.

Action: Check additional information returned. Contact Oracle Support Services.


ORA-07207 sigpidu: process ID string overflows internal buffer.

Cause: The SIGPIDU routine is given a maximum length buffer to hold process ID string. An overflow of this buffer occurred. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07208 sfwfb: failed to flush dirty buffers to disk.

Cause: The FSYNC system call returned an error. Possible operating system error.

Action: Check additional information returned. Contact Oracle Support Services.


ORA-07209 sfofi: file size limit was exceeded.

Cause: The size of the file to be opened exceeded the operating system limit imposed on this process.

Action: Run OSH to increase the file size limit.


ORA-07210 slcpu: getrusage error, unable to get cpu time.

Cause: GETRUSAGE system call returned an error. Possible operating system error.

Action: Check additional information returned. Contact Oracle Support Services.


ORA-07211 slgcs: gettimeofday error, unable to get wall clock.

Cause: GETTIMEOFDAY system call returned an error. Possible operating system error.

Action: Check additional information returned in the operating system reference manual. Contact Oracle Support Services.


ORA-07212 slcpu: times error, unable to get cpu time.

Cause: The times system call returned an error. Possible operating system error.

Action: Check additional information returned. Contact Oracle Support Services.


ORA-07213 slgcs: times error, unable to get wall clock.

Cause: Times system call returned an error. Possible operating system error.

Action: Check additional information returned in the operating system reference manual. Contact Oracle Support Services.


ORA-07214 slgunm: uname error, unable to get system information.

Cause: UNAME system call returned an error. Possible operating system error.

Action: Check additional information returned in the operating system reference manual. Contact Oracle Support Services.


ORA-07215 slsget: getrusage error.

Cause: GETRUSAGE system call returned an error. Possible operating system error.

Action: Check additional information returned. Look for information in the operating system reference manual. Contact Oracle Support Services.


ORA-07216 slghst: gethostname error, unable to get name of current host.

Cause: GETHOSTNAME system call returned an error. Possible operating system error.

Action: Check additional information returned in the operating system reference manual. Contact Oracle Support Services.


ORA-07217 sltln: environment variable cannot be evaluated.

Cause: GETENV call returned a null pointer.

Action: Set the environment variable and try again.


ORA-07218 slkhst: could not perform host operation

Cause: UNIX system() call failed.

Action: Examine system error message.


ORA-07219 slspool: unable to allocate spooler argument buffer.

Cause: MALLOC failed to allocate space to hold spooler arguments.

Action: Check additional information returned in the operating system reference manual. The process may have run out of heap space. Contact Oracle Support Services.


ORA-07220 slspool: wait error.

Cause: Wait returned an error, when waiting for spool job to complete. Possible spooler program error.

Action: Check additional information returned. Refer to the operating system reference manual. Contact Oracle Support Services.


ORA-07221 slspool: exec error, unable to start spooler program.

Cause: Exec failed when starting line printer spooler command. Likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set.

Action: Verify default line printer command and ORACLE_LPPROG are set correctly. Set ORACLE_LPPROG to working line printer spooler.


ORA-07222 slspool: line printer spooler command exited with an error.

Cause: The line printer spooler exited with a non-zero return value. This probably indicates an error in spooling file.

Action: Verify that line printer spooler is up. Verify that ORACLE_LPPROG, and ORACLE_LPARG are set properly. Check exit value returned as additional information.


ORA-07223 slspool: fork error, unable to spawn spool process.

Cause: Fork system call failed to create additional process. Probable resource limit reached.

Action: Check additional information returned. Retry operation. Contact system administrator.


ORA-07224 sfnfy: failed to obtain file size limit; errno = string.

Cause: The ULIMIT system call returned an error.

Action: Check errno and contact Oracle Support Services.


ORA-07225 sldext: translation error, unable to expand file name.

Cause: Additional information returned is error returned from SLTLN.

Action: Check additional information.


ORA-07226 rtneco: unable to get terminal mode.

Cause: The IOCTL call returned an error. Possible operating system error.

Action: Check additional information for errno. Contact Oracle Support Services.


ORA-07227 rtneco: unable to set noecho mode.

Cause: The IOCTL call returned an error. Possible operating system error.

Action: Check additional information for errno. Contact Oracle Support Services.


ORA-07228 rtecho: unable to restore terminal to echo mode.

Cause: The IOCTL call returned an error. Possible operating system error.

Action: Check additional information for errno. Contact Oracle Support Services.


ORA-07229 slcpuc: error in getting number of CPUs.

Cause: Error in MPCNTL system call.

Action: Examine errno. Contact your system administrator.


ORA-07230 slemcr: fopen error, unable to open error file.

Cause: FOPEN failed to open file.

Action: Try to determine which file was not opened. Check that file exists and is accessible.


ORA-07231 slemcc: invalid file handle, seals do not match.

Cause: Function was called with an invalid argument. The file handle used was not obtained be SLEMCR. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07232 slemcc: fclose error.

Cause: An error was encountered when closing the file. Possible operating system error.

Action: Contact system administrator.


ORA-07233 slemcw: invalid file handle, seals do not match.

Cause: Function was called with an invalid file handle. File handle was not obtained by SLEMCR. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07234 slemcw: fseek error.

Cause: Unable to seek to desired position in file. Possible operating system error. Possible internal error.

Action: Verify that error message file is intact. Try to regenerate error message file. Contact Oracle Support Services.


ORA-07235 slemcw: fwrite error.

Cause: Unable to write item to file. Possible operating system error. Possible permissions problem.

Action: Retry operation.


ORA-07236 slemop: open error.

Cause: Unable to open error file. Possible permissions problem.

Action: Verify permission on error message file. Check additional information for errno.


ORA-07237 slemcl: invalid file handle, seals do not match.

Cause: Function was called with an invalid file handle. Handle was not obtained by previous call to SLEMOP. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07238 slemcl: close error.

Cause: Unable to close file. Possible operating system error.

Action: Contact system administrator. Check additional information for errno.


ORA-07239 slemrd: invalid file handle, seals do not match.

Cause: Function was called with invalid file handle. Handle was not obtained by call to SLEMOP. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07240 slemrd: seek error.

Cause: Unable to seek to desired position in file. Possible operating system error.

Action: Check that error file is still intact. Verify space on device. Contact system administrator. Check additional information for errno.


ORA-07241 slemrd: read error.

Cause: Unable to read file. Possible operating system error.

Action: Verify that error file is intact. Regenerate error message file. Contact Oracle Support Services. Check additional information for errno.


ORA-07242 slembfn: translation error, unable to translate error file name.

Cause: Additional information indicates error returned from SLTLN.

Action: Check additional information.


ORA-07243 supplied buffer not big enough to hold entire line

Cause: The supplied buffer was not big enough. This is an internal error.

Action: Contact Oracle Support Services. Additional information indicates how big the supplied buffer was.


ORA-07244 ssfccf: create file failed, file size limit reached.

Cause: An attempt was made to create a file that exceeds the process's file size limit.

Action: Run OSH to raise the file size limit.


ORA-07245 sfccf: unable to lseek and write the last block.

Cause: An attempt was made to move and write to a bad device address.

Action: Check errno. Possible lack of space on device.


ORA-07246 sfofi: open error, unable to open database file.

Cause: SFOFI returns an error. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07247 sfrfb: read error, unable to read requested block from database file.

Cause: SFRFB returns an error. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07248 sfwfb: write error, unable to write database block.

Cause: SFWFB returns an error. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07249 slsget: open error, unable to open /proc/pid.

Cause: OPEN() returns an error.

Action: Check that /proc has the right permissions.


ORA-07250 spcre: semget error, unable to get first semaphore set.

Cause: An error occurred when trying to get first semaphore set.

Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.


ORA-07251 spcre: semget error, could not allocate any semaphores.

Cause: SEMGET failed to even allocate a single semaphore. Either they are all in use or the system is not configured to have any semaphores.

Action: Check to see if all semaphores are in use. Check to see if system is configured to have semaphores. Check errno.


ORA-07252 spcre: semget error, could not allocate semaphores.

Cause: SEMGET system call returned an error. Possible resource limit problem.

Action: Check errno. Verify that enough semaphores are available in system. If additional errors occur in destroying the semaphore sets then sercose[0] will be non-zero. If this occurs, remove the semaphore sets using IPCRM.


ORA-07253 spdes: semctl error, unable to destroy semaphore set.

Cause: SEMCTL system call returned an error.

Action: Check semaphore sets. May require manual cleanup. Check additional information returned. Consult operating system reference manual.


ORA-07254 spdcr: translation error while expanding ?/bin/oracle.

Cause: An error occurred while translating the name of the Oracle executable.

Action: Check sercose[0] for error returned from SLTLN. Perhaps $(ORACLE_HOME) is not set correctly.


ORA-07255 spini: cannot set up signal handler.

Cause: System failed to set up signal handler.

Action: Check errno and sercose[0] for the signal number that failed.


ORA-07256 sptrap: cannot set up signal handler to catch exceptions.

Cause: System failed to set up signal handler to catch exceptions.

Action: Check errno and sercose[0] for the signal number that failed.


ORA-07257 spdcr: translation error expanding program name.

Cause: Error occurred when expanding program name ora_PNAME_@. The result of this translation is put in argv[0] of Oracle process.

Action: Check error returned by SLTLN returned in sercose[0].


ORA-07258 spdcr: fork error, unable to create process.

Cause: An error occurred when creating a new process.

Action: Check errno. Perhaps a system limit on the number of processes has been exceeded.


ORA-07259 spdcr: exec error, detached process failed in startup.

Cause: An Oracle detached process died shortly after startup. Wait() indicated that a child process terminated.

Action: Check ?/dbs directory for trace or core files. Check errno.


ORA-07260 spdcr: wait error.

Cause: Wait system call returned an error.

Action: Check errno.


ORA-07261 spdde: kill error, unable to send signal to process.

Cause: Kill system call returned an error. Possibly an attempt to destroy an already gone process.

Action: Check errno.


ORA-07262 sptpa: sptpa called with invalid process id.

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-07263 sptpa: kill error.

Cause: Kill system call returned an error. Possible operating system error.

Action: Check errno. Additional information indicates the process ID tested.


ORA-07264 spwat: semop error, unable to decrement semaphore.

Cause: SEMOP system call returned an error. Semaphore set may not exist.

Action: Check errno. Semaphore ID is returned in sercose[0]. Verify semaphore set exists. A possible cause for this error is that a SHUTDOWN ABORT was done while this process was running.


ORA-07265 sppst: semop error, unable to increment semaphore.

Cause: SEMOP system call returned an error. Semaphore set may not exist.

Action: Check errno. Semaphore ID is returned in sercose[0]. Check semaphore set existence. A possible cause for this error is that a SHUTDOWN ABORT was done while this process was running.


ORA-07266 sppst: invalid process number passed to sppst.

Cause: Function was passed an invalid Oracle process ID. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07267 spwat: invalid process number.

Cause: Function was passed an invalid Oracle process ID. This is an internal error.

Action: Additional information indicates the invalid process ID. Contact Oracle Support Services.


ORA-07268 szguns: getpwuid error.

Cause: GETPWUID() could not find an entry in the passwd file for a user.

Action: Add an entry for the user in the passwd file.


ORA-07269 spdcr: detached process died after exec.

Cause: Detached process successfully executed, but died shortly thereafter. Additional information indicates exit code, and termination status.

Action: Check termination code for information as to why process exited. Check for core dump or trace file.


ORA-07270 spalck: setitimer error, unable to set interval timer.

Cause: An error occurred while trying to set an interval timer. Probable porting problem.

Action: Check errno.


ORA-07271 spwat: invalid oracle process number.

Cause: Function was called with an invalid Oracle process number (0).

Action: Internal Oracle error.


ORA-07272 spwat: invalid semaphore set id.

Cause: Semaphore ID fetched from SGA was not initialized to valid value. Additional information returned is semaphore set index, and Oracle process number. This is an internal error.

Action: Check semaphore set index. Check Oracle process number.


ORA-07273 sppst: invalid semaphore id.

Cause: Semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index, and Oracle process number. This is an internal error.

Action: Check semaphore set index. Check Oracle process number.


ORA-07274 spdcr: access error, access to oracle denied.

Cause: Unable to access Oracle program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable.

Action: Check errno returned.


ORA-07275 unable to send signal to process

Cause: The kill system call returned an error. Possibly an attempt to signal a process which does not exist.

Action: Check errno.


ORA-07276 no dba group in /etc/group.

Cause: A group has not been set up for dba users.

Action: Contact system administrator. Set up dba group in /ETC/GROUP.


ORA-07277 spdde: illegal pid passed as argument.

Cause: A 0 PID was passed to SPDDE. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07278 splon: ops$username exceeds buffer length.

Cause: SPLON constructed an OPS$USERNAME logon which exceeded the allocated buffer space.

Action: Use a shorter UNIX username, or use an Oracle username. Contact Oracle Support Services.


ORA-07279 spcre: semget error, unable to get first semaphore set.

Cause: An error occurred when trying to get first semaphore set.

Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.


ORA-07280 slsget: unable to get process information.

Cause: The IOCTL call returned an error. Possible operating system error.

Action: Check additional information for errno. Contact Oracle Support Services.


ORA-07281 slsget: times error, unable to get cpu time.

Cause: Times system call returned an error. Possible operating system error.

Action: Check additional information returned. Contact Oracle Support Services.


ORA-07282 sksaprd: string overflow.

Cause: The internal buffer is not big enough to hold the archive control string.

Action: Internal restriction. Try a shorter archive control string.


ORA-07283 sksaprd: invalid volume size for archive destination.

Cause: An invalid volume size was specified.

Action: Specify a valid volume size in archive control string.


ORA-07284 sksaprd: volume size specification not terminated properly.

Cause: Some non-numeric text follows the volume size specification.

Action: Enter a correct archive control string.


ORA-07285 sksaprd: volume size should not be specified for a disk file.

Cause: Volume size was specified for a disk file.

Action: If you are archiving to a disk file, do not specify its volume size.


ORA-07286 sksagdi: cannot obtain device information.

Cause: STAT on the log archiving device failed.

Action: Check the returned OSD error for the reason of failure.


ORA-07287 sksagdi: unsupported device for log archiving.

Cause: Log archiving to this device is unsupported.

Action: Try log archiving to a supported device.


ORA-07290 sksagdi: specified directory for archiving does not exist.

Cause: The specified path name is not a directory.

Action: Verify that the archive destination directory exists.


ORA-07303 ksmcsg: illegal database buffer size.

Cause: The database buffer size must be a multiple of the database block size, and less than the maximum block size.

Action: Verify that the DB_BLOCK_SIZE initialization parameter is set properly in your initialization parameter file.


ORA-07304 ksmcsg: illegal redo buffer size.

Cause: The redo buffer size must be a multiple of machine block size.

Action: Verify that the LOG_BUFFER initialization parameter is set properly in your initialization parameter file.


ORA-07305 ksmcsg: illegal database buffer size.

Cause: The database buffer size must be a multiple of the extended cache mapping size for indirect data buffers to be used.

Action: Verify that the DB_BLOCK_SIZE initialization parameter is set properly in your initialization parameter file, or disable the USE_INDIRECT_DATA_BUFFERS initialization parameter.


ORA-07324 smpall: malloc error while allocating pga.

Cause: MALLOC library routine returned an error.

Action: Check errno. Possibly out of swap space.


ORA-07327 smpdal: attempt to destroy pga when it was not mapped.

Cause: SMPDAL was called when the PGA had not been previously created. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07339 spcre: maximum number of semaphore sets exceeded.

Cause: The internal buffer is not big enough to hold the number of semaphore set identifiers requested.

Action: Reconfigure operating system to have more semaphores per set.


ORA-07345 The datafile name must not contain the string '..'.

Cause: The specified datafile name contains '..'.

Action: Correct the datafile name and retry the operation.


ORA-07390 sftopn: translate error, unable to translate file name.

Cause: An error occurred while expanding the file name to open. Additional information returns error generated in translation routine.

Action: Look up additional error code for further information.


ORA-07391 sftopn: fopen error, unable to open text file.

Cause: FOPEN library routine returned an error.

Action: Verify existence and permissions.


ORA-07392 sftcls: fclose error, unable to close text file.

Cause: FCLOSE library routine returned an error.

Action: Possible internal Oracle error.


ORA-07393 unable to delete text file

Cause: An error occurred while deleting a text file.

Action: Verify that the file exists and check additional errors.


ORA-07394 unable to append string to text file

Cause: An error occurred while performing a string put operation.

Action: This is an internal error. Check additional information.


ORA-07400 slemtr: translated name for the message file is too long.

Cause: The name for the message file overflows internal buffer.

Action: Try making the complete path-name of the message file shorter by reorganizing the directory hierarchy.


ORA-07401 sptrap: cannot restore user exception handlers.

Cause: The system failed to restore user exception handlers.

Action: Check errno and sercose[0] for the signal number that failed.


ORA-07402 sprst: cannot restore user signal handler.

Cause: The system failed to restore user signal handlers.

Action: Check errno and sercose[0] for the signal number that failed.


ORA-07403 sfanfy: db_writers parameter not valid.

Cause: The DB_WRITERS initialization parameter in your initialization parameter file exceeds the system-dependent maximum or is less than 0.

Action: Change the DB_WRITERS initialization parameter in your initialization parameter file.


ORA-07404 sfareq: Timeout occurred waiting for request to complete.

Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running.

Action: Check all database writer trace files. Shut down the database and try to warm start.


ORA-07406 slbtpd: invalid number.

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.


ORA-07407 slbtpd: invalid exponent.

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.


ORA-07408 slbtpd: overflow while converting to packed decimal.

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.


ORA-07409 slpdtb: invalid packed decimal nibble.

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.


ORA-07410 slpdtb: number too large for supplied buffer.

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.


ORA-07411 slgfn: full path name too big for supplied buffer.

Cause: The supplied buffer is not big enough to hold the full path name.

Action: The construction of the full path name cannot be performed.


ORA-07412 sfaslv: Error getting entry in asynchronous write array.

Cause: One of the database writer processes could not locate its entry in the SGA.

Action: Contact Oracle Support Services.


ORA-07415 slpath: allocation of memory buffer failed.

Cause: MALLOC() failed to allocate buffer for storing ORACLE_PATH.

Action: System has run out of heap space. Additional information indicates errno.


ORA-07416 slpath: pathname construction failed; lack of output buffer space.

Cause: The SLPATH routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. This may be an internal error.

Action: Check output buffer length stored in sercose[0] and constructed path name length in sercose[1].


ORA-07417 sfareq: One or more database writers not active.

Cause: One or more of the database writer processes is no longer running.

Action: Check the trace files for the database writers. Shut down the database and try to warm start.


ORA-07418 sfareq: Database writer got error in timing function.

Cause: An error occurred when the database writer called the system timing function.

Action: Check the database writer trace file. Shut down the database and try to warm start.


ORA-07419 sfareq: Database writer got error in timing function.

Cause: An error occurred when the database writer called the system timing function.

Action: Check the database writer trace file. Shut down the database and try to warm start.


ORA-07425 sdpri: error string in translating dump file location.

Cause: An Oracle error occurred when translating the location of the dump file.

Action: Check the Oracle error code.


ORA-07426 spstp: cannot obtain the location of dbs directory.

Cause: An Oracle error occurred when translating the location of the DBS directory.

Action: Check additional information for the error returned from SLTLN.


ORA-07427 spstp: cannot change directory to dbs.

Cause: CHDIR system call returned an error. Possible permission problems.

Action: Check additional information for the operating system error code.


ORA-07431 fork failed

Cause: The server process was unable to fork a child process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.


ORA-07432 unable to perform nested sleep

Cause: An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability.

Action: Try the SLEEP command when the process is not sleeping.


ORA-07440 WMON process terminated with error

Cause: The wakeup monitor process died.

Action: Warm start instance.


ORA-07441 function address must be aligned on string byte boundary

Cause: An improperly aligned function address was specified.

Action: Use a properly aligned function address.


ORA-07442 function address must be in the range string to string

Cause: An invalid function address was specified.

Action: Use a valid function address.


ORA-07443 function string not found

Cause: An invalid function name was specified.

Action: Use a valid function name.


ORA-07444 function address string is not readable

Cause: An invalid function name/address was specified.

Action: Use a valid function name/address.


ORA-07445 exception encountered: core dump [string] [string] [string] [string] [string] [string]

Cause: An operating system exception occurred which should result in the creation of a core file. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07446 sdnfy: bad value 'string' for parameter string.

Cause: The directory specified as the value for the stated parameter could not be used.

Action: Make sure the directory you have specified is a valid directory/file specification.


ORA-07447 ssarena: usinit failed.

Cause: Oracle failed to create a shared arena file.

Action: Use SERCERRNO field to determine cause of failure.


ORA-07448 ssarena: maximum number of shared arenas exceeded.

Cause: Oracle attempted to create more shared arena files than permitted.

Action: Raise the value for MAX_ARENA in INIT.ORA.


ORA-07449 sc: usnewlock failed.

Cause: Oracle failed to acquire a shared arena lock.

Action: Check result code in SERCERRNO to determine the cause of failure.


ORA-07451 slskstat: unable to obtain load information.

Cause: KSTAT library returned an error. Possible operating system failure.

Action: Check result code in sercose[0] for more information.


ORA-07452 specified resource manager plan does not exist in the data dictionary

Cause: User tried to load a resource manager plan that does not exist.

Action: Use a resource manager plan that exists in the data dictionary.


ORA-07453 requested resource manager plan schema does not contain OTHER_GROUPS

Cause: User tried to load a resource manager plan schema that does not contain the OTHER_GROUPS group.

Action: Use a resource manager plan schema that contains the OTHER_GROUPS group.


ORA-07454 queue timeout, string second(s), exceeded

Cause: User session queued for longer than maximum specified queue duration time for consumer group.

Action: Re-submit the job at a later time or increase queue timeout.


ORA-07455 estimated execution time (string secs), exceeds limit (string secs)

Cause: User attempted to execute an operation whose estimated execution time exceeds the limit specified for the consumer group.

Action: Execute job on behalf of another group, or increase the limit.


ORA-07456 cannot set RESOURCE_MANAGER_PLAN when database is closed

Cause: An attempt was made to turn on the Resource Manager when the database was closed.

Action: Open the database and try again.


ORA-07468 spwat: mset error, unable to set semaphore.

Cause: The MSET routine returned an error. Semaphore may not exist.

Action: Check result code in SERCERRNO. Semaphore number returned in sercose[0].


ORA-07469 sppst: mclear error, unable to clear semaphore.

Cause: The MCLEAR routine returned an error. Semaphore may not exist.

Action: Check result code in SERCERRNO. Semaphore number returned in sercose[0].


ORA-07470 snclget: cannot get cluster number.

Cause: The CLUSTER_STATUS system call failed to get status information for the current cluster.

Action: Check result code in sercose[0]. Possible operating system failure.


ORA-07471 snclrd: name translation error of sgadef.dbf file name.

Cause: Unable to expand out ?/dbs/sgadef@.dbf file name.

Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check error number returned from SLTLN in sercose[0].


ORA-07472 snclrd: open error when opening sgadef.dbf file.

Cause: Open failed when opening the file ?/dbs/sgadef@.dbf.

Action: Check errno. Possible permission problem. Verify that the file ?/dbs/sgadef@.dbf exists.


ORA-07473 snclrd: read error when trying to read sgadef.dbf file.

Cause: Read had an error when reading SGADEF.DBF file.

Action: Check errno. Verify file exists, and is correct size.


ORA-07474 snclrd: close error, unable to close sgadef.dbf file.

Cause: An error occurred in close, while closing the file ?/dbs/sgadef@.dbf.

Action: Check errno. Possible operating system error.


ORA-07475 slsget: cannot get vm statistics.

Cause: The VM_STATISTICS system call failed to get virtual memory statistics.

Action: Check result code in SERCERRNO. Possible operating system failure.


ORA-07476 slsget: cannot get mapped memory statistics.

Cause: The VM_MAPMEM system call failed to get mapped memory statistics.

Action: Check result code in SERCERRNO. Possible operating system failure.


ORA-07477 scgcmn: lock manager not initialized.

Cause: Lock manager must be initialized before converting locks.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07478 scgcmn: cannot get lock status.

Cause: LM_STAT_LOCK failed.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07479 scgcmn: cannot open or convert lock.

Cause: LM_OPEN or LM_OPEN_CONVERT failed.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07480 snchmod: cannot change permissions on ?/dbs/sgalm.dbf.

Cause: When creating an instance, SNLMINI could not change the permissions on ?/dbs/sgalm.dbf.

Action: Contact Oracle Support Services.


ORA-07481 snlmatt: cannot attach to lock manager instance.

Cause: LM_ATTACH failed to attach to Lock Manager instance.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07482 snlmini: cannot create lock manager instance.

Cause: LM_CREATE failed to create Lock Manager instance.

Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if it exists, then retry.


ORA-07483 snlkget: cannot convert(get) lock.

Cause: LM_CONVERT failed to convert(get) lock.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07484 snlkput: cannot convert(put) lock.

Cause: LM_CONVERT failed to put lock value.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07485 scg_get_inst: cannot open instance number lock.

Cause: LM_OPEN failed.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07486 scg_get_inst: cannot convert(get) instance number lock.

Cause: LM_CONVERT failed to get lock value.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07487 scg_init_lm: cannot create lock manager instance.

Cause: LM_CREATE failed.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07488 scgrcl: lock manager not initialized.

Cause: Lock manager must be initialized before releasing locks.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07489 scgrcl: cannot get lock status.

Cause: LM_STAT_LOCK failed during lock release/cancel.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07490 scgrcl: cannot convert lock.

Cause: LM_CONVERT failed during lock release/cancel.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07491 scgrcl: cannot cancel lock request.

Cause: LM_CANCEL failed during lock release/cancel.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07492 scgrcl: cannot close lock.

Cause: LM_CLOSE failed during lock release/cancel.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07493 scgrcl: lock manager error.

Cause: An error was encountered releasing the lock.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07494 scgcm: unexpected error.

Cause: Unknown or unexpected error code.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07495 spwat: lm_wait failed.

Cause: LM_WAIT failed.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07496 sppst: lm_post failed.

Cause: LM_POST failed.

Action: Check result code in SERCERRNO. Possible Lock Manager failure.


ORA-07497 sdpri: cannot create trace file 'string'; errno = string.

Cause:

  1. The trace file could not be created for writing.
  2. The trace file is a symbolic link.

Action:

  1. Check if the dump directory exists and whether it is writable.
  2. Remove the symbolic link.

ORA-07498 spstp: Unable to open /dev/resched.

Cause: The rescheduling driver /dev/resched is not found or is not working properly.

Action: Check installation of the Oracle rescheduling driver in the AIX kernel.


ORA-07499 spglk: Cannot reschedule.

Cause: The rescheduling driver /dev/resched is not open. This is an internal error and should not occur.

Action: Contact Oracle Support Services.


 

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)

Part Number A96525-01
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback


 

Go to previous page Go to next page

7
ORA-07500 to ORA-09857


ORA-07500 scglaa: $cantim unexpected return

Cause: VMS system service $CANTIM returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07501 scgtoa: $deq unexpected return

Cause: VMS system service $DEQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07502 scgcmn: $enq unexpected return

Cause: VMS system service $ENQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07503 scgcmn: $setimr unexpected return

Cause: VMS system service $SETIMR returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07504 scgcmn: $hiber unexpected return

Cause: VMS system service $HIBER returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07505 scggt: $enq parent lock unexpected return

Cause: VMS system service $ENQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07506 scgrl: $deq unexpected return on lockid string

Cause: VMS system service $DEQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07507 scgcm: unexpected lock status condition

Cause: A global locking system service returned an unexpected value.

Action: Check for system error message (if any) and refer to VMS documentation, or contact Oracle Support Services.


ORA-07508 scgfal: $deq all unexpected return

Cause: VMS system service $DEQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07509 scgfal: $deq parent lock unexpected return

Cause: VMS system service $DEQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07510 scgbrm: $getlki unexpected return on lockid string

Cause: VMS system service $GETLKI returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07511 sscggtl: $enq unexpected return for master termination lock

Cause: VMS system service $ENQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07512 sscggtl: $enq unexpected return for client termination lock

Cause: VMS system service $ENQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07513 sscgctl: $deq unexpected return on cancel of term. lock

Cause: VMS system service $DEQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07514 scgcan: $deq unexpected return while canceling lock

Cause: VMS system service $DEQ returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07534 scginq: $getlki unexpected return on lockid string

Cause: VMS system service $GETLKI returned an unexpected value.

Action: Check for system error message and refer to VMS documentation.


ORA-07548 sftopn: Maximum number of files already open

Cause: Too many test files open. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07549 sftopn: $OPEN failure

Cause: VMS system service $OPEN failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07550 sftopn: $CONNECT failure

Cause: VMS system service $CONNECT failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07551 sftcls: $CLOSE failure

Cause: VMS system service $CLOSE failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07552 sftget: $GET failure

Cause: VMS system service $GET failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07561 szprv: $IDTOASC failure

Cause: VMS system service $IDTOASC failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07562 sldext: extension must be 3 characters

Cause: An extension was found but it is of improper length. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07563 sldext: $PARSE failure

Cause: VMS system service $PARSE failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07564 sldext: wildcard in filename or extension

Cause: A wildcard was used in the file name.

Action: Re-enter the file name completely.


ORA-07565 sldext: $SEARCH failure

Cause: VMS system service $SEARCH failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07568 slspool: $OPEN failure

Cause: VMS system service $OPEN failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07569 slspool: $CLOSE failure

Cause: VMS system service $CLOSE failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07570 szrfc: $IDTOASC failure

Cause: VMS system service $IDTOASC failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07571 szrfc: $FIND_HELD failure

Cause: VMS system service $FIND_HELD failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07572 szrfc: insufficient rolename buffer space

Cause: An OS role name was too long.

Action: Re-define the role name to be of correct length.


ORA-07573 slkhst: could not perform host operation

Cause: VMS system service LIB$SPAWN failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07574 szrfc: $GETUAI failure

Cause: VMS system service $GETUAI failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07576 sspexst: $GETJPIW failure on process ID string

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07577 no such user in authorization file

Cause: An attempt was made to set an INTERNAL password (for either DBA or OPER privilege), but the corresponding VMS account (either ORA_sid_DBA or ORA_sid_OPER) has not been created yet.

Action: Add a VMS account for ORA_sid_DBA and/or ORA_sid_OPER before trying to set a password for them.


ORA-07578 szprv: $FIND_HELD failure

Cause: VMS system service $FIND_HELD failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07579 spini: $DCLEXH failure

Cause: VMS system service $DCLEXH failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07580 spstp: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07581 spstp: cannot derive SID from unexpected process name

Cause: A background process did not have name of correct form.

Action: If the job name was changed, restore it. Otherwise, this is an internal error; report it to Oracle Support Services.


ORA-07582 spstp: ORA_SID has illegal value

Cause: The ORA_SID must exist and be less than 6 characters.

Action: Consult the VMS Installation guide for information on setting the SID.


ORA-07584 spdcr: invalid value for ORA_sid_(proc_)PQL$_item

Cause: A logical name used to set a detached process quota value has an invalid value (probably non-numeric).

Action: Examine the values of these logical names, correct the one in error, and retry.


ORA-07585 spdcr: $PARSE failure

Cause: VMS system service $PARSE failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07586 spdcr: $SEARCH failure

Cause: VMS system service $SEARCH failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07587 spdcr: $CREPRC failure

Cause: VMS system service $CREPRC failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07588 spdcr: $GETJPIW get image name failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07589 spdde: system ID not set

Cause: The logical name ORA_SID does not translate to a valid value.

Action: Check the value of ORA_SID in the process that gets the error, and correct the installation or command procedures that caused ORA_SID to be set incorrectly.


ORA-07590 spdde: $DELPRC failure

Cause: VMS system service $DELPRC failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07591 spdde: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07592 sspgprv: Error obtaining required privileges

Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07593 ssprprv: Error release privileges

Cause: While releasing privileges, an error was returned from SYS$SETPRV. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07594 spiip: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07595 sppid: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07596 sptpa: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07597 spguns: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07598 spwat: $SETIMR failure

Cause: VMS system service $SETIMR failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07599 spwat: $SCHDWK failure

Cause: VMS system service $SCHDWK failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07600 slkmnm: $GETSYIW failure

Cause: VMS system service $GETSYIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07601 spguno: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07602 spgto: $GETJPIW failure

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07605 szprv: $ASCTOID failure

Cause: VMS system service $ASCTOID failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07606 szprv: $CHKPRO failure

Cause: VMS system service $CHKPRO failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07607 szaud: $SNDOPR failure

Cause: VMS system service $SNDOPR failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07608 szprv: $GETUAI failure

Cause: VMS system service $GETUAI failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07609 szprv: $HASH_PASSWORD failure

Cause: VMS system service $HASH_PASSWORD failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07610 $GETJPIW failed in retrieving the user's MAC priviledges

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07612 $GETUAI failed in retrieving the user's clearance level

Cause: VMS system service $GETUAI failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07613 $GETJPIW failed in retrieving the user's process label

Cause: VMS system service $GETJPIW failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07614 $CHANGE_CLASS failed in retrieving the user's process label

Cause: VMS system service $CHANGE_CLASS failed.

Action: Examine system error message and refer to SEVMS documentation.


ORA-07615 $CHANGE_CLASS failed in retrieving the specified file label

Cause: VMS system service $CHANGE_CLASSS failed.

Action: Examine system error message and refer to SEVMS documentation.


ORA-07616 $CHANGE_CLASS failed in retrieving the specified device label

Cause: VMS system service $CHANGE_CLASS failed.

Action: Examine system error message and refer to SEVMS documentation.


ORA-07617 $FORMAT_CLASS failed translating the binary label to a string

Cause: VMS system service $FORMAT_CLASS failed because the given binary classification was not valid.

Action: Examine system error message and refer to SEVMS documentation.


ORA-07618 $IDTOASC failed translating a secrecy level

Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy level.

Action: Define the entry in the rights database which the binary label you specified references.


ORA-07619 $IDTOASC failed translating an integrity level

Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity level.

Action: Define the entry in the rights database which the binary label you specified references.


ORA-07620 smscre: illegal database block size

Cause: An illegal database block size was specified in the parameter file. It must be positive, a multiple of 512, and less than the maximum physical i/o data size.

Action: Change DB_BLOCK_SIZE in the parameter file to conform to these limits.


ORA-07621 smscre: illegal redo block size

Cause: An illegal redo log buffer size was specified in the parameter file. It must be positive and a multiple of 512.

Action: Change LOG_BUFFER in the parameter file to conform to these limits.


ORA-07622 smscre: $CREATE failure

Cause: While creating the system global area (SGA) backing file, VMS system service $CREATE failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07623 smscre: $CRMPSC failure

Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07624 smsdes: $DGBLSC failure

Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07625 smsget: $MGBLSC failure

Cause: While mapping the system global area (SGA) during logon, VMS system service $MGBLSC failed. The usual reason is that Oracle has not been started up.

Action: Examine the system error message and refer to VMS documentation. Start Oracle if it is not already started.


ORA-07626 smsget: sga already mapped

Cause: An attempt to map the SGA during logon failed because it was already mapped. This is an internal error.

Action: Exit your program and try again, and report this to Oracle Support Services.


ORA-07627 smsfre: $CRETVA failure

Cause: While unmapping the system global area (SGA) during logoff, VMS system service $CRETVA failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07628 smsfre: sga not mapped

Cause: An attempt to unmap the SGA during logoff failed because it was not mapped. This is an internal error.

Action: Exit your program and try again, and report this to Oracle Support Services.


ORA-07629 smpall: $EXPREG failure

Cause: While extending the program global area (PGA), VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded.

Action: Examine the system error message and refer to VMS documentation.


ORA-07630 smpdal: $DELTVA failure

Cause: While deleting the program global area (PGA) during logoff, VMS system service $DELTVA failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07631 smcacx: $EXPREG failure

Cause: While creating or extending a context area, VMS system service $EXPREG failed. This often happens when the virtual memory page count quota is exceeded.

Action: Examine the system error message and refer to VMS documentation.


ORA-07632 smsrcx: $DELTVA failure

Cause: While deleting a context area, VMS system service $DELTVA failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07633 smsdbp: illegal protection value

Cause: The buffer debug function was called with an illegal value. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07634 smsdbp: $CRETVA failure

Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed.

Action: Contact Oracle Support Services.


ORA-07635 smsdbp: $SETPRT failure

Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed.

Action: Contact Oracle Support Services.


ORA-07636 smsdbp: $MGBLSC failure

Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed.

Action: Contact Oracle Support Services.


ORA-07637 smsdbp: buffer protect option not specified when sga created

Cause: An attempt was made to change the buffer protect mode when the SGA was not created with buffer protect debug option. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07638 smsget: SGA pad area not large enough for created SGA

Cause: An attempt was made to map an SGA with software in which the SGA pad area is not large enough.

Action: Create a smaller SGA, or relink the software with a larger pad.


ORA-07639 smscre: SGA pad area not large enough (string bytes required)

Cause: An attempt was made to create an SGA with software in which the SGA pad area is not large enough.

Action: Create a smaller SGA, or relink the software with a larger pad.


ORA-07640 smsget: SGA not yet valid. Initialization in progress

Cause: An attempt was made to map to the SGA while it was being initialized.

Action: Wait until initialization is complete, and try again.


ORA-07641 smscre: Unable to use the system pagefile for the SGA

Cause: The system global area (SGA) backing file could not be allocated using the system pagefile because the system-wide limit on global pages has been exceeded.

Action: Either increase the VMS system parameter GBLPAGFIL or use a disk file as the SGA backing file.


ORA-07642 smprtset: $CMKRNL failure

Cause: While attempting to set the protection of a region of memory, an error was returned from the $CMKRNL system service.

Action: Examine the system error message and refer to VMS documentation.


ORA-07643 smsalo: SMSVAR is invalid

Cause: This is an internal error.

Action: Report this error to Oracle Support Services; provide your initialization parameter file.


ORA-07645 sszfsl: $CHANGE_CLASS failure

Cause: While attempting to set the label on a file, SEVMS service $CHANGE_CLASS failed.

Action: Examine the system message and refer to SEVMS system documentation.


ORA-07646 sszfck: $CREATE failure

Cause: While attempting to create a file, VMS system service $CREATE failed.

Action: Examine the system message and refer to VMS system documentation.


ORA-07647 sszfck: $OPEN failure

Cause: While attempting to reopen a file, VMS system service $OPEN failed.

Action: Examine the system message and refer to VMS system documentation.


ORA-07650 sigunc: $GETJPIW failure

Cause: While attempting to get the user's terminal device name, user name, user program name, or process name during logon, VMS system service $GETJPIW failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07655 slsprom:$TRNLOG failure

Cause: While attempting to translate SYS$INPUT during a prompt for a password, VMS system service $TRNLOG failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07656 slsprom:$GETDVI failure

Cause: While attempting to get device characteristics during a prompt for a password, VMS system service $GETDVI failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07657 slsprom:$ASSIGN failure

Cause: While prompting for a password, VMS system service $ASSIGN failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07658 slsprom:$QIOW read failure

Cause: While prompting for a password, VMS system service $QIOW failed.

Action: Examine the system error message and refer to VMS documentation.


ORA-07665 ssrexhd: recursive exception encountered string string string string string string

Cause: A VMS exception occurred while executing in the Oracle exception handler. The message includes the signal number, first and second signal arguments, and exception PC, PSL and R0. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07670 $IDTOASC failed translating a secrecy category

Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of a secrecy category.

Action: Define the entry in the rights database which the binary label you specified references.


ORA-07671 $IDTOASC failed translating an integrity category

Cause: VMS system service $IDTOASC failed while looking up the string representation in the rights database of an integrity category.

Action: Define the entry in the rights database which the binary label you specified references.


ORA-07672 $PARSE_CLASS failed translating the string into a binary label

Cause: SEVMS system service $PARSE_CLASS failed because the given string did not represent a valid classification.

Action: Examine system error message and refer to SEVMS documentation.


ORA-07680 sou2os: another call to ORACLE currently executing

Cause: A call to the Oracle shared image entry point occurred from within the shared image. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07681 sou2os: An error occurred while initializing Oracle

Cause: While attempting to set up the dispatch vectors for the shared image, an error occurred. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07682 sou2os: set kernel dispatch fail err

Cause: During Oracle shared image entry, a dispatch to kernel mode failed.

Action: Make sure that your shared image is installed with the CMKRNL privilege, then contact Oracle Support Services.


ORA-07683 sou2os: $SETPRV reset error

Cause: During an attempt to restore user privileges at Oracle shared image exit, VMS system service $SETPRV failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07684 sou2os: supervisor stack reset error

Cause: During an attempt to restore the supervisor-mode stack at Oracle shared image exit, VMS system service $SETSTK failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07685 sou2os: supervisor stack set error

Cause: During an attempt to set the Oracle supervisor-mode stack at Oracle shared image entry, VMS system service $SETSTK failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07700 sksarch: interrupt received

Cause: An interrupt was received while archiving the logs.

Action: Retry the operation.


ORA-07701 sksatln: internal exception: output buffer too small

Cause: Overflow of buffer for parsing archive control text string. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07702 unrecognized device type in archive text

Cause: Unrecognized device type in archive text. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07703 error in archive text: need '/' after device type

Cause: The archive control text in the ARCHIVE command is invalid; the device type (to indicate a file or tape) must be followed by a '/'.

Action: Refer to the Oracle9i User-Managed Backup and Recovery Guide for the proper syntax of the text.


ORA-07704 error in archive text: need ':' after device name

Cause: The archive control text in the ARCHIVE command is invalid; the device name must be followed by a ':'.

Action: Refer to the Oracle9i User-Managed Backup and Recovery Guide for the proper syntax of the text.


ORA-07705 sksaprs: device name buffer too small

Cause: The buffer supplied for the device name is too small. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07706 error in archive text: need disk file name

Cause: The archive control text in the ARCHIVE command is invalid; the disk file name is missing.

Action: Refer to the Oracle9i User-Managed Backup and Recovery Guide for the proper syntax of the text.


ORA-07707 error in archive text: need tape label name

Cause: The archive control text in the ARCHIVE command is invalid; the tape label name is missing.

Action: Refer to the Oracle9i User-Managed Backup and Recovery Guide for the proper syntax of the text.


ORA-07708 sksaprs: tape label name buffer too small

Cause: The buffer supplied for the tape label is too small. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07709 sksaprs: archiving to a remote host is not allowed

Cause: The user specified a remote disk for archiving via DECnet.

Action: Archive to a disk on the local host.


ORA-07710 sksaprs: file name buffer too small

Cause: The buffer supplied for the file name is too small. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07713 sksamtd: could not mount archival device (SYS$MOUNT failure)

Cause: VMS system service SYS$MOUNT failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07715 sksadtd: could not dismount archival device (SYS$DISMNT failure)

Cause: VMS system service SYS$DISMNT failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07716 sksachk: invalid device specification for ARCHIVE

Cause: VMS system service SYS$GETDVI failed".

Action: Specify a valid device in ARCHIVE control string.


ORA-07717 sksaalo: error allocating memory

Cause: VMS system service LIB$GET_VM failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07718 sksafre: error freeing memory

Cause: VMS system service LIB$FREE_VM failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07721 scgcm: not enough OS resource to obtain system enqueue

Cause: A call to SYS$ENQ returned an error indicating that the operating system lacked the resources necessary to create a lock. This is caused by the messages SS$_EXENQLM or SS$_INSFMEM.

Action: Free up some of the required resource to allow the creation of the required lock.


ORA-07740 slemop: incorrect handle size (programming error)

Cause: Structures used for reading error message files do not match. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07741 slemop: $OPEN failure

Cause: VMS system service $OPEN failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07742 slemop: $CONNECT failure

Cause: VMS system service $CONNECT failed.

Action: Examine system error message and refer to VMS documentation.


ORA-07743 slemop: incorrect error file attributes

Cause: An error message file is of incorrect format.

Action: Unless an error file has been changed, report this to Oracle.


ORA-07744 slemcl: invalid error message file handle

Cause: Seal in passed in handle does not match correct value. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07745 slemcl: $CLOSE failure

Cause: VMS system service $CLOSE failed.

Action: Check system error and refer to VMS documentation.


ORA-07746 slemrd: invalid error message file handle

Cause: seal in passed in handle does not match correct value. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07747 slemrd: $READ failure

Cause: VMS system service $READ failed.

Action: Check system error and refer to VMS documentation.


ORA-07750 slemcr: fopen failure

Cause: An attempt to create a message file failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07751 slemcr: malloc failure

Cause: An attempt to allocate a cache for a newly-created message file failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07753 slemcf: fseek before write failure

Cause: An attempt to seek before writing a message file cache element failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07754 slemcf: fwrite failure

Cause: An attempt to write a message file cache element failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07755 slemcf: fseek before read failure

Cause: An attempt to seek before reading a message file cache element failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07756 slemcf: fread failure

Cause: An attempt to read a message file cache element failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07757 slemcc: invalid handle

Cause: The seal in a passed-in handle does not match correct value. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07758 slemcw: invalid handle

Cause: The seal in a passed-in handle does not match correct value. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07759 slemtr: invalid destination

Cause: The destination string provided to the function is too short. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07760 slemtr: $open failure

Cause: The $open service failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07800 slbtpd: invalid number

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.


ORA-07801 slbtpd: invalid exponent

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.


ORA-07802 slbtpd: overflow while converting to packed decimal

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.


ORA-07803 slpdtb: invalid packed decimal nibble

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.


ORA-07804 slpdtb: number too large for supplied buffer

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.


ORA-07820 sspscn: SYS$CRELNM failure

Cause: An error was returned from the SYS$CRELNM function.

Action: Check system error and refer to VMS documentation.


ORA-07821 sspsdn: SYS$DELLNM failure

Cause: An error was returned from the SYS$DELLNM function.

Action: Check system error and refer to VMS documentation.


ORA-07822 sspscm: SYS$CREMBX failure

Cause: An error was returned from the SYS$CREMBX function while trying to create the process dump mailbox.

Action: Check system error and refer to VMS documentation.


ORA-07823 sspsqr: $QIO failure

Cause: An error was returned from $QIO while trying to queue a read to the process dump mailbox.

Action: Check system error and refer to VMS documentation.


ORA-07824 sspain: $SETIMR failure

Cause: An error was returned from SYS$SETIMR while trying to queue a process spin-watch timer.

Action: Check system error and refer to VMS documentation.


ORA-07825 sspsck: $QIO failure at AST level

Cause: An error was returned from SYS$QIO while trying to read the process dump mailbox.

Action: Check system error and refer to VMS documentation.


ORA-07826 sspscm: SYS$GETDVIW failure

Cause: An error was returned from SYS$GETDVIW while trying to get information about the process dump mailbox.

Action: Check system error and refer to VMS documentation.


ORA-07840 sllfop: LIB$GET_VM failure

Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for an I/O vector.

Action: Check system error and refer to VMS documentation.


ORA-07841 sllfop: SYS$OPEN failure

Cause: An error was returned from SYS$OPEN while attempting to open the datafile for reading.

Action: Check system error and refer to VMS documentation.


ORA-07842 sllfcl: SYS$CLOSE failure

Cause: An error was returned from SYS$CLOSE while attempting to close the input datafile.

Action: Check system error and refer to VMS documentation.


ORA-07843 sllfcl: LIB$FREE_VM failure

Cause: An error was returned from LIB$FREE_VM while attempting to free the memory for the I/O vector.

Action: Check system error and refer to VMS documentation.


ORA-07844 sllfop: LIB$GET_VM failure

Cause: An error was returned from LIB$GET_VM while attempting to allocate memory for data and index buffers.

Action: Check system error and refer to VMS documentation.


ORA-07845 sllfcl: LIB$FREE_VM failue

Cause: An error was returned from LIB$FREE_VM while attempting to free memory used by data and index buffers.

Action: Check system error and refer to VMS documentation.


ORA-07846 sllfop: string byte record too big for string byte user buffer

Cause: The longest record in the file will not fit into the largest data buffer that can be allocated.

Action: Modify the RMS file to have smaller records.


ORA-07847 sllfop: $CONNECT failure

Cause: An error was returned by SYS$CONNECT while attempting to open the datafile.

Action: Check system error and refer to VMS documentation.


ORA-07848 sllfrb: $GET failure

Cause: An error was returned by SYS$GET while attempting to read the datafile.

Action: Check system error and refer to VMS documentation.


ORA-07849 sllfsk: $GET failure

Cause: An error was returned by SYS$GET while attempting to skip records in the input file.

Action: Check system error and refer to VMS documentation.


ORA-07850 sllfop: bad option

Cause: You are using a bad option to loader Fixed= is one legal option. Check documentation for others.

Action: Check documentation.


ORA-07860 osnsoi: error setting up interrupt handler

Cause: An error occurred while setting up the control interrupt handler. This is an internal error.

Action: Contact Oracle Support Services.


ORA-07880 sdopnf: internal error

Cause: A list of all files open by this process could not be obtained. This is an internal error.

Action: Contact Oracle Support Services.


ORA-08000 maximum number of session sequence lists exceeded

Cause: The sequence parent state objects for this session are all used. This is an internal error.

Action: Quit the session and begin a new one.


ORA-08001 maximum number of sequences per session exceeded

Cause: The limit on the number of sequences usable by session has been hit.

Action: Increase initialization parameter USER_SEQUENCES to get more.


ORA-08002 sequence string.CURRVAL is not yet defined in this session

Cause: Sequence CURRVAL has been selected before sequence NEXTVAL.

Action: Select NEXTVAL from the sequence before selecting CURRVAL.


ORA-08003 sequence string.NEXTVAL exceeds internal limits

Cause: The sequence was created with unsafe values for some of the parameters. The calculation of NEXTVAL cannot be made because it exceeds the legal representation size.

Action: Alter or re-create the sequence number with legal limits.


ORA-08004 sequence string.NEXTVAL string stringVALUE and cannot be instantiated

Cause: Instantiating NEXTVAL would violate one of MAX/MINVALUE.

Action: Alter the sequence so that a new value can be requested.


ORA-08005 specified row does not exist

Cause: A row with the given ROWID does not exist in any of the tables given.

Action: Check the query for misspellings of table names and the ROWID.


ORA-08006 specified row no longer exists

Cause: The row has been deleted by another user since the operation began.

Action: Retry the operation.


ORA-08008 another instance is mounted with USE_ROW_ENQUEUES = string

Cause: The shared instance being started does not have the same value for USE_ROW_ENQUEUES as already running instances.

Action: Ensure that all instances' INIT.ORA files specify the same value for the parameter USE_ROW_ENQUEUES.


ORA-08100 index is not valid - see trace file for diagnostics

Cause: Validate Index detected an inconsistency in its argument index.

Action: Send trace file to Oracle Support Services.


ORA-08101 index key does not exist root dba string, dba string (string)

Cause: This is an internal error; possible inconsistency in index.

Action: Send trace file to Oracle Support Services, along with information on reproducing the error.


ORA-08102 index key not found, obj# string, dba string (string)

Cause: This is an internal error; possible inconsistency in index.

Action: Send trace file to Oracle Support Services, along with information on reproducing the error.


ORA-08103 object no longer exists

Cause: The object has been deleted by another user since the operation began.

Action: Remove references to the object.


ORA-08104 this index object string is being online built or rebuilt

Cause: The index is being created or rebuild or waited for recovering from the online (re)build.

Action: Wait the online index build or recovery to complete.


ORA-08105 Oracle event to turn off smon cleanup for online index build

Cause: Set this event only under the supervision of Oracle development.

Action: Debugging only.


ORA-08106 can not create journal table string.string

Cause: Online index builder cannot create its journal table.

Action: Rename your table in conflict.


ORA-08108 may not build or rebuild this type of index online

Cause: Only support normal index or IOT top-level index.

Action: Change your index type.


ORA-08109 nosort is not a supported option for online index build

Cause: May not specify NOSORT for online index build.

Action: Get rid of NOSORT in the index creation command.


ORA-08110 Oracle event to test SMON cleanup for online index build

Cause: Oracle Kernel test only.

Action: Do not set this event (for test only).


ORA-08111 a partitioned index may not be coalesced as a whole

Cause: User attempted to coalesce a partitioned index using ALTER INDEX COALESCE statement, which is illegal.

Action: Coalesce the index a (sub)partition at a time (using ALTER INDEX MODIFY (sub)PARTITION COALESCE).


ORA-08112 a composite partition may not be coalesced as a whole

Cause: User attempted to coalesce a composite partition.

Action: Coalesce the index a subpartition at a time (using ALTER INDEX MODIFY SUBPARTITION COALESCE).


ORA-08113 composite partition index may not be compressed

Cause: User attempted to compress a composite partition index.

Action: Create uncompressed composite partition index.


ORA-08114 can not alter a fake index

Cause: An attempt was made to alter a fake index.

Action: Drop the fake index.


ORA-08115 can not online create/rebuild this index type

Cause: User attempted to create index type that online does not support.

Action: Use offline index create/rebuild command.


ORA-08116 can not acquire DML enough lock(S mode) for online index build

Cause: User attempted to create index online without allowing DML Share lock.

Action: Allow DML share lock on the base table.


ORA-08117 Index Organized Table operation released its block pin

Cause: Block maintenance forced the release of a block pin.

Action: Contact Oracle Support Services.


ORA-08118 Deferred FK constraints cannot be enforced, index too big (string)

Cause: Deferred Foreign Key constraints cannot be enforced due to the index key being too big and built on a non-default DB_BLOCK_SIZE.

Action: First try to drop the Foreign Key and then the primary key.


ORA-08119 The new initrans will make the index too big

Cause: The specified initrans needs additional space to hold the index key, which might make the index too big.

Action: Try specifying a smaller initrans value.


ORA-08175 discrete transaction restriction violated (string)

Cause: An attempt was made to perform an action that is not currently supported in a discrete transaction.

Action: Roll back the transaction, and retry it as a normal transaction.


ORA-08176 consistent read failure; rollback data not available

Cause: Encountered data changed by an operation that does not generate rollback data: create index, direct load or discrete transaction.

Action: In read/write transactions, retry the intended operation. Read-only transactions must be restarted.


ORA-08177 can't serialize access for this transaction

Cause: Encountered data changed by an operation that occurred after the start of this serializable transaction.

Action: In read/write transactions, retry the intended operation or transaction.


ORA-08178 illegal SERIALIZABLE clause specified for user INTERNAL

Cause: Serializable mode is not supported for user INTERNAL.

Action: Reconnect as another user and retry the SET TRANSACTION command.


ORA-08179 concurrency check failed

Cause: Encountered data changed by an operation that occurred after a specific snapshot. This is usually used to indicate that a particular cached copy of a data block is stale. This is used for internal use for now.

Action: Refresh the cached copy of the data block and retry operation.


ORA-08180 no snapshot found based on specified time

Cause: Could not match the time to an SCN from the mapping table.

Action: Try using a larger time.


ORA-08181 specified number is not a valid system change number

Cause: The supplied scn was beyond the bounds of a valid scn.

Action: Use a valid scn.


ORA-08182 operation not supported while in Flashback mode

Cause: User tried to do DML or DDL while in Flashback mode.

Action: Disable Flashback and re-attempt the operation.


ORA-08183 Flashback cannot be enabled in the middle of a transaction.

Cause: User tried to do Flashback in the middle of a transaction.

Action: Issue a COMMIT statement.


ORA-08184 attempting to re-enable Flashback while in Flashback mode

Cause: An attempt was made to re-enable Flashback while in Flashback mode.

Action: Disable Flashback before re-enabling Flashback mode.


ORA-08185 Flashback not supported for user SYS.

Cause: User logged in as SYS.

Action: Log in as a different user.


ORA-08186 invalid timestamp specified

Cause: An invalid timestamp was specified.

Action: Enter a valid timestamp.


ORA-08187 snapshot expression not allowed here

Cause: A snapshot expression using AS OF was specified when not allowed.

Action: Do not use the AS OF clause.


ORA-08205 ora_addr: $ORACLE_SID not set in environment

Cause: The environment variable ORACLE_SID is not set.

Action: Set the ORACLE_SID environment variable.


ORA-08206 ora_addr: cannot translate address file name

Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf.

Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set.


ORA-08207 ora_addr: cannot open address file

Cause: The address file could not be opened.

Action: Check that Oracle is up. Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and has correct permissions.


ORA-08208 ora_addr: cannot read from address file

Cause: The address file could not be read.

Action: Check that the file $(ORACLE_HOME)/dbs/sgadef$(ORACLE_SID).dbf exists and contains a single line of text.


ORA-08209 scngrs: SCN not yet initialized

Cause: The System Commit Number has not yet been initialized.

Action: Contact Oracle Support Services.


ORA-08210 Requested I/O error

Cause: Oracle requested that an I/O error be returned for this operation.

Action: This should not occur in normal Oracle operation. Contact support.


ORA-08230 smscre: failed to allocate SGA

Cause: The N_CORE system call failed, maybe due to insufficient memory.

Action: Specify a smaller number of buffers. Check INIT.ORA parameters.


ORA-08231 smscre: unable to attach to SGA

Cause: The process cannot attach to the SGA. This can happen if either the listener cannot attach, or the process cannot communicate with the listener.

Action: Verify that the instance is up and running. Contact Oracle Support Services.


ORA-08232 smsdes: cannot detach from SGA

Cause: Probably the listener process has died.

Action: Contact Oracle Support Services.


ORA-08233 smsdes: cannot unmap SGA

Cause: The N_CORE system call failed while detaching from the SGA.

Action: Note NCX error returned; contact Oracle Support Services.


ORA-08234 smsget: cannot get instance listener address

Cause: The instance listener address cannot be read from the SGADEF file.

Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Additional information gives error return from ORA_ADDR.


ORA-08235 smsget: listener not on this node

Cause: A process wishing to attach to the SGA is on a different node from its instance's listener.

Action: Verify $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Contact Oracle Support Services.


ORA-08236 smsget: cannot share subcube with listener

Cause: The N_SHARE call failed, probably because the listener has died.

Action: Check if the listener is running, and contact Oracle Support Services.


ORA-08237 smsget: SGA region not yet created

Cause: An attempt was made to attach to an SGA which has not yet been created.

Action: Verify that the instance is running. Contact Oracle Support Services.


ORA-08238 smsfre: cannot detach from SGA

Cause: The N_CORE system call failed while detaching from the SGA.

Action: Check NCX error, and contact Oracle Support Services.


ORA-08260 ora_addr: cannot open nameserver

Cause: A process could not connect to the name server.

Action: Make sure the name server is up and running. Additional information gives name server's returned status.


ORA-08261 ora_addr: cannot find name in nameserver

Cause: The listener name server entry for an instance could not be found.

Action: Make sure the name server is up and running. Additional information gives name server's returned status.


ORA-08263 ora_addr: cannot free listener address

Cause: The listener name server entry could not be freed.

Action: Additional information gives name server's returned status. Contact Oracle Support Services.


ORA-08264 ora_addr: cannot close nameserver

Cause: The connection to the name server could not be closed.

Action: Additional information gives name server's returned status. Contact Oracle Support Services.


ORA-08265 create_ora_addr: cannot open nameserver

Cause: A process could not connect to the name server.

Action: Make sure the name server is up and running. Additional information gives name server's returned status.


ORA-08266 create_ora_addr: cannot register name in nameserver

Cause: The listener's addressing information could not be registered.

Action: Make sure the name server is up and running. Additional information gives name server's returned status.


ORA-08267 destroy_ora_addr: cannot close nameserver

Cause: The connection to the name server could not be closed.

Action: Additional information gives name server's returned status. Contact Oracle Support Services.


ORA-08268 create_ora_addr: cannot close nameserver

Cause: The connection to the name server could not be closed.

Action: Additional information gives name server's returned status. Contact Oracle Support Services.


ORA-08269 destroy_ora_addr: cannot destroy name

Cause: The listener's addressing information could not be removed.

Action: Additional information gives name server's returned status. Contact Oracle Support Services.


ORA-08270 sksachk: Illegal archival control string

Cause: Archive files cannot be created with the given archival control string.

Action: Check that the volume exists.


ORA-08271 sksabln: Buffer size not large enough for archive control string

Cause: The given archival control string expands into too many characters.

Action: Reduce archive control string length.


ORA-08274 Out of memory for environment variable

Cause: There is insufficient memory to return the requested value.

Action: Reduce memory usage and retry.


ORA-08275 Environment variable unset

Cause: The requested environment variable is not set.

Action: Ensure that the variable name requested is correct.


ORA-08276 No room in nameserver for pid

Cause: There is no room to record the PID for a background process.

Action: SHUTDOWN ABORT and restart the database.


ORA-08277 Cannot set environment variable

Cause: There is insufficient memory to expand the environment.

Action: Reduce memory usage and retry.


ORA-08278 Cannot get CPU statistics

Cause: Could not retrieve CPU times because N_STAT failed.

Action: Contact Oracle Support Services.


ORA-08308 sllfop: Cannot open file

Cause: Oracle could not open a file.

Action: Check the UNIX errno returned as additional information.


ORA-08309 sllfop: Cannot fstat file

Cause: Oracle could not obtain information about an open file.

Action: Check the UNIX errno returned as additional information.


ORA-08310 sllfop: Bad value for recsize

Cause: An illegal value for the record size was specified.

Action: Specify a value for the RECSIZE option that is greater than 0.


ORA-08311 sllfop: bad value for maxrecsize

Cause: An illegal value for the maximum record size was specified.

Action: Specify a value for the MAXRECSIZE option that is greater than 0.


ORA-08312 sllfop: unrecognized processing option

Cause: An unrecognized processing option was specified.

Action: Check the Oracle for nCUBE 2 Installation and User's Guide for valid options.


ORA-08313 sllfop: could not allocate buffers

Cause: Memory for the load buffers could not be allocated.

Action: Reduce the maximum record size. Eliminate any unnecessary processes on your current node before running SQL*Loader again.


ORA-08314 sllfcf: Error closing file

Cause: An error occurred trying to close a file.

Action: Check the UNIX errno returned as additional information.


ORA-08315 sllfrb: Error reading file

Cause: An error occurred trying to read from a file.

Action: Check the UNIX errno returned as additional information.


ORA-08316 sllfsk: Error seeking in file.

Cause: The LSEEK system call returned an error.

Action: Check the UNIX errno returned as additional information.


ORA-08317 sllfsk: Error seeking in file.

Cause: The LSEEK system call returned an error.

Action: Check the UNIX errno returned as additional information.


ORA-08318 sllfsk: Error reading file

Cause: An error occurred trying to read from a file.

Action: Check the UNIX errno returned as additional information.


ORA-08319 sllfsk: Error reading file

Cause: An error occurred trying to read from a file.

Action: Check the UNIX errno returned as additional information.


ORA-08320 scnget: Call to scnget before scnset or scnfnd.

Cause: This is an internal error

Action: Contact Oracle Support Services.


ORA-08321 scnmin: NOT IMPLEMENTED YET

Cause: This is an internal error

Action: Contact Oracle Support Services.


ORA-08322 scnmin: open/convert of bias lock failed

Cause: A call to the LKMGR failed to open and convert the bias lock.

Action: Check to make sure the LKMGR is up.


ORA-08323 scnmin: close of bias lock failed

Cause: A call to the LKMGR failed to close the bias lock.

Action: Check to make sure the LKMGR is up.


ORA-08330 Printing not supported

Cause: An attempt was made to automatically spool a file to the printer.

Action: No action required.


ORA-08331 Wait operation timed out

Cause: Oracle timed out waiting for an event.

Action: Contact Oracle Support Services.


ORA-08332 rollback segment #string specified not available

Cause: See ORA-01545.

Action: See ORA-1545. Also, make sure you have created enough rollback segments for the number of instances you are trying to start.


ORA-08340 This command not allowed on nCUBE, only one thread is ever used.

Cause: An illegal command was executed for the nCUBE platform.

Action: There is no need to issue this command.


ORA-08341 On nCUBE, this command can only be executed from instance 1.

Cause: A command that can only be issued on instance 1 was issued elsewhere.

Action: Log on to instance 1 and repeat the command.


ORA-08342 sropen: failed to open a redo server connection

Cause: An error occurred trying to connect to the redo server.

Action: The operating system-specific error message should tell you what to do.


ORA-08343 srclose: failed to close a redo server connection

Cause: An error occurred trying to close the redo server connection.

Action: The operating system-specific error message should tell you what to do.


ORA-08344 srapp: failed to send redo data to the redo server

Cause: An error occurred trying to send redo to the redo server.

Action: The operating system-specific error message should tell you what to do.


ORA-08401 invalid compiler name: string

Cause: An invalid compiler name comp_name was passed to a UTL_PG conversion routine.

Action: Correct the compiler name parameter in the PL/SQL code that called the conversion routine.


ORA-08412 error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message

Cause: The WMSGBSIZ is the maximum size for warning message block, it is recommended to be 1024 bytes to 8 kilobytes.

Action: Defined WMSGBLK of size between 1k to 8k bytes and update the WMSGBSIZ to the sizeof(WMSGBLK).


ORA-08413 invalid compiler type in FORMAT parameter at string

Cause: An invalid compiler type is defined in format control block. The format control block is invalid.

Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure.


ORA-08414 error encountered in string

Cause: The function routine returned an error. Where routine may be:

  • RAW_TO_NUMBER
  • NUMBER_TO_RAW
  • RAW_TO_NUMBER_FORMAT
  • NUMBER_TO_RAW_FORMAT
  • MAKE_NUMBER_TO_RAW_FORMAT
  • MAKE_RAW_TO_NUMBER_FORMAT

Action: This message will be preceded by messages providing details about the error. Check those messages to determine what action to take.


ORA-08429 raw data has invalid digit in display type data

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid data. The picture mask parameter specified a digit, but the corresponding input from the raw data did not contain a valid digit.

Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.


ORA-08430 raw data missing leading sign

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.

Action: Correct the input raw data or the mask options so that they match.


ORA-08431 raw data missing zero as defined in picture

Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained a zero, but the corresponding input from the raw data was not a zero.

Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.


ORA-08432 raw data has invalid floating point data

Cause: The input raw data passed to a UTL_PG RAW_TO_NUMBER conversion routine contained invalid floating point data.

Action: Correct the input raw data.


ORA-08433 invalid picture type in convert raw to number

Cause: The picture mask parameter passed to a UTL_PG RAW_TO_NUMBER conversion routine contained non-numeric characters, but the conversion was to a numeric data type.

Action: Correct the picture mask parameter.


ORA-08434 raw data has invalid trailing sign

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had no trailing sign, but the mask options parameter specified a trailing sign.

Action: Correct the input raw data or the mask options so that they match.


ORA-08435 PICTURE MASK missing the leading sign when SIGN IS LEADING specified

Cause: The input MASK passed to a UTL_PG RAW_TO_NUMBER conversion routine had no leading sign, but the mask options parameter specified a leading sign.

Action: Correct the input raw data or the mask options so that they match.


ORA-08436 raw data has invalid sign digit

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine had an invalid sign digit in the position where the picture mask specified a sign.

Action: Correct the input raw data or the picture mask so that they match.


ORA-08437 invalid picture type in picture mask

Cause: The picture mask parameter passed to a UTL_PG NUMBER_TO_RAW conversion routine contained non-numeric characters, but the conversion was to a numeric data type.

Action: Correct the picture mask parameter.


ORA-08440 raw buffer is too short to hold converted data

Cause: The output raw buffer passed to a UTL_PG NUMBER_TO_RAW conversion routine was not large enough to contain the results of the conversion based on the picture mask.

Action: Increase the raw buffer size to the size necessary to hold the entire result of the conversion.


ORA-08441 closed parenthesis missing in picture mask

Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine.

Action: Correct the picture mask.


ORA-08443 syntax error in BLANK WHEN ZERO clause in mask options

Cause: A syntax error was found in the BLANK WHEN ZERO clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:

  • BLANK ZERO
  • BLANK ZEROS
  • BLANK ZEROES
  • BLANK WHEN ZERO
  • BLANK WHEN ZEROS
  • BLANK WHEN ZEROES

Action: Correct the mask options parameter.


ORA-08444 syntax error in JUSTIFIED clause in mask options

Cause: A syntax error was found in the JUSTIFIED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:

  • JUST
  • JUST RIGHT
  • JUSTIFIED
  • JUSTIFIED RIGHT

Action: Correct the mask options parameter.


ORA-08445 syntax error in SIGN clause in mask options

Cause: A syntax error was found in the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:

  • SIGN LEADING
  • SIGN LEADING SEPARATE
  • SIGN LEADING SEPARATE CHARACTER
  • SIGN TRAILING
  • SIGN TRAILING SEPARATE
  • SIGN TRAILING SEPARATE CHARACTER
  • SIGN IS LEADING
  • SIGN IS LEADING SEPARATE
  • SIGN IS LEADING SEPARATE CHARACTER
  • SIGN IS TRAILING
  • SIGN IS TRAILING SEPARATE
  • SIGN IS TRAILING SEPARATE CHARACTER

Action: Correct the mask options parameter.


ORA-08446 syntax error in SYNCHRONIZED clause in mask options

Cause: A syntax error was found in the SYNCHRONIZED clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:

  • SYNC
  • SYNC LEFT
  • SYNC RIGHT
  • SYNCHRONIZED
  • SYNCHRONIZED LEFT
  • SYNCHRONIZED RIGHT

Action: Correct the mask options parameter.


ORA-08447 syntax error in USAGE clause in mask options

Cause: A syntax error was found in the USAGE clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are:

  • USAGE DISPLAY
  • USAGE COMP
  • USAGE COMP-3
  • USAGE COMP-4
  • USAGE COMPUTATIONAL
  • USAGE COMPUTATIONAL-3
  • USAGE COMPUTATIONAL-4
  • USAGE IS DISPLAY
  • USAGE IS COMP
  • USAGE IS COMP-3
  • USAGE IS COMP-4
  • USAGE IS COMPUTATIONAL
  • USAGE IS COMPUTATIONAL-3
  • USAGE IS COMPUTATIONAL-4

Action: Correct the mask options parameter.


ORA-08448 syntax error in DECIMAL-POINT environment clause

Cause: A syntax error was found in the DECIMAL-POINT environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: DECIMAL-POINT IS COMMA.

Action: Correct the environment clause parameter.


ORA-08449 invalid numeric symbol found in picture mask

Cause: An invalid numeric symbol was found in the picture mask parameter passed to a UTL_PG conversion routine.

Action: Correct the picture mask parameter.


ORA-08450 invalid specification of CR in picture mask

Cause: The CR suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The CR suffix can only appear at the end of a picture mask.

Action: Correct the picture mask parameter.


ORA-08451 invalid specification of DB in picture mask

Cause: The DB suffix was incorrectly specified in the picture mask parameter passed to a UTL_PG conversion routine. The DB suffix can only appear at the end of a picture mask.

Action: Correct the picture mask parameter.


ORA-08452 specification of E in picture mask is unsupported

Cause: The floating point exponent symbol 'E' was specified in the picture mask parameter passed to a UTL_PG conversion routine. The floating point data type is currently not supported by the UTL_PG conversion routines.

Action: Correct the picture mask parameter, and the data, if necessary.


ORA-08453 more than one V symbol specified in picture mask

Cause: The picture mask passed to a UTL_PG conversion routine contained more than one decimal point indicator ('V'). Only one decimal point indicator is allowed in the picture mask.

Action: Correct the picture mask parameter.


ORA-08454 more than one S symbol specified in picture mask

Cause: The picture mask passed to a UTL_PG conversion routine contained more than one operational sign indicator ('S'). Only one operational sign indicator is allowed in the picture mask.

Action: Correct the picture mask parameter.


ORA-08455 syntax error in CURRENCY SIGN environment clause

Cause: A syntax error was found in the CURRENCY SIGN environment clause parameter passed to a UTL_PG conversion routine. Valid specifications are: CURRENCY SIGN IS x where x is a valid currency sign.

Action: Correct the environment clause parameter.


ORA-08456 no sign in picture mask but SIGN clause in mask options

Cause: The picture mask parameter passed to a UTL_PG conversion routine contained no sign symbol ('S', '+', or '-'), but the mask options parameter contained a SIGN clause. A sign symbol is required in the picture mask parameter when the mask options parameter contains a SIGN clause.

Action: Correct the picture mask parameter or the mask options parameter.


ORA-08457 syntax error in SEPARATE CHARACTER option of SIGN clause

Cause: A syntax error was found in the SEPARATE CHARACTER option of the SIGN clause in the mask options parameter passed to a UTL_PG conversion routine. Valid specifications are: SEPARATE, SEPARATE CHARACTER.

Action: Correct the mask options parameter.


ORA-08458 invalid format parameter

Cause: The format parameter passed to a UTL_PG conversion routine was invalid. The format parameter should have been built by a prior call to either MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT.

Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure.


ORA-08459 invalid format parameter length

Cause: The format parameter passed to a UTL_PG conversion routine was not the correct length. Format parameters must be 2048 bytes in length.

Action: Check to be sure that the format parameter was built by MAKE_RAW_TO_NUMBER_FORMAT or MAKE_NUMBER_TO_RAW_FORMAT, and that it was not accidentally overwritten or modified by the PL/SQL procedure.


ORA-08460 invalid environment clause in environment parameter

Cause: The environment parameter passed to a UTL_PG conversion routine contained an unsupported or invalid environment clause. Only the CURRENCY SIGN and the DECIMAL-POINT IS COMMA environment clauses are supported.

Action: Correct the environment parameter.


ORA-08462 raw buffer contains invalid decimal data

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data.

Action: Correct the input data.


ORA-08463 overflow converting decimal number to Oracle number

Cause: The output variable passed to a UTL_PG RAW_TO_NUMBER was not large enough to hold the Oracle number resulting from the input decimal number.

Action: Be sure that the input decimal number is valid, and be sure that the output variable is large enough to hold the Oracle number value.


ORA-08464 input raw decimal data contains more than 42 digits

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contained more than 42 digits. This exceeds the maximum size of an Oracle number.

Action: Correct the raw input buffer.


ORA-08465 input mask contains more than 32 characters

Cause: The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters.

Action: Correct the mask input buffer.


ORA-08466 raw buffer length string is too short for string

Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine was less than string bytes long, but the picture mask parameter specified that string bytes of input data were to be converted.

Action: Either the input data is incorrect, or the picture mask is incorrect. Correct the appropriate item.


ORA-08467 error converting Oracle number to string

Cause: An error occurred when converting an Oracle number to a COBOL type of: DISPLAY COMP-3 or character variable. The Oracle number was not in the correct format.

Action: Correct the call to the conversion routine. The input must be a valid Oracle number variable.


ORA-08468 mask option string is not supported

Cause: The mask option clause was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The clause can be:

  • USAGE IS POINTER
  • USAGE IS INDEX
  • USAGE IS COMP-1
  • USAGE IS COMP-2 POINTER

Action: Remove the clause from the mask options parameter in the PL/SQL call to UTL_PG.


ORA-08498 Warning: picture mask 'string' overrides picture mask option 'USAGE IS string' to 'USAGE IS DISPLAY'

Cause: Picture mask USAGE option was overridden by the picture mask.

Action: This is an informational message only. The message may be eliminated by changing the USAGE option to match the picture mask.


ORA-08499 Warning: picture mask options 'string' ignored by UTL_PG

Cause: Picture mask options such as OCCUR, SYNC and others are not processed by the UTL_PG numeric conversion routines.

Action: This is an informational message only. The message may be eliminated by removing the unnecessary picture mask options from the parameter list passed to the UTL_PG routine.


ORA-09200 sfccf: error creating file

Cause: Could be out of disk space.

Action: See OSD error accompanying this message.


ORA-09201 sfcopy: error copying file

Cause: Block sizes may not match.

Action: See OSD error accompanying this message.


ORA-09202 sfifi: error identifying file

Cause: DB_BLOCK_SIZE specified in the INIT.ORA file could be incorrect.

Action: See OSD error accompanying this message.


ORA-09203 sfofi: error opening file

Cause: File attributes may have changed.

Action: See OSD error accompanying this message.


ORA-09204 sfotf: error opening temporary file

Cause: Incorrect path may have been specified for the file.

Action: See OSD error accompanying this message.


ORA-09205 sfqio: error reading or writing to disk

Cause: File may have been truncated or corrupted.

Action: See OSD error accompanying this message.


ORA-09206 sfrfb: error reading from file

Cause: File may have been truncated or corrupted.

Action: See OSD error accompanying this message.


ORA-09207 sfsrd: error reading from file

Cause: File may have been truncated or corrupted.

Action: See OSD error accompanying this message.


ORA-09208 sftcls: error closing file

Cause: File may have been corrupted.

Action: See OSD error accompanying this message.


ORA-09209 sftget: error reading from file

Cause: File may have been truncated or corrupted.

Action: See OSD error accompanying this message.


ORA-09210 sftopn: error opening file

Cause: Incorrect path may have been specified for the file.

Action: See OSD error accompanying this message.


ORA-09211 sfwfb: error writing to file

Cause: File may have been truncated or corrupted.

Action: See OSD error accompanying this message.


ORA-09212 sfwfbmt: error writing to file

Cause: File may have been truncated or corrupted.

Action: See OSD error accompanying this message.


ORA-09213 slgfn: error fabricating file name

Cause: File name may be too long.

Action: See OSD error accompanying this message.


ORA-09214 sfdone: I/O error detected

Cause: File may have been truncated or corrupted.

Action: See OSD error accompanying this message.


ORA-09215 sfqio: error detected in IOCompletionRoutine

Cause: File may have been truncated or corrupted.

Action: See OSD error accompanying this message.


ORA-09216 sdnfy: bad value 'string' for parameter string

Cause: The directory specified as the value for the stated parameter could not be used.

Action: Make sure the directory you have specified is a valid directory/file specification.


ORA-09217 sfsfs: failed to resize file

Cause: Could be out of disk space.

Action: See OSD error accompanying this message.


ORA-09218 sfrfs: failed to refresh file size

Cause: File may be corrupted or truncated.

Action: See OSD error accompanying this message.


ORA-09240 smpalo: error allocating PGA memory

Cause: Could be out of memory.

Action: See OSD error accompanying this message.


ORA-09241 smsalo: error allocating SGA memory

Cause: Could be out of memory.

Action: See OSD error accompanying this message.


ORA-09242 smscre: error creating SGA

Cause: An error occurred while creating SGA.

Action: See OSD error accompanying this message.


ORA-09243 smsget: error attaching to SGA

Cause: SGA may not have been created (database not started).

Action: See OSD error accompanying this message.


ORA-09244 smprset: error setting memory protections

Cause: An error occurred while setting memory protections.

Action: See OSD error accompanying this message.


ORA-09245 smcstk: error switching stacks

Cause: An error occurred while switching stacks.

Action: See OSD error accompanying this message.


ORA-09246 sfsmap: unable to map SGA

Cause: Unable to map SGA.

Action: See OSD error accompanying this message.


ORA-09247 smsdes: error destroying the SGA

Cause: An error occurred while destroying the SGA.

Action: See OSD error accompanying this message.


ORA-09260 sigpidu: error obtaining process id

Cause: May be out of resources.

Action: See OSD error accompanying this message.


ORA-09261 spdcr: error creating detached (background) process

Cause: Could be out of resources.

Action: See OSD error accompanying this message.


ORA-09262 spdde: error terminating detached (background) process

Cause: Could be out of resources.

Action: See OSD error accompanying this message.


ORA-09263 spini: error initializing process

Cause: Could be out of memory.

Action: See OSD error accompanying this message.


ORA-09264 sptpa: error flagging process

Cause: Could be out of resources.

Action: See OSD error accompanying this message.


ORA-09265 spwat: error temporarily suspending process

Cause: Could be out of resources.

Action: See OSD error accompanying this message.


ORA-09266 spawn: error starting an Oracle process

Cause: Could be out memory.

Action: See OSD error accompanying this message.


ORA-09270 szalloc: error allocating memory for security

Cause: Could be out of memory.

Action: See OSD error accompanying this message.


ORA-09271 szlon: error verifying user name

Cause: Username may be too long.

Action: See OSD error accompanying this message.


ORA-09272 remote os logon is not allowed

Cause: Remote operating system login attempted when not allowed.

Action: See OSD error accompanying this message.


ORA-09273 szrfc: error verifying role name

Cause: An operating system error was returned when verifying the role name.

Action: See OSD error accompanying this message.


ORA-09274 szrfc: insufficient role name buffer space

Cause: An OS role name was too long.

Action: See OSD error accompanying this message.


ORA-09275 CONNECT INTERNAL is not a valid DBA connection

Cause: CONNECT INTERNAL is no longer supported for DBA connections.

Action: Please try to connect AS SYSDBA or AS SYSOPER.


ORA-09280 sllfcf: error closing file

Cause: File may be corrupted.

Action: See OSD error accompanying this message.


ORA-09281 sllfop: error opening file

Cause: Possibly incorrect path specified to the file.

Action: See OSD error accompanying this message.


ORA-09282 sllfrb: error reading records

Cause: File could be corrupted.

Action: See OSD error accompanying this message.


ORA-09283 sllfsk: error skipping records

Cause: File could be corrupted.

Action: See OSD error accompanying this message.


ORA-09284 sllfop: cannot allocate read buffer

Cause: MALLOC() system call returned an error. The system might have run out of heap space.

Action: Check additional information for the operating system error.


ORA-09285 sllfop: unrecognizable processing option, incorrect format

Cause: Processing option passed is of incorrect format.

Action: Consult your IUG for permissible formats.


ORA-09290 sksaalo: error allocating memory for archival

Cause: Could be out of memory.

Action: See OSD error accompanying this message.


ORA-09291 sksachk: invalid device specified for archive destination

Cause: Unable to access directory.

Action: Specify a valid device in ARCHIVE control string.


ORA-09292 sksabln: unable to build archive file name

Cause: Bad directory or format specified.

Action: Specify a valid directory in LOG_ARCHIVE_FORMAT and a valid format string in LOG_ARCHIVE_FORMAT in the INIT.ORA file.


ORA-09293 sksasmo: unable to send message to console

Cause: An error was returned while attempting to send a message to the console operator.

Action: See OSD error accompanying this message.


ORA-09300 osncon: unable to connect, DPMI not available

Cause: Unable to detect the presence of DPMI.

Action: Restart Windows and retry.


ORA-09301 osncon: local kernel only supported in standard mode

Cause: An attempt was made to connect to S: while in enhanced mode.

Action: Restart Windows in standard mode.


ORA-09310 sclgt: error freeing latch

Cause: This is an internal error.

Action: See OSD error accompanying this message.


ORA-09311 slsleep: error temporarily suspending process

Cause: May be out of resources.

Action: See OSD error accompanying this message.


ORA-09312 slspool: error spooling file to printer

Cause: Could be out of resources.

Action: See OSD error accompanying this message.


ORA-09313 slsprom: error prompting user

Cause: May be out of resources.

Action: See OSD error accompanying this message.


ORA-09314 sltln: error translating logical name

Cause: Internal buffer may have overflowed.

Action: See OSD error accompanying this message.


ORA-09315 sql2tt: two-task error translating ORACLE_EXECUTABLE

Cause: This is an internal error.

Action: See OSD error accompanying this message.


ORA-09316 szrpc: unable to verify password for role

Cause: OS roles may not be supported for this platform.

Action: See OSD error accompanying this message.


ORA-09317 szprv: insufficient privileges

Cause: The password specified is invalid.

Action: See OSD error accompanying this message.


ORA-09318 slkhst: unable to host out to operating system

Cause: There might not be enough memory for the command or hosting out may not be supported on this platform.

Action: See OSD error accompanying this message.


ORA-09319 slgtd: unable to obtain the current date and time

Cause: The system time might be set incorrectly.

Action: See OSD error accompanying this message.


ORA-09320 szrfc: unable to obtain the list of valid OS roles

Cause: OS roles may not be supported on this platform.

Action: See OSD error accompanying this message.


ORA-09321 slzdtb: unable to convert zoned decimal to binary

Cause: This is an internal error.

Action: See OSD error accompanying this message.


ORA-09322 slpdtb: unable to convert packed decimal to binary

Cause: This is an internal error.

Action: See OSD error accompanying this message.


ORA-09330 Session terminated internally by Oracle or by an Oracle DBA

Cause: A client workstation that is abnormally disconnected would cause Oracle to terminate that session after about a minute. This message also appears in the trace file if a SHUTDOWN ABORT is performed.

Action: No action required.


ORA-09340 Specified ORACLE_SID is either invalid or too long

Cause: ORACLE_SID must be at the most 4 alphanumeric characters.

Action: Specify an ORACLE_SID with the correct format.


ORA-09341 scumnt: unable to mount database

Cause: Another instance is currently mounting the database.

Action: Try again later.


ORA-09342 Detached process terminated by Oracle during shutdown abort

Cause: The user performed a SHUTDOWN ABORT.

Action: No action required.


ORA-09344 spsig: error signalling thread

Cause: This function may not be implemented.

Action: No action required.


ORA-09350 Windows 32-bit Two-Task driver unable to allocate context area

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09351 Windows 32-bit Two-Task driver unable to allocate shared memory

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09352 Windows 32-bit Two-Task driver unable to spawn new ORACLE task

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09353 Windows 32-bit Two-Task driver unable to open event semaphore

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09354 Windows 32-bit Two-Task driver: ORACLE task unexpectedly died

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09360 Windows 3.1 Two-Task driver unable to allocate context area

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09361 Windows 3.1 Two-Task driver unable to lock context area

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09362 Windows 3.1 Two-Task driver unable to deallocate context area

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09363 Windows 3.1 Two-Task driver invalid context area

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09364 Windows 3.1 Two-Task driver unable to create hidden window

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09365 Windows 3.1 Two-Task driver unable to destroy hidden window

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09366 Windows 3.1 Two-Task driver unable to allocate shared memory

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09367 Windows 3.1 Two-Task driver unable to deallocate shared memory

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09368 Windows 3.1 Two-Task driver unable to spawn ORACLE

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09369 Windows 3.1 Two-Task driver bad instance handle

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09370 Windows 3.1 Two-Task driver ORACLE task timed out

Cause: See OSD error accompanying this message.

Action: See OSD error accompanying this message.


ORA-09700 sclin: maximum number of latches exceeded

Cause: Oracle wants to use more latches then available.

Action: Increase the value of the initialization parameter LATCH_PAGES or decrease the amount of shared memory you are using.


ORA-09701 scnfy: maximum number of processes exceeded

Cause: The value of the PROCESSES initialization parameter was exceeded.

Action: Decrease the PROCESSES parameter and restart.


ORA-09702 sem_acquire: cannot acquire latch semaphore

Cause: The semaphore used for accessing latches could not be seized.

Action: Send trace file to Oracle Support Services, along with information on reproducing the error.


ORA-09703 sem_release: cannot release latch semaphore

Cause: The semaphore used for accessing latches could not be released.

Action: Send trace file to Oracle Support Services, along with information on reproducing the error.


ORA-09704 sstascre: ftok error in creating test and set pages.

Cause: the FTOK() library call failed in SSTASTCRE().

Action: Verify that TASDEF@.DBF file exists. If it does then this is a possible system failure. Perhaps System V compatibility is not enabled.


ORA-09705 spcre: cannot initialize latch semaphore

Cause: The semaphore used for accessing latches could not be initialized.

Action: Send trace file to Oracle Support Services, along with information on reproducing the error.


ORA-09706 slsget: get_process_stats error.

Cause: GET_PROCESS_STATS system call returned an error. Possible operating system error.

Action: Check additional information returned. Look for information in operating system reference. Contact Oracle Support Services.


ORA-09708 soacon: failed to bind socket to port.

Cause: The bind system call failed on the socket.

Action: Check additional information for operating system error. Try connecting again.


ORA-09709 soacon: failed to accept a connection.

Cause: The accept system call failed on the socket.

Action: Check additional information for operating system error. Try connecting again.


ORA-09710 soarcv: buffer overflow.

Cause: The internal buffer is not big enough to hold the message read. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09711 orasrv: archmon already connected.

Cause: An existing connection has already been made from ARCHMON to ORASRV.

Action: Stop trying to connect.


ORA-09712 orasrv: log archiver already connected.

Cause: An existing connection has already been made from log archiver to ORASRV.

Action: Stop trying to connect.


ORA-09713 Global hardware clock failure caused instance termination.

Cause: The global hardware clock used to generate the System Change Number for Oracle has failed.

Action: Check the global hardware clock.


ORA-09714 Two Task interface: cannot obtain puname

Cause: The TXIPC driver cannot obtain the name of the PU. (Possible operating system error.)

Action: Check if the PUs are named (consistent).


ORA-09715 orasrv: cannot obtain puname

Cause: ORASRV cannot obtain the name of the PU (possible operating system error).

Action: Check if the PUs are named (consistent).


ORA-09716 kslcll: Unable to fix in-flux lamport latch.

Cause: One Oracle process died while still holding a LAMPORT latch.

Action: Exit (kill) all Oracle user processes. SHUTDOWN ABORT and restart Oracle RDBMS kernel.


ORA-09717 osnsui: maximum number of user interrupt handlers exceeded.

Cause: The internal limit on the number of user interrupt handlers has been exceeded.

Action: Reduce the number of simultaneous logons or reduce the number of user interrupt handlers.


ORA-09718 osnsui: cannot set up user interrupt handler.

Cause: MALLOC() failed to allocate space to hold user interrupt handler.

Action: Possible memory resource shortage.


ORA-09719 osncui: invalid handle.

Cause: The handle passed to OSNCUI is out of the valid range.

Action: Use a valid handle.


ORA-09740 slsget: cannot get virtual memory region statistics.

Cause: The VM_REGION system call failed to get virtual memory region statistics.

Action: Check return code in SERCERRNO. Possible operating system failure.


ORA-09741 spwat: error waiting for a post.

Cause: MSG_RECEIVE system call returned an error. This is an internal error.

Action: Check return code in SERCERRNO. Port name is returned in sercose[0].


ORA-09742 sppst: error during a post.

Cause: MSG_SEND system call returned an error. This is an internal error.

Action: Check return code in SERCERRNO. Port name is returned in sercose[0].


ORA-09743 smscre: could not attach shared memory.

Cause: The MMAP or write system call returned an error. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09744 smsget: mmap returned an error.

Cause: The MMAP system call returned an error. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09745 smscre: vm_allocate error, unable to create shared memory.

Cause: Error in system call VM_ALLOCATE. Failed to create SGA as a single shared memory segment.

Action: Check result code returned in SERCERRNO. Verify that the SGA attach address is valid.


ORA-09746 smscre: shared memory attach address incorrect.

Cause: The VM_ALLOCATE system call attached the SGA at an incorrect location.

Action: Verify that the SGA attach address is valid.


ORA-09747 pw_detachPorts: server call pws_detach failed.

Cause: The call PWS_DETACH to (Oracle helper) failed.

Action: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file.


ORA-09748 pws_look_up: fork failed

Cause: The PWS_LOOK_UP call could not fork the (Oracle helper) process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.


ORA-09749 pws_look_up: port lookup failure

Cause: The PWS_LOOK_UP could not find a port to (Oracle helper).

Action: Make sure the (Oracle helper) server has been started correctly by PWS_LOOK_UP, and that the network name server is still running.


ORA-09750 pw_attachPorts: port_rename failed.

Cause: The PORT_RENAME system call failed; possible internal error.

Action: Check return code in SERCERRNO, report to Oracle Support Services.


ORA-09751 pw_attachPorts: server call pws_attach failed.

Cause: The call PWS_ATTACH to (Oracle helper) failed.

Action: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file.


ORA-09752 pw_attachPorts: port_allocate failed.

Cause: The PORT_ALLOCATE system call failed; possible resource exhaustion.

Action: Check return code in SERCERRNO, report to Oracle Support Services.


ORA-09753 spwat: invalid process number.

Cause: Function was passed an invalid Oracle process ID. This is an internal error.

Action: Additional information indicates the invalid process ID.


ORA-09754 sppst: invalid process number passed to sppst.

Cause: Function was passed an invalid Oracle process ID. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09755 osngpn: port allocation failure.

Cause: The PORT_ALLOCATE system call failed.

Action: Possible system resource shortage; check the error code in SERCERRNO.


ORA-09756 osnpns: no port in the name server.

Cause: OSNPNS could not find the given named port in the name server.

Action: Check the error code in SERCERRNO. Make sure the shadow process and network name server are still running.


ORA-09757 osnipn: port allocation failure.

Cause: The PORT_ALLOCATE system call failed.

Action: Possible system resource shortage; check the error code in SERCERRNO.


ORA-09758 osnipn: could not check port in name server.

Cause: The NETNAME_CHECK_IN call failed.

Action: Check the error code in SERCERRNO. Make sure the network name server is running.


ORA-09759 osnsbt: bad message received.

Cause: The MSG_RECEIVE system call failed, or received a bad message. This is an internal error.

Action: Report the error code returned in SERCERRNO.


ORA-09760 osnpui: cannot send break message

Cause: The Pipe driver could not send a break message to the Oracle shadow process break thread.

Action: Contact Oracle Support Services.


ORA-09761 pw_destroyPorts: server call pws_stop_instance failed.

Cause: The call PWS_STOP_INSTANCE to (Oracle helper) failed.

Action: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file.


ORA-09762 sNeXT_instanceName: translation error.

Cause: A failure was detected while translating the value of ORACLE_SID.

Action: Make sure ORACLE_SID is defined, and that it is of legal length.


ORA-09763 osnmpx: send/receive error exchanging Mach ports.

Cause: The Mach driver failed to exchange port information with the other side of the connection. Either MSG_SEND (sercose[0] == 1) or MSG_RECEIVE (sercose[0] == 2) failed.

Action: Check return code in SERCERRNO. Make sure both sides of the connection are still running.


ORA-09764 osnmop: access error on oracle executable

Cause: The Mach driver could not access the Oracle executable.

Action: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path.


ORA-09765 osnmop: fork failed

Cause: The Mach driver could not fork the Oracle shadow process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.


ORA-09766 osnmop: buffer allocation failure.

Cause: The Mach driver failed to allocate enough virtual memory space for its I/O buffers.

Action: Decrease the value of BUFFER_SIZE parameter in the Two-Task driver host string.


ORA-09767 osnmfs: bad return code from msg_send.

Cause: The MSG_SEND system call failed while flushing the Mach driver's send buffer. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09768 osnmgetmsg: could not read a message

Cause: The MSG_RECEIVE system call returned a failure code while waiting for a message in the Mach driver. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09769 osnmbr: cannot send break message

Cause: The Mach driver could not send a break message to the Oracle shadow process break thread. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09770 pws_look_up: translation failure.

Cause: The PWS_LOOK_UP routine failed to translate the name of the (Oracle helper) executable.

Action: Make sure ORACLE_SID and ORACLE_HOME are set and correct. Additional information gives the translation error code.


ORA-09771 osnmwrtbrkmsg: bad return code from msg_send.

Cause: The MSG_SEND system call failed while sending a Mach driver break. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09772 osnpmetbrkmsg: message from host had incorrect message type

Cause: The Mach driver received a message having an unrecognizable message type. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09773 osnmgetdatmsg: message from host had incorrect message type

Cause: The Mach driver received a message having an unrecognizable message type. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09774 osnmui: cannot send break message

Cause: The Mach driver could not send a break message to the Oracle shadow process break thread. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09775 osnmrs: reset protocol error

Cause: The Mach two-task driver could not reset the connection. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09776 pws_look_up: access error on (Oracle helper) executable

Cause: The PWS_LOOK_UP call could not access the (Oracle helper) executable.

Action: Check the permissions on the (Oracle helper) executable and each component of the ORACLE_HOME/bin path.


ORA-09777 osnpbr: cannot send break message

Cause: The pipe driver could not send a break message to the Oracle shadow process break thread. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09778 snynfyport: failure allocating the notify port.

Cause: The routine failed to allocate or set the task's notify port.

Action: Possible operating system error. Contact Oracle Support Services.


ORA-09779 snyGetPort: failure to allocate a port.

Cause: The PORT_ALLOCATE system call failed; system resources might be exhausted.

Action: Possible operating system error. Contact Oracle Support Services.


ORA-09786 sllfop: open error, unable to open file.

Cause: Open system call returned an error.

Action: Check errno.


ORA-09787 sllfop: unrecognizable processing option, incorrect format.

Cause: Processing option passed is of incorrect format.

Action: Consult your IUG for permissible formats.


ORA-09788 sllfrb: unable to read file.

Cause: Read system call returned an error.

Action: Check errno. Verify file exists.


ORA-09789 sllfsk: unable to read file.

Cause: Read system call returned an error.

Action: Check errno. Verify file exists.


ORA-09790 sllfcf: unable to close file.

Cause: Close system call returned an error.

Action: Check errno.


ORA-09791 slembdf: translation error, unable to translate error file name.

Cause: Additional information indicates error returned from SLTLN.

Action: Check additional information.


ORA-09792 sllfop: cannot allocate read buffer.

Cause: MALLOC system call returned an error. The system might have run out of heap space.

Action: Check additional information for the operating system error.


ORA-09793 szguns: length of user name is greater than buffer.

Cause: The length of the name of the user being looked up is longer than size of the buffer provided by the calling routine. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09794 szrbuild: length of role name is greater than buffer.

Cause: The length of the name of the role being looked up is longer than size of the buffer provided by the calling routine. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09795 szrbuild: malloc of role structure failed.

Cause: The allocation of memory for an internal structure used to hold a role descriptor failed.

Action: Check the UNIX error number for a possible operating system failure.


ORA-09796 szrbuild: malloc of role name failed.

Cause: The allocation of memory for an internal buffer used to hold the name of a role failed.

Action: Check the UNIX error number for a possible operating system failure.


ORA-09797 Failed to get O/S MAC privileges.

Cause: The operating system would not allow the retrieval of this process' privileges.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09798 Label comparison failed.

Cause: The comparison of two binary labels failed.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09799 File label retrieval failed.

Cause: Oracle was unable to get a label attached to a file.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09800 Process sensitivity label retrieval failed.

Cause: Oracle was unable to get the sensitivity label for a process.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09801 Unable to get user ID from connection

Cause: Oracle was unable to retrieve the user's ID number from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.


ORA-09802 Conversion of binary label to string failed.

Cause: Oracle was unable to convert a binary label to a string.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09803 Allocation of string buffer failed.

Cause: a buffer used to hold the name of the file for which a label was to be obtained could not be allocated.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The number of bytes that Oracle attempted to allocate is in the "Additional Information" field.


ORA-09804 Class conversion from binary to ORACLE failed.

Cause: Oracle was unable to convert a class component from binary format to Oracle format.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09805 conversion of category number to string failed.

Cause: Oracle was unable to translate a category number to its corresponding string representation failed.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The category number is contained in the "Additional information" field.


ORA-09806 Allocation of label string buffer failed.

Cause: A temporary buffer used to hold a label could not be allocated.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services. The number of bytes that Oracle attempted to allocate is in the "Additional Information" field.


ORA-09807 Conversion of label from string to binary failed.

Cause: Oracle was unable to convert the string representation of a label to binary format.

Action: Re-enter a valid label.


ORA-09808 Could not obtain user clearance.

Cause: Oracle was unable to get a user's clearance level.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09809 Unable to get user's group ID from connection

Cause: Oracle was unable to retrieve the user's group ID number from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.


ORA-09810 Unable to get process ID from connection

Cause: Oracle was unable to retrieve the user's process ID number from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.


ORA-09811 Unable to initialize package.

Cause: Oracle was unable to initialize the library used to obtain security information. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09812 Unable to get user clearance from connection

Cause: Oracle was unable to retrieve the user's operating system session clearance from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.


ORA-09813 Unable to get directory status

Cause: Oracle was unable to determine if a directory is multilevel.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.


ORA-09814 Unable to expand file name

Cause: Oracle was unable to expand the name of a file that resides in multilevel directory.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.


ORA-09815 File name buffer overflow

Cause: The buffer that Oracle uses to hold the expanded name of a too small. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09816 Unable to set effective privileges

Cause: This is an internal error.

Action: Contact Oracle Support Services.


ORA-09817 Write to audit file failed.

Cause: Oracle was unable to write an entry to the file used as the audit trail.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.


ORA-09818 Number is too large

Cause: Oracle was unable to convert a component string to a number because the number is larger than the largest possible value for an integer. The additional information field specifies the maximum.

Action: Correct the string and repeat the conversion.


ORA-09819 Number exceeds maximum legal value

Cause: the number specified for a component was greater than the maximum value allowed for that component.

Action: Change the component to a value less than the maximum and repeat the conversion. The maximum component number is contained in the "Additional information" field.


ORA-09820 Conversion of class string to numeric representation failed.

Cause: Oracle was unable to convert a class string to a number because all of the characters in the string were not numeric.

Action: Change the string to be either all numbers or all non-numeric characters and repeat the conversion.


ORA-09821 Numeric label is not valid

Cause: A label specified in Oracle numeric format was found not to be valid.

Action: Re-enter a valid label. Consult your system's encodings for valid numeric component values.


ORA-09822 Translation of audit file name failed.

Cause: Oracle was unable to translate the value of the AUDIT_TRAIL_DEST initialization parameter.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.


ORA-09823 device name is too long

Cause: The name of a device was too long to fit into an internal buffer. The additional information field contains the length of the device name. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09824 Unable to enable allowmacaccess privilege.

Cause: Oracle was not able to turn on ALLOWMACACCESS privilege so that it could do a label comparison.

Action: Check the UNIX error number. If it indicates that Oracle does not have the ALLOWMACACCESS privilege, add the ALLOWMACACCESS privilege to the potential privilege set of $ORACLE_HOME/bin/oracle using CHPRIV (1M). If the executable already has the ALLOWMACACCESS privilege, contact Oracle Support Services.


ORA-09825 Unable to disable allowmacaccess privilege.

Cause: Oracle was not able to turn off the ALLOWMACACCESS privilege after doing a label comparison. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09826 SCLIN: cannot initialize atomic latch.

Cause: System call ATOMIC_OP() return error.

Action: Check additional information in the trace file.


ORA-09827 SCLGT: atomic latch return unknown error.

Cause: System call ATOMIC_OP() return unexpected error.

Action: Check additional information in the trace file.


ORA-09828 SCLFR: atomic latch return error.

Cause: System call ATOMIC_OP() return unexpected error.

Action: Check additional information in the trace file.


ORA-09829 pw_createPorts: server call pws_start_instance failed.

Cause: The call PWS_START_INSTANCE to (Oracle helper) failed; system resources might be exhausted.

Action: Make sure the server is still active. Check the error code returned in SERCERRNO, and look for error messages in the server log file.


ORA-09830 snyAddPort: failed to perform a remote procedure call.

Cause: The MSG_RPC system call returned an error. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09831 snyStartThread: failed to build the server port set.

Cause: The routine failed to build a port set on which to listen for requests. Possible operating system failure.

Action: Contact Oracle Support Services.


ORA-09832 infoCallback: bad message format.

Cause: The routine received an incorrectly formatted request. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09833 addCallback: bad message format.

Cause: The routine received an incorrectly formatted request. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09834 snyGetPortSet: failed to collect info on a port.

Cause: The PORT_STATUS system called failed. Possible operating system error.

Action: Contact Oracle Support Services.


ORA-09835 addCallback: callback port is already in a set.

Cause: The port to be added to the callback list is already in a port set. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09836 addCallback: could not add a port to the callback set.

Cause: The PORT_SET_ADD system called failed. Possible operating system error.

Action: Contact Oracle Support Services.


ORA-09837 addCallback: could not add allocate a callback link.

Cause: The MALLOC library call failed to allocate space for a callback link. Possible operating system error.

Action: Contact Oracle Support Services.


ORA-09838 removeCallback: failure removing the callback port.

Cause: The port PORT_SET_REMOVE system call failed. Possible operating system error.

Action: Contact Oracle Support Services.


ORA-09839 removeCallback: callback port is not in the callback set.

Cause: The port to be removed to the callback list is not in the callback port set. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09840 soacon: Name translation failure.

Cause: SLTLN() could not translate the named pipe ?/dbs/mon2arch_@.

Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct.


ORA-09841 soacon: Name translation failure.

Cause: SLTLN() could not translate the named pipe ?/dbs/arch2mon_@.

Action: Make sure that the ORACLE_HOME specified for this ORACLE_SID in ORATAB is correct.


ORA-09842 soacon: Archmon unable to create named pipe.

Cause: MKNOD() failed to create named pipe ?/dbs/mon2arch_@.

Action: Your current operating system login may lack write permission for the ORACLE_HOME/dbs directory. Only USERIDs in the DBA group of a given instance can run ARCHMON for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in ORATAB.


ORA-09843 soacon: Archmon unable to create named pipe.

Cause: MKNOD() failed to create named pipe ?/dbs/arch2mon_@.

Action: Your current operating system login may lack write permission for the ORACLE_HOME/dbs directory. Only USERIDs in the dba group of a given instance can run ARCHMON for that ORACLE_SID. Make sure that the ORACLE_HOME directory is correct in ORATAB.


ORA-09844 soacon: Archmon unable to open named pipe.

Cause: OPEN() failed to open named pipe ?/dbs/mon2arch_@.

Action: Only the Oracle DBA can run ARCHMON. Make sure that your current operating system login has owner or group search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded.


ORA-09845 soacon: Archmon unable to open named pipe.

Cause: OPEN() failed to open named pipe ?/dbs/arch2mon_@.

Action: Only the Oracle DBA can run ARCHMON. Make sure that your current operating system login has owner or group search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded.


ORA-09846 soacon: ARCH unable to open named pipe.

Cause: OPEN() failed to open named pipe ?/dbs/mon2arch_@.

Action: Make sure that the operating system USERID of the currently running database has search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded.


ORA-09847 soacon: ARCH unable to open named pipe.

Cause: OPEN() failed to open named pipe ?/dbs/arch2mon_@.

Action: Make sure that the operating system USERID of the currently running database has search permission for the ORACLE_HOME/dbs directory. The maximum number of open files may have been exceeded.


ORA-09850 soacon: Archmon unable to lock named pipe.

Cause: FCNTL() failed to set write lock on named pipe ?/dbs/arch2mon_@.

Action: Make sure that ARCHMON is not already active on another terminal for this ORACLE_SID. Only one ARCHMON session is allowed at a time for a given instance.


ORA-09851 soacon: Archmon unable to lock named pipe.

Cause: FCNTL() failed to set read lock on named pipe ?/dbs/mon2arch_@.

Action: Make sure that ARCHMON is not already active on another terminal for this ORACLE_SID. Only one ARCHMON session is allowed at a time for a given instance.


ORA-09853 snyRemovePort: bad return code from request.

Cause: The request to remove a port from the callback set returned a failure code. Possible operating system error.

Action: Contact Oracle Support Services.


ORA-09854 snyPortInfo: bad return code from request.

Cause: The request to collect information on a port in the callback set returned a failure code. Possible operating system error.

Action: Contact Oracle Support Services.


ORA-09855 removeCallback: bad message format.

Cause: The routine received an incorrectly formatted request. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09856 smpalo: vm_allocate error while allocating pga.

Cause: The VM_ALLOCATE system call returned an error.

Action: Check returned error. Possibly out of system resources.


ORA-09857 smprset: vm_protect error while protecting pga.

Cause: The VM_PROTECT system call returned an error. This is an internal error.

Action: Contact Oracle Support Services.

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)

Part Number A96525-01
Go To Documentation Library
Home
Go To Product List
Book List
Go To Table Of Contents
Contents
Go To Index
Index

Master Index

Feedback


 

Go to previous page Go to next page

8
ORA-09858 to ORA-12299


ORA-09870 spini: failure initializing maximum number of open files.

Cause: ULIMIT system call returned an error.

Action: Check errno.


ORA-09871 TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.

Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages.

Action: Check additional return error for more information.


ORA-09872 TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.

Cause: CREATE() failed when trying to create the TASDEF file.

Action: Verify permissions on $(ORACLE_HOME)/dbs directory.


ORA-09873 TASDEF_OPEN: open error when opening tasdef@.dbf file.

Cause: Unable to open tasdef@.dbf file.

Action: Check errno. Possible permission problem. Verify that tasdef@.dbf file exists.


ORA-09874 TASDEF_READ: read error, unable to read tasdef@.dbf file.

Cause: Read system call returned an error when attempting to read ?/dbs/tasdef@.dbf.

Action: Check errno returned. SGADEF file may be corrupted or incompatible with Oracle version.


ORA-09875 TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.

Cause: Write call failed.

Action: Check errno returned. Possibly out of space on device.


ORA-09876 TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.

Cause: Close system call returned an error.

Action: Check errno returned. Possible operating system failure.


ORA-09877 sstascre: shmget error, unable to get a shared memory segment.

Cause: Error in SHMGET.

Action: Check errno returned. Verify that enough shared memory is available on the system.


ORA-09878 sstascre/sstasat: shmat error, unable to attach tas write page

Cause: Error in SHMAT.

Action: Check errno returned.Verify that enough shared memory is available on the system.


ORA-09879 sstascre/sstasat: shmat error, unable to attach tas read page

Cause: Error in SHMAT.

Action: Check errno returned.Verify that enough shared memory is available on the system.


ORA-09880 sstasfre/sstasdel: shmdt error, unable to detach tas write page

Cause: Error in SHMDT.

Action: Check errno returned.


ORA-09881 sstasfre/sstasdel: shmdt error, unable to detach tas read page

Cause: Error in SHMDT.

Action: Check errno returned.


ORA-09882 sstasfre/sstasdel: shmctl error, unable to remove tas shm page

Cause: Error in SHMCTL.

Action: Check errno returned.


ORA-09883 Two Task interface: oratab file does not exist

Cause: The ORATAB file does not exist.

Action: Install Oracle before you use it or re-create the ORATAB file.


ORA-09884 Two Task interface: SID doens't match current PU

Cause: You are trying to start Oracle on another PU than you configured Oracle on or there is no entry for this SID in the ORATAB file.

Action: Start Oracle with this SID on its designated PU (see the ORATAB file). Or install the new database with SID.


ORA-09885 osnTXtt: cannot create TXIPC channel

Cause: The TXIPC driver failed to create pipes for two-task communications with the Oracle shadow process.

Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table is full. Note the operating system error code and contact your system administrator.


ORA-09886 osnTXtt: translation error while expanding txipc@.trc.

Cause: Failure of sltln(txipc@.trc) while creating debug channel.

Action: Check additional return error for more information.


ORA-09887 osnTXtt: Failed to create/open debug channel.

ORA-09888 osnTXtt: txipc channel creation failed

Cause: The TXIPC driver failed to create channels for two-task communications with the Oracle shadow process.

Action: You have probably exceeded the maximum number of open file descriptors per user or the system file table operating system error code and contact your system administrator.


ORA-09889 osnTXtt: access error on oracle executable

Cause: The TXIPC driver could not access the Oracle executable.

Action: Check the permissions on the Oracle executable and each component of the ORACLE_HOME/bin path.


ORA-09890 osnTXtt: malloc failed

Cause: The TXIPX driver failed to allocate enough heap space for its context area buffers.

Action: Contact Oracle Support Services.


ORA-09908 slkmnm: gethostname returned error code.

Cause: The system call GETHOSTNAME returned an error. This is most likely an internal error.

Action: Make sure GETHOSTNAME is successful in other contexts, and if so contact Oracle Support Services.


ORA-09909 Malloc of scratch buffer failed.

Cause: Memory needed for a temporary buffer could not be allocated. The additional information field contains the number of bytes that Oracle attempted to allocate.

Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Support Services.


ORA-09910 Unable to find ORACLE password file entry for user.

Cause: No entry exists for the user in the Oracle password file.

Action: Have the database administrator install a password entry by running ORAPASSWD.


ORA-09911 Incorrect user password.

Cause: The password entered by the user was incorrect.

Action: Enter the correct password.


ORA-09912 Malloc of name buffer(s) failed.

Cause: Oracle was unable to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users.

Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Support Services.


ORA-09913 Malloc of dummy name failed.

Cause: Oracle was unable to allocate memory for the user name that is to be used in the encryption of the user's password.

Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Support Services.


ORA-09914 Unable to open the ORACLE password file.

Cause: Oracle could not open the password file for reading.

Action: Check the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running ORAPASSWD. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact Oracle Support Services.


ORA-09915 Password encryption failed.

Cause: Oracle was unable to encrypt a password. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09916 Required password was not specified.

Cause: A user attempted to connect as "internal," but did not specify a password.

Action: Connect as internal again and specify a password.


ORA-09918 Unable to get user privileges from SQL*Net

Cause: Oracle was unable to retrieve the user's privilege set from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.


ORA-09919 Unable to set label of dedicated server

Cause: Oracle was unable to set the label of the dedicated to server to the required value.

Action: Check the UNIX error number for a possible operating system error. Also, check the privileges on the Oracle executable. It should have at least ALLOWMACACCESS privilege.


ORA-09920 Unable to get sensitivity label from connection

Cause: Oracle was unable to retrieve the user's sensitivity label from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.


ORA-09921 Unable to get information label from connection

Cause: Oracle was unable to retrieve the user's information label from the SQL*Net connection.

Action: Check the UNIX error number for a possible operating system error. Also check the "additional information" field for the SQL*Net error. If there is no error, contact Oracle Support Services.


ORA-09922 Can't spawn process - background log directory not created properly

Cause: Oracle was unable to spawn a background process because the directory that will hold trace files of the background processes was not created properly.

Action: Examine the directory pointed to by the initialization parameter BACKGROUND_DUMP_DEST. Make sure that all of the following is true:

  1. The directory exists.
  2. The name indeed points to a directory, and is not a file.
  3. The directory is accessible and writable to the Oracle user.

ORA-09923 Can't spawn process - user log directory not created properly

Cause: Oracle was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly.

Action: Examine the directory pointed to by the initialization parameter USER_DUMP_DEST. Make sure that all of the following is true:

  1. The directory exists.
  2. The name indeed points to a directory, and is not a file.
  3. The directory is accessible and writable to the Oracle user.

ORA-09924 Can't spawn process - core dump directory not created properly

Cause: Oracle was unable to spawn a background process because the directory that holds the core dumps produced by Oracle processes in the event of exceptions was not created properly.

Action: Examine the directory pointed to by the initialization parameter CORE_DUMP_DEST. Make sure that all of the following is true:

  1. The directory exists.
  2. The name indeed points to a directory, and is not a file.
  3. The directory is accessible and writable to the Oracle user.

ORA-09925 Unable to create audit trail file

Cause: Oracle was not able to create the file being used to hold audit trail records.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.


ORA-09926 Unable to set effective privilege set of the server

Cause: A dedicated server was unable to set it's own privilege set.

Action: Check the privileges granted to the Oracle executable. It must have at least ALLOWMACACESS privilege.


ORA-09927 Unable to set label of server

Cause: Oracle was not able to set the label of a server to a new value.

Action: Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it has ALLOWMACACCESS privilege.


ORA-09928 Unable to restore the label of server

Cause: Oracle was unable to restore the label of the server to the value that it had before raising it to database high. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09929 GLB of two labels is invalid

Cause: The result of a greatest lower bound operation on two labels was not valid.

Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.


ORA-09930 LUB of two labels is invalid

Cause: The result of a least upper bound operation on two labels was not valid.

Action: Repeat the operation with two different labels. Consult the system encoding file for the values of valid labels.


ORA-09931 Unable to open ORACLE password file for reading

Cause: An attempt to open a password file for reading failed.

Action: Make sure that the permissions on the file have not been changed so that the Oracle user cannot open it.


ORA-09932 Close of ORACLE password file failed.

Cause: An attempt to close a password file failed.

Action: Check the UNIX error number for the specific reason.


ORA-09933 Deletion of old password file failed.

Cause: The removal of the old password file failed.

Action: Check the UNIX error number for the specific reason.


ORA-09934 Link of current password file to old failed.

Cause: Oracle was unable to create a link so that the old password file could be saved.

Action: Check the UNIX error number for the specific reason.


ORA-09935 Unlink of current password file failed.

Cause: Oracle was unable to complete the saving of the current password file.

Action: Check the UNIX error number for the specific reason.


ORA-09936 Open of ORACLE password file for write failed.

Cause: Oracle was unable to create a password file.

Action: Check the UNIX error number for the specific reason.


ORA-09937 Chmod of ORACLE password file failed.

Cause: Oracle was unable to change a password file to be read only.

Action: Check the UNIX error number for the specific reason.


ORA-09938 Save of signal handlers failed.

Cause: Oracle was unable to save the previous values of selected signal handlers. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09939 Restoration of signal handlers failed.

Cause: Oracle was unable to restore the previous values of selected signal handlers. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09940 ORACLE password file header is corrupt

Cause: The header of one of the password files was not in the format that Oracle expected.

Action: Check the headers of both files. The header should be in the format "FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N" where N is a number. Remove the corrupt file(s) and re-run ORAPASSWD.


ORA-09941 Version of orapasswd or installer is older than file.

Cause: The version of ORAPASSWD or installer that is being run is older than that of the Oracle password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created.

Action: Run a version of the installer or ORAPASSWD whose version is the same or later than that of the file.


ORA-09942 Write of ORACLE password file header failed.

Cause: The attempt to write out the header of the Oracle password file failed.

Action: Check the operating system error number. It is possible that the file system became full.


ORA-09943 Allocation of memory for password list component failed.

Cause: When it is building a list of password file entries, Oracle allocates memory for various components. One of the allocations failed.

Action: Check the operating system error number. The system has probably run out of memory.


ORA-09944 Password entry is corrupt.

Cause: An entry in an Oracle password file was not in the format that Oracle expected.

Action: Removed the corrupt file(s) and re-run ORAPASSWD.


ORA-09945 Unable to initialize the audit trail file

Cause: Oracle was unable to write header information to the file being used as the audit trail.

Action: Check the UNIX error number for a possible operating system error. If there is no error, contact Oracle Support Services.


ORA-09946 File name too long for buffer

Cause: The buffer that was to be used to hold a file name was determined to be too short for the generated name. This will happen if the translated name for either a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters.

Action: Use a shorter file name.


ORA-09947 Unable to allocate connection attributes structure

Cause: Oracle was not able to allocate the memory needed to hold the attributes of the SQL*Net connection. The "Additional Information" field holds the number of bytes that Oracle attempted to allocate.

Action: Check the UNIX error number. It is probable that the system has run out of memory. If there is no error, contact Oracle Support Services.


ORA-09948 Process information label retrieval failed.

Cause: Oracle was unable to get the information label for a process.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09949 Unable to get client operating system privileges

Cause: Oracle was unable to get the operating system privileges for the client process.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09950 Unable to get server operating system privileges

Cause: Oracle was unable to get its privileges from the operating system.

Action: This is an error that should never happen. Contact Oracle Support Services.


ORA-09951 Unable to create file

Cause: Oracle was unable to create a file.

Action: Check the UNIX error number for a possible operating system failure. If there is no error, contact Oracle Support Services.


ORA-09952 scgcmn: lk_open_convert unexpected return: open failed

Cause: The Distributed Lock Manager returned an unexpected value.

Action: Check for system error message and refer to the Distributed Lock Manager documentation or contact Oracle Support Services.


ORA-09953 scggc: unexpected return of a lock convert

Cause: The Distributed Lock Manager returned an unexpected value.

Action: Check for Lock Manager error messages and refer to the Distributed Lock Manager documentation or contact Oracle Support Services.


ORA-09954 scgcc: unexpected return status to callback of lock close

Cause: The Distributed Lock Manager returned an unexpected value.

Action: Check for Lock Manager error messages and refer to the Distributed Lock Manager documentation or contact Oracle Support Services.


ORA-09955 scgcan: unexpected return status when canceling a lock

Cause: DLM system service x returned an unexpected value.

Action: Check for system error message and refer to the Distributed Lock Manager documentation or contact Oracle Support Services.


ORA-09956 scgcm: unexpected lock status condition

Cause: A global locking system service returned an unexpected value.

Action: Check for system error message (if any) and refer to refer to the Distributed Lock Manager documentation or contact Oracle Support Services.


ORA-09957 Unable to send termination request to IMON

Cause: The attempt to send a termination signal to IMON failed. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09958 IMON: two processes with the same ORACLE pid are active

Cause: The IMON process was unable to add an entry for a server process because another active process occupies the slot. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09959 IMON: deletion of a process failed.

Cause: The IMON process was unable to delete a server process from its process ID array because no entry for the process could be found. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09960 Unable to establish signal handler for termination signal

Cause: Oracle was unable to set up a handler for the signal used to notify it that the instance was shutting down. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09961 Unable to restore termination signal handler

Cause: Oracle failed to set the handler for the termination signal to its previous value. This is an internal error.

Action: Contact Oracle Support Services.


ORA-09962 lk_group_create error in scggrc

ORA-09963 lk_group_attach error in scggra

ORA-09964 lk_group_detach error in scggrd

ORA-09966 scumnt: translation error while expanding ?/dbs/lk

Cause: Failure of SLTLN in SCUMNT.

Action: Check additional returned error for more information.


ORA-09967 scumnt: unable to create or open file

Cause: Open system call returned an error.

Action: Check errno.


ORA-09968 scumnt: unable to lock file

Cause: Lock file operating system call returned an error.

Action: Check errno.


ORA-09969 scurls: unable to close lock file

Cause: Close system call returned an error.

Action: Check errno.


ORA-09974 skxfidini: Error Initializing SDI Channel

Cause: The process was unable to initialize the SDI channel properly.

Action: Correct the operating system error and retry the operation.


ORA-09975 kxfspini: Error Initializing SDI Process

Cause: The process was unable to attach to the SDI channel.

Action: Verify that the SDI process specific limits correctly configured. Correct the operating system error and retry the operation.


ORA-09976 skxfqdini: Error Creating Port

Cause: The process was unable to create a communications endpoint.

Action: Verify that the SDI port specific limits correctly configured. Correct the operating system error and retry the operation.


ORA-09977 skxfqhini: Error Connecting

Cause: The process was unable to connect to another endpoint.

Action: Verify that the SDI port specific limits correctly configured. Check that the other node(s) is part of the cluster and operating properly. Correct the operating system error and retry the operation.


ORA-09978 skxfqhdel: Error Disconnecting from another endpoint.

Cause: The process was unable to disconnect cleanly from another endpoint.

Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.


ORA-09979 skxfqhsnd: Error Sending a message to another endpoint

Cause: The process was unable to send a message to an existing endpoint.

Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.


ORA-09980 skxfqdrcv: Error Receiving a message from another endpoint

Cause: The process encountered an error while trying to receive a message.

Action: Check that the other node(s) are part of the cluster and operating properly. Check the instance and processes on the other node(s). Correct the operating system error and retry the operation.


ORA-09981 skxfqdreg: Error Adding a page to the SDI buffer pool

Cause: The process was unable to add a page to the SDI buffer pool.

Action: Correct the operating system error and retry the operation.


ORA-09982 skxfqddrg: Error Removing a page from the SDI buffer pool

Cause: The process was unable to remove a page to the SDI buffer pool.

Action: Correct the operating system error and retry the operation.


ORA-09983 skxfidsht: Error shutting down SDI channel

Cause: The process was unable to shut down the SDI channel.

Action: Check the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance.


ORA-09984 SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist

Cause: File does not exist or is not accessible.

Action: Restart the instance to create the SGA definition file.


ORA-09985 SGA definition file could not be read

Cause: UNIX read() operation failed.

Action: Check errno and take appropriate action.


ORA-09986 wrong number of bytes read from SGA definition file

Cause: Struct SKGMSDEF size differs from the number of bytes read from the SGA file.

Action: Compare the two struct definitions and ensure that they are identical in size and structure.


ORA-09987 unable to attach to SGA in READ-ONLY mode

Cause: The instance is not up, or SGA segments are not read-accessible.

Action: Verify that the instance is up and read permissions for the SGA segments are set.


ORA-09988 error while detaching SGA

Cause: SKGMSDEF struct is corrupted and/or segment addresses are modified.

Action: Safely shut down the instance and mount the SGA segments again.


ORA-09989 attempt to use invalid skgmsdef struct pointer

Cause: Pointer to SKGMSDEF struct used without validating it.

Action: Assign a valid address to the SKGMSDEF struct pointer before using it.


ORA-10560 block type 'string'

Cause: Report block type for details of another error.

Action: See associated error message.


ORA-10561 block type 'string', data object# string

Cause: Report block type and data object number for details of another error.

Action: See associated error message.


ORA-10562 Error occurred while applying redo to data block (file# string, block# string)

Cause: See other errors on error stack.

Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.


ORA-10563 Test recovery had to corrupt data block (file# string, block# string) in order to proceed

Cause: Test recovery completed.

Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.


ORA-10564 tablespace string

Cause: Report tablespace name for details of another error.

Action: See associated error message.


ORA-10565 Another test recovery session is active

Cause: There can only be one test recovery session at any time. Another test recovery session is active.

Action: Wait until the other test recovery session completes.


ORA-10566 Test recovery has used all the memory it can use

Cause: Test recovery tests redo in memory. It can no longer proceed because it has consumed all the memory it can use.

Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.


ORA-10567 Redo is inconsistent with data block (file# string, block# string)

Cause: There are two possible causes of this error:

  1. A write issued by Oracle was lost by the underlying OS or storage system.
  2. An Oracle internal error.

Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.


ORA-10568 Failed to allocate recovery state object: out of SGA memory

Cause: Out of SGA memory.

Action: Restart the instance. If the problem persists, then contact Oracle Support Services.


ORA-10570 Test recovery complete

Cause: Test recovery completed.

Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.


ORA-10571 Test recovery canceled

Cause: User canceled test recovery.

Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.


ORA-10572 Test recovery canceled due to errors

Cause: See other errors on the error stack.

Action: See other messages on the error stack. It is possible that no action is needed. See other messages on error stack for a summary of the result of the test recovery so far.


ORA-10573 Test recovery tested redo from change string to string

Cause: This message shows the range of test recovery that has been tested.

Action: No action is needed. See other messages on the error stack.


ORA-10574 Test recovery did not corrupt any data block

Cause: This message summarizes test recovery result.

Action: No action is needed. See other messages on the error stack.


ORA-10575 Give up restoring recovered datafiles to consistent state: out of memory

Cause: There was not enough memory to restore recovered datafiles to consistent state.

Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.


ORA-10576 Give up restoring recovered datafiles to consistent state: some error occurred

Cause: See alert file or other errors on the stack for a cause of the problem.

Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.


ORA-10577 Can not invoke test recovery for managed standby database recovery

Cause: Test recovery option is used for managed standby database recovery.

Action: Either remove the test recovery option or invoke manual test standby database recovery.


ORA-10578 Can not allow corruption for managed standby database recovery

Cause: You used the allow corruption option for managed standby database recovery.

Action: Either remove the allow corruption option or invoke manual standby database recovery.


ORA-10579 Can not modify control file during test recovery

Cause: To proceed with recovery, test recovery needs to modify the control file. But test recovery is not allowed to modify the controlfile.

Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.


ORA-10580 Can not modify datafile header during test recovery

Cause: To proceed with recovery, test recovery needs to modify a datafile header. But test recovery is not allowed to modify datafile headers.

Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.


ORA-10581 Can not modify redo log header during test recovery

Cause: To proceed with recovery, test recovery needs to modify a redo log header. But test recovery is not allowed to modify redo log headers.

Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.


ORA-10582 The control file is not a backup control file

Cause: User requested backup control file test recovery, but the control file is not a backup control file.

Action: Use a backup control file, or do not use the USING BACKUP CONTROLFILE option.


ORA-10583 Can not recover file string renamed as missing during test recovery

Cause: One of the files to be recovered is renamed as missing.

Action: Rename the file to the correct file or offline it.


ORA-10584 Can not invoke parallel recovery for test recovery

Cause: Both test recovery and parallel recovery are requested.

Action: Drop either one of the two recovery options.


ORA-10585 Test recovery can not apply redo that may modify control file

Cause: Test recovery has encountered a special redo that may modify control file.

Action: No action is needed. Test recovery has proceeded successfully as far as it could from its starting point.


ORA-10586 Test recovery had to corrupt 1 data block in order to proceed

Cause: This message summarizes test recovery result: Oracle may have to corrupt one block in order to apply the range of redo tested.

Action: See the alert log for details of the problem.


ORA-10587 Invalid count for ALLOW n CORRUPTION option

Cause: The number specified in the ALLOW n CORRUPTION option is too big.

Action: Use a smaller number.


ORA-10588 Can only allow 1 corruption for normal media/standby recovery

Cause: The number specified in the ALLOW n CORRUPTION option is too big.

Action: Change to allow zero or one corruption.


ORA-10589 Test recovery had to corrupt string data blocks in order to proceed

Cause: This message summarizes test recovery result: Oracle may have to corrupt a number of data blocks as specified in the message in order to apply the range of redo tested.

Action: See the alert log for details of the problems.


ORA-10614 Operation not allowed on this segment

Cause: This procedure can be used only on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT.

Action: Recheck the segment name and type and re-issue the statement.


ORA-10615 Invalid tablespace type for temporary tablespace

Cause: Tablespace with AUTO SEGMENT SPACE MANAGEMENT specified cannot be used as a temporary tablespace.

Action: Recheck the tablespace name and re-issue the statement.


ORA-10616 Operation not allowed on this tablespace

Cause: Cannot perform the operation on tablespace with AUTO SEGMENT SPACE MANAGEMENT.

Action: Recheck the tablespace name and re-issue the statement.


ORA-10617 Cannot create rollback segment in dictionary managed tablespace

Cause: Rollback segments cannot be created in dictionary managed tablespaces when the SYSTEM tablespace is locally managed.

Action: Recheck the tablespace name and re-issue the statement.


ORA-10618 Operation not allowed on this segment

Cause: This DBMS_SPACE operation is not permitted on segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT.

Action: Recheck the segment name and type and re-issue the statement.


ORA-10620 Operation not allowed on this segment

Cause: Cannot alter freelist storage parameter for segments in tablespaces with AUTO SEGMENT SPACE MANAGEMENT.

Action: Recheck the segment name and re-issue the statement.


ORA-10621 data block does not belong to the segment

Cause: The specified file number and block number of the data block does not belong to the segment.

Action: Recheck the segment, file number, block number and re-issue the statement.


ORA-10640 Operation not permitted during SYSTEM tablespace migration

Cause: The SYSTEM tablespace is being migrated to locally managed format.

Action: Re-issue this command once SYSTEM tablespace migration is complete.


ORA-10641 Cannot find a rollback segment to bind to

Cause: SYSTEM tablespace migration requires rollback segment in locally managed tablespace.

Action: Drop rollback segments in dictionary managed tablespaces other than SYSTEM and create rollback segments in locally managed tablespace. Then retry migration.


ORA-10642 Found rollback segments in dictionary managed tablespaces

Cause: When SYSTEM tablespace is migrated, found rollback segments in dictionary managed tablespaces.

Action: Drop the rollback segments in dictionary managed tablespaces and re-issue the command.


ORA-10643 Database should be mounted in restricted mode and Exclusive mode

Cause: When SYSTEM tablespace is being migrated, database should be mounted in Exclusive mode and in Restricted mode.

Action: Re-issue this command after mounting the database in the correct mode.


ORA-10644 SYSTEM tablespace cannot be default temporary tablespace

Cause: When SYSTEM tablespace is being migrated, no user should have SYSTEM as the default temporary tablespace.

Action: Re-issue this command after altering the default temporary tablespace setting for all users.


ORA-10646 Too many recursive extensions during SYSTEM tablespace migration

Cause: When SYSTEM tablespace is being migrated, dictionary tables tried to extend recursively more than 1000 times.

Action: If SYSTEM tablespace is very large, then simply reissue the tablespace migration command.


ORA-10647 Tablespace other than SYSTEM,string, string not found in read only mode

Cause: When SYSTEM tablespace is being migrated, tablespaces other than the three should be ALTERed to read only.

Action: Alter the tablespace status to read only and retry migration.


ORA-10651 incorrect file number block number specified

Cause: The specified dba is not valid.

Action: Check if the specified dba belongs to the segment and is under the segment HWM and re-issue the statement.


ORA-12000 a materialized view log already exists on table 'string'

Cause: An attempt was made to create a materialized view log on a table that already has a materialized view log. Each master table can have only one materialized view log.

Action: All materialized views on a table can use the same materialized view log for that table. To make changes to the existing log, use the ALTER MATERIALIZED VIEW LOG command or drop the materialized view log and create it again.


ORA-12001 cannot create log: table 'string' already has a trigger

Cause: Materialized view logs are filled by a trigger on the master table. That trigger cannot be created.

Action: To create a materialized view log, drop the current trigger on the master.


ORA-12002 there is no materialized view log on table "string"."string"

Cause: There was no materialized view log on the master table.

Action: Create a materialized view log on the master table.


ORA-12003 materialized view "string"."string" does not exist

Cause: The materialized view with the given owner and name does not exist.

Action: Verify inputs and create a materialized view.


ORA-12004 REFRESH FAST cannot be used for materialized view "string"."string"

Cause: The materialized view log does not exist or cannot be used.

Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log, REFRESH FAST will be available starting the next time the materialized view is refreshed.


ORA-12005 may not schedule automatic refresh for times in the past

Cause: An attempt was made to schedule an automated materialized view refresh for a time in the past.

Action: Choose a time in the future instead.


ORA-12006 a materialized view with the same user.name already exists

Cause: An attempt was made to create a materialized view with the name of an existing materialized view.

Action: Create the materialized view using a different name or drop the existing materialized view.


ORA-12007 materialized view reuse parameters are inconsistent

Cause: The CREATE MATERIALIZED VIEW .. or CREATE MATERIALIZED VIEW LOG .. REUSE command was given inconsistent parameters immediately after the REUSE.

Action: Examine the other messages on the stack to find the problem.


ORA-12008 error in materialized view refresh path

Cause: Table SNAP$_mview_name reads rows from the view MVIEW$_mview_name, which is a view on the master table (the master may be at a remote site). Any error in this path will cause this error at refresh time. For fast refreshes, the table master_owner.MLOG$_master is also referenced.

Action: Examine the other messages on the stack to find the problem. See if the objects SNAP$_mview_name, MVIEW$_mview_name, mowner.master@dblink, mowner.MLOG$_master@dblink still exist.


ORA-12009 materialized views may not contain long columns

Cause: An attempt was made to create a materialized view with a long column.

Action: Do not attempt to create materialized view logs with long columns.


ORA-12010 cannot create materialized view log on table owned by SYS

Cause: An attempt was made to create a materialized view log on the table owned by SYS. CREATE MATERIALIZED VIEW LOG attempts to create a trigger on the table, but triggers can not be created on SYS tables.

Action: Do not create a materialized view log on SYS tables.


ORA-12011 execution of string jobs failed

Cause: An error was caught in dbms_ijob.run from one or more jobs which were due to be run.

Action: Look at the alert log for details on which jobs failed and why.


ORA-12012 error on auto execute of job string

Cause: Some kind of error was caught while doing an automatic execute of a job.

Action: Look at the accompanying errors for details on why the execute failed.


ORA-12013 updatable materialized views must be simple enough to do fast refresh

Cause: The updatable materialized view query contained a join, subquery, union, connect by, order by, or group by clause.

Action: Make the materialized view simpler. If a join is really needed, make multiple simple materialized views then put a view on top of them.


ORA-12014 table 'string' does not contain a primary key constraint

Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH PRIMARY KEY option and the master table did not contain a primary key constraint or the constraint was disabled.

Action: Reissue the command using only the WITH ROWID option, create a primary key constraint on the master table, or enable an existing primary key constraint.


ORA-12015 cannot create a fast refresh materialized view from a complex query

Cause: Neither ROWIDs nor primary key constraints are supported for complex queries.

Action: Reissue the command with the REFRESH FORCE or REFRESH COMPLETE option or create a simple materialized view.


ORA-12016 materialized view does not include all primary key columns

Cause: The query that instantiates the materialized view did not include all of the columns in the master's primary key constraint.

Action: Include all of the master's primary key columns in the materialized view query or create a ROWID materialized view.


ORA-12017 cannot alter primary key mview 'string' to a rowid mview

Cause: An attempt was made to convert the primary key of a materialized view to a ROWID materialized view.

Action: Conversion of a primary key materialized view to a ROWID materialized view is not supported. Create a new materialized view with ROWIDs or drop and recreate the materialized view with ROWIDs.


ORA-12018 following error encountered during code generation for "string"."string"

Cause: The refresh operations for the indicated materialized view could not be regenerated due to errors.

Action: Correct the problem indicated in the following error messages and repeat the operation.


ORA-12019 master table is a synonym to a remote object

Cause: An attempt was made to create a materialized view or a materialized view log on a remote synonym which is unsupported.

Action: Do not create a materialized view or materialized view log on a remote synonym.


ORA-12020 materialized view string is not registered

Cause: An attempt was made to unregister a materialized view that is not registered.

Action: No action required.


ORA-12021 materialized view "string"."string" is corrupt

Cause: The indicated materialized view is no longer valid.

Action: Contact Oracle Support Services.


ORA-12022 materialized view log on "string"."string" already has rowid

Cause: Materialized view log on the indicated table already has ROWID information.

Action: No action required.


ORA-12023 missing index on materialized view "string"."string"

Cause: The specified ROWID materialized view did not have the required index on the ROWID column of its underlying table.

Action: Drop and recreate the materialized view.


ORA-12024 materialized view log on "string"."string" does not have primary key columns

Cause: Materialized view log on the indicated table does not have primary key information.

Action: Add primary keys to the materialized view log using the ALTER MATERIALIZED VIEW command.


ORA-12025 materialized view log on "string"."string" already has primary keys

Cause: Materialized view log on the indicated table already has primary key columns.

Action: No action required.


ORA-12026 invalid filter column detected

Cause: One or more of the specified filter columns did not exist or was a primary key column or a primary key based object identifier.

Action: Ensure that all specified filter columns exist in the master table and ensure that primary key columns or primary key based object identifiers are not included in the list of filter columns.


ORA-12027 duplicate filter column

Cause: One or more of the specified filter columns was already being recorded in the materialized view log.

Action: Describe the materialized view log table and reissue the SQL command with the filter columns that are already being recorded in the materialized view log.


ORA-12028 materialized view type is not supported by master site string

Cause: Pre-Oracle8 master sites are not able to support primary key or subquery materialized views that are able to perform a fast refresh.

Action: Create a ROWID materialized view or use a master table from an Oracle8 site.


ORA-12029 LOB columns may not be used as filter columns

Cause: An attempt was made to use LOB columns as filter columns.

Action: Remove LOB columns from the filter columns list and retry command.


ORA-12030 cannot create a fast refresh materialized view
  • For primary key materialized views, the master table's primary key columns must be logged.
  • For subquery materialized views, the filter columns, primary key, and ROWID values must be logged.

Cause: The materialized view log did not exist or did not log the information needed by the materialized view to perform a fast refresh.

Action: Ensure that the materialized view log exists and logs the necessary information.

  • For ROWID materialized views, the master table's ROWID must be logged.
  • For primary key materialized views, the master table's primary key columns must be logged.
  • For subquery materialized views, the filter columns, primary key, and ROWID values must be logged.

ORA-12031 cannot use primary key columns from materialized view log on "string"."string"

Cause: The materialized view log either did not have primary key columns logged, or the timestamp associated with the primary key columns was more recent than the last refresh time.

Action: A complete refresh is required before the next fast refresh. Add primary key columns to the materialized view log, if required.


ORA-12032 cannot use rowid column from materialized view log on "string"."string"

Cause: The materialized view log either does not have ROWID columns logged, or the timestamp associated with the ROWID columns is more recent than the last refresh time.

Action: A complete refresh is required before the next fast refresh. Add ROWID columns to the materialized view log, if required.


ORA-12033 cannot use filter columns from materialized view log on "string"."string"

Cause: The materialized view log either did not have filter columns logged, or the timestamp associated with the filter columns was more recent than the last refresh time.

Action: A complete refresh is required before the next fast refresh. Add filter columns to the materialized view log, if required.


ORA-12034 materialized view log on "string"."string" younger than last refresh

Cause: The materialized view log was younger than the last refresh.

Action: A complete refresh is required before the next fast refresh.


ORA-12035 could not use materialized view log on "string"."string"

Cause: The materialized view log did not exist or could not be used.

Action: Use just REFRESH, which will reinstantiate the entire table. If a materialized view log exists and the form of the materialized view allows the use of a materialized view log, REFRESH FAST will be available starting the next time the materialized view is refreshed.


ORA-12036 updatable materialized view log is not empty, refresh materialized view

Cause: The updatable materialized view log was not empty. The updatable materialized view log must be empty before an updatable rowid materialized view can be altered to a primary key materialized view.

Action: Ensure that updatable materialized view log is empty by refreshing the materialized view before converting the updatable ROWID materialized view to a primary key materialized view.


ORA-12037 unknown export format

Cause: An attempt was made to import a materialized view exported by an unknown export version (for example, from a newer release than the importing site).

Action: Re-export the file using a version of export known by the importing site.


ORA-12039 unable to use local rollback segment "string"

Cause: A local rollback segment was specified in the CREATE MATERIALIZED VIEW command, but automatic refresh parameters were not specified. Therefore a refresh group was not created to automatically refresh the materialized view and the local rollback segment can't be registered for future use.

Action: Either supply the automatic refresh parameters so that a refresh group will be created or do not specify a local rollback segment.


ORA-12040 master rollback segment option not support by master site string

Cause: An attempt was made to specify master rollback segment in the current operation. The master site of the current materialized view does not allow users to specify a rollback segment to be used for materialized view operations. This feature is only supported by Oracle8 or later master sites.

Action: Do not specify a master rollback segment in the current operation or choose a new master site.


ORA-12041 cannot record ROWIDs for index-organized table "string"."string"

Cause: Index-organized tables do not have ROWIDs. Therefore a materialized view log that records the ROWIDs of an index-organized table could not be created.

Action: Do not include the WITH ROWID option when using the CREATE MATERIALIZED VIEW command and do not include the ADD ROWID option when using the ALTER MATERIALIZED VIEW command if the master table is index-organized.


ORA-12042 cannot alter job_queue_processes in single process mode

Cause: An attempt was made to alter job_queue_processes in single process mode.

Action: Do not attempt to set job_queue_processes in single process mode.


ORA-12043 invalid CREATE MATERIALIZED VIEW option

Cause: An invalid option was used in a CREATE MATERIALIZED VIEW statement.

Action: Specify only valid options.


ORA-12044 invalid CREATE MATERIALIZED VIEW LOG option

Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG statement.

Action: Specify only valid options.


ORA-12045 invalid ALTER MATERIALIZED VIEW LOG option

Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG statement.

Action: Specify only valid options.


ORA-12051 ON COMMIT attribute is incompatible with other options

Cause: The ON COMMIT refresh attribute, incompatible with other refresh options such as automatic periodic refresh, was specified.

Action: Specify only valid options.


ORA-12052 cannot fast refresh materialized view string.string

Cause: Either ROWIDs of certain tables were missing in the definition or the inner table of an outer join did not have UNIQUE constraints on join columns.

Action: Specify the FORCE or COMPLETE option. If this error occurred during creation, the materialized view definition may have been changed. Refer to the documentation on materialized views.


ORA-12053 this is not a valid nested materialized view

Cause: The list of objects in the FROM clause of the definition of this materialized view had some dependencies upon each other.

Action: Refer to the documentation to see which types of nesting are valid.


ORA-12054 cannot set the ON COMMIT refresh attribute for the materialized view

Cause: The materialized view did not satisfy conditions for refresh at commit time.

Action: Specify only valid options.


ORA-12055 materialized view definition contains cyclic dependencies with existing materialized views

Cause: The materialized view query definition introduced a cyclic dependency with existing materialized views.

Action: Modify the materialized view query definition.


ORA-12056 invalid REFRESH method

Cause: The NEVER REFRESH option may not be used under the following conditions:

  • The materialized view is updatable
  • The materialized view refreshes ON COMMIT
  • Automatic refresh options are specified

Action: For updatable materialized views, reissue the SQL command using REFRESH FORCE, REFRESH FAST, or REFRESH COMPLETE. For read-only materialized views, reissue the SQL command using ON DEMAND.


ORA-12057 materialized view "string"."string" is INVALID and must complete refresh

Cause: The status of the materialized view was INVALID and an attempt was made to fast refresh the materialized view.

Action: Perform a complete refresh of the materialized view. Check the value of the STATUS column in dba_mviews, all_mviews, or user_mviews to verify that the materialized view is VALID after the complete refresh.


ORA-12058 materialized view cannot use prebuilt table

Cause: An attempt was made to use the prebuilt tables.

Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED.


ORA-12059 prebuilt table "string"."string" does not exist

Cause: The specified prebuilt table did not exist.

Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table exists.


ORA-12060 shape of prebuilt table does not match definition query

Cause: The number of columns or the type or the length semantics of a column in the prebuilt table did not match the materialized view definition query.

Action: Reissue the SQL command using BUILD IMMEDIATE, BUILD DEFERRED, or ensure that the prebuilt table matches the materialized view definition query.


ORA-12061 invalid ALTER MATERIALIZED VIEW option

Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement.

Action: Specify only valid options.


ORA-12062 transaction string received out of sequence from site string

Cause: A transaction from the client site was received out of sequence. This implies that one or more transactions were missing.

Action: Ensure that the transaction queue at the client site is valid and has not been corrupted.


ORA-12063 unable to apply transaction from site string

Cause: The current transaction from the client site could not be applied to the master site.

Action: Ensure that the client site is still valid and that it has not been dropped from the master site.


ORA-12064 invalid refresh sequence number: string

Cause: The client site was attempting to perform a refresh with an invalid refresh sequence.

Action: Perform a complete refresh to synchronize the refresh sequence number.


ORA-12065 unknown refresh group identifier string

Cause: The specified refresh group did not exist at the master site.

Action: Ensure that the client site is still valid and that it has not been dropped from the master site.


ORA-12066 invalid CREATE MATERIALIZED VIEW command

Cause: The Replication API does not support the following options and types of materialized view:

  • ROWID materialized views
  • REFRESH ON COMMIT
  • ON PREBUILT TABLE
  • BUILD DEFERRED
  • NEVER REFRESH