Printable View
I am just looking for best and fast method to clone the database from NT to UNIX . I can't use backup control file and copy data files , since it is different OS . I can't use transportable tablespaces for the same reason . I got around 500 tables in 5 schemas . Even export/import doesn't work ,since i have to copy export file to new OS ..looking for solution ..
???Quote:
Originally posted by raghud
Even export/import doesn't work
1. U can make export, database which is on NT from NT machineQuote:
since i have to copy export file to new
OS ..looking for solution ..
2. and then perform IMP from NT machine into UNIX database Schema, so there is no OS problem in between. Hope u able to connect to database which is on UNIX m/c from NT m/c
It should work.. only take care about versions for two databases
Sameer
Hello,
I think that the only way to do that is to use export/import utilities.
I didn't understand why you said : 'Even export/import doesn't work ,since i have to copy export file to new OS '
Since my database is big . Easy way to import is , copy the file to local machine , where DB is running and start importing . Other wise I have to connect to Unix machine from nt client and have to perform import . MY DB size is 200 GB .
Since it is 200 GB Database I have to do export/import several times . I am looking for good way
Export/import is the only option to switch platforms.
Why would you need to perform export/import several times? Once will be more than enough IMHO! But it will probably take a hell lot of a time to import 200GB database....Quote:
Originally posted by raghud
Since it is 200 GB Database I have to do export/import several times.
It would be a lot easier to stay within the same platform i.e.
either go unix to unix or nt to nt. I would only go from nt to unix if it was a once shot deal in your case. Did you mean that your export is 200GB? You could do the export, zip the file, ftp it to unix, do a gunzip, and then import. This will shrink the size of the file that you are sending via ftp.
You should do 5 exports, one for each schema. This should make each export file smaller. I think that there is a way to make exports span over multiple files, but I haven't done that myself. and make sure that you take the database out of archive log during the import, have plenty of rollback, and a large temp tablespace.
I don't see any point in doing so. Why not simply perform full database export? Mind you, there are things that are exported in FULL mode but not in USER mode - what about those?. Cloning a database means creating an exact replica of the database, and the only way to do this (while switching the platform) is by doing FULL exp/imp.Quote:
Originally posted by gandolf989
You should do 5 exports, one for each schema. This should make each export file smaller.
Regarding the size of the dump file: as gandolf989 allready pointed out, you can make export dumping data into many smaller files.
This is the syntax send to a compressed file using pipes. I do this often.
To export to a compressed file:
/etc/mknod pipename p
compress < pipename > newfilename.Z &
exp/ file=pipename
To import from a compressed file:
/etc/mknod pipename p
uncompress < newfilename.Z > pipename &
imp/ file=pipename
rm -f pipename