- 1【Unity6.0+AI】Unity版的Pytorch之Sentis-把大模型植入Unity_unityai-sentis
- 2Pytorch入门实战（2）-使用BP神经网络实现MNIST手写数字识别_pyorch 手写数字识别 bp
- 3Hi3861鸿蒙物联网项目实战：智能测距仪_四川爱联wf-h861-rta1
- 4steam成就解锁器_SAM解锁steam成就教程科普
- 5PTA 7-9 重排链表 (25分) 链表操作_给定一个单链表 l 1 →l 2 → →l n 1 →l n ,请编写程序将链表重新排列为
- 6CUDA安装教程_安装cuda教程
- 7【转载】Kaldi thchs30手札（一）特征提取阶段（line 0-33)_倒谱均值方差归一化
- 8挑战杯 机器视觉人体跌倒检测系统 - opencv python
- 9（vite/webpack 通用）vue 白屏 Uncaught Syntaxerror: Unexpected token ‘?‘_uncaught syntaxerror: unexpected token '?
- 10（2.2）HarmonyOS鸿蒙页面跳转_学习harmonyos页面跳转的实验目的
Oracle Database Server Messages(二) ._primary receives updates while work location is di
赞
踩
Skip Headers
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
5
ORA-02100 to ORA-04099
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A SELECT...INTO statement returned more rows than can be stored in the host variable provided.
-
Action: There are three possible solutions:
-
Cause: An identifier does not follow ALTER TABLESPACE.
-
Action: Specify a tablespace name following ALTER TABLESPACE.
-
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.
-
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.
-
Cause: An option other than INITIAL, NEXT, MINEXTENTS, MAXEXTENTS, or PCTINCREASE was specified in the STORAGE clause.
-
Action: Specify only valid options.
-
Cause: No ALTER CLUSTER options are specified.
-
Action: Specify one or more of the following options: PCTFREE, PCTUSED, SIZE, STORAGE.
-
Cause: No STORAGE options were specified following STORAGE (.
-
Action: Specify one or more STORAGE option between the parentheses.
-
Cause: The SHARED option was specified in a CREATE DATABASE statement multiple times.
-
Action: Only specify the SHARED option once.
-
Cause: Both the SHARED and EXCLUSIVE options were specified in a CREATE DATABASE statement.
-
Action: Specify SHARED or EXCLUSIVE, but not both.
-
Cause: The EXCLUSIVE option was specified in a CREATE DATABASE statement multiple times.
-
Action: Only specify the EXCLUSIVE option once.
-
Cause: Partition not found for the object.
-
Action: Retry with correct partition name.
-
Cause: An encoded password string does not follow the VALUES clause.
-
Action: Place a proper encoded password string after the VALUES clause.
-
Cause: An identifier does not follow DEFAULT TABLESPACE.
-
Action: Place a tablespace name after DEFAULT TABLESPACE.
-
Cause: An identifier does not follow TEMPORARY TABLESPACE.
-
Action: Place a tablespace name after TEMPORARY TABLESPACE.
-
Cause: No options were specified.
-
Action: Specify at least one ALTER USER 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.
-
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.
-
Cause: A column of type LONG defined for index-organized table.
-
Action: Do not use columns of type LONG in index-organized tables.
-
Cause: A number does not follow MAXLOGFILES.
-
Action: Specify a number after MAXLOGFILES.
-
Cause: A number does not follow MAXDATAFILES.
-
Action: Specify a number after MAXDATAFILES.
-
Cause: A number does not follow FREELIST GROUPS.
-
Action: Specify a number after FREELIST GROUPS.
-
Cause: The CREATE DATABASE command contains more than one DATAFILE clause.
-
Action: Specify at most one DATAFILE clause.
-
Cause: An invalid CREATE DATABASE option is present.
-
Action: Specify only valid CREATE DATABASE options.
-
Cause: Both ARCHIVELOG and NOARCHIVELOG are specified in a CREATE DATABASE statement.
-
Action: Specify at most one of these two options.
-
Cause: The CREATE DATABASE command contains more than one LOGFILE clause.
-
Action: Specify at most one LOGFILE clause.
-
Cause: A number does not follow FREELISTS.
-
Action: Specify a number after FREELISTS.
-
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.
-
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.
-
Cause: A number does not follow MAXLOGHISTORY.
-
Action: Specify a number after MAXLOGHISTORY.
-
Cause: The PUBLIC keyword was specified for a disable.
-
Action: Remove the keyword and resubmit.
-
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.
-
Cause: A thread number must be specified after THREAD keyword.
-
Action: Use correct syntax.
-
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.
-
Cause: An invalid option was specified in a CREATE ROLLBACK SEGMENT statement.
-
Action: Specify one of the valid options: TABLESPACE and STORAGE.
-
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.
-
Cause: There is a syntax error in the user's statement.
-
Action: Correct the syntax as indicated.
-
Cause: There is a syntax error in the user's statement.
-
Action: Correct the syntax as indicated.
-
Cause: An invalid option appears.
-
Action: Specify one of the valid options: DATAFILE, DEFAULT STORAGE, ONLINE, OFFLINE, or FORCE.
-
Cause: A token other than TO follows ROLLBACK [WORK].
-
Action: Place nothing or TO SAVEPOINT name after ROLLBACK [WORK].
-
Cause: An identifier does not follow ROLLBACK [WORK] TO [SAVEPOINT].
-
Action: Place a savepoint name following TO [SAVEPOINT].
-
Cause: There is a syntax error in the user's statement.
-
Action: Correct the syntax as indicated.
-
Cause: In a revoke statement, a resource quota was specified.
-
Action: Specify resource privilege without the quota.
-
Cause: A token other than WORK follows COMMIT.
-
Action: Place either nothing or WORK after COMMIT.
-
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.
-
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.
-
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.
-
Cause: The keyword TABLES is expected following DROP CLUSTER name INCLUDING.
-
Action: Place TABLES after INCLUDING.
-
Cause: There is a syntax error in the user's statement.
-
Action: Correct the syntax as indicated.
-
Cause: The storage parameter PCTINCREASE was specified in a CREATE or ALTER ROLLBACK SEGMENT command.
-
Action: Retry the command without the PCTINCREASE clause.
-
Cause: There is a syntax error in an event specification.
-
Action: Check syntax and spelling and try again.
-
Cause: The object type is inconsistent with a tablespace contents.
-
Action: Create an object in a different tablespace, or change the user defaults.
-
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.
-
Cause: In CREATE TABLESPACE, more than one DATAFILE/TEMPFILE clause was specified.
-
Action: Merge the DATAFILE/TEMPFILE clauses into a single clause.
-
Cause: In CREATE TABLESPACE, the ONLINE and/or OFFLINE options were specified more than once.
-
Action: Specify at most one of ONLINE or OFFLINE.
-
Cause: A CREATE TABLESPACE statement has no DATAFILE/TEMPFILE clause.
-
Action: Specify a DATAFILE/TEMPFILE clause.
-
Cause: An attempt was made to GRANT to PUBLIC WITH GRANT OPTION.
-
Action: Remove the WITH GRANT OPTION clause.
-
Cause: An attempt was made to reference a sequence in a from-list.
-
Action: A sequence can only be referenced in a select-list.
-
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.
-
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.
-
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.
-
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.
-
Cause: INITRANS is specified more than once.
-
Action: Specify INITRANS at most once.
-
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.
-
Cause: MAXTRANS is specified more than once.
-
Action: Specify MAXTRANS at most once.
-
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.
-
Cause: No ALTER TABLE option was specified.
-
Action: Specify at least one alter table option.
-
Cause: The specified value for PCTFREE or PCTUSED is not an integer between 0 and 100.
-
Action: Choose an appropriate value for the option.
-
Cause: PCTFREE option specified more than once.
-
Action: Specify PCTFREE at most once.
-
Cause: PCTUSED option specified more than once.
-
Action: Specify PCTUSED at most once.
-
Cause: The BACKUP option to ALTER TABLE is specified more than once.
-
Action: Specify the option at most once.
-
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.
-
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.
-
Cause: A storage option (INIITAL, NEXT, MINEXTENTS, MAXEXTENTS, PCTINCREASE) is specified more than once.
-
Action: Specify all storage options at most once.
-
Cause: The specified value must be an integer.
-
Action: Choose an appropriate integer value.
-
Cause: The specified value must be an integer.
-
Action: Choose an appropriate integer value.
-
Cause: The specified value must be a positive integer less than or equal to MAXEXTENTS.
-
Action: Specify an appropriate value.
-
Cause: The specified value must be a positive integer greater than or equal to MINEXTENTS.
-
Action: Specify an appropriate value.
-
Cause: The specified value must be a positive integer.
-
Action: Specify an appropriate value.
-
Cause: The specified value must be an integer.
-
Action: Choose an appropriate integer value.
-
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.
-
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.
-
Cause: The MAXEXTENTS specified is too large for the database block size. This applies only to SYSTEM rollback segment.
-
Action: Specify a smaller value.
-
Cause: A cluster name was not properly formed.
-
Action: Check the rules for forming object names and enter an appropriate cluster name.
-
Cause: The SIZE option is specified more than once.
-
Action: Specify the SIZE option at most once.
-
Cause: The specified value must be an integer number of bytes.
-
Action: Specify an appropriate value.
-
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or SIZE is specified in an ALTER CLUSTER statement.
-
Action: Specify only legal options.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A character string literal was not used in the file name list of a LOGFILE, DATAFILE, or RENAME clause.
-
Action: Use correct syntax.
-
Cause: A non-integer value was specified in the SIZE or RESIZE clause.
-
Action: Use correct syntax.
-
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.
-
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.
-
Cause: A number does not follow either OBJNO or TABNO.
-
Action: Specify a number after OBJNO or TABNO.
-
Cause: There was an error in the extent storage clause.
-
Action: Respecify the storage clause using the correct syntax and retry the command.
-
Cause: No options specified.
-
Action: Specify at least one of REBUILD, INITRANS, MAXTRANS, or STORAGE.
-
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.
-
Cause: The STORAGE option is expected but not found.
-
Action: Specify the STORAGE option.
-
Cause: An identifier was expected, but not found, following ALTER [PUBLIC] ROLLBACK SEGMENT.
-
Action: Place a rollback segment name following SEGMENT.
-
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.
-
Cause: The option SET EVENTS was expected, but not found, following ALTER SESSION.
-
Action: Place the SET EVENTS option after 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.
-
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.
-
Cause: The constraint name is missing or invalid.
-
Action: Specify a valid identifier name for the constraint name.
-
Cause: Subquery is not allowed here in the statement.
-
Action: Remove the subquery from the statement.
-
Cause: The specified search condition for the check constraint is not properly ended.
-
Action: End the condition properly.
-
Cause: Constraint specification is not allowed here in the statement.
-
Action: Remove the constraint specification from the statement.
-
Cause: Default value expression is not allowed for the column here in the statement.
-
Action: Remove the default value expression from the statement.
-
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.
-
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.
-
Cause: The number of columns in the key list exceeds the maximum number.
-
Action: Reduce the number columns in the list.
-
Cause: A duplicate or conflicting NULL and/or NOT NULL was specified.
-
Action: Remove one of the conflicting specifications and try again.
-
Cause: A duplicate unique or primary key was specified.
-
Action: Remove the duplicate specification and try again.
-
Cause: Two or more primary keys were specified for the same table.
-
Action: Remove the extra primary keys and try again.
-
Cause: A unique or primary key was specified that already exists for the table.
-
Action: Remove the extra key and try again.
-
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.
-
Cause: The required datatype for the column is missing.
-
Action: Specify the required datatype.
-
Cause: The specified constraint name has to be unique.
-
Action: Specify a unique constraint name for the constraint.
-
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.
-
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');
-
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.
-
Cause: The referenced table does not have a primary key.
-
Action: Specify explicitly the referenced table unique key.
-
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.
-
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.
-
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.
-
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.
-
Cause: A unique or primary key referenced by foreign keys cannot be dropped.
-
Action: Remove all references to the key before dropping it.
-
Cause: A referential constraint was specified more than once. This is not allowed.
-
Action: Remove the duplicate specification.
-
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.
-
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.
-
Cause: The specified sequence name is not a valid identifier name.
-
Action: Specify a valid identifier name for the sequence name.
-
Cause: Duplicate or conflicting MAXVALUE and/or NOMAXVALUE specifications.
-
Action: Remove one of the conflicting specifications and try again.
-
Cause: Duplicate or conflicting MINVALUE and/or NOMINVALUE clauses were specified.
-
Action: Remove one of the conflicting specifications and try again.
-
Cause: Duplicate or conflicting CYCLE and/or NOCYCLE clauses were specified.
-
Action: Remove one of the conflicting specifications and try again.
-
Cause: Duplicate or conflicting CACHE and/or NOCACHE clauses were specified.
-
Action: Remove one of the conflicting specifications and try again.
-
Cause: Duplicate or conflicting ORDER and/or NOORDER clauses were specified.
-
Action: Remove one of the conflicting specifications and try again.
-
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.
-
Cause: A duplicate INCREMENT BY clause was specified.
-
Action: Remove the duplicate specification and try again.
-
Cause: A duplicate START WITH clause was specified.
-
Action: Remove the duplicate specification and try again.
-
Cause: No ALTER SEQUENCE option was specified.
-
Action: Check the syntax. Then specify at least one ALTER SEQUENCE option.
-
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.
-
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.
-
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.
-
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.
-
Cause: A foreign key value has no matching primary key value.
-
Action: Delete the foreign key or add a matching primary key.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A number was not specified for the value of OIDGENERATORS.
-
Action: Specify a number for OIDGENERATORS.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to enter an object identifier literal for CREATE TYPE that is either:
-
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.
-
Cause: An attempt was made to GRANT or REVOKE an invalid privilege (not
EXECUTE,DEBUG, orUNDER) on a type. -
Action: GRANT or REVOKE only the
EXECUTE,DEBUG, orUNDERprivilege on types. -
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The specified object type contains a nested attribute whose type is non-queryable.
-
Action: Use an object type with queryable attribute types.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A column constraint was not specified.
-
Action: Remove the column specification or specify a column constraint. Then retry the operation.
-
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.
-
Cause: An attempt was made to specify an UNPACKED column within a packed table.
-
Action: Remove the UNPACKED keyword in the column specification.
-
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.
-
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.
-
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.
-
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.
-
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. -
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.
-
Cause: The record indicated caused an Oracle error on insert.
-
Action: Determine the Oracle error and correct the record.
-
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.
-
Cause: Text specified by POSITION or terminated by newlines is invalid.
-
Action: Edit the control file or the datafile to fix alignment of column.
-
Cause: An error occurred during conversion initialization for a field. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: A CONSTANT field caused an Oracle error; all rows will be rejected.
-
Action: Determine the Oracle error and correct the record.
-
Cause: The load was discontinued due to space exhaustion in the database.
-
Action: Add space for the specified table.
-
Cause: The column could not be converted from packed decimal to character.
-
Action: Check the column and make it conform to packed decimal format.
-
Cause: The column could not be converted from packed decimal to character.
-
Action: Check the column and make it conform to packed decimal format.
-
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.
-
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.
-
Cause: The initial enclosing character of an enclosed field was not found.
-
Action: Supply the character before the start of the field.
-
Cause: The second enclosing character of an enclosed field was not found.
-
Action: Supply the character after the end of the field.
-
Cause: No terminator was found after a terminated and enclosed field.
-
Action: Supply the character after the end of the field.
-
Cause: The record was not loaded because it failed the WHEN clauses of all the tables.
-
Action: No action required.
-
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.
-
Cause: The indexes listed for the named table were loaded.
-
Action: No action required.
-
Cause: The index specified in the message was loaded.
-
Action: No action required.
-
Cause: The record was not loaded because all of the columns in the table were null for that record.
-
Action: No action required.
-
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.
-
Cause: The record indicated caused an warning.
-
Action: Determine the warning and correct the record if necessary.
-
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.
-
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.
-
Cause: A parsing error occurred.
-
Action: Check the message following this parsing error message.
-
Cause: There are no free read buffers.
-
Action: Use the READBUFFERS keyword in the loader to increase the number of read buffers.
-
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.
-
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.
-
Cause: An invalid resource limit of 0 was specified.
-
Action: Specify a resource limit greater than 0.
-
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.
-
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.
-
Cause: An attempt was made to assign a user to a non-existent profile.
-
Action: Assign the user to an existing profile.
-
Cause: An attempt was made to drop the PUBLIC_DEFAULT profile.
-
Action: The PUBLIC_DEFAULT profile cannot be dropped.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A user has exceeded the maximum time allowed to remain idle.
-
Action: The user must reconnect to the database.
-
Cause: This error occurs only when using a multi-threaded server.
-
Action: Contact the database administrator to expand the PRIVATE_SGA limit.
-
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.
-
Cause: A user has exceeded the maximum time allowed to be connected to the database.
-
Action: The user must reconnect to the database.
-
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.
-
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.
-
Cause: The explicit plan table does not have the appropriate field definitions.
-
Action: Redefine the plan table to have the appropriate field definitions.
-
Cause: The specified plan table does cannot be found.
-
Action: Create the specified plan table or use an existing plan table.
-
Cause: The AUTHORIZATION clause is missing from a create schema statement.
-
Action: Proceed the schema authorization identifier with the AUTHORIZATION keyword.
-
Cause: One of the following:
-
Action: If the cause is
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The named constraint does not exist for this table.
-
Action: Check that a constraint exists before trying to enable it.
-
Cause: The named constraint does not exist for this table.
-
Action: Check that a constraint exists before trying to disable it.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to define a column check constraint that references another column.
-
Action: Define it as a table check constraint.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to defer a nondeferrable constraint.
-
Action: Drop the constraint and create a new one that is deferrable.
-
Cause: The named constraint does not exist.
-
Action: Choose a constraint that does exist or do not perform this operation.
-
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";
-
Cause: Missing IS keyword.
-
Action: Specify HASH IS option.
-
Cause: The HASHKEYS option is specified more than once.
-
Action: Only specify the HASHKEYS option once.
-
Cause: The specified HASHKEYS option must be an integer value.
-
Action: Specify an appropriate value.
-
Cause: The HASH IS option is specified more than once.
-
Action: only specify the HASH IS option once.
-
Cause: The SIZE argument is too small.
-
Action: Increase the SIZE argument.
-
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.
-
Cause: The column specification must specify an integer.
-
Action: Specify the column definition as type NUMBER(precision, 0).
-
Cause: The HASH IS column name is not specified in the cluster definition.
-
Action: Specify a valid column name.
-
Cause: The HASHKEYS option must be specified when creating a HASH CLUSTER.
-
Action: Specify the HASHKEYS option.
-
Cause: The value of the hash key was not a positive number.
-
Action: Specify a positive integer.
-
Cause: An attempt to create a cluster index was issued on a hash cluster.
-
Action: Do not attempt to create such an index.
-
Cause: This option is only valid for non hash clusters.
-
Action: Do not specify this option.
-
Cause: The INDEX option is specified more than once.
-
Action: Only specify the INDEX option once.
-
Cause: The HASH IS option is specified more than once.
-
Action: Only specify the HASH IS option once.
-
Cause: The cluster can either be a hash or indexed cluster, not both.
-
Action: Remove either the HASH IS or INDEX options.
-
Cause: This option is only valid for clusters.
-
Action: Do not specify this option.
-
Cause: The SIZE cannot be changed once the hash cluster has been created.
-
Action: Do not specify this option.
-
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.
-
Cause: A constant or system variable was specified in the hash expression.
-
Action: Re-create the cluster and correct the error in hash expression.
-
Cause: Result of evaluating hash expression is not an Oracle Number.
-
Action: Re-create the cluster and correct the error 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.
-
Cause: SYSDATE, UID, USER, ROWNUM, or LEVEL are not allowed in hash expressions.
-
Action: Re-create the cluster and remove the offending keywords.
-
Cause: A PL/SQL function was used in the hash expression.
-
Action: Re-create the cluster and remove the PL/SQL function.
-
Cause: An error occurred while evaluating the clusters hash expression.
-
Action: Correct the query and retry.
-
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.
-
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.
-
Cause: A parallel direct load is occurring to the specified table.
-
Action: Retry statement after load is complete.
-
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.
-
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.
-
Cause: An invalid file name was specified to load data into.
-
Action: Specify a valid database file.
-
Cause: Too many processes specified than allowed per event.
-
Action: Enter fewer processes by using ranges or wildcards if possible.
-
Cause: Illegal event string.
-
Action: Enter a legal event string.
-
Cause: Illegal process string.
-
Action: Enter a legal process 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.
-
Cause: No value was specified for the RESIZE clause.
-
Action: Use the correct syntax.
-
Cause: The keyword ON or OFF was not specified for the AUTOEXTEND clause.
-
Action: Use the correct syntax.
-
Cause: No value was specified for the NEXT clause.
-
Action: Use the correct syntax.
-
Cause: A non-integer value was used for the NEXT clause of the DATAFILE list.
-
Action: Use the correct syntax.
-
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.
-
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.
-
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.
-
Cause: ORACLE_HOME environment variable not set.
-
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
-
Cause: ORACLE_HOME environment variable not set.
-
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
-
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.
-
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.
-
Cause: The pipe driver failed while polling the communications channel.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The invoked UNIX two-task driver could not allocate heap space for the context area.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: The pipe driver failed to write to the ORAPOP process.
-
Action: Contact Oracle Support Services.
-
Cause: The pipe driver failed to allocate enough heap space for its context area buffers.
-
Action: Contact Oracle Support Services.
-
Cause: The pipe driver failed to read a message from the communications channel.
-
Action: Contact Oracle Support Services.
-
Cause: The pipe driver failed to write a message to the communications channel.
-
Action: Contact Oracle Support Services.
-
Cause: The pipe driver received a message having an unrecognizable message type.
-
Action: Contact Oracle Support Services.
-
Cause: The Pipe driver received a message having an unrecognizable message type.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The two-task driver could not reset the connection.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: The Pipe driver could not send a break message to ORAPOP.
-
Action: Contact Oracle Support Services.
-
Cause: The Pipe driver could not send a break message to the Oracle shadow process.
-
Action: Contact Oracle Support Services.
-
Cause: The Pipe driver could not send a break message to ORAPOP.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
Cause: The driver you have specified is not supported.
-
Action: Check with your database administrator which drivers are supported.
-
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.
-
Cause: The specified driver could not find enough heap space to MALLOC a buffer.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The Fast driver was unable to reset shared memory permissions.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The Fast driver failed to establish a default shared memory address.
-
Action: Contact Oracle Support Services.
-
Cause: The Pipe driver failed to send ORAPOP the command to exit.
-
Action: Contact Oracle Support Services.
-
Cause: The pipe driver apparently sent an incomplete break message.
-
Action: Contact Oracle Support Services.
-
Cause: The alias used for a SQLNET host is longer than 161 characters.
-
Action: Use a shorter alias.
-
Cause: The Fast driver failed to create a shared memory file for two-task communication.
-
Action: Check the permissions on the directory ?/dbs.
-
Cause: The Fast driver failed to map a shared memory file for two-task communication.
-
Action: Contact Oracle Support Services.
-
Cause: The Fast driver failed to attach shared memory at the expected location.
-
Action: Contact Oracle Support Services.
-
Cause: The Fast driver cannot close the shared memory file.
-
Action: Contact Oracle Support Services.
-
Cause: The Fast driver could not alter the inheritance attributes of the shared memory.
-
Action: Contact Oracle Support Services.
-
Cause: The Fast driver failed to create a file for shared memory.
-
Action: Check the permissions on the directory ?/dbs.
-
Cause: The Fast driver encountered an error translating the shared memory file name ?/dbs/ftt_pid.dbf.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: The client was unable to close a file after forking the servers.
-
Action: This is a system problem; contact your System Administrator.
-
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.
-
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.
-
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.
-
Cause: The mode of the package can only be parallel or duplex.
-
Action: See SFA.H for the correct values.
-
Cause: The number of servers given was less than or equal to zero.
-
Action: Use a number greater than zero.
-
Cause: The number of request descriptors was less than or equal to zero.
-
Action: Use a number greater than zero.
-
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
-
Cause: The maximum number of files to be used by the package was less than or equal to zero.
-
Action: Use a positive number.
-
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.
-
Cause: The total number of blocks to be allocated for use by the package was not greater than zero.
-
Action: Use a positive number.
-
Cause: The number was not a positive number.
-
Action: Use a positive number.
-
Cause: The time given was not a positive number.
-
Action: Use a positive number.
-
Cause: The time given was not a positive number.
-
Action: Use a positive number.
-
Cause: The time given was not a positive number.
-
Action: Use a positive number.
-
Cause: The signal number was not a positive number.
-
Action: Use a positive number.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The value given was not TRUE or FALSE.
-
Action: Specify TRUE or FALSE for the timing wanted flag.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The package could not open file for some reason.
-
Action: Check the file name.
-
Cause: The fstat(2) call on a file being used for asynchronous I/O failed.
-
Action: Check the file name.
-
Cause: The client was unable to close a file being used for asynchronous I/O.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: A request is not in the right state. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The arming of a signal handler for the "done" signal failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: Some asynchronous operations timed out in kernel mode. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The client was unable to allocated a buffer for the name of the log file.
-
Action: Contact your system administrator.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The client was unable to allocate memory for an array of flags that the servers are to use.
-
Action: Contact your system administrator.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: SHMGET(2) failed.
-
Action: Check the UNIX number. If you are unsure about what it means, contact Oracle Support Services.
-
Cause: SHMAT(2) failed.
-
Action: Check the UNIX number. If you are unsure about what it means, contact Oracle Support Services.
-
Cause: A server did not die after being sent a kill signal.
-
Action: The process may be a runaway; contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A server was unable to seek to the designated block.
-
Action: Check the UNIX error number.
-
Cause: The buffer on which an I/O is being done is not on the correct boundary.
-
Action: Check the calling program.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: No segment of the proper size is ready for use by the caller.
-
Action: Free some segments and try again.
-
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.
-
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.
-
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.
-
Cause: A server was unable to close a file being used for asynchronous I/O.
-
Action: See the UNIX error number for more information.
-
Cause: The server was unable to open a file for use with asynchronous I/O.
-
Action: Check the UNIX error number for more information.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The arming of a signal handler for the alarm signal failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The server was unable to flush its writes out to disk.
-
Action: Check the UNIX error number.
-
Cause: The client process was unable to open its log file.
-
Action: Check the UNIX error number for more information.
-
Cause: A server exited during its initialization process.
-
Action: Check the servers' logs for more information.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A server could not read the requested amount of data from disk.
-
Action: Check the UNIX error number.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The time given was not a positive number.
-
Action: Use a positive number.
-
Cause: The time given was not a positive number.
-
Action: Use a positive number.
-
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.
-
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.
-
Cause: Stated in error code (errno).
-
Action: Resolve the problem.
-
Cause: Stated in error code (errno).
-
Action: Resolve the problem.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The environment variable EXTSHM was set before starting Oracle.
-
Action: Unset the environment variable EXTSHM and restart Oracle.
-
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.
-
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.
-
Cause: An attempt was made to use a feature that is no longer supported.
-
Action: No action required.
-
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.
-
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.
-
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.
-
Cause: This is an internal error message not usually issued.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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:
-
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.
-
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.
-
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.
-
Cause: This is an internal error message not usually issued.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error message not usually issued.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error message not usually issued.
-
Action: Contact Oracle Support Services.
-
Cause: Found both a datatype, and an anonymous datatype, declaration.
-
Action: Correct the specification.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The attempted operation cannot complete now.
-
Action: Retry the operation later.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
Cause: The application performed a piecewise bind on a column.
-
Action: Provide the next piece of this bind variable.
-
Cause: The application performed a piecewise define on the column.
-
Action: Provide the next buffer for the next piece to be retrieved.
-
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.
-
Cause: The default value specified for a record field was too large.
-
Action: Change the default value to fit the field size.
-
Cause: The segment type is not TABLE, INDEX, or CLUSTER.
-
Action: Use a correct segment type.
-
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.
-
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.
-
Cause: High volume of user updates interfere with the space analysis.
-
Action: Retry the command or lock the underlying objects.
-
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.
-
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.
-
Cause: The maximum file size for an autoextendable file has exceeded the maximum number of blocks allowed.
-
Action: Reduce the size and retry.
-
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.
-
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.
-
Cause: The value of file number or block number is outside of limits or inconsistent.
-
Action: Fix the file number/block number value.
-
Cause: The value of one of the option parameters is incorrect.
-
Action: Fix the option value.
-
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.
-
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.
-
Cause: The LOB segment specified in the DBMS_SPACE operation does not exist.
-
Action: Fix the segment specification.
-
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.
-
Cause: File size specified for resize datafile/temporary file causes bitmap control structures to overlap.
-
Action: Increase the specification for the file size.
-
Cause: Corruption was detected during verification which cannot be dealt with
-
Action: Do manual verification.
-
Cause: Invalid option for alter of temporary tablespace was specified.
-
Action: Specify one of the valid options: ADD TEMPFILE, TEMPFILE ONLINE, TEMPFILE OFFLINE.
-
Cause: Invalid option for create/alter tablespace of type locally-managed.
-
Action: Specify one of the valid options.
-
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.
-
Cause: Some of the procedures were called with missing or NULL parameters.
-
Action: Specify the missing parameter.
-
Cause: An attempt was made to do one of the following:
-
Action: There are three possible solutions:
ORA-02100 PCC: out of memory (i.e., could not allocate)
ORA-02101 PCC: inconsistent cursor cache (uce/cuc mismatch)
ORA-02102 PCC: inconsistent cursor cache (no cuc entry for this uce)
ORA-02103 PCC: inconsistent cursor cache (out-of-range cuc ref)
ORA-02104 PCC: inconsistent host cache (no cuc available)
ORA-02105 PCC: inconsistent cursor cache (no cuc entry in cache)
ORA-02106 PCC: inconsistent cursor cache (OraCursor nr is bad)
ORA-02107 PCC: this pgm too old for run-time library: please re-PCC it
ORA-02108 PCC: invalid descriptor passed to run-time library
ORA-02109 PCC: inconsistent host cache (out-of-range sit ref)
ORA-02110 PCC: inconsistent host cache (invalid sqi type)
ORA-02111 PCC: heap consistency error
ORA-02112 PCC: SELECT..INTO returns too many rows
ORA-02140 invalid tablespace name
ORA-02141 invalid OFFLINE option
ORA-02142 missing or invalid ALTER TABLESPACE option
ORA-02143 invalid STORAGE option
ORA-02144 no option specified for ALTER CLUSTER
ORA-02145 missing STORAGE option
ORA-02146 SHARED specified multiple times
ORA-02147 conflicting SHARED/EXCLUSIVE options
ORA-02148 EXCLUSIVE specified multiple times
ORA-02149 Specified partition does not exist
ORA-02153 invalid VALUES password string
ORA-02155 invalid DEFAULT tablespace identifier
ORA-02156 invalid TEMPORARY tablespace identifier
ORA-02157 no options specified for ALTER USER
ORA-02158 invalid CREATE INDEX option
ORA-02159 installed DLM does not support releasable locking mode
ORA-02160 index-organized table can not contain columns of type LONG
ORA-02161 invalid value for MAXLOGFILES
ORA-02162 invalid value for MAXDATAFILES
ORA-02163 invalid value for FREELIST GROUPS
ORA-02164 DATAFILE clause specified more than once
ORA-02165 invalid option for CREATE DATABASE
ORA-02166 ARCHIVELOG and NOARCHIVELOG specified
ORA-02167 LOGFILE clause specified more than once
ORA-02168 invalid value for FREELISTS
ORA-02169 FREELISTS storage option not allowed
ORA-02170 FREELIST GROUPS storage option not allowed
ORA-02171 invalid value for MAXLOGHISTORY
ORA-02172 The PUBLIC keyword is not appropriate for a disable thread
ORA-02173 invalid option for DROP TABLESPACE
ORA-02174 Missing required thread number
ORA-02175 invalid rollback segment name
ORA-02176 invalid option for CREATE ROLLBACK SEGMENT
ORA-02177 Missing required group number
ORA-02178 correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
ORA-02179 valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
ORA-02180 invalid option for CREATE TABLESPACE
ORA-02181 invalid option to ROLLBACK WORK
ORA-02182 savepoint name expected
ORA-02183 valid options: ISOLATION_LEVEL { SERIALIZABLE | READ COMMITTED }
ORA-02184 resource quotas are not allowed in REVOKE
ORA-02185 a token other than WORK follows COMMIT
ORA-02186 tablespace resource privilege may not appear with other privileges
ORA-02187 invalid quota specification
ORA-02189 ON tablespace required
ORA-02190 keyword TABLES expected
ORA-02191 correct syntax is: SET TRANSACTION USE ROLLBACK SEGMENT rbs
ORA-02192 PCTINCREASE not allowed for rollback segment storage clauses
ORA-02194 event specification syntax error string (minor error string) near 'string'
ORA-02195 Attempt to create string object in a string tablespace
ORA-02196 PERMANENT/TEMPORARY option already specified
ORA-02197 file list already specified
ORA-02198 ONLINE/OFFLINE option already specified
ORA-02199 missing DATAFILE/TEMPFILE clause
ORA-02200 WITH GRANT OPTION not allowed for PUBLIC
ORA-02201 sequence not allowed here
ORA-02202 no more tables permitted in this cluster
ORA-02203 INITIAL storage options not allowed
ORA-02204 ALTER, INDEX and EXECUTE not allowed for views
ORA-02205 only SELECT and ALTER privileges are valid for sequences
ORA-02206 duplicate INITRANS option specification
ORA-02207 invalid INITRANS option value
ORA-02208 duplicate MAXTRANS option specification
ORA-02209 invalid MAXTRANS option value
ORA-02210 no options specified for ALTER TABLE
ORA-02211 invalid value for PCTFREE or PCTUSED
ORA-02212 duplicate PCTFREE option specification
ORA-02213 duplicate PCTUSED option specification
ORA-02214 duplicate BACKUP option specification
ORA-02215 duplicate tablespace name clause
ORA-02216 tablespace name expected
ORA-02217 duplicate storage option specification
ORA-02218 invalid INITIAL storage option value
ORA-02219 invalid NEXT storage option value
ORA-02220 invalid MINEXTENTS storage option value
ORA-02221 invalid MAXEXTENTS storage option value
ORA-02222 invalid PCTINCREASE storage option value
ORA-02223 invalid OPTIMAL storage option value
ORA-02224 EXECUTE privilege not allowed for tables
ORA-02225 only EXECUTE and DEBUG privileges are valid for procedures
ORA-02226 invalid MAXEXTENTS value (max allowed: string)
ORA-02227 invalid cluster name
ORA-02228 duplicate SIZE specification
ORA-02229 invalid SIZE option value
ORA-02230 invalid ALTER CLUSTER option
ORA-02231 missing or invalid option to ALTER DATABASE
ORA-02232 invalid MOUNT mode
ORA-02233 invalid CLOSE mode
ORA-02234 changes to this table are already logged
ORA-02235 this table logs changes to another table already
ORA-02236 invalid file name
ORA-02237 invalid file size
ORA-02238 filename lists have different numbers of files
ORA-02239 there are objects which reference this sequence
ORA-02240 invalid value for OBJNO or TABNO
ORA-02241 must of form EXTENTS (FILE n BLOCK n SIZE n, ...)
ORA-02242 no options specified for ALTER INDEX
ORA-02243 invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
ORA-02244 invalid ALTER ROLLBACK SEGMENT option
ORA-02245 invalid ROLLBACK SEGMENT name
ORA-02246 missing EVENTS text
ORA-02247 no option specified for ALTER SESSION
ORA-02248 invalid option for ALTER SESSION
ORA-02249 missing or invalid value for MAXLOGMEMBERS
ORA-02250 missing or invalid constraint name
ORA-02251 subquery not allowed here
ORA-02252 check constraint condition not properly ended
ORA-02253 constraint specification not allowed here
ORA-02254 DEFAULT expression not allowed here
ORA-02255: NOT NULL not allowed after DEFAULT NULL
ORA-02256 number of referencing columns must match referenced columns
ORA-02257 maximum number of columns exceeded
ORA-02258 duplicate or conflicting NULL and/or NOT NULL specifications
ORA-02259 duplicate UNIQUE/PRIMARY KEY specifications
ORA-02260 table can have only one primary key
ORA-02261 such unique or primary key already exists in the table
ORA-02262 ORA-string occurs while type-checking column default value expressionexpression
ORA-02263 need to specify the datatype for this column
ORA-02264 name already used by an existing constraint
ORA-02265 cannot derive the datatype of the referencing column
ORA-02266 unique/primary keys in table referenced by enabled foreign keys
ORA-02267 column type incompatible with referenced column type
ORA-02268 referenced table does not have a primary key
ORA-02269 key column cannot be of LONG datatype
ORA-02270 no matching unique or primary key for this column-list
ORA-02271 table does not have such constraint
ORA-02272 constrained column cannot be of LONG datatype
ORA-02273 this unique/primary key is referenced by some foreign keys
ORA-02274 duplicate referential constraint specifications
ORA-02275 such a referential constraint already exists in the table
ORA-02276 default value type incompatible with column type
ORA-02277 invalid sequence name
ORA-02278 duplicate or conflicting MAXVALUE/NOMAXVALUE specifications
ORA-02279 duplicate or conflicting MINVALUE/NOMINVALUE specifications
ORA-02280 duplicate or conflicting CYCLE/NOCYCLE specifications
ORA-02281 duplicate or conflicting CACHE/NOCACHE specifications
ORA-02282 duplicate or conflicting ORDER/NOORDER specifications
ORA-02283 cannot alter starting sequence number
ORA-02284 duplicate INCREMENT BY specifications
ORA-02285 duplicate START WITH specifications
ORA-02286 no options specified for ALTER SEQUENCE
ORA-02287 sequence number not allowed here
ORA-02288 invalid OPEN mode
ORA-02289 sequence does not exist
ORA-02290 check constraint (string.string) violated
ORA-02291 integrity constraint (string.string) violated - parent key not found
ORA-02292 integrity constraint (string.string) violated - child record found
ORA-02293 cannot validate (string.string) - check constraint violated
ORA-02294 cannot enable (string.string) - constraint changed during validation
ORA-02295 found more than one enable/disable clause for constraint
ORA-02296 cannot enable (string.string) - null values found
ORA-02297 cannot disable constraint (string.string) - dependencies exist
ORA-02298 cannot validate (string.string) - parent keys not found
ORA-02299 cannot validate (string.string) - duplicate keys found
ORA-02300 invalid value for OIDGENERATORS
ORA-02301 maximum number of OIDGENERATORS is 255
ORA-02302 invalid or missing type name
ORA-02303 cannot drop or replace a type with type or table dependents
ORA-02304 invalid object identifier literal
ORA-02305 only EXECUTE, DEBUG, and UNDER privileges are valid for types
ORA-02306 cannot create a type that already has valid dependent(s)
ORA-02307 cannot alter with REPLACE option a type that is not valid
ORA-02308 invalid option string for object type column
ORA-02309 atomic NULL violation
ORA-02310 exceeded maximum number of allowable columns in table
ORA-02311 cannot alter with COMPILE option a valid type with type or table dependents
ORA-02313 object type contains non-queryable type string attribute
ORA-02315 incorrect number of arguments for default constructor
ORA-02320 failure in creating storage table for nested table column string
ORA-02322 failure in accessing storage table of the nested table column
ORA-02324 more than one column in the SELECT list of THE subquery
ORA-02327 cannot create index on expression with datatype string
ORA-02329 column of datatype string cannot be unique or a primary key
ORA-02330 datatype specification not allowed
ORA-02331 cannot create constraint on column of datatype string
ORA-02332 cannot create index on attributes of this column
ORA-02333 cannot create constraints on attributes of this column
ORA-02334 cannot infer type for column
ORA-02335 invalid datatype for cluster column
ORA-02336 column attribute cannot be accessed
ORA-02337 not an object type column
ORA-02338 missing or invalid column constraint specification
ORA-02339 invalid column specification
ORA-02340 invalid column specification
ORA-02342 replacement type has compilation errors
ORA-02344 cannot revoke execute on a type with table dependents
ORA-02345 cannot create a view with column based on CURSOR operator
ORA-02347 cannot grant privileges on columns of an object table
ORA-02348 cannot create VARRAY column with embedded LOB
ORA-02349 invalid user-defined type - type is incomplete
ORA-02351 Record string: Rejected - Error on table string, column string
ORA-02352 Direct path connection must be homogeneous
ORA-02353 Multibyte character error
ORA-02354 Conversion initialization error occurred on field string
ORA-02355 Conversion error occurred on CONSTANT field string
ORA-02356 The database is out of space. The load cannot continue
ORA-02357 Packed Decimal conversion error
ORA-02358 Zoned Decimal conversion error
ORA-02359 Field in data file exceeded maximum specified length
ORA-02360 Column not found before end of logical record (use TRAILING NULLCOLS)
ORA-02361 Initial enclosing character not found
ORA-02362 Logical record ended - second enclosing character not present
ORA-02363 No terminator found after TERMINATED and ENCLOSED field
ORA-02364 Record string: Discarded - failed all WHEN clauses
ORA-02365 Index string was made Index Unusable due to
ORA-02366 The following index(es) on table string were processed:
ORA-02367 Index string was loaded.
ORA-02368 Record string: Discarded - all columns null.
ORA-02369 Warning: Variable length field was truncated.
ORA-02370 Record string - Warning on table string, column string
ORA-02371 Loader must be at least version string.string.string.string.string for direct path
ORA-02372 Relative start position > absolute field end position.
ORA-02373 Error parsing insert statement for table string.
ORA-02374 No more slots for read buffer queue.
ORA-02375 Record string: Rejected - Error on table string
ORA-02376 invalid or redundant resource
ORA-02377 invalid resource limit
ORA-02378 duplicate resource name string
ORA-02379 profile string already exists
ORA-02380 profile string does not exist
ORA-02381 cannot drop PUBLIC_DEFAULT profile
ORA-02382 profile string has users assigned, cannot drop without CASCADE
ORA-02383 illegal cost factor
ORA-02390 exceeded COMPOSITE_LIMIT, you are being logged off
ORA-02391 exceeded simultaneous SESSIONS_PER_USER limit
ORA-02392 exceeded session limit on CPU usage, you are being logged off
ORA-02393 exceeded call limit on CPU usage
ORA-02394 exceeded session limit on IO usage, you are being logged off
ORA-02395 exceeded call limit on IO usage
ORA-02396 exceeded maximum idle time, please connect again
ORA-02397 exceeded PRIVATE_SGA limit, you are being logged off
ORA-02398 exceeded procedure space usage
ORA-02399 exceeded maximum connect time, you are being logged off
ORA-02401 cannot EXPLAIN view owned by another user
ORA-02402 PLAN_TABLE not found
ORA-02403 plan table does not have correct format
ORA-02404 specified plan table not found
ORA-02420 missing schema authorization clause
ORA-02421 missing or invalid schema authorization identifier
ORA-02422 missing or invalid schema element
ORA-02423 schema name does not match schema authorization identifier
ORA-02424 potential circular view references or unknown referenced tables
ORA-02425 create table failed
ORA-02426 privilege grant failed
ORA-02427 create view failed
ORA-02428 could not add foreign key reference
ORA-02429 cannot drop index used for enforcement of unique/primary key
ORA-02430 cannot enable constraint (string) - no such constraint
ORA-02431 cannot disable constraint (string) - no such constraint
ORA-02432 cannot enable primary key - primary key not defined for table
ORA-02433 cannot disable primary key - primary key not defined for table
ORA-02434 cannot enable unique(string) - unique key not defined for table
ORA-02435 cannot disable unique(string) - unique key not defined for table
ORA-02436 date or system variable wrongly specified in CHECK constraint
ORA-02437 cannot validate (string.string) - primary key violated
ORA-02438 Column check constraint cannot reference other columns
ORA-02439 Unique index on a deferrable constraint is not allowed
ORA-02440 Create as select with referential constraints not allowed
ORA-02441 Cannot drop nonexistent primary key
ORA-02442 Cannot drop nonexistent unique key
ORA-02443 Cannot drop constraint - nonexistent constraint
ORA-02444 Cannot resolve referenced object in referential constraints
ORA-02445 Exceptions table not found
ORA-02446 CREATE TABLE ... AS SELECT failed - check constraint violated
ORA-02447 cannot defer a constraint that is not deferrable
ORA-02448 constraint does not exist
ORA-02449 unique/primary keys in table referenced by foreign keys
ORA-02450 Invalid hash option - missing keyword IS
ORA-02451 duplicate HASHKEYS specification
ORA-02452 invalid HASHKEYS option value
ORA-02453 duplicate HASH IS specification
ORA-02454 Number of hash keys per block (string) exceeds maximum of string
ORA-02455 The number of cluster key column must be 1
ORA-02456 The HASH IS column specification must be NUMBER(*,0)
ORA-02457 The HASH IS option must specify a valid column
ORA-02458 HASHKEYS must be specified for a HASH CLUSTER
ORA-02459 Hashkey value must be a positive integer
ORA-02460 Inappropriate index operation on a hash cluster
ORA-02461 Inappropriate use of the INDEX option
ORA-02462 Duplicate INDEX option specified
ORA-02463 Duplicate HASH IS option specified
ORA-02464 Cluster definition can not be both HASH and INDEX
ORA-02465 Inappropriate use of the HASH IS option
ORA-02466 The SIZE option is not allow to be altered for HASH CLUSTERS
ORA-02467 Column referenced in expression not found in cluster definition
ORA-02468 Constant or system variable wrongly specified in expression
ORA-02469 Hash expression does not return an Oracle Number.
ORA-02470 TO_DATE, USERENV, or SYSDATE incorrectly used in hash expression.
ORA-02471 SYSDATE, UID, USER, ROWNUM, or LEVEL incorrectly used in hash expression.
ORA-02472 PL/SQL functions not allowed in hash expressions
ORA-02473 Error while evaluating the cluster's hash expression.
ORA-02474 Fixed hash area extents used (string) exceeds maximum allowed (string)
ORA-02475 maximum cluster chain block count of string has been exceeded
ORA-02476 can not create index due to parallel direct load on table
ORA-02477 can not perform parallel direct load on object string
ORA-02478 merge into base segment would overflow MAXEXTENTS limit
ORA-02479 error while translating file name for parallel load
ORA-02481 Too many processes specified for events (max string)
ORA-02482 Syntax error in event specification (string)
ORA-02483 Syntax error in process specification (string)
ORA-02486 Error in writing trace file string
ORA-02490 missing required file size in RESIZE clause
ORA-02491 missing required keyword ON or OFF in AUTOEXTEND clause
ORA-02492 missing required file block increment size in NEXT clause
ORA-02493 invalid file increment size in NEXT clause
ORA-02494 invalid or missing maximum file size in MAXSIZE clause
ORA-02495 cannot resize file string, tablespace string is read only
ORA-02700 osnoraenv: error translating ORACLE_SID
ORA-02701 osnoraenv: error translating oracle image name
ORA-02702 osnoraenv: error translating orapop image name
ORA-02703 osnpopipe: pipe creation failed
ORA-02704 osndopop: fork failed
ORA-02705 osnpol: polling of communication channel failed
ORA-02706 osnshs: host name too long
ORA-02707 osnacx: cannot allocate context area
ORA-02708 osnrntab: connect to host failed, unknown ORACLE_SID
ORA-02709 osnpop: pipe creation failed
ORA-02710 osnpop: fork failed
ORA-02711 osnpvalid: write to validation channel failed
ORA-02712 osnpop: malloc failed
ORA-02713 osnprd: message receive failure
ORA-02714 osnpwr: message send failure
ORA-02715 osnpgetbrkmsg: message from host had incorrect message type
ORA-02716 osnpgetdatmsg: message from host had incorrect message type
ORA-02717 osnpfs: incorrect number of bytes written
ORA-02718 osnprs: reset protocol error
ORA-02719 osnfop: fork failed
ORA-02720 osnfop: shmat failed
ORA-02721 osnseminit: cannot create semaphore set
ORA-02722 osnpui: cannot send break message to orapop
ORA-02723 osnpui: cannot send break signal
ORA-02724 osnpbr: cannot send break message to orapop
ORA-02725 osnpbr: cannot send break signal
ORA-02726 osnpop: access error on oracle executable
ORA-02727 osnpop: access error on orapop executable
ORA-02728 osnfop: access error on oracle executable
ORA-02729 osncon: driver not in osntab
ORA-02730 osnrnf: cannot find user logon directory
ORA-02731 osnrnf: malloc of buffer failed
ORA-02732 osnrnf: cannot find a matching database alias
ORA-02733 osnsnf: database string too long
ORA-02734 osnftt: cannot reset shared memory permission
ORA-02735 osnfpm: cannot create shared memory segment
ORA-02736 osnfpm: illegal default shared memory address
ORA-02737 osnpcl: cannot tell orapop to exit
ORA-02738 osnpwrtbrkmsg: incorrect number of bytes written
ORA-02739 osncon: host alias is too long
ORA-02750 osnfsmmap: cannot open shared memory file ?/dbs/ftt_pid.dbf
ORA-02751 osnfsmmap: cannot map shared memory file
ORA-02752 osnfsmmap: illegal shared memory address
ORA-02753 osnfsmmap: cannot close shared memory file
ORA-02754 osnfsmmap: cannot change shared memory inheritence
ORA-02755 osnfsmcre: cannot create chared memory file ?/dbs/ftt_pid.dbf
ORA-02756 osnfsmnam: name translation failure
ORA-02757 osnfop: fork_and_bind failed
ORA-02758 Allocation of internal array failed
ORA-02759 Not enough request descriptors available
ORA-02760 Client close of file failed.
ORA-02761 File number to be canceled is negative.
ORA-02762 file number to be cancelled is greater than the maximum.
ORA-02763 Unable to cancel at least one request
ORA-02764 Invalid package mode
ORA-02765 Invalid maximum number of servers
ORA-02766 Invalid maximum of request descriptors
ORA-02767 Less than one request descriptor was allocated per server
ORA-02768 Maximum number of files is invalid
ORA-02769 Setting of handler for SIGTERM failed
ORA-02770 Total number of blocks is invalid
ORA-02771 Illegal request time out value
ORA-02772 Invalid maximum server idle time
ORA-02773 Invalid maximum client wait time
ORA-02774 Invalid request list latch time out value
ORA-02775 Invalid request done signal
ORA-02776 Value for request done signal exceeds maximum
ORA-02777 Stat failed on log directory
ORA-02778 Name given for the log directory is invalid
ORA-02779 Stat failed on core dump directory
ORA-02780 Name given for the core dump directory is invalid
ORA-02781 Invalid value given for the timing wanted flag
ORA-02782 Both read and write functions were not specified
ORA-02783 Both post and wait functions were not specified
ORA-02784 Invalid shared memory ID specified
ORA-02785 Invalid shared memory buffer size
ORA-02786 Size needed for shared region is greater than segment size
ORA-02787 Unable to allocate memory for segment list
ORA-02788 Unable to find kernel process pointer in async process array
ORA-02789 Maximum number of files reached
ORA-02790 File name is too long
ORA-02791 Unable to open file for use with asynchronous I/O
ORA-02792 Unable to fstat() a file being used for asynchronous I/O.
ORA-02793 Close of asynchronous I/O failed.
ORA-02794 Client unable to get key for shared memory
ORA-02795 Request list is empty
ORA-02796 Done request is not in correct state
ORA-02797 No requests available
ORA-02798 Invalid number of requests
ORA-02799 Unable to arm signal handler
ORA-02800 Requests timed out
ORA-02801 Operations timed out
ORA-02802 No idle servers available in parallel mode
ORA-02803 Retrieval of current time failed
ORA-02804 Allocation of memory failed for log file name
ORA-02805 Unable to set handler for SIGTPA
ORA-02806 Unable to set handler for SIGALRM
ORA-02807 Allocation of memory for I/O vectors failed.
ORA-02808 Allocation of memory of open files array failed.
ORA-02809 Jump buffer not valid
ORA-02810 Unable to make temporary file name for memory mapped file
ORA-02811 Unable to attach shared memory segment
ORA-02812 Bad attach address
ORA-02813 Unable to make temporary file name in order to get key
ORA-02814 Unable to get shared memory
ORA-02815 Unable to attach shared memory
ORA-02816 Unable to kill a process
ORA-02817 Read failed
ORA-02818 Less than the number of blocks requested was read in
ORA-02819 Write failed
ORA-02820 Unable to write the requested number of blocks
ORA-02821 Unable to read the requested number of blocks.
ORA-02822 Invalid block offset
ORA-02823 Buffer is not aligned.
ORA-02824 Request free list is empty
ORA-02825 Request on free list was not free
ORA-02826 Illegal block size
ORA-02827 Invalid file number
ORA-02828 Segment free list is empty
ORA-02829 No segment of the proper size is available
ORA-02830 Segment could not be split - no free segments available
ORA-02831 Segment deallocation failed - empty segment list
ORA-02832 Segment deallocation failed - segment not on list
ORA-02833 Server was unable to close file
ORA-02834 Server unable to open file
ORA-02835 Server unable to send signal to client
ORA-02836 Unable to create temporary key file
ORA-02837 Unable to unlink temporary file
ORA-02838 Unable to arm signal handler for the alarm signal
ORA-02839 Sync of blocks to disk failed.
ORA-02840 Open of log file by client failed
ORA-02841 Server died on start up
ORA-02842 Client unable to fork a server
ORA-02843 Invalid value for kernel flag
ORA-02844 Invalid value for the leave open flag
ORA-02845 Invalid value for the timing wanted flag
ORA-02846 Unkillable server
ORA-02847 Server did not terminate when posted
ORA-02848 Asynchronous I/O package is not running
ORA-02849 Read failed because of an error
ORA-02850 File is closed
ORA-02851 Request list is empty when it should not be
ORA-02852 Invalid critical-section time out value
ORA-02853 Invalid server list latch time out value
ORA-02854 Invalid number of request buffers
ORA-02855 Number of requests is less than the number of slaves
ORA-02875 smpini: Unable to get shared memory for PGA
ORA-02876 smpini: Unable to attach to shared memory for PGA
ORA-02877 smpini: Unable to initialize memory protection
ORA-02878 sou2o: Variable smpdidini overwritten
ORA-02879 sou2o: Could not gain access to protected memory
ORA-02880 smpini: Could not register PGA for protection
ORA-02881 sou2o: Could not revoke access to protected memory
ORA-02882 sou2o: Could not register SGA for protection
ORA-02899 smscre: Cannot create SGA with Extended Shared Memory feature
ORA-03001 unimplemented feature
ORA-03002 operator not implemented
ORA-03007 obsolete feature
ORA-03008 parameter COMPATIBLE >= string needed for string
ORA-03100 communication area cannot be allocated; insufficient memory
ORA-03105 internal protocol error
ORA-03106 fatal two-task communication protocol error
ORA-03107 oranet buffer underflow
ORA-03108 oranet: ORACLE does not support this interface version
ORA-03109 oranet buffer overflow
ORA-03110 oranet: ORACLE does not support this SQL version
ORA-03111 break received on communication channel
ORA-03112 a server linked as single-task cannot use SQL*Net
ORA-03113 end-of-file on communication channel
ORA-03114 not connected to ORACLE
ORA-03115 unsupported network datatype or representation
ORA-03116 invalid buffer length passed to a conversion routine
ORA-03117 two-task save area overflow
ORA-03118 two-task coroutine has invalid state
ORA-03119 two-task detected inconsistent datatype specification
ORA-03120 two-task conversion routine: integer overflow
ORA-03121 no interface driver connected - function not performed
ORA-03122 attempt to close ORACLE-side window on user side
ORA-03123 operation would block
ORA-03124 two-task internal error
ORA-03125 client-server protocol violation
ORA-03126 network driver does not support non-blocking operations
ORA-03127 no new operations allowed until the active operation ends
ORA-03128 connection is in blocking mode
ORA-03129 the next piece to be inserted is required
ORA-03130 the buffer for the next piece to be fetched is required
ORA-03131 an invalid buffer was provided for the next piece
ORA-03132 two-task default value overflow
ORA-03200 the segment type specification is invalid
ORA-03201 the group number specification is invalid
ORA-03202 the scan limit specification is invalid
ORA-03203 concurrent update activity makes space analysis impossible
ORA-03204 the segment type specification should indicate partitioning
ORA-03205 partition name is required when partitioned type is specified
ORA-03206 maximum file size of (string) blocks in AUTOEXTEND clause is out of range
ORA-03207 subpartitioned type must be specified for composite object
ORA-03208 partitioned type must be specified for a non-composite object
ORA-03209 DBMS_ADMIN_PACKAGE invalid file/block specification
ORA-03210 DBMS_ADMIN_PACKAGE invalid option specification
ORA-03211 The segment does not exist or is not in a valid state
ORA-03212 Temporary Segment cannot be created in locally-managed tablespace
ORA-03213 Invalid Lob Segment Name for DBMS_SPACE package
ORA-03214 File Size specified is smaller than minimum required
ORA-03215 File Size specified for resize is too small
ORA-03216 Tablespace/Segment Verification cannot proceed
ORA-03217 invalid option for alter of TEMPORARY TABLESPACE
ORA-03218 invalid option for CREATE/ALTER TABLESPACE
ORA-03219 Tablespace 'string' is dictionary managed, offline, or temporary.
ORA-03220 DBMS_ADMIN_PACKAGE required parameter is NULL or missing
ORA-03221 temporary tablespaces and temporary segments must have standard block size
-
Cause: Attempt to preserve too many blocks.
-
Action: Reduce the KEEP amount.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Too large a size for an initial extent due to freelist group specification.
-
Action: Reduce number of freelist groups specified for the segment.
-
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.
-
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.
-
Cause: Users default temporary tablespace must be different from the tablespace being migrated.
-
Action: alter users default temporary tablespace to be different.
-
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.
-
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.
-
Cause: Cannot overlap control information during relocation.
-
Action: Choose another destination address.
-
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.
-
Cause: Tablespace was not dictionary managed, online, or permanent.
-
Action: Make sure the tablespace is online, permanent, or dictionary managed.
-
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.
-
Cause: Relocation of bitmaps to the said destination will make the tablespace self descriptive.
-
Action: Choose another destination DBA.
-
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.
-
Cause: For the given blocksize, the specified uniform size is insufficient.
-
Action: Specify a larger extent size and retry.
-
Cause: This segment cannot be marked corrupt because it contains data dictionary objects.
-
Action: Check the segment information and re-issue the command.
-
Cause: It is not permitted to migrate
SYSTEMtablespace from locally managed format to dictionary managed format or relocate bitmaps. -
Action: Check the tablespace name and procedure name.
-
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.
-
Cause: The DEALLOCATE UNUSED option to ALTER TABLE or ALTER INDEX is specified more than once.
-
Action: Specify the option at most once.
-
Cause: The ALLOCATE EXTENT option to ALTER TABLE or ALTER INDEX is specified more than once.
-
Action: Specify the option at most once.
-
Cause: The specified value must be an integer.
-
Action: Choose an appropriate integer value.
-
Cause: An option (DATAFILE, SIZE or INSTANCE) was specified more than once.
-
Action: Specify each option at most once.
-
Cause: The specified value is not recognized as a valid instance name.
-
Action: Use a valid name.
-
Cause: A character string literal is expected, but not found.
-
Action: Specify file names using character string literals.
-
Cause: An option other than DATAFILE, SIZE or INSTANCE was specified.
-
Action: Remove invalid option and retry the command.
-
Cause: No ALLOCATE EXTENT options were specified.
-
Action: Specified one or more of the following options: DATAFILE, SIZE or INSTANCE.
-
Cause: The datafile does not exist.
-
Action: Retry the option with the correct datafile.
-
Cause: The specified datafile does not belong to the tablespace that the object resides in.
-
Action: Retry the option with the correct datafile.
-
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.
-
Cause: The specified FREELIST GROUP number is invalid.
-
Action: Choose a number between 1 and the number of freelist groups for this object.
-
Cause: Both FREELIST GROUP and INSTANCE were specified in clause.
-
Action: Remove one of the two parameters.
-
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.
-
Cause: Invalid object specification given.
-
Action: Either specify TRUNCATE CLUSTER or TRUNCATE TABLE.
-
Cause: Expected STORAGE keyword.
-
Action: Either specify DROP STORAGE or REUSE STORAGE.
-
Cause: The table being truncated is a member of a cluster.
-
Action: Either use TRUNCATE CLUSTER or DROP TABLE.
-
Cause: Only INDEX CLUSTERS can be truncated.
-
Action: Drop and re-create the HASH CLUSTER instead of using truncate.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: string (a sequence parameter) specified was not an integer.
-
Action: Create the sequence, giving the specified parameter an integer value.
-
Cause: A sequence increment was specified to be zero.
-
Action: Specify the increment to be a non-zero value.
-
Cause: string (a sequencer parameter) had too many digits.
-
Action: Specify the parameter with the allowed number of digits.
-
Cause: MINVALUE was specified to be greater than or equal to MAXVALUE.
-
Action: Specify a MINVALUE that is less than MAXVALUE.
-
Cause: The INCREMENT specified is greater than or equal to MAXVALUE-MINVALUE.
-
Action: Specify an INCREMENT that is less than MAXVALUE-MINVALUE.
-
Cause: The given starting value is less than MINVALUE.
-
Action: Make sure that the starting value is greater than or equal to MINVALUE.
-
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.
-
Cause: The starting value would be larger than MAXVALUE.
-
Action: Make sure that the starting value is less than MAXVALUE.
-
Cause: The current value exceeds the given MAXVALUE.
-
Action: Make sure that the new MAXVALUE is larger than the current value.
-
Cause: The value in the CACHE clause was one.
-
Action: Specify NOCACHE, or a value larger than one.
-
Cause: The value specified for one of the sequence parameters exceeds limits.
-
Action: Specify a parameter within these limits.
-
Cause: The object specified cannot have sequence DDLs performed on it.
-
Action: Re-enter the statement being careful with the spelling of the name.
-
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.
-
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.
-
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.
-
Cause: Sequence was dropped while processing its next value.
-
Action: Re-create the sequence.
-
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.
-
Cause: The value specified for initialization parameter _SCN_SCHEME is not recognized as one of the defined schemes.
-
Action: Reassign a proper value.
-
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.
-
Cause: While trying to lock a library object, a deadlock is detected.
-
Action: Retry the operation later.
-
Cause: While waiting to lock a library object, a timeout is occurred.
-
Action: Retry the operation later.
-
Cause: Had to wait to lock a library object during a nowait request.
-
Action: Retry the operation later.
-
Cause: Cannot generate diana for an object because of lock conflict.
-
Action: Report this error to your support representative.
-
Cause: The table or view being queried might be missing. The error number indicates the error.
-
Action: Fix the error.
-
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.
-
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.
-
Cause: An attempt was made to set
WORKAREA_SIZE_POLICYtoAUTOwhilePGA_AGGREGATE_TARGETis not specified. -
Action: Before setting
WORKAREA_SIZE_POLICY, setPGA_AGGREGATE_TARGETto 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). -
Cause: The system had insufficient memory to grow the pool to the specified size.
-
Action: Specify a smaller value to grow the pool.
-
Cause: Attempt to create a package body before creating its package specification.
-
Action: Create the package specification first before creating the package body.
-
Cause: Attempt to access a procedure, function, package, or package body that does not exist.
-
Action: Make sure the name is correct.
-
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.)
-
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.
-
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.
-
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.
-
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.
-
Cause: The required procedure, function, or package name is invalid or missing.
-
Action: Specify a valid name.
-
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.
-
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.
-
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.
-
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.
-
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).
-
Cause: Attempt to execute a stored procedure without sufficient privileges.
-
Action: Get necessary privileges.
-
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.
-
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.
-
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.
-
Cause: Attempt to execute a stored procedure that has been invalidated.
-
Action: Recompile the stored procedure.
-
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.
-
Cause: Attempt to execute a non-procedure.
-
Action: Make sure that a correct name is given.
-
Cause: Attempt to execute a non-existent stored procedure.
-
Action: Make sure that a correct name is given.
-
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.
-
Cause: An invalid trigger name was specified.
-
Action: Verify that trigger name is not a reserved keyword.
-
Cause: The trigger statement is missing the BEFORE/AFTER/INSTEAD OF clause.
-
Action: Specify either BEFORE, AFTER or INSTEAD OF.
-
Cause: An invalid trigger type was given.
-
Action: Specify either INSERT, UPDATE or DELETE.
-
Cause: A column list was specified for a non-update trigger type.
-
Action: Remove the column list.
-
Cause: An invalid name was given in the referencing clause.
-
Action: Verify the referencing name is not a reserved word.
-
Cause: An statement was given for the trigger action.
-
Action: Re-specify the trigger action.
-
Cause: An invalid NEW or OLD specification was given for a column.
-
Action: Re-specify the column using the correct NEW or OLD specification.
-
Cause: The when clause can only be specified for row level triggers.
-
Action: Remove the when clause or specify for each row.
-
Cause: The referencing clause specifies identical values for NEW and OLD.
-
Action: Re-specify either the OLD or NEW referencing value.
-
Cause: The create TRIGGER statement is invalid.
-
Action: Check the statement for correct syntax.
-
Cause: The TRIGGER name is invalid.
-
Action: Check the trigger name.
-
Cause: The TRIGGER name or type already exists.
-
Action: Use a different trigger name or drop the trigger which is of the same name.
-
Cause: The trigger is accessing "new" or "old" values in a table trigger.
-
Action: Remove any new or old references.
-
Cause: The variable referenced in the trigger body is invalid.
-
Action: See the Oracle9i SQL Reference for valid trigger variable types.
-
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.
-
Cause: Old values can only be read and not changed.
-
Action: Do not attempt to change an old variable.
-
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.
-
Cause: ROWIDs can only be read and not changed.
-
Action: Do not attempt to change an ROWID value.
-
Cause: A runtime error occurred during execution of a trigger.
-
Action: Check the triggers which were involved in the operation.
-
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.
-
Cause: Trigger is of duplicate event and trigger time.
-
Action: Combine the triggering information into one trigger which is fired at the given time.
-
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.
-
Cause: A trigger attempted to commit or roll back.
-
Action: Rewrite the trigger so it does not commit or roll back.
-
Cause: A trigger attempted to reference a long column in the triggering table.
-
Action: Do not reference the long column.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
ORA-03230 segment only contains string blocks of unused space above high water mark
ORA-03231 the INITIAL extent may not be deallocated
ORA-03233 unable to extend table string.string subpartition string by string in tablespace string
ORA-03234 unable to extend index string.string subpartition string by string in tablespace string
ORA-03235 max # extents (string) reached in table string.string subpartition string
ORA-03236 max # extents (string) reached in index string.string subpartition string
ORA-03237 Initial Extent of specified size cannot be allocated in tablespace (string)
ORA-03238 unable to extend LOB segment string.string subpartition string by string in tablespace string
ORA-03239 maxextents (string) reached in LOB segment string.string subpartition string
ORA-03240 User's temporary tablespace same as tablespace being migrated
ORA-03241 Invalid unit size
ORA-03242 Tablespace migration retried 500 times
ORA-03243 destination dba overlaps with existing control information
ORA-03244 No free space found to place the control information
ORA-03245 Tablespace has to be dictionary managed, online and permanent to be able to migrate
ORA-03246 Invalid block number specified
ORA-03247 Invalid block number specified
ORA-03248 Too much of segment creation activity during migration
ORA-03249 Uniform size for auto segment space managed tablespace should have atleast string blocks.
ORA-03250 Cannot mark this segment corrupt
ORA-03251 Cannot issue this command on SYSTEM tablespace
ORA-03274 both ALLOCATE EXTENT and DEALLOCATE UNUSED options are specified
ORA-03275 duplicate DEALLOCATE option specification
ORA-03276 duplicate ALLOCATE EXTENT option specification
ORA-03277 invalid SIZE specified
ORA-03278 duplicate ALLOCATE EXTENT option specification
ORA-03279 invalid INSTANCE specified
ORA-03280 invalid DATAFILE filename specified
ORA-03281 invalid ALLOCATE EXTENT option
ORA-03282 missing ALLOCATE EXTENT option
ORA-03283 specified datafile string does not exist
ORA-03284 datafile string is not a member of tablespace string
ORA-03286 ALLOCATE EXTENT not valid for HASH CLUSTERS
ORA-03287 invalid FREELIST GROUP specified
ORA-03288 both FREELIST GROUP and INSTANCE parameters may not be specified
ORA-03289 partition name and segment type do not match
ORA-03290 Invalid truncate command - missing CLUSTER or TABLE keyword
ORA-03291 Invalid truncate option - missing STORAGE keyword
ORA-03292 Table to be truncated is part of a cluster
ORA-03293 Cluster to be truncated is a HASH CLUSTER
ORA-03296 cannot resize datafile - file string not found
ORA-03297 file contains used data beyond requested RESIZE value
ORA-03298 cannot shrink datafile - file string is under hot backup
ORA-03299 cannot create dictionary table string
ORA-04000 the sum of PCTUSED and PCTFREE cannot exceed 100
ORA-04001 sequence parameter string must be an integer
ORA-04002 INCREMENT must be a non-zero integer
ORA-04003 sequence parameter string exceeds maximum size allowed (string digits)
ORA-04004 MINVALUE must be less than MAXVALUE
ORA-04005 INCREMENT must be less than MAXVALUE minus MINVALUE
ORA-04006 START WITH cannot be less than MINVALUE
ORA-04007 MINVALUE cannot be made to exceed the current value
ORA-04008 START WITH cannot be more than MAXVALUE
ORA-04009 MAXVALUE cannot be made to be less than the current value
ORA-04010 the number of values to CACHE must be greater than 1
ORA-04011 sequence string must range between string and string
ORA-04012 object is not a sequence
ORA-04013 number to CACHE must be less than one cycle
ORA-04014 descending sequences that CYCLE must specify MINVALUE
ORA-04015 ascending sequences that CYCLE must specify MAXVALUE
ORA-04016 sequence string no longer exists
ORA-04017 invalid value string (length = string) for parameter max_dump_file_ size
ORA-04018 invalid value string for parameter _scn_scheme
ORA-04019 SCN scheme incompatible with other instances
ORA-04020 deadlock detected while trying to lock object stringstringstringstringstring
ORA-04021 timeout occurred while waiting to lock object stringstringstringstringstring
ORA-04022 nowait requested, but had to wait to lock dictionary object
ORA-04028 cannot generate diana for object stringstringstringstringstring
ORA-04029 error ORA-string occurred when querying stringstringstring
ORA-04030 out of process memory when trying to allocate string bytes (string,string)
ORA-04031 unable to allocate string bytes of shared memory ("string","string","string","string")
ORA-04032 pga_aggregate_target must be set before switching to auto mode
ORA-04033 insufficient memory to grow pool
ORA-04041 package specification must be created first before creating package body
ORA-04042 procedure, function, package, or package body does not exist
ORA-04043 object string does not exist
ORA-04044 procedure, function, package, or type is not allowed here
ORA-04045 errors during recompilation/revalidation of string.string
ORA-04046 results of compilation are too large to support
ORA-04047 object specified is incompatible with the flag specified
ORA-04050 invalid or missing procedure, function, or package name
ORA-04051 user string cannot use database link string.string
ORA-04052 error occurred when looking up remote object stringstringstringstringstring
ORA-04053 error occurred when validating remote object stringstringstringstringstring
ORA-04054 database link string does not exist
ORA-04055 Aborted: "string" formed a non-REF mutually-dependent cycle with "string".
ORA-04060 insufficient privileges to execute string
ORA-04061 existing state of string has been invalidated
ORA-04062 string of string has been changed
ORA-04063 string has errors
ORA-04064 not executed, invalidated string
ORA-04065 not executed, altered or dropped string
ORA-04066 non-executable object, string
ORA-04067 not executed, string does not exist
ORA-04068 existing state of packagesstringstringstring has been discarded
ORA-04070 invalid trigger name
ORA-04071 missing BEFORE, AFTER or INSTEAD OF keyword
ORA-04072 invalid trigger type
ORA-04073 column list not valid for this trigger type
ORA-04074 invalid REFERENCING name
ORA-04075 invalid trigger action
ORA-04076 invalid NEW or OLD specification
ORA-04077 WHEN clause cannot be used with table level triggers
ORA-04078 OLD and NEW values cannot be identical
ORA-04079 invalid trigger specification
ORA-04080 trigger 'string' does not exist
ORA-04081 trigger 'string' already exists
ORA-04082 NEW or OLD references not allowed in table level triggers
ORA-04083 invalid trigger variable 'string'
ORA-04084 cannot change NEW values for this trigger type
ORA-04085 cannot change the value of an OLD reference variable
ORA-04086 trigger description too long, move comments into triggering code
ORA-04087 cannot change the value of ROWID reference variable
ORA-04088 error during execution of trigger 'string.string'
ORA-04089 cannot create triggers on objects owned by SYS
ORA-04090 'string' specifies same table, event and trigger time as 'string'
ORA-04091 table string.string is mutating, trigger/function may not see it
ORA-04092 cannot string in a trigger
ORA-04093 references to columns of type LONG are not allowed in triggers
ORA-04094 table string.string is constraining, trigger may not modify it
ORA-04095 trigger 'string' already exists on another table, cannot replace it
ORA-04096 trigger 'string' has a WHEN clause which is too large, limit 2K
ORA-04097 DDL conflict while trying to drop or alter a trigger
ORA-04098 trigger 'string.string' is invalid and failed re-validation
ORA-04099 trigger 'string' is valid but not stored in compiled form
|  Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
6
ORA-04100 to ORA-07499
-
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.
-
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.
-
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.
-
Cause: A valid service identifier existed before the sequence number service was opened.
-
Action: Verify that the instance is completely shut down.
-
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.
-
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.
-
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.
-
Cause: Autologin unable to open port.
-
Action: Check log file for operating system-specific error code.
-
Cause: Autologin unable to change port attributes.
-
Action: Check log file for operating system-specific error code.
-
Cause: Autologin unable to read from port.
-
Action: Check log file for operating system-specific error code.
-
Cause: Autologin unable to write to port.
-
Action: Check log file for operating system-specific error code.
-
Cause: Autologin unable to open dialogue file.
-
Action: Check connect string for accuracy/typos.
-
Cause: Autologin unable to read dialogue file.
-
Action: Check log file for operating system-specific error code.
-
Cause: Expected response never received.
-
Action: Check log file for operating system-specific error code.
-
Cause: Dialogue file contains syntax error.
-
Action: Correct the dialogue file.
-
Cause: Full file specification for dialogue file exceeds 64 bytes.
-
Action: Amend connect string accordingly.
-
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.
-
Cause: One of the following:
-
Action: Simplify dialogue or split into two and link with the MORE command.
-
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.
-
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.
-
Cause: Syntax error in login string.
-
Action: Resubmit with correct string.
-
Cause: Asynchronous driver unable to complete initialization.
-
Action: Check log file for operating system-specific error code.
-
Cause: Asynchronous driver unable to establish connection with partner.
-
Action: Check log file for operating system-specific error code.
-
Cause: No free channel.
-
Action: Contact Oracle Support Services.
-
Cause: Asynchronous driver unable to open port.
-
Action: Check log file for operating system-specific error code.
-
Cause: Virtual Terminal Manager unable to read/write to port.
-
Action: Check log file for operating system-specific error code.
-
Cause: Asynchronous driver generated for server-only, but client service requested.
-
Action: Contact Oracle Support Services.
-
Cause: Asynchronous driver unable to close port.
-
Action: Check log file for operating system-specific error code.
-
Cause: Asynchronous driver unable to close channel.
-
Action: Check log file for operating system-specific error code.
-
Cause: Asynchronous driver unable to initialize for logging I/O.
-
Action: Contact Oracle Support Services.
-
Cause: Asynchronous driver unable to assign port to channel.
-
Action: Contact Oracle Support Services.
-
Cause: Node name specified in host string is unknown (probably misspelled).
-
Action: Retry with correct node name.
-
Cause: Host string contains reference to object (which does not exist):
@d:node-obj => object is ORDNobj;
-
Action: Retry with correct object name or create the required object on host node.
-
Cause: Host string contains invalid username/password.
-
Action: Retry with correct username/password.
-
Cause: Connection with partner was made but was rejected.
-
Action: Contact your network administrator.
-
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.
-
Cause: Insufficient system resources are available to complete the connection; for example, all DECnet channels are in use.
-
Action: Contact your network administrator.
-
Cause: Host node is down.
-
Action: Contact your network administrator.
-
Cause: Connect failed for unexpected reason (see OSD error).
-
Action: Contact Oracle Support Services.
-
Cause: Syntax error in login string.
-
Action: Resubmit with correct string.
-
Cause: Driver gets error while doing network close operation.
-
Action: Contact Oracle Support Services.
-
Cause: Driver gets I/O error while doing network read operation.
-
Action: Contact Oracle Support Services.
-
Cause: Driver gets I/O error while doing network write operation.
-
Action: Contact Oracle Support Services.
-
Cause: Connect failed because of insufficient byte count quota.
-
Action: Increase byte count quota.
-
Cause: Insufficient dynamic memory available for connection context area.
-
Action: Contact Oracle Support Services.
-
Cause: Host name specified in the login (connect) string is unknown.
-
Action: Check spelling; make sure name is in the TCP/IP HOST file.
-
Cause: Process open file quota probably exceeded.
-
Action: Contact Oracle Support Services.
-
Cause: No entry in SERVICES file for Oracle server.
-
Action: Add (ORASRV) entry to the TCP/IP SERVICES file.
-
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.
-
Cause: I/O error occurred while attempting network read operation.
-
Action: Contact Oracle Support Services.
-
Cause: I/O error occurred while attempting network write operation.
-
Action: Contact Oracle Support Services.
-
Cause: Error occurred while closing a socket.
-
Action: Contact Oracle Support Services.
-
Cause: The buffer size specified in the login string exceeds the allowed maximum (of 4096).
-
Action: Re-submit with valid buffer size.
-
Cause: The maximum no. of concurrently open connections has been reached.
-
Action: Exit an application with an open connection which is no longer required.
-
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).
-
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.
-
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.
-
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.
-
Cause: The Oracle server process was started but failed to complete its initialization.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The TCP/IP network driver is not loaded.
-
Action: Check that the TCP/IP driver is loaded correctly.
-
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.
-
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.
-
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.
-
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.
-
Cause: The Oracle server process was started but exited unexpectedly. Possible causes:
-
Action: If appropriate action is not obvious from the ORASRV output file, then contact Oracle Support Services.
-
Cause: The Oracle server process was started but was unable to open the socket passed to it by ORASRV.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The database administrator on the host has varied the SID offline.
-
Action: Wait for it to be varied back online.
-
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.
-
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.
-
Cause: ORACLE_HOME environment variable not set.
-
Action: Make sure that the ORACLE_HOME environment variable has been properly set and exported.
-
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.
-
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.
-
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.
-
Cause: An error occurred while reading the NTT communications link.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: An error occurred while writing the NTT communications link.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: An error occurred while reading the NTT communications link.
-
Action: Contact Oracle Support Services.
-
Cause: An error occurred while writing the NTT communications link.
-
Action: Contact Oracle Support Services.
-
Cause: The call to NRANGE() failed while attempting to establish a connection.
-
Action: Contact Oracle Support Services.
-
Cause: The call to NFCONN() failed while attempting to establish a connection.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The NTT two-task driver received an unexpected message type.
-
Action: Contact Oracle Support Services.
-
Cause: The NTT two-task driver received an unexpected message type.
-
Action: Contact Oracle Support Services.
-
Cause: The NTT two-task driver failed on an internal consistency check.
-
Action: Contact Oracle Support Services.
-
Cause: The NTT two-task driver failed on an internal consistency check.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: One of the following:
-
Action: Check sequentially for the above causes and eliminate the actual cause found.
-
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.
-
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.
-
Cause: The communication between user and Oracle is out of synchronization. This message should not normally be issued.
-
Action: Contact Oracle Support Services.
-
Cause: The IPA driver tried to write a message in the queue that was too big for the queue.
-
Action: Contact Oracle Support Services.
-
Cause: A fatal error occurred during the resetting of the connection.
-
Action: Contact Oracle Support Services.
-
Cause: You have exhausted all your connections.
-
Action: Try again when some of the current users have logged off.
-
Cause: The SQL*Net IPA servers have not been started.
-
Action: Run IPACTL.
-
Cause: Environment variable(s) not set correctly.
-
Action: Check and correct.
-
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.
-
Cause: Incorrect outgoing service name supplied.
-
Action: Check and correct the service name.
-
Cause: The shared memory has not been set up correctly.
-
Action: Contact your system administrator.
-
Cause: Fatal interprocess communication error.
-
Action: Contact your system administrator.
-
Cause: The connect string is malformed.
-
Action: Check and correct.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An internal error has occurred in the shared memory handling.
-
Action: Contact Oracle Support Services.
-
Cause: Fatal interprocess communication error.
-
Action: Contact your system administrator.
-
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.
-
Cause: The login (connect) string contains an invalid driver designator.
-
Action: Correct the string and re-submit.
-
Cause: Error occurred while attempting to read a break message.
-
Action: Contact Oracle Support Services.
-
Cause: System unable to allocate needed virtual memory.
-
Action: Configure more memory, reduce load, or try again.
-
Cause: Syntax error in login string.
-
Action: Correct string and re-submit.
-
Cause: Unable to reset out of break state.
-
Action: Contact Oracle Support Services.
-
Cause: Error occurred while attempting to send a break message.
-
Action: Contact Oracle Support Services.
-
Cause: Error occurred while attempting to set up asynchronous handlers for in-coming, out-of-band break messages.
-
Action: Contact Oracle Support Services.
-
Cause: Message from partner contains bad header.
-
Action: Contact Oracle Support Services.
-
Cause: Unable to establish connection.
-
Action: Use diagnostic procedures to ascertain exact problem.
-
Cause: Error occurred while testing I/O status of the network connection.
-
Action: Contact Oracle Support Services.
-
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.
-
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).
-
Cause: Error found during recomputation of checksum or CRC.
-
Action: Possible hardware failures of communication nodes. Contact system administrator immediately.
-
Cause: Unable to transmit data to remote host.
-
Action: Try reconnect to remote host, and contact your system administrator.
-
Cause: Unable to receive data from remote host.
-
Action: Try reconnect to remote host, and contact your system administrator.
-
Cause: A function was called with an invalid argument.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The I/O buffer was not aligned on a 2K boundary.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An invalid event ID is passed in to this routine.
-
Action: The additional information indicates the event ID.
-
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.
-
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.
-
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.
-
Cause: Invalid Oracle process ID is passed in to this routine.
-
Action: The additional information indicates the process ID.
-
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.
-
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.
-
Cause: This is a rare internal error message. Memory has been exhausted or corrupted.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error message. An error has been detected in a PL/SQL program.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: A call to PL/SQL function completed, but no
RETURNstatement was executed. -
Action: Rewrite PL/SQL function, making sure that it always returns a value of a proper type.
-
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.
-
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.
-
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.
-
Cause: This indicates a version clash between some package distributed with an Oracle product and the product executable.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: An attempt was made to open a cursor that was already open.
-
Action: Close cursor first before reopening.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An error occurred while passing a Probe operation to the server for execution.
-
Action: Refer to the entry for the embedded error message.
-
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.
-
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.
-
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.
-
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.
-
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
-
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.
-
Cause: The option specified is an unsupported feature for external procedures.
-
Action: Correct the syntax in the external specification.
-
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.
-
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.
-
Cause: An error occurred in SQLLIB during execution of a Pro* external procedure.
-
Action: The message text indicates the actual SQLLIB error that occurred.
-
Cause: An error occurred during execution of a PL/SQL profiler procedure.
-
Action: Check the stacked errors for more details.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A PL/SQL internal error occurred.
-
Action: Report as a bug; the first argument is the internal error number.
-
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.
-
Cause: DDL statement is executed dynamically in illegal PL/SQL context.
-
Action: Use
EXECUTE IMMEDIATEwithoutUSINGandINTOclauses to execute the DDL statement. -
Cause: EXECUTE IMMEDIATE with a
RETURNINGclause is used to execute dynamicUPDATE,INSERT, orDELETEstatements only. -
Action: Use the
RETURNINGclause inEXECUTE IMMEDIATEforINSERT,UPDATE, orDELETEstatements only. For other statements, use theUSINGclause instead. -
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.
-
Cause: One possible cause might be that there are too many DLLs open at the same time.
-
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.
-
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.
-
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.
-
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.
-
Cause: Internal error from the DBMS_PIPE package.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The sender put different datatype on the pipe than that being requested (package DBMS_PIPE). The numbers are:
-
Action: Check that the sender and receiver agree on the number and types of items placed on the pipe.
-
Cause: Internal error from the DBMS_PIPE package.
-
Action: Contact Oracle Support Services.
-
Cause: An attempt was made to parse an unsupported statement using procedure
PARSEprovided by packageDBMS_SQL. -
Action: Only statements which begin with
SELECT,DELETE,INSERT,UPDATE,LOCK,BEGIN,DECLARE, or<<(PL/SQL label delimiter) are supported. -
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.
-
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.
-
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.
-
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.
-
Cause: An invalid number of rows was specified in a call to the procedure
DEFINE_COLUMNin the packageDBMS_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 toDEFINE_COLUMNmust specify the same number of rows. -
Action: Specify a number that matches that for previously defined columns.
-
Cause: An invalid number of values to be bound was specified in a call to the procedure
BIND_VARIABLEin the packageDBMS_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.
-
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.
-
Cause: A collection with zero elements was bound to a bind variable in a call to procedure
BIND_ARRAYin the packageDBMS_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.
-
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.
-
Cause: One of the following:
-
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.
-
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.
-
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.
-
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
SELECTlist,VALUESclause of anINSERTstatement, orSETclause of anUPDATEstatement 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.
-
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.
-
Cause: Could not find a function (if an
INTOclause was present) or a procedure (if the statement did not have anINTOclause) to call. -
Action: Change the statement to invoke a function or procedure.
-
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.
-
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.
-
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.
-
Cause: A
CASEstatement must either list all possible cases or have anelseclause. -
Action: Add all missing cases or an
ELSEclause. -
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_FLAGSparameter toINTERPRETED. -
Cause: The SNA software is not running.
-
Action: Start the SNA software and try again.
-
Cause: The database string in the connect was invalid.
-
Action: Provide a valid database string, as defined in documentation.
-
Cause: Context area failure.
-
Action: Contact Oracle Support Services.
-
Cause: Operating system refused request for memory.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: SNA software switched from send to receive unexpectedly.
-
Action: Check the SNA configuration data, particularly parameters associated with a session.
-
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.
-
Cause: A reset was issued while in send state.
-
Action: Check the SNA LOG data, if relevant, for further information.
-
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.
-
Cause: LU6.2 driver was unable to deallocate gracefully.
-
Action: Check the reason for deallocation. Consult the SNA LOG data.
-
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.
-
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.
-
Cause: TLI received a message with an unrecognizable message type.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: TLI could not allocate heap space for the context area.
-
Action: Contact Oracle Support Services.
-
Cause: TLI failed to send a break message across the connection.
-
Action: Contact Oracle Support Services.
-
Cause: TLI failed to receive an expected break message.
-
Action: Contact Oracle Support Services.
-
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.)
-
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.
-
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.
-
Cause: TLI encountered an error receiving a message from the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error sending a message across the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI failed to send a break message while handling an interrupt signal from the user.
-
Action: Contact Oracle Support Services.
-
Cause: TLI failed to assign a network address to the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI failed to accept a connection request from the client.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The remote TLI server received an undefined request.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: TLI failed to open the Streams clone device associated with the transport provider.
-
Action: Contact Oracle Support Services.
-
Cause: TLI cannot allocate space for the client's connection information.
-
Action: Contact Oracle Support Services.
-
Cause: TLI cannot allocate space for the client's disconnection information.
-
Action: Contact Oracle Support Services.
-
Cause: TLI failed to receive an expected disconnection message during connection release.
-
Action: Contact Oracle Support Services.
-
Cause: TLI failed to connect the client to the remote server.
-
Action: Check that the remote TLI server is running.
-
Cause: TLI failed to properly close a connection after an error was received.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The TLI server failed to open the Streams device associated with the transport provider.
-
Action: Contact Oracle Support Services.
-
Cause: The TLI server cannot allocate space for its requested network address.
-
Action: Contact Oracle Support Services.
-
Cause: The TLI server cannot allocate space for its actual network address.
-
Action: Contact Oracle Support Services.
-
Cause: The TLI server failed to assign the correct network address on which to listen for connections.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: TLI cannot allocate space for the TLI server's connection information.
-
Action: Contact Oracle Support Services.
-
Cause: The TLI server encountered an error while listening for connection requests.
-
Action: Contact Oracle Support Services.
-
Cause: TLI cannot allocate space for the TLI server's disconnection information.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The Oracle process started by the TLI server was unable to synchronize its inherited connection.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: A call to SIGACTION() returned with a system error.
-
Action: Contact Oracle Support Services.
-
Cause: For SVR4, the NETDIR_GETBYNAME() call failed for some unknown reason.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The TLI server was unable to close a connection after passing it to an Oracle process.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The TLI server received an invalid command.
-
Action: Contact Oracle Support Services.
-
Cause: TLI was not able to retrieve an expected disconnect message while closing the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error sending a disconnect message closing the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error receiving an expected disconnect message while closing the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error sending a disconnect message closing the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI was not able to retrieve an expected disconnect message while closing the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error awaiting a disconnect message while closing the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI failed to close the communication channel after receiving a disconnect message.
-
Action: Contact Oracle Support Services.
-
Cause: TLI cannot allocate space for disconnection information while closing the communication channel.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while sending its version information during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while awaiting the expected version information during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while sending a command message during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while awaiting the expected command message during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while sending break-mode message during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while awaiting the expected break-mode message during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while sending the connection parameters during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while awaiting the expected connection parameter message during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while sending the completion status message during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while awaiting the expected completion status message during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while awaiting an expected error message during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI encountered an error while awaiting the expected negotiation message during connection establishment.
-
Action: Contact Oracle Support Services.
-
Cause: TLI was unable to poll the communication channel for possible incoming messages.
-
Action: Contact Oracle Support Services.
-
Cause: TLI received an unexpected event while polling the communication channel for possible incoming messages.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
Cause: An unknown event occurred on the client's listening socket.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The IPX driver has not been correctly installed.
-
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
-
Cause: The socket endpoint for sending SAP packet was corrupted for some unknown reason.
-
Action: Contact Oracle Support Services.
-
Cause: A step in the SPX/IPX protocol initialization failed.
-
Action: Check the previous error reported, and follow corrective action.
-
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.
-
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.
-
Cause: The IPX driver has not been correctly installed.
-
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
-
Cause: The IPX driver has not been correctly installed.
-
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
Cause: The SPX driver has not been correctly installed.
-
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
-
Cause: The SPX driver has not been correctly installed.
-
Action: Reinvoke the Oracle root installation. If problem continues, contact Oracle Support Services.
-
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.
-
Cause: CMX is not started on your system.
-
Action: Install and/or start CMX on your system.
-
Cause: Local application ORACMX has no local name assigned.
-
Action: Enter unique local name for ORACMX in the TNS directory.
-
Cause: CCP-xxxx is not started.
-
Action: Start your CCP software on the communication controller.
-
Cause: Remote application not entered in TNS directory.
-
Action: Enter remote application in TNS directory.
-
Cause: No local name assigned to remote application.
-
Action: Assign local name to remote application.
-
Cause: Remote partner not listening.
-
Action: Make sure remote node has CMX installed and running make sure ORACMX is running on remote host.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Remote partner aborted.
-
Action: Contact Oracle Support Services.
-
Cause: Remote partner aborted.
-
Action: Contact Oracle Support Services.
-
Cause: Remote partner aborted.
-
Action: Contact Oracle Support Services.
-
Cause: Oracle process not found or wrong mode (should be 4751).
-
Action: Change /etc/oratab or set mode to 4751.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: ORACMX has been stopped, or user process has been aborted.
-
Action: Contact Oracle Support Services.
-
Cause: Connect sequence out of sync.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Remote partner aborted.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Received packets are corrupted.
-
Action: Contact Oracle Support Services.
-
Cause: Received packets are corrupted.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Break handling out of sync.
-
Action: Contact Oracle Support Services.
-
Cause: Received packets are corrupted.
-
Action: Contact Oracle Support Services.
-
Cause: Partner is not responding.
-
Action: Make sure partner is up and running and reachable.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: ORACLE_SID is not entered in remote ORATAB.
-
Action: Add ORACLE_SID to remote ORATAB.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: Internal error in CMX.
-
Action: Contact Oracle Support Services.
-
Cause: SQL*Net AppleTalk error codes base. This is not an error.
-
Action: No action required.
-
Cause: AppleTalk API received error in VMS system service.
-
Action: Contact Oracle Support Services.
-
Cause: Peer program may have aborted.
-
Action: Investigate network problems and try again.
-
Cause: Not enough memory available.
-
Action: Check VMS process quotas and/or SYSGEN parameters.
-
Cause: Erroneous file name.
-
Action: Check path name for server output file, or SQL*Net Appletalk Logical names and symbols.
-
Cause: Too many database connections.
-
Action: Check ATKSRV_MAXCON parameter in configuration file.
-
Cause: Unable to get Appletalk host name.
-
Action: Check Appletalk configuration.
-
Cause: Incoming SQL*Net connection specified invalid SID name.
-
Action: Specify correct SID in connect string and retry.
-
Cause: Unable to access CONFIG.ATK.
-
Action: Check file protections.
-
Cause: Buffered I/O quota exceeded.
-
Action: Increase BIOLM using AUTHORIZE utility and retry.
-
Cause: SQL*Net Appletalk listener could not create log file.
-
Action: Check directory path and protections.
-
Cause: You do not have sufficient privileges for the attempted operation.
-
Action: Check process privileges and retry.
-
Cause: Host name specified in the login (connect string) is unknown.
-
Action: Check spelling; make sure name is in the X.25 HOST file.
-
Cause: The buffer size specified in the login string must be between 5 and 4096.
-
Action: Re-submit with valid buffer size.
-
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).
-
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.
-
Cause: Process open file quota probably exceeded.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: Call back address probably same as called address.
-
Action: Verify that the callback address and called address are different.
-
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.
-
Cause: The environment variable $(ORACLE_SID) is not set.
-
Action: Set ORACLE_SID environment variable.
-
Cause: $(ORACLE_HOME) environment variable not set.
-
Action: Set ORACLE_HOME.
-
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.
-
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.
-
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.
-
Cause: Time() system call returned an error. Possible operating system error.
-
Action: Check additional information returned. Contact Oracle Support Services.
-
Cause: GETTIMEOFDAY() system call returned an error. Possible operating system error.
-
Action: Check additional information returned. Contact Oracle Support Services.
-
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.
-
Cause: The FSYNC system call returned an error. Possible operating system error.
-
Action: Check additional information returned. Contact Oracle Support Services.
-
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.
-
Cause: GETRUSAGE system call returned an error. Possible operating system error.
-
Action: Check additional information returned. Contact Oracle Support Services.
-
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.
-
Cause: The times system call returned an error. Possible operating system error.
-
Action: Check additional information returned. Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
Cause: GETENV call returned a null pointer.
-
Action: Set the environment variable and try again.
-
Cause: UNIX system() call failed.
-
Action: Examine system error message.
-
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.
-
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.
-
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.
-
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.
-
Cause: Fork system call failed to create additional process. Probable resource limit reached.
-
Action: Check additional information returned. Retry operation. Contact system administrator.
-
Cause: The ULIMIT system call returned an error.
-
Action: Check errno and contact Oracle Support Services.
-
Cause: Additional information returned is error returned from SLTLN.
-
Action: Check additional information.
-
Cause: The IOCTL call returned an error. Possible operating system error.
-
Action: Check additional information for errno. Contact Oracle Support Services.
-
Cause: The IOCTL call returned an error. Possible operating system error.
-
Action: Check additional information for errno. Contact Oracle Support Services.
-
Cause: The IOCTL call returned an error. Possible operating system error.
-
Action: Check additional information for errno. Contact Oracle Support Services.
-
Cause: Error in MPCNTL system call.
-
Action: Examine errno. Contact your system administrator.
-
Cause: FOPEN failed to open file.
-
Action: Try to determine which file was not opened. Check that file exists and is accessible.
-
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.
-
Cause: An error was encountered when closing the file. Possible operating system error.
-
Action: Contact system administrator.
-
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.
-
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.
-
Cause: Unable to write item to file. Possible operating system error. Possible permissions problem.
-
Action: Retry operation.
-
Cause: Unable to open error file. Possible permissions problem.
-
Action: Verify permission on error message file. Check additional information for errno.
-
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.
-
Cause: Unable to close file. Possible operating system error.
-
Action: Contact system administrator. Check additional information for errno.
-
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.
-
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.
-
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.
-
Cause: Additional information indicates error returned from SLTLN.
-
Action: Check additional information.
-
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.
-
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.
-
Cause: An attempt was made to move and write to a bad device address.
-
Action: Check errno. Possible lack of space on device.
-
Cause: SFOFI returns an error. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: SFRFB returns an error. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: SFWFB returns an error. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: OPEN() returns an error.
-
Action: Check that /proc has the right permissions.
-
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.
-
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.
-
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.
-
Cause: SEMCTL system call returned an error.
-
Action: Check semaphore sets. May require manual cleanup. Check additional information returned. Consult operating system reference manual.
-
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.
-
Cause: System failed to set up signal handler.
-
Action: Check errno and sercose[0] for the signal number that failed.
-
Cause: System failed to set up signal handler to catch exceptions.
-
Action: Check errno and sercose[0] for the signal number that failed.
-
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].
-
Cause: An error occurred when creating a new process.
-
Action: Check errno. Perhaps a system limit on the number of processes has been exceeded.
-
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.
-
Cause: Wait system call returned an error.
-
Action: Check errno.
-
Cause: Kill system call returned an error. Possibly an attempt to destroy an already gone process.
-
Action: Check errno.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: Kill system call returned an error. Possible operating system error.
-
Action: Check errno. Additional information indicates the process ID tested.
-
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.
-
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.
-
Cause: Function was passed an invalid Oracle process ID. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: An error occurred while trying to set an interval timer. Probable porting problem.
-
Action: Check errno.
-
Cause: Function was called with an invalid Oracle process number (0).
-
Action: Internal Oracle error.
-
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.
-
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.
-
Cause: Unable to access Oracle program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable.
-
Action: Check errno returned.
-
Cause: The kill system call returned an error. Possibly an attempt to signal a process which does not exist.
-
Action: Check errno.
-
Cause: A group has not been set up for dba users.
-
Action: Contact system administrator. Set up dba group in /ETC/GROUP.
-
Cause: A 0 PID was passed to SPDDE. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The IOCTL call returned an error. Possible operating system error.
-
Action: Check additional information for errno. Contact Oracle Support Services.
-
Cause: Times system call returned an error. Possible operating system error.
-
Action: Check additional information returned. Contact Oracle Support Services.
-
Cause: The internal buffer is not big enough to hold the archive control string.
-
Action: Internal restriction. Try a shorter archive control string.
-
Cause: An invalid volume size was specified.
-
Action: Specify a valid volume size in archive control string.
-
Cause: Some non-numeric text follows the volume size specification.
-
Action: Enter a correct archive control string.
-
Cause: Volume size was specified for a disk file.
-
Action: If you are archiving to a disk file, do not specify its volume size.
-
Cause: STAT on the log archiving device failed.
-
Action: Check the returned OSD error for the reason of failure.
-
Cause: Log archiving to this device is unsupported.
-
Action: Try log archiving to a supported device.
-
Cause: The specified path name is not a directory.
-
Action: Verify that the archive destination directory exists.
-
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_SIZEinitialization parameter is set properly in your initialization parameter file. -
Cause: The redo buffer size must be a multiple of machine block size.
-
Action: Verify that the
LOG_BUFFERinitialization parameter is set properly in your initialization parameter file. -
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_SIZEinitialization parameter is set properly in your initialization parameter file, or disable theUSE_INDIRECT_DATA_BUFFERSinitialization parameter. -
Cause: MALLOC library routine returned an error.
-
Action: Check errno. Possibly out of swap space.
-
Cause: SMPDAL was called when the PGA had not been previously created. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The specified datafile name contains '..'.
-
Action: Correct the datafile name and retry the operation.
-
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.
-
Cause: FOPEN library routine returned an error.
-
Action: Verify existence and permissions.
-
Cause: FCLOSE library routine returned an error.
-
Action: Possible internal Oracle error.
-
Cause: An error occurred while deleting a text file.
-
Action: Verify that the file exists and check additional errors.
-
Cause: An error occurred while performing a string put operation.
-
Action: This is an internal error. Check additional information.
-
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.
-
Cause: The system failed to restore user exception handlers.
-
Action: Check errno and sercose[0] for the signal number that failed.
-
Cause: The system failed to restore user signal handlers.
-
Action: Check errno and sercose[0] for the signal number that failed.
-
Cause: The
DB_WRITERSinitialization parameter in your initialization parameter file exceeds the system-dependent maximum or is less than 0. -
Action: Change the
DB_WRITERSinitialization parameter in your initialization parameter file. -
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.
-
Cause: An impossible request for binary to decimal conversion was made.
-
Action: This conversion cannot be performed.
-
Cause: An impossible request for binary to decimal conversion was made.
-
Action: This conversion cannot be performed.
-
Cause: An impossible request for binary to decimal conversion was made.
-
Action: This conversion cannot be performed.
-
Cause: An impossible request for decimal to binary conversion was made.
-
Action: This conversion cannot be performed.
-
Cause: An impossible request for decimal to binary conversion was made.
-
Action: This conversion cannot be performed.
-
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.
-
Cause: One of the database writer processes could not locate its entry in the SGA.
-
Action: Contact Oracle Support Services.
-
Cause: MALLOC() failed to allocate buffer for storing ORACLE_PATH.
-
Action: System has run out of heap space. Additional information indicates errno.
-
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].
-
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.
-
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.
-
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.
-
Cause: An Oracle error occurred when translating the location of the dump file.
-
Action: Check the Oracle error code.
-
Cause: An Oracle error occurred when translating the location of the DBS directory.
-
Action: Check additional information for the error returned from SLTLN.
-
Cause: CHDIR system call returned an error. Possible permission problems.
-
Action: Check additional information for the operating system error code.
-
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.
-
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.
-
Cause: The wakeup monitor process died.
-
Action: Warm start instance.
-
Cause: An improperly aligned function address was specified.
-
Action: Use a properly aligned function address.
-
Cause: An invalid function address was specified.
-
Action: Use a valid function address.
-
Cause: An invalid function name was specified.
-
Action: Use a valid function name.
-
Cause: An invalid function name/address was specified.
-
Action: Use a valid function name/address.
-
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.
-
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.
-
Cause: Oracle failed to create a shared arena file.
-
Action: Use SERCERRNO field to determine cause of failure.
-
Cause: Oracle attempted to create more shared arena files than permitted.
-
Action: Raise the value for MAX_ARENA in INIT.ORA.
-
Cause: Oracle failed to acquire a shared arena lock.
-
Action: Check result code in SERCERRNO to determine the cause of failure.
-
Cause: KSTAT library returned an error. Possible operating system failure.
-
Action: Check result code in sercose[0] for more information.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to turn on the Resource Manager when the database was closed.
-
Action: Open the database and try again.
-
Cause: The MSET routine returned an error. Semaphore may not exist.
-
Action: Check result code in SERCERRNO. Semaphore number returned in sercose[0].
-
Cause: The MCLEAR routine returned an error. Semaphore may not exist.
-
Action: Check result code in SERCERRNO. Semaphore number returned in sercose[0].
-
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.
-
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].
-
Cause: Open failed when opening the file ?/dbs/sgadef@.dbf.
-
Action: Check errno. Possible permission problem. Verify that the file ?/dbs/sgadef@.dbf exists.
-
Cause: Read had an error when reading SGADEF.DBF file.
-
Action: Check errno. Verify file exists, and is correct size.
-
Cause: An error occurred in close, while closing the file ?/dbs/sgadef@.dbf.
-
Action: Check errno. Possible operating system error.
-
Cause: The VM_STATISTICS system call failed to get virtual memory statistics.
-
Action: Check result code in SERCERRNO. Possible operating system failure.
-
Cause: The VM_MAPMEM system call failed to get mapped memory statistics.
-
Action: Check result code in SERCERRNO. Possible operating system failure.
-
Cause: Lock manager must be initialized before converting locks.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_STAT_LOCK failed.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_OPEN or LM_OPEN_CONVERT failed.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: When creating an instance, SNLMINI could not change the permissions on ?/dbs/sgalm.dbf.
-
Action: Contact Oracle Support Services.
-
Cause: LM_ATTACH failed to attach to Lock Manager instance.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_CREATE failed to create Lock Manager instance.
-
Action: Check permissions on ?/dbs, and remove ?/dbs/sgalm.dbf if it exists, then retry.
-
Cause: LM_CONVERT failed to convert(get) lock.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_CONVERT failed to put lock value.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_OPEN failed.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_CONVERT failed to get lock value.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_CREATE failed.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: Lock manager must be initialized before releasing locks.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_STAT_LOCK failed during lock release/cancel.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_CONVERT failed during lock release/cancel.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_CANCEL failed during lock release/cancel.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_CLOSE failed during lock release/cancel.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: An error was encountered releasing the lock.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: Unknown or unexpected error code.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_WAIT failed.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause: LM_POST failed.
-
Action: Check result code in SERCERRNO. Possible Lock Manager failure.
-
Cause:
-
Action:
-
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.
-
Cause: The rescheduling driver /dev/resched is not open. This is an internal error and should not occur.
-
Action: Contact Oracle Support Services.
ORA-04930 open sequence number failed or initial state is valid
ORA-04931 unable to set initial sequence number value
ORA-04932 increment or adjust of sequence number failed
ORA-04933 initial service identifier is non-zero
ORA-04934 unable to obtain the current sequence number
ORA-04935 unable to get/convert SCN recovery lock
ORA-04940 unsupported optimization of Oracle binary, check alert log for more info
ORA-06000 NETASY: port open failure
ORA-06001 NETASY: port set-up failure
ORA-06002 NETASY: port read failure
ORA-06003 NETASY: port write failure
ORA-06004 NETASY: dialogue file open failure
ORA-06005 NETASY: dialogue file read failure
ORA-06006 NETASY: dialogue execute failure
ORA-06007 NETASY: bad dialogue format
ORA-06009 NETASY: dialogue filename too long
ORA-06010 NETASY: dialogue file too long
ORA-06011 NETASY: dialogue too long
ORA-06017 NETASY: message receive failure
ORA-06018 NETASY: message send failure
ORA-06019 NETASY: invalid login (connect) string
ORA-06020 NETASY: initialisation failure
ORA-06021 NETASY: connect failed
ORA-06022 NETASY: channel open failure
ORA-06023 NETASY: port open failure
ORA-06024 NETASY: VTM error
ORA-06025 NETASY: Configuration error
ORA-06026 NETASY: port close failure
ORA-06027 NETASY: channel close failure
ORA-06028 NETASY: unable to intialise for logging
ORA-06029 NETASY: port assignment failure
ORA-06030 NETDNT: connect failed, unrecognized node name
ORA-06031 NETDNT: connect failed, unrecognized object name
ORA-06032 NETDNT: connect failed, access control data rejected
ORA-06033 NETDNT: connect failed, partner rejected connection
ORA-06034 NETDNT: connect failed, partner exited unexpectedly
ORA-06035 NETDNT: connect failed, insufficient resources
ORA-06037 NETDNT: connect failed, node unreachable
ORA-06039 NETDNT: connect failed
ORA-06040 NETDNT: invalid login (connect) string
ORA-06041 NETDNT: disconnect failed
ORA-06042 NETDNT: message receive failure
ORA-06043 NETDNT: message send failure
ORA-06044 NETDNT: connect failed, byte count quota exceeded
ORA-06102 NETTCP: cannot allocate context area
ORA-06105 NETTCP: remote host is unknown
ORA-06106 NETTCP: socket creation failure
ORA-06107 NETTCP: ORACLE network server not found
ORA-06108 NETTCP: connect to host failed
ORA-06109 NETTCP: message receive failure
ORA-06110 NETTCP: message send failure
ORA-06111 NETTCP: disconnect failure
ORA-06112 NETTCP: invalid buffer size
ORA-06113 NETTCP: Too many connections
ORA-06114 NETTCP: SID lookup failure
ORA-06115 NETTCP: unable to create ORACLE logicals
ORA-06116 NETTCP: unable to create ORASRV process
ORA-06117 NETTCP: unable to create ORASRV: quota exceeded
ORA-06118 NETTCP: unable to complete handshake with ORASRV
ORA-06119 NETTCP: spurious client request
ORA-06120 NETTCP: network driver not loaded
ORA-06121 NETTCP: access failure
ORA-06122 NETTCP: setup failure
ORA-06123 NETTCP: cannot set KEEPALIVE
ORA-06124 NETTCP: timeout waiting for ORASRV
ORA-06125 NETTCP: ORASRV exited unexpectedly
ORA-06126 NETTCP: ORASRV unable to open network connection
ORA-06127 NETTCP: unable to change username
ORA-06128 NETTCP: unable to create mailbox
ORA-06129 NETTCP: unable to transfer socket ownership to ORASRV
ORA-06130 NETTCP: host access denied
ORA-06131 NETTCP: user access denied
ORA-06132 NETTCP: access denied, wrong password
ORA-06133 NETTCP: file not found
ORA-06134 NETTCP: file access privilege violation
ORA-06135 NETTCP: connection rejected; server is stopping
ORA-06136 NETTCP: error during connection handshake
ORA-06137 NETTCP: error during connection handshake
ORA-06138 NETTCP: error during connection handshake
ORA-06140 NETTCP: no such user
ORA-06141 NETTCP: no privilege for user
ORA-06142 NETTCP: error getting user information
ORA-06143 NETTCP: maximum connections exceeded
ORA-06144 NETTCP: SID (database) is unavailable
ORA-06145 NETTCP: unable to start ORASRV: images not installed
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
ORA-06251 NETNTT: cannot translate address file name
ORA-06252 NETNTT: cannot open address file
ORA-06253 NETNTT: cannot read arguments from address file
ORA-06254 NETNTT: cannot share connection to cube
ORA-06255 NETNTT: cannot read pid of remote process
ORA-06256 NETNTT: remote fork failed
ORA-06257 NETNTT: cannot send command line to shadow process
ORA-06258 NETNTT: cannot allocate context area
ORA-06259 NETNTT: cannot read from remote process
ORA-06260 NETNTT: cannot write to remote process
ORA-06261 NETNTT: nrange() failed
ORA-06262 NETNTT: nfconn() failed
ORA-06263 NETNTT: out of memory in pi_connect
ORA-06264 NETNTT: data protocol error
ORA-06265 NETNTT: break protocol error
ORA-06266 NETNTT: bad write length
ORA-06267 NETNTT: bad state
ORA-06268 NETNTT: cannot read /etc/oratab
ORA-06300 IPA: Disconnect failure
ORA-06301 IPA: Cannot allocate driver context
ORA-06302 IPA: Cannot connect to remote host
ORA-06303 IPA: Message send error
ORA-06304 IPA: Message receive error
ORA-06305 IPA: Illegal message type
ORA-06306 IPA: Message write length error
ORA-06307 IPA: Cannot reset connection
ORA-06308 IPA: No more connections available
ORA-06309 IPA: No message queue available
ORA-06310 IPA: Environment variable(s) not set
ORA-06311 IPA: Maximum number of servers reached
ORA-06312 IPA: Incorrect outgoing service name supplied
ORA-06313 IPA: Shared memory failed to initialise
ORA-06314 IPA: Event set up failure
ORA-06315 IPA: Invalid connect string
ORA-06316 IPA: Invalid database SID
ORA-06317 IPA: Local maximum number of users exceeded
ORA-06318 IPA: Local maximum number of connections exceeded
ORA-06319 IPA: Remote maximum number of users exceeded
ORA-06320 IPA: Remote maximum number of connections exceeded
ORA-06321 IPA: Cannot reach the remote side
ORA-06322 IPA: Fatal shared memory error
ORA-06323 IPA: Cause event error
ORA-06400 NETCMN: No default host string specified
ORA-06401 NETCMN: invalid driver designator
ORA-06402 NETCMN: error receiving break message
ORA-06403 Unable to allocate memory.
ORA-06404 NETCMN: invalid login (connect) string
ORA-06405 NETCMN: reset protocol error
ORA-06406 NETCMN: error sending break message
ORA-06407 NETCMN: unable to set up break handling environment
ORA-06408 NETCMN: incorrect message format
ORA-06413 Connection not open.
ORA-06416 NETCMN: error on test
ORA-06419 NETCMN: server can not start oracle
ORA-06420 NETCMN: SID lookup failure
ORA-06421 NETCMN: Error detected in the read-in data
ORA-06422 NETCMN: Error in sending data
ORA-06423 NETCMN: Error in receiving data
ORA-06430 ssaio: Seals do not match
ORA-06431 ssaio: Invalid Block number
ORA-06432 ssaio: Buffer Not Aligned
ORA-06433 ssaio: LSEEK error, unable to seek to requested block.
ORA-06434 ssaio: read error, unable to read requested block from database file.
ORA-06435 ssaio: write error, unable to write requested block to database file.
ORA-06436 ssaio: asynchronous I/O failed due to incorrect parameters.
ORA-06437 ssaio: the asynchronous write was unable to write to the database file.
ORA-06438 ssaio: the asynchronous read was unable to read from the database file.
ORA-06439 ssaio: the asynchronous write returned incorrect number of bytes
ORA-06440 ssaio: the asynchronous read returned incorrect number of bytes
ORA-06441 ssvwatev: Incorrect parameter passed to function call
ORA-06442 ssvwatev: Failed with unexpected error number.
ORA-06443 ssvpstev: Incorrect parameter passed to function call
ORA-06444 ssvpstev: Failed with unexpected error number.
ORA-06445 ssvpstevrg: Incorrect parameters passed to function call
ORA-06446 ssvpstevrg: Failed with unexpected error number.
ORA-06447 ssvpstp: Incorrect parameter passed to function call
ORA-06448 ssvpstp: Failed with unexpected error number.
ORA-06449 The list IO or the sysvendor is not installed.
ORA-06500 PL/SQL: storage error
ORA-06501 PL/SQL: program error
ORA-06502 PL/SQL: numeric or value error string
ORA-06503 PL/SQL: Function returned without value
ORA-06504 PL/SQL: Return types of Result Set variables or query do not match
ORA-06505 PL/SQL: variable requires more than 32767 bytes of contiguous memory
ORA-06508 PL/SQL: could not find program unit being called
ORA-06509 PL/SQL: ICD vector missing for this package
ORA-06510 PL/SQL: unhandled user-defined exception
ORA-06511 PL/SQL: cursor already open
ORA-06512 at string line string
ORA-06513 PL/SQL: index for PL/SQL table out of range for host language array
ORA-06514 PL/SQL: The remote call cannot be handled by the server
ORA-06515 PL/SQL: unhandled exception string
ORA-06516 PL/SQL: the Probe packages do not exist or are invalid
ORA-06517 PL/SQL: Probe error - string
ORA-06518 PL/SQL: Probe version string incompatible with version string
ORA-06519 active autonomous transaction detected and rolled back
ORA-06520 PL/SQL: Error loading external library
ORA-06521 PL/SQL: Error mapping function
ORA-06522 string
ORA-06523 Maximum number of arguments exceeded
ORA-06524 Unsupported option : string
ORA-06525 Length Mismatch for CHAR or RAW data
ORA-06526 Unable to load PL/SQL library
ORA-06527 External procedure SQLLIB error: string
ORA-06528 Error executing PL/SQL profiler
ORA-06529 Version mismatch - PL/SQL profiler
ORA-06530 Reference to uninitialized composite
ORA-06531 Reference to uninitialized collection
ORA-06532 Subscript outside of limit
ORA-06533 Subscript beyond count
ORA-06534 cannot access Serially Reusable package string in the context of a trigger
ORA-06535 statement string in string is NULL or 0 length
ORA-06536 IN bind variable bound to an OUT position
ORA-06537 OUT bind variable bound to an IN position
ORA-06538 statement violates string RESTRICT_REFERENCES pragma
ORA-06539 target of OPEN must be a query
ORA-06540 PL/SQL: compilation error
ORA-06541 PL/SQL: compilation error - compilation aborted
ORA-06544 PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
ORA-06545 PL/SQL: compilation error - compilation aborted
ORA-06546 DDL statement is executed in an illegal context
ORA-06547 RETURNING clause must be used with INSERT, UPDATE, or DELETE statements
ORA-06548 no more rows needed
ORA-06549 PL/SQL: failed to dynamically open shared object (DLL): string
ORA-06550 line string, column string:string
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
ORA-06555 this name is currently reserved for use by user SYS
ORA-06556 the pipe is empty, cannot fulfill the unpack_message request
ORA-06557 null values are not allowed for any parameters to pipe icd's
ORA-06558 buffer in dbms_pipe package is full. No more items allowed
ORA-06559 wrong datatype requested, string, actual datatype is string
ORA-06560 pos, string, is negative or larger than the buffer size, string
ORA-06561 given statement is not supported by package DBMS_SQL
ORA-06562 type of out argument must match type of column or bind variable
ORA-06563 top level procedure/function specified, cannot have subparts
ORA-06564 object string does not exist
ORA-06565 cannot execute string from within stored procedure
ORA-06566 invalid number of rows specified
ORA-06567 invalid number of values specified
ORA-06568 obsolete ICD procedure called
ORA-06569 Collection bound by bind_array contains no elements
ORA-06570 shared pool object does not exist, cannot be pinned
ORA-06571 Function string does not guarantee not to update database
ORA-06572 Function string has out arguments
ORA-06573 Function string modifies package state, cannot be used here
ORA-06574 Function string references package state, cannot execute remotely
ORA-06575 Package or function string is in an invalid state
ORA-06576 not a valid function or procedure name
ORA-06577 output parameter not a bind variable
ORA-06578 output parameter cannot be a duplicate bind
ORA-06580 Hash Join ran out of memory while keeping large rows in memory
ORA-06592 CASE not found while executing CASE statement
ORA-06593 string is not supported with natively compiled PL/SQL modules
ORA-06600 LU6.2 Driver: SNA software is not loaded
ORA-06601 LU6.2 Driver: Invalid database ID string
ORA-06602 LU6.2 Driver: Error allocating context area
ORA-06603 LU6.2 Driver: Error allocating memory
ORA-06604 LU6.2 Driver: Unable to allocate session with remote LU
ORA-06605 LU6.2 Driver: Unexpected line turnaround
ORA-06606 LU6.2 Driver: Unexpected response from SNA
ORA-06607 LU6.2 Driver: Reset occurred in send state
ORA-06608 LU6.2 Driver: Reset occurred in receive state
ORA-06610 LU6.2 Driver: Failed during deallocation
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
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
ORA-06700 TLI Driver: incorrect message type from host
ORA-06701 TLI Driver: incorrect number of bytes written
ORA-06702 TLI Driver: cannot allocate context area
ORA-06703 TLI Driver: send break message failed
ORA-06704 TLI Driver: receive break message failed
ORA-06705 TLI Driver: remote node is unknown
ORA-06706 TLI Driver: service not found
ORA-06707 TLI Driver: connection failed
ORA-06708 TLI Driver: message receive failure
ORA-06709 TLI Driver: message send failure
ORA-06710 TLI Driver: send interrupt break message failed
ORA-06711 TLI Driver: error on bind
ORA-06712 TLI Driver: error on accept
ORA-06713 TLI Driver: error on connect
ORA-06720 TLI Driver: SID lookup failure
ORA-06721 TLI Driver: spurious client req
ORA-06722 TLI Driver: connection setup failure
ORA-06730 TLI Driver: unable to open clone device
ORA-06731 TLI Driver: cannot alloc t_call
ORA-06732 TLI Driver: cannot alloc t_discon
ORA-06733 TLI Driver: failed to receive disconnect
ORA-06734 TLI Driver: cannot connect
ORA-06735 TLI Driver: client failed to close error conn
ORA-06736 TLI Driver: server not running
ORA-06737 TLI Driver: connection failed
ORA-06741 TLI Driver: unable to open protocol device
ORA-06742 TLI Driver: cannot alloc t_bind
ORA-06743 TLI Driver: cannot alloc t_bind
ORA-06744 TLI Driver: listener cannot bind
ORA-06745 TLI Driver: listener already running
ORA-06746 TLI Driver: cannot alloc t_call
ORA-06747 TLI Driver: error in listen
ORA-06748 TLI Driver: cannot allocate t_discon
ORA-06749 TLI Driver: option not allowed across network
ORA-06750 TLI Driver: sync failed
ORA-06751 TLI Driver: bound addresses unequal
ORA-06752 TLI: error in signal setup
ORA-06753 TLI Driver: name-to-address mapping failed
ORA-06754 TLI Driver: unable to get local host address
ORA-06755 TLI Driver: cannot close transport endpoint
ORA-06756 TLI Driver: cannot open oratab
ORA-06757 TLI Driver: server got bad command
ORA-06760 TLI Driver: timeout reading orderly release
ORA-06761 TLI Driver: error sending orderly release
ORA-06762 TLI Driver: error reading orderly release
ORA-06763 TLI Driver: error sending disconnect
ORA-06764 TLI Driver: error reading disconnect
ORA-06765 TLI Driver: error awaiting orderly release
ORA-06766 TLI Driver: close failed during release
ORA-06767 TLI Driver: alloc failed during release
ORA-06770 TLI Driver: error sending version
ORA-06771 TLI Driver: error reading version
ORA-06772 TLI Driver: error sending command
ORA-06773 TLI Driver: error reading command
ORA-06774 TLI Driver: error sending break mode
ORA-06775 TLI Driver: error reading break mode
ORA-06776 TLI Driver: error sending parms
ORA-06777 TLI Driver: error reading parms
ORA-06778 TLI Driver: error sending ccode
ORA-06779 TLI Driver: error reading ccode
ORA-06780 TLI Driver: recv error code failed
ORA-06781 TLI Driver: error reading negotation string
ORA-06790 TLI Driver: poll failed
ORA-06791 TLI Driver: poll returned error event
ORA-06792 TLI Driver: server cannot exec oracle
ORA-06793 TLI Driver: server cannot create new process
ORA-06794 TLI Driver: shadow process could not retrieve protocol info
ORA-06800 TLI Driver: SQL*Net SPX client went away during reconnect
ORA-06801 TLI Driver: listen for SPX server reconnect failed
ORA-06802 TLI Driver: could not open the /etc/netware/yellowpages file
ORA-06803 TLI Driver: the IPX device file could not be opened
ORA-06804 TLI Driver: could not bind an IPX address at initialization
ORA-06805 TLI Driver: could not send datagram SAP packet for SPX
ORA-06806 TLI Driver: could not complete protocol initialization for SPX
ORA-06807 TLI Driver: could not open ethernet device driver file
ORA-06808 TLI Driver: could not link IPX and ethernet streams
ORA-06809 TLI Driver: could not clear the IPX ethernet SAP at init
ORA-06810 TLI Driver: could not set the IPX ethernet SAP at init
ORA-06811 TLI Driver: could not set the IPX network number at init
ORA-06812 TLI Driver: could not read the ethernet driver's node address
ORA-06813 TLI Driver: the configured ethernet address is incorrect
ORA-06814 TLI Driver: the SPX device file could not be opened
ORA-06815 TLI Driver: could not link SPX and IPX streams
ORA-06816 TLI Driver: could not set the SPX SAP address
ORA-06817 TLI Driver: could not read the Novell network address
ORA-06900 CMX: cannot read tns directory
ORA-06901 CMX: no local name assigned to local application
ORA-06902 CMX: cannot attach to cmx subsystem
ORA-06903 CMX: cannot read transport address of remote application
ORA-06904 CMX: no transport address available for remote application
ORA-06905 CMX: connect error
ORA-06906 CMX: cannot get maximum packet size from CMX
ORA-06907 CMX: error during connect confirmation
ORA-06908 CMX: error during transfer of ORACLE_SID
ORA-06909 CMX: error during acknowledge of ORACLE_SID
ORA-06910 CMX: Cannot start oracle process on remote machine
ORA-06911 CMX: t_event returns ERROR
ORA-06912 CMX: write error in datarq
ORA-06913 CMX: error during redirection of connection
ORA-06914 CMX: unexepected event during start of oracle
ORA-06915 CMX: unknown t_event in datarq
ORA-06916 CMX: error in data read (t_datain)
ORA-06917 CMX: error in data read (too many bytes read)
ORA-06918 CMX: T_NOEVENT during wait for read event
ORA-06919 CMX: error during write request (unknown event)
ORA-06920 CMX: getbrkmsg illegal datatype
ORA-06921 CMX: getdatmsg illegal datatype
ORA-06922 CMX: bad write length
ORA-06923 CMX: illegal break condition
ORA-06924 CMX: wrong break message length
ORA-06925 CMX: disconnect during connect request
ORA-06926 CMX: T_ERROR during read data
ORA-06927 CMX: T_DATAIN received before all data written
ORA-06928 CMX: wrong ORACLE_SID
ORA-06929 CMX: error when sending ORACLE_SID
ORA-06930 CMX: error when checking ORACLE_SID
ORA-06931 CMX: error during read_properties for server
ORA-06932 CMX: error in local name
ORA-06933 CMX: error during attach
ORA-06950 No error
ORA-06951 Operating system call error
ORA-06952 Remote end of the communication issued a forward-reset packet.
ORA-06953 Not enough virtual memory
ORA-06954 Illegal file name
ORA-06955 Number of database servers exceed limit
ORA-06956 Failed to get local host name
ORA-06957 No SID is currently available
ORA-06958 Failed to access configuration file
ORA-06959 Buffer I/O quota is too small
ORA-06960 Failed to access log file
ORA-06961 Insufficient privilege for attempted operation
ORA-06970 X.25 Driver: remote host is unknown
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
ORA-06974 X.25 Driver: SID lookup failure
ORA-06975 X.25 Driver: connect to host failed
ORA-06976 X.25 Driver: endpoint creation failure
ORA-06977 X.25 Driver: X.25 Level 2 failure
ORA-06978 X.25 Driver: Too many callback tries
ORA-06979 X.25 Driver: server cannot start oracle
ORA-07200 slsid: oracle_sid not set.
ORA-07201 slhom: oracle_home variable not set in environment.
ORA-07202 sltln: invalid parameter to sltln.
ORA-07203 sltln: attempt to translate a long environment variable.
ORA-07204 sltln: name translation failed due to lack of output buffer space.
ORA-07205 slgtd: time error, unable to obtain time.
ORA-07206 slgtd: gettimeofday error, unable to obtain time.
ORA-07207 sigpidu: process ID string overflows internal buffer.
ORA-07208 sfwfb: failed to flush dirty buffers to disk.
ORA-07209 sfofi: file size limit was exceeded.
ORA-07210 slcpu: getrusage error, unable to get cpu time.
ORA-07211 slgcs: gettimeofday error, unable to get wall clock.
ORA-07212 slcpu: times error, unable to get cpu time.
ORA-07213 slgcs: times error, unable to get wall clock.
ORA-07214 slgunm: uname error, unable to get system information.
ORA-07215 slsget: getrusage error.
ORA-07216 slghst: gethostname error, unable to get name of current host.
ORA-07217 sltln: environment variable cannot be evaluated.
ORA-07218 slkhst: could not perform host operation
ORA-07219 slspool: unable to allocate spooler argument buffer.
ORA-07220 slspool: wait error.
ORA-07221 slspool: exec error, unable to start spooler program.
ORA-07222 slspool: line printer spooler command exited with an error.
ORA-07223 slspool: fork error, unable to spawn spool process.
ORA-07224 sfnfy: failed to obtain file size limit; errno = string.
ORA-07225 sldext: translation error, unable to expand file name.
ORA-07226 rtneco: unable to get terminal mode.
ORA-07227 rtneco: unable to set noecho mode.
ORA-07228 rtecho: unable to restore terminal to echo mode.
ORA-07229 slcpuc: error in getting number of CPUs.
ORA-07230 slemcr: fopen error, unable to open error file.
ORA-07231 slemcc: invalid file handle, seals do not match.
ORA-07232 slemcc: fclose error.
ORA-07233 slemcw: invalid file handle, seals do not match.
ORA-07234 slemcw: fseek error.
ORA-07235 slemcw: fwrite error.
ORA-07236 slemop: open error.
ORA-07237 slemcl: invalid file handle, seals do not match.
ORA-07238 slemcl: close error.
ORA-07239 slemrd: invalid file handle, seals do not match.
ORA-07240 slemrd: seek error.
ORA-07241 slemrd: read error.
ORA-07242 slembfn: translation error, unable to translate error file name.
ORA-07243 supplied buffer not big enough to hold entire line
ORA-07244 ssfccf: create file failed, file size limit reached.
ORA-07245 sfccf: unable to lseek and write the last block.
ORA-07246 sfofi: open error, unable to open database file.
ORA-07247 sfrfb: read error, unable to read requested block from database file.
ORA-07248 sfwfb: write error, unable to write database block.
ORA-07249 slsget: open error, unable to open /proc/pid.
ORA-07250 spcre: semget error, unable to get first semaphore set.
ORA-07251 spcre: semget error, could not allocate any semaphores.
ORA-07252 spcre: semget error, could not allocate semaphores.
ORA-07253 spdes: semctl error, unable to destroy semaphore set.
ORA-07254 spdcr: translation error while expanding ?/bin/oracle.
ORA-07255 spini: cannot set up signal handler.
ORA-07256 sptrap: cannot set up signal handler to catch exceptions.
ORA-07257 spdcr: translation error expanding program name.
ORA-07258 spdcr: fork error, unable to create process.
ORA-07259 spdcr: exec error, detached process failed in startup.
ORA-07260 spdcr: wait error.
ORA-07261 spdde: kill error, unable to send signal to process.
ORA-07262 sptpa: sptpa called with invalid process id.
ORA-07263 sptpa: kill error.
ORA-07264 spwat: semop error, unable to decrement semaphore.
ORA-07265 sppst: semop error, unable to increment semaphore.
ORA-07266 sppst: invalid process number passed to sppst.
ORA-07267 spwat: invalid process number.
ORA-07268 szguns: getpwuid error.
ORA-07269 spdcr: detached process died after exec.
ORA-07270 spalck: setitimer error, unable to set interval timer.
ORA-07271 spwat: invalid oracle process number.
ORA-07272 spwat: invalid semaphore set id.
ORA-07273 sppst: invalid semaphore id.
ORA-07274 spdcr: access error, access to oracle denied.
ORA-07275 unable to send signal to process
ORA-07276 no dba group in /etc/group.
ORA-07277 spdde: illegal pid passed as argument.
ORA-07278 splon: ops$username exceeds buffer length.
ORA-07279 spcre: semget error, unable to get first semaphore set.
ORA-07280 slsget: unable to get process information.
ORA-07281 slsget: times error, unable to get cpu time.
ORA-07282 sksaprd: string overflow.
ORA-07283 sksaprd: invalid volume size for archive destination.
ORA-07284 sksaprd: volume size specification not terminated properly.
ORA-07285 sksaprd: volume size should not be specified for a disk file.
ORA-07286 sksagdi: cannot obtain device information.
ORA-07287 sksagdi: unsupported device for log archiving.
ORA-07290 sksagdi: specified directory for archiving does not exist.
ORA-07303 ksmcsg: illegal database buffer size.
ORA-07304 ksmcsg: illegal redo buffer size.
ORA-07305 ksmcsg: illegal database buffer size.
ORA-07324 smpall: malloc error while allocating pga.
ORA-07327 smpdal: attempt to destroy pga when it was not mapped.
ORA-07339 spcre: maximum number of semaphore sets exceeded.
ORA-07345 The datafile name must not contain the string '..'.
ORA-07390 sftopn: translate error, unable to translate file name.
ORA-07391 sftopn: fopen error, unable to open text file.
ORA-07392 sftcls: fclose error, unable to close text file.
ORA-07393 unable to delete text file
ORA-07394 unable to append string to text file
ORA-07400 slemtr: translated name for the message file is too long.
ORA-07401 sptrap: cannot restore user exception handlers.
ORA-07402 sprst: cannot restore user signal handler.
ORA-07403 sfanfy: db_writers parameter not valid.
ORA-07404 sfareq: Timeout occurred waiting for request to complete.
ORA-07406 slbtpd: invalid number.
ORA-07407 slbtpd: invalid exponent.
ORA-07408 slbtpd: overflow while converting to packed decimal.
ORA-07409 slpdtb: invalid packed decimal nibble.
ORA-07410 slpdtb: number too large for supplied buffer.
ORA-07411 slgfn: full path name too big for supplied buffer.
ORA-07412 sfaslv: Error getting entry in asynchronous write array.
ORA-07415 slpath: allocation of memory buffer failed.
ORA-07416 slpath: pathname construction failed; lack of output buffer space.
ORA-07417 sfareq: One or more database writers not active.
ORA-07418 sfareq: Database writer got error in timing function.
ORA-07419 sfareq: Database writer got error in timing function.
ORA-07425 sdpri: error string in translating dump file location.
ORA-07426 spstp: cannot obtain the location of dbs directory.
ORA-07427 spstp: cannot change directory to dbs.
ORA-07431 fork failed
ORA-07432 unable to perform nested sleep
ORA-07440 WMON process terminated with error
ORA-07441 function address must be aligned on string byte boundary
ORA-07442 function address must be in the range string to string
ORA-07443 function string not found
ORA-07444 function address string is not readable
ORA-07445 exception encountered: core dump [string] [string] [string] [string] [string] [string]
ORA-07446 sdnfy: bad value 'string' for parameter string.
ORA-07447 ssarena: usinit failed.
ORA-07448 ssarena: maximum number of shared arenas exceeded.
ORA-07449 sc: usnewlock failed.
ORA-07451 slskstat: unable to obtain load information.
ORA-07452 specified resource manager plan does not exist in the data dictionary
ORA-07453 requested resource manager plan schema does not contain OTHER_GROUPS
ORA-07454 queue timeout, string second(s), exceeded
ORA-07455 estimated execution time (string secs), exceeds limit (string secs)
ORA-07456 cannot set RESOURCE_MANAGER_PLAN when database is closed
ORA-07468 spwat: mset error, unable to set semaphore.
ORA-07469 sppst: mclear error, unable to clear semaphore.
ORA-07470 snclget: cannot get cluster number.
ORA-07471 snclrd: name translation error of sgadef.dbf file name.
ORA-07472 snclrd: open error when opening sgadef.dbf file.
ORA-07473 snclrd: read error when trying to read sgadef.dbf file.
ORA-07474 snclrd: close error, unable to close sgadef.dbf file.
ORA-07475 slsget: cannot get vm statistics.
ORA-07476 slsget: cannot get mapped memory statistics.
ORA-07477 scgcmn: lock manager not initialized.
ORA-07478 scgcmn: cannot get lock status.
ORA-07479 scgcmn: cannot open or convert lock.
ORA-07480 snchmod: cannot change permissions on ?/dbs/sgalm.dbf.
ORA-07481 snlmatt: cannot attach to lock manager instance.
ORA-07482 snlmini: cannot create lock manager instance.
ORA-07483 snlkget: cannot convert(get) lock.
ORA-07484 snlkput: cannot convert(put) lock.
ORA-07485 scg_get_inst: cannot open instance number lock.
ORA-07486 scg_get_inst: cannot convert(get) instance number lock.
ORA-07487 scg_init_lm: cannot create lock manager instance.
ORA-07488 scgrcl: lock manager not initialized.
ORA-07489 scgrcl: cannot get lock status.
ORA-07490 scgrcl: cannot convert lock.
ORA-07491 scgrcl: cannot cancel lock request.
ORA-07492 scgrcl: cannot close lock.
ORA-07493 scgrcl: lock manager error.
ORA-07494 scgcm: unexpected error.
ORA-07495 spwat: lm_wait failed.
ORA-07496 sppst: lm_post failed.
ORA-07497 sdpri: cannot create trace file 'string'; errno = string.
ORA-07498 spstp: Unable to open /dev/resched.
ORA-07499 spglk: Cannot reschedule.
|
|
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
7
ORA-07500 to ORA-09857
-
Cause: VMS system service $CANTIM returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $DEQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $ENQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $SETIMR returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $HIBER returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $ENQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $DEQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
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.
-
Cause: VMS system service $DEQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $DEQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $GETLKI returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $ENQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $ENQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $DEQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $DEQ returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: VMS system service $GETLKI returned an unexpected value.
-
Action: Check for system error message and refer to VMS documentation.
-
Cause: Too many test files open. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: VMS system service $OPEN failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $CONNECT failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $CLOSE failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GET failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $IDTOASC failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: An extension was found but it is of improper length. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: VMS system service $PARSE failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: A wildcard was used in the file name.
-
Action: Re-enter the file name completely.
-
Cause: VMS system service $SEARCH failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $OPEN failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $CLOSE failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $IDTOASC failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $FIND_HELD failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: An OS role name was too long.
-
Action: Re-define the role name to be of correct length.
-
Cause: VMS system service LIB$SPAWN failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETUAI failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
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.
-
Cause: VMS system service $FIND_HELD failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $DCLEXH failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
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.
-
Cause: The ORA_SID must exist and be less than 6 characters.
-
Action: Consult the VMS Installation guide for information on setting the SID.
-
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.
-
Cause: VMS system service $PARSE failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $SEARCH failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $CREPRC failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
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.
-
Cause: VMS system service $DELPRC failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: While obtaining needed privileges, an error was returned from SYS$SETPRV. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: While releasing privileges, an error was returned from SYS$SETPRV. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $SETIMR failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $SCHDWK failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETSYIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $ASCTOID failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $CHKPRO failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $SNDOPR failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETUAI failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $HASH_PASSWORD failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETUAI failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $GETJPIW failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $CHANGE_CLASS failed.
-
Action: Examine system error message and refer to SEVMS documentation.
-
Cause: VMS system service $CHANGE_CLASSS failed.
-
Action: Examine system error message and refer to SEVMS documentation.
-
Cause: VMS system service $CHANGE_CLASS failed.
-
Action: Examine system error message and refer to SEVMS documentation.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: While creating the system global area (SGA), VMS system service $CRMPSC failed.
-
Action: Examine the system error message and refer to VMS documentation.
-
Cause: While deleting the system global area (SGA), VMS system service $DGBLSC failed.
-
Action: Examine the system error message and refer to VMS documentation.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: While deleting a context area, VMS system service $DELTVA failed.
-
Action: Examine the system error message and refer to VMS documentation.
-
Cause: The buffer debug function was called with an illegal value. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $CRETVA failed.
-
Action: Contact Oracle Support Services.
-
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $SETPRT failed.
-
Action: Contact Oracle Support Services.
-
Cause: While attempting to set protection in the database buffer debug mechanism, VMS system service $MGBLSC failed.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to map to the SGA while it was being initialized.
-
Action: Wait until initialization is complete, and try again.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Report this error to Oracle Support Services; provide your initialization parameter file.
-
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.
-
Cause: While attempting to create a file, VMS system service $CREATE failed.
-
Action: Examine the system message and refer to VMS system documentation.
-
Cause: While attempting to reopen a file, VMS system service $OPEN failed.
-
Action: Examine the system message and refer to VMS system documentation.
-
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.
-
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.
-
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.
-
Cause: While prompting for a password, VMS system service $ASSIGN failed.
-
Action: Examine the system error message and refer to VMS documentation.
-
Cause: While prompting for a password, VMS system service $QIOW failed.
-
Action: Examine the system error message and refer to VMS documentation.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An interrupt was received while archiving the logs.
-
Action: Retry the operation.
-
Cause: Overflow of buffer for parsing archive control text string. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: Unrecognized device type in archive text. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The buffer supplied for the device name is too small. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The buffer supplied for the tape label is too small. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The user specified a remote disk for archiving via DECnet.
-
Action: Archive to a disk on the local host.
-
Cause: The buffer supplied for the file name is too small. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: VMS system service SYS$MOUNT failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service SYS$DISMNT failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service SYS$GETDVI failed".
-
Action: Specify a valid device in ARCHIVE control string.
-
Cause: VMS system service LIB$GET_VM failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service LIB$FREE_VM failed.
-
Action: Examine system error message and refer to VMS documentation.
-
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.
-
Cause: Structures used for reading error message files do not match. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: VMS system service $OPEN failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: VMS system service $CONNECT failed.
-
Action: Examine system error message and refer to VMS documentation.
-
Cause: An error message file is of incorrect format.
-
Action: Unless an error file has been changed, report this to Oracle.
-
Cause: Seal in passed in handle does not match correct value. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: VMS system service $CLOSE failed.
-
Action: Check system error and refer to VMS documentation.
-
Cause: seal in passed in handle does not match correct value. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: VMS system service $READ failed.
-
Action: Check system error and refer to VMS documentation.
-
Cause: An attempt to create a message file failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: An attempt to allocate a cache for a newly-created message file failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: An attempt to seek before writing a message file cache element failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: An attempt to write a message file cache element failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: An attempt to seek before reading a message file cache element failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: An attempt to read a message file cache element failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The seal in a passed-in handle does not match correct value. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The destination string provided to the function is too short. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The $open service failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: An impossible request for binary to decimal conversion was made.
-
Action: This conversion cannot be performed.
-
Cause: An impossible request for binary to decimal conversion was made.
-
Action: This conversion cannot be performed.
-
Cause: An impossible request for binary to decimal conversion was made.
-
Action: This conversion cannot be performed.
-
Cause: An impossible request for decimal to binary conversion was made.
-
Action: This conversion cannot be performed.
-
Cause: An impossible request for decimal to binary conversion was made.
-
Action: This conversion cannot be performed.
-
Cause: An error was returned from the SYS$CRELNM function.
-
Action: Check system error and refer to VMS documentation.
-
Cause: An error was returned from the SYS$DELLNM function.
-
Action: Check system error and refer to VMS documentation.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An error was returned from SYS$CLOSE while attempting to close the input datafile.
-
Action: Check system error and refer to VMS documentation.
-
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.
-
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.
-
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.
-
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.
-
Cause: An error was returned by SYS$CONNECT while attempting to open the datafile.
-
Action: Check system error and refer to VMS documentation.
-
Cause: An error was returned by SYS$GET while attempting to read the datafile.
-
Action: Check system error and refer to VMS documentation.
-
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.
-
Cause: You are using a bad option to loader Fixed= is one legal option. Check documentation for others.
-
Action: Check documentation.
-
Cause: An error occurred while setting up the control interrupt handler. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: A list of all files open by this process could not be obtained. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The limit on the number of sequences usable by session has been hit.
-
Action: Increase initialization parameter USER_SEQUENCES to get more.
-
Cause: Sequence CURRVAL has been selected before sequence NEXTVAL.
-
Action: Select NEXTVAL from the sequence before selecting CURRVAL.
-
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.
-
Cause: Instantiating NEXTVAL would violate one of MAX/MINVALUE.
-
Action: Alter the sequence so that a new value can be requested.
-
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.
-
Cause: The row has been deleted by another user since the operation began.
-
Action: Retry the operation.
-
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.
-
Cause: Validate Index detected an inconsistency in its argument index.
-
Action: Send trace file to Oracle Support Services.
-
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.
-
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.
-
Cause: The object has been deleted by another user since the operation began.
-
Action: Remove references to the object.
-
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.
-
Cause: Set this event only under the supervision of Oracle development.
-
Action: Debugging only.
-
Cause: Online index builder cannot create its journal table.
-
Action: Rename your table in conflict.
-
Cause: Only support normal index or IOT top-level index.
-
Action: Change your index type.
-
Cause: May not specify NOSORT for online index build.
-
Action: Get rid of NOSORT in the index creation command.
-
Cause: Oracle Kernel test only.
-
Action: Do not set this event (for test only).
-
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).
-
Cause: User attempted to coalesce a composite partition.
-
Action: Coalesce the index a subpartition at a time (using ALTER INDEX MODIFY SUBPARTITION COALESCE).
-
Cause: User attempted to compress a composite partition index.
-
Action: Create uncompressed composite partition index.
-
Cause: An attempt was made to alter a fake index.
-
Action: Drop the fake index.
-
Cause: User attempted to create index type that online does not support.
-
Action: Use offline index create/rebuild command.
-
Cause: User attempted to create index online without allowing DML Share lock.
-
Action: Allow DML share lock on the base table.
-
Cause: Block maintenance forced the release of a block pin.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Serializable mode is not supported for user INTERNAL.
-
Action: Reconnect as another user and retry the SET TRANSACTION command.
-
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.
-
Cause: Could not match the time to an SCN from the mapping table.
-
Action: Try using a larger time.
-
Cause: The supplied scn was beyond the bounds of a valid scn.
-
Action: Use a valid scn.
-
Cause: User tried to do DML or DDL while in Flashback mode.
-
Action: Disable Flashback and re-attempt the operation.
-
Cause: User tried to do Flashback in the middle of a transaction.
-
Action: Issue a COMMIT statement.
-
Cause: An attempt was made to re-enable Flashback while in Flashback mode.
-
Action: Disable Flashback before re-enabling Flashback mode.
-
Cause: User logged in as
SYS. -
Action: Log in as a different user.
-
Cause: An invalid timestamp was specified.
-
Action: Enter a valid timestamp.
-
Cause: A snapshot expression using
AS OFwas specified when not allowed. -
Action: Do not use the
AS OFclause. -
Cause: The environment variable ORACLE_SID is not set.
-
Action: Set the ORACLE_SID environment variable.
-
Cause: Cannot translate $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf.
-
Action: Ensure that ORACLE_HOME and ORACLE_SID are properly set.
-
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.
-
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.
-
Cause: The System Commit Number has not yet been initialized.
-
Action: Contact Oracle Support Services.
-
Cause: Oracle requested that an I/O error be returned for this operation.
-
Action: This should not occur in normal Oracle operation. Contact support.
-
Cause: The N_CORE system call failed, maybe due to insufficient memory.
-
Action: Specify a smaller number of buffers. Check INIT.ORA parameters.
-
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.
-
Cause: Probably the listener process has died.
-
Action: Contact Oracle Support Services.
-
Cause: The N_CORE system call failed while detaching from the SGA.
-
Action: Note NCX error returned; contact Oracle Support Services.
-
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.
-
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.
-
Cause: The N_SHARE call failed, probably because the listener has died.
-
Action: Check if the listener is running, and contact Oracle Support Services.
-
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.
-
Cause: The N_CORE system call failed while detaching from the SGA.
-
Action: Check NCX error, and contact Oracle Support Services.
-
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.
-
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.
-
Cause: The listener name server entry could not be freed.
-
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
-
Cause: The connection to the name server could not be closed.
-
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The connection to the name server could not be closed.
-
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
-
Cause: The connection to the name server could not be closed.
-
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
-
Cause: The listener's addressing information could not be removed.
-
Action: Additional information gives name server's returned status. Contact Oracle Support Services.
-
Cause: Archive files cannot be created with the given archival control string.
-
Action: Check that the volume exists.
-
Cause: The given archival control string expands into too many characters.
-
Action: Reduce archive control string length.
-
Cause: There is insufficient memory to return the requested value.
-
Action: Reduce memory usage and retry.
-
Cause: The requested environment variable is not set.
-
Action: Ensure that the variable name requested is correct.
-
Cause: There is no room to record the PID for a background process.
-
Action: SHUTDOWN ABORT and restart the database.
-
Cause: There is insufficient memory to expand the environment.
-
Action: Reduce memory usage and retry.
-
Cause: Could not retrieve CPU times because N_STAT failed.
-
Action: Contact Oracle Support Services.
-
Cause: Oracle could not open a file.
-
Action: Check the UNIX errno returned as additional information.
-
Cause: Oracle could not obtain information about an open file.
-
Action: Check the UNIX errno returned as additional information.
-
Cause: An illegal value for the record size was specified.
-
Action: Specify a value for the RECSIZE option that is greater than 0.
-
Cause: An illegal value for the maximum record size was specified.
-
Action: Specify a value for the MAXRECSIZE option that is greater than 0.
-
Cause: An unrecognized processing option was specified.
-
Action: Check the Oracle for nCUBE 2 Installation and User's Guide for valid options.
-
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.
-
Cause: An error occurred trying to close a file.
-
Action: Check the UNIX errno returned as additional information.
-
Cause: An error occurred trying to read from a file.
-
Action: Check the UNIX errno returned as additional information.
-
Cause: The LSEEK system call returned an error.
-
Action: Check the UNIX errno returned as additional information.
-
Cause: The LSEEK system call returned an error.
-
Action: Check the UNIX errno returned as additional information.
-
Cause: An error occurred trying to read from a file.
-
Action: Check the UNIX errno returned as additional information.
-
Cause: An error occurred trying to read from a file.
-
Action: Check the UNIX errno returned as additional information.
-
Cause: This is an internal error
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error
-
Action: Contact Oracle Support Services.
-
Cause: A call to the LKMGR failed to open and convert the bias lock.
-
Action: Check to make sure the LKMGR is up.
-
Cause: A call to the LKMGR failed to close the bias lock.
-
Action: Check to make sure the LKMGR is up.
-
Cause: An attempt was made to automatically spool a file to the printer.
-
Action: No action required.
-
Cause: Oracle timed out waiting for an event.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: An illegal command was executed for the nCUBE platform.
-
Action: There is no need to issue this command.
-
Cause: A command that can only be issued on instance 1 was issued elsewhere.
-
Action: Log on to instance 1 and repeat the command.
-
Cause: An error occurred trying to connect to the redo server.
-
Action: The operating system-specific error message should tell you what to do.
-
Cause: An error occurred trying to close the redo server connection.
-
Action: The operating system-specific error message should tell you what to do.
-
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.
-
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.
-
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).
-
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.
-
Cause: The function routine returned an error. Where routine may be:
-
Action: This message will be preceded by messages providing details about the error. Check those messages to determine what action to take.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A closed parenthesis was missing from the picture mask passed to a UTL_PG conversion routine.
-
Action: Correct the picture mask.
-
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:
-
Action: Correct the mask options parameter.
-
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:
-
Action: Correct the mask options parameter.
-
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:
-
Action: Correct the mask options parameter.
-
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:
-
Action: Correct the mask options parameter.
-
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:
-
Action: Correct the mask options parameter.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The input raw buffer passed to a UTL_PG RAW_TO_NUMBER conversion routine contains invalid decimal data.
-
Action: Correct the input data.
-
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.
-
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.
-
Cause: The input mask passed to UTL_PG numeric conversion routine contained more the 32 characters.
-
Action: Correct the mask input buffer.
-
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.
-
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.
-
Cause: The mask option clause was passed to a UTL_PG conversion routine, but is not supported by UTL_PG. The clause can be:
-
Action: Remove the clause from the mask options parameter in the PL/SQL call to UTL_PG.
-
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.
-
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.
-
Cause: Could be out of disk space.
-
Action: See OSD error accompanying this message.
-
Cause: Block sizes may not match.
-
Action: See OSD error accompanying this message.
-
Cause: DB_BLOCK_SIZE specified in the INIT.ORA file could be incorrect.
-
Action: See OSD error accompanying this message.
-
Cause: File attributes may have changed.
-
Action: See OSD error accompanying this message.
-
Cause: Incorrect path may have been specified for the file.
-
Action: See OSD error accompanying this message.
-
Cause: File may have been truncated or corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: File may have been truncated or corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: File may have been truncated or corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: File may have been corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: File may have been truncated or corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: Incorrect path may have been specified for the file.
-
Action: See OSD error accompanying this message.
-
Cause: File may have been truncated or corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: File may have been truncated or corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: File name may be too long.
-
Action: See OSD error accompanying this message.
-
Cause: File may have been truncated or corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: File may have been truncated or corrupted.
-
Action: See OSD error accompanying this message.
-
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.
-
Cause: Could be out of disk space.
-
Action: See OSD error accompanying this message.
-
Cause: File may be corrupted or truncated.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out of memory.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out of memory.
-
Action: See OSD error accompanying this message.
-
Cause: An error occurred while creating SGA.
-
Action: See OSD error accompanying this message.
-
Cause: SGA may not have been created (database not started).
-
Action: See OSD error accompanying this message.
-
Cause: An error occurred while setting memory protections.
-
Action: See OSD error accompanying this message.
-
Cause: An error occurred while switching stacks.
-
Action: See OSD error accompanying this message.
-
Cause: Unable to map SGA.
-
Action: See OSD error accompanying this message.
-
Cause: An error occurred while destroying the SGA.
-
Action: See OSD error accompanying this message.
-
Cause: May be out of resources.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out of resources.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out of resources.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out of memory.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out of resources.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out of resources.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out memory.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out of memory.
-
Action: See OSD error accompanying this message.
-
Cause: Username may be too long.
-
Action: See OSD error accompanying this message.
-
Cause: Remote operating system login attempted when not allowed.
-
Action: See OSD error accompanying this message.
-
Cause: An operating system error was returned when verifying the role name.
-
Action: See OSD error accompanying this message.
-
Cause: An OS role name was too long.
-
Action: See OSD error accompanying this message.
-
Cause: CONNECT INTERNAL is no longer supported for DBA connections.
-
Action: Please try to connect AS SYSDBA or AS SYSOPER.
-
Cause: File may be corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: Possibly incorrect path specified to the file.
-
Action: See OSD error accompanying this message.
-
Cause: File could be corrupted.
-
Action: See OSD error accompanying this message.
-
Cause: File could be corrupted.
-
Action: See OSD error accompanying this message.
-
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.
-
Cause: Processing option passed is of incorrect format.
-
Action: Consult your IUG for permissible formats.
-
Cause: Could be out of memory.
-
Action: See OSD error accompanying this message.
-
Cause: Unable to access directory.
-
Action: Specify a valid device in ARCHIVE control string.
-
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.
-
Cause: An error was returned while attempting to send a message to the console operator.
-
Action: See OSD error accompanying this message.
-
Cause: Unable to detect the presence of DPMI.
-
Action: Restart Windows and retry.
-
Cause: An attempt was made to connect to S: while in enhanced mode.
-
Action: Restart Windows in standard mode.
-
Cause: This is an internal error.
-
Action: See OSD error accompanying this message.
-
Cause: May be out of resources.
-
Action: See OSD error accompanying this message.
-
Cause: Could be out of resources.
-
Action: See OSD error accompanying this message.
-
Cause: May be out of resources.
-
Action: See OSD error accompanying this message.
-
Cause: Internal buffer may have overflowed.
-
Action: See OSD error accompanying this message.
-
Cause: This is an internal error.
-
Action: See OSD error accompanying this message.
-
Cause: OS roles may not be supported for this platform.
-
Action: See OSD error accompanying this message.
-
Cause: The password specified is invalid.
-
Action: See OSD error accompanying this message.
-
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.
-
Cause: The system time might be set incorrectly.
-
Action: See OSD error accompanying this message.
-
Cause: OS roles may not be supported on this platform.
-
Action: See OSD error accompanying this message.
-
Cause: This is an internal error.
-
Action: See OSD error accompanying this message.
-
Cause: This is an internal error.
-
Action: See OSD error accompanying this message.
-
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.
-
Cause: ORACLE_SID must be at the most 4 alphanumeric characters.
-
Action: Specify an ORACLE_SID with the correct format.
-
Cause: Another instance is currently mounting the database.
-
Action: Try again later.
-
Cause: The user performed a SHUTDOWN ABORT.
-
Action: No action required.
-
Cause: This function may not be implemented.
-
Action: No action required.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
Cause: See OSD error accompanying this message.
-
Action: See OSD error accompanying this message.
-
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.
-
Cause: The value of the PROCESSES initialization parameter was exceeded.
-
Action: Decrease the PROCESSES parameter and restart.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The bind system call failed on the socket.
-
Action: Check additional information for operating system error. Try connecting again.
-
Cause: The accept system call failed on the socket.
-
Action: Check additional information for operating system error. Try connecting again.
-
Cause: The internal buffer is not big enough to hold the message read. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: An existing connection has already been made from ARCHMON to ORASRV.
-
Action: Stop trying to connect.
-
Cause: An existing connection has already been made from log archiver to ORASRV.
-
Action: Stop trying to connect.
-
Cause: The global hardware clock used to generate the System Change Number for Oracle has failed.
-
Action: Check the global hardware clock.
-
Cause: The TXIPC driver cannot obtain the name of the PU. (Possible operating system error.)
-
Action: Check if the PUs are named (consistent).
-
Cause: ORASRV cannot obtain the name of the PU (possible operating system error).
-
Action: Check if the PUs are named (consistent).
-
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.
-
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.
-
Cause: MALLOC() failed to allocate space to hold user interrupt handler.
-
Action: Possible memory resource shortage.
-
Cause: The handle passed to OSNCUI is out of the valid range.
-
Action: Use a valid handle.
-
Cause: The VM_REGION system call failed to get virtual memory region statistics.
-
Action: Check return code in SERCERRNO. Possible operating system failure.
-
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].
-
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].
-
Cause: The MMAP or write system call returned an error. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The MMAP system call returned an error. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The VM_ALLOCATE system call attached the SGA at an incorrect location.
-
Action: Verify that the SGA attach address is valid.
-
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.
-
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.
-
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.
-
Cause: The PORT_RENAME system call failed; possible internal error.
-
Action: Check return code in SERCERRNO, report to Oracle Support Services.
-
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.
-
Cause: The PORT_ALLOCATE system call failed; possible resource exhaustion.
-
Action: Check return code in SERCERRNO, report to Oracle Support Services.
-
Cause: Function was passed an invalid Oracle process ID. This is an internal error.
-
Action: Additional information indicates the invalid process ID.
-
Cause: Function was passed an invalid Oracle process ID. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The PORT_ALLOCATE system call failed.
-
Action: Possible system resource shortage; check the error code in SERCERRNO.
-
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.
-
Cause: The PORT_ALLOCATE system call failed.
-
Action: Possible system resource shortage; check the error code in SERCERRNO.
-
Cause: The NETNAME_CHECK_IN call failed.
-
Action: Check the error code in SERCERRNO. Make sure the network name server is running.
-
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.
-
Cause: The Pipe driver could not send a break message to the Oracle shadow process break thread.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The MSG_SEND system call failed while sending a Mach driver break. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The Mach driver received a message having an unrecognizable message type. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The Mach driver received a message having an unrecognizable message type. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The Mach two-task driver could not reset the connection. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: The routine failed to allocate or set the task's notify port.
-
Action: Possible operating system error. Contact Oracle Support Services.
-
Cause: The PORT_ALLOCATE system call failed; system resources might be exhausted.
-
Action: Possible operating system error. Contact Oracle Support Services.
-
Cause: Open system call returned an error.
-
Action: Check errno.
-
Cause: Processing option passed is of incorrect format.
-
Action: Consult your IUG for permissible formats.
-
Cause: Read system call returned an error.
-
Action: Check errno. Verify file exists.
-
Cause: Read system call returned an error.
-
Action: Check errno. Verify file exists.
-
Cause: Close system call returned an error.
-
Action: Check errno.
-
Cause: Additional information indicates error returned from SLTLN.
-
Action: Check additional information.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Oracle was unable to convert the string representation of a label to binary format.
-
Action: Re-enter a valid label.
-
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.
-
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.
-
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.
-
Cause: Oracle was unable to initialize the library used to obtain security information. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: System call ATOMIC_OP() return error.
-
Action: Check additional information in the trace file.
-
Cause: System call ATOMIC_OP() return unexpected error.
-
Action: Check additional information in the trace file.
-
Cause: System call ATOMIC_OP() return unexpected error.
-
Action: Check additional information in the trace file.
-
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.
-
Cause: The MSG_RPC system call returned an error. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The routine failed to build a port set on which to listen for requests. Possible operating system failure.
-
Action: Contact Oracle Support Services.
-
Cause: The routine received an incorrectly formatted request. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The routine received an incorrectly formatted request. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The PORT_STATUS system called failed. Possible operating system error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The PORT_SET_ADD system called failed. Possible operating system error.
-
Action: Contact Oracle Support Services.
-
Cause: The MALLOC library call failed to allocate space for a callback link. Possible operating system error.
-
Action: Contact Oracle Support Services.
-
Cause: The port PORT_SET_REMOVE system call failed. Possible operating system error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The request to remove a port from the callback set returned a failure code. Possible operating system error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The routine received an incorrectly formatted request. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The VM_ALLOCATE system call returned an error.
-
Action: Check returned error. Possibly out of system resources.
-
Cause: The VM_PROTECT system call returned an error. This is an internal error.
-
Action: Contact Oracle Support Services.
ORA-07500 scglaa: $cantim unexpected return
ORA-07501 scgtoa: $deq unexpected return
ORA-07502 scgcmn: $enq unexpected return
ORA-07503 scgcmn: $setimr unexpected return
ORA-07504 scgcmn: $hiber unexpected return
ORA-07505 scggt: $enq parent lock unexpected return
ORA-07506 scgrl: $deq unexpected return on lockid string
ORA-07507 scgcm: unexpected lock status condition
ORA-07508 scgfal: $deq all unexpected return
ORA-07509 scgfal: $deq parent lock unexpected return
ORA-07510 scgbrm: $getlki unexpected return on lockid string
ORA-07511 sscggtl: $enq unexpected return for master termination lock
ORA-07512 sscggtl: $enq unexpected return for client termination lock
ORA-07513 sscgctl: $deq unexpected return on cancel of term. lock
ORA-07514 scgcan: $deq unexpected return while canceling lock
ORA-07534 scginq: $getlki unexpected return on lockid string
ORA-07548 sftopn: Maximum number of files already open
ORA-07549 sftopn: $OPEN failure
ORA-07550 sftopn: $CONNECT failure
ORA-07551 sftcls: $CLOSE failure
ORA-07552 sftget: $GET failure
ORA-07561 szprv: $IDTOASC failure
ORA-07562 sldext: extension must be 3 characters
ORA-07563 sldext: $PARSE failure
ORA-07564 sldext: wildcard in filename or extension
ORA-07565 sldext: $SEARCH failure
ORA-07568 slspool: $OPEN failure
ORA-07569 slspool: $CLOSE failure
ORA-07570 szrfc: $IDTOASC failure
ORA-07571 szrfc: $FIND_HELD failure
ORA-07572 szrfc: insufficient rolename buffer space
ORA-07573 slkhst: could not perform host operation
ORA-07574 szrfc: $GETUAI failure
ORA-07576 sspexst: $GETJPIW failure on process ID string
ORA-07577 no such user in authorization file
ORA-07578 szprv: $FIND_HELD failure
ORA-07579 spini: $DCLEXH failure
ORA-07580 spstp: $GETJPIW failure
ORA-07581 spstp: cannot derive SID from unexpected process name
ORA-07582 spstp: ORA_SID has illegal value
ORA-07584 spdcr: invalid value for ORA_sid_(proc_)PQL$_item
ORA-07585 spdcr: $PARSE failure
ORA-07586 spdcr: $SEARCH failure
ORA-07587 spdcr: $CREPRC failure
ORA-07588 spdcr: $GETJPIW get image name failure
ORA-07589 spdde: system ID not set
ORA-07590 spdde: $DELPRC failure
ORA-07591 spdde: $GETJPIW failure
ORA-07592 sspgprv: Error obtaining required privileges
ORA-07593 ssprprv: Error release privileges
ORA-07594 spiip: $GETJPIW failure
ORA-07595 sppid: $GETJPIW failure
ORA-07596 sptpa: $GETJPIW failure
ORA-07597 spguns: $GETJPIW failure
ORA-07598 spwat: $SETIMR failure
ORA-07599 spwat: $SCHDWK failure
ORA-07600 slkmnm: $GETSYIW failure
ORA-07601 spguno: $GETJPIW failure
ORA-07602 spgto: $GETJPIW failure
ORA-07605 szprv: $ASCTOID failure
ORA-07606 szprv: $CHKPRO failure
ORA-07607 szaud: $SNDOPR failure
ORA-07608 szprv: $GETUAI failure
ORA-07609 szprv: $HASH_PASSWORD failure
ORA-07610 $GETJPIW failed in retrieving the user's MAC priviledges
ORA-07612 $GETUAI failed in retrieving the user's clearance level
ORA-07613 $GETJPIW failed in retrieving the user's process label
ORA-07614 $CHANGE_CLASS failed in retrieving the user's process label
ORA-07615 $CHANGE_CLASS failed in retrieving the specified file label
ORA-07616 $CHANGE_CLASS failed in retrieving the specified device label
ORA-07617 $FORMAT_CLASS failed translating the binary label to a string
ORA-07618 $IDTOASC failed translating a secrecy level
ORA-07619 $IDTOASC failed translating an integrity level
ORA-07620 smscre: illegal database block size
ORA-07621 smscre: illegal redo block size
ORA-07622 smscre: $CREATE failure
ORA-07623 smscre: $CRMPSC failure
ORA-07624 smsdes: $DGBLSC failure
ORA-07625 smsget: $MGBLSC failure
ORA-07626 smsget: sga already mapped
ORA-07627 smsfre: $CRETVA failure
ORA-07628 smsfre: sga not mapped
ORA-07629 smpall: $EXPREG failure
ORA-07630 smpdal: $DELTVA failure
ORA-07631 smcacx: $EXPREG failure
ORA-07632 smsrcx: $DELTVA failure
ORA-07633 smsdbp: illegal protection value
ORA-07634 smsdbp: $CRETVA failure
ORA-07635 smsdbp: $SETPRT failure
ORA-07636 smsdbp: $MGBLSC failure
ORA-07637 smsdbp: buffer protect option not specified when sga created
ORA-07638 smsget: SGA pad area not large enough for created SGA
ORA-07639 smscre: SGA pad area not large enough (string bytes required)
ORA-07640 smsget: SGA not yet valid. Initialization in progress
ORA-07641 smscre: Unable to use the system pagefile for the SGA
ORA-07642 smprtset: $CMKRNL failure
ORA-07643 smsalo: SMSVAR is invalid
ORA-07645 sszfsl: $CHANGE_CLASS failure
ORA-07646 sszfck: $CREATE failure
ORA-07647 sszfck: $OPEN failure
ORA-07650 sigunc: $GETJPIW failure
ORA-07655 slsprom:$TRNLOG failure
ORA-07656 slsprom:$GETDVI failure
ORA-07657 slsprom:$ASSIGN failure
ORA-07658 slsprom:$QIOW read failure
ORA-07665 ssrexhd: recursive exception encountered string string string string string string
ORA-07670 $IDTOASC failed translating a secrecy category
ORA-07671 $IDTOASC failed translating an integrity category
ORA-07672 $PARSE_CLASS failed translating the string into a binary label
ORA-07680 sou2os: another call to ORACLE currently executing
ORA-07681 sou2os: An error occurred while initializing Oracle
ORA-07682 sou2os: set kernel dispatch fail err
ORA-07683 sou2os: $SETPRV reset error
ORA-07684 sou2os: supervisor stack reset error
ORA-07685 sou2os: supervisor stack set error
ORA-07700 sksarch: interrupt received
ORA-07701 sksatln: internal exception: output buffer too small
ORA-07702 unrecognized device type in archive text
ORA-07703 error in archive text: need '/' after device type
ORA-07704 error in archive text: need ':' after device name
ORA-07705 sksaprs: device name buffer too small
ORA-07706 error in archive text: need disk file name
ORA-07707 error in archive text: need tape label name
ORA-07708 sksaprs: tape label name buffer too small
ORA-07709 sksaprs: archiving to a remote host is not allowed
ORA-07710 sksaprs: file name buffer too small
ORA-07713 sksamtd: could not mount archival device (SYS$MOUNT failure)
ORA-07715 sksadtd: could not dismount archival device (SYS$DISMNT failure)
ORA-07716 sksachk: invalid device specification for ARCHIVE
ORA-07717 sksaalo: error allocating memory
ORA-07718 sksafre: error freeing memory
ORA-07721 scgcm: not enough OS resource to obtain system enqueue
ORA-07740 slemop: incorrect handle size (programming error)
ORA-07741 slemop: $OPEN failure
ORA-07742 slemop: $CONNECT failure
ORA-07743 slemop: incorrect error file attributes
ORA-07744 slemcl: invalid error message file handle
ORA-07745 slemcl: $CLOSE failure
ORA-07746 slemrd: invalid error message file handle
ORA-07747 slemrd: $READ failure
ORA-07750 slemcr: fopen failure
ORA-07751 slemcr: malloc failure
ORA-07753 slemcf: fseek before write failure
ORA-07754 slemcf: fwrite failure
ORA-07755 slemcf: fseek before read failure
ORA-07756 slemcf: fread failure
ORA-07757 slemcc: invalid handle
ORA-07758 slemcw: invalid handle
ORA-07759 slemtr: invalid destination
ORA-07760 slemtr: $open failure
ORA-07800 slbtpd: invalid number
ORA-07801 slbtpd: invalid exponent
ORA-07802 slbtpd: overflow while converting to packed decimal
ORA-07803 slpdtb: invalid packed decimal nibble
ORA-07804 slpdtb: number too large for supplied buffer
ORA-07820 sspscn: SYS$CRELNM failure
ORA-07821 sspsdn: SYS$DELLNM failure
ORA-07822 sspscm: SYS$CREMBX failure
ORA-07823 sspsqr: $QIO failure
ORA-07824 sspain: $SETIMR failure
ORA-07825 sspsck: $QIO failure at AST level
ORA-07826 sspscm: SYS$GETDVIW failure
ORA-07840 sllfop: LIB$GET_VM failure
ORA-07841 sllfop: SYS$OPEN failure
ORA-07842 sllfcl: SYS$CLOSE failure
ORA-07843 sllfcl: LIB$FREE_VM failure
ORA-07844 sllfop: LIB$GET_VM failure
ORA-07845 sllfcl: LIB$FREE_VM failue
ORA-07846 sllfop: string byte record too big for string byte user buffer
ORA-07847 sllfop: $CONNECT failure
ORA-07848 sllfrb: $GET failure
ORA-07849 sllfsk: $GET failure
ORA-07850 sllfop: bad option
ORA-07860 osnsoi: error setting up interrupt handler
ORA-07880 sdopnf: internal error
ORA-08000 maximum number of session sequence lists exceeded
ORA-08001 maximum number of sequences per session exceeded
ORA-08002 sequence string.CURRVAL is not yet defined in this session
ORA-08003 sequence string.NEXTVAL exceeds internal limits
ORA-08004 sequence string.NEXTVAL string stringVALUE and cannot be instantiated
ORA-08005 specified row does not exist
ORA-08006 specified row no longer exists
ORA-08008 another instance is mounted with USE_ROW_ENQUEUES = string
ORA-08100 index is not valid - see trace file for diagnostics
ORA-08101 index key does not exist root dba string, dba string (string)
ORA-08102 index key not found, obj# string, dba string (string)
ORA-08103 object no longer exists
ORA-08104 this index object string is being online built or rebuilt
ORA-08105 Oracle event to turn off smon cleanup for online index build
ORA-08106 can not create journal table string.string
ORA-08108 may not build or rebuild this type of index online
ORA-08109 nosort is not a supported option for online index build
ORA-08110 Oracle event to test SMON cleanup for online index build
ORA-08111 a partitioned index may not be coalesced as a whole
ORA-08112 a composite partition may not be coalesced as a whole
ORA-08113 composite partition index may not be compressed
ORA-08114 can not alter a fake index
ORA-08115 can not online create/rebuild this index type
ORA-08116 can not acquire DML enough lock(S mode) for online index build
ORA-08117 Index Organized Table operation released its block pin
ORA-08118 Deferred FK constraints cannot be enforced, index too big (string)
ORA-08119 The new initrans will make the index too big
ORA-08175 discrete transaction restriction violated (string)
ORA-08176 consistent read failure; rollback data not available
ORA-08177 can't serialize access for this transaction
ORA-08178 illegal SERIALIZABLE clause specified for user INTERNAL
ORA-08179 concurrency check failed
ORA-08180 no snapshot found based on specified time
ORA-08181 specified number is not a valid system change number
ORA-08182 operation not supported while in Flashback mode
ORA-08183 Flashback cannot be enabled in the middle of a transaction.
ORA-08184 attempting to re-enable Flashback while in Flashback mode
ORA-08185 Flashback not supported for user SYS.
ORA-08186 invalid timestamp specified
ORA-08187 snapshot expression not allowed here
ORA-08205 ora_addr: $ORACLE_SID not set in environment
ORA-08206 ora_addr: cannot translate address file name
ORA-08207 ora_addr: cannot open address file
ORA-08208 ora_addr: cannot read from address file
ORA-08209 scngrs: SCN not yet initialized
ORA-08210 Requested I/O error
ORA-08230 smscre: failed to allocate SGA
ORA-08231 smscre: unable to attach to SGA
ORA-08232 smsdes: cannot detach from SGA
ORA-08233 smsdes: cannot unmap SGA
ORA-08234 smsget: cannot get instance listener address
ORA-08235 smsget: listener not on this node
ORA-08236 smsget: cannot share subcube with listener
ORA-08237 smsget: SGA region not yet created
ORA-08238 smsfre: cannot detach from SGA
ORA-08260 ora_addr: cannot open nameserver
ORA-08261 ora_addr: cannot find name in nameserver
ORA-08263 ora_addr: cannot free listener address
ORA-08264 ora_addr: cannot close nameserver
ORA-08265 create_ora_addr: cannot open nameserver
ORA-08266 create_ora_addr: cannot register name in nameserver
ORA-08267 destroy_ora_addr: cannot close nameserver
ORA-08268 create_ora_addr: cannot close nameserver
ORA-08269 destroy_ora_addr: cannot destroy name
ORA-08270 sksachk: Illegal archival control string
ORA-08271 sksabln: Buffer size not large enough for archive control string
ORA-08274 Out of memory for environment variable
ORA-08275 Environment variable unset
ORA-08276 No room in nameserver for pid
ORA-08277 Cannot set environment variable
ORA-08278 Cannot get CPU statistics
ORA-08308 sllfop: Cannot open file
ORA-08309 sllfop: Cannot fstat file
ORA-08310 sllfop: Bad value for recsize
ORA-08311 sllfop: bad value for maxrecsize
ORA-08312 sllfop: unrecognized processing option
ORA-08313 sllfop: could not allocate buffers
ORA-08314 sllfcf: Error closing file
ORA-08315 sllfrb: Error reading file
ORA-08316 sllfsk: Error seeking in file.
ORA-08317 sllfsk: Error seeking in file.
ORA-08318 sllfsk: Error reading file
ORA-08319 sllfsk: Error reading file
ORA-08320 scnget: Call to scnget before scnset or scnfnd.
ORA-08321 scnmin: NOT IMPLEMENTED YET
ORA-08322 scnmin: open/convert of bias lock failed
ORA-08323 scnmin: close of bias lock failed
ORA-08330 Printing not supported
ORA-08331 Wait operation timed out
ORA-08332 rollback segment #string specified not available
ORA-08340 This command not allowed on nCUBE, only one thread is ever used.
ORA-08341 On nCUBE, this command can only be executed from instance 1.
ORA-08342 sropen: failed to open a redo server connection
ORA-08343 srclose: failed to close a redo server connection
ORA-08344 srapp: failed to send redo data to the redo server
ORA-08401 invalid compiler name: string
ORA-08412 error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
ORA-08413 invalid compiler type in FORMAT parameter at string
ORA-08414 error encountered in string
ORA-08429 raw data has invalid digit in display type data
ORA-08430 raw data missing leading sign
ORA-08431 raw data missing zero as defined in picture
ORA-08432 raw data has invalid floating point data
ORA-08433 invalid picture type in convert raw to number
ORA-08434 raw data has invalid trailing sign
ORA-08435 PICTURE MASK missing the leading sign when SIGN IS LEADING specified
ORA-08436 raw data has invalid sign digit
ORA-08437 invalid picture type in picture mask
ORA-08440 raw buffer is too short to hold converted data
ORA-08441 closed parenthesis missing in picture mask
ORA-08443 syntax error in BLANK WHEN ZERO clause in mask options
ORA-08444 syntax error in JUSTIFIED clause in mask options
ORA-08445 syntax error in SIGN clause in mask options
ORA-08446 syntax error in SYNCHRONIZED clause in mask options
ORA-08447 syntax error in USAGE clause in mask options
ORA-08448 syntax error in DECIMAL-POINT environment clause
ORA-08449 invalid numeric symbol found in picture mask
ORA-08450 invalid specification of CR in picture mask
ORA-08451 invalid specification of DB in picture mask
ORA-08452 specification of E in picture mask is unsupported
ORA-08453 more than one V symbol specified in picture mask
ORA-08454 more than one S symbol specified in picture mask
ORA-08455 syntax error in CURRENCY SIGN environment clause
ORA-08456 no sign in picture mask but SIGN clause in mask options
ORA-08457 syntax error in SEPARATE CHARACTER option of SIGN clause
ORA-08458 invalid format parameter
ORA-08459 invalid format parameter length
ORA-08460 invalid environment clause in environment parameter
ORA-08462 raw buffer contains invalid decimal data
ORA-08463 overflow converting decimal number to Oracle number
ORA-08464 input raw decimal data contains more than 42 digits
ORA-08465 input mask contains more than 32 characters
ORA-08466 raw buffer length string is too short for string
ORA-08467 error converting Oracle number to string
ORA-08468 mask option string is not supported
ORA-08498 Warning: picture mask 'string' overrides picture mask option 'USAGE IS string' to 'USAGE IS DISPLAY'
ORA-08499 Warning: picture mask options 'string' ignored by UTL_PG
ORA-09200 sfccf: error creating file
ORA-09201 sfcopy: error copying file
ORA-09202 sfifi: error identifying file
ORA-09203 sfofi: error opening file
ORA-09204 sfotf: error opening temporary file
ORA-09205 sfqio: error reading or writing to disk
ORA-09206 sfrfb: error reading from file
ORA-09207 sfsrd: error reading from file
ORA-09208 sftcls: error closing file
ORA-09209 sftget: error reading from file
ORA-09210 sftopn: error opening file
ORA-09211 sfwfb: error writing to file
ORA-09212 sfwfbmt: error writing to file
ORA-09213 slgfn: error fabricating file name
ORA-09214 sfdone: I/O error detected
ORA-09215 sfqio: error detected in IOCompletionRoutine
ORA-09216 sdnfy: bad value 'string' for parameter string
ORA-09217 sfsfs: failed to resize file
ORA-09218 sfrfs: failed to refresh file size
ORA-09240 smpalo: error allocating PGA memory
ORA-09241 smsalo: error allocating SGA memory
ORA-09242 smscre: error creating SGA
ORA-09243 smsget: error attaching to SGA
ORA-09244 smprset: error setting memory protections
ORA-09245 smcstk: error switching stacks
ORA-09246 sfsmap: unable to map SGA
ORA-09247 smsdes: error destroying the SGA
ORA-09260 sigpidu: error obtaining process id
ORA-09261 spdcr: error creating detached (background) process
ORA-09262 spdde: error terminating detached (background) process
ORA-09263 spini: error initializing process
ORA-09264 sptpa: error flagging process
ORA-09265 spwat: error temporarily suspending process
ORA-09266 spawn: error starting an Oracle process
ORA-09270 szalloc: error allocating memory for security
ORA-09271 szlon: error verifying user name
ORA-09272 remote os logon is not allowed
ORA-09273 szrfc: error verifying role name
ORA-09274 szrfc: insufficient role name buffer space
ORA-09275 CONNECT INTERNAL is not a valid DBA connection
ORA-09280 sllfcf: error closing file
ORA-09281 sllfop: error opening file
ORA-09282 sllfrb: error reading records
ORA-09283 sllfsk: error skipping records
ORA-09284 sllfop: cannot allocate read buffer
ORA-09285 sllfop: unrecognizable processing option, incorrect format
ORA-09290 sksaalo: error allocating memory for archival
ORA-09291 sksachk: invalid device specified for archive destination
ORA-09292 sksabln: unable to build archive file name
ORA-09293 sksasmo: unable to send message to console
ORA-09300 osncon: unable to connect, DPMI not available
ORA-09301 osncon: local kernel only supported in standard mode
ORA-09310 sclgt: error freeing latch
ORA-09311 slsleep: error temporarily suspending process
ORA-09312 slspool: error spooling file to printer
ORA-09313 slsprom: error prompting user
ORA-09314 sltln: error translating logical name
ORA-09315 sql2tt: two-task error translating ORACLE_EXECUTABLE
ORA-09316 szrpc: unable to verify password for role
ORA-09317 szprv: insufficient privileges
ORA-09318 slkhst: unable to host out to operating system
ORA-09319 slgtd: unable to obtain the current date and time
ORA-09320 szrfc: unable to obtain the list of valid OS roles
ORA-09321 slzdtb: unable to convert zoned decimal to binary
ORA-09322 slpdtb: unable to convert packed decimal to binary
ORA-09330 Session terminated internally by Oracle or by an Oracle DBA
ORA-09340 Specified ORACLE_SID is either invalid or too long
ORA-09341 scumnt: unable to mount database
ORA-09342 Detached process terminated by Oracle during shutdown abort
ORA-09344 spsig: error signalling thread
ORA-09350 Windows 32-bit Two-Task driver unable to allocate context area
ORA-09351 Windows 32-bit Two-Task driver unable to allocate shared memory
ORA-09352 Windows 32-bit Two-Task driver unable to spawn new ORACLE task
ORA-09353 Windows 32-bit Two-Task driver unable to open event semaphore
ORA-09354 Windows 32-bit Two-Task driver: ORACLE task unexpectedly died
ORA-09360 Windows 3.1 Two-Task driver unable to allocate context area
ORA-09361 Windows 3.1 Two-Task driver unable to lock context area
ORA-09362 Windows 3.1 Two-Task driver unable to deallocate context area
ORA-09363 Windows 3.1 Two-Task driver invalid context area
ORA-09364 Windows 3.1 Two-Task driver unable to create hidden window
ORA-09365 Windows 3.1 Two-Task driver unable to destroy hidden window
ORA-09366 Windows 3.1 Two-Task driver unable to allocate shared memory
ORA-09367 Windows 3.1 Two-Task driver unable to deallocate shared memory
ORA-09368 Windows 3.1 Two-Task driver unable to spawn ORACLE
ORA-09369 Windows 3.1 Two-Task driver bad instance handle
ORA-09370 Windows 3.1 Two-Task driver ORACLE task timed out
ORA-09700 sclin: maximum number of latches exceeded
ORA-09701 scnfy: maximum number of processes exceeded
ORA-09702 sem_acquire: cannot acquire latch semaphore
ORA-09703 sem_release: cannot release latch semaphore
ORA-09704 sstascre: ftok error in creating test and set pages.
ORA-09705 spcre: cannot initialize latch semaphore
ORA-09706 slsget: get_process_stats error.
ORA-09708 soacon: failed to bind socket to port.
ORA-09709 soacon: failed to accept a connection.
ORA-09710 soarcv: buffer overflow.
ORA-09711 orasrv: archmon already connected.
ORA-09712 orasrv: log archiver already connected.
ORA-09713 Global hardware clock failure caused instance termination.
ORA-09714 Two Task interface: cannot obtain puname
ORA-09715 orasrv: cannot obtain puname
ORA-09716 kslcll: Unable to fix in-flux lamport latch.
ORA-09717 osnsui: maximum number of user interrupt handlers exceeded.
ORA-09718 osnsui: cannot set up user interrupt handler.
ORA-09719 osncui: invalid handle.
ORA-09740 slsget: cannot get virtual memory region statistics.
ORA-09741 spwat: error waiting for a post.
ORA-09742 sppst: error during a post.
ORA-09743 smscre: could not attach shared memory.
ORA-09744 smsget: mmap returned an error.
ORA-09745 smscre: vm_allocate error, unable to create shared memory.
ORA-09746 smscre: shared memory attach address incorrect.
ORA-09747 pw_detachPorts: server call pws_detach failed.
ORA-09748 pws_look_up: fork failed
ORA-09749 pws_look_up: port lookup failure
ORA-09750 pw_attachPorts: port_rename failed.
ORA-09751 pw_attachPorts: server call pws_attach failed.
ORA-09752 pw_attachPorts: port_allocate failed.
ORA-09753 spwat: invalid process number.
ORA-09754 sppst: invalid process number passed to sppst.
ORA-09755 osngpn: port allocation failure.
ORA-09756 osnpns: no port in the name server.
ORA-09757 osnipn: port allocation failure.
ORA-09758 osnipn: could not check port in name server.
ORA-09759 osnsbt: bad message received.
ORA-09760 osnpui: cannot send break message
ORA-09761 pw_destroyPorts: server call pws_stop_instance failed.
ORA-09762 sNeXT_instanceName: translation error.
ORA-09763 osnmpx: send/receive error exchanging Mach ports.
ORA-09764 osnmop: access error on oracle executable
ORA-09765 osnmop: fork failed
ORA-09766 osnmop: buffer allocation failure.
ORA-09767 osnmfs: bad return code from msg_send.
ORA-09768 osnmgetmsg: could not read a message
ORA-09769 osnmbr: cannot send break message
ORA-09770 pws_look_up: translation failure.
ORA-09771 osnmwrtbrkmsg: bad return code from msg_send.
ORA-09772 osnpmetbrkmsg: message from host had incorrect message type
ORA-09773 osnmgetdatmsg: message from host had incorrect message type
ORA-09774 osnmui: cannot send break message
ORA-09775 osnmrs: reset protocol error
ORA-09776 pws_look_up: access error on (Oracle helper) executable
ORA-09777 osnpbr: cannot send break message
ORA-09778 snynfyport: failure allocating the notify port.
ORA-09779 snyGetPort: failure to allocate a port.
ORA-09786 sllfop: open error, unable to open file.
ORA-09787 sllfop: unrecognizable processing option, incorrect format.
ORA-09788 sllfrb: unable to read file.
ORA-09789 sllfsk: unable to read file.
ORA-09790 sllfcf: unable to close file.
ORA-09791 slembdf: translation error, unable to translate error file name.
ORA-09792 sllfop: cannot allocate read buffer.
ORA-09793 szguns: length of user name is greater than buffer.
ORA-09794 szrbuild: length of role name is greater than buffer.
ORA-09795 szrbuild: malloc of role structure failed.
ORA-09796 szrbuild: malloc of role name failed.
ORA-09797 Failed to get O/S MAC privileges.
ORA-09798 Label comparison failed.
ORA-09799 File label retrieval failed.
ORA-09800 Process sensitivity label retrieval failed.
ORA-09801 Unable to get user ID from connection
ORA-09802 Conversion of binary label to string failed.
ORA-09803 Allocation of string buffer failed.
ORA-09804 Class conversion from binary to ORACLE failed.
ORA-09805 conversion of category number to string failed.
ORA-09806 Allocation of label string buffer failed.
ORA-09807 Conversion of label from string to binary failed.
ORA-09808 Could not obtain user clearance.
ORA-09809 Unable to get user's group ID from connection
ORA-09810 Unable to get process ID from connection
ORA-09811 Unable to initialize package.
ORA-09812 Unable to get user clearance from connection
ORA-09813 Unable to get directory status
ORA-09814 Unable to expand file name
ORA-09815 File name buffer overflow
ORA-09816 Unable to set effective privileges
ORA-09817 Write to audit file failed.
ORA-09818 Number is too large
ORA-09819 Number exceeds maximum legal value
ORA-09820 Conversion of class string to numeric representation failed.
ORA-09821 Numeric label is not valid
ORA-09822 Translation of audit file name failed.
ORA-09823 device name is too long
ORA-09824 Unable to enable allowmacaccess privilege.
ORA-09825 Unable to disable allowmacaccess privilege.
ORA-09826 SCLIN: cannot initialize atomic latch.
ORA-09827 SCLGT: atomic latch return unknown error.
ORA-09828 SCLFR: atomic latch return error.
ORA-09829 pw_createPorts: server call pws_start_instance failed.
ORA-09830 snyAddPort: failed to perform a remote procedure call.
ORA-09831 snyStartThread: failed to build the server port set.
ORA-09832 infoCallback: bad message format.
ORA-09833 addCallback: bad message format.
ORA-09834 snyGetPortSet: failed to collect info on a port.
ORA-09835 addCallback: callback port is already in a set.
ORA-09836 addCallback: could not add a port to the callback set.
ORA-09837 addCallback: could not add allocate a callback link.
ORA-09838 removeCallback: failure removing the callback port.
ORA-09839 removeCallback: callback port is not in the callback set.
ORA-09840 soacon: Name translation failure.
ORA-09841 soacon: Name translation failure.
ORA-09842 soacon: Archmon unable to create named pipe.
ORA-09843 soacon: Archmon unable to create named pipe.
ORA-09844 soacon: Archmon unable to open named pipe.
ORA-09845 soacon: Archmon unable to open named pipe.
ORA-09846 soacon: ARCH unable to open named pipe.
ORA-09847 soacon: ARCH unable to open named pipe.
ORA-09850 soacon: Archmon unable to lock named pipe.
ORA-09851 soacon: Archmon unable to lock named pipe.
ORA-09853 snyRemovePort: bad return code from request.
ORA-09854 snyPortInfo: bad return code from request.
ORA-09855 removeCallback: bad message format.
ORA-09856 smpalo: vm_allocate error while allocating pga.
ORA-09857 smprset: vm_protect error while protecting pga.
| Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
8
ORA-09858 to ORA-12299
-
Cause: ULIMIT system call returned an error.
-
Action: Check errno.
-
Cause: Failure of sltln(?/tasdef@.dbf) while creating test and set pages.
-
Action: Check additional return error for more information.
-
Cause: CREATE() failed when trying to create the TASDEF file.
-
Action: Verify permissions on $(ORACLE_HOME)/dbs directory.
-
Cause: Unable to open tasdef@.dbf file.
-
Action: Check errno. Possible permission problem. Verify that tasdef@.dbf file exists.
-
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.
-
Cause: Write call failed.
-
Action: Check errno returned. Possibly out of space on device.
-
Cause: Close system call returned an error.
-
Action: Check errno returned. Possible operating system failure.
-
Cause: Error in SHMGET.
-
Action: Check errno returned. Verify that enough shared memory is available on the system.
-
Cause: Error in SHMAT.
-
Action: Check errno returned.Verify that enough shared memory is available on the system.
-
Cause: Error in SHMAT.
-
Action: Check errno returned.Verify that enough shared memory is available on the system.
-
Cause: Error in SHMDT.
-
Action: Check errno returned.
-
Cause: Error in SHMDT.
-
Action: Check errno returned.
-
Cause: Error in SHMCTL.
-
Action: Check errno returned.
-
Cause: The ORATAB file does not exist.
-
Action: Install Oracle before you use it or re-create the ORATAB file.
-
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.
-
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.
-
Cause: Failure of sltln(txipc@.trc) while creating debug channel.
-
Action: Check additional return error for more information.
-
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.
-
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.
-
Cause: The TXIPX driver failed to allocate enough heap space for its context area buffers.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: No entry exists for the user in the Oracle password file.
-
Action: Have the database administrator install a password entry by running ORAPASSWD.
-
Cause: The password entered by the user was incorrect.
-
Action: Enter the correct password.
-
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.
-
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.
-
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.
-
Cause: Oracle was unable to encrypt a password. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: A user attempted to connect as "internal," but did not specify a password.
-
Action: Connect as internal again and specify a password.
-
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.
-
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.
-
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.
-
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.
-
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:
-
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:
-
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:
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt to close a password file failed.
-
Action: Check the UNIX error number for the specific reason.
-
Cause: The removal of the old password file failed.
-
Action: Check the UNIX error number for the specific reason.
-
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.
-
Cause: Oracle was unable to complete the saving of the current password file.
-
Action: Check the UNIX error number for the specific reason.
-
Cause: Oracle was unable to create a password file.
-
Action: Check the UNIX error number for the specific reason.
-
Cause: Oracle was unable to change a password file to be read only.
-
Action: Check the UNIX error number for the specific reason.
-
Cause: Oracle was unable to save the previous values of selected signal handlers. This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: Oracle was unable to restore the previous values of selected signal handlers. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The attempt to send a termination signal to IMON failed. This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
Cause: Failure of SLTLN in SCUMNT.
-
Action: Check additional returned error for more information.
-
Cause: Open system call returned an error.
-
Action: Check errno.
-
Cause: Lock file operating system call returned an error.
-
Action: Check errno.
-
Cause: Close system call returned an error.
-
Action: Check errno.
-
Cause: The process was unable to initialize the SDI channel properly.
-
Action: Correct the operating system error and retry the operation.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The process was unable to add a page to the SDI buffer pool.
-
Action: Correct the operating system error and retry the operation.
-
Cause: The process was unable to remove a page to the SDI buffer pool.
-
Action: Correct the operating system error and retry the operation.
-
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.
-
Cause: File does not exist or is not accessible.
-
Action: Restart the instance to create the SGA definition file.
-
Cause: UNIX read() operation failed.
-
Action: Check errno and take appropriate action.
-
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.
-
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.
-
Cause: SKGMSDEF struct is corrupted and/or segment addresses are modified.
-
Action: Safely shut down the instance and mount the SGA segments again.
-
Cause: Pointer to SKGMSDEF struct used without validating it.
-
Action: Assign a valid address to the SKGMSDEF struct pointer before using it.
-
Cause: Report block type for details of another error.
-
Action: See associated error message.
-
Cause: Report block type and data object number for details of another error.
-
Action: See associated error message.
-
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.
-
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.
-
Cause: Report tablespace name for details of another error.
-
Action: See associated error message.
-
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.
-
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.
-
Cause: There are two possible causes of this 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.
-
Cause: Out of SGA memory.
-
Action: Restart the instance. If the problem persists, then contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
Cause: This message summarizes test recovery result.
-
Action: No action is needed. See other messages on the error stack.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: One of the files to be recovered is renamed as missing.
-
Action: Rename the file to the correct file or offline it.
-
Cause: Both test recovery and parallel recovery are requested.
-
Action: Drop either one of the two recovery options.
-
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.
-
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.
-
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
-
Action: Use a smaller number.
-
Cause: The number specified in the ALLOW n CORRUPTION option is too big.
-
Action: Change to allow zero or one corruption.
-
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.
-
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.
-
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.
-
Cause: Cannot perform the operation on tablespace with AUTO SEGMENT SPACE MANAGEMENT.
-
Action: Recheck the tablespace name and re-issue the statement.
-
Cause: Rollback segments cannot be created in dictionary managed tablespaces when the
SYSTEMtablespace is locally managed. -
Action: Recheck the tablespace name and re-issue the statement.
-
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.
-
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.
-
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.
-
Cause: The
SYSTEMtablespace is being migrated to locally managed format. -
Action: Re-issue this command once
SYSTEMtablespace migration is complete. -
Cause:
SYSTEMtablespace migration requires rollback segment in locally managed tablespace. -
Action: Drop rollback segments in dictionary managed tablespaces other than
SYSTEMand create rollback segments in locally managed tablespace. Then retry migration. -
Cause: When
SYSTEMtablespace is migrated, found rollback segments in dictionary managed tablespaces. -
Action: Drop the rollback segments in dictionary managed tablespaces and re-issue the command.
-
Cause: When
SYSTEMtablespace 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.
-
Cause: When
SYSTEMtablespace is being migrated, no user should haveSYSTEMas the default temporary tablespace. -
Action: Re-issue this command after altering the default temporary tablespace setting for all users.
-
Cause: When
SYSTEMtablespace is being migrated, dictionary tables tried to extend recursively more than 1000 times. -
Action: If
SYSTEMtablespace is very large, then simply reissue the tablespace migration command. -
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.
-
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.
-
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.
-
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.
-
Cause: There was no materialized view log on the master table.
-
Action: Create a materialized view log on the master table.
-
Cause: The materialized view with the given owner and name does not exist.
-
Action: Verify inputs and create a materialized view.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to unregister a materialized view that is not registered.
-
Action: No action required.
-
Cause: The indicated materialized view is no longer valid.
-
Action: Contact Oracle Support Services.
-
Cause: Materialized view log on the indicated table already has ROWID information.
-
Action: No action required.
-
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.
-
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.
-
Cause: Materialized view log on the indicated table already has primary key columns.
-
Action: No action required.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to use LOB columns as filter columns.
-
Action: Remove LOB columns from the filter columns list and retry command.
-
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.
-
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.
-
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.
-
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.
-
Cause: The materialized view log was younger than the last refresh.
-
Action: A complete refresh is required before the next fast refresh.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW statement.
-
Action: Specify only valid options.
-
Cause: An invalid option was used in a CREATE MATERIALIZED VIEW LOG statement.
-
Action: Specify only valid options.
-
Cause: An invalid option was used in an ALTER MATERIALIZED VIEW LOG statement.
-
Action: Specify only valid options.
-
Cause: The ON COMMIT refresh attribute, incompatible with other refresh options such as automatic periodic refresh, was specified.
-
Action: Specify only valid options.
-
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.
-
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.
-
Cause: The materialized view did not satisfy conditions for refresh at commit time.
-
Action: Specify only valid options.
-
Cause: The materialized view query definition introduced a cyclic dependency with existing materialized views.
-
Action: Modify the materialized view query definition.
-
Cause: The NEVER REFRESH option may not be used under the following conditions:
-
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.
-
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.
-
Cause: An attempt was made to use the prebuilt tables.
-
Action: Reissue the SQL command using BUILD IMMEDIATE or BUILD DEFERRED.
-
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.
-
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.
-
Cause: An invalid option was used in an ALTER MATERIALIZED VIEW statement.
-
Action: Specify only valid options.
-
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.
-
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.
-
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.
-
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.
-
Cause: The Replication API does not support the following options and types of materialized view:
-
Action: Create a PRIMARY KEY materialized view using REFRESH WITH PRIMARY KEY and/or remove the invalid options.
-
Cause: The refresh group being instantiated did not contain any materialized views.
-
Action: Modify the template to include at least one materialized view.
-
Cause: The updatable materialized view was missing the updatable materialized view log required to track updates made to the materialized view.
-
Action: Create the updatable materialized view log.
-
Cause: Only materialized views can be offline instantiated. The object being offline instantiated was not a valid materialized view.
-
Action: Remove the object from the template or replace the object with a valid materialized view.
-
Cause: Offline instantiation does not support materialized views using the following options:
-
Action: Remove the invalid options.
-
Cause: Offline instantiation requires materialized view definition queries to observe the following constraints:
-
Action: Modify the materialized view definition query.
-
Cause: The updatable materialized view is missing the updatable materialized view log that is required to track updates made to the materialized view.
-
Action: Create the updatable materialized view log.
-
Cause: An out-of-sequence request was made and it cannot be processed.
-
Action: Try again with a valid request.
-
Cause: An attempt was made to access an invalid memory region.
-
Action: Reconnect and try the command again.
-
Cause: ] An attempt was made to access an invalid field or object in the Java Virtual Memory.
-
Action: Retry the request.
-
Cause: The result set threshold or LOB threshold value is not supported.
-
Action: Specify a threshold value below 64K.
-
Cause: Temporary updatable materialized view log was not created or was dropped.
-
Action: Re-create the temporary updatable materialized view log.
Warning: This will cause a complete refresh of the materialized view.
-
Cause: Refresh result set sent through client method REFRESH_REQ_RESULT returned an unknown value.
-
Action: Re-issue the refresh request.
-
Cause: The following materialized view options require an 8.1 or higher compatibility setting:
The following materialized view options require a 9.0.0 or higher compatibility setting:
-
Action: Shut down and restart with an appropriate compatibility setting.
-
Cause: An attempt was made to update a read-only materialized view. Only Oracle is allowed to update a read-only materialized view.
-
Action: No action required.
-
Cause: An attempt was made to create an index-organized materialized aggregate view or an index-organized updatable ROWID materialized view. This is not supported.
-
Action: Try to create the materialized view without the index organization clause.
-
Cause: An attempt was made to drop a materialized view using a command other than DROP MATERIALIZED VIEW.
-
Action: Use the DROP MATERIALIZED VIEW command.
-
Cause: An attempt was made to alter a materialized view using a command other than ALTER MATERIALIZED VIEW.
-
Action: Use the ALTER MATERIALIZED VIEW command.
-
Cause: Materialized view log on the indicated table already has object id information.
-
Action: No action required.
-
Cause: The CREATE MATERIALIZED VIEW LOG command was issued with the WITH OBJECT ID option and the master table is not an object table.
-
Action: Either specify the name of an object table, or remove the WITH OBJECT ID clause.
-
Cause: An attempt was made to online redefine a table owned by SYS or SYSTEM.
-
Action: Do not attempt to online redefine a table owned by SYS or SYSTEM.
-
Cause: An attempt was made to online redefine a table containing a LONG column, an ADT column, or a FILE column.
-
Action: Do not attempt to online redefine a table containing a LONG column, an ADT column, or a FILE column.
-
Cause: An attempt was made to online redefine a table that does not have a primary key defined on it.
-
Action: Do not attempt to online redefine a table that does not have a primary key defined on it.
-
Cause: An attempt was made to online redefine a table that is either a clustered table, AQ table, temporary table, or IOT overflow table.
-
Action: Do not attempt to online redefine a table that is a clustered table, AQ table, temporary table, or IOT overflow table.
-
Cause: An attempt was made to online redefine a table that had materialized views defined on it or had a materialized view log defined on it or is a master.
-
Action: Drop all materialized views and materialized view logs before attempting to online redefine the table.
-
Cause: An attempt was made to online redefine a table that is either a materialized view or a replicated table.
-
Action: Do not attempt to online redefine a table that is either a materialized view or a replicated table.
-
Cause: The table is not the interim table of the corresponding table to be online redefined.
-
Action: Pass in the valid interim table.
-
Cause: There was an error during the online redefinition process.
-
Action: Abort the online redefinition process.
-
Cause: There was an error originating from this materialized view log. One possible cause is that schema redefinition has occurred on the master table and one or more columns in the log is now a different type than the corresponding master columns. Another possible cause is that there is a problem accessing the underlying materialized view log table.
-
Action: Check further error messages in the stack for more detail about the cause. If there has been schema redefinition, drop the materialized view log and recreate it.
-
Cause: There are some changes (that is, conventional DML, direct load, partition maintenance operation) in the master tables during materialized view refresh.
-
Action: Refresh the affected materialized views again.
ORA-09870 spini: failure initializing maximum number of open files.
ORA-09871 TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.
ORA-09872 TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.
ORA-09873 TASDEF_OPEN: open error when opening tasdef@.dbf file.
ORA-09874 TASDEF_READ: read error, unable to read tasdef@.dbf file.
ORA-09875 TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.
ORA-09876 TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.
ORA-09877 sstascre: shmget error, unable to get a shared memory segment.
ORA-09878 sstascre/sstasat: shmat error, unable to attach tas write page
ORA-09879 sstascre/sstasat: shmat error, unable to attach tas read page
ORA-09880 sstasfre/sstasdel: shmdt error, unable to detach tas write page
ORA-09881 sstasfre/sstasdel: shmdt error, unable to detach tas read page
ORA-09882 sstasfre/sstasdel: shmctl error, unable to remove tas shm page
ORA-09883 Two Task interface: oratab file does not exist
ORA-09884 Two Task interface: SID doens't match current PU
ORA-09885 osnTXtt: cannot create TXIPC channel
ORA-09886 osnTXtt: translation error while expanding txipc@.trc.
ORA-09887 osnTXtt: Failed to create/open debug channel.
ORA-09888 osnTXtt: txipc channel creation failed
ORA-09889 osnTXtt: access error on oracle executable
ORA-09890 osnTXtt: malloc failed
ORA-09908 slkmnm: gethostname returned error code.
ORA-09909 Malloc of scratch buffer failed.
ORA-09910 Unable to find ORACLE password file entry for user.
ORA-09911 Incorrect user password.
ORA-09912 Malloc of name buffer(s) failed.
ORA-09913 Malloc of dummy name failed.
ORA-09914 Unable to open the ORACLE password file.
ORA-09915 Password encryption failed.
ORA-09916 Required password was not specified.
ORA-09918 Unable to get user privileges from SQL*Net
ORA-09919 Unable to set label of dedicated server
ORA-09920 Unable to get sensitivity label from connection
ORA-09921 Unable to get information label from connection
ORA-09922 Can't spawn process - background log directory not created properly
ORA-09923 Can't spawn process - user log directory not created properly
ORA-09924 Can't spawn process - core dump directory not created properly
ORA-09925 Unable to create audit trail file
ORA-09926 Unable to set effective privilege set of the server
ORA-09927 Unable to set label of server
ORA-09928 Unable to restore the label of server
ORA-09929 GLB of two labels is invalid
ORA-09930 LUB of two labels is invalid
ORA-09931 Unable to open ORACLE password file for reading
ORA-09932 Close of ORACLE password file failed.
ORA-09933 Deletion of old password file failed.
ORA-09934 Link of current password file to old failed.
ORA-09935 Unlink of current password file failed.
ORA-09936 Open of ORACLE password file for write failed.
ORA-09937 Chmod of ORACLE password file failed.
ORA-09938 Save of signal handlers failed.
ORA-09939 Restoration of signal handlers failed.
ORA-09940 ORACLE password file header is corrupt
ORA-09941 Version of orapasswd or installer is older than file.
ORA-09942 Write of ORACLE password file header failed.
ORA-09943 Allocation of memory for password list component failed.
ORA-09944 Password entry is corrupt.
ORA-09945 Unable to initialize the audit trail file
ORA-09946 File name too long for buffer
ORA-09947 Unable to allocate connection attributes structure
ORA-09948 Process information label retrieval failed.
ORA-09949 Unable to get client operating system privileges
ORA-09950 Unable to get server operating system privileges
ORA-09951 Unable to create file
ORA-09952 scgcmn: lk_open_convert unexpected return: open failed
ORA-09953 scggc: unexpected return of a lock convert
ORA-09954 scgcc: unexpected return status to callback of lock close
ORA-09955 scgcan: unexpected return status when canceling a lock
ORA-09956 scgcm: unexpected lock status condition
ORA-09957 Unable to send termination request to IMON
ORA-09958 IMON: two processes with the same ORACLE pid are active
ORA-09959 IMON: deletion of a process failed.
ORA-09960 Unable to establish signal handler for termination signal
ORA-09961 Unable to restore termination signal handler
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
ORA-09967 scumnt: unable to create or open file
ORA-09968 scumnt: unable to lock file
ORA-09969 scurls: unable to close lock file
ORA-09974 skxfidini: Error Initializing SDI Channel
ORA-09975 kxfspini: Error Initializing SDI Process
ORA-09976 skxfqdini: Error Creating Port
ORA-09977 skxfqhini: Error Connecting
ORA-09978 skxfqhdel: Error Disconnecting from another endpoint.
ORA-09979 skxfqhsnd: Error Sending a message to another endpoint
ORA-09980 skxfqdrcv: Error Receiving a message from another endpoint
ORA-09981 skxfqdreg: Error Adding a page to the SDI buffer pool
ORA-09982 skxfqddrg: Error Removing a page from the SDI buffer pool
ORA-09983 skxfidsht: Error shutting down SDI channel
ORA-09984 SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist
ORA-09985 SGA definition file could not be read
ORA-09986 wrong number of bytes read from SGA definition file
ORA-09987 unable to attach to SGA in READ-ONLY mode
ORA-09988 error while detaching SGA
ORA-09989 attempt to use invalid skgmsdef struct pointer
ORA-10560 block type 'string'
ORA-10561 block type 'string', data object# string
ORA-10562 Error occurred while applying redo to data block (file# string, block# string)
ORA-10563 Test recovery had to corrupt data block (file# string, block# string) in order to proceed
ORA-10564 tablespace string
ORA-10565 Another test recovery session is active
ORA-10566 Test recovery has used all the memory it can use
ORA-10567 Redo is inconsistent with data block (file# string, block# string)
ORA-10568 Failed to allocate recovery state object: out of SGA memory
ORA-10570 Test recovery complete
ORA-10571 Test recovery canceled
ORA-10572 Test recovery canceled due to errors
ORA-10573 Test recovery tested redo from change string to string
ORA-10574 Test recovery did not corrupt any data block
ORA-10575 Give up restoring recovered datafiles to consistent state: out of memory
ORA-10576 Give up restoring recovered datafiles to consistent state: some error occurred
ORA-10577 Can not invoke test recovery for managed standby database recovery
ORA-10578 Can not allow corruption for managed standby database recovery
ORA-10579 Can not modify control file during test recovery
ORA-10580 Can not modify datafile header during test recovery
ORA-10581 Can not modify redo log header during test recovery
ORA-10582 The control file is not a backup control file
ORA-10583 Can not recover file string renamed as missing during test recovery
ORA-10584 Can not invoke parallel recovery for test recovery
ORA-10585 Test recovery can not apply redo that may modify control file
ORA-10586 Test recovery had to corrupt 1 data block in order to proceed
ORA-10587 Invalid count for ALLOW n CORRUPTION option
ORA-10588 Can only allow 1 corruption for normal media/standby recovery
ORA-10589 Test recovery had to corrupt string data blocks in order to proceed
ORA-10614 Operation not allowed on this segment
ORA-10615 Invalid tablespace type for temporary tablespace
ORA-10616 Operation not allowed on this tablespace
ORA-10617 Cannot create rollback segment in dictionary managed tablespace
ORA-10618 Operation not allowed on this segment
ORA-10620 Operation not allowed on this segment
ORA-10621 data block does not belong to the segment
ORA-10640 Operation not permitted during SYSTEM tablespace migration
ORA-10641 Cannot find a rollback segment to bind to
ORA-10642 Found rollback segments in dictionary managed tablespaces
ORA-10643 Database should be mounted in restricted mode and Exclusive mode
ORA-10644 SYSTEM tablespace cannot be default temporary tablespace
ORA-10646 Too many recursive extensions during SYSTEM tablespace migration
ORA-10647 Tablespace other than SYSTEM,string, string not found in read only mode
ORA-10651 incorrect file number block number specified
ORA-12000 a materialized view log already exists on table 'string'
ORA-12001 cannot create log: table 'string' already has a trigger
ORA-12002 there is no materialized view log on table "string"."string"
ORA-12003 materialized view "string"."string" does not exist
ORA-12004 REFRESH FAST cannot be used for materialized view "string"."string"
ORA-12005 may not schedule automatic refresh for times in the past
ORA-12006 a materialized view with the same user.name already exists
ORA-12007 materialized view reuse parameters are inconsistent
ORA-12008 error in materialized view refresh path
ORA-12009 materialized views may not contain long columns
ORA-12010 cannot create materialized view log on table owned by SYS
ORA-12011 execution of string jobs failed
ORA-12012 error on auto execute of job string
ORA-12013 updatable materialized views must be simple enough to do fast refresh
ORA-12014 table 'string' does not contain a primary key constraint
ORA-12015 cannot create a fast refresh materialized view from a complex query
ORA-12016 materialized view does not include all primary key columns
ORA-12017 cannot alter primary key mview 'string' to a rowid mview
ORA-12018 following error encountered during code generation for "string"."string"
ORA-12019 master table is a synonym to a remote object
ORA-12020 materialized view string is not registered
ORA-12021 materialized view "string"."string" is corrupt
ORA-12022 materialized view log on "string"."string" already has rowid
ORA-12023 missing index on materialized view "string"."string"
ORA-12024 materialized view log on "string"."string" does not have primary key columns
ORA-12025 materialized view log on "string"."string" already has primary keys
ORA-12026 invalid filter column detected
ORA-12027 duplicate filter column
ORA-12028 materialized view type is not supported by master site string
ORA-12029 LOB columns may not be used as filter columns
ORA-12030 cannot create a fast refresh materialized view
ORA-12031 cannot use primary key columns from materialized view log on "string"."string"
ORA-12032 cannot use rowid column from materialized view log on "string"."string"
ORA-12033 cannot use filter columns from materialized view log on "string"."string"
ORA-12034 materialized view log on "string"."string" younger than last refresh
ORA-12035 could not use materialized view log on "string"."string"
ORA-12036 updatable materialized view log is not empty, refresh materialized view
ORA-12037 unknown export format
ORA-12039 unable to use local rollback segment "string"
ORA-12040 master rollback segment option not support by master site string
ORA-12041 cannot record ROWIDs for index-organized table "string"."string"
ORA-12042 cannot alter job_queue_processes in single process mode
ORA-12043 invalid CREATE MATERIALIZED VIEW option
ORA-12044 invalid CREATE MATERIALIZED VIEW LOG option
ORA-12045 invalid ALTER MATERIALIZED VIEW LOG option
ORA-12051 ON COMMIT attribute is incompatible with other options
ORA-12052 cannot fast refresh materialized view string.string
ORA-12053 this is not a valid nested materialized view
ORA-12054 cannot set the ON COMMIT refresh attribute for the materialized view
ORA-12055 materialized view definition contains cyclic dependencies with existing materialized views
ORA-12056 invalid REFRESH method
ORA-12057 materialized view "string"."string" is INVALID and must complete refresh
ORA-12058 materialized view cannot use prebuilt table
ORA-12059 prebuilt table "string"."string" does not exist
ORA-12060 shape of prebuilt table does not match definition query
ORA-12061 invalid ALTER MATERIALIZED VIEW option
ORA-12062 transaction string received out of sequence from site string
ORA-12063 unable to apply transaction from site string
ORA-12064 invalid refresh sequence number: string
ORA-12065 unknown refresh group identifier string
ORA-12066 invalid CREATE MATERIALIZED VIEW command
ORA-12067 empty refresh groups are not allowed
ORA-12068 updatable mview log for mview "string"."string" does not exist
ORA-12069 invalid object for offline instantiation
ORA-12070 cannot offline instantiate materialized view "string"."string"
ORA-12071 definition query of "string"."string" is invalid for offline instantiation
ORA-12072 updatable materialized view log data for 'string'.'string' cannot be created
ORA-12073 request cannot be processed
ORA-12074 invalid memory address
ORA-12075 invalid object or field
ORA-12076 invalid threshold value
ORA-12077 temporary updatable materialized view log does not exist
ORA-12078 fast refresh of refresh group ID string failed
ORA-12079 materialized view options require COMPATIBLE parameter to be string or greater
ORA-12081 update operation not allowed on table string.string
ORA-12082 'string'.'string' cannot be index organized
ORA-12083 must use DROP MATERIALIZED VIEW to drop string.string
ORA-12084 must use ALTER MATERIALIZED VIEW to alter string.string
ORA-12085 materialized view log on "string"."string" already has object id
ORA-12086 table "string"."string" is not an object table
ORA-12087 online redefinition not allowed on tables owned by "string"
ORA-12088 cannot online redefine table "string"."string" with unsupported datatype
ORA-12089 cannot online redefine table "string"."string" with no primary key
ORA-12090 cannot online redefine table "string"."string"
ORA-12091 cannot online redefine table "string"."string" with materialized views
ORA-12092 cannot online redefine replicated table "string"."string"
ORA-12093 invalid interim table "string"."string"
ORA-12094 error during online redefinition
ORA-12096 error in materialized view log on "string"."string"
ORA-12097 changes in the master tables during refresh, try refresh again
ORA-12150 through ORA-12299
See Chapter 30, "Oracle Net Messages (TNS)" (the messages are listed with the prefix TNS in that chapter even though they are displayed with the prefix ORA).
| Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
