Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> RE: migration from 32 bit to 64 bit problem

RE: migration from 32 bit to 64 bit problem

From: Duret, Kathy <>
Date: Fri, 19 Nov 2004 14:48:20 -0600
Message-ID: <>

Nothing was changed..... I tried to increase the shared pool on the new dev version and bounced it.... no good.

I am trying various hints in all the views and sub views to no avail. I finally got a descent tech now for my tar....

Yes I just updated the stats again for the new tech. I am going to give him a 10053 trace as well. The explain plan for the new database is very strange for this query.

-----Original Message-----
From: Powell, Mark D [] Sent: Friday, November 19, 2004 2:06 PM
To: ''
Subject: RE: 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-----
[]On Behalf Of Jeremiah Wilton Sent: Friday, November 19, 2004 2:09 PM
To: Oracle L (E-mail)
Subject: RE: 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

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
> are fairly similiar.
-- -- This transmission contains information solely for intended recipient and may be privileged, confidential and/or otherwise protect from disclosure. If you are not the intended recipient, please contact the sender and delete all copies of this transmission. This message and/or the materials contained herein are not an offer to sell, or a solicitation of an offer to buy, any securities or other instruments. The information has been obtained or derived from sources believed by us to be reliable, but we do not represent that it is accurate or complete. Any opinions or estimates contained in this information constitute our judgment as of this date and are subject to change without notice. Any information you share with us will be used in the operation of our business, and we do not request and do not want any material, nonpublic information. Absent an express prior written agreement, we are not agreeing to treat any information confidentially and will use any and all information and reserve the right to publish or disclose any information you share with us. --
Received on Fri Nov 19 2004 - 14:58:51 CST

Original text of this message