Skip to main content

ORA-39083 and ORA-02298

ORA-39083: Object type REF_CONSTRAINT failed to create with error:
ORA-02298: cannot validate <constraint_name> - parent keys not found
Failing sql is:
ALTER TABLE <detail_table_name> ADD CONSTRAINT <constraint_name> FOREIGN KEY <detail_table_column_name> REFERENCES <master_table_name> <master_table_column_name> ENABLE

This error may be seen when running datapump import. This is because you have master and detail tables that related with a foreign key constraint. Although detail table has some records, master table doesn't have corresponding records. This is about your database's integrity. It is recommended that broken records in the details table should be found and deleted. On the other hand you can enable constraint with the novalidate option. If you want to ignore this integrity problem, you could validate constraint with the following sql:

ALTER TABLE <detail_table_name> ADD CONSTRAINT <constraint_name> FOREIGN KEY <detail_table_column_name> REFERENCES <master_table_name> <master_table_column_name> ENABLE NOVALIDATE

Comments

Popular posts from this blog

Creating Multiple VLANs over Bonding Interfaces with Proper Routing on a Centos Linux Host

In this post, I am going to explain configuring multiple VLANs on a bond interface. First and foremost, I would like to describe the environment and give details of the infrastructure. The server has 4 Ethernet links to a layer 3 switch with names: enp3s0f0, enp3s0f1, enp4s0f0, enp4s0f1 There are two bond interfaces both configured as active-backup bond0, bond1 enp4s0f0 and enp4s0f1 interfaces are bonded as bond0. Bond0 is for making ssh connections and management only so corresponding switch ports are not configured in trunk mode. enp3s0f0 and enp3s0f1 interfaces are bonded as bond1. Bond1 is for data and corresponding switch ports are configured in trunk mode. Bond0 is the default gateway for the server and has IP address 10.1.10.11 Bond1 has three subinterfaces with VLAN 4, 36, 41. IP addresses are 10.1.3.11, 10.1.35.11, 10.1.40.11 respectively. Proper communication with other servers on the network we should use routing tables. There are three

Listing Zimbra Accounts with Some Details

Recently I have to export the user list for a particular domain. Luckily Zimbra has Admin GUI with a search feature. When you search accounts, you can download search results as a comma-separated csv file. So I did a search and download the result file, but the result did not have all the columns I need and also there is no option for customizing columns for search results. So I had to write a bash script to get the desired list. Here is the bash script ( It can be customized by adding or removing field names. Run it under zimbra user like ./zimbra_account_list.sh <domain_name_here> ):