Juan Loaiza Senior Vice President, Oracle System Technology

Juan Loaiza Senior Vice President, Oracle System Technology
Oracle’s High-Availability Vision: What’s New in Oracle Database 11g Release 2 Juan Loaiza Senior Vice President, Oracle System Technology

Oracle High Availability Architecture
Scale-Out & Low-Cost High-volume hardware All components active Application Oriented Protect and recover application objects Enable online application changes Integrated & Simple Availability integrated into all components Automated Complete & Open Handles all planned and unplanned downtime Pluggable components

Oracle’s Database HA Unplanned Downtime Planned Downtime
Server Failures Unplanned Downtime Data Failures System Changes This slide is useful in two critical aspects. Firstly – it shows you how Oracle Database’s HA solutions are available in an integrated manner, as built-in features of the Oracle Database. So – if you have an Oracle Database – you have all of these capabilities available to you. No extra integration is required. The other thing this slide shows is to provide you with some guidance regarding a step-by-step approach to HA. If you are looking at re-architecting your HA configuration, it’s probably not a good idea to configure all these solutions at the same time. Maybe minimizing planned downtime is a higher priority to your data center than safeguarding for unplanned failures. If that is the case, you start with the solutions in the planned downtime category. Once that is tested and implemented, you can start looking at other areas. Planned Downtime Data Changes App Changes

Best-of-Breed Server Protection At Lowest Cost
Server Failures Real Application Clusters (RAC) Unplanned Downtime Data Failures System Changes Planned Downtime Data Changes App Changes

Real Application Clusters
HR SALES ERP Scale workloads across multiple low cost servers Consolidate into fewer servers and databases Runs all Oracle database applications Built-in HA

RAC One Node Virtualization Benefits for Oracle Databases
New in 11.2 RAC One Node Virtualization Benefits for Oracle Databases A virtualized single instance database Omotion - live migration of instances across servers Move services, then shutdown transactional Built-in cluster failover for high availability Better than OS level virtualization Rolling database patches Manage fewer Operating Systems 10 DBs on a node does not mean 10 Operating Systems to manage Rolling OS upgrades

Best-of-Breed Data Failure Protection At Lowest Cost
Data Corruptions Storage Failures Site Failures Human Errors Server Failures Unplanned Downtime Flashback RMAN Oracle Secure Backup ASM Data Guard Streams Data Failures System Changes Planned Downtime Data Changes App Changes

Flashback Technologies Error Detection & Correction
Traditional Recovery Flashback Technologies Error Detection & Correction Flashback revolutionizes error recovery View ‘good’ data as of a past point-in-time Simply rewind data changes Time to correct error equals time to make error Recovery Time Flashback Correction Time = Error Time + f(DB_SIZE) Low impact, easy – simple commands, no complex procedure Flashback Query, Table, Transaction, Database, Drop SQL> flashback database to <timestamp>; Enhancements in 11.2: Flashback database performance & monitoring optimizations Flashback archive support for schema evolution Flashback enables easy navigation through time See all rows at a given time See all changes to a row See all changes made by a transaction Flashback enables easy correction of errors Row level Table level Database level Flashback applies to all types of users End users Developers Administrators Flashback is much faster and easier than traditional recovery ================= Flashback impact The environment for the OLTP < 2% overhead (actually < 1% in my tests) was a single instance database running the Swingbench Order Entry workload with on Linux 32-bit, RHEL ( ELhugemem) and the I/O subsystem was: Array Serial # Disks Memory EMC Clariion CX700 # Trays - 15 disks per Tray - 73Gb 4Gb per SP (512Mb Read Cache / 2631Mb Write Cache) EMC Clariion CX500 # Trays - 15 disks per Tray - 73Gb 2Gb per SP (365Mb Read Cache / 1107Mb Write Cache) where the cx700 was the data ASM disk group and the cx500 was the ASM flash recovery area disk group. So the FRA had 28 spindles. Other qualitative reasons for low FB logging impact: - Only one before-image is logged per 30 min interval, regardless of number of changes to the block - No extra block reads are required when writing to flashback logs (note: except for direct insert loads, which is fixed in 11.1 for single instance) - Only data file block changes are tracked, not all database files (e.g. online redo, controlfile, etc.) - In general, no process needs to wait for flashback log I/O in a well configured OLTP system. New in 11.2

Oracle Backup & Recovery Integrated Disk, Tape & Cloud Backup
Oracle Enterprise Manager Recovery Manager (RMAN) manages Database Backup & Recovery Oracle Secure Backup Intrinsic knowledge of database file formats and recovery procedures Block validation Online block-level recovery Unused block compression Online, multi-streamed backup Native encryption RMAN Tape Drive Recovery Manager (RMAN) – ensures valid backup & restore Always verifies block checksums on backup & restore Provides optional logical block validation (e.g. missing row piece) Checks on-demand for backup / restore corruptions without creating backups / restores (BACKUP VALIDATE / RESTORE VALIDATE) Provides online recovery of individual block corruptions or all identified corruptions with Block Media Recovery (RECOVER BLOCK) Fast Recovery Area Cloud Data Files

