Prepare GoldenGate for Data Transfer

Use Oracle GoldenGate to load, distribute, and filter transactions within your enterprise in real-time and to enable migrations between different databases.

The Oracle GoldenGate microservice compute node acts as a hub where you can manage your connections to source and target databases. To do this, establish a network connection between the compute node (Oracle GoldenGate) and your source and target databases.

Provision Oracle GoldenGate

Provision Oracle GoldenGate microservice from Oracle Cloud Marketplace.

Sign in to the Oracle Cloud Infrastructure service console.
Click Marketplace.
Enter GoldenGate in the search field.
Click Oracle GoldenGate in the search results.
Select the version. Oracle GoldenGate Microservices Edition is selected by default.
Select the compartment where the associated compute node is built.
Click Launch Stack.
Specify the required Stack information and then click Next:
- Name - Name of the Stack. The stack has a default name and provides a date-time stamp. You can edit this detail, if required.
- Description - Description that you provide while creating the Stack.
- Create In Compartment – The stack defaults to the compartment you have selected for the microservice.
Configure the required variables. This information is required to build the compute node with Oracle GoldenGate Microservices.
- Name for New Resources -
  1. Display name – Display name used to identify all new Oracle Cloud Infrastructure resources.
  2. Host DNS Name – Name of the Domain Name Service for the new compute node.
- Network Settings -
  1. Create New Network – Select this check box if you wish to create a new network resource.
    - If you select this check box, the Create New Network wizard appears allowing you to add and edit the new network information.
    - If you do not select this check box, the Create New Network wizard does not appear and the compute node is created with the existing network options in the VCN.
  2. Network Compartment (optional) – Compartment for new or existing network resources.
- Use Existing Network -
  1. VCN (optional) – Existing VCN to use for the newly created instance if you are not creating a new network.
  2. Subnet (optional) – Existing subnet to use for the newly created instance if you are not creating a new network. The subnet that you have selected must match the same Availability Domain set in the Instance Settings.
- Instance Settings -
  1. Availability Domain – Specifies the availability domain for the newly created Oracle GoldenGate Instance. It must match the Subnet that you have selected in the Use Existing Network settings.
  2. Compute Shape – A shape is a template that determines the number of CPUs, amount of memory, and other resources allocated to a newly created virtual machine (VM) instance.
  3. Assign Public IP – This option indicates if the newly created VM should have a public IP address. This option is selected by default. If you clear this check box, no public IP address will be assigned preventing public access to the compute node.
  4. Custom Volume Sizes - Select this check box to customize the size of the new block storage volumes that are built for the compute node. Block Storage (Custom Volume Sizes)
    1. Boot Volume Size – Default value is 50GB
    2. Swap Volume Size – Default value is 256GB
    3. Trails Volume Size – Default value is 512GB
    4. Deployments Volume Size – Default value is 128GB
- Create OGG Deployments -
  1. Deployment 1 – Name (mandatory) – Name of the first Oracle GoldenGate Microservices deployment. For example source.
  2. Deployment 1 – Database (mandatory) – Oracle Database version for deployment 1.
  3. Deployment 2 – Name (optional) – Name of the second Oracle GoldenGate deployment. For example, target.
  4. Deployment 2 – Database (optional) – Oracle Database version for deployment 2.
- Shell Access -
  1. SSH Public Key - Public Key for allowing SSH access as the standard opc user.
Click Next.
Review the information you provided and then click Create.
Use the Stacks Job Details page to monitor the creation of the compute node. This process can take several minutes.
When the job completes, you can view the Oracle GoldenGate Microservices compute node under the Instances tab.

Change Default Service Manager Password

Use secure shell (SSH) to sign in to the virtual machine as the oracle user (opc).
```
$ ssh -i <private key> opc@<public_ip_address>
```

Get the Oracle GoldenGate admin credential for the Oracle GoldenGate admin user (oggadmin):

$ pwd
$ /home/opc
$ ls -lrt
  total 0
  lrwxrwxrwx. 1 opc opc 37 Jul 25 05:54 ogg-credentails.json -> /u02/deployments/ogg-credential.json
$ cat ogg-credentails.json
  ("username": "oggadmin", "credential": "<credential>")

Use a browser to open the public IP assigned to your Oracle GoldenGate instance and sign in as oggadmin with the password credential you discovered in the previous step.
Click the menu at the top left corner and select Administrator.
For the oggadmin user, click the associated pencil icon under Action.
Enter a new password in the Password field.
Enter the password again in the Verify Password field.

Note:
Passwords must be 8 to 30 characters long and contain at least 1 uppercase, 1 lowercase, 1 numeric, and 1 special character. Special characters such as ‘$’, ‘^’, or ‘?’ are not allowed.

After successfully resetting the password, you are signed out. Sign in again using the new password.

Change Default Administration Server Password

Sign in to your newly provisioned Oracle GoldenGate instance to change the default passwords for both the source and target administration servers.

Perform the steps below for both the source and target administration servers.

