Re: Clone/Migration database from Sun Solaris to AIX

As stated by others: different platform so copy files is not possible. The Oracle solution is full export - full import. Don't know the size of the database but for big databases problems can occur with the size of the dump file.
The parameter filesize can solve this problem.

I choose for another solution. I have build a script that does export and import in one stream using a fifo pipe. It runs on the machine where the new database is created empty. I create the pipe, start full export (with consistent=yes) on the remote source database to the pipe file in the background and then start a full import to the local target database (file is the same pipe file).

Pre-create the new database with only the system tablespace if datafile names do not change. Full import will recreate the tablespaces then. Pre-create all tablespaces when file names can't be the same. Install required options as SYS too in advance.

After import check differences in objects owned by sys and priviliges granted to others on SYS objects because the SYS schema is not included in any export.

Rauf Sarwar <rs_arwar_at_hotmail.com> schreef in berichtnieuws 92eeeff0.0207092057.6721a9b5_at_posting.google.com...
| vwu_at_anacomp.com (Vance Wu) wrote in message
news:<c3d4638a.0207091349.3eaaf646_at_posting.google.com>...
| > My current production database is running on Sun Solaris, I try to
| > duplicate the production database onto AIX platform.
| >
| > Is there a easy way to clone a database from Sun (Solaris 2.6) to AIX
| > (4.3) without creating new database on AIX and exp/imp the data,
| > assuming Oracle installed is same version (EE 8.1.7) in both OS
| > platforms.
|
| The easiest way is to take existing datafiles and recreate the control
| files. *BUT* since you are changing platforms...That is out of the
| question. Anything other then Exp/Imp (In my opinion) would amount to
| using a hammer to do a screw driver's job.
|
| >
| > Because the script we have for re-creating the database may not match
| > the current production database schema, from time to time more objects
| > have been added to the production database, even-though the script was
| > updated but never been tested, I'm afraid they are not identical.
|
| This should be left to your best judgment. -:)
| >
| > If re-creating the database is unavoidable, then any utility or Oracle
| > provided script that I can find to help capture the schema from an
| > existing database.
|
| Your best and perhaps the easiest bet is to do a FULL Export and
| Import.
|
| >
| > Any help would be greatly appreciated.
| >
| > Vance.
|
| HTH
| file://Rauf Sarwar
Received on Thu Jul 11 2002 - 13:39:10 CDT