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.

EXP-00074: rounding VOLSIZE down, new value is string

EXP-00074: rounding VOLSIZE down, new value is string

Cause: The VOLSIZE parameter must be a multiple of the RECORDLENGTH, but the value you specified for VOLSIZE does not meet this requirement. The value of VOLSIZE 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 VOLSIZE or RECORDLENGTH parameter to avoid this message. When importing this file, you must specify the VOLSIZE value reported by this message.

EXP-00073: dump file size too small

EXP-00073: dump file size too small

Cause: You specified either the FILESIZE parameter or the VOLSIZE parameter (if your platform supports it), and the value of the parameter is too small to hold the header information for the export file, plus any data.

Action: Increase the value of the FILESIZE or VOLSIZE parameter.

EXP-00072: error closing export file string

EXP-00072: error closing export file string

Cause: An error occurred while trying to close the export file.

Action: Contact Oracle Worldwide Support.

EXP-00071: QUERY parameter not compatible with Direct Path export

EXP-00071: QUERY parameter not compatible with Direct Path export

Cause: You specified a value for the QUERY parameter for a direct path export. The QUERY parameter cannot be used with a direct path export.

Action: Re-issue the export command with DIRECT=N or omit the DIRECT parameter from the command line.

EXP-00070: attempt to free unallocated memory

EXP-00070: attempt to free unallocated memory

Cause: An attempt was made to free memory that was not allocated.

Action: Contact Oracle Worldwide Support

EXP-00068: tablespace string is offline

EXP-00068: tablespace string is offline

Cause: Export failed to export tablespace (tablespace being offline).

Action: Make tablespace online and re export.

EXP-00066: Object table string is missing its object identifier index

EXP-00066: Object table string is missing its object identifier index

Cause: All object tables must have an object identifier index, but the specified table was missing an index on its object identifier column.

Action: Recreate the type table and retry the operation.

EXP-00065: Error writing lob to the dump file.

EXP-00065: Error writing lob to the dump file.

Cause: The current LOB could not be written to the dump file.

Action: Identify the cause of the write failure and fix it.

EXP-00064: %s is an inner nested table and cannot be exported.

EXP-00064: %s is an inner nested table and cannot be exported.

Cause: An attempt was made to export an inner nested table without its parent table.

Action: Export the parent of the inner nested table.

EXP-00063: error in changing language handle

EXP-00063: error in changing language handle

Cause: Unable to change language handle.

Action: Contact Oracle Worldwide Support.

EXP-00062: invalid source statements for an object type

EXP-00062: invalid source statements for an object type

Cause: TYPE was not found in the statements in SOURCE$ for an Object Type

Action: Contact Oracle Worldwide Support.

EXP-00061: unable to find the outer table name of a nested table

EXP-00061: unable to find the outer table name of a nested table

Cause: While exporting a bitmap index or posttable action on an inner nested table, the name of the outer table could not be located, using the NTAB$ table.

Action: Verify the table is properly defined.

EXP-00060: an object type had multiple TYPE BODYs

EXP-00060: an object type had multiple TYPE BODYs

Cause: More than one TYPE BODY was found for an object type.

Action: Try dropping the TYPE BODY, if that is not successful, contact Oracle Worldwide Support

EXP-00029: Incremental export mode and consistent mode are not compatible

EXP-00029: Incremental export mode and consistent mode are not compatible

Cause: Both consistent and incremental exports were specified.

Action: None. Consistent mode is turned off.

EXP-00028: failed to open string for write

EXP-00028: failed to open string for write

Cause: Export failed to open the export file for writing. This message is usually followed by device messages from the operating system.

Action: Take appropriate action to restore the device.

EXP-00027: failed to calculate ORACLE block size

EXP-00027: failed to calculate ORACLE block size

Cause: Export failed to calculate the Oracle block size.

Action: Report this as an Export internal error to customer support.

EXP-00026: conflicting modes specified

EXP-00026: conflicting modes specified

Cause: Conflicting export modes were specified.

Action: Specify only one parameter and retry.

EXP-00025: dictionary shows no column for constraint string.number

EXP-00025: dictionary shows no column for constraint string.number

Cause: Export failed to gather column information about the referenced constraint from the data dictionary. The constraint may have been altered.

Action: Retry the export and, if this error recurs, report it as an Export internal error to customer support.

EXP-00024: Export views not installed, please notify your DBA

EXP-00024: Export views not installed, please notify your DBA

Cause: The necessary Export views were not installed.

Action: Ask the database administrator to install the required Export views.

EXP-00023: must be a DBA to do Full Database or Tablespace export

EXP-00023: must be a DBA to do Full Database or Tablespace export

Cause: The privileges needed to do a FULL database export do not exist. Only a database administrator can do a FULL database export.

Action: Ask the database administrator to do the FULL database export.

EXP-00022: must be SYS or SYSTEM to do incremental export

