Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
This chapter lists messages generated by the Import utility. For more information about this utility, refer to Oracle9i Database Utilities.
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 Oracle Support Services.
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 Support Services.
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 Support Services.
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.
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 Support Services.
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 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.
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 (for example). Use this step-by-step approach because a buffer size that is too large may cause a similar problem.
Cause: Import encountered the INCTYPE parameter when parsing Import options. Incremental Imports are no longer supported.
Action: Consult the Oracle9i User-Managed Backup and Recovery Guide. Import will attempt to continue.
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:
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)
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: 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.
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 Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
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.
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.
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: Run the Import command again with a larger value for the buffer option.
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.
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.
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.
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.
Cause: An unknown language was listed in the CHARSET option.
Action: Use a known character set.
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 Support Services 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 must log in 'as SYSDBA' to perform transportable tablespace imports or Point-In-Time Recovery imports.
Action: Ask your database administrator to perform the Transportable Tablespace import or the Tablespace Point-in-time Recovery import.
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.
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.
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 Support Services 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. This is an internal error.
Action: Contact Oracle Support Services.
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 while re-creating a LOB within an imported object.
Action: Report this to Oracle Support Services as an Import internal error.
Cause: No value for NLS_CHARACTERSET in props$.
Action: Contact Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
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: Contact Oracle Support Services.
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.
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.
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 Support Services.
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.
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 Oracle Support Services.
Cause: This is an internal error.
Action: Contact Oracle Support Services.
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.
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.
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.
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Support Services.
Cause: An error occurred while attempting to convert a ROWID from an export dump file into an internal format.
Action: Report this to Oracle Support Services as an Import internal error.
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.
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.
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.
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.
Cause: Most likely a problem with allocating memory for the hash table entries.
Action: Contact Oracle Support Services.
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 Support Services.
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.
Action: Ask the database administrator to perform the export/import of this table/view.
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 Support Services.
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 Support Services so they may determine the development group responsible for the package that failed.
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.
Cause: Import failed to locate a base table for a constraint that was defined in the dump file and statistics were not imported.
Action: Check to see if the table and constraint exist. If the table and constraint exist, then report this to Oracle Support Services as an Import internal error.
Cause: The character string representing the object type's identifier could not be converted.
Action: Contact Oracle Support Services.
Cause: The current session is not resumable.
Action: Must specify RESUMABLE=Y to enable resumable sessions in order for the RESUMABLE_NAME and RESUMABLE_TIMEOUT parameters to take effect.
Cause: An error occurred creating a synonym for a type that is used by the table.
Action: Examine the import log to determine why the type synonym could not be created. If the synonym already existed, but is not needed, then drop the synonym and retry the import. If the synonym is PUBLIC but the importer does not have the CREATE PUBLIC SYNONYM system privilege, then the import must be done by someone possessing that privilege, or the importer must be granted the privilege.
Cause: STREAMS_CONFIGURATION=Y can only be used when FULL=Y is present on the command line.
Action: Remove conflicting command arguments.
Cause: An INTERNAL error has occurred.
Action: Contact Oracle Support Services.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
