Oracle GoldenGate 11g Installation on IBM AIX 6x (RAC and Single Instance)

Oracle GoldenGate 11g Installation on IBM AIX 6x

Supported Platforms:

Databases:

Oracle 9.2 (DML and DDL support)

Oracle 10.1 and 10.2 (DML and DDL support)

Oracle 11g (DML and DDL support)

Pre-requisites:

The Oracle GoldenGate GGSCI command interface fully supports up to 300 concurrent Extract and Replicat processes per instance of Oracle GoldenGate. Each Extract and Replicat process needs approximately 25-55 MB of memory, or more depending on the size of the transactions and the number of concurrent transactions.

Disk requirements

Assign the following free disk space:

50-150 MB, depending on the database and platform. This includes space for the compressed download file and space for the uncompressed files. You can delete the download file after the installation is complete.

To install Oracle GoldenGate into a cluster environment, install the Oracle GoldenGate binaries and files on a shared file system that is available to all cluster nodes.

Additional disk space on any system that hosts Oracle GoldenGate trails, which are files that contain the working data. The space that is consumed by the trails varies, depending on the volume of data that will be processed. A good starting point is 1 GB. Use the following formula to calculate the required disk space.

[log volume in one hour] x [number of hours downtime] x .4 = trail disk space

Oracle RAC requirements

To install Oracle GoldenGate in an Oracle Real Application Cluster (RAC) environment, install Oracle GoldenGate on the shared drive(s) that are accessed by the RAC nodes. This allows you to start the Oracle GoldenGate processes from any of the nodes. If the node where they are running fails, you can start them on another node without modifying parameter files, because the processing checkpoints are preserved in the installation directory.

All nodes in the RAC cluster must have synchronized system clocks. These clocks must be synchronized with the clock on the system where Extract is executed. Oracle GoldenGate compares the time of the local system to the commit timestamps to make critical decisions.

TCP/IP

Configure the system to use TCP/IP services, including DNS. A range of ports for local Oracle GoldenGate communications: can be the default range starting at port 7840 or a customized range of up to 256 other ports.

Configure your firewalls to accept connections through the Oracle GoldenGate ports.

Operating system privileges

To install on IBM AIX or any UNIX system, the user installing Oracle GoldenGate must have read and write privileges on the Oracle GoldenGate installation directory. On AIX or UNIX systems, that user must be a member of the group that owns the Oracle instance.

Database user

Create a database user that is dedicated to Oracle GoldenGate. It can be the same user for all of the Oracle GoldenGate processes that must connect to a database.

Oracle recycle bin

Because of a known issue in Oracle 10g, the Oracle recycle bin must be turned off to support Oracle GoldenGate DDL replication. If the recycle bin is enabled, the Oracle GoldenGate DDL trigger session receives implicit recycle bin DDL operations that cause the trigger to fail.

Installation Steps:

Setting Environment Variables:

Make certain that the ORACLE_HOME and ORACLE_SID system environment variables are set to the correct Oracle instance. The Oracle GoldenGate processes refer to them when connecting to the database.

PATH=<absolute path of installation directory>:$PATH

export PATH

Note : On  IBM AIX the shared libraries vairiable would be   LIBPATH so, 
LIBPATH = <absolute path of installation directory>

Export  LIBPATH

Installing into a UNIX or Linux cluster

To install Oracle GoldenGate into a cluster environment, install the Oracle GoldenGate binaries and files on a file system that is available to all cluster nodes, according to the directions that follow.

After installing Oracle GoldenGate, configure the Manager process within the cluster application, as directed by the cluster documentation, so that Oracle GoldenGate will fail over properly with the other applications.

Installing the Oracle GoldenGate files

Extract the Oracle Oracle GoldenGate mediapack.zip file to the AIX or unix system and directory where you want Oracle GoldenGate to be installed.

Run the command shell and change directories to the new Oracle GoldenGate directory.

From the Oracle GoldenGate directory, run the GGSCI program.

GGSCI

In GGSCI, issue the following command to create the Oracle GoldenGate working directories.

CREATE SUBDIRS

Issue the following command to exit GGSCI.

EXIT

Oracle GoldenGate parameters settings for RAC

On AIX and Solaris machines, use the Extract parameter THREADOPTIONS with the BINDCPU option. This parameter handles thread-safety issues related to memory that is updated by different processors.

Oracle GoldenGate queues data in memory before sending it to the target system. The INQUEUESIZE and OUTQUEUESIZE options of the THREADOPTIONS parameter determine how much data to queue. If needed, you can increase the performance of Extract on Oracle RAC by tuning these parameters.

Special procedures on RAC

If the primary database instance against which Oracle GoldenGate is running stops or fails for any reason, Extract will abend. To resume processing, you can restart the instance, or you can mount the Oracle GoldenGate binaries to another node where the database is running and then restart the Oracle GoldenGate processes. Stop the Manager process on the original node before starting Oracle GoldenGate processes from another node.

Any time the number of redo threads changes, the Extract group must be dropped and re-created.

Applying database patches and upgrades when DDL support is enabled

Database patches and upgrades usually invalidate the Oracle GoldenGate DDL trigger and other Oracle GoldenGate DDL objects. Before applying a database patch, do the following.

Disable the Oracle GoldenGate DDL trigger by running the following script.

@ddl_disable

Apply the patch.

Enable the DDL trigger by running the following script.

@ddl_enable