An Oracle White Paper January 2013

Oracle Goldengate On Oracle Exadata Database Machine Configuration

Oracle Maximum Availabiity Architecture Configuration

Oracle GoldenGate on Oracle Exadata Database Machine

Executive Overview ........................................................................... 1 Configuration Overview ..................................................................... 2 Oracle GoldenGate........................................................................ 2 Oracle Exadata Database Machine ............................................... 3 Oracle Database File System ........................................................ 4 Oracle Clusterware ........................................................................ 4 Migrating to Oracle Exadata Database Machine ................................ 5 Configuration Best Practices ............................................................. 6 Step 1: Set Up DBFS on Oracle Exadata Database Machine ........ 6 Step 2: Install Oracle GoldenGate ............................................... 10 Step 3: Configure GoldenGate and Database Parameters .......... 10 Step 4: Set Up Checkpoint Files and Trail Files in DBFS ............. 12 Step 5: Set Up Page Files on the Local File System .................... 14 Step 6: Configure Replicat Commit Behavior ............................... 14 Step 7: Configure Autostart of Extract, Data Pump and Replicat Processes.................................................................................... 15 Step 8: Oracle Clusterware Configuration .................................... 15 Appendix A: Creating GoldenGate Clusterware Resource ............... 20 Recommendations When Deploying on Oracle RAC ................... 23 Appendix B: Example Agent Script .................................................. 24 References ...................................................................................... 29

Oracle Maximum Availabiity Architecture

Oracle GoldenGate on Oracle Exadata Database Machine Configuration

Executive Overview
The strategic integration of Oracle Exadata Database Machine and Oracle Maximum Availability Architecture (MAA) best practices (Exadata MAA) provides the best and most comprehensive Oracle Database availability solution. This white paper describes best practices for configuring Oracle GoldenGate to work with Oracle Exadata Database Machine and Exadata storage. Oracle GoldenGate is instrumental for many reasons, including the following: To migrate to an Oracle Exadata Database Machine, incurring minimal downtime As part of an application architecture that requires Oracle Exadata Database Machine plus the flexible availability features provided by Oracle GoldenGate, such as active-active database for data distribution and continuous availability, and zero or minimal downtime during planned outages for system migrations, upgrades, and maintenance To implement a near real-time data warehouse or consolidated database on Oracle Exadata Database Machine, sourced from various, possibly heterogeneous source databases, populated by Oracle GoldenGate To capture from an OLTP application running on Oracle Exadata Database Machine to support further downstream consumption such as a SOA type integration This paper focuses on configuring Oracle GoldenGate to run on Oracle Exadata Database Machine. Oracle Exadata Database Machine can act as the source database, as the target database, or in some cases as both source and target databases for Oracle GoldenGate processing.

1

Figure 1 shows the Oracle GoldenGate architecture. and high availability.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration In addition. Oracle Exadata Database Machine. and active-active databases for data distribution. zero-downtime upgrades and migrations. and Oracle Database File System (DBFS). this paper covers the Oracle GoldenGate regular mode of continuously extracting logical changes from either online redo log files or archived redo log files. For more information about these features. many-to-many. and bidirectional. see the References section at the end of this white paper. cascading. query offloading. data synchronization. Using this technology. Oracle GoldenGate moves committed transactions with transaction integrity and minimal overhead on your existing infrastructure. it enables a cost-effective and low-impact realtime data integration and continuous availability solution. The architecture supports multiple data replication topologies such as one-to-many. 2 . Configuration Overview This section introduces Oracle GoldenGate. Its wide variety of use cases includes real-time business intelligence. log-based change data capture and delivery between heterogeneous systems. Oracle GoldenGate Oracle GoldenGate provides real-time.

high-speed InfiniBand connectivity. data warehousing (DW). Oracle Exadata Database Machine is a “grid in a box” composed of database servers. out-of-the-box solution for hosting the Oracle Database for all applications while delivering the highest levels of performance available.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Datasource for Initial Load: Source tables Network Target Database Initial Load Extract Manager Manager Replicat Extract Datasource for Change Synchronization: Transaction Log or Vendor Access Module Collector Trail or File Replicat (Optional) Data Pump Change Synchronization Figure 1. an InfiniBand fabric for storage networking. Exadata storage. 3 . and consolidation of mixed workloads. Oracle Exadata Storage Server is a storage product optimized for use with Oracle Database applications and is the storage building block of Oracle Exadata Database Machine. Exadata Smart Flash Cache. Oracle Exadata Storage Servers (Exadata). Oracle GoldenGate Architecture Oracle Exadata Database Machine Oracle Exadata Database Machine is an easy to deploy. and all the other components required for hosting an Oracle Database. Exadata delivers outstanding I/O and SQL processing performance for online transaction processing (OLTP). and compression technology. Extreme performance is delivered for all types of database applications by leveraging a massively parallel grid architecture using Oracle Real Application Clusters (Oracle RAC).

Oracle Clusterware also manages resources. The Manager process should then be configured to automatically start or restart other Oracle GoldenGate processes. In this way the separate servers appear as if they are one system to applications and end users. databases. Each file system has its own dedicated tables that hold the file system content. open. and so on. You use the APIs to register the Oracle GoldenGate Manager process as an application managed through Oracle Clusterware. the file system inherits all the high availability and disaster recovery capabilities provided by the database. listeners. write. Files are stored as SecureFiles LOBs. Oracle Clusterware Oracle Clusterware enables servers to communicate with each other. Although the servers are standalone servers. The DBFS SecureFiles Store allows users to create file systems that can be mounted by clients. services.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Oracle Database File System The Oracle Database File System (DBFS) creates a file system interface to files stored in the database. Because the data is stored in the database. Oracle Clusterware provides the infrastructure necessary to run Oracle Real Application Clusters (Oracle RAC). The implementation of the file system in the database is called the DBFS SecureFiles Store. With DBFS. so that they appear to function as a collective unit. read. PL/SQL procedures implement file system access primitives such as create. 4 . This combination of servers is commonly known as a cluster. DBFS is similar to NFS in that it provides a shared network file system that looks like a local file system. There are APIs to register an application and instruct Oracle Clusterware regarding the way an application is managed in a clustered environment. such as virtual IP (VIP) addresses. the server is the Oracle Database. and list directory. each server has additional processes that communicate with other servers.

This provides the ability to migrate to Oracle Exadata Database Machine allowing the new system to work in tandem until testing is completed and a switchover planned. Refer to Exadata MAA Paper: Best Practices for Migrating to Exadata Database Machine for determining which migration option is best for your specific case. where Oracle GoldenGate replicates data from an active primary database to a full replica database on a live standby system that is ready for failover during planned and unplanned outages. Migrating Oracle GoldenGate to Oracle Exadata Database Machine Oracle GoldenGate supports an active-passive bidirectional configuration.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Migrating to Oracle Exadata Database Machine Application Switchover / Failover to Secondary Primary Data Flow Capture Trail Trail Delivery GOLDEN GATE Route LAN/WAN/Web/IP GOLDEN GATE Teradata Database Delivery Trail Switchback / Failback Data Flow Trail Capture Oracle Database Machine Figure 2. 5 . Using Oracle GoldenGate for database migration is most applicable when reduced downtime is a requirement and Oracle Data Guard cannot be used for this database migration. This paper includes instructions for configuring a target system on Oracle Exadata Database Machine that will act as the standby database shown in Figure 2.

so that recoverability is not compromised in the event of media failures or corruptions. temp files. checkpoint files. and failover capabilities in the event of a system failure. It is recommended that you allocate enough trail file disk space to permit storage of up to 12 hours of trail files. Using DBFS is fundamental to the continuing availability of the checkpoint and trail files in the event of a node failure. Doing this will give sufficient space to Extract trail file generation should a problem occur with the target environment that prevents it from receiving new trail files.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Configuration Best Practices Step 1: Set Up DBFS on Oracle Exadata Database Machine When setting up the configuration.Create the tablespace: SQL> create bigfile tablespace dbfs_gg_source_tbs datafile ‘+DBFS_DG’ size 200g autoextend on next 8g maxsize 400g LOGGING EXTENT MANAGEMENT LOCAL AUTOALLOCATE SEGMENT SPACE MANAGEMENT AUTO. The amount of space needed for 12 hours can only be determined by testing trail file generation rates with real production data. and parameter files. 6 . bounded recovery and configuration files in DBFS to provide the best performance. Follow instructions in My Oracle Support note 1054431. scalability. Ensuring the availability of the checkpoint files clusterwide is essential to ensure that. after a failure occurs. Create the DBFS tablespace: -.Connect to the DBFS database SQL> connect system/<passwd>@<source_dbfs_tns_alias> -. It is therefore recommended to run the DBFS database in ARCHIVELOG mode. patches. Source Environment (Extract/Datapump) Create a single file system for storing the Oracle GoldenGate trail files. and permissions on source or target environments. the best practice is to store the Oracle GoldenGate trail files. On an Oracle Exadata Database Machine environment there is little performance difference when running the DBFS database used by Oracle GoldenGate in ARCHIVELOG or NOARCHIVELOG mode. DBFS database. Substitute the size parameters with your required trail file storage size. checkpoint files. required users. bounded recovery files. the Extract process can continue mining from the last known archived redo log file position. Using DBFS allows one of the surviving database instances to be the source of an Extract/Data Pump processes or a destination for the Replicat processes. discard files. and Replicat processes can start applying from the same trail file position before a failure occurred. recoverability.1 to install the required libraries.

------.---------- If the LOB segment is not using NOCACHE LOGGING.logging FROM dba_lobs WHERE tablespace_name='DBFS_GG_SOURCE_TBS'.---------- Follow instructions in My Oracle Support note 1054431. -.---------------------. -. -. alter it: SQL> ALTER TABLE DBFS.<TABLE_NAME> MODIFY LOB (FILEDATA) (NOCACHE LOGGING). segment_name.------.Connect to the DBFS database SQL> connect system/<passwd>@<dbfs_tns_alias> -.View current LOB storage: SQL> SELECT table_name.-----------------.TABLE_NAME -. be sure to create it as a cluster_resource instead of a local_resource as specified in the My Oracle Support note: crsctl add resource $RESNAME \ -type cluster_resource \ 7 . segment_name.logging FROM dba_lobs WHERE tablespace_name='DBFS_GG_SOURCE_TBS'.View the new LOB storage: SQL> SELECT table_name. When registering the resource with Oracle Clusterware.T_GOLDENGATE SEGMENT_NAME LOB_SFS$_FST_73 LOGGING CACHE YES NO -.More than likely it will be something like this: --.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Create the file system: % cd $ORACLE_HOME/rdbms/admin % sqlplus dbfs_user/dbfs_password SQL> start dbfs_create_filesystem dbfs_gg_source gg_source1 The LOB segment used by DBFS should be configured with the storage options NOCACHE LOGGING which is the default: -.T_GOLDENGATE SEGMENT_NAME LOB_SFS$_FST_73 LOGGING CACHE YES NO -.TABLE_NAME -.-----------------.1 for configuring the newly created DBFS file system so that the DBFS instance and mount point resources are automatically started by Cluster Ready Services (CRS) after a node failure.---------------------.

