Making DB2 thread Inactive

Question

0.00/5 (No votes)

See more:

.NET2.0

Hi All,
I am using OLEDB driver to connect DB2 to DotNet. There in no SP's in my application. The problem in the application is that there are lots of active threads in DB2. How can i make these threads inactive.
I have already closed and disposed all the open connections.

In our application, even after closing all the connection from .Net, we are having active threads in the DB2 database which leads to DB2 Page latch timeout and distributed thread timeout.
Received abend: 04E
Reason for error: 00D3003B

Our SA is suggesting us to commit all the transactions. Will it be the efficient solution of that problem.

As per my understanding when we commit the transaction, all the DB2 threads will be released from the application and they should be marked inactive by the DB2 database itself.
Correct me if i am wrong.

Posted 13-Jul-12 0:07am

Mohit Garg 2

Updated 8-Mar-16 11:46am

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

E.F. Nijboer · Answer 1 · 2012-07-13T00:50:00

Solution 1

Maybe you can try releasing the object pool. Check out msdn about it:
http://msdn.microsoft.com/en-us/library/system.data.oledb.oledbconnection.releaseobjectpool[^]

Good luck!

Posted 13-Jul-12 0:50am

E.F. Nijboer

Member 12378664 · Answer 2 · 2016-03-08T11:46:00

Solution 2

Yes, if no resources are being held across commit boundaries, then the thread should go inactive.

You should also verify your zParm 'CMTSTAT' is set to 'INACTIVE'. If set to 'ACTIVE', threads will stay active until terminated (or timed out by the IDTHTOIN value).

Posted 8-Mar-16 11:46am

Member 12378664