SQL*Loader-00408: Physical record stack overflow
Cause: An internal error has occurred.
Action: Contact customer support.
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-00407: If data is all generated, number to skip is meaningless
SQL*Loader-00407: If data is all generated, number to skip is meaningless
Cause: When all data is generated, no file is read, and there are no records to skip.
Action: Remove the number to skip.
Cause: When all data is generated, no file is read, and there are no records to skip.
Action: Remove the number to skip.
SQL*Loader-00405: Need termination delim with optional enclosure delim: column string table string
SQL*Loader-00405: Need termination delim with optional enclosure delim: column string table string
Cause: The named column was specified with an optional enclosure delimiter, but no termination delimiter. Enclosure delimiters can only be optional when termination delimiters are present.
Action: Specify a termination delimiter or make the enclosure delimiters
Cause: The named column was specified with an optional enclosure delimiter, but no termination delimiter. Enclosure delimiters can only be optional when termination delimiters are present.
Action: Specify a termination delimiter or make the enclosure delimiters
SQL*Loader-00404: Column string present more than once in string s INTO TABLE block.
SQL*Loader-00404: Column string present more than once in string s INTO TABLE block.
Cause: The named column is specified more than once in a single INTO TABLE statement.
Action: Remove the extraneous column specification.
Cause: The named column is specified more than once in a single INTO TABLE statement.
Action: Remove the extraneous column specification.
SQL*Loader-00403: Referenced column string not present in table string.
SQL*Loader-00403: Referenced column string not present in table string.
Cause: The named column is not present in the given table.
Action: Correct the column name or table name.
Cause: The named column is not present in the given table.
Action: Correct the column name or table name.
SQL*Loader-00402: Unable to determine length of column string from specification
SQL*Loader-00402: Unable to determine length of column string from specification
Cause: The specified datatype does not have an implied length (for example, a numeric external or RAW datatype), it is not specified with delimiters, no length was specified, and a length cannot be determined from a POSITION clause.
Action: If a POSITION clause is specified, adding an end location to it produces a length specification. This clause then has the form POSITION(start:end) A length can also specified after the datatype, as in INTEGER EXTERNAL (6) Finally, the field could be specified with delimiters, or the datatype changed to one that has an implied length.
Cause: The specified datatype does not have an implied length (for example, a numeric external or RAW datatype), it is not specified with delimiters, no length was specified, and a length cannot be determined from a POSITION clause.
Action: If a POSITION clause is specified, adding an end location to it produces a length specification. This clause then has the form POSITION(start:end) A length can also specified after the datatype, as in INTEGER EXTERNAL (6) Finally, the field could be specified with delimiters, or the datatype changed to one that has an implied length.
SQL*Loader-00250: Work data sets are not used by SQL*Loader
SQL*Loader-00250: Work data sets are not used by SQL*Loader
Cause: The SQL*Loader control file contains a WRKDDN statement. SQL*Loader ignores this clause.
Action: No action required. This is an informational message.
Cause: The SQL*Loader control file contains a WRKDDN statement. SQL*Loader ignores this clause.
Action: No action required. This is an informational message.
SQL*Loader-00200: FORMAT clause should not be present - flat data files only
SQL*Loader-00200: FORMAT clause should not be present - flat data files only
Cause: SQL or DS FORMAT clause is not supported.
Action: Remove the FORMAT command from the SQL*Loader control file or
Cause: SQL or DS FORMAT clause is not supported.
Action: Remove the FORMAT command from the SQL*Loader control file or
SQL*Loader-00138: Invalid value for DATE_CACHE
SQL*Loader-00138: Invalid value for DATE_CACHE
Cause: The command line argument specified for DATE_CACHE was not a valid positive integer.
Action: Check the command line and retry.
Cause: The command line argument specified for DATE_CACHE was not a valid positive integer.
Action: Check the command line and retry.
SQL*Loader-00137: Invalid value for RESUMABLE_TIMEOUT
SQL*Loader-00137: Invalid value for RESUMABLE_TIMEOUT
Cause: The command line argument specified for RESUMABLE_TIMEOUT was not a valid positive integer.
Action: Check the command line and retry.
Cause: The command line argument specified for RESUMABLE_TIMEOUT was not a valid positive integer.
Action: Check the command line and retry.
SQL*Loader-00136: Invalid argument for RESUMABLE_NAME
SQL*Loader-00136: Invalid argument for RESUMABLE_NAME
Cause: The command line argument specified for RESUMABLE_NAME was not a valid string.
Action: Check the command line and retry.
Cause: The command line argument specified for RESUMABLE_NAME was not a valid string.
Action: Check the command line and retry.
SQL*Loader-00135: Invalid argument for RESUMABLE
SQL*Loader-00135: Invalid argument for RESUMABLE
Cause: The command line argument specified for RESUMABLE was not TRUE or FALSE.
Action: Check the command line and retry.
Cause: The command line argument specified for RESUMABLE was not TRUE or FALSE.
Action: Check the command line and retry.
SQL*Loader-00134: invalid option specified for EXTERNAL_TABLE parameter
SQL*Loader-00134: invalid option specified for EXTERNAL_TABLE parameter
Cause: An invalid value was specified for the EXTERNAL_TABLE parameter.
Action: Specify one of the following values. NOT_USED disables use of external tables. GENERATE_ONLY generates the SQL statements that will use external tables to load the data. EXECUTE both generates the SQL statements and then executes them.
Cause: An invalid value was specified for the EXTERNAL_TABLE parameter.
Action: Specify one of the following values. NOT_USED disables use of external tables. GENERATE_ONLY generates the SQL statements that will use external tables to load the data. EXECUTE both generates the SQL statements and then executes them.
SQL*Loader-00133: Can t specify both direct path and external tables
SQL*Loader-00133: Can t specify both direct path and external tables
Cause: Both options for direct path and exrernal tables were indicated. Only one of these can be applied at a time.
Action: Change at least one of the parameters to enable only one.
Cause: Both options for direct path and exrernal tables were indicated. Only one of these can be applied at a time.
Action: Change at least one of the parameters to enable only one.
SQL*Loader-00132: invalid argument for external table option
SQL*Loader-00132: invalid argument for external table option
Cause: The command line argument specified for external_tables was not TRUE or FALSE
Action: Check the command line and retry.
Cause: The command line argument specified for external_tables was not TRUE or FALSE
Action: Check the command line and retry.
SQL*Loader-00131: Invalid multithreading option
SQL*Loader-00131: Invalid multithreading option
Cause: The only valid options for the MULTITHREADING command-line argument are TRUE or FALSE. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the command line and retry.
Cause: The only valid options for the MULTITHREADING command-line argument are TRUE or FALSE. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the command line and retry.
SQL*Loader-00130: Invalid direct path stream size
SQL*Loader-00130: Invalid direct path stream size
Cause: The argument s value is inappropriate
Action: Check the command line and retry.
Cause: The argument s value is inappropriate
Action: Check the command line and retry.
SQL*Loader-00129: Invalid number of rows for direct path column array
SQL*Loader-00129: Invalid number of rows for direct path column array
Cause: The argument s value is inappropriate
Action: Check the command line and retry.
Cause: The argument s value is inappropriate
Action: Check the command line and retry.
SQL*Loader-00128: unable to begin a session
SQL*Loader-00128: unable to begin a session
Cause: An error occurred when attempting to start a session on the database.
Action: See the message that follows this message for information on the cause of the error.
Cause: An error occurred when attempting to start a session on the database.
Action: See the message that follows this message for information on the cause of the error.
SQL*Loader-00127: Invalid maximum record size
SQL*Loader-00127: Invalid maximum record size
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00126: Invalid read size
SQL*Loader-00126: Invalid read size
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00125: specified value for readsize(number) less than max_record_ size(number)
SQL*Loader-00125: specified value for readsize(number) less than max_record_ size(number)
Cause: The command line argument specified for readsize was less than the value of max_record_size.
Action: No action is required. SQL*Loader automatically adjusts the value of readsize to equal the value of max_record_size.
Cause: The command line argument specified for readsize was less than the value of max_record_size.
Action: No action is required. SQL*Loader automatically adjusts the value of readsize to equal the value of max_record_size.
SQL*Loader-00124: specified value for readsize(number) less than bindsize(number)
SQL*Loader-00124: specified value for readsize(number) less than bindsize(number)
Cause: The command line argument specified for readsize was less than the value of bindsize.
Action: No action is required. SQL*Loader automatically adjusts the value of readsize to equal the value of bindsize.
Cause: The command line argument specified for readsize was less than the value of bindsize.
Action: No action is required. SQL*Loader automatically adjusts the value of readsize to equal the value of bindsize.
SQL*Loader-00123: specified value for bindsize(number) less than readsize(number)
SQL*Loader-00123: specified value for bindsize(number) less than readsize(number)
Cause: The command line argument specified for bindsize was less than the value of readsize.
Action: No action is required. SQL*Loader automatically adjusts the value of bindsize to equal the value of readsize.
Cause: The command line argument specified for bindsize was less than the value of readsize.
Action: No action is required. SQL*Loader automatically adjusts the value of bindsize to equal the value of readsize.
SQL*Loader-00122: Invalid skip_index_maintenance option
SQL*Loader-00122: Invalid skip_index_maintenance option
Cause: The command line argument for skip_index_maintenance is incorrect.
Action: Use only true or falseas the value for the skip_index_maintenance option. (Note: only on direct loads )
Cause: The command line argument for skip_index_maintenance is incorrect.
Action: Use only true or falseas the value for the skip_index_maintenance option. (Note: only on direct loads )
SQL*Loader-00121: Invalid skip_unusable_indexes option
SQL*Loader-00121: Invalid skip_unusable_indexes option
Cause: The command line argument for skip_unusable_indexes is incorrect.
Action: Use only TRUE or FALSE as the value for the skip_unusable_indexes option.
Cause: The command line argument for skip_unusable_indexes is incorrect.
Action: Use only TRUE or FALSE as the value for the skip_unusable_indexes option.
SQL*Loader-00120: Invalid _synchro option string
SQL*Loader-00120: Invalid _synchro option string
Cause: The command-line argument _synchro is incorrect.
Action: Use only one of the allowed modes: see ulminv((.
Cause: The command-line argument _synchro is incorrect.
Action: Use only one of the allowed modes: see ulminv((.
SQL*Loader-00119: Invalid parallel file (data file) name on command line
SQL*Loader-00119: Invalid parallel file (data file) name on command line
Cause: The command-line argument for the parallel file was entered incorrectly.
Action: Check the command line argument and retry the operation.
Cause: The command-line argument for the parallel file was entered incorrectly.
Action: Check the command line argument and retry the operation.
SQL*Loader-00118: Invalid parallel load option
SQL*Loader-00118: Invalid parallel load option
Cause: The command-line argument used for the parallel load is incorrect.
Action: Use only TRUE or FALSE as the value for the parallel load option.
Cause: The command-line argument used for the parallel load is incorrect.
Action: Use only TRUE or FALSE as the value for the parallel load option.
SQL*Loader-00116: Error prompting for password
SQL*Loader-00116: Error prompting for password
Cause: An internal error has occurred.
Action: Contact customer support.
Cause: An internal error has occurred.
Action: Contact customer support.
SQL*Loader-00115: Invalid direct path option
SQL*Loader-00115: Invalid direct path option
Cause: The only valid options for the DIRECT command-line argument are TRUE or FALSE. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the command line and retry.
Cause: The only valid options for the DIRECT command-line argument are TRUE or FALSE. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the command line and retry.
SQL*Loader-00114: Error in OPTIONS statement
SQL*Loader-00114: Error in OPTIONS statement
Cause: Command line options specified in the SQL*Loader control file with the OPTIONS clause were found to be incorrect.
Action: Check the format of the OPTIONS clause in the SQL*Loader control file.
Cause: Command line options specified in the SQL*Loader control file with the OPTIONS clause were found to be incorrect.
Action: Check the format of the OPTIONS clause in the SQL*Loader control file.
SQL*Loader-00113: Invalid silent mode option
SQL*Loader-00113: Invalid silent mode option
Cause: The only valid options for the SILENT command-line argument are ALL, ERROR, FEEDBACK, or HEADER. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the command line and retry.
Cause: The only valid options for the SILENT command-line argument are ALL, ERROR, FEEDBACK, or HEADER. The argument could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the command line and retry.
SQL*Loader-00112: Invalid maximum bind array size
SQL*Loader-00112: Invalid maximum bind array size
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00111: Invalid number of rows for bind array or data saves
SQL*Loader-00111: Invalid number of rows for bind array or data saves
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00110: Invalid maximum number of errors
SQL*Loader-00110: Invalid maximum number of errors
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00109: Invalid number of logical records to skip
SQL*Loader-00109: Invalid number of logical records to skip
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00108: Invalid number of logical records to load
SQL*Loader-00108: Invalid number of logical records to load
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00107: Invalid maximum number of discards
SQL*Loader-00107: Invalid maximum number of discards
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
Cause: The argument s value is inappropriate, or another argument (not identified by a keyword) is in its place.
Action: Check the command line and retry.
SQL*Loader-00106: Invalid discard file name on command line
SQL*Loader-00106: Invalid discard file name on command line
Cause: The discard file name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the spelling and position of the arguments on the command line.
Cause: The discard file name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the spelling and position of the arguments on the command line.
SQL*Loader-00105: Invalid data file name on command line
SQL*Loader-00105: Invalid data file name on command line
Cause: The datafile name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the spelling and position of the arguments on the command line.
Cause: The datafile name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the spelling and position of the arguments on the command line.
SQL*Loader-00104: Invalid bad file name on command line
SQL*Loader-00104: Invalid bad file name on command line
Cause: The bad file name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Correct it.
Cause: The bad file name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Correct it.
SQL*Loader-00103: Invalid log file name on command line
SQL*Loader-00103: Invalid log file name on command line
Cause: The log file name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the spelling and position of the arguments on the command line.
Cause: The log file name specified on the command line was not recognized. It could be misspelled, or another argument (not identified by a keyword) could be in its place.
Action: Check the spelling and position of the arguments on the command line.
SQL*Loader-00102: Invalid control file name on command line
SQL*Loader-00102: Invalid control file name on command line
Cause: is the existence of a space between username and password. See error 101, above.
Action: Check the spelling and position of the arguments on the command line.
Cause: is the existence of a space between username and password. See error 101, above.
Action: Check the spelling and position of the arguments on the command line.
SQL*Loader-00101: Invalid argument for username or password
SQL*Loader-00101: Invalid argument for username or password
Cause: The username or password argument specified on the command line was not recognized. Another argument (not identified by a keyword) could be in the position where username or password is expected.
Action: Check the format of the username or password argument, which is the first argument on the command line, if arguments are given without keywords.
Cause: The username or password argument specified on the command line was not recognized. Another argument (not identified by a keyword) could be in the position where username or password is expected.
Action: Check the format of the username or password argument, which is the first argument on the command line, if arguments are given without keywords.
SQL*Loader-00100: Syntax error on command-line
SQL*Loader-00100: Syntax error on command-line
Cause: Possible causes for this error include: placing a positional argument after keyword arguments, misspelling a keyword, not balancing parentheses or quotes, or leaving space between the operator, = , and an argument.
Action: Check the command syntax and the spelling, then retry.
Cause: Possible causes for this error include: placing a positional argument after keyword arguments, misspelling a keyword, not balancing parentheses or quotes, or leaving space between the operator, = , and an argument.
Action: Check the command syntax and the spelling, then retry.
IMP-00401: dump file string may be an Data Pump export dump file
IMP-00401: dump file string may be an Data Pump export dump file
Cause: A dump file was specified for an import operation which appears to have been created using the Data Pump export utility. These dump files cannot be processed by the original import utility.
Action: Try using the Data Pump import utility to process this dump file.
Cause: A dump file was specified for an import operation which appears to have been created using the Data Pump export utility. These dump files cannot be processed by the original import utility.
Action: Try using the Data Pump import utility to process this dump file.
IMP-00400: Warning: Object type string . string already exists with a different typeid
IMP-00400: Warning: Object type string . string already exists with a different typeid
Cause: An object type could not be created because it already existed on the * target system, but with a different typeid
Action: Drop the object type from the target system and retry the operation.
Cause: An object type could not be created because it already existed on the * target system, but with a different typeid
Action: Drop the object type from the target system and retry the operation.
IMP-00099: Warning: The typeid in the dump file for object type string . string is invalid
IMP-00099: Warning: The typeid in the dump file for object type string . string is invalid
Cause: The character string representing the object type s identifier * could not be converted.
Action: Contact Oracle Worldwide Support.
Cause: The character string representing the object type s identifier * could not be converted.
Action: Contact Oracle Worldwide Support.
IMP-00098: INTERNAL ERROR: string
IMP-00098: INTERNAL ERROR: string
Cause: An INTERNAL error occurred.
Action: Contact Oracle Worldwide Support.
Cause: An INTERNAL error occurred.
Action: Contact Oracle Worldwide Support.
IMP-00097: STREAMS_CONFIGURATION=Y ignored, only valid with FULL=Y
IMP-00097: STREAMS_CONFIGURATION=Y ignored, only valid with FULL=Y
Cause: STREAMS_CONFIGURATION=Y can only be used * when FULL=Y is present on the command line
Action: Remove conflicting command arguments
Cause: STREAMS_CONFIGURATION=Y can only be used * when FULL=Y is present on the command line
Action: Remove conflicting command arguments
IMP-00096: Warning: Skipping table string . string because type synonym string. string cannot be created
IMP-00096: Warning: Skipping table string . string because type synonym string. string cannot be created
Cause: An error occurred creating a synonym for a type that is used by the * table.
Action: Examine the import log to determine why the type synonym could * not be created. If the synonym already existed, but is not * needed, then drop the synonym and retry the import. If the * synonym is PUBLIC but the importer does not have the * CREATE PUBLIC SYNONYM system privilege, then the import must * be done by someone possessing that privilege, or the importer * must be granted the privilege.
Cause: An error occurred creating a synonym for a type that is used by the * table.
Action: Examine the import log to determine why the type synonym could * not be created. If the synonym already existed, but is not * needed, then drop the synonym and retry the import. If the * synonym is PUBLIC but the importer does not have the * CREATE PUBLIC SYNONYM system privilege, then the import must * be done by someone possessing that privilege, or the importer * must be granted the privilege.
IMP-00095: Resumable parameters ignored -- current session not resumable
IMP-00095: Resumable parameters ignored -- current session not resumable
Cause: Current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable session in order for the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
Cause: Current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable session in order for the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
IMP-00094: Warning: The identifier on the dump file for object type string . string is invalid
IMP-00094: Warning: The identifier on the dump file for object type string . string is invalid
Cause: The character string representing the object type s identifier * could not be converted.
Action: Contact Oracle Worldwide Support.
Cause: The character string representing the object type s identifier * could not be converted.
Action: Contact Oracle Worldwide Support.
IMP-00093: Inconsistency between dumpfile constraint definition for table string with columns (string)
IMP-00093: Inconsistency between dumpfile constraint definition for table string with columns (string)
Cause: Import failed to locate a base table for a constraint that was defined in the dump file and statistics were not imported.
Action: Check to see if the table and constraint exist. If the table and constraint exist, then report this to Oracle Support Services as an Import internal error.
Cause: Import failed to locate a base table for a constraint that was defined in the dump file and statistics were not imported.
Action: Check to see if the table and constraint exist. If the table and constraint exist, then report this to Oracle Support Services as an Import internal error.
IMP-00092: Java object string . string already exists, cannot be created
IMP-00092: Java object string . string already exists, cannot be created
Cause: Import failed to create the Java source, class or resource object because it already exists.
Action: Drop the object type from the target system and retry the operation.
Cause: Import failed to create the Java source, class or resource object because it already exists.
Action: Drop the object type from the target system and retry the operation.
IMP-00091: Above error occurred on the following function and object: string. Remaining PL or SQL blocks for this object will be skipped.
IMP-00091: Above error occurred on the following function and object: string. Remaining PL or SQL blocks for this object will be skipped.
Cause: An error occurred while executing a PL or SQL block that implements the DDL for the named function and procedural object. A procedural object is one whose DDL is implemented as stored procedures rather than as standard SQL statements.
Action: Contact Oracle Worldwide Support so they may determine the development group responsible for the package that failed.
Cause: An error occurred while executing a PL or SQL block that implements the DDL for the named function and procedural object. A procedural object is one whose DDL is implemented as stored procedures rather than as standard SQL statements.
Action: Contact Oracle Worldwide Support so they may determine the development group responsible for the package that failed.
IMP-00090: Unexpected DbmsJava error number at step number while creating string
IMP-00090: Unexpected DbmsJava error number at step number while creating string
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Import internal error to customer support.
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Import internal error to customer support.
IMP-00089: Fine grain policy string not recreated on table or view string
IMP-00089: Fine grain policy string not recreated on table or view string
Cause: Import user fails to recreate fine grained policies of the table or view being imported. To recreate the policy, the user doing the import needs execute privilege on the package DBMS_RLS for access policies or DBMS_FGA for audit policies.
Action: Ask the database administrator to perform the export or import of this table or view.
Cause: Import user fails to recreate fine grained policies of the table or view being imported. To recreate the policy, the user doing the import needs execute privilege on the package DBMS_RLS for access policies or DBMS_FGA for audit policies.
Action: Ask the database administrator to perform the export or import of this table or view.
IMP-00088: Problem importing metadata for index string. Index creation will be skipped
IMP-00088: Problem importing metadata for index string. Index creation will be skipped
Cause: Domain indexes import private metadata via anonymous PL or SQL blocks prior to the CREATE INDEX statement. The execution of one of these PL or SQL blocks failed. Because the metadata is considered an integral part of the index, the subsequent CREATE INDEX statement was skipped.
Action: Contact the developer of the index s implementation type. If this is an Oracle-supplied index (perhaps via a data cartridge), contact Oracle Worldwide Support.
Cause: Domain indexes import private metadata via anonymous PL or SQL blocks prior to the CREATE INDEX statement. The execution of one of these PL or SQL blocks failed. Because the metadata is considered an integral part of the index, the subsequent CREATE INDEX statement was skipped.
Action: Contact the developer of the index s implementation type. If this is an Oracle-supplied index (perhaps via a data cartridge), contact Oracle Worldwide Support.
Subscribe to:
Posts (Atom)