hi!
i have been asked to move the present oracle 9.2.0.5 production db from solaris to aix box.
Aix box is very new nothing on it, any idea how to do this.
Plz guide me.
Printable View
hi!
i have been asked to move the present oracle 9.2.0.5 production db from solaris to aix box.
Aix box is very new nothing on it, any idea how to do this.
Plz guide me.
How large is your database? How much downtime do you have to move the database? Are you using RAC, Replication, Standby server? Are you going to move the data, conduct stress test on the new database, and then move the data again to go live?
My database size is 150 gigs, used only for reporting purposes so downtime is acceptable (on weekends is ok), Not on rac or replication OR Standby .Only one instance which is up and running 24hrs.
One procedure to go ahead , I dont even know how to approach this.
export/import??
logical standby??
replication??
depends what you want to do.
I wanna go ahead with export/import.
But how to start working this project? Any idea ?
guys any procedure or docs to start working on this project? Can you suggest me from where to start working on this? Like any step by step by procedure .
Check out the Utilities documentation for all the details on export/import
http://download-west.oracle.com/docs...a96652/toc.htm
Very high level process would be something like:
Create empty DB on target OS
Full, consistent export of source database
Copy export file to target OS
Do full import on target OS
There are a few different ways to handle the "create empty DB" bit so this discussion might help you:
http://asktom.oracle.com/pls/ask/f?p...D:550622776061
HTH
export/import is may be the way to do it
logical standby can be an option as well
I would not use replication, setting replication for hundreds of tables can be tedious
the other option, probaly not considered by you but can be fun is, upgrade to 10gR2 and transport all the tablespaces
Is it not possible to put all the tablespaces in begin backup and copy all the files from solaris to aix... and apply the archives?
Or since down time is acceptable in the weekend... a cold backup of the source database... and use the files to create aix db? ... would these files be still valid across plat forms?
and what about RMAN backed up files?
cant mix files between OS's old chap
But can he rmount a drive from the AIX server, create transportable tablespaces, create a new schema, use create tablespace as select to move the data over, then migrate the transportable tablespaces to your new database on AIX?
cross platform TTS is a 10g thing is it not?
I was thinking that if the tablespace was created on an AIX partition, then it would be transportable to AIX. It was mostly curiosity.Quote:
Originally Posted by davey23uk
I feel it is easy to go ahead for export/import, But Iam afraid for 150 gigs db how much space does the exp file will occupy and how to estimate the export time for the whole db , what is best way to write the exp and imp code.
do a test and find out - only way yuu will now.
Use direct=y to make it a little quicker and export to a named pipe if you can or split across multiple files
got this while collecting info for export:Quote:
Originally Posted by davey23uk
Ensuring Sufficient Disk Space
Before you run Export, ensure that there is sufficient disk or tape storage space to write the export file. If there is not enough space, Export terminates with a write-failure error.
You can use table sizes to estimate the maximum space needed. You can find table sizes in the USER_SEGMENTS view of the Oracle data dictionary. The following query displays disk usage for all tables:
SELECT SUM(BYTES) FROM USER_SEGMENTS WHERE SEGMENT_TYPE='TABLE';
The result of the query does not include disk space used for data stored in LOB (large object) or VARRAY columns or in partitioned tables.
can you write the exact line for the exp/imp
you can estimate your export file size by using pipes and dd, export to the pipe and dd reads the pipe
I will test with pipes and I guess I have to go for schema level exp/imp Since my current db is on solaris 32 bit so .dmp filesize issues.Quote:
Originally Posted by pando
Hi,
I have not been in the forums for quite a while now , but this thread, which I got thru the newsletter got me, since I am also working on a similar project.
As Davey pointed out, cross-platform transportable tablespaces is only from 10g and is not supported in prior versions.
As you yourself have pointed out, the best way will be to do a schema level export on the Solaris box and then use Import on the Aix server. You will have to ensure that the OS is 32-bit on either side.
Another way to do the same thing would be to use a tool to create a dump file and then using SQL*Loader to load the data in the target database...but I am still experimenting with this....so am not sure of this...any suggestions folks..?
Regards,
Sriraman
Un why? EXP/IMP does not care about number of bitsQuote:
Originally Posted by donneskold
Hi,
It has got to do with the way the file headers and segment headers are organized. It is handled in 10g well. But in releases prior to 10g, while the dmp will be read, it might cause problems like fragmentation et cetera in later stages.....better to nip such issues in the bud right......?
Regards,
Sriraman
not right
Hi,
Could u pls explain?
Regards,
Sriraman
imp just doesnt care about bits and bytes at all, you can just imp from versio n to version. Its only a bunch of create / statements