Multiple RMAN Compression Levels More Cost Savings
New in 11.2 Multiple RMAN Compression Levels More Cost Savings Backup compression: popular way to save on storage Multiple RMAN backup compression levels Choose between compression levels & backup throughput [BASIC] | HIGH | MEDIUM | LOW LOW - corresponds to LZO (11gR2) MEDIUM - corresponds to ZLIB (11gR1) BASIC - corresponds to BZIP2 (10g style compression) HIGH - corresponds to GZIP (11gR2)

Tape Backup for Oracle Environment Virtual Tape Library (VTL)
Oracle Secure Backup Enterprise Tape Backup Management Oracle Enterprise Manager Tape Backup for Oracle Environment Built-in Oracle Integration 25 – 40% faster than leading competition 4X less expensive than comparable products Supports Oracle Database 11g through Oracle9i Oracle Secure Backup Oracle Database RMAN Integration File System Data Oracle Secure Backup is centralized tape backup management software protecting the Oracle database and file systems in distributed UNIX, Linux, Windows and Network Attached Storage (NAS) environments. From one central console, you can easy manage the distributed servers and tape devices within the backup domain. As Oracle is no longer just a database company, Oracle Secure Backup provides tape backup for application files as well as the database. Integrated with Recovery Manager (RMAN), Oracle Secure Backup provides the media management layer for RMAN backups to tape. Complete data protection for your entire environment, OSB provides an alternative to expensive media management products increasing ROI for your customers Oracle investment. Using OSB, tape backup management is automated through user-defined policies through the life cycle of the backup tape from first write to tape duplication (if any) to rotation between multiple locations (vaulting) and finally re-use when upon expiration of the tape. File system and database backup may be encrypted per user-defined policy or on a one-off basis using OSB native encryption capability or LTO-4 tape drive encryption….OSB seamlessly manages encryption keys for both native encryption or hardware (LTO-4 drives). OSB is integrated with Enterprise Manager 10gR2…With EM Grid , both OSB file system backup operations, database backup operations and media management can be managed through Grid. In addition to EM, OSB backup management may be managed using a command line interface or native web tool. Oracle database backups provide the fastest database backup to tape (about 25 – 40 % faster) due to optimizations, particularly: Unused block compression: Only used data blocks are backed up (Oracle Database 10g R2) Backup undo optimization: Only "active" undo data is backed up (Oracle Database 11g R1) NOTE: OSB supports 6 platforms and 3 NAS devices. Virtual Tape Library (VTL) Tape Library

Oracle Secure Backup Cloud Module Offsite Database Backups in the Cloud
Database Files / Fast Recovery Area RMAN Oracle Secure Backup Cloud Module Amazon S3 Compression / Encryption Oracle Secure Backup Cloud module: Backup databases to Amazon Cloud Complements local disk and/or tape backup Eliminates IT management overhead of a disaster recovery site Works with Oracle9i R2 and higher DB versions

Automatic Storage Management (ASM) Stores & Manages All Data
Database Application 3rd Party FS ASM Disk Group ASM dynamic volume manager supports file systems ASM directly supports Clusterware files – Cluster Repository, Voting Disk Built-in mirroring protects from disk failures Enables auto-repair from corrupt blocks using a valid mirror copy

ASM Cluster File System Oracle Management of File System Data
New in 11.2 ASM Cluster File System Oracle Management of File System Data Manage both database & file system data E.g.: Oracle & Application binaries, trace files, alert logs, BFILEs, image files, etc. Clustered or local file system Data stored in ASM Inherits all ASM manageability benefits Online disk add/drop/rebalance Integrated mirroring Cross-platform Read-Only Snapshots Up to 63 point-in-time space efficient copies of file system Linux and Windows only in first release Shared File System

Active-Active Availability Minimizing Downtime During Site Failures
Data Corruptions Storage Failures Site Failures Human Errors Server Failures Unplanned Downtime Data Failures Data Guard GoldenGate Streams

Oracle Data Guard Best Disaster Recovery
Dallas Physical Standby Open R/O with Active Data Guard Sync or Async Redo Shipping Production Database Redo Apply Network Backup Broker Open R/W for peripheral writes Logical Standby Transform Redo to SQL Chicago SQL Apply Boston

Active Data Guard Offload Queries to Standby
New in 11.1 Active Data Guard Offload Queries to Standby Real-time Queries Concurrent Real-Time Query Continuous Redo Shipment and Apply Primary Database Physical Standby Database Queries on standby database concurrent with apply Available with Physical Standby in 11.1 Handles all data types, very fast, operationally simple Eliminates cost of DR All hardware used for production load

Oracle Active Data Guard Read Scalability, with DR
New in 11.2 Oracle Active Data Guard Read Scalability, with DR Up to 30 active standby databases Flexible options to scale read performance Add more active standby databases Scale active standby databases using Oracle RAC Queries Scalable Reader Farm Queries Production Database Updates Queries Queries

Continuous redo shipping validation & apply
New in 11.2 Oracle Active Data Guard Auto Block Protection Automatically repair block corruptions online Primary repaired from standby and vice-versa Read/Write Workload Real-time Reporting Primary Database Continuous redo shipping validation & apply Active Standby Database

