Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Former Member

                                                                                     Oracle Golden Gate

Oracle GoldenGate enables the exchange and manipulation of data at the transaction level among multiple, heterogeneous platforms across the enterprise1. Its modular architecture gives you the flexibility to extract and replicate selected data records, transactional changes, and changes to DDL (data definition language2) across a variety of topologies.


With this flexibility, and the filtering, transformation, and custom processing features of Oracle GoldenGate, you can support numerous business requirements: Oracle GoldenGate enables the exchange and manipulation of data at the transaction level among multiple, heterogeneous platforms across the enterprise1. Its modular architecture gives you the flexibility to extract and replicate selected data records, transactional changes, and changes to DDL (data definition language2) across a variety of topologies.


With this flexibility, and the filtering, transformation, and custom processing features of
Oracle GoldenGate, you can support numerous business requirements:
• Business continuance and high availability.
• Initial load and database migration.
• Data integration.
• Decision support and data warehousing. Business continuance and high availability.
• Initial load and database migration.
• Data integration.
• Decision support and data warehousing.

Oracle Golden Gate Architecture

Oracle GoldenGate can be configured for the following purposes:
• A static extraction of data records from one database and the loading of those records to another database.
• Continuous extraction and replication of transactional DML1 operations and DDL changes (for supported databases) to keep source and target data consistent.
• Extraction from a database and replication to a file outside the database


• Initialize the Oracle Advanced Customer Service (ACS) for SAP O2O (Oracle to Oracle) package which includes all functionality to create a complete set of migration scripts including a new source user creation, target database and related tablespace creation, and the OGG source and target configurations.


•  Install the Oracle GoldenGate software on source and target


• Run the O2O package on the source system

Start GoldenGate change data extract and pump processes on the source system, which will being capturing and queuing change data and DDL (as needed).


Note: All tables in the SAPR3 schema will be included and will contain a SCN/CSN token so that later each table can be filtered by SCN/CSN.

A code snippet to add such as token is:\
Table SAPR3.*, Tokens (tk-csn = @GETENV ("TRANSACTION", "CSN"));
• Start the initial database load to copy the database objects from the source to target database.
• Validate initial database load.
• Start GoldenGate replicate apply processes on the target system, which will be applying captured change data and DDL (as needed). Note: While the replicate process(es) will be started using the AFTERCSN option, tables within a single replicate will be configured to skip transactions based on the table grouping of the initial loads. This automatically configured by the O2O scripts. Transaction filter by table will be done with something similar to the following code snippet:\
Map SAPR3.MYTABLE, Target SAPR3.MYTABLE, Filter ( @NUMSTR (@TOKEN ("TK-CSN")) > 1234567);
• Switch over. Once both system are in sync the source SAP system may be stopped. After the last changes is applied to the target the SAP system can be started
• On the target system. The source SAP shutdown and target SAP start-up will typically take approximately Minimal time regardless of the system size.

High Level Steps

Identify schemas to be migrated.
Identify Triggers which needs to be disabled on 11g target database
Identify Sequences which needs to be replicated.
Identify Services which needs to be created on the 11g target database
Identify cron jobs or any other jobs which needs to be transferred to 11g target database server.
Verify Firewall is open between the 11g source and 11g target database and also the clients connecting to the 11g target database.
Check the GG ports are enabled for source and target (7809-7840)
Create database on 11g target cluster
Install OGG on source and target servers.
Enable the supplementary login for database and table level GG configuration on source
Setup the GG environment on source and target.
Configure the GG parameter files on source and target.
Start OGG Manager &  Extract on source database.
Perform consistent Export on source database with current SCN for initial load.
Perform initial load using import on the target database
Start OGG replication on the target database after SCN(which is used in EXPDP)
Keep target database in-sync with source database.
Lock all the user accounts on target database.
Perform test on target database.
Start SAP application.

1 Comment
Labels in this area