Hi all, I'm using the High/low sequence manager with one of my applications and I noticed that it sometimes decreases the MAX_KEY field without any reason. I'm not an expert of this algorithm but I don't think it's a normal behavior. Here is a sample of the P6SPY log, when the MAX_KEY decreases (the name of the table is UNITE_TEMPS_UTE and the primary key is UTE_ID, the value jumps from 29108 to 28959):
03 mars 2005 - 17:14:54,594 - 1109866494594|1|7|statement|SELECT MAX_KEY,TABLENAME,GRAB_SIZE,VERSION,FIELDNAME FROM OJB_HL_SEQ WHERE TABLENAME = ? AND FIELDNAME = ? |SELECT MAX_KEY,TABLENAME,GRAB_SIZE,VERSION,FIELDNAME FROM OJB_HL_SEQ WHERE TABLENAME = 'SEQ_UNITE_TEMPS_UTE' AND FIELDNAME = 'UTE_ID' 03 mars 2005 - 17:14:54,596 - 1109866494596|1|7|statement|UPDATE OJB_HL_SEQ SET MAX_KEY=?,GRAB_SIZE=?,VERSION=? WHERE TABLENAME = ? AND FIELDNAME = ? AND VERSION = ? |UPDATE OJB_HL_SEQ SET MAX_KEY='29108',GRAB_SIZE='1',VERSION='0' WHERE TABLENAME = 'SEQ_UNITE_TEMPS_UTE' AND FIELDNAME = 'UTE_ID' AND VERSION = '0' 03 mars 2005 - 17:15:02,850 - 1109866502850|1|4|statement|SELECT A0.MAX_KEY,A0.TABLENAME,A0.GRAB_SIZE,A0.VERSION,A0.FIELDNAME FROM OJB_HL_SEQ A0 WHERE (A0.TABLENAME LIKE ? ) AND A0.FIELDNAME LIKE ? |SELECT A0.MAX_KEY,A0.TABLENAME,A0.GRAB_SIZE,A0.VERSION,A0.FIELDNAME FROM OJB_HL_SEQ A0 WHERE (A0.TABLENAME LIKE 'SEQ_UNITE_TEMPS_UTE' ) AND A0.FIELDNAME LIKE 'UTE_ID' 03 mars 2005 - 17:15:02,851 - 1109866502851|-1||resultset|SELECT A0.MAX_KEY,A0.TABLENAME,A0.GRAB_SIZE,A0.VERSION,A0.FIELDNAME FROM OJB_HL_SEQ A0 WHERE (A0.TABLENAME LIKE 'SEQ_UNITE_TEMPS_UTE' ) AND A0.FIELDNAME LIKE 'UTE_ID' |FIELDNAME = UTE_ID, GRAB_SIZE = 1, TABLENAME = SEQ_UNITE_TEMPS_UTE, VERSION = 0 03 mars 2005 - 17:15:02,852 - 1109866502852|1|4|statement|SELECT MAX_KEY,TABLENAME,GRAB_SIZE,VERSION,FIELDNAME FROM OJB_HL_SEQ WHERE TABLENAME = ? AND FIELDNAME = ? |SELECT MAX_KEY,TABLENAME,GRAB_SIZE,VERSION,FIELDNAME FROM OJB_HL_SEQ WHERE TABLENAME = 'SEQ_UNITE_TEMPS_UTE' AND FIELDNAME = 'UTE_ID' 03 mars 2005 - 17:15:02,854 - 1109866502854|1|4|statement|UPDATE OJB_HL_SEQ SET MAX_KEY=?,GRAB_SIZE=?,VERSION=? WHERE TABLENAME = ? AND FIELDNAME = ? AND VERSION = ? |UPDATE OJB_HL_SEQ SET MAX_KEY='28959',GRAB_SIZE='1',VERSION='0' WHERE TABLENAME = 'SEQ_UNITE_TEMPS_UTE' AND FIELDNAME = 'UTE_ID' AND VERSION = '0' That's a really annoying issue as OJB makes UPDATE queries instead of INSERT on the recovery interval and mess up the whole database. I use OJB 1.0 rc4 and OJB is the only application making INSERT on this table. Thanks in advance. Arno --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
