Release 8.1.5
A67785-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8i Error Messages Release 8.1.5 A67785-01 |
|
This chapter lists messages generated by the Import utility. For more information about this utility, refer to Oracle8i Utilities.
IMP-00000 Import terminated unsuccessfully
Cause: Import encountered an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual, and take appropriate action.
IMP-00001 respond with either string, string, RETURN or '.' to quit
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
IMP-00002 failed to open string for read
Cause: Import failed to open the export file for reading. This message is usually followed by a device message from the operating system.
Action: Take appropriate action to restore the device.
IMP-00003 ORACLE error number encountered
Cause: Import encountered the referenced Oracle error.
Action: Look up the Oracle message in the ORA message chapters of this manual, and take appropriate action.
IMP-00004 invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
IMP-00005 all allowable logon attempts failed
Cause: An attempt was repeatedly made to log on with an invalid username or password.
Action: Retry with valid username and password.
IMP-00006 failed to allocate memory of size number
Cause: Import failed to allocate the necessary memory.
Action: Decrease the import buffer size so that less memory is required, or increase the runtime memory size for Import.
IMP-00007 must be a DBA to import objects to another user's account
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.
Action: Ask the database administrator to do the import.
IMP-00008 unrecognized statement in the export file: string
Cause: Import did not recognize a statement in the export file. Either the export file was corrupted, or an Import internal error has occurred.
Action: If the export file was corrupted, retry with a new export file. Otherwise, report this as an Import internal error and submit the export file to Oracle Customer Support.
IMP-00009 abnormal end of export file
Cause: The export file is probably from an aborted Export session.
Action: If so, retry the export and import. Otherwise, report this as an Import bug and submit the export file that caused this error to Oracle Customer Support.
IMP-00010 not a valid export file, header failed verification
Cause: Either the file was not generated by Export or it was corrupted.
Action: If the file was indeed generated by Export, report this an Import bug and submit the export file to Oracle Customer Support.
IMP-00011 formatted table data not currently supported
Cause: An attempt was made to import an export file that contains formatted table data. Import only supports export files containing binary table data.
Action: Retry using an export file that contains only binary table data.
IMP-00012 invalid export mode (character) in header
Cause: The Export mode specified in the export file header is invalid.
Action: Check the export file to see if it was corrupted. If it was not, report this as an Import bug and submit the export file to Oracle Customer Support.
IMP-00013 only a DBA can import a file exported by another DBA
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.
Action: Ask the database administrator to do the import.
IMP-00014 option "string" is needed, but not present in database
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.
Action: Reinstall Oracle with the option specified by the message.
IMP-00015 following statement failed because the object already exists:
Cause: Import failed to create an object because it already exists.
Action: Specify IGNORE=Y to ignore such errors and import rows even when tables are not created because they already exist.
IMP-00016 required character set conversion (type number to number) not supported
Cause: Import could not convert the character format of the export file into the native character format.
Action: Change the user character set by setting the NLS_LANG environment variable to match the character set of the export file.
IMP-00017 following statement failed with ORACLE error number:
Cause: Import failed to execute the statement from the export file because of an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
IMP-00018 partial import of previous table completed: number rows imported
Cause: A table was only partially imported because of an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
IMP-00019 row rejected due to ORACLE error number
Cause: Import encountered the referenced Oracle error while trying to import a row.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
IMP-00020 long column too large for column buffer size (number)
Cause: The column buffer is too small. This usually occurs when importing LONG data.
Action: Increase the insert buffer size 10,000 bytes at a time (for example). Use this step-by-step approach because a buffer size that is too large may cause a similar problem.
IMP-00021 operating system error - error code (dec number, hex 0xnumber)
Cause: An operating system error has occurred.
Action: Look up the referenced message in your operating system-specific Oracle documentation and take appropriate action.
IMP-00022 failed to process parameters, type 'IMP 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.
IMP-00023 Import views not installed, please notify your DBA
Cause: The necessary Import views were not installed.
Action: Ask your database administrator to install the required Import views.
IMP-00024 Only one mode (TABLES, FROMUSER, or FULL) can be specified
Cause: Parameters were specified that conflict with the import specification FULL=Y.
Action: Retry, making sure not to specify FULL=Y.
IMP-00025 for DBA export files, FROMUSER must be specified with TOUSER option
Cause: When importing a database administrator export file, you specified the TOUSER parameter but not the FROMUSER parameter.
Action: Specify the FROMUSER parameter so that Import knows which user's objects to import.
IMP-00027 failed to rollback partial import of previous table
Cause: Import encountered an Oracle error while trying to roll back a partial import.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action. Then, log on to Oracle and check that the partial import was not committed.
IMP-00028 partial import of previous table rolled back: number rows rolled back
Cause: Import encountered an Oracle error while trying to import a table.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action. Then, if necessary, re-import the table.
IMP-00029 cannot qualify table name by owner (string), use FROMUSER parameter
Cause: A table name was qualified with the name of its owner, as shown in the following example:
IMP SYSTEM/MANAGER TABLES=(SCOTT.EMP)
This is not allowed.
Action: Use the FROMUSER parameter to specify the table's owner, as shown in the following example:
IMP SYSTEM/MANAGER FROMUSER=SCOTT TABLES=(EMP, DEPT)
IMP-00030 failed to create file string for write
Cause: Import was unable to create the specified file with write enabled.
Action: Check the file name and file system for the source of the error.
IMP-00031 Must specify FULL=Y or provide FROMUSER/TOUSER or TABLES arguments
Cause: The database administrator did not specify full or partial import.
Action: The database administrator must specify FROMUSER/TOUSER or table arguments if not a full import.
IMP-00032 SQL statement exceeded buffer length
Cause: The buffer was too small for the SQL statement being read.
Action: Rerun with a larger buffer. This can also be an indication of a corruption in the import datafile.
IMP-00033 Warning: Table "string" not found in export file
Cause: A table name was specified that does not exist in export file.
Action: Correct the table specification.
IMP-00034 Warning: FromUser "string" not found in export file
Cause: The user specified a FROMUSER name that does not exist in export file.
Action: Correct the FROMUSER specification.
IMP-00035 input file string must be on a disk
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.
Action: Verify that you have specified the correct file name for the import file. Remember that all input files can be either on disk or all files can be on tape, but not mixed both tape and disk.
IMP-00036 Could not find environment character set
Cause: An environment character set was specified that was not recognized by the Import utility.
Action: Ensure that the spelling of the character set specified in the command line parameter CHARSET (for Release 6 only) or the environment variable NLS_LANG is correct.
IMP-00037 Character set marker unknown
Cause: The export file is corrupted.
Action: Try to obtain an uncorrupted version of the export file. If the export file is not corrupted, report this as an Import internal error and submit the export file to Oracle Customer Support.
IMP-00038 Could not convert to environment character set's handle
Cause: This is an internal error.
Action: Contact Oracle Customer Support.
IMP-00039 VOLSIZE does not match the value used for export: string
Cause: The value specified for VOLSIZE does not match the value specified during the creation of the export file.
Action: If you believe that the specified VOLSIZE value is correct, verify that you specified the correct file for import. If you specified the correct file but are unsure about the correct value, re-execute the import command but specify VOLSIZE=0.
IMP-00040 FILESIZE does not match the value used for export: string
Cause: The value specified for FILESIZE does not match the value specified during the creation of the export file.
Action: If you believe the specified FILESIZE value is correct, verify that you specified the correct file for import. If you specified the correct file but are unsure about the correct value, re-execute the import command but specify FILESIZE=0.
IMP-00041 Warning: object created with compilation warnings
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.
Action: This is a warning. The object may have to be recompiled before being used.
IMP-00042 CHARSET used, but the export file has specific character set
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.
Action: Remove the CHARSET keyword from the command line.
IMP-00043 export file character set inconsistent
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.
Action: Specify the correct character set with the CHARSET keyword.
IMP-00044 unable to allocate enough memory for statement
Cause: Import was unable to allocate sufficient memory to read in the specified statement and execute it.
Action: Increase the allocation for database buffers, restart the instance, and re-execute the Import command.
IMP-00045 using VOLSIZE value from export file of string
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.
Action: No action required.
IMP-00046 using FILESIZE value from export file of string
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.
Action: No action required.
IMP-00047 unexpected file sequence number; expected number but found number
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
Action: Execute the import command again, but specify the files in the order in which Export wrote them.
IMP-00048 mismatched 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.
Action: Check the names of the files created by Export and verify that you specified them correctly for the import operation.
IMP-00049 Unknown language specified in CHARSET
Cause: An unknown language was listed in the CHARSET option.
Action: Use a known character set.
IMP-00050 Dump file and log file cannot be identical
Cause: Identical names were given to the dump file and log file.
Action: Specify different names for the dump file and log file and retry the operation.
IMP-00051 Direct path exported dump file contains illegal column length
Cause: An invalid column length was encountered while processing column pieces.
Action: Check to make sure the export file is not corrupted, or else report this to Oracle Customer Support as an Import/Export internal bug and submit the export file.
IMP-00052 Warning: Unable to set event for freelist communication with server
Cause: An event could not be set for current the session.
Action: If Import fails, give the Import user ALTER SESSION PRIV and retry the operation.
IMP-00053 Import mode incompatible with Export dump file
Cause: The specified import option is incompatible with point-in-time- recovery dump file.
Action: Generate a proper dump file or use point-in-time-recovery import mode.
IMP-00054 must be a DBA to do Tablespace Point-in-time Recovery import
Cause: The user does not have the privileges to perform Tablespace Point- in-time Recovery import.
Action: Ask your database administrator to perform the Tablespace Point-in- time Recovery import.
IMP-00055 Warning: partition or subpartition "string":"string" not found in export file
Cause: A partition or subpartition name was specified that does not exist in export file.
Action: Check to make sure the partition or subpartition name belongs to the table.
IMP-00056 multiple devices specified for tape input
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.
Action: Re-enter the IMPORT command, but specify only one tape device in the FILE parameter.
IMP-00057 Warning: Dump file may not contain data of all partitions of this table
Cause: The dump file used for this Table Import might not contain all of the data belonging to the exported table.
Action: Check to see if the export was done as intended, or try performing a Partition Import.
IMP-00059 Failure to initialize parameter manager
Cause: Parameter manager failed in initialization.
Action: Report this to Oracle Customer Support as an Import internal bug.
IMP-00060 Warning: Skipping table "string"."string" because object type "string"."string" does not exist or has different identifier
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.
Action: Create the object type on the target system with a valid identifier.
IMP-00061 Warning: Object type "string"."string" already exists with a different identifier
Cause: An object type cannot be created because it already exists on the target system, but with a different identifier.
Action: Drop the object type from the target system and retry the operation.
IMP-00062 Warning: The identifier on the dump file for object type "string"."string" is invalid
Cause: The character string representing the object type's identifier could not be converted to an object identifier. This is an internal error.
Action: Contact Oracle Customer Support.
IMP-00063 Warning: Skipping table "string"."string" because object type "string"."string" cannot be created or has different identifier
Cause: An error occurred creating an object type that is used by the table.
Action: Examine the import log to determine why the object type could not be created. If the object type already existed, with a different object identifier, then drop the object type and retry the import.
IMP-00064 Definition of LOB was truncated by export
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.
Action: Delete the offending row in the exported database and retry the export.
IMP-00065 Import is unable to recreate lobs within objects.
Cause: An error occurred while re-creating a LOB within an imported object.
Action: Report this to Oracle Customer Support as an Import internal error.
IMP-00066 Missing NLS_CHARACTERSET in props$
Cause: No value for NLS_CHARACTERSET in props$.
Action: Contact Oracle Customer Support.
IMP-00067 Could not convert to server character set's handle
Cause: This is an internal error.
Action: Contact Oracle Customer Support.
IMP-00068 Could not find environment national character set
Cause: An environment national character set was specified that was not recognized by the Import utility.
Action: Ensure that the spelling of the national character set specified in the environment variable NLS_NCHAR is correct.
IMP-00069 Could not convert to environment national character set's handle
Cause: This is an internal error.
Action: Contact Oracle Customer Support.
IMP-00070 Lob definitions in dump file are inconsistent with database.
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.
Action: Modify the table being imported so that it matches the column attribute layout of the table that was exported.
IMP-00071 Object identifier of imported table mismatches object identifier of existing table
Cause: An attempt was made to import data into a table that was re-created 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.
Action: Drop the offending object table prior to import.
IMP-00072 Warning: The object table's object identifier is invalid.
Cause: The character string representing the table's object identifier could not be converted to an internal object identifier. This is an internal error.
Action: Contact Oracle Customer Support.
IMP-00073 FILE locator "string" "string" is truncated to "string" "string" in server character set
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.
Action: Rename the directory aliases and external file names to match the truncated names in the specified FILE column or attribute.
IMP-00074 The constraints flagged by ALL_CONSTRAINTS.BAD will break in 2000 A.D.
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.
Action: Query ALL_CONSTRAINTS and correct those constraints marked as bad.
IMP-00075 Warning: The nested table may contain partial rows or duplicate rows
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.
Action: Examine the data in the tables. Delete the incorrect rows or drop the entire table and perform the import again.
IMP-00076 Missing NLS_NCHAR_CHARACTERSET in props$
Cause: No value for NLS_NCHAR_CHARACTERSET in props$.
Action: Contact Oracle Customer Support.
IMP-00077 Could not convert to server national character set's handle
Cause: This is an internal error.
Action: Contact Oracle Customer Support.
IMP-00078 Cannot translate FILE locator to "string" "string" in server character set
Cause:
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.
Action: After import completes, rename the directory aliases and external file names to match the real names used for the target database.
IMP-00079 Warning: National character set data in this table may be incorrect
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 character sets did not fit that criteria.
Action: Examine the national character data. If incorrect, update the data with correct data.
IMP-00080 Error during character conversion of long column or long command
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.
Action: Retry the import with a different character set.
IMP-00081 attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Customer Support
IMP-00082 Error during conversion ROWID from string format to internal
Cause: An error occurred while attempting to convert a ROWID from an export dump file into an internal format.
Action: Report this to Oracle Customer Support as an Import internal error.
IMP-00083 dump file does not contain an incremental export
Cause: An incremental import was requested and the dump file specified for the import command is either a user or table export.
Action: Reissue the command import command but specify the name of a dump file containing an incremental export.
IMP-00084 attempt to mix incremental import with user or table import
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.
Action: Determine whether you want to do an incremental import, full import, user import or table import and reissue the import command with the appropriate qualifiers.
IMP-00085 multiple input files specified for unbounded export file
Cause: You specified multiple file names for the FILE parameter when doing an import, but the header in the export file indicates 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.
Action: If you believe the export contains multiple files, verify that you have specified the correct files. If you believe the export should be in only one file then try the import operation again, but specify only one value for the FILE parameter.
IMP-00086 TOID "string" not found in export file
Cause: Import did not find the type identification specified in the TOID_NOVALIDATE parameter. The specified type identification does not exist in export file.
Action: Correct or omit the TOID_NOVALIDATE parameter.
IMP-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 Customer Support
IMP-00088 Problem importing metadata for index string. Index creation will be skipped
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.
Action: Contact the developer of the index's implementation type. If this is an Oracle-supplied index (perhaps via a data cartridge), contact Oracle Customer Support.
IMP-00089 Fine grain access control policies not recreated on table/view "string"
Cause: Import user fails to re-create access control policies of the table/view being imported. To re-create the policy, the user doing the import needs execute privilege on the package DBMS_RLS.
Action: Ask the database administrator to perform the export/import of this table/view.
IMP-00090 Unexpected DbmsJava error number at step number while creating string
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Import internal error to Oracle Customer Support.
IMP-00091 Above error occurred on the following function and object: string. Remaining PL/SQL blocks for this object will be skipped.
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.
Action: Contact Oracle Customer Support so they may determine the development group responsible for the package that failed.
IMP-00092 Java object "string"."string" already exists, cannot be created
Cause: Import failed to create the Java source, class or resource object because it already exists.
Action: Drop the object type from the target system and retry the operation.
