EXP-00095: Flashback_time and Flashback_scn are not compatible

EXP-00095: Flashback_time and Flashback_scn are not compatible

Cause: Both flashback_time and flashback_scn paramerers were specified.

Action: Reissue command with only one flashback parameter.

EXP-00094: Could not convert to server national character set s handle

EXP-00094: Could not convert to server national character set s handle

Cause: Internal error.

Action: Contact Worldwide support.

EXP-00093: Could not convert to server character set s handle

EXP-00093: Could not convert to server character set s handle

Cause: Internal error.

Action: Contact Worldwide support.

EXP-00092: Unable to set NLS_NUMERIC_CHARACTERS to required defaults.

EXP-00092: Unable to set NLS_NUMERIC_CHARACTERS to required defaults.

Cause: Export was unable to set NLS_NUMERIC_CHARACTERS to .,

Action: Record the accompanying messages and report this as an Export internal error to customer support.

EXP-00091: Exporting questionable statistics.

EXP-00091: Exporting questionable statistics.

Cause: Export was able export statistics, but the statistics may not be usuable. The statistics are questionable because one or more of the following happened during export: a row error occurred, client character set or NCHARSET does not match with the server, a query clause was specified on export, only certain partitions or subpartitions were exported, or a fatal error occurred while processing a table.

Action: To export non-questionable statistics, change the client character set or NCHARSET to match the server, export with no query clause, export complete tables. If desired, import parameters can be supplied so that only non-questionable statistics will be imported, and all questionable statistics will be recalculated.

EXP-00090: cannot pin type string . string

EXP-00090: cannot pin type string . string

Cause: Export was unable to pin the specified type in the object cache. This is typically caused because a type could not be made valid (for example because of authorization violations in accessing subtypes).

Action: Fix the problem with the offending type until the type can be successfully compiled.

EXP-00089: invalid FILE_FORMAT specification

EXP-00089: invalid FILE_FORMAT specification

Cause: The FILE_FORMAT specification did not contain an instance of %s . This wildcard string must be present.

Action: Correct the error and reenter the EXPORT command.

EXP-00087: Problem with internal hash table of schema or table names

EXP-00087: Problem with internal hash table of schema or table names

Cause: Most likely a problem with allocating memory for the hash table entries.

Action: Contact Oracle Worldwide Support NLS_DO_NOT_TRANSLATE (88,88(

EXP-00086: Primary key REFs in table string may not be valid on import

EXP-00086: Primary key REFs in table string may not be valid on import

Cause: The specified table contains primary key REFs which may not be valid in the import database.

Action: Do not use Export or Import to move Primary key REFs between databases having differing character sets.

EXP-00085: The previous problem occurred when calling string.string.string for object number

EXP-00085: The previous problem occurred when calling string.string.string for object number

Cause: The listed package provides export or import support for procedural objects, i.e, those whose DDL is supplied by stored procedures. The previously listed error occurred while calling the specified function.

Action: Contact Oracle Worldwide Support. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Support determine the correct owner of the problem.

EXP-00084: Unexpected DbmsJava error number at step number

EXP-00084: Unexpected DbmsJava error number at step number

Cause: The error was returned from a call to a DbmsJava procedure.

Action: Record the accompanying messages and report this as an Export internal error to customer support.

EXP-00083: The previous problem occurred when calling string.string.string

EXP-00083: The previous problem occurred when calling string.string.string

Cause: The listed package provides export or import support for procedural

Action: Contact Oracle Worldwide Support. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Support determine the correct owner of the problem.

EXP-00082: Invalid function name passed to procedural object support: string

EXP-00082: Invalid function name passed to procedural object support: string

Cause: Internal inconsistency error: The listed function is not a method on export s procedural object interface specification.

Action: Contact Oracle Worldwide Support

EXP-00081: Exporting access control for table or view string as non-DBA.

EXP-00081: Exporting access control for table or view string as non-DBA.

Cause: A non-DBA user tries to export table or view and the associated fine grain access control policies. The user may not have enough privilege to recreate the access control policies when importing the table or view. And such an event may cause inconsistency in the security model of the table or view.

Action: Ask the database administrator to export or import this table or view.

EXP-00080: Data in table string is protected. Using conventional mode.

EXP-00080: Data in table string is protected. Using conventional mode.

Cause: User without the execute privilege on DBMS_RLS, the access control package, tries to direct export a table that has access control enabled. Using conventional export mode instead. Note that because of access control, only a partial table may be exported.

Action: Ask the database administrator to export or import this table or view.

EXP-00079: Data in table string is protected. Conventional path may only be exporting partial table.

EXP-00079: Data in table string is protected. Conventional path may only be exporting partial table.

Cause: User without the execute privilege on DBMS_RLS, the access control package, tries to export a table that has access control. Since table owner is also subjected to access control, the owner may not be able to export all rows in the table, but only the ones he can see. Also, to preserve integrity of the table, user exporting the table should have enough privilege to recreate the table with the security policies at import time. Therefore, it is strongly recommended the database administrator should be handling exporting of this table. Granting the table owner execute privilege would also satisfy this security check, though it might have other security implications. If the table does not have objects, can use direct mode.

Action: Ask the database administrator to export or import this table or view.

EXP-00078: Error exporting metadata for index string. Index creation will be skipped

EXP-00078: Error exporting metadata for index string. Index creation will be skipped

Cause: Domain indexes export private metadata via anonymous PL or SQL blocks prior to the CREATE INDEX statement. Export does this by calling the ODCIIndexGetMetadata method on the implementation type associated with the index. A problem occurred inside this routine. Because the metadata is considered an integral part of the index, the CREATE INDEX statement was not written to the dump file.

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.

EXP-00077: multiple output files specified for unbounded export file

EXP-00077: multiple output files specified for unbounded export file

Cause: You specified multiple file names when doing an export and you also specified a value of 0 for the FILESIZE parameter. Note that 0 is the value used if FILESIZE is not specified on the command line. Since a value of 0 for FILESIZE means that only one file will be written and there is no size limit for that file, the other files you specified in the FILE parameter can never be used.

Action: If you intended to write multiple files, respecify the command but use the FILESIZE to specify the maximum number of bytes that EXPORT should write to each file. If you intended to write only one file with no limits on it s size, reissue the EXPORT command but specify only one file name for the FILE parameter.

EXP-00076: multiple devices specified for tape output

EXP-00076: multiple devices specified for tape output

Cause: You specified multiple file names when doing an export to a tape device. EXPORT uses the same device for writing all files, of the number of tape volumes required. For this reason, export will accept only one value for the FILE parameter when writing to tape.

Action: Reenter the EXPORT command, but specify only one tape device in the FILE parameter.

EXP-00075: rounding FILESIZE down, new value is string

EXP-00075: rounding FILESIZE down, new value is string

Cause: The FILESIZE parameter must be a multiple of the RECORDLENGTH, but the value you specified for FILESIZE does not meet this requirement. The value of FILESIZE has been rounded down to be a multiple of the RECORDLENGTH used for the dump file.

Action: No action is required. You can adjust the FILESIZE or RECORDLENGTH parameter to avoid this message. When importing this file, you must specify the FILESIZE value reported by this message.