IDS Forum

Re: 154 error

Posted By: Art Kagel
Date: Tuesday, 20 January 2009, at 3:17 p.m.

In Response To: 154 error (Guo, Denny)

Attachments don' t flow through the forum interface, we don't see them.

ISAM error -154, lock timeout, happens when a task that is running a server
session with SET LOCK MODE TO WAIT <n-seconds>; encounters a lock that
persists for more than n seconds. It has nothing to do with the ONCONFIG
settings (OK very little). Likely some other process which is badly behaved
was hung or paused while holding a lock, or was engaged in a massive
transaction holding many locks for a long period of time before committing.
The fact that today you are not getting the error indicates that the timing
of other applications is such that they are not interferring with the
transaction load.

Art

On Tue, Jan 20, 2009 at 1:00 PM, Guo, Denny <DGuo@livingstonintl.com> wrote:

> Hi All,
>
> I just upgrade our IDS from Ver731 to Ver115UC3 on aix V5.3tl8 few days ago
> on
> our development server.
> I start to process our daily transaction files. And at one point get 154
> error
> which is lock time out expired.
> Not quite sure what it really means. I try to process another sets of
> transaction files today and produces no error.
> Could it related to new configuration file? I attach our original v731
> configuration file and new V115 configuration file.
> Hope somebody could point me to right direction.
>
> Thanks,
> Denny
>
> *******************************************
>
> The information contained in this e-mail message may
> contain privileged and confidential information.
> If you are not the intended recipient, you are
> hereby notified that any review, dissemination,
> distribution or duplication of this communication
> is strictly prohibited. If you have received this
> message in error, please notify the sender by return
> e-mail, delete this message and destroy any copies.
> Internet e- mail is not guaranteed to be secure or
> error-free. Messages could be intercepted, corrupted,
> lost, arrive late or contain viruses.
> The sender will not be liable for
> these risks.
>
> *******************************************
> Ce message électronique pourrait contenir des informations
> privilégiées et confidentielles. Si vous n'en êtes pas le
> récipiendaire prévu, nous vous signalons qu'il est strictement
> interdit d'examiner, de diffuser, de distribuer et de reproduire le
> présent message. Si vous l'avez reçu par erreur, veuillez prévenir
> l'expéditeur par courriel, puis effacer ce message et en détruire
> toute copie. Le courrier électronique n'est pas garanti sécuritaire
> ni exempt d'erreurs. Les messages pourraient être interceptés,
> corrompus, égarés, retardés ou contaminés par des virus.
> L'expéditeur n'est pas responsable de ces risques.
>
>
>
> *******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>

--
Art S. Kagel
Oninit (www.oninit.com)
IIUG Board of Directors (art@iiug.org)

Disclaimer: Please keep in mind that my own opinions are my own opinions and
do not reflect on my employer, Oninit, the IIUG, nor any other organization
with which I am associated either explicitly or implicitly. Neither do
those opinions reflect those of other individuals affiliated with any entity
with which I am affiliated nor those of the entities themselves.

Messages In This Thread

• 154 error
  Guo, Denny -- Tuesday, 20 January 2009, at 1:00 p.m.
  • Re: 154 error
    Art Kagel -- Tuesday, 20 January 2009, at 3:17 p.m.
    • RE: 154 error
      Guo, Denny -- Tuesday, 20 January 2009, at 3:28 p.m.
      • Re: 154 error
        Art Kagel -- Tuesday, 20 January 2009, at 3:45 p.m.
        • RE: 154 error
          Guo, Denny -- Tuesday, 20 January 2009, at 3:56 p.m.
          • Re: 154 error
            Art Kagel -- Tuesday, 20 January 2009, at 10:42 p.m.

IDS Forum is maintained by Administrator with WebBBS 5.12.