Re: Re Oracle Licensing

From: Stefan Knecht <knecht.stefan_at_gmail.com>
Date: Wed, 14 Nov 2018 22:30:37 +0700
Message-ID: <CAP50yQ-Ej=w4TaPwRYpCYfyPCCfsa+-tZROntN3o_5QUgK4eWw_at_mail.gmail.com>



Your primary is on x86 and your failover host is on POWER? Aren't they different endianness?

Does that work?

On Wed, Nov 14, 2018 at 9:30 PM Rich J <rjoralist3_at_society.servebeer.com> wrote:

> On 2018/11/13 21:56, post.ethan_at_gmail.com wrote:
>
> I recall the guidelines here also. I knew of a customer who kept the
> oracle home tar gzd (nothing installed). Backups shipped over the wire
> slowly to DR DC once per week. Archive logs shipped every 20 minutes. All
> rsync. Worked very well. Was simple and reliable. We would test the system
> twice a year and DB would only be running for a couple hours. Per the
> customer's understanding this was all 100% legit and within bounds.
>
> I had argued that since our DR site is only storage until we fail over
> that the binaries are not -- *CANNOT* -- be "installed". Oracle
> respectfully disagreed, saying the binaries are in the DR site, even though
> the architecture of the DR replicating servers (x86) does not match the
> architecture of the binaries (POWER) and therefore cannot be "installed".
>
> Instead of bringing legal into it, we exclude replication of the
> binaries. The Oracle installation is part of our DR failover process, with
> all of the implied complexities.
>
> My $.02,
> Rich
>

-- 
//
zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
Visit us at zztat.net | _at_zztat_oracle | fb.me/zztat | zztat.net/blog/

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Nov 14 2018 - 16:30:37 CET

Original text of this message