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 Export utility. For more information about this utility, refer to Oracle9i Database Utilities.
Cause: Export encountered an Oracle error.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual, and take appropriate action.
Cause: Export could not fit a column in the data buffer.
Action: Record the given size parameters and the accompanying messages and report this as an Export internal error to Oracle Support Services. (Part of the table has been exported. Export will continue with the next table.)
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.
Action: Take appropriate action to restore the device.
Cause: Export could not find the storage definitions for a cluster, index, or table.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
Cause: Attempts were repeatedly made to log on with an invalid username or password.
Action: Shut down the utility, then restart and retry with a valid username and password.
Cause: Export's data structure was corrupted.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
Cause: Export failed to gather column information from the data dictionary. The table may have been dropped.
Action: Retry the export and, if this error recurs, report it as an Export internal error to Oracle Support Services.
Cause: Export 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 attempt was made to export another user's table. Only a database administrator can export another user's tables.
Action: Ask your database administrator to do the export.
Cause: An invalid username was specified.
Action: Shut down the utility, then restart and retry with a valid username.
Cause: Export could not find the specified table.
Action: Retry with the correct table name.
Cause: An invalid export mode was specified.
Action: Retry with a valid export mode.
Cause: An invalid response was entered.
Action: Enter any of the responses shown in the message.
Cause: Export encountered an Oracle error while fetching rows.
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
Cause: Export encountered an error while fetching or writing the column. An accompanying message gives more information.
Action: Correct the error and try again.
Cause: Export encountered an Oracle error while reading the default auditing options (those for updates, deletes, and so on).
Action: Look up the accompanying Oracle message in the ORA message chapters of this manual and take appropriate action.
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.
Action: Re-install Oracle with the feature specified in the message.
Cause: Export does not support the referenced datatype.
Action: Retry with an acceptable datatype (CHAR, NUMBER, DATE, LONG, or RAW).
Cause: Invalid command-line parameters were specified.
Action: Check the online help screen for the set of valid parameters, then retry.
Cause: Export failed to allocate the necessary memory.
Action: Decrease the export buffer size so that less memory is required, or increase the runtime memory size for Export.
Cause: USER or TABLE mode was specified when doing an incremental export.
Action: Specify FULL database mode (FULL=Y) and retry.
Cause: The privileges needed to do an incremental export do not exist. Only a data base administrator can do incremental exports.
Action: Ask the database administrator to do the incremental export.
Cause: The privileges needed to do a FULL database export do not exist. Only a database administrator can do a FULL database export.
Action: Ask the database administrator to do the FULL database export.
Cause: The necessary Export views were not installed.
Action: Ask the database administrator to install the required Export views.
Cause: Export failed to gather column information about the referenced constraint from the data dictionary. The constraint may have been altered.
Action: Retry the export and, if this error recurs, report it as an Export internal error to Oracle Support Services.
Cause: Conflicting export modes were specified.
Action: Specify only one parameter and retry.
Cause: Export failed to calculate the Oracle block size.
Action: Report this as an Export internal error to Oracle Support Services.
Cause: Export failed to open the export file for writing. This message is usually followed by device messages from the operating system.
Action: Take appropriate action to restore the device.
Cause: Both consistent and incremental exports were specified.
Action: No action is required. Consistent mode is turned off.
Cause: Encountered an End-Of-File while reading the user input.
Action: If input to export is being redirected, check the file for errors.
Cause: The array size value specified is not in the valid range.
Action: No action required.
Cause: Only database administrators can export to other users. A non-database administrator attempted to specify OWNER=USER where exporter is not the user.
Action: Request that this operation be performed by the database administrator.
Cause: The environment character set is missing or incorrectly specified.
Action: Ensure that the environment character set is correctly specified and is present.
Cause: Identifies the ROWID on which an error occurred.
Action: This is an information message. No action is required.
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.
Action: If you want to select a subset of rows for a table, you must export the table independently with a table mode export. Issue a table mode export command that specifies the table name and the query you want to execute during export.
Cause: The specified object could not be found in the dictionary. The object might have been dropped during the export
Action: The object no longer exists; no action is needed.
Cause: The Export utility is at a higher version than the database version and is thereby incompatible.
Action: Use the same version of Export utility as the database.
Cause: The function ID in CLU$ is not a legal number. CLU$ has become corrupted.
Action: Contact Oracle Support Services.
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.
Action: Verify that you have specified the correct file name for the export file. Remember that all export files can be either on disk or all files can be on tape, but not mixed both tape and disk.
Cause: The dump file and log file cannot be the same file.
Action: Specify different file names for the dump file and the log file, then retry the operation.
Cause: Export encountered the INCTYPE parameter when parsing Export options. Incremental Exports are no longer supported.
Action: Consult the Oracle9i User-Managed Backup and Recovery Guide. Export will attempt to continue.
Cause: A value for NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET was not entered in the props$ table. This is an internal error.
Action: Contact Oracle Support Services.
Cause: The export utility retrieved invalid data from the data dictionary.
Action: Contact Oracle Support Services.
Cause: The user must log in 'as SYSDBA' to perform transportable tablespace imports or Point-In-Time Recovery imports.
Action: Ask your database adminstrator to perform the Transportable Tablespace import or the Tablespace Point-in-time Recovery import.
Cause: SYSTEM tablespace cannot be part of recovery set or transportable tablespace set.
Action: Contact Oracle Support Services.
Cause: The specified tablespace does not exist in dictionary.
Action: Contact Oracle Support Services.
Cause: Tablespace name(s) were not supplied.
Action: Provide tablespace name(s).
Cause: An option was specified that is incompatible with Point-in-time Recovery or Transportable Tablespace Export.
Action: Retry the export without the displayed option.
Cause: The table specified in this Partition Export is not a partitioned table.
Action: Use Table mode, or specify a non-partitioned table.
Cause: The specified partition or subpartition name is not in the specified table.
Action: Check if the correct table, partition or subpartition name was specified.
Cause: Export encountered the referenced Oracle error while fetching rows.
Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.
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.
Action: Export the entire table by omitting the QUERY parameter.
Cause: Export encountered the referenced Oracle error while fetching rows.
Action: Look up the Oracle message in the ORA message chapters of this manual and take appropriate action.
Cause: An object was marked as non-exportable in the NOEXP$ table.
Action: Consult your database administrator.
Cause: The parameter manager failed in intialization.
Action: Record the messages that follow and report this to Oracle Support Services as an Export internal bug.
Cause: Cannot find the function for the profile.
Action: Check if the profile was created properly.
Cause: An invalid length of an object type identifier prevented its conversion.
Action: Contact Oracle Support Services.
Cause: More than one TYPE BODY was found for an object type.
Action: Try dropping the TYPE BODY, if that is not successful, contact Oracle Support Services.
Cause: While exporting a bitmap index or postable action on an inner nested table, the name of the outer table could not be located, using the NTAB$ table.
Action: Verify the table is properly defined.
Cause: TYPE was not found in the statements in SOURCE$ for an Object Type.
Action: Contact Oracle Support Services.
Cause: Unable to change language handle.
Action: Contact Oracle Support Services.
Cause: An attempt was made to export an inner nested table without its parent table.
Action: Export the parent of the inner nested table.
Cause: The current LOB could not be written to the dump file.
Action: Identify the cause of the write failure and fix it.
Cause: All object tables must have an object identifier index, but the specified table was missing an index on its object identifier column.
Action: Re-create the type table and retry the operation.
Cause: Export failed to export tablespace (tablespace being offline).
Action: Make tablespace online and re-export.
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Support Services.
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.
Action: Re-issue the export command with DIRECT=N or omit the DIRECT parameter from the command line.
Cause: An error occurred while trying to close the export file.
Action: Contact Oracle Support Services.
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.
Action: Increase the value of the FILESIZE or VOLSIZE parameter.
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.
Action: No action is required. You can adjust the VOLSIZE or RECORDLENGTH parameter to avoid this message. When importing this file, you must specify the VOLSIZE value reported by this message.
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.
Action: No action is required. You can adjust the FILESIZE or RECORDLENGTH parameter to avoid this message. When importing this file, you must specify the FILESIZE value reported by this message.
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.
Action: Re-enter the EXPORT command, but specify only one tape device in the FILE parameter.
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.
Action: If you intended to write multiple files, respecify the command but use the FILESIZE to specify the maximum number of bytes that EXPORT should write to each file. If you intended to write only one file with no limits on it's size, reissue the EXPORT command but specify only one file name for the FILE parameter.
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.
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: 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 re-create 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.
Action: Ask the database administrator to export/import this table/view.
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.
Action: Ask the database administrator to export/import this table/view.
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 re-create the access control policies when importing the table/view. And such an event may cause inconsistency in the security model of the table/view.
Action: Ask the database administrator to export/import this table/view.
Cause: Internal inconsistency error: The listed function is not a method on export's procedural object interface specification.
Action: Contact Oracle Support Services.
Cause: The listed package provides export/import support for procedural actions. The previously listed error occurred while calling the specified function.
Action: Contact Oracle Support Services. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Oracle Support Services determine the correct owner of the problem.
Cause: The error was returned from a call to a DbmsJava procedure.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
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.
Action: Contact Oracle Support Services. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Oracle Support Services determine the correct owner of the problem.
Cause: The specified table contains primary key REFs which may not be valid in the import database.
Action: Do not use Export/Import to move Primary key REFs between databases having differing character sets.
Cause: Most likely a problem with allocating memory for the hash table entries.
Action: Contact Oracle Support Services.
Cause: The FILE_FORMAT specification did not contain an instance of "string". This wildcard string must be present.
Action: Correct the error and re-enter the EXPORT command.
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).
Action: Fix the problem with the offending type until the type can be successfully compiled.
Cause: Export was able to export statistics, but the statistics may not be useable. 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.
Action: To export non-questionable statistics, change the client character set or NCHARSET to match the server, export with no query clause, or export complete tables. If desired, import parameters can be supplied so that only non-questionable statistics will be imported, and all questionable statistics will be recalculated.
Cause: Export was unable to set NLS_NUMERIC_CHARACTERS to '.,'.
Action: Record the accompanying messages and report this as an Export internal error to Oracle Support Services.
Cause: Internal error.
Action: Contact Oracle Support Services.
Cause: Internal error.
Action: Contact Oracle Support Services.
Cause: Both flashback_time and flashback_scn parameters were specified.
Action: Reissue the command with only one flashback parameter.
Cause: The specified template name does not exist.
Action: Verify the template name by looking up view %_ias_template.
Cause: The object type's status is invalid which may be caused by a dependant type's modification (or removal) without cascading the change.
Action: The type must be recompiled using ALTER TYPE COMPILE.
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.
Action: The table must be updated using ALTER TABLE UPGRADE DATA.
Cause: A table or one of its dependant types has modified without cascading the change. This left the table in an INVALID state.
Action: The table must be updated using ALTER TABLE UPDATE.
Cause: An invalid length of an object type identifier prevented its conversion.
Action: Contact Oracle Support Services.
Cause: Transportable Tablespace extensible indexes must be at least version 2.
Action: Upgrade the extensible index implementation to version 2 specifications.
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.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
