<sid>GEN000 Db2 corrid

[marco_mica]

Looking on one of our DB2 systems where we run ECC, we see DB2 threads originating from some of our application servers with name <sid>GEN000

One of these threads has been on the system for almost a week now, with 2 updates and no commit.

We also see a number of these with no updates and no commit.

Based on the naming, I would think this is a work process thread of type 'GEN', however I cannot find any documentation that this type of thread exists (we only see DIA,BTC,UPD,ENQ,SPL etc).

We thought it might be something related to SGEN processing, but cannot really find confirmation of that or reproduce it.

Any idea on what these Db2 threads are used for ?

[marco_mica · Accepted solution]

Did some further research, and based on the tables used by the thread, it seems to be a work process / thread type used by the change and transport system.

Maybe a transport has abended and left the threads out there.

Just looking for confirmation if these are indeed from the Transport system.

[brian_walker · Accepted solution]

Marco,

When running STMS/tp in one of our systems, I also see threads in DB2 like <sid>GEN000. Normally they are not there very long, but if there was a problem importing the transport they may stay around longer. Every now and then we'll get a -913 error because something else has a lock in DB2 that tp wants. This happened most recently when we had some daily DB02 update jobs that ran much longer than normal. We opened a message with SAP and they created SAP note 1278100 to fix the long running problem. We have our DB2 parameters configured so that resource timeouts are stopped after 10 minutes, so in this case tp gets stuck and after 10 minutes or so stops. I believe the ZPARM for that is IRLMRWT.

Brian