2. but when Extract performs recovery after a node failure. no matter how many open (uncommitted) transactions there were at the time that Extract stopped. To set the Bounded Recovery file directory use the following Extract parameter: BR BRDIR /mnt/dbfs_source/goldengate/BR 8 . create directories in the newly created filesystem for storing the Oracle GoldenGate files. With earlier releases the Bounded Recovery files need to be stored on NFS storage such as ZFS Storage appliance connected to Exadata. Starting in Oracle GoldenGate version 11.db)pullup(ora. planned or unplanned. \ START_DEPENDENCIES='hard(ora.$DBNAMEL. nor how old they were.1.db)'. Extract can use Bounded Recovery to reduce the time to taken to perform recovery.RESTART_ATTEMPTS=10. Bounded Recovery sets an upper boundary for the maximum amount of time that it would take for Extract to recover to the point where it stopped and then resume normal processing. \ CHECK_INTERVAL=30. the standard checkpoint mechanism will be used until new local Bounded Recovery checkpoint files are subsequently created. It is possible to store the checkpoint files on the local file system.db)'.1 the Bounded Recovery files are supported and it is recommended that you place them on DBFS. The Bounded Recovery checkpoint files should be placed on a shared file system such that.\ SCRIPT_TIMEOUT=300" Once the file system is mounted.\ STOP_DEPENDENCIES='hard(ora. This feature guarantees an efficient recovery after Extract stops for any reason.1. in an event of a failover when there are open long running transactions.$DBNAMEL. This will only be noticeable if there are long running transactions at the time of the failure. Example: % cd /mnt/dbfs_source/goldengate % mkdir dirchk % mkdir dirpcs % mkdir dirprm % mkdir dirdat % mkdir BR Create symbolic links for the directories that are not controlled by Oracle GoldenGate parameters: % ln –s /mnt/dbfs_source/goldengate/dirprm $GG_HOME/dirprm % ln –s /mnt/dbfs_source/goldengate/dirchk $GG_HOME/dirchk % ln –s /mnt/dbfs_source/goldengate/dirpcs $GG_HOME/dirpcs The Bounded Recovery (BR) feature was added to Extract in Oracle GoldenGate version 11.$DBNAMEL.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration -attr "ACTION_SCRIPT=$ACTION_SCRIPT.

For Extract it is also specified in the parameter file with the EXTTRAIL. Trail files are written to by the Collection Server process on the target host using consecutive serial I/O’s from the start to the end of the file. Create the second DBFS file system for the checkpoint files in much the same way as the file system on the source environment (above). reading from the same portion of the trail file at the same time. In testing this has shown to increase checkpoint performance by a factor of 2 to 5 times compared to using the NOCACHE configuration with DBFS. where the Replicat processes read the trail files and apply the data to the target database there is a requirement for two separate DBFS file systems to separate the different I/O requirements of the trail and checkpoint files. Because of this.oracle. Target Environment (Replicat) On the target environment.Likely it will be something like this: --. The same trail files are read by each Replicat process. segment_name.Connect to the DBFS database SQL> connect system/<passwd>@<dbfs_tns_alias> -. -. overwriting previous data.logging FROM dba_lobs WHERE tablespace_name='DBFS_GG_CKPT_TBS'.pdf The location of the Extract/Datapump trail file directory is specified during process creation. The file doesn’t grow in size and is only read during process startup to determine the proper starting point for recovery or initiation. Some important notes: • • The file system is only for checkpoint files. The checkpoint files are small (approximately 4KB) but written to frequently. the best configuration for DBFS is with NOCACHE LOGGING storage options. also using consecutive serial I/O requests. performance is best when the file is stored in DBFS with the CACHE LOGGING storage option. and not issuing direct writes to disk causing higher waits on I/O.View current LOB storage: SQL> SELECT table_name. so it can be sized less than 100MB Create the file system using the same user as the first file system created. This is described above in configuring the source environment. When using multiple Replicat processes reading from the same trail files. Setting the CACHE option causes the small amount of data being written to the checkpoint files to be written into the buffer cache of the DBFS instance.com/cd/E35209_01/doc. Once a portion of the trail is read by a Replicat process it will not normally be read a second time by the same process.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration For more information on Bounded Recovery refer to the Oracle GoldenGate Reference Guide: http://docs. It is important to make sure the same user creates both file systems.TABLE_NAME SEGMENT_NAME • LOGGING CACHE 9 . it is rare that they remain in sync. Change the LOB storage parameters to CACHE LOGGING: -.1121/e29399. sized according to your Datapump configuration. Because the checkpoint file is written to over and over.

3. Step 3: Configure Oracle GoldenGate and Database Parameters It is recommended that you configure Oracle GoldenGate Extract in Integrated Capture Mode to take advantage of the increased data type support.0. Install Oracle GoldenGate locally on the primary source and target nodes in the Oracle RAC configuration.---------------------. TDE.1.1.1121/e35957.<TABLE_NAME> MODIFY LOB (FILEDATA) (NOCACHE LOGGING).----------.logging FROM dba_lobs WHERE tablespace_name='DBFS_GG_CKPT_TBS'. Extract integrates with an Oracle database log mining server to receive change data from that server in the form of logical change records (LCR). segment_name. and data compression.1.---------------------.2. -. ASM.2. Follow the generic installation instructions for the source and target machine installations available in Chapter 2: “Installing GoldenGate” at: http://docs.3 with the patches described in My Oracle Support note 1411356. Download the Oracle GoldenGate software from Oracle Technology Network (OTN) at: http://www.4 in a downstream mining deployment.oracle.1. It can also be used to capture changes from Oracle versions starting with 10. Because integrated capture is fully integrated with the database.-----------------.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration -.------. Extract can be used in integrated capture mode. Integrated capture can be used starting with Oracle 11.com/cd/E35209_01/doc. TDE. Introduced in Oracle GoldenGate version 11.------. then contact Oracle GoldenGate Support to obtain the fix to Bug 10146318. 10 . shut down Extract/Replicat and copy the entire Oracle GoldenGate home directory to the other source and target nodes.html 2. no additional setup is required to work with Oracle RAC. This bug fix improves trail file creation performance on DBFS by the Oracle GoldenGate server/collector process. Make sure the installation directory is the same on all nodes.---------T_GOLDENGATE2 LOB_SFS$_FST_75 YES YES Note: If you are using an Oracle GoldenGate Data Pump process to transfer the trail files from a source host on the database machine using DBFS.pdf 4. This only affects Oracle GoldenGate versions before 11.0. Once you have successfully configured Oracle GoldenGate on the primary source and/or target nodes. TABLE_NAME SEGMENT_NAME LOGGING CACHE -----------------. Extract can be configured to capture from a local or downstream mining database. Step 2: Install Oracle GoldenGate 1.5.View the new LOB storage: SQL> SELECT table_name.2. and data compression.com/technetwork/middleware/goldengate/downloads/index.oracle.T_GOLDENGATE2 LOB_SFS$_FST_75 YES NO SQL> ALTER TABLE DBFS.0.

Use the default Oracle Automatic Storage Manager (Oracle ASM) naming convention for the archived redo log files. For example: TRANLOGOPTIONS DBLOGREADER 3.0. refer to the Oracle GoldenGate Windows and UNIX Reference Guide: http://docs.1121/e29399. To successfully mine the Oracle archived redo log files located on the storage cells that are managed by Oracle ASM.2. a.0. Using PASSTHRU reduces CPU by the Data Pump because it does not have to look up table definitions. This new method uses the database server to access the redo and archived redo log files. b.1121/e35957. Extract in Classic Capture mode.2 and 11. Oracle GoldenGate release 11. either from the database or from a data definitions file. Set the database initialization parameter STREAMS_POOL_SIZE = 1.pdf 11 . Configure Data Pump.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Extract can still be configured to capture directly from the redo logs for any supported Oracle version. refer to the Oracle GoldenGate Installation and Setup Guide: http://docs.1 introduces a new method of reading log files stored in Oracle ASM. Configure the Oracle GoldenGate Extract parameter for the newer Oracle ASM log read API. a. Configure the Data Pump with the PASSTHRU parameter if the process is not carrying out any mappings or conversions. instead of connecting directly to the Oracle ASM instance.oracle.oracle.5.com/cd/E35209_01/doc. configure the Oracle GoldenGate Extract parameter as follows: Set the TRANLOGOPTIONS parameter to specify use of the new log read API.2.2.0. 11. The libraries are currently included with Oracle Database release 10. For further details on Extract configuration or Data Pump with PASSTHRU. This configuration is now called classic capture mode. Extract using Integrated Capture mode. 1.1.pdf 2. The database must contain the libraries with the API modules.3.25GB X #Integrated Capture Processes.com/cd/E35209_01/doc. For further details about configuring Extract in Integrated Capture mode.

the network. the best practice is to create a symbolic link from the Oracle GoldenGate home directory to a directory in DBFS. Create and mount the DBFS file system. This will in turn prevent the Extract or Replicat from being started concurrently on multiple nodes. much like an NFS mount. DBFS does not support this method of file locking. Set up trail files. Checkpoint files contain the current read and write positions of the Extract and Replicat processes. A checkpoint table can be used to record Replicat checkpoint information to provide an alternative method of fault tolerance To store the checkpoint files on DBFS. Be sure to use DBFS to provide fault tolerance for the trail files. Checkpoints provide fault tolerance by preventing the loss of data should the system. This is detailed in the DBFS configuration in Step 1 above. the Replicat process can read from the same trails created by the Extract process. By mounting the same DBFS directory on both the source and target databases. Trail files contain the data extracted from the archived redo log files.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Step 4: Set Up Checkpoint Files and Trail Files in DBFS 1. Note: Oracle GoldenGate uses file locking on the checkpoint files to determine if the Extract or Replicat processes are already running. 12 . To configure Oracle GoldenGate trail files on DBFS for the source database: 1. This removes the need for the Oracle GoldenGate Data Pump if both the source and target databases run in the same Oracle Exadata Database Machine. If the source and target databases are not part of the same Exadata Database Machine. Store the trail files on DBFS. Placing the checkpoint files on the local file system will not provide high availability in the event of a database node failure. then use an Oracle GoldenGate Data Pump to transfer the trail files between the hosts. The trail files are automatically generated by the Extract process. 2. This would normally prevent the process from being started a second time on another Oracle RAC node that has access to the checkpoint files. or an Oracle GoldenGate process need to be restarted. Mounting DBFS on a single Oracle RAC node prevents access to the checkpoint files from other nodes. This is detailed above in the DBFS configuration in Step 1. Set up checkpoint files.

EXTTRAIL /mnt/dbfs/goldengate/dirdat/aa Do not place trail files on the local file system because it will lengthen restart times in the event of a node failure. EXTRACT ext_db. Make sure the DBFS directory is already created on the target environment Set the EXTTRAIL Replicat parameter.1121/e29397. 2. use the same EXTTRAIL parameter value: % ggsci GGSCI (ggtest. Set the RMTTRAIL Data Pump parameter to the trail file location on the target host: RMTTRAIL /mnt/dbfs/goldengate/dirdat/aa 13 .oracle. as follows: EXTTRAIL /mnt/dbfs/goldengate/dirdat/aa 3. When adding the Replicat. In Step 7 below.oracle. After creating the Extract. Make sure Extract and Replicat are configured Set the RMTHOST Data Pump parameter to the IP or hostname that will be used for connecting to the target. so that Data Pump can continue to connect to the target host when it moves from a failed node to a surviving node: RMTHOST gg_dbmachine. use the same EXTTRAIL parameter value to add the local trail: % ggsci GGSCI (ggtest. the Application Virtual IP address is created with Cluster Ready Services (CRS) so that a single IP address can be moved between compute nodes. MGRPORT 8901 3.pdf To configure Oracle GoldenGate trail files on DBFS for the target database: 1. Megabytes 500 Further instructions about creating the Extract are available in the Oracle GoldenGate Administration Guide at http://docs.com) 1> ADD REPLICAT rep_db1. Set the EXTTRAIL Extract parameter: EXTTRAIL /mnt/dbfs/goldengate/dirdat/aa 3.com) 1> ADD EXTTRAIL /mnt/dbfs/goldengate/dirdat/aa.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration 2. To configure Data Pump between a source and target database outside the same Exadata Database Machine: 1.oracle.com/cd/E35209_01/doc. reducing availability. 2.

Store page files on the database server local file system within the Oracle GoldenGate installation directory structure. For instructions on creating the checkpoint table. transactions can be paged out to disk.com/cd/E35209_01/doc. Page files cannot be stored in DBFS because it is a memory mapped file.1121/e35957.1 or lower. When the cache becomes full. MEGABYTES 500 Further instructions about creating the Data Pump process are available in the Oracle GoldenGate Administration Guide at http://docs. EXTTRAILSOURCE /mnt/dbfs/goldengate/dirdat/aa 5. setting the Replicat commit behavior to COMMIT NOWAIT is configured separately from creating a checkpoint table. This should only be considered when using a checkpoint table due to protection of recovery data during a checkpoint.oracle.pdf Step 6: Configure Replicat Commit Behavior With Oracle GoldenGate version 11.1.pdf Step 5: Set Up Page Files on the Local File System Because Oracle GoldenGate only replicates transactions that are committed.com) 1> ADD EXTRACT dpump_1.com/cd/E35209_01/doc. see CACHEMGR in the Oracle GoldenGate Reference Guide at http://docs. Create a Data Pump process using the local trail file location on the source host: % ggsci GGSCI (ggtest.oracle.1 and above.com) 1> ADD RMTTRAIL /mnt/dbfs/goldengate/dirdat/aa EXTRACT dpump_1. Replicat will automatically operate using COMMIT NOWAIT. increasing throughput performance.1121/e29399.oracle. refer to the Oracle GoldenGate Installation and Setup Guide (Chapter 4): http://docs. By default. a file type that is not currently supported by DBFS.com/cd/E35209_01/doc.1121/e29397. The Replicat processes will no longer wait at each commit when applying transactions. Use the ADD RMTTRAIL command to specify the remote trail file location on the target host: % ggsci GGSCI (ggtest. the capture component stores the operations of each transaction in a virtual-memory pool known as a cache until it receives a commit or rollback for that transaction. 14 .pdf If using Oracle GoldenGate version 11.oracle. For more details. if a checkpoint table is configured.oracle.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration 4.2. the files are stored in the dirtmp sub-directory of the Oracle GoldenGate installation directory.

3 Oracle Grid Infrastructure Bundled Agent. Create an Application VIP. Otherwise. regardless of which node is hosting Oracle GoldenGate. perform the following steps: 15 .2.0. The VIP is assigned to a cluster node and will be migrated to another node in the event of a node failure. This allows Oracle GoldenGate data pump to continue transferring data to the newly assigned target node. explicitly name the processes you want to be restarted automatically. Step 7: Configure Autostart of Extract.3 use the instructions in Appendix A to create and register an Oracle GoldenGate resource with clusterware. If using a Grid Infrastructure release earlier than 11. An application virtual internet protocol address (VIP) is a cluster resource that Oracle Clusterware manages. an application VIP is required to ensure the remote data pumps can communicate with the target database machine.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Set the Replicat parameter file to COMMIT NOWAIT as follows: SQLEXEC "ALTER SESSION SET COMMIT_WRITE='NOWAIT'". and Replicat Processes Configure the Extract. 1. Add the following parameter to the Manager parameter file: AUTOSTART ER * AUTORESTART ER * If required. and Replicat processes to automatically start when the Manager process is started.2. Data Pump. and it uses Oracle GoldenGate Data Pump to transfer the trail file data to the target database machine. If both the Extract and Replicat processes are running within the same database machine and Data Pump is not used. If the source system is outside of the same Oracle Exadata Database Machine. Example: AUTOSTART EXTRACT EXT_1A AUTOSTART EXTRACT DPUMP_1A AUTORESTART EXTRACT EXT_1A AUTORESTART EXTRACT DPUMP_1A Step 8: Oracle Clusterware Configuration The following step-by-step procedure shows how to instruct Oracle Clusterware to start Oracle GoldenGate using the 11. then there is no need to create the Application VIP and you can skip to step 2 to create an agent script. instead of using the Oracle GoldenGate process name wildcard (*). Data Pump (if used).0.

execute: $GRID_HOME/bin/crsctl status resource gg_vip_source See the Oracle Clusterware documentation for further details about creating an Application VIP: http://docs.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration a. • ip is the IP address provided by your system administrator for the new Application VIP. As the Oracle Database installation owner.oracle. This IP address must be in the same subnet as determined above.network indicates this is network 1.41.network -ie subnet |grep -ie name -ie subnet Consider the following sample output: NAME=ora. and the second line indicates the subnet on which the VIP will be created.1. • gg_vip_source is the name of the application VIP that you will create. you can find the network number using the following command: crsctl stat res -p |grep -ie . Run the following command to give the Oracle Database installation owner permission to start the VIP: $GRID_HOME/bin/crsctl setperm resource gg_vip_source -u user:oracle:r-x c.network USR_ORA_SUBNET=10. start the VIP resource: $GRID_HOME/bin/crsctl start resource gg_vip_source d. • network is the network number that you want to use. b. run the following as the root user: $GRID_HOME/bin/appvipcfg create -network=1 \ -ip=10.htm 16 . With Oracle Clusterware release 11.com/cd/E11882_01/rac.93 \ -vipname=gg_vip_source \ -user=root In the example: • $GRID_HOME is the Oracle home in which Oracle 11g Release 2 Grid infrastructure components have been installed (for example: /u01/app/grid).0 net1 in NAME=ora.net1.112/e16794/toc.1.0. To validate whether the VIP is running and on which node it is running.41.2.net1.1. To create the application VIP.

dpump_1a On the Target environment: % agctl add goldengate GG_Target --gg_home /home/oracle/goldengate \ --instance_type target \ --nodes dbm03db01.2. and the DBFS mount point. 11.3/dbhome_1 \ --monitor_extracts ext_1a.2.0. Siebel.dbm03db02 \ --vip_name gg_vip_target \ --filesystems dbfs_mount --databases ggt \ --oracle_home /u01/app/oracle/product/11. The bundled agent for Oracle GoldenGate fully supports use of Extract running in classic or integrated capture modes.html Follow the installation instructions provided in the readme.2+ The bundled agent software should be downloaded from the following location: http://www. it is simple to create dependencies on the source/target database. Using the bundled agent for Oracle GoldenGate.2.1 and test to make sure crsctl can be used to mount and unmount the file system.3. Configure Oracle Grid Infrastructure Bundled Agent.0.dbm01db06 \ --vip_name gg_vip_source \ --filesystems dbfs_mount --databases ggs \ --oracle_home /u01/app/oracle/product/11.0.0. b. Mounting the file system should also start the DBFS instance if it is not already running.5.com/technetwork/products/clusterware/downloads/index. the Oracle Infrastructure Bundled Agents provide predefined clusterware resources for Oracle GoldenGate. and Apache applications. the application VIP. Configure DBFS as detailed in MOS note 1054431. The current version certification matrix: Grid Infrastructure 11.oracle.+ Database 10. Introduced in 11. The agent command line utility (agctl) is used to start and stop Oracle GoldenGate and can also be used to relocate Oracle GoldenGate between the nodes in the cluster.2.0.2.3 for 64bit Linux.1. Use agctl to create the Clusterware resource: On the Source environment % agctl add goldengate GG_Source --gg_home /home/oracle/goldengate \ --instance_type source \ --nodes dbm01db05.+ Oracle GoldenGate 11.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration 2.2.rep_3b Once the Oracle GoldenGate processes have been added to a bundled they should only be started and stopped using agctl.txt file.2.rep_3a. The bundled agent starts the Oracle 17 .rep_2a. Example configuration of the bundled agent: a.0.3/dbhome_1 \ --monitor_replicats rep_1a.

To view the configuration parameters for the Oracle GoldenGate resource: % agctl config goldengate GG_Target GoldenGate location is: /home/oracle/goldengate GoldenGate instance type is: source Configured to run on Nodes: dbm01db05 dbm01db06 ORACLE_HOME location is: /u01/app/oracle/product/11. Replicat) that have been configured to autostart.0. If an Oracle GoldenGate process aborts due to a problem. unless a node name or serverpool name is specified. as long as the manager process is still running it is okay to use ggsci to restart the failed process. Datapump. To start Oracle GoldenGate manager. To stop all Oracle GoldenGate processes: % agctl stop goldengate GG_Target [--serverpool serverpool_name | --node node_name] To relocate Oracle GoldenGate to another node: % agctl relocate goldengate GG_Source [--serverpool serverpool_name | --node node_name] Note: The Oracle GoldenGate resource MUST be running before relocating it.3/dbhome_1 Databases needed: ggs File System resources needed: dbfs_mount 18 . and all processes that have autostart enabled: % agctl start goldengate GG_Target [--serverpool serverpool_name | --node node_name] Note: Oracle GoldenGate will start up on the node you issue the command from. To check the status of Oracle GoldenGate: % agctl status goldengate GG_Source Goldengate instance 'GG_Source' is running on dbm01db06 ggsci can be used to check the status of individual Oracle GoldenGate processes.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration GoldenGate processes by starting Manager which in turn will automatically start the processes (Extract.2.

GG_Source.html 19 .Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Extracts to monitor: ext_1a.com/technetwork/products/clusterware/overview/ogibareference-guide-v1-1844341.goldengate" –p To delete the Oracle GoldenGate resource: % agctl remove goldengate GG_Source Further information on the Oracle Grid Infrastructure Bundled Agent: http://www.dpump_1a Replicats to monitor: To view more detailed clusterware configuration information: % crsctl stat res -w "NAME = xag.oracle.

Mounting of DBFS is carried out by a Clusterware resource which in turn has a start dependency on the DBFS instance. tnsnames. It is important to manually test the agent script to start and stop the Oracle GoldenGate processes before moving onto the next step. In this example. 20 . it is recommended to follow the configuration guidelines provided in My Oracle Support note 1054431. The agent script: • • • • • Must be able to accept five parameter values: start.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Appendix A: Creating Oracle GoldenGate Clusterware Resource If the Grid Infrastructure release is earlier than 11. Must be owned by the Oracle Grid Infrastructure user and have execute permissions. Oracle Clusterware runs resource-specific commands through an entity called an agent. Must include environment variable settings for ORACLE_HOME. The DBFS mount resource is named as a start dependency for the Oracle GoldenGate resource such that the required file systems are mounted BEFORE the Oracle GoldenGate processes are started. Register a resource in Oracle Clusterware. See Appendix B for an example agent script starts and stops the Oracle GoldenGate Manager.0. and Replicat processes. Register Oracle GoldenGate as a resource in Oracle Clusterware using the crsctl utility. ORACLE_SID. it will be started automatically. When using DBFS to store Oracle GoldenGate files. stop.2. Data Pump.ora or dbfs_client executable cannot be found when CRS tries to mount DBFS it will fail. Create an agent script (if not using the Bundled Agent) If you are not able to use the Oracle Grid Infrastructure Bundled Agent it is still possible to use Oracle Clusterware to manage automatic starting and stopping of Oracle GoldenGate. It is also recommended to list the source or target databases as start dependencies for the Oracle GoldenGate resource so that the Extract or Replicat processes won’t fail when it can’t connect to the database. Oracle GoldenGate can still be registered as a resource with Clusterware using the following instructions. If the correct sqlnet. 2. it is stored in the Grid Infrastructure ($GRID_HOME) ORACLE_HOME/crs/script directory. Extract. IF the DBFS resource is started and the instance is not running.3. clean and abort. TNS_ADMIN and LD_LIBRARY path so that CRS will be able to find the correct program executables and Oracle Net configuration. 1.ora. Must be accessible at the same location on every node in the cluster. PATH.1 (detailed above). Must be stored in the same location on all nodes. check.

CHECK_INTERVAL=30.htm 3.com/cd/E11882_01/rac.0/grid/crs/script/11gr2_gg_action.db)'.oracle.ora.ggs.dbfs_mount) pullup(gg_vip_source)'. SCRIPT_TIMEOUT=300" If an Application VIP is not used. START_DEPENDENCIES='hard(gg_vip_source.2.0/grid/crs/script/11gr2_gg_action. CHECK_INTERVAL=30. in this example) to execute the following: $GRID_HOME/bin/crsctl add resource GG_Source \ -type cluster_resource \ -attr "ACTION_SCRIPT=/u01/app/11. STOP_DEPENDENCIES=’hard(gg_vip_source)’.2. SCRIPT_TIMEOUT=300" For more information about the crsctl add resource command and its options. see the Oracle Clusterware Administration and Deployment Guide at http://docs. CHECK_INTERVAL=30.dbfs_mount. Start the resource. START_DEPENDENCIES='hard(dbfs_mount. Use the Oracle Grid Infrastructure user (oracle. you should always use Oracle Clusterware to start Oracle GoldenGate. HOSTING_MEMBERS=’dbm01db05 dbm01db06’. STOP_DEPENDENCIES=’hard(gg_vip_source)’.scr. Login as the Oracle Grid Infrastructure user (oracle) and execute the following: % $GRID_HOME/bin/crsctl start resource GG_Source 21 .0/grid/crs/script/11gr2_gg_action. then make sure the Extract and Replicat is restricted to the designated cluster nodes: $GRID_HOME/bin/crsctl add resource GG_Source \ -type cluster_resource \ -attr "ACTION_SCRIPT=/u01/app/11.scr.ggt. START_DEPENDENCIES='hard(gg_vip_source.2.scr. If the database machine is split into separate clusters such that the source and target run within the same database machine. issue the following command: $GRID_HOME/bin/crsctl add resource GG_Source \ -type cluster_resource \ -attr "ACTION_SCRIPT=/u01/app/11.112/e16794/toc. PLACEMENT=’restricted’.db) pullup(gg_vip_source)'. Determine the name of the DBFS or source/target database resource for the start dependency: crsctl status resource | grep -i dbfs|source/target DB name 2. Once the resource has been added.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration 1. SCRIPT_TIMEOUT=300" This paper assumes a single Oracle Exadata Database Machine is used for either a source (Extract) or target (Replicat) host.ora.

perform the following tasks: a) Stop Oracle GoldenGate (login as the Oracle Grid Infrastructure (oracle) user): $GRID_HOME/bin/crsctl stop resource GG_Source 22 . Manage the application. This command can be run on any node in the cluster as the Grid Infrastructure user (oracle). For example: [oracle@dbm01db05 ~]$ crsctl relocate resource gg_vip_source –f CRS-2673: Attempting to stop 'GG_Source' on 'dbm01db05' CRS-2677: Stop of 'GG_Source' on 'dbm01db05' succeeded CRS-2673: Attempting to stop 'gg_vip_source' on 'dbm01db05' CRS-2677: Stop of 'gg_vip_source' on 'dbm01db05' succeeded CRS-2672: Attempting to start 'gg_vip_source' on 'dbm01db06' CRS-2676: Start of 'gg_vip_source' on 'dbm01db06' succeeded CRS-2672: Attempting to start 'dbfs_mount' on 'dbm01db06' CRS-2676: Start of 'dbfs_mount' on 'dbm01db06' succeeded CRS-2672: Attempting to start 'GG_Source' on 'dbm01db06' CRS-2676: Start of 'GG_Source' on 'dbm01db06' succeeded To stop the Oracle GoldenGate resource. If there is a dependency on an Application VIP you need to relocate the VIP resource which in turn will stop Oracle GoldenGate. To remove Oracle GoldenGate from Oracle Clusterware management. CRS cleanup. enter the command: % $GRID_HOME/bin/crsctl status resource GG_Source For example: % crsctl status resource GG_Source NAME=GG_Source TYPE=cluster_resource TARGET=ONLINE STATE=ONLINE on dbm01db05 4. use the ‘$GRID_HOME/bin/crsctl relocate resource’ API and include the force (-f) option.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration To check the status of the application. enter the following command: $GRID_HOME/bin/crsctl stop resource GG_Source 5. relocate and restart it on the new node. To relocate Oracle GoldenGate onto a different cluster node.

scr. only the Clusterware resource. mount the file system only on the node where Oracle GoldenGate is running. delete the Oracle GoldenGate resource: $GRID_HOME/bin/crsctl delete resource GG_Source c) If no longer needed. delete the agent action script: 11gr2_gg_action. This action provides access to Oracle GoldenGate if it is restarted after a node failure. This does not delete the Oracle GoldenGate or DBFS configuration. 23 . Use the same mount point names on all the nodes to ensure seamless failover. • Ensure that the DBFS file system is mountable on all database nodes in the Oracle RAC configuration.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration b) As the root user. Recommendations When Deploying on Oracle RAC When Oracle GoldenGate is configured in an Oracle RAC environment. Mounting DBFS using a Clusterware resource to prevent the Extract or Replicat processes from being started on multiple nodes concurrently. follow these recommendations: • Ensure that the DBFS database has instances running on all the database nodes involved in the Oracle RAC configuration.

