Index monitoring could be initiated and stopped using ALTER INDEX syntax shown below.
ALTER INDEX my_index_i MONITORING USAGE; ALTER INDEX my_index_i NOMONITORING USAGE;
Information about the index usage can be displayed using the V$OBJECT_USAGE view.
SELECT index_name, table_name, monitoring, used, start_monitoring, end_monitoring FROM v$object_usage WHERE index_name = 'MY_INDEX_I' ORDER BY index_name;
The V$OBJECT_USAGE view does not contain an OWNER column so you must to log on as the object owner to see the usage data.
Foreign Key Indexes
To quote the Oracle Database Concepts manual:
“You should almost always index foreign keys. The only exception is when the matching unique or primary key is never updated or deleted.”
When a foreign key is unindexed, DML on the parent primary key results in a share row exclusive table lock (or share-subexclusive table lock, SSX) on the child table, preventing DML from other transactions against the child table. If the DML affects several rows in the parent table, the lock on the child table is obtained and released immediately for each row in turn. Despite the speed of the lock-release process, this can cause significant amounts of contention on the child table during periods of heavy update/delete activity on the parent table.
When a foreign key is indexed, DML on the parent primary key results in a row share table lock (or subshare table lock, SS) on the child table. This type of lock prevents other transactions from issuing whole table locks on the child table, but does not block DML on either the parent or the child table. Only the rows relating to the parent primary key are locked in the child table.