RE: Real life implementation of 7 year data retention requirement

From: Ruel, Chris <>
Date: Thu, 13 Feb 2014 21:54:18 +0000
Message-ID: <>

I’ll add that if you are on Flashback Data Archive is included with the EE license. You just can’t use it in conjunction with Advanced Compression...unless of course you license AC.

From the license doc:

For releases earlier than Oracle Database 11g Release 2 ( You must license the Oracle Advanced Compression option to use Flashback Data Archive (formerly known as Total Recall).

Beginning with Oracle Database 11g Release 2 ( You must license the Oracle Advanced Compression option to use Optimization for Flashback Data Archive history tables. Basic Flashback Data Archive—without history table optimization—is available in all editions.

Chris Ruel * Oracle Database Administrator<> * Desk:317.759.2172 * Cell 317.523.8482

From: [] On Behalf Of Kevin Jernigan Sent: Thursday, February 13, 2014 4:33 PM To:; Cc:;;; Subject: Re: Real life implementation of 7 year data retention requirement

As the PM for Flashback Data Archive (FDA), I strongly agree with your suggestion to use FDA to keep track of all changes to data over time ;-) This will give you easy Flashback Query access to view your data AS OF any point in time back to "the beginning of time" (i.e. whenever you enabled FDA on the underlying tables).

Now you might be saying "Wait a minute, that's a lot of disk space / expense / etc!" And you might be right - but you can use compression, partitioning, and even HCC on Oracle Storage to keep the older FDA-managed history data online in cheaper / denser storage, while transparently keeping the more recent (usually hotter) data on Tier 1 storage etc etc. And, the question is always "What's the value to the business of having online access to the historical data using Flashback Query?" versus the slower more complex approach of restoring the right backup, rolling forward to the right point in time, etc etc...



Kevin Jernigan

Senior Director Product Management

Advanced Compression, Hybrid Columnar

Compression (HCC), Database File System

(DBFS), SecureFiles, Database Smart Flash

Cache, Total Recall, Database Resource

Manager (DBRM), Direct NFS Client (dNFS),

Continuous Query Notification (CQN),

Index Organized Tables (IOT), Information

Lifecycle Management (ILM)

+1-650-607-0392 (o)

+1-415-710-8828 (m)
On 2/13/14, 12:50 PM, Freek D'Hooge wrote: But not a history of how a record changed through time.

I think the reasoning behind the restore to any point between now and 7 years back is the need to be able to show what a record looked like x time back. If so, maybe flashback data archive and / or auditing could be used to fulfil such a requirement?

Freek D'Hooge
Exitas NV
Senior Oracle DBA
email:<> tel +32(03) 443 12 38<>

On do, 2014-02-13 at 21:36 +0100, Frits Hoogland wrote: Just as a bold statement, and something to think about: isn't your most recent backup a complete backup of all the history contained in your database?

Frits Hoogland<> Phone: +31 20 8946342

(Sent from my iPhone, typo's are expected)

Op 13 feb. 2014 om 21:13 heeft Paresh Yadav <<>> het volgende geschreven:

Thank you David, Rich, Frits, and Johnson for your useful replies.

The point about compatibility and cost is very important. Isn't it necessary by law with so many businesses to retain 7 years of data? What do people do in this case? In many places that I know of (including fortune 100 organizations) there is a 7 year retention policy for backup in place but as I had mentioned God only knows what actually happens to those tapes. At times I have asked to test a restore from backup taken long time a go but no one wants to open that can of worms.


On Thu, Feb 13, 2014 at 1:44 PM, Johnson, William L (TEIS) <<>> wrote: I may be kicked off this list for making this comment...but I would look into a simple Hadoop cluster to store the data...I am not sure if your data is written once and done - or if you update it frequently, but there is a lot to be said for the cost/TB and the ability to store data long term in a Hadoop cluster. Bill

-----Original Message-----
From:<> [<>] On Behalf Of Rich Jesse Sent: Thursday, February 13, 2014 12:36 PM To:<> Subject: Re: Real life implementation of 7 year data retention requirement

Paresh writes:

> period (say 6 or 7 years from "now") (e.g. challenges in locating the
> tapes (physical or virtual), rman catalog not having record of backup
> pieces for the time period etc.). Does magnetic tape remain good for 7
> years in a climate controlled environment or you do copy them after 3
> years or so to a new tape? If yes, is this automated as manual process
> will be too much cumbersome and prone to errors.

And don't forget about compatibility. For example, an LTO-3 tape written 7 years ago won't be able to be read on an LTO-6 drive -- a very plausible timeline example.




Notice of Confidentiality: **This E-mail and any of its attachments may contain Lincoln National Corporation proprietary information, which is privileged, confidential, or subject to copyright belonging to the Lincoln National Corporation family of companies. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. Thank You.**

Received on Thu Feb 13 2014 - 22:54:18 CET

Original text of this message