Extract. and Replicat processes. check. clean. stop.2.3/dbhome_1 export ORACLE_SID=GGS1 GGS_HOME=/home/oracle/goldengate/latest export PATH=$ORACLE_HOME/bin:$PATH export TNS_ADMIN=$ORACLE_HOME/network/admin #Include the GoldenGate home in the library path to start GGSCI export LD_LIBRARY_PATH=${ORACLE_HOME}/lib:${LD_LIBRARY_PATH}:${GGS_HOME} # Edit this to indicate the DBFS mount point DBFS_MOUNT_POINT=/mnt/dbfs # Edit this to indicate at least one of the file systems mounted in # the DBFS mount point DBFS_FILE_SYSTEM=/mnt/dbfs/goldengate # Edit for correct Extract/Datapump name if running this script on # the source (widlcard is appended to these names in the script): EXTRACT=EXT DATAPUMP=DPUMP # Edit for current Replicat names if running script on the target # (widlcard is appended to these names in the script): REPLICAT=REP # Specify delay after start before checking for successful start start_delay_secs=5 ### Syslog facility name (default user) 24 . The agent script accepts the parameter values: start.scr # Edit the following environment variables: # NOTE: The ORACLE_SID will be different on each node export ORACLE_HOME=/u01/app/oracle/product/11.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration Appendix B: Example Agent Script The following example agent script mounts and unmounts a DBFS file system upon startup and failover.0. as well as starting and stopping the Oracle GoldenGate Manager. and abort. #!/bin/bash #11gr2_gg_action.

