21 EXP-00000 to EXP-00107

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.

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-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-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-00004: invalid username or password: Cause: An invalid username or password was specified.; Action: Retry with a valid username and password.

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-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-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-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-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-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-00011: %s.string does not exist: Cause: Export could not find the specified table.; Action: Retry with the correct table name.

EXP-00012: %s is not a valid export mode: Cause: An invalid export mode was specified.; Action: Retry with a valid export mode.

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-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-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-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-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-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-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-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-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-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-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-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-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-00026: conflicting modes specified: Cause: Conflicting export modes were specified.; Action: Specify only one parameter and retry.

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-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-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-00030: Unexpected End-Of-File encountered while reading input: Cause: Encountered an End-Of-File while reading the user input.; Action: If input to export is being redirected, check the file for errors.

EXP-00031: Arraysize not in valid range. Using arraysize=number: Cause: The arraysize value specified is not in the valid range.; Action: None

EXP-00032: Non-DBAs may not export other users: Cause: Only database administrators can export to other users. A non- database administrator attempted to specify owner=user where exporter is not the user.; Action: Request that this operation be performed by the database administrator.

EXP-00033: Could not find environment character set: Cause: The environment character set is missing or incorrectly specified.; Action: Ensure that the environment character set is correctly specified and is present.

EXP-00034: error on rowid: file# number block# number slot# number: Cause: Identifies the rowid on which an error occurred.; Action: This is an information message. No action is required.

EXP-00035: QUERY parameter valid only for table mode exports: Cause: You specified the QUERY parameter in an export command, but you are not performing a table mode export. The QUERY parameter cannot be used for a user mode export, a full export, nor a point in time recovery export.; Action: If you want to select a subset of rows for a table, you must export the table independently with a table mode export. Issue a table mode export command that specifies the table name and the query you want to execute during export.

EXP-00036: Object number non-existent in dictionary: Cause: The specified object could not be found in the dictionary. The object might have been dropped during the export; Action: The object no longer exists; no action is needed.

EXP-00037: Export views not compatible with database version: Cause: The Export utility is at a higher version than the database version and is thereby incompatible.; Action: Use the same version of Export utility as the database.

EXP-00038: Bad Hash cluster id in clu$: Cause: The function id in clu$ is not a legal number. Clu$ has become corrupted.; Action: Contact Worldwide Support

EXP-00039: export file string must be on a disk: Cause: On some platforms, export can read files from tape. This message is displayed if the first file in an export file set was on disk and you specified a tape device for a second or subsequent file.; Action: Verify that you have specified the correct file name for the export file. Remember that all export files can be either on disk or all files can be on tape, but not mixed both tape and disk.

EXP-00040: Dump file and log file must be different: Cause: The dump file and log file cannot be the same file.; Action: Specify different file names for the dump file and the log file, then retry the operation.

EXP-00041: INCTYPE parameter is obsolete: Cause: Export encountered the INCTYPE parameter when parsing Export options. Incremental Exports are no longer supported.; Action: Consult the Oracle Backup and Recovery guide. Export will attempt to continue.

EXP-00042: Missing NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET in props$: Cause: A value for NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET was not entered in the props$ table"; Action: internal error.

EXP-00043: Invalid data dictionary information in the row where column "string" is "string" in table string: Cause: The export utility retrieved invalid data from the data dictionary.; Action: Contact Oracle Worldwide Suport.

EXP-00044: must be connected "AS SYSDBA" to do Point-in-time Recovery or Transportable Tablespace import: Cause: The user must log in "as SYSDBA" to perform transportable tablespace imports or Point-In-Time Recovery imports.; Action: Ask your database adminstrator to perform the Transportable Tablespace import or the Tablespace Point-in-time Recovery import.

EXP-00045: Cannot export SYSTEM Tablespace for Point-in-time Recovery or Transportable Tablespace: Cause: SYSTEM tablespace cannot be part of recovery set or transportable tablespace set.; Action: Contact Oracle Wordwide Support.

EXP-00046: Tablespace named string does not exist: Cause: The specified tablespace does not exist in dictionary.; Action: Contact Oracle Wordwide Support.

EXP-00047: Missing tablespace name(s): Cause: Tablespace name(s) were not supplied; Action: Provide tablespace name(s)

EXP-00048: Cannot export SYSAUX Tablespace for Point-in-time Recovery or Transportable Tablespace: Cause: SYSAUX tablespace cannot be part of recovery set or transportable tablespace set.; Action: Contact Oracle Wordwide Support.

EXP-00049: %s option is not compatible with Point-in-time Recovery or Transportable Tablespace Export: Cause: An option was specified incompatible with Point-in-time Recovery or Transportable Tablespace Export.; Action: Retry the Export without the displayed option.

EXP-00050: Cannot perform Partition Export "string" on non-partitioned table "string": Cause: The table specified in this Partition Export is not a partitioned table.; Action: Use Table mode, or specify a non-partitioned table.

