IDS Forum

RE: 154 error

Posted By: Guo, Denny
Date: Tuesday, 20 January 2009, at 3:56 p.m.

In Response To: Re: 154 error (Art Kagel)

Thanks for quick reply, Art=2E=0D=0A=0D=0AI guest I found out why=2E It is =
just bad timing=2E=0D=0AOur application is using repeatable-read isolation =
mode=2E=0D=0AOur db design is like this=2E Table B is child table of table =
A=2E=0D=0AI finally found that when we try to update table A and there is a=
nother session try to update table B and will require information from tabl=
e A=2E=0D=0AThat is why causing failure=2E On production server, the proces=
sing timing is not causing problem=2E=0D=0A=0D=0APlease correct me if my un=
derstanding is wrong=2E=0D=0A=0D=0AThanks,=0D=0ADenny=0D=0A=0D=0A=0D=0A----=
-Original Message-----=0D=0AFrom: ids-bounces@iiug=2Eorg [mailto:ids-bounce=
s@iiug=2Eorg] On Behalf Of Art Kagel=0D=0ASent: Tuesday, January 20, 2009 3=
:45 PM=0D=0ATo: ids@iiug=2Eorg=0D=0ASubject: Re: 154 error [14584]=0D=0A=0D=
=0A=0D=0AWhoa, big formatting problem there=2E Denny, There's something goi=
ng on=0D=0Athere=2E You simply cannot get a lock timeout if you are not con=
tending for=0D=0Alocks somehow=2E The one other possibility would be a long=
checkpoint=0D=0Ablocking the application in a critical section, but checkp=
oints are=0D=0Anon-blocking in 11=2E50, so that also should not happen=2E D=
oes the one=0D=0Aapplication maintain multiple connections to the server? I=
s there a SELECT=0D=0A=2E=2E=2E=2E=2E FOR UPDATE loop with insert, delete, =
or updates happening inside the=0D=0Aloop?=0D=0A=0D=0AA8rt=0D=0A=0D=0AOn Tu=
e, Jan 20, 2009 at 3:28 PM, Guo, Denny <DGuo@livingstonintl=2Ecom> wrote:=
=0D=0A=0D=0A> Thanks Art,=3D0D=3D0A=3D0D=3D0ABut there is only one applicat=
ion=0D=0A> running=3D2E=3D0D=3D0ATh=3D=0D=0A> e application runs update on =
particular transaction=3D2E We run the same=0D=0A> appl=3D=0D=0A> ication a=
nd process same transaction on production server, and we do not=0D=0A> se=
=3D=0D=0A> e the error=3D2E That is why upset me=3D2E=3D0D=3D0AThe only dif=
ferent is on=0D=0A> produc=3D=0D=0A> tion server using IDS731UD10 and devel=
op server using IDS v115UC3=3D2E=3D0D=3D0A=3D=0D=0A> =3D0D=3D0AThanks again=
,=3D0D=3D0ADenny=3D0D=3D0A=3D0D=3D0A-----Original=0D=0A> Message-----=3D0D=
=3D0AF=3D=0D=0A> rom: ids-bounces@iiug=3D2Eorg [mailto:ids-bounces@iiug=3D2=
Eorg] On Behalf Of=0D=0A> Ar=3D=0D=0A> t Kagel=3D0D=3D0ASent: Tuesday, Janu=
ary 20, 2009 3:18 PM=3D0D=3D0ATo: ids@iiug=0D=0A> =3D2Eor=3D=0D=0A> g=3D0D=
=3D0ASubject: Re: 154 error [14582]=3D0D=3D0A=3D0D=3D0A=3D0D=3D0AAttachment=
s don' t=0D=0A> f=3D=0D=0A> low through the forum interface, we don't see t=
hem=3D2E=3D0D=3D0A=3D0D=3D0AISAM=0D=0A> error=3D=0D=0A> -154, lock timeout,=
happens when a task that is running a server=3D0D=3D0Asess=3D=0D=0A> ion w=
ith SET LOCK MODE TO WAIT <n-seconds>; encounters a lock=0D=0A> that=3D0D=
=3D0Aper=3D=0D=0A> sists for more than n seconds=3D2E It has nothing to do =
with the ONCONFIG=3D0D=3D=0D=0A> =3D0Asettings (OK very little)=3D2E Likely=
some other process which is badly=0D=0A> be=3D=0D=0A> haved=3D0D=3D0Awas h=
ung or paused while holding a lock, or was engaged in a=0D=0A> mas=3D=0D=0A=
> sive=3D0D=3D0Atransaction holding many locks for a long period of time be=
fore=0D=0A> c=3D=0D=0A> ommitting=3D2E=3D0D=3D0AThe fact that today you are=
not getting the error=0D=0A> indicat=3D=0D=0A> es that the timing=3D0D=3D0=
Aof other applications is such that they are not=0D=0A> int=3D=0D=0A> erfer=
ring with the=3D0D=3D0Atransaction load=3D2E=3D0D=3D0A=3D0D=3D0AArt=3D0D=3D=
0A=3D0D=3D0AOn=0D=0A> Tu=3D=0D=0A> e, Jan 20, 2009 at 1:00 PM, Guo, Denny <=
DGuo@livingstonintl=3D2Ecom> wrote:=3D=0D=0A> =3D0D=3D0A=3D0D=3D0A> Hi All,=
=3D0D=3D0A>=3D0D=3D0A> I just upgrade our IDS from Ver731 to=0D=0A> V=3D=0D=
=0A> er115UC3 on aix V5=3D2E3tl8 few days ago=3D0D=3D0A> on=3D0D=3D0A> our =
development=0D=0A> ser=3D=0D=0A> ver=3D2E=3D0D=3D0A> I start to process our=
daily transaction files=3D2E And at one=0D=0A> =3D=0D=0A> point get 154=3D=
0D=3D0A> error=3D0D=3D0A> which is lock time out expired=3D2E=3D0D=3D0A>=0D=
=0A> =3D=0D=0A> Not quite sure what it really means=3D2E I try to process a=
nother sets of=3D0D=3D=0D=0A> =3D0A> transaction files today and produces n=
o error=3D2E=3D0D=3D0A> Could it=0D=0A> relat=3D=0D=0A> ed to new configura=
tion file? I attach our original v731=3D0D=3D0A>=0D=0A> configurati=3D=0D=
=0A> on file and new V115 configuration file=3D2E=3D0D=3D0A> Hope somebody =
could=0D=0A> point=3D=0D=0A> me to right direction=3D2E=3D0D=3D0A>=3D0D=3D0=
A> Thanks,=3D0D=3D0A> Denny=3D0D=3D0A>=3D0D=3D0A> =3D=0D=0A> **************=
*****************************=3D0D=3D0A>=3D0D=3D0A> The information=0D=0A> =
c=3D=0D=0A> ontained in this e-mail message may=3D0D=3D0A> contain privileg=
ed and=0D=0A> confident=3D=0D=0A2> ial information=3D2E=3D0D=3D0A> If you a=
re not the intended recipient, you=0D=0A> are=3D0D=3D=0D=0A> =3D0A> hereby =
notified that any review, dissemination,=3D0D=3D0A> distribution=0D=0A> or=
=3D=0D=0A> duplication of this communication=3D0D=3D0A> is strictly prohibi=
ted=3D2E If you =3D=0D=0A> have received this=3D0D=3D0A> message in error, =
please notify the sender by=0D=0A> ret=3D=0D=0A> urn=3D0D=3D0A> e-mail, del=
ete this message and destroy any copies=3D2E=3D0D=3D0A>=0D=0A> Int=3D=0D=0A=
> ernet e- mail is not guaranteed to be secure or=3D0D=3D0A> error-free=3D2=
E=0D=0A> Messag=3D=0D=0A> es could be intercepted, corrupted,=3D0D=3D0A> lo=
st, arrive late or contain=0D=0A> vir=3D=0D=0A> uses=3D2E=3D0D=3D0A> The se=
nder will not be liable for=3D0D=3D0A> these risks=3D2E=3D0D=3D=0D=0A> =3D0=
A>=3D0D=3D0A> *******************************************=3D0D=3D0A> Ce mes=
sage =3D=0D=0A> =3DE9lectronique pourrait contenir des informations=3D0D=3D=
0A> privil=3DE9gi=3DE9es=0D=0A> e=3D=0D=0A> t confidentielles=3D2E Si vous =
n'en =3DEAtes pas le=3D0D=3D0A> r=3DE9cipiendaire pr=3D=0D=0A> =3DE9vu, nou=
s vous signalons qu'il est strictement=3D0D=3D0A> interdit=0D=0A> d'examine=
r=3D=0D=0A> , de diffuser, de distribuer et de reproduire le=3D0D=3D0A> pr=
=3DE9sent message=3D=0D=0A> =3D2E Si vous l'avez re=3DE7u par erreur, veuil=
lez pr=3DE9venir=3D0D=3D0A>=0D=0A> l'exp=3DE9di=3D=0D=0A> teur par courriel=
, puis effacer ce message et en d=3DE9truire=3D0D=3D0A> toute=0D=0A> co=3D=
=0D=0A> pie=3D2E Le courrier =3DE9lectronique n'est pas garanti s=3DE9curit=
aire=3D0D=3D0A>=0D=0A> ni=3D=0D=0A> exempt d'erreurs=3D2E Les messages pour=
raient =3DEAtre intercept=3DE9s,=3D0D=3D0A> c=3D=0D=0A> orrompus, =3DE9gar=
=3DE9s, retard=3DE9s ou contamin=3DE9s par des virus=3D2E=3D0D=3D0A>=0D=0A>=
L'=3D=0D=0A> exp=3DE9diteur n'est pas responsable de ces risques=3D2E=3D0D=
=3D0A>=3D0D=3D0A>=3D0D=3D0A>=3D=0D=0A>=0D=0A> =3D0D=3D0A>=3D0D=3D0A********=
******************************************************=3D=0D=0A> **********=
*******=3D0D=3D0A> Forum Note: Use "Reply" to post a response in the=0D=0A>=
=3D=0D=0A> discussion forum=3D2E=3D0D=3D0A>=3D0D=3D0A>=3D0D=3D0A=3D0D=3D0A=
--=3D0D=3D0AArt S=3D2E=0D=0A> Kagel=3D0D=3D0AOn=3D=0D=0A> init (www=3D2Eoni=
nit=3D2Ecom)=3D0D=3D0AIIUG Board of Directors (art@iiug=0D=0A> =3D2Eorg)=3D=
0D=3D=0D=0A> =3D0A=3D0D=3D0ADisclaimer: Please keep in mind that my own opi=
nions are my own=0D=0A> op=3D=0D=0A> inions and=3D0D=3D0Ado not reflect on =
my employer, Oninit, the IIUG, nor any=0D=0A> ot=3D=0D=0A> her organization=
=3D0D=3D0Awith which I am associated either explicitly or=0D=0A> impli=3D=
=0D=0A> citly=3D2E Neither do=3D0D=3D0Athose opinions reflect those of othe=
r individuals=0D=0A> =3D=0D=0A> affiliated with any entity=3D0D=3D0Awith wh=
ich I am affiliated nor those of=0D=0A> the=3D=0D=0A> entities themselves=
=3D2E=3D0D=3D0A=3D0D=3D0A=3D0D=3D0A**********************************=3D=0D=
=0A> *********************************************=3D0D=3D0A Forum Note: Us=
e "Reply=3D=0D=0A> " to post a response in the discussion=0D=0A> forum=3D2E=
=3D0D=3D0A=3D0D=3D0A****************=3D=0D=0A> ***************************=
=3D0D=3D0A=3D0D=3D0AThe information contained in this=0D=0A> e-=3D=0D=0A> m=
ail message may =3D0D=3D0Acontain privileged and confidential information=
=3D2E =3D=0D=0A> =3D0D=3D0AIf you are not the intended recipient, you are =
=3D0D=3D0Ahereby notified=0D=0A> =3D=0D=0A> that any review, dissemination,=
=3D0D=3D0Adistribution or duplication of this=0D=0A> c=3D=0D=0A> ommunicat=
ion =3D0D=3D0Ais strictly prohibited=3D2E If you have received this =3D0D=
=3D=0D=0A> =3D0Amessage in error, please notify the sender by return =3D0D=
=3D0Ae-mail,=0D=0A> delet=3D=0D=0A> e this message and destroy any copies=
=3D2E =3D0D=3D0AInternet e- mail is not=0D=0A> guar=3D=0D=0A> anteed to be =
secure or =3D0D=3D0Aerror-free=3D2E Messages could be intercepted,=0D=0A> c=
=3D=0D=0A> orrupted, =3D0D=3D0Alost, arrive late or contain viruses=3D2E =
=3D0D=3D0AThe sender=0D=0A> wi=3D=0D=0A> ll not be liable for =3D0D=3D0Athe=
se risks=3D2E=0D=0A> =3D0D=3D0A=3D0D=3D0A*********************=3D=0D=0A> **=
******************** =3D0D=3D0ACe message =3DE9lectronique pourrait conteni=
r=0D=0A> de=3D=0D=0A> s informations=3D0Aprivil=3DE9gi=3DE9es et confidenti=
elles=3D2E Si vous n'en=0D=0A> =3DEAtes=3D=0D=0A> pas le=3D0Ar=3DE9cipienda=
ire pr=3DE9vu, nous vous signalons qu'il est strictemen=3D=0D=0A> t=3D0Aint=
erdit d'examiner, de diffuser, de distribuer et de reproduire=0D=0A> le=3D0=
Ap=3D=0D=0A> r=3DE9sent message=3D2E Si vous l'avez re=3DE7u par erreur, ve=
uillez pr=3DE9venir=3D=0D=0A> =3D0Al'exp=3DE9diteur par courriel, puis effa=
cer ce message et en=0D=0A> d=3DE9truire=3D0A=3D=0D=0A> toute copie=3D2E Le=
courrier =3DE9lectronique n'est pas garanti s=3DE9curitaire=3D=0D=0A> =3D0=
Ani exempt d'erreurs=3D2E Les messages pourraient =3DEAtre=0D=0A> intercept=
=3DE9s,=3D0Ac=3D=0D=0A> orrompus, =3DE9gar=3DE9s, retard=3DE9s ou contamin=
=3DE9s par des virus=3D2E=3D0AL'exp=3D=0D=0A> =3DE9diteur n'est pas respons=
able de ces risques=3D2E=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=0AOninit (www=2Eoninit=2Ecom)=0D=
=0AIIUG Board of Directors (art@iiug=2Eorg)=0D=0A=0D=0ADisclaimer: Please k=
eep in mind that my own opinions are my own opinions and=0D=0Ado not reflec=
t on my employer, Oninit, the IIUG, nor any other organization=0D=0Awith wh=
ich I am associated either explicitly or implicitly=2E Neither do=0D=0Athos=
e 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 d=
iscussion forum=2E=0D=0A=0D=0A*******************************************=
=0D=0A=0D=0AThe information contained in this e-mail message may =0D=0Acont=
ain privileged and confidential information=2E =0D=0AIf you are not the int=
ended recipient, you are =0D=0Ahereby notified that any review, disseminati=
on, =0D=0Adistribution or duplication of this communication =0D=0Ais strict=
ly prohibited=2E If you have received this =0D=0Amessage in error, please n=
otify the sender by return =0D=0Ae-mail, delete this message and destroy an=
y copies=2E =0D=0AInternet e- mail is not guaranteed to be secure or =0D=0A=
error-free=2E Messages could be intercepted, corrupted, =0D=0Alost, arrive =
late or contain viruses=2E =0D=0AThe sender will not be liable for =0D=0Ath=
ese risks=2E =0D=0A=0D=0A******************************************* =0D=0A=
Ce message =E9lectronique pourrait contenir des informations=0Aprivil=E9gi=
=E9es et confidentielles=2E Si vous n'en =EAtes pas le=0Ar=E9cipiendaire pr=
=E9vu, nous vous signalons qu'il est strictement=0Ainterdit d'examiner, de =
diffuser, de distribuer et de reproduire le=0Apr=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=0Atoute copie=2E Le courrier =E9=
lectronique n'est pas garanti s=E9curitaire=0Ani exempt d'erreurs=2E Les me=
ssages pourraient =EAtre intercept=E9s,=0Acorrompus, =E9gar=E9s, retard=E9s=
ou contamin=E9s par des virus=2E=0AL'exp=E9diteur n'est pas responsable de=
ces risques=2E

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.