RE: migration from 32 bit to 64 bit problem

  • From: "Reidy, Ron" <Ron.Reidy@xxxxxxxxxxxxxxxxxx>
  • To: <kduret@xxxxxxxxxxxxxxxxxxxx>, <mark.powell@xxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Fri, 19 Nov 2004 14:04:35 -0700

Can you post both plans?

Maybe someone here can give you an idea.

Ron Reidy
Lead DBA
Array BioPharma, Inc.

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]On Behalf Of Duret, Kathy
Sent: Friday, November 19, 2004 1:48 PM
To: 'mark.powell@xxxxxxx'; 'oracle-l@xxxxxxxxxxxxx'
Subject: RE: migration from 32 bit to 64 bit problem

Nothing was changed..... I tried to increase the shared pool on the new =
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....=20

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

-----Original Message-----
From: Powell, Mark D [mailto:mark.powell@xxxxxxx]
Sent: Friday, November 19, 2004 2:06 PM
To: 'oracle-l@xxxxxxxxxxxxx'
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 =

Were any database parameters changed?

HTH -- Mark D Powell --

-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx]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 =
> company running on the database uses less than 1/2 G of temp =
> Query ONLY running on new production database get ora-1652 (out of =
> space) on 1G of temp space after 81 seconds.
> Once again same set up, same data,  BUT the explain plans are =
> are fairly similiar.

This transmission contains information solely for intended recipient and =
be privileged, confidential and/or otherwise protect from disclosure.  =
you are not the intended recipient, please contact the sender and delete =
copies of this transmission.  This message and/or the materials =
herein are not an offer to sell, or a solicitation of an offer to buy, =
securities or other instruments.  The information has been obtained or
derived from sources believed by us to be reliable, but we do not =
that it is accurate or complete.  Any opinions or estimates contained in
this information constitute our judgment as of this date and are subject =
change without notice.  Any information you share with us will be used =
the operation of our business, and we do not request and do not want any
material, nonpublic information. Absent an express prior written =
we are not agreeing to treat any information confidentially and will use =
and all information and reserve the right to publish or disclose any
information you share with us.

This electronic message transmission is a PRIVATE communication which =
information which may be confidential or privileged. The information is =
to be for the use of the individual or entity named above. If you are =
not the=20
intended recipient, please be aware that any disclosure, copying, =
or use of the contents of this information is prohibited. Please notify =
sender  of the delivery error by replying to this message, or notify us =
telephone (877-633-2436, ext. 0), and then delete it from your system.


Other related posts: