Replicating An Index to the Secondary Server

If an index on an HDR secondary database server becomes corrupt, the normal process for correcting the problem is to drop the index on the primary database server and then rebuild it. This process requires a lock on the table and can take a considerable amount of time to complete. However, instead you can replicate the index from the primary database server to the secondary database server without rebuilding the index on the primary database server.

To manually start index replication, use the onmode -d command.

To set up automatic index replication if an index on the secondary database server is detected as corrupt, set the DRIDXAUTO configuration parameter. Use the onmode -d idxauto command to update the value of the DRIDXAUTO configuration parameter for the session.