Re: TDE shared wallet

Of course, that which is valid for a physical standby is not necessarily valid for any-old-clone. But it might be.

(Physical standbys are a special case, after all. Same DBNAME, same DBID, same SYS password, ...)

On Fri, Mar 6, 2015 at 7:30 PM, Jeff Chirco <backseatdba_at_gmail.com> wrote:

> 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