onchecks error - sqispnlock()

Hi All, HP-UX 11/IDS 9.40.FC4 Couple of days ago, nightly onchecks reported below errors on 5 tables: -------------------------------------------------------------------------------- ---------------------- Validating indexes for whics:informix.tw041... oncheck failure: sqispnlock() ISAM error: the file is locked.TBLspace data check for whics:informix.tw041 ERROR: Could not obtain lock for whics:informix.tw041 Validating indexes for whics:informix.tw201... oncheck failure: sqispnlock() ISAM error: the file is locked.ERROR: Could not obtain lock for whics:informix.tw201. Validating indexes for whics:informix.tw290... oncheck failure: sqispnlock() ISAM error: the file is locked.ERROR: Could not obtain lock for whics:informix.tw290. Validating indexes for whics:informix.tw301... oncheck failure: sqispnlock() ISAM error: the file is locked.ERROR: Could not obtain lock for whics:informix.tw301. Validating indexes for whics:informix.tw304... oncheck failure: sqispnlock() ISAM error: the file is locked.ERROR: Could not obtain lock for whics:informix.tw304. ---------------------------------------------------------------------- Can someone please shed some light on sqispnlock() function with onchecks? I tried to google but no luck? TIA --------------------------------- Get the name you always wanted with the new y7mail email address.

Oncheck wants an exclusive lock on each table as it checks it. You have apps running against these five tables at the time that the onchecks were run. Nightly onchecks are really not necessary in my book. Run them weekly or monthly during downtime. I've never seen oncheck reveal any data or structure problems that I wasn't already aware of and knew I either had to fix or knew there were likley problems that required an oncheck (such as after a disk controller failure). Art S. Kagel Oninit On Tue, May 13, 2008 at 6:45 AM, H.G <hariog@yahoo.com> wrote: > Hi All, > > HP-UX 11/IDS 9.40.FC4 > > Couple of days ago, nightly onchecks reported below errors on 5 tables: > > > -------------------------------------------------------------------------------- ---------------------- > Validating indexes for whics:informix.tw041... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> TBLspace data check for whics:informix.tw041 > ERROR: Could not obtain lock for whics:informix.tw041 > > Validating indexes for whics:informix.tw201... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> ERROR: Could not obtain lock for whics:informix.tw201. > > Validating indexes for whics:informix.tw290... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> ERROR: Could not obtain lock for whics:informix.tw290. > > Validating indexes for whics:informix.tw301... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> ERROR: Could not obtain lock for whics:informix.tw301. > > Validating indexes for whics:informix.tw304... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> ERROR: Could not obtain lock for whics:informix.tw304. > ---------------------------------------------------------------------- > Can someone please shed some light on sqispnlock() function with onchecks? > I > tried to google but no luck? > > TIA > > --------------------------------- > Get the name you always wanted with the new y7mail email address. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >

As always, thank you very much for prompt response and generous support to this forum. Yes, your book is correct for running onchecks weekly/monthly as we also run onchecks weekly. Apologies for incorrect info. on nightly onchecks in earlier post. Just to clarify on your comments that you have never seen any error revealed by onchecks on data/structure, is due to the fact that onchecks also perform repair for any inconsistancy (depending upon onchecks option)? If yes, does this repair info. goes to onchecks output? TIA Art Kagel <art.kagel@gmail.com> wrote: Oncheck wants an exclusive lock on each table as it checks it. You have apps running against these five tables at the time that the onchecks were run. Nightly onchecks are really not necessary in my book. Run them weekly or monthly during downtime. I've never seen oncheck reveal any data or structure problems that I wasn't already aware of and knew I either had to fix or knew there were likley problems that required an oncheck (such as after a disk controller failure). Art S. Kagel Oninit On Tue, May 13, 2008 at 6:45 AM, H.G wrote: > Hi All, > > HP-UX 11/IDS 9.40.FC4 > > Couple of days ago, nightly onchecks reported below errors on 5 tables: > > > -------------------------------------------------------------------------------- ---------------------- > Validating indexes for whics:informix.tw041... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> TBLspace data check for whics:informix.tw041 > ERROR: Could not obtain lock for whics:informix.tw041 > > Validating indexes for whics:informix.tw201... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> ERROR: Could not obtain lock for whics:informix.tw201. > > Validating indexes for whics:informix.tw290... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> ERROR: Could not obtain lock for whics:informix.tw290. > > Validating indexes for whics:informix.tw301... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> ERROR: Could not obtain lock for whics:informix.tw301. > > Validating indexes for whics:informix.tw304... > oncheck failure: sqispnlock() > ISAM error: the file is locked.> ERROR: Could not obtain lock for whics:informix.tw304. > ---------------------------------------------------------------------- > Can someone please shed some light on sqispnlock() function with onchecks? > I > tried to google but no luck? > > TIA > > --------------------------------- > Get the name you always wanted with the new y7mail email address. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum. --------------------------------- Get the name you always wanted with the new y7mail email address.

