DIH ORA-01407: cannot update ("FSI_JOINS"."LEFT_SDE_ID") to NULL Error Running ADI Refresh Post Model Upload
(Doc ID 2827246.1)
Last updated on MAY 17, 2023
Applies to:
Oracle Financial Services Data Integration Hub - Version 8.0.7 and laterInformation in this document applies to any platform.
Oracle Financial Services Data Integration Hub (DIH)
Symptoms
On DIH 8.0.7.3, after adding a custom table within Erwin and loading the Data Model, while running the ADI Refresh, the following error appears in the log file:
ERROR
17-11-21 22:45:16.702][ERROR] [ADIRefresh][trigger]Error occured while updating connector tables:
java.lang.Exception: Error occured while updating connector tables:
at com.ofss.fsgbu.dihref.util.UpdateADIData.updateContTables(UpdateADIData.java:92) ~[dih-adiref.jar:8.0.7.3.0_10178217946290]
at com.ofss.fsgbu.dihref.impl.ADIRefresh.trigger(ADIRefresh.java:145) [dih-adiref.jar:8.0.7.3.0_10178217946290]
at com.ofs.reveleus.DIH.rest.service.Refresh$2.run(Refresh.java:86) [dih.jar:8.0.7.3.0_10178217946290]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_241]
Caused by: java.lang.Exception: Error occured while updating joins:
at com.ofss.fsgbu.dihref.util.UpdateADIDataUtils.updateJoins(UpdateADIDataUtils.java:171) ~[dih-adiref.jar:8.0.7.3.0_10178217946290]
at com.ofss.fsgbu.dihref.util.UpdateADIData.updateContTables(UpdateADIData.java:65) ~[dih-adiref.jar:8.0.7.3.0_10178217946290]
... 3 more
Caused by: java.lang.Exception: Error occured while executing batch
at com.ofss.fsgbu.dihcore.utils.QueryRunnerUtils.executeBatchUpdate(QueryRunnerUtils.java:139) ~[dih-core.jar:8.0.7.3.0_10178217946290]
at com.ofss.fsgbu.dihref.util.UpdateADIDataUtils.updateJoins(UpdateADIDataUtils.java:169) ~[dih-adiref.jar:8.0.7.3.0_10178217946290]
at com.ofss.fsgbu.dihref.util.UpdateADIData.updateContTables(UpdateADIData.java:65) ~[dih-adiref.jar:8.0.7.3.0_10178217946290]
... 3 more
Caused by: java.sql.BatchUpdateException: ORA-01407: cannot update (""."FSI_JOINS"."LEFT_SDE_ID") to NULL
The issue can be reproduced at will with the following steps:
1. Create a new custom table in Erwin data model
2. Load the new Data Model
3. Run Datamodel Validation ==> successful, no error
4. Run ADI refresh
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |