oncheck -cc: ISAM error: record is locked
IDS 10.00.FC6 on RHEL4
We are 24/7 OLTP and we run oncheck at a reasonably slow time.
Sometimes I get this error:
Validating systables for database mn
ISAM error: record is locked.
And this error seems to coincide with this from ontape:
Archive failed - The existing level-0 backup for DBspace rootdbs
is too old to allow any incremental backup.
Most references to the ontape error say that it happens after
adding or dropping a chunk, but there is none of that going on here.
I think bouncing the engine clears this, but that's a lousy
solution. Any way to clear this while remaining online?
--
Jeff
jlar310 at yahoo
Hi,
can you open a case (aka PMR) with IBM Informix Tech Support?
I think this needs further analysis. If it is possible to reproduce
this behaviour, then it is most likely a defect, which should then
be treated accordingly.
I don't "see" the connection between the two things (oncheck and
ontape) in this particular scenario. That's why I think a working
reproduction will be necessary to analyse and really understand
the problem and its cause. Hence Tech Support looks like the
best route ...
TIA,
Martin
--
Martin Fuerderer
IBM Informix Development Munich, Germany
Information Management
IBM Deutschland GmbH
Chairman of the Supervisory Board: Hans Ulrich Märki
Board of Management: Martin Jetter (Chairman), Rudolf Bauer, Christian
Diedrich, Christoph Grandpierre, Matthias Hartmann, Thomas Fell, Michael
Diemer
Corporate Seat: Stuttgart, Germany; Reg.-Gericht: Amtsgericht Stuttgart,
HRB-Nr.: 14 562 WEEE-Reg.-Nr. DE 99369940
Jeff <nobody@localhost.iiug.org>
Sent by: informix-list-bounces@iiug.org
12.07.2007 06:20
To
informix-list@iiug.org
cc
Subject
oncheck -cc: ISAM error: record is locked
IDS 10.00.FC6 on RHEL4
We are 24/7 OLTP and we run oncheck at a reasonably slow time.
Sometimes I get this error:
Validating systables for database mn
ISAM error: record is locked.
And this error seems to coincide with this from ontape:
Archive failed - The existing level-0 backup for DBspace rootdbs
is too old to allow any incremental backup.
Most references to the ontape error say that it happens after
adding or dropping a chunk, but there is none of that going on here.
I think bouncing the engine clears this, but that's a lousy
solution. Any way to clear this while remaining online?
--
Jeff
jlar310 at yahoo
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list