Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
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 customer support. (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 customer support.
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
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 customer support.
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 customer support.
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: 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 users SYS and SYSTEM 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 customer support.
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 customer support.
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: None. 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 arraysize 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 Worldwide Support.
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: The specified NLS_LANG/NLS_NCHAR parameter is incompatible with the value specified for the server in PROPS$.
Action: Change the client's value for NLS_LANG/NLS_NCHAR to server's value and retry the operation.
Cause: A value for NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET was not entered in the PROPS$ table.
Action: This is an internal error. Contact Oracle Worldwide Support.
Cause: The export utility retrieved invalid data from the data dictionary.
Action: Contact Oracle Worldwide Support.
Cause: The user does not have privileges to do Tablespace Point-in-time Recovery export.
Action: Have the database administrator do Tablespace Point-in-time Recovery export for you.
Cause: SYSTEM tablespace cannot be part of recovery set.
Action: Contact Oracle Worldwide Support.
Cause: The specified tablespace does not exist in dictionary.
Action: Contact Oracle Worldwide Support.
Cause: Tablespace name(s) were not supplied for Point-in-time Recovery.
Action: Enter tablespace name(s) with Point-in-time Recovery option set.
Cause: The tablespace option was not used in Point-in-time Recovery.
Action: Use the tablespace option only with the Point-in-time Recovery Option set.
Cause: An option was specified that cannot be used in Point-in-time Recovery Export.
Action: Consult the Oracle Server Utility Guide for the correct list of options.
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 name is not in the specified table.
Action: Check if the correct table or partition 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: Could not find the storage definitions for partitioned table/index.
Action: Record the error messages that follow and report this to Oracle Worldwide Support as an Export internal error.
Cause: An object was marked as non-exportable in the NOEXP$ table.
Action: Consult your database administrator.
Cause: The parameter manager failed in initialization.
Action: Record the messages that follow and report this to Oracle Worldwide Support 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 Worldwide Support.
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 Worldwide Support.
Cause: While exporting a bitmap index or post-able 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 Worldwide Support.
Cause: Unable to change language handle.
Action: Contact Oracle Worldwide Support.
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: Recreate the type table and retry the operation.
Cause: Direct path export cannot export tables that contain LOBs, files, or object datatypes.
Action: Use conventional path export to export tables containing these datatypes.
Cause: An attempt was made to export a view with more than 200 dependent views.
Action: Contact Oracle Worldwide Support.
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Worldwide Support.
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 Worldwide Support.
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.
