Migration of oracle 10g from AIX 5.3L to Windows 2003 or 2008

Dear All ,
 
We are planning to migrate or deploy  Oracle 10g from AIX 5.3L to Windows 2003 or 2008 for testing purpose.  In short an exact copy of the database on Windows Server.
My database size is 99 GB .

AIX Version 5.3L
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 64bit

I know that it can be done using datapump or imp/exp. I need step by step information to migrate from aix to windows.
oraclescsaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Richard OlutolaConsultantCommented:

The best thing is:

1. Export only schemas of interest from AIX (excluding any system schemas)

2. create your virgin database on Windows.
3. Create tablespaces as desired for the schemas on Windows
4. Create users that will become the schemas exported from AIX. Assign the tablespaces to the users
5. Import the exported schemas into Windows users that you created.

Don't forget to specify logfile for the import job so that you can spot any issues post-import.

R.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sdstuberCommented:
as you said, you can do it with data pump easily.

First - use dbca, create your database first.
Second - create all tablespaces you will need, you need to do this step manually rather than importing since your windows paths will be different than your AIX paths.
Third - create a database link from your new database to your old one.  The user on the old db must have the EXP_FULL_DATABASE role
Fourth - create a directory on your windows server (change the path as needed)

CREATE OR REPLACE DIRECTORY DATA_PUMP_DIR AS  'c:\oracle\your\path\dpdump\';

Open in new window


Fifth - run the script below  on your new database as a user with the IMP_FULL_DATABASE role, make any name/path changes as needed
declare
   v_handle NUMBER;
   l_state VARCHAR2(20);
BEGIN
   v_handle :=
   DBMS_DATAPUMP.OPEN (operation   => 'IMPORT',
                       job_mode    => 'FULL',
                       remote_link => 'AIX_LINK'  -- change this link to whatever link you created
                               );

   dbms_datapump.add_file(handle => v_handle,
                          filename => 'your_import.log',  -- change this to whatever file name you want
                          directory => 'DATA_PUMP_DIR',  -- change this to whatever directory you created earlier
                          filetype=>3); 

   DBMS_DATAPUMP.set_parallel(v_handle, 4);

   DBMS_DATAPUMP.start_job (v_handle);

   -- you can uncomment the WAIT line if you want it to run in the foreground
   --DBMS_DATAPUMP.WAIT_FOR_JOB (v_handle, l_state);
END;

Open in new window

Mark GeerlingsDatabase AdministratorCommented:
What kind of disk system do you have for the Windows server?  You should *NOT* use only local SCSI or SATA disks that are all in one RAID5 array!  Oracle on Windows will perform *MUCH* better if you have some RAID1 (or RAID10) disks for the system, undo, data and index tablespaces as well as the on-line redo logs.  The temp tablespace, the Windows swapfile and archived redo logs could (or should) be on RAID0 or a non-RAID disk.  The Windows and Oracle executables can be on RAID5 if you like.
oraclescsaAuthor Commented:
Dear Markgeer,

We are using RAID 1 system. There is no issue with the performance as this system is going to be a testing system. I am trying to follow the above methods which was suggested by above experts.
Mark GeerlingsDatabase AdministratorCommented:
OK, you should be fine then.  One other thing you may want to check or change is the archivelog mode in the new Windows database.  Set that to "noarchivelog" while you do the intial database configuration and the import.  Then if you want it in archivelog mode after that, do a shutdown and a backup and switch the archivelog mode.  But having archivelog mode on while you do the import will slow down the import considerably.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.