Export 400gb database - urgent Help

Hi,

I have sun solaries and oracle 9i database.I need to export 400gb Production database to import on test database server(it can be done with backup).

My question:
1) Is it feasible to export 400gb database?
2) What will be the size of export dump file?
3) Will it affect by unix file size limit?
4) What long will it take .guess only on normal basis as it depends on lot of parameters. I agree.
5) How long will it take to ftp? only guess
6) What are the parameters need to consider for import on test seerver?
7) What is raw device?can we use it for export or import?
8) Same size database restore on new test server with backup? how long will it take for ftp and restore and database availability time.

I can understand with limited information it will not be nice to give correct answer. I need some reference point.nothing is hard and fast.

Thanks a lot in advance. I would appreciate your help asap.
Deep

1) Is it feasible to export 400gb database?

400Gb is practically too big for an export.

2) What will be the size of export dump file?

ummm 400Gb??

3) Will it affect by unix file size limit?

yes

4) What long will it take .guess only on normal basis as it depends on lot of parameters. I agree.

hours and hours (days?)

5) How long will it take to ftp? only guess

depends how quick your network is

6) What are the parameters need to consider for import on test seerver?

if you got a spare few days to wait

7) What is raw device?can we use it for export or import?

if you dont know what a raw device, you dont want to know

8) Same size database restore on new test server with backup? how long will it take for ftp and restore and database availability time.

how long is a piece of string?


heres a better idea for you. If it is the same OS on the other server (which I assume it is due to it being a test server) then shutdown your database, copy all the database files to your new server, backup the control file to trace then recreate the database from there - no export and no import and a whole lot of saved time

Quote:

---

Originally posted by dcmumbai
Hi,

My question:
1) Is it feasible to export 400gb database?

---

No.

ok did anyine give any thought to much data is actually contained in them there data files?

maybe it's smallish, maybe the export will only turn out to be 20gb
or something

Quote:

---

Originally posted by stmontgo
ok did anyine give any thought to much data is actually contained in them there data files?

maybe it's smallish, maybe the export will only turn out to be 20gb
or something

---

Hee hee good call Stmotgo.. 20 gig tablespace with only 200 meg used. tell me you haven't seen that before?!

Quote:

---

Originally posted by OracleDoc
Hee hee good call Stmotgo.. 20 gig tablespace with only 200 meg used. tell me you haven't seen that before?!

---

or maybe a 8gb database that fits into a 116m dump file......?


SQL> select sum(bytes/1024/1024/1024) GB from v$datafile;

GB
----------
7.97167969

host exp system/manager file=c:\temp\myexport.dmp full=y
.
.
.
Export terminated successfully without warnings.

SQL> host dir c:\temp\*.dmp
Volume in drive C has no label.
Volume Serial Number is 9C16-6AC4

Directory of c:\temp

09/28/2003 11:11 PM 122,112,000 myexport.dmp
1 File(s) 122,112,000 bytes
0 Dir(s) 13,340,061,696 bytes free

SQL>

Hi,

If your test and production environments are homogeneous then you can use the trasport tablespace facility provided in export utility in oracle 8i and above.

In case of trasnport tablespace export just takes dump of metadata related to tablespace you are exporting and you just need to copy data files accross to test environment and sync them using import.

In this case ftp make take a little longer but you can try zipping them and transfer the files to test environment.

Thanks

Just go through the following note on metalink to find out the size of the export dump without creating the dump file. This will help you decide whether to export or not to export.

http://metalink.oracle.com/metalink/...&p_id=106465.1

Unless you have complicated file structure, you can just install Oracle on a test box and copy all data, control and log files into the same location and just start the database on the test box.

Venu

It is possible to export 400 GB DB. Our group did 600 GB export during the conversion project and imported back again into the database.


All you need is many disks under different controllers with a stripe size of 1MB. For example, if you have 48 disks (each size is 8 GB) , then form 8 disks group so that you get 6 disk groups. The stripe size per disk could be 1 MB. These are the target devices for storing your export dump files.

Enable Large file system on the backup file system. If not possible, use filesize parameter in the export.

Now Look your tablespaces (datafiles). Create 16 parameter files that can be used for the export. Choose the tables while forming the group in such way that READ contention will not occur.
Fire 16 exports thru shell scripts using 16 parameters files. Each dump file goes to different target devices, then it get compressed.

We do not do this exercise daily.
The best option is either BMC SQL*BACKTRACK or RMAN.

Good Luck.
Tamil

Transportable tablespaces..

I would use vbadba's method.
I did this a year ago.
What I did was, compressed all files(130gig) and ftp(from London to New York,used 14 hours) to test machine, and uncompress and recreted control file and bring up the database.(it would take 7 days plus to use imp to import into our test database). This way is much faster than doing export and import. Of course, depending how long you can afford to shutdown your production database, you could always use export and import, but you would encounter more issues, like file size limit on your O/S etc. We did this over the weekend and did not affect business.

Making export of such big database and to be able to support option "consistent=y" you have to have big ROOLBACK segments.

Hi Guy's ,

Thank you very much for your help.I had skipped the imp/exp option and used cold backup.

Once again thank you very muck.
dcmumbai

Quote:

---

Originally posted by dcmumbai
Hi Guy's ,

Thank you very much for your help.I had skipped the imp/exp option and used cold backup.

Once again thank you very muck.
dcmumbai

---

You should have cloned that database with RMAN. Much quicker.