Re: TDE shared wallet

From: Jeff Chirco <backseatdba_at_gmail.com>
Date: Fri, 6 Mar 2015 16:30:12 -0800
Message-ID: <CAKsxbLqCpa35CkhDp66EXLASkED+wCaKkGQVFA0UWDE39ZbwfQ_at_mail.gmail.com>

Oh yeah right Standby. I to have a physical standby database (not Active) where I just copy over the wallet file anytime there is changes.

On Fri, Mar 6, 2015 at 2:59 PM, MARK BRINSMEAD <mark.brinsmead_at_gmail.com> wrote:

> Surely, it must be supported. Unless Active Dataguard is not supported
> with TDE tablespaces, you would need to have common encryption keys between
> your primary and standby databases.
>
> This is not a "shared" wallet, of course. Just a "wallet copied and held
> in common". :-)
>
> I wonder what sort of hidden risks there might be, though? What events
> would require you to refresh copies of the wallet? Is there a possibility
> of conflicts?
>
>
>
> On Fri, Mar 6, 2015 at 4:12 PM, Jeremy Schneider <
> jeremy.schneider_at_ardentperf.com> wrote:
>
>> On Fri, Mar 6, 2015 at 4:05 PM, Job Miller <jobmiller_at_yahoo.com> wrote:
>> > If there are multiple Oracle Databases installed on the same server,
>> they
>> > must access their own individual TDE wallet. Sharing the same wallet
>> between
>> > independent instances is not supported and can potentially lead to the
>> loss
>> > of encrypted data.
>>
>> ok, copies only - i was aware of the problems/risks with shared
>> wallets. original question still stands though...
>>
>> --
>> http://about.me/jeremy_schneider
>> --
>> http://www.freelists.org/webpage/oracle-l
>>
>>
>>
>

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

Received on Sat Mar 07 2015 - 01:30:12 CET