EXP-00022: must be SYS or SYSTEM to do incremental export

Cause: The privileges needed to do an incremental export do not exist. Only a data base administrator can do incremental exports.

Action: Ask the database administrator to do the incremental export.

EXP-00021: can only perform incremental export in Full Database mode

EXP-00021: can only perform incremental export in Full Database mode

Cause: USER or TABLE mode was specified when doing an incremental export.

Action: Specify FULL database mode (FULL=Y) and retry.

EXP-00020: failed to allocate memory of size number

EXP-00020: failed to allocate memory of size number

Cause: Export failed to allocate the necessary memory.

Action: Decrease the export buffer size so that less memory is required, or increase the runtime memory size for Export.

EXP-00019: failed to process parameters, type EXP HELP=Y for help

EXP-00019: failed to process parameters, type EXP HELP=Y for help

Cause: Invalid command-line parameters were specified.

Action: Check the online help screen for the set of valid parameters, then retry.

EXP-00018: datatype (number) for column string, table string.string is not supported

EXP-00018: datatype (number) for column string, table string.string is not supported

Cause: Export does not support the referenced datatype.

Action: Retry with an acceptable datatype (CHAR, NUMBER, DATE, LONG, or RAW).

EXP-00017: feature string is needed, but not present in database

EXP-00017: feature string is needed, but not present in database

Cause: The command entered requires the specified feature. Either that feature is not installed, or the row describing the feature is missing from table V$OPTION

Action: Reinstall Oracle with the feature specified in the message.

EXP-00016: ORACLE error encountered while reading default auditing options

EXP-00016: ORACLE error encountered while reading default auditing options

Cause: Export encountered an Oracle error while reading the default auditing options (those for updates, deletes, and so on).

Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.

EXP-00015: error on row number of table string, column string, datatype number

EXP-00015: error on row number of table string, column string, datatype number

Cause: Export encountered an error while fetching or writing the column. An accompanying message gives more information.

Action: Correct the error and try again.

EXP-00014: error on row number of table string

EXP-00014: error on row number of table string

Cause: Export encountered an Oracle error while fetching rows.

Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.

EXP-00013: respond with either Y , N , RETURN or . to quit

EXP-00013: respond with either Y , N , RETURN or . to quit

Cause: An invalid response was entered.

Action: Enter any of the responses shown in the message.

EXP-00012: %s is not a valid export mode

EXP-00012: %s is not a valid export mode

Cause: An invalid export mode was specified.

Action: Retry with a valid export mode.

EXP-00011: %s.string does not exist

EXP-00011: %s.string does not exist

Cause: Export could not find the specified table.

Action: Retry with the correct table name.

EXP-00010: %s is not a valid username

EXP-00010: %s is not a valid username

Cause: An invalid username was specified.

Action: Shut down the utility, then restart and retry with a valid username.

EXP-00009: no privilege to export string s table string

EXP-00009: no privilege to export string s table string

Cause: An attempt was made to export another user s table. Only a database administrator can export another user s tables.

Action: Ask your database administrator to do the export.

EXP-00008: ORACLE error number encountered

EXP-00008: ORACLE error number encountered

Cause: Export encountered the referenced Oracle error.

Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.

EXP-00007: dictionary shows no columns for string.string

EXP-00007: dictionary shows no columns for string.string

Cause: Export failed to gather column information from the data dictionary. The table may have been dropped.

Action: Retry the export and, if this error recurs, report it as an Export internal error to customer support.

EXP-00006: internal inconsistency error

EXP-00006: internal inconsistency error

Cause: Export s data structure was corrupted.

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

EXP-00005: all allowable logon attempts failed

EXP-00005: all allowable logon attempts failed

Cause: Attempts were repeatedly made to log on with an invalid username or password.

Action: Shut down the utility, then restart and retry with a valid username and password.

EXP-00004: invalid username or password

EXP-00004: invalid username or password

Cause: An invalid username or password was specified.

Action: Retry with a valid username and password.

EXP-00003: no storage definition found for segment(number, number)

EXP-00003: no storage definition found for segment(number, number)

Cause: Export could not find the storage definitions for a cluster, index, or table.

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

EXP-00002: error in writing to export file

EXP-00002: error in writing to export file

Cause: Export could not write to the export file, probably because of a device error. This message is usually followed by a device message from the operating system.

Action: Take appropriate action to restore the device.

EXP-00001: data field truncation - column length=number, buffer size=number actual size=number

EXP-00001: data field truncation - column length=number, buffer size=number actual size=number

Cause: Export could not fit a column in the data buffer.

Action: Record the given size parameters and the accompanying messages and report this as an Export internal error to customer support. (Part of the table has been exported. Export will continue with the next table.)

EXP-00000: Export terminated unsuccessfully

EXP-00000: Export terminated unsuccessfully

Cause: Export encountered an Oracle error.

Action: Look up the accompanying Oracle message in the ORA message chapters of this manual, and take appropriate action.