RTC 3.0.1 Problem during DB2 reorgs
RTC servers on windowx XP and zLinux - DB2 is on z/OS
The RTC servers are continuing to affect our weekend DB2 reorg jobs.
There are just too many DDF threads active during the Reorgs for us to
get the proper locks for the Reorgs to run and our Reorgs end up abending.
We have been skipping the objects in the RTC database that we have been having locking issues on
Question, at the time of the maintenance cycle there is no one logged on to the server. It is sitting there. Why would the servers at this point in time keep the threads active? Is there a way to force the thread to close on non-use after a given timeframe?
Should the the servers be brought down during the Reorg window?
The RTC servers are continuing to affect our weekend DB2 reorg jobs.
There are just too many DDF threads active during the Reorgs for us to
get the proper locks for the Reorgs to run and our Reorgs end up abending.
We have been skipping the objects in the RTC database that we have been having locking issues on
Question, at the time of the maintenance cycle there is no one logged on to the server. It is sitting there. Why would the servers at this point in time keep the threads active? Is there a way to force the thread to close on non-use after a given timeframe?
Should the the servers be brought down during the Reorg window?
One answer
RTC servers on windowx XP and zLinux - DB2 is on z/OS
The RTC servers are continuing to affect our weekend DB2 reorg jobs.
There are just too many DDF threads active during the Reorgs for us to
get the proper locks for the Reorgs to run and our Reorgs end up abending.
We have been skipping the objects in the RTC database that we have been having locking issues on
Question, at the time of the maintenance cycle there is no one logged on to the server. It is sitting there. Why would the servers at this point in time keep the threads active? Is there a way to force the thread to close on non-use after a given timeframe?
Should the the servers be brought down during the Reorg window?
The issue is that the jdbc connection pool in the RTC server never lets go of connections even if no one is using the server. Also there are async back ground tasks that periodically wake up and do things on the db. Therefore, yes bring down the server while doing the reorg.