Snapshot Standby Test with Production Data Before Deployment
New in 11.1 Snapshot Standby Test with Production Data Before Deployment Physical Standby Apply Logs Use Standby Database for testing and development Eliminates cost of DR Justify full scale test and DR environments by combining into one Preserves zero data loss while in test/dev mode But no real time query or fast failover Similar to storage snapshots, but: Provides DR at the same time Single copy of storage Open Database Back out Changes Snapshot Standby Perform Testing Continuous Redo Shipping

Wide Area Network (ASYNC)
New in 11.2 Oracle Data Guard Better Application Availability Automate client failover with role-based services and FAN Auto-start of primary database services Fast notification of application clients FAN enabled JDBC and OCI clients Wide Area Network (ASYNC) Primary Database Standby Database New Primary Database

Continuous redo shipping validation & apply
New in 11.2 Oracle Active Data Guard Ensure Service Levels for Query Latency Automatically enforce service levels for standby queries Query receives error if data delay exceeds SLA Applications can redirect query to primary Read/Write Workload Real-time Reporting Monitoring Apply Lag in a Real-time Query Environment If you are using real-time query to offload queries from a primary database to a physical standby database, you may want to monitor the apply lag to ensure that it is within acceptable limits. The current "apply lag" is the difference, in elapsed time, between when the last applied change became visible on the standby and when that same change was first visible on the primary. This metric is computed to the nearest second. To obtain the apply lag, query the V$DATAGUARD_STATS view. For example, the following query returns the current apply lag as of the time_computed value: SQL> SELECT name, value, unit, time_computed, 2> to_char(sysdate, 'DD-MON-YY HH24:MI:ss') "CURRENT_TIME" 3> FROM V$DATAGUARD_STATS WHERE name like 'apply lag'; NAME VALUE UNIT TIME_COMPUTED CURRENT_TIME apply lag :00:00 day(2) to second(0) interval 03/19/ :04: MAR-09 17:04:37 To obtain a histogram that shows the history of apply lag values since the standby instance was last started, query the V$STANDBY_EVENT_HISTOGRAM view. For example: SQL > SELECT * FROM V$STANDBY_EVENT_HISTOGRAM WHERE NAME = 'APPLY LAG' AND COUNT > 0; NAME TIME UNIT COUNT LAST_TIME_UPDATED APPLY LAG seconds OCT :56:51 APPLY LAG seconds OCT :20:16 APPLY LAG minutes OCT :35:02 APPLY LAG hours OCT :45:24 APPLY LAG days SEP :47:04 Configuring Apply Lag Tolerance in a Real-time Query Environment The STANDBY_MAX_DATA_DELAY session parameter can be used to specify a session-specific apply lag tolerance, measured in seconds, for queries issued by non-administrative users to a physical standby database that is in real-time query mode. This capability allows queries to be safely offloaded from the primary database to a physical standby database, because it is possible to detect if the standby database has become unacceptably stale. If STANDBY_MAX_DATA_DELAY is set to the default value of NONE, queries issued to a physical standby database will be executed regardless of the apply lag on that database. If STANDBY_MAX_DATA_DELAY is set to a non-zero value, a query issued to a physical standby database will be executed only if the apply lag is less than or equal to STANDBY_MAX_DATA_DELAY. Otherwise, an ORA-3172 error is returned to alert the client that the apply lag is too large. If STANDBY_MAX_DATA_DELAY is set to 0, a query issued to a physical standby database is guaranteed to return the exact same result as if the query were issued on the primary database, unless the standby database is lagging behind the primary database, in which case an ORA-3172 error is returned. Use the ALTER SESSION SQL statement to set STANDBY_MAX_DATA_DELAY. For example: SQL> ALTER SESSION SET STANDBY_MAX_DATA_DELAY=2 Forcing Redo Apply Synchronization in a Real-time Query Environment Issue the following SQL statement on a physical standby database to ensure that all redo data received from the primary database has been applied to a physical standby database: SQL> ALTER SESSION SYNC WITH PRIMARY; This statement will block until all redo data received by the standby database at the time that this command is issued has been applied to the physical standby database. An ORA-3173 error is returned immediately, and synchronization will not occur, if the redo transport status at the standby database is not SYNCHRONIZED or if redo apply is not active. You can ensure that redo apply synchronization occurs in specific cases by using the SYS_CONTEXT('USERENV','DATABASE_ROLE') function to create a standby-only trigger (that is, a trigger that is enabled on the primary but that only takes certain actions if it is running on a standby). For example, you could create the following trigger that would execute the ALTER SESSION SYNC WITH PRIMARY statement for a specific user connection at logon: CREATE TRIGGER adg_logon_sync_trigger AFTER LOGON ON user.schema begin if (SYS_CONTEXT('USERENV', 'DATABASE_ROLE') IN ('PHYSICAL STANDBY')) then execute immediate 'alter session sync with primary'; end if; end; Real-time Query Restrictions The apply lag control and redo apply synchronization mechanisms described above require that the client be connected and issuing queries to a physical standby database that is in real-time query mode. The following additional restrictions apply if STANDBY_MAX_DATA_DELAY is set to 0 or if the ALTER SESSION SYNC WITH PRIMARY SQL statement is used: The standby database must receive redo data via the SYNC transport. The redo transport status at the standby database must be SYNCHRONIZED and the primary database must be running in either maximum protection mode or maximum availability mode. Automatic Repair of Corrupt Data Blocks A physical standby database operating in real-time query mode can also be used to repair corrupt data blocks in a primary database. If possible, any corrupt data block encountered when a primary database is accessed is automatically replaced with an uncorrupted copy of that block from a physical standby database operating in real-time query mode. An ORA-1578 error is returned when automatic repair is not possible. Manual Repair of Corrupt Data Blocks The RMAN RECOVER BLOCK command is used to manually repair a corrupted data block. This command searches several locations for an uncorrupted copy of the data block. By default, one of the locations is any available physical standby database operating in real-time query mode. The EXCLUDE STANDBY option of the RMAN RECOVER BLOCK command can be used to exclude physical standby databases as a source for replacement blocks. Primary Database Continuous redo shipping validation & apply Active Standby Database

Additional Data Type Support Both Data Guard SQL Apply & Streams
New in 11.2 Additional Data Type Support Both Data Guard SQL Apply & Streams Additional Data Type support: Basic Table Compression OLTP Table Compression SecureFiles Without deduplication Online Table Redefinition Extended data type support for SDO_GEOMETRY (SQL Apply)

Comprehensive Data Guard Monitoring Using Enterprise Manager 10g Release 5
Critical Data Guard metrics reported on HA console

Oracle Streams Built-in Oracle Database Replication Solution
Source Database Target Database Propagate Capture Apply1 Redo Logs Apply2 Most people think of Streams as replication where all databases can be updateable, and without platform or release considerations. All sites active and updateable Automatic conflict detection & optional resolution Supports data transformations Flexible configurations – n-way, hub & spoke, … Database platform / release / schema structure can differ Provides HA for custom apps where update conflicts can be avoided or managed Transparent Gateway Active-active databases with automatic conflict detection & optional resolution Provides HA for custom apps where update conflicts can be avoided or managed Non-Oracle Database

XStream Fast Real-Time Programmatic Access to Data Changes
New in 11.2 XStream Fast Real-Time Programmatic Access to Data Changes Extended Streams - XStream API for fast real-time access to changes in Oracle database Client attaches directly to Streams apply process using OCI/Java Outbound server (XStream Out) Stream changes out of the Oracle database Inbound server (XStream In) Stream changes from external sources into an Oracle database XStream

Better Streams Performance
New in 11.2 Better Streams Performance Performance optimizations of uni-directional Streams extended to one-to-many Faster transformations Statement DML Handlers Up to 4x faster than procedural DML handlers New Declarative Transformation - Keep Columns Extensive tuning throughout Streams Improved JMS integration and faster Streams Advanced Queuing AQ dequeue is 30%-100% faster than previous releases Statement Handler example; Creating a Statement DML Handler With One Statement Create the statement DML handler and add it to the apply process: DECLARE stmt CLOB; BEGIN stmt := 'INSERT INTO oe.orders( order_id, order_date, order_mode, customer_id, order_status, order_total, sales_rep_id, promotion_id) VALUES( :new.order_id, :new.order_date, :new.order_mode, :new.customer_id, DECODE(:new.order_status, 1, 2, :new.order_status), :new.order_total, :new.sales_rep_id, :new.promotion_id)'; DBMS_APPLY_ADM.ADD_STMT_HANDLER( object_name => 'oe.orders', operation_name => 'INSERT', handler_name => 'modify_orders', statement => stmt, apply_name => 'apply$_sta_2', comment => 'Modifies inserts into the orders table'); END; / Notice that the DECODE function changes the an order_status of 1 to 2. If the order_status in the row LCR is not 1, then the DECODE function used the original order_status value by specifying :new.order_status for the default in the DECODE function. The ADD_STMT_HANDLER procedure creates the modify_orders statement DML handler and adds it to the apply$_sta_2 apply process. The statement DML handler is invoked when this apply process dequeues a row LCR that performs an insert on the oe.orders table. To modify row LCRs that perform updates and deletes made to this table, separate statement DML handlers are required. ======================= To record table changes in a change table, an Oracle Stream apply process uses a change handler. A change handler is a special type of statement DML handler that tracks table changes and was created by either the DBMS_STREAMS_ADM.MAINTAIN_CHANGE_TABLE procedure or the DBMS_APPLY_ADM.SET_CHANGE_HANDLER procedure. This chapter describes using these procedures to create and manage change handlers. Information about change handlers is stored in the ALL_APPLY_CHANGE_HANDLERS and DBA_APPLY_CHANGE_HANDLERS views. The keep columns declarative rule-based transformation keeps a list of columns in a row logical change record (LCR) that satisfies the specified rule. The transformation deletes columns that are not in the list from the row LCR. You specify a keep columns declarative rule-based transformation using the KEEP_COLUMNS procedure in the DBMS_STREAMS_ADM package. Additional Details Declarative rule-based transformations cover a set of common transformation scenarios for row LCRs. You specify (or declare) such a transformation using one of the following procedures in the DBMS_STREAMS_ADM package: - ADD_COLUMN either adds or removes a declarative transformation that adds a column to a row LCR. - DELETE_COLUMN either adds or removes a declarative transformation that deletes a column from a row LCR. - KEEP_COLUMNS either adds or removes a declarative transformation that keeps a list of columns in a row LCR. The transformation removes columns that are not in the list from the row LCR. - RENAME_COLUMN either adds or removes a declarative transformation that renames a column in a row LCR. - RENAME_SCHEMA either adds or removes a declarative transformation that renames the schema in a row LCR. - RENAME_TABLE either adds or removes a declarative transformation that renames the table in a row LCR. When you specify a declarative rule-based transformation, you specify the rule that is associated with it. When the specified rule evaluates to TRUE for a row LCR, Oracle Streams performs the declarative transformation internally on the row LCR, without invoking PL/SQL. Declarative rule-based transformations provide the following advantages: - Performance is improved because the transformations are run internally without using PL/SQL. - Complexity is reduced because custom PL/SQL functions are not required. ====================== About Splitting and Merging Oracle Streams Splitting and merging an Oracle Streams destination is useful under the following conditions: - A single capture process captures changes that are sent to two or more apply processes. - An apply process stops accepting changes captured by the capture process. The apply process might stop accepting changes if, for example, the apply process is disabled, the database that contains the apply process goes down, there is a network problem, the computer system running the database that contains the apply process goes down, or for some other reason. When these conditions are met, it is best to split the problem destination off from the other destinations. The reason to split the destination off depends on whether the configuration uses the combined capture and apply optimization: - If the apply process at the problem destination is part of a combined capture and apply optimization and the destination is not split off, then performance will suffer when the destination becomes available again. In this case, the capture process must capture the changes that must now be applied at the destination that was split off. The other destinations will not receive more recent changes until the problem destination has caught up. However, if the problem destination is split off, then it can catch up to the other destinations independently, without affecting the other destinations. - If the apply process at the destination is not part of a combined capture and apply optimization, then captured changes that cannot be sent to the problem destination queue remain in the source queue, causing the source queue size to increase. Eventually, the source queue will spill captured logical change records (LCRs) to hard disk, and the performance of the Oracle Streams replication environment will suffer. You can configure capture process parameters to split and merge a problem stream automatically, or you can split and merge a problem stream manually. Either way, the SPLIT_STREAMS, MERGE_STREAMS_JOB, and MERGE_STREAMS procedures in the DBMS_STREAMS_ADM package are used. You can set two capture process parameters, split_threshold and merge_theshold, so that Oracle Streams performs split and merge operations automatically. When these parameters are set to specify automatic split and merge, an Oracle Scheduler job monitors the streams flowing from the capture process. When an Oracle Scheduler job identifies a problem with a stream, the job splits the problem stream off from the other streams flowing from the capture process. When a split operation is complete, a new Oracle Scheduler merge job monitors the split stream. When the problem is corrected, this job merges the stream back with the other streams. When the split_threshold capture process parameter is set to INFINITE, automatic splitting is disabled. When the split_threshold parameter is not set to INFINITE, automatic splitting is enabled. Automatic splitting only occurs when communication with an apply process has been lost for the number of seconds specified in the split_threshold parameter. For example, communication with an apply process is lost when an apply process becomes disabled or a destination database goes down. Automatic splitting does not occur when one stream is processing changes slower than other streams. ================================================ About Combined Capture and Apply Optimization For improved efficiency, a capture process can create a propagation sender to transmit logical change records (LCRs) directly to a propagation receiver under specific conditions. The propagation receiver enqueues the LCRs into the buffered queue portion of the destination queue, and an apply process dequeues the LCRs. This optimization is called combined capture and apply. When the capture process and apply process run on different databases, or on different instances in the same database, combined capture and apply is possible only if all of the following conditions are met: The capture process's queue must have a single publisher, and it must be the capture process. A propagation must be configured between the capture process's queue and the apply process's queue. There can be no intermediate queues (no directed network). Each apply process that applies changes from the same source database must use a different queue. ==================================================

Real-time information
GoldenGate Best-in-class leader in real-time data solutions Continuous Availability for heterogeneous systems Real-time data access for Reporting Real-time data for BI, EPM, Exadata Zero-downtime migrations / upgrades to Oracle Database and Applications Over 400 customers with 4,000+ implementations across Fortune 500 companies: Financial Services, Communications, Healthcare, Public Sector, Retail & Utilities industries Top 3 of 5 largest commercial banks Top 3 of 3 busiest ATM networks Top 7 of 10 financial data services companies Top 4 of 5 telecommunications providers Top 3 of 5 largest food & drug stores Real-time information Real-time Access

