In the previous article, we have seen installing Golden Gate software.
Preparing Environment for Oracle Golden Gate Extract and Replication Part – I
In this article, we will see
  1. Creation of user for  Golden Gate extract process configuration
  2. Golden Gate replicat process configuration
  3. Enable Archive logging
  4. Enable Supplemental Logging
We will start with User Creation
  • User Creation at extserver
  • User Creation at repserver
First, we will create user extserver : Step 1: Create a tablespace for golden gate user Step 2: Create a user for Golden Gate configuration Here I have created a common user as I am using Golden Gate for a multitenant environment. Step 3: Grant necessary privileges for Golden Gate extract process Now we will create a user at repserver Step 1: Create a tablespace Step 2: Create a user Step 3: Grant necessary privileges to replication configuration user Note: We can see the difference between the privileges of extract and replicat process  Extract process does not need DML operation privileges whereas the replicat process does not need flashback any table privilege. 3. Enable Archivelog: Archivelog mode is must in golden gate configuration so if your database does not have archiving enabled, enable it Archivelog in Oracle Database 4. Enable Force logging 5. Enable supplemental logging. 6. Set enable_goldengate_replication parameter to TRUE value. Now we have set all necessary parameters at the database level. Step 7: Add trandata for objects to be replicated using Golden Gate with the ggsci prompt We can add trandata using ADD TRANDATA or ADD SCHEMATRANDATA ADD TRANDATA :  Add Trandata enables supplemental logging of key values in the transaction logs whenever a row change occurs. If we do not use Add Trandata for objects, DML [update and delete] will fail to be propagated to the target system and Replicat process may abend as by default only those columns are recorded in redo log which is updated. ADD SCHEMATRANDATA :  ADD SCHEMATRANDATA functions as Add Trandata only but using this will give extra functionality as it will also add trandata for future tables which will be created in that schema. Means, Add Trandata will add trandata for existing tables only, and if we create a new table in that schema we need to explicitly add trandata for those tables whereas adding schema trandata will help in this case we don’t need to add trandata for that table explicitly, it will happen implicitly. Note: Oracle strongly recommends using schema-level logging rather than table-level logging, because it ensures that any new tables added to a schema are captured if they satisfy wildcard specifications. So I am going to add SchemaTrandata for my configuration. Before adding SCHEMATRANDATA grant admin privileges to golden gate user : In the next lecture, we will see the configuring manager in Golden Gate If you want to be updated with all our articles send us an Invitation or Follow us: Telegram Channel: Skant Gupta’s LinkedIn: Joel Perez’s LinkedIn: Joel Perez’s Profile LinkedIn Group: Oracle Cloud DBAAS Facebook Page: OracleHelp

About The Author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.