Re: How do you refresh your databases?

  Luckily it is possible for us (referential integrity-wise) to just ignore that table and be done with it, so the skip tablespace option looks good. However, if we had referential integrity issues, this would not be the case and data masking would be our only option.

Cheers
Alan.-

On Wed, Mar 23, 2011 at 1:10 PM, Niall Litchfield < niall.litchfield_at_gmail.com> wrote:

> I see you've got good answers on how to exclude the PCI data, other than
> the data masking pack or third party data masking applications I've not seen
> any suggestions on how to copy *and change* the PCI data.
>
> On Tue, Mar 22, 2011 at 8:00 PM, Guillermo Alan Bort <cicciuxdba_at_gmail.com
> > wrote:
>
>> List,
>>
>> We have to refresh a QA database from production (to have some real
>> data) but we need to exclude all the PCI/PII from the refresh (it absolutely
>> cannot be copied from Prod to QA). In addition, we have GG replication on
>> Prod so anything we do is subject to that.
>>
>> What would be your approach?
>>
>> My idea was rman duplicate, but those pci/pii tables rule this out.
>>
>> Oh, GG cannot be used due to firewall restrictions, we only have database
>> ports and SSH from Prod to QA
>>
>> any ideas?
>> Alan.-
>>
>
>
>
> --
> Niall Litchfield
> Oracle DBA
> http://www.orawin.info
>

--
http://www.freelists.org/webpage/oracle-l