GoldenGate for Heterogeneous Platforms
Databases O/S and Platforms Capture: Oracle DB2 Microsoft SQL Server Sybase ASE Teradata Enscribe SQL/MP SQL/MX Delivery - all listed above, plus: HP Neoview, Netezza, Greenplum, and any ODBC compatible databases ETL products JMS message queues MySQL TimesTen Windows 2000, 2003, XP Linux Sun Solaris HP NonStop HP-UX HP TRU64 HP OpenVMS IBM AIX IBM z/OS GoldenGate is ideal for heterogeneous environments – not just supporting different versions of the same database or operation system/hardware, but replicating and integrating data across vendor systems. We support log-based Capture of changed data from nearly all major database vendors. We can Deliver that data to an even wider range of targets – including open source databases, several data warehouse appliances, ETL servers, and JMS message queues to support Service Oriented Architectures (SOA) and Event-Driven Architectures (EDA). 30

GoldenGate and Streams
Oracle GoldenGate Oracle Streams GoldenGate is Oracle’s strategic replication solution Streams continues to be a supported Oracle Database feature Best Streams technology will be integrated into GoldenGate

GoldenGate and Data Guard
Oracle Active Data Guard Oracle DB Primary Oracle DB Standby Heterogeneous Distributed Fully-active Subset Replicas Oracle GoldenGate Information Distribution & Consolidation, Application Upgrades & Changes Use GoldenGate - heterogeneous, active-active, transformations, subsetting Disaster Recovery / Data Protection / HA Simple Full Oracle Database Protection Use Active Data Guard High-performance, simple, drop-in solution for HA and DR, readable at standby Works for all apps and data types, including packaged apps that can’t be changed Application desiring flexible HA, active-active, schema changes, platform changes Use GoldenGate Avoid or manage active-active conflicts at application level Combine the two for full database protection and information distribution

Best Online Planned Maintenance At Lowest Cost
Server Failures Unplanned Downtime Data Failures Online Reconfiguration Rolling Upgrades System Changes Planned Downtime Data Changes Online Redefinition Edition-based Redefinition App Changes

Online Reconfiguration Scaling on Demand
Servers Add/Remove RAC nodes online No data movement needed Storage Add/Remove ASM disks or arrays online Automatically rebalance after storage change Clusterware, ASM Upgrade Oracle Clusterware and ASM (11g) in an online manner Database Storage

Online Patching and Upgrades
Most one-off patches can be applied to a running Oracle instance Linux-x86, Solaris 10, HP-UX 11i [New in 11.2] Windows 32-bit and Windows 64-bit, AIX v6.1 [TL2 SP1] More complex one-off patches can be deployed online using RAC rolling patches (available 10g onwards) Database release/patchset upgrades, operating system upgrades, platform migrations can be applied in rolling fashion using Data Guard / GoldenGate / Streams Data Center moves / SAN migration / Technology Refresh etc. can be done with minimal downtime using Data Guard / GoldenGate / Streams

Continuous Queries & Updates
Online Index & Table Redefinition All index changes can be done online 11gR1 – table is never locked during online index creation Tables can be Reorganized & Redefined online Allows changing location, table type, partitioning, columns, column types Contents can be transformed as they are copied Copy Table Transform Source Table Result Table Uses the DBMS_REDEFINITION package Store Updates Continuous Queries & Updates Update Tracking Transform Updates

Edition-based Redefinition Overview
New in 11.2 Edition-based Redefinition Overview Enables online application patches and upgrades Allows old and new version of application to co-exist even though schema is changed by new version Capabilities primarily used by application developers The features for online application upgrade are used by developers - when preparing the application for online upgrade - when implementing an upgrade script DBAs, of course, will need to understand the features

Edition-based Redefinition How Does it Work?
New in 11.2 Edition-based Redefinition How Does it Work? Post-upgrade Edition Maintains logical versions of changed database objects, through: Edition Editioning View Crossedition Trigger PL/SQL code changes and view changes installed in the privacy of a new edition New data changes made to new columns/tables not seen by old edition Editioning view exposes a private projection of a table into each edition Crossedition trigger propagates changes made by old edition into new edition’s columns, or vice-versa Crossedition Triggers Pre-upgrade Edition The installation of the upgrade into the production database must not perturb live users of the pre-upgrade application - Many objects must be changed in concert. The changes must be made in privacy Data must persist across a patch or upgrade - Transactions done by the users of the pre-upgrade application must by reflected in the post-upgrade application For hot rollover, we also need the reverse of this: - Transactions done by the users of the post-upgrade application must by reflected in the pre-upgrade application

End-to-End Availability

Sun Oracle Database Machine
Grid is the architecture of the future Highest performance, lowest cost, incrementally scalable Redundant and Fault Tolerant Sun Oracle Database Machine delivers the first and only complete grid architecture for all data management needs Oracle Database Server Grid 8 High-performance compute servers InfiniBand Network 40 Gb/sec fault-tolerant unified server and storage network Exadata Storage Server Grid 14 High-performance storage servers 5TB flash storage Data is mirrored across storage servers 14 Exadata cells 168 disk drives 64 database server cores total 3 36-port Infiniband QDR (40Gb/sec) switches Enough for adding up to 7 more racks by just adding cables between the racks Cisco Ethernet 48-port switch (admin) KVM © 2009 Oracle Corporation - Confidential 40 40