EXP-00051: "string" - given partition or subpartition name is not part of "string" table: Cause: The specified partition or subpartition name is not in the specified table.; Action: Check if the correct table, partition or subpartition name was specified.

EXP-00052: error on row number of partition string: Cause: Export encountered the referenced Oracle error while fetching rows.; Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.

EXP-00053: unable to execute QUERY on table string because the table has inner nested tables: Cause: You specified the QUERY parameter on a table that has one or more inner nested tables. The QUERY parameter cannot be specified on tables that have inner nested tables.; Action: Export the entire table by omitting the QUERY parameter.

EXP-00054: error on row number of subpartition string: Cause: Export encountered the referenced Oracle error while fetching rows.; Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.

EXP-00055: %s.string is marked not exportable: Cause: An object was marked as non-exportable in the NOEXP$ table.; Action: Consult your database administrator.

EXP-00057: Failure to initialize parameter manager: Cause: The parameter manager failed in intialization.; Action: Record the messages that follow and report this to Oracle Wordwide Support as an Export internal bug.

EXP-00058: Password Verify Function for string profile does not exist: Cause: Cannot find the function for the profile.; Action: Check if the profile was created properly.

EXP-00059: error converting an object type"s identifier to characters: Cause: An invalid length of an object type identifier prevented its conversion.; Action: Contact Oracle Worldwide Support

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-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-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-00063: error in changing language handle: Cause: Unable to change language handle.; Action: Contact Oracle Worldwide Support.

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-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-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-00068: tablespace string is offline: Cause: Export failed to export tablespace (tablespace being offline).; Action: Make tablespace online and re export.

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-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-00072: error closing export file string: Cause: An error occurred while trying to close the export file.; Action: Contact Oracle Worldwide Support.

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-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-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-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-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-00078: Error exporting metadata for index string. Index creation will be skipped: Cause: Domain indexes export private metadata via anonymous PL/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-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/import this table/view.

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/import this table/view.

EXP-00081: Exporting access control for table/view "string" as non-DBA.: Cause: A non-DBA user tries to export table/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/view. And such an event may cause inconsistency in the security model of the table/view.; Action: Ask the database administrator to export/import this table/view.

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-00083: The previous problem occurred when calling string.string.string: Cause: The listed package provides export/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-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-00085: The previous problem occurred when calling string.string.string for object number: Cause: The listed package provides export/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-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/Import to move Primary key REFs between databases having differing character sets.

EXP-00087: Problem with internal hash table of schema/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-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-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-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-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-00093: Could not convert to server character set"s handle: Cause: Internal error.; Action: Contact Worldwide support.

EXP-00094: Could not convert to server national character set"s handle: Cause: Internal error.; Action: Contact Worldwide support.

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-00097: Object type "string"."string" is not in a valid state, type will not be exported: Cause: The object type"s status is invalid which may be caused by a dependant type"s modification (or removal) without cascading the change.; Action: The type must be recompiled using ALTER TYPE COMPILE.

EXP-00098: Data in table has not been upgraded, table will not be exported: Cause: Export is attempting to process a table containing references to a type which has evolved. In order for Export to process the table successfully, all data within each table must be upgraded to the latest revision of each referenced type.; Action: The table must be updated using ALTER TABLE UPGRADE DATA.

EXP-00099: Table "string"."string" is not in a valid state, table will not be exported: Cause: A table or one of its dependant types has modified without cascading the change. This left the table in an INVALID state.; Action: The table must be updated using ALTER TABLE UPDATE.

EXP-00100: error converting an object type"s hashcode to characters: Cause: An invalid length of an object type identifier prevented its conversion.; Action: Contact Oracle Worldwide Support

EXP-00101: Version 1 extensible index "string"."string" can not be included in Transportable Tablespace Export: Cause: Transporable Tablespace extensible indexes must be at least version 2.; Action: Upgrade extensibile index implementation to version 2 specifications.

EXP-00102: 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.

EXP-00103: The FLASHBACK_TIME parameter was invalid: Cause: FLASHBACK_TIME did not contain a valid timestamp or an expression that yields a valid timestamp.; Action: Specify a timestamp value in the format of YYYY-MM-DD HH24:MI:SS or an expression that evaluates to a valid timestamp.

EXP-00104: datatype (string) of column string in table string.string is not supported, table will not be exported: Cause: The column is of a datatype which does not contain the required support. The table will not be exported.; Action: Use the Data Pump version of Export to export this table.

EXP-00105: parameter string is not supported for this user: Cause: The user attempted to specify either CONSISTENT or OBJECT_CONSISTENT when connected as sysdba.; Action: If a consistent export is needed, then connect as another user.

EXP-00106: Invalid Database Link Passwords: Cause: Invalid Encoded Password for Database Link; Action: Please drop the Database Link and recreate it after import.

EXP-00107: Feature (string) of column string in table string.string is not supported. The table will not be exported.: Cause: Export does not contain the required support for this feature. The table will not be exported.; Action: Use the Data Pump version of Export to export this table.