Oninit cdi / Archive
Talk to an expert →

v11.50.fc2 excessive kernel reads

Posted in 2008

Topics: Installation, Setup & Upgrades, Platform-Specific Issues

Peter_Logan@spartanstores.com — — source: IIUG Forums & Mailing Lists

I just installed v11.50.fc2 on an Aix 5.3 system. Only changes to the config file was that I changed the sqltrace to be global and not user ... and I added SCANNER num=2,treashold=500000,rangesize=100,alice=6 previous that was not set ... Since the upgrade the kernel reads on this system have gone crazy ... normally they range to about 2.5m with an average around 200000. Since the upgrade they have been as high asa range of 35m with an average of 500000. I think that is per second ... Stats have been updated and that sort of stuff ... Does anyone know if the sqltrace and the scanner can cause something like this ... I have since turned off sqltrace to see if that helped any .. Thanks in advance for any info ... Peter Peter Logan Senior Database Administrator Phone: 616/878-8309

↪ replying to Peter_Logan@spartanstores.com
Mark Jamison — — source: IIUG Forums & Mailing Lists

Hi Peter, Can you run an onstat -C prof, and an onstat -g cpu? Looking at those might be able to help answer the question. How are you measuring Kernel reads? ----- Original Message ---- From: "Peter_Logan@spartanstores.com" <Peter_Logan@spartanstores.com> To: ids@iiug.org Sent: Wednesday, October 8, 2008 4:38:10 PM Subject: v11.50.fc2 excessive kernel reads [13643] I just installed v11.50.fc2 on an Aix 5.3 system. Only changes to the config file was that I changed the sqltrace to be global and not user ... and I added SCANNER num=2,treashold=500000,rangesize=100,alice=6 previous that was not set ... Since the upgrade the kernel reads on this system have gone crazy ... normally they range to about 2.5m with an average around 200000. Since the upgrade they have been as high asa range of 35m with an average of 500000. I think that is per second ... Stats have been updated and that sort of stuff ... Does anyone know if the sqltrace and the scanner can cause something like this ... I have since turned off sqltrace to see if that helped any .. Thanks in advance for any info ... Peter Peter Logan Senior Database Administrator Phone: 616/878-8309 ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Related threads