Table Classification Fails with 'No Valid Unique Index Found' When Unique Indexes Exist (Doc ID 1459734.1)

Last updated on MAY 25, 2012

Applies to:

Oracle Financial Services Analytical Applications Infrastructure - Version 7.2 and later
Information 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:

  1. Go to Operations > Batch Maintenance
  2. Create a Batch
  3. Create a Task in the Batch with Component Type = TRANSFORM DATA and rule = Batch_Table_Class_Req
  4. Run the batch

"No valid unique index found" errors are listed in FSI_MESSAGE_LOG for the instrument tables.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms