Cause: Import encountered an Oracle error.

Cause: An invalid response was entered.

Cause: Import failed to open the export file for reading. This message is usually followed by a device message from the operating system.

Cause: Import encountered the referenced Oracle error.

Cause: An invalid username or password was specified.

Cause: An attempt was repeatedly made to log on with an invalid username or password.

Cause: Import failed to allocate the necessary memory.

Cause: The privileges needed to import into another user's account do not exist. Only a database administrator can import into another user's account.

Cause: Import did not recognize a statement in the export file. Either the export file was corrupted, or an Import internal error has occurred.

Cause: The export file is probably from an aborted Export session.

Cause: Either the file was not generated by Export or it was corrupted.

Cause: You tried to import an export file that contains formatted table data. Import only supports export files containing binary table data. wher

Cause: The Export mode specified in the export file header is invalid.

Cause: The privileges needed to Import an export file generated by a database administrator do not exist. Only a database administrator can import such files.

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

Cause: Import failed to create an object because it already exists.

Cause: Import could not convert the character format of the export file into the native character format.

Cause: Import failed to execute the statement from the export file because of an Oracle error.

Cause: A table was only partially imported because of an Oracle error.

Cause: Import encountered the referenced Oracle error while trying to import a row.

Cause: The column buffer is too small. This usually occurs when importing LONG data.

Cause: Import encountered the INCTYPE parameter when parsing Import options. Incremental Imports are no longer supported.

Cause: Invalid command-line parameters were specified.

Cause: The necessary Import views were not installed.

Cause: Parameters were specified that conflict with the import specification FULL=Y.

Cause: When importing a database administrator export file, you specified the TOUSER parameter but not the FROMUSER parameter.

Cause: Import encountered an Oracle error while trying to roll back a partial import.

Cause: Import encountered an Oracle error while trying to import a table.

Cause: A table name was qualified with the name of its owner, as shown in the following example. This is not allowed. IMP SYSTEM/MANAGER TABLES=(SCOTT.EMP)

Cause: Import was unable to create the specified file with write enabled.

Cause: The database administrator did not specify full or partial import.

Cause: The buffer was too small for the SQL statement being read.

Cause: A table name was specified that does not exist in export file.

Cause: The user specified a FROMUSER name that does not exist in export file.

Cause: On some platforms, import 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: An environment character set was specified that was not recognized by the Import utility.

Cause: The export file is corrupted.

Cause: Internal error.

Cause: The value specified for VOLSIZE does not match the value specified during the creation of the export file.

Cause: The value specified for FILESIZE does not match the value specified during the creation of the export file.

Cause: The object in the SQL statement following this error was created with compilation errors. If this error occurred for a view, it is possible that the base table of the view was missing.

Cause: The user requested that a specific character set be used to process an export file that has a specific embedded character set ID. The ID in the export file is accurate and should be used.

Cause: The character set of the export file and the environment character set (or the character set specified with the CHARSET keyword) are inconsistent. One character set is ASCII-based while the other is EBCDIC based.

Cause: Import was unable to allocate sufficient memory to read in the specified statement and execute it.

Cause: Either you did not specify the VOLSIZE parameter in your IMPORT command, or you specified VOLSIZE=0 and the export was created with a non-zero value for VOLSIZE. Import will use the value specified in the export file.

Cause: Either you did not specify the FILESIZE parameter in your IMPORT command, or you specified FILESIZE=0 and the export file was created with a non-zero value for FILESIZE. Import will use the value specified in the export file.

Cause: The header in the export file contains a sequence number that is used to track the order in which multiple export files are written. The first export file is assigned sequence number one, the second file is assigned sequence number two and so on. This message is displayed when a number other than the expected sequence number is found in the file header

Cause: During verification of the 2nd or subsequent file in a multi-file export, Import found header fields in the file that did not match values in the first file.

Cause: An unknown language was listed in the CHARSET option.

Cause: Identical names were given to the dump file and log file.

Cause: An invalid column length was encountered while processing column pieces."

Cause: An event could not be set for current the session.

Cause: The specified import option is incompatible with point-in-time- recovery dump file.

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

Cause: A partition or subpartition name was specified that does not exist in export file.

Cause: You specified multiple file names when doing an import from a tape device. Import uses the same device for reading all tapes, regardless 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: The dump file used for this Table Import might not contain all of the data belonging to the exported table.

Cause: Parameter manager failed in initialization.

Cause: An object type needed by the table, either does not exist on the * target system or, if it does exist, it has a different object identifier.

