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?
Printable View
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