Index lock issues

My client is having lock contention problems on indexes. I'm working to track down the culprit indexes and provide lasting solutions. Can anyone answer the following: (1) How do you tell from all those 7+ digit rowids in tbstat -k *which* index it refers to? (2) The database makes big use of foreign keys, which generate lots of heavily-duplicate indexes all over the place. I would like to be able to replace the generated indexes on, say, (col1,col2) with one on (col1,col2,col3,col4) to improve their usefulness. However, OnLine generates its own index when you add the constraint unless there's already one with exactly the same (*only*) keys. I can't see a way round this with 5.02. Is there one? Does 6.00 improve things? If it doesn't, does anyone have any views on possibly replacing the foreign keys with trigger language, thereby choosing my own indexes? akent@cix.compulink.co.uk (Andy Kent) ------------------------------------- 44 272 742815