Real Application Clusters
Database Technology Drives Availability Real Application Clusters Active Data Guard WAN ASM Oracle Secure Backup Fast Recovery Area Real-time remote standby open for queries Human error correction Database, table, row, transaction level Online indexing and table redefinition Online patching and upgrades Protection from Server Failures Storage Failures Network Failures Site Failures

Database Machine HA Metrics
Backup & Recovery Backup shows extreme performance and scalability using Exadata Full Database Backup to tape demonstrated at 7.8 TB/hr Limited by tape performance of 14 tape drives used in test Incremental backup to tape at 10% change rate: 70TB/hr Single RMAN backup channel runs full backup to disk at 2.5 TB/hr Data Guard Full DR demonstrated with uncompressed loads over 2TB/hour Compressed tables reduce redo & net traffic enhancing Data Guard 5 TB/hour load rates with Data Guard into compressed tables 5 customers have implemented Data Guard on a Database Machine in first year

Oracle High Availability Architecture
Scale-Out & Low-Cost High-volume hardware All components active Application Oriented Protect and recover application objects Enable online application changes Integrated & Simple Availability integrated into all components Automated Complete & Open Handles all planned and unplanned downtime Pluggable components

HA Sessions, Labs, & Demos by Oracle Development
Sunday, 11 October – Hilton Hotel Imperial Ballroom B 3:45p Online Application Upgrade Monday, 12 October – Marriott Hotel Golden Gate B1 11:30a Introducing Oracle GoldenGate Products Monday, 12 October – Moscone South 1:00p Oracle’s HA Vision: What’s New in 11.2, Room 103 2:30p Oracle Streams: What's New in 11.2, Room 301 4:00p Database 11g: Performance Innovations, Room 103 5:30p Comparing Data Protection Solutions, Room 102 Tuesday, 13 October – Moscone South 11:30a Oracle Streams: Replication Made Easy, Room 308 11:30a Backup & Recovery on the Database Machine, Room 307 11:30a Next-Generation Database Grid Overview, Room 103 1:00p Oracle Data Guard: What’s New in 11.2, Room 104 2:30p GoldenGate and Streams - The Future, Room 270 2:30p Backup & Recovery Best Practices, Room 104 2:30p Single-Instance RAC, Room 300 4:00p Enterprise Manager HA Best Practices, Room 303 Tuesday, 13 October – Marriott Hotel Golden Gate B1 11:30a GoldenGate Zero-Downtime Application Upgrades 1:00p GoldenGate Deep Dive: Architecture for Real-Time Wednesday, 14 October – Moscone South 10:15a Announcing OSB 10.3, Room 300 11:45a Active Data Guard, Room 103 5:00p Exadata Storage & Database Machine, Room 104 Thursday, 15 October – Moscone South 9:00a Empowering Availability for Apps, Room 300 12:00p Exadata Technical Deep Dive, Room 307 1:30p Zero-Downtime DB Maintenance, Room 103 Demos Moscone West DEMOGrounds Mon & Tue 10:30a - 6:30p; Wed 9:15a - 5:15p Maximum Availability Architecture (MAA), W-045 Oracle Streams: Replication & Advanced Queuing, W-043 Oracle Active Data Guard, W-048 Oracle Secure Backup, W-044 Oracle Recovery Manager & Flashback, W-046 Oracle GoldenGate, 3709 Hands-on Labs Marriott Hotel Golden Gate B2 Monday 11:30a-2:00p Oracle Active Data Guard, Parts I & II Thursday 9:00a-11:30a Oracle Active Data Guard, Parts I & II

Complete List of New HA Features Oracle Database 11g Release 2 Oracle Database 11g Release 1

Complete List of New HA Features Oracle Database 11g Release 2
Data Guard Active Data Guard: Online block repair Query SLA Primary with 30 standbys Parallel local & remote SYNC transport Retrieve remaining redo from primary before failover Improved client failover Role-based services Broker support for ONS Support auto-client failover for logical standby for JDBC, OCI, ODP.Net No shutdown of RAC instances in old standby for switchover No shutdown moving from Max Availability to Max Protection Comprehensive support for compressed redo transport Data Guard (contd.) SQL Apply support of OLTP Compression, SecureFiles, XA in RAC, Online Redefinition & Edition-based Redefinition, SDO_GEOMETRY (EDS) Use logical standby as Streams source Streams XStream IN & OUT Statement DML Handlers Better infrastructure to track changes to table data New Declarative Transformation: keep_columns Optimized one-to-many propagation AQ: Improved JMS integration & performance improvements Support of OLTP Compression, SecureFiles, Online Redefinition RAC Server pools RAC One Node Omotion ASM Cluster File System OCR & Voting Disk in ASM Flashback Flashback Database: better performance for direct loads Flashback Database: enable while database is open Flashback Database: better monitoring of progress Flashback Transaction: track foreign key dependency In Data Guard 11g Release 1 we offered redo transport compression when resolving gaps. In Data Guard 11g Release 2, supports compression for all Data Guard redo transports – SYNC, ASYNC and Gaps. Note that compression ratios will vary from one workload to the next.