then echo $msg $LOGGER -p ${LOGGER_FACILITY}. error.pcm 25 .debug "$msg" fi } # check_process validates that Manager/Extract/Replicat process is # running #at PID that GoldenGate specifies. then LINUX=0. SOLARIS=1. then LINUX=1.info "$msg" elif [ "$type" = "error" ]. check_process () { PROCESS=$1 if [ ${PROCESS} = mgr ] then PFILE=MGR. SOLARIS=0. logit () { ### type: info. debug type=$1 msg=$2 if [ "$type" = "info" ].Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration ### Changed default from local3 to user for Solaris default support on 17FEB-2012 ### This will allow us to log messages to the syslog ### (/var/log/messages on Linux. then echo $msg $LOGGER -p ${LOGGER_FACILITY}.error "$msg" elif [ "$type" = "debug" ]. then echo $msg $LOGGER -p ${LOGGER_FACILITY}. /var/adm/messages on Solaris) LOGGER_FACILITY=user ########################################### ### No editing is required below this point ########################################### ### determine platform UNAME_S=`uname -s` if fi LOGGER="/bin/logger -t GoldenGate" [ $UNAME_S = 'Linux' ]. elif [ $UNAME_S = 'SunOS' ].

no pid file" exit 1 fi } # call_ggsci is a generic routine that executes a ggsci command call_ggsci () { ggsci_command=$1 ggsci_output=`${GGS_HOME}/ggsci << EOF ${ggsci_command} exit 26 .Procese(s) ${PROCESS} IS running" exit 0 else if [ ${pid} = `ps -e |grep ${pid} |grep ${PROCESS} |cut -d " " -f1` ] then logit info "${SCRIPTNAME}(check_process) .Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration elif [ ${PROCESS} = ext ] then PFILE=${EXTRACT}*.Procese(s) ${PROCESS} IS running" exit 0 else logit error "${SCRIPTNAME}(check_process) .Procese(s) ${PROCESS} is NOT running" exit 1 fi fi else logit error "${SCRIPTNAME}(check_process) .pce fi if ( [ -f "${GGS_HOME}/dirpcs/${PFILE}" ] ) then pid=`cut -f8 "${GGS_HOME}/dirpcs/${PFILE}"` if [ ${pid} = `ps -e |grep ${pid} |grep ${PROCESS} |cut -d " " -f2` ] then logit info "${SCRIPTNAME}(check_process) .Procese(s) ${PROCESS} is NOT running .pce elif [ ${PROCESS} = rep ] then PFILE=${REPLICAT}*.pcr else PFILE=${DATAPUMP}*.

