Is it possible to have different index definition on target table vis-à-vis source table? (150353)

Is it possible to have different index definition on target table vis-à-vis source table?

Is it possible to have different index definition on target table vis-à-vis source table?

Index definition on target differs from source due to application requirement.

Customers sometimes want to have a different index definition on target than that on the source. This is due to the nature of queries they run on target for reporting purposes. The way indexes are defined (e.g.  composite), it can have a bearing on the query performance.  As far as Shareplex is concerned, it does not matter if the target table has indexes which are different than that on the source table. Shareplex simply submits the SQL to the target database and the target database will use the index as appropriate. 

For details on how Oracle Optimizer uses index, please refer to Oracle documentation.