Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
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, or UNDER) on a type.
Action: GRANT or REVOKE only the EXECUTE, DEBUG, or UNDER privilege 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:
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 SYSTEM tablespace 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_POLICY to AUTO while PGA_AGGREGATE_TARGET is not specified.
Action: Before setting WORKAREA_SIZE_POLICY, set PGA_AGGREGATE_TARGET to a value representing the total private memory available to the instance. This total is generally the total physical memory available in the system minus what is needed for the SGA minus what is needed for the operating system (for example, such as 500 MB).
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:
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.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
