Do you you have any utils running at that time, theycan spoil it
Phone 0031 (0)30 215 2220
Mobile 0031 (0)6 5374 0167
e-Mail <mailto:[login to unmask email]>
Reserve your AGENDA for next DB2 Users Group Conference IDUG
8/11 October 2001 - < http://www.idug.org
No trees were killed in the sending of this message. However - a
number of electrons were terribly inconvenienced.
Van: Brian Picard [mailto:[login to unmask email]
Verzonden: donderdag 21 december 2000 15:33
Aan: [login to unmask email]
Onderwerp: Re: Timeouts / Deadlocks on resource type D01.(DBID,
The application team is trying to run about 10 concurrent
program and difft plans each using difft qualifier). All the 9 jobs
down, except job1. Subsequent restarts also failed because job1 had
completed at that time.
There were no DDL executed at this database at that time.
This is a dynamic application and we have to use the delivered
cannot change the commit frequency as it is next to impossible. It
is not a
static program where you can analyze and commit periodically(thats
was told when I asked the same question, don't know exactly what
complexities are, perhaps being able to restart).
This is not a everyday affair. According to the application, these
happen at their own wish and will and not necessarily everytime. So
involved now to look at the cause at the holiday season being a
By looking at the EDM pool snapshot I see, the available free pages
close to zero at most of the time and hence i assume approximately
could have been the case when the abends occured. Almost 99% has
by Dyn SQL Cache. We didnt have history capture turned on
I thought during the mini bind process(Dyn SQL), it is trying to
load a DBD
which is not in the pool and failed to fit the dbd block. The DBD
question needs 61 pages. We run Ver 5.1 and I checked the ZPARM
been set as NO. But even this guess logic by me doesn't make any
one program was able to succesfully bind(mini bind) and execute so
must have been in the EDM Pool.
The plan has been granted to public, with zero auth cache. We don't
packages. So I would rule out PLANAUTH locks.
MSTR information is of no use other than telling which jobs
what the DBID.OBID table was. It refers to the same table in all
When would DBDs be locked exclusively in the absence of a DDL?.
this case it should be IX and not exclusive. From the manuals, Dyn
take a shared lock on the DBD. So timeout or deadlock on a shared
doesnt make any sense.
De informatie opgenomen in dit bericht kan vertrouwelijk zijn
is uitsluitend bestemd voor de geadresseerde. Indien u dit
onterecht ontvangt, wordt u verzocht de inhoud niet te gebruiken
de afzender direct te informeren door het bericht te
The information contained in this message may be confidential
and is intended to be exclusively for the addressee. Should you
receive this message unintentionally, please do not use the
herein and notify the sender immediately by return e-mail.