IMPDP-ORA-39083&2298.pdf - 墨天轮文档

IMPDP-ORA-39083&2298.pdf

chencheng

245

2页

1次

2022-10-10

免费下载

2022/3/7 下午1:58

文档显示

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=lpyn02rvf_4

1/2

ORA-39083 And ORA-2298 Encountered During DataPump Import (文档 ID 462645.1)

In this Document

Symptoms

Changes

Cause

Solution

References

APPLIES TO:

Oracle Database Exadata Cloud Machine - Version N/A and later

Oracle Cloud Infrastructure - Database Service - Version N/A and later

Oracle Database Cloud Exadata Service - Version N/A and later

Oracle Database Exadata Express Cloud Service - Version N/A and later

Oracle Database Cloud Schema Service - Version N/A and later

Information in this document applies to any platform.

SYMPTOMS

DataPump export completed without any errors/warnings but the following error in encountered in the import

log:

ORA-39083: Object type REF_CONSTRAINT failed to create with error:

ORA-02298: cannot validate (<SCHEMA_NAME>.<FK_CONSTRAINT_NAME>) - parent keys not found

CHANGES

CAUSE

From the error encountered, it appears that the export dump is inconsistent. DataPump export is not consistent

in time, even though the consistency is maintained at table level.

Furthermore, this is an expected error if there are orphaned child records.

An orphaned child record is a record in the table with a foreign key constraint for which no corresponding

primary key value exists.

The following query can be used to identify the orphaned child record:

select <FK_column_name> from <child_table>

minus

select <PK_column_name> from <parent_table>;

SOLUTION

Similar to the parameter "CONSISTENT" associated with the traditional export utility, we have the parameters

FLASHBACK_SCN and FLASHBACK_TIME with the datapump export utility in order to achieve a consistent export

dump. These parameters do not have a default value. This means that if the parameters are not specified

explicitly, that the Export DataPump job will not be consistent in time. There still is a consistency on table level

though.

2022/3/7 下午1:58

文档显示

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=lpyn02rvf_4

2/2

FLASHBACK_SCN

Specifies the system change number (SCN) that Export will use to enable the Flashback utility. The export

operation is performed with data that is consistent as of this SCN. If the NETWORK_LINK parameter is specified,

the SCN refers to the SCN of the source database.

FLASHBACK_TIME

The SCN that most closely matches the specified time is found, and this SCN is used to enable the Flashback

utility. The export operation is performed with data that is consistent as of this SCN.

If there are orphaned child records, work with application team to decide whether those extra records to be

inserted to parent table or to be deleted from child table.

To make a consistency backup: Either close the application or use FLASHBACK_SCN/FLASHBACK_TIME during the

expdp period .

Note:

With 11.2, you can also use the Legacy Mode Parameter CONSISTENT which is internally translated to

FLASHBACK_TIME

Please refer to http://docs.oracle.com/cd/E11882_01/server.112/e22490/dp_legacy.htm#SUTIL961

REFERENCES

BUG:4477014 - ORA-39083 AND ORA-2298 DURING DATAPUMP IMPORT

NOTE:377218.1 - Expdp Message "FLASHBACK automatically enabled" Does Not Guarantee Export Consistency

未找到您要查找的产品?

of 2

免费下载

ora

相关文档

评论