I am not familiar with db2 internal working , and I have a one serious problem to handle
actually I have been using db2 8.2 on win2003 4 core CPU and it was working fine since my heavy data report started tacking 24hrs to complete , So I bought IBM Server with 8 core and 12 GB of RAM
Now problem is using EE db2 9.7 on RHEL 6 , my report process only use 2 CPU out of 8 core and If I initiate second thread manually only then process spreads to 4 CPU,
So problem is why in linux 9.7 my process is limited to 2 CPU in Db2 EE but use 4 CPU on db 8.2 on windows automatically
(and workgroup edition use only one CPU )
I have already run the INTRA_PARALLEL, but no luck
Have you recycled instance after you alter set INTRA_PARALLEL to Yes?
Maybe you also need to alter the db cfg (DFT_DEGREE) to any to let db2 choose query parallel degree.
You can use db2expln or db2exfmt to see query degree for the specific sql。
yeah , recycle = restart.
Maybe access plans for your query have been changed when you migrate your system on db2 v9.7。
You can use get snapshot for application to see how much agents associated with your application when runing the data report.
"Maximum associated agents = XX"
and Not all excuting phases of a query can't be processed parallelly ( fetch ,compile,etc)
anyway it will be ealier to dig out what the problem is if you put the exactly access plan here.