VERIFIED SOLUTION i
X

CONFIRM - “ORA-02291 - Integrity constraint" and "Parent Key not found” when trying to resequence the Feature.

Issue

Getting  error “ORA-02291 - Integrity constraint" and "Parent Key not found” when trying to resequence a feature within Confirm V15.00a.

Cause

This is a bug within the Feature Resequencing functionality introduced in V15. Raised as CNB-60027.
This is reproducible in any database where there are Inspection Conditions against the corresponding Inspection Feature.

This is the query which gets run internally for updating corresponding Inspection Condition data:-

UPDATE insp_condition
SET site_code = :as_NewSitecode, 
plot_number = :ac_NewPlotNo 
WHERE insp_condition.site_code     = :as_OldSiteCode AND 
insp_condition.plot_number = :ac_OldPlotNo ;

But the referenced data in insp_condition table cannot be directly modified unless parent table data i.e. inspection_feature one is modified first.
Due to this the integrity constraint error occurs.

Resolution

UPDATED: March 30, 2017


Fixed as a maintenance release V15.00b. No workaround, client must upgrade.

Environment Details

Product Feature: Asset Register
 

Downloads

  • No Downloads