Oracle 导出错误 EXP-00000~EXP-00107
- 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=number, buffer size=number actual size=number
-
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-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-00025: dictionary shows no column for constraint string.number
-
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-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-00039: export file string must be on a disk
-
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.
- EXP-00044: must be connected 'AS SYSDBA' to do Point-in-time Recovery or Transportable Tablespace import
-
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.
- EXP-00053: unable to execute QUERY on table string 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-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-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 string
-
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 string
-
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-00076: multiple devices specified for tape output
-
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: Reenter the EXPORT command, but specify only one tape device in the FILE parameter.
- EXP-00077: multiple output files specified for unbounded export file
-
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.
- EXP-00078: Error exporting metadata for index string. Index creation will be skipped
-
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 Worldwide Support.
- EXP-00079: Data in table "string" is protected. Conventional path may only be exporting partial table.
-
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 recreate 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.
- EXP-00080: Data in table "string" is protected. Using conventional mode.
-
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.
- EXP-00081: Exporting access control for table/view "string" as non-DBA.
-
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 recreate 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.
- EXP-00083: The previous problem occurred when calling string.string.string
-
Cause: The listed package provides export/import support for procedural
-
Action: Contact Oracle Worldwide Support. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Support determine the correct owner of the problem.
- EXP-00085: The previous problem occurred when calling string.string.string for object number
-
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 Worldwide Support. Most packages are supplied by Oracle internal cartridge or server development groups. The package name will help Support determine the correct owner of the problem.
- EXP-00090: cannot pin type "string"."string"
-
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.
- EXP-00091: Exporting questionable statistics.
-
Cause: Export was able export statistics, but the statistics may not be usuable. 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, 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.
- EXP-00098: Data in table has not been upgraded, table will not be exported
-
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.
- EXP-00107: Feature (string) of column string in table string.string is not supported. The table will not be exported.
-
Cause: Export does not contain the required support for this feature. The table will not be exported.
-
Action: Use the Data Pump version of Export to export this table.https://web.njit.edu/info/limpid/DOC/server.102/b14219/expus.htm
坚持就是胜利、欧耶~
