Re: 8.1.7.4 upgrade - 10g or 11
- From: "Jared Still" <jkstill@xxxxxxxxx>
- To: Brandon.Allen@xxxxxxxxxxx
- Date: Wed, 16 Apr 2008 10:38:57 -0700
On Wed, Apr 9, 2008 at 10:27 AM, Allen, Brandon <Brandon.Allen@xxxxxxxxxxx>
wrote:
>
> I'd recommend you create a new database and migrate via exp/imp rather
> than doing an in-place upgrade. There is at least one nasty bug with
> upgrades to 10.2.0.3 and last time I checked the only solution was to
> use exp/imp or just stay on 10.2.0.2 instead, although it may be fixed
> in 10.2.0.4 now.
>
>
I'll go along with that.
We have SAP databases that we are migrating from 9i to 10g.
We've run into some rather nasty bugs for which there is no fix in 10.2.0.2
We were waiting for a backport of the bug fix from 10.2.0.3, but we are
now going to exp/imp the data into a new database.
(SAP is not certified for 10.2.0.3, and never will be 10.2.0.4 not yet
available
for SAP)
These particular SAP databases were migrated from 8i to 9i previously.
This just complicates problems.
SAP support has documented that databases migrated from 8i to 10g are
fraught with problems.
If at all possible, consider building a new database.
We are going to use the SAP utilities for this (forget the name) which are
more
like unload/load via SQL Loader than exp/imp.
An 800 gig database would take a very long time to export and import with
exp/imp.
On other thing to note: if you have created any views in the sys schema on
X$ tables,
drop them before the migration.
Here's what can happen:
View created on x$ table in 8i database
migrate db to 9i
some x$ tables no longer exist on the newly migrated db
the views on the now defunct $x tables remain
attempts to drop the views will result in ORA-600 [16206]
all attempts to drop the view will fail.
Not fatal, but rather annoying.
--
Jared Still
Certifiable Oracle DBA and Part Time Perl Evangelist
Other related posts: