21 EXP-00000 to EXP-00105

Cause: Export encountered an Oracle error.

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

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.

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

Cause: An invalid username or password was specified.

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

Cause: Export's data structure was corrupted.

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

Cause: Export encountered the referenced Oracle error.

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

Cause: An invalid username was specified.

Cause: Export could not find the specified table.

Cause: An invalid export mode was specified.

Cause: An invalid response was entered.

Cause: Export encountered an Oracle error while fetching rows.

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

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

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

Cause: Export does not support the referenced datatype.

Cause: Invalid command-line parameters were specified.

Cause: Export failed to allocate the necessary memory.

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

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

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

Cause: The necessary Export views were not installed.

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

Cause: Conflicting export modes were specified.

Cause: Export failed to calculate the Oracle block size.

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

Cause: Both consistent and incremental exports were specified.

Cause: Encountered an End-Of-File while reading the user input.

Cause: The arraysize value specified is not in the valid range.

Cause: Only database administrators can export to other users. A non- database administrator attempted to specify owner=user where exporter is not the user.

Cause: The environment character set is missing or incorrectly specified.

Cause: Identifies the rowid on which an error occurred.

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.

Cause: The specified object could not be found in the dictionary. The object might have been dropped during the export

Cause: The Export utility is at a higher version than the database version and is thereby incompatible.

Cause: The function id in clu$ is not a legal number. Clu$ has become corrupted.

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.

Cause: The dump file and log file cannot be the same file.

Cause: Export encountered the INCTYPE parameter when parsing Export options. Incremental Exports are no longer supported.

Cause: A value for NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET was not entered in the props$ table"

Cause: The export utility retrieved invalid data from the data dictionary.

Cause: The user must log in 'as SYSDBA' to perform transportable tablespace imports or Point-In-Time Recovery imports.

Cause: SYSTEM tablespace cannot be part of recovery set or transportable tablespace set.

Cause: The specified tablespace does not exist in dictionary.

Cause: Tablespace name(s) were not supplied

Cause: SYSAUX tablespace cannot be part of recovery set or transportable tablespace set.

Cause: An option was specified incompatible with Point-in-time Recovery or Transportable Tablespace Export.

Cause: The table specified in this Partition Export is not a partitioned table.

Cause: The specified partition or subpartition name is not in the specified table.

Cause: Export encountered the referenced Oracle error while fetching rows.

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.

Cause: Export encountered the referenced Oracle error while fetching rows.

Cause: An object was marked as non-exportable in the NOEXP$ table.

Cause: The parameter manager failed in intialization.

Cause: Cannot find the function for the profile.

Cause: An invalid length of an object type identifier prevented its conversion.

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

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.

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

Cause: Unable to change language handle.

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

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

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

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

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

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.

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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

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

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

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.

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

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

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

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).

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.

Cause: Export was unable to set NLS_NUMERIC_CHARACTERS to '.,'

Cause: Internal error.

Cause: Internal error.

Cause: Both flashback_time and flashback_scn paramerers were specified.

Cause: The object type's status is invalid which may be caused by a dependant type's modification (or removal) without cascading the change.

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.

Cause: A table or one of its dependant types has modified without cascading the change. This left the table in an INVALID state.

Cause: An invalid length of an object type identifier prevented its conversion.

Cause: Transporable Tablespace extensible indexes must be at least version 2.

Cause: Current session is not resumable.

Cause: FLASHBACK_TIME did not contain a valid timestamp or an expression that yields a valid timestamp.

Cause: The column is of a datatype which does not contain the required support. The table will not be exported.

Cause: The user attempted to specify either CONSISTENT or OBJECT_CONSISTENT when connected as sysdba.