Online Patching & Upgrades Edition-based Redefinition using Edition, Editioning View and Crossedition Trigger Online Patching for Windows & AIX RMAN Multiple compression levels Target-less DUPLICATE Optimized checks for DUPLICATE Expanded DUPLICATE options Enhanced tablespace point-in-time recovery using transportable tablespace and Data Pump Improved flexibility of SET NEWNAME Faster transportable database OSB 10.3 Server-less tape duplication for VTL using NDMP tape copy Better automation for tape vaulting Support for IPv6 as well as IPv4 Supports LTO-4 tape drive encryption Manages encryption key seamlessly between native or LTO-4 encryption More comprehensive backup / restore monitoring Verification of tape device configurations Grid Control HA Console MAA Advisor Minimal downtime ASM migration & RAC conversion Streams dashboard and improved monitoring of Streams configurations. Database Clone from existing database backups Comprehensive OSB management OSB File System Backup/Restore and reports Task based workflow for mining redo and archived logs Means that we can track dependent transactions whose modified rows are associated thru foreign key, e.g. Assumption: Table a Table b (has foreign key constraint to column A in Table a) Txn1: Modified row 1 of table a; commit; Txn2: Modified row 2 of table b; When you backout txn1 with CASCADE option, it will find txn2 as dependent txn and backout those changes out first (i.e. in reverse txn commit SCNs), then txn1 changes. This was not supported in so, if you tried to backout txn1 with CASCADE, you may get foreign key violation error. In that case, you need to supply both txns to the Flashback Txn, and it would back them out in reverse txn commit order.

Clusters Better performance, failover, management Seamless integration with XA and Microsoft Transaction Server Optimized Cache Fusion protocols ASM Temporarily freeze I/O to unresponsive storage and replay writes when it returns Rolling Upgrade for ASM instances Data Guard - Generic Snapshot standby Fast-Start Failover in secs Fast-Start Failover for asynchronous mode Fast Redo Transport Redo Transport Compression for gaps SYS user no longer required for redo shipping Standby across Linux/Windows on x86 Flashback Flashback Transaction Flashback Data Archive Data Guard SQL Apply Support XMLType data type (CLOB) Support Transparent Data Encryption (TDE) Apply performance improved significantly Support Fine Grained Auditing Support Virtual Private Database Data Guard Redo Apply Active Data Guard New parallel media recovery doubles redo apply performance Fast Incremental Backup Better RMAN integration

Backup & Recovery Data Recovery Advisor Intra-file parallel backup and restore Faster backup compression Duplicate database over the network Integration with Windows Volume Shadow Copy Services (VSS) API Integrated protection through ultra safe mode Upgrades Online patching Transient logical standby Online Redefinition Fast add column with default value Invisible Indexes prevent premature use of newly created indexes Online index build with NO pause to DML No recompilation of dependent objects Easier to execute table DDL operations online Streams Support XMLType data type (CLOB) Support Transparent Data Encryption (TDE) Apply performance improved significantly Support AWR, ADDM, ASH Streams Performance Advisor Synchronous capture Table Data Comparison JMS/AQ performance improvements

Oracle GoldenGate Key Features in v10
General – Across the Platforms Event Marker Infrastructure Start Delivery as of CSN (Commit Sequence Number) for efficient instantiation Enhanced Memory Management Deferred Apply Array Fetching to increase initial load performance Oracle Additional data type support – Spatial, IOTs, Sequences, clustered table, object table Support of Append hints (Apply only) Increased Oracle DDL text maximum size to 2MB Filtering by User for more efficient loop detection and capture task type separation (e.g. batch vs OLTP) Expanded Support of ALO (Archive Log Only) mode for RAC environments SQL Server SQL Server 2008 Delivery Capture of tables without primary keys (SQL Server 2005) DB2 LUW Support for Multi Dimensional Clustered Tables (MDC) Support for Materialized Query Tables (MQT) NSK Support of HP Blades Support Primary Key Updates from Open Systems (e.g. Oracle to NSK) Teradata Integration of Oracle GoldenGate Director with TMSM (Teradata Multi-System Manager) Support of Teradata v13 – DDL replication Support for additional platforms: Solaris 10, SUSE 9/10 Full Unicode Support for Linux ODBC 50 50

Resources Oracle.com: http://www.oracle.com/ha
Oracle HA Customer Success Stories on OTN: Maximum Availability Architecture (MAA): MAA Assessment:

Q & Q U E S T I O N S A N S W E R S A

For More Information search.oracle.com or oracle.com

Juan Loaiza Senior Vice President, Oracle System Technology

Similar presentations

Presentation on theme: "Juan Loaiza Senior Vice President, Oracle System Technology"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

Juan Loaiza Senior Vice President, Oracle System Technology

Similar presentations

Presentation on theme: "Juan Loaiza Senior Vice President, Oracle System Technology"— Presentation transcript:

Similar presentations

About project

Feedback