Use a browser to open the public IP assigned to your Oracle GoldenGate instance and sign in as oggadmin.
Click the Port number for the source Administration Server.
For the oggadmin user, click the associated pencil icon under Action.
Enter a new password in the Password field.
Enter the password again in the Verify Password field.

Note:
Passwords must be 8 to 30 characters long and contain at least 1 uppercase, 1 lowercase, 1 numeric, and 1 special character. Special characters such as ‘$’, ‘^’, or ‘?’ are not allowed.

After successfully resetting the password, you are signed out. Sign in again using the new password.
Repeat the above steps for the target Administration Server.

Verify Service Manager Environment Variables

Use the Oracle GoldenGate Service Manager to validate and change environment variables as necessary.

Perform the steps below for both the source and target deployments.

Use a browser to open the public IP assigned to your Oracle GoldenGate instance and sign in as oggadmin.
Under Deployments, click the deployment name, such as source.
Click the Configuration tab to view environment variables.
Verify that the values for the environment variables are correct.
For example, to change the TNS_Admin variable:
1. Click the pencil icon next to the variable name.
2. Enter the new variable value. For example, for the source deployment, enter:
```
/u01/app/client/oracle12/network/admin
```
If you change an environment variable, restart the deployment. From the Service Manager page, click the Action menu next to the deployment, select Stop, and then select Start.
Repeat steps 2 through 5 for the target deployment, updating the TNS_Admin variable with the appropriate path, for example, /u01/app/client/oracle18/network/admin.

Verify Virtual Machine Connectivity

Verify the connections from the compute node to the source and target databases.

Use secure shell (SSH) to sign in to the virtual machine as the oracle user (opc).
```
$ ssh -i <private key> opc@<public_ip_address>
```

Set the necessary environment variables. For example:

$ export ORACLE_HOME=/u01/app/client/oracle12
$ export TNS_ADMIN=$ORACLE_HOME/network/admin
$ export PATH=$ORACLE_HOME/bin:$PATH

Verify the values in the tnsnames.ora file:

$ cat $TNS_ADMIN/tnsnames.ora
ORCL= 
 (DESCRIPTION= 
   (ADDRESS=(PROTOCOL = TCP)(HOST = example)(PORT = 1521))
   (CONNECT_DATA= 
     (SERVER = DEDICATED)
	SERVICE_NAME = <ORCL_service_name>)
    ) 
)

PDB1= 
 (DESCRIPTION= 
   (ADDRESS=(PROTOCOL = TCP)(HOST = example)(PORT = 1521))
   (CONNECT_DATA= 
     (SERVER = DEDICATED)
	SERVICE_NAME = <pdb1_service_name>)
    ) 
)

Verify the values in the sqlnet.ora file:

$ cat $TNS_ADMIN/sqlnet.ora
NAMES.DIRECTORY_PATH = (TNSNAMES, ONAMES, HOSTNAMES)
#NAMES.DEFAULT_DOMAIN = ora.com

Verify the values in the hosts file:

$ cat /etc/hosts
127.0.0.1	localhost  localhost.localdomain  localhost4  localhost4.localdomain4
::1		localhost  localhost.localdomain  localhost6  localhost6.localdomain6
255.255.255.1  ogg191.example.com ogg191
255.255.255.2  adwsrc.example adwsrc

Use SQL*Plus to validate the connection to the source database. For example:

$ sqlplus adwsrc@pdb1/ADWpass123_#

SQL*Plus: Release 12.2.0.1.0 Production on Thu Jul 25 10:30:01 2019
Version 18.1.0.0.0

Copyright (c) 1982, 2016, Oracle.  All rights reserved.

Last Successful login time: Tue Jul 25 2019 12:45:05 -07:00

Connected to:
Oracle Database 18c EE Extreme Perf Release 18.0.0.0.0 – Production

SQL>

Verify connection information and use SQL*Plus to validate the connection to the target database. For example:

$ cd $TNS_ADMIN
$ grep adwus2_low tnsnames.ora
adwus2_low = (description= (address=(protocol=tcps)(port=1522)(host=example.com))(connect_data=(service_name=eo4tfsiqpxmhmow_example.com))(security=(ssl_server_cert_dn=
        "CN=example.com,OU=Oracle BMCS US,O=corporation,L=city,ST=state,C=country"))   )


$ cat sqlnet.ora
WALLET_LOCATION = (SOURCE = (METHOD = file) (METHOD_DATA = (DIRECTORY="/u01/app/client/oracle18/network/admin")))
SSL_SERVER_DN_MATCH=yes
$ sqlplus admin@adwus2_low/ADWpass123_#
SQL*Plus: Release 18.0.0.0.0 Production on Thu Jul 25 07:30:01 2019
Version 18.3.0.0.0

Copyright (c) 1982, 2018, Oracle.  All rights reserved.

Last Successful login time: Tue Jul 25 2019 07:45:05 -07:00

Connected to:
Oracle Database 18c Enterprise Edition Release 18.0.0.0.0 – Production
Version 18.4.0.0.0

SQL>