Cause: An object type cannot be created because it already exists on the * target system, but with a different identifier

Cause: The character string representing the object type's identifier * could not be converted to an object identifier.

Cause: An error occurred creating an object type that is used by the * table.

Cause: While producing the dump file, Export was unable to write the * entire contents of a LOB. Import is therefore unable to * reconstruct the contents of the LOB. The remainder of the * import of the current table will be skipped.

Cause: An error occurred recreating a LOB within an imported object.

Cause: No value for NLS_CHARACTERSET in props$.

Cause: Internal error.

Cause: An environment national character set was specified that was not recognized by the Import utility.

Cause: Internal error..

Cause: The number of LOBS per row in the dump file is different than the * number of LOBS per row in the table being populated.

Cause: An attempt was made to import data into a table that was recreated under a different object identifier than the object identifier used for the exported object table. Under this situation, REF's to this table that are contained within the dump file will also be invalid.

Cause: The character string representing the table's object identifier could not be converted to an internal object identifier.

Cause: The conversion of the specified directory and name strings for a file attribute or column from the export server's character set into the import server's character set exceeded the maximum string lengths allowed within FILE descriptors. The strings will be truncated to the maximum supported lengths.

Cause: Constraints exist in the data base that specify date values without fully specifying the year. These constraints could break in the year 2000 A.D.

Cause: An error occurred inserting data into an outer or inner nested table. If the error occurred in the outer table, rows are still inserted into the inner tables. If the error occurred in an inner table, data is still inserted into the outer table and other inner tables. This can result in duplicate inner table rows or partial logical rows.

Cause: No value for NLS_NCHAR_CHARACTERSET in props$.

Cause: Internal error.

Cause: (1) The current export dump file was generated using Beta-2 of Oracle8.0 AND (2) there was a File that appeared as an an attribute of an ADT within a table's column AND (3) the character set of the export server's database was different than the character set of the import server's database AND (4) when the filename or the aliasname of the File increased in size when it was translated to the character set of the import server. When all of these conditions are true, translation of the strings could yield corruption of the data in the column. Rather than proceeding with the translation, import will leave the character strings in the File in the old character set.

Cause: Due to a problem in 8.0.2 Export, national character data in NCHAR and NVARCHAR2 columns was incorrectly assumed to be in the export server's data base character set and was converted to the export client's data base character set. This conversion would only be correct if the export server's data base character set was the same as the export server's national character set and the export client's data base character set was the same as the export client's national character set. All other combinations would likely be incorrect. This export dump file was generated by 8.0.2 Export and the export client and server characater sets did not fit that criteria.

Cause: During piecewise character conversion of the data in a long column or of a long command, a fatal conversion error occurred. Either character truncation occurred or an invalid character set handle was used.

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

Cause: An error occured while attempting to to convert a ROWID from an export dump file into an internal format.

Cause: An incremental import was requested and the dump file specified for the import command is either a user or table export.

Cause: An incremental import was requested along with the FROMUSER, TOUSER, or TABLE qualifier. An incremental import cannot be done if any of these other qualifiers are also specified.

Cause: You specified multiple file names for the FILE parameter when doing an import, but the header in the export file indicates that that the export operation could create only one file. Specifying multiple file names is valid for an import operation only if the export files were created by an export operation in which the user specified a non-zero value for the FILESIZE parameter.

Cause: Import did not find the type identification specified in the TOID_NOVALIDATE parameter. The specified type identification does not exist in export file.

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

Cause: Domain indexes import private metadata via anonymous PL/SQL blocks prior to the CREATE INDEX statement. The execution of one of these PL/SQL blocks failed. Because the metadata is considered an integral part of the index, the subsequent CREATE INDEX statement was skipped.

Cause: Import user fails to recreate fine grained policies of the table/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.

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

Cause: An error occurred while executing a PL/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.

Cause: Import failed to create the Java source, class or resource object because it already exists.

Cause: Import failed to locate a base table for a constraint that was defined in the dump file and statistics were not imported.

Cause: The character string representing the object type's identifier * could not be converted.

Cause: Current session is not resumable.

Cause: An error occurred creating a synonym for a type that is used by the * table.

Cause: STREAMS_CONFIGURATION=Y can only be used * when FULL=Y is present on the command line

Cause: An INTERNAL error occurred.

Cause: The character string representing the object type's identifier * could not be converted.

Cause: An object type could not be created because it already existed on the * target system, but with a different typeid

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.

Cause: Parameter provided along data_only is invalid.

Cause: The import failed because the DDL had insufficient privileges.