IDS Forum

Re: 154 error

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

In Response To: RE: 154 error (Guo, Denny)

Whoa, big formatting problem there. Denny, There's something going on
there. You simply cannot get a lock timeout if you are not contending for
locks somehow. The one other possibility would be a long checkpoint
blocking the application in a critical section, but checkpoints are
non-blocking in 11.50, so that also should not happen. Does the one
application maintain multiple connections to the server? Is there a SELECT
... FOR UPDATE loop with insert, delete, or updates happening inside the
loop?

Art

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

> Thanks Art,=0D=0A=0D=0ABut there is only one application
> running=2E=0D=0ATh=
> e application runs update on particular transaction=2E We run the same
> appl=
> ication and process same transaction on production server, and we do not
> se=
> e the error=2E That is why upset me=2E=0D=0AThe only different is on
> produc=
> tion server using IDS731UD10 and develop server using IDS v115UC3=2E=0D=0A=
> =0D=0AThanks again,=0D=0ADenny=0D=0A=0D=0A-----Original
> Message-----=0D=0AF=
> rom: ids-bounces@iiug=2Eorg [mailto:ids-bounces@iiug=2Eorg] On Behalf Of
> Ar=
> t Kagel=0D=0ASent: Tuesday, January 20, 2009 3:18 PM=0D=0ATo: ids@iiug
> =2Eor=
> g=0D=0ASubject: Re: 154 error [14582]=0D=0A=0D=0A=0D=0AAttachments don' t
> f=
> low through the forum interface, we don't see them=2E=0D=0A=0D=0AISAM
> error=
> -154, lock timeout, happens when a task that is running a server=0D=0Asess=
> ion with SET LOCK MODE TO WAIT <n-seconds>; encounters a lock
> that=0D=0Aper=
> sists for more than n seconds=2E It has nothing to do with the ONCONFIG=0D=
> =0Asettings (OK very little)=2E Likely some other process which is badly
> be=
> haved=0D=0Awas hung or paused while holding a lock, or was engaged in a
> mas=
> sive=0D=0Atransaction holding many locks for a long period of time before
> c=
> ommitting=2E=0D=0AThe fact that today you are not getting the error
> indicat=
> es that the timing=0D=0Aof other applications is such that they are not
> int=
> erferring with the=0D=0Atransaction load=2E=0D=0A=0D=0AArt=0D=0A=0D=0AOn
> Tu=
> e, Jan 20, 2009 at 1:00 PM, Guo, Denny <DGuo@livingstonintl=2Ecom> wrote:=
> =0D=0A=0D=0A> Hi All,=0D=0A>=0D=0A> I just upgrade our IDS from Ver731 to
> V=
> er115UC3 on aix V5=2E3tl8 few days ago=0D=0A> on=0D=0A> our development
> ser=
> ver=2E=0D=0A> I start to process our daily transaction files=2E And at one
> =
> point get 154=0D=0A> error=0D=0A> which is lock time out expired=2E=0D=0A>
> =
> Not quite sure what it really means=2E I try to process another sets of=0D=
> =0A> transaction files today and produces no error=2E=0D=0A> Could it
> relat=
> ed to new configuration file? I attach our original v731=0D=0A>
> configurati=
> on file and new V115 configuration file=2E=0D=0A> Hope somebody could
> point=
> me to right direction=2E=0D=0A>=0D=0A> Thanks,=0D=0A> Denny=0D=0A>=0D=0A> =
> *******************************************=0D=0A>=0D=0A> The information
> c=
> ontained in this e-mail message may=0D=0A> contain privileged and
> confident=
> ial information=2E=0D=0A> If you are not the intended recipient, you
> are=0D=
> =0A> hereby notified that any review, dissemination,=0D=0A> distribution
> or=
> duplication of this communication=0D=0A> is strictly prohibited=2E If you =
> have received this=0D=0A> message in error, please notify the sender by
> ret=
> urn=0D=0A> e-mail, delete this message and destroy any copies=2E=0D=0A>
> Int=
> ernet e- mail is not guaranteed to be secure or=0D=0A> error-free=2E
> Messag=
> es could be intercepted, corrupted,=0D=0A> lost, arrive late or contain
> vir=
> uses=2E=0D=0A> The sender will not be liable for=0D=0A> these risks=2E=0D=
> =0A>=0D=0A> *******************************************=0D=0A> Ce message =
> =E9lectronique pourrait contenir des informations=0D=0A> privil=E9gi=E9es
> e=
> t confidentielles=2E Si vous n'en =EAtes pas le=0D=0A> r=E9cipiendaire pr=
> =E9vu, nous vous signalons qu'il est strictement=0D=0A> interdit
> d'examiner=
> , de diffuser, de distribuer et de reproduire le=0D=0A> pr=E9sent message=
> =2E Si vous l'avez re=E7u par erreur, veuillez pr=E9venir=0D=0A>
> l'exp=E9di=
> teur par courriel, puis effacer ce message et en d=E9truire=0D=0A> toute
> co=
> pie=2E Le courrier =E9lectronique n'est pas garanti s=E9curitaire=0D=0A>
> ni=
> exempt d'erreurs=2E Les messages pourraient =EAtre intercept=E9s,=0D=0A> c=
> orrompus, =E9gar=E9s, retard=E9s ou contamin=E9s par des virus=2E=0D=0A>
> L'=
> exp=E9diteur n'est pas responsable de ces risques=2E=0D=0A>=0D=0A>=0D=0A>=
>
> =0D=0A>=0D=0A**************************************************************=
> *****************=0D=0A> Forum Note: Use "Reply" to post a response in the
> =
> discussion forum=2E=0D=0A>=0D=0A>=0D=0A=0D=0A--=0D=0AArt S=2E
> Kagel=0D=0AOn=
> init (www=2Eoninit=2Ecom)=0D=0AIIUG Board of Directors (art@iiug
> =2Eorg)=0D=
> =0A=0D=0ADisclaimer: Please keep in mind that my own opinions are my own
> op=
> inions and=0D=0Ado not reflect on my employer, Oninit, the IIUG, nor any
> ot=
> her organization=0D=0Awith which I am associated either explicitly or
> impli=
> citly=2E Neither do=0D=0Athose opinions reflect those of other individuals
> =
> affiliated with any entity=0D=0Awith which I am affiliated nor those of
> the=
> entities themselves=2E=0D=0A=0D=0A=0D=0A**********************************=
> *********************************************=0D=0A Forum Note: Use "Reply=
> " to post a response in the discussion
> forum=2E=0D=0A=0D=0A****************=
> ***************************=0D=0A=0D=0AThe information contained in this
> e-=
> mail message may =0D=0Acontain privileged and confidential information=2E =
> =0D=0AIf you are not the intended recipient, you are =0D=0Ahereby notified
> =
> that any review, dissemination, =0D=0Adistribution or duplication of this
> c=
> ommunication =0D=0Ais strictly prohibited=2E If you have received this =0D=
> =0Amessage in error, please notify the sender by return =0D=0Ae-mail,
> delet=
> e this message and destroy any copies=2E =0D=0AInternet e- mail is not
> guar=
> anteed to be secure or =0D=0Aerror-free=2E Messages could be intercepted,
> c=
> orrupted, =0D=0Alost, arrive late or contain viruses=2E =0D=0AThe sender
> wi=
> ll not be liable for =0D=0Athese risks=2E
> =0D=0A=0D=0A*********************=
> ********************** =0D=0ACe message =E9lectronique pourrait contenir
> de=
> s informations=0Aprivil=E9gi=E9es et confidentielles=2E Si vous n'en
> =EAtes=
> pas le=0Ar=E9cipiendaire pr=E9vu, nous vous signalons qu'il est strictemen=
> t=0Ainterdit d'examiner, de diffuser, de distribuer et de reproduire
> le=0Ap=
> r=E9sent message=2E Si vous l'avez re=E7u par erreur, veuillez pr=E9venir=
> =0Al'exp=E9diteur par courriel, puis effacer ce message et en
> d=E9truire=0A=
> toute copie=2E Le courrier =E9lectronique n'est pas garanti s=E9curitaire=
> =0Ani exempt d'erreurs=2E Les messages pourraient =EAtre
> intercept=E9s,=0Ac=
> orrompus, =E9gar=E9s, retard=E9s ou contamin=E9s par des virus=2E=0AL'exp=
> =E9diteur n'est pas responsable de ces risques=2E
>
>
>
> *******************************************************************************
> 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.