ADI Refresh Failure Post Cloning
(Doc ID 2952355.1)
Last updated on JUNE 05, 2023
Applies to:
Oracle Financial Services Data Integration Hub - Version 8.0.5 to 8.0.5 [Release 8]Information in this document applies to any platform.
Symptoms
On : DIH 8.0.5.1 Version, ADI_OFSS
When attempting to perform ADI refresh, it fails
ERROR
-----------
no error observed in logs.
INFO ~ ADILOGGER ~ [ADILOGGER] [ADIRefresh][refresh]<NOTE>--Infodom name: OFSADOM
INFO ~ ADILOGGER ~ [ADILOGGER] [ADIRefresh][refresh]runid 158
INFO ~ ADILOGGER ~ [ADILOGGER] [ADIRefresh][refresh]<NOTE>--ADI Refresh has been initiated at: 2023/05/09 10:49:27
INFO ~ ADILOGGER ~ [ADILOGGER] [ADIRefresh][refresh]entered to insert the row
INFO ~ ADILOGGER ~ [ADILOGGER] [ADIRefresh][refresh]successful to insert the row
INFO ~ ADILOGGER ~ [ADILOGGER] [ADIRefresh][refresh]<NOTE>--The infodom OFSADOM is currently populated with ADI related data. Initiating check for changes in data.
In DIH.log, we see that ADI completed successfully message:
INFO ~ DIHLOGGER ~ [ADIRefresh][refresh]LOG INSERTED
INFO ~ DIHLOGGER ~ [Refresh$2][run]Refresh ADI completed successfully
INFO ~ DIHLOGGER ~ [RegisterAction][getADIData]infodom OFSADOM.
STEPS
-----------
The issue can be reproduced at will with the following steps:
1. Try to perform ADI refresh after performing Cloning
BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot perform ADI refresh successfully
Changes
Environment Cloning
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 |