|
|
|
| High
Availability Demonstrations |
demo |
Oracle Active Data Guard 11g
This demonstrates the benefits of
using a synchronized physical standby database that is open read-only
to offload ad-hoc queries and reporting from your production database,
thus achieving scalable performance and fast, predictable response
times for read-write business
transactions. Click on demo link to start the demo in your browser
using
flash and manually advance through several introductory slides.
When the actual demonstration begins it will automatically run through
to completion. Click here
for the complete MAA best practices presentation that complements this
demonstration and includes the experiences of Amazon.com with Oracle
Active Data Guard 11g.
|
|
demo |
Data Guard Fast-Start Failover
- Automatic
Database Failover for High Availability in an MAA configuration
This demonstrates automatic
failover between an Oracle RAC primary database and an Oracle RAC
standby database in an MAA configuration. Following failover, the
original primary is automatically reinstated as a standby database, and
automatically resynchronized with the new primary database. Thus
high availability and maximum data protection are achieved during a
site failure with zero manual intervention required. The
demo automatically runs in your browser when you click
on the demo link - use the
control's at the bottom of the demo screen
if you prefer to manually advance the demo. Click here
for the accompanying presentation that includes the production
experiences of Amazon.com with Data Guard Fast-Start Failover.
|
|
demo
|
Database Rolling Upgrades using
Physical Standby Databases - Oracle Database 11g
This
demonstration shows how to
easily convert a physical standby to a transient logical standby
database and effect a rolling database upgrade. The standby database
will revert to its original state as a physical standby database once
the upgrade is complete - through use of the KEEP IDENTITY clause, new
in Data Guard 11g.
This benefits physical standby users who wish to execute a rolling
database upgrade without investing in redundant storage that would
otherwise be needed to create a logical standby database. This process
utilizes SQL Apply in a very limited way - as the method to
resynchronize the standby database following its upgrade to the new
release and to maintain synchronization until it first assumes the
primary production role. The original primary database (now a
standby) is then upgraded to the new release via the redo stream using
Redo Apply (the physical standby apply process).
Click here
for the accompanying MAA best practices presentation that includes the
experiences of the United Parcel Service (UPS).
|
|
demo
|
Extended Datatype Support for
SQL Apply and Streams
Extended Datatype Support (EDS)
enables SQL Apply and Streams to replicate changes to tables that
contain datatypes not natively supported from one database to
another. Without EDS, only the tables that contain natively
supported datatypes can be replicated.
Click here
for more details in the accompanying MAA best practices paper.
|
|
demo |
Online Patching
with Oracle Database 11g
This demonstrates a patch being applied
online to Oracle Database 11g in
order to achieve continuous and
uninterrupted database service. The
demo automatically runs in your browser when you click
on the demo link - use the
control's at the bottom of the demo screen
if you prefer to manually advance the demo. Click here
for the accompanying presentation of MAA best practices and
capabilities included with the Oracle
Database to minimize planned downtime during software upgrades.
|
|
demo |
E-Business Suite Site Failure - Automatic
Application and
Database Failover
This demonstrates a completely automated
site failover for an MAA configuration of E-Business Suite Release 12
running under load. Data Guard Fast-Start Failover automates
database failover. A role change trigger fires at failover time - and
executes an E-Business Suite failover script that removes the topology,
runs AutoConfig on the database and application tiers, and restarts the
application. The network is switched via a DNS push, users are
routed to the new production site and login. The
demo automatically runs in your browser when you click
on the demo link - use the
control's at the bottom of the demo screen
if you prefer to manually advance the demo. Click here
for the accompanying presentation that provides more details of the MAA
best practices utilized in this demonstration.
|
|
demo |
Siebel 8.0 RAC Instance Failover
This demonstrates Siebel 8.0
running under load on a two-node Oracle RAC cluster. The Oracle
instance on the first node is aborted - and the demonstration shows the
surviving instance perform recovery, Siebel Servers reconnect
automatically are are routed to the surviving instance, Oracle
Transparent Application Failover reconstructs the database sessions and
users continue processing. RAC node
failure is transparent to the Siebel user. The
demo automatically runs in your browser when you click
on the demo link - use the
control's at the bottom of the demo screen
if you prefer to manually advance the demo.
Click here
for the accompanying MAA best practices presentation.
|
|
demo |
Siebel 8.0 Site Failover -
Automatic Application and Database Failover
Similar to the E-Business Suite
Site Failure demonstration above, this demo simulates site failure when
both primary RAC instances are powered down. Data Guard Automatic
Failover the transition of the standby database at the remote site to
the production role. The role change to production fires a
trigger that executes the Siebel failover script. Sieble Gateway,
Siebel Servers and Web Servers are started and client connections are
switched to the standby site through DNS push. The
demo automatically runs in your browser when you click
on the demo link - use the
control's at the bottom of the demo screen
if you prefer to manually advance the demo.
Click here
for the accompanying MAA best practices presentation.
|
|
demo
|
Siebel 8.0 - Transparent
Database Upgrade
The Siebel database is upgraded to
a new Oracle release using Data Guard SQL Apply rolling database
upgrades. First a SQL Apply standby database is upgraded to the
new release. Then Oracle Transparent Application Failover (TAF)
is used during the switchover to the upgraded database, eliminating the
need to restart Siebel. Siebel users only see a slight pause in
processing, then resume work on the new production database operating
at the new Oracle release.
Click here
for the accompanying MAA best practices presentation.
|
|
demo1
demo2
|
Data Recovery Advisor - Repair Block Corruption & Missing Files
This demonstrates how easy it is to automatically detect and repair database failures with the Data Recovery Advisor (DRA) in Oracle Database 11g. DRA eliminates the DBA time spent analyzing failures and planning an appropriate recovery strategy, by automating the entire process. The first scenario shows how DRA minimizes overall recovery time by automatically identifying block corruptions in real-time and recommending an appropriate recovery strategy. The second scenario shows how DRA facilitates with recovering a down database, by automatically detecting all missing files and recommending a recovery strategy. Click here for more information on DRA and other Backup & Recovery technologies.
|
|
demo
|
Recovery Manager - Fast Recovery with Switch to Copy
This demonstrates how to use Recovery Manager's Switch to Copy Feature to quickly use an existing image copy backup in place of a production data file, eliminating the time to restore the backup. Click here for more information on RMAN and other Backup & Recovery technologies.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Bookmark
