RE: storing blobs in database

You mentioned the main objection I have with separating the blob data into a different database: inconsistency between metadata and data (especially when you need to restore backups or switchover to the standby site).

As mentioned by others, you can speed up the daily backups by portioning your data (by time) and exclude the tablespaces (both the ones holding the actual securefiles and the ones holding the metadata) from the daily backup. Or by using incremental (cumulative) backups (especially with the block change tracking functionality).

Regards,  

Freek D'Hooge
Uptime
Oracle Database Administrator
email: freek.dhooge_at_uptime.be
tel +32(0)3 451 23 82
http://www.uptime.be
disclaimer: www.uptime.be/disclaimer

-----Original Message-----

From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Jeff Chirco Sent: dinsdag 17 januari 2012 22:20
To: Andy Klock; Gsais_at_mypalmbeachclerk.com Cc: oracle-l_at_freelists.org
Subject: RE: storing blobs in database

I am going to use SecureFiles, which is still a blob though. I forgot to mention that our main production data is part of a physical data guard environment so I am not sure if that changes anything. Also, we plan on encrypting these blobs, which SecureFiles will come in handy. And I don't need a new EE license since I plan on make the database on the same server as my main production instance. Also these pdf's will be static once they are created. I will need regular backups of this blob data, we can't afford to loose it. And I am not sure yet but it might need to be consistent with the backups on our main production database because there will be a document ID value that will be used in other applications on our main database.
--

http://www.freelists.org/webpage/oracle-l Received on Wed Jan 18 2012 - 03:06:51 CST