Onchecks only repair after prompting you, but even if you run it with -y (which I never do for a -cI run since oncheck doesn't build indexes in parallel so it is MUCH slower than dropping and rebuilding by hand. OK, I meant that the only time oncheck has identified a problem and possibly fixed it is when I ran it knowing from other sources that there was a problem. It's not that oncheck doesn't work, but rather that IDS as a whole is so reliable that only outside influences are likely to corrupt it, so I find the periodic onchecks redundant and mostly unnecessary. Art S. Kagel Oninit On Tue, May 13, 2008 at 3:59 PM, H.G <hariog@yahoo.com> wrote: > As always, thank you very much for prompt response and generous support to > this forum. Yes, your book is correct for running onchecks weekly/monthly > as > we also run onchecks weekly. Apologies for incorrect info. on nightly > onchecks > in earlier post. > > Just to clarify on your comments that you have never seen any error > revealed > by onchecks on data/structure, is due to the fact that onchecks also > perform > repair for any inconsistancy (depending upon onchecks option)? If yes, > does > this repair info. goes to onchecks output? > > TIA > > Art Kagel <art.kagel@gmail.com> wrote: > Oncheck wants an exclusive lock on each table as it checks it. You have > apps running against these five tables at the time that the onchecks were > run. Nightly onchecks are really not necessary in my book. Run them weekly > or monthly during downtime. I've never seen oncheck reveal any data or > structure problems that I wasn't already aware of and knew I either had to > fix or knew there were likley problems that required an oncheck (such as > after a disk controller failure). > > Art S. Kagel > Oninit > > On Tue, May 13, 2008 at 6:45 AM, H.G wrote: > > > Hi All, > > > > HP-UX 11/IDS 9.40.FC4 > > > > Couple of days ago, nightly onchecks reported below errors on 5 tables: > > > > > > > > > -------------------------------------------------------------------------------- ---------------------- > > Validating indexes for whics:informix.tw041... > > oncheck failure: sqispnlock() > > ISAM error: the file is locked.> > TBLspace data check for whics:informix.tw041 > > ERROR: Could not obtain lock for whics:informix.tw041 > > > > Validating indexes for whics:informix.tw201... > > oncheck failure: sqispnlock() > > ISAM error: the file is locked.> > ERROR: Could not obtain lock for whics:informix.tw201. > > > > Validating indexes for whics:informix.tw290... > > oncheck failure: sqispnlock() > > ISAM error: the file is locked.> > ERROR: Could not obtain lock for whics:informix.tw290. > > > > Validating indexes for whics:informix.tw301... > > oncheck failure: sqispnlock() > > ISAM error: the file is locked.> > ERROR: Could not obtain lock for whics:informix.tw301. > > > > Validating indexes for whics:informix.tw304... > > oncheck failure: sqispnlock() > > ISAM error: the file is locked.> > ERROR: Could not obtain lock for whics:informix.tw304. > > ---------------------------------------------------------------------- > > Can someone please shed some light on sqispnlock() function with > onchecks? > > I > > tried to google but no luck? > > > > TIA > > > > --------------------------------- > > Get the name you always wanted with the new y7mail email address. > > > > > > > > > > > ******************************************************************************* > > Forum Note: Use "Reply" to post a response in the discussion forum. > > > > > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --------------------------------- > Get the name you always wanted with the new y7mail email address. > > > > ******************************************************************************* > Forum Note: Use "Reply" to post a response in the discussion forum. > >