When the index name gets attached to the schema name, the index name exceeds the maximum characters allowed and causes issues. This happens while attempting to create cache.

Ex:- 
Oracle mostly allows 30 characters index names.

Let's assume there is a 20 characters index name: "POABCHDFGHJ123456KLG"
and 15 characters schema name: "1QWERT7890BHJFD". And there are 2 DV instances with different settings. Where, in 1 instance it concatenates the Schema name and Index name and in another instance, it does not.

We run the same steps in 2 different TDV instances(maybe different versions) and in one instance we observe this to be working.

But in the second instance schema name combines with the index name and the final index name becomes 35 characters in all: "POABCHDFGHJ123456KLG_1QWERT7890BHJFD".

Now, it will not run in 2nd instance as it is exceeding the 30 characters limit.

You can find out the settings which will help to stop concatenation of Schema name and Index name in Resolution.

All Supported Platforms.

Navigate to: <TDV_Server_Directory>\apps\dlm\cis_ds_oracle\conf\oracle.capabilities

Try changing the value of below capabilities mentioned below:

jdbcds.qualify_index_with_table_schema: True   ->   False                       (Required)
jdbcds.table.name.max_length: 30                                                (Change only if required)

If the above capabilities do not help try this:
jdbcds.schemas_in_tables: true

If the above-mentioned changes work,  you'll need to generate a "values.xml" file with the same information and replace it with the existing "values.xml" file at path <TDV_INSTALL>\conf\adapters\system\ -> choose the datasource required.

This article explains how to resolve the issue when schema name gets attached to index name while creating index.