Cause: An attept was made to modify optimizer statistics of the object.
Action: Unlock statistics with the DBMS_STATS.UNLOCK_TABLE_STATS procedure on base table(s). Retry the operation if it is okay to update statistics.
ORA-38101: Invalid column in the INSERT VALUES Clause: string
Cause: INSERT VALUES clause refers to the destination table columns
Action: none
ORA-38102: Invalid column in the INSERT WHERE Clause: string
Cause: INSERT WHERE clause refers to the destination table columns
Action: none
ORA-38103: Invalid column in the UPDATE SET Clause: string
Cause: UPDATE SET clause refers to the source table columns in the LHS
Action: none
ORA-38104: Columns referenced in the ON Clause cannot be updated: string
Cause: LHS of UPDATE SET contains the columns referenced in the ON Clause
Action: none
ORA-38105: Delete not yet supported when Update row-migration is possible
Cause: When Update Row-Migration is possible, Delete in MERGE is not yet supported
Action: none
ORA-38201: assert if pin during flush
Cause: internal use only
Action: enables checking for bugs in upper layers when there is a pin on a buffer or there are users for buffer and we are trying to flush the object associated with the buffer
ORA-38303: invalid option for PURGE TABLESPACE
Cause: Either a token other than USER was found following the tablespace name or some text was found following USER <user name>.
Action: Place nothing or only USER <user name> after the tablespace name
ORA-38304: missing or invalid user name
Cause: A valid user name was expected.
Action: Specify a valid user name.
ORA-38305: object not in RECYCLE BIN
Cause: Trying to Flashback Drop an object which is not in RecycleBin.
Action: Only the objects in RecycleBin can be Flashback Dropped.
ORA-38306: this object is not recoverable standalone
Cause: Trying to flashback drop an object other than of type TABLE.
Action: Only tables are recoverable.
ORA-38307: object not in RECYCLE BIN
Cause: Trying to Purge the object which is not in RecycleBin.
Action: Only the objects in RecycleBin can be PURGEDED.
ORA-38309: object not purgable
Cause: An attempt was made to purge an object that is either not purgable or else dependent upon some other object.
Action: Cannot purge this object.
ORA-38310: cannot purge tablespace for other users
Cause: An attempt was made to purge the tablespace for a different user by a user who does not have system DBA priviledges.
Action: Cannot purge the tablespace for some other user.
ORA-38311: cannot purge objects owned by other users
Cause: An attempt was made to purge an object which is owned by some other user.
Action: Cannot purge this object.
ORA-38312: original name is used by an existing object
Cause: An attempt was made to recover an object preserving the original name, but that name is taken up by some other object.
Action: use the RENAME clause to recover the object with a different name.
ORA-38401: synonym string not allowed
Cause: An attempt was made to use a synonym for a data type of an attribute or a table alias.
Action: Use the object name instead of the synonym.
ORA-38402: invalid name: empty string or spaces in the name
Cause: There were spaces in the name.
Action: Remove spaces in the name or use quotes around the name.
ORA-38403: attribute set name may not be longer than 22 characters
Cause: The attribute set name was longer than 22 characters.
Action: Choose a name that has 22 or fewer characters.
ORA-38404: schema extension not allowed for the attribute set name
Cause: There was a schema extension for the attribute set name. Attribute sets are always created in the current schema and thus schema extended names are not allowed.
Action: Create the attribute set from the appropriate schema.
ORA-38405: quotes not allowed in the attribute set name
Cause: The attribute set name contained quotes.
Action: Remove quotes in the attribute set name.
ORA-38406: attribute set string already exists
Cause: An attribute set with a matching name already exists in the current schema.
Action: Drop the existing attribute set or choose a different name.
ORA-38407: The ADT associated with the attribute set already exists.
Cause: The Abstract type (ADT) with the same name as the attribute set already exists in the current schema.
Action: Create the attribute set for the existing ADT or drop the ADT.
ORA-38408: The ADT "string" does not exist in the current schema.
Cause: An attempt was made to create the attribute set from a nonexistent ADT.
Action: Make sure that the ADT with the same name as the attribute set exists in the current schema.
ORA-38409: invalid name or option for the attribute set: string
Cause: An invalid name or option was used for the attribute set.
Action: Set serveroutput ON and repeat the operation for additional information.
ORA-38410: schema extension not allowed for the table name
Cause: An attempt was made to use a schema extended name for the table storing expressions.
Action: The table storing expressions and the corresponding attribute set should be created in the same schema.
ORA-38411: invalid datatype for the column storing expressions
Cause: An attempt was made to create an expression column from a column of invalid datatype.
Action: Create a VARCHAR2 or CHAR column to store expressions in a table.
ORA-38412: Expression set column string does not exist.
Cause: The column storing expressions does not exist.
Action: Pass a valid name for the column storing expressions.
ORA-38413: elementary attribute name may not be longer than 32 characters
Cause: An attempt was made to create an elementary attribute with a name longer than 32 characters.
Action: Use a shorter name for the elementary attribute.
ORA-38414: invalid datatype for the attribute string
Cause: The datatype specified for the attribute was invalid.
Action: If the datatype is an ADT, make sure that the ADT exists and the current user has execute permissions to it.
ORA-38415: invalid name or datatype for the attribute: string
Cause: An invalid name or datatype was used for the attribute.
Action: Set serveroutput ON and repeat the operation for additional information.
ORA-38416: A stored attribute may not be longer then 300 characters.
Cause: An attempt was made to create a stored or indexed attribute longer than 300 characters.
Action: A predicate with such attribute may not be indexed. It will be evaluated as sparse predicate.
ORA-38417: attribute set string does not exist
Cause: An attempt was made to use an attribute set that does not exist.
Action: Create the attribute set or choose an existing attribute set.
ORA-38418: ADT associated with the attribute set string does not exist
Cause: The ADT with the same name as the attribute set was not found in the current schema.
Action: Drop the attribute set and recreate it.
ORA-38419: invalid identifier in attribute : string
Cause: An identifier used in the stored/indexed attribute sub-expression was not defined or was invalid.
Action: Create all the required elementary attributes and user-defined functions and try again.
Cause: The sub-expression used for the stored expression was invalid.
Action: Set serveroutput ON and repeat the operation for additional information.
ORA-38421: attribute string already exists
Cause: An attribute with a matching name (or form) already exists in the attribute set.
Action: Drop the existing attribute or choose a different name for the new attribute.
ORA-38422: invalid datatype for the attribute: string
Cause: An attempt was made to create an attribute with invalid datatype.
Action: If the data type of the attribute is an ADT, make sure that the type exists.
ORA-38423: Attribute set created from an ADT may not be extended.
Cause: An attempt was made to add an elementary attribute to an attribute set created from an ADT.
Action: Create a new attribute set and add all the required elementary attributes one at a time.
ORA-38424: no attribute set currently assigned to the expression set
Cause: An attempt was made to un-assign an attribute set from an expression set when there is no attribute set assigned to it.
Action: No action is required.
ORA-38425: attribute set used for an index object may not be unassigned
Cause: An attempt was made to un-assign an attribute set from an expression set when there is an Expression Filter index defined on the column.
Action: Drop the index before un-assigning the attribute set.
ORA-38426: attribute set assigned to an expression set may not be dropped
Cause: An attempt was made to drop an attribute set when it is still associated with an expression set.
Action: Un-assign the attribute set from the expression set before dropping it.
ORA-38427: attribute string does not exist
Cause: An attempt was made to use an attribute set that does not exist.
Action: Create the attribute set.
ORA-38428: too many attributes selected for indexing
Cause: An attempt was made to create an expression filter index with more than 490 indexed attributes.
Action: Remove some of the indexed attributes. Make sure that the default indexed attributes associated with the attribute set combined with the indexed attributes specified in the Create Index Parameters clause are less than or equal to 490.
ORA-38429: invalid datatype for a stored attribute: string
Cause: The (resulting) datatype for the attribute was not appropriate for storing.
Action: Choose a stored attribute that has a resulting datatype of NUMBER, VARCHAR2, CHAR or DATE.
ORA-38430: Operation "string" not supported in the current release.
Cause: An attempt was made to perform an unsupported operation.
Action: Do not use the operation.
ORA-38431: could not evaluate subexpression "string" for rowid "string"
Cause: Either the expression was not a valid SQL-WHERE clause format or it had references to nonexistent schema objects.
Action: Correct the expression.
ORA-38432: EVALUATE operator only allowed on an expression column
Cause: An attempt was made to use the EVALUATE operator on a column not configured as a column storing expressions.
Action: Assign an attribute set to the column.
ORA-38433: index "string" could not be maintained due to "string"
Cause: The error was caused by the recursive operation.
Action: Fix the error and retry.
ORA-38434: could not evaluate expression "string"
Cause: Either the expression was not in a valid SQL-WHERE clause format or it had references to nonexistent schema objects or there is a missing attribute value.
Action: Set serveroutput ON for more details.
ORA-38435: missing elementary attribute value or invalid name-value pairs
Cause: The second argument to the EVALUATE operator had either a missing attribute or an invalid value for an attribute.
Action: Try again after fixing the error.
ORA-38436: attribute set used for an Expression set may not be modified.
Cause: An attempt was made to add an elementary attribute to an attribute set assigned to an expression set.
Action: Un-assign the attribute set and try again.
ORA-38437: The ADT "string" may not contain any user methods.
Cause: An attempt was made to create an attribute set from an ADT that has one or more user methods.
Action: Drop the ADT and recreate it with no user methods.
ORA-38438: getVarchar not possible due to "string" datatype in the attribute set
Cause: An attempt was made to use the getVarchar API when the attribute set has one or more non-scalar types.
Action: Use AnyData conversion to encode the data item.
ORA-38439: invalid operation "string"
Cause: An attempt was made to use an invalid operation.
Action: Use one of the following operations : ADD, DROP
ORA-38440: attribute set string does not exist
Cause: An attempt was made to copy an attribute set that is not accessible from the current schema.
Action: Grant execute permissions on the corresponding ADT to the current user and try again.
ORA-38441: System could not derive the list of STORED and INDEXED attributes.
Cause: The attribute set was created without default index parameters.
Action: Specify the default index parameters for the attribute set or include a valid PARAMETERS clause for the CREATE INDEX command.
ORA-38442: The ADT "string" is not in a valid state.
Cause: An attempt was made to use an ADT that is not in a valid state.
Action: Check the INCOMPLETE field in the user_types catalog view to make sure that the ADT is in a valid state. Drop the invalid ADT and recreate the corresponding attribute set.
ORA-38443: An attribute set should be assigned to the expression set for statistics collection.
Cause: An attempt was made to collect statistics for an expression set with no attribute set assigned to it.
Action: Assign an attribute set to the expression set before collecting the statistics.
ORA-38444: statistics do not exist for the expression set
Cause: An attempt was made to clear the statistics that do not exist.
Action: No action was required.
ORA-38445: TOP clause not allowed with no statistics
Cause: An attempt was made to use the TOP parameters clause with no statistics available for the expression set.
Action: Collect statistics for the expression set and try again.
ORA-38446: Error with embedded ADT "string" in the attribute set.
Cause: The embedded ADT has errors.
Action: Set serveroutput ON for additional information.
ORA-38447: Type required for the embedded ADT attribute "string" is missing
Cause: Object type required for the embedded ADT was missing.
Action: Set serveroutput ON for additional information.
ORA-38448: Indexing predicates with "string" operator is not supported.
Cause: An unsupported operator was used in the exf$indexoper array.
Action: Choose the operators from this list : =, <, >, <=, >=, !=, is null, is not null, nvl, and between.
ORA-38449: table "string" does not exist or is not accessible
Cause: An attempt was made to create a table alias for a table that does not exist or is not accessible.
Action: Grant select privileges on the table to the current user.
ORA-38450: error computing a stored attribute for the expression set.
Cause: Either values for one of the attributes was incorrect or a stored attribute was invalid due to broken dependencies.
Action: Correct the input.
ORA-38451: index is in an inconsistent state
Cause: One or more secondary objects used to maintain the index did not exist
Action: Drop the index and recreate it.
ORA-38452: Expression Filter index name may not be longer than 25 characters
Cause: An attempt was made to use a name longer than 25 characters for the Expression Filter index.
Action: Choose a name that has 25 or fewer characters
ORA-38453: ExpFilter index should be created in the same schema as the base table.
Cause: An attempt was made to create the Expression Filter index in a schema other than that of the base table.
Action: Create the index in the same schema as the base table.
ORA-38454: attribute set not defined for the column being indexed
Cause: An attempt was made to create an Expression Filter index on a column with no attribute set association.
Action: Assign an attribute set to the expression set column begin indexed.
ORA-38455: Expression Filter index should be created by the owner.
Cause: An attempt was made to create the Expression Filter index by a user who is not the owner of the index.
Action: Create the index using owner"s privileges.
ORA-38456: The attribute set "string" is in an inconsistent state.
Cause: The attribute set was in an inconsistent state due to broken dependencies.
Action: Set serveroutput ON for more details. The attribute set may not be reused after this error.
ORA-38457: The attribute "string" is not a valid XMLType attribute.
Cause: An attempt was made to use a non-XMLType attribute to configure XPath filtering.
Action: Use an attribute of sys.XMLType datatype to configure XPath filtering.
ORA-38458: invalid operation "string" for XPATH_FILTER_PARAMETERS
Cause: An attempt was made to use an invalid operation.
Action: Use one of the following operations : ADD, DROP.
ORA-38459: XML Tag "string" not found for the XMLType attribute "string"
Cause: An Attempt was made to use a non-existent XML Tag.
Action: Correct the name of the XML Tag or the XMLType attribute.
ORA-38460: filtering based on datatype "string" not supported for XML Tags
Cause: An attempt was made to configure XPath filtering with an XML Tag of unsupported datatype.
Action: Leave the XML Tag out of filter parameters. It will be processed as sparse predicate
ORA-38461: XML Tag "string" already exists for the XMLType attribute "string"
Cause: An attempt was made to create a duplicate XML Tag.
Action: Choose a different XML Tag.
ORA-38462: invalid attribute list
Cause: The input was missing an attribute list or had null values for the attribute names.
Action: Correct the input.
ORA-38463: invalid XML Tag list
Cause: The input was missing a tag list or had null values for the tag names.
Action: Correct the input.
ORA-38464: expression set is not empty.
Cause: An attempt was made to assign an attribute set to a non-empty expression set.
Action: Use FORCE = "TRUE" to validate all the existing expressions.
ORA-38465: failed to create the privilege checking trigger due to: string
Cause: Creation of the trigger failed due to the error listed in the message.
Action: Set serveroutput ON for more information.
ORA-38466: user does not have privileges to CREATE/MODIFY expressions
Cause: An attempt was made to INSERT or UPDATE a column storing expression without appropriate permissions.
Action: Appropriate privileges on the expression set should be granted by the owner of the expression set.
ORA-38467: user cannot GRANT/REVOKE privileges to/from himself
Cause: An attempt was made to GRANT or REVOKE privileges to or from the current user.
Action: The the to_user or from_user field should be different from the user performing the operation.
ORA-38468: column "string" is not identified as a column storing expressions.
Cause: An attempt was made to grant permission on a nonexistent expression set.
Action: Make sure that the table and the column exist and an attribute set is associated with the column.
ORA-38469: invalid privilege for an expression set: string
Cause: An attempt was made to use an invalid privilege.
Action: See documentation for a valid privilege.
ORA-38470: cannot revoke a privilege that was not granted.
Cause: An attempt was made to revoke a privilege that had not been granted.
Action: Check catalog views to see if the user has the privilege.
ORA-38471: ROWIDs for table aliases cannot be null
Cause: An attempt was made to pass a null value for the table alias attribute in the data item, which is not permitted.
Action: Pass a valid rowid value for the table alias.
ORA-38472: VARCHAR representation of the data item is too long.
Cause: The VARCHAR representation of data item was too long.
Action: Use the EVALUATE operator with AnyData argument instead.
ORA-38473: cannot drop a type used for Expression Filter attribute set
Cause: An attempt was made to drop an ADT that was used to maintain an attribute set for the Expression Filter.
Action: Query USER_EXPFIL_ATTRIBUTE_SETS view to see the dependency.
ORA-38474: attribute set may not have attributes of TABLE COLLECTION type.
Cause: An attempt was made to create an attribute with a TABLE COLLECTION type.
Action: Use VARRAYs instead of table collection, if possible.
ORA-38475: The attribute set and the associated ADT are out of sync.
Cause: The ADT was directly modified by CREATE or ALTER operations.
Action: Drop the attribute set and recreate it from scratch.
ORA-38476: abstract type used for an Attribute set may not be modified.
Cause: An attempt was made to alter a type (ADT) that is used to maintain an attribute set of an Expression set.
Action: Do not modify the ADT directly. Use DBMS_EXPFIL APIs instead.
ORA-38477: attribute set cannot be derived from an evolved type or a subtype.
Cause: An attempt was made to create an attribute set from an evolved ADT or a subtype.
Action: The ADT used for the attribute set cannot be an evolved type or a subtype.
ORA-38478: creation of system trigger EXPFIL_DROPOBJ_MAINT failed
Cause: The creation of the system trigger EXPFIL_DROPOBJ_MAINT failed due to missing Expression Filter dictionary tables.
Action: Try a clean installation again. If this error is ignored, the Expression Filter dictionary could have some stale entries.
ORA-38479: creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed
Cause: The creation of system trigger EXPFIL_RESTRICT_TYPEEVOLVE failed due to missing Expression Filter dictionary tables.
Action: Try a clean installation again. If this error is ignored, the user will be able to evolve ADTs associated with the attribute set, thus causing spurious errors.
ORA-38480: creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed.
Cause: The creation of system trigger EXPFIL_ALTEREXPTAB_MAINT failed due to errors in SYS.EXF$DBMS_EXPFIL_SYSPACK package.
Action: Try a clean installation again. If this error is ignored, a RENAME of the expression table may cause the EVALUATE queries to fail.
ORA-38481: ADT "string" is used for a dependent object.
Cause: An attempt was made to create an attribute set from an ADT which is used by one or more dependent objects.
Action: Use a new ADT instead.
ORA-38482: no elementary attributes defined in the attribute set
Cause: An attempt was made to use an empty attribute set.
Action: Create one or more elementary attributes for the attribute set.
Cause: An attempt was made to use an invalid name format.
Action: The function/package/type name should be specified in the following format [owner.]object_name
ORA-38484: FUNCTION/PACKAGE/TYPE string does not exist
Cause: Attempt was made to use a object that does not exist.
Action: Query ALL_OBJECT view to ensure that the object exists.
ORA-38485: invalid object type for the user-defined function
Cause: An attempt was made to use an invalid object as a function.
Action: Valid object types are FUNCTION / PACKAGE / TYPE
ORA-38486: FUNCTION/PACKAGE/TYPE already exists for the attribute set
Cause: An attempt was made to add a duplicate function to the list.
Action: Use a different object name.
ORA-38487: FUNCTION/PACKAGE/TYPE "string" not allowed in the expression
Cause: An attempt was made to use an un-approved function in the expression.
Action: Add the function to the corresponding attribute set
ORA-38488: attribute set already assigned to the column storing expressions
Cause: An attempt was made to reassign an attribute set to an expression column.
Action: Query USER_EXPFIL_EXPRESSION_SETS view to find the attribute set assigned the expression set
ORA-38489: predicate table creation failed due to: ORAstring
Cause: Predicate table creation failed due to the reported error.
Action: Set serveroutput ON for additional information
ORA-38490: invalid name: quotes do not match
Cause: The quotes in the name did not match.
Action: Correct the name to match the quotes.
ORA-38491: could not evaluate subexpression for rowid "string"
Cause: Either the expression was not in a valid SQL-WHERE clause format or it had references to nonexistent schema objects.
Action: Correct the expression.
ORA-38492: invalid ALTER INDEX parameters clause "string"
Cause: An invalid parameters clause was specified with the ALTER INDEX command.
Action: See documentation for a valid list of parameters.
ORA-38493: feature not enabled : Expression Filter index
Cause: An attempt was made to create an Expression Filter index in Standard Edition.
Action: Do not attempt to use this feature.
ORA-38494: column in the table alias and an attribute have matching names
Cause: One of the attributes in the set has the same name as the name of one of the columns in the table configured for table alias.
Action: If possible, use a different name for the attribute.
ORA-38495: data type for the stored attribute string is inconsistent.
Cause: The actual data type for the stored attribute configured for the Expression Filter index object did not match the data type recorded in the Expression Filter dictionary.
Action: Delete the attribute from the default index attributes and recreate it.
ORA-38496: Expression Filter index is not in a valid state
Cause: An attempt was made to REBUILD an Expression Filter index that was not valid.
Action: Use DEFAULT keyword in the parameters clause to rebuild the index from defaults or drop and recreate the index.
ORA-38497: Expression Filter index does not exist
Cause: Index with a matching name does not exist or the index was not created using ExpFilter indextype.
Action: Identify the correct index using the Expression Filter catalog views
ORA-38498: invalid stored attribute for the index object : string
Cause: The expression filter index object has a stored or indexed attribute that had broken dependencies.
Action: Make sure that all the identifiers used in the attribute are valid.
ORA-38499: expression set already configured for stored/indexed attributes
Cause: The expression set already had a list of stored and indexed attributes. Additional attributes cannot be specified in the CREATE INDEX parameters clause.
Action: Remove TOP, STOREATTRS and INDEXATTRS clauses from the parameters clause or clear the expression set statistics using DBMS_EXPFIL.INDEX_PARAMETERS API.
ORA-38500: %s
Cause: There was a generic error
Action: See documentation for further information.
ORA-38501: sub-query not allowed in the expression
Cause: An attempt was made to use a sub-query in the expression.
Action: Do not use sub-queries in the expressions.
ORA-38502: invalid XML tag: string
Cause: An attempt was made to use an invalid XML tag for the index.
Action: Correct the XML tag and retry.
ORA-38503: index already defined using the parameters
Cause: An attempt was made to modify the index parameters after the index creation.
Action: Drop the index and retry.
ORA-38504: this operator not allowed with the configured attribute set
Cause: An attempt was made to use the operator binding with an attribute set containing more than one (table alias) attribute. This is not permitted.
Action: Use a different operator binding.
ORA-38505: invalid default value for the attribute
Cause: An attempt was made to use an invalid default value or a default that is larger than 100 characters.
Action: Specify a correct default value.
ORA-38601: FI Not enough memory for frequent itemset counting: string
Cause: The memory size did not satisfy the minimum memory requirement.
Action: In workarea_size_policy="manual" mode, set _fic_area_size to a reasonably larger value. Or, In workarea_size_policy="auto" mode, this error should never happen.
ORA-38602: FI invalid input cursor
Cause: The input cursor did not return exactly two columns for transactional input format or the input cursor didn"t have consistent data types for horizontal input format
Action: For transactional input format, specify that the input cursor returns exactly two columns: one for transaction-id, one for item-id. For horizontal input format, make sure the input cursor"s columns have the same data types.
ORA-38603: FI including & excluding cursor can only return one column
Cause: The including & excluding cursor did not return exactly one column.
Action: Specify that the cursor return only one column: item-id.
ORA-38604: FI including & excluding cursor item-id type must match input cursor item-id type
Cause: The including & excluding cursor item-id type did not match input cursor item-id type
Action: Specify that the item-id type of the cursors match each other.
ORA-38605: FI not enough memory(stringK) for candidate generation(stringK)
Cause: There was insufficient available memory for candidate generation.
Action: In workarea_size_policy="manual" mode, set _fic_area_size to a reasonably larger value. Or, in workarea_size_policy="auto" mode, set pga_aggregate_target to a reasonably larger value.
ORA-38606: FI support threshold not between [0, 1]
Cause: The user inputed a support threshold not in the range of [0, 1].
Action: The user should adjust the input value in the range of [0, 1].
ORA-38607: FI minimum and maximum itemset length not between [1, string]
Cause: The inputed minimum or maximum itemset length exceed the internal maximum itemset length or less than 1.
Action: The user should adjust the input value not larger than the internal maximum itemset length and not less than 1.
ORA-38608: FI itemset minimum-length(string) should not be greater than maximum length(string)
Cause: The user inputed minimum length is more than maximum length.
Action: The user should adjust the input values to make the minimum length less than or equal to the maximum length.
ORA-38609: FI Not enough memory for tree counting, requires at least stringKB
Cause: The memory size did not satisfy the minimum memory requirement for tree counting.
Action: In workarea_size_policy="manual" mode, set _fic_area_size to a reasonably larger value. Or, In workarea_size_policy="auto" mode, this error should never happen.
ORA-38610: FI "string" name prefix is reserved for frequent itemset counting
Cause: An error occurred because DBMS_FREQUENT_ITEMSET and prefix ORA_FI are reserved for the DBMS_FREQUENT_ITEMSET package"s internal use.
Action: Do not re-define functions with names starting with DBMS_FREQUENT_ITEMSET package or ORA_FI.
ORA-38611: FI input cursor"s item type is not supported
Cause: The input cursor"s item type is not number or character type
Action: Redefine the input cursor so that item type is number or character type.
ORA-38612: FI item length cannot exceed half of one database block.
Cause: The item"s length was more than half of one database block.
Action: Redefine the data type of the item column so that its maximum length is less than half of one database block.
ORA-38620: DT expressions in input cursor do not have an alias name
Cause: Expressions in input cursor do not have an alias name.
Action: Add an alias name for the expression.
ORA-38621: Decision Tree maximum depth setting not between [2, 20]
Cause: The user specified a max tree depth not in the range of [2, 20].
Action: The user should adjust the input value to be in the range of [2, 20].
ORA-38622: Decision Tree not enough memory, requires at least stringKB
Cause: The memory size did not satisfy the minimum memory requirement for decision tree building.
Action: In workarea_size_policy="manual" mode, set _dtree_area_size to a reasonably larger value. Or, In workarea_size_policy="auto" mode, please raise pga_aggregate_target to a reasonably larger value.
ORA-38700: Limit of string flashback database logs has been exceeded.
Cause: The maximum number of flashback database log files was exceeded.
Action: DB_FLASHBACK_RETENTION_TARGET may be set to high. Modify it to a smaller value.
Cause: Could not write to the flashback database log file.
Action: Restore access to the file.
ORA-38703: Type string in header is not a flashback database log file.
Cause: A corrupt flashback database log file header was read.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38704: Checksum error in flashback database log file header.
Cause: The flashback database log file header contained a checksum that does not match the value calculated from the file header as read from disk. This means the file header was corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38705: Expected block size string does not match string in log header.
Cause: When the flashback log file header was read, the block size in the control file did not match the block size contained in the header.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38706: Cannot turn on FLASHBACK DATABASE logging.
Cause: An ALTER DATABASE FLASHBACK ON command failed. Other messages in the alert log describe the problem.
Action: Fix the problem and retry.
ORA-38707: Media recovery is not enabled.
Cause: An ALTER DATABASE FLASHBACK ON command failed because media recovery was not enabled.
Action: Turn on media recovery with an ALTER DATABASE ARCHIVELOG command and then retry the command.
ORA-38708: not enough space for first flashback database log file
Cause: An ALTER DATABASE FLASHBACK ON command failed because there was not enough space in the Recovery Area for the first flashback database log file.
Action: Make more space in the Recovery Area. For example, this can be done by increasing the value of DB_RECOVERY_FILE_DEST_SIZE.
ORA-38709: Recovery Area is not enabled.
Cause: An ALTER DATABASE FLASHBACK ON command failed because the Recovery Area was not enabled.
Action: Set DB_RECOVERY_FILE_DEST to a location and retry.
ORA-38710: Flashback log version string is incompatible with ORACLE version string.
Cause: The flashback database log file was rejected because it appeared to be written by an incompatible version of Oracle.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
Cause: A corrupt Flashback Database log file block header was read. More information was dumped to the trace file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38712: Corrupt flashback log record header: block string, offset string.
Cause: A corrupt flashback database log record header was read. Either the record type or length were incorrect. More information was dumped to the trace file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38713: Flashback Database logging is already turned on.
Cause: An ALTER DATABASE FLASHBACK ON command had no effect because flashback database logging was already on.
Action: No action required.
ORA-38714: Instance recovery required.
Cause: An ALTER DATABASE FLASHBACK ON command failed because the database either crashed or was shutdown with the ABORT option.
Action: Open the database and then enter the SHUTDOWN command with the NORMAL or IMMEDIATE option.
ORA-38715: Invalid log number specified in the DUMP FLASHBACK command.
Cause: An invalid log number was used when dumping a flashback database log file.
Action: Specify a valid flashback database log number.
ORA-38716: Must supply an integer for the TYPE option.
Cause: An invalid value was specified for TYPE in the DUMP FLASHBACK command.
Action: Specify an integer value.
ORA-38717: Invalid DUMP FLASHBACK option.
Cause: An invalid option was specified in the DUMP FLASHBACK command. Currently the only options allowed are: DBA, TYPE, and LOGICAL.
Action: Retry the command with the correct options.
ORA-38718: Invalid thread number specified in the DUMP FLASHBACK command.
Cause: An invalid thread number was used in dumping the flashback database log files for a thread.
Action: Specify a valid thread number.
ORA-38719: Invalid DUMP FLASHBACK object.
Cause: An invalid object was specified in a DUMP FLASHBACK command. Currently the only objects allowed are: LOGFILE or THREAD.
Action: Retry the command with the correct options.
ORA-38720: Missing log file number.
Cause: A log file number was missing in a DUMP FLASHBACK LOGFILE command.
Action: Supply a valid log file number.
ORA-38721: Invalid file number.
Cause: An invalid file number was specified in the DBA clause of a DUMP FLASHBACK command.
Action: Supply a valid file number.
ORA-38722: ON or OFF expected.
Cause: The ALTER DATABASE FLASHBACK command was specified without the ON or OFF keyword.
Action: Retry the command with the ON or OFF keyword.
ORA-38723: Invalid SCN expression.
Cause: The SCN keyword was specified in a FLASHBACK DATABASE command but the SCN expression was invalid.
Action: Retry the command using a valid SCN number.
ORA-38724: Invalid option to the FLASHBACK DATABASE command.
Cause: An invalid option was specified to the FLASHBACK DATABASE command. Valid options are: SCN or TIMESTAMP.
Action: Correct the syntax and retry the command.
ORA-38725: specified name "string" does not match actual "string"
Cause: The database name specified in a FLASHBACK DATABASE command did not match the name of the currently mounted database.
Action: Correct the database name spelling or DISMOUNT the mounted database and mount the correct database.
ORA-38726: Flashback database logging is not on.
Cause: A FLASHBACK DATABASE command was tried but flashback database logging has not been enabled.
Action: Flashback database logging must be enabled via the ALTER DATABASE FLASHBACK ON command before a FLASHBACK DATABASE command can be tried. If the database must be taken back in time then a restore and incomplete recovery must be performed.
ORA-38727: FLASHBACK DATABASE requires a current control file.
Cause: The control file being used is a backup control file.
Action: FLASHBACK DATABASE cannot be used with a backup control file. If the database must be taken back in time then a restore and an incomplete recovery must be performed.
ORA-38728: Cannot FLASHBACK DATABASE to the future.
Cause: An SCN or time stamp provided in a FLASHBACK DATABASE command was in the future.
Action: Supply a proper SCN or time stamp and retry the command.
ORA-38729: Not enough flashback database log data to do FLASHBACK.
Cause: There was not enough flashback database log data to do the FLASHBACK DATABASE.
Action: If the database must be taken back in time then a restore and incomplete recovery must be performed.
ORA-38730: Invalid SCN/TIMESTAMP expression.
Cause: The expression supplied in a FLASHBACK DATABASE command was invalid.
Action: Retry the command using a valid number or time stamp expression.
ORA-38731: Expected version string does not match string in log header.
Cause: The version of the flashback database log file header was corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38732: Expected file size string does not match string.
Cause: The file size indicated in the control file did not match the file size contained in the flashback log file header. The flashback database log file was corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38733: Physical size string less than needed string.
Cause: A flashback database log file shrank in size. This was likely to have been caused by operator or operating system error.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38734: Flashback log is inconsistent; belongs to another database.
Cause: The database ID in the flashback database log file did not match the database ID in the control file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38735: Wrong log number string in flashback log file header.
Cause: The log file number in the flashback database log file did not match the control file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38736: Wrong thread number string in flashback log file header.
Cause: The thread number in the flashback database log file did not match the control file.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38737: Expected sequence number string doesn"t match string
Cause: The flashback database log is corrupted or is an old version.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38738: Flashback log file is not current copy.
Cause: A check of flashback database log file header at database open found that the flashback database log appeared to be an incorrectly restored backup. Flashback database log files cannot be backed up and restored.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38739: Flashback log file is more recent than control file.
Cause: The control file change sequence number in the flashback database log file was greater than the number in the control file. This implies that the wrong control file was being used. Note that repeatedly causing this error can make it stop happening without correcting the real problem. Every attempt to open the database will advance the control file change sequence number until it is great enough.
Action: FLASHBACK DATABASE can only be used with the current control file. If it is not available, then a restore and an incomplete recovery must be performed instead.
ORA-38740: Usable blocks value string is not valid.
Cause: A flashback database log file header contained a usable blocks value greater than the file size. The flashback database log file file is corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38741: Formatted blocks value string is not valid.
Cause: The formatted blocks value in the flashback database log file was greater than the file size. The flashback database log file was corrupt.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38742: Flashback log file has incorrect log reset status.
Cause: The flashback database log file header had log reset data that was different than the control file. The log was probably an incorrectly restored backup. Flashback database logs cannot be backed up.
Action: If you are doing a FLASHBACK DATABASE, then the flashback cannot be performed because of the corrupted log. A restore and an incomplete recovery must be performed instead.
ORA-38743: Time/SCN is in the future of the database.
Cause: The Time/SCN provided in a FLASHBACK DATABASE command was in the future of the database.
Action: Retry the command with a correct Time/SCN or RECOVER the database.
ORA-38744: file string is not the same file seen at start of flashback
Cause: A different copy of the file was accessed the last time FLASHBACK DATABASE looked at the file header. A backup of the file was restored or the meaning of the file name changed during FLASHBACK DATABASE.
Action: Ensure the correct file is available, then retry FLASHBACK DATABASE.
ORA-38746: error occurred while restoring data block (file# string, block# string)
Cause: An error occurred during a FLASHBACK DATABASE command. See other errors on error stack.
Action: Investigate why the error occurred. It may be that the flashback database log data is corrupt. If so, a restore and an incomplete recovery must be performed instead.
ORA-38747: corrupt before image (file# string, block# string)
Cause: A corrupt data block before image was encountered during a FLASHBACK DATABASE command.
Action: The flashback log data is probably corrupt. If so, a restore and an incomplete recovery must be performed instead.
ORA-38748: cannot flashback data file string - file is in use or recovery
Cause: An attempt to do FLASHBACK DATABASE found that the file was not available for recovery. Either it was online and the database was open in some instance, or another process was currently doing media recovery or flashback on the file.
Action: Do not do FLASHBACK DATABASE.
ORA-38749: A media recovery has been started.
Cause: An attempt was made to start a FLASHBACK DATABASE in the same session as a media recovery.
Action: Complete or cancel the first media recovery session.
ORA-38750: FLASHBACK DATABASE may not be performed using a dispatcher.
Cause: An attempt was made to use a dispatcher process for FLASHBACK DATABASE. Memory requirements disallow this recovery method.
Action: Connect to the instance via a dedicated server process to perform FLASHBACK DATABASE.
ORA-38752: file string does not exist
Cause: During an RMAN FLASHBACK DATABASE conversation, a file was listed which was not part of the database. The RMAN conversation was aborted.
Action: Retry the conversation with the appropriate file numbers.
ORA-38753: Cannot flashback data file string; no flashback log data.
Cause: An attempt to perform a FLASHBACK DATABASE failed because the file does not have enough flashback log data to cover the time to flash back. Either the file did not have flashback generation enabled for it, or had flashback generation turned off for it some time during the time span of the flashba
