Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: Migration from 7.3.4 to 8.1.6

RE: Migration from 7.3.4 to 8.1.6

From: <Dan.Hubler_at_Metavante.com>
Date: Fri, 23 Mar 2001 08:52:40 -0800
Message-ID: <F001.002D621F.20010323081037@fatcity.com>

The thing that is killing us is a single query.

This query does a group by.

It also references some user-defined functions in the column-list of the SELECT statement.

These user-defined functions are actually SELECTS from 2 other small tables.

It is not behaving the same way it did in version 7.3.4.

The table that the query runs against is pretty big (700,000 rows across 4 gig).
The 2 tables referenced by the user-defined functions are very small (10-20 rows).

"Ruiz, Mary A (CAP, CDI)" <Mary.Ruiz_at_gecapital.com> on 03/22/2001 04:18:30 PM

To: "'Dan.Hubler_at_Metavante.com'" <Dan.Hubler_at_Metavante.com> cc: "'ORACLE-L_at_fatcity.com'" <ORACLE-L_at_fatcity.com>

Dan:
  What kinds of problems ? I am beginning a migration of a hybrid OLTP / OLAP database from 7.3.4 to 8.1.5 on Solaris 2.6 We are planning to take 6 weeks to "clean up" the
database and fix the chained /migrated rows before we migrate (mainly on the big tables). We will spend a month testing on a migrated copy before migrating production. Our apps
are custom Powerbuilder apps. I decided to go to 8.1.5 because our other databases are 8.1.5, and just live with the fact I cannot import a table from a multiple-table export.
(that bugs me to no end) I am most interested in responses to this post.
Maybe some truly compelling reasons to go to 8.1.6 , although I heard about hanging listener problems
with that version which scared me.

thanks in advance,
Mary Ruiz / Atlanta

-----Original Message-----
Sent: Thursday, March 22, 2001 3:46 PM
To: Multiple recipients of list ORACLE-L

We just migrated the first of our environments from 7.3.4 to 8.1.6 ( Solaris 2.6 ).

We have run into a couple of problems that only seem to appear when processing
large tables or large amounts of data.

This is kind of what we expected because we did not have the resources to do full-blown, production size testing.

Anybody have any information on things that go wrong with this type of migration?

--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
  INET: Dan.Hubler_at_Metavante.com

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L

(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: INET: Dan.Hubler_at_Metavante.com Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Lists -------------------------------------------------------------------- To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Fri Mar 23 2001 - 10:52:40 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US