Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 00000-00199: Export Messages

##### EXP-00000: export terminated unsuccessfully

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.

##### EXP-00001: data field truncation - column length=num, buffer size=num fetched=num

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.)

##### EXP-00002: error in writing to export file

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.

##### EXP-00003: no storage definition found for segment (name, num)

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.

##### EXP-00004: invalid username or password

Cause: An invalid username or password was specified.

Action: Retry with a valid username and password.

##### EXP-00004: invalid username or password

Cause: An invalid username or password was specified.

Action: Retry with a valid username and password.

##### EXP-00005: all allowable logon attempts failed

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.

##### EXP-00006: internal inconsistency error

Cause: Export's data structure was corrupted.

Action: Record the accompanying messages and report this as an Export internal error to customer support.

##### EXP-00007: dictionary shows no columns for name.name

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.

##### EXP-00008: Oracle error num encountered

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.

##### EXP-00009: no privilege to export name's table name

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.

##### EXP-00010: name is not a valid username

Cause: An invalid username was specified.

Action: Shut down the utility, then restart and retry with a valid username.

##### EXP-00011: name.name does not exist

Cause: Export could not find the specified table.

Action: Retry with the correct table name.

##### EXP-00012: num is not a valid export mode

Cause: An invalid export mode was specified.

Action: Retry with a valid export mode.

##### EXP-00013: respond with either "Y", "N", RETURN or "." to quit

Cause: An invalid response was entered.

Action: Enter any of the responses shown in the message.

##### EXP-00014: error on row num of table name

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.

##### EXP-00015: error on row num of table name, column name, datatype num

Cause: Export encountered an error while fetching or writing the column. An accompanying message gives more information.

Action: Correct the error and try again.

##### EXP-00016: Oracle error encountered while reading default auditing options

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.

##### EXP-00018: datatype (num) for column name, table name.name is not supported

Cause: Export does not support the referenced datatype.

Action: Retry with an acceptable datatype (CHAR, NUMBER, DATE, LONG, or RAW).

##### EXP-00019: failed to process parameters, type "EXP 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.

##### EXP-00020: failed to allocate memory of size num

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.

##### EXP-00021: can only perform incremental export in Full Database mode

Cause: USER or TABLE mode was specified when doing an incremental export.

Action: Specify FULL database mode (FULL=Y) and retry.

##### EXP-00022: must be SYS or SYSTEM to do incremental export

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.

##### EXP-00023: must be a DBA to do Full Database 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.

##### EXP-00024: export views not installed, please notify your DBA

Cause: The necessary Export views were not installed.

Action: Ask the database administrator to install the required Export views.

##### EXP-00025: dictionary shows no column for constraint name.num

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.

##### EXP-00026: only one parameter (TABLES, OWNER, or FULL) can be specified

Cause: Conflicting export modes were specified.

Action: Specify only one parameter and retry.

##### EXP-00027: failed to calculate Oracle block size

Cause: Export failed to calculate the Oracle block size.

Action: Report this as an Export internal error to customer support.

##### EXP-00028: failed to open name for write

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.

##### EXP-00029: incremental export mode and consistent mode are not compatible

Cause: Both consistent and incremental exports were specified.

Action: None. Consistent mode is turned off.

##### EXP-00030: unexpected End-Of-File encountered while reading input

Cause: Encountered an End-Of-File while reading the user input.

Action: If input to export is being redirected, check the file for errors.

##### EXP-00031: arraysize not in valid range. Using arraysize=num

Cause: The arraysize value specified is not in the valid range.

Action: No action required.

##### EXP-00032: non-DBAs may not export other users

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.

##### EXP-00033: could not find environment character set

Cause: The environment character set is missing or incorrectly specified.

Action: Ensure that the environment character set is correctly specified and is present.

##### EXP-00034: error on rowid: file# num block# num slot# num

Cause: Identifies the rowid on which an error occurred.

Action: This is an information message. No action is required.

##### EXP-00035: QUERY parameter valid only for table mode exports

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.

##### EXP-00036: object name non-existent in dictionary

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.

##### EXP-00037: export views not compatible with database version

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.

##### EXP-00038: bad Hash cluster id in CLU$

