Table Classification Fails with 'No Valid Unique Index Found' When Unique Indexes Exist
(Doc ID 1459734.1)
Last updated on DECEMBER 03, 2019
Applies to:
Oracle Financial Services Analytical Applications Infrastructure - Version 7.2 and laterInformation in this document applies to any platform.
Oracle Financial Services Analytical Applications (OFSAA)
Symptoms
In Oracle Financial Services Analytical Applications (OFSAA), when you run the Batch_Table_Class_Req program to classify instrument tables, you get the following errors in FSI_MESSAGE_LOG even though all of the tables have unique indexes with the columns IDENTITY_CODE and ID_NUMBER:
Table FSI_D_BORROWINGS Failed. Validate Instrument.No valid unique index found
Table FSI_D_BORROWINGS Failed (210)
Table FSI_D_BORROWINGS Failed. Validate Instrument.No valid unique index found
Table FSI_D_BORROWINGS Failed (370)
If you check USER_INDEXES and USER_IND_COLUMNS, these tables do have a unique index that contains IDENTITY_CODE and ID_NUMBER.
The errors prevent you from classifying the tables to make them available is certain Financial Services Applications.
Steps to Reproduce:
- Go to Operations > Batch Maintenance
- Create a Batch
- Create a Task in the Batch with Component Type = TRANSFORM DATA and rule = Batch_Table_Class_Req
- Run the batch
"No valid unique index found" errors are listed in FSI_MESSAGE_LOG for the instrument tables.
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 |