RE: Detached index rowid under onstat -k

I have figured out the rowid question, 0x186ea is Logical page 100074, slot 3 in partnum 0x500226, the data extent of my detached index. The fact that it was pointing the data partition threw me as I know how to convert rowid. I still don't quite understance the K- 1 relation, as all of my indexes are detached, does it have something to do with indexes within data extents? Thanks again, John -----Original Message----- From: Porcello, John [mailto:jep-corp@kaman.com] Sent: Tuesday, November 02, 1999 1:47 PM To: 'informix-list@iiug.org' Subject: Detached index rowid under onstat -k The following is an example of a exclusive lock on a detached index. My question is the need for an explanation of rowid and key#/bsiz columns. The only information I can dig up is the following: rowid >six digits is an Index key value lock (What does the 0x186ea03 value actually relate to?) Key#/bsiz is Index key number or #bytes of varchar locked. (Does K- 1 relate to the char(3) key value?) Detached index(600329) (char(3),date,char(8),date) Locks address wtlist owner lklist type tblsnum rowid key#/bsiz 200648990 20cdc3ab8 20cdce628 20060b5e0 HDR+X 600329 186ea03 K- 1 TIA, John E. Porcello, Jr., ICP, MCSE Corporate DBA Kaman Corporation jep-corp@kaman.com My views and opinions may not reflect those of Kaman Corporation.