|
Thanks, our problem seems to be more of a PASE issue, our native apps are running ok. This is very strange to us. -----Original Message----- From: Elvis Budimlic [mailto:ebudimlic@xxxxxxxxxxxxxxxxxxxxxxxxx] Sent: Friday, April 07, 2006 12:17 PM To: 'Midrange Systems Technical Discussion' Subject: RE: V5R3M0 Performance Issues Small correction, old query engine is CQE (Classic Query Engine). New query engine is SQE (SQL Query Engine). I don't see how access path can be considered old. Did you perhaps encounter an issue with access path size (*MAX4GB vs *MAX1TB)? Or in CQE engine you were encountering query optimizer time-out due to large number of indexes over the files? Elvis B. -----Original Message----- Subject: Re: V5R3M0 Performance Issues I know from upgrading to 5.3 that we did run into alot of issues with the change to cqe engine for the queries (sql). I'm not sure how your app is running but we did find that with the change to cqe if you are running sql statements over logicals with include or omits in it, the queries will tank unless you tell the optomizer to use the old query engine (sqe). The other issue that we hit it large files with access paths that were "old", you cant telll that they are but if you do a chglf and just take the option to force the access path rebuild that helped alot. Not sure if it helps you, but thought I'd mention it Important Confidentiality Notice: This email message, including all attachments is for the exclusive use by the person(s) to whom it is addressed, and may contain information that is confidential or privileged. Any unauthorized review, use, disclosure or distribution is prohibited under applicable law. If you have received this email in error, please notify me immediately by reply email and delete this message and any attachments. Thank you.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.