Release 8.0
A54625_01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0 A54625_01 |
|
This chapter lists messages generated by the Import utility. For more information on this utility, refer to Oracle8 Server Utilities.
The messages listed in this chapter are displayed with the prefix IMP signifying Import.
If you are using Trusted Oracle, see the Trusted Oracle documentation for information about error messages in that environment.
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.
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
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.
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.
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
Cause: An attempt was repeatedly made to log on with an invalid username or password.
Action: Retry with valid username and password.
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.
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.
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 customer support.
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 customer support.
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 customer support.
Cause: You tried 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.
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 customer support.
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.
Cause: The privileges needed to do an import do not exist. A minimum of CONNECT privilege is required to do an import.
Action: Ask the database administrator to grant the necessary privileges.
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.
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.
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.
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.
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.
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 up to 66,000 or greater (for example). Use this step-by-step approach because a buffer size that is too large may cause a similar problem.
Cause: An operating system error has occurred.
Action: Look up the referenced message in your operating system-specific Oracle documentation and take appropriate action.
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
Cause: The necessary Import views were not installed.
Action: Ask your database administrator to install the required Import views.
Cause: Parameters were specified that conflict with the import specification FULL=Y.
Action: Retry, making sure not to specify FULL=Y.
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.
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.
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.
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,SCOTT.DEPT)
Action: Use the FROMUSER parameter to specify the table's owner, as shown in the following example:
IMP SYSTEM/MANAGER FROM USER=SCOTT TABLES=(EMP,DEPT)
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.
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.
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.
Cause: A table name was specified that does not exist in export file.
Action: Correct the table specification.
Cause: The user specified a FROMUSER name that does not exist in export file.
Action: Correct the FROMUSER specification.
Cause: The user specified a TOUSER name that does not exist in export file.
Action: Correct the TOUSER specification.
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.
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 Worldwide Support.
Cause: This is an internal error.
Action: Contact Oracle Worldwide Support.
Cause: The string is corrupted.
Action: Try to obtain an uncorrupted version 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.
Action: This is a warning. The object may have to be recompiled before being used.
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.
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.
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.
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.
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 Worldwide Support as an Import/Export internal bug and submit the export file.
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.
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.
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.
Cause: A partition name was specified that does not exist in export file.
Action: Check to make sure the partition name belongs to the table.
Cause: The specified table is not a partitioned table.
Action: Retry the operation using a partitioned 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.
Cause: Parameter manager failed in initialization.
Action: Report this to Oracle Worldwide Support as an Import internal bug.
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.
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.
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.
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.
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.
Cause: An error occurred recreating a LOB within an imported object.
Action: Report this to Oracle Worldwide Support as an Import internal error.
Cause: No value for NLS_CHARACTERSET in props$.
Action: Report this to Oracle Worldwide Support as an Import internal error.
Cause: This is an internal error.
Action: Report this to Oracle Worldwide Support as an Import internal error.
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.
Cause: This is an internal error.
Action: Report this to Oracle Worldwide Support as an Import 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.
Action: Modify the table being imported so that it matches the attribute layout of the table that was exported.
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.
Action: Drop the offending object table prior to import.
Cause: The character string representing the table's object identifier could not be converted to an internal object identifier.
Action: Report this to Oracle Worldwide Support as an Import internal error.
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 filenames to match the truncated names in the specified FILE column or attribute.
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.
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.
Cause: No value for NLS_NCHAR_CHARACTERSET in props$.
Action: Contact Worldwide support.
Action: Contact Worldwide support.
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 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.
Action: After import completes, rename the directory aliases and external filenames to match the real names used for the target database.
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.
Action: Examine the national character data. If incorrect, update the data with correct data.
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.
