Skip to Main Content
  • Questions
  • Migration of about 20000 Tablespaces from Solaris Sparc 10 with Oracle 9.2.0.4 to OL 7.2 64bit Oracle 12c

Breadcrumb

May 4th

Question and Answer

Connor McDonald

Thanks for the question, Siegfried.

Asked: July 13, 2016 - 8:53 pm UTC

Last updated: July 20, 2016 - 11:24 pm UTC

Version: 9.2.0.4

Viewed 1000+ times

You Asked

Hello Tom
we plan a migration of our production system.
we think we have two possibilities

1) one is from the 9i system exporting all TS's with exp and go directly to the 12c and do with imp
all tablespaces in the new database
but this option does not work I guess because of the differnt endianess of Solaris sparc 10 and OL 7.2 and because of the not working direct connection between 9i and 12c

2) the second will be: to run a backup on 9i, do the restore of this backup on a migration database on another solaris sparc system
set all 20000 Ts's offline; start the database; run an backup of migration system; do an update to 10g on this migration system
and insert in migartion system in sections of 1000 Ts's , expdp this tablespaces with transportable and convert them wih RMAN in 10g

Is option 2) a possible way?

BR
Siegfried

and Connor said...

With (1), you didnt specify whether you mean to use export for the *data*, or use export to generate a transportable tablespace set. I'm going to assume the latter, in which case, you cant go from 9i to 12c, because the datafiles do not have enough information on them for the conversion. You need to be on at least 10g for that.

http://docs.oracle.com/cd/B28359_01/server.111/b28310/tspaces013.htm#i1007244


With (2), I think you will need to at least open the database once with compatible set to 10 or higher, so that can be stamped into the datafiles. Otherwise, they'd still be marked as 9i and I think you'll be stuck with the same issue as (1). But other than that, I think the approach is valid. So it would look something like:

- upgrade 9i to 10g with compat = 9
- shutdown 10g
- open 10g database with compat = 10
- shutdown 10g

and at this point, you can commence the cross-platform migration.

MOS Note Doc ID 1389592.1 and http://www.oracle.com/technetwork/database/features/availability/maa-wp-11g-platformmigrationtts-129269.pdf are both excellent notes on the cross-platform migration.

Rating

  (2 ratings)

Is this answer out of date? If it is, please let us know via a Comment

Comments

I need further details about the speed!!

Siegfried Ley, July 15, 2016 - 12:08 pm UTC

Hello,

thank you.

I need details to speed. how long does it last to run an upgrade to 10g on a v880 with 20000 tablespaces?

how long does it last to convert the 20000 tablespaces with rman to little endianess?

how long does it last to expdp the 20000 tablespaces on v880 ora10g?

how long does it last to impdp the 20000 tablespaces on a ora linux 7.2 with ora 12c?

many thanks in advance
BR
Siegfried


Connor McDonald
July 16, 2016 - 4:52 am UTC

An upgrade is typically unrelated to the size of the database, because it is predominantly the dictionary objects that are upgrade. Of course, if you have millions of objects in the database, then this could have an impact.

Converting tablespaces with RMAN is a read-entire-file-write-entire-file operation, so I'd expect it to be similar to the time/cost to backup the entire database.

But in all of these cases, no matter what *I* tell you, to get the best estimates for timings is for you to do some benchmarking on your own system.

another question in this case

A reader, July 18, 2016 - 9:39 am UTC

Ok i will talk about opion 1 because our team will favor this option! because we will switch to 12c and powerful machine as soon as possible.

let me repeat option 1: one is from the 9i system exporting all TS's with exp and go directly to the 12c and do with imp
all tablespaces in the new database
but this option does not work I guess because of the differnt endianess of Solaris sparc 10 and OL 7.2 and because of the not working direct connection between 9i and 12c.
Doing:
1.export them on 9i with exp .. transportable_tablespace=Y
2.copy datafile to 10g (same endianess),
3.import with imp .. transportable_tablespace=Y
4.exp them on 10g .. transportable_tablespace=Y
5. copy datafile to 12c
6.imp it in 12c .. transportable_tablespace=Y
Does this present a possible way?
BR
Siegfried
Connor McDonald
July 20, 2016 - 11:24 pm UTC

Yes - on the assumption that you are doing the endian conversion as part of your 10g =>12c.

More to Explore

Data Pump

All of the database utilities including Data Pump are explained in the Utilities guide.