Re: 8i to 10g migration
- From: Bjørn Dörr Jensen <B.D.Jensen@xxxxxxx>
- To: <paulastankus@xxxxxxxxx>
- Date: Tue, 18 Jul 2006 16:42:52 +0200
Hi!
The upgrade-manual, but I think you have looked at that.
Expect problems with dangling synonyms and
differences with parameter-types between spec and body in packages,
for example leaving default-values. Package Body's wont compile if there are
these minor differences.
So look at invalids.
You can upgrade directly ;-)
export/import: how big are your db? Try with your clone to see how long time it
tooks.
And make your test on correct os-platform.
Measure time of typical batch-jobs and queries before upgrading.
Check your access to Metalink.
Plan in your calender that it won't succeed at 1. try.
And when upgraded - enjoy the big amount of new features (-: PL/SQL-developer
group and DBA's should be prepared using the new features).
Greetings
Bjørn
----- Original Message -----
From: Paula Stankus
To: oracle-l@xxxxxxxxxxxxx
Sent: Tuesday, July 18, 2006 1:07 PM
Subject: Re: 8i to 10g migration
We have the following environment:
-a great deal of database links
-materialized views over database links
-Oracle 8.1.7
-Solaris 2.9
- .Net with ODP
-Powerbuilder
-Data Junction
-Siebel
-Cobol programs precompiled
and are planning a migration from 8.1.7 to 10g.
Where is the best place to look for gotchas:
-database links
-hints that have been desupported
-Issues with .Net
-Issues with Cobol precompilers
-Performance concerns
-migration path - direct migration or export/import????
I am planning to clone production, give ample time to multiple development
teams to test this out. I am planning to take sample queries generating
execution plans in both environments and traces. I am planning a stress-test.
Any advice would be greatly appreciated.
-required PL/SQL changes
------------------------------------------------------------------------------
See the all-new, redesigned Yahoo.com. Check it out.
Other related posts:
