Microsoft
Software
Hardware
Network
Question : Slow Session Database Queries since WAS Upgrade
Hi all,
Since upgrading from WAS 5.1 to 6.0.2.33, we have noticed queries running against the session database are taking a long time to complete. It sometimes takes up to 16 secs for an UPDATE/INSERT/DELETE/SELEC
T to complete. One notable item is the issue presents itself as load increases.
We have a test environment which is nearly identical to our production environment and we have not been able to reprodiuce the issue.
Our WAS admins have confirmed the setting in both environmnets are identical and our DB2 DBA's are not seeing anything obvious on the database side (no table scans, locks, etc).
What else can we look at to help identify the problem? We are planning on recreating the session db from scratch on wednesday as a last ditch effort.
Application Servers: Windows 2003 Enterprise, Websphere 6.0.2.33
The session database is run on AIX 5.3 with DB2 ver 8.2
Thanks in advance for your help!
Answer : Slow Session Database Queries since WAS Upgrade
Finally figured this out.
Archive logging on the the session DB turned out to be the cuplirt. Change this to circular logging dramtically improved the performance. A new log was being created every 2 seconds and was causing the SQL execution delay.
Random Solutions
Citrix Secure Gateway
How does ICQ make money?
Can ping everything and can browse LAN but cannot browse the Internet with IE
Stack Trace in Eclipse
Logon Unsuccessful
How I can convert coordinates from xls to google maps KML file?
Why are BGP messages called messages and not packets?
No Logon Servers Available to service the request
NetGear Setup to Allow PCAnywhere Connection
New PC can not send emails via Postfix with SPF error generated.