dkey

Oracle Database Server Messages(三) . .

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01

Home

Book List

Contents

Index

Master Index

Feedback

9
ORA-12300 to ORA-12399

ORA-12315 database link type is invalid for the ALTER DATABASE statement: Cause: The database link name you specified on the ALTER DATABASE statement is not an ROM: link. You must specify an ROM: link when using the ALTER DATABASE statement to mount or open a secondary database.; Action: Re-issue the ALTER DATABASE statement using a valid ROM: link to the database you want to mount or open. If a valid ROM: link does not exist, create one using the CREATE DATABASE LINK statement. See your documentation for Oracle security-related products for more information about creating database links using the ROM: link type.
ORA-12316 syntax error in database link's connect string: Cause: The connect string in the CREATE DATABASE LINK statement has a syntactical error.; Action: Drop the database link and re-create it using valid syntax. See the Oracle9i SQL Reference for more information about the connect string portion of the CREATE DATABASE LINK statement.
ORA-12317 logon to database (link name string) denied: Cause: There are several possible causes for this error. First, you can get this error if your username (and password, if you are using database instead of operating system authentication) in the secondary database are not identical to your username (and password) in the primary database. Second, you can get this error if your username in the secondary database is invalid (has not been created). Third, you can get this error if the username/password combination specified in the connect string of the database link definition is invalid (either not created or has an invalid password).; Action: In the first case, ensure that the secondary database contains a username (and password, if you are using database authentication) identical to the one you are using in the primary database. In the second case, ensure that your username in the secondary database has been created. In the third case, ensure that the username specified in the connect string has been created in the secondary database.
ORA-12318 database (link name string) is already mounted: Cause: You are attempting to mount a secondary database that has already been mounted by your instance.; Action: The database is already mounted, so you need not take additional action to mount it. To establish access, use the ALTER DATABASE linkname OPEN statement to open the database.
ORA-12319 database (link name string) is already open: Cause: You are attempting to open a secondary database that is already open.; Action: The database is open and you need not take additional action to establish access.
ORA-12321 database (link name string) is not open and AUTO_MOUNTING=FALSE: Cause: The secondary database that your instance is attempting to mount is not open and automatic mounting has not been enabled.; Action: Manually mount and open the secondary database using ALTER DATABASE linkname with the OPEN and MOUNT options. Alternately, to allow your instance to automatically mount and open secondary databases, set the AUTO_MOUNTING parameter in the parameter file to TRUE.
ORA-12322 unable to mount database (link name string): Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.; Action: Follow the steps outlined in the accompanying error messages to resolve the problem.
ORA-12323 unable to open database (link name string): Cause: This message should be accompanied by additional error messages that indicate the cause of the problem.; Action: Follow the steps outlined in the accompanying error messages to resolve the problem.
ORA-12324 cannot use the ROM: link type on a private database link: Cause: You can only specify the ROM: link type on a public, not a private, database link.; Action: Determine if there is an existing public database link to the secondary database. If not, and if you wish to establish public access to the secondary database, create a public database link to the secondary database using the CREATE DATABASE LINK command.
ORA-12326 database string is closing immediately; no operations are permitted: Cause: The database you attempted to access is closing, so your operation has been terminated.; Action: Wait until the database has been reopened, or contact the database administrator.
ORA-12329 database string is closed; no operations are permitted: Cause: The database you attempted to access is closed, so your operation has been terminated.; Action: Wait until the database is reopened, or contact the database administrator.
ORA-12333 database (link name string) is not mounted: Cause: An attempt was made to open a database that has not been mounted.; Action: Mount the database with the ALTER DATABASE linkname MOUNT statement, then re-attempt to open the database.
ORA-12334 database (link name string) is still open: Cause: An attempt was made to dismount a database that is still open.; Action: Close the database with the ALTER DATABASE linkname CLOSE statement, then re-attempt to dismount the database.
ORA-12335 database (link name string) is not open: Cause: An attempt was made to close a database that is not open.; Action: The database is closed; you can proceed with dismounting it.
ORA-12336 cannot login to database (link name string): Cause: An attempt was made to login while another user is mounting or dismounting the same database.; Action: Check to see if the database is in the middle of being mounted or opened and try your login again once the database is accessible.
ORA-12341 maximum number of open mounts exceeded: Cause: The number specified on the OPEN_MOUNTS parameter in the parameter file exceeds the maximum allowed (255).; Action: Change the value of this parameter so that it reflects the actual number of possible open mounts to secondary databases. This must be less than 255.
ORA-12342 open mounts exceeds limit set on the OPEN_MOUNTS parameter: Cause: The number of currently open mounts exceeds the value you specified on the OPEN_MOUNTS parameter.; Action: Increase the value of the OPEN_MOUNTS parameter so that it accommodates the maximum possible number of open mounts to secondary databases.
ORA-12345 user string lacks CREATE SESSION privilege in database link (linkname string): Cause: There are several possible causes for this message: First, you will get this message if your username in the second database specified was not granted the CREATE SESSION system privilege. Second, you will get this message if the username specified in the connect string of the database link definition was not granted the CREATE SESSION system privilege.; Action: The action you take depends upon the cause of the message: In the first case, ensure that your username in the secondary database was granted the CREATE SESSION system privilege. In the second case, ensure the username specified in the connect string of the database link definition was granted the CREATE SESSION system privilege in the secondary database.
ORA-12350 database link being dropped is still mounted: Cause: An attempt was made to drop a ROM: database link that was still mounted and/or opened.; Action: Close and dismount the database and then re-issue the drop statement.
ORA-12351 cannot create view using a remote object which has a remote object reference: Cause: An attempt was made to create a view which references a remote object which, in turn, references an object on another database. Since the view that would have been created references a remote object, that object cannot reference an object on another database.; Action: Choose a different object to reference in your view or change the remote object so that it does not reference another database.
ORA-12352 object string.string@string is invalid: Cause: An attempt was made to reference (compile against) an object of a secondary database but the object is invalid and the system cannot validate or recompile it because it is in a secondary database.; Action: Manually recompile the invalid object in the secondary database.
ORA-12353 secondary stored object cannot reference remote object: Cause: An attempt was made to either select from a remote view or execute a remote procedure which references an object on another database. Since the remote view or procedure is on a secondary database, an additional reference to another database cannot be done.; Action: Choose a different object to reference or change the remote view or procedure so that it does not reference another database.
ORA-12354 secondary object being dropped: Cause: An attempt was made to access an object (for example, a table or view) on a secondary database that was in the process of being dropped.; Action: Repeat the operation. If you receive this message again, try to access the object from the secondary database. If you receive an internal error or a trace file, contact Oracle Support Services.

Home

Book List

Contents

Index

Master Index

Feedback

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01

Home

Book List

Contents

Index

Master Index

Feedback

10
ORA-12400 to ORA-12699

ORA-12400 invalid argument to facility error handling: Cause: An argument to a facility error handling function exceeded a maximum limit or referred to an invalid product/facility.; Action: Specify a valid facility error handling parameter value.
ORA-12401 invalid label string: string: Cause: The policy could not convert the label string to a valid internal label.; Action: Correct the syntax of the label string.
ORA-12402 invalid format string: string: Cause: The format string is not supported by the policy.; Action: Correct the syntax of the format string.
ORA-12403 invalid internal label: Cause: An internal label could not be converted to a valid label for the policy.; Action: Analyze any additional messages on the error stack and consult the policy documentation.
ORA-12404 invalid privilege string: string: Cause: The policy could not interpret the privilege string.; Action: Specify a privilege string that is supported by the policy.
ORA-12405 invalid label list: Cause: The policy determined that the label list was invalid for its intended use.; Action: Check the policy constraints on the specific list of labels.
ORA-12406 unauthorized SQL statement for policy string: Cause: The policy did not authorize the database session to perform the requested SQL statement.; Action: Grant the user or program unit the necessary policy privilege or additional authorizations.
ORA-12407 unauthorized operation for policy string: Cause: The policy did not authorize the database session to perform the requested operation.; Action: Grant the user or program unit the necessary policy privilege or additional authorizations.
ORA-12408 unsupported operation: string: Cause: The specified policy does not support the requested operation.; Action: Consult the policy documentation to determine the supported access mediation operations.
ORA-12409 policy startup failure for string policy: Cause: The policy encountered an error during startup processing; access to the data protected by the policy is prohibited.; Action: Check the alert log for additional information, correct the policy error, and restart the instance.
ORA-12410 internal policy error for policy: string Error: string: Cause: The policy enforcement encountered an internal error.; Action: Consult the policy documentation for details.
ORA-12411 invalid label value: Cause: The specified label value does not exist.; Action: Check the data dictionary views for the policy to identify valid labels.
ORA-12412 policy package string is not installed: Cause: The policy package does not exist in the database.; Action: Check that the policy package name is correct or install the required policy package.
ORA-12413 labels do not belong to the same policy: Cause: The labels being compared belong to different policies.; Action: Only compare labels that belong to the same policy.
ORA-12414 internal LBAC error: string Error: string: Cause: An internal label policy framework error occurred.; Action: Contact Oracle Support Services.
ORA-12415 A column of another datatype exists on the specified table: Cause: The datatype of the column present in the table is different from the datatype set for the policy column.; Action: Drop the column on the table or change the datatype for the policy column.
ORA-12416 policy string not found: Cause: The specified policy does not exist in the database.; Action: Enter the correct policy name or create the policy.
ORA-12417 database object "string" not found: Cause: The specified object was not in the database.; Action: Enter the correct name for the database object.
ORA-12418 user string not found: Cause: The specified user does not exist in the database.; Action: Correct the user name or create the user.
ORA-12419 null binary label value: Cause: A null value was provided for a binary label operation.; Action: Provide a valid binary label for the operation.
ORA-12420 required procedures and functions not in policy package "string": Cause: The policy package did not contain all of the procedures and functions necessary to enforce the policy.; Action: Consult the label framework documentation for a list of required procedures and functions for a policy package.
ORA-12421 different size binary labels: Cause: The label sizes for the binary label operation were not equal.; Action: Provide binary labels with the same lengths for the operation.
ORA-12422 max policies exceeded: Cause: You tried to create a new policy, but the maximum number of policies for the instance had already been created.; Action: Increase the size of the MAX_LABEL_POLICIES initialization parameter and restart the server.
ORA-12423 invalid position specified: Cause: The position specified for a binary label operation was invalid.; Action: Provide a position that is within the label size limits.
ORA-12424 length exceeds binary label size: Cause: The length specified for a binary label operation exceeded the size of the binary label.; Action: Provide a bit or byte length that is within the label size limits.
ORA-12425 cannot apply policies or set authorizations for system schemas: Cause: You tried to either apply a policy to the SYS, SYSTEM, or LBACSYS schema or to set user labels/privileges for the SYS, SYSTEM, or LBACSYS user.; Action: Apply policies and set authorizations only for non-system users.
ORA-12426 invalid audit option: Cause: The option specified was not a valid audit option for the specified policy.; Action: Enter a correct audit option.
ORA-12427 invalid input value for string parameter: Cause: An input parameter was specified incorrectly.; Action: Correct the parameter value.
ORA-12429 label list range exceeded: Cause: The specified index value was not between 1 and 6.; Action: Correct the index value for the label list operation.
ORA-12430 invalid privilege number: Cause: The specified privilege number was not between 1 and 32.; Action: Correct the privilege number.
ORA-12431 invalid audit action: Cause: The specified audit action was not a valid audit action.; Action: Correct the audit action number.
ORA-12432 LBAC error: string: Cause: LBAC enforcement resulted in an error.; Action: Correct the problem identified in the error message.
ORA-12433 create trigger failed, policy not applied: Cause: The policy could not be applied due to errors during the creation of a DML trigger.; Action: Correct the SQL syntax of the label function specification.
ORA-12434 invalid audit type: string: Cause: The audit type must be BY ACCESS or BY SESSION.; Action: Correct the audit type value.
ORA-12435 invalid audit success: string: Cause: The audit success parameter must be SUCCESSFUL or NOT SUCCESSFUL.; Action: Correct the audit success value.
ORA-12436 no policy options specified: Cause: A NULL option string was specified, but no default schema or policy option string was found.; Action: Enter a valid option string, or alter the schema or policy to have a valid default option string.
ORA-12437 invalid policy option: string: Cause: A value that was not a valid policy option was entered.; Action: Correct the policy option value.
ORA-12438 repeated policy option: string: Cause: A policy option was entered more than once in the option string.; Action: Remove the duplicate policy option value.
ORA-12439 invalid combination of policy options: Cause: A set of contradictory policy options was entered.; Action: Provide a set of compatible policy options.
ORA-12440 insufficient authorization for the SYSDBA package: Cause: The use of the SYSDBA package requires the LBAC_DBA role.; Action: Grant the LBAC_DBA role to the database user.
ORA-12441 policy string already exists: Cause: You tried to create a policy with the same name as an existing one.; Action: Use a different name or drop the existing policy.
ORA-12442 policy column "string" already used by an existing policy: Cause: You tried to create a policy with the same policy column name as an existing policy.; Action: Use a different name for the policy column or drop the existing policy.
ORA-12443 policy not applied to some tables in schema: Cause: You applied a policy to a schema, and some of the tables in the schema already had the policy applied.; Action: No action necessary; the policy was applied to the remaining tables.
ORA-12444 policy already applied to table: Cause: You tried to apply a policy to a table that was already protected by the policy.; Action: To change the policy options, predicate, or label function, remove the policy from the table and re-apply it.
ORA-12445 cannot change HIDDEN property of column: Cause: You tried to specify a different HIDE option for a table with an existing policy column.; Action: Drop the column from the table and re-apply the policy with the new HIDE option.
ORA-12446 Insufficient authorization for administration of policy string: Cause: You tried to perform an administrative function for a policy, but you have not been granted the policy_DBA role.; Action: Grant the user the policy_DBA role for the specified policy.
ORA-12447 policy role already exists for policy string: Cause: The role named policy_DBA already exists.; Action: Correct the policy name or delete the existing policy.
ORA-12448 policy string not applied to schema string: Cause: You tried to alter a schema policy that was not applied.; Action: Correct the policy name or schema name.
ORA-12449 Labels specified for user must be of type USER: Cause: You tried to set labels for a user, but the labels in the list were not all designated as USER labels.; Action: Alter the labels to be USER labels.
ORA-12450 LOB datatype disabled in LBAC initialization file: Cause: You tried to specify a LOB datatype for a column or attribute, but the use of the LOB datatype has been disabled.; Action: Change the LBAC initialization file to allow the creation of LOB columns and attributes.
ORA-12451 label not designated as USER or DATA: Cause: A label is either a DATA label, a USER label, or both DATA and USER.; Action: Enter TRUE for at least DATA or USER.
ORA-12452 label tag string already exists: Cause: The label tag value you entered is already in use for another label.; Action: Enter a different value for the label tag.
ORA-12453 label string already exists: Cause: The label value you entered already exists.; Action: No action necessary; alter the label to change its tag or type.
ORA-12454 label string does not exist for policy string: Cause: The label tag or value you entered did not identify a label for the policy.; Action: Enter a label value or tag that is in use by the policy.
ORA-12461 undefined level string for policy string: Cause: The specified level is not defined for the policy.; Action: Correct the level identifier value.
ORA-12462 undefined compartment string for policy string: Cause: The specified compartment is not defined for the policy.; Action: Correct the compartment identifier value.
ORA-12463 undefined group string for policy string: Cause: The specified group is not defined for the policy.; Action: Correct the group identifier value.
ORA-12464 invalid characters in label component string: Cause: Label components can contain only alphanumeric characters, blanks, and underscores.; Action: Correct syntax of the label component.
ORA-12465 not authorized for read or write on specified groups or compartments: Cause: You included groups or compartments that are not in the user's list of groups and compartments authorized for read or write access.; Action: Include read access when authorizing groups or compartments for write access.
ORA-12466 default level is greater than the user's maximum: Cause: The default level cannot be greater than the user's maximum.; Action: Enter an authorized level.
ORA-12467 minimum label can contain a level only: Cause: You included compartments or groups in the minimum label.; Action: Enter only an authorized minimum level as the label.
ORA-12468 max write level does not equal max read level: Cause: The level in the max write label must equal the level in the max read label.; Action: Enter max read and max write labels with the same level component.
ORA-12469 no user levels found for user string and policy string: Cause: No levels have been specified for the user.; Action: Enter the maximum and minimum labels for the user.
ORA-12470 NULL or invalid user label: string: Cause: The label entered is NULL or not within the user's authorizations.; Action: Enter the authorized labels for the user.
ORA-12471 Specified compartment or group is not authorized for user: Cause: The specified compartment or group is not in user's authorizations or the user does not have read on compartment or group specified for write.; Action: Enter an authorized compartment or group.
ORA-12476 least upper bound resulted in an invalid OS label: Cause: You tried to do an operation that generated a least upper bound (LUB) label which is not a valid label on your operating system.; Action: Consult your OS label management documentation for information on invalid label generation.
ORA-12477 greatest lower bound resulted in an invalid OS label: Cause: You tried to do an operation that generated a greatest lower bound (GLB) label which is not a valid label on your operating system.; Action: Consult your OS label management documentation for information on invalid label generation.
ORA-12479 file label string must equal DBHIGH string: Cause: A database file had an OS label that did not match DBHIGH. Either DBHIGH was altered or the OS file was relabeled.; Action: Relabel the file so that its label matches DBHIGH, or alter DBHIGH so that it matches the label on the file.
ORA-12480 specified clearance labels not within the effective clearance: Cause: You specified a clearance range that was not within your authorized clearance; you can only specify clearance ranges that are within your clearance.; Action: Specify clearance labels that are within your own clearance range.
ORA-12481 effective label not within program unit clearance range: Cause: The effective label when the program unit was invoked was not within the range authorized for the program unit.; Action: Modify the program unit clearance range or invoke the program unit from a session with an authorized effective clearance.
ORA-12482 internal MLS error: string Error: string: Cause: An internal MLS policy error occurred.; Action: Contact Oracle Support Services.
ORA-12483 label not in OS system accreditation range: Cause: The specified label is above the OS maximum label or below the OS minimum label.; Action: Use a label that is within the accreditation range for the host OS.
ORA-12484 invalid OS label: Cause: The specified label does not exist in the OS host's label definition file.; Action: Use the OS label management tools to define the label.
ORA-12485 new effective label not within effective clearance: Cause: You attempted to enter a value for an effective label that did not dominate the effective min label or was not dominated by the effective max label.; Action: Enter a value between the min and the max labels.
ORA-12486 effective max labels and min labels cannot be changed: Cause: You attempted to enter a value for an effective min label or effective max label, but these labels cannot be changed.; Action: Enter NULL values for the effective minimum and maximum labels.
ORA-12487 clearance labels not between DBHIGH and DBLOW: Cause: You attempted to enter a value for a clearance label that was not dominated by DBHIGH or did not dominate DBLOW.; Action: Enter clearance label values between DBHIGH and DBLOW.
ORA-12488 maximum label does not dominate minimum label: Cause: You attempted to enter a value for a clearance label that did not preserve the dominance relationship between the minimum and maximum labels.; Action: Enter label values that preserves the dominance relationship between the minimum and maximum.
ORA-12489 default label not within clearance range: Cause: You attempted to enter a value for a default label that did not dominate the minimum clearance or was not dominated by the maximum clearance.; Action: Enter a default label value within the clearance range.
ORA-12490 DBHIGH cannot be lowered: Cause: You attempted to enter a value for DBHIGH that did not dominate the existing value of DBHIGH.; Action: Enter a value for DBHIGH that dominates the old value.
ORA-12491 DBHIGH value does not dominate DBLOW: Cause: You attempted to enter a value for DBHIGH that did not dominate DBLOW.; Action: Enter a value for DBHIGH that dominates DBLOW.
ORA-12492 DBLOW cannot be changed: Cause: You attempted to change the value of DBLOW after it had been set to any initial value. DBLOW can only be set once after initial database creation.; Action: To change DBLOW, you have to create a new database, set DBLOW to the new value, and import your data into the new database.
ORA-12493 invalid MLS binary label: Cause: The MLS binary label contained an invalid value, was not the correct size, or contained a level, category, or release category that was not enabled.; Action: Check the DBA_MLS_LABELS view for the valid MLS labels.
ORA-12494 cannot insert or delete a level, category, or release category: Cause: You attempted to insert or delete a level, category, or release category definition.; Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used.
ORA-12495 cannot disable an enabled level, category, or release category: Cause: You attempted to disable a level, category, or release category that had previously been enabled. An enabled label definition may exist in some database label, so it cannot be disabled.; Action: If the label definition is no longer valid, change its name to one that identifies it as invalid. When any labels are converted to character strings, the new label definition will be used.
ORA-12496 cannot change existing level, category, or release numbers: Cause: You attempted to change the number assigned to level, category or releasability category.; Action: Change the character string representations, not the numbers.
ORA-12497 maximum combined categories exceeds string: Cause: The maximum number of descriptive categories plus release categories supported by the MLS policy was exceeded.; Action: Enter numbers that do not add up to more than the maximum.
ORA-12500 through ORA-12699

See Chapter 30, "Oracle Net Messages (TNS)" (the messages are listed with the prefix TNS in that chapter even though they are displayed with the prefix ORA).

Home

Book List

Contents

Index

Master Index

Feedback

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01

Home

Book List

Contents

Index

Master Index

Feedback

11
ORA-12700 to ORA-19399

ORA-12700 invalid NLS parameter value (string)

Cause: An invalid NLS initialization parameter was specified.

Action: Check the syntax and spelling of the parameter. Enter the correct parameter into the initialization parameter file.

ORA-12701 CREATE DATABASE character set is not known

Cause: The character set specified in the CREATE DATABASE command does not exist on the system.

Action: Refer to your Oracle operating system-specific documentation for more information about character sets on the system. Use a valid character set in the CREATE DATABASE command.

ORA-12702 invalid NLS parameter string used in SQL function

Cause: An invalid parameter or value was entered in the NLS parameter string in a SQL function.

Action: Check the syntax of the function and the parameters. Enter the command again using the correct syntax and valid values.

ORA-12703 this character set conversion is not supported

Cause: An attempt was made to use the CONVERT function to convert between two character sets, and the requested conversion is not possible due to unavailability of one or both character sets.

Action: Use character sets available on the system in the CONVERT function.

ORA-12704 character set mismatch

Cause: One of the following:

The string operands (other than an NLSPARAMS argument) to an operator or built-in function do not have the same character set.
An NLSPARAMS operand is not in the database character set.
String data with character set other than the database character set is passed to a built-in function not expecting it.
The second argument to CHR() or CSCONVERT() is not CHAR_CS or NCHAR_CS.
A string expression in the VALUES clause of an INSERT statement, or the SET clause of an UPDATE statement, does not have the same character set as the column into which the value would be inserted.
A value provided in a DEFAULT clause when creating a table does not have the same character set as declared for the column.
An argument to a PL/SQL function does not conform to the character set requirements of the corresponding parameter.

Action: Strings declared with NCHAR or NCHAR VARYING do not interoperate with strings declared with CHAR or VARCHAR2. Use TRANSLATE() function to explicitly convert one to the other.

ORA-12705 invalid or unknown NLS parameter value specified

Cause: There are two possible causes: Either an attempt was made to issue an ALTER SESSION statement with an invalid NLS parameter or value; or the NLS_LANG environment variable contains an invalid language, territory, or character set.

Action: Check the syntax of the ALTER SESSION statement and the NLS parameter, correct the syntax and retry the statement, or specify correct values in the NLS_LANG environment variable. For more information about the syntax of the ALTER SESSION statement, see the Oracle9i SQL Reference.

ORA-12706 this CREATE DATABASE character set is not allowed

Cause: An attempt was made to create a database on an ASCII-based machine using an EBCDIC-based character set or vice versa. This is not permitted.

Action: Create the database using either ASCII-based or EBCDIC-based character sets, depending on what is supported by the hardware. Refer to your Oracle operating system-specific documentation for more information about the type of character set supported.

ORA-12707 error while getting create database NLS parameter string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-12708 error while loading create database NLS parameter string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-12709 error while loading create database character set

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-12710 CREATE CONTROLFILE character set is not known

Cause: The character set specified when creating the control file is unknown.

Action: Specify a known character set.

ORA-12711 this CREATE CONTROLFILE character set is not allowed

Cause: It is not allowed to create a control file on a native ASCII-based machine using an EBCDIC-based character set, and vice versa.

Action: Create the correct control file for machine and character set.

ORA-12712 new character set must be a superset of old character set

Cause: When you ALTER DATABASE ... CHARACTER SET, the new character set must be a superset of the old character set. For example, WE8ISO8859P1 is not a superset of the WE8DEC.

Action: Specify a superset character set.

ORA-12713 Character data loss in NCHAR/CHAR conversion

Cause: When character set conversion happens between CHAR and NCHAR either implicitly or explicitly, some characters are lost due to no mapping characters in the destination character set.

Action: Make sure all the characters can be mapped to destination character set or set NLS_NCHAR_CONV_EXCP to false.

ORA-12714 invalid national character set specified

Cause: Only UTF8 and AL16UTF16 are allowed to be used as the national character set.

Action: Ensure that the specified national character set is valid.

ORA-12715 invalid character set specified

Cause: The character set specified is not allowed for this operation or is invalid.

Action: Ensure that the specified character set is valid.

ORA-12716 Cannot ALTER DATABASE CHARACTER SET when CLOB data exists

Cause: CLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.

Action: Remove CLOB data as listed in the alert file. CLOB data can be migrated by methods such as export/import.

ORA-12717 Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists

Cause: NCLOB data changes representation to Unicode when converting to a multibyte character set and must be migrated.

Action: Remove NCLOB data as listed in the alert file. NCLOB data can be migrated by methods such as export/import.

ORA-12718 operation requires connection as SYS

Cause: This command can only be run when connecting as user SYS.

Action: Connect as user SYS to run this command.

ORA-12719 operation requires database is in RESTRICTED mode

Cause: This command can only be run when the database is in RESTRICTED mode.

Action: Ensure that the system is in RESTRICTED mode.

ORA-12720 operation requires database is in EXCLUSIVE mode

Cause: This command can only be run when the database is in EXCLUSIVE mode.

Action: Ensure that the system is in EXCLUSIVE mode.

ORA-12721 operation cannot execute when other sessions are active

Cause: This command can only be run when there are no other sessions active.

Action: Ensure there are no other connections to the database.

ORA-12800 system appears too busy for parallel query execution

Cause: Load on the system is too high to perform parallel queries.

Action: Re-execute serially or wait until the system load is reduced.

ORA-12801 error signaled in parallel query server string

Cause: A parallel query server reached an exception condition.

Action: Check the following error message for the cause.

ORA-12802 parallel query server lost contact with coordinator

Cause: A parallel query server lost contact with the foreground (coordinator) process/thread.

Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.

ORA-12803 parallel query server lost contact with another server

Cause: A parallel query server lost contact with another server.

Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.

ORA-12804 parallel query server appears to have died

Cause: Cannot find process information for a parallel query server thread.

Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services.

ORA-12805 parallel query server died unexpectedly

Cause: A parallel query server died unexpectedly, PMON cleaning up the process.

Action: Check your system for anomalies and reissue the statement. If this error persists, then contact Oracle Support Services. See trace file for more details.

ORA-12806 could not get background process to hold enqueue

Cause: This is an internal error.

Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.

ORA-12807 process queue could not receive parallel query message

Cause: This is an internal error.

Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.

ORA-12808 cannot set string_INSTANCES greater than number of instances string

Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement to a value larger than the number of available instances.

Action: See the accompanying message for the current allowable maximum value, or set SCAN_INSTANCES / CACHE_INSTANCES to ALL.

ORA-12809 cannot set string_INSTANCES when mounted in exclusive mode

Cause: An attempt was made to set SCAN_INSTANCES or CACHE_INSTANCES using the ALTER SYSTEM statement while the database was mounted in exclusive mode.

Action: SCAN_INSTANCES / CACHE_INSTANCES may not be set unless running Oracle9i Real Application Clusters mounted in CLUSTER_DATABASE mode.

ORA-12810 PARALLEL_MAX_SERVERS must be less than or equal to string

Cause: An attempt was made to set the PARALLEL_MAX_SERVERS parameter to a value higher than the maximum allowed by the system.

Action: Set PARALLEL_MAX_SERVERS to a value less than or equal to the maximum specified in the accompanying message and retry.

ORA-12811 PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string

Cause: An attempt was made to set the PARALLEL_MIN_SERVERS parameter to a value higher than PARALLEL_MAX_SERVERS.

Action: Set PARALLEL_MIN_SERVERS to a value less than or equal to PARALLEL_MAX_SERVERS (indicated in the accompanying message) and retry.

ORA-12812 only one PARALLEL or NOPARALLEL clause may be specified

Cause: PARALLEL was specified more than once, NOPARALLEL was specified more than once, or both PARALLEL and NOPARALLEL were specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement, or in a RECOVER command.

Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.

ORA-12813 value for PARALLEL or DEGREE must be greater than 0

Cause: PARALLEL 0 or DEGREE 0 was specified in a CREATE TABLE, CLUSTER, or INDEX or in an ALTER TABLE or CLUSTER statement.

Action: Specify a degree of parallelism greater than 0 or specify default parallelism using PARALLEL with no degree or using DEGREE DEFAULT within a PARALLEL clause.

ORA-12814 only one CACHE or NOCACHE clause may be specified

Cause: CACHE was specified more than once, NOCACHE was specified more than once, or both CACHE and NOCACHE were specified in a CREATE TABLE or CLUSTER, or in an ALTER TABLE or CLUSTER statement.

Action: Remove all but one of the CACHE or NOCACHE clauses and reissue the statement.

ORA-12815 value for INSTANCES must be greater than 0

Cause: PARALLEL parameter specifying number of instances must be a positive integer or DEFAULT.

Action: specify a positive integer or DEFAULT for INSTANCES if parallelism across instances is desired.

ORA-12816 parallel create index fastpath operation

Cause: The parallel create index fastpath operation event has been set.

Action: Set this event only under the supervision Oracle development.

ORA-12817 parallel query option must be enabled

Cause: A parallel query option feature has been invoked but this option has not been enabled.

Action: Enable the parallel query option.

ORA-12818 invalid option in PARALLEL clause

Cause: An unrecognized option was used within a PARALLEL clause.

Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.

ORA-12819 missing options in PARALLEL clause

Cause: PARALLEL clause cannot be empty.

Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.

ORA-12820 invalid value for DEGREE

Cause: Invalid value for DEGREE was specified within a PARALLEL clause.

Action: Specify a positive integer or DEFAULT for the DEGREE option within a PARALLEL clause.

ORA-12821 invalid value for INSTANCES

Cause: An invalid value for INSTANCES was specified within a PARALLEL clause.

Action: Specify a positive integer or DEFAULT for the INSTANCES option within a PARALLEL clause.

ORA-12822 duplicate option in PARALLEL clause

Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.

Action: Specify each desired PARALLEL clause option only once.

ORA-12823 default degree of parallelism may not be specified here

Cause: The PARALLEL keyword was used alone or DEGREE DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER statement.

Action: Respecify with an explicit degree of parallelism.

ORA-12824 INSTANCES DEFAULT may not be specified here

Cause: INSTANCES DEFAULT was specified in the PARALLEL clause of an ALTER DATABASE RECOVER command.

Action: Respecify with an explicit value for INSTANCES or omit the INSTANCES option if single instance recovery is desired.

ORA-12825 explicit degree of parallelism must be specified here

Cause: The DEGREE option was omitted from an ALTER DATABASE RECOVER command.

Action: Respecify with an explicit degree of parallelism.

ORA-12826 hung parallel query server was killed

Cause: The parallel query server was hung and subsequently killed.

Action: Re-execute the query and report suspicious events in the trace file to Oracle Support Services if the error persists.

ORA-12827 insufficient parallel query slaves available

Cause: PARALLEL_MIN_PERCENT parameter was specified and fewer than minimum slaves were acquired.

Action: Either re-execute query with lower PARALLEL_MIN_PERCENT or wait until some running queries are completed, thus freeing up slaves.

ORA-12828 Can't start parallel transaction at a remote site

Cause: PDML transaction cannot be started because we are not in the coordinator site of the distributed transaction.

Action: Do not use PDML at remote sites.

ORA-12829 Deadlock - itls occupied by siblings at block string of file string

Cause: A parallel statement failed because all ITLS in the current block are occupied by siblings of the same transaction.

Action: Increase the value of MAXTRANS of the block or reduce the degree of parallelism for the statement. Re-execute the statement. Report suspicious events in the trace file to Oracle Support Services if the error persists.

ORA-12830 Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE

Cause: After executing a parallel INSERT/UPDATE/DELETE statement, a command other than COMMIT or ROLLBACK was issued.

Action: Execute COMMIT or ROLLBACK before issuing another SQL command.

ORA-12831 Must COMMIT or ROLLBACK after executing INSERT with APPEND hint

Cause: After executing an INSERT statement with an APPEND hint, a command other than COMMIT or ROLLBACK was issued.

Action: Execute COMMIT or ROLLBACK before issuing another SQL command.

ORA-12832 Could not allocate slaves on all specified instances

Cause: After executing a query on a global v$ fixed view, one or more instances failed to allocate a slave to process query.

Action: To allow results to be returned by successfully allocated slaves, execute ALTER SESSION SET ALLOW_PARTIAL_SN_RESULTS=TRUE statement, or check parameters of instances.

ORA-12833 Coordinator's instance not a member of parallel_instance_group

Cause: The coordinator's instance must be a member of the PARALLEL_INSTANCE_GROUP in which this operation will be run.

Action: Either add the coordinator's instance to the current PARALLEL_INSTANCE_GROUP or change PARALLEL_INSTANCE_GROUP.

ORA-12834 Instance group name, 'string', too long, must be less than string characters

Cause: The instance group name is too long.

Action: Either shorten the name or get rid of the instance group.

ORA-12835 No instances are active in the GLOBAL_VIEW_ADMIN_GROUP

Cause: There must be at least one instance in the GLOBAL_VIEW_ADMIN_GROUP in order to execute a query on global views.

Action: Change the value of GLOBAL_VIEW_ADMIN_GROUP.

ORA-12838 cannot read/modify an object after modifying it in parallel

Cause: Within the same transaction, an attempt was made to add read or modification statements on a table after it had been modified in parallel or with direct load. This is not permitted.

Action: Rewrite the transaction, or break it up into two transactions: one containing the initial modification and the second containing the parallel modification operation.

ORA-12839 cannot modify an object in parallel after modifying it

Cause: Within the same transaction, an attempt was made to perform parallel modification operations on a table after it had been modified. This is not permitted.

Action: Rewrite the transaction or break it up into two transactions: one containing the parallel modification and the second containing the initial modification operation.

ORA-12840 cannot access a remote table after parallel/insert direct load txn

Cause: Within a transaction, an attempt was made to perform distributed access after a PDML or insert direct statement had been issued.

Action: Commit/roll back the PDML transaction first, and then perform the distributed access, or perform the distributed access before the first PDML statement in the transaction.

ORA-12841 Cannot alter the session parallel DML state within a transaction

Cause: Transaction in progress.

Action: Commit or roll back the transaction and then re-execute.

ORA-12842 schema modified during parallel execution

Cause: Schema modified during the parse phase of parallel processing.

Action: No action required.

ORA-12843 pdml lock not held properly on the table

Cause: The coodinator crashed or released the lock on the partition which the slave is trying to aquire.

Action: Check if the coordinator or some of the other slaves died. Also check that the lock has not been corrupted. Issue the PDML again.

ORA-12900 must specify a default temporary tablespace for a locally managed database

Cause: A locally managed database must have a temporary tablespace other than SYSTEM tablespace.

Action: Specify the default temporary tablespace when creating a locally managed database.

ORA-12901 Default temporary tablespace must be of TEMPORARY type

Cause: In a locally managed database, default temporary tablespace must be TEMPORARY type.

Action:

ORA-12902 default temporary tablespace must be SYSTEM or of TEMPORARY type

Cause: In a dictionary-managed database, default temporary tablespace must be SYSTEM or TEMPORARY type.

Action:

ORA-12903 default temporary tablespace must be an ONLINE tablespace

ORA-12904 default temporary tablespace cannot be altered to PERMANENT type

ORA-12905 default temporary tablespace cannot be brought OFFLINE

ORA-12906 cannot drop default temporary tablespace

ORA-12907 tablespace string is already the default temporary tablespace

ORA-12908 cannot specify SYSTEM as default temporary tablespace when creating database

ORA-12909 TEMPORARY keyword expected

ORA-12910 cannot specify temporary tablespace as default tablespace

Cause: An attempt was made to assign a temporary tablespace to be a user's default tablespace.

Action: Assign a permanent tablespace to be the default tablespace.

ORA-12911 permanent tablespace cannot be temporary tablespace

Cause: An attempt was made to assign a permanent tablespace to be a user's temporary tablespace.

Action: Assign a temporary tablespace to be user's temporary tablespace.

ORA-12912 Dictionary managed tablespace specified as temporary tablespace

Cause: An attempt was made to assign a dictionary managed tablespace to be a user's temporary tablespace.

Action: Assign a locally managed temporary tablespace to be the user's temporary tablespace.

ORA-12913 Cannot create dictionary managed tablespace

Cause: An attempt was made to create a dictionary managed tablespace in a database whose SYSTEM tablespace is locally managed.

Action: Create a locally managed tablespace.

ORA-12914 Cannot migrate tablespace to dictionary managed type

Cause: An attempt was made to migrate a locally managed tablespace to dictionary managed type when the database has a locally managed SYSTEM tablespace.

Action: Such an operation cannot be issued.

ORA-12915 Cannot alter dictionary managed tablespace to read write

Cause: An attempt was made to alter a dictionary managed tablespace to read write in a database whose SYSTEM tablespace is locally managed. This tablespace can only be dropped.

Action: Such an operation cannot be issued.

ORA-12920 database is already in force logging mode

Cause: The ALTER DATABASE FORCE LOGGING statement failed because the database is already in force logging mode.

Action: No action required.

ORA-12921 database is not in force logging mode

Cause: The ALTER DATABASE NO FORCE LOGGING statement failed because the database is not in force logging mode.

Action: No action required.

ORA-12922 concurrent ALTER DATABASE [NO] FORCE LOGGING command is running

Cause: There is a concurrent ALTER DATABASE FORCE LOGGING or ALTER DATABASE NO FORCE LOGGING statement running in the system.

Action: Contact the database administrator who is responsible for the concurrent statement.

ORA-12923 tablespace string is in force logging mode

Cause: An attempt to alter the specified temporary tablespace failed because the tablespace is in force logging mode.

Action: Put the tablespace out of force logging mode by issuing an ALTER TABLESPACE NO FORCE LOGGING statement.

ORA-12924 tablespace string is already in force logging mode

Cause: An attempt to alter the specified tablespace into force logging mode failed because it is already in force logging mode.

Action: No action required.

ORA-12925 tablespace string is not in force logging mode

Cause: An attempt to alter the specified tablespace out of force logging mode failed because it is not in force logging mode.

Action: No action required.

ORA-12926 FORCE LOGGING option already specified

Cause: In CREATE TABLESPACE, the FORCE LOGGING option was specified more than once.

Action: Remove all but one of the FORCE LOGGING options.

ORA-12980 checkpoint option not allowed with SET UNUSED

Cause: An attempt was made to specify checkpoint option with SET UNUSED.

Action: Remove the checkpoint option.

ORA-12981 cannot drop column from an object type table

Cause: An attempt was made to drop a column from an object type table.

Action: This action is not allowed.

ORA-12982 cannot drop column from a nested table

Cause: An attempt was made to drop a column from a nested table.

Action: This action is not allowed.

ORA-12983 cannot drop all columns in a table

Cause: An attempt was made to drop all columns in a table.

Action: Make sure at least one column remains in the table after the drop column operation.

ORA-12984 cannot drop partitioning column

Cause: An attempt was made to drop a column used as the partitioning key.

Action: This action is not allowed.

ORA-12985 tablespace 'string' is read only, cannot drop column

Cause: An attempt was made to drop column from a partition/subpartition on a read-only tablespace.

Action: Set the tablespace to read write and resubmit statement.

ORA-12986 columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE

Cause: An attempt was made to access a table with columns in partially dropped state (that is, drop column operation was interrupted).

Action: Submit ALTER TABLE DROP COLUMNS CONTINUE to complete the drop column operation before accessing the table.

ORA-12987 cannot combine drop column with other operations

Cause: An attempt was made to combine drop column with other ALTER TABLE operations.

Action: Ensure that drop column is the sole operation specified in ALTER TABLE.

ORA-12988 cannot drop column from table owned by SYS

Cause: An attempt was made to drop a column from a system table.

Action: This action is not allowed.

ORA-12989 invalid value for checkpoint interval

Cause: An invalid checkpoint interval specified in statement. Checkpoint interval must be between 0 and (2^31-1).

Action: Correct checkpoint interval and resubmit statement.

ORA-12990 duplicate option specified

Cause: Duplicate option specified in statement.

Action: Remove the duplicate option and resubmit statement.

ORA-12991 column is referenced in a multi-column constraint

Cause: An attempt was made to drop a column referenced by some constraints.

Action: Drop all constraints referencing the dropped column or specify CASCADE CONSTRAINTS in statement.

ORA-12992 cannot drop parent key column

Cause: An attempt was made to drop a parent key column.

Action: Drop all constraints referencing the parent key column, or specify CASCADE CONSTRAINTS in statement.

ORA-12993 tablespace 'string' is offline, cannot drop column

Cause: An attempt was made to drop a column from a partition/subpartition on an offline tablespace.

Action: Bring the tablespace online and resubmit statement.

ORA-12994 drop column option only allowed once in statement

Cause: An attempt was made to repeat the drop column option in a single statement.

Action: Separate drop column options into different statements and resubmit statements.

ORA-12995 no columns in partially dropped state

Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns.

Action: Cannot submit this statement.

ORA-12996 cannot drop system-generated virtual column

Cause: An attempt was made to drop a virtual column generated by the system.

Action: This action is not allowed.

ORA-12997 cannot drop primary key column from an index-organized table

Cause: An attempt was made to drop a primary key column from an index- organized table.

Action: This action is not allowed.

ORA-13000 dimension number is out of range

Cause: The specified dimension is either smaller than 1 or greater than the number of dimensions encoded in the HHCODE.

Action: Make sure that the dimension number is between 1 and the maximum number of dimensions encoded in the HHCODE.

ORA-13001 dimensions mismatch error

Cause: The number of dimensions in two HHCODEs involved in a binary HHCODE operation do not match.

Action: Make sure that the number of dimensions in the HHCODEs match.

ORA-13002 specified level is out of range

Cause: The specified level is either smaller than 1 or greater than the maximum level encoded in an HHCODE.

Action: Verify that all levels are between 1 and the maximum number of levels encoded in the HHCODE.

ORA-13003 the specified range for a dimension is invalid

Cause: The specified range for a dimension is invalid.

Action: Make sure that the lower bound (lb) is less than the upper bound (ub).

ORA-13004 the specified buffer size is invalid

Cause: The buffer size for a function is not valid.

Action: This is an internal error. Contact Oracle Support Services.

ORA-13005 recursive HHCODE function error

Cause: An error occurred in a recursively called HHCODE function.

Action: This is an internal error. Contact Oracle Support Services.

ORA-13006 the specified cell number is invalid

Cause: The cell identifier is either less than 0 or greater than (2^ndim - 1).

Action: Make sure that the cell identifier is between 0 and (2^ndim - 1).

ORA-13007 an invalid HEX character was detected

Cause: A character that is not in the range [0-9] or [A-Fa-f] was detected.

Action: Verify that all characters in a string are in the range [0-9] or [A-Fa-f].

ORA-13008 the specified date format has an invalid component

Cause: Part of the specified date format is invalid.

Action: Verify that the date format is valid.

ORA-13009 the specified date string is invalid

Cause: The specified date string has a bad component or does not match the specified format string.

Action: Make sure that the components of the date string are valid and that the date and format strings match.

ORA-13010 an invalid number of arguments has been specified

Cause: An invalid number of arguments was specified for an SDO function.

Action: Verify the syntax of the function call.

ORA-13011 value is out of range

Cause: A specified dimension value is outside the range defined for that dimension.

Action: Make sure that all values to be encoded are within the defined dimension range.

ORA-13012 an invalid window type was specified

Cause: An invalid window type was specified.

Action: Valid window types are RANGE, PROXIMITY, POLYGON.

ORA-13013 the specified topology was not INTERIOR or BOUNDARY

Cause: A topology was specified that was not INTERIOR or BOUNDARY.

Action: Make sure that INTERIOR or BOUNDARY is used to describe an HHCODE's topology.

ORA-13014 a topology identifier outside the range of 1 to 8 was specified

Cause: A topology identifier outside the range of 1 to 8 was specified.

Action: Specify a topology in the range of 1 to 8.

ORA-13015 the window definition is not valid

Cause: The number of values used to define the window does not correspond to the window type.

Action: Verify that the number of values used to define the window is correct for the window type and number of dimensions.

ORA-13016 bad partition definition

Cause: The partition common code was not correctly decoded.

Action: This is an internal error. Contact Oracle Support Services.

ORA-13017 unrecognized line partition shape

Cause: The shape of a 2-D line partition could not be determined.

Action: This is an internal error. Contact Oracle Support Services.

ORA-13018 bad distance type

Cause: The specified distance type is invalid.

Action: The only supported distance functions are EUCLID and MANHATTAN.

ORA-13019 coordinates out of bounds

Cause: Vertex coordinates lie outside the valid range for the specified dimension.

Action: Re-define vertex coordinates within specified boundaries.

ORA-13020 coordinate is NULL

Cause: A vertex coordinate has a NULL value.

Action: Re-define vertex coordinate to have a non-NULL value.

ORA-13021 element not continuous

Cause: The coordinates defining a geometric element are not connected.

Action: Re-define coordinates for the geometric element.

ORA-13022 polygon crosses itself

Cause: The coordinates defining a polygonal geometric element represent crossing segments.

Action: Re-define the coordinates for the polygon.

ORA-13023 interior element interacts with exterior element

Cause: An interior element of a geometric object interacts with the exterior element of that object.

Action: Re-define coordinates for the geometric elements.

ORA-13024 polygon has less than three segments

Cause: The coordinates defining a polygonal geometric element represent less than three segments.

Action: Re-define the coordinates for the polygon.

ORA-13025 polygon does not close

Cause: The coordinates defining a polygonal geometric element represent an open polygon.

Action: Re-define the coordinates of the polygon.

ORA-13026 unknown element type for element string.string.string

Cause: The SDO_ETYPE column in the layer_SDOGEOM table contains an invalid geometric element type value.

Action: Re-define the geometric element type in the layer_SDOGEOM table for the specified geometric element using one of the supported SDO_ETYPE values. See the Oracle Spatial User's Guide and Reference for an explanation of SDO_ETYPE and its possible values.

ORA-13027 unable to read dimension definition from string

Cause: There was a problem reading the dimension definition from the layer_SDODIM table.

Action: Verify that the layer_SDODIM table exists and that the appropriate privileges exist on the table. Address any other errors that might appear with the message.

ORA-13028 Invalid Gtype in the SDO_GEOMETRY object

Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.

Action: Verify that the geometries have valid gtypes.

ORA-13029 Invalid SRID in the SDO_GEOMETRY object

Cause: There is an invalid SDO_SRID in the SDO_GEOMETRY object. The specified SRID may be outside the valid SRID range.

Action: Verify that the geometries have valid SRIDs.

ORA-13030 Invalid dimension for the SDO_GEOMETRY object

Cause: There is a mismatch between the dimension in the SDO_GTYPE and the dimension in the SDO_GEOM_METADATA for the SDO_GEOMETRY object.

Action: Verify that the geometries have valid dimensionality.

ORA-13031 Invalid Gtype in the SDO_GEOMETRY object for point object

Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object where the VARRAYs are NULL but the SDO_GTYPE is not of type POINT.

Action: Verify that the geometries have valid gtypes.

ORA-13032 Invalid NULL SDO_GEOMETRY object

Cause: There are invalid SDO_POINT_TYPE, SDO_ELEM_INFO_ARRAY, or SDO_ORDINATE_ARRAY fields in the SDO_GEOMETRY object.

Action: Verify that the geometries have valid fields. To specify a NULL Geometry, specify the whole SDO_GEOMETRY as NULL instead of setting each field to NULL.

ORA-13033 Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object

Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. The triplets in this field do not make up a valid geometry.

Action: Verify that the geometries have valid data.

ORA-13034 Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object

Cause: There is invalid data in the SDO_ORDINATE_ARRAY field of the SDO_GEOMETRY object. The coordinates in this field do not make up a valid geometry. There may be NULL values for X, Y, or both.

Action: Verify that the geometries have valid data.

ORA-13035 Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object

Cause: There is invalid data in the SDO_ELEM_INFO_ARRAY field of the SDO_GEOMETRY object. There are arcs in a geometry that has geodetic coordinates.

Action: Verify that the geometries have valid data.

ORA-13036 Operation [string] not supported for Point Data

Cause: The specified geometry function is not supported for Point data.

Action: Make sure that the specified geometry function is not called on point data.

ORA-13037 SRIDs do not match for the two geometries

Cause: A Spatial operation is invoked with two geometries where one geometry has an SRID and the other geometry does not have an SRID.

Action: Make sure that the spatial operations are invoked between two geometries with compatible SRIDs.

ORA-13039 failed to update spatial index for element string.string.string

Cause: Another error will accompany this message that will indicate the problem.

Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.

ORA-13040 failed to subdivide tile

Cause: This is an internal error.

Action: Note any accompanying errors and contact Oracle Support Services.

ORA-13041 failed to compare tile with element string.string.string

Cause: The spatial relationship between a generated tile and the specified element could not be determined.

Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any errors which accompany ORA-13041 and contact Oracle Support Services.

ORA-13042 invalid SDO_LEVEL and SDO_NUMTILES combination

Cause: An invalid combination of SDO_LEVEL and SDO_NUMTILES values was read from the layer_SDOLAYER table. The most likely cause is that the columns are NULL.

Action: Verify that the SDO_LEVEL and SDO_NUMTILES columns contain valid integer values as described in the Oracle Spatial User's Guide and Reference. Retry the operation.

ORA-13043 failed to read meta data from the layer_SDOLAYER table

Cause: An error was encountered reading the layer meta data from the layer_SDOLAYER table.

Action: This error is usually the result of an earlier error which should also have been reported. Address this accompanying error and retry the current operation. If no accompanying error was reported, then contact Oracle Support Services.

ORA-13044 the specified tile size exceeds the maximum resolution

Cause: The tile size specified for fixed size tessellation exceeds the maximum resolution as computed from the layer meta data.

Action: See the Oracle Spatial User's Guide and Reference for an explanation of tiling levels, tile size, and tiling resolution. Ensure that the tiling parameters are set such that any generated tile is always larger than or equal to a tile at the maximum level of resolution. This can be achieved by using a fewer number of tiles per geometric object or specifying a lesser tile size value than the current one.

ORA-13045 invalid compatibility flag

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13046 invalid number of arguments

Cause: An invalid number of arguments was specified for an SDO_GEOM function.

Action: Refer to the Oracle Spatial User's Guide and Reference for a description of the syntax and semantics of the relevant SDO_GEOM function.

ORA-13047 unable to determine ordinate count from table layer_SDOLAYER

Cause: An SDO_GEOM function was unable to determine the number of ordinates for the SDO layer layer.

Action: Verify that the layer_SDOLAYER table has a valid value for the column SDO_ORDCNT. Retry the operation.

ORA-13048 recursive SQL fetch error

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13049 unable to determine tolerance value from table layer_SDODIM

Cause: An SDO_GEOM function was unable to determine the tolerance value for the SDO layer layer.

Action: Verify that the layer_SDODIM table has a valid value for the column SDO_TOLERANCE.

ORA-13050 unable to construct spatial object

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13051 failed to initialize spatial object

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13052 unsupported geometric type for geometry string.string

Cause: The geometry type for a specific instance in a layer_SDOGEOM table is not among the set of geometry types supported by the Oracle Spatial Cartridge.

Action: Check the Oracle Spatial User's Guide and Reference for the list of supported geometry types and workarounds that permit the storage and retrieval of non-supported geometric types with the SDO schema.

ORA-13053 maximum number of geometric elements in argument list exceeded

Cause: The maximum number of geometric elements that can be specified in the argument list for an SDO_GEOM function was exceeded.

Action: Check the Oracle Spatial User's Guide and Reference for the syntax of the SDO_GEOM function and use fewer arguments to describe the geometry, or check the description of the SDO_WINDOW package for a workaround that permits storing the object in a table and then using it as an argument in a call to the SDO_GEOM function.

ORA-13054 recursive SQL parse error

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13055 Oracle object string does not exist in specified table

Cause: The requested object is not present in the specified table.

Action: Verify the syntax of the function or procedure that reported this error and verify that the object does indeed exist in the specified table. Retry the operation.

ORA-13108 spatial table string not found

Cause: The specified spatial table does not exist.

Action: Check the Spatial Data option data dictionary to make sure that the table is registered.

ORA-13109 spatial table string exists

Cause: The specified spatial table is registered in the Spatial Data option data dictionary.

Action: Remove the existing table from the Spatial Data option data dictionary or use a different name.

ORA-13110 spatial table string is not partitioned

Cause: The specified spatial table is not partitioned.

Action: Check the Spatial Data option data dictionary and make sure that a high water mark is set.

ORA-13111 spatial table string has no partition key defined

Cause: The specified spatial table does not have a partition key defined.

Action: Check the Spatial Data option data dictionary and make sure that the table is partitioned.

ORA-13112 invalid count mode string

Cause: The specified count mode is not valid.

Action: Alter the count mode. Valid count modes are ESTIMATE or EXACT.

ORA-13113 Oracle table string does not exist

Cause: The specified Oracle table does not exist.

Action: Check the Oracle7 data dictionary and make sure that the table exists.

ORA-13114 tablespace string not found

Cause: The specified tablespace does not exist.

Action: Check the Oracle7 data dictionary and make sure that the specified tablespace exists and that there is a space quota defined on it.

ORA-13115 tablespace string is already allocated

Cause: The specified tablespace is already allocated to the spatial table.

Action: Allocate another tablespace name to the table.

ORA-13116 tablespace string is not allocated to table string

Cause: The specified tablespace is not allocated to the specified spatial table.

Action: Allocate the tablespace to the spatial table.

ORA-13117 partition string not found

Cause: The specified partition does not exist.

Action: Verify the name of the partition by checking the Spatial Data option data dictionary.

ORA-13119 source and target tablespaces are identical

Cause: Identical source and target tablespaces were specified when trying to move partition.

Action: Specify different source and target tablespaces if you wish to move a partition.

ORA-13121 failed to create child partition

Cause: The creation of a child partition failed.

Action: Check for other errors that accompany this error and correct them first.

ORA-13122 child partition string not found

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13123 column string is already defined

Cause: The specified column is already defined for the spatial table.

Action: Use a different column name.

ORA-13124 unable to determine column id for column string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13125 partition key is already set

Cause: A partition key is already set for the spatial table.

Action: Only one partition key can be specified per spatial table.

ORA-13126 unable to determine class for spatial table string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13127 failed to generate target partition

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13128 current tiling level exceeds user specified tiling level

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13129 HHCODE column string not found

Cause: The specified spatial column does not exist.

Action: Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary.

ORA-13135 failed to alter spatial table

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13136 null common code generated

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13137 failed to generate tablespace sequence number

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13138 could not determine name of object string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13139 could not obtain column definition for string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13140 invalid target type

Cause: The specified target type is not valid.

Action: Substitute a valid target type. Valid target types are TABLE or VIEW.

ORA-13141 invalid RANGE window definition

Cause: The RANGE window specified is not correctly defined.

Action: A RANGE window is defined by specifying the lower and upper boundary of each dimension as a pair of values (for example, such as: lower_bound1,upper_bound1,lower_bound2,upper_bound2,...). There should be an even number of values.

ORA-13142 invalid PROXIMITY window definition

Cause: The PROXIMITY window specified is not correctly defined.

Action: A PROXIMITY window is defined by specifying a center point and a radius. The center point is defined by ND values. There should be ND+1 values.

ORA-13143 invalid POLYGON window definition

Cause: The POLYGON window specified is not correctly defined.

Action: A POLYGON window is defined by specifying N pairs of values that represent the vertices of the polygon. There should be an even number of values.

ORA-13144 target table string not found

Cause: This is an internal error.

Action: Document messages and contact Oracle Support Services.

ORA-13145 failed to generate range list

Cause: This is an internal error.

Action: Document messages and contact Oracle Support Services.

ORA-13146 could not find table substitution variable string

Cause: The partition name substitution variable string was not found in the SQL filter.

Action: The substitution variable string must be in the SQL filter to indicate where that partition name should be placed.

ORA-13147 failed to generate MBR

Cause: This is an internal error.

Action: Document messages and contact Oracle Support Services.

ORA-13148 failed to generate SQL filter

Cause: This is an internal error.

Action: Document messages and contact Oracle Support Services.

ORA-13149 failed to generate next sequence number for spatial table string

Cause: This is an internal error.

Action: Document messages and contact Oracle Support Services.

ORA-13150 failed to insert exception record

Cause: Operation failed to insert a record into the exception table.

Action: Fix any other errors reported.

ORA-13151 failed to remove exception record

Cause: Operation failed to insert a record into the exception table.

Action: Fix any other errors reported.

ORA-13152 invalid HHCODE type

Cause: The specified HHCODE type is not valid.

Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.

ORA-13153 invalid high water mark specified

Cause: The highwater mark must be greater than or equal to zero.

Action: Make sure that the highwater mark is an integer greater than or equal to zero.

ORA-13154 invalid precision specified

Cause: The precision specified is out of range.

Action: The precision must be an integer greater than or equal to zero.

ORA-13155 invalid number of dimensions specified

Cause: The number of dimensions specified is out of range.

Action: The number of dimensions must be between 1 and 32.

ORA-13156 table to be registered string.string is not empty

Cause: The specified table has rows in it.

Action: Make sure that the table to be registered is empty.

ORA-13157 Oracle error ORAstring encountered while string

Cause: The specified Oracle error was encountered.

Action: Correct the Oracle error.

ORA-13158 Oracle object string does not exist

Cause: The specified object does not exist.

Action: Verify that the specified object exists.

ORA-13159 Oracle table string already exists

Cause: The specified table already exists.

Action: Drop the specified table.

ORA-13181 unable to determine length of column string_SDOINDEX.SDO_CODE

Cause: The length of the SDO_CODE column in the layer_SDOINDEX table could not be determined.

Action: Make sure that the layer_SDOINDEX table exists with the SDO_CODE column. Verify that the appropriate privileges exist on the table. Retry the operation.

ORA-13182 failed to read element string.string.string

Cause: The specified element could not be read from the layer_SDOGEOM table.

Action: Verify that the specified element exists in the table. Retry the operation.

ORA-13183 unsupported geometric type for geometry string.string

Cause: The geometry type in the layer_SDOGEOM table is unsupported.

Action: Modify the geometry type to be one of the supported types.

ORA-13184 failed to initialize tessellation package

Cause: Initialization of the tessellation package failed.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13185 failed to generate initial HHCODE

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13186 fixed tile size tessellation failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13187 subdivision failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13188 cell decode failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13189 recursive SQL parse failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13190 recursive SQL fetch failed

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13191 failed to read SDO_ORDCNT value

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13192 failed to read number of element rows

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13193 failed to allocate space for geometry

Cause: There was insufficient memory to read the geometry from the database.

Action: Validate the geometry. Record the error messages that are returned and contact Oracle Support Services.

ORA-13194 failed to decode supercell

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13195 failed to generate maximum tile value

Cause: This is an internal error.

Action: Record the error messages that are returned and contact Oracle Support Services.

ORA-13196 failed to compute supercell for element string.string.string

Cause: The system was unable to compute the minimum bounding HHCODE or supercell for the geometry.

Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.

ORA-13197 element string.string.string is out of range

Cause: Tessellation did not generate any tiles for this element. This error could be caused if the geometry definition puts the geometry outside the domain defined in the layer_SDODIM table.

Action: Verify that the geometry is valid and within the defined domain.

ORA-13198 Spatial Cartridge error: string

Cause: Internal error in some Spatial Cartridge stored procedure.

Action: Record the sequence of procedure calls or events that preceeded this error and contact Oracle Support Services if the error message text does not clearly specify the cause of the error.

ORA-13199 string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-13200 internal error [string] in spatial indexing.

Cause: This is an internal error.

Action: Contact Oracle Support Services with the exact error text.

ORA-13201 invalid parameters supplied in CREATE INDEX statement

Cause: An error was encountered while trying to parse the parameters clause for the spatial CREATE INDEX statement.

Action: Check the Spatial Cartridge User Guide for the number, syntax, and semantics of expected parameters for spatial index creation.

ORA-13202 failed to create or insert into the SDO_INDEX_METADATA table

Cause: An error was encountered while trying to create the SDO_INDEX_METADATA table or insert data into it.

Action: Verify that the current user has CREATE TABLE privilege and that the user has sufficient quota in the default or specified tablespace.

ORA-13203 failed to read USER_SDO_GEOM_METADATA table

Cause: An error was encountered while trying to read USER_SDO_GEOM_METADATA table.

Action: Check that USER_SDO_GEOM_METADATA has an entry for the current geometry table.

ORA-13204 failed to create spatial index table

Cause: An error was encountered while trying to create the index table.

Action: Check that user has create table privilege in the current schema and that the user has sufficient quota in the default or specified tablespace.

ORA-13205 internal error while parsing spatial parameters

Cause: An internal error was encountered while parsing the spatial parameters.

Action: Check to make sure that the parameters passed in the parameter string are all valid.

ORA-13206 internal error [string] while creating the spatial index

Cause: An internal error was encountered while creating the spatial index.

Action: Contact Oracle Support Services with the exact error text.

ORA-13207 incorrect use of the [string] operator

Cause: An error was encountered while evaluating the specified operator.

Action: Check the parameters and the return type of the specified operator.

ORA-13208 internal error while evaluating [string] operator

Cause: An internal error was encountered.

Action: Contact Oracle Support Services with the exact error text.

ORA-13209 internal error while reading SDO_INDEX_METADATA table

Cause: An internal error was encountered while trying to read SDO_INDEX_METADATA table.

Action: Contact Oracle Support Services. Note this and accompanying error numbers.

ORA-13210 error inserting data into the index table

Cause: An error was encountered while trying to insert data into the index table. Likely causes are:

Insufficient quota in the current tablespace
User does not appropriate privileges

Action: Check the accompanying error messages.

ORA-13211 failed to tessellate the window object

Cause: An internal error was encountered while trying to tessellate the window object.

Action: Verify the geometric integrity of the window object using the VALIDATE_GEOMETRY procedure.

ORA-13212 failed to compare tile with the window object

Cause: The spatial relationship between a generated tile and the specified window object could not be determined.

Action: This is an internal error. Verify the geometry using the VALIDATE_GEOMETRY procedure. If the procedure does not return any errors, then note any accompanying errors and contact Oracle Support Services.

ORA-13213 failed to generate spatial index for window object

Cause: Another error, indicating the real cause of the problem, should accompany this error.

Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.

ORA-13214 failed to compute supercell for window object

Cause: The system was unable to compute the minimum bounding tile or supercell for the geometry.

Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.

ORA-13215 window object is out of range

Cause: Tessellation did not generate any tiles for this geometry. This error could be caused if the geometry definition puts the geometry outside the domain defined in the USER_SDO_GEOM_METADATA view.

Action: Verify that the geometry is valid and within the defined domain.

ORA-13216 failed to update spatial index

Cause: Another error will accompany this message that will indicate the problem.

Action: Correct any accompanying errors. If no accompanying error message appears, then contact Oracle Support Services.

ORA-13217 invalid parameters supplied in ALTER INDEX statement

Cause: An error was encountered while trying to parse the parameters clause for the spatial ALTER INDEX statement.

Action: Check the Oracle Spatial User's Guide and Reference for the number, syntax, and semantics of expected parameters for spatial alter index command.

ORA-13218 max number of supported index tables reached for [string] index

Cause: An add_index parameter is passed to ALTER INDEX when the number of existing index tables is already at maximum.

Action: Delete one of the index tables before adding another index table.

ORA-13219 failed to create spatial index table [string]

Cause: An error was encountered while trying to create the index table.

Action: There is a table in the index's schema with the specified name. The create index will try to create an index table with this name. Either rename this table or change the name of the index.

ORA-13220 failed to compare tile with the geometry

Cause: The spatial relationship between a generated tile and the specified geometry could not be determined.

ORA-13221 unknown geometry type in the geometry object

Cause: The SDO_GTYPE attribute in the geometry object contains an invalid value.

Action: Re-define the geometric type in the geometry table using one of the supported SDO_GTYPE values. See the Oracle Spatial User's Guide and Reference for an explanation of SDO_GTYPE and its possible values.

ORA-13222 failed to compute supercell for geometry in string

Cause: The system was unable to compute the minimum bounding tile or supercell for a geometry in the specified table.

Action: Another error might accompany this error. Correct the accompanying error. Also, validate the geometry for correctness.

ORA-13223 duplicate entry for string in SDO_GEOM_METADATA table

Cause: There are duplicate entries for the given table and column value pair in the SDO_GEOM_METADATA table

Action: Check that the specified table and geometry column names are correct. There should be only one entry per table, geometry column pair in the SDO_GEOME_METADATA table.

ORA-13224 specified index name is too long for a spatial index

Cause: An index name was specified which is longer than the supported length of the spatial index name.

Action: Check the supported size of the index name and reduce the size of the index name.

ORA-13225 specified index table name is too long for a spatial index

Cause: An index table name was specified which is longer than the supported length of the spatial index table name.

Action: Check the supported size of the index table name and reduce the size of the index name.

ORA-13226 interface not supported without a spatial index

Cause: The geometry table does not have a spatial index.

Action: Verify that the geometry table referenced in the spatial operator has a spatial index on it.

ORA-13227 SDO_LEVEL values for the two index tables do not match

Cause: The SDO_LEVEL values for the two index tables used in the spatial join operator do not match.

Action: Verify that two compatible indexes are used for the spatial join operator. Indexes are compatible if they have the same SDO_LEVEL and SDO_NUMTILES values.

ORA-13228 Spatial index create failed due to invalid type

Cause: An Attempt was made to create a spatial index on a column of type other than SDO_GEOMETRY.

Action: Make sure that the index is created on a column of type SDO_GEOMETRY.

ORA-13230 failed to create temporary table [string] during R-tree creation

Cause: The specified temporary table either already exists or there is not enough tablespace.

Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.

ORA-13231 failed to create index table [string] during R-tree creation

Cause: The specified index table either already exists or there is not enough tablespace. Otherwise, contact Oracle Support Services.

Action: Delete the table if it already exists and verify if the current user has CREATE TABLE privleges and has sufficient space in the default or specified tablespace.

ORA-13232 failed to allocate memory during R-tree creation

Cause: This feature assumes a minimum of 64 KB memory for bulk creation.

Action: Create the index for a small subset of the data. Then, use transactional inserts for the rest.

ORA-13233 failed to create sequence number [string] for R-tree

Cause: The specified sequence number exists.

Action: Delete the sequence object or contact Oracle Support Services.

ORA-13234 failed to access R-tree-index table [string]

Cause: The index table is either deleted or corrupted.

Action: Rebuild the index or contact Oracle Support Services with accompanying error messages.

ORA-13236 internal error in R-tree processing: [string]

Cause: An internal error occurred in R-tree processing.

Action: Contact Oracle Support Services with message text.

ORA-13237 internal error during R-tree concurrent updates: [string]

Cause: An inconsistency was encountered during concurrent updates possibly due to the use of serializable isolation level.

Action: Change the isolation level to "read committed" using alter session or contact Oracle Support Services with the message text.

ORA-13239 sdo_dimensionality not specified during n-d R-tree creation

Cause: An error occurred in reading the dimensionality parameter.

Action: Check the documentation for a valid range and specify the dimensionality as a parameter.

ORA-13240 specified dimensionality greater than that of the query mbr

Cause: An error occurred because of too few values in query mbr.

Action: Omit the dimensionality or use the dimensionality of the query.

ORA-13241 specified dimensionality does not match that of the data

Cause: An error occurred because the dimensionality specified in the CREATE INDEX does not match that of the data.

Action: Change it to the data dimensionality.

ORA-13242 failed to read tolerance values for n-d R-tree

Cause: An error occurred in reading the information for the specified table and column in USER_SDO_GEOM_METADATA table.

Action: Insert appropriate row specifying the tolerance.

ORA-13243 specified operator is not supported for n-d R-tree: [string]

Cause: Currently, an n-d R-tree only supports sdo_filter operator.

Action: Check the documentation for querytype parameters for sdo_filter or contact Oracle Support Services.

ORA-13249 string

Cause: An internal error was encountered in the extensible spatial index component. The text of the message is obtained from some other server component.

Action: Contact Oracle Support Services with the exact error text.

ORA-13250 insufficient privileges to modify metadata table entries

Cause: The user requesting the operation does not have the appropriate privileges on the referenced tables.

Action: Check that the specified feature and geometry table names are correct and then verify that the current user has at least SELECT privilege on those tables.

ORA-13251 duplicate entry string in metadata table

Cause: The specified entry already exists in the metadata table.

Action: Check that the specified feature and geometry table names are correct. A feature-geometry table association should be registered only once.

ORA-13260 layer table string does not exist

Cause: Data migration source table layer_SDOGEOM does not exist.

Action: Ensure that the specified layername is correct and that the corresponding spatial layer tables exist in the current schema.

ORA-13261 geometry table string does not exist

Cause: The specified geometry table does not exist in the current schema.

Action: Create a table containing a column of type SDO_GEOMETRY and a column of type NUMBER for the GID values.

ORA-13262 geometry column string does not exist in table string

Cause: The specified table does not have a column of type SDO_GEOMETRY.

Action: Alter or recreate the table such that it includes a column of type SDO_GEOMETRY and a column of type NUMBER.

ORA-13263 column string in table string is not of type SDO_GEOMETRY

Cause: The column intended for storing the geometry is not of type SDO_GEOMETRY.

Action: Alter the column definition to be of type SDO_GEOMETRY.

ORA-13264 geometry identifier column string does not exist in table string

Cause: The specified table does not contain a GID column.

Action: Confirm that the GID columnname was correctly specified and that it exists in the specified table.

ORA-13265 geometry identifier column string in table string is not of type NUMBER.

Cause: GID column is not of type NUMBER.

Action: Alter the table definition such that the column containing the geometry identifier (GID) is of type NUMBER.

ORA-13266 error inserting data into table string

Cause: An OCI error occurred or the user has insufficient quota in the active tablespace or the rollback segments are too small.

Action: There should be an accompanying error message that indicates the cause of the problem. Take appropriate action to correct the indicated problem.

ORA-13267 error reading data from layer table string

Cause: There was an error reading the geometry data from the layer_SDOGEOM table.

Action: Verify that layer_SDOGEOM and layer_SDODIM exist. If they do exist, then run VALIDATE_GEOMETRY on the specified layer.

ORA-13268 error obtaining dimension from USER_SDO_GEOM_METADATA

Cause: There is no entry in USER_SDO_GEOM_METADATA for the specified geometry table.

Action: Insert an entry for the destination geometry table with the dimension information obtained from the source layer_SDODIM table.

ORA-13269 internal error [string] encountered when processing geometry table

Cause: An internal error occurred.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13270 OCI error string

Cause: An OCI error occurred while processing the layer or geometry tables.

Action: Take the appropriate steps to correct the OCI specific error.

ORA-13271 error allocating memory for geometry object

Cause: Insufficient memory.

Action: Make more memory available to the current session/process.

ORA-13272 geometric object string in table string is invalid

Cause: The specified object failed the geometric integrity checks performed by VALIDATE_GEOMETRY.

Action: Consult the Oracle Spatial User's Guide and Reference for information on the geometric integrity checks performed by VALIDATE_GEOMETRY and correct the geometry definition if required.

ORA-13273 dimension metadata table string does not exist

Cause: The layer_SDODIM table does not exist.

Action: Verify that the specified layer name is correct and that the layer_SDODIM table exists in the current schema.

ORA-13274 Operator invoked with non compatible SRIDs

Cause: A Spatial operator was invoked with a window geometry with an SRID and the layer without an SRID or window has no SRID and the layer has an SRID.

Action: Make sure that the layer and window both have an SRID or they both do not have an SRID.

ORA-13275 Spatial index creation failure on unsupported type

Cause: A spatial index create was invoked on a column that is not of type SDO_GEOMETRY.

Action: Spatial index can only be created on a column of type SDO_GEOMETRY. Make sure the indexed column has SDO_GEOMETRY type.

ORA-13276 internal error [string] in coordinate transformation

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13278 failure to convert SRID to native format

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13281 failure in execution of sql statement to retrieve WKT

Cause: OCI internal error or SRID does not match a table entry.

Action: Check that a valid SRID is being used.

ORA-13282 failure on initialization of coordinate transformation

Cause: Parsing error on source or destination coordinate system WKT or incompatible coordinate systems.

Action: Check validity of WKT for table entries and the legitimacy of the requested transformation.

ORA-13283 failure to get new geometry object for conversion in place

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13284 failure to copy geometry object for conversion in place

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13285 Geometry coordinate transformation error

Cause: A coordinate pair was out of valid range for a conversion/projection.

Action: Check that data to be transformed is consistent with the desired conversion/projection.

ORA-13287 can't transform unknown gtype

Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed.

Action:

ORA-13288 Point coordinate transformation error

Cause: An internal error while transforming points.

Action: Check the accompanying error messages.

ORA-13290 The specified unit is not supported

Cause: Spatial function called with an unknown UNIT.

Action: Check the supported units by Spatial and call the spatial function with the correct UNIT parameter.

ORA-13291 Conversion error between the specified unit and standard unit

Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.

Action: Check unit specification and respecify it.

ORA-13292 Incorrect ARC_TOLERANCE specification

Cause: When a SDO_BUFFER or SDO_AGGR_BUFFER function is called on a Geodetic geometry, or SDO_ARC_DENSIFY is called, ARC_TOLERANCE must be specified and it should not be less than the tolerance specified for the geometry.

Action: Check ARC_TOLERANCE specification and make sure it is correct.

ORA-13293 Cannot specify unit for geometry without a georeferenced SRID

Cause: A Spatial function with unit parameter is called on a geometry without a georeferenced SRID.

Action: Make sure that spatial functions with UNIT parameters are only called on geometries with georeferenced SRIDs.

ORA-13294 Cannot transform geometry containing circular arcs

Cause: It is impossible to transform a 3-point representation of a circular arc without distortion.

Action: Make sure a geometry does not contain circular arcs.

ORA-13295 Geometry objects are in different coordinate systems

Cause: A Spatial function is called with two geometries with two different SRIDs.

Action: Transform geometry objects to be in the same coordinate system and call the spatial function.

ORA-13296 Incorrect Coordinate System Specification

Cause: Wrong numbers in WKT for Earth radius or flattening for the current SRID.

Action: Check WKT in CS_SRS table for Earth radius and inverse flattening.

ORA-13300 Single point transform error

Cause: Low level coordinate transformation error trap.

Action: Check the accompanying error messages.

ORA-13303 failure to retrieve a geometry object from a table

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13304 failure to insert a transformed geometry object in a table

Cause: OCI internal error.

Action: Contact Oracle Support Services with the exact error message text.

ORA-13330 invalid MASK

Cause: The MASK you passed to RELATE function is not valid.

Action: Verify that the mask is not NULL. See the Oracle Spatial User's Guide and Reference for a list of supported masks.

ORA-13331 invalid LRS segment

Cause: The given LRS segment was not a valid linestring.

Action: A valid LRS geometric segment is a line string geometry in Oracle Spatial. It could be a simple or compound line string (made of lines or arcs, or both). The dimension information must include the measure dimension as the last element in Oracle Spatial metadata. Currently, the number of dimensions for an LRS segment must be greater than 2 (x/y or latitude/longitude plus measure).

ORA-13332 invalid LRS point

Cause: Given LRS point was not a point-geometry with measure information.

Action: Check the given point geometry.A valid LRS point is a point geometry in Oracle Spatial with additional measure dimension.

ORA-13333 invalid LRS measure

Cause: The given measure for linear referencing was out of range.

Action: Re-define the given measure.

ORA-13334 LRS segments not connected

Cause: The given geometric segments were not connected.

Action: Check the start/end points of the given geometric segments.

ORA-13335 LRS measure information not defined

Cause: The measure information of a given geometric segments was not assigned (IS NULL).

Action: Assign/define the measure information. An LRS geometric segment is defined if its start and end measure are assigned (non-null).

ORA-13336 Failure in converting standard diminfo/geometry to LRS dim/geom

Cause: No room for measure dimension in the given diminfo or the given standard geometry is not a point a linestring.

Action: Check if the diminfo dimensions are less than 3 or given geometry type is point or linestring.

ORA-13337 failure in concatenating LRS polygons

Cause: LRS concatenation involving LRS polygons is not supported.

Action: Check geometry and element type to make sure the concatenate operation is not called with a polygon type.

ORA-13338 failure in reversing LRS polygon/collection geometry

Cause: Reversing an LRS polygon/collection geometry produces an invalid geometry as this operation is not well defined for polygon geometry.

Action: Check the geometry type to make sure this operation is called on non polygon type geometry.

ORA-13339 LRS Polygon clipping across multiple rings

Cause: Clipping (dynseg) a polygon across multiple rings.

Action: Polygon clipping only allowed for a single ring.

ORA-13340 a point geometry has more than one coordinate

Cause: A geometry, specified as being a point, has more than one coordinate in its definition.

Action: A point has only one coordinate. If this geometry is intended to represent a point cluster, line, or polygon, then set the appropriate SDO_GTYPE or SDO_ETYPE value. If this is a single point object, then remove the extraneous coordinates from its definition.

ORA-13341 a line geometry has less than two coordinates

Cause: A geometry, specified as being a line, has less than two coordinates in its definition.

Action: A line must consist of at least two distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13342 an arc geometry has less than three coordinates

Cause: A geometry, specified as being an arc, has less than three coordinates in its definition.

Action: An arc must consist of at least three distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13343 a polygon geometry has less than four coordinates

Cause: A geometry, specified as being a polygon, has less than four coordinates in its definition.

Action: A polygon must consist of at least four distinct coordinates. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13344 an arcpolygon geometry has less than five coordinates

Cause: A geometry, specified as being an arcpolygon, has less than six coordinates in its definition.

Action: An arcpolygon must consist of at least five coordinates. An arcpolygon consists of an ordered sequence of arcs, each of which must be described using three coordinates. Since arcs are connected, the end-point of the first is the start of the second and does not have to be repeated. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13345 a compound polygon geometry has less than five coordinates

Cause: A geometry, specified as being a compound polygon, has less than five coordinates in its definition.

Action: A compound polygon must contain at least five coordinates. A compound polygon consists of at least one arc and one line, each of which must be described using three and at least two distinct coordinates, respectively. Correct the geometric definition or set the appropriate SDO_GTYPE or SDO_ETYPE attribute for this geometry.

ORA-13346 the coordinates defining an arc are collinear

Cause: Invalid definition of an arc. An arc is defined using three non-collinear coordinates.

Action: Alter the definition or the arc or set the SDO_ETYPE or SDO_GTYPE to the line type.

ORA-13347 the coordinates defining an arc are not distinct

Cause: Two or more of the three points defining an arc are the same.

Action: Alter the definition of the arc, ensuring that three distinct coordinate values are used.

ORA-13348 polygon boundary is not closed

Cause: The boundary of a polygon does not close.

Action: Alter the coordinate values or the definition of the SDO_GTYPE or SDO_ETYPE attribute of the geometry.

ORA-13349 polygon boundary crosses itself

Cause: The boundary of a polygon intersects itself.

Action: Correct the geometric definition of the object.

ORA-13350 two or more rings of a complex polygon touch

Cause: The inner or outer rings of a complex polygon touch.

Action: All rings of a complex polygon must be disjoint. Correct the geometric description of the object.

ORA-13351 two or more rings of a complex polygon overlap

Cause: The inner or outer rings of a complex polygon overlap.

Action: All rings of a complex polygon must be disjoint. Correct the geometric description of the object.

ORA-13352 the coordinates do not describe a circle

Cause: The set of coordinates used to describe a circle are incorrect.

Action: Confirm that the set of coordinates actually represent points on the circumference of a circle.

ORA-13353 ELEM_INFO_ARRAY not grouped in threes

Cause: The ELEM_INFO_ARRAY in SDO_GEOMETRY has more or fewer elements than expected.

Action: Confirm that the number of elements in ELEM_INFO_ARRAY is divisible by 3.

ORA-13354 incorrect offset in ELEM_INFO_ARRAY

Cause: The offset field in ELEM_INFO_ARRAY of SDO_GEOMETRY references an invalid array subscript in SDO_ORDINATE_ARRAY.

Action: Confirm that the offset is a valid array subscript in SDO_ORDINATE_ARRAY.

ORA-13355 SDO_ORDINATE_ARRAY not grouped by number of dimensions specified

Cause: The number of elements in SDO_ORDINATE_ARRAY is not a multiple of the number of dimensions supplied by the user.

Action: Confirm that the number of dimensions is consistent with data representation in SDO_ORDINATE_ARRAY.

ORA-13356 adjacent points in a geometry are redundant

Cause: There are repeated points in the sequence of coordinates.

Action: Remove the redundant point.

ORA-13357 extent type does not contain 2 points

Cause: Extent type should be represented by 2 points: lower left and upper right.

Action: Confirm that there are only 2 points for extent type.

ORA-13358 circle type does not contain 3 points

Cause: Circle type should be represented by 3 distinct points on the circumference.

Action: Confirm that there are only 3 points for circle type.

ORA-13359 extent does not have an area

Cause: The 2 points representing the extent are identical.

Action: Confirm that the 2 points describing the extent type are distinct.

ORA-13360 invalid subtype in a compound type

Cause: This subtype is not allowed within the ETYPE specified.

Action: Refer to Oracle Spatial User's Guide and Reference for type definitions.

ORA-13361 not enough sub-elements within a compound ETYPE

Cause: The compound type declare more sub-elements than actually defined.

Action: Confirm that the number of sub-elements is consistent with the compound type declaration.

ORA-13362 disjoint sub-element in a compound polygon

Cause: Compound polygon must describe an enclosed area.

Action: Confirm that all sub-elements are connected.

ORA-13363 no valid ETYPE in the geometry

Cause: None of the ETYPEs within the geometry is supported.

Action: Confirm that there is at least one valid ETYPE.

ORA-13364 Layer Dimensionality does not match geometry dimensions

Cause: Spatial layer has a geometry with a different dimensions than the dimensions specified for the layer.

Action: Make sure that all geometries in a layer have the same dimensions and they match the dimensions in the SDO_DIM_ARRAY object for the layer in USER_SDO_GEOM_METADATA.

ORA-13365 Layer SRID does not match geometry SRID

Cause: Spatial layer has a geometry with a different SRID than the SRID specified for the layer.

Action: Make sure that all geometries in a layer have the same SRID and the SRIDs match the SRID in USER_SDO_GEOM_METADATA for the layer.

ORA-13366 Invalid combination of interior exterior rings

Cause: In the Spatial geometry, interior and exterior rings are not used consistently.

Action: Make sure that the interior rings corresponding to an exterior ring follow the exterior ring in the ordinate array.

ORA-13367 Wrong orientation for interior/exterior rings

Cause: In a spatial geometry, the exterior and/or interior rings are not oriented correctly.

Action: The exterior rings should be oriented counter clock-wise and interior rings should be oriented clock wise.

ORA-13368 Simple Polygon type has more than one exterior ring

Cause: In a polygon type geometry, there is more than one exterior ring.

Action: Set the type to be multi-polygon if more than one exterior is present in the geometry.

ORA-13369 Invalid value for etype in the 4 digit format

Cause: A 4 digit etype for non polygon type element is used or the orientation is not a valid orientation for interior/exterior rings of the polygon.

ORA-13370 failure in applying 3D LRS functions

Cause: Only Non-geodetic 3D linestring geometry (made of line segments) are supported for 3D LRS package.

Action: Check the geometry and element types and SRID.

ORA-13371 invalid position of measure dimension

Cause: LRS measure dimension has to be after spatial dimensions. The position has to be either 3rd or 4th in dim_info_array.

Action: Check geometry gtype and its dim_info_array.

ORA-13372 failure in modifying metadata for a table with spatial index

Cause: Modifying the metadata after the index is created will cause inconsistency between geometry gtype and diminfo.

Action: Modify(or Prepare) metadata before creating index on sdo_geometry column.

ORA-13373 Element of type Extent is not supported for Geodetic data

Cause: Element type extent for a polygon geometry is not supported for geodetic data.

Action: Convert the extent type polygon to a regular 5 point polygon and set etype accordingly.

ORA-13374 SDO_MBR not supported for geodetic data

Cause: The SDO_MBR functionality is not supported for geodetic data.

Action: Find an alternative function that can be used in this context.

ORA-13375 The layer is of type [string] while geometry inserted has type [string]

Cause: The layer has a type that is different or inconsistent with the type of the current geometry.

Action: Change the geometry type to agree with the layer type or change the layer type to agree with the geometry type.

ORA-13376 Invalid type name specified for layer_gtype parameter

Cause: An invalid type name is specified for the layer gtype constraint.

Action: Consult the Oracle Spatial User's Guide and Reference to get a list of valid layer gtypes that can be used in defining a layer gtype constraint.

ORA-13377 Invalid combination of elements with orientation

Cause: An element of the geometry has orientation specified while some other element has no orientation specified (4 digit etype).

Action: Make sure all the polygon elements have orientation specified using the 4 digit etype notation.

ORA-13378 Invalid index for element to be extracted

Cause: An invalid (or out of bounds) index was specified for extracting an element from a geometry.

Action: Make sure the parameters to the extract function are in the valid range for the given geometry.

ORA-13379 Invalid index for sub-element to be extracted

Cause: An invalid (or out of bounds) index was specified for extracting a sub-element from a geometry.

Action: Make sure the parameters to the extract function are in the valid range for the given geometry.

ORA-13400 Oracle GeoImage internal error, arguments: [string], [string], [string], [string], [string]

Cause: This is an internal Oracle GeoImage error.

Action: Contact Oracle Support Services.

ORA-13401 unsupported geoimage format

Cause: The GeoImage format is not supported.

Action: Confirm that the GeoImage format is valid and supported.

ORA-13402 NULL destination

Cause: The object specified as the destination is NULL.

Action: Confirm that the object specified as the destination is not NULL.

ORA-13403 NULL source geometry

Cause: The source GeoImage has a NULL geometry.

Action: Verify that the geometry of the source GeoImage is not NULL.

ORA-13404 not a local source

Cause: An attempt has been made to modify a GeoImage which is not stored in the database.

Action: Import the GeoImage in order to modify it.

ORA-13405 NULL source

Cause: The object specified as the source is NULL.

Action: Confirm that the object specified as the source is not NULL.

ORA-13406 unsupported image processing command [string]

Cause: The image processing command specified is not supported for a GeoImage.

Action: Consult the Oracle interMedia User's Guide and Reference to verify which image processing commands are supported within an Oracle GeoImage method.

ORA-13407 unrecognized space type qualifier [string]

Cause: The GeoImage space type qualifier is invalid.

Action: Use a valid space type qualifier (RASTER or MODEL).

ORA-13408 NULL table name

Cause: The table name parameter is NULL.

Action: Verify that the parameter used for the table name is not NULL.

ORA-13409 Oracle table "string" does not exist.

Cause: The table specified does not exist.

Action: Verify that the table name used is valid and the table exists.

ORA-13410 NULL column name

Cause: The column name parameter is NULL.

Action: Verify that the parameter used for the column name is not NULL.

ORA-13411 Oracle column "string" does not exist.

Cause: The column specified does not exist.

Action: Verify that the column name used is valid and the column exists.

ORA-13412 invalid ROWID

Cause: The ROWID value used is not valid.

Action: Verify that the ROWID value used is valid.

ORA-13413 could not select the GeoImage for initialization

Cause: The GeoImage in the table could not be selected.

Action: Verify that the GeoIMage is present in the table and the supplied parameters are valid.

ORA-13414 could not update the table containing the GeoImage

Cause: The table containing the GeoImage could not be updated.

Action: Verify that the table exists and is valid.

ORA-13415 invalid domain

Cause: The SDO_DIMINFO value used is not valid or the SDO_GEOMETRY supplied is not defined in the domain.

Action: Verify that the SDO_DIMINFO value is valid, and that the SDO_GEOMETRY is defined within the domain specified.

ORA-13416 invalid geometry, arguments [string]

Cause: The SDO_GEOMETRY value used is not valid.

Action: Verify that the SDO_GEOMETRY is valid. Consult the Oracle Spatial User's Guide and Reference for a list of valid geometries.

ORA-13417 undefined raster to model space transformation

Cause: The raster to model space transformation associated with a GeoImage is undefined.

Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format.

ORA-13418 undefined model to raster space transformation

Cause: The model to raster space transformation associated with a GeoImage is undefined.

Action: Verify that the GeoImage format is valid and that the particular operation is supported for that format.

ORA-13419 invalid latitude value

Cause: A latitude value outside the valid range [-90,90] has been used.

Action: Verify that the GeoImage geometry definition is within the domain.

ORA-13420 invalid model to raster space transformation

Cause: The model to raster space transformation associated with a GeoImage is not valid or cannot be calculated.

Action: Verify that the transformation is supported and that the GeoImage format is valid.

ORA-13421 invalid raster to model space transformation

Cause: The raster to model space transformation associated with a GeoImage is not valid or cannot be calculated.

Action: Verify that the transformation is supported and that the GeoImage format is valid.

ORA-13422 uninitialized source

Cause: The LOB used for the source is not initialized.

Action: Verify that the source is properly initialized.

ORA-13423 empty source

Cause: The LOB used for the source is empty.

Action: Verify that the source is properly initialized and data has been imported into it.

ORA-13424 uninitialized destination

Cause: The LOB used for the destination is not initialized.

Action: Verify that the destination is properly initialized.

ORA-13425 empty destination

Cause: The LOB used for the destination is empty.

Action: Verify that the destination is properly initialized and data has been imported into it.

ORA-13426 unsupported raster origin

Cause: The raster origin specified is not supported.

Action: Verify that the origin specified is supported.

ORA-13427 unknown raster origin

Cause: The value specified for the raster origin is invalid.

Action: Verify that the value used to specify the raster origin is valid and supported.

ORA-13428 source does not exist

Cause: The source does not exist or cannot be accessed.

Action: Verify that the source specification is correct and accessible.

ORA-13429 operation "string" not supported on GeoImage type "string"

Cause: The specified operation is not supported on the particular geoimage type.

Action: Verify that the operation is supported.

ORA-13430 model coordinate system not supported

Cause: The model specified for the definition of the coordinate system is not supported.

Action: Verify that the model value is correct.

ORA-13433 NULL crop geometry

Cause: The geometry used to crop a GeoImage is NULL.

Action: Verify that the geometry used for the crop operation is not NULL.

ORA-13442 invalid scaling parameters [string] [string]

Cause: The parameters used in the scale operation are invalid.

Action: Verify that the scaling parameters are greater than zero.

ORA-13443 unrecognized scale mode [string]

Cause: The scale mode used in the scale operation is invalid.

Action: Consult the Oracle interMedia User's Guide and Reference for a list of valid scale mode qualifiers.

ORA-13451 unsupported conversion format [string]

Cause: The format specified for conversion is invalid or unsupported.

Action: Verify that the conversion format specified is valid.

ORA-13461 invalid tag/key [string]

Cause: The tag or key is invalid.

Action: Verify that the format version is supported or the format is valid.

ORA-13462 invalid tie point

Cause: One of the tie points is invalid.

Action: Verify that the tie points used are valid (for example all raster tie points are >= 0).

ORA-13463 unsupported GeoTIFF geometry definition

Cause: The combination of keys/tags used to define the geometry footprint of the GeoImage is not supported.

Action: Verify that the GeoTIFF format version is supported and the format is valid.

ORA-13464 unsupported conversion

Cause: The format specified for conversion is not supported. In GeoTIFF, only a limited number of tags/keys combinations are supported for conversion.

Action: Verify that the GeoTIFF format version is supported and conversion to the desired format is available.

ORA-13465 invalid destination window

Cause: The window specified as destination in the command is not valid.

Action: Verify that the window definition is correct.

ORA-14000 only one LOCAL clause may be specified

Cause: CREATE INDEX statement contained more than one LOCAL clause.

Action: Specify LOCAL option at most once.

ORA-14001 LOCAL clause contradicts previosly specified GLOBAL clause

Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause.

Action: Specify LOCAL or GLOBAL clause, but not both.

ORA-14002 only one GLOBAL clause may be specified

Cause: CREATE INDEX statement contained more than one GLOBAL clause.

Action: Specify GLOBAL option at most once.

ORA-14003 GLOBAL clause contradicts previosly specified LOCAL clause

Cause: CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause.

Action: Specify GLOBAL or LOCAL clause, but not both.

ORA-14004 missing PARTITION keyword

Cause: Keyword PARTITION missing.

Action: Supply missing keyword.

ORA-14005 missing RANGE keyword

Cause: Keyword RANGE missing.

Action: Supply missing keyword.

ORA-14006 invalid partition name

Cause: A partition name of the form identifier is expected but not present.

Action: Enter an appropriate partition name.

ORA-14007 missing LESS keyword

Cause: Keyword LESS missing.

Action: Supply missing keyword.

ORA-14008 missing THAN keyword

Cause: Keyword THAN missing.

Action: Supply missing keyword.

ORA-14009 partition bound may not be specified for a LOCAL index partition

Cause: While parsing a CREATE INDEX statement to create a LOCAL partitioned index, partition_description of one of partitions was found to contain VALUES LESS THAN clause which is illegal since a LOCAL index inherits partition bounds from its base table.

Action: Remove all VALUES LESS THAN clauses from descriptions of LOCAL index partitions.

ORA-14010 this physical attribute may not be specified for an index partition

Cause: Unexpected option was encountered while parsing physical attributes of an index partition; valid options for range or composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE; only TABLESPACE may be specified for hash partitions.

Action: Remove invalid option(s) from the list of physical attributes of an index partition.

ORA-14011 names assigned to resulting partitions must be distinct

Cause: Names of partitions resulting from splitting of an existing table or index partition are not distinct.

Action: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.

ORA-14012 resulting partition name conflicts with that of an existing partition

Cause: Name of a partition resulting from splitting of an existing table or index partition is identical to that of some other existing partition of that table or index.

Action: Rename resulting partition(s) to ensure that their names are distinct and different from those of any other partition of the table or index.

ORA-14013 duplicate partition name

Cause: Name of a partition of a table or index being created is not unique.

Action: Rename partition(s) to ensure that their names are unique among partitions of the table or index being created.

ORA-14014 maximum number of partitioning columns is 16

Cause: Number of columns in a partitioning column list exceeded the legal limit of 16.

Action: Modify partitioning column list so that it consists of at most 16 columns.

ORA-14015 too many partition descriptions

Cause: CREATE TABLE or CREATE INDEX contained too many partition descriptions; maximum number of partitions is 65535.

Action: Reduce the number of partitions to not exceed 65535.

ORA-14016 underlying table of a LOCAL partitioned index must be partitioned

Cause: An attempt was made to create a LOCAL partitioned index on a non-partitioned table which is illegal. Only GLOBAL indices (partitioned or otherwise) may be created on a non-partitioned table.

Action: Correct the statement and re-enter it.

ORA-14017 partition bound list contains too many elements

Cause: Partition bound list contained more elements than there are partitioning columns.

Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index.

ORA-14018 partition bound list contains too few elements

Cause: Partition bound list contained fewer elements than there are partitioning columns.

Action: Ensure that the number of elements in partition bound list is equal to the number of partitioning columns of the table or index.

ORA-14019 partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE

Cause: Partition bound list contained an element of invalid type (that is, not a number, non-empty string, datetime or interval literal, or MAXVALUE).

Action: Ensure that all elements of partition bound list are of valid type.

ORA-14020 this physical attribute may not be specified for a table partition

Cause: Unexpected option was encountered while parsing physical attributes of a table partition; valid options for range or composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, and PCTUSED; only TABLESPACE may be specified for hash partitions.

Action: Remove invalid option(s) from the list of physical attributes of a table partition.

ORA-14021 MAXVALUE must be specified for all columns

Cause: In the VALUES LESS THAN clause for the highest (last) partition of a GLOBAL index, MAXVALUE must be specified for all columns.

Action: Ensure that VALUES LESS THAN clause for the last partition of a GLOBAL index has MAXVALUE specified for all columns.

ORA-14022 creation of LOCAL partitioned cluster indices is not supported

Cause: An attempt was made to create a LOCAL partitioned cluster index, which is currently illegal.

Action: Remove LOCAL along with partition_descriptions, if any, from the CREATE INDEX statement.

ORA-14023 creation of GLOBAL partitioned cluster indices is not supported

Cause: An attempt was made to create a GLOBAL partitioned cluster index, which is currently illegal.

Action: Remove PARTITION BY RANGE clause along with partition_descriptions from the CREATE INDEX statement.

ORA-14024 number of partitions of LOCAL index must equal that of the underlying table

Cause: An attempt was made to create a LOCAL partitioned index with a number of partitions which is different from that of the underlying table.

Action: Correct the CREATE INDEX statement to specify a correct number of partitions.

ORA-14025 PARTITION may not be specified for a materialized view or a materialized view log

Cause: PARTITION option was encountered while parsing a definition of a materialized view or a materialized view log.

Action: Ensure that a definition of a MATERIALIZED VIEW does not include invalid options.

ORA-14026 PARTITION and CLUSTER clauses are mutually exclusive

Cause: Definition of a table contained both PARTITION and CLUSTER clauses which is illegal.

Action: Remove one of the conflicting clauses.

ORA-14027 only one PARTITION clause may be specified

Cause: CREATE TABLE statement contained more than one PARTITION clause.

Action: Specify PARTITION option at most once.

ORA-14028 missing AT or VALUES keyword

Cause: Keyword AT or VALUES is missing.

Action: Supply missing keyword.

ORA-14029 GLOBAL partitioned index must be prefixed

Cause: The partitioning columns of a global partitioned index did not contain a prefix of the index's key columns.

Action: Ensure that the GLOBAL partitioned index being created is prefixed and retry the operation.

ORA-14030 non-existent partitioning column in CREATE TABLE statement

Cause: Partitioning column specified in CREATE TABLE statement is not one of columns of the table being created.

Action: Ensure that all columns in the partitioning column list are columns of the table being created.

ORA-14031 partitioning column may not be of type LONG or LONG RAW

Cause: Partitioning column specified by the user was of type LONG or LONG RAW, which is illegal.

Action: Ensure that no partitioning column is of type LONG or LONG RAW.

ORA-14032 partition bound of partition number string is too high

Cause: High bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message did not collate lower than that of the following partition, which is illegal.

Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition.

ORA-14036 partition bound value too large for column

Cause: Length of partition bound value is longer than that of the corresponding partitioning column.

Action: Ensure that lengths of high bound values do not exceed those of corresponding partitioning columns.

ORA-14037 partition bound of partition "string" is too high

Cause: High bound of the partition whose name (explicitly specified by the user) is displayed in this message did not collate lower than that of the following partition, which is illegal.

Action: Ensure that high bound of every partition (except for the last one) collates lower than that of a following partition.

ORA-14038 GLOBAL partitioned index must be prefixed

Cause: An attempt was made to create a GLOBAL non-prefixed partitioned index which is illegal.

Action: If a non-prefixed index is desired, it must be created as LOCAL; otherwise, correct the list of key and/or partitioning columns to ensure that the index is prefixed. Then retry the operation.

ORA-14039 partitioning columns must form a subset of key columns of a UNIQUE index

Cause: An attempt was made to create a UNIQUE partitioned index whose partitioning columns do not form a subset of its key columns which is illegal.

Action: If you want to create an index whose partitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or partitioning columns to ensure that the index's partitioning columns form a subset of its key columns.

ORA-14041 partition bound may not be specified for resulting partitions

Cause: While parsing an ALTER {TABLE|INDEX} SPLIT PARTITION statement, partition_description of a resulting partition was found to contain VALUES LESS THAN clause which is illegal.

Action: Remove VALUES LESS THAN clause from the description(s) of partitions resulting from splitting an existing table or index partition.

ORA-14042 partition bound may not be specified for a partition being moved, modified or rebuilt

Cause: While parsing an ALTER {TABLE|INDEX} MODIFY PARTITION, ALTER TABLE MOVE PARTITION, or ALTER INDEX REBUILD PARTITION statement, description of new physical attributes of the partition being moved, modified, or rebuilt was found to contain VALUES LESS THAN clause which is illegal.

Action: Remove VALUES LESS THAN clause from the description of new attributes of the partition being moved, modified, or rebuilt.

ORA-14043 only one partition may be added

Cause: ALTER TABLE ADD PARTITION contained descriptions of more than one partition to be added.

Action: Ensure that the statement contains exactly one partition definition and that it does not contain any commas.

ORA-14044 only one partition may be moved

Cause: ALTER TABLE MOVE PARTITION contained descriptions of more than one partition to be moved.

Action: Ensure that the statement describes exactly one partition to be moved and that it does not contain any commas.

ORA-14045 only one partition may be modified

Cause: ALTER TABLE|INDEX MODIFY PARTITION contained descriptions of more than one partition to be modified.

Action: Ensure that the statement describes exactly one partition to be modified and that it does not contain any commas.

ORA-14046 a partition may be split into exactly two new partitions

Cause: ALTER TABLE|INDEX SPLIT PARTITION did not contain descriptions of exactly two new partitions into which an existing table or index partition was to be split.

Action: Ensure that the statement describes exactly two partition into which an existing partition is to be split.

ORA-14047 ALTER TABLE|INDEX RENAME may not be combined with other operations

Cause: ALTER TABLE or ALTER INDEX statement attempted to combine a RENAME operation with some other operation which is illegal.

Action: Ensure that RENAME operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement.

ORA-14048 a partition maintenance operation may not be combined with other operations

Cause: The ALTER TABLE or ALTER INDEX statement attempted to combine a partition maintenance operation (for example, MOVE PARTITION) with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.

Action: Ensure that a partition maintenance operation is the sole operation specified in an ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices, or specifying that a table be renamed (ALTER TABLE RENAME) can be combined.

ORA-14049 invalid ALTER TABLE MODIFY PARTITION option

Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, BACKUP, ALLOCATE EXTENT, or DEALLOCATE UNUSED was specified in an ALTER TABLE MODIFY PARTITION statement for a range or composite range partition.

Action: Specify only legal options.

ORA-14050 invalid ALTER INDEX MODIFY PARTITION option

Cause: An option other than INITRANS, MAXTRANS, STORAGE, or DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY PARTITION statement.

Action: Specify only legal options.

ORA-14051 invalid ALTER MATERIALIZED VIEW option

Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, or BACKUP was specified in an ALTER MATERIALIZED VIEW statement.

Action: Specify only legal options.

ORA-14052 partition-extended table name syntax is disallowed in this context

Cause: An attempt was made to use partition-extended table name syntax in illegal context (that is, not in FROM-clause or INSERT, DELETE, or UPDATE statement).

Action: Avoid use of partition-extended table name in contexts other those mentioned above.

ORA-14053 illegal attempt to modify string in string statement

Cause: Certain attributes of objects (for example, tables) may be specified at creation time, but may not be modified using ALTER statement. Unfortunately, user specified one of such attributes.

Action: Ensure that ALTER statement specifies new values only for attributes which may be changed once an object has been created.

ORA-14054 invalid ALTER TABLE TRUNCATE PARTITION option

Cause: Name of the partition to be truncated may be followed by DROP STORAGE or REUSE STORAGE.

Action: Ensure that no options besides DROP STORAGE or REUSE STORAGE are specified with ALTER TABLE TRUNCATE PARTITION.

ORA-14055 keyword REBUILD in ALTER INDEX REBUILD must immediately follow index_name

Cause: ALTER INDEX statement contained REBUILD keyword following some index attributes (for example, INITRANS).

Action: Ensure that keyword REBUILD immediately follows the name of the index being altered.

ORA-14056 partition number string: sum of PCTUSED and PCTFREE may not exceed 100

Cause: The sum of PCTUSED and PCTFREE for a partition whose number (partitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used.

Action: Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100.

ORA-14057 partition "string": sum of PCTUSED and PCTFREE may not exceed 100

Cause: The sum of PCTUSED and PCTFREE for a partition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default PCTUSED and/or PCTFREE values for the partitioned table or index were not specified, system defaults would be used.

Action: Ensure that a sum of PCTUSED and PCTFREE for the partition does not exceed 100.

ORA-14058 partition number string: INITRANS value must be less than MAXTRANS value

Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose number (partitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used.

Action: Ensure that the value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS.

ORA-14059 partition "string": INITRANS value must be less than MAXTRANS value

Cause: Value of INITRANS was found to be greater than that of MAXTRANS for a partition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this partition were not specified explicitly, default values for the partitioned table or index would be used. If, in turn, default INITRANS and/or MAXTRANS values for the partitioned table or index were not specified, system defaults would be used.

Action: Ensure that the value of INITRANS (whether specified explicitly or derived from the default value for the partitioned table or index) is no greater than that of MAXTRANS.

ORA-14060 data type or length of a table partitioning column may not be changed

Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition the table named in ALTER TABLE statement, which is illegal.

Action: Avoid modifying data type and/or length of table partitioning column(s).

ORA-14061 data type or length of an index partitioning column may not be changed

Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to partition some index defined on the table named in ALTER TABLE statement, which is illegal.

Action: Avoid modifying data type and/or length of index partitioning column(s).

ORA-14062 one or more of table's partitions reside in a read-only tablespace

Cause: User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more partitions of which reside in read-only tablespaces, which is illegal.

Action: Avoid performing aforementioned operations on a partitioned table one or more partitions of which reside in read-only tablespaces.

ORA-14063 Unusable index exists on unique/primary constraint key

Cause: An attempt was made to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index marked Index Unusable.

Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD.

ORA-14064 Index with Unusable partition exists on unique/primary constraint key

Cause: An attempt was made to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index one or more partitions of which are marked Index Unusable.

Action: Drop the existing index or rebuild unusable partitions it using ALTER INDEX REBUILD PARTITION.

ORA-14065 ALLOCATE STORAGE may not be specified for a partitioned table

Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a partitioned table which is illegal.

Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION statement.

ORA-14066 illegal option for a non-partitioned index-organized table

Cause: An attempt was made to issue a CREATE or ALTER TABLE command on a non-partitioned index-organized table, but the command contains an option that is legal only for partitioned index-organized tables. Such options are: ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT.

Action: Remove the illegal options from the command.

ORA-14067 duplicate TABLESPACE_NUMBER specification

Cause: TABLESPACE_NUMBER clause was specified more than once for a table, an index, or an index partition.

Action: Correct the code generating text of CREATE INDEX statement sent to the slaves.

ORA-14068 TABLESPACE and TABLESPACE_NUMBER may not be both specified

Cause: Both TABLESPACE and TABLESPACE_NUMBER clauses were specified for a table, an index, or an index partition.

Action: Correct the code generating text of CREATE INDEX statement sent to the slaves.

ORA-14069 invalid TABLESPACE_NUMBER value

Cause: The TABLESPACE_NUMBER value is not an integer between 0 and 0x7FFFFFFF.

Action: Correct the code generating text of CREATE INDEX statement sent to the slaves.

ORA-14070 option may be specified only for partitioned indices or with REBUILD

Cause: User issued ALTER INDEX statement containing an option which is legal only for partitioned indices or in conjunction with REBUILD against a non-partitioned index. Such options are: PCTFREE, TABLESPACE, [NO]PARALLEL and INITIAL, FREELISTS, and FREELIST GROUPS inside STORAGE clause.

Action: Remove illegal option(s).

ORA-14071 invalid option for an index used to enforce a constraint

Cause: An option other than COMPRESS, NOCOMPRESS, PCTFREE, INITRANS, MAXTRANS, STORAGE, TABLESPACE, PARALLEL, NOPARALLEL, RECOVERABLE, UNRECOVERABLE, LOGGING, NOLOGGING, LOCAL, or GLOBAL was specified for an index used to enforce a constraint.

Action: Choose one of the valid index options.

ORA-14072 fixed table may not be truncated

Cause: An attempt was made to truncate a fixed table which is illegal.

Action: Ensure that the table being truncated is not a fixed table.

ORA-14073 bootstrap table or cluster may not be truncated

Cause: An attempt was made to truncate a bootstrap table or cluster which is illegal.

Action: Ensure that the table (or cluster) being truncated is not a bootstrap table (or cluster).

ORA-14074 partition bound must collate higher than that of the last partition

Cause: Partition bound specified in ALTER TABLE ADD PARTITION statement did not collate higher than that of the table's last partition, which is illegal.

Action: Ensure that the partition bound of the partition to be added collates higher than that of the table's last partition.

ORA-14075 partition maintenance operations may only be performed on partitioned indices

Cause: Index named in ALTER INDEX partition maintenance operation is not partitioned, making a partition maintenance operation, at best, meaningless.

Action: Ensure that the index named in ALTER INDEX statement specifying a partition maintenance operation is, indeed, partitioned.

ORA-14076 DROP/SPLIT PARTITION may not be applied to a LOCAL index partition

Cause: An attempt was made to drop or split a partition of a LOCAL index which is illegal.

Action: Ensure that the index named in such statement is a GLOBAL partitioned index.

ORA-14078 you may not drop the highest partition of a GLOBAL index

Cause: An attempt was made to drop highest partition of a GLOBAL index, which is illegal.

Action: Ensure that the partition specified in ALTER INDEX DROP PARTITION statement is not the highest partition of the index.

ORA-14079 illegal option for a partition marked Index Unusable

Cause: ALTER INDEX MODIFY PARTITION statement against an index partition marked Index Unusable contained STORAGE and/or DEALLOCATE SPACE clauses which is illegal.

Action: Ensure that only valid options are specified.

ORA-14080 partition cannot be split along the specified high bound

Cause: An attempt was made to split a partition along a bound which either collates higher than that of the partition to be split or lower than that of a partition immediately preceding the one to be split.

Action: Ensure that the bound along which a partition is to be split collates lower than that of the partition to be split and higher that of a partition immediately preceding the one to be split.

ORA-14081 new partition name must differ from the old partition name

Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying new_partition_name which is identical to the name of the partition being renamed.

Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index.

ORA-14082 new partition name must differ from that of any other partition of the object

Cause: User entered ALTER TABLE/INDEX RENAME PARTITION specifying new_partition_name which is identical to the name of some existing partition of the object.

Action: Ensure that the new partition name is different from the name of any (including the one being renamed) existing partition of a given table or index.

ORA-14083 cannot drop the only partition of a partitioned table

Cause: A drop partition command is being executed when there is only one partition in the table.

Action: Ensure that there is at least one partition. Drop table to remove all partitions.

ORA-14084 you may specify TABLESPACE DEFAULT only for a LOCAL index

Cause: An attempt was made to specify TABLESPACE DEFAULT for an object other than a LOCAL index, which is illegal.

Action: Re-enter the statement without TABLESPACE DEFAULT clause.

ORA-14085 partitioned table cannot have column with LONG datatype

Cause: An attempt was made to create a partitioned table with a LONG datatype or tried to add a LONG datatype column to a partitioned table.

Action: LONG data types are not supported with partitioned tables. Create table without LONG column or change table to not partitioned. If adding column, do not use LONG datatype. If modifying attributes of a column to change data type to LONG, it has to be a non-partitioned table.

ORA-14086 a partitioned index may not be rebuilt as a whole

Cause: An attempt was made to rebuild a partitioned index using ALTER INDEX REBUILD statement, which is illegal.

Action: Rebuild the index a partition at a time (using ALTER INDEX REBUILD PARTITION) or drop and re-create the entire index.

ORA-14094 invalid ALTER TABLE EXCHANGE PARTITION option

Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEXES][{WITH|WITHOUT} VALIDATION].

Action: Ensure that no options besides INCLUDING INDEXES or EXCLUDING INDEXES are specified with ALTER TABLE EXCHANGE PARTITION.

ORA-14095 ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table

Cause: The table in the EXCHANGE operation is either clustered or partitioned.

Action: Ensure that the table with which the partition is being exchanged for is not partitioned or clustered.

ORA-14096 tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns

Cause: The two tables specified in the EXCHANGE have different number of columns.

Action: Ensure that the two tables have the same number of columns with the same type and size.

ORA-14097 column type or size mismatch in ALTER TABLE EXCHANGE PARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION are of different type or size.

Action: Ensure that the two tables have the same number of columns with the same type and size.

ORA-14098 index mismatch for tables in ALTER TABLE EXCHANGE PARTITION

Cause: The two tables specified in the EXCHANGE have indexes which are not equivalent.

Action: Ensure that the indexes for the two tables have indexes which follow this rule For every non-partitioned index for the non-partitioned table, there has to be an identical LOCAL index on the partitioned table and vice versa. By identical, the column position, type and size have to be the same.

ORA-14099 all rows in table do not qualify for specified partition

Cause: There is at least one row in the non-partitioned table which does not qualify for the partition specified in the ALTER TABLE EXCHANGE PARTITION.

Action: Ensure that all the rows in the segment qualify for the partition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that partition to find out the invalid rows and delete them.

ORA-14100 partition extended table name cannot refer to a remote object

Cause: An attempt was made to use partition-extended table name syntax in conjunction with remote object name which is illegal.

Action: Correct the statement and re-enter it.

ORA-14101 partition extended table name cannot refer to a synonym

Cause: An attempt was made to use partition-extended table name syntax in conjunction with synonym name which is illegal.

Action: Correct the statement and re-enter it.

ORA-14102 only one LOGGING or NOLOGGING clause may be specified

Cause: LOGGING was specified more than once, NOLOGGING was specified more than once, or both LOGGING and NOLOGGING were specified.

Action: Remove all but one of the LOGGING or NOLOGGING clauses and reissue the statement.

ORA-14103 LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE

Cause: A statement contained both [NO]LOGGING and [UN]RECOVERABLE clauses which is disallowed.

Action: Remove one of the offending clauses. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.

ORA-14104 RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices

Cause: CREATE TABLE/INDEX statement used to create a partitioned table/index contained RECOVERABLE or UNRECOVERABLE clause which is illegal.

Action: Remove offending clause. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.

ORA-14105 RECOVERABLE/UNRECOVERABLE may not be specified in this context

Cause: RECOVERABLE/UNRECOVERABLE clause is not allowed in this context.

Action: Remove offending clause. RECOVERABLE/UNRECOVERABLE may only be specified in CREATE TABLE/INDEX statement describing a non-partitioned table or index and ALTER INDEX REBUILD statement. [UN]RECOVERABLE is being deprecated in V8 and will be obsoleted in V9. To duplicate semantics of UNRECOVERABLE clause, create an object with NOLOGGING option and then ALTER it specifying LOGGING. To duplicate semantics of RECOVERABLE clause, create an object with LOGGING option.

ORA-14106 LOGGING/NOLOGGING may not be specified for a clustered table

Cause: An attempt was made to specify LOGGING or NOLOGGING clause in CREATE TABLE or ALTER TABLE statement involving a clustered table.

Action: Remove offending clause.

ORA-14107 partition specification is required for a partitioned object

Cause: parameter which supplies partition name is missing. This parameter is optional for non-partitioned objects, but is required for partitioned objects.

Action: Supply the missing parameter.

ORA-14108 illegal partition-extended table name syntax

Cause: Partition to be accessed may only be specified using its name. An attempt was made to use a partition number or a bind variable.

Action: Modify the statement to refer to a partition using its name.

ORA-14109 partition-extended object names may only be used with tables

Cause: An attempt was made to use a partition-extended object name with an object which is not a table.

Action: Avoid using partition-extended name syntax with objects which are not tables.

ORA-14110 partitioning column may not be of type ROWID

Cause: Partitioning column specified by the user was of type ROWID, which is illegal.

Action: Ensure that no partitioning column is of type ROWID.

ORA-14111 creation of GLOBAL partitioned indices on clustered tables is not supported

Cause: An attempt was made to create a GLOBAL partitioned index on a clustered table which is currently illegal.

Action: Remove PARTITION BY RANGE() clause along with (partition_list) to create a GLOBAL non-partitioned index on a clustered table.

ORA-14112 RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition

Cause: Description of a partition or subpartition found in CREATE TABLE/INDEX statement contained RECOVERABLE or UNRECOVERABLE clause which is illegal.

Action: Remove offending clause. Use LOGGING or NOLOGGING instead.

ORA-14113 partitioned table cannot have column with LOB datatype

Cause: An attempt was made to create a partitioned table with a LOB datatype or tried to add a LOB datatype column to a partitioned table.

Action: LOB data types are not supported with partitioned tables. Create table without LOB column or change table to not partitioned. If adding column, do not use LOB datatype. If modifying attributes of a column to change data type to LOB, it has to be a non-partitioned table.

ORA-14114 partitioned table cannot have column with object, REF, nested table, array datatype

Cause: An attempt was made to create a partitioned table with a object datatype (object, REF, nested table, array) or tried to add a object datatype column to a partitioned table.

Action: object data types are not supported with partitioned tables. Create table without object column or change table to not partitioned. If adding column, do not use object datatypes. If modifying attributes of a column to change data type to object, it has to be a non-partitioned table.

ORA-14115 partition bound of partition number string is too long

Cause: Length of linear key representation of a high bound of the partition whose number (partitions are numbered starting with 1) is displayed in this message exceeded the legal limit (4K).

Action: Change representation of a partition high bound to bring its length within legal limit.

ORA-14116 partition bound of partition "string" is too long

Cause: Length of linear key representation of a high bound of the partition whose name (explicitly specified by the user) is displayed in this message exceeded the legal limit (4K).

Action: Change representation of a partition high bound to bring its length within legal limit.

ORA-14117 partition resides in offlined tablespace

Cause: User attempted an operation requiring that we access data in a partition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.

Action: Bring the tablespace online before attempting the operation.

ORA-14118 CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have CHECK constraint defined on them.

Action: Ensure that the two tables do not have CHECK constraint defined on any column.

ORA-14119 specified partition bound is too long

Cause: Length of a linear key representation of a high bound of a table partition being added or along which an existing table or index partition is being split exceeded the legal limit (4K).

Action: Change representation of a partition high bound to bring its length within legal limit.

ORA-14120 incompletely specified partition bound for a DATE column

Cause: An attempt was made to use a date expression whose format does not fully (that is, day, month, and year (including century)) specify a date as a partition bound for a DATE column. The format may have been specified explicitly (using TO_DATE() function) or implicitly (NLS_DATE_FORMAT).

Action: Ensure that date format used in a partition bound for a DATE column supports complete specification of a date (that is, day, month, and year (including century)). If NLS_DATE_FORMAT does not support complete (that is, including the century) specification of the year, use TO_DATE() (for example, TO_DATE('01-01-1999', 'MM-DD-YYYY') to fully express the desired date.

ORA-14121 MODIFY DEFAULT ATTRIBUTES may not be combined with other operations

Cause: ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.

Action: Ensure that MODIFY DEFAULT ATTRIBUTES is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with partitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will.

ORA-14122 only one REVERSE or NOREVERSE clause may be specified

Cause: Both REVERSE and NOREVERSE were specified in CREATE INDEX statement.

Action: Remove all but one of the REVERSE or NOREVERSE clauses and reissue the statement.

ORA-14123 duplicate NOREVERSE clause

Cause: NOREVERSE was specified more than once in ALTER INDEX statement.

Action: Remove all but one of the NOREVERSE clauses and reissue the statement.

ORA-14124 duplicate REVERSE clause

Cause: REVERSE was specified more than once in ALTER INDEX or CREATE INDEX statements.

Action: Remove all but one of the REVERSE clauses and reissue the statement.

ORA-14125 REVERSE/NOREVERSE may not be specified in this context

Cause: REVERSE/NOREVERSE clause is not allowed in this context.

Action: Remove offending clause. REVERSE may be specified as an attribute of an index (not of an individual partition, if creating a partitioned index) in CREATE INDEX statement and ALTER INDEX REBUILD statement. NOREVERSE may be specified only in ALTER INDEX REBUILD statement.

ORA-14126 only a parallel_clause may follow description(s) of resulting partitions

Cause: Descriptions of partition(s) resulting from splitting of a table or index partition may be followed by an optional parallel_clause which applies to the entire statement and which, in turn, may not be followed by any other clause.

Action: Ensure that all partition attributes appear within the parenthesized list of descriptions of resulting partitions in ALTER TABLE/INDEX SPLIT PARTITION statement.

ORA-14128 FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE PARTITION statement have different FOREIGN KEY constraints.

Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation.

ORA-14129 INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints

Cause: Matching UNIQUE constraints in both table are enabled and validated but INCLUDING INDEXES is not specified in ALTER TABLE EXCHANGE PARTITION|SUBPARTITION command.

Action: Disable currently enabled matching UNIQUE constraints on both tables or ensure that INCLUDING INDEXES option is used.

ORA-14130 UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION

Cause: One of the tables named in the ALTER TABLE EXCHANGE PARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and/or validated.

Action: Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE PARTITION statement there is a matching (vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes.

ORA-14131 enabled UNIQUE constraint exists on one of the tables

Cause: One of the tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement has enabled UNIQUE constraint(s) defined on it, which prevents EXCHANGE from proceeding.

Action: Disable constraints defined on tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and retry the statement.

ORA-14132 table cannot be used in EXCHANGE

Cause: An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but the non-partitioned table cannot be used in the EXCHANGE because one or more of the following apply:

it is a typed table
it contains ADT columns
it contains nested-table columns
it contains REF columns
it contains array columns
it is an index-organized table
it contains LOB columns
it is a nested table

Action: Make sure the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command.

ORA-14133 ALTER TABLE MOVE cannot be combined with other operations

Cause: An attempt was made to combine an ALTER TABLE MOVE statement with another operation, such as MODIFY.

Action: Make sure that MOVE is the only operation specified in ALTER TABLE statement.

ORA-14134 indexes cannot use both DESC and REVERSE

Cause: An attempt was made to make a reverse index with some index columns marked DESC.

Action: Do not use DESC in reverse indexes. The rule-based optimizer can scan indexes backwards, which allows a normal reverse index to simulate a reverse index with columns marked DESC.

ORA-14135 a LOB column cannot serve as a partitioning column

Cause: An attempt was made to specify a column of type BLOB or CLOB as a partitioning or subpartitioning column.

Action: Ensure that no partitioning or subpartitioning column is of type BLOB or CLOB.

ORA-14136 ALTER TABLE EXCHANGE restricted by fine-grained security

Cause: User doing exchange does not have full table access due to VPD policies.

Action: Grant exempt priviliges to this user.

ORA-14150 missing SUBPARTITION keyword

Cause: Keyword SUBPARTITION missing.

Action: Supply the missing parameter.

ORA-14151 invalid table partitioning method

Cause: Invalid partitioning method was specified in CREATE TABLE statement. A table may be partitioned by RANGE, HASH, or composite range/hash (R+H).

Action: Specify one of valid partitioning methods.

ORA-14152 invalid number of partitions specified in PARTITIONS clause

Cause: number-of-partitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of partitions outside of legal range (1-65535).

Action: Specify a number between 1 and 65535 in the number-of-partitions clause.

ORA-14153 only one of STORE IN or partition_description clause may be specified

Cause: Both STORE IN and partition_description clauses were specified in a CREATE TABLE|INDEX command.

Action: Remove one of offending clauses.

ORA-14154 only one of STORE IN or subpartition_description clause may be specified

Cause: Both STORE IN and subpartition_description clauses were specified in a CREATE TABLE|INDEX, or ALTER TABLE ADD|SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS command for a composite range-partitioned object.

Action: Remove one of offending clauses.

ORA-14155 missing PARTITION or SUBPARTITION keyword

Cause: Expected either the PARTITION or SUBPARTITION keyword but neither was supplied.

Action: Supply the missing keyword.

ORA-14156 invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause

Cause: Number-of-subpartitions clause contained in CREATE TABLE or CREATE INDEX statement specified a number of subpartitions outside of legal range (1-65535).

Action: Specify a number between 1 and 65535 in the number-of-subpartitions clause.

ORA-14157 invalid subpartition name

Cause: A subpartition name of the form identifier is expected but not present.

Action: Enter an appropriate subpartition name.

ORA-14158 too many subpartition descriptions

Cause: CREATE TABLE or CREATE INDEX contained too many subpartition descriptions; maximum number of subpartitions is 65535.

Action: Reduce the number of subpartitions to not exceed 65535.

ORA-14159 duplicate subpartition name

Cause: Name of a subpartition of a table or index being created is not unique.

Action: Rename the subpartition(s) to ensure that their names are unique among subpartitions of the table or index being created.

ORA-14160 this physical attribute may not be specified for a table subpartition

Cause: An unexpected option was encountered while parsing physical attributes of a table subpartition; TABLESPACE is the only valid option.

Action: Remove the invalid option(s).

ORA-14161 subpartition number string: sum of PCTUSED and PCTFREE may not exceed 100

Cause: The sum of PCTUSED and PCTFREE for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used.

Action: Ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100.

ORA-14162 subpartition "string": sum of PCTUSED and PCTFREE may not exceed 100

Cause: The sum of PCTUSED and PCTFREE for a subpartition whose name (explicitly specified by the user) is displayed in this message exceeds 100. Note that if PCTUSED and/or PCTFREE values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default PCTUSED and/or PCTFREE values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used.

Action: Ensure that a sum of PCTUSED and PCTFREE for the subpartition does not exceed 100.

ORA-14163 subpartition number string: INITRANS value must be less than MAXTRANS value

Cause: The value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose number (subpartitions are numbered starting with 1) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used.

Action: Ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS.

ORA-14164 subpartition "string": INITRANS value must be less than MAXTRANS value

Cause: The value of INITRANS was found to be greater than that of MAXTRANS for a subpartition whose name (explicitly specified by the user) is displayed in this message. Note that if INITRANS and/or MAXTRANS values for this subpartition were not specified explicitly, default values at partition-level would be used. If, in turn, default INITRANS and/or MAXTRANS values at partition-level were not specified, default values for the partitioned table or index would be used. If those values were also not specified explicitly, system defaults would be used.

Action: Ensure that value of INITRANS (whether specified explicitly or derived from the default value at partition-level, table-level or index-level) is no greater than that of MAXTRANS.

ORA-14165 MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations

Cause: An ALTER TABLE or ALTER INDEX statement attempted to combine MODIFY DEFAULT ATTRIBUTES OF PARTITION with some other operation (for example, ADD PARTITION or PCTFREE) which is illegal.

ORA-14166 missing INTO keyword

Cause: Keyword INTO missing.

Action: Supply the missing keyword.

ORA-14167 only one subpartition may be moved

Cause: ALTER TABLE MOVE SUBPARTITION contained descriptions of more than one subpartition to be moved.

Action: Ensure that the statement describes exactly one subpartition to be moved and that it does not contain any commas.

ORA-14168 only one subpartition may be modified

Cause: ALTER TABLE|INDEX MODIFY SUBPARTITION contained descriptions of more than one subpartition to be modified.

Action: Ensure that the statement describes exactly one subpartition to be modified and that it does not contain any commas.

ORA-14169 invalid ALTER TABLE MODIFY SUBPARTITION option

Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION statement.

Action: Specify only legal options.

ORA-14170 cannot specify partition_description clause in CREATE TABLE|INDEX

Cause: User requested to generate default partition description(s) (possibly via PARTITIONS number_of_partitions) while at the same time specified partition_description clause which is illegal.

Action: Remove one of offending clauses.

ORA-14171 cannot specify subpartition_description clause in CREATE|ALTER TABLE

Cause: User requested to generate default subpartition description(s) (possibly via SUBPARTITIONS) while at the same time specified subpartition_description clause which is illegal.

Action: Remove one of offending clauses.

ORA-14172 invalid ALTER TABLE EXCHANGE SUBPARTITION option

Cause: Name of the table to be EXCHANGED has to be followed by [{INCLUDING|EXCLUDING} INDEX][{WITH|WITHOUT} VALIDATION].

Action: Ensure that no options besides INCLDING INDEX or EXCLUDING INDEX are specified with ALTER TABLE EXCHANGE SUBPARTITION.

ORA-14173 illegal subpartition-extended table name syntax

Cause: Subpartition to be accessed may only be specified using its name. An attempt was made to use a subpartition number or a bind variable.

Action: Modify statement to refer to a subpartition using its name.

ORA-14174 only a parallel_clause may follow COALESCE PARTITION|SUBPARTITION

Cause: ALTER TABLE COALESCE PARTITION|SUBPARTITION may be followed by an optional parallel_clause. No partition/subpartition attributes may be specified.

Action: Ensure that no partition/subpartition attribute was specified.

ORA-14175 a subpartition maintenance operation may not be combined with other operations

Cause: An ALTER TABLE or ALTER INDEX statement attempted to combine a subpartition maintenance operation (for example, MOVE SUBPARTITION) with some other operation (for example, MODIFY PARTITION ADD SUBPARTITION or PCTFREE) which is illegal.

Action: Ensure that a subpartition maintenance operation is the sole operation specified in ALTER TABLE or ALTER INDEX statement; operations other than those dealing with subpartitions, default attributes of partitioned tables/indices or specifying that a table be renamed (ALTER TABLE RENAME) may be combined at will.

ORA-14176 this attribute may not be specified for a hash partition

Cause: An invalid option was encountered while parsing physical attributes of a partition of a table partitioned using the HASH method. The TABLESPACE option is the only valid option for such partitions.

Action: Remove the invalid option(s).

ORA-14177 STORE-IN (Tablespace list) can only be specified for a LOCAL index on a table which is hash or composite partitioned

Cause: STORE-IN (Tablespace list) clause was used while creating a local index on a table which is range or list partitioned.

Action: Do not use the STORE_IN (Tablespace list) clause while creating a local index on range or list partitioned table.

ORA-14183 TABLESPACE DEFAULT can be specified only for Composite LOCAL index

Cause: An attempt was made to specify TABLESPACE DEFAULT for a partition of a range/system/hash-partitioned LOCAL index object, which is illegal.

Action: Replace TABLESPACE DEFAULT with TABLESPACE ts_name or remove it.

ORA-14185 incorrect physical attribute specified for this index partition

Cause: An unexpected option was encountered while parsing physical attributes of a local index partition; valid options for range composite range partitions are INITRANS, MAXTRANS, TABLESPACE, STORAGE, PCTFREE, PCTUSED, LOGGING and TABLESPACE; but only TABLESPACE may be specified for hash partitions STORE IN () is also disallowed for all but composite range partitions.

Action: Remove the invalid option(s) from the list of physical attributes of an index partition.

ORA-14186 number of sub-partitions of LOCAL index must equal that of the underlying table

Cause: An attempt was made to create a LOCAL partitioned index with a number of subpartitions which is different from that of the underlying table.

Action: Correct the CREATE INDEX statement to specify a correct number of subpartitions.

ORA-14187 partitioning method for LOCAL index is inconsistent with that of the underlying table

Cause: An attempt was made to create a LOCAL partitioned index that is not equipartitioned with the underlying table. The partitioning types are mismatched.

Action: Correct the CREATE INDEX statement to ensure that the index partitioning method is consistent with that of the base table.

ORA-14188 sub-partitioning columns must form a subset of key columns of a UNIQUE index

Cause: An attempt was made to create a UNIQUE partitioned index whose subpartitioning columns do not form a subset of its key columns which is illegal.

Action: If you want to create an index whose subpartitioning columns do not form a subset of its key columns, it must be created as non-UNIQUE; otherwise, correct the list of key and/or subpartitioning columns to ensure that the index's subpartitioning columns form a subset of its key columns.

ORA-14189 this physical attribute may not be specified for an index subpartition

Cause: An unexpected option was encountered while parsing physical attributes of an index subpartition; TABLESPACE is the only valid option.

Action: Remove the invalid option(s).

ORA-14190 only one ENABLE/DISABLE ROW MOVEMENT clause can be specified

Cause: One of the following:

ENABLE ROW MOVEMENT was specified more than once.
DISABLE ROW MOVEMENT was specified more than once.
Both ENABLE ROW MOVEMENT and DISABLE ROW MOVEMENT were specified.

Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses and then reissue the command.

ORA-14191 ALLOCATE STORAGE may not be specified for Composite Range partitioned object

Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal.

Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement.

ORA-14192 cannot modify physical index attributes of a Hash index partition

Cause: An attempt was made to modify one of INITRANS/MAXTRANS/LOGGING/STORAGE clause for an index partition of a hash-partitioned index.

Action: Remove the physical attributes one is trying to modify.

ORA-14193 invalid ALTER INDEX MODIFY SUBPARTITION option

Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement.

Action: Specify only legal options.

ORA-14194 only one subpartition may be rebuilt

Cause: ALTER INDEX REBUILD SUBPARTITION contained descriptions of more than one subpartition to be rebuilt.

Action: Ensure that the statement describes exactly one subpartition to be rebuilt and that it does not contain any commas.

ORA-14195 ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object

Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE/ALTER INDEX statement issued against a range-partitioned index which is illegal.

Action: Remove the illegal option. If it is desired to add storage to individual partitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE/INDEX MODIFY PARTITION statement.

ORA-14251 Specified subpartition does not exist

Cause: Subpartition not found for the object.

Action: Retry with correct subpartition name.

ORA-14252 invalid ALTER TABLE MODIFY PARTITION option for a Hash partition

Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in ALTER TABLE MODIFY PARTITION for a hash partition.

Action: Specify only legal options.

ORA-14253 table is not partitioned by Composite Range method

Cause: The table in a subpartition maintenance operation (ALTER TABLE EXCHANGE/MODIFY/MOVE/TRUNCATE SUBPARTITION, or ALTER TABLE MODIFY PARTITION ADD/COALESCE SUBPARTITION command must be partitioned by composite range method.

Action: Ensure that the table is partitioned by composite range method.

ORA-14254 cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table

Cause: User specified ALLOCATE STORAGE clause in ALTER TABLE statement issued against a range or composite range partitioned table which is illegal.

Action: Remove the illegal option. If it is desired to add storage to individual partitions/subpartitions, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION/SUBPARTITION statement. If it is desired to add storage to all subpartitions of a Composite partition, ALLOCATE STORAGE clause may be specified with ALTER TABLE MODIFY PARTITION.

ORA-14255 table is not partitioned by Range or Composite Range or List method

Cause: ALTER TABLE SPLIT/DROP PARTITION or ALTER TABLE MERGE PARTITIONS command is only valid for table partitioned by range, list, or composite range method.

Action: Ensure that the table is partitioned by range, list, or composite range method.

ORA-14256 invalid resulting partition description(s)

Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or subpartition_description clause in partition description(s) in ALTER TABLE SPLIT PARTITION or ALTER TABLE MERGE PARTITIONS statement but the table in the maintenance operation is not a composite range-partitioned table which is illegal.

Action: Remove the invalid clause(s), or ensure that the table is partitioned by composite range method.

ORA-14257 cannot move partition other than a Range or Hash partition

Cause: An attempt was made to move a partition that is not a range or hash partition which is illegal.

Action: Specify MOVE PARTITION for a range or hash partition only.

ORA-14258 invalid partition description

Cause: User specified STORE-IN clause, SUBPARTITIONS clause, and/or subpartition_description clause in ALTER TABLE ADD PARTITION statement but the table in the maintenance operation is not a composite range/hash-partitioned table which is illegal.

Action: Remove the invalid clause(s), or ensure that the table is partitioned by composite range/hash method.

ORA-14259 table is not partitioned by Hash method

Cause: ALTER TABLE COALESCE PARTITION is only valid for table partitioned by Hash method.

Action: Specify a valid ALTER TABLE option for the table, or ensure that the table is partitioned by Hash method.

ORA-14260 incorrect physical attribute specified for this partition

Cause: User specified INITRANS, MAXTRANS, STORAGE, PCTFREE, PCTUSED, and/or [NO]LOGGING option to a hash partition via ALTER TABLE ADD/MOVE PARTITION command which is illegal. Only TABLESPACE may be specified.

Action: Remove the invalid option(s).

ORA-14261 partition bound may not be specified when adding this Hash partition

Cause: User specified VALUES LESS THAN clause when adding a partition (via ALTER TABLE ADD PARTITION) to a hash-partitioned table which is illegal.

Action: Remove the VALUES LESS THAN clause from the description of partition being added.

ORA-14262 new subpartition name must differ from the old subpartition name

Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying new_subpartition_name which is identical to the name of the subpartition being renamed.

Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index.

ORA-14263 new subpartition name must differ from that of any other subpartition of the object

Cause: User entered ALTER TABLE/INDEX RENAME SUBPARTITION specifying new_subpartition_name which is identical to the name of some existing subpartition of the object.

Action: Ensure that the new subpartition name is different from the name of any (including the one being renamed) existing subpartition of a given table or index.

ORA-14264 table is not partitioned by Composite Range method

Cause: The table in the MODIFY DEFAULT ATTRIBUTES FOR PARTITION operation is partitioned by method other than Composite method.

Action: Ensure that the table is partitioned by Composite method.

ORA-14265 data type or length of a table subpartitioning column may not be changed

Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition the table named in ALTER TABLE statement, which is illegal.

Action: Avoid modifying data type and/or length of table subpartitioning column(s).

ORA-14266 data type or length of an index subpartitioning column may not be changed

Cause: User issued ALTER TABLE statement attempting to modify data type and/or length of a column used to subpartition some index defined on the table named in ALTER TABLE statement, which is illegal.

Action: Avoid modifying data type and/or length of index subpartitioning column(s).

ORA-14267 cannot specify PARALLEL clause when adding a (Composite) Range partition

Cause: User issued ALTER TABLE ADD PARTITION statement with PARALLEL clause for a range or composite range partition which is illegal.

Action: Remove the PARALLEL clause.

ORA-14268 subpartition 'string' of the partition resides in offlined tablespace

Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indices defined on it or is referenced by a constraint.

Action: Bring tablespace online before attempting the operation.

ORA-14269 cannot exchange partition other than a Range or Hash partition

Cause: User attempt to exchange a partition with a non-partitioned table but the specified partition is not a range or hash partition which is illegal.

Action: Specify EXCHANGE PARTITION for a range or hash partition only.

ORA-14270 table is not partitioned by Range or Hash or List method

Cause: The table in ALTER TABLE MODIFY PARTITION {UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES} statement is not partitioned by range or hash method which is illegal.

Action: Ensure that the table is partitioned by range or hash method.

ORA-14271 table is not partitioned by Composite Range method

Cause: The table in ALTER TABLE MODIFY SUBPARTITION {UNUSABLE LOCAL INDEXES | REBUILD UNUSABLE LOCAL INDEXES} statement is not partitioned by composite range method which is illegal.

Action: Ensure that the table is partitioned by composite range method.

ORA-14272 only a partition with higher bound can be reused

Cause: User attempt to reuse a lower-bound partition in ALTER TABLE MERGE PARTITIONS statement as the resulting partition which is illegal.

Action: Use the higher-bound partition to be the resulting partition or specify a new partition name.

ORA-14273 lower-bound partition must be specified first

Cause: User specified higher-bound partition before lower-bound partition in ALTER TABLE MERGE PARTITIONS statement which is illegal.

Action: Specify lower-bound partition then higher-bound partition.

ORA-14274 partitions being merged are not adjacent

Cause: User attempt to merge two partitions that are not adjacent to each other which is illegal.

Action: Specify two partitions that are adjacent.

ORA-14275 cannot reuse lower-bound partition as resulting partition

Cause: User attempt to reuse lower-bound partition of the partitions being merged which is illegal.

Action: Specify new resulting partition name or reuse the higher-bound partition only.

ORA-14276 EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table

Cause: The table in the ALTER TABLE EXCHANGE SUBPARTITION operation is either clustered or partitioned.

Action: Ensure that the table with which the subpartition is being exchanged for is not partitioned or clustered.

ORA-14277 tables in EXCHANGE SUBPARTITION must have the same number of columns

Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have different number of columns.

Action: Ensure that the two tables have the same number of columns with the same type and size.

ORA-14278 column type or size mismatch in EXCHANGE SUBPARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION are of different type or size.

Action: Ensure that the two tables have the same number of columns with the same type and size.

ORA-14279 index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION

Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION have indexes which are not equivalent.

ORA-14280 all rows in table do not qualify for specified subpartition

Cause: There is at least one row in the non-partitioned table which does not qualify for the subpartition specified in the ALTER TABLE EXCHANGE SUBPARTITION.

Action: Ensure that all the rows in the segment qualify for the subpartition. Perform the alter table operation with the NO CHECKING option. Run ANALYZE table VALIDATE on that subpartition to find out the invalid rows and delete them.

ORA-14281 CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have CHECK constraint defined on them.

Action: Ensure that the two tables do not have CHECK constraint defined on any column.

ORA-14282 FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE SUBPARTITION statement have different FOREIGN KEY constraints.

Action: Ensure that the two tables do not have FOREIGN KEY constraints defined on any column or disable all FOREIGN KEY constraints on both tables. Then retry the operation.

ORA-14283 UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION

Cause: One of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and/or validated.

Action: Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE SUBPARTITION statement there is a matching (vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes.

ORA-14284 one or more of table's subpartitions reside in a read-only tablespace

Cause: User issued ALTER TABLE statement attempting to modify an existing VARCHAR2 (or VARCHAR) column to be of type CHAR (or CHARACTER), increase length of an existing CHAR (or CHARACTER) column, or add a column with user-specified default for a table one or more subpartitions of which reside in read-only tablespaces, which is illegal.

Action: Avoid performing aforementioned operations on a partitioned table one or more subpartitions of which reside in read-only tablespaces.

ORA-14285 cannot COALESCE the only partition of this partitioned table

Cause: A COALESCE PARTITION command was issued when there is only one partition in the table which is illegal.

Action: Ensure that there is at least one partition. Drop table to remove all partitions.

ORA-14286 cannot COALESCE the only subpartition of this table partition

Cause: A COALESCE SUBPARTITION command was issued when there is only one subpartition in the partition which is illegal.

Action: Ensure that there is at least one subpartition. Drop partition to remove all subpartitions.

ORA-14287 cannot REBUILD a partition of a Composite Range partitioned index

Cause: An attempt was made to rebuild a partition of a composite range-partitioned index which is illegal.

Action: REBUILD the index partition, a subpartition at a time.

ORA-14288 index is not partitioned by Composite Range method

Cause: The index in a partition or subpartition maintenance operation (ALTER INDEX MODIFY [SUBPARTITION|DEFAULT ATTRIBUTES FOR PARTITION] or ALTER INDEX REBUILD SUBPARTITION command must be partitioned by composite range method.

Action: No action required.

ORA-14289 cannot make local index partition of Composite Range partitioned table unusable

Cause: An attempt was made to rebuild a partition of a composite range partitioned index which is illegal.

Action: No action required.

ORA-14290 PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

Cause: The corresponding columns in the tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement have different PRIMARY KEY constraints.

Action: Ensure that the two tables do not have PRIMARY KEY constraints defined on any column or disable all PRIMARY KEY constraints on both tables. Then retry the operation.

ORA-14291 cannot EXCHANGE a composite partition with a non-partitioned table

Cause: A composite partition can only be exchanged with a partitioned table.

Action: Ensure that the table being exchanged is partitioned or that that the partition being exchanged is non-composite.

ORA-14292 Partitioning type of table must match subpartitioning type of composite partition

Cause: When exchanging a partitioned table with a composite partition, the partitioning type of the table must match the subpartitioning type of the composite partition.

Action: Ensure that the partitioning type of partitioned table is the same as the subpartitioning type of the composite partition.

ORA-14293 Number of partitioning columns does not match number of subpartitioning columns

Cause: When exchanging a partitioned table with a composite partition, the number of partitioning columns of the table must match the number of subpartitioning columns of the composite partition.

Action: Ensure that the number of partitioning columns in the partitioned table is the same as the number of subpartitioning columns in the composite partition.

ORA-14294 Number of partitions does not match number of subpartitions

Cause: When exchanging a partitioned table with a composite partition, the number of partitions of the table must match the number of subpartitions of the composite partition.

Action: Ensure that the number of partitions in the partitioned table is the same as the number of subpartitions in the the composite partition.

ORA-14295 column type or size mismatch between partitioning columns and subpartitioning columns

Cause: When exchanging a partitioned table with a composite partition, the type and size of the partitioning columns of the table must match the type and size of the subpartitioning columns of the composite partition.

Action: Ensure that the type and size of the partitioning columns of the partitioned is the same as the type and size of the subpartitioning columns of the composite partition.

ORA-14296 Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

Cause: The block sizes of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different. For index organized tables, either the block sizes of the index or the overflow (or both) do not match.

Action: Ensure that the block sizes of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same. For index organized tables, ensure that the block sizes of both the index and the overflow of the two tables match.

ORA-14297 Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

Cause: The block sizes of a pair of indexes being exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.

Action: Ensure that the block sizes of the corresponding pairs of indexes that need to be exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.

ORA-14298 LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

Cause: The block sizes of a pair of corresponding LOB columns of the two tables specified in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.

Action: Ensure that the block sizes of corresponding pairs of LOB columns of the tables involved in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.

ORA-14301 table-level attributes must be specified before partition-level attributes

Cause: While processing an ALTER TABLE ADD COLUMN statement, table-level attributes of LOB columns were encountered after processing partition-level attributes of LOB columns or while processing CREATE TABLE statement, table-level attributes of LOB columns were encountered after processing partition descriptions.

Action: Modify the SQL statement to specify table-level attributes prior to partition-level attributes or partition descriptions; then retry the statement.

ORA-14302 only one list of added-LOB-storage-clauses can be specified in a statement

Cause: While parsing an ALTER TABLE ADD COLUMN statement, one list of added-LOB-storage-clauses was parsed when another list of added-LOB-storage-clauses was encountered. There cannot be more than one list of added-LOB-storage-clauses in a statement; all added-LOB-storage-clauses must be combined into one list.

Action: Combine all of the lists of added-LOB-storage-clauses into one list and retry the statement.

ORA-14303 partitions or subpartitions are not in the right order

Cause: Descriptions of partitions or subpartitions in an ALTER TABLE ADD COLUMN statement were ordered differently from the DDL order of partitions or subpartitions.

Action: Re-order the partitions or subpartitions in the added LOB storage clause by partition or subpartition DDL order, and retry the statement.

ORA-14304 List partitioning method expects a single partitioning column

Cause: Number of columns in a partitioning column list exceeded the legal limit of 1 for list partitioned objects.

Action: Modify partitioning column list so that it consists of at most 1 column.

ORA-14305 List value 'string' specified twice in partition 'string'

Cause: A list value cannot be specified more that once.

Action: Remove one of the specifications of the value.

ORA-14306 List value 'string' specified twice in partitions 'string', 'string'

Cause: A list value cannot be specified more that once.

Action: Remove one of the specifications of the value.

ORA-14307 partition contains too many list values

Cause: Partition list contains more than 65535 list values.

Action: Reduce the number of values to not exceed 65535 values.

ORA-14308 partition bound element must be one of: string, datetime or interval literal, number, or NULL

Cause: Partition bound list contained an element of invalid type (i.e. not a number, non-empty string, datetime or interval literal, or NULL).

Action: Ensure that all elements of partition bound list are of valid type.

ORA-14309 Total count of list values exceeds maximum allowed

Cause: Partitioned object contains more than 65535 list values.

Action: Reduce number of values to less than 65535.

ORA-14310 VALUES LESS THAN or AT clause cannot be used with List partitioned tables

Cause: VALUES LESS THAN or AT clause can be used only with range partitioned tables.

Action: Use VALUES () clause with list partitioned tables.

ORA-14311 Expecting VALUES LESS THAN or AT clause

Cause: VALUES () clause can be used only with list partitioned tables.

Action: Use VALUES LESS THAN clause with range partitioned tables.

ORA-14312 Value string already exists in partition string

Cause: One of the list values in the ADD PARTITION or ADD VALUES statement already exists in another partition.

Action: Remove the duplicate value from the statement and try again.

ORA-14313 Value string does not exist in partition string

Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the partition.

Action: Remove the value from the statement and try again.

ORA-14314 resulting List partition(s) must contain atleast 1 value

Cause: After a SPLIT/DROP VALUE of a list partition, each resulting partition(as applicable) must contain at least 1 value.

Action: Ensure that each of the resulting partitions contains at least 1 value.

ORA-14315 cannot merge a partition with itself

Cause: The same partition name was specified twice for the merge operation.

Action: Re-submit operation with 2 distinct partition names.

ORA-14316 table is not partitioned by List method

Cause: ALTER TABLE ADD|DROP VALUES can only be performed on list partitioned objects.

Action: reissue the command against a list partitoned object.

ORA-14317 cannot drop the last value of partition

Cause: ALTER TABLE DROP VALUES tried to drop the last value of the partition.

Action: Cannot execute the command, unless two or more values exist for partition.

ORA-14318 DEFAULT partition must be last partition specified

Cause: A partition description follows the one describing the default partition.

Action: Ensure that the DEFAULT partition is the last partition description.

ORA-14319 DEFAULT cannot be specified with other values

Cause: DEFAULT keyword has been specified along with other values when specifying the values for a list partition.

Action: Ensure that if DEFAULT is specified, it is the only value specified.

ORA-14320 DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT

Cause: DEFAULT keyword has been specified when performing an ADD VALUES, DROP VALUES, SPLIT partition, or subpartition.

Action: Ensure that DEFAULT is not specified for ADD/DROP VALUES or SPLIT partition/subpartition operations.

ORA-14321 cannot add/drop values to DEFAULT partition

Cause: An ADD/DROP VALUES operation is being performed on the default partition.

Action: Ensure that ADD/DROP VALUES is not performed on the DEFAULT partition.

ORA-14322 DEFAULT partition already exists

Cause: A partition already exists with DEFAULT value.

ORA-14323 cannot add partition when DEFAULT partition exists

Cause: An ADD PARTITION operation cannot be executed when a partition with DEFAULT values exists.

Action: Issue a SPLIT of the DEFAULT partition instead.

ORA-14324 values being added already exist in DEFAULT partition

Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT partition.

Action: Issue a SPLIT of the DEFAULT partition and then MERGE the split partition into the partition to which values need to be added.

ORA-14400 inserted partition key does not map to any partition

Cause: An attempt was made to insert a record into, a range or composite range object, with a concatenated partition key that is beyond the concatenated partition bound list of the last partition -OR- an attempt was made to insert a record into a list object with a partition key that did not match the literal values specified for any of the partitions.

Action: Do not insert the key. Or, add a partition capable of accepting the key. Or, add values matching the key to a partition specification.

ORA-14401 inserted partition key is outside specified partition

Cause: The concatenated partition key of an inserted record is outside the ranges of the two concatenated partition bound lists that delimit the partition named in the INSERT statement.

Action: Do not insert the key or insert it in another partition.

ORA-14402 updating partition key column would cause a partition change

Cause: An UPDATE statement attempted to change the value of a partition key column causing migration of the row to another partition.

Action: Do not attempt to update a partition key column or make sure that the new partition key is within the range containing the old partition key.

ORA-14403 cursor invalidation detected after getting DML partition lock

Cause: Cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement.

Action: No action required.

ORA-14404 partitioned table contains partitions in a different tablespace

Cause: An attempt was made to drop a tablespace which contains tables whose partitions are not completely contained in this tablespace.

Action: Find tables with partitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move partitions to a different tablespace.

ORA-14405 partitioned index contains partitions in a different tablespace

Cause: An attempt was made to drop a tablespace which contains indexes whose partitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace.

Action: Find indexes with partitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them.

ORA-14406 updated partition key is beyond highest legal partition key

Cause: At attempt was made to update a record with a concatenated partition key that is beyond the concatenated partition bound list of the last partition.

Action: Do not update the key. Or, add a partition capable of accepting the key.

ORA-14407 partitioned table contains subpartitions in a different tablespace

Cause: An attempt was made to drop a tablespace which contains tables whose subpartitions are not completely contained in this tablespace.

Action: Find tables with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these tables or move subpartitions to a different tablespace.

ORA-14408 partitioned index contains subpartitions in a different tablespace

Cause: An attempt was made to drop a tablespace which contains indexes whose subpartitions are not completely contained in this tablespace, and which are defined on the tables which are completely contained in this tablespace.

Action: Find indexes with subpartitions which span the tablespace being dropped and some other tablespace(s). Drop these indexes, or move the index partitions to a different tablespace, or find the tables on which the indexes are defined, and drop (or move) them.

ORA-14409 inserted partition key is outside specified subpartition

Cause: The concatenated partition key of an inserted record is outside the ranges of the two concatenated subpartition bound lists that delimit the subpartition named in the INSERT statement.

Action: Do not insert the key or insert it in another subpartition.

ORA-14450 attempt to access a transactional temp table already in use

Cause: An attempt was made to access a transactional temporary table that has been already populated by a concurrent transaction of the same session.

Action: Do not attempt to access the temporary table until the concurrent transaction has committed or aborted.

ORA-14451 unsupported feature with temporary table

Cause: An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause.

Action: No action required.

ORA-14452 attempt to create, alter or drop an index on temporary table already in use

Cause: An attempt was made to create, alter or drop an index on temporary table which is already in use.

Action: All the sessions using the session-specific temporary table have to truncate table and all the transactions using transaction specific temporary table have to end their transactions.

ORA-14453 attempt to use a LOB of a temporary table, whose data has already been purged

Cause: An attempt was made to use LOB from a temporary table whose data has been dropped either because table was transaction-specific and transaction has committed or aborted, table was truncated or session which created this LOB has ended.

Action: This LOB locator is invalid and cannot be used.

ORA-14454 attempt to reference temporary table in a referential integrity constraint

Cause: An attempt was made to reference temporary table in a referential integrity constraint. This is not supported.

Action: Use triggers.

ORA-14455 attempt to create referential integrity constraint on temporary table

Cause: An attempt was made to create a referential integrity constraint on a temporary table. This is not supported.

Action: Use triggers.

ORA-14456 cannot rebuild index on a temporary table

Cause: An attempt was made to rebuild an index on a temporary table.

Action: The index data is anyway lost at end of session/transaction.

ORA-14457 disallowed VARRAY and Nested Table column in a Temporary table

Cause: An attempt made to create a VARRAY or Nested Table column in a temporary table. This is not supported.

Action: Do not specify these datatypes for temporary tables.

ORA-14458 attempt was made to create a temporary table with INDEX organization

Cause: An attempt was made to create an Index Organized Temporary table. This is not supported.

Action: Create the table with HEAP organization and the primary key.

ORA-14459 missing GLOBAL keyword

Cause: Keyword GLOBAL is missing while creating temporary table.

Action: Supply the missing keyword.

ORA-14460 only one COMPRESS or NOCOMPRESS clause may be specified

Cause: COMPRESS was specified more than once, NOCOMPRESS was specified more than once, or both COMPRESS and NOCOMPRESS were specified.

Action: Specify each desired COMPRESS or NOCOMPRESS clause option only once.

ORA-14500 LOCAL option not valid without partition name

Cause: Incorrect syntax specified.

Action: Retry the command.

ORA-14501 object is not partitioned

Cause: Table or index is not partitioned. Invalid syntax.

Action: Retry the command with correct syntax.

ORA-14503 only one partition name can be specified

Cause: More than one partition name has been specified for analyze.

Action: Specify one partition name.

ORA-14504 syntax not supported for analyze

Cause: A partition/subpartition number or bind variable has been used.

Action: Specify a valid partition/subpartition name.

ORA-14505 LOCAL option valid only for partitioned indexes

Cause: Incorrect syntax specified.

Action: Retry the command.

ORA-14506 LOCAL option required for partitioned indexes

Cause: Incorrect syntax specified.

Action: Retry the command.

ORA-14507 partition corrupt. all rows do not fall within partition bounds

Cause: The partition contains rows which should really be in some other partition. Possibly due to an exchange partition without validation.

Action: Delete rows in partition which do not qualify.

ORA-14508 specified VALIDATE INTO table not found

Cause: The specified table either does not exist or user does not have the proper privileges.

Action: Specify the correct table to use.

ORA-14509 specified VALIDATE INTO table form incorrect

Cause: The specified table does not have the proper field definitions.

Action: Specify the correct table to use. See UTLVALID.SQL for more information.

ORA-14510 can specify VALIDATE INTO clause only for partitioned tables

Cause: The VALIDATE INTO has been specified for a non-partitioned table or cluster or index.

Action: Use the syntax correctly.

ORA-14511 cannot perform operation on a partitioned object

Cause: An attempt was made to perform an operation that is not allowed on partitioned tables or indexes.

Action: Retry the command with correct syntax.

ORA-14512 cannot perform operation on a clustered object

Cause: An attempt was made to perform an operation that is not allowed on clustered tables or indexes.

Action: Retry the command with correct syntax.

ORA-14513 partitioning column may not be of object datatype

Cause: Partitioning column specified by the user was an object datatype (object, REF, nested table, array) which is illegal.

Action: Ensure that no partitioning column is an object datatype.

ORA-14514 LOCAL option not valid without subpartition name

Cause: Incorrect syntax specified.

Action: Retry the command.

ORA-14515 only one aubpartition name can be specified

Cause: More than one subpartition name has been specified for analyze.

Action: Specify one subpartition name.

ORA-14516 subpartition corrupt. all rows do not fall within subpartition bounds

Cause: The subpartition contains rows which should really be in some other subpartition. Possibly due to an exchange subpartition without validation.

Action: Delete rows in subpartition which do not qualify.

ORA-14517 subpartition of index 'string.string' is in unusable state

Cause: An attempt has been made to access an index subpartition that has been marked unusable by a direct load or by a DDL operation.

Action: REBUILD the unusable index subpartition.

ORA-14518 partition contains rows corresponding to values being dropped

Cause: A table partition contains rows for the values being dropped.

Action: DELETE all rows for the values being dropped and reissue statement.

ORA-14519 Conflicting tablespace blocksizes for string string: Tablespace string block size string [string] conflicts with previously specified/implied tablespace string block size string [string]

Cause: An attempt has been made to create a partitioned object in a manner that would require the partitioned object to span tablespaces of more than one block size.

Action: Ensure that all tablespaces specified in the DDL command for the given object as well as any tablespaces implicitly assigned to partitions or subpartitions of the object being created are all of the same block size.

ORA-14520 Tablespace string block size [string] does not match existing object block size [string]

Cause: A DDL statement was issued that would require a tablespace of a block size different from the block size of the specified partitioned object to be assigned either: (1) As the object's default tablespace (or one of the object's partition-level default tablespaces, if composite partitioning is being used) OR (2) To one of the object's partitions/subpartitions.

Action: Specify a tablespace of the same block size as the partitioned object.

ORA-14521 Default tablespace string block size [string] for string string does not match existing string block size [string]

Cause: A DDL statement was issued that would require creation of a new partition/subpartition in the object-level default tablespace of an existing partitioned object. However, the object-level default tablespace block size does not match the block size of the partitioned object.

Action: Either (1) Modify the default tablespace of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created.

ORA-14522 Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]

Cause: A DDL statement was issued that would require creation of a new subpartition in one of the partition-level default tablespaces of an existing composite partitioned object. However, the partition-level default tablespace block size does not match the block size of the partitioned object.

Action: Either (1) Modify the partition-level default tablespace of the appropriate partition of the partitioned object to a tablespace of the same block size as the object and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new subpartitions being created.

ORA-14523 Cannot co-locate [sub]partition of string string with table [sub]partition because string block size [string] does not match table block size [string]

Cause: A DDL statement was issued that would require a partition/subpartition of a local index/LOB column to be co-located with the corresponding partition/subpartition of the base table. However, this is not possible because the block sizes of the table and the LOB column/local index are different.

Action: Either (1) Specify an object-level default tablespace (or partition-level default tablespace for the appropriate partition, if composite partitioning is used) for the partitioned local index/LOB column and then retry the DDL command, OR (2) Ensure that tablespaces of the correct block size are specified for all new partitions/subpartitions being created. Also ensure that neither of TABLESPACE DEFAULT and STORE IN (DEFAULT) is specified for a local index whose block size does not match that of the base table.

ORA-14551 cannot perform a DML operation inside a query

Cause: DML operation like insert, update, delete or select-for-update cannot be performed inside a query or under a PDML slave.

Action: Ensure that the offending DML operation is not performed or use an autonomous transaction to perform the DML operation within the query or PDML slave.

ORA-14552 cannot perform a DDL, commit or rollback inside a query or DML

Cause: DDL operations like creation tables, views etc. and transaction control statements such as commit/rollback cannot be performed inside a query or a DML statement.

Action: Ensure that the offending operation is not performed or use autonomous transactions to perform the operation within the query/DML operation.

ORA-14553 cannot perform a lob write operation inside a query

Cause: A LOB write operation cannot be performed inside a query or a PDML slave.

Action: Ensure that the offending LOB write operation is not performed or use an autonomous transaction to perform the operation within the query or PDML slave.

ORA-14601 Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template

Cause: Cannot specify these clauses while specifying a template.

Action: Correct the subpartition template clause.

ORA-14602 SUBPARTITION TEMPLATE is legal only for a composite partitioned table

Cause: SUBPARTITION TEMPLATEs can only be specified for composite partitioned tables.

Action: Do not use SUBPARTITION TEMPLATEs on non-partitioned or non-composite partitioned tables.

ORA-14603 [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables

Cause: This syntax is valid only if subpartitioning dimension is hash.

ORA-14604 During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified

Cause: Once a subpartition template has been specified during CREATE TABLE, it is illegal to specify SUBPARTITIONS or STORE IN anywhere else.

Action: Remove either SUBPARTITIONS or STORE IN, or remove the SUBPARTITION TEMPLATE clause.

ORA-14605 Name missing for subpartition / lob segment in template

Cause: A subpartition / lob segment was not specified a name in the template descriptions.

Action: All subpartitions / lob segments must have names specified in the template.

ORA-14606 Tablespace was specified for previous subpartitions in template but is not specified for string

Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions.

Action: Either specify tablespaces for all or for none of the subpartitions.

ORA-14607 Tablespace was not specified for previous subpartitions in template but is specified for string

Cause: Tablespaces may either be specified for all subpartitions or must not be specified for any subpartitions.

Action: Either specify tablespaces for all or for none of the subpartitions.

ORA-14608 Tablespace was specified for the previous lob segments of column string in template but is not specified for string

Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column.

Action: Either specify tablespaces for all or for none of the lob segments.

ORA-14609 Tablespace was not specified for the previous lob segments of column string in template but is specified for string

Cause: Tablespaces may either be specified for all lob segments of a column or must not be specified for any lob segments of this column.

Action: Either specify tablespaces for all or for none of the lob segments.

ORA-14610 Lob attributes not specified for lob column string for subpartition string

Cause: Lob attributes of a column must be specified for all subpartitions or must not be specified at all.

Action: Ensure lob attributes of a column are specified for all subpartitions or not specified at all.

ORA-14611 Duplicate subpartition name string in template

Cause: A subpartition name cannot be duplicated within the template.

Action: Rename one of the subpartitions.

ORA-14612 Duplicate lob segment name string for lob column string in template

Cause: Two lob segments of the same column were given the same name in the template.

Action: Rename one of the lob segments.

ORA-14613 Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed

Cause: Any name generated from a partition name and template name must be less than the maximum permissible name for an identifier.

Action: Shorten either the partition name or the template name.

ORA-14614 List value 'string' specified twice in subpartition 'string'

Cause: A list value cannot be specified more than once.

Action: Remove one of the specifications of the value.

ORA-14615 List value 'string' specified twice in subpartitions 'string', 'string'

Cause: A list value cannot be specified more than once.

Action: Remove one of the specifications of the value.

ORA-14616 table is not subpartitioned by List method

Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY SUBPARTITION ADD | DROP VALUES or ALTER TABLE DROP | SPLIT | MERGE SUBPARTITION can only be performed on List subpartitioned objects.

Action: Re-issue the command against a List subpartitioned object.

ORA-14617 cannot add/drop values to DEFAULT subpartition

Cause: An ADD/DROP VALUES operation is being performed on the default subpartition.

Action: Ensure that ADD/DROP VALUES is not done on the DEFAULT subpartition.

ORA-14618 cannot drop the last value of subpartition

Cause: ALTER TABLE DROP VALUES tried to drop the last value of the subpartition.

Action: Cannot execute the command, unless two or more values exist for subpartition.

ORA-14619 resulting List subpartition(s) must contain at least 1 value

Cause: After a SPLIT/DROP VALUE of a list subpartition, each resulting subpartition(as applicable) must contain at least 1 value.

Action: Ensure that each of the resulting subpartitions contains at least 1 value.

ORA-14620 DEFAULT subpartition already exists

Cause: A subpartition already exists with DEFAULT value.

Action: Remove the DEFAULT value from the specified list.

ORA-14621 cannot add subpartition when DEFAULT subpartition exists

Cause: An ADD SUBPARTITION operation cannot be executed when a subpartition with DEFAULT values exists.

Action: Issue a SPLIT of the DEFAULT subpartition instead.

ORA-14622 Value string already exists in subpartition string

Cause: One of the list values in the ADD SUBPARTITION or ADD VALUES statement already exists in another subpartition.

Action: Remove the duplicate value from the statement and try again.

ORA-14623 Value string does not exist in subpartition string

Cause: One of the list values in the SPLIT PARTITION or DROP VALUES statement does not exist in the subpartition.

Action: Remove the value from the statement and try again.

ORA-14624 DEFAULT subpartition must be last subpartition specified

Cause: A subpartition description follows the one describing the default subpartition.

Action: Ensure that the DEFAULT subpartition is the last subpartition description.

ORA-14625 subpartition contains rows corresponding to values being dropped

Cause: Table subpartition contains rows for the values being dropped.

Action: DELETE all rows for the values being dropped and re-issue the statement.

ORA-14626 values being added already exist in DEFAULT subpartition

Cause: An ADD VALUE operation cannot be executed because the values being added exist in the DEFAULT subpartition.

Action: Issue a SPLIT of the DEFAULT subpartition and then MERGE the split subpartition into the subpartition to which values need to be added.

ORA-14627 Invalid operation was specified on a GLOBAL partitioned index

Cause: An invalid operation such as ALTER INDEX DROP|SPLIT SUBPARTITION was specified on the global index.

Action: Ensure that subpartition level operations are not specified on a GLOBAL index, since these are only RANGE partitioned.

ORA-14628 specification of bounds is inconsistent with LIST method

Cause: An operation such as ALTER TABLE SPLIT | ADD SUBPARTITION specified bounds that were inconsistent with List subpartitioning method.

Action: Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List subpartitions.

ORA-14629 cannot drop the only subpartition of a partition

Cause: A drop subpartition command is being executed when there is only one subpartition in the partition.

ORA-14630 subpartition resides in offlined tablespace

Cause: User attempted an operation requiring that we access data in a subpartition which resides in a tablespace which was taken offline. Such operations include trying to drop a tablespace of a table which has indexes defined on it or is referenced by a constraint.

Action: Bring the tablespace online before attempting the operation.

ORA-14631 the partition bounds do not match the subpartition bounds of the partition

Cause: When exchanging a partitioned table with a composite partition, the bounds that describe the partitions of the table must match the bounds that describe the subpartitions of the composite partition.

Action: Ensure that the bounds describing partitions in the partitioned table are the same as the bounds of the subpartitions in the composite partition.

ORA-14632 cannot specify PARALLEL clause when adding a List subpartition

Cause: An ALTER TABLE ADD SUBPARTITION statement was issued with a PARALLEL clause for a List subpartition of a Range/List partitioned object. This is not allowed.

Action: Remove the PARALLEL clause.

ORA-14633 Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table

Cause: The clause INVALIDATE or UPDATE GLOBAL INDEXES is allowed only for ADD hash subpartition to a composite partitioned table.

Action: Remove clause and re-issue the operation.

ORA-14634 Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table

Cause: During a split or a merge of a partition of a range list partitioned table, you cannot specify any subpartitioning information for the resulting partitions.

Action: Remove all subpartitioning information from the DDL.

ORA-14635 only one resulting subpartition can be specified for MERGE SUBPARTITIONS

Cause: ALTER TABLE MERGE SUBPARTITIONS contained more than one resulting subpartition for the MERGE.

Action: Ensure that the statement describes exactly one subpartition as the target that needs to be MERGEd.

ORA-14636 only 2 resulting subpartition can be specified for SPLIT SUBPARTITION

Cause: ALTER TABLE SPLIT SUBPARTITION contained more than 2 resulting subpartition for the SPLIT.

Action: Ensure that the statement describes exactly 2 subpartitions as the target of the SPLIT operation.

ORA-14637 cannot merge a subpartition with itself

Cause: The same subpartition name was specified twice for the merge operation.

Action: Re-submit operation with 2 distinct subpartition names within the same composite partition.

ORA-14638 cannot MERGE subpartitions in different Range Composite partitions

Cause: An attempt was made to MERGE subpartitions in different Range Composite partitions.

Action: Re-issue the command after ensuring that the 2 subpartitions being merged lie within the same composite partition.

ORA-14639 SUBPARTITIONS clause can be specified only for Hash, Composite Range Hash table/partition

Cause: Attempted to specify SUBPARTITIONS clause on table that is not partitioned by the Composite Range-Hash method.

Action: Re-issue the command after ensuring that the SUBPARTITIONS clause is not specified. To specify a template for a Composite Range List object use the SUBPARTITION TEMPLATE clause.

ORA-14640 DROP/SPLIT SUBPARTITION may not be applied to a LOCAL index subpartition

Cause: User attempted to drop or split a subpartition of a LOCAL index which is illegal.

Action: Issue the statement on a table subpartition instead.

ORA-14641 STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition

Cause: Specifying a STORE-IN clause during CREATE/ALTER of a Range, Composite Range List partitioned table which is not allowed.

Action: Re-issue the statement after removing the STORE-IN clause.

ORA-14642 Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION

Cause: The two tables in the EXCHANGE have usable bitmap indexes, and the INCLUDING INDEXES option has been specified and the tables have different hakan factors.

Action: Perform the exchange with the EXCLUDING INDEXES option or alter the bitmap indexes to be unusable.

ORA-14643 Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION

Cause: Either records_per_block has been minimized for one of the tables to be exchanged, but not the other, or the hakan factors for the tables to be exchanged are not equal.

Action: If records_per_block has been minimized for one of the tables, but not the other, either perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables, or perform alter table with the MINIMIZE RECORDS_PER_BLOCK for both tables. If the hakan factors do not match, then perform alter table with the NOMINIMIZE RECORDS_PER_BLOCK option for both tables.

ORA-14644 table is not subpartitioned by Hash method

Cause: A subpartition maintenance operation such as ALTER TABLE MODIFY PARTITION COALESCE SUBPARTITION can only be performed on Hash subpartitioned objects.

Action: Re-issue the command against a Hash subpartitioned object.

ORA-14645 STORE IN clause cannot be specified for Range List objects

Cause: A STORE IN clause was specified for Range List partitioned object.

Action: Re-issue the command after removing the STORE IN clause.

ORA-16000 database open for read-only access

Cause: The database has been opened for read-only access. Attempts to modify the database using inappropriate DML or DDL statements generate this error.

Action: In order to modify the database, it must first be shut down and reopened for read-write access.

ORA-16001 database already open for read-only access by another instance

Cause: The database has been opened for read-only access by another instance, and cannot be opened for read-write access by this instance.

Action: This instance must be opened for read-write access, or all other instances must first be shut down and reopened for read-only access.

ORA-16002 database already open for read-write access by another instance

Cause: The database has been opened for read-write access by another instance, and cannot be opened for read-only access by this instance.

Action: This instance must be opened for read-only access, or all other instances must first be shut down and reopened for read-write access.

ORA-16003 standby database is restricted to read-only access

Cause: To ensure its integrity, a standby database can only be opened for read-only access.

Action: reissue the ALTER DATABASE OPEN specifying READ ONLY.

ORA-16004 backup database requires recovery

Cause: The control file is for a backup database which requires recovery, and cannot be opened for read-only access by this instance.

Action: Perform the necessary recovery and re-open for read-only access.

ORA-16005 database requires recovery

Cause: The database requires recovery, and therefore cannot be opened for read-only access by this instance.

Action: Perform the necessary recovery and re-open for read-only access.

ORA-16006 audit_trail destination incompatible with database open mode

Cause: The AUDIT_TRAIL initialization parameter was set to "DB" (or TRUE), which is incompatible with a database opened for read-only access.

Action: When the database is opened for read-only access, the AUDIT_TRAIL initialization parameter can only be set to "OS" or "NONE" (FALSE).

ORA-16007 invalid backup control file checkpoint

Cause: The backup control file being opened for read-only access does not contain a valid control file checkpoint. Therefore the database cannot be opened for read-only access.

Action: First open the database for read-write access which will result in a valid control file checkpoint. Then re-open the database for read-only access.

ORA-16008 indeterminate control file checkpoint

Cause: The control file for the database being opened for read-only access was created via CREATE CONTROLFILE. Therefore a control file checkpoint could not be calculated and the database cannot be opened for read-only access.

Action: First open the database for read-write access which will result in a valid control file checkpoint. Then re-open the database for read-only access.

ORA-16009 remote archive log destination must be a STANDBY database

Cause: The database associated with the archive log destination service name is other than the required STANDBY type database. Remote archival of redo log files is not allowed to non-STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16010 remote archive log destination database is opened for update

Cause: The database associated with the archive log destination service name is opened for update access. Remote archival of redo log files to standby databases opened for update access is not allowed.

Action: Shut down the standby destination instance and re-open for read-only access or simply leave the standby instance mounted and unopened.

ORA-16011 Archivelog Remote File Server process in Error state

Cause: The archivelog remote file server (RFS) process at the specified standby database site has experienced an unrecoverable error and is unable to receive further archive log data.

Action: Correct the problem at the standby database site.

ORA-16012 Archive log standby database identifier mismatch

Cause: The database identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16013 log string sequence# string does not need archiving

Cause: An attempt was made to archive the named file manually, but the file did not require archiving. The file had previously been successfully archived.

Action: No action is required.

ORA-16014 log string sequence# string not archived, no available destinations

Cause: An attempt was made to archive the named log, but the archive was unsuccessful. The archive failed because there were no archive log destinations specified or all destinations experienced debilitating errors.

Action: Verify that archive log destinations are being specified and/or take the necessary step to correct any errors that may have occurred.

ORA-16015 log string sequence# string not archived, media recovery disabled

Cause: An attempt was made to archive the named log, but the archive was unsuccessful. A standby archive log destination was specified and the database was not media recovery enabled. This is not allowed.

Action: Disable the standby destination or enable media recovery and retry.

ORA-16016 archived log for thread string sequence# string unavailable

Cause: The managed standby database recovery operation has timed out waiting for the requested archived log file.

Action: Verify that the primary database is still archiving redo logs to the standby recovery database site and reissue the RECOVER STANDBY DATABASE WAIT command.

ORA-16017 cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination

Cause: The LOG_ARCHIVE_DUPLEX_DEST parameter was set to a non-NULL value when the primary archive destination was explicitly set to NULL.

Action: Set the primary archive destination to a valid non-NULL value.

ORA-16018 cannot use string with LOG_ARCHIVE_DEST_n

Cause: One of the following events caused an incompatibility:

The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST initialization parameter was in use when a LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) was encountered while fetching initialization parameters.
An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when a LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters.
A LOG_ARCHIVE_DEST_n parameter was in use when an ALTER SYSTEM statement was used to define a value for either the LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST parameter.

Action: Eliminate any incompatible parameter definitions.

ORA-16019 cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST

Cause: One of the following events caused an incompatibility:

The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST initialization parameter was in use when the specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) was encountered while fetching initialization parameters.
The LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST initialization parameter was in use when an attempt was made to use an ALTER SYSTEM or ALTER SESSION statement to define a value for the specified LOG_ARCHIVE_DEST_n parameter.
An ALTER SYSTEM ARCHIVE LOG START TO statement was in effect when the specified LOG_ARCHIVE_DEST_n parameter was encountered while fetching initialization parameters.
An ALTER SYSTEM ARCHIVE LOG START TO command was in effect when an attempt was made to use an ALTER SYSTEM or ALTER SESSION command to define a value for the specified LOG_ARCHIVE_DEST_n parameter.

Action: Eliminate any incompatible parameter definitions.

ORA-16020 less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST

Cause: With automatic archiving enabled, the number of archive log destinations that could be used for the database was less than the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value.

Action: Either adjust the settings of the log archive destination parameters, or lower the value of LOG_ARCHIVE_MIN_SUCCEED_DEST.

ORA-16021 session string destination cannot be the same as session string destination

Cause: An attempt was made to change the first specified archive log parameter using ALTER SESSION to have a destination value that duplicates the session-level destination value of the second specified archive log parameter.

Action: Specify a different session destination value for one of the LOG_ARCHIVE_DEST_n parameters.

ORA-16022 LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL

Cause: An attempt was made to change the LOG_ARCHIVE_DEST initialization parameter to NULL when the LOG_ARCHIVE_DUPLEX_DEST initialization parameter is non-NULL.

Action: Either set the LOG_ARCHIVE_DEST initialization parameter to a non-NULL value, or set the LOG_ARCHIVE_DUPLEX_DEST initialization parameter to a NULL value.

ORA-16023 system string destination cannot be the same as session string destination

Cause: An attempt to change the first specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) produced a destination that duplicates the session destination value of the second specified LOG_ARCHIVE_DEST_n parameter. This error can occur when setting a non-NULL value with the ALTER SYSTEM statement. Or, this error can occur when setting a NULL value with ALTER SESSION command, because then the associated system destination value may appear as a duplicate.

Action: Specify a different destination value for the first specified LOG_ARCHIVE_DEST_n parameter.

ORA-16024 parameter string cannot be parsed

Cause: The value for the indicated LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) could not be parsed. Common causes for this error are a misplaced equal sign, an unrecognized attribute, or an attribute that is missing a required value.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16025 parameter string contains repeated or conflicting attributes

Cause: The value for the specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) contained either repeated attributes or attributes that conflicted with each other.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16026 parameter string contains an invalid numeric attribute value

Cause: The value for the specified LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) contained a REOPEN attribute with an invalid numeric value. The valid range is 0 - 65535.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16027 parameter string is missing a destination option

Cause: The value for the indicated LOG_ARCHIVE_DEST_n parameter (n = 1, 2, ... 10) failed to include a destination option. A destination option is specified using either the LOCATION or SERVICE attribute.

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16028 new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires

Cause: With automatic archiving enabled, an attempt was made to change the indicated LOG_ARCHIVE_DEST_n or a LOG_ARCHIVE_DEST_STATE_n parameter (n = 1, 2, ... 10) to a value that reduces the number of archive log destinations to less than the specified LOG_ARCHIVE_MIN_SUCCEED_DEST value.

Action: Either select different options for the LOG_ARCHIVE_DEST_n or LOG_ARCHIVE_DEST_STATE_n parameters, or reduce the value for the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter.

ORA-16029 cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations

Cause: An attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter when there are no archive log destinations.

Action: Define one or more log archive destinations using the LOG_ARCHIVE_DEST, LOG_ARCHIVE_DUPLEX_DEST, or LOG_ARCHIVE_DEST_n parameters (n = 1, 2, ... 10). Then, change the value of the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter.

ORA-16030 session specific change requires a LOG_ARCHIVE_DEST_n destination

Cause: The following event caused an incompatibility: Parameter LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST was in use when an attempt was made to change the LOG_ARCHIVE_MIN_SUCCEED_DEST parameter with an ALTER SESSION statement.

Action: Replace any LOG_ARCHIVE_DEST and LOG_ARCHIVE_DUPLEX_DEST parameters with LOG_ARCHIVE_DEST_n (n = 1, 2, ... 10) parameters.

ORA-16031 parameter string destination string exceeds string character limit

Cause: The value for the specified parameter contained a destination string that is too long.

Action: Replace the destination value for the specified parameter with a character string that has a length below the limit specified in the error message.

ORA-16032 parameter string destination string cannot be translated

Cause: The value for the specified parameter contained a destination string that could not be translated.

Action: Use a valid destination string in the specified parameter.

ORA-16033 parameter string destination cannot be the same as parameter string destination

Cause: An attempt was made to change the first specified archive log parameter to have a destination value that duplicates the system-level destination value of the second specified archive log parameter.

Action: Specify a different value for one of the archive log parameters.

ORA-16034 FROM parameter is incompatible with MANAGED recovery

Cause: Use of the FROM 'location' parameter is not allowed when MANAGED recovery has been specified.

Action: Correct the syntax and retry the command.

ORA-16035 missing required keyword string

Cause: The indicated keyword is required but was not specified.

Action: Correct the syntax and retry the command.

ORA-16036 invalid MANAGED recovery CANCEL option

Cause: A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.

Action: Specify either nothing or IMMEDIATE following CANCEL.

ORA-16037 user requested cancel of managed recovery operation

Cause: The managed standby database recovery operation has been canceled per user request.

Action: No action is required.

ORA-16038 log string sequence# string cannot be archived

Cause: An attempt was made to archive the named file, but the file could not be archived. Examine the secondary error messages to determine the cause of the error.

Action: No action is required.

ORA-16039 RFS request version mismatch

Cause: A request to archive a redo log to a standby site failed because the request was incompatible with the Remote File Server (RFS) at the standby site.

Action: Verify that compatible versions of Oracle are running on the primary and all standby sites.

ORA-16040 standby destination archive log file is locked

Cause: The target standby destination archive log file is currently locked. This indicates that the file is being archived to by another Remote File Server (RFS) process.

Action: Check for and eliminate duplicate standby destination archive log service names defined for the primary database.

ORA-16041 Remote File Server fatal error

Cause: The Remote File Server (RFS) process at the standby destination archive log site has encountered a disabling error and is no longer available. Further archiving to the standby site may not be possible.

Action: Refer to the appropriate RFS trace file located at the standby site for details regarding the error encountered and if possible, take corrective action.

ORA-16042 user requested cancel immediate of managed recovery operation

Cause: The managed standby database recovery operation has been canceled immediately per user request. Processing of the current archive log file has been interrupted and therefore the database is in an inconsistent state.

Action: No action required.

ORA-16043 managed recovery session canceled

Cause: The standby database managed recovery operation has been canceled per user request or operation timeout.

Action: More specific messages will accompany this message.

ORA-16044 destination string attribute cannot be specified at session level

Cause: An archive log destination attribute was attempted to be modified at the session level.

Action: Use the ALTER SYSTEM command to modify the destination attribute.

ORA-16045 circular archive log destination dependency chain

Cause: An archive log destination contains a dependency to another archive log destination that also contains a dependency.

Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM statement to remove one of the dependency attributes.

ORA-16046 Archive log destination failed due to failed dependent destination

Cause: The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails.

Action: No action required.

ORA-16047 Dependent archive log destination cannot be a standby database

Cause: The parent archive log destination cannot be a standby database. It must be a local archive log destination.

Action: Change the parent archive log destination from referencing a standby database to referencing a local archive log repository.

ORA-16048 enable simulated error on archive log write

Cause: Causes an I/O error to be signalled during the writing of an archival operation.

Action: No action required.

ORA-16049 simulated error on archive log write

Cause: I/O error returned for a simulated archival failure during an archival operation.

Action: No action required.

ORA-16050 destination exceeded specified quota size

Cause: An archive log was attempted to be created in a destination with a specified maximum quota size. The creation of the archive log exceeded the specified quota size. Therefore, the destination has been made inaccessible to future archival operations.

Action: No action required.

ORA-16051 parameter string contains an invalid delay time

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a DELAY attribute with an invalid numeric value. The valid range is 0-5760 (in minutes).

Action: Correct the value for the indicated LOG_ARCHIVE_DEST_n parameter.

ORA-16052 Problem with fetching gap sequence, media recovery cancelled.

Cause: A gap sequence is detected on the standby database while it was trying to perform managed standby recovery. The fetching of the gap sequence fails. The failures are logged in the alert log on the primary database.

Action: Check the alert log on primary and standby database. Take appropriate action to make the gap sequence available again. Managed standby recovery on the standby database cannot proceed further until the standby database is able to get the gap sequence redo log files.

ORA-16053 FAL archive failed, cannot archive thread# string sequence# string

Cause: The FAL server on the primary database has problem archiving a redo log file requested by the standby database. The cause for this failure is logged in the alert log file.

Action: Check the alert log on the primary database. Take the appropriate action to solve the problem. Re-issue Managed Standby Recovery on the standby database again.

ORA-16055 FAL request rejected

Cause: FAL server rejects the FAL request from the FAL client. This may be caused by different reasons.

Action: Check the alert log on the primary database. Take the appropriate action to solve the problem.

ORA-16056 backup control file archival requires proper syntax

Cause: An attempt was made to perform an online log file archival using a backup control file. However, the USING BACKUP CONTROLFILE syntax was not specified.

Action: If the archival operation is correct when using a backup control file, then the USING BACKUP CONTROLFILE syntax is required.

ORA-16057 current control file archival requires proper syntax

Cause: An attempt was made to perform an online log file archival using a current control file. However, the USING BACKUP CONTROLFILE syntax was specified.

Action: If the archival operation is correct when using a current control file, then the USING BACKUP CONTROLFILE syntax is not required.

ORA-16058 standby database instance is not mounted

Cause: The RFS process on the standby database received an internal error.

Action: Check the standby alert log and RFS trace files for more information.

ORA-16059 Log file is empty or invalid next available block

Cause: Archiving not allowed of an empty or invalid log file.

Action: No action required.

ORA-16060 Log file is current

Cause: The current log file cannot be archived using its file name.

Action: No action required.

ORA-16061 Log file status has changed

Cause: It is possible the online log file was reclaimed as a new log file either before archival started, or during the archival operation.

Action: No action required.

ORA-16062 The log was NOT archived

Cause: Archiving not allowed of current log file.

Action: Check the alert log and archive trace files for additional information.

ORA-16063 remote archival is enabled by another instance

Cause: Remote archival of database REDO log files has been enabled by another instance, and cannot be disabled for this instance.

Action: Set the REMOTE_ARCHIVE_ENABLE parameter to true and restart this instance.

ORA-16064 remote archival is disabled by another instance

Cause: Remote archival of database REDO log files has been disabled by another instance, and cannot be enabled for this instance.

Action: Set the REMOTE_ARCHIVE_ENABLE parameter to false and restart this instance.

ORA-16065 remote archival disabled at standby destination

Cause: Receipt of remote archived REDO log files has been disabled at the associated standby destination host database.

Action: If appropriate, change the associated archive log parameter to specify a local destination with the LOCATION keyword or defer the associated archive log destination. Or, if possible, set the standby REMOTE_ARCHIVE_ENABLE parameter to true and restart the standby database instance before further REDO log file archivals occur.

ORA-16066 remote archival disabled

Cause: An archive log destination parameter has specified a remote destination with the SERVICE keyword. Remote archival of REDO log files has been disabled for this database. The associated archive log destination has been disabled.

Action: If appropriate, change the archive log parameter to specify a local destination with the LOCATION keyword or (if appropriate) set the REMOTE_ARCHIVE_ENABLE parameter to true and restart the database instance before further REDO log file archivals occur.

ORA-16067 activation identifier mismatch in archive log string

Cause: The activation identifier contained in the archive log file header does not match the activation identifier of the database being recovered. The indicated archive log cannot be applied to the database.

Action: Locate the appropriate archive log for the database.

ORA-16068 redo log file activation identifier mismatch

Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database.

ORA-16069 Archive Log standby database activation identifier mismatch

Cause: The activation identifiers of the Primary and Standby database do not match. Remote archival of redo log files is not allowed to incompatible STANDBY database instances. This can occur when trying to apply an incorrect archive log to a standby database, or when trying to archive to a standby database that does not match the primary database.

Action: Take the necessary steps to create the required compatible STANDBY database before retrying the ARCHIVE LOG processing.

ORA-16070 parameter string contains an invalid REGISTER attribute value

Cause: The value for the specified LOG_ARCHIVE_DEST_n (n = 1...10) parameter contained a REGISTER attribute that specified an invalid file name template string. If specified, the REGISTER file name template string must indicate an operating system-specific file path name including thread and log sequence number substitution directives (%t, %T, %s, %S).

Action: Correct the value for the LOG_ARCHIVE_DEST_n parameter.

ORA-16071 dependency archived log file not found string

Cause: The specified archived log file was not found at the indicated standby destination.

Action: Verify the correctness of the dependency archived log file name template specified for the indicated standby destination against the actual dependency archived log file.

ORA-16072 a minimum of one standby database destination is required

Cause: No standby database archive log destinations were specified.

Action: Specify a standby archive log destination in the initialization parameter file.

ORA-16073 archiving must be enabled

Cause: Online log file archiving is disabled.

Action: Enable log file archiving.

ORA-16074 ARCH processes must be active

Cause: There are no active ARCH processes.

Action: It is required that at least one ARCH process be active.

ORA-16075 standby database destination mismatch

Cause: A standby database destination was specified that is not accessed by another instance.

Action: All database instances must access the same standby databases.

ORA-16076 unknown standby database destination

Cause: A standby database destination was specified that is not accessed by another instance.

Action: All database instances must access the same standby databases.

ORA-16078 media recovery disabled

Cause: The database is not in ARCHIVELOG mode.

Action: Place the database in ARCHIVELOG mode.

ORA-16079 standby archival not enabled

Cause: The standby database does not have archival enabled.

Action: In order to allow the standby database to access the standby log files, the ARCH process must be enabled and active.

ORA-16080 invalid LogMiner session string for APPLY

Cause: Logical standby apply engine was started with an invalid LogMiner session identifier.

Action: Fix the problem with the LogMiner session or create a new session.

ORA-16081 insufficient number of processes for APPLY

Cause: Logical standby apply engine was started with fewer processes available than needed.

Action: Increase the values of the initialization parameters PROCESSES and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.

ORA-16082 logical standby is not initialized correctly

Cause: Logical standby apply engine was started but it found inconsistencies in its metadata.

Action: Look in the trace file for more information.

ORA-16083 LogMiner session has not been created

Cause: Logical standby apply engine was started without creating a LogMiner session.

Action: Create a LogMiner session and restart the apply engine.

ORA-16084 an apply engine is already running

Cause: A logical standby apply engine was running when another was created.

Action: Shut down the previous apply engine before starting a new one.

ORA-16086 standby database does not contain available standby log files

Cause: The primary database is in "no data loss" mode, but the standby database does not contain any "standby log files".

Action: Add one or more standby log files to the standby database. This can be done while the standby database is mounted.

ORA-16087 graceful switchover requires standby or current control file

Cause: An attempt was made to perform a graceful switchover operation using a backup or clone control file.

Action: Convert the backup control file into a current control file prior to attempting a graceful switchover operation. A clone control file cannot be used for a graceful switchover operation.

ORA-16088 archive log has not been completely archived

Cause: An attempt was made to register an archive log that has not been completely archived. The specified archive log may be a "current" log file.

Action: Specify a completed archive log.

ORA-16089 archive log has already been registered

Cause: An attempt was made to register an archive log that already has a corresponding thread# and sequence# entry in the standby database control file. Duplicate information is not permitted.

Action: Use the V$ARCHIVED_LOG fixed view to verify the archive log information.

ORA-16090 archive log to be replaced not created by managed standby process

Cause: An attempt was made to replace an archive log entry that was not originally created by the managed standby operation.

Action: No user action required.

ORA-16091 dependent archive log destination already archived

Cause: An archive log destination contains a dependency to another archive log destination that has previously been archived.

Action: The parent archive log destination cannot be dependent on another archive log destination. Use the ALTER SYSTEM statement to remove one of the dependency attributes.

ORA-16092 dependent archive log destination is not active

Cause: An archive log destination contains a dependency to another archive log destination that is not active.

Action: The child archive log destination cannot be dependent on another invalid archive log destination. Use the ALTER SYSTEM statement to remove one of the dependency attributes.

ORA-16093 dependent archive log destination is not LGWR-enabled

Cause: An archive log destination contains a dependency to another archive log destination that is not enabled for the LGWR process.

Action: The child archive log destination cannot be dependent on another archive log destination not archived by the LGWR. Use the ALTER SYSTEM statement to change the parent archive log to specify the LGWR process.

ORA-16094 database shutdown during archival operation

Cause: The database was shut down while an online log file archival was active.

Action: No action required. The ARCH process is terminated.

ORA-16095 Dependent destination removal for inactivation

Cause: A dependent archive log destination was inactivated due to the parent archive log destination becoming inelligible for archival. This may be due to the parent destination being manually deferred by an application user.

Action: No action required.

ORA-16098 inaccessible standby database forced shutdown to protect primary

Cause: No standby database archive log destinations remain accessible and the primary database is in "protected" no-data-loss mode.

Action: Specify an alternate standby archive log destination in the initialization parameter file.

ORA-16099 internal error ORA-00600 occurred at standby database

Cause: The RFS process on the standby database received an internal error.

Action: Check the standby alert log and RFS trace files for more information.

ORA-16100 not a valid Logical Standby database

Cause: This database has not been completely configured as a Logical Standby database.

Action: Verify that the database is the intended Logical Standby database. Ensure that you already started logical standby apply with the ALTER DATABASE START LOGICAL APPLY INITIAL statement. See the Oracle9i SQL Reference for the statement syntax.

ORA-16101 a valid start SCN could not be found

Cause: An SCN from which to start could not be found.

Action: Register the first log file following the backup from which this database was generated. Using the ALTER DATABASE REGISTER LOGFILE statement to register the database is recommended. Alternatively, you can provide a starting SCN value with this statement.

ORA-16102 remote information is not available on the specified primary

Cause: The new primary has not completed generating the necessary information for the standby to begin consuming its log stream.

Action: Verify that the database link provided references a system that is about to become a new primary. Wait a short time before retrying the command to allow the primary some time to generate the necessary information.

ORA-16103 Logical Standby apply must be stopped to allow this operation

Cause: Logical Standby is currently applying changes. The apply must complete or be stopped to allow the requested operation.

Action: Execute the ALTER DATABASE STOP LOGICAL STANDBY APPLY statement, then re-enter or re-specify the operation.

ORA-16104 invalid Logical Standby option requested

Cause: The option requested is not valid.

Action: Check spelling or refer to the Oracle9i SQL Reference for the correct statement syntax, then re-enter the request.

ORA-16105 Logical Standby is already running in background

Cause: A Logical Standby apply operation is already running.

Action: no action required.

ORA-16107 all log data from primary has been processed

Cause: On the primary system, the log stream has been ended by the ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY statement.

Action: Issue one of the following statements to make this standby a primary or resume applying changes from a new primary:

ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL PRIMARY;
ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;

ORA-16108 database is no longer a standby database

Cause: The current database has already been made a primary database.

Action: Issue the following statements to make this primary a standby:

ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBY;
ALTER DATABASE START LOGICAL STANDBY APPLY NEW PRIMARY dblink;

ORA-16109 failed to apply log data from previous primary

Cause: Log data from previous primary could not be completely applied.

Action: Check DBA_LOGSTDBY_EVENTS for failures and take corrective action. Then, re-issue command.

ORA-16110 user procedure processing of logical standby apply DDL

Cause: A user provided stored procedure has been called to inspect a DDL statement prior to it being processed.

Action: No action required; this informational statement is provided to record user involvement in the processing of a statement. Additional information can be found in the DBA_LOGSTDBY_EVENTS and the DBA_LOGSTDBY_SKIP views.

ORA-16111 log mining and apply setting up

Cause: This logical standby process is setting up to begin processing changes.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16112 log mining and apply stopping

Cause: This logical standby process is cleaning up and stopping Logical Standby apply.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16113 applying change to table or sequence object number string

Cause: The process is applying changes to a specific schema object.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16114 applying DDL transaction with commit SCN string

Cause: The process is applying a DDL change that's committed at the given SCN.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16115 loading Log Miner dictionary data

Cause: The process is loading dictionary information from the redo stream. This activity may take a few minutes.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16116 no work available

Cause: The process is idle waiting for additional changes to be made available.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16117 processing

Cause: The process is performing its primary function and is not waiting on any significant event.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16119 building transaction at SCN string

Cause: The transaction being committed at the given SCN is being prepared for apply.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16120 dependencies being computed for transaction at SCN string

Cause: The transaction committed at the given SCN is being analyzed for dependencies.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16121 applying transaction with commit SCN string

Cause: The transaction committed at the given SCN is being applied.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16122 applying large dml transaction at SCN string

Cause: A large transaction is being applied before the commit has been seen. The current redo being applied ends as the given SCN.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16123 transaction string string string is waiting for commit approval

Cause: The apply process is waiting for approval to commit a transaction. This transaction may depend on another or other synchronization activity may delay the committing of a transaction.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16124 transaction string string string is waiting on another transaction

Cause: The apply process is waiting to apply additional changes. This transaction likely depends on another.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16125 large transaction string string string is waiting on another transaction

Cause: The apply process is waiting until additional changes for a large transaction are retrieved from the log stream.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16126 loading table or sequence object number string

Cause: Information on the given table or sequence is being loaded into an in memory cache for future use.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16127 stalled waiting for additional transactions to be applied

Cause: This process is waiting for additional memory before continuing. Additional log information cannot be read into memory until more transactions have been applied to the database, thus freeing up additional memory.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes. If this message occurs often and changes are not being applied quickly, then increase available SGA or the number of apply processes.

ORA-16128 User initiated shut down successfully completed

Cause: Logical standby was shutdown in an orderly fashion.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16129 unsupported dml encountered

Cause: DML to tables in the SYS schema have been updated and are not part of a DDL operation. This may be due to some DBA activity or DML associated with a kernel PL/SQL request that Logical Standby does not yet support.

Action: Check the DBA_LOGSTDBY_EVENTS table for the name of the table being processed. Possibly use Log Miner to understand the transaction, and provide a compensating transaction on the standby system. Once complete, call DBMS_LOGSTDBY.SKIP_TRANSACTION with the associated transaction id, and resume apply.

ORA-16130 supplemental log information is missing from log stream

Cause: Supplemental logging is not enabled at the primary database.

Action: Issue the following statement to enable supplemental logging:

ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) 
COLUMNS;

ORA-16131 An error occurred during a Terminal Recovery of the standby.

Cause: An error occurred during a Terminal Recovery of the standby.

Action: Check the standby alert log additional information.

ORA-16132 An error occurred during activation of the standby.

Cause: An error occurred during activation of the standby database following a Terminal Recovery.

Action: Check the standby alert log additional information.

ORA-16133 Datafile string has incorrect terminal recovery stamp.

Cause: After activation of a standby database following a terminal recovery (recovery of standby using current logs), recovery of a datafile from before the activation must have completed the same terminal recovery to avoid corruption.

Action: A backup of the datafile taken after the terminal recovery and before activating the standby must be used for recovery.

ORA-16134 invalid MANAGED recovery FINISH option

Cause: A mode other than NOWAIT follows the FINISH keyword in the RECOVER MANAGED STANDBY DATABASE statement.

Action: Specify either nothing or NOWAIT following FINISH.

ORA-16135 terminal recovery could not find log for thread# string seq# string.

Cause: A terminal recovery (initiated by the RECOVER MANAGED STANDBY FINISH command) could not find the current log for the requested thread and sequence.

Action: Check that the standby current logs are in the correct location.

ORA-16136 Managed Standby Recovery not active

Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active.

Action: No action required.

ORA-16137 No terminal recovery is required

Cause: All archived logs have been applied, and there are no current logs to be applied. Terminal recovery is not required.

Action: No action required. The standby database may be activated as a new primary or may continue as a standby.

ORA-16138 end of log stream not received from primary

Cause: The standby system has not received notification that the primary system log stream has been terminated. A graceful switchover is not possible.

Action: Verify that the primary log stream has been terminated. Ensure that the standby has applied all necessary redo from the primary system and, if appropriate, reissue the graceful switchover command.

ORA-16139 media recovery required

Cause: The database has not been recovered through the end of log stream. Graceful switchover is not possible.

Action: Ensure that the entire log stream has been applied. If appropriate, re-issue the graceful switchover command.

ORA-16140 standby online logs have not been recovered

Cause: The standby database has online logs containing redo that has not been recovered. Activating the standby would lose redo contained in the online logs.

Action: To recover the standby online logs issue the following command:

ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH;

Then re-issue the ALTER DATABASE ACTIVATE STANDBY DATABASE statement. To activate the standby without recovering the online logs, issue the following command:

ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE;

ORA-16143 RFS connections not allowed during or after terminal recovery

Cause: An attempt was made, by an RFS process, to access a standby online log file during or after a terminal recovery.

Action: The primary must not attempt to archive to the standby after a terminal recovery.

ORA-16145 archival for thread# string sequence# string in progress

Cause: The indicated archived log file is not available for recovery due to the fact that it is still being archived.

Action: Verify that archival of the indicated log file has completed and re-issue the RECOVER STANDBY DATABASE command.

ORA-16146 standby destination control file enqueue unavailable

Cause: The target standby destination control file is currently unavailable to the Remote File Server (RFS) process. This indicates that the target destination is the primary database itself.

Action: Check for and eliminate the standby destination archive log parameter in question.

ORA-16147 standby database referenced by multiple archive log destinations

Cause: Multiple archive log destinations reference the same standby database, using different service names. This is not allowed.

Action: Remove one of the duplicate archive log destinations.

ORA-16148 user requested expiration of managed recovery operation

Cause: The managed standby database recovery operation has been canceled per user specified EXPIRE option of the RECOVER MANAGED STANDBY DATABASE statement.

Action: No action required.

ORA-16150 FINISH recovery performed on another, older standby database

Cause: An archive log containing a FINISH recovery indicator was received by a standby database that has received archive logs in the future of the received archive log. Because of the possibility that these future archive logs have been applied to this standby database, the received archive log must be rejected.

Action: No action required.

ORA-16151 Managed Standby Recovery not available

Cause: The attempted operation failed because of a pending CANCEL of the managed standby recovery operation.

Action: Wait for the managed standby recovery session to end. Then retry the operation.

ORA-16152 standby database is in 'no-data-loss' protected mode

Cause: The attempted database operation is not allowed while the standby database is in 'no-data-loss' protected mode.

Action: Verify that the attempted database operation is warranted, ALTER DATABASE SET STANDBY DATABASE UNPROTECTED and re-issue the statement.

ORA-16154 suspect attribute: string

Cause: Use of the indicated attribute is illegal in the given context.

Action: Make the appropriate changes and re-issue the statement.

ORA-16156 LGWR archive log dependency not allowed if database is standby protected

Cause: The use of a LGWR archive log dependency is not allowed when the primary is protected by a standby database, as this requires use of the standby redo log files.

Action: Remove the LGWR archive log dependency and use normal LGWR archival instead.

ORA-16157 media recovery not allowed following successful FINISH recovery

Cause: A RECOVER MANAGED STANDBY DATABASE FINISH command has previously completed successfully. Another media recovery is not allowed.

Action: Issue one of these operations following a FINISH recovery:

ALTER DATABASE OPEN READ ONLY;
ALTER DATABASE COMMIT TO SWITCHOVER TO PRIMARY;

ORA-16159 Cannot change protected standby destination attributes

Cause: An attempt was made to change the LGWR/ARCH or SYNC/ASYNC attributes for a destination that is participating in the standby protection mode of the database.

Action: No action required.

ORA-16160 Cannot change protected standby database configuration

Cause: An attempt was made to change the standby database configuration when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16161 Cannot mix standby and online redo log file members for group string

Cause: An attempt was made to add a log file member that does not match the other member types. This problem typically occurs when adding a standby log file member to an online redo logfile group, or adding an online redo log file member to a standby redo log file group.

Action: Verify the log file group type using the TYPE column of the V$LOG fixed view.

ORA-16162 Cannot add new standby databases to protected configuration

Cause: An attempt was made to enable a new standby database destination when the primary database is in standby protected mode.

Action: The standby database must be added to the configuration before the primary database is opened.

ORA-16163 LGWR network server host attach error

Cause: The LGWR network server could not attach to remote host.

Action: The alert log contains more problem-specific information.

ORA-16164 LGWR network server host detach error

Cause: The LGWR network server could not detach from remote host.

Action: The alert log contains more problem-specific information.

ORA-16165 LGWR failed to hear from network server

Cause: The LGWR lost its connection to the network server.

Action: The alert log contains more problem-specific information.

ORA-16166 LGWR network server failed to send remote message

Cause: The LGWR network server could not communicate with the remote host.

Action: The alert log contains more problem-specific information.

ORA-16167 LGWR network server could not switch to non-blocking mode

Cause: The LGWR network server could not switch to non-blocking mode.

Action: The alert log contains more problem-specific information.

ORA-16168 LGWR network server could not switch to blocking mode

Cause: The LGWR network server could not switch to blocking mode.

Action: The alert log contains more problem-specific information.

ORA-16169 LGWR network server invalid parameters

Cause: The LGWR network server could not switch to blocking mode.

Action: The alert log contains more problem-specific information.

ORA-16170 Parallel terminal recovery may lose more data than necessary

Cause: Serial terminal recovery can always recover the standby database to the last consistent point in the redo stream. Parallel terminal recovery cannot.

Action: Retry with serial terminal recovery.

ORA-16171 RECOVER...FINISH not allowed due to gap for the string, seq string-string

Cause: See alert log for more details.

Action: Copy missing archived logs from primary or another standby. Register the logs and re-issue the RECOVER...FINISH command. If the logs are not available, then issue the ALTER DATABASE RECOVER MANAGED STANDBY SKIP statement to ignore the standby redo log files.

ORA-16172 archive logs detected beyond Terminal End-Of-Redo

Cause: An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to the existence, at the remote site, of archive logs containing REDO in the future of the Terminal EOR.

ORA-16173 incompatible archival network connections active

Cause: One of two situations can cause this error:

An attempt to start a Terminal Incomplete Recovery operation failed due to an active Remote File Server process detected.
An attempt to archive a Terminal End-Of-Redo archive log to a remote destination failed due to an active Remote File Server process at the remote site.

An active Remote File Server (RFS) process implies connectivity with the primary database which may indicate that a Terminal Incomplete Recovery operation is not warrented.

Action: Verify the Managed Standby environment and re-evaluate the necessity of a Terminal Incomplete Recovery operation.

ORA-16174 user requested thread/sequence termination of managed recovery

Cause: The managed standby database recovery operation has been terminated per user specified THROUGH THREAD/SEQUENCE option of the RECOVER MANAGED STANDBY DATABASE statement.

Action: No action required.

ORA-16175 cannot shut down database when media recovery is active

Cause: An attempt was made to shut down a standby database while media recovery was active.

Action: Cancel media recovery to proceed with the shutdown.

ORA-16199 Terminal recovery failed to recover to a consistent point

Cause: See alert log for more details.

Action: Try to resolve the problem. Retry terminal recovery. If the problem occurs repeatedly and cannot be resolved, then contact Oracle Support Services.

ORA-16200 Skip procedure requested to skip statement

Cause: Logical standby called a skip procedure that requested for a particular statement not to be applied.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16201 Skip procedure requested to apply statement

Cause: Logical standby called a skip procedure that requested for a particular statement to be applied.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16202 Skip procedure requested to replace statement

Cause: Logical standby called a skip procedure that requested for a particular statement to be replaced with a new statement.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16203 Unable to interpret skip procedure return values

Cause: The skip procedure returned conflicting or invalid values.

Action: Ensure that the new_statement output parameter is non-NULL when returning DBMS_LOGSTDBY.SKIP_ACTION_REPLACE, and NULL otherwise. Also ensure SKIP_ACTION is specified correctly.

ORA-16204 DDL successfully applied

Cause: A DDL statement has successfully committed on the logical standby database.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16205 DDL skipped due to skip setting

Cause: A setting in the logical standby skip table indicates that this type of DDL should always be skipped.

Action: No action required; this informational statement is provided to record the event for diagnostic purposes.

ORA-16206 database already configured as Logical Standby database

Cause: This database has been previously configured as a Logical Standby database. A Logical Standby database is not capable of processing the requested operation.

Action: Ensure that you entered the command on the correct database as this database is a Logical Standby and is not capable of servicing the request.

ORA-16207 Logical standby dictionary build not permitted.

Cause: A dictionary build is currently in progress. Only one build can be active at a time.

Action: Wait for the active build to complete before invoking a new build.

ORA-16208 Logical standby dictionary build failed to start.

Cause: Failure to start the logical standby dictionary build process (LSP1).

Action: Check the accompanying messages and the background process trace file. Correct the problem mentioned in the messages. Then shut down and restart the instance. If the trace file mentions any other background process messages, then check the trace file for the mentioned process until the root message is found.

ORA-16209 Logical standby dictionary build failed to complete.

Cause: The logical standby dictionary build process terminated abnormally.

ORA-16210 Logical standby coordinator process terminated with error

Cause: The logical standby coordinator process terminated abnormally.

ORA-16211 unsupported record found in the archived redo log

Cause: Log apply services encountered a record in the archived redo log that could not be interpreted.

Action:

Use DBMS_LOGSTDBY.INSTANTIATE_TABLE to re-create the table on the standby database or simply drop the table if it's unimportant.
ALTER DATABASE START LOGICAL STANDBY APPLY;
Examine the current_scn column in the DBA_LOGSTDBY_EVENTS view to determine which log file contains the unsupported record.
Provide the log file to Oracle Support Services.

ORA-16212 number processes specified for APPLY is too great

Cause: Logical standby apply engine was started with more processes requested than are available.

Action: Adjust the values of the initialization parameters PROCESSES and PARALLEL_MAX_SERVERS, or the MAX_SLAVES parameter seen in the DBA_LOGSTDBY_PARAMETERS view.

ORA-16213 ddl encountered, stopping apply engine

Cause: stop_on_ddl callout specified and DDL was encountered.

Action: Either disable stop_on_ddl callout or remove DDL.

ORA-16214 apply stalled for apply delay

Cause: A delay has been specified on the primary database for this destination.

Action: Either turn off the delay on the primary or use DBMS_LOGSTDBY.APPLY_UNSET('APPLY_DELAY'); to override.

ORA-16501 the Data Guard broker operation failed

Cause: The Data Guard broker operation failed.

Action: See other messages for details.

ORA-16502 the Data Guard broker operation succeeded with warnings

Cause: The Data Guard broker operation succeeded with warnings.

Action: See other messages for details.

ORA-16503 site ID allocation failure

Cause: Number of sites in the Data Guard configuration has exceeded the limit.

Action: Delete unused sites.

ORA-16504 the Data Guard configuration already exists

Cause: A request to create a Data Guard configuration was made on a site that is part of an existing configuration.

Action: Delete the existing configuration if you desire to create a new configuration.

ORA-16505 site ID is invalid

Cause: The request contained an invalid site ID.

Action: Make the request again with a valid site ID.

ORA-16506 out of memory

Cause: Process exceeded private or shared memory limits.

Action: Check for memory leaks, increase system parameters, and restart.

ORA-16507 unrecognized request identifier

Cause: The specified request identifier was not recognized by the Data Guard broker.

Action: Re-issue the request using a valid request identifier.

ORA-16508 channel handle not initialized

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16509 the request timed out

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16510 messaging error using ksrwait

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16511 messaging error using ksrget

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16512 parameter exceeded maximum size limit

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16513 maximum requests exceeded

Cause: Non-blocking commands were issued but responses are not read or the commands did not complete execution.

Action: Read pending responses or delete outstanding requests and try again.

ORA-16514 the request was not found

Cause: An attempt was made to read a response but a matching request was not found.

Action: Verify request identifier is valid and references a previously issued request.

ORA-16515 no rcv channel

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16516 the resource state is invalid for the attempted operation

Cause: The broker will return this error for switchover operations and for resource state change operations. If this error is returned for a switchover operation, then the broker has determined that either:

The sites changing roles are offline.
The primary database is not shipping log files.
The standby database that will become the primary is not applying log files.

The broker returns this error for resource state change operations if the resource state specified is invalid for the resource.

Action: If this error is returned when attempting a switchover operation, then make sure that:

The sites changing roles are online.
The primary database is shipping log files.
The standby database is applying log files.

If this error is returned when attempting a resource state change operation, then make sure you specify a valid state for the resource.

ORA-16517 the object handle is invalid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16518 unable to allocate virtual instance id

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16519 the resource handle is invalid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16520 unable to allocate resource id

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16521 unable to create generic template id

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16522 generic template not found

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16523 property count exhausted

Cause: Total number of resource properties exceeded the limit.

ORA-16524 unsupported operation

Cause: A command or option is not supported in this release.

Action: Contact Oracle Support Services.

ORA-16525 the Data Guard broker is not yet available

Cause: The Data Guard broker process has not yet been started, is initializing, or has failed to start.

Action: If the broker has not been started, then set DG_BROKER_START to true and allow the broker to finish initializing before making the request. If the broker failed to start, then check the Data Guard log for possible errors. Otherwise, retry the operation.

ORA-16526 unable to allocate task element

Cause: The Data Guard broker was unable to allocate memory for a request.

Action: Increase the size of your SGA.

ORA-16527 unable to allocate SGA heap

Cause: The Data Guard broker was unable to allocate a heap within the SGA.

Action: Increase SGA memory.

ORA-16528 unable to allocate PGA heap

Cause: No space in PGA to allocate heap.

Action: Increase process virtual memory.

ORA-16529 bad sender id

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16530 invalid buffer or length

Cause: A NULL buffer or a length of zero was specified.

Action: Correct command parameters and retry.

ORA-16531 unable to post message

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16532 Data Guard configuration does not exist

Cause: The Data Guard configuration does not exist.

Action: Create a DRC prior to issuing other requests.

ORA-16533 inconsistent Data Guard broker state

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16534 no more requests accepted

Cause: The Data Guard broker returns this status when:

A failover operation has been submitted or is currently in progress
A switchover operation has been submitted or is currently in progress
An instance restart is pending for one or more sites

Action: Wait until the operation is complete and then re-issue the request.

ORA-16535 failover request rejected

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16536 unknown object type

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16537 child count exceeded

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16538 no match on requested item

Cause: The Data Guard broker did not recognize the specified property or state name.

Action: Verify command parameters and re-issue the request.

ORA-16539 task element not found

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16540 invalid argument

Cause: One of the arguments for the specified request is invalid for the request type. In the case of failover, the failover level must be specified. That is, a graceful failover or a forced failover.

Action: Verify arguments and then re-issue the request.

ORA-16541 site is not enabled

Cause: The site specified in the request is not enabled.

Action: Select an enabled site and re-issue the request.

ORA-16542 unrecognized operation

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16543 invalid request made to broker

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16544 unable to make request

Cause: The Data Guard broker was unable to accept the request.

Action: Contact Oracle Support Services.

ORA-16545 unable to get response

Cause: The Data Guard broker was unable to return the result of a previous request.

Action: Contact Oracle Support Services.

ORA-16546 missing or invalid piece

Cause: The piece of the request to return was not specified or is invalid.

Action: Specify the piece of the response starting from 1.

ORA-16547 unable to delete request

Cause: The Data Guard broker was unable to delete the given request.

Action: Contact Oracle Support Services.

ORA-16548 the resource is not enabled

Cause: An attempt was made to modify or query a disabled Data Guard resource. This error is also returned on an attempt to enable, modify, or query a resource that the broker has permanently disabled. A permanently disabled resource cannot be re-enabled. The broker permanently disables site resources when it detects that the database on that site needs to be reinstantiated. The broker also permanently disables sites that lag behind in terms of DRC Unique ID sequence value.

Action: If the resource is not permanently disabled, enable the resource and re-issue the request.

ORA-16549 invalid string

Cause: A request contains an invalid or NULL string value.

Action: Correct command parameters and retry.

ORA-16550 truncated result

Cause: A string property value was truncated due to insufficient buffer size.

Action: Specify a larger recieve buffer.

ORA-16551 short string copied

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16552 the Data Guard broker process (DMON) failed to start

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16553 the Data Guard broker process (DMON) failed to shutdown

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16554 translation not valid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16555 the Data Guard resource is not active

Cause: An operation was attempted on a resource that is currently not active (off path).

Action: Verify that the resource is active.

ORA-16557 the resource is already in use

Cause: An attempt was made to create a duplicate resource.

Action: Check the resource to be added and be sure there are no duplicates.

ORA-16558 the site specified for switchover is not a standby

Cause: An attempt was made to switchover to a site that is not a standby site.

Action: Locate an enabled standby site and select that site as the target of the switchover.

ORA-16559 out of memory at string

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16560 unable to convert document, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16561 must use ONLINE parent state, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16562 intended_state not used here, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16563 unable to add value, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16564 lookup failed, syntax error at string

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16565 duplicate property, syntax error at "string"

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16566 unsupported document type

Cause: The submitted XML document is not supported.

Action: Correct the errors and resubmit the request.

ORA-16567 Data Guard broker internal parser error at "string"

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16568 cannot set property string

Cause: The named property could not be modified. The property may not be editable or may not exist.

Action: Retry the operation with a valid property.

ORA-16569 Data Guard configuration is not enabled

Cause: The requested operation requires the Data Guard configuration to be enabled.

Action: Enable the Data Guard configuration and re-issue the request.

ORA-16570 Operation requires restart of site "string"

Cause: Some Data Guard broker operations require the given site to be shut down and restarted.

Action: If the client has not already done so, then shut down the Oracle instance at the given site and then restart it.

ORA-16571 Data Guard configuration file creation failure

Cause: The Data Guard broker was unable to create the configuration file on permanent storage.

Action: Verify space, permissions, and filename as indicated by the DG_BROKER_CONFIG_FILE[1 | 2] parameter and retry.

ORA-16572 Data Guard configuration file not found

Cause: The Data Guard broker configuration file is either unavailable or does not exist.

Action: Verify that the configuration file was successfully created. If the DG_BROKER_CONFIG_FILE[1 | 2] parameter was changed, then ensure the filename on disk and the parameter value match, there is space on the device, and you have the right permissions.

ORA-16573 attempt to change configuration file in an enabled DRC

Cause: An attempt was made to change the Data Guard broker configuration file parameter while a DRC was enabled.

Action: Disable the configuration and shut down the Data Guard broker before changing this value. Also be sure to rename the file at the operating system level.

ORA-16574 switchover disallowed when required resources are offline

Cause: Switchover fails because the primary database resource and/or the designated standby database resource are offline.

Action: Check the states of the configuration, primary site, primary database resource, standby site, and standby database resource. Set their states to ONLINE if necessary.

ORA-16575 request terminated at broker discretion

Cause: This status is returned when the Broker terminates a user-initiated request. The broker will terminate all other current and pending requests when it begins processing a failover request. These other requests are terminated with this status.

Action: No action required.

ORA-16576 failed to update Data Guard configuration file

Cause: A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.

Action: Contact Oracle Support Services.

ORA-16577 corruption detected in Data Guard configuration file

Cause: The Data Guard broker detected errors while loading the configuration file.

Action: Contact Oracle Support Services.

ORA-16578 failed to read Data Guard configuration file

Cause: A failure was encountered while the broker was reading the configuration file on permanent storage.

Action: Contact Oracle Support Services.

ORA-16579 bad Data Guard NetSlave state detected

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16580 bad Data Guard NetSlave network link

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16581 Data Guard NetSlave failed to send message to DRCX

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16582 Data Guard connection process received error from NetSlave

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16583 bad Data Guard Connection Process DRCX state

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16584 illegal operation on a standby site

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16585 illegal operation on a primary site

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16586 Data Guard broker unable to update configuration on site

Cause: The Data Guard broker was unable to update the configuration file on a particular site.

Action: Verify that your Oracle Net connections are operational between the Data Guard sites.

ORA-16587 ambiguous object handle

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16588 no more internal buffers

Cause: See trace file.

Action: Contact Oracle Support Services.

ORA-16589 Data Guard Connection process detected a network transfer error

Cause: The Data Guard Connection Process (DRCX) detected an error while transferring data from one site to another. This error is returned in the following situations:

While transmitting the configuration file between sites, DRCX detected an inconsistency in the block count of the file.
The DRCX process got an error while writing the configuration file.

Action: Contact Oracle Support Services.

ORA-16590 no primary established in Data Guard configuration

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16591 unknown field "string" in document

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16592 missing field "string" in document

Cause: There was an error at the given token.

Action: Correct the errors and resubmit the request.

ORA-16593 XML conversion failed

Cause: There was an error in the XML request document.

Action: Correct the errors and resubmit the request.

ORA-16594 string process discovered that DMON process does not exist

Cause: The Data Guard NetSlave (NSV*) processes discovered that the Data Guard broker process (DMON) is not running.

Action: Check the Data Guard console log and DMON process trace file to determine why the DMON process is missing.

ORA-16595 NetSlave process string failed to terminate

Cause: The specified NetSlave process did not terminate at the request of the Data Guard broker.

Action: Contact Oracle Support Services.

ORA-16596 site is not a member of the Data Guard configuration

Cause: A request was made on a site that is not a member of the Data Guard configuration.

Action: Re-issue the request on a site that is a part of the configuration.

ORA-16597 Data Guard broker detects two or more primaries

Cause: The Data Guard broker has detected two or more primaries in the configuration and cannot continue.

Action: Contact Oracle Support Services.

ORA-16598 The Data Guard broker has detected a mismatch in configuration

Cause: The Data Guard broker on this site has detected a mismatch in configuration generation. This can occur when the primary site has a stale configuration.

Action: Contact Oracle Support Services.

ORA-16599 The Data Guard broker has detected a stale configuration

Cause: The Data Guard broker has detected a stale configuration during initialization on this site.

Action: The broker will automatically resolve this situation once the primary site completes its initialization.

ORA-16600 Failover operation can only be submitted on target site

Cause: This error is returned when a failover request specifies a different site than the site the client is currently connected to.

Action: Explicitly connect to the site you wish to failover to and re-issue the failover request.

ORA-16601 site contains required resources that are disabled

Cause: The Data Guard broker detected disabled, required resources prior to performing an operation that needs those resources to be enabled.

Action: Enable all required resources and re-issue the request.

ORA-16602 resource must be disabled to perform this operation

Cause: An attempt was made to modify a resource that can only be changed while that resource is disabled.

Action: Disable the resource and re-issue the request.

ORA-16603 Data Guard broker detected mismatch in configuration ID

Cause: The Data Guard broker on this site has detected a mismatch in configuration Unique ID. This can occur if the original configuration was re-created while this site was disconnected from the network or the same site was added to two different configurations.

Action: Make sure the site belongs to only one configuration. Remove Data Guard broker configuration files and restart the server.

ORA-16604 unable to describe template using package "string"

Cause: The Data Guard broker was unable to execute the OnDescribe function in the named package.

Action: Verify that the named package is loaded on the primary site. Also verify that the OnDescribe function is in the package.

ORA-16605 unable to delete template, template is in use

Cause: The Data Guard broker was unable to delete the template because the template is still being used by one or more resources.

Action: Delete all resources using the template before deleting the template. You cannot delete the database template.

ORA-16606 unable to find property "string"

Cause: The named property does not exist.

Action: Specify a valid property name and re-issue the request.

ORA-16607 one or more sites have failed

Cause: The Data Guard broker detected a failure on one or more sites.

Action: Locate the sites with a failure status and correct it.

ORA-16608 one or more sites have warnings

Cause: The Data Guard broker detected a warning status on one or more sites.

Action: Locate the sites with a warning status and correct it.

ORA-16609 one or more resources have failed

Cause: The Data Guard Broker detected a failure on one or more resources on a site.

Action: Locate the resources with a failure status and correct it.

ORA-16610 one or more resources have warnings

Cause: The Data Guard broker detected a warning status on one or more resources on a site.

Action: Locate the resources with a warning status and correct it.

ORA-16611 operation aborted at user request

Cause: The Data Guard broker aborted an operation at the user's request.

Action: No action required.

ORA-16612 string value too long for attribute "string"

Cause: The string value for the named attribute is too long.

Action: Use a shorter string.

ORA-16613 initialization in progress for site

Cause: The site received a directive to change its initialization state or a change in its configuration before it has completed initialization.

Action: Wait until the site has completed initialization before issuing requests to modify run-time state or configuration.

ORA-16614 object has an ancestor that is disabled

Cause: A request to enable an object that has an ancestor that is disabled was received by the server. The Data Guard broker has enabled the object to the extent that it can, but cannot fully enable the object until its ancestor is enabled.

Action: Determine the ancestor object that is disabled and enable that ancestor prior to enabling the child object.

ORA-16617 Unknown object identifier specified in request

Cause: The Data Guard broker returns this error when the object identifier specified in the request is invalid or unknown. For example, this error is returned if an invalid or unknown site object identifier is specified in a request that requires a site object identifier.

Action: Verify that a valid object identifier was specified in the request and then re-issue the request.

ORA-16618 response document of size "string" bytes is too large

Cause: The document response cannot be returned because the size of the document is too large. This can occur when displaying the Data Guard console log.

Action: View the console log on the given site directly.

ORA-16619 Health Check timed out

Cause: This status is returned when the Data Guard broker could not reach a standby site during routine health check.

Action: This typically indicates a network problem where the standby site is unable to respond to the primary within the predefined time frame.

ORA-16620 one or more sites could not be contacted for a delete operation

Cause: This status is returned when the Data Guard broker could not reach one or more standby sites for either a delete site or a delete configuration operation.

Action: This typically indicates a network problem where the standby site is unable to respond to the primary. In the event of this situation, examine the Data Guard broker log file on the primary site to determine which standby sites could not be reached. Then for each standby site not reached, connect to that site and shut down the broker by setting the DG_BROKER_START initialization parameter to false. After the broker has been shut down on the standby site, locate the Data Guard broker configuration files from the standby site's DG_BROKER_CONFIG_FILE[1 | 2] parameter values and delete them.

ORA-16621 host and SID names for create site must be unique

Cause: This status is returned when an attempt is made to add a site whose host and SID names match those of an existing site.

Action: Verify that you have specified a unique host and SID name pair for the new site you wish to add. This can be done by checking that there are no sites with the same host and SID names.

ORA-16622 two or more Broker sites resolve to the same physical site

Cause: This status is returned when the Broker determines that there are multiple site objects referring to the same physical or material site.

Action: Examine the host names, SID names, and connect descriptors of all sites in the configuration and verify that there are not two or more sites that refer to the same physical site. If you detect this situation, then correct the site definition to eliminate the ambiguity.

ORA-16623 stale DRC UID sequence number detected

Cause: This status is returned when the Broker detects a stale sequence value during bootstrap or during health check. The sequence value is changed each time a role change occurs. A site that is unavailable for the role change operation will end up with a stale sequence number. Should that site attempt to rejoin the configuration, the broker will determine that it missed a role change and disable that site. The broker permanently disables the site since it may no longer be a viable standby site for the new primary.

Action: Examine the configuration and the sites that were permanently disabled to determine if they require manual intervention.

ORA-16624 broker protocol version mismatch detected

Cause: This status is returned when the Broker detects a network protocol version number mismatch. This can happen if the sites in question are not running the same release of Oracle. The broker will permanently disable the sites that do not have the same network protocol version number as the primary.

Action: Examine the release of Oracle installed on all sites to make sure they are identical. Once the Oracle releases are the same on all sites, delete and re-add the sites that were permanently disabled.

ORA-16625 cannot reach the primary site

Cause: This status is returned when the Broker rejects a write operation requested by the client when the primary site is not reachable from the site the request is made. All write operations made to the DataGuard configuration must be processed by the primary site.

Action: Check your network connection from the site your client is connected to, to the primary site. Alternatively, you can connect your client to a different site in the DataGuard Configuration and try your request again.

ORA-16626 failed to enable specified object

Cause: This status is returned when the broker fails to enable an object (most typically a standby site). You can expect to see this status when attempting to enable a standby site that:

Cannot locate itself in the configuration
Fails to distiguish itself from two or more site objects in the configuration
Determines it was not part of a change of primary due to failover

Action: To correct the problem, try one of these actions:

Confirm that the host and SID names you specified when you created the site exactly match the values in the HOST_NAME and INSTANCE_NAME columns of V$INSTANCE.
Confirm that you have not created two or more sites with the same connect descriptor. That is, the site objects should not lead you to the same material site.
If you had performed a failover and have re-instantiated your old primary site (or standby site that had to be reinstantiated), then make sure the Data Guard Broker configuration files have been removed from that site. Do NOT remove the configuration files that are in use by the new primary.

ORA-16627 no standby databases support overall protection mode

Cause: This status is returned in the following situations:

The Broker rejects an attempt to change the configuration's overall protection mode since it could not find any online, managed standby databases that support the proposed protection mode.
The Broker rejects an attempt to enable the configuration if it determines that there are no online managed standby databases that support the overall protection mode.
The Broker rejects an attempt to disable or delete a site or database resource, that if disabled or deleted, would result in no standby databases that support the configuration's overall protection mode.
The Broker rejects an attempt to set the configuration offline if doing so would violate the configuration's overall protection mode.
The Broker rejects an attempt to set a standby site or database offline if doing so would violate the configuration's overall protection mode.
The Broker rejects a switchover attempt if doing so would violate the configuration's overall protection mode.
The Broker returns this error during a health check.

Action:

If changing the overall protection mode, then confirm that at least one standby database satisfies the new protection mode.
For enable failures, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.
For delete and disable failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode.
For the state change failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If setting the configuration OFFLINE, you may have to downgrade the protection mode setting to maximum performance beforehand.
For switchover failures, confirm that at least one other standby database has a LogXptMode configuration property setting that supports the overall protection mode. If your configuration contains a primary and a single standby, then ensure that the LogXptMode configuration property established for the primary site supports the overall protection mode. After the switchover the old primary will become the standby and its LogXptMode configuration property setting must support the overall protection mode.
For health check error, confirm that at least one standby database has a LogXptMode configuration property setting that supports the current overall protection mode.

ORA-16628 The Broker protection mode is inconsistent with the database setting

Cause: The Data Guard Broker protection mode saved in metadata is inconsistent with the actual database setting.

Action: Reset the protection mode through the Data Guard Broker.

ORA-16629 database reports a different protection level from the protection mode

Cause: The actual protection level supported by the standby database is different from the protection mode set on the primary. This is likely caused by the log transport problems.

Action: Check the database alert logs and Data Guard Broker console logs for more details. Check the log transport status. Make sure at least one standby log transport is supporting the protection mode and that the network to the standby has no problems.

ORA-16701 generic resource guard request failed

Cause: Request to modify or query the resource failed.

Action: Check the Data Guard console log for the reason for the failure, and re-issue the request.

ORA-16702 generic resource manager warning

Cause: Request to modify or query the resource resulted in a warning.

Action: Check the console log for the reason for the warning, and re-issue the request if necessary.

ORA-16703 status of request is unknown

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16704 a previous set state operation is pending

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16705 severe internal error in resource guard

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16706 no resource guard is available

Cause: No resource guard is available to service the request.

Action: Contact Oracle Support Services.

ORA-16707 the value supplied to resource guard is invalid

Cause: The value specified in the request is invalid.

Action: Check value and re-issue the request.

ORA-16708 the state supplied to resource guard is invalid

Cause: The state name specified is invalid for the resource.

Action: Check the state name and re-issue the request.

ORA-16709 the resource guard is busy and cannot service the request

Cause: Request to resource guard failed because the guard is busy.

Action: Wait for resource guard to finish previous request and then re-issue the request.

ORA-16710 the resource guard is out of memory

Cause: The resource guard was unable to allocate memory while trying to service a request.

Action: Disable the configuration, shutdown oracle, increase SGA size, and restart.

ORA-16711 the resource guard index is out of bounds

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16712 the resource handle is invalid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16713 the resource guard timed out while servicing the request

Cause: The resource guard timed out while servicing the request.

Action: Verify that the operation is valid for the resource and then re-issue the request.

ORA-16714 the resource guard exceeded its retry limit

Cause: The resource guard exceeded its retry limit while trying to service a request.

Action: Verify that the resource is operational and then re-issue the request.

ORA-16715 the logical standby database requires instantiation

Cause: The resource guard could not execute the request since the logical standby database requires instantiation.

Action: Instantiate logical standby on the site and then re-issue the request.

ORA-16716 clearing parameter LOG_ARCHIVE_DEST failed

Cause: An attempt to clear the LOG_ARCHIVE_DEST initialization parameter failed.

Action: Contact Oracle Support Services.

ORA-16717 clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed

Cause: An attempt to clear the LOG_ARCHIVE_DUPLEX_DEST initialization parameter failed.

Action: Contact Oracle Support Services.

ORA-16718 failed to locate the database resource

Cause: The resource guard was unable to locate the database resource in the configuration.

Action: Add the database resource and then re-issue the request.

ORA-16719 unable to query V$ARCHIVE_DEST fixed view

Cause: A SQL statement to query V$ARCHIVE_DEST failed.

Action: Test and clear the problem using SQL*Plus.

ORA-16720 no available LOG_ARCHIVE_DEST_n parameters to use

Cause: All LOG_ARCHIVE_DEST_n parameters have been defined.

Action: Set some of the LOG_ARCHIVE_DEST_n parameters to an empty string.

ORA-16721 unable to set LOG_ARCHIVE_DEST_n parameters

Cause: An attempt of setting some of the LOG_ARCHIVE_DEST_n parameters failed.

Action: Check the Data Guard console log and database alert logs for further details.

ORA-16722 unable to set LOG_ARCHIVE_DEST_STATE_n parameters

Cause: An attempt of setting some of the LOG_ARCHIVE_DEST_STATE_n parameters failed.

Action: Check the Data Guard console log and database alert logs for further details.

ORA-16723 the connect descriptor is missing from V$ARCHIVE_DEST

Cause: The resource guard was unable to locate a connect descriptor to a certain standby site in V$ARCHIVE_DEST.

Action: Check the Data Guard console log for further details. One may need to reset log transport service.

ORA-16724 the intended state for resource has been set to OFFLINE

Cause: The intended state of the resource has been set to offline.

Action: If resource is managed, change intended state to online.

ORA-16725 the phase supplied to resource manager is invalid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16726 the external condition supplied to resource manager is invalid

Cause: This is an internal error.

Action: Contact Oracle Support Services.

ORA-16727 resource guard cannot close database

Cause: The resource guard could not close the database.

Action: If there are any active sessions connected to the database, then terminate them and re-issue the request.

ORA-16728 Log archive destination could not be set

Cause: The resource guard could not set the log archive destination.

Action: Check the Data Guard console log and the Oracle Alert log for further details.

ORA-16729 Error executing dbms_logstdby.log procedure

Cause: Logical standby package may not be installed.

Action: Install logical standby packages and re-issue the request.

ORA-16730 Error executing dbms_logstdby.skip_txn procedure

Cause: Logical standby package may not be installed.

Action: Install logical standby packages and re-issue the request.

ORA-16731 Error executing dbms_logstdby.unskip_txn procedure

Cause: Logical standby package may not be installed.

Action: Install logical standby packages and re-issue the request.

ORA-16732 Error executing dbms_logstdby.skip procedure

Cause: Logical standby package may not be installed.

Action: Install logical standby packages and re-issue the request.

ORA-16733 Error executing dbms_logstdby.unskip procedure

Cause: Logical standby package may not be installed.

Action: Install logical standby packages and re-issue the request.

ORA-16734 Error executing dbms_logstdby.skip_error procedure

Cause: Logical standby package may not be installed.

Action: Install logical standby packages and re-issue the request.

ORA-16735 Error executing dbms_logstdby.unskip_error procedure

Cause: Logical standby package may not be installed.

Action: Install logical standby packages and re-issue the request.

ORA-16736 Standby log archive destination parameter could not be set

Cause: Resource guard could not set the standby log archive destination parameter.

Action: Check the Data Guard console log for further details.

ORA-16737 Log archive format parameter could not be set

Cause: Resource guard could not set the log archive format parameter.

Action: Check the Data Guard console log for further details.

ORA-16738 Database file name convert parameter could not be set

Cause: Resource guard could not set the database file name convert parameter.

Action: Check the Data Guard console log for further details.

ORA-16739 Log file name convert parameter could not be set

Cause: Resource guard could not set log file name convert parameter.

Action: Check the Data Guard console log for further details.

ORA-16740 Log archive trace parameter could not be set

Cause: Resource guard could not set log archive trace parameter.

Action: Check the Data Guard console log for further details.

ORA-16741 Control files parameter could not be set

Cause: Resource guard could not set the control files parameter.

Action: Check the Data Guard console log for further details.

ORA-16742 lock name trace parameter could not be set

Cause: Resource guard could not set lock name trace parameter.

Action: Check the Data Guard console log for further details.

ORA-16743 FAL client parameter could not be set

Cause: Resource guard could not set FAL client parameter.

Action: Check the Data Guard console log for further details.

ORA-16744 FAL server parameter could not be set

Cause: Resource guard could not set FAL server.

Action: Check the Data Guard console log for further details.

ORA-16745 Resource guard encountered error during database dismount

Cause: Resource guard could not dismount database.

Action: Check the Data Guard console log for further details.

ORA-16746 Resource guard encountered error during database mount

Cause: Resource guard could not mount database.

Action: Check the Data Guard console log for further details.

ORA-16747 Logical standby guard could not be turned on

Cause: Resource guard could not turn on the logical standby guard.

Action: Check the Data Guard console log for further details.

ORA-16748 Resource guard encountered errors during database open

Cause: Resource guard could not open database.

Action: Check the Data Guard console log for further details.

ORA-16749 Resource guard encountered errors in switchover to logical primary

Cause: Resource guard could not prepare to switch to logical primary.

Action: Check the Data Guard console log for further details.

ORA-16750 Resource guard encountered errors while activating logical primary

Cause: Resource guard could not activate logical primary.

Action: Check the Data Guard console log for further details.

ORA-16751 Resource guard encountered errors in switchover to primary

Cause: Resource guard could not prepare to switch to primary.

Action: Check the Data Guard console log for further details.

ORA-16752 Resource guard could not mount standby

Cause: Resource guard could not mount standby.

Action: Check the Data Guard console log for further details.

ORA-16753 Resource guard could not open standby database

Cause: Resource guard could not open standby database.

Action: Check the Data Guard console log for further details.

ORA-16754 Resource guard could not activate standby

Cause: Resource guard could not activate standby.

Action: Check the Data Guard console log for further details.

ORA-16755 Resource guard could not dismount standby

Cause: Resource guard could not dismount standby.

Action: Check the Data Guard console log for further details.

ORA-16756 Resource guard could not open standby read-only

Cause: Resource guard could not open standby read-only.

Action: Check the Data Guard console log for further details.

ORA-16757 Resource guard could not get property

Cause: Resource guard failed to get property.

Action: Check the Data Guard console log for further details.

ORA-16758 Resource guard could not verify property

Cause: Resource guard failed to verify property.

Action: Check the Data Guard console log for further details.

ORA-16759 Resource guard unable to start logical apply engine with initial SCN

Cause: Resource guard failed to start logical apply engine with an initial SCN.

Action: Check the Data Guard console log for further details.

ORA-16760 Resource guard could not start logical apply engine

Cause: Resource guard failed to start logical apply engine.

Action: Check the Data Guard console log for further details.

ORA-16761 Resource guard could not stop logical apply engine

Cause: Resource guard failed to stop logical apply engine correctly.

Action: Check the Data Guard console log for further details.

ORA-16762 Invalid database state

Cause: Database is not in the intended state.

Action: Determine the reason for invalid state, and re-issue get status request.

ORA-16763 Log transport service for some site unexpectedly online

Cause: Log transport service for some site is online when it should be offline.

Action: Check the Data Guard console log for further details. If necessary, stop the log transport service for the site.

ORA-16764 Log transport service for some site unexpectedly offline

Cause: Log transport service for some site is offline when it should be online.

Action: Check the Data Guard console log for further details. If necessary, start the log transport service.

ORA-16765 Physical apply service unexpectedly online

Cause: Physical apply service is online when it should be offline.

Action: If necessary, stop the physical apply service.

ORA-16766 Physical apply service unexpectedly offline

Cause: Physical apply service is offline when it should be online.

Action: If necessary, start the physical apply service.

ORA-16767 Logical apply service unexpectedly online

Cause: Logical apply service is online when it should be offline.

Action: If necessary, stop the logical apply service.

ORA-16768 Logical apply service unexpectedly offline

Cause: Logical apply service is offline when it should be online.

Action: If necessary, start the logical apply service.

ORA-16769 Error executing apply_set procedure

Cause: There was an error executing dbms_logstdby$apply_set procedure.

Action: Check the values for the property, and set configuration property again.

ORA-16770 Error executing apply_unset procedure

Cause: There was an error executing dbms_logstdby$apply_unset procedure.

Action: Check the values for the property, and set configuration set property again.

ORA-16771 Error starting ARCH process(es)

Cause: There was an error starting the archival processes.

Action: Check the Data Guard console log for further details.

ORA-16772 Error in switching over between primary and standby databases

Cause: There was an error during switchover of primary and standby databases.

Action: Check the Data Guard console log for further details.

ORA-16773 Error in starting the physical apply service (MRP process)

Cause: There was an error in starting the physical apply service (MRP process).

Action: Check the Data Guard console log for further details.

ORA-16774 Error in stopping the physical apply service (MRP process)

Cause: There was an error in stopping the physical apply service (MRP process).

Action: Check the Data Guard console log for further details.

ORA-16775 The physical apply service terminated prematurely

Cause: The physical apply service terminated prematurely with an error.

Action: Check the Data Guard console log and Oracle Alert log for further details.

ORA-16776 Health check of the log transport service failed

Cause: Due to some internal failure, the database resource guard cannot complete the health check of the log transport service.

Action: Check the Data Guard console log and Oracle Alert log for further details.

ORA-16777 Unable to find the destination entry of a site in V$ARCHIVE_DEST

Cause: Some destination may be manually deleted, or no entry is available for Data Guard.

Action: Check the Data Guard console log and Oracle Alert log for further details. One may need to reset log transport service.

ORA-16778 The log transport service for some site has an error

Cause: Some problem in communicating with a standby site causes the log transport to fail.

Action: Check the Data Guard console log and Oracle Alert log for further details. Query the LogXptStatus property to see the error message.

ORA-16779 The destination parameter of some site has wrong syntax

Cause: The destination is defined in the initialization parameter file with wrong syntax, and the Data Guard broker fails to update the destination when the log transport is turned on.

Action: Check the Data Guard console log to see which site has the problem. Fix the syntax error in the initialization parameter file or remove the entry. Check if the syntax of the log transport related properties are correct.

ORA-16780 Some site has used up its quota

Cause: Some site has used up its quota for storing archived redo logs.

Action: Check the Data Guard console log to see which site has the problem. Remove some archived logs at the standby site or increase its quota.

ORA-16781 The status of log transport service for some site is unknown

Cause: Log transport to some site has an unknown status.

Action: Check the Data Guard console log and Oracle Alert log for further details.

ORA-16782 Unable to get values of some critical configurable properties

Cause: Log transport cannot be turned on because some critical property values cannot be retrieved from Data Guard metadata.

Action: Check the Data Guard console log and Oracle Alert log for further details.

ORA-16783 Some critical configurable property has not been set

Cause: Log transport cannot be turned on because some critical property has not been set.

Action: Check the Data Guard console log to see which property has not been set, and set it properly.

ORA-16784 The site name given in property Dependency or Alternate is incorrect

Cause: Site name provided in property Dependency or Alternate is wrong.

Action: Reset property to the correct name of the site.

ORA-16785 The database is not in ARCHIVELOG mode

Cause: The database is in NOARCHIVELOG mode, when it is either a primary database or a standby database that is being switched over to the primary database.

Action: Reset the primary database to ARCHIVELOG mode by issuing the ALTER DATABASE ARCHIVELOG statement.

ORA-16786 Resource guard cannot access Data Guard metadata

Cause: The Data Guard broker configuration files do not exist or the resource guard cannot access the Data Guard metadata.

Action: Check the Data Guard console log for further details.

ORA-16788 Unable to set one or more database configuration property values

Cause: This situation occurs when database resource guard attempts to set database configuration property values into the database by issuing ALTER SYSTEM or ALTER DATABASE statements. Typical causes of this error are:

The values of log transport related properties have syntax errors
The Value of LogArchiveTrace is out of range
Database initialization parameter STANDBY_FILE_MANAGEMENT cannot be set to AUTO because the database compatability is not set to 9.0.0.0.0 or higher.

Action: Check the Data Guard console log to see which property has the problem and reset the property correctly.

ORA-16789 Missing standby redo logs

Cause: Standby redo logs are missing when needed for certain log transport modes.

Action: Check the Data Guard documentation to create standby redo logs on the standby.

ORA-16790 The value of the configurable property is invalid

Cause: An invalid property value was entered.

Action: Reset the value to a correct one.

ORA-16791 Unable to check the existence of the standby redo logs

Cause: The database may not be mounted, or the query of V$STANDBY_LOG failed.

Action: Bring the database to an online state, or fix the problem during the query of V$STANDBY_LOG.

ORA-16792 Some configurable property value is inconsistent with the database setting

Cause: The values of one or more configurable properties are inconsistent with database in-memory settings or SPFILE settings. This may be caused by a user operation on database outside of the Data Guard broker control.

Action: Query property InconsistentProperties on the site or check the Data Guard console log to find which properties are inconsistent. Reset these properties to make them consistent with the database settings.

ORA-16793 Logical Standby Database Guard is unexpectedly OFF

Cause: The logical standby database guard is OFF.

Action: Issue the ALTER DATABASE GUARD ALL statement to turn the guard ON and verify that Data Guard health check error/warning is cleared.

ORA-16794 Database Guard is ON for primary database

Cause: Primary database has database guard ON, which is not normal.

Action: Issue the ALTER DATABASE GUARD NONE statement to turn the guard OFF and verify that Data Guard health check error/warning is cleared.

ORA-16795 Database resource guard detects that database reinstantiation is required

Cause: In the act of failover or switchover, the database resource guard may detect that reinstantiation of the database is necessary due to the impending role change. This occurs when the database resource guard recognizes a situation in which the database in question cannot be a viable standby database for the new primary database.

Action: Reinstantiate the database on the site indicated by the broker and then re-add that site to your broker configuration.

ORA-16796 One or more property cannot be imported from database

Cause: Importing existing database settings into the Data Guard properties failed for one or more properties. The cause may be that the database is not mounted or open, or the connection to the standby database being imported is down.

Action: Check the Data Guard console log to find more details about the problem.

ORA-16797 SPFILE is missing in the Data Guard Broker environment

Cause: Server parameter file is not being used in the database, or the resource guard failed to retrieve the status of the SPFILE.

Action: Issue a CREATE SPFILE='...' FROM PFILE='...' statement to create an SPFILE, and restart the database to use the SPFILE.

ORA-16798 Unable to complete terminal recovery on the standby

Cause: Terminal recovery on the standby failed during the graceful failover operation.

Action: Check Data Guard console log and alert logs to see more details on the reason of the failure.

ORA-16799 Physical apply service is offline

Cause: Either the Data Guard metadata indicates the physical apply service is turned off, or the recovery process MRP0 is not running. In either of the cases, physical apply related properties cannot be set.

Action: Turn on the physical apply service through Data Guard broker, then reset the physical apply related property again.

ORA-16800 Log transport service for some site is incorrectly set to ALTERNATE

Cause: Log transport service for some site is currently set to ALTERNATE while no other destinations is set to alternate to this site.

Action: Check the Data Guard console log for further details. Reset database state to turn on log transport again if necessary.

ORA-16801 Some log transport related property is inconsistent

Cause: The values of one or more log transport related configurable properties of a standby database resource are inconsistent with the primary's log transport service settings. This may be caused by a user operation on database outside of the Data Guard broker control.

Action: Query property InconsistentLogXptProps on the primary or Check the Data Guard console log to find which properties are inconsistent. Reset these properties on the appropriate standby to make them consistent with the primary's log transport settings.

ORA-16802 Cannot set property 'Alternate' to the primary site name

Cause: Data Guard Broker does not allow the primary site to be an alternate archival destination for a standby site.

Action: Set property Alternate to empty or to the name of a standby site.

ORA-16803 Unable to query a database table or fixed view

Cause: Failed to query a database table or fixed view. The database may not be open or mounted.

Action: Check Data Guard console log for more details.

ORA-16804 One or more configuration properties in metadata have invalid values

Cause: Data Guard Broker health check detects that one or more configuration properties in metadata have invalid values. They may be entered during the disabled period of database resource or through other means.

Action: Check Data Guard console log for more details on which properties have invalid values and reset them through Data Guard Broker.

ORA-16805 Change of LogXptMode property violates overall protection mode

Cause: The standby database resource guard rejected the attempt to change the LogXptMode configuration property for the standby database resource. The rejection was necessary since doing so would violate the overall protection mode for the configuration.

Action: If the LogXptMode configuration property must be changed for the specified standby database resource, then first downgrade the overall protection mode for the configuration. After that operation has completed, you will be able to change the LogXptMode configuration property for the standby database resource.

ORA-16806 Supplemental logging is not turned on

Cause: Supplemental logging is not turned on while there is a logical standby database in the configuration. This could happen either6854// on the primary or on the logical standby that is being switched over to the primary.

Action: Check Data Guard console log for more details. Issue ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY, UNIQUE INDEX) COLUMNS to add supplemental logging.

ORA-16807 unable to set protection mode to the database

Cause: An attempt to issue an ALTER DATABASE SET STANDBY TO ... statement failed.

Action: Check database alter logs and Data Guard console logs for more information.

ORA-16900 Unable to initialize client

Cause: The client could not be initialized.

Action: This is an internal error. Contact Oracle Support Services.

ORA-16901 Unable to initialize environment

Cause: The database environment could not be allocated and initialized.

Action: This is an internal error. Contact Oracle Support Services.

ORA-16902 Unable to allocate handle

Cause: The database handles could not be allocated.

Action: This is an internal error. Contact Oracle Support Services.

ORA-16903 Unable to connect to database

Cause: The specified database was unreachable because it does not exist or was not started.

Action: Correct the request or start the database and try again.

ORA-16904 Unable to set attribute

Cause: The server attributes could not be set.

Action: check additional error messages.

ORA-16905 Failed.

Cause: The given action failed.

Action: check additional error messages.

ORA-16906 Unable to accept commands: no memory

Cause: No memory was available for the program.

Action: Increase memory and try again.

ORA-16907 missing field

Cause: A required field was missing.

Action: Type "help" for syntax and try again.

ORA-16908 Unknown option: "string"

Cause: The given option is not supported.

Action: Try again using the proper command line syntax.

ORA-16909 Fatal Error. quitting...

Cause: A fatal error was encountered.

Action: See additional error messages and contact Oracle Support Services.

ORA-16910 unable to issue command to server

Cause: Commands cannot be issued to the server.

Action: See additional error messages and contact Oracle Support Services.

ORA-16911 Warning:

Cause: An action succeeded with warnings.

Action: See error message and take appropriate action.

ORA-16912 Unknown command "string". Try "help"

Cause: An unknown command was issued.

Action: Try again using a valid command.

ORA-16914 Missing connect string. Try "help"

Cause: The connect string for the database is missing.

Action: Try the command again with a valid connect string.

ORA-16916 Missing site. Try "help"

Cause: The site name is missing.

Action: Try the command again using correct syntax.

ORA-16917 Missing XML document. Try "help"

Cause: The XML document argument was missing.

Action: Try the command again using correct syntax.

ORA-16939 Could not start up "string" as primary

Cause: The named site could not be started in the primary role.

Action: See additional messages.

ORA-16940 Started "string" as new primary

Cause: The named site was started as the new primary site.

Action: No action is required.

ORA-16942 Could not start up "string" as standby

Cause: The named site could not be started in the standby role.

Action: See additional messages..

ORA-16943 Started "string" as standby

Cause: The named site was started as the new primary site.

Action: No action required.

ORA-16944 Failover succeeded. New primary is "string"

Cause: The failover operation succeeded.

Action: No action required.

ORA-16945 Syntax error before or at "string"

Cause: The given command could not be processed because a syntax error occurred at the named token.

Action: Try the command again using valid syntax.

ORA-16946 Site "string" was not found

Cause: The named site could not be found.

Action: Try the command again using a valid site.

ORA-16947 "string" does not run in the primary role

Cause: The named resource does not run in the primary role.

Action: Try the command again using a resource that runs in the primary role.

ORA-16948 "string" does not run in the standby role

Cause: The named resource does not run in the standby role.

Action: Try the command again using a resource that runs in the standby role.

ORA-16949 Resource "string" was not found

Cause: The named resource was not found.

Action: Try the command again using a valid resource.

ORA-16950 Unable to retrieve "string" for editing

Cause: The named object could not be retrieved for editing.

Action: Contact Oracle Support Services.

ORA-16951 manager information not found

Cause: The manager information could not be retrieved for a generic resource.

Action: Contact Oracle Support Services.

ORA-16952 unable to describe configuration

Cause: The configuration could not be described.

Action: The framework could not be contacted. Check to see that the DMON process is running.

ORA-16953 site or resource "string" does not exist

Cause: The named site or resource does not exist.

Action: Try the command again using a valid site or resource.

ORA-16954 a resource cannot run on multiple sites this way

Cause: An attempt was made to create a resource that depends on multiple sites. This is not possible using one command.

Action: Issue the command twice; one with the first site and the second using the second site.

ORA-16955 unable to create or locate template

Cause: The template could not be found.

Action: See additional error messages.

ORA-16956 missing template name

Cause: The template name was omitted from the command.

Action: Try the command again using a valid template name.

ORA-16957 template "string" was not found

Cause: The named template could not be found.

Action: Try the command again using a valid template name.

ORA-16958 unable to convert document

Cause: The document could not be converted.

Action: Contact Oracle Support Services.

ORA-16959 NULL answer from framework

Cause: No answer came from the framework.

Action: The framework is not available. Check to see that the DMON process exists.

ORA-16960 status not available

Cause: The status could not be retrieved.

Action: The framework is not available. Check to see that the DMON process exists.

ORA-16991 ambiguous resource name

Cause: The named resource exists on more than one site.

Action: The request must be more specific. Issue the command again using the ON SITE clause.

ORA-16992 You must restart site "string" manually.

Cause: The operation was successfully completed, and it requires a restart of given site. However, DGMGRL was unable to perform an automatic restart. The user has to shutdown and startup the site manually.

Action: Shut down the given site and start it up.

ORA-17500 ODM err:string

Cause: An error returned by ODM library

Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance.

ORA-17501 logical block size string is invalid

Cause: logical block size for oracle files must be a multiple of the physical block size, and less than the maximum

Action: check parameters in the initialization parameter file.

ORA-17502 ksfdcre: string Failed to create file string

Cause: file creation failed due to either insufficient OS permission or the file already exists

Action: check additional error messages

ORA-17503 ksfdopn: string Failed to open file string

Cause: file open failed due to either insufficient OS permission or the name of file exceeds maximum file name length.

Action: check additional error messages

ORA-17504 ksfddel:Failed to delete file string

Cause: The file thats being deleted is still in use or the process has insufficient permission to delete file.

Action: check additional error messages

ORA-17505 ksfdrsz: string Failed to resize file to size number blocks

Cause: There is insufficient space left on the device or the process has insufficient permission to resize file.

Action: check additional error messages

ORA-17506 I/O Error Simulation

Cause: The i/o request is marked with error because the i/o error simulation event is turned on.

Action: none

ORA-17507 I/O request size string is not a multiple of logical block size

Cause: i/o's are done in multiple of logical block size

Action: Check additional error messages

ORA-17508 I/O request buffer ptr is not alligned

Cause: i/o request buffer should be alligned, check additional information for buffer ptr value

Action: Contact Oracle Support Services.

ORA-17509 Attempt to do i/o beyond block1 offset

Cause: When a file is identified with logical block size of 0, only i/o's to block1 is allowed.

Action: check additional error messages and contact Oracle Support Services.

ORA-17510 Attempt to do i/o beyond file size

Cause: The i/o request points to a block beyond End Of File

Action: check additional error messages and contact Oracle Support Services.

ORA-17610 file 'string' does not exist and no size specified

Cause: An attempt to create a file a file found neither an existing file nor a size for creating the file.

Action: Specify a size for the file.

ORA-17611 ksfd: file 'string' cannot be accessed, global open closed

Cause: An attempt to write to a file which has gone offline/unidentified.

Action: Check for other errno in the stack.

ORA-18000 invalid outline name

Cause: The parser detected a missing or invalid outline name.

Action: reissue the command, specifying a valid outline name.

ORA-18001 no options specified for ALTER OUTLINE

Cause: The parser detected that no clause was specified on the command.

Action: reissue the command, specifying a valid ALTER OUTLINE clause.

ORA-18002 the specified outline does not exist

Cause: Either the outline did not exist to begin with, or a timing window allowed for another thread to drop or alter the outline midstream.

Action: Check for the existence of the outline and try again.

ORA-18003 an outline already exists with this signature

Cause: The signature generation algorithm generates signatures that are 16 bytes in length so it is highly unlikely that any 2 signatures will be identical. This message is raised in such a rare case.

Action: Either reissue the statement that led to the outline being created with some white space added or force the outline to be created in a different category.

ORA-18004 outline already exists

Cause: An outline already exists, either with the specified name, or for the specified SQL text.

Action: Try again with another name.

ORA-18005 create any outline privilege is required for this operation

Cause: Create any outline privilege is required for the attempted operation.

Action: Make sure you have create any outline privilege and retry the operation.

ORA-18006 drop any outline privilege is required for this operation

Cause: Drop any outline privilege is required for the attempted operation.

Action: Make sure you have drop any outline privilege and retry the operation.

ORA-18007 alter any outline privilege is required for this operation

Cause: Alter any outline privilege is required for the attempted operation.

Action: Make sure you have alter any outline privilege and retry the operation.

ORA-18008 cannot find OUTLN schema

Cause: The database creation script that creates this schema must not have been executed.

Action: Review the log files to see what happened when the database was created.

ORA-18009 one or more outline system tables do not exist

Cause: Either the database creation script that creates these tables was not executed or a user accidently deleted the table.

Action: Review the log files to see what happened when the database was created.

ORA-18010 command missing mandatory CATEGORY keyword

Cause: User failed to specify the CATEGORY keyword.

Action: reissue the command with the CATEGORY keyword included.

ORA-18011 the outline specified in the FROM clause does not exist

ORA-18012 select_catalog_role role is required for this operation

ORA-18013 timed out while waiting for resource string

ORA-18014 deadlock detected while waiting for resource string

ORA-18015 invalid source outline signature

Cause: User imported an 8i outline into a 9i database without updating signatures.

Action: Execute dbms_outln.update_signatures.

ORA-19000 missing RELATIONAL keyword

Cause: The keyword RELATIONAL in the work OBJECT RELATIONAL is missing in the XMLTYPE storage clause specification.

Action: Supply the RELATIONAL keyword in the storage clause

ORA-19001 Invalid storage option specified

Cause: An invalid storage option was specified for the XMLType.

Action: Supply a valid storage option.

ORA-19002 Missing XMLSchema URL

Cause: A XML schema URL must be specified in the storage option.

Action: Specify a URL for the XMLSchema.

ORA-19003 Missing XML root element name

Cause: A root element in the XMLSchema must be specified if the XML schema is given.

Action: Specify a root element in the XML schema.

ORA-19004 Duplicate XMLType OBJECT RELATIONAL storage option

Cause: A duplicate storage option for the XMLType column was specified

Action: Specify a single storage option for an XMLType column

ORA-19005 Duplicate XMLType LOB storage option

Cause: A duplicate storage option for the XMLType column was specified

Action: Specify a single storage option for an XMLType column

ORA-19006 XMLType TYPE storage option not appropriate for storage type

Cause: The TYPE option can only be used in case of OBJECT RELATIONAL storage option

Action: Remove the TYPE option or specify an OBJECT RELATIONAL storage for the XMLType column

ORA-19007 Schema and element do not match

Cause: The schema and element specified in the inserted data does not match that of the column

Action: Insert/Update only the XML documents that conform to that particular schema and element.

ORA-19008 Invalid version of the XMLType

Cause: An invalid version of the XMLType was found.

Action: This is possible due to data corruption or an internal error or running an older client against a newer version of the database. Make sure that the version of the client can understand the XMLType in the database.

ORA-19009 Missing XMLSchema keyword

Cause: The XMLSchema keyword is missing

Action: Specify the XMLSchema URL and element name.

ORA-19010 Cannot insert XML fragments

Cause: XML fragments got from extractNode cannot be inserted into the database.

Action: Convert the fragment into a proper XML document before insertion.

ORA-19011 Character string buffer too small

Cause: The string result asked for is too big to return back

Action: Get the result as a lob instead

ORA-19012 Cannot convert XML fragment to the required datatype

Cause: A conversion to a datatype was requested which cannot be performed

Action: The XMLType may contain fragments and other elements which cannot be converted to the appropriate datatype.

ORA-19013 Cannot create VARRAY columns containing XMLType

Cause: An attempt was made to create a VARRAY column which contains a XMLType

Action: You cannot store VARRAYs containing XMLTypes in tables. Use nested tables instead

ORA-19015 Invalid XML tag identifier (string)

Cause: An invalid XML identifier was detected during XML generation.

Action: Fix the offending tag so it does not contain characters or symbols that are not allowed by the XML specification.

ORA-19016 attributes cannot occur after element specifications

Cause: Attributes specified using the "@" identifier can only occur before any other element definition when creating XML.

Action: Change the order of the types so that the attributes occur at the beginning.

ORA-19017 Attributes can only be simple scalars

Cause: Attribute values can only be simple scalar values.

Action: Use only simple datatypes for attribute values.

ORA-19018 Invalid character in XML tag 'string'

Cause: A tag name was found to have an invalid XML character during XML generation.

Action: Rewrite the query so that the generated XML tag, corresponding to a column name or alias, contains only valid characters.

ORA-19019 Invalid context passed to DBMS_XMLGEN.GETXML

Cause: The value of context passed to GETXML was invalid.

Action: Rewrite the query so that the value of context passed to GETXML is valid.

ORA-19020 invalid dereference of XMLType columns

Cause: An attempt was made to dereference the attributes of an XMLType column which is not part of a base table.

Action: You can only dereference the attributes of a base table XMLType column.

ORA-19023 The first argument to UPDATEXML operator has to be an XMLTYPE

Cause: The first argument passed to the update value operator was not an XMLTYPE.

Action: Rewrite the query so that the first argument to the UPDATEXML operator is XMLTYPE.

ORA-19024 Cursor expression must be named

Cause: The value of context passed to GETXML was invalid.

Action: Rewrite the query so that the value of context passed to GETXML is valid.

ORA-19025 EXTRACTVALUE returns value of only one node

Cause: Given XPath points to more than one node.

Action: Rewrite the query so that exactly one node is returned.

ORA-19026 EXTRACTVALUE can only retrieve value of leaf node

Cause: Given XPath does not point to a leaf node.

Action: Rewrite the query so that a leaf node is returned.

ORA-19028 Invalid ADT parameter passed to toObject() function

Cause: The object passed as ADT parameter to sys.XMLType.toObject() is not the same type, or a super-type, of the mapped type.

Action: Pass an object of the correct type to toObject().

ORA-19029 Cannot convert the given XMLType to the required type

Cause: The passed in XMLType could not be converted to the required type.

Action: Binary XMLtype instances or other objects cannot be converted to the required object or collection types.

ORA-19030 Method invalid for non-schema based XML Documents.

Cause: The method can be invoked on only schema based xmltype objects.

Action: Don't invoke the method for non schema based xmltype objects.

ORA-19031 XML element or attribute string does not match any in type string.string

Cause: The passed in XML tag does not match any in the object type.

Action: Pass a valid canonical XML that can map to the given object type.

ORA-19032 Expected XML tag string got string

Cause: When converting XML to object, a wrong tag name was present.

Action: Pass a valid canonical XML that can map to the given object type

ORA-19033 schema specified in the XML document does not match the schema parameter

Cause: When creating schema-based XML, the schema specified in the XML document is different from the schema passed in as the 'schema' parameter.

Action: Change the schema parameter to match the schema specified in the XML document.

ORA-19034 Type not supported during schema generation

Cause: The object type contained a type that is not supported for schema generation.

Action: Use a different type or do not generate a schema.

ORA-19200 Invalid column specification

Cause: All input arguments must be valid columns

Action: Specify a valid list of columns

ORA-19201 Datatype not supported

Cause: The particular datatype is not supported in the XMLGEN operator

Action: Specify only supported datatypes as arguments to the XMLGEN operator

ORA-19202 Error occurred in XML processing string

Cause: An error occurred when processing the XML function

Action: Check the given error message and fix the appropriate problem

ORA-19203 Error occurred in DBMS_XMLGEN processing string

Cause: An error occurred when processing the DBMS_XMLGEN functions

Action: Check the given error message and fix the appropriate problem

ORA-19204 Non-scalar value 'string' is marked as XML attribute

Cause: Only scalar values (that is values which are not of object or collection type) can be marked as XML attribute, that is prefixed by '@'. In this case, a non-scalar value was prefixed with '@'.

Action: Remove the '@' sign, or make the value a scalar.

ORA-19205 Attribute 'string' qualifies a non-scalar value in the select list

Cause: The attribute immediately follows a value of object or collection type in the select list or type definition.

Action: Remove the '@' sign, or make the previous value a scalar.

ORA-19206 Invalid value for query or REF CURSOR parameter

Cause: The queryString argument passed to DBMS_XMLGEN.newContext was not a valid query or REF CURSOR.

Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR.

ORA-19207 scalar parameter string of XMLELEMENT cannot have an alias.

Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.

Action: Remove the AS clause of the scalar element.

ORA-19208 parameter string of function string must be aliased

Cause: The indicated parameter of the XML generation function has not been aliased, although it is an expression.

Action: Specify an alias for the expression using the AS clause.

ORA-19209 invalid or unsupported formatting argument

Cause: An invalid or unsupported formatting argument was supplied.

Action: Change the formatting argument to legal supported values.

ORA-19300 Error occurred in uri processing string

Cause: An error occurred when processing the URL

Action: Check the given error message and fix the appropriate problem

ORA-19320 Host name not specified in HTTP URL

Cause: A host name was not specified in the HTTP url

Action: Specify a host name in the HTTP url when creating the URL string

ORA-19321 Could not open HTTP connection to host (string): port (string)

Cause: A HTTP connection could not be opened to the host

Action: Specify a valid host name and port to connect to

ORA-19322 An error occurred while reading from host (string): port (string)

Cause: An error occurred while reading from the HTTP host

Action: Specify a valid host name and port to read from

ORA-19323 Invalid url string

Cause: The URL must be a valid URL string

Action: Specify a valid url string

ORA-19330 Type 'string'.'string' not installed. Please install the type before using the CREATE_DBURI operator

Cause: The type required for the CREATE_DBURI operator has not been installed correctly.

Action: Read the installation notes to install the type correctly.

ORA-19331 Last argument to CREATE_DBURI operator must be a column

Cause: The final argument to the CREATE_DBURI operator must be a column to which the reference is being created.

Action: Specify a valid column name in the query.

ORA-19332 Invalid column in the CREATE_DBURI operator

Cause: The argument to the CREATE_DBURI operator can only be a column.

Action: Specify a valid column name for the operator

ORA-19333 Invalid flags for the CREATE_DBURI operator

Cause: The flags argument given to the DBURI operator is invalid

Action: Specify a valid flag value (TEXT) for the DBURI operator

ORA-19334 Invalid column specification for CREATE_DBURI operator

Cause: All columns must be valid and pointing to the same table or view

Action: Specify valid list of columns that are from the same table or view.

ORA-19335 Invalid format type object

Cause: An invalid format type object was specified for the XML function

Action: Specify a valid format type object

ORA-19336 Missing XML root element

Cause: The XML being generated does not have an enclosing root element.

Action: The generated XML must have a root element.

Home

Book List

Contents

Index

Master Index

Feedback

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01

Home

Book List

Contents

Index

Master Index

Feedback

Skip Headers

Oracle9i Database Error Messages
Release 2 (9.2)
Part Number A96525-01

Home

Book List

Contents

Index

Master Index

Feedback

12
ORA-19400 to ORA-24279

ORA-19400 System type conflict with object SYS.string

Cause: The user had an object with the same name as one of the system types. The system types were not initialized properly.

Action: Remove the conflicting object and re-run migration.

ORA-19500 device block size string is invalid

Cause: The device block size returned by sequential I/O OSD is invalid.

Action: If the block size was set by using the PARMS option of the Recovery Manager ALLOCATE CHANNEL command, then the specified block size must be changed. If no PARMS option was specified on the ALLOCATE CHANNEL command, then this is an internal error that should be reported to Oracle.

ORA-19501 read error on file "string", blockno string (blocksize=string)

Cause: Read error on input file.

Action: Check the file.

ORA-19502 write error on file "string", blockno string (blocksize=string)

Cause: Write error on output file.

Action: Check the file.

ORA-19503 cannot obtain information on device, name="string", type="string", parms="string"

Cause: Call to get device information returned an error.

Action: Check device name, type, and parameters.

ORA-19504 failed to create file "string"

Cause: Call to create file returned an error.

Action: Check additional messages and check access permissions.

ORA-19505 failed to identify file "string"

Cause: Call to identify the file returned an error.

Action: Check additional messages, and check whether the file exists.

ORA-19506 failed to create sequential file, name="string", parms="string"

Cause: Call to create the sequential file returned an error.

Action: Check additional messages, check access permissions.

ORA-19507 failed to retrieve sequential file, handle="string", parms="string"

Cause: Call to retrieve the sequential file returned an error.

Action: Check additional messages, and check if the file exists.

ORA-19508 failed to delete file "string"

Cause: Call to delete the file returned an error.

Action: Check additional messages.

ORA-19509 failed to delete sequential file, handle="string", parms="string"

Cause: Call to delete the sequential file returned an error.

Action: Check additional messages.

ORA-19510 failed to set size of string blocks for file "string" (blocksize=string)

Cause: Call to resize the file returned an error.

Action: Check additional messages.

ORA-19511 Error received from media manager layer, error text: string

Cause: An error occurred in the media management software which is linked with the Oracle server to perform backup and restore in cooperation with Recovery Manager.

Action: If the text of message 19511 does not provide enough information to resolve the problem, then you should contact the vendor of the media management software.

ORA-19550 cannot use backup/restore functions while using dispatcher

Cause: An attempt was made to use backup/restore functions while connected to the dispatcher in a shared server. This is not allowed because the device that is used for backup and restore must remain allocated to a single process.

Action: Connect directly to the instance then re-execute the backup or restore function.

ORA-19551 device is busy, device type: string, device name: string

Cause: The indicated device could not be allocated because it is allocated to another session, or no device was named, or all devices of the requested type are busy.

Action: Either attempt to allocate another device or wait until the required device is no longer busy.

ORA-19552 device type string is invalid

Cause: The device type indicated is invalid.

Action: Supply a correct device type and retry the allocation.

ORA-19553 device name string is invalid

Cause: The device name indicated is invalid.

Action: Supply a correct device name and retry the allocation.

ORA-19554 error allocating device, device type: string, device name: string

Cause: The specified device could not be allocated.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19555 invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value

Cause: The value of parameter LOG_ARCHIVE_MIN_SUCCEED_DEST was not set within the valid range.

Action: Specify a correct value for parameter LOG_ARCHIVE_MIN_SUCCEED_DEST. If the archive log parameters LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST are in use, set parameter LOG_ARCHIVE_MIN_SUCCEED_DEST to either 1 or 2.

ORA-19556 required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred

Cause: The destination for parameter LOG_ARCHIVE_DUPLEX_DEST was deferred when it was required to be enabled. The destination was deferred automatically when an ALTER SYSTEM command for parameter LOG_ARCHIVE_DEST defined a destination which duplicated an existing LOG_ARCHIVE_DUPLEX_DEST parameter destination.

Action: Change the destination value for the LOG_ARCHIVE_DUPLEX_DEST parameter.

ORA-19557 device error, device type: string, device name: string

Cause: An error occurred in the platform-specific device code.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19558 error de-allocating device

Cause: The specified device could not be de-allocated.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19559 error sending device command: string

Cause: An error occurred while sending the indicated command to the session device.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error and retry the allocation.

ORA-19560 string is not a valid device limit

Cause: An invalid type of device limit was specified in a call to X$DBMS_BACKUP_RESTORE.SETLIMIT.

Action: Use one of the documented limits: KBYTES, READRATE, or PARALLEL.

ORA-19561 string requires a DISK channel

Cause: The attempted command requires that a DISK device channel be allocated to the session, but a non-DISK device was found.

Action: Deallocate the current device and allocate a DISK channel, then retry the command.

ORA-19562 file string is empty

Cause: The indicated file, which is an archive log, control file, or datafile was found to be empty during a copy, backup, or scan] operation.

Action: Ensure that the correct files are being specified for the copy or backup operation.

ORA-19563 string header validation failed for file string

Cause: When opening the file to be placed in a copy or backup set, to be inspected, or used as the target for an incremental restore, the header was not recognized as a valid file header for a file of the indicated type (datafile, archived log, or control file), belonging to the current database.

Action: Ensure that the correct files are being specified for the copy or backup operation.

ORA-19564 error occurred writing string bytes at block number string

Cause: An error occurred while writing to a file.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error if possible, then retry the copy, backup, or restore operation.

ORA-19565 BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices

Cause: An attempt was made to specify duplexing to sequential devices, but the BACKUP_TAPE_IO_SLAVES initialization parameter was not enabled.

Action: Specify BACKUP_TAPE_IO_SLAVES=TRUE in the INIT.ORA file, or do not specify duplexing to sequential devices.

ORA-19566 exceeded limit of string corrupt blocks for file string

Cause: The user specified limit of allowable corrupt blocks was exceeded while reading the specified datafile for a datafile copy or backup.

Action: No action required. The copy or backup operation fails. The session trace file contains detailed information about which blocks were corrupt.

ORA-19567 cannot shrink file string because it is being backed up or copied

Cause: An ALTER statement attempted to reduce the size of the indicated file while the same file is being backed up or copied.

Action: Retry the resize after the backup or copy is complete.

ORA-19568 a device is already allocated to this session

Cause: A device cannot be allocated to a session if another device is already allocated.

Action: Deallocate the current device.

ORA-19569 no device is allocated to this session

Cause: An operation was attempted which requires a device to be allocated to the current session, and there is no device allocated.

Action: Allocate a device then retry the operation.

ORA-19570 file number string is outside valid range of 1 through string

Cause: A file number used in a copy, backup, or restore operation is not valid for the current database.

Action: Specify a valid file number.

ORA-19571 string recid string stamp string not found in controlfile

Cause: The input file specified for a copy or backup operation could not be opened because the record describing the file is not found in the control file.

Action: Specify a correct RECID/stamp and retry the copy or backup.

ORA-19572 cannot process file string, file is being being resized

Cause: The input file specified for a copy or backup operation could not be opened because the file is being resized.

Action: Wait for the resize to complete then retry the copy or backup.

ORA-19573 cannot obtain string enqueue for datafile string

Cause: The file access enqueue could not be obtained for a file specified in a backup, copy or restore operation. If the enqueue type shown is SHARED, then the file is the input file for a backup or copy. If the type is EXCLUSIVE, then the file is the output file for a datafile copy or restore which is attempting to overwrite the currently active version of that file. In this case, the file must be offline or the database must be closed. If the type is read-only, then you are attempting to back up or copy this file while the database is in NOARCHIVELOG mode.

Action: Wait until the conflicting operation is complete, then retry the copy or backup. If the database is in NOARCHIVELOG mode, then all files being backed up must be closed cleanly.

ORA-19574 output filename must be specified

Cause: This type of copy or restore requires an output file name.

Action: Specify an output file name and retry the copy.

ORA-19575 expected string blocks in file string, found string

Cause: During a backup, restore, copy, or scan operation, the indicated file did not contain as many blocks as were indicated in the file header.

Action: The input copy or backup piece is probably corrupt. If another backup or copy exists of the file that is being restored, then the corrupt file can be deleted from the recovery catalog and the operation can be restarted.

ORA-19576 datafile string not defined in control file

Cause: The specified file number was not found in the control file.

Action: Specify a correct file number and retry the operation.

ORA-19577 file string is MISSING

Cause: A copyDataFileCopy, restoreDataFileTo or proxyRestoreDataFile function specified a file number but no output file name, indicating that the output file name should be taken from the control file. However, the control file entry for this file indicates that it was created for a file that was present in the data dictionary but not named during the last CREATE CONTROLFILE statement, so the name in the control file cannot be used for restoration.

Action: Either specify an output file name or issue a SQL RENAME command to enter a valid name for this file in the control file.

ORA-19578 end of volume while duplexing to sequential files, backup piece incomplete

Cause: An end of volume (EOV) condition was detected while duplexing to sequential files, and this condition cannot be handled currently.

Action: Before retrying the backup, make sure the backup pieces will fit in the volume, or disable duplexing.

ORA-19579 archivelog record for string not found

Cause: No archived log record corresponding to the input file could be found in the control file.

Action: Specify a valid archive log file name and retry the operation.

ORA-19580 string conversation not active

Cause: A backup or restore operation was attempted before a conversation was started.

Action: Start a conversation then retry the operation.

ORA-19581 no files have been named

Cause: An attempt was made to proceed from the file naming phase to the piece processing phase of a backup or restore conversation before any files have been specified for backup or restore.

Action: Specify some files then retry the operation.

ORA-19582 archivelog file header validation for string failed

Cause: The archived log file header is corrupt and could not be validated.

Action: Provide a valid archive log file and retry the operation.

ORA-19583 conversation terminated due to error

Cause: An error occurred which forced the termination of the current backup or restore conversation.

Action: There should be other error messages to help identify the cause of the problem. Correct the error and begin another conversation.

ORA-19584 file string already in use

Cause: The indicated file, which was specified as the target for a copy, restore, or delete operation is already in use by the database.

Action: Specify a different name and retry the operation.

ORA-19585 premature end of volume on piece string

Cause: While creating the indicated backup piece, an end-of-volume condition was encountered before all of the backup set control data was written to the backup piece. This is most likely a media error, because the amount of backup set control data is very small in relation to the total amount of data in a backup set.

Action: Retry the piece with a larger piece of output media.

ORA-19586 string k-byte limit is too small to hold piece directory

Cause: The user-specified limit of k-bytes per backup piece is not enough to hold the backup set control data.

Action: Use the setLimit procedure to increase the k-byte limit and retry the operation.

ORA-19587 error occurred reading string bytes at block number string

Cause: An error occurred while reading from a file.

Action: One or more other messages should be displayed to help pinpoint the cause of the error. Correct the error then retry the copy, backup, or restore operation.

ORA-19588 string recid string stamp string is no longer valid

Cause: The indicated record has been marked as deleted. This indicates that the corresponding file has either been overwritten by another copy or restore, or that the copy was 'consumed' by a switchToCopy operation.

Action: If you know the name of the file you wish to copy, then inspect it and then retry the copy specifying the new RECID.

ORA-19589 string is not a snapshot or backup controlfile

Cause: The control file that is the source for a backup or copy operation is not a snapshot or backup control file.

Action: Specify the name of a snapshot or backup control file.

ORA-19590 conversation already active

Cause: An attempt was made to begin a backup or restore conversation, but another conversation is already active in this session.

Action: Either continue the current conversation, or call backupCancel or restoreCancel to end the current conversation before starting a new one.

ORA-19592 wrong string conversation type

Cause: An attempt was made to specify a type of file to be backed-up or restored, but the current conversation cannot process this type of file. For example, you specified an archived log to be included in a datafile backup set. The specified file will not be included in the backup or restore operation.

Action: No action required. The conversation is still active, and more files can be specified.

ORA-19593 datafile number string already included as string

Cause: This datafile is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of a datafile.

Action: No action required. The conversation is still active, and more files can be specified.

ORA-19594 controlfile already included as string

Cause: The control file is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the control file.

Action: No action required. The conversation is still active, and more files can be specified.

ORA-19595 archivelog string already included in backup conversation

Cause: The indicated archive log has already been specified for inclusion in this backup conversation.

Action: No action required. The conversation is still active, and more files can be specified.

ORA-19596 SPFILE already included

Cause: The SPFILE is already specified for inclusion in this backup or restore conversation. A backup or restore conversation may process only a single instance of the SPFILE.

Action: No action required. The conversation is still active, and more files can be specified.

ORA-19597 file string blocksize string does not match set blocksize of string

Cause: A file was specified for inclusion in a backup set but it has a logical block size different from the rest of the files in the backup set. All files in a backup set must have the same logical block size.

Action: Specify a file that has the same block size as the rest of the files in the backup set. The conversation is still active and more files can be specified.

ORA-19598 can not backup SPFILE because the instance was not started with SPFILE

Cause: A backup command requested a backup of the SPFILE, but no SPFILE was used to start up the instance.

Action: Create an SPFILE and restart the instance using the SPFILE.

ORA-19599 block number string is corrupt in string string

Cause: A corrupt block was found in a controlfile, archivelog, or backup piece that is being read for a backup or copy. Corruption is not tolerated in controlfiles, archivelogs, or backup pieces.

Action: No action required. The copy or backup operation fails. Note that in the case of a backup set, the conversation is still active and the piece may be retried.

ORA-19600 input file is string string (string)

Cause: This message identifies the input file for a failed copy operation. Both the file number and name (if the name has been determined) are shown.

For a datafile, the file number refers to the datafile's absolute file number as shown in the DBA_DATA_FILES view.
For a datafile-copy, the file number refers to the copy's control file record number as shown in the V$DATAFILE_COPY view.
For a datafile-copy, the file number refers to the copy's control file record number as shown in the RECID column of the V$DATAFILE_COPY view.
For an archived log, the file number refers to the log's control file record number as shown in the RECID column of the V$ARCHIVED_LOG view.

Action: Other messages should display to help pinpoint the cause and the solution.

ORA-19601 output file is string string (string)

Cause: This message identifies the output file for a failed copy operation. The fields are as described in message 19600. When creating a new datafile copy, its control file record number may not have been determined when the message is printed. In that case, the record number shown is zero.

Action: See other error message.

ORA-19602 cannot backup or copy active file in NOARCHIVELOG mode

Cause: An attempt was made to copy or backup a file that was not closed cleanly, and the database was in NOARCHIVELOG mode. This is not allowed because when restored, the file will require redo application before it is usable, and redo is not currently being saved beyond the contents of the online redo logs.

Action: Take the tablespace offline clean or close the database and retry the copy or backup.

ORA-19603 cannot backup or copy active file with KEEP .. UNRECOVERABLE option

Cause: The user tried to copy or backup a file that was not closed cleanly, with the KEEP .. UNRECOVERABLE option. This is not allowed because when restored, the file will require redo application before it is usable, and redo will not be saved because of the KEEP .. UNRECOVERABLE option.

Action: Take the tablespace offline cleanly, or close the database and retry the copy or backup.

ORA-19604 conversation file naming phase is over

Cause: A call was made to specify a file to be backed up or restored after the first backup piece has been processed.

Action: You cannot specify more files to be processed during a backup or restore conversation after the first backup piece has been processed. If more files must be specified, you must begin a new conversation.

ORA-19605 input filename must be specified

Cause: The input file name was not specified for a control file copy operation.

Action: Specify an input file name and retry the operation.

ORA-19606 Cannot copy or restore to snapshot controlfile

Cause: A control file copy or restore operation specified the name of the snapshot control file as the output file. It is not permitted to overwrite the snapshot control file in this manner. Other methods are available to create the snapshot control file.

Action: Specify a different file name and retry the operation. If this is a restore, then the restore conversation remains active and more files may be specified.

ORA-19607 string is an active controlfile

Cause: A control file copy, restore, or backup specified the name of a control file named in the INIT.ORA file as the input or output file.

Action: Specify a different file name and retry the operation. If this is a backup or restore conversation, then the conversation remains active and more files may be specified.

ORA-19608 string is not a backup piece

Cause: The specified file is not a backup piece produced by the DBMS_BACKUP_RESTORE package. Either the first block of the backup piece is corrupt or this file is not a backup piece.

Action: Specify a different file name and retry the operation.

ORA-19609 string is from different backup set: stamp string count string

Cause: The specified file is not from the backup set which is currently being processed. It is part of a different backup set. The identification of the set containing this piece is shown.

Action: Specify the correct backup piece and retry the operation.

ORA-19610 directory block string is corrupt

Cause: The indicated directory block failed checksum validation. This backup piece is unusable.

Action: Supply another copy of the same backup piece, or terminate the restore conversation.

ORA-19611 backup piece out of order. Expected string but found string

Cause: This backup piece is out of sequence.

Action: Supply the correct backup piece.

ORA-19612 datafile string not restored due to string

Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.

Action: The restore conversation remains active, and the current piece must be reprocessed. If the failure cannot be resolved by reprocessing the current piece, then the restore conversation must be cancelled.

ORA-19613 datafile string not found in backup set

Cause: The indicated file could not be restored, because it is not in this backup set. If the file number is zero, then this refers to the control file.

Action: This message is issued when the directory from the first backup piece is read and one or more files named for restoration were not found. The restore conversation is still active, but no data has been read and you must supply the first backup piece of a backup set that contains all of the requested files.

ORA-19614 archivelog thread string sequence string not found in backup set

Cause: The indicated archived log file was named explicitly for restoration but is not contained in this backup set.

ORA-19615 some files not found in backup set

Cause: Some files that were specified for restoration were not found in the backup set directory. Message 19613 or 19614 is issued for each file that was not found.

Action: See the instructions for message 19613.

ORA-19616 output filename must be specified if database not mounted

Cause: A datafile restore specified no target file name, but the database is not mounted. The database must be mounted when no target file name is specified, so that the target file name can be obtained from the control file.

Action: The restore conversation remains active. If you wish to restore datafiles without their target file names, then mount the database before continuing. Otherwise, a target file name must be specified on all datafile restoration calls.

ORA-19617 file string contains different resetlogs data

Cause: The indicated file contains resetlogs data which is different from the archived log files which are already included in the backup set. All archived log files in a backup set must have the same resetlogs data.

Action: The restore conversation remains active, and you may continue to specify archived log files for inclusion in the backup set.

ORA-19618 cannot name files after restoreValidate has been called

Cause: A call was made to specify a file to restore from a backup set, but a previous call to restoreValidate has already been made.

Action: You must cancel and restart the conversation if you wish to specify files to restore.

ORA-19619 cannot call restoreValidate after files have been named

Cause: restoreValidate was called after some files had already been specified for restoration.

Action: You must cancel and restart the conversation if you wish to call restoreValidate.

ORA-19621 archivelog range has already been specified

Cause: A range of logs has already been specified. Only one SCN range may be specified per conversation.

Action: The restore conversation remains active and more logs may be specified by thread and sequence number, if desired.

ORA-19622 archivelog thread string sequence string not restored due to string

Cause: The indicated file could not be restored, because all of its data blocks were not found in the backup piece.

ORA-19623 file string is open

Cause: A SwitchToCopy operation specified a datafile copy whose parent datafile is open.

Action: Take the owning tablespace offline or close the database, then retry the operation.

ORA-19624 operation failed, retry possible

Cause: A backup, restore or image copy operation failed with an I/O error. If the source of the I/O error can be corrected, then the operation may be retried.

Action: This message is used by Recovery Manager to decide whether or not to retry the operation.

ORA-19625 error identifying file string

Cause: A file specified as input to a copy or backup operation, or as the target for an incremental restore, could not be identified as an Oracle file. An operating system-specific error accompanies this error to help pinpoint the problem.

Action: Specify an different file and retry the operation.

ORA-19626 backup set type is string - can not be processed by this conversation

Cause: The data in the backup set is not compatible with the current conversation.

Action: Either supply the first piece from a backup set that matches the current conversation or start a new restore conversation which can process this backup set.

ORA-19627 cannot read backup pieces during controlfile application

Cause: This is a control file restore conversation, which is using the offline range information from one or more control files to update datafile checkpoint data. Backup sets are not used during this type of conversation.

Action: The conversation is still active and more control files may be applied.

ORA-19628 invalid SCN range

Cause: The starting SCN for restoreRedoLogRange is greater than the ending SCN.

Action: Specify a starting SCN which is less than or equal to the ending SCN.

ORA-19629 no files in specified archivelog SCN range

Cause: This backup set contains no files in the specified range.

Action: Either supply a backup set that contains files in the correct range or start a new conversation and specify a range which will select some files from this backup set.

ORA-19630 end of volume encountered while copying backup piece

Cause: While copying a backup piece from the operating system native file system to an output device, the output device encountered end-of-volume.

Action: The copy fails. This could happen if a tape was used which is not large enough to hold the entire backup piece.

ORA-19631 archivelog record contains no file name

Cause: This archive log record represents a switch into an active log that took place without archiving its prior contents. The prior contents of the log file are lost.

Action: Specify the RECID of an archive log record that contains a file name. Fixed view V$ARCHIVED_LOG can be used to examine the archived logs.

ORA-19632 file name not found in controlfile

Cause: The name passed to getFno was not found in the control file.

Action: Supply a valid file name.

ORA-19633 controlfile record string is out of sync with recovery catalog

Cause: The control file record describing the file to be deleted in a call to deleteBackupPiece, deleteDataFilecopy, proxyDelete or deleteArchivedLog does not match the validation data supplied by Recovery Manager.

Action: Contact Oracle Support Services.

ORA-19634 filename required for this function

Cause: The FNAME or handle parameter was not specified for deletePiece, deleteDataFileCopy, deleteRedoLog or proxyDelete.

Action: Specify the FNAME or handle parameter when calling these functions.

ORA-19635 input and output filenames are identical

Cause: Identical input and output file names were specified for a datafile copy operation.

Action: Specify an output file name which is different from the input file name.

ORA-19636 archivelog thread string sequence string already included

Cause: The indicated archive log has already been specified for inclusion in this restore conversation. A restore conversation may process only one copy of any archive log.

Action: No action required. The conversation is still active, and more files can be specified.

ORA-19637 backupPieceCreate requires file name when using DISK device

Cause: The session device is currently allocated to disk, and so a file name is required.

Action: Supply a file name and retry the operation.

ORA-19638 file string is not current enough to apply this incremental backup

Cause: The checkpoint of the target for this incremental backup is less than the start of the incremental backup. If this backup were applied, then any changes made between the datafile checkpoint and the start of the incremental backup could be lost.

Action: Supply a backup set that can be applied and retry the operation.

ORA-19639 file string is more current than this incremental backup

Cause: The checkpoint of the target for this incremental backup is greater than or equal to the checkpoint of the file in the incremental backup set. This backup cannot advance the checkpoint of the target file, so there is no point in applying it.

Action: Supply a backup set that can be applied and retry the operation.

ORA-19640 datafile checkpoint is SCN string time string

Cause: This message identifies the datafile checkpoint for a datafile that was too old to take an incremental backup from, or the target of an incremental restore that could not be applied.

Action: See other error message.

ORA-19641 backup datafile checkpoint is SCN string time string

Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied.

Action: See other error message.

ORA-19642 incremental-start SCN is string

Cause: This message identifies the starting SCN of an incremental backup that could not be applied.

Action: See other error message.

ORA-19643 datafile string: incremental-start SCN is too recent

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is greater than the datafile checkpoint SCN, which could cause some blocks to be missed.

Action: Specify a smaller incremental-start SCN.

ORA-19644 datafile string: incremental-start SCN is prior to resetlogs SCN string

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the resetlogs SCN.

Action: Specify a larger incremental-start SCN.

ORA-19645 datafile string: incremental-start SCN is prior to creation SCN string

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is less than the datafile's creation SCN.

Action: Specify a larger incremental-start SCN.

ORA-19646 cannot change size of datafile string from string to string

Cause: The indicated file was resized before this incremental backup was taken, but the incremental backup failed to set the file to the new size.

Action: Examine the other messages which should be present to indicate the cause of the failure.

ORA-19647 non-zero LEVEL cannot be specified when INCREMENTAL is FALSE

Cause: BackupSetDataFile was called with a non-zero BACKUP_LEVEL and a FALSE incremental indication.

Action: Either set incremental to TRUE or change BACKUP_LEVEL to zero.

ORA-19648 datafile string: incremental-start SCN equals checkpoint SCN

Cause: The incremental-start SCN which was specified when starting an incremental datafile backup is equal to the datafile's checkpoint SCN. Since an incremental backup can only be applied to a datafile whose checkpoint SCN is between the backup set incremental-start SCN (inclusive) and the backup set checkpoint SCN (exclusive), there is no datafile that this backup set could ever be applied to.

Action: Specify a smaller incremental-start SCN.

ORA-19649 offline-range record recid string stamp string not found in file string

Cause: applyOfflineRange was called with a RECID/stamp which was not found in the indicated control file. This probably means that the specified control file is no longer the same control file that Recovery Manager thinks it is.

Action: Specify the RECID/stamp of a record that exists in the control file copy.

ORA-19650 Offline-range record recid string stamp string in file string has SCN string

Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.

Action: See other error message.

ORA-19651 cannot apply offline-range record to datafile string: SCN mismatch

Cause: applyOfflineRange cannot apply an offline-range record to a target datafile unless the datafile's checkpoint SCN exactly matches the offline-clean SCN in the specified offline-range record.

Action: Specify an offline-range record whose offline-clean SCN matches the target datafile's checkpoint.

ORA-19652 cannot apply offline-range record to datafile string: file is fuzzy

Cause: The target datafile for an applyOfflineRange call is fuzzy.

Action: Specify a target datafile that is closed cleanly.

ORA-19653 cannot switch to older file incarnation

Cause: SwitchToCopy was called with a datafile copy for a datafile that was dropped prior to the time this control file was backed up.

Action: Restore and mount an earlier control file. It is acceptable to use a control file that was backed up prior to the creation of the specified datafile.

ORA-19654 must use backup controlfile to switch file incarnations

Cause: This switchToCopy operation is attempting to switch incarnations of a datafile, but the currently mounted control file is not a backup control file.

Action: Restore and mount a backup control file.

ORA-19655 cannot switch to incarnation with different resetlogs data

Cause: This switchToCopy operation is attempting to switch to a datafile which comes from a different resetlogs version of the database.

Action: Either restore a backup control file that was taken from the same database version as the target datafile-copy, or switch to a different datafile-copy.

ORA-19656 cannot backup, copy, or delete online log string

Cause: The indicated log file is an active log. You can only backup, copy, or delete archived logs.

Action: The indicated log file cannot be processed. Select another file.

ORA-19657 cannot inspect current datafile string

Cause: The file being inspected is already part of the currently mounted database.

Action: No action required. The file is already part of the database.

ORA-19658 cannot inspect string - file is from different resetlogs

Cause: The resetlogs data in the log file being inspected does not match that in the currently mounted control file.

Action: The indicated file cannot be processed; inspect another file.

ORA-19659 incremental restore would advance file string past resetlogs

Cause: This incremental backup cannot be applied to the specified datafile, because the datafile is from an earlier incarnation of the database, and its checkpoint would be advanced too far to be recoverable in the current incarnation of the database.

Action: This incremental cannot be applied to this datafile. If you wish to recover the file to the resetlogs SCN so that the database can be opened with the RESETLOGS option, then you must use redo-log recovery, not incremental restore, to continue recovering this file.

ORA-19660 some files in the backup set could not be verified

Cause: A restore conversation was made to verify all the files in a backup set, and the files which were printed in messages 19661 or 19662 could not be verified because corrupt blocks for those files were found in the backup set.

Action: Unless the damage to the backup set can be repaired, the indicated files cannot be restored from this backup set.

ORA-19661 datafile string could not be verified

Cause: Some data blocks for the indicated datafile were corrupt in the backup set.

Action: Unless the damage to the backup set can be repaired, the indicated datafile cannot be restored from this backup set.

ORA-19662 archived log thread string sequence string could not be verified

Cause: Some data blocks for the indicated archived log were corrupt in the backup set.

Action: Unless the damage to the backup set can be repaired, the indicated archived log cannot be restored from this backup set.

ORA-19663 cannot apply current offline range to datafile string

Cause: An attempt was made to apply the current offline range to the specified datafile, but the datafile is either not current enough or is not at the correct SCN to apply the offline range.

Action: The datafile remains unchanged.

ORA-19664 file type: string, file name: string

Cause: This message is issued to identify the file which is the subject of an error.

Action: No action required. This is an informational message. There should be other Oracle messages explaining the cause of the error.

ORA-19665 size string in file header does not match actual file size of string

Cause: The size of the file as indicated in the file header does not match the true size of the file. The two differing sizes are shown in units of logical blocks.

Action: This file is not usable; it has most likely been truncated.

ORA-19666 cannot do incremental restore of the controlfile

Cause: The control file was included in an incremental restore conversation

Action: If you wish to restore the control file, you must do a full restore of the control file.

ORA-19667 cannot do incremental restore of datafile string

Cause: The backup of the datafile is a full backup.

Action: If you wish to restore the datafile, you must do a full restore of the datafile.

ORA-19668 cannot do full restore of datafile string

Cause: The backup of the datafile is an incremental backup.

Action: If you wish to restore the datafile, you must do an incremental restore of the datafile.

ORA-19669 proxy copy functions cannot be run on DISK channel

Cause: A proxy copy procedure was called, but the device which is allocated to the current session has type DISK.

Action: Allocate a non-DISK channel and retry the operation. Note that proxy copy requires a third-party media management software product that supports the this backup/restore feature.

ORA-19670 file string already being restored

Cause: A proxy restore function has already named this file as a restore destination.

Action: Use a different file name. If this message occurs during a Recovery Manager job, then this is an internal error in Recovery Manager, and you should contact Oracle Support Services.

ORA-19671 media management software returned invalid proxy handle

Cause: During a proxy backup or restore, the media management software returned an invalid file handle. This is an internal error in the media management software which is linked with Oracle to provide backup/restore services.

Action: Contact the media management software vendor.

ORA-19672 media management software returned invalid file status

Cause: During a proxy backup or restore, the media management software returned an invalid file status. This is an internal error in the media management software which is linked with Oracle to provide backup/restore services.

Action: Contact the media management software vendor.

ORA-19673 error during proxy copy of file string

Cause: During a proxy backup or restore, an error occurred while copying this file, but other files may have been copied successfully.

Action: There should be other errors on the error stack which explain why the file could not be successfully copied.

ORA-19674 file string is already being backed up with proxy copy

Cause: Recovery Manager attempted to back up the specified file with proxy copy, but the file is already being backed up by another Recovery Manager job.

Action: Wait until the other Recovery Manager backup of this file is complete, then retry the backup.

ORA-19675 file string was modified during proxy copy

Cause: A proxy backup of the specified file failed because the file was brought online or otherwise modified while the proxy backup was in progress. This file was offline or read only when the backup began, so the file was not put into hot-backup mode, therefore no modifications are permitted while the backup is in progress.

Action: Take another backup of this file.

ORA-19676 one or more files failed during proxy backup or restore

Cause: During a proxy backup or restore, errors were encountered while processing some files. The files for which no error messages are shown were processed successfully.

Action: Examine the messages regarding the specific files to determine the cause of the problems.

ORA-19677 RMAN configuration name exceeds maximum length of string

Cause: The configuration name string exceeds the maximum length.

Action: Supply a correct configuration name and retry the function.

ORA-19678 RMAN configuration value exceeds maximum length of string

Cause: The configuration value string exceeds the maximum length.

Action: Supply a correct configuration value and retry the operation.

ORA-19679 RMAN configuration number string is outside valid range of 1 through string

Cause: An invalid RMAN Configuration number was specified.

Action: Specify a correct datafile number and retry the operation.

ORA-19680 some blocks not recovered. See trace file for details

Cause: Some blocks were not recovered during block media recovery.

Action: See trace files for details of the problem.

ORA-19681 block media recovery on control file not possible

Cause: File number 0 was specified in block media recovery.

Action: Check file number.

ORA-19683 real and backup blocksize of file string are unequal

Cause: The block size changed between the backup & the real file.

Action: Use the correct backup.

ORA-19684 block media recovery failed because database is suspended

Cause: Database is suspended, probably by an ALTER SYSTEM SUSPEND statement.

Action: Execute ALTER SYSTEM RESUME then retry block media recovery.

ORA-19690 backup piece release string incompatible with Oracle release string

Cause: The backup piece was created by incompatible software.

Action: Either restart with a compatible software release or create another backup using the current release.

ORA-19700 device type exceeds maximum length of string

Cause: The device type indicated is invalid.

Action: Supply a correct device type and retry the allocation.

ORA-19701 device name exceeds maximum length of string

Cause: The device name indicated is invalid.

Action: Supply a correct device name and retry the allocation.

ORA-19702 device parameter exceeds maximum length of string

Cause: The device parameter exceeds the port-specific maximum length.

Action: Correct the parameter and retry the operation.

ORA-19703 device command string exceeds maximum length of string

Cause: The device command string exceeds maximum length.

Action: Correct the command and retry the operation.

ORA-19704 file name exceeds maximum length of string

Cause: The specified file name, which was a parameter to a copy, backup, or restore operation, exceeds the maximum file name length for this operating system.

Action: Retry the operation with a shorter file name.

ORA-19705 tag value exceeds maximum length of string characters

Cause: During a backup or copy operation, the user supplied a tag value too long to fit in the file header.

Action: Supply a shorter tag and retry the operation.

ORA-19706 invalid SCN

Cause: The input SCN is either not a positive integer or too large.

Action: Check the input SCN and make sure it is a valid SCN.

ORA-19707 invalid record block number - string

Cause: The input number is either negative or too large.

Action: Check the input record block number and make sure it is a valid number clauses in the CREATE DATABASE statement.

ORA-19708 log destination exceeds maximum length of string characters

Cause: When starting a restore conversation, the user specified a log restore destination longer than the port-specific maximum.

Action: Supply a shorter destination and retry the operation.

ORA-19709 numeric parameter must be non-negative integer

Cause: A numeric parameter to an X$DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.

Action: Supply a valid numeric parameter.

ORA-19710 unsupported character set string

Cause: When the target database is not mounted, RMAN sets the target database character set to the value specified in the users environment.

Action: Specify a valid character set in the environment. This is usually done via the NLS_LANG environment variable.

ORA-19711 cannot use reNormalizeAllFileNames while database is open

Cause: An attempt was made to re-normalize all the file names in the control file while the database is open.

Action: Close the database before using the reNormalizeAllFileNames procedure.

ORA-19712 table name exceeds maximum length of string

Cause: The table name string exceeds the maximum length.

Action: Retry the operation with a shorter table name.

ORA-19713 invalid copy number: string

Cause: The copy number is not in a valid range or you have reached the maximum limit.

Action: Report the error and other information to support.

ORA-19714 length for generated piece name longer than string

Cause: The specified format exceeds the maximum length for the piece name.

Action: Change the format to create shorter piece names.

ORA-19715 invalid format for piece name

Cause: A restricted format was used incorrectly.

Action: Change the format by removing the restricted format.

ORA-19720 Error occurred when converting an OCI number into an SCN

Cause: This is most likely caused by an invalid SCN number that came from an external file, such as an export file.

Action: See other errors on the error stack to look for the source of the problem.

ORA-19721 Cannot find datafile with absolute file number string in tablespace string

Cause: Cannot find one of the data files that should be in the pluggable set.

Action: Make sure all datafiles are specified via import command line option or parameter files.

ORA-19722 datafile string is an incorrect version

Cause: The datafile is an incorrect version. It contains either less or more changes then the desired version.

Action: Make sure the right datafiles are transported. Make sure the datafile is copied while its tablespace is read only.

ORA-19723 Cannot recreate plugged in read-only datafile string

Cause: The datafile is plugged in read only. It cannot re-created.

Action: Use ALTER DATABASE RENAME FILE command instead.

ORA-19724 snapshot too old: snapshot time is before file string plug-in time

Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.

Action: retry the query.

ORA-19725 can not acquire plug-in enqueue

Cause: There maybe another ALTER DATABASE RESET COMPATIBILITY command issued concurrently, preventing this process from acquiring the plug-in enqueue.

Action: Retry the operation.

ORA-19726 cannot plug data [string] at level string into database running at compatibility level string

Cause: Some of the data in the pluggable set requires a compatibility level higher than what is currently allowed by the database. The string in square bracket is the name of the compatibility type associated with the data.

Action: Raise the value of the COMPATIBLE initialization parameter and retry the operation.

ORA-19727 cannot plug data [string] at level string into database running Oracle string

Cause: Some of the data in the pluggable set requires a compatibility level higher than the release level of the Oracle executable. The string in square bracket is the name of the compatibility type associated with the data.

Action: Upgrade Oracle and retry the operation.

ORA-19728 data object number conflict between table string and partition string in table string

Cause: The non-partitioned table has the same data object number as one of the partitions in the partitioned table. One cannot exchange the table with the partition in this case.

Action: Use the ALTER TABLE MOVE PARTITION command to move the offending partition, so that the partition will get a new data object number. Retry the operation then.

ORA-19729 File string is not the initial version of the plugged in datafile

Cause: The file is not the initial version of the plugged in datafile.

Action: Use the correct initial version of the plugged in datafile.

ORA-19730 can not convert offline plugged-in datafile string

Cause: As part of making a tablespace read-write, we need to convert datafiles that are plugged in read only. The file must be online.

Action: Bring the datafile online and retry the operation.

ORA-19731 cannot apply change to unverified plugged-in datafile string

Cause: Recovery was not able to verify the referred datafile according to information in the control file. Before encountering this change vector for this file, somehow recovery did not encounter the file conversion redo that is supposed to verify the file. This may happen due to corrupted or incorrect control file used for media recovery.

Action: Use the correct control file and continue recovery.

ORA-19732 incorrect number of datafiles for tablespace string

Cause: The number of datafiles in the export file for the referred tablespace is not the same as expected. This is most likely caused by a user editing the export file.

Action: Use the correct export file and retry the operation.

ORA-19733 COMPATIBLE parameter needs to be string or greater

Cause: The COMPATIBLE initialization parameter is not high enough to allow the operation. Allowing the command would make the database incompatible with the release specified by the current COMPATIBLE parameter.

Action: Shutdown and restart with a higher compatibility setting.

ORA-19734 wrong creation SCN - control file expects converted plugged-in datafile

Cause: When a tablespace is plugged into a database, the tablespace is initially read only. Oracle converts the header of the plugged-in datafiles (assign them a new creation SCN) when the tablespace is first made read-write. This error occurs when the creation SCN in the file header is different from the creation SCN in the control file, possibly because this is the initial version of plugged-in datafile.

Action: Either restore the converted datafile or continue recovering the datafile.

ORA-19735 wrong creation SCN - control file expects initial plugged-in datafile

Action: Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file.

ORA-19736 can not plug a tablespace into a database using a different national character set

Cause: Oracle does not support plugging a tablespace into a database using a different national character set.

Action: Use import/export or unload/load to move data instead.

ORA-19999 skip_row procedure was called

Cause: The SKIP_ROW procedure was called which raises this error.

Action: SKIP_ROW should only be called within a trigger or a procedure called by a trigger.

ORA-20000 string

Cause: The stored procedure RAISE_APPLICATION_ERROR was called which causes this error to be generated.

Action: Correct the problem as described in the error message or contact the application administrator or database administrator for more information.

ORA-21000 error number argument to raise_application_error of stringstring is out of range

Cause: An attempt was made to specify a number not in the allowed range.

Action: Use an error number in the range of -20000 to -20999, inclusive.

ORA-21001 error number argument to raise_system_error of stringstring is out of range

Cause: An attempt was made to specify a number not in the allowed range.

Action: Use an error number in the range of -23300 to -24299, or -29300 to -29399, inclusive.

ORA-21300 objects option not installed

Cause: The objects option is not installed at this site. object types and other object features are, therefore, unavailable.

Action: Install the objects option. The objects option is not part of the Oracle Server product and must be purchased separately. Contact Oracle Support Services if the objects option needs to be purchased.

ORA-21301 not initialized in object mode

Cause: This function requires the OCI process to be initialized in object mode.

Action: Specify OCI_OBJECT mode when calling OCIInitialize().

ORA-21500 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]

Cause: This is the generic error number for the OCI environment (client-side) internal errors. This indicates that the OCI environment has encountered an exceptional condition.

Action: Report to Oracle Support Services. The first argument is the internal error number.

ORA-21501 program could not allocate memory

Cause: The operating system has run out of memory.

Action: Take action to make more memory available to the program.

ORA-21503 program terminated by fatal error

Cause: A program is in an unrecoverable error state.

Action: Report to Oracle Support Services.

ORA-21520 database server driver not installed

Cause: User attempted to access a database server through an object-mode OCI environment but the necessary driver for supporting such access to the database server is not installed or linked in.

Action: Check if the driver corresponding to the database server has been installed/linked in and entered in the server driver table.

ORA-21521 exceeded maximum number of connections in OCI (object mode only)

Cause: User exceeded the maximum number of connections (255) that can be supported by an OCI environment in object mode.

Action: Close some of existing and unused connections before opening more connections.

ORA-21522 attempted to use an invalid connection in OCI (object mode only)

Cause: User attempted to use an invalid connection or a connection that has been terminated in an OCI environment (object mode), or user attempted to de-reference a REF obtained from a connection which has been terminated.

Action: Ensure that the connection exists and is still valid.

ORA-21523 functionality not supported by the server (object mode only)

Cause: User attempted to use a functionality that the server does not support.

Action: Upgrade the server.

ORA-21524 object type mismatch

Cause: The object type of the object is different from what is specified.

Action: Check the type of the object and correct it.

ORA-21525 attribute number or (collection element at index) string violated its constraints

Cause: Attribute value or collection element value violated its constraint.

Action: Change the value of the attribute or collection element such that it meets its constraints. The constraints are specified as part of the attribute or collection element's schema information.

ORA-21526 initialization failed

Cause: The initialization sequence failed. This can happen, for example, if an environment variable such as NLS_DATE_FORMAT is set to an invalid value.

Action: Check that all NLS environment variables are well-formed.

ORA-21560 argument string is null, invalid, or out of range

Cause: The argument is expecting a non-null, valid value but the argument value passed in is null, invalid, or out of range. Examples include when the LOB/FILE positional or size argument has a value outside the range 1 through (4GB - 1), or when an invalid open mode is used to open a file, and so on.

Action: Check your program and correct the caller of the routine to not pass a null, invalid or out-of-range argument value.

ORA-21561 OID generation failed

Cause: The handles passed in may not be valid.

Action: Check the validity of the env, svc handles.

ORA-21600 path expression too long

Cause: The path expression that is supplied by the user is too long. The path expression is used to specify the position of an attribute in an object. This error occurs when one of the intermediate elements in the path expression refers to an attribute of a built-in type. Thus, the OCI function cannot proceed on to process the rest of the elements in the path expression.

Action: Pass in the correct path expression to locate the attribute.

ORA-21601 attribute is not an object

Cause: The user attempts to perform an operation (that is valid only for an object) to an attribute of a built-in type. An example of such an illegal operation is to dynamically set a null structure to an attribute of a built-in type.

Action: Avoid performing such operation to an attribute of built-in type.

ORA-21602 operation does not support the specified typecode

Cause: The user attempts to perform an operation that does not support the specified type code.

Action: Use the range of valid type codes that are supported by this operation.

ORA-21603 property id [string] is invalid

Cause: The specified property ID is invalid.

Action: Specify a valid property ID. Valid property IDs are enumerated by OCIObjectPropId.

ORA-21604 property [string] is not a property of transient or value instances

Cause: An attempt was made to get a property which applies only to persistent objects.

Action: Check the lifetime and only get this property for persistent objects.

ORA-21605 property [string] is not a property of value instances

Cause: An attempt was made to get a property which applies only to persistent and transient objects.

Action: Check the lifetime and only get this property for persistent and transient objects.

ORA-21606 can not free this object

Cause: An attempt was made to free an object that is persistent and dirty and the OCI_OBJECTFREE_FORCE flag is not specified.

Action: Either flush the persistent object or set the flag to OCI_OBJECTFREE_FORCE

ORA-21607 memory cartridge service handle not initialized

Cause: Attempt to use the handle without initializing it.

Action: Initialize the memory cartridge service handle.

ORA-21608 duration is invalid for this function

Cause: Attempt to use a duration not valid for this function.

Action: Use a valid duration: a previously created user duration or OCI_DURATION_STATEMENT or OCI_DURATION_SESSION. For callout duration or external procedure duration, use OCIExtProcAllocCallMemory.

ORA-21609 memory being resized without being allocated first

Cause: Attempt to resize memory without allocating it first.

Action: Allocate the memory first before resizing it.

ORA-21610 size [string] is invalid

Cause: Attempt to resize memory with invalid size.

Action: Pass in a valid size (must be a positive integer).

ORA-21611 key length [string] is invalid

Cause: Attempt to use an invalid key length.

Action: Key length is invalid and valid range is 0 to 64.

ORA-21612 key is already being used

Cause: Attempt to use a key that is already used.

Action: Use a new key that is not yet being used.

ORA-21613 key does not exist

Cause: Attempt to use a non-existent key.

Action: Use a key that already exists.

ORA-21614 constraint violation for attribute number string

Cause: Constraints on the attribute were violated.

Action: Correct the value (of the attribute) so that it satisfies constraints.

ORA-21615 copy of an OTS (named or simple) instance failed

Cause: See following message.

Action: Check that no attribute value violates constraints.

ORA-21700 object does not exist or is marked for delete

Cause: User attempted to perform an inappropriate operation to an object that is non-existent or marked for delete. Operations such as pinning, deleting and updating cannot be applied to an object that is non-existent or marked for delete.

Action: Re-initialize the reference to reference an existent object or unmark the object.

ORA-21701 attempt to flush objects to different servers

Cause: User attempted to flush objects to different servers in one function call. These objects are obtained by calling a callback functions provided by the program.

Action: Avoid performing this operation.

ORA-21702 object is not instantiated or has been de-instantiated in cache

Cause: User attempted to perform an inappropriate operation to a transient object that is not instantiated in the object cache. Operations that cannot be applied to a not-instantiated transient object include deleting or pinning such an object.

Action: Check their code to see if they are performing such an operation without instantiating the object first, or performing such an operation after the allocation duration of the object has expired.

ORA-21703 cannot flush an object that is not modified

Cause: See the error message.

Action: The object should not be flushed.

ORA-21704 cannot terminate cache or connection without flushing first

Cause: See the error message.

Action: The transaction should be aborted or committed before terminating the cache or connection.

ORA-21705 service context is invalid

Cause: The service context that is supplied by the user is not valid.

Action: Establish the service context.

ORA-21706 duration does not exist or is invalid

Cause: The duration number that is supplied by the user is not valid.

Action: Establish the duration or use a correct predefined duration.

ORA-21707 pin duration is longer than allocation duration

Cause: The pin duration supplied by the user is longer than the allocation duration. This affects operations such as pinning and setting default parameters.

Action: Use a shorter pin duration or use the null duration.

ORA-21708 inappropriate operation on a transient object

Cause: An attempt was made to perform an inappropriate operation on a transient object. Operations that cannot be applied to a transient object include flushing and locking.

Action: Avoid performing such operations on a transient object.

ORA-21709 cannot refresh an object that has been modified

Cause: An attempt was made to refresh an object that has been marked for delete, update or insert (new).

Action: Unmark the object before refreshing it.

ORA-21710 argument is expecting a valid memory address of an object

Cause: The object memory address that is supplied by the user is invalid. The user may have passed in a bad memory address to a function that is expecting a valid memory address of an object.

Action: Pass in a valid memory address of an object to the function.

ORA-21779 duration not active

Cause: An attempt was made to use a duration that has been terminated.

Action: Avoid performing such operation.

ORA-22053 overflow error

Cause: This operation's result is above the range of Oracle number.

Action: Decrease the input value(s) so that the result is in the range of Oracle number.

ORA-22054 underflow error

Cause: This operation's result is below the range of Oracle number.

Action: Increase the input value(s) so that the result is in the range of Oracle number.

ORA-22055 unknown sign flag value [string]

Cause: Signed flag used is not OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED.

Action: Use either OCI_NUMBER_SIGNED or OCI_NUMBER_UNSIGNED as sign flag.

ORA-22056 value [string] is divided by zero

Cause: Given value is divided by zero.

Action: Modify divisor value to be non-zero.

ORA-22057 bad integer length [string]

Cause: The length of the integer (that is, number of bytes) to be converted to or from an Oracle number is invalid.

Action: Use integer length 1, 2, 4 or 8 bytes only.

ORA-22059 buffer size [string] is too small - [string] is needed

Cause: The buffer to hold the resulting text string is too small.

Action: Provide a buffer of the required size.

ORA-22060 argument [string] is an invalid or uninitialized number

Cause: An invalid or uninitialized number was passed in.

Action: Use a valid number. To initialize a number, call OCINumberSetZero().

ORA-22061 invalid format text [string]

Cause: The numeric format string for converting characters to or from an Oracle number is invalid.

Action: Use valid format string as documented in the Oracle Call Interface Programmer's Guide.

ORA-22062 invalid input string [string]

Cause: The text string for converting to numbers is invalid.

Action: Use a valid input string as documented in the Oracle Call Interface Programmer's Guide.

ORA-22063 reading negative value [string] as unsigned

Cause: An attempt was made to convert a negative number to an unsigned integer.

Action: Use the sign flag ORLTSB to convert a signed number.

ORA-22064 invalid NLS parameter string [string]

Cause: The NLS parameter string for converting characters to or from an Oracle number is invalid.

Action: Use valid format string as documented in the Oracle Call Interface Programmer's Guide.

ORA-22065 number to text translation for the given format causes overflow

Cause: Rounding done due to the given string format causes overflow.

Action: Change the string format such that overflow does not occur.

ORA-22130 buffer size [string] is less than the required size [string]

Cause: The size of the buffer into which the hexadecimal REF string is to be written is too small.

Action: Provide a buffer of the required size.

ORA-22131 hexadecimal string length is zero

Cause: The given hexadecimal string length must be greater than zero.

Action: Specify a length greater than zero.

ORA-22132 hexadecimal string does not correspond to a valid REF

Cause: The given hexadecimal string is invalid.

Action: Provide a valid hexadecimal string which was previously returned by a call to OCIRefToHex().

ORA-22140 given size [string] must be in the range of 0 to [string]

Cause: The given resize size is invalid.

Action: Ensure that the given size is in the required range.

ORA-22150 variable-length array has not been initialized

Cause: An un-initialized variable-length array is being operated upon.

Action: Initialize the variable-length array prior to calling this function.

ORA-22151 cannot resize non-zero variable-length array to zero elements

Cause: An attempt was made to resize a non-zero variable-length array to 0 elements.

Action: Specify a non-zero size.

ORA-22152 destination variable-length array is not initialized

Cause: The variable-length array on the right-hand-side of an assignment or the destination array of an append is not initialized.

Action: Initialize the destination variable-length array prior to calling this function.

ORA-22153 source variable-length array is not initialized

Cause: The variable-length array on the left-hand-side of an assignment or the source array of an append is not initialized.

Action: Initialize the destination variable-length array prior to calling this function.

ORA-22160 element at index [string] does not exist

Cause: Collection element at the given index does not exist.

Action: Specify the index of an element which exists.

ORA-22161 type code [string] is not valid

Cause: Given type code is not valid.

Action: Use one of the type codes enumerated in OCITypeCode.

ORA-22162 element at index [string] has been previously deleted

Cause: An attempt was made to delete a non-existent collection element.

Action: Check for the existence of the element prior to calling this function.

ORA-22163 left hand and right hand side collections are not of same type

Cause: Left hand and right side collections are not of same type.

Action: Ensure that the same collection type is passed for both left hand and right hand side of this function.

ORA-22164 delete element operation is not allowed for variable-length array

Cause: An attempt was made to delete an element of a variable-length array.

Action: Ensure that the collection is not a variable-length array prior to calling this function.

ORA-22165 given index [string] must be in the range of 0 to [string]

Cause: Given index is not in the required range.

Action: Ensure that the given index is in the required range.

ORA-22166 collection is empty

Cause: Given collection is empty.

Action: Test if collection is empty prior to invoking this function.

ORA-22167 given trim size [string] must be less than or equal to [string]

Cause: Given trim size is greater than the current collection size.

Action: Ensure that the given size is less than or equal to the collection size prior to calling this function.

ORA-22275 invalid LOB locator specified

Cause: There are several causes:

The LOB locator was never initialized
The locator is for a BFILE and the routine expects a BLOB/CLOB/NCLOB locator
The locator is for a BLOB/CLOB/NCLOB and the routine expects a BFILE locator
Trying to update the LOB in a trigger body -- LOBs in trigger bodies are read-only
The locator is for a BFILE/BLOB and the routine expects a CLOB/NCLOB locator
The locator is for a CLOB/NCLOB and the routine expects a BFILE/BLOB locator

Action: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2),(3), (5), and (6),pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value.

ORA-22276 invalid locator for LOB buffering

Cause: One of the following:

The locator was never enabled for buffering.
It is not an updated locator but is being used for a write/flush operation.

Action: For (1) enable the locator for buffering; (2) ensure that only an updated locator is used for a LOB update operation.

ORA-22277 cannot use two different locators to modify the same LOB

Cause: LOB buffering is enabled and an attempt was made to modify the LOB using two different LOB locators.

Action: When using LOB buffering, modify the LOB through one LOB locator only.

ORA-22278 must update the LOB only through the LOB buffers

Cause: LOB buffering is enabled for this LOB and there are buffers for this LOB in the buffer pool. Thus, updating the LOB through means other than the LOB buffers is not allowed.

Action: Update the LOB through the LOB buffers using the locator that has LOB buffering enabled. If this operation is required, buffers associated with this LOB should either be flushed as necessary or buffering should be disabled. Once this is done, reissue the command.

ORA-22279 cannot perform operation with LOB buffering enabled

Cause: The operation attempted is not allowed when LOB buffering is enabled.

Action: If the operation is required, LOB buffering should not be used. In this case, flush buffers associated with the input LOB locator as necessary, disable buffering on the input LOB locator and reissue the command.

ORA-22280 no more buffers available for operation

Cause: One of the following:

All buffers in the buffer pool have been used up by previous operations.
An attempt was made to flush a LOB without any previous buffered update operations.

Action: For (1), flush the LOB(s) through the locator that is being used to update the LOB. For (2), write to the LOB through a locator enabled for buffering before attempting to flush buffers.

ORA-22281 cannot perform operation with an updated locator

Cause: The input locator has buffering enabled and was used to update the LOB value through the LOB buffering subsystem. The modified buffer has not been flushed since the write that was performed by the input locator; thus, the input locator is considered an updated locator. Updated locators cannot be the source of a copy operation. Only one locator per LOB may be used to modify the LOB value through the LOB buffering subsystem.

Action: Depending on whether the modifications made through the input locator to the LOB buffering subsystem should be written to the server, either flush the buffer to write the modifications, or, disable buffering on the locator to discard the modifications. Then, reissue the command.

ORA-22282 non-contiguous append to a buffering enabled LOB not allowed

Cause: The buffered write operation has an input offset value more than one byte or character past the end of the LOB.

Action: Specify an input offset value which is exactly one character or byte greater than the length of the LOB that you are attempting to update through a buffered write operation.

ORA-22283 filename contains characters that refer to parent directory

Cause: Filename contains a path "../" which references a parent directory.

Action: Ensure that the filename does not contain characters which reference a parent directory.

ORA-22285 non-existent directory or file for string operation

Cause: An attempt was made to access a directory that does not exist, or attempted to access a file in a directory that does not exist.

Action: Ensure that a system object corresponding to the specified directory exists in the database dictionary, or make sure the name is correct.

ORA-22286 insufficient privileges on file or directory to perform string operation

Cause: The user does not have the necessary access privileges on the directory alias and/or the file for the operation.

Action: Ask the database/system administrator to grant the required privileges on the directory alias and/or the file.

ORA-22287 invalid or modified directory occurred during string operation

Cause: The directory alias used for the current operation is not valid if being accessed for the first time, or has been modified by the database administrator since the last access.

Action: If you are accessing this directory for the first time, provide a valid directory name. If you have been already successful in opening a file under this directory before this error occurred, then close the file and retry the operation with a valid directory alias as modified by your database administrator. Oracle recommends that directories should be modified only during quiescent periods.

ORA-22288 file or LOB operation string failed string

Cause: The operation attempted on the file or LOB failed.

Action: See the next error message in the error stack for more detailed information. Also, verify that the file or LOB exists and that the necessary privileges are set for the specified operation. If the error still persists, report the error to the database administrator.

ORA-22289 cannot perform string operation on an unopened file or LOB

Cause: The file or LOB is not open for the required operation to be performed.

Action: Precede the current operation with a successful open operation on the file or LOB.

ORA-22290 operation would exceed the maximum number of opened files or LOBs

Cause: The number of open files or LOBs has reached the maximum limit.

Action: Close some of the opened files or LOBs and retry the operation.

ORA-22291 Open LOBs exist at transaction commit time

Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time.

Action: Close the LOBs before committing the transaction.

ORA-22292 Cannot open a LOB in read-write mode without a transaction

Cause: An attempt was made to open a LOB in read-write mode before a transaction was started.

Action: Start a transaction before opening the LOB in read-write mode. Ways to start a transaction include issuing a SQL DML or SELECT FOR UPDATE command. Opening the LOB in read-only mode does not require a transaction.

ORA-22293 LOB already opened in the same transaction

Cause: An attempt was made to open a LOB that already is open in this transaction.

Action: Close the LOB before attempting to reopen it.

ORA-22294 cannot update a LOB opened in read-only mode

Cause: An attempt was made to write to or update a LOB opened in read-only mode.

Action: Close the LOB and reopen it in read-write mode before attempting to write to or update the LOB.

ORA-22295 cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement

Cause: An attempt was made to bind more than 4000 bytes of data to both LOB and LONG columns in the same insert or update statement. You can bind more than 4000 bytes of data to either a LONG column or one or more LOB columns, but not both.

Action: Bind more than 4000 bytes of data to either the LONG column or one or more LOB columns, but not both.

ORA-22296 invalid ALTER TABLE option for conversion of LONG datatype to LOB

Cause: An attempt was made to specify ALTER TABLE options which are disallowed during conversion of LONG datatype to LOB. The only ALTER TABLE options allowed during conversion of LONG datatype to LOB are the default clause and LOB storage clause for the column being converted to LOB.

Action: Remove the disallowed options.

ORA-22297 warning: Open LOBs exist at transaction commit time

Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time.

Action: This is just a warning. The transaction was commited successfully, but any domain or functional indexes on the open LOBs were not updated. You may want to rebuild those indexes.

ORA-22303 type "string"."string" not found

Cause: An attempt was made to obtain information for a type that cannot be found.

Action: Check that the schema is correct and that the type has been created correctly.

ORA-22304 input type is not an object type

Cause: An attempt was made to obtain the supertype information for a non-object type.

Action: Pass in only an object type.

ORA-22305 attribute/method/parameter "string" not found

Cause: Type element with the given name is not found in the type.

Action: Check to make sure that the type element exists.

ORA-22306 type "string"."string" already exists

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

Action: Check to make sure that the type has not been created prior to this.

ORA-22307 operation must be on a user-defined type

Cause: An attempt was made to perform an operation that is allowed only on a user-defined type, and the type is not a user-defined type.

Action: Check to make sure that only user-defined types are being operated on.

ORA-22308 operation not allowed on evolved type

Cause: An attempt was made to replace a type whose attribute definition has been altered.

Action: Submit ALTER TYPE ADD/DROP statement instead of ALTER TYPE REPLACE.

ORA-22309 attribute with name "string" already exists

Cause: An attempt was made to create an object type where more than one attributes have the same name.

Action: Check to make sure that all attribute names are unique.

ORA-22310 ALTER TYPE error. Refer to table "string"."string" for errors

Cause: An invalid alter type statement was submitted.

Action: Correct the errors listed in the specified table and resubmit the statement.

ORA-22311 type for attribute "string" does not exist

Cause: The type of the attribute does not exist.

Action: No types were created/modified for this DDL transaction. Redo the DDL transaction and add the creation of the attribute's type in the DDL transaction.

ORA-22312 must specify either CASCADE or INVALIDATE option

Cause: An attempt was made to alter a type which has a dependent type or table without specifying the CASCADE or INVALIDATE option.

Action: Resubmit the statement with either the CASCADE or INVALIDATE option. Specify CASCADE if you want to cascade the type change to dependent types and tables; otherwise, specify INVALIDATE to invalidate all dependents.

ORA-22313 cannot use two versions of the same type "string"

Cause: The version of this type conflicts with the version of this type used by another library that was linked in with the application. An application may only use one version of a type.

Action: Check that the libraries being linked with this application and use the same versions of the type.

ORA-22314 method information mismatch in ALTER TYPE

Cause: The number of methods or the method signature do not match that of the original type declaration. This is not supported.

Action: Make sure the method signature stay identical for the previously declared method. Do not drop existing methods.

ORA-22315 type "string" does not contain a map or order function

Cause: The input type does not contain a map or order function so one cannot be returned.

Action: Add a map or order function to the type or catch this error.

ORA-22316 input type is not a collection type

Cause: An attempt was made to obtain information for collection types on a non-named collection type.

Action: Use a named collection type for the function.

ORA-22317 typecode number is not legal as a number type

Cause: An attempt was made to use a number type code that is not valid.

Action: Use only OCI_TYPECODE_SMALLINT, OCI_TYPECODE_INTEGER, OCI_TYPECODE_REAL, OCI_TYPECODE_DOUBLE, OCI_TYPECODE_FLOAT, OCI_TYPECODE_NUMBER, or OCI_TYPECODE_DECIMAL.

ORA-22318 input type is not an array type

Cause: An attempt was made to obtain the number of elements for a non-array type.

Action: Pass in only a named collection type which is an array.

ORA-22319 type attribute information altered in ALTER TYPE

Cause: The type attribute information does not match that of the original type declaration when altering type. Attributes cannot be altered during ALTER TYPE. Only new methods can be added.

Action: Check that all type alterations are legal.

ORA-22320 missing user version string

Cause: The VERSION option is specified without a user version string.

Action: Resubmit the statement with the version string following the VERSION keyword.

ORA-22321 method does not return any result

Cause: OCITypeResult() was called on a method that does not return any results.

Action: Check that you are passing in the correct method descriptor, or that your method creation was done correctly.

ORA-22322 error table "string"."string" has incorrect structure

Cause: The specified error table does not have the expected table structure.

Action: Execute the DBMS_UTILITY.CREATE_ALTER_TYPE_ERROR_TABLE procedure to create an error table, then resubmit the statement using the new error table.

ORA-22323 error table "string"."string" does not exist

Cause: The error table does not exist.

Action: Resubmit the statement with a correct error table name.

ORA-22324 altered type has compilation errors

Cause: The use of the ALTER TYPE statement caused a compilation error.

Action: Correct the error reported and resubmit the statement.

ORA-22326 cannot change a type to FINAL if it has subtypes

Cause: An attempt was made to change a type with subtypes to FINAL.

Action: Drop all subtypes of the target type before changing it to FINAL.

ORA-22327 cannot change a type to NOT INSTANTIABLE if it has dependent tables

Cause: An attempt was made to change a type with dependent tables to NOT INSTANTIABLE.

Action: Drop all dependent tables of the target type and resubmit the statement.

ORA-22328 object "string"."string" has errors. string

Cause: Altering the target type causes errors in its dependent object.

Action: Correct the problem in the dependent object and resubmit the statement.

ORA-22329 cannot alter a non-object type

Cause: An attempt was made to execute ALTER TYPE on a non-object type.

Action: Drop the non-object type first, then re-create it as an object type.

ORA-22330 cannot alter a type that is not valid

Cause: An attempt was made to perform ALTER TYPE on an invalid type.

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

ORA-22331 cannot alter an incomplete type

Cause: An attempt was made to perform ALTER TYPE on an incomplete type.

Action: Use CREATE TYPE to completely define the original type before executing the ALTER TYPE.

ORA-22332 a dependent object in schema "string" has errors. string

Cause: Altering the target type causes errors in its dependent object.

Action: Correct the problem in the dependent object and resubmit the statement.

ORA-22333 cannot reset type "string"."string" due to invalid dependent types and tables

Cause: An attempt was made to reset the type version with invalid dependent types and tables.

Action: Use the ALTER TYPE COMPILE statement to compile all invalid dependent types and use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade all the dependent tables, then resubmit the statement.

ORA-22334 cannot reset type "string"."string". Dependent tables must be upgraded to latest version.

Cause: An attempt was made to reset the type version when the data in the dependent table has not been upgraded to the latest type version.

Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement.

ORA-22335 The client cannot work with an altered type

Cause: A pre 9.0.0 client has requested a type that has been altered on the server.

Action: Only 9.0.0 and higher clients can access altered types.

ORA-22336 table contained 8.0 image format, must specify INCLUDING DATA

Cause: One of the following:

An attempt was made to alter a type with a dependent table in 8.0 image format and the NOT INCLUDING TABLE DATA option was specified.
An attempt was made to upgrade a table in 8.0 image format with the NOT INCLUDING DATA option specified.

Action: Resubmit the statement with the INCLUDING DATA option.

ORA-22337 the type of accessed object has been evolved

Cause: The type of the accessed object has been altered and the client's object is based on an earlier type definition.

Action: The user needs to exit the application and modify the application to accommodate the type change. From SQL/PLUS, reconnect and resubmit the statement.

ORA-22338 must specify CASCADE INCLUDING DATA when altering the final property

Cause: An attempt was made to alter the final property of a type with dependent tables without specifying the CASCADE INCLUDING DATA option.

Action: Resubmit the statement with the CASCADE INCLUDING DATA option.

ORA-22339 cannot alter to not final since its attribute column is substitutable

Cause: An attempt was made to alter a type to not final when its embedded attribute is defined as substitutable in some tables. Note, this is a restriction in 9.0 version because when a type is altered to not final, column of that type is set to not substitutable at all levels; thus, it is an error if one of its embedded attribute column is already marked substitutable.

Action: Recreate the table and specify NOT SUBSTITUTABLE AT ALL LEVELS for all columns of non final type. Then resubmit the ALTER TYPE statement.

ORA-22340 cannot string type "string"."string". Dependent tables must be upgraded to latest version

Cause: An attempt was made to reset the version, drop or alter a type when the data in dependent table has not been upgraded to the latest version.

Action: Use the ALTER TABLE UPGRADE INCLUDING DATA statement to upgrade the data in the dependent tables then resubmit the statement.

ORA-22341 cannot assign supertype instance to subtype

Cause: An attempt was made to assign or copy a supertype instance to a container (destination) that can only hold a subtype instance.

Action: Make sure the runtime type of the source of the assignment or copy is the same type as the destination or is a subtype of the destination type.

ORA-22342 dependent VARRAY column exceeds the maximum inline column size

Cause: An attempt was made to alter a type (add or modify attribute) which causes the size of its dependent VARRAY column to exceed the maximum inline column size. However, the VARRAY column was not specified to be stored as LOB at the table level when the table was created.

Action: Specify the VARRAY column to be stored as LOB at the table level when the table is created.

ORA-22343 Compilation error for type invalidated by ALTER TYPE

Cause: Compilation failed for a type which was invalidated by ALTER TYPE.

Action: Check what is causing the compilation error, correct it, and try again.

ORA-22344 can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change

Cause: An attempt was made to specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change.

Action: Specify CONVERT TO SUBSTITUTABLE option only for ALTER TYPE NOT FINAL change.

ORA-22345 recompile type string.string before attempting this operation

Cause: An attempt was made to perform an operation which requires the specified datatype to be valid, but the datatype is invalid.

Action: Recompile the specified type and retry the operation.

ORA-22369 invalid parameter encountered in method string

Cause: An invalid parameter is being passed to this method of SYS.AnyType, SYS.AnyData, or SYS.AnyDataSet.

Action: Check the parameters being passed to this method and make sure that the parameters are allowed.

ORA-22370 incorrect usage of method string

Cause: This method of SYS.AnyType, SYS.AnyData, or SYS.AnyDataSet is being used inappropriately.

Action: Check the documentation for correct usage.

ORA-22371 Table contains data of type string.string, version string, which does not exist

Cause: Some of the older versions of the type may have been deleted because one or more of the referenced types was dropped.

Action: These data could not be read as the whole ADT. Read the data at individual scalar attribute level.

ORA-22600 encountered 8.0.2 (Beta) VARRAY data that cannot be processed

Cause: Production Oracle8 (8.0.3 and beyond) encountered some VARRAY data which was created and stored by Oracle8 8.0.2 (Beta 2). Production Oracle8 cannot understand or process such VARRAY data.

Action: Delete the VARRAY data from the table by dropping the table, deleting the rows, or nulling out the VARRAY columns, and then reinsert the VARRAY data. There is no provided script or tool to help automate this conversion.

ORA-22601 pickler TDS context [string] is not initialized

Cause: An attempt was made to use the pickler TDS context without initializing it.

Action: Use OCIPicklerTdsCtxInit to initialize the context.

ORA-22602 pickler TDS handle [string] is not well-formed

Cause: An attempt was made to use the pickler TDS handle without initializing or constructing it.

Action: Use OCIPicklerTdsInit to initialize the handle before it is constructed. Use OCIPicklerTdsGenerate to generate the TDS before its attributes can be accessed.

ORA-22603 cannot add an attribute to the already generated TDS handle

Cause: An attempt was made to add an attribute to the already constructed TDS.

Action: Use a TDS handle that is initialized but not yet constructed.

ORA-22604 TDS handle already generated

Cause: An attempt was made to generate TDS that is already generated.

Action: Use a TDS handle that is initialized but not yet generated.

ORA-22605 FDO handle [string] is not initialized

Cause: An attempt was made to use an uninitialized FDO handle.

Action: Use OCIPicklerFdoInit to initialize FDO handle.

ORA-22606 pickler image handle [string] is not well-formed

Cause: An attempt was made to use the image handle without initializing/ constructing it.

Action: Use OCIPicklerImageInit to initialize the handle before it is constructed. Use OCIPicklerImageGenerate to generate the image before its attributes can be accessed.

ORA-22607 image handle already generated

Cause: An attempt was made to generate image that is already generated.

Action: Use a image handle that is initialized but not yet generated.

ORA-22608 cannot add an attribute to the already generated image handle

Cause: An attempt was made to add an attribute to the already constructed image.

Action: Use a image handle that is initialized but not yet constructed.

ORA-22609 error string during initialization of FDO

Cause: An error occurred during FDO initialization.

Action: Take an action based on the specified error.

ORA-22610 error while adding a scalar to the image handle

Cause: An error occurred while adding a scalar attribute to the image handle.

Action: Make sure image handle is initialized before adding scalar.

ORA-22611 TDS version is not recognized

Cause: Incorrect TDS handle is passed.

Action: Make sure image handle is initialized with the correct TDS.

ORA-22612 TDS does not describe a collection TDS

Cause: Collection construct/access routines are being on an image but the TDS does not describe that a collection TDS.

Action: Make sure a collection TDS is used before invoking collection routines on the image handle.

ORA-22613 buflen does not match the size of the scalar

Cause: BUFLEN is incorrect.

Action: Make sure BUFLEN is correct and matches the size of the scalar.

ORA-22614 error while construction the collection in the image

Cause: An error occurred during the construction of collection.

Action: Make sure image handle is initialized and OCIPicklerImageCollBegin is called to begin collection.

ORA-22615 attribute is not a collection

Cause: Collection routine is invoked upon a non-collection attribute.

Action: Make sure attribute is a collection.

ORA-22616 image is not of Oracle 8.1 format

Cause: The function being invoked is applicable only for 8.1 images.

Action: Make sure image is of 8.1 format.

ORA-22617 error while accessing the image handle collection

Cause: An error occurred while accessing collection in the image handle.

Action: Make sure image is initialized correctly and the collection is constructed properly.

ORA-22618 attribute is a BAD NULL in the image handle

Cause: The attribute in question is probably the attribute of a null embedded image.

Action: Make sure attribute number is valid or it is NULL or NOT NULL.

ORA-22619 all collection elements have already been accessed

Cause: An attempt was made to access a collection element after all the collection elements are already accessed.

Action: This function should not be invoked any more.

ORA-22620 buffer size too small to hold the value

Cause: Buffer size is not enough to hold the value. Most likely while doing the character set conversion, a bigger buffer is needed.

Action: Pass in a bigger buffer. If the client character set format differs from that of server, doing the conversion may result in 4X expansion.

ORA-22621 error transfering an object from the agent

Cause: An error was returned from the pickler routines on the agent side.

Action: Contact Oracle Support Services.

ORA-22625 OCIAnyData is not well-formed

Cause: Attempt to use the OCIAnyData without initializing constructing it.

Action: Use OCIAnyDataBeginConstruct to initialize the handle before it is adding attributes. Use OCIAnyDataEndConstruct to complete the construction. Or use OCIAnyDataConvert to do the construction. MAke sure it is properly constructed before accessing attributes.

ORA-22626 Type Mismatch while constructing or accessing OCIAnyData

Cause: Type supplied is not matching the type of the AnyData. If piece wise construction or access is being attempted, the type supplied is not matching the type of the current attribute.

Action: Make sure the type supplied matches the type of object to be constructed or accessed.

ORA-22627 tc [string] must be that of object/varray/nested table

Cause: Type code is not that of object/varray/nested table

Action: Make sure the type code is OCI_TYPECODE_OBJECT, OCI_TYPECODE_VARRAY, or OCI_TYPECODE_TABLE

ORA-22628 OCIAnyData already constructed

Cause: Attempt to add attributes to OCIAnyData that is already constructed.

Action: Use the OCIAnyData that is initialized but not yet constructed.

ORA-22629 OCIAnyData is null

Cause: Attempting an operation that is not valid on null OCIAnyData.

Action: Make sure OCIAnyData is not null.

ORA-22630 attribute [string] is null or it is not well-formed

Cause: Passing an attribute that is null or not well-formed.

Action: Make sure the attribute is not null or is well-formed.

ORA-22631 attribute [string] is is not well-formed or does not match the type

Cause: Passing an attribute that is not well-formed or does not match the input type.

Action: Make sure the attribute is well-formed and matches the type specified.

ORA-22632 AnyDataSet parameter is not valid for the current operation

Cause: The AnyDataSet parameter is null or invalid for the current operation.

Action: Check the documentation for the current operation.

ORA-22633 Error freeing AnyDataSet

Cause: AnyDataSet that is passed in may not be valid.

Action: Check all the AnyDataSet parameters.

ORA-22634 Error adding new instance to AnyDataSet

Cause: Current instance in the AnyDataSet has not been fully constructed.

Action: Make sure that the current instance is fully constructed before adding new instance.

ORA-22800 invalid user-defined type

Cause: An attempt was made to use an incomplete type as a constructor.

Action: Complete the type definition before using it in a query.

ORA-22801 invalid object row variable

Cause: The specified object row variable is not available in the scope of name resolution.

Action: Verify the specified object row variable is correct, or use an object row variable visible in scope.

ORA-22803 object type contains zero attributes

Cause: An attempt was made to create or specify a column or constructor of an object type that has no attributes. Only object types that have at least one attribute are allowed in this context.

Action: Specify a valid object type.

ORA-22804 remote operations not permitted on object tables or user-defined type columns

Cause: An attempt was made to perform queries or DML operations on remote object tables or on remote table columns whose type is one of object, REF, nested table or VARRAY.

Action: Remove the reference to remote tables in the statement.

ORA-22805 cannot insert NULL object into object tables or nested tables

Cause: An attempt was made to insert a NULL object into an object table or a Nested Table.

Action: Ensure that a non-NULL object is inserted into the table or insert an object with attributes whose values

Oracle Database Server Messages(三) . .

9 ORA-12300 to ORA-12399

10 ORA-12400 to ORA-12699

11 ORA-12700 to ORA-19399

12 ORA-19400 to ORA-24279

你可能感兴趣的:(oracle)

9
ORA-12300 to ORA-12399

10
ORA-12400 to ORA-12699

11
ORA-12700 to ORA-19399

12
ORA-19400 to ORA-24279