start .Starting Manager.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration EOF` } stop_everything () { # Before starting.Stopping all processes" call_ggsci 'stop er *' #ensure everything is stopped call_ggsci 'stop er *!' #in case there are lingering processes call_ggsci 'kill er *' #stop Manager without (y/n) confirmation call_ggsci 'stop manager!' #Remove the process files: rm -f $GGS_HOME/dirpcs/MGR.Starting all processes" stop_everything sleep ${start_delay_secs} #Now can start everything.pcm rm -f $GGS_HOME/dirpcs/*.pcr } case $1 in 'start') # stop all GG processes and remove process files logit info "${SCRIPTNAME} ..pce rm -f $GGS_HOME/dirpcs/*. make sure everything is shutdown and process files are removed #attempt a clean stop for all non-manager processes logit info "${SCRIPTNAME}(stop_everything) .. #start Manager logit info "${SCRIPTNAME} .start . autostarting processes" call_ggsci 'start manager' 27 .

.Checking all processes" check_process mgr check_process ext check_process dpump check_process rep .Checking Manager status" check_process mgr sleep ${start_delay_secs} #Check whether Extract is running logit info "${SCRIPTNAME} .Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration #there is a small delay between issuing the start manager command #and the process being spawned on the OS <96> wait before checking sleep ${start_delay_secs} #start Extract or Replicats call_ggsci 'start er *' #check whether Manager is running and exit accordingly logit info "${SCRIPTNAME} .start .start .stop ..Stopping all processes" stop_everything #exit success exit 0 . 'clean') # stop all GG processes and remove process files logit info "${SCRIPTNAME} .Checking GoldenGate statuses" check_process ext check_process dpump .check .. 'check') logit info "${SCRIPTNAME} . 'stop') # stop all GG processes and remove process files logit info "${SCRIPTNAME} .clean .Stopping all processes" stop_everything 28 .

.1..1. esac References • • • • • Oracle GoldenGate Administration Guide version 11.2.com/goto/maa 29 .0.1 Oracle Database SecureFiles and Large Object Developer’s Guide (DBFS) Oracle Clusterware Administration and Deployment Guide Oracle Maximum Availability Architecture Web site http://www.1.otn.Stopping all processes" stop_everything #exit success exit 0 .1 Oracle GoldenGate Reference Guide version 11.2.abort .oracle.0.2.1 Oracle GoldenGate Oracle Installation and Setup Guide version 11. 'abort') # stop all GG processes and remove process files logit info "${SCRIPTNAME} .0.Oracle Maximum Availabiity Architecture Oracle GoldenGate on Oracle Exadata Database Machine Configuration #exit success exit 0 .

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Oracle and/or its affiliates. including implied warranties and conditions of merchantability or fitness for a particular purpose. and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. AMD. Inc. without our prior written permission. This document is not warranted to be error-free. for any purpose. Other names may be trademarks of their respective owners.506.650. the AMD logo.S. whether expressed orally or implied in law. nor subject to any other warranties or conditions.650. 1010 .506. UNIX is a registered trademark licensed through X/Open Company. This document is provided for information purposes only and the contents hereof are subject to change without notice. We specifically disclaim any liability with respect to this document and no contractual obligations are formed either directly or indirectly by this document.A. CA 94065 U.7200 oracle. Opteron. All rights reserved. Ltd. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International.7000 Fax: +1. Worldwide Inquiries: Phone: +1.com Copyright © 2013.Oracle GoldenGate on Oracle Exadata Database Machine Configuration January 2013 Author: Stephan Haisley Contributing Authors: MAA team Oracle Corporation World Headquarters 500 Oracle Parkway Redwood Shores. electronic or mechanical. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. This document may not be reproduced or transmitted in any form or by any means.