tailieunhanh - Client Failover Best Practices for Highly Available Oracle Databases: Oracle Database 11g Release 2

Similar to a clustered index on a table, both horizontal and vertical partitioning are non-redundant, ., they incur little or no storage overhead. Also, in the same way that only one clustering can be chosen for a table, only one partitioning can be chosen for a table. This makes partitioning particularly attractive in storage constrained or update intensive environments. Commercial systems today support hash and/or range horizontal partitioning, and in some cases hybrid schemes as well. Horizontal partitioning can be useful for speeding up joins, particularly when each of the joining tables are partitioned identically (known as a . | Client Failover Best Practices for Highly Available Oracle Databases Oracle Database 11g Release 2 Oracle Maximum Availability Architecture White Paper February 2011 Maximum Availability Architecture Oracle Best Practices For High Availability ORACLỄ Oracle White Paper - Client Failover Best Practices for Highly Available Oracle Databases Oracle Database 11g Release 2 Executive Automatic Failover for Client Applications that Support Role-Based Database OCI and JDBC Client OLE DB and ODP .Net Configuring PeopleSoft for Automatic Client Automatic Failover for Clients Applications that do not Support FAN 17 OCI Applications .17 JDBC Applications .18 Additional Considerations for Active Data Guard Initial Connections .18 Managing Existing Connections for Unplanned Additional Considerations for Data Guard SQL Client Transition during Switchover Physical standby switchover .21 Logical standby switchover .21 Considerations for Prior Oracle Oracle White Paper - Client Failover Best Practices for Highly Available Oracle Databases Oracle Database 11g Release 2 Executive Overview Oracle Maximum Availability Architecture MAA 1 is a best practices blueprint for implementing Oracle high availability technologies. Oracle Data Guard is a key component of MAA. It provides the management monitoring and automation software to create and maintain one or more synchronized standby databases to protect Oracle data from failures disasters errors and data corruptions. If a production database becomes unavailable for any reason administrators can execute either manual or automatic failover to a standby database in order to maintain high availability. This paper describes best practices to automatically transition application connections from a failed primary database to a new primary database after a Data Guard role .