Using Oracle GoldenGate Cloud Service with Database Classic Cloud Service

This topic does not apply to Oracle Cloud Infrastructure.

Oracle GoldenGate Cloud Service is a secure, high performance data integration and replication service that can replicate data in real time from on-premises databases to single-instance databases in Oracle Database Classic Cloud Service.

You must create a Database Classic Cloud Service database deployment that is properly configured for use as a GoldenGate Cloud Service replication target before you create a GoldenGate Cloud Service instance.

To properly configure a Database Classic Cloud Service database deployment for use as a replication target:

You must configure the database deployment to use characteristics (like database release, database edition and so on) that are supported by Oracle GoldenGate Cloud Service.

See Before You Begin with Oracle GoldenGate Cloud Service in Using Oracle GoldenGate Cloud Service for information about the Database Classic Cloud Service characteristics that Oracle GoldenGate Cloud Service supports.
You must configure the database deployment for use as a replication database.

You can configure the database deployment for use as a replication database by setting the Enable Oracle GoldenGate option on the Instance Details page of the Create Instance wizard, or you can configure it manually after the database deployment is created by using the dbaascli utility. See Manually Configuring a Deployment’s Database for Oracle GoldenGate Cloud Service Replication for instructions on configuring it manually.
The target database must be network accessible on the listener port.

To enable access on the listener port, you need to enable the ora_p2_dblistener security rule automatically created for the Database Classic Cloud Service database deployment when the deployment was created. See Enabling Port Access by Enabling an Automatically Created Access Rulefor instructions.

Once you have created and properly configured a Database Classic Cloud Service database deployment for use as a replication target, you can create an Oracle GoldenGate Cloud Service instance that uses it. See Provision an Oracle GoldenGate Cloud Service Instance in Using Oracle GoldenGate Cloud Service.

Manually Configuring a Deployment’s Database for Oracle GoldenGate Cloud Service Replication

Before you can use an Oracle Database Classic Cloud Service database deployment as a replication target in Oracle GoldenGate Cloud Service, you must configure its database as a valid replication database.

You can configure the database during database deployment creation by setting the Enable Oracle GoldenGate option on the Service Details page of the wizard. If you do not, you can configure it manually after the database deployment is created by using the dbaascli utility.

To configure the database manually after the database deployment is created:

Connect as the oracle user to the database deployment’s compute node.

For detailed instructions, see Connecting to a Compute Node Through Secure Shell (SSH).
Confirm that the database is not yet configured as a valid replication database:
```
$ dbaascli gg status
DBAAS CLI version 1.0.0
Executing command gg status

Golden Gate status: disabled.
```
If the status is listed as disabled, you need to configure the database; if it is listed as enabled, you do not.
Configure the database as a valid replication database by using the dbaascli gg setup command:
```
$ dbaascli gg setup
DBAAS CLI version 1.0.0
Executing command gg setup
Enter Golden Gate admin username: admin-username
Enter Golden Gate admin password: admin-password
Re-enter Golden Gate admin password: admin-password
Setting up Golden Gate
Updating the registry
Successfully setup GG
```
Where:
- admin-username is the database user name for Oracle GoldenGate Cloud Service access to the database:
  - For Oracle Database 11g, specify ggadmin.
  - For Oracle Database 12c or later, specify c##ggadmin.
- admin-password is the password to use for the database user. You can use the administrator password provided when the database deployment was created, or you can use a different password that conforms to password requirements for Oracle Database users.
Close your connection to the compute node.