By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,018 Members | 901 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,018 IT Pros & Developers. It's quick & easy.

DB21015E - New Error with Fixpack 8?

P: n/a
Hi all,

i saw that Jacelyn Yswan has posted already at 23th of February for the
same problem, but apparently there was no solution. Maybe someone knows the
reason today.

We use Fix 8 since 7th of march on AIX 5L and we still get the error
DB21015E since then every night at run time of our batch jobs. Because the
error occur every night on another job i can say that the db2 command cause
this problem is not allways the same (db2 connect to..., db2 get db
cfg...,etc.).

The standard "todos" like increasing DB2BQTIME + DB2BQTRY and repeating
db2iupdt does not solve the problem. The db2bp program also reside in the
correct dbm installation path. Next i will increase maxuproc, maybe this
will help but i have my doubts.

I have posted this problem to the DB2 Support, but maybe someone has
knowledge of this problem and can give me faster informations.

Thanks
Tino

--
Message posted via http://www.dbmonster.com
Nov 12 '05 #1
Share this Question
Share on Google+
2 Replies


P: n/a
DB2BQTIME's default value is 1 second - the maximum allowed.
DB2BQTRY defaults to 60.

This indicates that whatever is causing this problem has a duration
longer than 60 seconds.

If you are getting an immediate error when issuing the command then I'd
suspect a permissions problem. If it takes a full minute for the error
to show up then the problem lies in starting the db2bp program. If db2bp
cannot start at this time but runs ok (from this userid) at other times
of the day then this could be operating system related. (ie. Maximum
concurrent tasks has been reached.) I believe that if db2bp cannot
connect to the instance/database; then you get a different error.

Phil Sherman

Tino Lecomte via DBMonster.com wrote:
Hi all,

i saw that Jacelyn Yswan has posted already at 23th of February for the
same problem, but apparently there was no solution. Maybe someone knows the
reason today.

We use Fix 8 since 7th of march on AIX 5L and we still get the error
DB21015E since then every night at run time of our batch jobs. Because the
error occur every night on another job i can say that the db2 command cause
this problem is not allways the same (db2 connect to..., db2 get db
cfg...,etc.).

The standard "todos" like increasing DB2BQTIME + DB2BQTRY and repeating
db2iupdt does not solve the problem. The db2bp program also reside in the
correct dbm installation path. Next i will increase maxuproc, maybe this
will help but i have my doubts.

I have posted this problem to the DB2 Support, but maybe someone has
knowledge of this problem and can give me faster informations.

Thanks
Tino


Nov 12 '05 #2

P: n/a
It is not a permission problem. The night batches are all running with DBM
authority. If you start the same job 5 Minutes later the job is running
very nice and you got no errors. The problem occur after you reach the
DB2BQTIME, the big question is why?

I have tested the last few days seperate settings. I increase DB2BQTIME at
least to 90 seconds and increase maxuproc to about 50%, no influence to my
problem.

I think the problem is a new Fix 8 one.
Nov 12 '05 #3

This discussion thread is closed

Replies have been disabled for this discussion.