RE: Dumping contents of a view to CSV file
Date: Thu, 27 Oct 2011 09:31:00 +0200
Why are you dumping the content to a text file? Would it not be easier to just create a table of that view and then use exp to export that table out of the database?
Unless you are switching to a different rdbms, I don't realy see a benefit of a 440GB text file over an oracle export file. It is not that someone will just open the file in notepad to have a quick look at it...
Oracle Database Administrator
tel +32(0)3 451 23 82
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Steve Wales Sent: donderdag 27 oktober 2011 0:00
Subject: Dumping contents of a view to CSV file
I've been tasked with generating a CSV file with the contents of a view in an old database as an extra copy before the DB is decommissioned.
I've done this in the past for smaller tables or views without issue.
There are 80 million rows in the view, full row length is 5500 bytes (most probably shorter since the columns on the base tables are mostly varchar2).
Doing the math on that, that's a maximum possible size of 440GB.
I had seen a stored procedure on a website somewhere that read through a cursor and dumped the records out to a text file via utl_file.put. Anyone have a better method or is that my best option ? I've had some TEMP tablespace failures, I may just need to allocate a bunch of space in temp, kick it off one afternoon and let it run overnight.
I've could shrink the overall output size of the file by running "trim" on the columns too.
Any ideas appreciated.
Environment: Oracle 18.104.22.168 on HP-UX 11.11
http://www.freelists.org/webpage/oracle-l Received on Thu Oct 27 2011 - 02:31:00 CDT