Do i need sames OS for standby database?

Question

Im planning on implementing a stand by database for my production db, and i have a few questions.-
1.- Do i need to have the same os?
2.- Do i need a license for a standby db?
Thanks

Answer 1

elvyscruz wrote:
Im planning on implementing a stand by database for my production db, and i have a few questions.-
1.- Do i need to have the same os?It depends on version which you don't tell us. For 11g no ([http://download.oracle.com/docs/cd/B28359_01/server.111/b28294/standby.htm#i72053]) for other versions basically yes, though you will likely get away with small point differences in os version). I'd argue that for best practice for physical standby the answer is yes, not least since you'll likely want to do role switchover as part of your operational requirements - changing OS at the same time as Role switchover just adds unnecessary complexity.
2.- Do I need a license for a standby db?
Yes. See the OLSA at [http://oraclestore.oracle.com/OA_HTML/ibeCCtpSctDspRte.jsp?section=11365&media=os_local_license_agreement] especially
>
Failover: Subject to the conditions that follow below, your license for the following programs, Oracle Database (Enterprise Edition, Standard Edition or Standard Edition One), Oracle Database Enterprise Edition Options, Oracle Internet Application Server (Enterprise Edition, Standard Edition, Standard Edition One or Java Edition), Oracle Internet Application Server Options, Business Intelligence Suite Enterprise Edition Plus, Business Intelligence Server Enterprise Edition, Business Intelligence (Standard Edition or Standard Edition One), WebLogic (Server Standard Edition, Server Enterprise Edition, Suite, Suite Options or Application Grid), Tuxedo and Adapters, Oracle Enterprise Repository, Entitlements Server, Entitlements Server Security Module, Directory Services, Identity Federation and those programs with “BEA” in the program name includes the right to run the licensed program(s) on an unlicensed spare computer in a failover environment for up to a total of ten separate days in any given calendar year (for example, if a failover node is down for two hours on Tuesday and three hours on Friday, it counts as two days). The above right only applies when a number of machines are arranged in a cluster and share one disk array. When the primary node fails, the failover node acts as the primary node. Once the primary node is repaired, you must switch back to the primary node. Once the failover period has exceeded ten days, the failover node must be licensed. In addition, only one failover node per clustered environment is at no charge for up to ten separate days even if multiple nodes are configured as failover. Downtime for maintenance purposes counts towards the ten separate days limitation. When licensing options on a failover environment, the options must match the number of licenses of the associated database. Additionally, when licensing by Named User Plus, the user minimums are waived on one failover node only. Any use beyond the right granted in this section must be licensed separately. In a failover environment, the same license metric must be used for the production and failover nodes when licensing a given clustered configuration.
Edited by: Niall Litchfield on Sep 8, 2008 2:14 PM
Edited by: Niall Litchfield on Sep 8, 2008 2:15 PM