EXP-00082: Invalid function name passed to procedural object support: string
Cause: Internal inconsistency error: The listed function is not a method on export’s procedural object interface specification.
Action: Contact Oracle Worldwide Support
Category Archives: EXP Database Error Messages
EXP-00081: Exporting access control for table/view “string” as non-DBA
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-00080: Data in table “string” is protected. Using conventional mode
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-00079: Data in table “string” is protected. Conventional path may only be exporting partial table
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-00078: Error exporting metadata for index string. Index creation will be skipped
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-00077: multiple output files specified for unbounded export file
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-00076: multiple devices specified for tape output
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-00075: rounding FILESIZE down, new value is string
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-00074: rounding VOLSIZE down, new value is string
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-00073: dump file size too small
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.