RE: 8.1.7.4 migration from 32 bit to 64 bit problem

Sometimes even a small change in plans can result in a large change in performance for the query depending on what the change is.

Were the statistics updated on the new version?

Was the shared pool increased in size to compensate for the additional 4 bytes in every address pointer used. The 64 bit version of 8.1.7 needs about a 20% increase in the shared pool just to run the same load in our experience, but then we have a lot of stored code (pl/sql in the database).

Were any database parameters changed?

HTH -- Mark D Powell --

-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Jeremiah Wilton Sent: Friday, November 19, 2004 2:09 PM
To: Oracle L (E-mail)
Subject: RE: 8.1.7.4 migration from 32 bit to 64 bit problem

Sorry if this has been explored, but it sounds like the difference in the plans is the problem. Can you elaborate on WHAT is different about the plans?

Is something else hogging temp?

--
Jeremiah Wilton
Independent Oracle Professional
Oracle Certified Master
Disaster Recovery - Seminars - Technical Interviews
http://www.speakeasy.net/~jwilton

On Fri, 19 Nov 2004, Duret, Kathy wrote:



> two database set up is EXACTLY the same (init.ora, files size etc)

>

> Query using two views in OLD 32 bit runs in 2 seonds and with the WHOLE

> company running on the database uses less than 1/2 G of temp tablespaces.

>

> Query ONLY running on new production database get ora-1652 (out of temp

> space) on 1G of temp space after 81 seconds.

>

> Once again same set up, same data,  BUT the explain plans are different

but


> are fairly similiar.

--
http://www.freelists.org/webpage/oracle-l
--
http://www.freelists.org/webpage/oracle-l