| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
9
ORA-12300 to ORA-12399
-
Cause: The database link name you specified on the
ALTER DATABASEstatement is not an ROM: link. You must specify an ROM: link when using theALTER DATABASEstatement to mount or open a secondary database. -
Action: Re-issue the
ALTER DATABASEstatement 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 theCREATE DATABASE LINKstatement. See your documentation for Oracle security-related products for more information about creating database links using the ROM: link type. -
Cause: The connect string in the
CREATE DATABASE LINKstatement 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 LINKstatement. -
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.
-
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 DATABASElinknameOPENstatement to open the database. -
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.
-
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 DATABASElinknamewith theOPENandMOUNToptions. Alternately, to allow your instance to automatically mount and open secondary databases, set theAUTO_MOUNTINGparameter in the parameter file to TRUE. -
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to open a database that has not been mounted.
-
Action: Mount the database with the
ALTER DATABASElinknameMOUNTstatement, then re-attempt to open the database. -
Cause: An attempt was made to dismount a database that is still open.
-
Action: Close the database with the
ALTER DATABASElinknameCLOSEstatement, then re-attempt to dismount the database. -
Cause: An attempt was made to close a database that is not open.
-
Action: The database is closed; you can proceed with dismounting it.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
ORA-12315 database link type is invalid for the ALTER DATABASE statement
ORA-12316 syntax error in database link's connect string
ORA-12317 logon to database (link name string) denied
ORA-12318 database (link name string) is already mounted
ORA-12319 database (link name string) is already open
ORA-12321 database (link name string) is not open and AUTO_MOUNTING=FALSE
ORA-12322 unable to mount database (link name string)
ORA-12323 unable to open database (link name string)
ORA-12324 cannot use the ROM: link type on a private database link
ORA-12326 database string is closing immediately; no operations are permitted
ORA-12329 database string is closed; no operations are permitted
ORA-12333 database (link name string) is not mounted
ORA-12334 database (link name string) is still open
ORA-12335 database (link name string) is not open
ORA-12336 cannot login to database (link name string)
ORA-12341 maximum number of open mounts exceeded
ORA-12342 open mounts exceeds limit set on the OPEN_MOUNTS parameter
ORA-12345 user string lacks CREATE SESSION privilege in database link (linkname string)
ORA-12350 database link being dropped is still mounted
ORA-12351 cannot create view using a remote object which has a remote object reference
ORA-12352 object string.string@string is invalid
ORA-12353 secondary stored object cannot reference remote object
ORA-12354 secondary object being dropped
|  Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
10
ORA-12400 to ORA-12699
-
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.
-
Cause: The policy could not convert the label string to a valid internal label.
-
Action: Correct the syntax of the label string.
-
Cause: The format string is not supported by the policy.
-
Action: Correct the syntax of the format string.
-
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.
-
Cause: The policy could not interpret the privilege string.
-
Action: Specify a privilege string that is supported by the policy.
-
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.
-
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.
-
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.
-
Cause: The specified policy does not support the requested operation.
-
Action: Consult the policy documentation to determine the supported access mediation operations.
-
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.
-
Cause: The policy enforcement encountered an internal error.
-
Action: Consult the policy documentation for details.
-
Cause: The specified label value does not exist.
-
Action: Check the data dictionary views for the policy to identify valid labels.
-
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.
-
Cause: The labels being compared belong to different policies.
-
Action: Only compare labels that belong to the same policy.
-
Cause: An internal label policy framework error occurred.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The specified policy does not exist in the database.
-
Action: Enter the correct policy name or create the policy.
-
Cause: The specified object was not in the database.
-
Action: Enter the correct name for the database object.
-
Cause: The specified user does not exist in the database.
-
Action: Correct the user name or create the user.
-
Cause: A null value was provided for a binary label operation.
-
Action: Provide a valid binary label for the operation.
-
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.
-
Cause: The label sizes for the binary label operation were not equal.
-
Action: Provide binary labels with the same lengths for the operation.
-
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_POLICIESinitialization parameter and restart the server. -
Cause: The position specified for a binary label operation was invalid.
-
Action: Provide a position that is within the label size limits.
-
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.
-
Cause: You tried to either apply a policy to the
SYS,SYSTEM, orLBACSYSschema or to set user labels/privileges for theSYS,SYSTEM, orLBACSYSuser. -
Action: Apply policies and set authorizations only for non-system users.
-
Cause: The option specified was not a valid audit option for the specified policy.
-
Action: Enter a correct audit option.
-
Cause: An input parameter was specified incorrectly.
-
Action: Correct the parameter value.
-
Cause: The specified index value was not between 1 and 6.
-
Action: Correct the index value for the label list operation.
-
Cause: The specified privilege number was not between 1 and 32.
-
Action: Correct the privilege number.
-
Cause: The specified audit action was not a valid audit action.
-
Action: Correct the audit action number.
-
Cause: LBAC enforcement resulted in an error.
-
Action: Correct the problem identified in the error message.
-
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.
-
Cause: The audit type must be
BY ACCESSorBY SESSION. -
Action: Correct the audit type value.
-
Cause: The audit success parameter must be SUCCESSFUL or NOT SUCCESSFUL.
-
Action: Correct the audit success value.
-
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.
-
Cause: A value that was not a valid policy option was entered.
-
Action: Correct the policy option value.
-
Cause: A policy option was entered more than once in the option string.
-
Action: Remove the duplicate policy option value.
-
Cause: A set of contradictory policy options was entered.
-
Action: Provide a set of compatible policy options.
-
Cause: The use of the
SYSDBApackage requires theLBAC_DBArole. -
Action: Grant the
LBAC_DBArole to the database user. -
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: You tried to perform an administrative function for a policy, but you have not been granted the
policy_DBArole. -
Action: Grant the user the
policy_DBArole for the specified policy. -
Cause: The role named
policy_DBAalready exists. -
Action: Correct the policy name or delete the existing policy.
-
Cause: You tried to alter a schema policy that was not applied.
-
Action: Correct the policy name or schema name.
-
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.
-
Cause: You tried to specify a
LOBdatatype for a column or attribute, but the use of theLOBdatatype has been disabled. -
Action: Change the LBAC initialization file to allow the creation of
LOBcolumns and attributes. -
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.
-
Cause: The label tag value you entered is already in use for another label.
-
Action: Enter a different value for the label tag.
-
Cause: The label value you entered already exists.
-
Action: No action necessary; alter the label to change its tag or type.
-
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.
-
Cause: The specified level is not defined for the policy.
-
Action: Correct the level identifier value.
-
Cause: The specified compartment is not defined for the policy.
-
Action: Correct the compartment identifier value.
-
Cause: The specified group is not defined for the policy.
-
Action: Correct the group identifier value.
-
Cause: Label components can contain only alphanumeric characters, blanks, and underscores.
-
Action: Correct syntax of the label component.
-
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.
-
Cause: The default level cannot be greater than the user's maximum.
-
Action: Enter an authorized level.
-
Cause: You included compartments or groups in the minimum label.
-
Action: Enter only an authorized minimum level as the label.
-
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.
-
Cause: No levels have been specified for the user.
-
Action: Enter the maximum and minimum labels for the user.
-
Cause: The label entered is NULL or not within the user's authorizations.
-
Action: Enter the authorized labels for the 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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An internal MLS policy error occurred.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: You attempted to enter a value for DBHIGH that did not dominate DBLOW.
-
Action: Enter a value for DBHIGH that dominates DBLOW.
-
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.
-
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_LABELSview for the valid MLS labels. -
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.
-
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.
-
Cause: You attempted to change the number assigned to level, category or releasability category.
-
Action: Change the character string representations, not the numbers.
-
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-12400 invalid argument to facility error handling
ORA-12401 invalid label string: string
ORA-12402 invalid format string: string
ORA-12403 invalid internal label
ORA-12404 invalid privilege string: string
ORA-12405 invalid label list
ORA-12406 unauthorized SQL statement for policy string
ORA-12407 unauthorized operation for policy string
ORA-12408 unsupported operation: string
ORA-12409 policy startup failure for string policy
ORA-12410 internal policy error for policy: string Error: string
ORA-12411 invalid label value
ORA-12412 policy package string is not installed
ORA-12413 labels do not belong to the same policy
ORA-12414 internal LBAC error: string Error: string
ORA-12415 A column of another datatype exists on the specified table
ORA-12416 policy string not found
ORA-12417 database object "string" not found
ORA-12418 user string not found
ORA-12419 null binary label value
ORA-12420 required procedures and functions not in policy package "string"
ORA-12421 different size binary labels
ORA-12422 max policies exceeded
ORA-12423 invalid position specified
ORA-12424 length exceeds binary label size
ORA-12425 cannot apply policies or set authorizations for system schemas
ORA-12426 invalid audit option
ORA-12427 invalid input value for string parameter
ORA-12429 label list range exceeded
ORA-12430 invalid privilege number
ORA-12431 invalid audit action
ORA-12432 LBAC error: string
ORA-12433 create trigger failed, policy not applied
ORA-12434 invalid audit type: string
ORA-12435 invalid audit success: string
ORA-12436 no policy options specified
ORA-12437 invalid policy option: string
ORA-12438 repeated policy option: string
ORA-12439 invalid combination of policy options
ORA-12440 insufficient authorization for the SYSDBA package
ORA-12441 policy string already exists
ORA-12442 policy column "string" already used by an existing policy
ORA-12443 policy not applied to some tables in schema
ORA-12444 policy already applied to table
ORA-12445 cannot change HIDDEN property of column
ORA-12446 Insufficient authorization for administration of policy string
ORA-12447 policy role already exists for policy string
ORA-12448 policy string not applied to schema string
ORA-12449 Labels specified for user must be of type USER
ORA-12450 LOB datatype disabled in LBAC initialization file
ORA-12451 label not designated as USER or DATA
ORA-12452 label tag string already exists
ORA-12453 label string already exists
ORA-12454 label string does not exist for policy string
ORA-12461 undefined level string for policy string
ORA-12462 undefined compartment string for policy string
ORA-12463 undefined group string for policy string
ORA-12464 invalid characters in label component string
ORA-12465 not authorized for read or write on specified groups or compartments
ORA-12466 default level is greater than the user's maximum
ORA-12467 minimum label can contain a level only
ORA-12468 max write level does not equal max read level
ORA-12469 no user levels found for user string and policy string
ORA-12470 NULL or invalid user label: string
ORA-12471 Specified compartment or group is not authorized for user
ORA-12476 least upper bound resulted in an invalid OS label
ORA-12477 greatest lower bound resulted in an invalid OS label
ORA-12479 file label string must equal DBHIGH string
ORA-12480 specified clearance labels not within the effective clearance
ORA-12481 effective label not within program unit clearance range
ORA-12482 internal MLS error: string Error: string
ORA-12483 label not in OS system accreditation range
ORA-12484 invalid OS label
ORA-12485 new effective label not within effective clearance
ORA-12486 effective max labels and min labels cannot be changed
ORA-12487 clearance labels not between DBHIGH and DBLOW
ORA-12488 maximum label does not dominate minimum label
ORA-12489 default label not within clearance range
ORA-12490 DBHIGH cannot be lowered
ORA-12491 DBHIGH value does not dominate DBLOW
ORA-12492 DBLOW cannot be changed
ORA-12493 invalid MLS binary label
ORA-12494 cannot insert or delete a level, category, or release category
ORA-12495 cannot disable an enabled level, category, or release category
ORA-12496 cannot change existing level, category, or release numbers
ORA-12497 maximum combined categories exceeds string
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).
| Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
11
ORA-12700 to ORA-19399
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: There are two possible causes: Either an attempt was made to issue an
ALTER SESSIONstatement with an invalid NLS parameter or value; or theNLS_LANGenvironment variable contains an invalid language, territory, or character set. -
Action: Check the syntax of the
ALTER SESSIONstatement and the NLS parameter, correct the syntax and retry the statement, or specify correct values in theNLS_LANGenvironment variable. For more information about the syntax of theALTER SESSIONstatement, see the Oracle9i SQL Reference. -
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The character set specified when creating the control file is unknown.
-
Action: Specify a known character set.
-
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.
-
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.
-
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_EXCPtofalse. -
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.
-
Cause: The character set specified is not allowed for this operation or is invalid.
-
Action: Ensure that the specified character set is valid.
-
Cause:
CLOBdata changes representation to Unicode when converting to a multibyte character set and must be migrated. -
Action: Remove
CLOBdata as listed in the alert file.CLOBdata can be migrated by methods such as export/import. -
Cause:
NCLOBdata changes representation to Unicode when converting to a multibyte character set and must be migrated. -
Action: Remove
NCLOBdata as listed in the alert file. NCLOB data can be migrated by methods such as export/import. -
Cause: This command can only be run when connecting as user
SYS. -
Action: Connect as user
SYSto run this command. -
Cause: This command can only be run when the database is in RESTRICTED mode.
-
Action: Ensure that the system is in RESTRICTED mode.
-
Cause: This command can only be run when the database is in EXCLUSIVE mode.
-
Action: Ensure that the system is in EXCLUSIVE mode.
-
Cause: This command can only be run when there are no other sessions active.
-
Action: Ensure there are no other connections to the database.
-
Cause: Load on the system is too high to perform parallel queries.
-
Action: Re-execute serially or wait until the system load is reduced.
-
Cause: A parallel query server reached an exception condition.
-
Action: Check the following error message for the cause.
-
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.
-
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.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: This error should not normally occur. If it persists, THEN contact Oracle Support Services.
-
Cause: An attempt was made to set
SCAN_INSTANCESorCACHE_INSTANCESusing theALTER SYSTEMstatement 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.
-
Cause: An attempt was made to set
SCAN_INSTANCESorCACHE_INSTANCESusing theALTER SYSTEMstatement 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.
-
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.
-
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.
-
Cause:
PARALLELwas specified more than once,NOPARALLELwas specified more than once, or bothPARALLELandNOPARALLELwere specified in aCREATE TABLE,CLUSTER, orINDEXor in anALTER TABLEorCLUSTERstatement, or in aRECOVERcommand. -
Action: Remove all but one of the PARALLEL or NOPARALLEL clauses and reissue the statement.
-
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.
-
Cause:
CACHEwas specified more than once,NOCACHEwas specified more than once, or bothCACHEandNOCACHEwere specified in aCREATE TABLEorCLUSTER, or in anALTER TABLEorCLUSTERstatement. -
Action: Remove all but one of the
CACHEorNOCACHEclauses and reissue the statement. -
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.
-
Cause: The parallel create index fastpath operation event has been set.
-
Action: Set this event only under the supervision Oracle development.
-
Cause: A parallel query option feature has been invoked but this option has not been enabled.
-
Action: Enable the parallel query option.
-
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.
-
Cause: PARALLEL clause cannot be empty.
-
Action: specify any combination of DEGREE { n | DEFAULT } and INSTANCES { n | DEFAULT } within the PARALLEL clause.
-
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.
-
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.
-
Cause: DEGREE or INSTANCES was specified more than once within a PARALLEL clause.
-
Action: Specify each desired PARALLEL clause option only once.
-
Cause: The
PARALLELkeyword was used alone orDEGREE DEFAULTwas specified in thePARALLELclause of anALTER DATABASE RECOVERstatement. -
Action: Respecify with an explicit degree of parallelism.
-
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.
-
Cause: The DEGREE option was omitted from an ALTER DATABASE RECOVER command.
-
Action: Respecify with an explicit degree of parallelism.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The instance group name is too long.
-
Action: Either shorten the name or get rid of the instance 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.
-
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.
-
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.
-
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.
-
Cause: Transaction in progress.
-
Action: Commit or roll back the transaction and then re-execute.
-
Cause: Schema modified during the parse phase of parallel processing.
-
Action: No action required.
-
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.
-
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.
-
Cause: In a locally managed database, default temporary tablespace must be TEMPORARY type.
-
Action:
-
Cause: In a dictionary-managed database, default temporary tablespace must be SYSTEM or TEMPORARY type.
-
Action:
-
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.
-
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.
-
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.
-
Cause: An attempt was made to create a dictionary managed tablespace in a database whose
SYSTEMtablespace is locally managed. -
Action: Create a locally managed tablespace.
-
Cause: An attempt was made to migrate a locally managed tablespace to dictionary managed type when the database has a locally managed
SYSTEMtablespace. -
Action: Such an operation cannot be issued.
-
Cause: An attempt was made to alter a dictionary managed tablespace to read write in a database whose
SYSTEMtablespace is locally managed. This tablespace can only be dropped. -
Action: Such an operation cannot be issued.
-
Cause: The
ALTER DATABASE FORCE LOGGINGstatement failed because the database is already in force logging mode. -
Action: No action required.
-
Cause: The
ALTER DATABASE NO FORCE LOGGINGstatement failed because the database is not in force logging mode. -
Action: No action required.
-
Cause: There is a concurrent
ALTER DATABASE FORCE LOGGINGorALTER DATABASE NO FORCE LOGGINGstatement running in the system. -
Action: Contact the database administrator who is responsible for the concurrent statement.
-
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 LOGGINGstatement. -
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.
-
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.
-
Cause: In
CREATE TABLESPACE, theFORCE LOGGINGoption was specified more than once. -
Action: Remove all but one of the
FORCE LOGGINGoptions. -
Cause: An attempt was made to specify checkpoint option with SET UNUSED.
-
Action: Remove the checkpoint option.
-
Cause: An attempt was made to drop a column from an object type table.
-
Action: This action is not allowed.
-
Cause: An attempt was made to drop a column from a nested table.
-
Action: This action is not allowed.
-
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.
-
Cause: An attempt was made to drop a column used as the partitioning key.
-
Action: This action is not allowed.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to drop a column from a system table.
-
Action: This action is not allowed.
-
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.
-
Cause: Duplicate option specified in statement.
-
Action: Remove the duplicate option and resubmit statement.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to submit DROP COLUMNS CONTINUE statement while there are no partially dropped columns.
-
Action: Cannot submit this statement.
-
Cause: An attempt was made to drop a virtual column generated by the system.
-
Action: This action is not allowed.
-
Cause: An attempt was made to drop a primary key column from an index- organized table.
-
Action: This action is not allowed.
-
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.
-
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.
-
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.
-
Cause: The specified range for a dimension is invalid.
-
Action: Make sure that the lower bound (lb) is less than the upper bound (ub).
-
Cause: The buffer size for a function is not valid.
-
Action: This is an internal error. Contact Oracle Support Services.
-
Cause: An error occurred in a recursively called HHCODE function.
-
Action: This is an internal error. Contact Oracle Support Services.
-
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).
-
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].
-
Cause: Part of the specified date format is invalid.
-
Action: Verify that the date format is valid.
-
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.
-
Cause: An invalid number of arguments was specified for an SDO function.
-
Action: Verify the syntax of the function call.
-
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.
-
Cause: An invalid window type was specified.
-
Action: Valid window types are RANGE, PROXIMITY, POLYGON.
-
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.
-
Cause: A topology identifier outside the range of 1 to 8 was specified.
-
Action: Specify a topology in the range of 1 to 8.
-
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.
-
Cause: The partition common code was not correctly decoded.
-
Action: This is an internal error. Contact Oracle Support Services.
-
Cause: The shape of a 2-D line partition could not be determined.
-
Action: This is an internal error. Contact Oracle Support Services.
-
Cause: The specified distance type is invalid.
-
Action: The only supported distance functions are EUCLID and MANHATTAN.
-
Cause: Vertex coordinates lie outside the valid range for the specified dimension.
-
Action: Re-define vertex coordinates within specified boundaries.
-
Cause: A vertex coordinate has a NULL value.
-
Action: Re-define vertex coordinate to have a non-NULL value.
-
Cause: The coordinates defining a geometric element are not connected.
-
Action: Re-define coordinates for the geometric element.
-
Cause: The coordinates defining a polygonal geometric element represent crossing segments.
-
Action: Re-define the coordinates for the polygon.
-
Cause: An interior element of a geometric object interacts with the exterior element of that object.
-
Action: Re-define coordinates for the geometric elements.
-
Cause: The coordinates defining a polygonal geometric element represent less than three segments.
-
Action: Re-define the coordinates for the polygon.
-
Cause: The coordinates defining a polygonal geometric element represent an open polygon.
-
Action: Re-define the coordinates of the polygon.
-
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.
-
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.
-
Cause: There is an invalid SDO_GTYPE in the SDO_GEOMETRY object.
-
Action: Verify that the geometries have valid gtypes.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Note any accompanying errors and contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The specified spatial table does not exist.
-
Action: Check the Spatial Data option data dictionary to make sure that the table is registered.
-
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.
-
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.
-
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.
-
Cause: The specified count mode is not valid.
-
Action: Alter the count mode. Valid count modes are ESTIMATE or EXACT.
-
Cause: The specified Oracle table does not exist.
-
Action: Check the Oracle7 data dictionary and make sure that the table exists.
-
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.
-
Cause: The specified tablespace is already allocated to the spatial table.
-
Action: Allocate another tablespace name to the table.
-
Cause: The specified tablespace is not allocated to the specified spatial table.
-
Action: Allocate the tablespace to the spatial table.
-
Cause: The specified partition does not exist.
-
Action: Verify the name of the partition by checking the Spatial Data option data dictionary.
-
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.
-
Cause: The creation of a child partition failed.
-
Action: Check for other errors that accompany this error and correct them first.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The specified column is already defined for the spatial table.
-
Action: Use a different column name.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: A partition key is already set for the spatial table.
-
Action: Only one partition key can be specified per spatial table.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The specified spatial column does not exist.
-
Action: Verify that the specified column is a spatial column by checking the Spatial Data option data dictionary.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The specified target type is not valid.
-
Action: Substitute a valid target type. Valid target types are TABLE or VIEW.
-
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.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Document messages and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Document messages and contact Oracle Support Services.
-
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.
-
Cause: This is an internal error.
-
Action: Document messages and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Document messages and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Document messages and contact Oracle Support Services.
-
Cause: Operation failed to insert a record into the exception table.
-
Action: Fix any other errors reported.
-
Cause: Operation failed to insert a record into the exception table.
-
Action: Fix any other errors reported.
-
Cause: The specified HHCODE type is not valid.
-
Action: Substitute a valid HHCODE type. Valid HHCODE types are POINT and LINE.
-
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.
-
Cause: The precision specified is out of range.
-
Action: The precision must be an integer greater than or equal to zero.
-
Cause: The number of dimensions specified is out of range.
-
Action: The number of dimensions must be between 1 and 32.
-
Cause: The specified table has rows in it.
-
Action: Make sure that the table to be registered is empty.
-
Cause: The specified Oracle error was encountered.
-
Action: Correct the Oracle error.
-
Cause: The specified object does not exist.
-
Action: Verify that the specified object exists.
-
Cause: The specified table already exists.
-
Action: Drop the specified table.
-
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.
-
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.
-
Cause: The geometry type in the layer_SDOGEOM table is unsupported.
-
Action: Modify the geometry type to be one of the supported types.
-
Cause: Initialization of the tessellation package failed.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Record the error messages that are returned and contact Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services with the exact error text.
-
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.
-
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 TABLEprivilege and that the user has sufficient quota in the default or specified tablespace. -
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.
-
Cause: An error was encountered while trying to create the index table.
-
Action: Check that user has
create tableprivilege in the current schema and that the user has sufficient quota in the default or specified tablespace. -
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.
-
Cause: An internal error was encountered while creating the spatial index.
-
Action: Contact Oracle Support Services with the exact error text.
-
Cause: An error was encountered while evaluating the specified operator.
-
Action: Check the parameters and the return type of the specified operator.
-
Cause: An internal error was encountered.
-
Action: Contact Oracle Support Services with the exact error text.
-
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.
-
Cause: An error was encountered while trying to insert data into the index table. Likely causes are:
-
Action: Check the accompanying error messages.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The spatial relationship between a generated tile and the specified geometry 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-13220 and contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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 TABLEprivleges and has sufficient space in the default or specified tablespace. -
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 TABLEprivleges and has sufficient space in the default or specified tablespace. -
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.
-
Cause: The specified sequence number exists.
-
Action: Delete the sequence object or contact Oracle Support Services.
-
Cause: The index table is either deleted or corrupted.
-
Action: Rebuild the index or contact Oracle Support Services with accompanying error messages.
-
Cause: An internal error occurred in R-tree processing.
-
Action: Contact Oracle Support Services with message text.
-
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.
-
Cause: An error occurred in reading the dimensionality parameter.
-
Action: Check the documentation for a valid range and specify the dimensionality as a parameter.
-
Cause: An error occurred because of too few values in query mbr.
-
Action: Omit the dimensionality or use the dimensionality of the query.
-
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.
-
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.
-
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.
-
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.
-
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
SELECTprivilege on those tables. -
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An internal error occurred.
-
Action: Contact Oracle Support Services with the exact error message text.
-
Cause: An OCI error occurred while processing the layer or geometry tables.
-
Action: Take the appropriate steps to correct the OCI specific error.
-
Cause: Insufficient memory.
-
Action: Make more memory available to the current session/process.
-
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.
-
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.
-
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.
-
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.
-
Cause: OCI internal error.
-
Action: Contact Oracle Support Services with the exact error message text.
-
Cause: OCI internal error.
-
Action: Contact Oracle Support Services with the exact error message text.
-
Cause: OCI internal error or SRID does not match a table entry.
-
Action: Check that a valid SRID is being used.
-
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.
-
Cause: OCI internal error.
-
Action: Contact Oracle Support Services with the exact error message text.
-
Cause: OCI internal error.
-
Action: Contact Oracle Support Services with the exact error message text.
-
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.
-
Cause: A geometry with a gtype of <= 0 was specified for transformation. Only a gtype >= 1 is allowed.
-
Action:
-
Cause: An internal error while transforming points.
-
Action: Check the accompanying error messages.
-
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.
-
Cause: Cannot convert the specified unit from/to standard unit for linear distance, angle, or area.
-
Action: Check unit specification and respecify it.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Low level coordinate transformation error trap.
-
Action: Check the accompanying error messages.
-
Cause: OCI internal error.
-
Action: Contact Oracle Support Services with the exact error message text.
-
Cause: OCI internal error.
-
Action: Contact Oracle Support Services with the exact error message text.
-
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.
-
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).
-
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.
-
Cause: The given measure for linear referencing was out of range.
-
Action: Re-define the given measure.
-
Cause: The given geometric segments were not connected.
-
Action: Check the start/end points of the given geometric segments.
-
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).
-
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.
-
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.
-
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.
-
Cause: Clipping (dynseg) a polygon across multiple rings.
-
Action: Polygon clipping only allowed for a single ring.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The boundary of a polygon intersects itself.
-
Action: Correct the geometric definition of the object.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: There are repeated points in the sequence of coordinates.
-
Action: Remove the redundant point.
-
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.
-
Cause: Circle type should be represented by 3 distinct points on the circumference.
-
Action: Confirm that there are only 3 points for circle type.
-
Cause: The 2 points representing the extent are identical.
-
Action: Confirm that the 2 points describing the extent type are distinct.
-
Cause: This subtype is not allowed within the ETYPE specified.
-
Action: Refer to Oracle Spatial User's Guide and Reference for type definitions.
-
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.
-
Cause: Compound polygon must describe an enclosed area.
-
Action: Confirm that all sub-elements are connected.
-
Cause: None of the ETYPEs within the geometry is supported.
-
Action: Confirm that there is at least one valid ETYPE.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The SDO_MBR functionality is not supported for geodetic data.
-
Action: Find an alternative function that can be used in this context.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This is an internal Oracle GeoImage error.
-
Action: Contact Oracle Support Services.
-
Cause: The GeoImage format is not supported.
-
Action: Confirm that the GeoImage format is valid and supported.
-
Cause: The object specified as the destination is NULL.
-
Action: Confirm that the object specified as the destination is not NULL.
-
Cause: The source GeoImage has a NULL geometry.
-
Action: Verify that the geometry of the source GeoImage is not NULL.
-
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.
-
Cause: The object specified as the source is NULL.
-
Action: Confirm that the object specified as the source is not NULL.
-
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.
-
Cause: The GeoImage space type qualifier is invalid.
-
Action: Use a valid space type qualifier (RASTER or MODEL).
-
Cause: The table name parameter is NULL.
-
Action: Verify that the parameter used for the table name is not NULL.
-
Cause: The table specified does not exist.
-
Action: Verify that the table name used is valid and the table exists.
-
Cause: The column name parameter is NULL.
-
Action: Verify that the parameter used for the column name is not NULL.
-
Cause: The column specified does not exist.
-
Action: Verify that the column name used is valid and the column exists.
-
Cause: The ROWID value used is not valid.
-
Action: Verify that the ROWID value used is valid.
-
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.
-
Cause: The table containing the GeoImage could not be updated.
-
Action: Verify that the table exists and is valid.
-
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.
-
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.
-
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.
-
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.
-
Cause: A latitude value outside the valid range [-90,90] has been used.
-
Action: Verify that the GeoImage geometry definition is within the domain.
-
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.
-
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.
-
Cause: The LOB used for the source is not initialized.
-
Action: Verify that the source is properly initialized.
-
Cause: The LOB used for the source is empty.
-
Action: Verify that the source is properly initialized and data has been imported into it.
-
Cause: The LOB used for the destination is not initialized.
-
Action: Verify that the destination is properly initialized.
-
Cause: The LOB used for the destination is empty.
-
Action: Verify that the destination is properly initialized and data has been imported into it.
-
Cause: The raster origin specified is not supported.
-
Action: Verify that the origin specified is supported.
-
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.
-
Cause: The source does not exist or cannot be accessed.
-
Action: Verify that the source specification is correct and accessible.
-
Cause: The specified operation is not supported on the particular geoimage type.
-
Action: Verify that the operation is supported.
-
Cause: The model specified for the definition of the coordinate system is not supported.
-
Action: Verify that the model value is correct.
-
Cause: The geometry used to crop a GeoImage is NULL.
-
Action: Verify that the geometry used for the crop operation is not NULL.
-
Cause: The parameters used in the scale operation are invalid.
-
Action: Verify that the scaling parameters are greater than zero.
-
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.
-
Cause: The format specified for conversion is invalid or unsupported.
-
Action: Verify that the conversion format specified is valid.
-
Cause: The tag or key is invalid.
-
Action: Verify that the format version is supported or the format is valid.
-
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).
-
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.
-
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.
-
Cause: The window specified as destination in the command is not valid.
-
Action: Verify that the window definition is correct.
-
Cause: CREATE INDEX statement contained more than one LOCAL clause.
-
Action: Specify LOCAL option at most once.
-
Cause: CREATE INDEX statement contained a GLOBAL clause and a LOCAL clause.
-
Action: Specify LOCAL or GLOBAL clause, but not both.
-
Cause: CREATE INDEX statement contained more than one GLOBAL clause.
-
Action: Specify GLOBAL option at most once.
-
Cause: CREATE INDEX statement contained a LOCAL clause and a GLOBAL clause.
-
Action: Specify GLOBAL or LOCAL clause, but not both.
-
Cause: Keyword PARTITION missing.
-
Action: Supply missing keyword.
-
Cause: Keyword RANGE missing.
-
Action: Supply missing keyword.
-
Cause: A partition name of the form identifier is expected but not present.
-
Action: Enter an appropriate partition name.
-
Cause: Keyword LESS missing.
-
Action: Supply missing keyword.
-
Cause: Keyword THAN missing.
-
Action: Supply missing keyword.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Definition of a table contained both PARTITION and CLUSTER clauses which is illegal.
-
Action: Remove one of the conflicting clauses.
-
Cause: CREATE TABLE statement contained more than one PARTITION clause.
-
Action: Specify PARTITION option at most once.
-
Cause: Keyword AT or VALUES is missing.
-
Action: Supply missing keyword.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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).
-
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).
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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).
-
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.
-
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.
-
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).
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Partitioning column specified by the user was of type ROWID, which is illegal.
-
Action: Ensure that no partitioning column is of type ROWID.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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_FORMATdoes 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. -
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.
-
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.
-
Cause: NOREVERSE was specified more than once in ALTER INDEX statement.
-
Action: Remove all but one of the NOREVERSE clauses and reissue the statement.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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:
-
Action: Make sure the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command.
-
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.
-
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.
-
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.
-
Cause: User doing exchange does not have full table access due to VPD policies.
-
Action: Grant exempt priviliges to this user.
-
Cause: Keyword SUBPARTITION missing.
-
Action: Supply the missing parameter.
-
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.
-
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.
-
Cause: Both STORE IN and partition_description clauses were specified in a CREATE TABLE|INDEX command.
-
Action: Remove one of offending clauses.
-
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.
-
Cause: Expected either the PARTITION or SUBPARTITION keyword but neither was supplied.
-
Action: Supply the missing keyword.
-
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.
-
Cause: A subpartition name of the form identifier is expected but not present.
-
Action: Enter an appropriate subpartition name.
-
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.
-
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.
-
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).
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Keyword INTO missing.
-
Action: Supply the missing keyword.
-
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.
-
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.
-
Cause: An option other than PCTFREE, PCTUSED, INITRANS, MAXTRANS, STORAGE, was specified in an ALTER TABLE MODIFY SUBPARTITION statement.
-
Action: Specify only legal options.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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).
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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).
-
Cause: One of the following:
-
Action: Remove all but one of the ENABLE ROW MOVEMENT or DISABLE ROW MOVEMENT clauses and then reissue the command.
-
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.
-
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.
-
Cause: An option other than UNUSABLE, ALLOCATE EXTENT, DEALLOCATE UNUSED was specified in an ALTER INDEX MODIFY SUBPARTITION statement.
-
Action: Specify only legal options.
-
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.
-
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.
-
Cause: Subpartition not found for the object.
-
Action: Retry with correct subpartition name.
-
Cause: Only ALLOCATE EXTENT and DEALLOCATE UNUSED may be specified in ALTER TABLE MODIFY PARTITION for a hash partition.
-
Action: Specify only legal options.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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).
-
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.
-
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.
-
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.
-
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.
-
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).
-
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).
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: User attempt to merge two partitions that are not adjacent to each other which is illegal.
-
Action: Specify two partitions that are adjacent.
-
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.
-
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.
-
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.
-
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.
-
Cause: The two tables specified in the ALTER TABLE EXCHANGE SUBPARTITION 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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to rebuild a partition of a composite range partitioned index which is illegal.
-
Action: No action required.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A list value cannot be specified more that once.
-
Action: Remove one of the specifications of the value.
-
Cause: A list value cannot be specified more that once.
-
Action: Remove one of the specifications of the value.
-
Cause: Partition list contains more than 65535 list values.
-
Action: Reduce the number of values to not exceed 65535 values.
-
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.
-
Cause: Partitioned object contains more than 65535 list values.
-
Action: Reduce number of values to less than 65535.
-
Cause: VALUES LESS THAN or AT clause can be used only with range partitioned tables.
-
Action: Use VALUES (<value list>) clause with list partitioned tables.
-
Cause: VALUES (<value list>) clause can be used only with list partitioned tables.
-
Action: Use VALUES LESS THAN clause with range partitioned tables.
-
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.
-
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.
-
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.
-
Cause: The same partition name was specified twice for the merge operation.
-
Action: Re-submit operation with 2 distinct partition names.
-
Cause: ALTER TABLE ADD|DROP VALUES can only be performed on list partitioned objects.
-
Action: reissue the command against a list partitoned object.
-
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.
-
Cause: A partition description follows the one describing the default partition.
-
Action: Ensure that the DEFAULT partition is the last partition description.
-
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.
-
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.
-
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.
-
Cause: A partition already exists with DEFAULT value.
-
Cause: An ADD PARTITION operation cannot be executed when a partition with DEFAULT values exists.
-
Action: Issue a SPLIT of the DEFAULT partition instead.
-
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.
-
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.
-
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.
-
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.
-
Cause: Cursor invalidation was detected after acquiring a partition lock during an INSERT, UPDATE, DELETE statement.
-
Action: No action required.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to create an IOT, specify physical attributes, specify partition or parallel clause.
-
Action: No action required.
-
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.
-
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.
-
Cause: An attempt was made to reference temporary table in a referential integrity constraint. This is not supported.
-
Action: Use triggers.
-
Cause: An attempt was made to create a referential integrity constraint on a temporary table. This is not supported.
-
Action: Use triggers.
-
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.
-
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.
-
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.
-
Cause: Keyword GLOBAL is missing while creating temporary table.
-
Action: Supply the missing keyword.
-
Cause:
COMPRESSwas specified more than once,NOCOMPRESSwas specified more than once, or bothCOMPRESSandNOCOMPRESSwere specified. -
Action: Specify each desired
COMPRESSorNOCOMPRESSclause option only once. -
Cause: Incorrect syntax specified.
-
Action: Retry the command.
-
Cause: Table or index is not partitioned. Invalid syntax.
-
Action: Retry the command with correct syntax.
-
Cause: More than one partition name has been specified for analyze.
-
Action: Specify one partition name.
-
Cause: A partition/subpartition number or bind variable has been used.
-
Action: Specify a valid partition/subpartition name.
-
Cause: Incorrect syntax specified.
-
Action: Retry the command.
-
Cause: Incorrect syntax specified.
-
Action: Retry the command.
-
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.
-
Cause: The specified table either does not exist or user does not have the proper privileges.
-
Action: Specify the correct table to use.
-
Cause: The specified table does not have the proper field definitions.
-
Action: Specify the correct table to use. See UTLVALID.SQL for more information.
-
Cause: The VALIDATE INTO has been specified for a non-partitioned table or cluster or index.
-
Action: Use the syntax correctly.
-
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.
-
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.
-
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.
-
Cause: Incorrect syntax specified.
-
Action: Retry the command.
-
Cause: More than one subpartition name has been specified for analyze.
-
Action: Specify one subpartition name.
-
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.
-
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.
-
Cause: A table partition contains rows for the values being dropped.
-
Action: DELETE all rows for the values being dropped and reissue statement.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Cannot specify these clauses while specifying a template.
-
Action: Correct the subpartition template clause.
-
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.
-
Cause: This syntax is valid only if subpartitioning dimension is hash.
-
Cause: Once a subpartition template has been specified during
CREATE TABLE, it is illegal to specifySUBPARTITIONSorSTORE INanywhere else. -
Action: Remove either
SUBPARTITIONSorSTORE IN, or remove theSUBPARTITION TEMPLATEclause. -
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A subpartition name cannot be duplicated within the template.
-
Action: Rename one of the subpartitions.
-
Cause: Two lob segments of the same column were given the same name in the template.
-
Action: Rename one of the lob segments.
-
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.
-
Cause: A list value cannot be specified more than once.
-
Action: Remove one of the specifications of the value.
-
Cause: A list value cannot be specified more than once.
-
Action: Remove one of the specifications of the value.
-
Cause: A subpartition maintenance operation such as
ALTER TABLE MODIFY SUBPARTITION ADD | DROP VALUESorALTER TABLE DROP | SPLIT | MERGE SUBPARTITIONcan only be performed on List subpartitioned objects. -
Action: Re-issue the command against a List subpartitioned object.
-
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.
-
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.
-
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.
-
Cause: A subpartition already exists with DEFAULT value.
-
Action: Remove the DEFAULT value from the specified list.
-
Cause: An ADD SUBPARTITION operation cannot be executed when a subpartition with DEFAULT values exists.
-
Action: Issue a SPLIT of the DEFAULT subpartition instead.
-
Cause: One of the list values in the
ADD SUBPARTITIONorADD VALUESstatement already exists in another subpartition. -
Action: Remove the duplicate value from the statement and try again.
-
Cause: One of the list values in the
SPLIT PARTITIONorDROP VALUESstatement does not exist in the subpartition. -
Action: Remove the value from the statement and try again.
-
Cause: A subpartition description follows the one describing the default subpartition.
-
Action: Ensure that the DEFAULT subpartition is the last subpartition description.
-
Cause: Table subpartition contains rows for the values being dropped.
-
Action: DELETE all rows for the values being dropped and re-issue the statement.
-
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.
-
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.
-
Cause: An operation such as
ALTER TABLE SPLIT | ADD SUBPARTITIONspecified bounds that were inconsistent with List subpartitioning method. -
Action: Specify VALUES/subpartition descriptions correctly for SPLIT/ADD of List subpartitions.
-
Cause: A drop subpartition command is being executed when there is only one subpartition in the partition.
-
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.
-
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.
-
Cause: An
ALTER TABLE ADD SUBPARTITIONstatement was issued with aPARALLELclause for a List subpartition of a Range/List partitioned object. This is not allowed. -
Action: Remove the
PARALLELclause. -
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A STORE IN clause was specified for Range List partitioned object.
-
Action: Re-issue the command after removing the STORE IN clause.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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).
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The
LOG_ARCHIVE_DUPLEX_DESTparameter 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.
-
Cause: One of the following events caused an incompatibility:
- The
LOG_ARCHIVE_DESTorLOG_ARCHIVE_DUPLEX_DESTinitialization parameter was in use when aLOG_ARCHIVE_DEST_nparameter (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_nparameter was encountered while fetching initialization parameters. - A
LOG_ARCHIVE_DEST_nparameter was in use when anALTER SYSTEMstatement was used to define a value for either theLOG_ARCHIVE_DESTorLOG_ARCHIVE_DUPLEX_DESTparameter.
- The
-
Action: Eliminate any incompatible parameter definitions.
-
Cause: One of the following events caused an incompatibility:
- The
LOG_ARCHIVE_DESTorLOG_ARCHIVE_DUPLEX_DESTinitialization parameter was in use when the specifiedLOG_ARCHIVE_DEST_nparameter (n= 1, 2, ... 10) was encountered while fetching initialization parameters. - The
LOG_ARCHIVE_DESTorLOG_ARCHIVE_DUPLEX_DESTinitialization parameter was in use when an attempt was made to use anALTER SYSTEMorALTER SESSIONstatement to define a value for the specifiedLOG_ARCHIVE_DEST_nparameter. - An ALTER SYSTEM ARCHIVE LOG START TO statement was in effect when the specified
LOG_ARCHIVE_DEST_nparameter 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_nparameter.
- The
-
Action: Eliminate any incompatible parameter definitions.
-
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_DESTparameter value. -
Action: Either adjust the settings of the log archive destination parameters, or lower the value of
LOG_ARCHIVE_MIN_SUCCEED_DEST. -
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_nparameters. -
Cause: An attempt was made to change the
LOG_ARCHIVE_DESTinitialization parameter to NULL when theLOG_ARCHIVE_DUPLEX_DESTinitialization parameter is non-NULL. -
Action: Either set the
LOG_ARCHIVE_DESTinitialization parameter to a non-NULL value, or set theLOG_ARCHIVE_DUPLEX_DESTinitialization parameter to a NULL value. -
Cause: An attempt to change the first specified
LOG_ARCHIVE_DEST_nparameter (n= 1, 2, ... 10) produced a destination that duplicates the session destination value of the second specifiedLOG_ARCHIVE_DEST_nparameter. 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_nparameter. -
Cause: The value for the indicated
LOG_ARCHIVE_DEST_nparameter (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_nparameter. -
Cause: The value for the specified
LOG_ARCHIVE_DEST_nparameter (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_nparameter. -
Cause: The value for the specified
LOG_ARCHIVE_DEST_nparameter (n= 1, 2, ... 10) contained aREOPENattribute with an invalid numeric value. The valid range is 0 - 65535. -
Action: Correct the value for the indicated
LOG_ARCHIVE_DEST_nparameter. -
Cause: The value for the indicated
LOG_ARCHIVE_DEST_nparameter (n= 1, 2, ... 10) failed to include a destination option. A destination option is specified using either theLOCATIONorSERVICEattribute. -
Action: Correct the value for the indicated
LOG_ARCHIVE_DEST_nparameter. -
Cause: With automatic archiving enabled, an attempt was made to change the indicated
LOG_ARCHIVE_DEST_nor aLOG_ARCHIVE_DEST_STATE_nparameter (n= 1, 2, ... 10) to a value that reduces the number of archive log destinations to less than the specifiedLOG_ARCHIVE_MIN_SUCCEED_DESTvalue. -
Action: Either select different options for the
LOG_ARCHIVE_DEST_norLOG_ARCHIVE_DEST_STATE_nparameters, or reduce the value for theLOG_ARCHIVE_MIN_SUCCEED_DESTparameter. -
Cause: An attempt was made to change the
LOG_ARCHIVE_MIN_SUCCEED_DESTparameter when there are no archive log destinations. -
Action: Define one or more log archive destinations using the
LOG_ARCHIVE_DEST,LOG_ARCHIVE_DUPLEX_DEST, orLOG_ARCHIVE_DEST_nparameters (n= 1, 2, ... 10). Then, change the value of theLOG_ARCHIVE_MIN_SUCCEED_DESTparameter. -
Cause: The following event caused an incompatibility: Parameter
LOG_ARCHIVE_DESTorLOG_ARCHIVE_DUPLEX_DESTwas in use when an attempt was made to change theLOG_ARCHIVE_MIN_SUCCEED_DESTparameter with anALTER SESSIONstatement. -
Action: Replace any
LOG_ARCHIVE_DESTandLOG_ARCHIVE_DUPLEX_DESTparameters withLOG_ARCHIVE_DEST_n(n= 1, 2, ... 10) parameters. -
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.
-
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.
-
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.
-
Cause: Use of the FROM 'location' parameter is not allowed when MANAGED recovery has been specified.
-
Action: Correct the syntax and retry the command.
-
Cause: The indicated keyword is required but was not specified.
-
Action: Correct the syntax and retry the command.
-
Cause: A mode other than IMMEDIATE follows the CANCEL keyword in RECOVER MANAGED STANDBY DATABASE statement.
-
Action: Specify either nothing or IMMEDIATE following CANCEL.
-
Cause: The managed standby database recovery operation has been canceled per user request.
-
Action: No action is required.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The standby database managed recovery operation has been canceled per user request or operation timeout.
-
Action: More specific messages will accompany this message.
-
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.
-
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.
-
Cause: The archive log destination is dependent upon another destination, which has failed. Therefore, this destination also fails.
-
Action: No action required.
-
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.
-
Cause: Causes an I/O error to be signalled during the writing of an archival operation.
-
Action: No action required.
-
Cause: I/O error returned for a simulated archival failure during an archival operation.
-
Action: No action required.
-
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.
-
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_nparameter. -
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Archiving not allowed of an empty or invalid log file.
-
Action: No action required.
-
Cause: The current log file cannot be archived using its file name.
-
Action: No action required.
-
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.
-
Cause: Archiving not allowed of current log file.
-
Action: Check the alert log and archive trace files for additional information.
-
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_ENABLEparameter totrueand restart this 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_ENABLEparameter tofalseand restart this instance. -
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
LOCATIONkeyword or defer the associated archive log destination. Or, if possible, set the standbyREMOTE_ARCHIVE_ENABLEparameter totrueand restart the standby database instance before further REDO log file archivals occur. -
Cause: An archive log destination parameter has specified a remote destination with the
SERVICEkeyword. 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
LOCATIONkeyword or (if appropriate) set theREMOTE_ARCHIVE_ENABLEparameter totrueand restart the database instance before further REDO log file archivals occur. -
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.
-
Cause: The activation identifier of the indicated redo log file does not match the activation identifier of the database.
-
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.
-
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_nparameter. -
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.
-
Cause: No standby database archive log destinations were specified.
-
Action: Specify a standby archive log destination in the initialization parameter file.
-
Cause: Online log file archiving is disabled.
-
Action: Enable log file archiving.
-
Cause: There are no active ARCH processes.
-
Action: It is required that at least one ARCH process be active.
-
Cause: A standby database destination was specified that is not accessed by another instance.
-
Action: All database instances must access the same standby databases.
-
Cause: A standby database destination was specified that is not accessed by another instance.
-
Action: All database instances must access the same standby databases.
-
Cause: The database is not in ARCHIVELOG mode.
-
Action: Place the database in ARCHIVELOG mode.
-
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.
-
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.
-
Cause: Logical standby apply engine was started with fewer processes available than needed.
-
Action: Increase the values of the initialization parameters
PROCESSESandPARALLEL_MAX_SERVERS, or theMAX_SLAVESparameter seen in theDBA_LOGSTDBY_PARAMETERSview. -
Cause: Logical standby apply engine was started but it found inconsistencies in its metadata.
-
Action: Look in the trace file for more information.
-
Cause: Logical standby apply engine was started without creating a LogMiner session.
-
Action: Create a LogMiner session and restart the apply engine.
-
Cause: A logical standby apply engine was running when another was created.
-
Action: Shut down the previous apply engine before starting a new one.
-
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.
-
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.
-
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.
-
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_LOGfixed view to verify the archive log information. -
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.
-
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 SYSTEMstatement to remove one of the dependency attributes. -
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 SYSTEMstatement to remove one of the dependency attributes. -
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 SYSTEMstatement to change the parent archive log to specify the LGWR process. -
Cause: The database was shut down while an online log file archival was active.
-
Action: No action required. The ARCH process is terminated.
-
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.
-
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.
-
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.
-
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 INITIALstatement. See the Oracle9i SQL Reference for the statement syntax. -
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 LOGFILEstatement to register the database is recommended. Alternatively, you can provide a starting SCN value with this statement. -
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.
-
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 APPLYstatement, then re-enter or re-specify the operation. -
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.
-
Cause: A Logical Standby apply operation is already running.
-
Action: no action required.
-
Cause: On the primary system, the log stream has been ended by the
ALTER DATABASE PREPARE TO SWITCHOVER TO LOGICAL STANDBYstatement. -
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;
-
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;
-
Cause: Log data from previous primary could not be completely applied.
-
Action: Check
DBA_LOGSTDBY_EVENTSfor failures and take corrective action. Then, re-issue command. -
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_EVENTSand theDBA_LOGSTDBY_SKIPviews. -
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: DML to tables in the
SYSschema 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_EVENTStable 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, callDBMS_LOGSTDBY.SKIP_TRANSACTIONwith the associated transaction id, and resume apply. -
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;
-
Cause: An error occurred during a Terminal Recovery of the standby.
-
Action: Check the standby alert log additional information.
-
Cause: An error occurred during activation of the standby database following a Terminal Recovery.
-
Action: Check the standby alert log additional information.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to cancel a managed recovery session but no managed recovery session was active.
-
Action: No action 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.
-
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.
-
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.
-
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 DATABASEstatement. To activate the standby without recovering the online logs, issue the following command:ALTER DATABASE ACTIVATE STANDBY DATABASE SKIP STANDBY LOGFILE;
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Use of the indicated attribute is illegal in the given context.
-
Action: Make the appropriate changes and re-issue the statement.
-
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.
-
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;
-
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.
-
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.
-
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
TYPEcolumn of theV$LOGfixed view. -
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.
-
Cause: The LGWR network server could not attach to remote host.
-
Action: The alert log contains more problem-specific information.
-
Cause: The LGWR network server could not detach from remote host.
-
Action: The alert log contains more problem-specific information.
-
Cause: The LGWR lost its connection to the network server.
-
Action: The alert log contains more problem-specific information.
-
Cause: The LGWR network server could not communicate with the remote host.
-
Action: The alert log contains more problem-specific information.
-
Cause: The LGWR network server could not switch to non-blocking mode.
-
Action: The alert log contains more problem-specific information.
-
Cause: The LGWR network server could not switch to blocking mode.
-
Action: The alert log contains more problem-specific information.
-
Cause: The LGWR network server could not switch to blocking mode.
-
Action: The alert log contains more problem-specific information.
-
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.
-
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 SKIPstatement to ignore the standby redo log files. -
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The logical standby dictionary build process terminated abnormally.
-
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.
-
Cause: The logical standby coordinator process terminated abnormally.
-
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.
-
Cause: Log apply services encountered a record in the archived redo log that could not be interpreted.
-
Action:
- Use
DBMS_LOGSTDBY.INSTANTIATE_TABLEto 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_scncolumn in theDBA_LOGSTDBY_EVENTSview to determine which log file contains the unsupported record. - Provide the log file to Oracle Support Services.
- Use
-
Cause: Logical standby apply engine was started with more processes requested than are available.
-
Action: Adjust the values of the initialization parameters
PROCESSESandPARALLEL_MAX_SERVERS, or theMAX_SLAVESparameter seen in theDBA_LOGSTDBY_PARAMETERSview. -
Cause: stop_on_ddl callout specified and DDL was encountered.
-
Action: Either disable stop_on_ddl callout or remove DDL.
-
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. -
Cause: The Data Guard broker operation failed.
-
Action: See other messages for details.
-
Cause: The Data Guard broker operation succeeded with warnings.
-
Action: See other messages for details.
-
Cause: Number of sites in the Data Guard configuration has exceeded the limit.
-
Action: Delete unused sites.
-
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.
-
Cause: The request contained an invalid site ID.
-
Action: Make the request again with a valid site ID.
-
Cause: Process exceeded private or shared memory limits.
-
Action: Check for memory leaks, increase system parameters, and restart.
-
Cause: The specified request identifier was not recognized by the Data Guard broker.
-
Action: Re-issue the request using a valid request identifier.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: 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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: Total number of resource properties exceeded the limit.
-
Cause: A command or option is not supported in this release.
-
Action: Contact Oracle Support Services.
-
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_STARTtotrueand 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. -
Cause: The Data Guard broker was unable to allocate memory for a request.
-
Action: Increase the size of your SGA.
-
Cause: The Data Guard broker was unable to allocate a heap within the SGA.
-
Action: Increase SGA memory.
-
Cause: No space in PGA to allocate heap.
-
Action: Increase process virtual memory.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: A NULL buffer or a length of zero was specified.
-
Action: Correct command parameters and retry.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The Data Guard configuration does not exist.
-
Action: Create a DRC prior to issuing other requests.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The Data Guard broker returns this status when:
-
Action: Wait until the operation is complete and then re-issue the request.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The Data Guard broker did not recognize the specified property or state name.
-
Action: Verify command parameters and re-issue the request.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The site specified in the request is not enabled.
-
Action: Select an enabled site and re-issue the request.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The Data Guard broker was unable to accept the request.
-
Action: Contact Oracle Support Services.
-
Cause: The Data Guard broker was unable to return the result of a previous request.
-
Action: Contact Oracle Support Services.
-
Cause: The piece of the request to return was not specified or is invalid.
-
Action: Specify the piece of the response starting from 1.
-
Cause: The Data Guard broker was unable to delete the given request.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: A request contains an invalid or NULL string value.
-
Action: Correct command parameters and retry.
-
Cause: A string property value was truncated due to insufficient buffer size.
-
Action: Specify a larger recieve buffer.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: An operation was attempted on a resource that is currently not active (off path).
-
Action: Verify that the resource is active.
-
Cause: An attempt was made to create a duplicate resource.
-
Action: Check the resource to be added and be sure there are no duplicates.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: There was an error at the given token.
-
Action: Correct the errors and resubmit the request.
-
Cause: There was an error at the given token.
-
Action: Correct the errors and resubmit the request.
-
Cause: There was an error at the given token.
-
Action: Correct the errors and resubmit the request.
-
Cause: There was an error at the given token.
-
Action: Correct the errors and resubmit the request.
-
Cause: There was an error at the given token.
-
Action: Correct the errors and resubmit the request.
-
Cause: There was an error at the given token.
-
Action: Correct the errors and resubmit the request.
-
Cause: The submitted XML document is not supported.
-
Action: Correct the errors and resubmit the request.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The requested operation requires the Data Guard configuration to be enabled.
-
Action: Enable the Data Guard configuration and re-issue the request.
-
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.
-
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. -
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. -
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.
-
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.
-
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.
-
Cause: A failure was encountered while the broker was updating the Data Guard broker configuration file on permanent storage.
-
Action: Contact Oracle Support Services.
-
Cause: The Data Guard broker detected errors while loading the configuration file.
-
Action: Contact Oracle Support Services.
-
Cause: A failure was encountered while the broker was reading the configuration file on permanent storage.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: The 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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: See trace file.
-
Action: Contact Oracle Support Services.
-
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:
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: There was an error at the given token.
-
Action: Correct the errors and resubmit the request.
-
Cause: There was an error at the given token.
-
Action: Correct the errors and resubmit the request.
-
Cause: There was an error in the XML request document.
-
Action: Correct the errors and resubmit the request.
-
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.
-
Cause: The specified NetSlave process did not terminate at the request of the Data Guard broker.
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The Data Guard broker has detected two or more primaries in the configuration and cannot continue.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The named property does not exist.
-
Action: Specify a valid property name and re-issue the request.
-
Cause: The Data Guard broker detected a failure on one or more sites.
-
Action: Locate the sites with a failure status and correct it.
-
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.
-
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.
-
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.
-
Cause: The Data Guard broker aborted an operation at the user's request.
-
Action: No action required.
-
Cause: The string value for the named attribute is too long.
-
Action: Use a shorter string.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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_STARTinitialization parameter tofalse. After the broker has been shut down on the standby site, locate the Data Guard broker configuration files from the standby site'sDG_BROKER_CONFIG_FILE[1 | 2]parameter values and delete them. -
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.
-
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.
-
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.
-
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.
-
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.
-
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:
-
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_NAMEandINSTANCE_NAMEcolumns ofV$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.
- Confirm that the host and SID names you specified when you created the site exactly match the values in the
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: No resource guard is available to service the request.
-
Action: Contact Oracle Support Services.
-
Cause: The value specified in the request is invalid.
-
Action: Check value and re-issue the request.
-
Cause: The state name specified is invalid for the resource.
-
Action: Check the state name and re-issue 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.
-
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.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: An attempt to clear the
LOG_ARCHIVE_DESTinitialization parameter failed. -
Action: Contact Oracle Support Services.
-
Cause: An attempt to clear the
LOG_ARCHIVE_DUPLEX_DESTinitialization parameter failed. -
Action: Contact Oracle Support Services.
-
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.
-
Cause: A SQL statement to query
V$ARCHIVE_DESTfailed. -
Action: Test and clear the problem using SQL*Plus.
-
Cause: All
LOG_ARCHIVE_DEST_nparameters have been defined. -
Action: Set some of the
LOG_ARCHIVE_DEST_nparameters to an empty string. -
Cause: An attempt of setting some of the
LOG_ARCHIVE_DEST_nparameters failed. -
Action: Check the Data Guard console log and database alert logs for further details.
-
Cause: An attempt of setting some of the
LOG_ARCHIVE_DEST_STATE_nparameters failed. -
Action: Check the Data Guard console log and database alert logs for further details.
-
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.
-
Cause: The intended state of the resource has been set to offline.
-
Action: If resource is managed, change intended state to online.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
Cause: This is an internal error.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
Cause: Logical standby package may not be installed.
-
Action: Install logical standby packages and re-issue the request.
-
Cause: Logical standby package may not be installed.
-
Action: Install logical standby packages and re-issue the request.
-
Cause: Logical standby package may not be installed.
-
Action: Install logical standby packages and re-issue the request.
-
Cause: Logical standby package may not be installed.
-
Action: Install logical standby packages and re-issue the request.
-
Cause: Logical standby package may not be installed.
-
Action: Install logical standby packages and re-issue the request.
-
Cause: Logical standby package may not be installed.
-
Action: Install logical standby packages and re-issue the request.
-
Cause: Logical standby package may not be installed.
-
Action: Install logical standby packages and re-issue the request.
-
Cause: Resource guard could not set the standby log archive destination parameter.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not set the log archive format parameter.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not set the database file name convert parameter.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not set log file name convert parameter.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not set log archive trace parameter.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not set the control files parameter.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not set lock name trace parameter.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not set FAL client parameter.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not set FAL server.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not dismount database.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not mount database.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not turn on the logical standby guard.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not open database.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not prepare to switch to logical primary.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not activate logical primary.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not prepare to switch to primary.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not mount standby.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not open standby database.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not activate standby.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not dismount standby.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard could not open standby read-only.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard failed to get property.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard failed to verify property.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard failed to start logical apply engine with an initial SCN.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard failed to start logical apply engine.
-
Action: Check the Data Guard console log for further details.
-
Cause: Resource guard failed to stop logical apply engine correctly.
-
Action: Check the Data Guard console log for further details.
-
Cause: Database is not in the intended state.
-
Action: Determine the reason for invalid state, and re-issue get status request.
-
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.
-
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.
-
Cause: Physical apply service is online when it should be offline.
-
Action: If necessary, stop the physical apply service.
-
Cause: Physical apply service is offline when it should be online.
-
Action: If necessary, start the physical apply service.
-
Cause: Logical apply service is online when it should be offline.
-
Action: If necessary, stop the logical apply service.
-
Cause: Logical apply service is offline when it should be online.
-
Action: If necessary, start the logical apply service.
-
Cause: There was an error executing dbms_logstdby$apply_set procedure.
-
Action: Check the values for the property, and set configuration property again.
-
Cause: There was an error executing dbms_logstdby$apply_unset procedure.
-
Action: Check the values for the property, and set configuration set property again.
-
Cause: There was an error starting the archival processes.
-
Action: Check the Data Guard console log for further details.
-
Cause: There was an error during switchover of primary and standby databases.
-
Action: Check the Data Guard console log for further details.
-
Cause: There was an error in starting the physical apply service (MRP process).
-
Action: Check the Data Guard console log for further details.
-
Cause: There was an error in stopping the physical apply service (MRP process).
-
Action: Check the Data Guard console log for further details.
-
Cause: The physical apply service terminated prematurely with an error.
-
Action: Check the Data Guard console log and Oracle Alert log for further details.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: Log transport to some site has an unknown status.
-
Action: Check the Data Guard console log and Oracle Alert log for further details.
-
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.
-
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.
-
Cause: Site name provided in property Dependency or Alternate is wrong.
-
Action: Reset property to the correct name of the site.
-
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 ARCHIVELOGstatement. -
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.
-
Cause: This situation occurs when database resource guard attempts to set database configuration property values into the database by issuing
ALTER SYSTEMorALTER DATABASEstatements. Typical causes of this error are: -
Action: Check the Data Guard console log to see which property has the problem and reset the property correctly.
-
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.
-
Cause: An invalid property value was entered.
-
Action: Reset the value to a correct one.
-
Cause: The database may not be mounted, or the query of
V$STANDBY_LOGfailed. -
Action: Bring the database to an online state, or fix the problem during the query of
V$STANDBY_LOG. -
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.
-
Cause: The logical standby database guard is OFF.
-
Action: Issue the
ALTER DATABASE GUARD ALLstatement to turn the guard ON and verify that Data Guard health check error/warning is cleared. -
Cause: Primary database has database guard ON, which is not normal.
-
Action: Issue the
ALTER DATABASE GUARD NONEstatement to turn the guard OFF and verify that Data Guard health check error/warning is cleared. -
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.
-
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.
-
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. -
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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) COLUMNSto add supplemental logging. -
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.
-
Cause: The client could not be initialized.
-
Action: This is an internal error. Contact Oracle Support Services.
-
Cause: The database environment could not be allocated and initialized.
-
Action: This is an internal error. Contact Oracle Support Services.
-
Cause: The database handles could not be allocated.
-
Action: This is an internal error. Contact Oracle Support Services.
-
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.
-
Cause: The server attributes could not be set.
-
Action: check additional error messages.
-
Cause: The given action failed.
-
Action: check additional error messages.
-
Cause: No memory was available for the program.
-
Action: Increase memory and try again.
-
Cause: A required field was missing.
-
Action: Type "help" for syntax and try again.
-
Cause: The given option is not supported.
-
Action: Try again using the proper command line syntax.
-
Cause: A fatal error was encountered.
-
Action: See additional error messages and contact Oracle Support Services.
-
Cause: Commands cannot be issued to the server.
-
Action: See additional error messages and contact Oracle Support Services.
-
Cause: An action succeeded with warnings.
-
Action: See error message and take appropriate action.
-
Cause: An unknown command was issued.
-
Action: Try again using a valid command.
-
Cause: The connect string for the database is missing.
-
Action: Try the command again with a valid connect string.
-
Cause: The site name is missing.
-
Action: Try the command again using correct syntax.
-
Cause: The XML document argument was missing.
-
Action: Try the command again using correct syntax.
-
Cause: The named site could not be started in the primary role.
-
Action: See additional messages.
-
Cause: The named site was started as the new primary site.
-
Action: No action is required.
-
Cause: The named site could not be started in the standby role.
-
Action: See additional messages..
-
Cause: The named site was started as the new primary site.
-
Action: No action required.
-
Cause: The failover operation succeeded.
-
Action: No action required.
-
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.
-
Cause: The named site could not be found.
-
Action: Try the command again using a valid site.
-
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.
-
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.
-
Cause: The named resource was not found.
-
Action: Try the command again using a valid resource.
-
Cause: The named object could not be retrieved for editing.
-
Action: Contact Oracle Support Services.
-
Cause: The manager information could not be retrieved for a generic resource.
-
Action: Contact Oracle Support Services.
-
Cause: The configuration could not be described.
-
Action: The framework could not be contacted. Check to see that the DMON process is running.
-
Cause: The named site or resource does not exist.
-
Action: Try the command again using a valid site or resource.
-
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.
-
Cause: The template could not be found.
-
Action: See additional error messages.
-
Cause: The template name was omitted from the command.
-
Action: Try the command again using a valid template name.
-
Cause: The named template could not be found.
-
Action: Try the command again using a valid template name.
-
Cause: The document could not be converted.
-
Action: Contact Oracle Support Services.
-
Cause: No answer came from the framework.
-
Action: The framework is not available. Check to see that the DMON process exists.
-
Cause: The status could not be retrieved.
-
Action: The framework is not available. Check to see that the DMON process exists.
-
Cause: The named resource exists on more than one site.
-
Action: The request must be more specific. Issue the command again using the
ON SITEclause. -
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.
-
Cause: An error returned by ODM library
-
Action: Look at error message and take appropriate action or contact Oracle Support Services for further assistance.
-
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.
-
Cause: file creation failed due to either insufficient OS permission or the file already exists
-
Action: check additional error messages
-
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
-
Cause: The file thats being deleted is still in use or the process has insufficient permission to delete file.
-
Action: check additional error messages
-
Cause: There is insufficient space left on the device or the process has insufficient permission to resize file.
-
Action: check additional error messages
-
Cause: The i/o request is marked with error because the i/o error simulation event is turned on.
-
Action: none
-
Cause: i/o's are done in multiple of logical block size
-
Action: Check additional error messages
-
Cause: i/o request buffer should be alligned, check additional information for buffer ptr value
-
Action: Contact Oracle Support Services.
-
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.
-
Cause: The i/o request points to a block beyond End Of File
-
Action: check additional error messages and contact Oracle Support Services.
-
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.
-
Cause: An attempt to write to a file which has gone offline/unidentified.
-
Action: Check for other errno in the stack.
-
Cause: The parser detected a missing or invalid outline name.
-
Action: reissue the command, specifying a valid outline name.
-
Cause: The parser detected that no clause was specified on the command.
-
Action: reissue the command, specifying a valid ALTER OUTLINE clause.
-
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.
-
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.
-
Cause: An outline already exists, either with the specified name, or for the specified SQL text.
-
Action: Try again with another name.
-
Cause: Create any outline privilege is required for the attempted operation.
-
Action: Make sure you have create any outline privilege and retry the 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.
-
Cause: Alter any outline privilege is required for the attempted operation.
-
Action: Make sure you have alter any outline privilege and retry the operation.
-
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.
-
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.
-
Cause: User failed to specify the CATEGORY keyword.
-
Action: reissue the command with the CATEGORY keyword included.
-
Cause: User imported an 8i outline into a 9i database without updating signatures.
-
Action: Execute dbms_outln.update_signatures.
-
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
-
Cause: An invalid storage option was specified for the XMLType.
-
Action: Supply a valid storage option.
-
Cause: A XML schema URL must be specified in the storage option.
-
Action: Specify a URL for the XMLSchema.
-
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.
-
Cause: A duplicate storage option for the XMLType column was specified
-
Action: Specify a single storage option for an XMLType column
-
Cause: A duplicate storage option for the XMLType column was specified
-
Action: Specify a single storage option for an XMLType column
-
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
-
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.
-
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.
-
Cause: The XMLSchema keyword is missing
-
Action: Specify the XMLSchema URL and element name.
-
Cause: XML fragments got from extractNode cannot be inserted into the database.
-
Action: Convert the fragment into a proper XML document before insertion.
-
Cause: The string result asked for is too big to return back
-
Action: Get the result as a lob instead
-
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.
-
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
-
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.
-
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.
-
Cause: Attribute values can only be simple scalar values.
-
Action: Use only simple datatypes for attribute values.
-
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.
-
Cause: The value of context passed to
GETXMLwas invalid. -
Action: Rewrite the query so that the value of context passed to
GETXMLis valid. -
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.
-
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.
-
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.
-
Cause: Given XPath points to more than one node.
-
Action: Rewrite the query so that exactly one node is returned.
-
Cause: Given XPath does not point to a leaf node.
-
Action: Rewrite the query so that a leaf node is returned.
-
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().
-
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.
-
Cause: The method can be invoked on only schema based xmltype objects.
-
Action: Don't invoke the method for non schema based xmltype objects.
-
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.
-
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
-
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.
-
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.
-
Cause: All input arguments must be valid columns
-
Action: Specify a valid list of columns
-
Cause: The particular datatype is not supported in the XMLGEN operator
-
Action: Specify only supported datatypes as arguments to the XMLGEN operator
-
Cause: An error occurred when processing the XML function
-
Action: Check the given error message and fix the appropriate problem
-
Cause: An error occurred when processing the DBMS_XMLGEN functions
-
Action: Check the given error message and fix the appropriate problem
-
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.
-
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.
-
Cause: The queryString argument passed to
DBMS_XMLGEN.newContextwas not a valid query or REF CURSOR. -
Action: Rewrite the query so that the queryString argument is a valid query or REF CURSOR.
-
Cause: The scalar parameter to XMLELEMENT has been qualified with an alias.
-
Action: Remove the
ASclause of the scalar element. -
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
ASclause. -
Cause: An invalid or unsupported formatting argument was supplied.
-
Action: Change the formatting argument to legal supported values.
-
Cause: An error occurred when processing the URL
-
Action: Check the given error message and fix the appropriate problem
-
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
-
Cause: A HTTP connection could not be opened to the host
-
Action: Specify a valid host name and port to connect to
-
Cause: An error occurred while reading from the HTTP host
-
Action: Specify a valid host name and port to read from
-
Cause: The URL must be a valid URL string
-
Action: Specify a valid url string
-
Cause: The type required for the CREATE_DBURI operator has not been installed correctly.
-
Action: Read the installation notes to install the type correctly.
-
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.
-
Cause: The argument to the CREATE_DBURI operator can only be a column.
-
Action: Specify a valid column name for the operator
-
Cause: The flags argument given to the DBURI operator is invalid
-
Action: Specify a valid flag value (TEXT) for the 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.
-
Cause: An invalid format type object was specified for the XML function
-
Action: Specify a valid format type object
-
Cause: The XML being generated does not have an enclosing root element.
-
Action: The generated XML must have a root element.
ORA-12700 invalid NLS parameter value (string)
ORA-12701 CREATE DATABASE character set is not known
ORA-12702 invalid NLS parameter string used in SQL function
ORA-12703 this character set conversion is not supported
ORA-12704 character set mismatch
ORA-12705 invalid or unknown NLS parameter value specified
ORA-12706 this CREATE DATABASE character set is not allowed
ORA-12707 error while getting create database NLS parameter string
ORA-12708 error while loading create database NLS parameter string
ORA-12709 error while loading create database character set
ORA-12710 CREATE CONTROLFILE character set is not known
ORA-12711 this CREATE CONTROLFILE character set is not allowed
ORA-12712 new character set must be a superset of old character set
ORA-12713 Character data loss in NCHAR/CHAR conversion
ORA-12714 invalid national character set specified
ORA-12715 invalid character set specified
ORA-12716 Cannot ALTER DATABASE CHARACTER SET when CLOB data exists
ORA-12717 Cannot ALTER DATABASE NATIONAL CHARACTER SET when NCLOB data exists
ORA-12718 operation requires connection as SYS
ORA-12719 operation requires database is in RESTRICTED mode
ORA-12720 operation requires database is in EXCLUSIVE mode
ORA-12721 operation cannot execute when other sessions are active
ORA-12800 system appears too busy for parallel query execution
ORA-12801 error signaled in parallel query server string
ORA-12802 parallel query server lost contact with coordinator
ORA-12803 parallel query server lost contact with another server
ORA-12804 parallel query server appears to have died
ORA-12805 parallel query server died unexpectedly
ORA-12806 could not get background process to hold enqueue
ORA-12807 process queue could not receive parallel query message
ORA-12808 cannot set string_INSTANCES greater than number of instances string
ORA-12809 cannot set string_INSTANCES when mounted in exclusive mode
ORA-12810 PARALLEL_MAX_SERVERS must be less than or equal to string
ORA-12811 PARALLEL_MIN_SERVERS must be less than or equal to PARALLEL_MAX_SERVERS, string
ORA-12812 only one PARALLEL or NOPARALLEL clause may be specified
ORA-12813 value for PARALLEL or DEGREE must be greater than 0
ORA-12814 only one CACHE or NOCACHE clause may be specified
ORA-12815 value for INSTANCES must be greater than 0
ORA-12816 parallel create index fastpath operation
ORA-12817 parallel query option must be enabled
ORA-12818 invalid option in PARALLEL clause
ORA-12819 missing options in PARALLEL clause
ORA-12820 invalid value for DEGREE
ORA-12821 invalid value for INSTANCES
ORA-12822 duplicate option in PARALLEL clause
ORA-12823 default degree of parallelism may not be specified here
ORA-12824 INSTANCES DEFAULT may not be specified here
ORA-12825 explicit degree of parallelism must be specified here
ORA-12826 hung parallel query server was killed
ORA-12827 insufficient parallel query slaves available
ORA-12828 Can't start parallel transaction at a remote site
ORA-12829 Deadlock - itls occupied by siblings at block string of file string
ORA-12830 Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
ORA-12831 Must COMMIT or ROLLBACK after executing INSERT with APPEND hint
ORA-12832 Could not allocate slaves on all specified instances
ORA-12833 Coordinator's instance not a member of parallel_instance_group
ORA-12834 Instance group name, 'string', too long, must be less than string characters
ORA-12835 No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
ORA-12838 cannot read/modify an object after modifying it in parallel
ORA-12839 cannot modify an object in parallel after modifying it
ORA-12840 cannot access a remote table after parallel/insert direct load txn
ORA-12841 Cannot alter the session parallel DML state within a transaction
ORA-12842 schema modified during parallel execution
ORA-12843 pdml lock not held properly on the table
ORA-12900 must specify a default temporary tablespace for a locally managed database
ORA-12901 Default temporary tablespace must be of TEMPORARY type
ORA-12902 default temporary tablespace must be SYSTEM or of TEMPORARY type
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
ORA-12911 permanent tablespace cannot be temporary tablespace
ORA-12912 Dictionary managed tablespace specified as temporary tablespace
ORA-12913 Cannot create dictionary managed tablespace
ORA-12914 Cannot migrate tablespace to dictionary managed type
ORA-12915 Cannot alter dictionary managed tablespace to read write
ORA-12920 database is already in force logging mode
ORA-12921 database is not in force logging mode
ORA-12922 concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
ORA-12923 tablespace string is in force logging mode
ORA-12924 tablespace string is already in force logging mode
ORA-12925 tablespace string is not in force logging mode
ORA-12926 FORCE LOGGING option already specified
ORA-12980 checkpoint option not allowed with SET UNUSED
ORA-12981 cannot drop column from an object type table
ORA-12982 cannot drop column from a nested table
ORA-12983 cannot drop all columns in a table
ORA-12984 cannot drop partitioning column
ORA-12985 tablespace 'string' is read only, cannot drop column
ORA-12986 columns in partially dropped state. Submit ALTER TABLE DROP COLUMNS CONTINUE
ORA-12987 cannot combine drop column with other operations
ORA-12988 cannot drop column from table owned by SYS
ORA-12989 invalid value for checkpoint interval
ORA-12990 duplicate option specified
ORA-12991 column is referenced in a multi-column constraint
ORA-12992 cannot drop parent key column
ORA-12993 tablespace 'string' is offline, cannot drop column
ORA-12994 drop column option only allowed once in statement
ORA-12995 no columns in partially dropped state
ORA-12996 cannot drop system-generated virtual column
ORA-12997 cannot drop primary key column from an index-organized table
ORA-13000 dimension number is out of range
ORA-13001 dimensions mismatch error
ORA-13002 specified level is out of range
ORA-13003 the specified range for a dimension is invalid
ORA-13004 the specified buffer size is invalid
ORA-13005 recursive HHCODE function error
ORA-13006 the specified cell number is invalid
ORA-13007 an invalid HEX character was detected
ORA-13008 the specified date format has an invalid component
ORA-13009 the specified date string is invalid
ORA-13010 an invalid number of arguments has been specified
ORA-13011 value is out of range
ORA-13012 an invalid window type was specified
ORA-13013 the specified topology was not INTERIOR or BOUNDARY
ORA-13014 a topology identifier outside the range of 1 to 8 was specified
ORA-13015 the window definition is not valid
ORA-13016 bad partition definition
ORA-13017 unrecognized line partition shape
ORA-13018 bad distance type
ORA-13019 coordinates out of bounds
ORA-13020 coordinate is NULL
ORA-13021 element not continuous
ORA-13022 polygon crosses itself
ORA-13023 interior element interacts with exterior element
ORA-13024 polygon has less than three segments
ORA-13025 polygon does not close
ORA-13026 unknown element type for element string.string.string
ORA-13027 unable to read dimension definition from string
ORA-13028 Invalid Gtype in the SDO_GEOMETRY object
ORA-13029 Invalid SRID in the SDO_GEOMETRY object
ORA-13030 Invalid dimension for the SDO_GEOMETRY object
ORA-13031 Invalid Gtype in the SDO_GEOMETRY object for point object
ORA-13032 Invalid NULL SDO_GEOMETRY object
ORA-13033 Invalid data in the SDO_ELEM_INFO_ARRAY in SDO_GEOMETRY object
ORA-13034 Invalid data in the SDO_ORDINATE_ARRAY in SDO_GEOMETRY object
ORA-13035 Invalid data (arcs in geodetic data) in the SDO_GEOMETRY object
ORA-13036 Operation [string] not supported for Point Data
ORA-13037 SRIDs do not match for the two geometries
ORA-13039 failed to update spatial index for element string.string.string
ORA-13040 failed to subdivide tile
ORA-13041 failed to compare tile with element string.string.string
ORA-13042 invalid SDO_LEVEL and SDO_NUMTILES combination
ORA-13043 failed to read meta data from the layer_SDOLAYER table
ORA-13044 the specified tile size exceeds the maximum resolution
ORA-13045 invalid compatibility flag
ORA-13046 invalid number of arguments
ORA-13047 unable to determine ordinate count from table layer_SDOLAYER
ORA-13048 recursive SQL fetch error
ORA-13049 unable to determine tolerance value from table layer_SDODIM
ORA-13050 unable to construct spatial object
ORA-13051 failed to initialize spatial object
ORA-13052 unsupported geometric type for geometry string.string
ORA-13053 maximum number of geometric elements in argument list exceeded
ORA-13054 recursive SQL parse error
ORA-13055 Oracle object string does not exist in specified table
ORA-13108 spatial table string not found
ORA-13109 spatial table string exists
ORA-13110 spatial table string is not partitioned
ORA-13111 spatial table string has no partition key defined
ORA-13112 invalid count mode string
ORA-13113 Oracle table string does not exist
ORA-13114 tablespace string not found
ORA-13115 tablespace string is already allocated
ORA-13116 tablespace string is not allocated to table string
ORA-13117 partition string not found
ORA-13119 source and target tablespaces are identical
ORA-13121 failed to create child partition
ORA-13122 child partition string not found
ORA-13123 column string is already defined
ORA-13124 unable to determine column id for column string
ORA-13125 partition key is already set
ORA-13126 unable to determine class for spatial table string
ORA-13127 failed to generate target partition
ORA-13128 current tiling level exceeds user specified tiling level
ORA-13129 HHCODE column string not found
ORA-13135 failed to alter spatial table
ORA-13136 null common code generated
ORA-13137 failed to generate tablespace sequence number
ORA-13138 could not determine name of object string
ORA-13139 could not obtain column definition for string
ORA-13140 invalid target type
ORA-13141 invalid RANGE window definition
ORA-13142 invalid PROXIMITY window definition
ORA-13143 invalid POLYGON window definition
ORA-13144 target table string not found
ORA-13145 failed to generate range list
ORA-13146 could not find table substitution variable string
ORA-13147 failed to generate MBR
ORA-13148 failed to generate SQL filter
ORA-13149 failed to generate next sequence number for spatial table string
ORA-13150 failed to insert exception record
ORA-13151 failed to remove exception record
ORA-13152 invalid HHCODE type
ORA-13153 invalid high water mark specified
ORA-13154 invalid precision specified
ORA-13155 invalid number of dimensions specified
ORA-13156 table to be registered string.string is not empty
ORA-13157 Oracle error ORAstring encountered while string
ORA-13158 Oracle object string does not exist
ORA-13159 Oracle table string already exists
ORA-13181 unable to determine length of column string_SDOINDEX.SDO_CODE
ORA-13182 failed to read element string.string.string
ORA-13183 unsupported geometric type for geometry string.string
ORA-13184 failed to initialize tessellation package
ORA-13185 failed to generate initial HHCODE
ORA-13186 fixed tile size tessellation failed
ORA-13187 subdivision failed
ORA-13188 cell decode failed
ORA-13189 recursive SQL parse failed
ORA-13190 recursive SQL fetch failed
ORA-13191 failed to read SDO_ORDCNT value
ORA-13192 failed to read number of element rows
ORA-13193 failed to allocate space for geometry
ORA-13194 failed to decode supercell
ORA-13195 failed to generate maximum tile value
ORA-13196 failed to compute supercell for element string.string.string
ORA-13197 element string.string.string is out of range
ORA-13198 Spatial Cartridge error: string
ORA-13199 string
ORA-13200 internal error [string] in spatial indexing.
ORA-13201 invalid parameters supplied in CREATE INDEX statement
ORA-13202 failed to create or insert into the SDO_INDEX_METADATA table
ORA-13203 failed to read USER_SDO_GEOM_METADATA table
ORA-13204 failed to create spatial index table
ORA-13205 internal error while parsing spatial parameters
ORA-13206 internal error [string] while creating the spatial index
ORA-13207 incorrect use of the [string] operator
ORA-13208 internal error while evaluating [string] operator
ORA-13209 internal error while reading SDO_INDEX_METADATA table
ORA-13210 error inserting data into the index table
ORA-13211 failed to tessellate the window object
ORA-13212 failed to compare tile with the window object
ORA-13213 failed to generate spatial index for window object
ORA-13214 failed to compute supercell for window object
ORA-13215 window object is out of range
ORA-13216 failed to update spatial index
ORA-13217 invalid parameters supplied in ALTER INDEX statement
ORA-13218 max number of supported index tables reached for [string] index
ORA-13219 failed to create spatial index table [string]
ORA-13220 failed to compare tile with the geometry
ORA-13221 unknown geometry type in the geometry object
ORA-13222 failed to compute supercell for geometry in string
ORA-13223 duplicate entry for string in SDO_GEOM_METADATA table
ORA-13224 specified index name is too long for a spatial index
ORA-13225 specified index table name is too long for a spatial index
ORA-13226 interface not supported without a spatial index
ORA-13227 SDO_LEVEL values for the two index tables do not match
ORA-13228 Spatial index create failed due to invalid type
ORA-13230 failed to create temporary table [string] during R-tree creation
ORA-13231 failed to create index table [string] during R-tree creation
ORA-13232 failed to allocate memory during R-tree creation
ORA-13233 failed to create sequence number [string] for R-tree
ORA-13234 failed to access R-tree-index table [string]
ORA-13236 internal error in R-tree processing: [string]
ORA-13237 internal error during R-tree concurrent updates: [string]
ORA-13239 sdo_dimensionality not specified during n-d R-tree creation
ORA-13240 specified dimensionality greater than that of the query mbr
ORA-13241 specified dimensionality does not match that of the data
ORA-13242 failed to read tolerance values for n-d R-tree
ORA-13243 specified operator is not supported for n-d R-tree: [string]
ORA-13249 string
ORA-13250 insufficient privileges to modify metadata table entries
ORA-13251 duplicate entry string in metadata table
ORA-13260 layer table string does not exist
ORA-13261 geometry table string does not exist
ORA-13262 geometry column string does not exist in table string
ORA-13263 column string in table string is not of type SDO_GEOMETRY
ORA-13264 geometry identifier column string does not exist in table string
ORA-13265 geometry identifier column string in table string is not of type NUMBER.
ORA-13266 error inserting data into table string
ORA-13267 error reading data from layer table string
ORA-13268 error obtaining dimension from USER_SDO_GEOM_METADATA
ORA-13269 internal error [string] encountered when processing geometry table
ORA-13270 OCI error string
ORA-13271 error allocating memory for geometry object
ORA-13272 geometric object string in table string is invalid
ORA-13273 dimension metadata table string does not exist
ORA-13274 Operator invoked with non compatible SRIDs
ORA-13275 Spatial index creation failure on unsupported type
ORA-13276 internal error [string] in coordinate transformation
ORA-13278 failure to convert SRID to native format
ORA-13281 failure in execution of sql statement to retrieve WKT
ORA-13282 failure on initialization of coordinate transformation
ORA-13283 failure to get new geometry object for conversion in place
ORA-13284 failure to copy geometry object for conversion in place
ORA-13285 Geometry coordinate transformation error
ORA-13287 can't transform unknown gtype
ORA-13288 Point coordinate transformation error
ORA-13290 The specified unit is not supported
ORA-13291 Conversion error between the specified unit and standard unit
ORA-13292 Incorrect ARC_TOLERANCE specification
ORA-13293 Cannot specify unit for geometry without a georeferenced SRID
ORA-13294 Cannot transform geometry containing circular arcs
ORA-13295 Geometry objects are in different coordinate systems
ORA-13296 Incorrect Coordinate System Specification
ORA-13300 Single point transform error
ORA-13303 failure to retrieve a geometry object from a table
ORA-13304 failure to insert a transformed geometry object in a table
ORA-13330 invalid MASK
ORA-13331 invalid LRS segment
ORA-13332 invalid LRS point
ORA-13333 invalid LRS measure
ORA-13334 LRS segments not connected
ORA-13335 LRS measure information not defined
ORA-13336 Failure in converting standard diminfo/geometry to LRS dim/geom
ORA-13337 failure in concatenating LRS polygons
ORA-13338 failure in reversing LRS polygon/collection geometry
ORA-13339 LRS Polygon clipping across multiple rings
ORA-13340 a point geometry has more than one coordinate
ORA-13341 a line geometry has less than two coordinates
ORA-13342 an arc geometry has less than three coordinates
ORA-13343 a polygon geometry has less than four coordinates
ORA-13344 an arcpolygon geometry has less than five coordinates
ORA-13345 a compound polygon geometry has less than five coordinates
ORA-13346 the coordinates defining an arc are collinear
ORA-13347 the coordinates defining an arc are not distinct
ORA-13348 polygon boundary is not closed
ORA-13349 polygon boundary crosses itself
ORA-13350 two or more rings of a complex polygon touch
ORA-13351 two or more rings of a complex polygon overlap
ORA-13352 the coordinates do not describe a circle
ORA-13353 ELEM_INFO_ARRAY not grouped in threes
ORA-13354 incorrect offset in ELEM_INFO_ARRAY
ORA-13355 SDO_ORDINATE_ARRAY not grouped by number of dimensions specified
ORA-13356 adjacent points in a geometry are redundant
ORA-13357 extent type does not contain 2 points
ORA-13358 circle type does not contain 3 points
ORA-13359 extent does not have an area
ORA-13360 invalid subtype in a compound type
ORA-13361 not enough sub-elements within a compound ETYPE
ORA-13362 disjoint sub-element in a compound polygon
ORA-13363 no valid ETYPE in the geometry
ORA-13364 Layer Dimensionality does not match geometry dimensions
ORA-13365 Layer SRID does not match geometry SRID
ORA-13366 Invalid combination of interior exterior rings
ORA-13367 Wrong orientation for interior/exterior rings
ORA-13368 Simple Polygon type has more than one exterior ring
ORA-13369 Invalid value for etype in the 4 digit format
ORA-13370 failure in applying 3D LRS functions
ORA-13371 invalid position of measure dimension
ORA-13372 failure in modifying metadata for a table with spatial index
ORA-13373 Element of type Extent is not supported for Geodetic data
ORA-13374 SDO_MBR not supported for geodetic data
ORA-13375 The layer is of type [string] while geometry inserted has type [string]
ORA-13376 Invalid type name specified for layer_gtype parameter
ORA-13377 Invalid combination of elements with orientation
ORA-13378 Invalid index for element to be extracted
ORA-13379 Invalid index for sub-element to be extracted
ORA-13400 Oracle GeoImage internal error, arguments: [string], [string], [string], [string], [string]
ORA-13401 unsupported geoimage format
ORA-13402 NULL destination
ORA-13403 NULL source geometry
ORA-13404 not a local source
ORA-13405 NULL source
ORA-13406 unsupported image processing command [string]
ORA-13407 unrecognized space type qualifier [string]
ORA-13408 NULL table name
ORA-13409 Oracle table "string" does not exist.
ORA-13410 NULL column name
ORA-13411 Oracle column "string" does not exist.
ORA-13412 invalid ROWID
ORA-13413 could not select the GeoImage for initialization
ORA-13414 could not update the table containing the GeoImage
ORA-13415 invalid domain
ORA-13416 invalid geometry, arguments [string]
ORA-13417 undefined raster to model space transformation
ORA-13418 undefined model to raster space transformation
ORA-13419 invalid latitude value
ORA-13420 invalid model to raster space transformation
ORA-13421 invalid raster to model space transformation
ORA-13422 uninitialized source
ORA-13423 empty source
ORA-13424 uninitialized destination
ORA-13425 empty destination
ORA-13426 unsupported raster origin
ORA-13427 unknown raster origin
ORA-13428 source does not exist
ORA-13429 operation "string" not supported on GeoImage type "string"
ORA-13430 model coordinate system not supported
ORA-13433 NULL crop geometry
ORA-13442 invalid scaling parameters [string] [string]
ORA-13443 unrecognized scale mode [string]
ORA-13451 unsupported conversion format [string]
ORA-13461 invalid tag/key [string]
ORA-13462 invalid tie point
ORA-13463 unsupported GeoTIFF geometry definition
ORA-13464 unsupported conversion
ORA-13465 invalid destination window
ORA-14000 only one LOCAL clause may be specified
ORA-14001 LOCAL clause contradicts previosly specified GLOBAL clause
ORA-14002 only one GLOBAL clause may be specified
ORA-14003 GLOBAL clause contradicts previosly specified LOCAL clause
ORA-14004 missing PARTITION keyword
ORA-14005 missing RANGE keyword
ORA-14006 invalid partition name
ORA-14007 missing LESS keyword
ORA-14008 missing THAN keyword
ORA-14009 partition bound may not be specified for a LOCAL index partition
ORA-14010 this physical attribute may not be specified for an index partition
ORA-14011 names assigned to resulting partitions must be distinct
ORA-14012 resulting partition name conflicts with that of an existing partition
ORA-14013 duplicate partition name
ORA-14014 maximum number of partitioning columns is 16
ORA-14015 too many partition descriptions
ORA-14016 underlying table of a LOCAL partitioned index must be partitioned
ORA-14017 partition bound list contains too many elements
ORA-14018 partition bound list contains too few elements
ORA-14019 partition bound element must be one of: string, datetime or interval literal, number, or MAXVALUE
ORA-14020 this physical attribute may not be specified for a table partition
ORA-14021 MAXVALUE must be specified for all columns
ORA-14022 creation of LOCAL partitioned cluster indices is not supported
ORA-14023 creation of GLOBAL partitioned cluster indices is not supported
ORA-14024 number of partitions of LOCAL index must equal that of the underlying table
ORA-14025 PARTITION may not be specified for a materialized view or a materialized view log
ORA-14026 PARTITION and CLUSTER clauses are mutually exclusive
ORA-14027 only one PARTITION clause may be specified
ORA-14028 missing AT or VALUES keyword
ORA-14029 GLOBAL partitioned index must be prefixed
ORA-14030 non-existent partitioning column in CREATE TABLE statement
ORA-14031 partitioning column may not be of type LONG or LONG RAW
ORA-14032 partition bound of partition number string is too high
ORA-14036 partition bound value too large for column
ORA-14037 partition bound of partition "string" is too high
ORA-14038 GLOBAL partitioned index must be prefixed
ORA-14039 partitioning columns must form a subset of key columns of a UNIQUE index
ORA-14041 partition bound may not be specified for resulting partitions
ORA-14042 partition bound may not be specified for a partition being moved, modified or rebuilt
ORA-14043 only one partition may be added
ORA-14044 only one partition may be moved
ORA-14045 only one partition may be modified
ORA-14046 a partition may be split into exactly two new partitions
ORA-14047 ALTER TABLE|INDEX RENAME may not be combined with other operations
ORA-14048 a partition maintenance operation may not be combined with other operations
ORA-14049 invalid ALTER TABLE MODIFY PARTITION option
ORA-14050 invalid ALTER INDEX MODIFY PARTITION option
ORA-14051 invalid ALTER MATERIALIZED VIEW option
ORA-14052 partition-extended table name syntax is disallowed in this context
ORA-14053 illegal attempt to modify string in string statement
ORA-14054 invalid ALTER TABLE TRUNCATE PARTITION option
ORA-14055 keyword REBUILD in ALTER INDEX REBUILD must immediately follow index_name
ORA-14056 partition number string: sum of PCTUSED and PCTFREE may not exceed 100
ORA-14057 partition "string": sum of PCTUSED and PCTFREE may not exceed 100
ORA-14058 partition number string: INITRANS value must be less than MAXTRANS value
ORA-14059 partition "string": INITRANS value must be less than MAXTRANS value
ORA-14060 data type or length of a table partitioning column may not be changed
ORA-14061 data type or length of an index partitioning column may not be changed
ORA-14062 one or more of table's partitions reside in a read-only tablespace
ORA-14063 Unusable index exists on unique/primary constraint key
ORA-14064 Index with Unusable partition exists on unique/primary constraint key
ORA-14065 ALLOCATE STORAGE may not be specified for a partitioned table
ORA-14066 illegal option for a non-partitioned index-organized table
ORA-14067 duplicate TABLESPACE_NUMBER specification
ORA-14068 TABLESPACE and TABLESPACE_NUMBER may not be both specified
ORA-14069 invalid TABLESPACE_NUMBER value
ORA-14070 option may be specified only for partitioned indices or with REBUILD
ORA-14071 invalid option for an index used to enforce a constraint
ORA-14072 fixed table may not be truncated
ORA-14073 bootstrap table or cluster may not be truncated
ORA-14074 partition bound must collate higher than that of the last partition
ORA-14075 partition maintenance operations may only be performed on partitioned indices
ORA-14076 DROP/SPLIT PARTITION may not be applied to a LOCAL index partition
ORA-14078 you may not drop the highest partition of a GLOBAL index
ORA-14079 illegal option for a partition marked Index Unusable
ORA-14080 partition cannot be split along the specified high bound
ORA-14081 new partition name must differ from the old partition name
ORA-14082 new partition name must differ from that of any other partition of the object
ORA-14083 cannot drop the only partition of a partitioned table
ORA-14084 you may specify TABLESPACE DEFAULT only for a LOCAL index
ORA-14085 partitioned table cannot have column with LONG datatype
ORA-14086 a partitioned index may not be rebuilt as a whole
ORA-14094 invalid ALTER TABLE EXCHANGE PARTITION option
ORA-14095 ALTER TABLE EXCHANGE requires a non-partitioned, non-clustered table
ORA-14096 tables in ALTER TABLE EXCHANGE PARTITION must have the same number of columns
ORA-14097 column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
ORA-14098 index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
ORA-14099 all rows in table do not qualify for specified partition
ORA-14100 partition extended table name cannot refer to a remote object
ORA-14101 partition extended table name cannot refer to a synonym
ORA-14102 only one LOGGING or NOLOGGING clause may be specified
ORA-14103 LOGGING/NOLOGGING may not be combined with RECOVERABLE/UNRECOVERABLE
ORA-14104 RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
ORA-14105 RECOVERABLE/UNRECOVERABLE may not be specified in this context
ORA-14106 LOGGING/NOLOGGING may not be specified for a clustered table
ORA-14107 partition specification is required for a partitioned object
ORA-14108 illegal partition-extended table name syntax
ORA-14109 partition-extended object names may only be used with tables
ORA-14110 partitioning column may not be of type ROWID
ORA-14111 creation of GLOBAL partitioned indices on clustered tables is not supported
ORA-14112 RECOVERABLE/UNRECOVERABLE may not be specified for a partition or subpartition
ORA-14113 partitioned table cannot have column with LOB datatype
ORA-14114 partitioned table cannot have column with object, REF, nested table, array datatype
ORA-14115 partition bound of partition number string is too long
ORA-14116 partition bound of partition "string" is too long
ORA-14117 partition resides in offlined tablespace
ORA-14118 CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
ORA-14119 specified partition bound is too long
ORA-14120 incompletely specified partition bound for a DATE column
ORA-14121 MODIFY DEFAULT ATTRIBUTES may not be combined with other operations
ORA-14122 only one REVERSE or NOREVERSE clause may be specified
ORA-14123 duplicate NOREVERSE clause
ORA-14124 duplicate REVERSE clause
ORA-14125 REVERSE/NOREVERSE may not be specified in this context
ORA-14126 only a parallel_clause may follow description(s) of resulting partitions
ORA-14128 FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE PARTITION
ORA-14129 INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
ORA-14130 UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION
ORA-14131 enabled UNIQUE constraint exists on one of the tables
ORA-14132 table cannot be used in EXCHANGE
ORA-14133 ALTER TABLE MOVE cannot be combined with other operations
ORA-14134 indexes cannot use both DESC and REVERSE
ORA-14135 a LOB column cannot serve as a partitioning column
ORA-14136 ALTER TABLE EXCHANGE restricted by fine-grained security
ORA-14150 missing SUBPARTITION keyword
ORA-14151 invalid table partitioning method
ORA-14152 invalid number of partitions specified in PARTITIONS clause
ORA-14153 only one of STORE IN or partition_description clause may be specified
ORA-14154 only one of STORE IN or subpartition_description clause may be specified
ORA-14155 missing PARTITION or SUBPARTITION keyword
ORA-14156 invalid number of subpartitions specified in [SUBPARTITIONS | SUBPARTITION TEMPLATE] clause
ORA-14157 invalid subpartition name
ORA-14158 too many subpartition descriptions
ORA-14159 duplicate subpartition name
ORA-14160 this physical attribute may not be specified for a table subpartition
ORA-14161 subpartition number string: sum of PCTUSED and PCTFREE may not exceed 100
ORA-14162 subpartition "string": sum of PCTUSED and PCTFREE may not exceed 100
ORA-14163 subpartition number string: INITRANS value must be less than MAXTRANS value
ORA-14164 subpartition "string": INITRANS value must be less than MAXTRANS value
ORA-14165 MODIFY DEFAULT ATTRIBUTES FOR PARTITION may not be combined with other operations
ORA-14166 missing INTO keyword
ORA-14167 only one subpartition may be moved
ORA-14168 only one subpartition may be modified
ORA-14169 invalid ALTER TABLE MODIFY SUBPARTITION option
ORA-14170 cannot specify partition_description clause in CREATE TABLE|INDEX
ORA-14171 cannot specify subpartition_description clause in CREATE|ALTER TABLE
ORA-14172 invalid ALTER TABLE EXCHANGE SUBPARTITION option
ORA-14173 illegal subpartition-extended table name syntax
ORA-14174 only a parallel_clause may follow COALESCE PARTITION|SUBPARTITION
ORA-14175 a subpartition maintenance operation may not be combined with other operations
ORA-14176 this attribute may not be specified for a hash partition
ORA-14177 STORE-IN (Tablespace list) can only be specified for a LOCAL index on a table which is hash or composite partitioned
ORA-14183 TABLESPACE DEFAULT can be specified only for Composite LOCAL index
ORA-14185 incorrect physical attribute specified for this index partition
ORA-14186 number of sub-partitions of LOCAL index must equal that of the underlying table
ORA-14187 partitioning method for LOCAL index is inconsistent with that of the underlying table
ORA-14188 sub-partitioning columns must form a subset of key columns of a UNIQUE index
ORA-14189 this physical attribute may not be specified for an index subpartition
ORA-14190 only one ENABLE/DISABLE ROW MOVEMENT clause can be specified
ORA-14191 ALLOCATE STORAGE may not be specified for Composite Range partitioned object
ORA-14192 cannot modify physical index attributes of a Hash index partition
ORA-14193 invalid ALTER INDEX MODIFY SUBPARTITION option
ORA-14194 only one subpartition may be rebuilt
ORA-14195 ALLOCATE STORAGE may not be specified for RANGE or LIST partitioned object
ORA-14251 Specified subpartition does not exist
ORA-14252 invalid ALTER TABLE MODIFY PARTITION option for a Hash partition
ORA-14253 table is not partitioned by Composite Range method
ORA-14254 cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table
ORA-14255 table is not partitioned by Range or Composite Range or List method
ORA-14256 invalid resulting partition description(s)
ORA-14257 cannot move partition other than a Range or Hash partition
ORA-14258 invalid partition description
ORA-14259 table is not partitioned by Hash method
ORA-14260 incorrect physical attribute specified for this partition
ORA-14261 partition bound may not be specified when adding this Hash partition
ORA-14262 new subpartition name must differ from the old subpartition name
ORA-14263 new subpartition name must differ from that of any other subpartition of the object
ORA-14264 table is not partitioned by Composite Range method
ORA-14265 data type or length of a table subpartitioning column may not be changed
ORA-14266 data type or length of an index subpartitioning column may not be changed
ORA-14267 cannot specify PARALLEL clause when adding a (Composite) Range partition
ORA-14268 subpartition 'string' of the partition resides in offlined tablespace
ORA-14269 cannot exchange partition other than a Range or Hash partition
ORA-14270 table is not partitioned by Range or Hash or List method
ORA-14271 table is not partitioned by Composite Range method
ORA-14272 only a partition with higher bound can be reused
ORA-14273 lower-bound partition must be specified first
ORA-14274 partitions being merged are not adjacent
ORA-14275 cannot reuse lower-bound partition as resulting partition
ORA-14276 EXCHANGE SUBPARTITION requires a non-partitioned, non-clustered table
ORA-14277 tables in EXCHANGE SUBPARTITION must have the same number of columns
ORA-14278 column type or size mismatch in EXCHANGE SUBPARTITION
ORA-14279 index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION
ORA-14280 all rows in table do not qualify for specified subpartition
ORA-14281 CHECK constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
ORA-14282 FOREIGN KEY constraint mismatch in ALTER TABLE EXCHANGE SUBPARTITION
ORA-14283 UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION
ORA-14284 one or more of table's subpartitions reside in a read-only tablespace
ORA-14285 cannot COALESCE the only partition of this partitioned table
ORA-14286 cannot COALESCE the only subpartition of this table partition
ORA-14287 cannot REBUILD a partition of a Composite Range partitioned index
ORA-14288 index is not partitioned by Composite Range method
ORA-14289 cannot make local index partition of Composite Range partitioned table unusable
ORA-14290 PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
ORA-14291 cannot EXCHANGE a composite partition with a non-partitioned table
ORA-14292 Partitioning type of table must match subpartitioning type of composite partition
ORA-14293 Number of partitioning columns does not match number of subpartitioning columns
ORA-14294 Number of partitions does not match number of subpartitions
ORA-14295 column type or size mismatch between partitioning columns and subpartitioning columns
ORA-14296 Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
ORA-14297 Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
ORA-14298 LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
ORA-14301 table-level attributes must be specified before partition-level attributes
ORA-14302 only one list of added-LOB-storage-clauses can be specified in a statement
ORA-14303 partitions or subpartitions are not in the right order
ORA-14304 List partitioning method expects a single partitioning column
ORA-14305 List value 'string' specified twice in partition 'string'
ORA-14306 List value 'string' specified twice in partitions 'string', 'string'
ORA-14307 partition contains too many list values
ORA-14308 partition bound element must be one of: string, datetime or interval literal, number, or NULL
ORA-14309 Total count of list values exceeds maximum allowed
ORA-14310 VALUES LESS THAN or AT clause cannot be used with List partitioned tables
ORA-14311 Expecting VALUES LESS THAN or AT clause
ORA-14312 Value string already exists in partition string
ORA-14313 Value string does not exist in partition string
ORA-14314 resulting List partition(s) must contain atleast 1 value
ORA-14315 cannot merge a partition with itself
ORA-14316 table is not partitioned by List method
ORA-14317 cannot drop the last value of partition
ORA-14318 DEFAULT partition must be last partition specified
ORA-14319 DEFAULT cannot be specified with other values
ORA-14320 DEFAULT cannot be specified for ADD/DROP VALUES or SPLIT
ORA-14321 cannot add/drop values to DEFAULT partition
ORA-14322 DEFAULT partition already exists
ORA-14323 cannot add partition when DEFAULT partition exists
ORA-14324 values being added already exist in DEFAULT partition
ORA-14400 inserted partition key does not map to any partition
ORA-14401 inserted partition key is outside specified partition
ORA-14402 updating partition key column would cause a partition change
ORA-14403 cursor invalidation detected after getting DML partition lock
ORA-14404 partitioned table contains partitions in a different tablespace
ORA-14405 partitioned index contains partitions in a different tablespace
ORA-14406 updated partition key is beyond highest legal partition key
ORA-14407 partitioned table contains subpartitions in a different tablespace
ORA-14408 partitioned index contains subpartitions in a different tablespace
ORA-14409 inserted partition key is outside specified subpartition
ORA-14450 attempt to access a transactional temp table already in use
ORA-14451 unsupported feature with temporary table
ORA-14452 attempt to create, alter or drop an index on temporary table already in use
ORA-14453 attempt to use a LOB of a temporary table, whose data has already been purged
ORA-14454 attempt to reference temporary table in a referential integrity constraint
ORA-14455 attempt to create referential integrity constraint on temporary table
ORA-14456 cannot rebuild index on a temporary table
ORA-14457 disallowed VARRAY and Nested Table column in a Temporary table
ORA-14458 attempt was made to create a temporary table with INDEX organization
ORA-14459 missing GLOBAL keyword
ORA-14460 only one COMPRESS or NOCOMPRESS clause may be specified
ORA-14500 LOCAL option not valid without partition name
ORA-14501 object is not partitioned
ORA-14503 only one partition name can be specified
ORA-14504 syntax not supported for analyze
ORA-14505 LOCAL option valid only for partitioned indexes
ORA-14506 LOCAL option required for partitioned indexes
ORA-14507 partition corrupt. all rows do not fall within partition bounds
ORA-14508 specified VALIDATE INTO table not found
ORA-14509 specified VALIDATE INTO table form incorrect
ORA-14510 can specify VALIDATE INTO clause only for partitioned tables
ORA-14511 cannot perform operation on a partitioned object
ORA-14512 cannot perform operation on a clustered object
ORA-14513 partitioning column may not be of object datatype
ORA-14514 LOCAL option not valid without subpartition name
ORA-14515 only one aubpartition name can be specified
ORA-14516 subpartition corrupt. all rows do not fall within subpartition bounds
ORA-14517 subpartition of index 'string.string' is in unusable state
ORA-14518 partition contains rows corresponding to values being dropped
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]
ORA-14520 Tablespace string block size [string] does not match existing object block size [string]
ORA-14521 Default tablespace string block size [string] for string string does not match existing string block size [string]
ORA-14522 Partition-level default tablespace string block size [string] for string string does not match existing string block size [string]
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]
ORA-14551 cannot perform a DML operation inside a query
ORA-14552 cannot perform a DDL, commit or rollback inside a query or DML
ORA-14553 cannot perform a lob write operation inside a query
ORA-14601 Illegal to specify SUBPARTITIONS or STORE-IN while specifying a subpartition template
ORA-14602 SUBPARTITION TEMPLATE is legal only for a composite partitioned table
ORA-14603 [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
ORA-14604 During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
ORA-14605 Name missing for subpartition / lob segment in template
ORA-14606 Tablespace was specified for previous subpartitions in template but is not specified for string
ORA-14607 Tablespace was not specified for previous subpartitions in template but is specified for string
ORA-14608 Tablespace was specified for the previous lob segments of column string in template but is not specified for string
ORA-14609 Tablespace was not specified for the previous lob segments of column string in template but is specified for string
ORA-14610 Lob attributes not specified for lob column string for subpartition string
ORA-14611 Duplicate subpartition name string in template
ORA-14612 Duplicate lob segment name string for lob column string in template
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
ORA-14614 List value 'string' specified twice in subpartition 'string'
ORA-14615 List value 'string' specified twice in subpartitions 'string', 'string'
ORA-14616 table is not subpartitioned by List method
ORA-14617 cannot add/drop values to DEFAULT subpartition
ORA-14618 cannot drop the last value of subpartition
ORA-14619 resulting List subpartition(s) must contain at least 1 value
ORA-14620 DEFAULT subpartition already exists
ORA-14621 cannot add subpartition when DEFAULT subpartition exists
ORA-14622 Value string already exists in subpartition string
ORA-14623 Value string does not exist in subpartition string
ORA-14624 DEFAULT subpartition must be last subpartition specified
ORA-14625 subpartition contains rows corresponding to values being dropped
ORA-14626 values being added already exist in DEFAULT subpartition
ORA-14627 Invalid operation was specified on a GLOBAL partitioned index
ORA-14628 specification of bounds is inconsistent with LIST method
ORA-14629 cannot drop the only subpartition of a partition
ORA-14630 subpartition resides in offlined tablespace
ORA-14631 the partition bounds do not match the subpartition bounds of the partition
ORA-14632 cannot specify PARALLEL clause when adding a List subpartition
ORA-14633 Index maintainence clause not allowed for ADD list subpartition to a Composite partitioned table
ORA-14634 Subpartition descriptions cannot be specified during the SPLIT/MERGE of a partition of a Range-List partitioned table
ORA-14635 only one resulting subpartition can be specified for MERGE SUBPARTITIONS
ORA-14636 only 2 resulting subpartition can be specified for SPLIT SUBPARTITION
ORA-14637 cannot merge a subpartition with itself
ORA-14638 cannot MERGE subpartitions in different Range Composite partitions
ORA-14639 SUBPARTITIONS clause can be specified only for Hash, Composite Range Hash table/partition
ORA-14640 DROP/SPLIT SUBPARTITION may not be applied to a LOCAL index subpartition
ORA-14641 STORE-IN clause can be specified only for a Hash, Composite Range Hash table/partition
ORA-14642 Bitmap index mismatch for tables in ALTER TABLE EXCHANGE PARTITION
ORA-14643 Hakan factor mismatch for tables in ALTER TABLE EXCHANGE PARTITION
ORA-14644 table is not subpartitioned by Hash method
ORA-14645 STORE IN clause cannot be specified for Range List objects
ORA-16000 database open for read-only access
ORA-16001 database already open for read-only access by another instance
ORA-16002 database already open for read-write access by another instance
ORA-16003 standby database is restricted to read-only access
ORA-16004 backup database requires recovery
ORA-16005 database requires recovery
ORA-16006 audit_trail destination incompatible with database open mode
ORA-16007 invalid backup control file checkpoint
ORA-16008 indeterminate control file checkpoint
ORA-16009 remote archive log destination must be a STANDBY database
ORA-16010 remote archive log destination database is opened for update
ORA-16011 Archivelog Remote File Server process in Error state
ORA-16012 Archive log standby database identifier mismatch
ORA-16013 log string sequence# string does not need archiving
ORA-16014 log string sequence# string not archived, no available destinations
ORA-16015 log string sequence# string not archived, media recovery disabled
ORA-16016 archived log for thread string sequence# string unavailable
ORA-16017 cannot use LOG_ARCHIVE_DUPLEX_DEST without a primary archive destination
ORA-16018 cannot use string with LOG_ARCHIVE_DEST_n
ORA-16019 cannot use string with LOG_ARCHIVE_DEST or LOG_ARCHIVE_DUPLEX_DEST
ORA-16020 less destinations available than specified by LOG_ARCHIVE_MIN_SUCCEED_DEST
ORA-16021 session string destination cannot be the same as session string destination
ORA-16022 LOG_ARCHIVE_DEST cannot be NULL because LOG_ARCHIVE_DUPLEX_DEST is non-NULL
ORA-16023 system string destination cannot be the same as session string destination
ORA-16024 parameter string cannot be parsed
ORA-16025 parameter string contains repeated or conflicting attributes
ORA-16026 parameter string contains an invalid numeric attribute value
ORA-16027 parameter string is missing a destination option
ORA-16028 new string causes less destinations than LOG_ARCHIVE_MIN_SUCCEED_DEST requires
ORA-16029 cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations
ORA-16030 session specific change requires a LOG_ARCHIVE_DEST_n destination
ORA-16031 parameter string destination string exceeds string character limit
ORA-16032 parameter string destination string cannot be translated
ORA-16033 parameter string destination cannot be the same as parameter string destination
ORA-16034 FROM parameter is incompatible with MANAGED recovery
ORA-16035 missing required keyword string
ORA-16036 invalid MANAGED recovery CANCEL option
ORA-16037 user requested cancel of managed recovery operation
ORA-16038 log string sequence# string cannot be archived
ORA-16039 RFS request version mismatch
ORA-16040 standby destination archive log file is locked
ORA-16041 Remote File Server fatal error
ORA-16042 user requested cancel immediate of managed recovery operation
ORA-16043 managed recovery session canceled
ORA-16044 destination string attribute cannot be specified at session level
ORA-16045 circular archive log destination dependency chain
ORA-16046 Archive log destination failed due to failed dependent destination
ORA-16047 Dependent archive log destination cannot be a standby database
ORA-16048 enable simulated error on archive log write
ORA-16049 simulated error on archive log write
ORA-16050 destination exceeded specified quota size
ORA-16051 parameter string contains an invalid delay time
ORA-16052 Problem with fetching gap sequence, media recovery cancelled.
ORA-16053 FAL archive failed, cannot archive thread# string sequence# string
ORA-16055 FAL request rejected
ORA-16056 backup control file archival requires proper syntax
ORA-16057 current control file archival requires proper syntax
ORA-16058 standby database instance is not mounted
ORA-16059 Log file is empty or invalid next available block
ORA-16060 Log file is current
ORA-16061 Log file status has changed
ORA-16062 The log was NOT archived
ORA-16063 remote archival is enabled by another instance
ORA-16064 remote archival is disabled by another instance
ORA-16065 remote archival disabled at standby destination
ORA-16066 remote archival disabled
ORA-16067 activation identifier mismatch in archive log string
ORA-16068 redo log file activation identifier mismatch
ORA-16069 Archive Log standby database activation identifier mismatch
ORA-16070 parameter string contains an invalid REGISTER attribute value
ORA-16071 dependency archived log file not found string
ORA-16072 a minimum of one standby database destination is required
ORA-16073 archiving must be enabled
ORA-16074 ARCH processes must be active
ORA-16075 standby database destination mismatch
ORA-16076 unknown standby database destination
ORA-16078 media recovery disabled
ORA-16079 standby archival not enabled
ORA-16080 invalid LogMiner session string for APPLY
ORA-16081 insufficient number of processes for APPLY
ORA-16082 logical standby is not initialized correctly
ORA-16083 LogMiner session has not been created
ORA-16084 an apply engine is already running
ORA-16086 standby database does not contain available standby log files
ORA-16087 graceful switchover requires standby or current control file
ORA-16088 archive log has not been completely archived
ORA-16089 archive log has already been registered
ORA-16090 archive log to be replaced not created by managed standby process
ORA-16091 dependent archive log destination already archived
ORA-16092 dependent archive log destination is not active
ORA-16093 dependent archive log destination is not LGWR-enabled
ORA-16094 database shutdown during archival operation
ORA-16095 Dependent destination removal for inactivation
ORA-16098 inaccessible standby database forced shutdown to protect primary
ORA-16099 internal error ORA-00600 occurred at standby database
ORA-16100 not a valid Logical Standby database
ORA-16101 a valid start SCN could not be found
ORA-16102 remote information is not available on the specified primary
ORA-16103 Logical Standby apply must be stopped to allow this operation
ORA-16104 invalid Logical Standby option requested
ORA-16105 Logical Standby is already running in background
ORA-16107 all log data from primary has been processed
ORA-16108 database is no longer a standby database
ORA-16109 failed to apply log data from previous primary
ORA-16110 user procedure processing of logical standby apply DDL
ORA-16111 log mining and apply setting up
ORA-16112 log mining and apply stopping
ORA-16113 applying change to table or sequence object number string
ORA-16114 applying DDL transaction with commit SCN string
ORA-16115 loading Log Miner dictionary data
ORA-16116 no work available
ORA-16117 processing
ORA-16119 building transaction at SCN string
ORA-16120 dependencies being computed for transaction at SCN string
ORA-16121 applying transaction with commit SCN string
ORA-16122 applying large dml transaction at SCN string
ORA-16123 transaction string string string is waiting for commit approval
ORA-16124 transaction string string string is waiting on another transaction
ORA-16125 large transaction string string string is waiting on another transaction
ORA-16126 loading table or sequence object number string
ORA-16127 stalled waiting for additional transactions to be applied
ORA-16128 User initiated shut down successfully completed
ORA-16129 unsupported dml encountered
ORA-16130 supplemental log information is missing from log stream
ORA-16131 An error occurred during a Terminal Recovery of the standby.
ORA-16132 An error occurred during activation of the standby.
ORA-16133 Datafile string has incorrect terminal recovery stamp.
ORA-16134 invalid MANAGED recovery FINISH option
ORA-16135 terminal recovery could not find log for thread# string seq# string.
ORA-16136 Managed Standby Recovery not active
ORA-16137 No terminal recovery is required
ORA-16138 end of log stream not received from primary
ORA-16139 media recovery required
ORA-16140 standby online logs have not been recovered
ORA-16143 RFS connections not allowed during or after terminal recovery
ORA-16145 archival for thread# string sequence# string in progress
ORA-16146 standby destination control file enqueue unavailable
ORA-16147 standby database referenced by multiple archive log destinations
ORA-16148 user requested expiration of managed recovery operation
ORA-16150 FINISH recovery performed on another, older standby database
ORA-16151 Managed Standby Recovery not available
ORA-16152 standby database is in 'no-data-loss' protected mode
ORA-16154 suspect attribute: string
ORA-16156 LGWR archive log dependency not allowed if database is standby protected
ORA-16157 media recovery not allowed following successful FINISH recovery
ORA-16159 Cannot change protected standby destination attributes
ORA-16160 Cannot change protected standby database configuration
ORA-16161 Cannot mix standby and online redo log file members for group string
ORA-16162 Cannot add new standby databases to protected configuration
ORA-16163 LGWR network server host attach error
ORA-16164 LGWR network server host detach error
ORA-16165 LGWR failed to hear from network server
ORA-16166 LGWR network server failed to send remote message
ORA-16167 LGWR network server could not switch to non-blocking mode
ORA-16168 LGWR network server could not switch to blocking mode
ORA-16169 LGWR network server invalid parameters
ORA-16170 Parallel terminal recovery may lose more data than necessary
ORA-16171 RECOVER...FINISH not allowed due to gap for the string, seq string-string
ORA-16172 archive logs detected beyond Terminal End-Of-Redo
ORA-16173 incompatible archival network connections active
ORA-16174 user requested thread/sequence termination of managed recovery
ORA-16175 cannot shut down database when media recovery is active
ORA-16199 Terminal recovery failed to recover to a consistent point
ORA-16200 Skip procedure requested to skip statement
ORA-16201 Skip procedure requested to apply statement
ORA-16202 Skip procedure requested to replace statement
ORA-16203 Unable to interpret skip procedure return values
ORA-16204 DDL successfully applied
ORA-16205 DDL skipped due to skip setting
ORA-16206 database already configured as Logical Standby database
ORA-16207 Logical standby dictionary build not permitted.
ORA-16208 Logical standby dictionary build failed to start.
ORA-16209 Logical standby dictionary build failed to complete.
ORA-16210 Logical standby coordinator process terminated with error
ORA-16211 unsupported record found in the archived redo log
ORA-16212 number processes specified for APPLY is too great
ORA-16213 ddl encountered, stopping apply engine
ORA-16214 apply stalled for apply delay
ORA-16501 the Data Guard broker operation failed
ORA-16502 the Data Guard broker operation succeeded with warnings
ORA-16503 site ID allocation failure
ORA-16504 the Data Guard configuration already exists
ORA-16505 site ID is invalid
ORA-16506 out of memory
ORA-16507 unrecognized request identifier
ORA-16508 channel handle not initialized
ORA-16509 the request timed out
ORA-16510 messaging error using ksrwait
ORA-16511 messaging error using ksrget
ORA-16512 parameter exceeded maximum size limit
ORA-16513 maximum requests exceeded
ORA-16514 the request was not found
ORA-16515 no rcv channel
ORA-16516 the resource state is invalid for the attempted operation
ORA-16517 the object handle is invalid
ORA-16518 unable to allocate virtual instance id
ORA-16519 the resource handle is invalid
ORA-16520 unable to allocate resource id
ORA-16521 unable to create generic template id
ORA-16522 generic template not found
ORA-16523 property count exhausted
ORA-16524 unsupported operation
ORA-16525 the Data Guard broker is not yet available
ORA-16526 unable to allocate task element
ORA-16527 unable to allocate SGA heap
ORA-16528 unable to allocate PGA heap
ORA-16529 bad sender id
ORA-16530 invalid buffer or length
ORA-16531 unable to post message
ORA-16532 Data Guard configuration does not exist
ORA-16533 inconsistent Data Guard broker state
ORA-16534 no more requests accepted
ORA-16535 failover request rejected
ORA-16536 unknown object type
ORA-16537 child count exceeded
ORA-16538 no match on requested item
ORA-16539 task element not found
ORA-16540 invalid argument
ORA-16541 site is not enabled
ORA-16542 unrecognized operation
ORA-16543 invalid request made to broker
ORA-16544 unable to make request
ORA-16545 unable to get response
ORA-16546 missing or invalid piece
ORA-16547 unable to delete request
ORA-16548 the resource is not enabled
ORA-16549 invalid string
ORA-16550 truncated result
ORA-16551 short string copied
ORA-16552 the Data Guard broker process (DMON) failed to start
ORA-16553 the Data Guard broker process (DMON) failed to shutdown
ORA-16554 translation not valid
ORA-16555 the Data Guard resource is not active
ORA-16557 the resource is already in use
ORA-16558 the site specified for switchover is not a standby
ORA-16559 out of memory at string
ORA-16560 unable to convert document, syntax error at "string"
ORA-16561 must use ONLINE parent state, syntax error at "string"
ORA-16562 intended_state not used here, syntax error at "string"
ORA-16563 unable to add value, syntax error at "string"
ORA-16564 lookup failed, syntax error at string
ORA-16565 duplicate property, syntax error at "string"
ORA-16566 unsupported document type
ORA-16567 Data Guard broker internal parser error at "string"
ORA-16568 cannot set property string
ORA-16569 Data Guard configuration is not enabled
ORA-16570 Operation requires restart of site "string"
ORA-16571 Data Guard configuration file creation failure
ORA-16572 Data Guard configuration file not found
ORA-16573 attempt to change configuration file in an enabled DRC
ORA-16574 switchover disallowed when required resources are offline
ORA-16575 request terminated at broker discretion
ORA-16576 failed to update Data Guard configuration file
ORA-16577 corruption detected in Data Guard configuration file
ORA-16578 failed to read Data Guard configuration file
ORA-16579 bad Data Guard NetSlave state detected
ORA-16580 bad Data Guard NetSlave network link
ORA-16581 Data Guard NetSlave failed to send message to DRCX
ORA-16582 Data Guard connection process received error from NetSlave
ORA-16583 bad Data Guard Connection Process DRCX state
ORA-16584 illegal operation on a standby site
ORA-16585 illegal operation on a primary site
ORA-16586 Data Guard broker unable to update configuration on site
ORA-16587 ambiguous object handle
ORA-16588 no more internal buffers
ORA-16589 Data Guard Connection process detected a network transfer error
ORA-16590 no primary established in Data Guard configuration
ORA-16591 unknown field "string" in document
ORA-16592 missing field "string" in document
ORA-16593 XML conversion failed
ORA-16594 string process discovered that DMON process does not exist
ORA-16595 NetSlave process string failed to terminate
ORA-16596 site is not a member of the Data Guard configuration
ORA-16597 Data Guard broker detects two or more primaries
ORA-16598 The Data Guard broker has detected a mismatch in configuration
ORA-16599 The Data Guard broker has detected a stale configuration
ORA-16600 Failover operation can only be submitted on target site
ORA-16601 site contains required resources that are disabled
ORA-16602 resource must be disabled to perform this operation
ORA-16603 Data Guard broker detected mismatch in configuration ID
ORA-16604 unable to describe template using package "string"
ORA-16605 unable to delete template, template is in use
ORA-16606 unable to find property "string"
ORA-16607 one or more sites have failed
ORA-16608 one or more sites have warnings
ORA-16609 one or more resources have failed
ORA-16610 one or more resources have warnings
ORA-16611 operation aborted at user request
ORA-16612 string value too long for attribute "string"
ORA-16613 initialization in progress for site
ORA-16614 object has an ancestor that is disabled
ORA-16617 Unknown object identifier specified in request
ORA-16618 response document of size "string" bytes is too large
ORA-16619 Health Check timed out
ORA-16620 one or more sites could not be contacted for a delete operation
ORA-16621 host and SID names for create site must be unique
ORA-16622 two or more Broker sites resolve to the same physical site
ORA-16623 stale DRC UID sequence number detected
ORA-16624 broker protocol version mismatch detected
ORA-16625 cannot reach the primary site
ORA-16626 failed to enable specified object
ORA-16627 no standby databases support overall protection mode
ORA-16628 The Broker protection mode is inconsistent with the database setting
ORA-16629 database reports a different protection level from the protection mode
ORA-16701 generic resource guard request failed
ORA-16702 generic resource manager warning
ORA-16703 status of request is unknown
ORA-16704 a previous set state operation is pending
ORA-16705 severe internal error in resource guard
ORA-16706 no resource guard is available
ORA-16707 the value supplied to resource guard is invalid
ORA-16708 the state supplied to resource guard is invalid
ORA-16709 the resource guard is busy and cannot service the request
ORA-16710 the resource guard is out of memory
ORA-16711 the resource guard index is out of bounds
ORA-16712 the resource handle is invalid
ORA-16713 the resource guard timed out while servicing the request
ORA-16714 the resource guard exceeded its retry limit
ORA-16715 the logical standby database requires instantiation
ORA-16716 clearing parameter LOG_ARCHIVE_DEST failed
ORA-16717 clearing parameter LOG_ARCHIVE_DUPLEX_DEST failed
ORA-16718 failed to locate the database resource
ORA-16719 unable to query V$ARCHIVE_DEST fixed view
ORA-16720 no available LOG_ARCHIVE_DEST_n parameters to use
ORA-16721 unable to set LOG_ARCHIVE_DEST_n parameters
ORA-16722 unable to set LOG_ARCHIVE_DEST_STATE_n parameters
ORA-16723 the connect descriptor is missing from V$ARCHIVE_DEST
ORA-16724 the intended state for resource has been set to OFFLINE
ORA-16725 the phase supplied to resource manager is invalid
ORA-16726 the external condition supplied to resource manager is invalid
ORA-16727 resource guard cannot close database
ORA-16728 Log archive destination could not be set
ORA-16729 Error executing dbms_logstdby.log procedure
ORA-16730 Error executing dbms_logstdby.skip_txn procedure
ORA-16731 Error executing dbms_logstdby.unskip_txn procedure
ORA-16732 Error executing dbms_logstdby.skip procedure
ORA-16733 Error executing dbms_logstdby.unskip procedure
ORA-16734 Error executing dbms_logstdby.skip_error procedure
ORA-16735 Error executing dbms_logstdby.unskip_error procedure
ORA-16736 Standby log archive destination parameter could not be set
ORA-16737 Log archive format parameter could not be set
ORA-16738 Database file name convert parameter could not be set
ORA-16739 Log file name convert parameter could not be set
ORA-16740 Log archive trace parameter could not be set
ORA-16741 Control files parameter could not be set
ORA-16742 lock name trace parameter could not be set
ORA-16743 FAL client parameter could not be set
ORA-16744 FAL server parameter could not be set
ORA-16745 Resource guard encountered error during database dismount
ORA-16746 Resource guard encountered error during database mount
ORA-16747 Logical standby guard could not be turned on
ORA-16748 Resource guard encountered errors during database open
ORA-16749 Resource guard encountered errors in switchover to logical primary
ORA-16750 Resource guard encountered errors while activating logical primary
ORA-16751 Resource guard encountered errors in switchover to primary
ORA-16752 Resource guard could not mount standby
ORA-16753 Resource guard could not open standby database
ORA-16754 Resource guard could not activate standby
ORA-16755 Resource guard could not dismount standby
ORA-16756 Resource guard could not open standby read-only
ORA-16757 Resource guard could not get property
ORA-16758 Resource guard could not verify property
ORA-16759 Resource guard unable to start logical apply engine with initial SCN
ORA-16760 Resource guard could not start logical apply engine
ORA-16761 Resource guard could not stop logical apply engine
ORA-16762 Invalid database state
ORA-16763 Log transport service for some site unexpectedly online
ORA-16764 Log transport service for some site unexpectedly offline
ORA-16765 Physical apply service unexpectedly online
ORA-16766 Physical apply service unexpectedly offline
ORA-16767 Logical apply service unexpectedly online
ORA-16768 Logical apply service unexpectedly offline
ORA-16769 Error executing apply_set procedure
ORA-16770 Error executing apply_unset procedure
ORA-16771 Error starting ARCH process(es)
ORA-16772 Error in switching over between primary and standby databases
ORA-16773 Error in starting the physical apply service (MRP process)
ORA-16774 Error in stopping the physical apply service (MRP process)
ORA-16775 The physical apply service terminated prematurely
ORA-16776 Health check of the log transport service failed
ORA-16777 Unable to find the destination entry of a site in V$ARCHIVE_DEST
ORA-16778 The log transport service for some site has an error
ORA-16779 The destination parameter of some site has wrong syntax
ORA-16780 Some site has used up its quota
ORA-16781 The status of log transport service for some site is unknown
ORA-16782 Unable to get values of some critical configurable properties
ORA-16783 Some critical configurable property has not been set
ORA-16784 The site name given in property Dependency or Alternate is incorrect
ORA-16785 The database is not in ARCHIVELOG mode
ORA-16786 Resource guard cannot access Data Guard metadata
ORA-16788 Unable to set one or more database configuration property values
ORA-16789 Missing standby redo logs
ORA-16790 The value of the configurable property is invalid
ORA-16791 Unable to check the existence of the standby redo logs
ORA-16792 Some configurable property value is inconsistent with the database setting
ORA-16793 Logical Standby Database Guard is unexpectedly OFF
ORA-16794 Database Guard is ON for primary database
ORA-16795 Database resource guard detects that database reinstantiation is required
ORA-16796 One or more property cannot be imported from database
ORA-16797 SPFILE is missing in the Data Guard Broker environment
ORA-16798 Unable to complete terminal recovery on the standby
ORA-16799 Physical apply service is offline
ORA-16800 Log transport service for some site is incorrectly set to ALTERNATE
ORA-16801 Some log transport related property is inconsistent
ORA-16802 Cannot set property 'Alternate' to the primary site name
ORA-16803 Unable to query a database table or fixed view
ORA-16804 One or more configuration properties in metadata have invalid values
ORA-16805 Change of LogXptMode property violates overall protection mode
ORA-16806 Supplemental logging is not turned on
ORA-16807 unable to set protection mode to the database
ORA-16900 Unable to initialize client
ORA-16901 Unable to initialize environment
ORA-16902 Unable to allocate handle
ORA-16903 Unable to connect to database
ORA-16904 Unable to set attribute
ORA-16905 Failed.
ORA-16906 Unable to accept commands: no memory
ORA-16907 missing field
ORA-16908 Unknown option: "string"
ORA-16909 Fatal Error. quitting...
ORA-16910 unable to issue command to server
ORA-16911 Warning:
ORA-16912 Unknown command "string". Try "help"
ORA-16914 Missing connect string. Try "help"
ORA-16916 Missing site. Try "help"
ORA-16917 Missing XML document. Try "help"
ORA-16939 Could not start up "string" as primary
ORA-16940 Started "string" as new primary
ORA-16942 Could not start up "string" as standby
ORA-16943 Started "string" as standby
ORA-16944 Failover succeeded. New primary is "string"
ORA-16945 Syntax error before or at "string"
ORA-16946 Site "string" was not found
ORA-16947 "string" does not run in the primary role
ORA-16948 "string" does not run in the standby role
ORA-16949 Resource "string" was not found
ORA-16950 Unable to retrieve "string" for editing
ORA-16951 manager information not found
ORA-16952 unable to describe configuration
ORA-16953 site or resource "string" does not exist
ORA-16954 a resource cannot run on multiple sites this way
ORA-16955 unable to create or locate template
ORA-16956 missing template name
ORA-16957 template "string" was not found
ORA-16958 unable to convert document
ORA-16959 NULL answer from framework
ORA-16960 status not available
ORA-16991 ambiguous resource name
ORA-16992 You must restart site "string" manually.
ORA-17500 ODM err:string
ORA-17501 logical block size string is invalid
ORA-17502 ksfdcre: string Failed to create file string
ORA-17503 ksfdopn: string Failed to open file string
ORA-17504 ksfddel:Failed to delete file string
ORA-17505 ksfdrsz: string Failed to resize file to size number blocks
ORA-17506 I/O Error Simulation
ORA-17507 I/O request size string is not a multiple of logical block size
ORA-17508 I/O request buffer ptr is not alligned
ORA-17509 Attempt to do i/o beyond block1 offset
ORA-17510 Attempt to do i/o beyond file size
ORA-17610 file 'string' does not exist and no size specified
ORA-17611 ksfd: file 'string' cannot be accessed, global open closed
ORA-18000 invalid outline name
ORA-18001 no options specified for ALTER OUTLINE
ORA-18002 the specified outline does not exist
ORA-18003 an outline already exists with this signature
ORA-18004 outline already exists
ORA-18005 create any outline privilege is required for this operation
ORA-18006 drop any outline privilege is required for this operation
ORA-18007 alter any outline privilege is required for this operation
ORA-18008 cannot find OUTLN schema
ORA-18009 one or more outline system tables do not exist
ORA-18010 command missing mandatory CATEGORY keyword
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
ORA-19000 missing RELATIONAL keyword
ORA-19001 Invalid storage option specified
ORA-19002 Missing XMLSchema URL
ORA-19003 Missing XML root element name
ORA-19004 Duplicate XMLType OBJECT RELATIONAL storage option
ORA-19005 Duplicate XMLType LOB storage option
ORA-19006 XMLType TYPE storage option not appropriate for storage type
ORA-19007 Schema and element do not match
ORA-19008 Invalid version of the XMLType
ORA-19009 Missing XMLSchema keyword
ORA-19010 Cannot insert XML fragments
ORA-19011 Character string buffer too small
ORA-19012 Cannot convert XML fragment to the required datatype
ORA-19013 Cannot create VARRAY columns containing XMLType
ORA-19015 Invalid XML tag identifier (string)
ORA-19016 attributes cannot occur after element specifications
ORA-19017 Attributes can only be simple scalars
ORA-19018 Invalid character in XML tag 'string'
ORA-19019 Invalid context passed to DBMS_XMLGEN.GETXML
ORA-19020 invalid dereference of XMLType columns
ORA-19023 The first argument to UPDATEXML operator has to be an XMLTYPE
ORA-19024 Cursor expression must be named
ORA-19025 EXTRACTVALUE returns value of only one node
ORA-19026 EXTRACTVALUE can only retrieve value of leaf node
ORA-19028 Invalid ADT parameter passed to toObject() function
ORA-19029 Cannot convert the given XMLType to the required type
ORA-19030 Method invalid for non-schema based XML Documents.
ORA-19031 XML element or attribute string does not match any in type string.string
ORA-19032 Expected XML tag string got string
ORA-19033 schema specified in the XML document does not match the schema parameter
ORA-19034 Type not supported during schema generation
ORA-19200 Invalid column specification
ORA-19201 Datatype not supported
ORA-19202 Error occurred in XML processing string
ORA-19203 Error occurred in DBMS_XMLGEN processing string
ORA-19204 Non-scalar value 'string' is marked as XML attribute
ORA-19205 Attribute 'string' qualifies a non-scalar value in the select list
ORA-19206 Invalid value for query or REF CURSOR parameter
ORA-19207 scalar parameter string of XMLELEMENT cannot have an alias.
ORA-19208 parameter string of function string must be aliased
ORA-19209 invalid or unsupported formatting argument
ORA-19300 Error occurred in uri processing string
ORA-19320 Host name not specified in HTTP URL
ORA-19321 Could not open HTTP connection to host (string): port (string)
ORA-19322 An error occurred while reading from host (string): port (string)
ORA-19323 Invalid url string
ORA-19330 Type 'string'.'string' not installed. Please install the type before using the CREATE_DBURI operator
ORA-19331 Last argument to CREATE_DBURI operator must be a column
ORA-19332 Invalid column in the CREATE_DBURI operator
ORA-19333 Invalid flags for the CREATE_DBURI operator
ORA-19334 Invalid column specification for CREATE_DBURI operator
ORA-19335 Invalid format type object
ORA-19336 Missing XML root element
| Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
12
ORA-19400 to ORA-24279
-
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.
-
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.
-
Cause: Read error on input file.
-
Action: Check the file.
-
Cause: Write error on output file.
-
Action: Check the file.
-
Cause: Call to get device information returned an error.
-
Action: Check device name, type, and parameters.
-
Cause: Call to create file returned an error.
-
Action: Check additional messages and check access permissions.
-
Cause: Call to identify the file returned an error.
-
Action: Check additional messages, and check whether the file exists.
-
Cause: Call to create the sequential file returned an error.
-
Action: Check additional messages, check access permissions.
-
Cause: Call to retrieve the sequential file returned an error.
-
Action: Check additional messages, and check if the file exists.
-
Cause: Call to delete the file returned an error.
-
Action: Check additional messages.
-
Cause: Call to delete the sequential file returned an error.
-
Action: Check additional messages.
-
Cause: Call to resize the file returned an error.
-
Action: Check additional messages.
-
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.
-
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.
-
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.
-
Cause: The device type indicated is invalid.
-
Action: Supply a correct device type and retry the allocation.
-
Cause: The device name indicated is invalid.
-
Action: Supply a correct device name and retry the allocation.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A device cannot be allocated to a session if another device is already allocated.
-
Action: Deallocate the current device.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This type of copy or restore requires an output file name.
-
Action: Specify an output file name and retry the copy.
-
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.
-
Cause: The specified file number was not found in the control file.
-
Action: Specify a correct file number and retry the operation.
-
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.
-
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.
-
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.
-
Cause: A backup or restore operation was attempted before a conversation was started.
-
Action: Start a conversation then retry the operation.
-
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.
-
Cause: The archived log file header is corrupt and could not be validated.
-
Action: Provide a valid archive log file and retry the operation.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The input file name was not specified for a control file copy operation.
-
Action: Specify an input file name and retry the operation.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This backup piece is out of sequence.
-
Action: Supply the correct backup piece.
-
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.
-
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.
-
Cause: The indicated archived log file was named explicitly for restoration but is not contained in this backup set.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The name passed to getFno was not found in the control file.
-
Action: Supply a valid file name.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This message identifies the checkpoint of a datafile in an incremental backup set that could not be applied.
-
Action: See other error message.
-
Cause: This message identifies the starting SCN of an incremental backup that could not be applied.
-
Action: See other error message.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This messages identifies the offline-clean SCN from the indicated offline-range record in the indicated file.
-
Action: See other error message.
-
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.
-
Cause: The target datafile for an applyOfflineRange call is fuzzy.
-
Action: Specify a target datafile that is closed cleanly.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The configuration name string exceeds the maximum length.
-
Action: Supply a correct configuration name and retry the function.
-
Cause: The configuration value string exceeds the maximum length.
-
Action: Supply a correct configuration value and retry the operation.
-
Cause: An invalid RMAN Configuration number was specified.
-
Action: Specify a correct datafile number and retry the operation.
-
Cause: Some blocks were not recovered during block media recovery.
-
Action: See trace files for details of the problem.
-
Cause: File number 0 was specified in block media recovery.
-
Action: Check file number.
-
Cause: The block size changed between the backup & the real file.
-
Action: Use the correct backup.
-
Cause: Database is suspended, probably by an
ALTER SYSTEM SUSPENDstatement. -
Action: Execute
ALTER SYSTEM RESUMEthen retry block media recovery. -
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.
-
Cause: The device type indicated is invalid.
-
Action: Supply a correct device type and retry the allocation.
-
Cause: The device name indicated is invalid.
-
Action: Supply a correct device name and retry the allocation.
-
Cause: The device parameter exceeds the port-specific maximum length.
-
Action: Correct the parameter and retry the operation.
-
Cause: The device command string exceeds maximum length.
-
Action: Correct the command and retry the operation.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: A numeric parameter to an X$DBMS_BACKUP_RESTORE procedure is negative or contains a fractional portion.
-
Action: Supply a valid numeric parameter.
-
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.
-
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.
-
Cause: The table name string exceeds the maximum length.
-
Action: Retry the operation with a shorter table name.
-
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.
-
Cause: The specified format exceeds the maximum length for the piece name.
-
Action: Change the format to create shorter piece names.
-
Cause: A restricted format was used incorrectly.
-
Action: Change the format by removing the restricted format.
-
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.
-
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.
-
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.
-
Cause: The datafile is plugged in read only. It cannot re-created.
-
Action: Use ALTER DATABASE RENAME FILE command instead.
-
Cause: The snapshot SCN is before the SCN at which the referred datafile is plugged into the database.
-
Action: retry the query.
-
Cause: There maybe another ALTER DATABASE RESET COMPATIBILITY command issued concurrently, preventing this process from acquiring the plug-in enqueue.
-
Action: Retry the operation.
-
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.
-
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.
-
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.
-
Cause: The file is not the initial version of the plugged in datafile.
-
Action: Use the correct initial version of the plugged in datafile.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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 converted datafile.
-
Action: Either restore the initial version of the plugged-in datafile, or continue database recovery, which will recover the control file.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This function requires the OCI process to be initialized in object mode.
-
Action: Specify OCI_OBJECT mode when calling OCIInitialize().
-
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.
-
Cause: The operating system has run out of memory.
-
Action: Take action to make more memory available to the program.
-
Cause: A program is in an unrecoverable error state.
-
Action: Report to Oracle Support Services.
-
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.
-
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.
-
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.
-
Cause: User attempted to use a functionality that the server does not support.
-
Action: Upgrade the server.
-
Cause: The object type of the object is different from what is specified.
-
Action: Check the type of the object and correct it.
-
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.
-
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.
-
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.
-
Cause: The handles passed in may not be valid.
-
Action: Check the validity of the env, svc handles.
-
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.
-
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.
-
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.
-
Cause: The specified property ID is invalid.
-
Action: Specify a valid property ID. Valid property IDs are enumerated by OCIObjectPropId.
-
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.
-
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.
-
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
-
Cause: Attempt to use the handle without initializing it.
-
Action: Initialize the memory cartridge service handle.
-
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.
-
Cause: Attempt to resize memory without allocating it first.
-
Action: Allocate the memory first before resizing it.
-
Cause: Attempt to resize memory with invalid size.
-
Action: Pass in a valid size (must be a positive integer).
-
Cause: Attempt to use an invalid key length.
-
Action: Key length is invalid and valid range is 0 to 64.
-
Cause: Attempt to use a key that is already used.
-
Action: Use a new key that is not yet being used.
-
Cause: Attempt to use a non-existent key.
-
Action: Use a key that already exists.
-
Cause: Constraints on the attribute were violated.
-
Action: Correct the value (of the attribute) so that it satisfies constraints.
-
Cause: See following message.
-
Action: Check that no attribute value violates constraints.
-
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.
-
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.
-
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.
-
Cause: See the error message.
-
Action: The object should not be flushed.
-
Cause: See the error message.
-
Action: The transaction should be aborted or committed before terminating the cache or connection.
-
Cause: The service context that is supplied by the user is not valid.
-
Action: Establish the service context.
-
Cause: The duration number that is supplied by the user is not valid.
-
Action: Establish the duration or use a correct predefined 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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to use a duration that has been terminated.
-
Action: Avoid performing such operation.
-
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.
-
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.
-
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.
-
Cause: Given value is divided by zero.
-
Action: Modify divisor value to be non-zero.
-
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.
-
Cause: The buffer to hold the resulting text string is too small.
-
Action: Provide a buffer of the required size.
-
Cause: An invalid or uninitialized number was passed in.
-
Action: Use a valid number. To initialize a number, call OCINumberSetZero().
-
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.
-
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.
-
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.
-
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.
-
Cause: Rounding done due to the given string format causes overflow.
-
Action: Change the string format such that overflow does not occur.
-
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.
-
Cause: The given hexadecimal string length must be greater than zero.
-
Action: Specify a length greater than zero.
-
Cause: The given hexadecimal string is invalid.
-
Action: Provide a valid hexadecimal string which was previously returned by a call to OCIRefToHex().
-
Cause: The given resize size is invalid.
-
Action: Ensure that the given size is in the required range.
-
Cause: An un-initialized variable-length array is being operated upon.
-
Action: Initialize the variable-length array prior to calling this function.
-
Cause: An attempt was made to resize a non-zero variable-length array to 0 elements.
-
Action: Specify a non-zero size.
-
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.
-
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.
-
Cause: Collection element at the given index does not exist.
-
Action: Specify the index of an element which exists.
-
Cause: Given type code is not valid.
-
Action: Use one of the type codes enumerated in OCITypeCode.
-
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.
-
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.
-
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.
-
Cause: Given index is not in the required range.
-
Action: Ensure that the given index is in the required range.
-
Cause: Given collection is empty.
-
Action: Test if collection is empty prior to invoking this function.
-
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.
-
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.
-
Cause: One of the following:
-
Action: For (1) enable the locator for buffering; (2) ensure that only an updated locator is used for a LOB update operation.
-
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.
-
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.
-
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.
-
Cause: One of the following:
-
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.
-
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.
-
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.
-
Cause: Filename contains a path "../" which references a parent directory.
-
Action: Ensure that the filename does not contain characters which reference a parent directory.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to commit a transaction with open LOBs at transaction commit time.
-
Action: Close the LOBs before committing the 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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: An attempt was made to obtain the supertype information for a non-object type.
-
Action: Pass in only an object type.
-
Cause: Type element with the given name is not found in the type.
-
Action: Check to make sure that the type element 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.
-
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.
-
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.
-
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.
-
Cause: An invalid alter type statement was submitted.
-
Action: Correct the errors listed in the specified table and resubmit the statement.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: The VERSION option is specified without a user version string.
-
Action: Resubmit the statement with the version string following the VERSION keyword.
-
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.
-
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.
-
Cause: The error table does not exist.
-
Action: Resubmit the statement with a correct error table name.
-
Cause: The use of the ALTER TYPE statement caused a compilation error.
-
Action: Correct the error reported and resubmit the statement.
-
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.
-
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.
-
Cause: Altering the target type causes errors in its dependent object.
-
Action: Correct the problem in the dependent object and resubmit the statement.
-
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.
-
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.
-
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.
-
Cause: Altering the target type causes errors in its dependent object.
-
Action: Correct the problem in the dependent object and resubmit the statement.
-
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.
-
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.
-
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.
-
Cause: One of the following:
-
Action: Resubmit the statement with the INCLUDING DATA option.
-
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.
-
Cause: An attempt was made to alter the final property of a type with dependent tables without specifying the
CASCADE INCLUDING DATAoption. -
Action: Resubmit the statement with the
CASCADE INCLUDING DATAoption. -
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 TYPEstatement. -
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 DATAstatement to upgrade the data in the dependent tables then resubmit the statement. -
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.
-
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.
-
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.
-
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.
-
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.
-
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.
-
Cause: This method of SYS.AnyType, SYS.AnyData, or SYS.AnyDataSet is being used inappropriately.
-
Action: Check the documentation for correct usage.
-
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.
-
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.
-
Cause: An attempt was made to use the pickler TDS context without initializing it.
-
Action: Use OCIPicklerTdsCtxInit to initialize the context.
-
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.
-
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.
-
Cause: An attempt was made to generate TDS that is already generated.
-
Action: Use a TDS handle that is initialized but not yet generated.
-
Cause: An attempt was made to use an uninitialized FDO handle.
-
Action: Use OCIPicklerFdoInit to initialize FDO handle.
-
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.
-
Cause: An attempt was made to generate image that is already generated.
-
Action: Use a image handle that is initialized but not yet generated.
-
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.
-
Cause: An error occurred during FDO initialization.
-
Action: Take an action based on the specified error.
-
Cause: An error occurred while adding a scalar attribute to the image handle.
-
Action: Make sure image handle is initialized before adding scalar.
-
Cause: Incorrect TDS handle is passed.
-
Action: Make sure image handle is initialized with the correct 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.
-
Cause: BUFLEN is incorrect.
-
Action: Make sure BUFLEN is correct and matches the size of the scalar.
-
Cause: An error occurred during the construction of collection.
-
Action: Make sure image handle is initialized and OCIPicklerImageCollBegin is called to begin collection.
-
Cause: Collection routine is invoked upon a non-collection attribute.
-
Action: Make sure attribute is a collection.
-
Cause: The function being invoked is applicable only for 8.1 images.
-
Action: Make sure image is of 8.1 format.
-
Cause: An error occurred while accessing collection in the image handle.
-
Action: Make sure image is initialized correctly and the collection is constructed properly.
-
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.
-
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.
-
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.
-
Cause: An error was returned from the pickler routines on the agent side.
-
Action: Contact Oracle Support Services.
-
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.
-
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.
-
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
-
Cause: Attempt to add attributes to OCIAnyData that is already constructed.
-
Action: Use the OCIAnyData that is initialized but not yet constructed.
-
Cause: Attempting an operation that is not valid on null OCIAnyData.
-
Action: Make sure OCIAnyData is not null.
-
Cause: Passing an attribute that is null or not well-formed.
-
Action: Make sure the attribute is not null or is well-formed.
-
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.
-
Cause: The AnyDataSet parameter is null or invalid for the current operation.
-
Action: Check the documentation for the current operation.
-
Cause: AnyDataSet that is passed in may not be valid.
-
Action: Check all the AnyDataSet parameters.
-
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.
-
Cause: An attempt was made to use an incomplete type as a constructor.
-
Action: Complete the type definition before using it in a query.
-
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.
-
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.
-
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.
-
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 are NULL.
-
Cause: An attempt was made to extract an attribute from an item that is neither an object nor a REF.
-
Action: Use an object type or REF type item and retry the operation.
-
Cause: Invalid use of a non-scalar (for example, object type) item.
-
Action: Change the item's data type and retry the operation.
-
Cause: An attempt was made to access an object type's attributes by de-referencing a REF item.
-
Action: Make the item an object type instead of a REF to an object type.
-
Cause: An attempt was made to access a non-existent attribute of an object type.
-
Action: Check the attribute reference to see if it is valid. Then retry the operation.
-
Cause: An attempt was made to modify the attributes an object by de-referencing a REF column in an UPDATE statement.
-
Action: Update the table containing the object that the REF points to, or change the REF column to an object type column.
-
Cause: An attempt to access the nested table column's storage table is not allowed in the given context.
-
Action: Issue the statement against the parent table containing the nested table column.
-
Cause: Object or Collection value was too large. The size of the value might have exceeded 30k in a SORT context, or the size might be too big for available memory.
-
Action: Choose another value and retry the operation.
-
Cause: Value provided for the object type attribute or collection element exceeded the size specified in the type declaration.
-
Action: Choose another value and retry the operation.
-
Cause: RETURNING clause is currently not supported for object type columns, LONG columns, remote tables, INSERT with subquery, and dereferencing inside returning clause.
-
Action: Use separate SELECT statements to get the values.
-
Cause: An attempt was made to use a subquery in the column default clause expression.
-
Action: Remove the subquery from the default clause.
-
Cause: An attempt was made to use a subquery expression where these are not supported.
-
Action: Rewrite the statement without the subquery expression.
-
Cause: An attempt was made to operate on a REF value scoped to a different table than the expected one.
-
Action: Use a REF which is scoped to the expected table and retry the operation.
-
Cause: An attempt was made to use a non instantiable type as a constructor.
-
Action: None.
-
Cause: Value provided for the pattern or replacement string in the form of
VARCHAR2orCLOBfor LOB SQL functions exceeded the 32K size limit. -
Action: Use a shorter pattern or process a long pattern string in multiple passes.
-
Cause: A LOB storage option (CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX) was specified more than once.
-
Action: Specify all LOB storage options only once.
-
Cause: The specified CHUNK LOB storage option value must be an integer.
-
Action: Choose an appropriate integer value and retry the operation.
-
Cause: The specified PCTVERSION LOB storage option value must be an integer.
-
Action: Choose an appropriate integer value and retry the operation.
-
Cause: A LOB storage option was not specified.
-
Action: Specify one of CHUNK, PCTVERSION, CACHE, NOCACHE, TABLESPACE, STORAGE, INDEX as part of the LOB storage clause.
-
Cause: A valid LOB store index option was not specified.
-
Action: Specify one of (INITTRANS, MAXTRANS, TABLESPACE, STORAGE) as part of the LOB storage index.
-
Cause: The optional name for LOB storage segment was specified with multiple columns in the column list.
-
Action: Specify each column LOB storage only with optional name(s).
-
Cause: An attempt was made to add columns to an object table. Object tables cannot be altered to add columns since its definition is based on an object type.
-
Action: Create a new type with additional attributes, and use the new type to create an object table. The new object table will have the desired columns.
-
Cause: An attempt was made to alter the object table by modifying existing columns. An object table cannot be altered to modify existing columns since it is based on an object type. The table definition must be in sync with the corresponding type.
-
Action: Create a new type with the desired attribute types and use it to create an object table. The new object table will have the desired columns.
-
Cause: An attempt was made to modify the column type to object, REF, nested table, VARRAY or LOB type.
-
Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor.
-
Cause: An attempt was made to modify an object, REF, VARRAY, nested table, or LOB column type.
-
Action: Create a new column of the desired type and copy the current column data to the new type using the appropriate type constructor.
-
Cause: An attempt was made to create an object table using a non- object type, or to create a column that is a REF to a non-object type.
-
Action: Use a valid object type in the table or column definition.
-
Cause: An attempt was made to create a column or object table of a non-existent type.
-
Action: Specify a valid type in the table or column definition.
-
Cause: An attempt was made to specify an object identifier for the type that does not match the existing identifier of the incomplete type of the same name.
-
Action: Specify the correct object identifier or leave it out of the statement.
-
Cause: A synonym specification for a datatype is not supported.
-
Action: Do not use the synonym for the datatype.
-
Cause: An attempt was made to ALTER or DROP a LOB index.
-
Action: Do not operate directly on the system-defined LOB index. Perform operations on the corresponding LOB column.
-
Cause: An attempt was made to specify multiple columns where only one is allowed.
-
Action: Specify a single column and retry the operation.
-
Cause: A character LOB was defined but the default character set is not fixed width.
-
Action: Ensure that the character set is of fixed width before defining character LOBs.
-
Cause: An attempt was made to drop a tablespace which contains the segment(s) for the LOB columns of a table but does not contain the table segment.
-
Action: Find table(s) with LOB columns which have non-table segments in this tablespace. Drop these tables and reissue drop tablespace.
-
Cause: The type dependency hierarchy was structured to have depth greater than 1024.
-
Action: Restructure the type dependency hierarchy to a shorter depth.
-
Cause: An attempt was made to perform ALTER TYPE with REPLACE option a non-object type.
-
Action: Drop the non-object type first, then re-create it as an object type.
-
Cause: An attempt was made to perform ALTER TYPE with REPLACE option for a pure incomplete type.
-
Action: Completely define the original type, before using the ALTER TYPE with REPLACE option.
-
Cause: An attempt was made to create an OID INDEX on a table with primary key-based object identifiers.
-
Action: Remove the OID INDEX clause.
-
Cause: An attempt was made to create a primary key based object table without specifying a primary key.
-
Action: Specify a primary key and retry the operation.
-
Cause: Attribute specified in the USER_DEFINED clause is not an attribute of the REF type.
-
Action: Ensure that the name specified in the USER_DEFINED clause is the name of a valid attribute of the REF type.
-
Cause: An attempt was made to drop the primary key of an object table which has a primary key based object identifier.
-
Action: Remove the drop primary key clause.
-
Cause: An attempt was made to create a kind of user-defined type which is not allowed, or an attempt to create table columns or use default constructor with a type on which these are not supported.
-
Action: Ensure that the type is permitted in this context.
-
Cause: One or more invalid options were encountered while parsing the physical attributes of a LOB partition or subpartition. Either the LOB partition is in a table partitioned using the HASH method, or the LOB subpartition is in a table subpartitioned using the HASH method. TABLESPACE is the only valid option for a HASH partition or subpartition.
-
Action: Remove the invalid option(s).
-
Cause: An attempt was made was made to specify a partition or subpartition that has already been specified for the LOB column.
-
Action: Remove the duplicate specification.
-
Cause: An attempt was made to specify a LOB INDEX clause in a CREATE TABLE or ALTER TABLE statement for a partitioned table.
-
Action: Remove the LOB INDEX clause.
-
Cause: An invalid REF was accessed.
-
Action: Modify the REF and retry the operation.
-
Cause: The object corresponding to the REF that was accessed does not exist.
-
Action: Ensure that the REF value is pointing to an existing object.
-
Cause: The object cannot be created in the database.
-
Action: Check to see if the object table exists and the object size is not too big. Then retry the operation.
-
Cause: The object could not be deleted from the database.
-
Action: Check to see if the object table exists. Then retry the operation.
-
Cause: The object could not be modified in the database.
-
Action: Check to see if the object table exists and the object size is not too big. Then retry the operation.
-
Cause: An attempt was made to get a REF for something other than an object in an object table. REFs can only be taken for objects in object tables.
-
Action: Rewrite the query to obtain REF values from object tables.
-
Cause: The scoped table specified for a REF column is not an object table.
-
Action: Ensure that the scoped table is an object table. Then retry the operation.
-
Cause: The type specified for the REF column and the type specified for the scope table are different.
-
Action: Ensure that the types of a REF column and its scoped table are the same.
-
Cause: Multiple SCOPE clauses were specified for a single REF column.
-
Action: Remove the duplicate SCOPE clauses and retry the operation.
-
Cause: An attempt was made to insert a REF value that does not point to the scoped table.
-
Action: Ensure that the REF values point to the scoped table.
-
Cause: An attempt was made to specify a constraint name for a constraint on a REF column.
-
Action: Remove the constraint name and retry the operation.
-
Cause: An attempt was made to specify multiple columns in a single REF constraint.
-
Action: Specify separate constraints for each column and retry the operation.
-
Cause: The scoped table specified for a REF column does not exist.
-
Action: Ensure that the scoped table exists and retry the operation.
-
Cause: The constraint specified does not apply to non-REF columns.
-
Action: Remove the constraint and retry the operation.
-
Cause: An attempt was made to add a constraint to existing unscoped REF columns of a table which contains one or more rows.
-
Action: Remove the constraint specification or add the constraint after emptying the table.
-
Cause: The referenced table specified for a REF column is not an object table.
-
Action: Ensure that the referenced table is an object table. Then retry the operation.
-
Cause: REF column has both a referential and a scope constraint. A referential constraint implies a scope constraint.
-
Action: Remove either the referential or scope constraint and then retry the operation.
-
Cause: User-defined REF column does not have a scope constraint.
-
Action: Specify a scope constraint for the user-defined REF column and retry the operation.
-
Cause: Table mentioned in the referential integrity constraint is different from the scope table of the REF column.
-
Action: Specify the scope table of the REF column in the referential integrity constraint and then retry the operation.
-
Cause: An attempt was made to specify both a scope and a ROWID constraint on a REF column.
-
Action: Remove either the ROWID or scope constraint and then retry the operation.
-
Cause: The THE subquery must SELECT a nested table or VARRAY item.
-
Action: Change the subquery to SELECT a nested table or VARRAY item.
-
Cause: Comparison of nested table or VARRAY or LOB attributes of an object type was attempted in the absence of a MAP or ORDER method.
-
Action: Define a MAP or ORDER method for the object type.
-
Cause: CURSOR on a subquery is allowed only in the top-level SELECT list of a query.
-
Action: Remove the CURSOR expression and retry the operation.
-
Cause: MULTISET expressions are allowed only inside a CAST to a nested table or VARRAY type.
-
Action: put the MULTISET (subquery) expression inside a CAST to a nested table or VARRAY type.
-
Cause: An invalid reference was made to a nested table column.
-
Action: Remove invalid reference to the nested table column and retry the operation.
-
Cause: An attempt was made to access rows of an item whose type is not known at parse time or that is not of a nested table type.
-
Action: Use CAST to cast the item to a nested table type.
-
Cause: An attempt was made to perform a DML on an expression or on a nested table view column where a nested table column of a base table is expected.
-
Action: Only nested table column of a base table is allowed in the DML.
-
Cause: An attempt was made to CAST to a type that is not a nested table or VARRAY.
-
Action: Respecify CAST to a nested table or VARRAY type.
-
Cause: The evaluation of the THE subquery or nested table column resulted in a NULL value implying a NULL table instance. The THE subquery or nested table column must identify a single non-NULL table instance.
-
Action: Ensure that the evaluation of the THE subquery or nested table column results in a single non-null table instance. If happening in the context of an INSERT statement where the THE subquery is the target of an insert, then ensure that an empty nested table instance is created by updating the nested table column of the parent table's row specifying an empty nested table constructor.
-
Cause: The total number of elements used in VARRAY construction exceeds the specified VARRAY limit.
-
Action: Do not use the more than the specified limit of elements for VARRAY construction.
-
Cause: Table name was qualified with schema name in the nested table column's (or attribute's) storage clause.
-
Action: Respecify the nested table item's storage clause without the schema name qualification. By default, the storage table for the nested table item is created in the same schema as the containing table.
-
Cause: The storage clause is specified more than once for the NESTED TABLE column.
-
Action: Remove the duplicate storage specification.
-
Cause: The storage clause is specified for a column or attribute that is not a nested table column or attribute.
-
Action: Specify a valid nested table column or attribute.
-
Cause: The storage clause is not specified for a nested table column or attribute.
-
Action: Specify the nested table storage clause for the nested table column or attribute.
-
Cause: An attempt was made to DROP a nested table.
-
Action: Nested tables cannot be explicitly dropped. nested tables can only be dropped by dropping their containing parent table.
-
Cause: An attempt was made to ADD or MODIFY columns of a nested table. Columns cannot be added or modified for a nested table.
-
Action: Instead, alter the parent table's nested table column to cause any such change.
-
Cause: Exact FETCH on a query was specified which is not allowed if the query returns any cursors.
-
Action: Do not use an exact FETCH.
-
Cause: Not using VARRAY to define storage clause for VARRAY column or attribute.
-
Action: Specify VARRAY before the column storage clause and resubmit the statement.
-
Cause: An attempt was made to define a VARRAY storage clause for a column or attribute which is not VARRAY type.
-
Action: Specify VARRAY storage clause for a VARRAY column or attribute.
-
Cause: The error could be one of the following: the object corresponding to the REF does not exist or the object was locked by another user and the lock with nowait request failed.
-
Action: Ensure that the REF value is pointing to an existing object or issue a lock request without the nowait option.
-
Cause: The row containing the LOB value must be locked before updating the LOB value.
-
Action: Lock the row containing the LOB value before updating the LOB value.
-
Cause: The buffer length is not big enough to hold the amount of data requested.
-
Action: Verify that the number of bytes/characters specified in the input amount parameter is not bigger than the number of bytes specified in the input buffer length parameter. Allocate more space for the input buffer if necessary.
-
Cause: The LOB value associated with the input locator does not exist. The information in the locator does not refer to an existing LOB.
-
Action: Repopulate the locator by issuing a SELECT statement and retry the operation.
-
Cause: An attempt was made to write LOB value via the streaming mechanism (that is, unlimited write) but the input amount of data to stream was specified as 0. Thus, the user is trying to write 0 bytes to the LOB value.
-
Action: Write more than 0 bytes to the LOB value.
-
Cause: The version of the LOB value needed for the consistent read was already overwritten by another writer.
-
Action: Use a larger version pool.
-
Cause: An attempt was made to write too much data to the LOB value. LOB size is limited to 4 gigabytes.
-
Action: Either start writing at a smaller LOB offset or write less data to the LOB value.
-
Cause: The input length for which to trim the LOB value to is greater than the current length of the LOB value.
-
Action: May not need to trim the LOB value because it's already smaller than the trim length specified. Or, if trimming the LOB value really is required, use a smaller trim length.
-
Cause: One of the following:
-
Action: For (1), initialize the LOB locator by selecting into the locator variable or by setting the LOB locator to empty. For (2) and (3), pass the correct type of locator into the routine. For (4), remove the trigger body code that updates the LOB value.
-
Cause: An attempt was made to grant or revoke an invalid privilege on a directory.
-
Action: Only CREATE, DELETE, READ and WRITE privileges can be granted or revoked on directories. Do not grant or revoke other privileges.
-
Cause: The required directory name is invalid or missing.
-
Action: Specify a valid name.
-
Cause: An attempt was made to access a directory that does not exist.
-
Action: Make sure the name is correct.
-
Cause: An attempt was made to move a nested table to a different tablespace.
-
Action: Nested tables always collocate in the same tablespace as the parent. A nested table can be moved to a different tablespace only by moving its containing table to the target tablespace.
-
Cause: An attempt was made to replace, drop, or rename an object with type or table dependents.
-
Action: Drop depending objects or use FORCE option if available.
-
Cause: An object type must have a MAP or ORDER method defined for all comparisons other than equality and inequality comparisons.
-
Action: Define a MAP or ORDER method for the object type.
-
Cause: ORDER method used to compare two object values returned NULL which is not allowed.
-
Action: Redefine the ORDER method to not return a NULL.
-
Cause: Either the expression is not a view name or the name specified does not correspond to an object view.
-
Action: Replace the expression with the name of an object view.
-
Cause: When creating an object view, the datatype of an expression in the WITH OBJECT OID clause is not allowed for PRIMARY KEY-based OID.
-
Action: Replace the expression with one of appropriate scalar datatype.
-
Cause: A value constituting the PRIMARY KEY-based object identifier is NULL.
-
Action: Ensure the expressions in MAKE_REF system function or attributes in the WITH OBJECT OID clause of an object view do not evaluate to NULL.
-
Cause: Size of the PRIMARY KEY-based object identifier of an object view exceeded the maximum size of 1000 bytes.
-
Action: Specify fewer or smaller PRIMARY KEY attributes in the WITH object OID clause when creating the object view.
-
Cause: WITH OBJECT OID clause was not specified when creating an object view.
-
Action: Specify the WITH OBJECT OID clause.
-
Cause: The object view specified in the MAKE_REF function does not have a PRIMARY KEY-based object identifier. A PRIMARY KEY-based REF cannot be created for such a view.
-
Action: Specify an object view that has a PRIMARY KEY-based object identifier in the MAKE_REF function.
-
Cause: Number of arguments for MAKE_REF is different from the number of PRIMARY KEY attributes of the object view.
-
Action: Specify all the necessary arguments for MAKE_REF.
-
Cause: Either the attribute name is missing in the WITH OBJECT OID clause or it is invalid.
-
Action: Specify a valid attribute of the object type of the object view.
-
Cause: An attempt was made to specify a Nested attribute in the WITH OBJECT OID clause.
-
Action: Specify a top-level attribute of the object type of the object view.
-
Cause: An attempt was made to insert an object view REF or user-defined REF in a REF column created to store system generated REF values.
-
Action: Make sure the REF to be inserted is not from an object view or from a user-defined REF column
-
Cause: The WITH OBJECT OID DEFAULT clause was used, but the underlying view or table does not have a OID.
-
Action: Specify attributes for the WITH OBJECT OID clause to create a primary key based object identifier for the object view.
-
Cause: The super-view is based on a table/view having the system generated OID and the sub-view must also be based on a similar table/view.
-
Action: Specify a table/view having the system generated OID and retry the operation.
-
Cause: The view derives its OID from a table/view having primary key based OID and sub-views cannot be created under such views.
-
Action: Specify a view having the system generated OID or a view created with the specification of attributes in the WITH OBJECT ID clause and retry the operation.
-
Cause: Attempt to use a system generated REF value where a user-defined REF value should be used.
-
Action: Make sure the REF value is user-defined.
-
Cause: The query defining the view contains references to a super-view of the view being created.
-
Action: Make sure that the view query does not reference a super-view.
-
Cause: A LOB locator selected in one transaction cannot be used in a different transaction.
-
Action: Reselect the LOB locator and retry the operation.
-
Cause: The data to be returned in the argument is greater than the amount of space allocated for the argument.
-
Action: Allocate more space for the argument.
-
Cause: A remote LOB column cannot be referenced.
-
Action: Remove references to LOBs in remote tables.
-
Cause:
-
Action: (1) will happen when using OCI's piecewise mechanism with polling or with a callback function. Modify the code either to send the amount specified or to pass 0 as the input amount so that any amount of data can be sent. (2) will happen if the specified input amount is too large for the source LOB/FILE given the starting source offset. Either decrease the starting source offset, or decrease the amount to copy/load.
-
Cause: The source offset for a LOB COPY or LOB LOADFROMFILE is beyond the end of the source LOB.
-
Action: Check the length of the LOB and then adjust the source offset.
-
Cause: TABLESPACE DEFAULT option can be specified for LOB columns only in the following contexts:
An attempt was made to use the TABLESPACE DEFAULT option in a different context.
-
Action: Remove the TABLESPACE DEFAULT option.
-
Cause: An attempt was made to create or alter a LOB segment so that its NEXT extent size was less than the LOB chunk size.
-
Action: Specify a NEXT extent size that is greater than or equal to the LOB chunk size.
-
Cause: An attempt was made to specify a VARRAY|OPAQUE column to be stored as LOB at the partition/subpartition/template level. However, the VARRAY|OPAQUE column was not specified to be stored as LOB at the table level when the table was created.
-
Action: Specify the VARRAY | OPAQUE column to be stored as LOB at the table level when the table is created. Alternatively, do not specify the VARRAY | OPAQUE column to be stored as LOB at the partition/subpartition/template level if it is not specified at the table level when the table is created.
-
Cause: A CLOB or NCLOB in a fixed-width or varying-width multibyte character set was passed to a SQL character function which does not support multibyte LOB data.
-
Action: Use DBMS_LOB functions such as DBMS_LOB.INSTR() and DBMS_LOB.SUBSTR() or use PLSQL DBMS_LOB.READ/WRITE to access LOB data.
-
Cause: An
ALTER TABLE RENAME [COLUMN | CONSTRAINT]operation was given in conjunction with anotherALTER TABLEOperation. This is not allowed. -
Action: Ensure that
RENAME COLUMN/RENAME CONSTRAINTis the only operation specified in theALTER TABLEstatement. -
Cause: An attempt was made to rename a column of a non-base table, such as an object table, nested table, or materialized view table. This is not allowed.
-
Action: No action required.
-
Cause: The given constraint name does not exist.
-
Action: Give an existing constraint's name.
-
Cause: The column participates in a join index.
-
Action: If you need to rename the column, then you need to drop the join index.
-
Cause: The stored procedure RAISE_SYSTEM_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.
-
Cause: Replication catalog determined deferred RPC destinations were mixed with destination determined by other mechanisms in the same transaction.
-
Action: Do not mix destination types in the same transaction.
-
Cause: An application declared a communication failure during a deferred RPC.
-
Action: Retry the application when communication is restored.
-
Cause: An application declared a generic failure during a deferred RPC.
-
Action: Determined by the application.
-
Cause: A deferred RPC call was issued without the correct number of arguments as determined by the count parameter to DBMS_DEFER.CALL.
-
Action: Be sure the number of arguments matches the count.
-
Cause: An internal error occurred in deferred RPC.
-
Action: Report the error and other information to support.
-
Cause: The schema name was null or misspelled, or the schema does not exist locally.
-
Action: Specify the schema correctly, or create it with CREATE USER.
-
Cause: The given database already replicates the given schema.
-
Action: Choose a different schema or a different database.
-
Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status.
-
Action: Ensure the object is valid in the database, is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT.
-
Cause: An object in the same name space exists, perhaps with a different type or shape, or the same object has already been registered as an REPOBJECT in another object group.
-
Action: Remove the offending object with the SQL DROP command, unregister the offending object with DBMS_REPCAT.DROP_MASTER_REPOBJECT(), or reinvoke the request using TRUE for a boolean parameter such as retry or USE_EXISTING_OBJECT.
-
Cause: The requested operation requires the object group to be suspended.
-
Action: Invoke SUSPEND_MASTER_ACTIVITY at the REPGROUP's MASTERDEF, wait until the status has changed to quiesced, and then retry the original request.
-
Cause: The group name is null, the group name is misspelled, the invocation or given database is not the MASTERDEF, or one of the masters does not believe the invocation database is the MASTERDEF.
-
Action: If the given group name and MASTERDEF were both correct, connect to the MASTERDEF and retry the request, or relocate the MASTERDEF at the (errant) databases using RELOCATE_MASTERDEF.
-
Cause: The group name is null, the group name is misspelled, the invocation database is not a master, or the invocation database does not believe the given database is a master.
-
Action: If the given group name was correct, connect to a current master and retry the request, make the invocation database a master with ADD_MASTER_DATABASE, or use SWITCH_MVIEW_MASTER if the invocation database is a materialized view site.
-
Cause: The invocation database is not a snapshot database for the given object group.
-
Action: Connect to the desired materialized view database and retry the request, or make the invocation database a materialized view site with CREATE_MVIEW_REPSCHEMA or CREATE_MVIEW_REPGROUP.
-
Cause: Either incompatible REPCAT versions are used, or a REPCATLOG record has been corrupted.
-
Action: Convert the master to a compatible version of REPCAT or retry the request.
-
Cause: The requested operation is not permitted on a MASTERDEF site.
-
Action: Relocate the MASTERDEF to another master and retry the operation.
-
Cause: The remote database is inaccessible.
-
Action: Ensure the remote database is running, the communications network is functioning, and the appropriate database links are present.
-
Cause: User-supplied or system-generated DDL did not execute successfully.
-
Action: Examine DDL, database state, REPCATLOG, and ALL_ERRORS to determine why the failure occurred.
-
Cause: The given value of a parameter is either null, misspelled, or not supported.
-
Action: Refer to the documentation and use parameter values that are appropriate for the given situation.
-
Cause: A missing DDL record for a REPCATLOG record, or inconsistency in REPCAT views.
-
Action: Retry the request, or make the views consistent.
-
Cause: You called DBMS_PIPE with a null pipe name.
-
Action: Find out the name of the pipe and call function with non-null pipe name.
-
Cause: You either tried to create a pipe that already existed and belonged to someone else, or remove a pipe that you were not authorized to use, or put a message into a pipe that you were not authorized for, or get a message from a pipe that you were not authorized for.
-
Action: You may have to use a different pipe name.
-
Cause: A deferred RPC parameter was longer than the deferred RPC limits of 4000 bytes for char/varchar2 parameters and 2000 bytes for raw parameters.
-
Action: Use smaller parameters.
-
Cause: The given error was encountered while attempting to create a DEFERROR entry for the give error code and the give database.
-
Action: Correct the cause of the given error.
-
Cause: A conflict resolution priority function was given a type different than the type assigned to the priority group; or the priority group has no type assigned or a function; or DBMS_DEFER_SYS_QUERY was called to retrieve a deferred RPC parameter from the deferred RPC queue, but the type of the parameter does not match the return type of the function.
-
Action: Use the function corresponding to the parameter type.
-
Cause: Either SUSPEND_MASTER_ACTIVITY has been called before the object group has resumed normal operation or a (deferred) RPC operation was attempted while the object group was quiesced.
-
Action: If SUSPEND_MASTER_ACTIVITY has been called and a RESUME_MASTER_ACTIVITY request is pending, wait until it completes, and then reinvoke SUSPEND_MASTER_ACTIVITY. Otherwise, resume database activity with the RESUME_MASTER_ACTIVITY call.
-
Cause: Deferred RPC queues were imported from a database with a different global name or operating system than importing database.
-
Action: Deferred RPC data should only be imported into a database with the same global name and hardware and operating system.
-
Cause: When creating a materialized view through REPCAT, the materialized view base table name did not match a replicated table name at the master.
-
Action: Change the materialized view DDL to use the same base table as the replicated table name at the master.
-
Cause: The DDL provided by the user to create a materialized view was executed without error, but materialized view does not exist.
-
Action: Manually back-out the DDL, and reregister with matching DDL and materialized view.
-
Cause: The column group was already registered in the object group.
-
Action: Use a column group name not yet registered in the replicated object group.
-
Cause: The given column group is either null, misspelled or not registered.
-
Action: Use a registered column group.
-
Cause: The given column group or priority group is being used to resolve conflicts.
-
Action: Call DBMS_REPCAT procedures DROP_UPDATE_RESOLUTION, DROP_DELETE_RESOLUTION, DROP_UNIQUE_RESOLUTION so that the column group or priority group is no longer in use before dropping.
-
Cause: An attempt was made to add a column to a column group when the column was already a member of a column group.
-
Action: Drop the column from its existing column group before trying to add it to another.
-
Cause: The given column is either null, misspelled or is not part of the given table or column group.
-
Action: Use a column that is a member of the table or column group.
-
Cause: The priority group was already registered in the object group.
-
Action: Use a column group name not yet registered in the object group.
-
Cause: The priority group was already registered in the object group.
-
Action: Use a priority group name not yet registered in the object group.
-
Cause: The specified value or priority has not been registered as part of the priority group.
-
Action: Either specify a different value or priority that is already part of the priority group, or add the value to the priority group.
-
Cause: The specified value or priority has already been registered as part of the priority group.
-
Action: Either specify a different value or priority that not already part of the priority group, or drop the value to the priority group.
-
Cause: The specified combination of column group, sequence, conflict type and/or parameter table name, parameter column name, and parameter sequence number has already been registered.
-
Action: Verify that additional conflict resolution information needs to be added and provide a new sequence number. If modifying existing information, the existing information must be dropped first.
-
Cause: User function is specified when conflict resolution method was not "USER FUNCTION" or specified resolution method is not one of the predefined methods.
-
Action: If user function is specified when conflict resolution method was not "USER FUNCTION", either reregister function with method as "USER FUNCTION" or specify a NULL user function. Otherwise, specify one of the documented supported conflict resolution methods.
-
Cause: A NULL user function was specified for the "USER FUNCTION" method.
-
Action: Provide user function name (for example, "schema"."package"."function") that conforms to the documented user function specifications or specify one of the documented supported conflict resolution methods.
-
Cause: The parameter column name is null or misspelled, the invocation database is not a master, or is of the wrong type for the specified conflict resolution method.
-
Action: Specify a parameter column from the specified column group that has a correct type for the conflict resolution method.
-
Cause: The specified combination of column group, sequence, conflict type has not been registered (for example, for adding a comment).
-
Action: Specify a combination of column group, sequence, conflict type has been registered.
-
Cause: A null, misspelled or non-existent constraint was specified when registering a uniqueness conflict.
-
Action: Register a named constraint for the specified table.
-
Cause: A procedure that deals with conflict resolution statistics-gathering was called for a table that was not registered to collect statistics.
-
Action: Call DBMS_REPCAT.REGISTER_STATISTICS to register the table.
-
Cause: An attempt was made to generate replication support for a table or materialized view without a primary key (as defined by a constraint or
DBMS_REPCAT.SET_COLUMNS) or an object ID. -
Action: For a table, add a primary key constraint or define a primary key using
DBMS_REPCAT.SET_COLUMNSor use object tables. For a ROWID materialized view, set min_communication to false or use primary key or object ID materialized views. -
Cause: The table has a column whose datatype is not supported by REPCAT.
-
Action: Remove the column from the table, or alter the column to have one of the supported datatypes.
-
Cause: An attempt was made to generate replication support for a package that has a procedure with OUT or IN OUT parameters.
-
Action: Remove the procedure from the package, or remove the OUT or IN OUT parameters from the procedure.
-
Cause: An attempt was made to generate replication support for a package that has a public function, or for a standalone function.
-
Action: Remove the public function from the package, or alter the function to be a procedure.
-
Cause: This usually occurs when trying to resolve conflicts in a table while concurrent updates to the same row create more conflicts.
-
Action: Re-execute the deferred transaction from DefError using DBMS_DEFER_SYS.EXECUTE_ERROR.
-
Cause: The procedure has a parameter whose datatype is not supported by REPCAT.
-
Action: Remove the parameter from the procedure, or alter the parameter to have one of the supported datatypes.
-
Cause: A duplicate destination was specified for a deferred transaction either in a DBMS_DEFER.CALL call or an earlier DBMS_DEFER.TRANSACTION call or a dbms_defer_sys.add_default_dest call.
-
Action: Remove the duplicate entry.
-
Cause: The requested action cannot be performed until the queue is empty for the given object group.
-
Action: Use DBMS_DEFER_SYS.EXECUTE or DBMS_DEFER_SYS.DELETE_TRAN to empty the queue.
-
Cause: Deferred RPC cannot be executed at the destination with the specified catchup value because their propagation has been disabled.
-
Action: Enable deferred RPC execution with the DBMS_DEFER_SYS.SET_DISABLED call.
-
Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object at the master site, or the object does not exist as a replicated object with the appropriate status.
-
Action: Ensure the object is valid in the master database, and is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT.
-
Cause: Possibly DROP_MASTER_REPGROUP was run at a master site but REMOVE_MASTER_DATABASES was not run at master definition site for that master.
-
Action: Run REMOVE_MASTER_DATABASES from master definition site to remove the appropriate master (see associated error messages).
-
Cause: The propagator does not exist.
-
Action: Register a new propagator.
-
Cause: The local user does not match the remote user connected via a database link.
-
Action: Drop and re-create the identified database link with the connect-to user identical to the owner of the database link.
-
Cause: The USERID in the REPCATLOG record does not match the USERID of the connected user.
-
Action: Retry the operation with a different user.
-
Cause: An attempt was made to create more than one materialized view on a given master table in the same rep group.
-
Action: Create these other materialized views in a different rep group at another site.
-
Cause: The materialized view does not exist at the master site for offline instantiation of the materialized view.
-
Action: The correct procedure is to create the materialized view in a different schema at the master site, and then follow the instructions for offline instantiation of materialized views.
-
Cause: The given user does not exist.
-
Action: Enter the name of a valid user and retry the operation.
-
Cause: The name of the base table of the materialized view at the master site is different from the base table at the materialized view site. This error may arise during offline instantiation of materialized views.
-
Action: Retry offline instantiation with a materialized view name less than 24 bytes.
-
Cause: The Advanced Replication feature is not enabled at this site. Updatable materialized views, deferred RPCs, and other replication features are, therefore, unavailable.
-
Action: Do not attempt to use this feature. Contact Oracle Support Services if the Advanced Replication feature has been purchased but not enabled.
-
Cause: site specified in argument REFERENCE_SITE or argument COMPARISON_SITE in call to DIFFERENCES() routine or RECTIFY() routine does not name an existing site.
-
Action: Make sure that database sites specified really do exist, and rerun the routine.
-
Cause: Value of argument MAX_MISSING to routine DIFFERENCES() cannot be less than 1. Value of argument COMMIT_ROWS to routines DIFFERENCES() and RECTIFY() cannot be less than 1.
-
Action: Choose an integer value for those arguments to be 1 or greater.
-
Cause: Table specified in argument "oname1" or "oname2" in call to "differences()" routine does not contain either a primary key or a virtual primary key (defined through DBMS_REPCAT package under symmetric replication).
-
Action: Make sure the tables specified have a primary key defined.
-
Cause: Argument SNAME1, SNAME2, ONAME1, ONAME2, MISSING_ROWS_SNAME, MISSING_ROWS_ONAME1, MISSING_ROWS_ONAME2 to DIFFERENCES() or RECTIFY() cannot be NULL or '' (empty string).
-
Action: Change argument to non-null or non-empty string.
-
Cause: Argument MAX_MISSING to DIFFERENCES() routine cannot be NULL.
-
Action: Legal values for MAX_MISSING are integers 1 or greater.
-
Cause: The tables specified are not shape equivalent, which means intuitively that the number of columns, the names, their datatypes and lengths are not the same. Specifically, problem is in the parentheses and is one of the following: the number of columns are not equal, datatypes of columns with same name in different tables are different, lengths of varchar2 and char columns are not equal, precision and scale of number datatypes are not equal.
-
Action: Make sure the two tables being compared have the same number of columns, same column names, and same datatypes.
-
Cause: Some column in ARRAY_COLUMNS argument (or COLUMN_LIST argument) to DIFFERENCES() routine does not correspond to a column in the specified table.
-
Action: Make sure that all the columns in either ARRAY_COLUMNS or COLUMN_LIST are present in the specified table.
-
Cause: Certain types in the table comparison utility are not supported.
-
Action: Make sure that the types of columns in the tables to be compared are the ones supported by symmetric replication.
-
Cause: The group name was null or misspelled, or the group does not exist locally.
-
Action: Specify the group correctly, or create it with DBMS_REPCAT.CREATE_MASTER_REPGROUP().
-
Cause: The given database already replicates the given object group. A materialized view repgroup cannot be created at a given site where a master repgroup with the same name already exists.
-
Action: Choose a different group or a different database.
-
Cause: A feature not compatible with the specified database was used.
-
Action: Set or raise the value of the COMPATIBLE initialization parameter to match the necessary compatibility level.
-
Cause: A feature not compatible with the remote database was used.
-
Action: Upgrade the remote database and retry the operation.
-
Cause: An attempt was made to use the name of the reference site table as the name of the missing_rows_oname1 argument.
-
Action: Provide a separately created table with a different name for MISSING_ROWS_ONAME1 argument. The separately created table will contain the differences between the tables being compared.
-
Cause: The connection qualifier used in the database link for the specified object group does not match the qualifier specified for the group in CREATE_MASTER_REPGROUP.
-
Action: Use or create a database link which contains the correct connection qualifier.
-
Cause: The maximum length of a database link, including the connection qualifier, is 128 bytes.
-
Action: Use a shorter connection qualifier, or shorten the name of the database link
-
Cause: The specified propagation is misspelled, or is not supported. For materialized view sites, all materialized view object groups at the same materialized view site with the same master object group must all have the same propagation method.
-
Action: Refer to Oracle9i Replication for valid propagation modes. For materialized view sites, also ensure that the propagation modes of all materialized view object groups with the same master object group are the same.
-
Cause: The system generated object(s) for the specified base object do not exist at the specified site. The current operation requires the base object to have generated replication support.
-
Action: Ensure that the generated replication object(s) for the base object exist and are valid at the specified site. If the generated object(s) do not exist, then the procedure DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() needs to be called from the master definition site for the base object. missing_rows_oname1 argument. The separately created table will contain the differences between the tables being compared.
-
Cause: The materialized view REPGROUP is not currently registered at the master and so cannot be unregistered.
-
Action: No action required.
-
Cause: Insertion into local REPSCHEMA table failed.
-
Action: No action required.
-
Cause: Specified numeric argument to DBMS_DEFER_SYS.PUSH is invalid.
-
Action: Fix the argument value and try again.
-
Cause: Specified string argument to DBMS_DEFER_SYS.PUSH is invalid.
-
Action: Fix the argument value and try again.
-
Cause: An error was occurred while creating slave processes for parallel push.
-
Action: If the PARALLEL_MAX_SERVERS initialization parameter is zero, reconfigure the parameter to be greater than zero. Otherwise, contact Oracle Support Services.
-
Cause: An attempt to dequeue a deferred transaction failed while trying to assign a new queue batch number.
-
Action: Contact Oracle Support Services.
-
Cause: An error occurred during parallel push while trying to update the high-water-mark information in SYSTEM.DEF$_DESTINATION.
-
Action: Contact Oracle Support Services.
-
Cause: DBMS_REPCAT.SWITCH_MVIEW_MASTER is no longer supported.
-
Action: Drop the objects in the object group and re-create them using the new master.
-
Cause: Could not find materialized view associated with a trigger or index that is being pulled from the master site.
-
Action: Ensure that materialized view, master, and master index or trigger are registered as replicated objects.
-
Cause: The given user is already the current propagator.
-
Action: No action required.
-
Cause: More than one valid propagator exists.
-
Action: Unregister any duplicate propagator.
-
Cause: The given name was null or misspelled, the given type was wrong, the object does not exist as a valid database object, or the object does not exist as a replicated object with the appropriate status.
-
Action: Ensure the object is valid in the database, is visible to the user, and, if appropriate, is a valid object in ALL_REPOBJECT.
-
Cause: The database link does not exist in the schema of the replication propagator or has not been scheduled.
-
Action: Ensure that the database link exists in the database, is accessible and is scheduled for execution.
-
Cause: The database link name at the local node does not match the global name of the database that the link accesses.
-
Action: Ensure that global names is set to true and the link name matches the global name.
-
Cause: The user name of the replication administration user at the local node and the user name at the node corresponding to the database link are not the same. Symmetric replication expects the two users to be the same.
-
Action: Ensure that the user ID of the replication administration user at the local node and the user ID at the node corresponding to the database link are the same.
-
Cause: Replication support for the specified object has not been generated or the generation process is not yet complete.
-
Action: Ensure that replication support has been generated for the object. Use DBMS_REPCAT.GENERATE_REPLICATION_SUPPORT() to generate replication support for the object.
-
Cause: A null, misspelled, or badly formed materialized view name was given to DBMS_MVIEW.REFRESH.
-
Action: Provide a valid materialized view name to DBMS_MVIEW.REFRESH.
-
Cause: A materialized view name was given to DBMS_MVIEW.REFRESH that is not in SYS.SNAP$ or its associated views.
-
Action: Provide a materialized view name that is in SYS.SNAP$, ALL_MVIEWS or USER_MVIEWS.
-
Cause: There are outstanding conflicts logged in the DefError table at the materialized view's master.
-
Action: Resolve the conflicts in the master DefError table and refresh again after the table is empty. Alternatively, refresh with REFRESH_AFTER_ERRORS set to TRUE, which will proceed with the refresh even if there are conflicts in the master's DefError table. Proceeding despite conflicts can result with an updatable materialized view's changes appearing to be temporarily lost (until a refresh succeeds after the conflicts are resolved).
-
Cause: Making a new refresh group when there is already a group of the same name in SYS.RGROUP$.
-
Action: Choose a different refresh group name.
-
Cause: A refresh group name was given that is not in SYS.RGROUP$.
-
Action: Provide a refresh group name that is in SYS.RGROUP$ or DBS_RGROUP.
-
Cause: A refresh group number was given that is not in SYS.RGROUP$.
-
Action: Provide a refresh group number that is in SYS.RGROUP$ or DBS_RGROUP.
-
Cause: The caller is not the owner of the materialized view and does not have ALTER ANY MATERIALIZED VIEW privileges.
-
Action: Perform the operation as the owner of the materialized view or as a user with ALTER ANY MATERIALIZED VIEW privileges.
-
Cause: The object name (for example, the rollback segment, the materialized view name, the refresh group) was incorrectly specified.
-
Action: Retry the operation with the object name properly specified (like "schema"."object" or "object").
-
Cause: Operation is not supported if the object group is replicated at a pre-V8 node.
-
Action: Ensure that all nodes of the replicated object group are V8.
-
Cause: 1000 consecutive refresh group numbers, as defined by the RGROUPSEQ number, were already used by rows in SYS.RGROUP$.
-
Action: Alter the sequence number to be within a legal unused range and destroy unneeded refresh groups.
-
Cause: A materialized view of the same name is already in a refresh group.
-
Action: Subtract the materialized view from the current refresh group and add it to its new refresh group, or combine the two refresh groups into a single refresh group.
-
Cause: The specified materialized view is not in the specified refresh group.
-
Action: Try again with the proper materialized view and refresh group names.
-
Cause: The master table's primary key constraint was modified after the primary key materialized view was created.
-
Action: Drop and re-create the primary key materialized view.
-
Cause: The fast refresh cannot be performed because the master table does not contain a materialized view log.
-
Action: Use the CREATE MATERIALIZED VIEW LOG command to create a materialized view log on the master table.
-
Cause: A ROWID materialized view is being fast refreshed, but the materialized view log does not record ROWID information.
-
Action: Use the CREATE MATERIALIZED VIEW LOG...ADD ROWID command to begin recording ROWID information in the materialized view log.
-
Cause: A primary key materialized view is being fast refreshed, but the materialized view log does not record primary key information.
-
Action: Use the CREATE MATERIALIZED VIEW LOG...ADD PRIMARY KEY command to begin recording primary key information in the materialized view log.
-
Cause: The master table does not contain a primary key constraint or the primary key constraint has been disabled.
-
Action: Create a primary key constraint on the master table or enable the existing constraint.
-
Cause: A fast refresh is being performed on a materialized view of an unknown or unsupported type.
-
Action: Check ALL_MVIEWS and ensure that the materialized view being refreshed is a valid materialized view.
-
Cause: The propagator is currently used in propagating replication RPCs.
-
Action: Try again later when there is no transaction active in propagating replication RPCs.
-
Cause: There are tables in the object group that require regeneration of replication support.
-
Action: Check the
GENERATION_STATUScolumn in theALL_REPOBJECTview. Regenerate replication support for any table in the object group with a 'NEEDSGEN' status. Resume master activity. -
Cause: The parameter INTERVAL evaluates to a time earlier than SYSDATE.
-
Action: Choose an expression that evaluates to a time later than SYSDATE.
-
Cause: There is no job visible to the caller with the given job number.
-
Action: Choose the number of a job visible to the caller.
-
Cause: Oracle Server could not generate a job number that was not used to identify another job.
-
Action: Retry the operation.
-
Cause: The given job number is less than 1.
-
Action: Choose a positive integer.
-
Cause: The specified materialized view has not been successfully registered at this site.
-
Action: Register the materialized view manually at either the master site or the materialized view site.
-
Cause: The argument provided to DBMS_MVIEW.PURGE_MVIEW_FROM_LOG is an invalid materialized view identifier or it does not identify an Oracle8 fast refreshable materialized view or the materialized view has already been purged.
-
Action: If the materialized view is an Oracle8 fast refreshable materialized view then provide PURGE_MVIEW_FROM_LOG with its valid materialized view identifier.
-
Cause: The requested action cannot be performed until the queue is empty for the given site/database link.
-
Action: Use DBMS_DEFER_SYS.PUSH, DBMS_DEFER_SYS.PURGE_QUEUE or DBMS_DEFER_SYS.DELETE_TRAN to empty the queue.
-
Cause: Specified numeric argument to DBMS_DEFER_SYS.PURGE_QUEUE is invalid.
-
Action: Fix the argument value and try again.
-
Cause: A job is associated with an instance that is not running.
-
Action: Choose a running instance for job affinity, or set force parameter to TRUE.
-
Cause: The caller has provided an argument whose value cannot be NULL or the empty string.
-
Action: Check that the varchar2 value provided is not NULL or the empty string, and retry the call.
-
Cause: The routine was executed against a replicated object group that was in the wrong state.
-
Action: Make sure that the replicated object group is in the state given in the error message.
-
Cause: An attempt was made to instantiate a replicated object group at a master site that was already a part of the object group.
-
Action: If you were trying to add this site, do nothing because it already exists; otherwise, pick the name of another site, and rerun the routine.
-
Cause: An attempt was made to execute the routine at a site that is different from the site specified in the argument of the routine.
-
Action: Provide an argument to the routine that correctly indicates the site against which the routine should be executing.
-
Cause: The site name given as an argument to a routine was not already known to the replicated object group.
-
Action: Execute the DBMS_OFFLINE_OG.BEGIN_INSTANTIATION() routine to add a new site to the replicated object group.
-
Cause: The propagation of LOB data from materialized view sites to the master site requires a primary key on the replicated table. Thus updatable ROWID materialized views that contain LOB columns are not supported.
-
Action: Create a primary key materialized view instead of a ROWID materialized view. If the materialized view already exists, it can be converted to a primary key materialized view using the ALTER MATERIALIZED VIEW DDL command.
-
Cause: The specified template authorization does not exist.
-
Action: Check the values for user name and refresh template name to ensure a valid row exists in the DBA_REPCAT_USER_AUTHORIZATIONS view.
-
Cause: The specified user already has been authorized to use the specified refresh group template.
-
Action: Check the values for user name and refresh template name or query the DBA_REPCAT_USER_AUTHORIZATIONS view to ensure that the correct values were passed as parameters.
-
Cause: The specified refresh group template does not exist.
-
Action: Verify that the refresh group template does not exist by querying the DBA_REPCAT_REFRESH_TEMPLATES view.
-
Cause: The specified refresh group template already exists.
-
Action: Verify that the refresh group template exists by querying the DBA_REPCAT_REFRESH_TEMPLATES view.
-
Cause: The public template parameter is not 'Y', 'N' or NULL.
-
Action: Correct the value of the public template parameter. It must be 'Y','N' or NULL.
-
Cause: The specified object does not exist in the refresh group template.
-
Action: Correct the object name and object type parameters. Check the DBA_REPCAT_TEMPLATE_OBJECTS view to verify the correct name and type of the object.
-
Cause: The specified object already exists in the refresh group template.
-
Action: Change the object name and object type parameters. Query the DBA_REPCAT_REMPLATE_OBJECTS view to verify the correct name and type of the object.
-
Cause: The specified template parameter does not exist.
-
Action: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name.
-
Cause: The template parameter already exists for the specified refresh group template.
-
Action: Correct the template parameter value and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_PARMS view to verify the name of the refresh group template and parameter name.
-
Cause: The template site specified by the site name, user name and refresh group template name does not exist.
-
Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites.
-
Cause: The template site specified by the site name, user name and refresh group template name already exists.
-
Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_TEMPLATE_SITES view to query the existing template sites.
-
Cause: The user parameter value specified by the user name, parameter name and refresh group template name does not exist.
-
Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARM_VALUES view to query the existing user parameters.
-
Cause: The user parameter value specified by the user name, parameter name and refresh group template name already exists.
-
Action: Correct the invalid parameter and execute the procedure again. Use the DBA_REPCAT_USER_PARM_VALUES view to query the existing user parameters.
-
Cause: The user specified by the user name parameter does not exist in the database.
-
Action: Correct an invalid user name or create the user in the master database. Use the DBA_USERS view to select the valid database users.
-
Cause: The flavor already contains the specified object.
-
Action: Check that the specified object is correct. To add all columns of a table object, delete the object from the flavor and then add it again.
-
Cause: The given object group already contains a (possibly unpublished) definition of the specified flavor.
-
Action: Check the spelling of the flavor name. Check for an unpublished flavor of the desired name.
-
Cause: The given object group already contains a (published) definition of the specified flavor.
-
Action: Check the spelling of the flavor name.
-
Cause: The TOP flavor has a NULL name and may not be directly defined or deleted.
-
Action: Supply the name of a flavor other than the TOP flavor or use DBMS_REPCAT routines to implicitly change the TOP flavor.
-
Cause: The given object group does not contain a (published) definition of the specified flavor.
-
Action: Check the spelling of the flavor name. Ensure the flavor has been defined (and published) for the object group.
-
Cause: The given flavor contains the object to be dropped.
-
Action: Purge the flavor or choose another object to drop.
-
Cause: The flavor does not contain the given object, column, or attribute.
-
Action: Either drop the flavor or choose a different object, column, or attribute.
-
Cause: The given flavor ID is invalid.
-
Action: Make sure this flavor has been instantiated. If the flavor ID is outside the range (-2147483647, 2147483647), contact Oracle Support Services.
-
Cause: The given flavor at the given database prevents the operation from succeeding.
-
Action: Either change the database flavor or choose a different operation.
-
Cause: The flavor must contain the given object, column, or attribute.
-
Action: Either choose a different database flavor or ensure the object, column, or attribute is available.
-
Cause: Before resolving conflicts, some values necessary for resolving conflicts are not available; or, after resolving conflicts, some values necessary for retrying the SQL are not available.
-
Action: define appropriate flavors, provide necessary values through availability vector in USER FLAVOR FUNCTION for conflict resolution.
-
Cause: The given flavor cannot be deleted because it is being used at the given site.
-
Action: Change the flavor of the site, or unregister it if it is a materialized view site.
-
Cause: An existing flavor includes the specified object with an incompatible type.
-
Action: Change the type of the object, or delete the flavor if it is not in use.
-
Cause: The flavor includes some columns of an object group but not all the required columns.
-
Action: Change the flavor definition to include all required columns.
-
Cause: The flavor includes the specified column which is being added.
-
Action: Check that the specified column is correct.
-
Cause: The flavor includes the specified object which does not exist.
-
Action: Check that the specified object name is correct, and create the object if appropriate.
-
Cause: The flavor does not include the specified object which is being dropped.
-
Action: Check that the specified object is correct.
-
Cause: The template is missing the object with the specified key.
-
Action: Add the object to the template.
-
Cause: The values for the specified columns are different in each template for the same key values.
-
Action: Correct the column values to make the templates the same.
-
Cause: The status should be DELETED, INSTALLING or INSTALLED. Any other status is invalid.
-
Action: Check that the specified status value is correct.
-
Cause: The refresh template is private and the user has not been authorized to instantiate the template.
-
Action: Authorize the user to use the template.
-
Cause: Non-atomic refresh is not supported for the specified materialized view.
-
Action: Set the value of the ATOMIC parameter to FALSE in the refresh procedure being used or remove the specified materialized view from the set of materialized views being refreshed.
-
Cause: The processing of replication RPCs for the object group that contains this object is disabled. This includes RPCs in the error queue.
-
Action: Processing of replication RPCs is disabled when the object group is being offline instantiated. Wait until offline instantiation is finished.
-
Cause: The current columns in the specified table and their column types do not match the columns and column types when replication support was last generated.
-
Action: Regenerate replication support for the affected table. All flavors that include the specified table should be checked for validity. Types for any UDT columns should also be checked for validity.
-
Cause: The specified column is a key column and must be sent and compared during replication propagation.
-
Action: Make sure every key column is sent and compared.
-
Cause: This object was imported from a database with a different global name than the importing database.
-
Action: Only import this object into a database with the same global name.
-
Cause: The propagation method of a materialized view object group can only be altered when no other object groups with the same master object group are sharing the materialized view site.
-
Action: Ensure that there are no other materialized view object groups at the local site with the same master object group.
-
Cause: There is at least one other materialized view repgroup at the local site with the same group name but a different master site.
-
Action: Ensure that all materialized view repgroups at the local site with the same group name have the same master.
-
Cause: The column is either not a top-level column or is not present in the table or materialized view.
-
Action: Ensure only valid top-level columns are used.
-
Cause: The column is of Object Type.
-
Action: Ensure that all the columns are not of Object Type.
-
Cause: The specified operation does not support the given object.
-
Action: Do not invoke the operation for this object.
-
Cause: An internal error occurred in internet Application Server.
-
Action: Report the error and other information to support.
-
Cause: The column group doesn't contain only one numeric column.
-
Action: Use a column group containing a single numeric column.
-
Cause: The specified two object groups do not have the same connection qualifier.
-
Action: Do not invoke the operation on the above object groups, or ensure they have the same connection qualifier.
-
Cause: This operation does not support the specified dblink in the above propagation mode.
-
Action: Do not invoke the operation for this dblink, or change the propagation mode for this dblink.
-
Cause: The specified value is duplicated in the parameter list.
-
Action: Remove duplicated entries in the parameter list.
-
Cause: The specified operation is not allowed for the extension request with the specified status.
-
Action: Ensure the extension request has the appropriate status before retrying this operation.
-
Cause: The specified database does not have a valid extension request.
-
Action: Ensure there is a valid extension request in the DBA_REPEXTENSIONS view before retrying this operation.
-
Cause: There is no new site with the specified extension request.
-
Action: Ensure there is at least one new site in the DBA_REPSITES_NEW view for this request before retrying this operation.
-
Cause: The specified extension request does not include the specified site as a new site.
-
Action: Ensure the specified site is a new site for this extension request before retrying this operation.
-
Cause: The specified destination has too many rows in the system.def$_destination table.
-
Action: Ensure the specified destination has at most two valid rows before retrying this operation.
-
Cause: The sites involved may be in the process of adding a new site without quiescing.
-
Action: Check the def$_destination table for this destination and try parallel propagation.
-
Cause: The disabled status for this site is set internally for synchronization during adding a new master without quiescing.
-
Action: Ensure adding a new master without quiescing finished before invoking this procedure.
-
Cause: An attempt was made to switch master for a materialized view repgroup when its parent repgroup is also a materialized view repgroup. This is not allowed.
-
Action: Drop and recreate the materialized view repgroup based on a proper parent repgroup.
-
Cause: Instantiation of a refresh template is not supported for database compatibility equal to or less than 8.0.
-
Action: Be sure the database compatibility is equal to 8.1 or higher.
-
Cause: An attempt was made to offline instantiate to a directory which is not specified or null.
-
Action: There are two ways to specify the directory:
Make sure you have specified an appropriate directory in which the offline file can be created.
-
Cause: An attempt was made to instantiate a IAS site. Error occurred during IAS instantiation.
-
Action: See the other errors on the error stack to look for the source of the problem. If the error still persists, contact Oracle Support Services.
-
Cause: The list of columns passed as a parameter does not match the columns to be added to the table.
-
Action: Correct the DDL string or list of columns and rexecute.
-
Cause: The specified object does not exist.
-
Action: Check that the specified object is correct.
-
Cause: The arguments passed to the online redefinition API were invalid or missing.
-
Action: Call the online redefinition API with the right number of valid arguments.
-
Cause: An attempt was made to drop a tablespace which contains materialized views and/or their indices.
-
Action: Drop the materialized views in this tablespace. Also, find indices belonging to materialized views in this tablespace and drop then. Then try dropping the tablespace.
-
Cause: Site owner for the template already exists.
-
Action: Do not create multiple siteowners for this template.
-
Cause: Tables belonging to the same replication group were specified to be cached with different synchronization mechanisms.
-
Action: Do not specify different synchronization mechanisms while caching tables belonging to the same replication group.
-
Cause: An attempt was made to cache an object which is not supported.
-
Action: Do not cache an object which is not supported.
-
Cause: After import, the materialized view container table has missing columns.
-
Action: Check if materialized view container table was imported correctly.
-
Cause: An attempt was made to set a new non-null back end database for an iAS site.
-
Action: Call dbms_ias_configure.set_back_end_db procedure with null dblink. Then, call the same procedure with the new non-null dblink.
-
Cause: The object may have been dropped or renamed at the back end after dbms_ias_inst.start_ias_inst was executed.
-
Action: Check the validity of the object at the back end and retry the instantiation.
-
Cause: This function or procedure is restricted to the backend or middle tier site.
-
Action: Connect to the proper site before calling this function or procedure.
-
Cause: An attempt was made to explicitly refresh a NEVER REFRESH materialized view.
-
Action: Do not perform this refresh operation or remove the materialized views from the list.
-
Cause: The propagate_name already exists.
-
Action: Drop the propagate_name using DROP_PROPAGATE command or specify propagate_name.
-
Cause: Propagation does not exist.
-
Action: Query the
DBA_PROPAGATIONview to find existing propagation_name. -
Cause: Specified streams process type is not valid.
-
Action: Specify either capture or apply.
-
Cause: An attempt was made to specify an invalid parameter value.
-
Action: Specify a valid value for the parameter. Check the documentation for valid parameter values.
-
Cause: An attempt was made to specify an invalid object.
-
Action: Specify a valid object.
-
Cause: An invalid column was specified in the column list.
-
Action: Check the columns in the object and specify the right column name.
-
Cause: An invalid column was specified as the resolution column. The resolution column must belong to the list of columns specified in the 'column_list' parameter.
-
Action: Check the columns in the column_list and specify the right resolution column name.
-
Cause: A non-Oracle database has returned an error message to STREAMS when attempting to apply a DML statement. The non-Oracle system error message is a parameter to this Oracle error.
-
Action: Corrective action may or may not be possible (depending on the non-Oracle system error). If corrective action is possible, then correct the problem and try applying the transaction again.
-
Cause: An invalid value was specified for the parameter.
-
Action: Specify a string of the form [SCHEMA.]NAME.
-
Cause: The queue table already exists in the queueing system.
-
Action: Drop the table first using the DROP_QUEUE_TABLE() command or specify another table.
-
Cause: QUEUE_TABLE does not exist.
-
Action: Query on the user view USER_QUEUE_TABLES to find out existing queue tables.
-
Cause: The queue table index has not yet been successfully imported.
-
Action: Import the queue table index before attempting to use the queue table. If the import failed, correct the problem and try to import the queue table index again.
-
Cause: Invalid column name was specified in the SORT_LIST.
-
Action: The valid column names are ENQ_TIME and PRIORITY.
-
Cause: An attempt was made to use the SQL command DROP TABLE for queue tables, but DROP TABLE is not supported for queue tables.
-
Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure instead of the DROP TABLE command.
-
Cause: The queue requested to be created already exists.
-
Action: Specify another queue name. Query USER_QUEUES for all the existing queues in the users's schema.
-
Cause: An invalid value was specified for MAX_RETRIES.
-
Action: Specify a non-negative integer.
-
Cause: An error was detected when dropping a queue table in a cluster, tablespace, or schema.
-
Action: Use the DBMS_AQADM.DROP_QUEUE_TABLE procedure to drop the specified queue table first; then, retry the operation.
-
Cause: Invalid queue type parameter.
-
Action: Valid values are NORMAL_QUEUE for normal queue and EXCEPTION_QUEUE for exception queue.
-
Cause: The specified queue does not exist.
-
Action: Specify a valid queue. Query USER_QUEUES for all the valid queues.
-
Cause: The queue has not been stopped. That is, either enqueue or dequeue is still enabled.
-
Action: Stop the queue first using the STOP_QUEUE command and disable it from both enqueueing and dequeueing.
-
Cause: A queue exists in the queue table which has not been dropped. All queues need to be dropped first.
-
Action: Drop all queues belonging to this queue table using the DROP_QUEUE() command. Be sure to stop the queues appropriately before dropping them. Alternately, use the force option in DROP_QUEUETABLE.
-
Cause: A negative value was specified for RETRY_DELAY.
-
Action: Specify a non-negative value for RETRY_DELAY.
-
Cause: Queue retention was specified, but the retention time was specified to be less than zero.
-
Action: Specify the retention time to be non-negative or FOREVER. Alternately do not specify retention.
-
Cause: An invalid QUEUE_PAYLOAD_TYPE specified during CREATE_QUEUE_TABLE.
-
Action: The QUEUE_PAYLOAD_TYPE should be RAW or an object type that already exists in the database.
-
Cause: An invalid object type specified for QUEUE_PAYLOAD_TYPE during CREATE_QUEUE_TABLE.
-
Action: Make sure you have execute privileges on the object type specified for the queue.
-
Cause: An attempt was made to enable enqueueing to an exception queue.
-
Action: No action required.
-
Cause: There were outstanding transactions on the queue, and WAIT was set to false, so STOP_QUEUE was unsuccessful in stopping the queue.
-
Action: Set WAIT to TRUE and try STOP_QUEUE again. It will hang till all outstanding transactions are completed.
-
Cause: The identifier specified is too long.
-
Action: Try again with a shorter identifier.
-
Cause: An internal error occurred in the package. DBMS_AQ_IMPORT_INTERNAL.
-
Action: Contact Oracle Support Services.
-
Cause: The queue definition is not updated because the queue table was not imported properly.
-
Action: Import the queue table again.
-
Cause: The parameter combination will not cause the queue to be started or stopped.
-
Action: No action required. This is a warning.
-
Cause: An internal error occurred in the package DBMS_AQ_EXP_INTERNAL.
-
Action: Contact Oracle Support Services.
-
Cause: An internal error occurred in the package DBMS_AQ_IMP_INTERNAL.
-
Action: Contact Oracle Support Services.
-
Cause: Parameter QUEUE_PAYLOAD_TYPE has invalid value.
-
Action: Specify a valid object type or RAW.
-
Cause: An attempt was made to enqueue, dequeue or administer a queue which has errors.
-
Action: Drop the queue table setting the force option to true.
-
Cause: AQ propagation's HTTP request to the propagation servlet at the specified address encountered an error.
-
Action: Specify a valid address in the connect string of the propagation destination dblink, the dblink user has the correct permissions, check if the AQ propagation servlet was properly installed.
-
Cause: Tried to create a reciever non-repudiable single consumer queue.
-
Action: This feature is not supported.
-
Cause: Tried an operation not allowed on a single-consumer queue.
-
Action: Specify the operation on a multi-consumer queue.
-
Cause: Specified both a rule and rule-set for the operation.
-
Action: Specify only one of rule or rule-set.
-
Cause: Parameter is NULL.
-
Action: Specify a non-NULL value for the parameter.
-
Cause: Oracle AQ tried to create an index with the name specified in the error message. The index could not be created for the specified queue table because a object exists with the same name.
-
Action: Drop the object specified in the error message and retry the command. You can also choose a different name for the queue table.
-
Cause: An enqueue was performed on a queue that has been set up for multiple dequeuers but there were neither explicit recipients specified in the call nor were any queue subscribers determined to be recipients for this message.
-
Action: Either pass a list of recipients in the enqueue call or add subscribers to the queue for receiving this message.
-
Cause: An application name that was already a subscriber for the queue was specified in the DBMS_AQ.SUBSCRIBE call.
-
Action: Choose another application name and retry the call.
-
Cause: An AQ agent that was not a subscriber for the queue was specified.
-
Action: Check the name and/or address of the agent and retry the call.
-
Cause: The CREATE QUEUE TABLE command was issued with MESSAGE_GROUPING set to TRANSACTIONAL and a sort order column other than priority. Only the priority column can be specified in the sort order for queue tables with transactional grouping.
-
Action: Change the sort order list in the CREATE QUEUE TABLE command and retry the call.
-
Cause: The schema specified in the QUEUE_NAME parameter of CREATE_QUEUE is not the same as the schema specified in the QUEUE_TABLE parameter.
-
Action: Use the same schema name for both the QUEUE_NAME and QUEUE_TABLE parameters and retry the command.
-
Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and a QUEUE_TABLE that was created for multiple consumers and with COMPATIBLE parameter set to '8.0'.
-
Action: Either set the RETRY_DELAY to zero or upgrade the queue table to 8.1 compatible using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
-
Cause: Either an ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure, or an ENQUEUE with a non-empty recipient list, was issued on a queue that was not created for multiple consumers.
-
Action: Create the queue in a queue table that was created for multiple consumers and retry the call.
-
Cause: A SCHEDULE_PROPAGATION was issued for a queue and destination pair which has an existing propagation schedule.
-
Action: Issue UNSCHEDULE_PROPAGATION to remove the existing schedule and then reissue the SCHEDULE_PROPAGATION call.
-
Cause: AN UNSCHEDULE_PROPAGATION was issued for a queue and destination pair which has no existing propagation schedule.
-
Action: Verify the spelling of the specified QUEUE and DESTINATION and then reissue the call with the correct spelling.
-
Cause: An attempt was made to specify a reserved name for a destination.
-
Action: Enter a different value or NULL for the local destination. Then retry the operation.
-
Cause: A message recipient's queue has a different object structure than the sender's queue. The message cannot be propagated.
-
Action: Either remove the recipient from the subscriber's list for the sender's queue or create the destination queue with an object type that matches the source queue's object type.
-
Cause: An invalid value was specified for the agent address parameter.
-
Action: Specify a string of the form [SCHEMA.]NAME[@DATABASE LINK].
-
Cause: The protocol attribute of the AQ agent object type is reserved for future use.
-
Action: Do not specify the protocol attribute in the agent object type.
-
Cause: An invalid value was specified for the agent name parameter.
-
Action: Specify a string of the form NAME. Then retry the operation.
-
Cause: An attempt was made to issue the CREATE_QUEUE_TABLE command, but the user who issued the command does not have access to internal AQ object types.
-
Action: Use the DBMS_AQADM.GRANT_TYPE_ACCESS procedure to grant the user access to the AQ object types.
-
Cause: An attempt was made to use a reserved prefix in the agent name.
-
Action: Enter a different value for the agent name. Then, retry the operation.
-
Cause: An ADD_SUBSCRIBER, ALTER_SUBSCRIBER, or REMOVE_SUBSCRIBER procedure was issued on a queue that was created as an EXCEPTION_QUEUE.
-
Action: Specify a NORMAL_QUEUE in the procedure.
-
Cause: An ADD_SUBSCRIBER or ENQUEUE procedure with a non-NULL address field in the agent type was issued on a queue whose payload has a REF or BFILE attribute. Propagation of object type payloads that have a REF or BFILE attribute currently is not supported.
-
Action: Specify an agent with a NULL address field so that the agent can dequeue from the same queue. Or, change the object type definition to one that does not use REF or BFILE attributes.
-
Cause: The recipient of a message with LOB attributes was using an Oracle 8.0 release. Propagation of LOB attributes is supported only in Oracle 8.1 and higher releases.
-
Action: Upgrade the target release to Oracle 8.1 and retry. Or, change the object type definition to one that does not use LOBs.
-
Cause: One of PRIMARY_INSTANCE or SECONDARY_INSTANCE was negative.
-
Action: Specify non-negative integers for PRIMARY_INSTANCE and SECONDARY_INSTANCE.
-
Cause: The recipient of a message was using an Oracle 8.0.3 release or lower release. Propagation is supported only in Oracle 8.0.4 and higher releases.
-
Action: Upgrade the target release to Oracle 8.0.4 or higher and retry.
-
Cause: An attempt was made to use the internal administration procedure to delete status rows from the SYS.AQ$_PROPAGATION_STATUS table that were in the prepared state.
-
Action: Wait for the propagation to complete successfully before retrying the operation.
-
Cause: The sequence numbers used in the SYS.AQ$_PROPAGATION_STATUS table were inconsistent for the given queue and destination.
-
Action: Contact Oracle Support Services.
-
Cause: An ADD_SUBSCRIBER or ALTER_SUBSCRIBER procedure with a rule was issued on a queue for which rule based subscribers are not supported. Rule based subscribers currently are supported only for NORMAL (persistent) multi-consumer queues created using an Oracle release 8.1.0 or higher compatible queue table.
-
Action: Create a NORMAL multi-consumer queue in an Oracle release 8.1.0 or higher compatible queue table, and retry the call. Or, if the queue is a normal (persistent) multi-consumer queue, convert the queue table to Oracle 8.1.0 or higher compatibility and retry.
-
Cause: An attempt was made to downgrade the queue table when there were messages being propagated that were in the prepared state.
-
Action: Wait for the propagation to complete before retrying the operation.
-
Cause: An invalid compatible parameter was specified in the DBMS_AQADM procedure. The parameter setting must be of the form '8.x.y' where x is the release number and y is the update number.
-
Action: Specify a valid COMPATIBLE parameter setting, and retry the operation.
-
Cause: The source queue table in the DBMS_AQADM procedure is compatible with the specified COMPATIBLE parameter setting.
-
Action: Choose a different COMPATIBLE parameter setting to convert the queue table to the desired compatibility.
-
Cause: A non-zero value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was zero.
-
Action: Specify a non-zero primary instance before you specify a non-zero secondary instance.
-
Cause: The subscriber table has not yet been successfully imported.
-
Action: Import the subscriber table before attempting to use the queue table. If the import failed, correct the problem and try to import the subscriber table again.
-
Cause: An attempt was made to downgrade the queue table when there were queues on which rule-based subscribers are defined.
-
Action: Remove the rule-based subscribers for all queues in this queue table and retry.
-
Cause: An ENABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was enabled.
-
Action: Make sure the QUEUE and DESTINATION are correct when you issue the ENABLE_SCHEDULE_PROPAGATION command.
-
Cause: A DISABLE_SCHEDULE_PROPAGATION command was issued for a queue and destination pair whose propagation schedule already was disabled.
-
Action: Make sure the QUEUE and DESTINATION are correct when you issue the DISABLE_SCHEDULE_PROPAGATION command.
-
Cause: An invalid privilege is specified for granting or revoking privilege.
-
Action: Specify a valid privilege.
-
Cause: An attempt was made to add new subscribers to the specified, but the number of subscribers for this queue has exceeded the maximum number (1024) of subscribers allowed per queue.
-
Action: Remove existing subscribers before trying to add new subscribers.
-
Cause: An attempt was made to start a queue in a queue table that is being migrated.
-
Action: Complete the queue table migration, and retry the operation.
-
Cause: An attempt was made to downgrade a queue table, but a previous command to upgrade the queue table has not yet completed successfully.
-
Action: Complete the upgrade of the queue table by re-executing the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, downgrade the queue table.
-
Cause: An attempt was made to upgrade a queue table, but a previous command to downgrade the queue table has not yet completed successfully.
-
Action: Complete the downgrade of the queue table by re-executing the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure. Then, upgrade the queue table.
-
Cause: An attempt was made to perform an operation on a queue in a queue table that is being migrated.
-
Action: Complete the queue table migration, and retry the operation.
-
Cause: An attempt was made to upgrade or downgrade a queue table using the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure, but the user who executed the procedure does not own the queue.
-
Action: Reconnect as the owner of the queue table, and then execute the DBMS_AQADM.MIGRATE_QUEUE_TABLE procedure.
-
Cause: An attempt was made to create or alter an exception queue by specifying a non-zero RETENTION_TIME.
-
Action: Use the default RETENTION_TIME parameter value for exception queues.
-
Cause: The CREATE_QUEUE or ALTER_QUEUE command was issued with a non-zero RETRY_DELAY and an exception queue.
-
Action: Do not specify RETRY_DELAY or MAX_RETRIES for exception queues.
-
Cause: An ADD_SUBSCRIBER or enqueue was attempted with an agent that had a NULL address and a non-NULL protocol.
-
Action: Either specify a non-NULL address or set the protocol to NULL.
-
Cause: One of the operations, SCHEDULE_PROPAGATION, ALTER_QUEUE, LISTEN, DEQUEUE was issued for a NON_PERSISTENT queue.
-
Action: Do not specify a NON_PERSISTENT queue for these operations.
-
Cause: A SCHEDULE_PROPAGATION was issued for an EXCEPTION queue. Propagation schedules can be created only for NORMAL queues.
-
Action: To propagate messages from a queue, specify the queue type as NORMAL.
-
Cause: A non-NULL value was specified for SECONDARY_INSTANCE when PRIMARY_INSTANCE was NULL.
-
Action: Specify a non-NULL primary instance before you specify a non-NULL secondary instance.
-
Cause: An attempt was made to use a reserved prefix for the object name.
-
Action: Enter a different name for this object. Then, retry the operation.
-
Cause: A propagation administration command was issued for a queue and destination pair whose propagation is being unscheduled.
-
Action: Do not issue propagation administration commands for a propagation schedule on which there is a pending unschedule request.
-
Cause: The value of the COMPATIBLE parameter was not high enough to allow the operation.
-
Action: Shut down and restart with a higher compatibility setting.
-
Cause: The snapshot process executing the propagation schedule did not respond to the disable propagation command.
-
Action: Make sure that the job for the propagation schedule has been ended.
-
Cause: An ADD_SUBSCRIBER call with a non-null address field was issued on a queue which does not support remote subscribers. Remote subscribers are not supported for NON_PERSISTENT QUEUES.
-
Action: Specify a null address field and retry the call.
-
Cause: Advanced Queuing requires that the agent's DBLINK name should be unique within the first 24 bytes (for 8.0 compatible queue tables)
-
Action: Specify a DBLINK name that is unique within the first 24 bytes or migrate to 8.1 compatible queue tables where this restriction is not there.
-
Cause: An attempt was made to enqueue, dequeue or administer a queue which is invalid. This could have occurred because the payload type of the queue's queue table was dropped.
-
Action: Drop the queue table setting the force option to true.
-
Cause: An attempt was made to create an 8.0 compatible queue table and enable a feature that is supported only on 8.1 style queue tables.
-
Action: This feature is not supported.
-
Cause: An invalid database username was specified.
-
Action: Specify a valid database user.
-
Cause: This AQ Agent does not exist.
-
Action: Specify a valid AQ agent. Check the DBA_AQ_AGENTS view for a list of valid aq agents.
-
Cause: This AQ agent has already been created.
-
Action: Specify another agent name or use the ALTER api to modify the agent.
-
Cause: No protocol was enabled for aq agent.
-
Action: Enable one of the protocols by setting one of the enable parameters to true.
-
Cause: The specified AQ agent does not have privileges of the specified database user.
-
Action: Specify a valid combination of AQ agent and database user. Check the
DBA_AQ_AGENT_PRIVSorUSER_AQ_AGENT_PRIVSview for user/agent mappings. -
Cause: The target type of the transformation specified was different from the type of the queue.
-
Action: Provide a valid transformation whose target type is the same as the queue type.
-
Cause: The source type of the transformation specified was different from the type of the queue.
-
Action: Provide a valid transformation whose source type is the same as the queue type.
-
Cause: Invalid value was specified for message state.
-
Action: Provide a valid message state as specified in the documentation.
-
Cause: A negative value or NULL was specified for the parameter.
-
Action: Specify a non-negative integer.
-
Cause: An Invalid value or NULL was specified for the parameter.
-
Action: Check the documentation for valid values.
-
Cause: The specified operation is only supported for queues with compatibility equal to 8.1 or higher.
-
Action: Upgrade the 8.0 compatible queue to release 8.1 using DBMS_AQADM.MIGRATE_QUEUE_TABLE or specify a queue with compatibility euqal to 8.1 or higher.
-
Cause: There is an error in the Transaction layer test ICDs.
-
Cause: An invalid parameter was passed to the specified DBMS_REPAIR procedure.
-
Action: Specify a valid parameter value or use the parameter's default.
-
Cause: Both cascade and a block range were specified in a call to DBMS_REPAIR.CHECK_OBJECT.
-
Action: Use either cascade or a block range, or do not use either one.
-
Cause: An incorrect block range was specified.
-
Action: Specify correct values for the BLOCK_START and BLOCK_END parameters.
-
Cause: An attempt was made to use the specified feature, but the feature is not yet implemented.
-
Action: Do not attempt to use the feature.
-
Cause: An invalid ACTION parameter was specified.
-
Action: Specify CREATE_ACTION, PURGE_ACTION or DROP_ACTION for the ACTION parameter.
-
Cause: An attempt was made to fix corrupt blocks on an object that has been dropped or truncated since DBMS_REPAIR.CHECK_OBJECT was run.
-
Action: Use DBMS_REPAIR.ADMIN_TABLES to purge the repair table and run DBMS_REPAIR.CHECK_OBJECT to determine whether there are any corrupt blocks to be fixed.
-
Cause: CASCADE_FLAG was specified for an object that is not a table.
-
Action: Use CASCADE_FLAG only for tables.
-
Cause: The TABLESPACE parameter can only be used with CREATE_ACTION.
-
Action: Do not specify TABLESPACE when performing actions other than CREATE_ACTION.
-
Cause: A partition name was specified for an object that is not partitioned.
-
Action: Specify a partition name only if the object is partitioned.
-
Cause: An attempt was made to pass a table name parameter without the specified prefix.
-
Action: Pass a valid table name parameter.
-
Cause: An attempt was made to specify a map, repair, or sync table that does not exist.
-
Action: Specify a valid table name parameter.
-
Cause: An attempt was made to specify a map, repair, or sync table that does not have a correct definition.
-
Action: Specify a table name that refers to a properly created table.
-
Cause: An attempt was made to specify a table name is greater than 30 characters long.
-
Action: Specify a valid table name parameter.
-
Cause: An attempt to access or modify a ruleset was made, which failed because the ruleset does not exist.
-
Action: Only access or modify existing rulesets.
-
Cause: An attempt to create a ruleset with an invalid name was made. The ruleset name cannot be NULL, and cannot be more than 26 characters, unless a RULES_TABLE_NAME is also specified, in which case the ruleset name may be up to 30 characters.
-
Action: Retry the create with a valid ruleset name.
-
Cause: An attempt to create a rule/ruleset on an invalid evaluation name was made. The evaluation_context can not be more than 30 characters. The evaluation context with the name specified must exist.
-
Action: Retry the create with a valid evaluation context name.
-
Cause: An internal error occurred in the rules engine. This indicates that the rules engine has encountered an exception condition.
-
Action: Contact Oracle Support Services. The first argument is the error and the second argument is the package.
-
Cause: An evaluation context of the given name already exists.
-
Action: Specify another name for the evaluation context being created.
-
Cause: A rule of the given name already exists.
-
Action: Specify another name for the rule being created.
-
Cause: The rule of the given name does not exist.
-
Action: Create the rule or specify one that exists.
-
Cause: The rule still belongs to some rulesets, cannot be dropped.
-
Action: Do not drop a rule that belongs to rulesets without force option.
-
Cause: An attempt to create a rule with an invalid name was made.
-
Action: The rule name can not be NULL, and can not be more than 30 characters.
-
Cause: The evaluation context of the given name does not exist.
-
Action: Create the evaluation context or specify one that exists.
-
Cause: When adding a rule to a rule set, either the rule or the rule set must have an evaluation context associated with it.
-
Action: Do not add a rule without an evaluation context to a ruleset that does not have a default evaluation context.
-
Cause: The evaluation context still belongs to some rules or rule sets, cannot be dropped.
-
Action: Do not drop an evaluation context with dependents without force option.
-
Cause: A rule set of the given name already exists.
-
Action: Specify another name for the rule set being created.
-
Cause: A rule can be added to a rule set only once.
-
Action: Do not add a rule to a rule set that already contains this rule.
-
Cause: The rule to be removed from the rule set is not in the rule set.
-
Action: Do not remove a rule from a rule set that does not contain the rule.
-
Cause: There is a table alias of the same name in the evaluation context.
-
Action: Do not add two table aliases of the same name to an evaluation context.
-
Cause: There is a variable of the same name in the evaluation context.
-
Action: Do not add two variables of the same name to an evaluation context.
-
Cause: Table alias name or base table name is not specified in the table alias definition.
-
Action: Specify both alias name and alias base table in the table alias structure.
-
Cause: Variable name or variable type is not specified in the variable definition.
-
Action: Specify both variable name and variable type in the variable definition structure.
-
Cause: There is already a name-value pair with the same name in the NVlist.
-
Action: Try another name.
-
Cause: There is not such a name-value pair in the NVlist.
-
Action: Check that the name-value pair exists in the NVList.
-
Cause: The NVList is full (1024 elements) and cannot hold more elements.
-
Action: Do not add elements to a full list.
-
Cause: The object name has a database link in it, which is not supported.
-
Action: Do not specify remote objects in rules engine DDLs.
-
Cause: No such system privilege number for rule engine objects.
-
Action: Check specification of dbms_rule_adm for valid system privilege numbers.
-
Cause: No such object privilege number for rule engine objects.
-
Action: Check specification of dbms_rule_adm for valid object privilege numbers.
-
Cause: Cannot resolve the table aliases and the variable types specified in the evaluation context.
-
Action: Make sure all base tables exist and all variable types are correct.
-
Action: ORA-24167 incompatible rule engine objects, cannot downgrade
-
Cause: There are rule engine objects in the database that cannot be downgraded.
-
Action: Check utlincmp.sql and remove all incompatible rules engine objects before downgrading.
-
Cause: If a rule is added to a rule set with more than one evaluation context, then it must not have an evaluation context itself.
-
Action: Do not set the evaluation context of such rules to a non-null value.
-
Cause: The rule references variables not in the evaluation context.
-
Action: Modify the rule condition to remove illegal reference.
-
Cause: The transformation expression does not evaluate to the target type or the target type's specified attribute.
-
Action: Provide valid transformation expression which evaluates to the target type or the target type's specified attribute.
-
Cause: The source or destination type for the transformation does not exist
-
Action: Create the type or specify one that exists.
-
Cause: The target type of the transformation does not have the attribute number specified in the ADD_ATTRIBUTE_TRANSFORMATION command.
-
Action: check the target type definition and specify a valid attribute number.
-
Cause: The transformation specified is invalid because the source or the target type have been dropped/modified.
-
Action: Drop and recreate the transformation.
-
Cause: A transformation of the given name already exists.
-
Action: Specify another name for the transformation being created.
-
Cause: The transformation being specified does not exist.
-
Action: Create the transformation before using it or specify an existing transformation.
-
Cause: The object type of the message to be transformed does not match the source type of the specified transfomation.
-
Action: Specify another transformation or specify a message of the correct type.
-
Cause: The length of payload being taken excceeds the limit of varchar2 or raw.
-
Action: Use clob type or blob type to call get_text or get_bytes.
-
Cause: The property name being set has existed.
-
Action: Use another property name.
-
Cause: The property name cannot be null.
-
Action: Make sure the property name is not null.
-
Cause: The property values being set exceeds the valid range.
-
Action: Make sure the property value is within the valid range.
-
Cause: Attempted to add a publisher to the queue again.
-
Action: Specify another publisher or use DBMS_AQADM.ALTER_PUBLISHER to alter the publisher's properties.
-
Cause: Attempted to alter or drop a non existent publisher from a queue.
-
Action: Specify another publisher.
-
Cause: A call was made to create a new row in the specified table. A row already exists in the table with the specified values.
-
Action: Delete the existing row using the appropriate API or check the parameters used to create the row.
-
Cause: The translation type parameter is not a T, S or an M. A value other than T, S or M was specified.
-
Action: Correct the translation type and re-execute the API call.
-
Cause: The initialization value must be either F or T. A value other than F or T was specified.
-
Action: Correct the initialization value and re-execute the API call.
-
Cause: If a translation type of T or S is specified, translation text must be supplied.
-
Action: Provide translation text and re-execute the API call.
-
Cause: A call was made to update a row that does not exist or a foreign key value supplied to create a table does not exist.
-
Action: Create the row using the appropriate API or check the parameters used to create the new row to ensure that all specified values exist.
-
Cause: The function pkgname.funcname was called with a parameter parmname that was null, 0 length, or had an invalid value.
-
Action: Correct the parameter to supply values that comply with its datatype and limits as specified in the documentation.
-
Cause: The function pkgname.funcname computed a value for the output parmname that exceeded the maximum allowed. This can occur when multiple input parameters, each valid separately, combine to specify an invalid result. For example, when a length parameter multiplied by a copies parameter yields a total length exceeding the maximum for the output datatype.
-
Action: Correct the input values to produce a result that will comply with the limits as specified in the documentation.
ORA-19400 System type conflict with object SYS.string
ORA-19500 device block size string is invalid
ORA-19501 read error on file "string", blockno string (blocksize=string)
ORA-19502 write error on file "string", blockno string (blocksize=string)
ORA-19503 cannot obtain information on device, name="string", type="string", parms="string"
ORA-19504 failed to create file "string"
ORA-19505 failed to identify file "string"
ORA-19506 failed to create sequential file, name="string", parms="string"
ORA-19507 failed to retrieve sequential file, handle="string", parms="string"
ORA-19508 failed to delete file "string"
ORA-19509 failed to delete sequential file, handle="string", parms="string"
ORA-19510 failed to set size of string blocks for file "string" (blocksize=string)
ORA-19511 Error received from media manager layer, error text: string
ORA-19550 cannot use backup/restore functions while using dispatcher
ORA-19551 device is busy, device type: string, device name: string
ORA-19552 device type string is invalid
ORA-19553 device name string is invalid
ORA-19554 error allocating device, device type: string, device name: string
ORA-19555 invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
ORA-19556 required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred
ORA-19557 device error, device type: string, device name: string
ORA-19558 error de-allocating device
ORA-19559 error sending device command: string
ORA-19560 string is not a valid device limit
ORA-19561 string requires a DISK channel
ORA-19562 file string is empty
ORA-19563 string header validation failed for file string
ORA-19564 error occurred writing string bytes at block number string
ORA-19565 BACKUP_TAPE_IO_SLAVES not enabled when duplexing to sequential devices
ORA-19566 exceeded limit of string corrupt blocks for file string
ORA-19567 cannot shrink file string because it is being backed up or copied
ORA-19568 a device is already allocated to this session
ORA-19569 no device is allocated to this session
ORA-19570 file number string is outside valid range of 1 through string
ORA-19571 string recid string stamp string not found in controlfile
ORA-19572 cannot process file string, file is being being resized
ORA-19573 cannot obtain string enqueue for datafile string
ORA-19574 output filename must be specified
ORA-19575 expected string blocks in file string, found string
ORA-19576 datafile string not defined in control file
ORA-19577 file string is MISSING
ORA-19578 end of volume while duplexing to sequential files, backup piece incomplete
ORA-19579 archivelog record for string not found
ORA-19580 string conversation not active
ORA-19581 no files have been named
ORA-19582 archivelog file header validation for string failed
ORA-19583 conversation terminated due to error
ORA-19584 file string already in use
ORA-19585 premature end of volume on piece string
ORA-19586 string k-byte limit is too small to hold piece directory
ORA-19587 error occurred reading string bytes at block number string
ORA-19588 string recid string stamp string is no longer valid
ORA-19589 string is not a snapshot or backup controlfile
ORA-19590 conversation already active
ORA-19592 wrong string conversation type
ORA-19593 datafile number string already included as string
ORA-19594 controlfile already included as string
ORA-19595 archivelog string already included in backup conversation
ORA-19596 SPFILE already included
ORA-19597 file string blocksize string does not match set blocksize of string
ORA-19598 can not backup SPFILE because the instance was not started with SPFILE
ORA-19599 block number string is corrupt in string string
ORA-19600 input file is string string (string)
ORA-19601 output file is string string (string)
ORA-19602 cannot backup or copy active file in NOARCHIVELOG mode
ORA-19603 cannot backup or copy active file with KEEP .. UNRECOVERABLE option
ORA-19604 conversation file naming phase is over
ORA-19605 input filename must be specified
ORA-19606 Cannot copy or restore to snapshot controlfile
ORA-19607 string is an active controlfile
ORA-19608 string is not a backup piece
ORA-19609 string is from different backup set: stamp string count string
ORA-19610 directory block string is corrupt
ORA-19611 backup piece out of order. Expected string but found string
ORA-19612 datafile string not restored due to string
ORA-19613 datafile string not found in backup set
ORA-19614 archivelog thread string sequence string not found in backup set
ORA-19615 some files not found in backup set
ORA-19616 output filename must be specified if database not mounted
ORA-19617 file string contains different resetlogs data
ORA-19618 cannot name files after restoreValidate has been called
ORA-19619 cannot call restoreValidate after files have been named
ORA-19621 archivelog range has already been specified
ORA-19622 archivelog thread string sequence string not restored due to string
ORA-19623 file string is open
ORA-19624 operation failed, retry possible
ORA-19625 error identifying file string
ORA-19626 backup set type is string - can not be processed by this conversation
ORA-19627 cannot read backup pieces during controlfile application
ORA-19628 invalid SCN range
ORA-19629 no files in specified archivelog SCN range
ORA-19630 end of volume encountered while copying backup piece
ORA-19631 archivelog record contains no file name
ORA-19632 file name not found in controlfile
ORA-19633 controlfile record string is out of sync with recovery catalog
ORA-19634 filename required for this function
ORA-19635 input and output filenames are identical
ORA-19636 archivelog thread string sequence string already included
ORA-19637 backupPieceCreate requires file name when using DISK device
ORA-19638 file string is not current enough to apply this incremental backup
ORA-19639 file string is more current than this incremental backup
ORA-19640 datafile checkpoint is SCN string time string
ORA-19641 backup datafile checkpoint is SCN string time string
ORA-19642 incremental-start SCN is string
ORA-19643 datafile string: incremental-start SCN is too recent
ORA-19644 datafile string: incremental-start SCN is prior to resetlogs SCN string
ORA-19645 datafile string: incremental-start SCN is prior to creation SCN string
ORA-19646 cannot change size of datafile string from string to string
ORA-19647 non-zero LEVEL cannot be specified when INCREMENTAL is FALSE
ORA-19648 datafile string: incremental-start SCN equals checkpoint SCN
ORA-19649 offline-range record recid string stamp string not found in file string
ORA-19650 Offline-range record recid string stamp string in file string has SCN string
ORA-19651 cannot apply offline-range record to datafile string: SCN mismatch
ORA-19652 cannot apply offline-range record to datafile string: file is fuzzy
ORA-19653 cannot switch to older file incarnation
ORA-19654 must use backup controlfile to switch file incarnations
ORA-19655 cannot switch to incarnation with different resetlogs data
ORA-19656 cannot backup, copy, or delete online log string
ORA-19657 cannot inspect current datafile string
ORA-19658 cannot inspect string - file is from different resetlogs
ORA-19659 incremental restore would advance file string past resetlogs
ORA-19660 some files in the backup set could not be verified
ORA-19661 datafile string could not be verified
ORA-19662 archived log thread string sequence string could not be verified
ORA-19663 cannot apply current offline range to datafile string
ORA-19664 file type: string, file name: string
ORA-19665 size string in file header does not match actual file size of string
ORA-19666 cannot do incremental restore of the controlfile
ORA-19667 cannot do incremental restore of datafile string
ORA-19668 cannot do full restore of datafile string
ORA-19669 proxy copy functions cannot be run on DISK channel
ORA-19670 file string already being restored
ORA-19671 media management software returned invalid proxy handle
ORA-19672 media management software returned invalid file status
ORA-19673 error during proxy copy of file string
ORA-19674 file string is already being backed up with proxy copy
ORA-19675 file string was modified during proxy copy
ORA-19676 one or more files failed during proxy backup or restore
ORA-19677 RMAN configuration name exceeds maximum length of string
ORA-19678 RMAN configuration value exceeds maximum length of string
ORA-19679 RMAN configuration number string is outside valid range of 1 through string
ORA-19680 some blocks not recovered. See trace file for details
ORA-19681 block media recovery on control file not possible
ORA-19683 real and backup blocksize of file string are unequal
ORA-19684 block media recovery failed because database is suspended
ORA-19690 backup piece release string incompatible with Oracle release string
ORA-19700 device type exceeds maximum length of string
ORA-19701 device name exceeds maximum length of string
ORA-19702 device parameter exceeds maximum length of string
ORA-19703 device command string exceeds maximum length of string
ORA-19704 file name exceeds maximum length of string
ORA-19705 tag value exceeds maximum length of string characters
ORA-19706 invalid SCN
ORA-19707 invalid record block number - string
ORA-19708 log destination exceeds maximum length of string characters
ORA-19709 numeric parameter must be non-negative integer
ORA-19710 unsupported character set string
ORA-19711 cannot use reNormalizeAllFileNames while database is open
ORA-19712 table name exceeds maximum length of string
ORA-19713 invalid copy number: string
ORA-19714 length for generated piece name longer than string
ORA-19715 invalid format for piece name
ORA-19720 Error occurred when converting an OCI number into an SCN
ORA-19721 Cannot find datafile with absolute file number string in tablespace string
ORA-19722 datafile string is an incorrect version
ORA-19723 Cannot recreate plugged in read-only datafile string
ORA-19724 snapshot too old: snapshot time is before file string plug-in time
ORA-19725 can not acquire plug-in enqueue
ORA-19726 cannot plug data [string] at level string into database running at compatibility level string
ORA-19727 cannot plug data [string] at level string into database running Oracle string
ORA-19728 data object number conflict between table string and partition string in table string
ORA-19729 File string is not the initial version of the plugged in datafile
ORA-19730 can not convert offline plugged-in datafile string
ORA-19731 cannot apply change to unverified plugged-in datafile string
ORA-19732 incorrect number of datafiles for tablespace string
ORA-19733 COMPATIBLE parameter needs to be string or greater
ORA-19734 wrong creation SCN - control file expects converted plugged-in datafile
ORA-19735 wrong creation SCN - control file expects initial plugged-in datafile
ORA-19736 can not plug a tablespace into a database using a different national character set
ORA-19999 skip_row procedure was called
ORA-20000 string
ORA-21000 error number argument to raise_application_error of stringstring is out of range
ORA-21001 error number argument to raise_system_error of stringstring is out of range
ORA-21300 objects option not installed
ORA-21301 not initialized in object mode
ORA-21500 internal error code, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
ORA-21501 program could not allocate memory
ORA-21503 program terminated by fatal error
ORA-21520 database server driver not installed
ORA-21521 exceeded maximum number of connections in OCI (object mode only)
ORA-21522 attempted to use an invalid connection in OCI (object mode only)
ORA-21523 functionality not supported by the server (object mode only)
ORA-21524 object type mismatch
ORA-21525 attribute number or (collection element at index) string violated its constraints
ORA-21526 initialization failed
ORA-21560 argument string is null, invalid, or out of range
ORA-21561 OID generation failed
ORA-21600 path expression too long
ORA-21601 attribute is not an object
ORA-21602 operation does not support the specified typecode
ORA-21603 property id [string] is invalid
ORA-21604 property [string] is not a property of transient or value instances
ORA-21605 property [string] is not a property of value instances
ORA-21606 can not free this object
ORA-21607 memory cartridge service handle not initialized
ORA-21608 duration is invalid for this function
ORA-21609 memory being resized without being allocated first
ORA-21610 size [string] is invalid
ORA-21611 key length [string] is invalid
ORA-21612 key is already being used
ORA-21613 key does not exist
ORA-21614 constraint violation for attribute number string
ORA-21615 copy of an OTS (named or simple) instance failed
ORA-21700 object does not exist or is marked for delete
ORA-21701 attempt to flush objects to different servers
ORA-21702 object is not instantiated or has been de-instantiated in cache
ORA-21703 cannot flush an object that is not modified
ORA-21704 cannot terminate cache or connection without flushing first
ORA-21705 service context is invalid
ORA-21706 duration does not exist or is invalid
ORA-21707 pin duration is longer than allocation duration
ORA-21708 inappropriate operation on a transient object
ORA-21709 cannot refresh an object that has been modified
ORA-21710 argument is expecting a valid memory address of an object
ORA-21779 duration not active
ORA-22053 overflow error
ORA-22054 underflow error
ORA-22055 unknown sign flag value [string]
ORA-22056 value [string] is divided by zero
ORA-22057 bad integer length [string]
ORA-22059 buffer size [string] is too small - [string] is needed
ORA-22060 argument [string] is an invalid or uninitialized number
ORA-22061 invalid format text [string]
ORA-22062 invalid input string [string]
ORA-22063 reading negative value [string] as unsigned
ORA-22064 invalid NLS parameter string [string]
ORA-22065 number to text translation for the given format causes overflow
ORA-22130 buffer size [string] is less than the required size [string]
ORA-22131 hexadecimal string length is zero
ORA-22132 hexadecimal string does not correspond to a valid REF
ORA-22140 given size [string] must be in the range of 0 to [string]
ORA-22150 variable-length array has not been initialized
ORA-22151 cannot resize non-zero variable-length array to zero elements
ORA-22152 destination variable-length array is not initialized
ORA-22153 source variable-length array is not initialized
ORA-22160 element at index [string] does not exist
ORA-22161 type code [string] is not valid
ORA-22162 element at index [string] has been previously deleted
ORA-22163 left hand and right hand side collections are not of same type
ORA-22164 delete element operation is not allowed for variable-length array
ORA-22165 given index [string] must be in the range of 0 to [string]
ORA-22166 collection is empty
ORA-22167 given trim size [string] must be less than or equal to [string]
ORA-22275 invalid LOB locator specified
ORA-22276 invalid locator for LOB buffering
ORA-22277 cannot use two different locators to modify the same LOB
ORA-22278 must update the LOB only through the LOB buffers
ORA-22279 cannot perform operation with LOB buffering enabled
ORA-22280 no more buffers available for operation
ORA-22281 cannot perform operation with an updated locator
ORA-22282 non-contiguous append to a buffering enabled LOB not allowed
ORA-22283 filename contains characters that refer to parent directory
ORA-22285 non-existent directory or file for string operation
ORA-22286 insufficient privileges on file or directory to perform string operation
ORA-22287 invalid or modified directory occurred during string operation
ORA-22288 file or LOB operation string failed string
ORA-22289 cannot perform string operation on an unopened file or LOB
ORA-22290 operation would exceed the maximum number of opened files or LOBs
ORA-22291 Open LOBs exist at transaction commit time
ORA-22292 Cannot open a LOB in read-write mode without a transaction
ORA-22293 LOB already opened in the same transaction
ORA-22294 cannot update a LOB opened in read-only mode
ORA-22295 cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement
ORA-22296 invalid ALTER TABLE option for conversion of LONG datatype to LOB
ORA-22297 warning: Open LOBs exist at transaction commit time
ORA-22303 type "string"."string" not found
ORA-22304 input type is not an object type
ORA-22305 attribute/method/parameter "string" not found
ORA-22306 type "string"."string" already exists
ORA-22307 operation must be on a user-defined type
ORA-22308 operation not allowed on evolved type
ORA-22309 attribute with name "string" already exists
ORA-22310 ALTER TYPE error. Refer to table "string"."string" for errors
ORA-22311 type for attribute "string" does not exist
ORA-22312 must specify either CASCADE or INVALIDATE option
ORA-22313 cannot use two versions of the same type "string"
ORA-22314 method information mismatch in ALTER TYPE
ORA-22315 type "string" does not contain a map or order function
ORA-22316 input type is not a collection type
ORA-22317 typecode number is not legal as a number type
ORA-22318 input type is not an array type
ORA-22319 type attribute information altered in ALTER TYPE
ORA-22320 missing user version string
ORA-22321 method does not return any result
ORA-22322 error table "string"."string" has incorrect structure
ORA-22323 error table "string"."string" does not exist
ORA-22324 altered type has compilation errors
ORA-22326 cannot change a type to FINAL if it has subtypes
ORA-22327 cannot change a type to NOT INSTANTIABLE if it has dependent tables
ORA-22328 object "string"."string" has errors. string
ORA-22329 cannot alter a non-object type
ORA-22330 cannot alter a type that is not valid
ORA-22331 cannot alter an incomplete type
ORA-22332 a dependent object in schema "string" has errors. string
ORA-22333 cannot reset type "string"."string" due to invalid dependent types and tables
ORA-22334 cannot reset type "string"."string". Dependent tables must be upgraded to latest version.
ORA-22335 The client cannot work with an altered type
ORA-22336 table contained 8.0 image format, must specify INCLUDING DATA
ORA-22337 the type of accessed object has been evolved
ORA-22338 must specify CASCADE INCLUDING DATA when altering the final property
ORA-22339 cannot alter to not final since its attribute column is substitutable
ORA-22340 cannot string type "string"."string". Dependent tables must be upgraded to latest version
ORA-22341 cannot assign supertype instance to subtype
ORA-22342 dependent VARRAY column exceeds the maximum inline column size
ORA-22343 Compilation error for type invalidated by ALTER TYPE
ORA-22344 can not specify CONVERT TO SUBSTITUTABLE option for ALTER TYPE other than NOT FINAL change
ORA-22345 recompile type string.string before attempting this operation
ORA-22369 invalid parameter encountered in method string
ORA-22370 incorrect usage of method string
ORA-22371 Table contains data of type string.string, version string, which does not exist
ORA-22600 encountered 8.0.2 (Beta) VARRAY data that cannot be processed
ORA-22601 pickler TDS context [string] is not initialized
ORA-22602 pickler TDS handle [string] is not well-formed
ORA-22603 cannot add an attribute to the already generated TDS handle
ORA-22604 TDS handle already generated
ORA-22605 FDO handle [string] is not initialized
ORA-22606 pickler image handle [string] is not well-formed
ORA-22607 image handle already generated
ORA-22608 cannot add an attribute to the already generated image handle
ORA-22609 error string during initialization of FDO
ORA-22610 error while adding a scalar to the image handle
ORA-22611 TDS version is not recognized
ORA-22612 TDS does not describe a collection TDS
ORA-22613 buflen does not match the size of the scalar
ORA-22614 error while construction the collection in the image
ORA-22615 attribute is not a collection
ORA-22616 image is not of Oracle 8.1 format
ORA-22617 error while accessing the image handle collection
ORA-22618 attribute is a BAD NULL in the image handle
ORA-22619 all collection elements have already been accessed
ORA-22620 buffer size too small to hold the value
ORA-22621 error transfering an object from the agent
ORA-22625 OCIAnyData is not well-formed
ORA-22626 Type Mismatch while constructing or accessing OCIAnyData
ORA-22627 tc [string] must be that of object/varray/nested table
ORA-22628 OCIAnyData already constructed
ORA-22629 OCIAnyData is null
ORA-22630 attribute [string] is null or it is not well-formed
ORA-22631 attribute [string] is is not well-formed or does not match the type
ORA-22632 AnyDataSet parameter is not valid for the current operation
ORA-22633 Error freeing AnyDataSet
ORA-22634 Error adding new instance to AnyDataSet
ORA-22800 invalid user-defined type
ORA-22801 invalid object row variable
ORA-22803 object type contains zero attributes
ORA-22804 remote operations not permitted on object tables or user-defined type columns
ORA-22805 cannot insert NULL object into object tables or nested tables
ORA-22806 not an object or REF
ORA-22807 cannot resolve to a scalar type or a collection type
ORA-22808 REF dereferencing not allowed
ORA-22809 nonexistent attribute
ORA-22810 cannot modify object attributes with REF dereferencing
ORA-22812 cannot reference nested table column's storage table
ORA-22813 operand value exceeds system limits
ORA-22814 attribute or element value is larger than specified in type
ORA-22816 unsupported feature with RETURNING clause
ORA-22817 subquery not allowed in the default clause
ORA-22818 subquery expressions not allowed here
ORA-22819 scope of input value does not correspond to the scope of the target
ORA-22826 cannot construct an instance of a non instantiable type
ORA-22828 input pattern or replacement parameters exceed 32K size limit
ORA-22850 duplicate LOB storage option specificed
ORA-22851 invalid CHUNK LOB storage option value
ORA-22852 invalid PCTVERSION LOB storage option value
ORA-22853 invalid LOB storage option specification
ORA-22854 invalid option for LOB storage index
ORA-22855 optional name for LOB storage segment incorrectly specified
ORA-22856 cannot add columns to object tables
ORA-22857 cannot modify columns of object tables
ORA-22858 invalid alteration of datatype
ORA-22859 invalid modification of columns
ORA-22860 object type expected
ORA-22861 invalid user-defined type
ORA-22862 specified object identifier doesn't match existing object identifier
ORA-22863 synonym for datatype string.string not allowed
ORA-22864 cannot ALTER or DROP LOB indexes
ORA-22865 more than one column specified
ORA-22866 default character set is of varying width
ORA-22868 table with LOBs contains segments in different tablespaces
ORA-22869 depth of type dependency hierarchy exceeds maximum limit
ORA-22870 ALTER TYPE with REPLACE option a non-object type
ORA-22871 ALTER TYPE with REPLACE is not allowed for pure incomplete types
ORA-22872 OID INDEX clause not allowed on tables with primary key based object identifiers
ORA-22873 primary key not specified for primary key based object table
ORA-22874 attribute "string" is not part of the type "string"
ORA-22875 cannot drop primary key of an object table whose object identifier is primary key based
ORA-22876 this user-defined type is not allowed or it cannot be used in this context
ORA-22877 invalid option specified for a HASH partition or subpartition of a LOB column
ORA-22878 duplicate LOB partition or subpartition specified
ORA-22879 cannot use the LOB INDEX clause for partitioned tables
ORA-22880 invalid REF
ORA-22881 dangling REF
ORA-22882 object creation failed
ORA-22883 object deletion failed
ORA-22884 object modification failed
ORA-22885 cannot get REF to a non-persistent object
ORA-22886 scoped table "string" in schema "string" is not an object table
ORA-22887 type of REF column is not the same as that of its scoped table
ORA-22888 duplicate SCOPE clauses for a REF column
ORA-22889 REF value does not point to scoped table
ORA-22890 cannot specify name for REF column constraint
ORA-22891 cannot have multiple columns in REF constraint
ORA-22892 scoped table "string" does not exist in schema "string"
ORA-22893 constraint can be specified only for REF columns
ORA-22894 cannot add constraint on existing unscoped REF columns of non-empty tables
ORA-22895 referenced table "string" in schema "string" is not an object table
ORA-22896 cannot have both scope and referential constraint on REF column "string"
ORA-22897 no scope clause specified for user-defined REF column "string"
ORA-22898 existing scope clause on "string" points to a table other than the one mentioned in the referential constraint
ORA-22899 cannot specify both scope and rowid constraint on ref column
ORA-22900 the SELECT list item of THE subquery is not a collection type
ORA-22901 cannot compare nested table or VARRAY or LOB attributes of an object type
ORA-22902 CURSOR expression not allowed
ORA-22903 MULTISET expression not allowed
ORA-22904 invalid reference to a nested table column
ORA-22905 cannot access rows from a non-nested table item
ORA-22906 cannot perform DML on expression or on nested table view column
ORA-22907 invalid CAST to a type that is not a nested table or VARRAY
ORA-22908 reference to NULL table value
ORA-22909 exceeded maximum VARRAY limit
ORA-22910 cannot specify schema name for nested tables
ORA-22911 duplicate storage specification for the nested table item
ORA-22912 specified column or attribute is not a nested table type
ORA-22913 must specify table name for nested table column or attribute
ORA-22914 DROP of nested tables not supported
ORA-22915 cannot ALTER nested tables to ADD/MODIFY columns
ORA-22916 cannot do an exact FETCH on a query with Nested cursors
ORA-22917 use VARRAY to define the storage clause for this column or attribute
ORA-22918 specified column or attribute is not a VARRAY type
ORA-22919 dangling REF error or lock object failed for no wait request
ORA-22920 row containing the LOB value is not locked
ORA-22921 length of input buffer is smaller than amount requested
ORA-22922 nonexistent LOB value
ORA-22923 amount of data specified in streaming LOB write is 0
ORA-22924 snapshot too old
ORA-22925 operation would exceed maximum size allowed for a LOB value
ORA-22926 specified trim length is greater than current LOB value's length
ORA-22927 invalid LOB locator specified
ORA-22928 invalid privilege on directories
ORA-22929 invalid or missing directory name
ORA-22930 directory does not exist
ORA-22931 MOVE of nested table to a different tablespace not supported
ORA-22933 cannot change object with type or table dependents
ORA-22950 cannot ORDER objects without MAP or ORDER method
ORA-22951 NULL returned by ORDER method
ORA-22970 name does not correspond to an object view
ORA-22971 invalid datatype for PRIMARY KEY-based object identifier
ORA-22972 NULL value not allowed in PRIMARY KEY-based object identifier
ORA-22973 size of object identifier exceeds maximum size allowed
ORA-22974 missing WITH OBJECT OID clause
ORA-22975 cannot create a PRIMARY KEY-based REF to this object view
ORA-22976 incorrect number of arguments to MAKE_REF
ORA-22977 missing or invalid attribute
ORA-22978 only simple attribute name is allowed in the WITH OBJECT OID clause
ORA-22979 cannot INSERT object view REF or user-defined REF
ORA-22980 must specify a set of attributes for the WITH OBJECT OID clause
ORA-22981 must specify a table/view having system generated OID
ORA-22982 cannot create sub-view under this view
ORA-22983 not a user-defined REF
ORA-22984 view query cannot contain references to a super view
ORA-22990 LOB locators cannot span transactions
ORA-22991 insufficient space allocated for argument string
ORA-22992 cannot use LOB locators selected from remote tables
ORA-22993 specified input amount is greater than actual source amount
ORA-22994 source offset is beyond the end of the source LOB
ORA-22995 TABLESPACE DEFAULT option is invalid in this context
ORA-22996 NEXT extent size is smaller than LOB chunksize
ORA-22997 VARRAY | OPAQUE stored as LOB is not specified at the table level
ORA-22998 CLOB or NCLOB in multibyte character set not supported
ORA-23290 This operation may not be combined with any other operation
ORA-23291 Only base table columns may be renamed
ORA-23292 The constraint does not exist
ORA-23293 Cannot rename a column which is part of a join index
ORA-23300 string
ORA-23301 mixed use of deferred rpc destination modes
ORA-23302 application raised communication failure during deferred RPC
ORA-23303 application raised generic exception during deferred RPC
ORA-23304 malformed deferred rpc at arg string of string in call string, in tid string
ORA-23305 internal deferred RPC error: string
ORA-23306 schema string does not exist
ORA-23307 replicated schema string already exists
ORA-23308 object string.string does not exist or is invalid
ORA-23309 object string.string of type string exists
ORA-23310 object group "string"."string" is not quiesced
ORA-23312 not the masterdef according to string
ORA-23313 object group "string"."string" is not mastered at string
ORA-23314 database is not a materialized view site for "string"."string"
ORA-23315 repcatlog version or request string is not supported by version string
ORA-23316 the masterdef is string
ORA-23317 a communication failure has occurred
ORA-23318 a ddl failure has occurred
ORA-23319 parameter value string is not appropriate
ORA-23320 the request failed because of values string and string
ORA-23321 Pipename may not be null
ORA-23322 Privilege error accessing pipe
ORA-23323 parameter length exceeds deferred RPC limits
ORA-23324 error string, while creating deferror entry at "string" with error string
ORA-23325 parameter type is not string
ORA-23326 object group "string"."string" is quiesced
ORA-23327 imported deferred rpc data does not match string of importing db
ORA-23328 mview base table "string"."string" differs from master table "string"."string"
ORA-23329 successful user-provided ddl but no materialized view "string"."string"
ORA-23330 column group string already exists
ORA-23331 column group string does not exist
ORA-23332 group string is in use; cannot drop
ORA-23333 column string is already part of a column group
ORA-23334 column string does not exist in table or column group
ORA-23335 priority group string already exists
ORA-23336 priority group string does not exist
ORA-23337 priority or value not in priority group string
ORA-23338 priority or value already in priority group string
ORA-23339 duplicate conflict resolution information
ORA-23340 incorrect resolution method string
ORA-23341 user function required
ORA-23342 invalid parameter column string
ORA-23343 no match for specified conflict resolution information
ORA-23344 constraint (string.string) does not exist
ORA-23345 table "string"."string" not registered to collect statistics
ORA-23346 primary key or object ID is undefined for table or materialized view string
ORA-23347 datatype string for column string table string not supported
ORA-23348 cannot replicate procedure string; only IN parameters supported
ORA-23349 cannot generate replication support for functions
ORA-23350 maximum number of recursive calls exceeded
ORA-23351 parameter datatype string for procedure string not supported
ORA-23352 duplicate destination for deferred transaction
ORA-23353 deferred RPC queue has entries for object group "string"."string"
ORA-23354 deferred RPC execution disabled for "string" with "string"
ORA-23355 object string.string does not exist or is invalid at master site
ORA-23356 masterdef recognizes a master which does not recognize the masterdef
ORA-23357 the propagator does not exist
ORA-23358 invalid remote user
ORA-23359 error on creating a ddl record for a repcatlog record
ORA-23360 only one materialized view for master table "string" can be created
ORA-23361 materialized view "string" does not exist at master site
ORA-23362 invalid user
ORA-23363 mismatch of mview base table "string" at master and mview site
ORA-23364 Feature not enabled: Advanced replication
ORA-23365 site string does not exist
ORA-23366 integer value string is less than 1
ORA-23367 table string is missing the primary key
ORA-23368 name string cannot be null or the empty string
ORA-23369 value of "string" argument cannot be null
ORA-23370 table string and table string are not shape equivalent (string)
ORA-23371 column string unknown in table string
ORA-23372 type string in table string is unsupported
ORA-23373 object group "string"."string" does not exist
ORA-23374 object group "string"."string" already exists
ORA-23375 feature is incompatible with database version at string
ORA-23376 node string is not compatible with replication version "string"
ORA-23377 bad name string for missing_rows_oname1 argument
ORA-23378 connection qualifier "string" is not valid for object group "string"."string"
ORA-23379 connection qualifier "string" is too long
ORA-23380 propagation mode "string" is not valid
ORA-23381 generated object for base object string.string@string does not exist
ORA-23382 materialized view repgroup "string"."string" is not registered at site string
ORA-23383 registration for materialized view repgroup "string"."string" failed at site string
ORA-23384 replication parallel push string argument out of range
ORA-23385 replication parallel push string argument not valid
ORA-23386 replication parallel push cannot create slave processes
ORA-23387 replication parallel push dequeue error
ORA-23388 replication parallel push watermark error
ORA-23389 obsolete procedure; drop objects and recreate using new master
ORA-23392 could not find materialized view to be associated with "string"."string"
ORA-23393 the user is already the propagator
ORA-23394 duplicate propagator
ORA-23395 object "string"."string" of type "string" does not exist or is invalid
ORA-23396 database link "string" does not exist or has not been scheduled
ORA-23397 global name "string" does not match database link name "string"
ORA-23398 user name "string" at database link "string" does not match local user name "string"
ORA-23399 generation of replication support for "string"."string" is not complete
ORA-23400 invalid materialized view name "string"
ORA-23401 materialized view "string"."string" does not exist
ORA-23402 refresh was aborted because of conflicts caused by deferred txns
ORA-23403 refresh group "string"."string" already exists
ORA-23404 refresh group "string"."string" does not exist
ORA-23405 refresh group number string does not exist
ORA-23406 insufficient privileges on user "string"
ORA-23407 object name string must be shaped like "schema"."object" or "object"
ORA-23408 this replication operation is not supported in a mixed configuration
ORA-23409 could not find an unused refresh group number
ORA-23410 materialized view "string"."string" is already in a refresh group
ORA-23411 materialized view "string"."string" is not in refresh group "string"."string"
ORA-23412 master table's primary key columns have changed
ORA-23413 table "string"."string" does not have a materialized view log
ORA-23414 materialized view log for "string"."string" does not record rowid values
ORA-23415 materialized view log for "string"."string" does not record the primary key
ORA-23416 table "string"."string" does not contain a primary key constraint
ORA-23417 unknown materialized view type: string
ORA-23418 cannot unregister the propagator who is currently in use
ORA-23419 regenerate replication support before resuming master activity
ORA-23420 interval must evaluate to a time in the future
ORA-23421 job number string is not a job in the job queue
ORA-23422 Oracle Server could not generate an unused job number
ORA-23423 job number string is not positive
ORA-23424 materialized view "string"."string" at string not registered
ORA-23425 invalid materialized view identifier string
ORA-23426 deferred RPC queue has entries for string
ORA-23427 deferred purge queue argument string out of range
ORA-23428 job associated instance number string is not valid
ORA-23430 argument "string" cannot be NULL or empty string
ORA-23431 wrong state: string
ORA-23432 master site string already exists
ORA-23433 executing against wrong master site string
ORA-23434 master site string not known for object group
ORA-23435 cannot create an updatable ROWID materialized view with LOB columns
ORA-23436 missing template authorization for user
ORA-23437 template authorization already exists for user
ORA-23438 missing refresh group template
ORA-23439 refresh group template already exists
ORA-23440 incorrect public template value
ORA-23441 object does not exist for refresh group template
ORA-23442 object already exists for the refresh group template
ORA-23443 missing template parameter
ORA-23444 duplicate template parameter
ORA-23445 missing template site
ORA-23446 duplicate template site
ORA-23447 missing user parameter value
ORA-23448 duplicate user parameter value
ORA-23449 missing user name
ORA-23450 flavor already contains object "string"."string"
ORA-23451 flavor string already defined for object group "string"."string"
ORA-23452 flavor string of object group "string"."string" is already published
ORA-23453 requested operation is not supported on top flavor
ORA-23454 flavor string not defined for object group "string"."string"
ORA-23455 flavor string contains object "string"
ORA-23456 flavor string does not contain "string"
ORA-23457 invalid flavor ID string
ORA-23458 inappropriate flavor string at string
ORA-23459 flavor string must contain "string"
ORA-23460 missing value for column string in resolution method "string" for "string"."string"."string"
ORA-23461 fail to resolve conflict for "string"."string"."string"
ORA-23462 flavor string in use at site string
ORA-23463 flavor incompatible with object "string"."string"
ORA-23464 flavor lacks column string of "string"."string"
ORA-23465 flavor already includes column string of "string"."string"
ORA-23466 flavor requires missing object "string"."string"
ORA-23467 flavor lacks object "string"."string"
ORA-23468 missing string string
ORA-23469 string is different between templates
ORA-23470 invalid status
ORA-23471 template not authorized for user
ORA-23472 materialized view "string"."string" must be atomically refreshed
ORA-23473 replication RPC processing for "string"."string" is disabled
ORA-23474 definition of "string"."string" has changed since generation of replication support
ORA-23475 key column string must be sent and compared
ORA-23476 cannot import from string to string
ORA-23477 unable to alter propagation mode for object group "string"."string"
ORA-23478 object group string is already mastered at string
ORA-23480 Column string is not a top-level column of "string"."string".
ORA-23482 column string of "string"."string": object types not allowed.
ORA-23483 object "string"."string" not allowed in this operation.
ORA-23484 internal internet Application Server error: string
ORA-23485 Column group "string" must consist of a single numeric column only
ORA-23487 object groups "string"."string" and "string"."string" do not have the same connection qualifier
ORA-23488 propagation mode "string" for "string" is not allowed for this operation
ORA-23489 duplicate entry "string"
ORA-23490 extension request "string" with status "string" not allowed in this operation
ORA-23491 no valid extension request at "string"
ORA-23492 no new sites for extension request "string"
ORA-23493 "string" is not a new site for extension request "string"
ORA-23494 too many rows for destination "string"
ORA-23495 serial propagation can not be used for "string"
ORA-23496 can not change disabled status for "string" and "string"
ORA-23500 cannot switch master for a multi-tier materialized view repgroup "string"."string"
ORA-23501 refresh template cannot be instantiated for database with compatibility equal to or less than 8.0
ORA-23502 valid directory for offline instantiation is not specified
ORA-23503 error occurred during IAS instantiation
ORA-23504 columns added to table do not match list of columns to be added
ORA-23505 Object "string"."string" is missing.
ORA-23514 invalid or incorrect number of arguments
ORA-23515 materialized views and/or their indices exist in the tablespace
ORA-23531 site owner already exists in the template
ORA-23532 tables with different synchronization mechanisms are in the same group
ORA-23533 object "string"."string" can not be cached
ORA-23534 missing column in materialized view container table "string"."string"
ORA-23535 instantiating templates from multiple back ends is not allowed
ORA-23536 the object "string"."string" is not cached at the middle tier as expected.
ORA-23537 function or procedure string is not allowed to be invoked from this site.
ORA-23538 cannot explicitly refresh a NEVER REFRESH materialized view ("string")
ORA-23600 cannot create PROPAGATION, string already exists
ORA-23601 PROPAGATION_NAME string does not exist
ORA-23602 Invalid streams process type string
ORA-23605 invalid value "string" for STREAMS parameter string
ORA-23606 invalid object string
ORA-23607 invalid column "string"
ORA-23608 invalid resolution column "string"
ORA-23619 non-Oracle system error: string
ORA-24000 invalid value string, string should be of the form [SCHEMA.]NAME
ORA-24001 cannot create QUEUE_TABLE, string already exists
ORA-24002 QUEUE_TABLE string does not exist
ORA-24003 Queue table index string inconsistent with queue table string
ORA-24004 invalid column name string in SORT_LIST, should be ENQ_TIME or PRIORITY
ORA-24005 must use DBMS_AQADM.DROP_QUEUE_TABLE to drop queue tables
ORA-24006 cannot create QUEUE, string already exists
ORA-24007 invalid value string, MAX_RETRIES should be non-negative integer
ORA-24008 queue table string.string must be dropped first
ORA-24009 invalid value string, QUEUE_TYPE should be NORMAL_QUEUE or EXCEPTION_QUEUE
ORA-24010 QUEUE string does not exist
ORA-24011 cannot drop QUEUE, string should be stopped first
ORA-24012 cannot drop QUEUE_TABLE, some queues in string have not been dropped
ORA-24013 invalid value string, RETRY_DELAY should be non-negative
ORA-24014 invalid value string, RETENTION_TIME should be FOREVER or non-negative
ORA-24015 cannot create QUEUE_TABLE, QUEUE_PAYLOAD_TYPE string.string does not exist
ORA-24016 cannot create QUEUE_TABLE, user string does not have execute privileges on QUEUE_PAYLOAD_TYPE string.string
ORA-24017 cannot enable enqueue on QUEUE, string is an exception queue
ORA-24018 STOP_QUEUE on string failed, outstanding transactions found
ORA-24019 identifier for string too long, should not be greater than string characters
ORA-24020 Internal error in DBMS_AQ_IMPORT_INTERNAL, string
ORA-24021 queue table definition not imported for string.string
ORA-24022 the specified parameters has no effect on the queue
ORA-24023 Internal error in DBMS_AQ_EXP_INTERNAL.string [string] [string]
ORA-24024 Internal error in DBMS_AQ_IMP_INTERNAL.string [string] [string]
ORA-24025 invalid value string, QUEUE_PAYLOAD_TYPE should be RAW or an object type
ORA-24026 operation failed, queue string.string has errors
ORA-24027 AQ HTTP propagation encountered error, status-code string, string
ORA-24028 cannot create a reciever non-repudiable single consumer queue
ORA-24029 operation not allowed on a single-consumer queue
ORA-24030 Only one of rule or rule-set must be specified
ORA-24031 invalid value, string should be non-NULL
ORA-24032 object string exists, index could not be created for queue table string
ORA-24033 no recipients for message
ORA-24034 application string is already a subscriber for queue string
ORA-24035 AQ agent string is not a subscriber for queue string
ORA-24036 invalid SORT_ORDER column string specified for queue table
ORA-24037 schema string in QUEUE_NAME is not same as schema string in QUEUE_TABLE
ORA-24038 RETRY_DELAY and MAX_RETRIES cannot be used for a 8.0 compatible multiple consumer queue
ORA-24039 Queue string not created in queue table for multiple consumers
ORA-24041 propagation schedule exists for QUEUE string and DESTINATION string
ORA-24042 no propagation schedule exists for QUEUE string and DESTINATION string
ORA-24043 destination string uses a reserved name, names with AQ$_ prefix are not valid
ORA-24044 source string and destination string object types do not match
ORA-24045 invalid agent address string, agent address should be of the form [SCHEMA.]NAME[@DATABASE LINK]
ORA-24046 protocol attribute reserved for future use
ORA-24047 invalid agent name string, agent name should be of the form NAME
ORA-24048 cannot create QUEUE_TABLE, user does not have access to AQ object types
ORA-24049 invalid agent name string, names with AQ$_ prefix are not valid
ORA-24050 subscribers are not supported for exception queue string
ORA-24051 cannot propagate object type payloads that have a REF or BFILE attribute
ORA-24052 cannot propagate object type payloads with LOB attributes to an 8.0 release
ORA-24053 PRIMARY_INSTANCE and SECONDARY_INSTANCE must be non-negative
ORA-24054 cannot propagate to an Oracle 8.0.3 release or lower release
ORA-24055 cannot delete propagation status rows that are in prepared state
ORA-24056 internal inconsistency for QUEUE string and destination string
ORA-24057 cannot define subscriber with rule for queue string
ORA-24058 cannot downgrade QUEUE_TABLE that has propagation in a prepared state
ORA-24059 invalid COMPATIBLE parameter setting string specified in DBMS_AQADM.string
ORA-24060 cannot convert QUEUE_TABLE, string already is compatible with release string
ORA-24061 cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero
ORA-24062 Subscriber table string inconsistent with queue table string
ORA-24063 cannot downgrade QUEUE_TABLE that has queues with rule-based subscribers
ORA-24064 propagation for QUEUE string and DESTINATION string already enabled
ORA-24065 propagation for QUEUE string and DESTINATION string already disabled
ORA-24066 invalid privilege specified
ORA-24067 exceeded maximum number of subscribers for queue string
ORA-24068 cannot start queue string, queue table string is being migrated
ORA-24069 cannot downgrade queue table string while it is being upgraded
ORA-24070 cannot upgrade queue table string while it is being downgraded
ORA-24071 cannot perform operation string, queue table string is being migrated
ORA-24072 cannot execute MIGRATE_QUEUE_TABLE procedure; must own queue table
ORA-24073 cannot specify RETENTION_TIME on exception queue string.string
ORA-24074 RETRY_DELAY and MAX_RETRIES cannot be used for exception queue string
ORA-24075 cannot specify agent with NULL address and non-NULL protocol
ORA-24076 cannot perform operation string for NON_PERSISTENT queue string.string
ORA-24077 cannot create propagation schedule for EXCEPTION queue string.string
ORA-24078 cannot specify a non-NULL SECONDARY_INSTANCE if PRIMARY_INSTANCE was NULL
ORA-24079 invalid name string, names with AQ$_ prefix are not valid for string
ORA-24080 unschedule_propagation pending for QUEUE string and DESTINATION string
ORA-24081 compatible parameter needs to be string or greater
ORA-24082 propagation may still be happening for the schedule for QUEUE string and DESTINATION string
ORA-24083 cannot specify remote subscribers for string QUEUE string
ORA-24084 DBLINK name in address field of agent string is not unique within the first 24 bytes"
ORA-24085 operation failed, queue string is invalid
ORA-24086 cannot create an 8.0 compatible string queue
ORA-24087 Invalid database user string
ORA-24088 AQ Agent string does not exist
ORA-24089 AQ Agent string already exists
ORA-24090 at least one protocol must be enabled
ORA-24093 AQ agent string not granted privileges of database user string
ORA-24094 invalid transformation, target type does not match that of the queue
ORA-24095 invalid transformation, source type does not match that of the queue
ORA-24096 invalid message state specified
ORA-24097 Invalid value string, string should be non-negative
ORA-24098 invalid value string for string
ORA-24099 operation not allowed for 8.0 compatible queues
ORA-24100 error in ktz testing layer
ORA-24120 invalid string parameter passed to DBMS_REPAIR.string procedure
ORA-24121 both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
ORA-24122 invalid block range specification
ORA-24123 feature string is not yet implemented
ORA-24124 invalid ACTION parameter passed to DBMS_REPAIR.string procedure
ORA-24125 Object string.string has changed
ORA-24126 invalid CASCADE_FLAG passed to DBMS_REPAIR.string procedure
ORA-24127 TABLESPACE parameter specified with an ACTION other than CREATE_ACTION
ORA-24128 partition name specified for a non-partitioned object
ORA-24129 table name string does not start with string prefix
ORA-24130 table string does not exist
ORA-24131 table string has incorrect columns
ORA-24132 table name string is too long
ORA-24141 rule set string.string does not exist
ORA-24142 invalid ruleset name
ORA-24143 invalid evaluation context name
ORA-24144 rules engine internal error, arguments: [string], [string]
ORA-24145 evaluation context string.string already exists
ORA-24146 rule string.string already exists
ORA-24147 rule string.string does not exist
ORA-24148 cannot drop rule string.string with dependents
ORA-24149 invalid rule name
ORA-24150 evaluation context string.string does not exist
ORA-24151 no evaluation context is associated with rule string.string or rule set string.string
ORA-24152 cannot drop evaluation context string.string with dependents
ORA-24153 rule set string.string already exists
ORA-24154 rule string.string already in rule set string.string
ORA-24155 rule string.string not in rule set string.string
ORA-24156 duplicate table alias string
ORA-24157 duplicate variable name string
ORA-24158 invalid table alias
ORA-24159 invalid variable definition
ORA-24160 name string already exists in the name value pair list
ORA-24161 name string does not exist in the name value pair list
ORA-24162 name value pair list is full, cannot add another entry
ORA-24163 dblink is not supported in rules engine DDLs
ORA-24164 invalid rule engine system privilege: string
ORA-24165 invalid rule engine object privilege: string
ORA-24166 evaluation context string.string has errors
ORA-24168 rule string.string cannot have default evaluation context
ORA-24169 rule condition has unrecognized variables
ORA-24180 invalid transformation expression, the transformation expression does not evaluate to the target type/attribute
ORA-24181 The type string does not exist
ORA-24182 attribute number specified does not exist
ORA-24183 invalid transformation
ORA-24184 transformation string.string, already exists
ORA-24185 Transformation string.string, does not exist
ORA-24186 wrong object type, could not transform message
ORA-24190 length of payload excceeds string
ORA-24191 the property name string has existed
ORA-24192 the property name cannot be null
ORA-24193 the property value exceeds the valid range string
ORA-24201 duplicate publisher, publisher already added to the queue
ORA-24202 publisher does not exist for the queue
ORA-24270 a row already exists in the string table for these parameters
ORA-24271 translation type must be either T, S or M
ORA-24272 initialization value must be either F or T
ORA-24273 translation text is required if translation type is T or S
ORA-24274 no row exists in the string table for these parameters
ORA-24275 function 'string' parameter 'string' missing or invalid
ORA-24276 function 'string' output 'string' maximum value exceeded
| Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
1万+
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