Cause: The function id in clu$ is not a legal number. CLU$ has become corrupted.

Action: Contact Oracle Worldwide Support.

##### EXP-00040: dump file and log file must be different

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.

##### EXP-00041: export done in server's name, different from user's name character set name

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.

##### EXP-00042: missing NLS_CHARACTERSET/NLS_NCHAR_CHARACTERSET in PROPS$

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.

##### EXP-00043: invalid data dictionary information in the row where column name is name in table name

Cause: The export utility retrieved invalid data from the data dictionary.

Action: Contact Oracle Worldwide Support.

##### EXP-00044: must be a DBA to do Tablespace Point-in-time Recovery export

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.

##### EXP-00045: cannot export SYSTEM Tablespace for Point-in-time Recovery

Cause: SYSTEM tablespace cannot be part of recovery set.

Action: Contact Oracle Worldwide Support.

##### EXP-00046: tablespace named name does not exist

Cause: The specified tablespace does not exist in dictionary.

Action: Contact Oracle Worldwide Support.

##### EXP-00047: missing tablespace name(s) in Point-in-time Recovery set

Cause: Tablespace name(s) were not supplied for Point-in-time Recovery.

Action: Enter tablespace name(s) with Point-in-time Recovery option set.

##### EXP-00048: tablespace point-in-time Recover option not 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.

##### EXP-00049: name option is not compatible with Point-in-time Recovery Export

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.

##### EXP-00050: cannot perform Partition Export name on non-partitioned table name

Cause: The table specified in this Partition Export is not a partitioned table.

Action: Use Table mode, or specify a non-partitioned table.

##### EXP-00051: name - given partition name is not part of name table

Cause: The specified partition name is not in the specified table.

Action: Check if the correct table or partition name was specified.

##### EXP-00052: error on row num of partition name

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.

##### EXP-00053: unable to execute QUERY on table name because the table has inner nested tables

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.

##### EXP-00054: no storage definition found for partitioned object (name)

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.

##### EXP-00055: name.name is marked not exportable

Cause: An object was marked as non-exportable in the NOEXP$ table.

Action: Consult your database administrator.

##### EXP-00057: failure to initialize parameter manager

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.

##### EXP-00058: password Verify Function for name profile does not exist

Cause: Cannot find the function for the profile.

Action: Check if the profile was created properly.

##### EXP-00059: error converting an object type's identifier to characters

Cause: An invalid length of an object type identifier prevented its conversion.

Action: Contact Oracle Worldwide Support.

##### EXP-00060: an object type had multiple TYPE BODYs

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.

##### EXP-00061: unable to find the outer table name of a nested table

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.

##### EXP-00062: invalid source statements for an object type

Cause: TYPE was not found in the statements in SOURCE$ for an Object Type.

Action: Contact Oracle Worldwide Support.

##### EXP-00063: error in changing language handle

Cause: Unable to change language handle.

Action: Contact Oracle Worldwide Support.

##### EXP-00064: name is an inner nested table and cannot be exported.

Cause: An attempt was made to export an inner nested table without its parent table.

Action: Export the parent of the inner nested table.

##### EXP-00065: error writing LOB to the dump file.

Cause: The current LOB could not be written to the dump file.

Action: Identify the cause of the write failure and fix it.

##### EXP-00066: object table name is missing its object identifier index

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.

##### EXP-00067: direct path can not export name which contains object or lob data.

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.

##### EXP-00068: view has too many dependent views

Cause: An attempt was made to export a view with more than 200 dependent views.

Action: Contact Oracle Worldwide Support.

##### EXP-00070: attempt to free unallocated memory

Cause: An attempt was made to free memory that was not allocated.

Action: Contact Oracle Worldwide Support.

##### EXP-00071: QUERY parameter not compatible with Direct Path export

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.

##### EXP-00072: error closing export file name

Cause: An error occurred while trying to close the export file.

Action: Contact Oracle Worldwide Support.

##### EXP-00073: dump file size too small

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.

##### EXP-00074: rounding VOLSIZE down, new value is num

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.

##### EXP-00075: rounding FILESIZE down, new value is num

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.

##### EXP-00258: continuing export into file name

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index