Friday , December 6 2024

Install Oracle GoldenGate 12.2.0.0.0

In today’s article, we will be talking about how to install Oracle GoldenGate 12.2.0.0.0.

Before starting the GoldenGate installation, GRID, RDBMS and Database are installed on both SOURCE and TARGET servers.

In addition, there are Schemas, Tables and data in them on the SOURCE database.

After this, the steps for the GOLDENGATE installation are as follows.

1. A user is created for GoldenGate on the operating system side (Source1-2, Target1-2).

2. Goldengate users’ BASH_PROFILE files are set as follows (Source1-2, Target1-2).

3. GoldenGate software needs to be installed in a SHARED area in RAC systems.

Therefore, Shared areas should be MOUNTED to all servers. Shared area should be NFS. (Source1-2, Target1-2).

4. The OGG_HOME folder is created on the SOURCE side (Source1-2).

5. The OGG_HOME folder is created on the TARGET side (Target1-2).

6. The ZIP file we downloaded is opened in the Shared area (Source1, Target1).

7. Now we can install GoldenGate on both SOURCE and TARGET sides (Source1 , Target1).

a. We perform the installation process on only 1 node on both the source and target sides.

b. The database we are installing is Oracle 11g R2, I choose the second option below.

c. We determine the Software location where the GoldenGate application will be installed.

This location must be a SHARED area in RAC systems and must be accessible from both server sides.

These locations are as follows for me;

After determining the location where the software will be installed, the MANAGER PORT needs to be specified.

I specified 7809 for source and 7810 for target.

Before giving these ports, it is necessary to check if the ports below are used.

f. After completing the above operations, when we pass with “NEXT”, it may give a warning as below. We can pass this with “YES”.

 

g. When we click the Install button, the installation will start.

h. Let’s pass with “YES”.

8. After the installation is completed on both sides, we check whether the MANAGER Ports are in use.

9. We can control goldengate usage with GGSCI.

10. We create a tablespace and user for GG in the Source database. Then we give DBA permission to this user (SOURCE1).

11. We do the same operations as above for the Target side (TARGET1).

12. Putting the database in archive mode will be good for GoldenGate replication. This can be done as follows (SOURCE1).

13. We perform SUPPLEMENTAL LOGGING and FORCE LOGGING operations in the source database (SOURCE1).

14. We do the same operations as above in the Target database (TARGET1).

15. On the source side, I set the TNS file as follows (SOURCE1-2).

16. On the target side, the TNS file was edited as above (TARGET1-2).

17. The “enable_goldengate_replication” parameter in the database must be set to TRUE as shown below. Otherwise, the following error will be received (SOURCE1).

Error:

18. The value of the “enable_goldengate_replication” parameter must also be set to TRUE on the Target side. Otherwise, when REPLICAT is started, it will receive an error as above (TARGET1).

19. We create a GLOBAL parameter file in the target database with the following operations. We specify the checkpoint table in this parameter file for later use (TARGET1).

20. On the source side, we perform the TRANDATA operation as follows (SOURCE1).

21. We check the tables added to the TRANDATA transaction (SOURCE1).

22. We added the SCOTT schema that we will replicate above with the TRANDATA Option. Now we create an EXTRACT for this schema (SOURCE1).

23. The EXTRACT that performs the PUMP operation is created (SOURCE1).

24. Now we can start our EXTRACT Processes (SOURCE1).

25. Using the GLOBAL parameter file we created earlier, the CHECKPOINT table can be created in the Target database as follows (TARGET1).

26. The REPLICAT that will replicate the tables of the SCOTT schema is created as follows (TARGET1).

27. The tables to be replicated must be created on the Target side in advance, for this the INITIAL LOAD process will be performed.

The process steps are as follows.

a. The export of the schema is taken according to the SCN number (SOURCE1).

b. The received export target is imported into the database (TARGET1).

c. RELICAT export is started from the received SCN number (TARGET1).

e. The status of REPLICAT is checked (TARGET1).

28. Finally, let’s check whether the data has been transferred to the other party.

a. First, data is added to the replicated table on the Source side (SOURCE1).

b. RBA values ​​can be recorded before and after the INSERT operation for control purposes (TARGET1).

c. The table is checked on the target side.

Loading

About Onur ARDAHANLI

Leave a Reply

Your email address will not be published. Required fields are marked *