Using Oracle GoldenGate Cloud Service

Oracle Cloud
Using Oracle GoldenGate Cloud Service

E65310-10
January 2017
Documentation for system administrators and database
administrators that describes how to work with the
components of Oracle GoldenGate Cloud Service to manage,
troubleshoot and perform other administrative operations on
these services.
Oracle Cloud Using Oracle GoldenGate Cloud Service,

E65310-10
Copyright 2015, 2016, Oracle and/or its affiliates. All rights reserved.
Primary Author: Adriana Garcia Padilla
Contributing Authors: Laleh Haghshenass
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on
behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are
"commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agencyspecific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the
programs, including any operating system, integrated software, any programs installed on the hardware,
and/or documentation, shall be subject to license terms and license restrictions applicable to the programs.
No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications.
It is not developed or intended for use in any inherently dangerous applications, including applications that
may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you
shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its
safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this
software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are
used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron,
the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro
Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services unless
otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates
will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party
content, products, or services, except as set forth in an applicable agreement between you and Oracle.
Contents
Preface ................................................................................................................................................................. v
Audience ........................................................................................................................................................ v
Documentation Accessibility ...................................................................................................................... v
Related Resources ......................................................................................................................................... v
Conventions.................................................................................................................................................. vi
1 Getting Started with Oracle GoldenGate Cloud Service

About Oracle GoldenGate Cloud Service .............................................................................................
1-1
About the Components of Oracle GoldenGate Cloud Service...........................................................
1-3
About the Interfaces to Oracle GoldenGate Cloud Service ................................................................
1-6
Replication Configuration Templates....................................................................................................
1-7
Before You Begin with Oracle GoldenGate Cloud Service.................................................................
1-8
Create and Configure Your Account on Oracle Cloud...............................................................
1-9
Create an Oracle Database Cloud Service Instance................................................................... 1-10

Backup and Recovery Configuration .......................................................................................... 1-12
Accessing Oracle GoldenGate Cloud Service ..................................................................................... 1-13
Exploring the Oracle My Services Dashboard ........................................................................... 1-14
Oracle GoldenGate Cloud Service Console ........................................................................................ 1-15
Oracle GoldenGate Cloud Service Terminology................................................................................ 1-16
Typical Workflow for Using Oracle GoldenGate Cloud Service..................................................... 1-18
Steps to Configure gguser Alias and Credential Store ............................................................. 1-20
Setting up SOCKS5 Proxy ............................................................................................................. 1-22
Configuring Extracts and Data Pumps ....................................................................................... 1-24
Configuring Replication ................................................................................................................ 1-26
2 Administering Oracle GoldenGate Cloud Service

Accessing a Virtual Machine Through a Secure Shell .........................................................................
2-1
Understanding the Default Access Ports...............................................................................................
2-1
Scaling an Oracle GoldenGate Cloud Service Block Storage .............................................................
2-2
Keeping Your Oracle GoldenGate Cloud Service Instances Manageable ........................................
2-2
Software Components Installation Directory Structure......................................................................
2-3
iii
3 Managing the Life Cycle of Oracle GoldenGate Cloud Service Instances

Exploring the Oracle GoldenGate Cloud Service Instance Detail Page............................................
3-1
Provision an Oracle GoldenGate Cloud Service Instance ..........................................................
3-3
Backup and Restore........................................................................................................................ 3-10

Upgrade and Patch......................................................................................................................... 3-13
Start, Stop, and Restart a GoldenGate Cloud Service Instance................................................ 3-14
Configure Access Rules ................................................................................................................. 3-15
Update the SSH Access Key.......................................................................................................... 3-18
Search Activity Log ........................................................................................................................ 3-18
Get Information About All Oracle GoldenGate Cloud Service Instances.............................. 3-19
Get Detailed Information About an Oracle GoldenGate Cloud Service Instance ................ 3-19
Delete an Oracle GoldenGate Cloud Service Instance ...................................................................... 3-20
4 Getting Started with Oracle GoldenGate Cloud Control

About Oracle GoldenGate Cloud Control.............................................................................................
4-1
Oracle GoldenGate Cloud Control Agent.............................................................................................
4-3
Prerequisites for the GoldenGate Cloud Control Agent Set Up................................................
4-4
Installation of the GoldenGate Cloud Control Agent .................................................................
4-4
Oracle GoldenGate Cloud Control Agent Properties File..........................................................
4-6
Oracle GoldenGate Cloud Control Agent Commands ...............................................................
4-8
Setup An Oracle GoldenGate Cloud Control Agent ......................................................................... 4-10

WebLogic Server Administration Console ......................................................................................... 4-12
5 Frequently Asked Questions

What's the Data Replication Scope for Oracle GoldenGate Cloud Service? ....................................
5-1
What are the supported topologies for GGCS replication? ................................................................
5-2
Why Is Oracle GoldenGate Cloud Service set up with Oracle Database Cloud Service?..............
What are the benefits of using your current Oracle GoldenGate installation with Oracle
5-2
GoldenGate Cloud Service?...............................................................................................................
5-2
Can I use my existing GoldenGate deployments with GoldenGate Cloud Service?......................
5-2
Is there any additional charge for support?..........................................................................................
5-3
6 Troubleshooting Oracle GoldenGate Cloud Service
iv
I Cant Create Service Instances..............................................................................................................
6-1
Problems with Scaling..............................................................................................................................

Why I Can't Login To My Remote Server With My Private Key After Typing Correct
6-2
Passphrase? ..........................................................................................................................................
6-2
Preface
Topics:
Audience
Documentation Accessibility
Related Resources
Conventions
Using Oracle GoldenGate Cloud Service explains how to provision Oracle GoldenGate
Cloud Service instances, and ensure reliable functioning of provisioned service
instances. This document explains how to perform these tasks by using the Oracle
GoldenGate Cloud Service web interface.
Audience
This document is intended for database administrators, or application developers who
are setting up or using Oracle GoldenGate Cloud Service. This guide assumes you're
familiar with web technologies and have experience with Oracle GoldenGate
environments.
Documentation Accessibility
For information about our accessibility commitment, visit the Oracle Accessibility
Program website at http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=docacc.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For
information, visit http://www.oracle.com/pls/topic/lookup?
ctx=acc&id=info.
Related Resources
For more information, see these Oracle resources:
Oracle Public Cloud
Getting Started with Oracle Cloud
Oracle Database Cloud Service
Oracle Storage Cloud Service

Oracle GoldenGate for Windows and UNIX 12c (12.2.0.1)
Conventions
The following text conventions are used in this document:
vi
Convention
Meaning
Boldface
Indicates graphical user interface elements associated with an

action, or terms defined in text or the glossary.
Italic
Indicates book titles, emphasis, or placeholder variables for

which you supply particular values.
Monospace
Indicates commands within a paragraph, URLs, code in

examples, text that appears on the screen, or text that you enter.
1
Getting Started with Oracle GoldenGate
Cloud Service
This section describes how you can get started with Oracle GoldenGate Cloud Service.
Topics:
About Oracle GoldenGate Cloud Service
About the Components of Oracle GoldenGate Cloud Service
About the Interfaces to Oracle GoldenGate Cloud Service
Replication Configuration Templates
Before You Begin with Oracle GoldenGate Cloud Service
Oracle GoldenGate Cloud Service Console
Oracle GoldenGate Cloud Service Terminology
Accessing Oracle GoldenGate Cloud Service
Typical Workflow for Using Oracle GoldenGate Cloud Service

Oracle GoldenGate Cloud Service, is a real time, high performance, and secure public
cloud data integration and replication solution. A cloud-based service that provides
seamless and real-time data movement while maintaining data consistency and
offering fault tolerance and resiliency.
You create and configure an Oracle GoldenGate Cloud Service environment without
having to set up any infrastructure or platform details yourself. By using the Oracle
GoldenGate Cloud Service wizard, you create a GoldenGate environment in the cloud.
When you complete the wizard, your environment is provisioned and fully integrated
with the target database. The GoldenGate Cloud Service is started automatically, and
you can begin to prepare your data for replication. All Oracle GoldenGate Cloud
Service instances that you create are immediately used with Oracle Database Cloud
Service.
Getting Started with Oracle GoldenGate Cloud Service 1-1
Note:
The source databases include Oracle Databases 11g and 12c, MySQL 5.6,
DB2 z/OS On-Premise, and Oracle Database Cloud Service instances.
The target replication database is an Oracle Database Cloud Service
instance.
DB 12.2 delivery with no features is certified.
With GoldenGate Cloud Service metered pricing, MySQL Database Cloud
Service is supported.
Oracle GoldenGate supported databases use VPN connection.
Oracle GoldenGate for Oracle, MySQL, and SQL Server uses SOCK5 Proxy
connection.
Certified on Oracle Fast Connect and Corente VPN, allowing to secure
your data delivery over the network with VPN connections to on-premises
GoldenGate servers.
Using Oracle GoldenGate Cloud Service, you can do the following:

Perform real time data replication with low impact, low latency, and high
throughput in data replication.
Capture and store each piece of data in an Oracle GoldenGate Cloud Service trail
file to be delivered to GoldenGate service instances in the target.
Deliver the information to the target database by reading the trail files through
Replicat processes.
Have data delivery process with optimum performance because of the setup of
Oracle GoldenGate Cloud Service with Oracle Database Cloud Service.
Enable the data encryption in trail files by delivering compressed data through
secure TCP/IP transport.
Administer Oracle GoldenGate Cloud Service through the central Oracle Cloud
Customer Portal.
It delivers data in real time with the following topologies:
One-to-one replication of on-premises to cloud where local data is replicated in the
cloud.
One-to-one, one-to-many (broadcast) and bi-directional replication of cloud data in
the cloud.
One-to-one replication from cloud to on-premises.
Note:
Bi-directional replication of cloud data in the cloud now includes the Conflict
Detection and Recovery (CDR) feature of GoldenGate.
1-2 Using Oracle GoldenGate Cloud Service

Oracle GoldenGate Cloud Service is a part of the platform service offerings in Oracle
Public Cloud Services. It provides a platform on top of enterprise-grade cloud
infrastructure for developing and deploying new or existing GoldenGate
environments in different replication scopes.
The following image illustrates the replication from on-premises to cloud where local
data is replicated in the cloud.
The following image illustrates the bi-directional replication from cloud to cloud.
The following image illustrates the replication from cloud to on-premises.
Corente allows you to provision and manage global private networks connecting to
any site, over any IP network, in a secure, centralized, and simple manner.
The components of Oracle GoldenGate Cloud Service are described in the following
sections.
My Account and My Services
Oracle Database Cloud Service and Console
Oracle Compute Cloud Service and Console
Oracle GoldenGate Cloud Control Console
WebLogic Server Administration Console
My Account and My Services
My Account is for order management. It allows you to complete orders, initiate cloud
service provisioning, activate paid services and trial requests. You use My Account to
request for GoldenGate Cloud Service.
My Services Dashboard lets administrators operate all active services within a single
identity domain. It gives you dashboards and administrative tools for your services.
You can manage and access all your Oracle Cloud Services from this link.
For more information see, Accessing Oracle GoldenGate Cloud Service

You use the Oracle GoldenGate Cloud Service Console to create service instances, and
to access and manage the life cycle of this service instances. For more information, see
Oracle GoldenGate Cloud Service Console.
Oracle Database Cloud Service and Console
Each Oracle GoldenGate Cloud Service instance must be associated with a service
instance in Oracle Database Cloud Service. This association is to determine the
database to be used for the target replication. Oracle GoldenGate Cloud Service can
detect and use Oracle Database Cloud Service instances that are up and running. See
Before You Begin with Oracle GoldenGate Cloud Service for more information about
what you need to create before provision Oracle GoldenGate Cloud Service instances.
For information about Oracle Database Cloud Service, see Create an Oracle Database
Cloud Service Instance.
If needed, then you optionally use Oracle storage Cloud Service for backup and
recovery. For information about object storage and Oracle Storage Cloud Service, see
Backup and Recovery Configuration and Managing Objects in Oracle Storage Cloud
Service.
Oracle Compute Cloud Service and Console
Oracle GoldenGate Cloud Service is built on top of infrastructure provided by Oracle
Compute Cloud Service. Oracle GoldenGate Cloud Service instances are hosted on
Oracle Compute virtual machines (VMs) that are based on the Oracle Linux 6.6. For
more information, see About Oracle Compute Cloud Service.
Oracle GoldenGate Cloud Control Console
Oracle GoldenGate Cloud Control, is a real time, high performance, monitoring
solution. A supporting tool for GoldenGate Cloud Service that provides statistics,
policies, and monitoring tools to control the functionality of GoldenGate Cloud
Service.
You can have statistics of your connections, tasks and notifications. The tasks you
create can be organized according to its priority and you can monitor them by its data
volume. For more information, review Getting Started with Oracle GoldenGate Cloud
Control
WebLogic Server Administration console with a user interface makes management
tasks more efficient. You can also use the WebLogic Server Administration Console to
manage your users. This procedures are described in Managing Users from the
WebLogic Administration Console.

An interface to Oracle GoldenGate Cloud Service is any software that has any kind of
interaction with the service.
The following table summarizes the key interfaces to Oracle GoldenGate Cloud
Service:
Interface
Description
More Information
Oracle
Enterprise
Manager
(OEM)
GoldenGa
te
Monitor
plug-in
The Enterprise Manager Plug-in for Oracle

GoldenGate extends the Oracle Enterprise
Manager cloud control for monitoring and
managing Oracle GoldenGate processes.
Oracle GoldenGate Plug-in

for Oracle Enterprise
Manager
Oracle
GoldenGa
te Cloud
Control
Console
The GoldenGate Cloud Control Console for

Oracle GoldenGate extends the Oracle
GoldenGate Cloud Service performance. You can
easily monitor and manage Oracle GoldenGate
processes through the administration of policies
and tasks, and the constant review of tasks and
notifications.
Getting Started with Oracle

GoldenGate Cloud Control
WebLogic
Server
Administr
ation
Console
WebLogic Server Administration Console with a

user interface makes management tasks more
efficient.
Provision an Oracle
GoldenGate Cloud Service
Instance
In the WebLogic Server Administration Console

you can administer the users of your services.
WebLogic Server
Administration Console
Web
browser
Supported browsers include:

Microsoft Internet Explorer 11.x
Mozilla Firefox ESR 38+
Google Chrome 42+
Apple Safari 8.x and 7.x
Accessing Oracle GoldenGate

Cloud Service
Service
Console
To create service instances and perform lifecycle

operations, like remove, search and view details
of service instances, use the Oracle GoldenGate
Cloud Service Console.
Oracle GoldenGate Cloud

Service Console
Secure
Shell
(SSH)
Access the Oracle GoldenGate Cloud Service

virtual machine (VM) locally or remotely
through SSH to create and manage the
replication process.
Create a New, or Use an

Existent SSH Key Pair
Enterprise Manager Oracle

GoldenGate System
Monitoring Plug-in
Installation Guide

Having replication configuration templates, helps you to save time when creating
Oracle GoldenGate replication in GoldenGate Cloud Service. The templates include
extract, pump and Replicat parameter files, and shell script to create credential stores
and SOCKS5 Proxy.
The following files are located under the dirprm directory:
File
Description
MGR.prm
Manager parameter file.
EXTIN.prm
For integrated Extract.
File
Description
PUMP.prm
Parameter file that can be used in case of bi-directional replication.
ADD_EXTRAC
T.oby
Obey file for create Extract and pump.
REPCO.prm
For coordinated Replicat.
REPIN.prm
For integrated Replicat.
ADD_REPLICA
T.oby
Obey file for create Replicat.
The following table describes other files that are included in the GoldenGate Cloud
Service structure:
File
Description
README
Contains general information.
CREDENTIAL_
STORE_SETUP.
sh
Shell script for creating credential store.
SSH_SOCK5_SE
TUP.sh
Shell script for creating SOCK5 Proxy.
GLOBALS
Oracle GoldenGate global configuration. (located in $GGHOME)

Meet all the prerequisites to start using Oracle GoldenGate Cloud Service.
You Should Have:
Description
An Oracle Cloud account.

Subscriptions to:
Refer to these sections for a specific

description of required services:
Create and Configure Your Account on
Oracle Cloud
Create an Oracle Database Cloud Service
Instance
Optional Backup and Recovery
Configuration
Oracle GoldenGate Cloud Service
subscription.
Oracle GoldenGate Cloud Service.

Oracle Database Cloud Service (DBCS)
to host the replicated data
Oracle GoldenGate Cloud Service to
perform the replication
Purchase a subscription. See Requesting a

Subscription to an Oracle Cloud Service
Get into the service. See Accessing Oracle
GoldenGate Cloud Service
You Should Have:
Description
Your Oracle Cloud user name, password, and

identity domain
Locate your account details in the postactivation e-mail that you received from
Oracle Cloud when your user account was set
up. If you don't have your New Account
Information e-mail, contact your account
administrator.
Service Administrator role for your Oracle

Cloud services
If you aren't sure whether your Oracle Cloud

user account has the Service Administrator
role, contact your account administrator.
A Supported Browser
Supported browsers include:
Microsoft Internet Explorer 11.x

Mozilla Firefox ESR 38+
Google Chrome 42+
Apple Safari 8.x and 7.x
Create and Configure Your Account on Oracle Cloud

Before you can request a trial subscription or purchase a subscription to Oracle
GoldenGate Cloud Service, you must have an Oracle.com account.
To sign up for a free Oracle.com account:
1.
Open your web browser and go to the Oracle.com website: http://

www.oracle.com
2.
Click Sign In/Register. The Sign In page opens.
3.
Click the Sign Up link. The Create Your Oracle Account page opens.
4.
Enter your account and personal information into the appropriate fields. Be sure
to complete all required fields.
Note:
We prefer that you use a valid business email address as the user name for
your Oracle account. Valid email addresses use the following standard
format:
user-name@company-name.com
Only one account can be created for each business email address.
Your password must have at least eight characters, must contain both
uppercase and lowercase letters, and must contain at least one number.
5.
Click Create. We create your account and send you a confirmation email to the
address you used to create the account.
6.
To verify the status of your email address, follow the instructions in the email.
After your email address is verified, you can use your Oracle.com account to register
for Oracle Cloud services. See Accessing Oracle GoldenGate Cloud Service
Follow this steps through the tutorial Get Started with Oracle GoldenGate Cloud
Service
Create an Oracle Database Cloud Service Instance

Before you create an Oracle GoldenGate Cloud Service instance, you must create
a Database Cloud Service instance. For example, if you have a cloud database for
source and one cloud database for target, create two service instances. Later, when you
create a GoldenGate Cloud Service instance, you select one database for the
GoldenGate Cloud Service. Most likely its your target replication database. Then,
similar to other GoldenGate cases, you perform some additional steps to set up the
target to communicate with the source database.
You have to be sure that your Database Cloud Service entitlement of your GoldenGate
Cloud Service account is active. If your Database Cloud Service entitlement is
terminated, then you can't provision GoldenGate Cloud Service instances. The reason
is because they point to a valid running Database Cloud Service instance.
Oracle GoldenGate Cloud Service uses Oracle Database Cloud Service instances to
replicate your transactions to and from the cloud.
For information about subscribing to Oracle Database Cloud Service, see How to
Begin with Database Cloud Service Subscriptions.
Invoke the wizard.
1.
In My Services Dashboard, click the Database menu and then click Open Service
Console
a.
If you are creating your first instance, you get a Welcome page, there click
either the Services button or the Go to console link.
b.
If you have instances created, then you go direct to the Services page, there
click the Create Service button.
Create and provision your instances.

Provision your Database Cloud Service instance to be used with GoldenGate.
Steps
Valid selections
Service
Specify the value of the SSH public key, or the name of the file that contains the
public key value.
This key is used for authentication when connecting to the Oracle GoldenGate
Cloud Service instance using an SSH client.
To display the public key input for VM access, click Edit and specify the public key
using one of the following methods:
To select a file that contains a Secure Shell (SSH) public key to assign to this
service instance, select Key File Name.
To associate the value of an existing SSH public key with this service instance:
Select Key Value and then copy and paste the value.
Click Create a New Key to create a public and private key file, zipped, and
ready for you to save both files on your computer. This option saves the public
key information for the service instance.
Click Enter.
Get more information on: Create a New, or Use an Existent SSH Key Pair
Details
Compute Shape: The compute shape specifies the number of Oracle Compute
Units (OCPUs) and amount of memory (RAM) for the virtual machine (VM)
hosting the new service instance.
General compute shapes: OC3, OC4, OC5, OC6, and high memory compute
shapes: OC1M, OC2M, OC3M, OC4M are allowed.
Usable Database Storage (GB): The amount of storage you want for your
database. The minimum value you can enter is 15GB.
Total Data File Storage (GB): This field is updated reflecting the amount of
storage allocated to your instance. You can add more data storage as needed,
any time.
Administration Password: Enter your choice of password following the tooltips
about allowed passwords, then Confirm Password.
DB Name (SID): The unique database name that identifies it on the server, is
known as the service name or System ID (SID).
PDB Name: Only when using Oracle Database 12c, you provide a Pluggable
Database (PDB) name. A PDB is a portable collection of schemas, schema
objects, and non-schema objects that can be used with the multitenant
architecture of Oracle Database 12c.
Depending on your needs, you can opt for Backup and Recovery. To learn how to
configure this section, review Backup and Recovery Configuration.
You can create a storage container, in case you dont have one, by clicking in the
Create Cloud Storage Container checkbox.
Select the Enable Oracle GoldenGate option, then, when you create the Oracle
GoldenGate Cloud Service instance, choose this Database Cloud Service instance
for the associated database.
You can deselect Include "Demos" PDB to save some database space. Selecting this
option configures several PDB demos in the database with the service instance
creation. These demos are for 12c new features.
Confir
mation
Summary of your selections to be confirmed.
The following table lists database options to use as source and target.
Replication Options
Supported Database Options to Use With Oracle GoldenGate

Cloud Service
For non-cloud to cloud

replication:
Non-cloud source: Oracle Databases 11g and 12c, DB2 z/OS

On-Premises, and MySQL 5.6.
Cloud target: Oracle 12c version 12.1.0.2 and Oracle Database
11g version 11.2.0.4.0, available through Oracle Database
Cloud Service.
For cloud to cloud

replication:
Cloud source: Oracle 12c version 12.1.0.2, available through

Oracle Database Cloud Service.
Cloud target: Oracle 12c version 12.1.0.2, available through
For cloud to non-cloud

replication:
Cloud source: Oracle 12c version 12.1.0.2, available through

Non-cloud target: Oracle Databases 11g and 12c, and MySQL
5.6.
Note:
DB 12.2 delivery is certified, but with no feature.
Final considerations
When you create an Oracle GoldenGate Cloud Service instance, you choose
an Oracle Database Cloud Service instance that youve already created. This
instance corresponds to what you want your GoldenGate Cloud Service VM to see
and connect to seamlessly. This instance has to be in the same identity domain as
the Oracle GoldenGate Cloud Service instance, and it has to be up and running.
Avoid using the same Oracle Database Cloud ServiceOracle Database Cloud
Service instance for multiple Oracle GoldenGate Cloud Service instances. Instead,
create one Database Cloud Service instance for each cloud database in your
replication topology.
Theres a way to ensure that you can restore the database for an Oracle GoldenGate
Cloud Service instance without risking data loss. You're responsible for ensuring
that the service instance is in a consistent state after the service instance is restored.
Is highly recommended to use a separate Database instance for GoldenGate Cloud
Control repository, which is not same as replication source and target.
Follow these steps through the tutorial Get Started with Oracle GoldenGate Cloud
Service
Backup and Recovery Configuration

If you decide to use backup and recovery of the replicated data and transactions
residing in the target database, then you create a Storage Container.
As GoldenGate Cloud Service is set up with Database Cloud Service, when
provisioning the Database, you can decide to use backup and recovery. In this case,
you can select an Oracle Storage Cloud Service you already have or you can create a
new one.
If you want to create a container before provisioning your GoldenGate Cloud Service,
you must have an active subscription to Oracle Storage Cloud Service.
To get your subscriptions, follow the next steps:
1.
Purchase a subscription. See Requesting a Subscription to an Oracle Cloud Service

in Getting Started with Oracle Cloud.
2.
Activate and verify the service. See Activating Your Subscription For an Oracle
Cloud Service in Getting Started with Oracle Cloud.
3.
Verify activation. See Verifying That Your Subscription is Up And Running in

Getting Started with Oracle Cloud.
Select the Both Cloud Storage and Local Storage option from the Backup
Destination list, this option is actually Cloud Storage Only and youll get a backup
on Oracle Storage Cloud Service. This option provides no backup on Disk Storage.
Name of an Oracle Storage Cloud Service container in the format: Storage<identity domain name>/<container name> where <container name>
is the name of the container you want to create or the one you already have.
User name and password for the Oracle Storage Cloud Service user who has read/
write access to the container. The user has the format: Storage<identityDomainID>:<account-emailId>
If you dont have any Cloud Storage Container Created, then select the Create Cloud
Storage Container check box, to have the wizard create the container for you.
The Total Estimated Monthly Storage (GB) field is updated to reflect the amount of
storage in GBs that is estimated for your instance as configured, including data files
and backup storage.
For more information about creating a container in Oracle Storage Cloud Service, see:
Creating Containers in Using Oracle Storage Cloud Service
Follow this steps through the tutorial Get Started with Oracle GoldenGate Cloud
Service

You can access Oracle GoldenGate Cloud Service through the mails you received after
signing, or through a service web console
Sign Into The My Services
Do one of the following:
1.
Sign in to the Oracle Cloud Services through the URL on your signing-mails
a.
After signing up for a service on http://cloud.oracle.com, then, you

receive your first e-mail that asks you to activate your service.
b.
You activate the service by clicking a button from within the e-mail or by
signing into your Cloud Account. This action requires you to enter your
Oracle.com account/password.
c.
When the service is activated, you get a second e-mail with your user name,
temporary password, and link to My Services.
Note:
The My Services URL includes the data center. If you access My Services by
clicking this URL from within the e-mail, then you are taken directly to your
My Services URL.
Heres an example: (https://myservices.us2.oraclecloud.com/
mycloud/faces/dashboard.jspx).
d.
2.
To sign in to the My Services, youre required to enter your identity domain,

user name, and temporary password. Because youre signing in to My
Services for the first time, youre presented with a password reset screen. You
change your password and set your challenge questions.
Or, go to the My Services application:

a.
Open your web browser and go to http://cloud.oracle.com.
b.
Click Sign In.
c.
In the Cloud Account box, from the Select Data Center drop-down list, select
your location.
d.
Click My Services.
e.
On the Sign In to Oracle Cloud page, enter your sign-in credentials (Identity
Domain, user name and password).
Sign Into Oracle GoldenGate Cloud Service

1. In My Services Dashboard, click the Open Service Console link for Oracle
GoldenGate Cloud Service. See Exploring the Oracle My Services Dashboard
2. To open the Oracle GoldenGate Cloud Service Instance Detail page, you click the
service name you are interested in.
3. To manage a service instance, click the
for that selected service.
4. To view a help topic for a page, click the logged in user menu icon, select Help, and
then Help for This Page.
If you dont have access to the My Services application, then contact your
administrator for the service console URL.
For more information, see Get Started with Oracle GoldenGate Cloud Service.
Exploring the Oracle My Services Dashboard

The Oracle Cloud My Services Dashboard page has all the elements you have in your
identity domain, and allows you to administer them from a custom interface.
What You See on the Oracle My Services Dashboard Page
You can see the following sections on the Oracle My Services Dashboard.
Section
Description
Database
Oracle Database Cloud Service Details (Overview, Billing Metrics,

Resource Quotas, Monitoring Metrics, and Documents) and the Open
Service Console button.
Compute
Oracle Compute Cloud Service Details (Overview, Billing Metrics,

Resource Quotas, Monitoring Metrics, and Documents).
Database Backup
Oracle Database Backup Service Details (Overview, Billing Metrics,

Resource Quotas, and Documents).
Storage
Oracle Storage Cloud Service Details (Overview, Billing Metrics, Resource

Quotas, Business Metrics, and Documents).
GGCS
Oracle GoldenGate Cloud Service Details (Overview, Billing Metrics,

Resource Quotas, Documents, and Quota Branch Details) and the Open
Service Console button.
Clicking in the Create instance button you find the access to create a
Database or a GGCS Instance.
You can customize your Dashboard adding or hiding sections to make
your navigation easier.
Notifications
You can monitor your services through the warnings you may encounter in your
dashboard.
Element
Description
Ongoing quota breach
When finding this message you have one or more instances over the limit,
so the service will turn into quota breach/suspended state, then you are
not allowed to create more instances.
To solve this issue, you can arise the limit by purchasing amount or
defining a new limit amount.

From the Welcome page, open the Oracle GoldenGate Cloud Service Console.
What You Can Do From the Oracle GoldenGate Cloud Service Console
Use the Oracle GoldenGate Cloud Service Console to perform the tasks described in
the following topics:
Get Information About All Oracle GoldenGate Cloud Service Instances
You can have the overview list of all your services. You can review if some
instances are candidates for patching, or you can start, stop, or restart any of them.
Provision an Oracle GoldenGate Cloud Service Instance
Through the provision step, you configure your instance and you tune it to let it
ready for start using it. This step is the most important before start replicating.
Get Detailed Information About an Oracle GoldenGate Cloud Service Instance
Through the detail page, you can review all the services one by one. You can check
the configuration in which a service is working and make any needed changes.
Configure Access Rules
Your access rule are the key to control your network access. On this step, you
decide about how this access is being administered.
Update the SSH Access Key
For extra security, you have to know how to update your SSH Access Key.
Through this action, you can administer your ssh keys in an easy way.
Search Activity Log
By reviewing the activity log, you can see what had happened during the life cycle
of any of your instances. With this information, you can have enough information
for the administration of your services.
Delete an Oracle GoldenGate Cloud Service Instance
You can remove any unnecessary service to stop be billed for it. This action gets
you the control to administer your quota.
Get access to the GoldenGate Cloud Control Console and the WebLogic Server
Administration Console.

The following table lists and describes the key terms used in the context of Oracle
GoldenGate Cloud Service.
Term
Definition
Change Data
Capture (CDC)
A Change Data Capture captures changes in data over time. It is an

ongoing process and does not handle initial loads.
Collector
Collector is a process that runs in the background on the target system

with continuous, online change synchronization is active.
Data pumps
Data pumps are secondary Extract mechanisms that exist in the source
configuration. They are optional components. If a data pump isnt used,
then Extract sends data through TCP/IP to the remote trail on the target.
When a data pump is configured, the primary Extract process writes to the
local trail. The data pump reads the trail, and data is sent over the network
to remote trail on the target system.
Data source
A data source is the data you can obtain directly from the database
transaction logs.
Datastore
A Datastore is a set of integrated objects that are most commonly used as

the source and target of replication.
DDL
DDL is the Data Definition Language used to define objects and artifacts
within a database.
Term
Definition
Deployment
Profile
A Deployment Profile defines the way the Solution is packaged into an

Oracle GoldenGate Deployment Archive. It also defines to where the
archive should be deployed and what actions should be taken after
deployment.
ER
ER is the set of Extracts and Replicats.
Extract
The Oracle GoldenGate capture process is known as Extract. The Extract

process runs on the source and is configured for initial loading as well as
capturing any changes between the source and target. The data continuity
is maintained between source and target tables as consequence.
Extract runs continuously and maintains checkpoints in the data source
and trail. This process ensures data integrity and fault tolerance
throughout planned or unplanned process termination, system outages, or
network failure.
FCP
FCP is the Oracle Fusion Client Platform. Customizable and extendable

platform for building rich Java clients.
Identity Domain
An identity domain controls the authentication and authorization of the

users who can sign in to Oracle Public Cloud services. You log in to Oracle
GoldenGate Cloud Service by using your credentials and your identity
domain.
Manager
Manager is a process that must be running on both the source and target
systems before the Extract or Replicat process can be started. It also
performs various functions including starting other GoldenGate processes,
managing the trail files, and reporting.
Monitoring
Profile
The Monitoring Profile, contains settings used to monitor a solution

including which attributes to display (e.g. status and lag) and how often to
retrieve monitoring attributes.
Oracle
GoldenGate
Cloud Service
Oracle GoldenGate Cloud Service is a cloud service offered in Oracle

Cloud. This service provides GoldenGate replication services for a source
database to an Oracle Cloud target database on cloud.
Oracle
GoldenGate
Cloud Service
Instance
An Oracle GoldenGate Cloud Service instance is a virtual machine

providing GoldenGate replication services for the database that you
specify.
POC
The POC is the proof of concept typically for a new user.
Profile
Profiles are used for and will be specific to Deployments and Monitoring.
A single solution may have multiple profiles.
Provisioning
Provisioning is the process of creating new Oracle GoldenGate Cloud

Service instances.
Replicat
Replicat is a process that runs on the target system. It reads transactional

and DDL changes captured from the source and applies them to the target
database. It can also be configured to apply initial loads. Like the Extract
process, the Replicat process can be configured for both initial loading of
data and synchronization of changed data.
Term
Definition
Replication
Node
An Oracle Linux virtual machine that has a GoldenGate Cloud replication

service installed on it is called a replication node. Each Oracle GoldenGate
Cloud Service instance consists of one replication node. You can create
many service instances, each with one replication node.
Resource
Resources include:
Hosts
Datastores
OGG Instances
Credentials
Files
Scheduling
Profile
A Scheduling Profile, defines the coordination of components in a

solution, how they are added, altered and started. For example, an initial
load must be completed before real time changes are replicated. A
Schedule also applies to when a solution will be deployed.
Solution
A solution in OGG Studio is a collection of one or more OGG instances,

one or more deployment profiles, one or more monitoring profiles, one or
more schedules, and files associated both directly and indirectly to
instance artifacts.
Source
A source is anything that OGG 12c can extract from including: Database
(e.g. direct DB access for initial load), Transaction Log File, Local Trail File
(UDF), OGG Vendor Access Module (VAM), JMS Queue. Considering that
one source can have multiple targets.
Target
A target is the location for the replicated data. Targets will include:
Database, Local Trail File (UDF, ASCII, SQL, XML), Remote Trail File
(UDF, ASCII, SQL, XML), JMS Queue and, Custom User Exit. Considering
that one target can have multiple sources.
Trail
A trail is a series of files that GoldenGate temporarily stores on disks.

These files are written to and read from by the Extract and Replicat
processes. Depending on the configuration chosen, these trail files can
exist on the source as well as on the target systems. A trail file on the local
system is known as an extract trail. A trail file on the target system is
known as a remote trail.

To start using Oracle GoldenGate Cloud Service for replication, consider the typical
workflow described in the following table as a guide.
Task
Description
More Information
Create an oracle.com
account.
Go to oracle.com and follow the

instructions.
Signing In to My Services for Oracle Public

Cloud Services in Getting Started with Oracle
Cloud.
Task
Description
More Information
Purchase a subscription
to the following services:
Oracle Database
Cloud Service
Oracle Cloud Storage
Oracle GoldenGate
Cloud Service
Sign up for a subscription to Oracle

Buying a Non-metered Subscription to an

Oracle Cloud Service in Getting Started with
Oracle Cloud.
Other Oracle Cloud services are

also required. See Before You Begin
with Oracle GoldenGate Cloud
Service for the cloud services that
must be provisioned before you can
use Oracle GoldenGate Cloud
Service.
You can also request an Oracle Public Cloud

Trial account, GoldenGate Cloud Service is
included, along with other services. All the
Trial accounts are valid for 30 days, after that
you can convert this account to a Production
account, otherwise, the Trial account gets
expired after 30 days.
Set up the Oracle Public

Cloud Services account
or activate the order
After Oracle processes your

purchase order, sign in to My
Account and set up your account
details.
Activating Your Order in Getting Started with

Oracle Cloud
Verify that the service is

ready for use
After the account setup is complete,

sign in to My Services and confirm
that your service is available for
use.
Verifying That a Service is Running in Getting

Started with Oracle Cloud
Access the GoldenGate

Cloud Service console
Access the GoldenGate Cloud

Service console and other interfaces
to your service.
Configure SSH Keys
To connect remotely to Oracle

GoldenGate Cloud Service,
configure or create SSH keys.
Create a New, or Use an Existent SSH Key Pair
Configure your Backup

and Recovery
If you opt for backup and recovery

of your data, then you use Oracle
Storage Cloud Service,
Backup and Recovery Configuration
Create a Database Cloud

Service instance
You use Database Cloud Service, as

target when replicating from onpremises to cloud, or from cloud to
cloud.
Create an Oracle Database Cloud Service

Instance
To create a service
instance, use the Create
New Oracle GoldenGate
Cloud Service Instance
Wizard
See Before You Begin with Oracle

GoldenGate Cloud Service for the
Oracle Cloud services and servicespecific information that you must
have before you can create an
Oracle GoldenGate Cloud Service
instance.
Provision an Oracle GoldenGate Cloud Service

Instance
Configure Replicat
Use previously created SSH keys

and Oracle GoldenGate commandline tools to connect to a service
instance and configure a Replicat
process to interact with the
database.
Configuring Replication
Set up the gguser alias

and credential store
Configure your template files, to set

up the gguser alias and credential
store..
Steps to Configure gguser Alias and Credential

Store
Task
Description
More Information
Set up SOCKS5 proxy
After setting up the SOCKS5 proxy,

you can set up Oracle GoldenGate
on-premises Pump component to
deliver data to GoldenGate Cloud
Service through the proxy.
Setting up SOCKS5 Proxy
Configure an Extract
process and data pump
To configure an Extract process and

a data pump, use Oracle
GoldenGate command-line tools
and service instance information.
Configuring Extracts and Data Pumps
Back up your data
Use your storage container to

backup and keep your data safe.
Backup and Restore
Restore your data from a

backup
Use your backup to restore your

data keep it safe from system
failures
Backup and Restore
Patch your service

instances after an
upgrade
Apply patches to get all your

instance services working with the
latest features.
Upgrade and Patch
Delete a service instance
Remove a service instance.
Delete an Oracle GoldenGate Cloud Service

Instance
Steps to Configure gguser Alias and Credential Store

Oracle GoldenGate Cloud Service Replication VM comes with the template parameter
files to set up the Replicat process.
The template parameter (.prm) and obey (.oby) files are located on:
/u01/app/oracle/gghome/dirprm which are mapped to /u02/data/
ggdata/dirprm
Note:
Do not change the u01 directory. Instead, perform all your tasks in the u02
directory.
Before you start using these files, update a few entries in the .oby, and .prm files.
Replicat parameter file (.prm)
-################################################################
###
-- Runcmd: ADD REPLICAT <REPLICAT name>, INTEGRATED EXTTRAIL
<trail file path/two -- character trail id>
-- Name of the Replicat process. Limited to 8 characters.
--GGCS Added default REPLICAT name
REPLICAT REPIN
-- OGG database user login

--GGCS Added default useridalias name to ggcsuser_alias
useridalias ggcsuser_alias
--Integrated parameter
DBOPTIONS INTEGRATEDPARAMS (parallelism <n>)
--Discard file location.
--GGCS Added default Discard file location
DISCARDFILE ./dirrpt/REPIN.dsc, APPEND Megabytes 50
--DDL replication parameters
DDL INCLUDE ALL, EXCLUDE OBJNAME "<schema name>.<object name>"
DDLOPTIONS REPORT
-- The following parameter speeds up Replicat processing rate.
The
-- parameter alters the Replicat oracle session not to wait for
commits -- to be persisted to the redo.
-- Use the DISCARDROLLOVER parameter to set a schedule for aging
discard files.
DISCARDROLLOVER AT <hh:mi> on < day of the week>
-- Use the REPORTROLLOVER parameter to force report files to age
on a
-- regular schedule, instead of when a process starts
REPORTROLLOVER AT <hh:mi> on < day of the week>
-- Use the REPORTCOUNT parameter to report a count of
transaction
-- records that Extract or Replicat processed since start up
REPORTCOUNT EVERY <n> HOURS, RATE
ASSUMETARGETDEFS
-- List of tables (MAP statements)
MAP <source schema name>.<table name>, TARGET <target schema
name>.<tablename>;
1.
Open the file /u02/data/ggdata/dirprm/REPIN.prm
2.
You have to update the bold text with actual values, as indicated on the
comments.
Replicat obey file (.oby)

--DBLOGIN (IF integrated or coordinated Replicat).
--DBLOGIN userid <Database userid>, password <Database password>
- encrypted password
--GGCS Added default USERIDALIAS name to ggcsuser_alias
ALTER CREDENTIALSTORE ADD USER <USERNAME>@target PASSWORD

<password> ALIAS ggcsuser_alias
DBLOGIN USERIDALIAS ggcsuser_alias
--Add replicat (IF integrated)
--GGCS Added default <extract pump trail id> as p1
Add replicat REPIN, integrated,EXTTRAIL ./dirdat/p1
--Add checkpoint table (if Classic or coordinated)
-- IF coordinated, uncomment the below line. GGCS Added default
<checkpoint table name> as REPCO_CHKPT
--add replicat REPCO, exttrail ./dirdat/p1, COORDINATED,
MAXTHREADS <20>, checkpointtable REPCO_CHKPT
--add checkpointtable REPCO_CHKPT
-- If Classic, uncomment the below 2 lines. GGCS Added default
<checkpoint table name> as REPCL_CHKPT
--add replicat REPCL, exttrail ./dirdat/p1
--add checkpointtable REPCL_CHKPT
1. Open the file /u02/data/ggdata/dirprm/replicat_obey.oby
2. If you created your DBCS service with GoldenGate enable option, then there will
be a pre-created user. In the other case, you have to manually create the user you
want (for example, REPUSER) by connecting from GoldenGate VM and give the
required privileges as below.
SQL>exec
dbms_goldengate_auth.grant_admin_privilege('REPUSER',containe
r=>'PDB1');
3. Provide the target Database schema user name and password details by changing
this lines from the script replacing with your own information.
ALTER CREDENTIALSTORE ADD USER <USERNAME>@target PASSWORD
<password> ALIAS ggcsuser_alias
@target connect descriptor will be in /u01/app/oracle/oci/network/admin/

tnsnames.ora, this has SERVICE_NAME to which container it connects.
4. Run the obey file from the GGSCI console.
GGSCI > obey /u02/data/ggdata/dirprm/replicat_obey.oby

These steps create an alias username in the GoldenGate wallet, so then you can start
using this alias user name instead of providing the DB user name and password
details.
You can review this steps by following the tutorial Replicate On-Premises Data to
Cloud with Oracle GoldenGate Cloud Service
Setting up SOCKS5 Proxy

Oracle GoldenGate, introduces the SOCKS5 proxy support. This support,
makes Oracle GoldenGate SOCKS5 compliant or SOCK5 enabled. The feature allows
delivering data using GoldenGate Cloud Service without VPN connections.
What is SOCKS5?
SOCKS5 proxy is used for prevent others from identifying who you are and where
you are from. An SOCKS5 proxy server establishes a TCP connection to another server
on behalf of a client. Then the proxy routes all the traffic back and forth between the
client and server. When using SOCK5 proxy, it's like an agent representing you for
public communications. Therefore, no one really knows who you are. Instead, others
can only see this agent.
How to set up SOCKS5 Proxy?
On Linux, an SOCKS5 proxy with 1080 port can be set up using the following SSH
command:
ssh i <private_key file> -v N f D <listening IP
Address>:<listening IP port> <GGCS Oracle User>@<GGCS IP
Address> where:
Parameter
Description
-i
Private Key File
-v
Verbose Mode
-N
No execution command on remote system
-f
Run the proxy process in the background
-D
Dynamic Port Forwarding
The following is an example setup of an SOCKS5 proxy with the SSH tunnel
connecting to GoldenGate Cloud Service (with IP 111.111.1.11):
ssh -N -f -i opc_rsa.ppk -D 127.0.0.0:1080 opc@111.111.1.11
This setup the SOCKS5 proxy with the SSH tunneling. You provide the private key
(opc_rsa.ppk) and the user login (opc@111.111.1.11) to the remote host.
After the SOCKS5 proxy is set up, you can use the following command to check if it's
running OK:
curl -sSf --socks5 222.2.2.2:1080 www.google.com
If it returns the Web page content, then the connection is set up correctly.
Why do I get the Permission denied error when starting the SOCKS5 proxy with
SSH?
$ssh -N -i opc_rsa.ppk -D 0.0.0.0:1080 localhost
Permission denied (publickey,gssapi-keyex,gssapi-with-mic).
The reason is missing the user and host name to connect. In an EC2 environment, you
get this error.
How to Use SOCKS5 proxy with Oracle GoldenGate Cloud Service?
After setting up the SOCKS5 proxy, you can set up Oracle GoldenGate on-premises
Pump component to deliver data to GoldenGate Cloud Service through the proxy. For
this purpose, use the SOCKSPROXY parameter. The following is an example:
RMTHOST 111.111.1.11, COMPRESS, MGRPORT 1021, SOCKSPROXY

222.2.2.2:1080
Don't confuse SSH tunneling with SOCKS5. SSH tunneling is the additional encrypted
tunnel created through an SSH connection (through port 22). In other words, with
SOCKS5 proxy, one local port (any port) is configured to listen to internal requests.
Then the proxy routes all the traffic to the external servers. With SSH tunneling, all
traffic sending through encrypted an SSH tunnel is encrypted through a secure data
transfer.
Note:
You can follow detailed steps in the Set Up a SOCKS5 Proxy for Oracle Public
Cloud Services tutorial.
Configuring Extracts and Data Pumps

Oracle GoldenGate Cloud Service replication requires you to configure Extract and
data pump process on source.
1.
To connect to the replication node, use one of the following options:

Local trail (ExtTrail) on the local system
Remote trail (RmtTrail) on the remote system
Note:
Oracle GoldenGate Cloud Service trails support the continuous extraction and
replication of database changes storing these changes temporarily on cloud. A
trail can reside on any platform that Oracle GoldenGate Cloud Service
supports. (Oracle and MySQL databases are supported).
You can configure one Replication node to process a trail for target databases.
After all the data has been consumed, Replicat can then purge the data using
the MinKeepDays parameter. As long as Replicat remains current, your
temporary storage requirements for trails can be low.
2.
Format the Trail:

By default, trails are formatted in canonical format, allowing them to be
exchanged rapidly and accurately among databases.
Each trail file contains the following:
Record header area: Stored at the beginning of the file and contains
information about the trail file itself.
Trail File Information
Compatibility level
Character set (globalization function with version 11.2.1 and later)
Creation time
File sequence number
File size
First and Last Record Information
Timestamp
Commit Sequence Number (CSN)
Extract Information
Oracle GoldenGate Cloud Service version
Group name
Host name and Hardware type
Operating system type and version
DB type, version, and character set
Record data area: Contains a header area as well as a data area.
Checkpoints: Both Extract and Replicat maintain checkpoints into the trails.
Checkpoints provide persistent processing whenever a failure occurs. Each
process resumes where the last checkpoint was saved, guaranteeing that no
data is lost. One Extract can write to one or many trails. One or many Replicat
processes are involved in processing each trail.
Note:
Instead of the default canonical format, you can use alternative formats to
output data.
This feature is beneficial if database load utilities or other programs are used
that require different input format.
These alternative formats include:
Logical Change Records (LCRs)
FormatASCII
FormatSQL
FormatXML
3.
Set Up a View
Objective
Command
To view the trail file

header:
Logdump 1> fileheader on
To view the record

header with the data:
Logdump 2> ghdr on
To add column
information:
Logdump 3> detail on
4.
Objective
Command
To add hexadecimal
and ASCII data values to
the column list:
Logdump 4> detail data
To control how much

record data is displayed:
Logdump 5> reclen 280
Keep a log of your session

Objective
Command
To start and stop the logging of a

logdump session, use the Log option:
Logdump> Log to MySession.txt
When enabled, logging remains in effect

for all sessions of Logdump until its
disabled with the Log Stopcommand:
Logdump> Log Stop
Supported Scenarios
Oracle GoldenGate supports heterogeneous replication through the Classic Extract
mechanism.
This table describes different scenarios considering that integrated extract and
integrated delivery are not supported on any of the non-Oracle databases.
Source
Target
Extract
Replicat
Oracle 12c
Oracle Database
Cloud Service
Integrated Extract is
supported
Integrated and
Coordinated
Delivery supported
MySQL
Oracle Database
Cloud Service
Only Classic Extract

is supported
Integrated and
Coordinated
Delivery supported
Note:
With Oracle 12c when not using multi-tenancy, you can still use Classic
Extract, however it cant be used when container/pluggable databases are
used.
You can review this detailed steps, by following the tutorial Replicate On-Premises
Data to Cloud with Oracle GoldenGate Cloud Service.
Configuring Replication
Oracle GoldenGate Cloud replication requires connecting to and configuring database
support for the replication node.
Configure a General Replication Process

1.
Connect to the node defined in the Manager parameter file mgr.prm located
at /u01/app/oracle/gghome/dirprm
2.
Avoid using root user to run GoldenGate processes, otherwise some operations
can fail to read using 'oracle' user.
In the following table, you can review the parameters and descriptions necessary to
configure a replication process.
Parameter
Description
Port:
Establishes the TCP/IP Port Number on Which Manager Listens For Requests
DynamicPortList:
Specifies the ports that Manager can dynamically allocate
Autostart:
Specifies the processes to be restarted after abnormal termination
LagReportHours:
Sets the interval, in hours, at which Manager checks the lag for Extract and
Replicat processing. Alternatively, this interval can be set in minutes.
LagInfoMinutes:
Specifies the interval at which Extract and Replicat send an informational

message to the event log. Alternatively, this interval can be set in seconds or
hours.
LagCriticalMinutes:
Specifies the interval at which Extract and Replicat send a critical message to
the event log. Alternatively, this interval can be set in seconds or hours.
PurgeOldExtracts:
Purges the Oracle GoldenGate Cloud Service trails that are no longer needed,
based on option settings.
If you copy and paste text into parameter files, then beware of editors
that try to turn a double-minus into emdashes.
Note:
Managing Trail Files Use the PurgeOldExtracts parameter in the Manager

parameter file to purge trail files when Oracle GoldenGate Cloud Service has finished
processing them.
Note: Trail files, if not managed properly, can consume a significant amount
of disk space!
Configure Replication process, using the DMZ (Demilitarized Zone) Server

A DMZ server is a public-facing computer host placed on a separate or isolated
network segment. The intention of this server is to provide an addition layer of
network security between servers in the trusted network and servers in the public
network.
Follow the four high-level steps to configuring a replication from a non-cloud
database to cloud.
1.
Start the SSH Proxy Server on the DMZ Server.
2.
Configure and start the Online Change Capture Process (Extract) on the onpremise server.
3.
Configure and start the Data pump Extract on the on-premise Server (SOCKS
PROXY pointing to DMZ Server).
4.
Configure and start the Online Change Delivery Process (Replicat) on the GGCS
server.
1. Start the SSH Proxy Tunnel Setup on the DMZ Server

Start the SSH SOCKS Proxy Server on the DMZ Server
Command Syntax:
ssh i <private_key file> -v N f D <listening IP
Address>:<listening IP port><GGCS Oracle User>@<GGCS IP
Address>><socksproxy output file>2>&1
Parameter
Description
Private Key file.
-v
Verbose Mode.
Dont execute remote command (used for port forwarding).
Run SSH process in the background.
Specifies to run as local dynamic application level forwarding;

act as a SOCKS proxy server on a specified interface and port.
2>&1
Redirect Stdout and Stderr to the output filelistening.
IP Address
DMZ Server IP Address.
listening IP port
TCP/IP Port Number.
Verify that the SSH SOCKS Proxy server has started successfully.
Check the socks proxy output file using the cat Unix command.
Look for the:
Local connections to <dmz-server:port> and
Local forwarding listening on <ip_address> port <port #>.
This information helps you to make sure youre pointing to the right DMZ server
address and port.
2. Configure and Start the Online Change Capture Process (Extract) on the Onpremises Server
On the source server, create the online change capture (Extract) process, using the
following commands:
GGCSI>
GGSCI>
GGSCI>
GGSCI>
add extract etpcadb, tranlog, begin now

add exttrail ./dirdat/ea, extract etpcadb, megabytes 100
start extract etpcadb
info extract etpcadb detail
3. Configure and Start the Data pump Extract on the On-premise Server
On the source server, create the datapump (Extract) process, using the following
commands:
GGCSI>
GGSCI>
GGSCI>
GGSCI>
add extract ptpcadb, exttrailsource ./dirdat/ea

add rmttrail ./dirdat/pa, extract ptpcadb, megabytes 100
start extract ptpcadb
info extract ptpcadb detail
4. Configure and Start the Online Change Delivery Process (Replicat) on the
Cloud Server.
On the GoldenGate Cloud Service (GGCS) server, create the Change Delivery process
(Replicat) using the following commands:
GGCSI>
GGSCI>
GGSCI>
GGSCI>
dblogin useridaalias ggcsuser_alias

add replicat rtpcadb integrated, exttrail ./dirdat/pa
start replicat rtpcadb
info replicat rtpcadb detail
You can review this detailed steps by following the tutorial Replicate On-Premises
Data to Cloud with Oracle GoldenGate Cloud Service.
2
Administering Oracle GoldenGate Cloud
Service
This section provides the information you have to manage Oracle GoldenGate Cloud
Service instances.
Topics:
Accessing a Virtual Machine Through a Secure Shell
Understanding the Default Access Ports
Scaling an Oracle GoldenGate Cloud Service Block Storage
Keeping Your Oracle GoldenGate Cloud Service Instances Manageable
Software Components Installation Directory Structure
Accessing a Virtual Machine Through a Secure Shell

You access the services and resources provided by the virtual machine (VM) of a cloud
service instance through a Secure Shell (SSH) connection.
The SSH protocol uses two keys, a public key and a private key, to provide secure
communication between two computers. You can use any SSH utility to generate a
public/private key pair and later, to log in to your Oracle GoldenGate Cloud Service
instance. For example, you can use PuTTY or you can use OpenSSH.
For Windows you can follow the steps through the tutorial:
Connect to a Cloud VM on Windows with PuTTY
Understanding the Default Access Ports

You can access resources through Oracle GoldenGate Cloud Service by using the
default ports.
Available Ports
In the following table, you find the default ports used by Oracle GoldenGate Cloud
Service.
Source
Use
Default Port
GoldenGate in the Cloud Manager Process
Default Manager port
7744
GoldenGate Cloud Service VM
Secure Shell (SSH)

Connection
22
Administering Oracle GoldenGate Cloud Service 2-1

You can scale up your virtual machine block storage up to 1TB. This feature helps
increase the capacity of replication data storage.
Storage Scale Up Details
Once you create an instance, you can scale up the data volume from existing 100G
to 1TB or to any size within this range. Consider that your first attempt has to be
200G minimum. This scaling is to make sure that old instances can be brought to
LVM (Logical Volume Management) in single scale up request.
Scale up can be done multiple times but total consumption is up to 1TB.
There is no storage scale down supported.
Scale Up Workflow
1.
Click on the right center menu. It gives Add Storage option.
2.
A pop-up menu (with existing /u02/data partition size) shows, for selecting
your data volume size to scale up to (displaying the current size).
3.
Selecting the new size and click on Yes, Add Storage button results in accepting
request. At this point, the service status show Maintenance that means the
instance is on service maintenance mode.
4.
The Maintenance status reviews all GoldenGate Cloud Service processes are shut
down. Also, it reviews if any older instance (before 16.3.3) is upgraded with patch
available in 16.4.1. This review is to make sure no loose of root partition since
these instances use root partition for installation. If any of these checks fail, then
the scale up attempt fails.
5.
After the first scale up, next scale up will be allowed from existing size.
For additional information, see: Problems with Scaling
Keeping Your Oracle GoldenGate Cloud Service Instances Manageable

The following best practices ensure that your Oracle GoldenGate Cloud Service
instances stay manageable.
Reliable management of Oracle GoldenGate Cloud Service instances requires a specific
software environment. This environment includes service instances of Oracle Database
Cloud Service and Oracle Storage Cloud Service, and a Secure Shell (SSH) public key.
For more information about these features, see Before You Begin with Oracle
To keep your Oracle GoldenGate Cloud Service instances manageable, follow these
guidelines:
Dont use the same Oracle Database Cloud Service instance with multiple Oracle
GoldenGate Cloud Service instances. This action ensures that you can restore the
database for an Oracle GoldenGate Cloud Service instance without risking data
loss for other service instances.
Don't change the ingress and egress network and security settings of any
infrastructure resources that the cloud service instance uses.
Dont close any ports or protocols that Oracle GoldenGate Cloud Service opened
during creation of a cloud service instance.
You can open new ports and protocols, but closing existing ports and protocols
impair the functioning of a service instance.
For more information about the ports that Oracle GoldenGate Cloud Service opens
during creation of a cloud service instance, see Understanding the Default Access
Ports.
Dont change OS users and SSH key settings that Oracle GoldenGate Cloud Service
configured during the creation of a cloud service instance. If necessary, you can
update your SSH key at any time, see: Update the SSH Access Key.

You have access to all Oracle Compute Cloud Service virtual machine service
instances created for Oracle GoldenGate Cloud Service.
The following table lists the details of directory structure individual components:
Software
Installation | Runtime directory
Comments
GoldenGate
Replication
/u02/app/oracle/gghome
GoldenGate home directory
GG parameter files
/u02/data/ggdata/dirprm
Highly available block storage

volume
Oracle OCI (Oracle

Call Interface)
/u01/app/oracle/oci
OCI libraries
Note:
/u01 have to be treated as a read-only volume. This directory includes

gghome also. Any entries in gghome that can be modified are symbolically
linked to /u02.
You can modify entries in /u02/data/ggdata.
Administering Oracle GoldenGate Cloud Service 2-3
3
Managing the Life Cycle of Oracle
GoldenGate Cloud Service Instances
Oracle GoldenGate Cloud Service, sets up and manages the compute and storage
resources required for replication. By using Oracle GoldenGate Cloud Service you can
create and configure a cloud Oracle GoldenGate environment, because all Oracle
GoldenGate Cloud Service instances that you create are preconfigured to use Oracle
Database Cloud Service.
Topics:
Exploring the Oracle GoldenGate Cloud Service Instance Detail Page

The Oracle Cloud Service Instance Detail page has all the details of each service
instance you have in your identity domain.
You can access the GoldenGate Cloud Service Instance Detail page by clicking into a
service name.
The GoldenGate Cloud Service Instance Detail page helps you to perform the tasks of:
Backup and Restore
Upgrade and Patch
Start, Stop, and Restart a GoldenGate Cloud Service Instance
Search Activity Log
What You See on the Oracle GoldenGate Cloud Service Detail Page
You can review the following information on the Oracle GoldenGate Cloud Service
Instance Detail page when clicking on a service instance name. You have to have one
or more service instances created.
Managing the Life Cycle of Oracle GoldenGate Cloud Service Instances 3-1
Element
Description
Administration section
Displays if there are patches available for the service instance and the
status of the last successful backup, if exists.
Shows the following options:
GoldenGate Cloud Control Console Opens the console, unless the
service is stopped.
WebLogic Server Administration Console Opens the console,
unless the service is stopped.
Start Starts the service.
Stop
Stops the service.
Restart
Restarts the service.
SSH Access To upload a new SSH Key for your service, unless the
service is stopped. For more information, review Update the SSH
Access Key
Access Rules To define where traffic is allowed, configure sources,
destinations, and ports for your service. For more information, review
View Activity Goes to the Activity tab in which you can search and
review the operation log of your services in your identity domain.
Note:
This menu is disabled while the instance service selected is being created,
terminated or in maintenance.
Starts the service.

Stops the service.
Re-starts the service.
Opens the Healthcheck section.
Healthcheck results (retrieving

date)
Displays monitoring information:
Nodes
Number of Oracle GoldenGate Cloud Service instances in the identity

domain
OCPUs
Total number of Oracle Compute Units (OCPUs) allocated across all Oracle
GoldenGate Cloud Service instances
Memory
Total amount of memory in GBs allocated across all Oracle GoldenGate

Cloud Service instances
Memory utilization percent

File system usage percent
CPU utilization percent
Element
Description
Storage
Total amount of storage in GBs allocated across all Oracle GoldenGate

Cloud Service instances
Virtual Machines Details
The summary of the following details

Status of the instance.
Location: ID of where the service is placed.
Version: Version of the used service, for example 12.1.2.1.10-1.
Backup destination: Configuration of the backup.
Replication Component when
The summary of the following details of a ready service.

State
Database Service: The Oracle Database Cloud Service associated to this
service.
PDB Name: The Pluggable DataBase Name related to this service.
Username
Compute Shape: The compute shape youre using. General compute
shapes: OC3 and OC5 are allowed.
Node Description: The description you entered for your service.
Schema Prefix: The prefix you selected for your service. Remember that
this prefix should be unique.
clicking the
it shows:
Resources when clicking the

shows:
it
Associated Services when clicking

the
it shows:
The summary of the following details

Host Name
Public IP
Instance
OCPUs
Memory
Storage
Service Name The name you provided to the associated service.
Service Type Oracle Database Cloud Service
Status The activity indicator for the service.
Note:
If theres an in-progress operation, a message section appears at the bottom

with:
Service Name
Operation
Status
Start and End times

You create a service instance of the Oracle GoldenGate Cloud Service by running the
Create New Oracle GoldenGate Cloud Service Instance Wizard.
A GoldenGate service instance is a virtual machine that provides GoldenGate

replication services for a database that you specify. Before creating an Oracle
GoldenGate Cloud Service instance, review the prerequisites described in Before You
Begin with Oracle GoldenGate Cloud Service.
Log in to Oracle GoldenGate Cloud Service (Accessing Oracle GoldenGate Cloud
Service), and then click the Create Service button to start the wizard.
Note:
Any time during provisioning you can cancel the process by clicking Cancel.
To keep following the provisioning steps, click Next button or go back to
previous step by clicking the Previous button (when available).
Service Configuration Step

Enter the details for the service configuration on at least each required field.
Element
Description
Service Name
To compose your service instance name, use the following pattern for the
naming convention:
[a-zA-Z][a-zA-Z0-9-]{1,49} which means:
The name must start with a letter.
The name can't contain more than 50 characters.
The name can't contain special characters other than the hyphen.
Service Description
To provide a business reason for creating this service instance, use the
Description field, so future administrators can easily identify its functionality.
For example, Replication service instance for transferring the System X output data
from our on-premises data center to our database service in the cloud.
SSH Public Key
Specify the value of the SSH public key, or the name of the file that contains
the public key value.
This key is used for authentication when connecting to the Oracle GoldenGate
Cloud Service instance using an SSH client.
To display the public key input for VM access, click Edit and specify the
public key using one of the following methods:
To select a file that contains a Secure Shell (SSH) public key to assign to
this service instance, select Key File Name.
To associate the value of an existing SSH public key with this service
instance: Select Key Value and then copy and paste the value.
Click Create a New Key to create a public and private key file, zipped, and
ready for you to save both files on your computer. This option saves the
public key information for the service instance.
Click Enter.
Get more information on: Create a New, or Use an Existent SSH Key Pair
Metering Frequency
The Metering Frequency is your billing frequency, that can be either Monthly
or Hourly.
For additional information, see: More subscription types
Details Configuration Step

Fill the Backup and Recovery Configuration section, if you opt for backup and
recovery.
Element
Description
Backup Destination
If you need Backup and Restore you can use the Both Remote and Disk
Storage option. By now, this option means Cloud Only for Oracle Database
Cloud Service.
Cloud Storage Container
If you choose backup and recovery on cloud storage when creating your
Oracle Database Cloud Service Instance, then you provide the following
information:
Name of an existing Oracle Storage Cloud Service container of the form
<storage service name>-<identity domain name>/<container name>. For
example: storagesvc999-usoracleaccoutrial00999 /backupContainer.
If not already created, you must create the container following the Oracle
Cloud Storage documentation. See Backup and Recovery Configuration.
Cloud Storage User Name
User name for the Oracle Storage Cloud Service user who has read/write
access to the container.
Cloud Storage Password
Password for the Oracle Storage Cloud Service user who has read/write
access to the container.
Note:
You can select the Create Cloud Storage Container option by clicking the
checkbox in case you didnt when provisioning your Oracle Database Cloud
Service Instance.
The following table describes the Database Service Details fields and their description
for the database service.
Element
Description
Database Service
Select one of the Oracle Database Cloud Service Instance names that are listed
and can be associated for the Cloud Replication Service.
PDB Name
When selecting a 12c Database Service, you are required to enter the Pluggable
Data Base Name. If you dont know the PDB name, you can enter <use
default> to use the PDB. This information was associated with the Database
Cloud Service instance when it was provisioned.
Username
Use the same user name you used when create your Oracle Database Cloud
Service Instance. You or your administrator provided this user name to create
the Database Cloud Service instance.
Password
Refer to your Oracle Database Cloud Service instance information for the
password your user. You or your administrator provided this password to
create the Database Cloud Service instance.
In the Replication Node Configuration section, configure the description and shape
of the Replication node.
Element
Description
Node Description
Provide the node information that you want to see in the GoldenGate Cloud
Service Instance Detail page.
Compute Shape
A shape is a resource profile that specifies the number of CPUs and the
amount of memory to be allocated to a service instance. General compute
shapes: OC3 and OC5 are available.
In the Database Service Details for Cloud Control Schemas section, configure the
description and schema you use for the replication.
Element
Description
Database Service
Select one of the Oracle Database Cloud Service Instance names that are listed
and can be associated for the Cloud Replication Service.
PDB Name
When selecting a 12c Database Service, you are required to enter the Pluggable
Data Base Name. If you dont know the PDB name, you can enter <use
default> to use the PDB. This information was associated with the Database
Cloud Service instance when it was provisioned.
Username
Use the same user name you used when create your Oracle Database Cloud
Service Instance. You or your administrator provided this user name to create
the Database Cloud Service instance.
Password
Refer to your Oracle Database Cloud Service instance information for the
password your user. You or your administrator provided this password to
create the Database Cloud Service instance.
Schema Prefix
The prefix that is prepended to the schema name in the form

prefix_schemaname, the suggested prefix is PROD1. You use unique prefixes
for each instance, otherwise the instance creation fails.
Schema Password
The password to be used for the RCU schemas of the GoldenGate Cloud
Control repository
Confirm Schema Password
Confirmation of previous password.
In the WebLogic Server Administration Console Access section, configure the user
name and password for your WebLogic access.
Element
Description
Username
The username for your access in the WebLogic Server Console for Cloud
Control administration.
Password
A password for the WebLogic Server.
Confirm Password
Confirmation of your previous choice of password.
Note:
Dont use the same Oracle Database Cloud Service instance with multiple
Oracle GoldenGate Cloud Service instances. This action ensures that you can
restore the database for an Oracle GoldenGate Cloud Service instance without
risking data loss for other service instances.
Selection Summary
, you can review the Service Level, Billing frequency, Software
By clicking in the
version, and edition that is available for your service Instance.
Get the Software Release
In the Selection Summary link, you can get the version of GoldenGate that's installed
for this GoldenGate Cloud Service instance.
The software release is GoldenGate Cloud Service with GoldenGate
12.1.2.1.10 for DB12c/11g on Oracle Linux 6.6.
Confirming Your Selections
The Confirmation page displays the configuration values that you chose in the Create
New Oracle GoldenGate Cloud Service Instance Wizard.
Review the service details.
If you want to go back through the pages, click Previous or the train located on top
of a step.
If you want to cancel out of the wizard without creating a new service instance,
then click Cancel.
If youre satisfied with your choices on the Confirmation page, then click Create.
Note:
You can use your service instance when the instance up icon for GoldenGate
appears for that instance in the Services page.
Create a New, or Use an Existent SSH Key Pair

Oracle GoldenGate Cloud Service requires an SSH public/private key pair for
authenticating access to your service instances through an SSH client.
When you create an Oracle GoldenGate Cloud Service instance, you are asked to
provide the public key of the virtual machine.
When you use SSH to connect to the virtual machine, you provide the private key.
This key matches the public key associated with the Oracle GoldenGate Cloud Service
instance.
You can use the same SSH public/private key pair for all your Oracle cloud services.
You can create your SSH key during the provisioning step by selecting the Create a
New Key option. This option creates a public and a private key file, zipped, and ready
for you to save both files on your computer. This option saves the public key
information for the service instance.
When having an existent SSH Key, the Key File Name option browse to the location of
a file containing a public key. Also the Key Value option allows you to enter the value
of an existing SSH public key.
Extra you can create your independent SSH key and load it using the options for an
existing SSH public key.
Next, two alternatives if you want to crate your SSH key by your own, and then use it
into the required wizard step.
Generate an SSH key pair using the PuTTY Key Generator
1.
Find puttygen.exe in the PuTTY folder on your computer, for example, C:

\Program Files (x86)\PuTTY. Double-click puttygen.exe.
2.
Accept the default key type, SSH-2 RSA.

Note:
SSH-2 is the most recent version of the SSH protocol (and is incompatible
with SSH-1). RSA and DSA are algorithms for computing digital signatures.
3.
Set the Number of bits in a generated key to 2048 bits, if it is not already set with
that value.
Note:
This action sets the size of your key and thus the security level. A minimum of
2048 bits is recommended for SSH-2 RSA.
4.
Click Generate.
5.
To generate randomness to the key, move your mouse around the blank area.
6.
The generated key appears under Public key for pasting into OpenSSH
authorized_keys file.
7.
The key comment is the name of the key that you use to identify it. You can keep
the generated key comment or create your own.
8.
If you want to password-protect your key, enter a Key passphrase and enter it
again for Confirm passphrase. When you reload a saved private key, if one is set,
then you are asked for the passphrase.
While a passphrase is not required, you specify one as a security measure to
protect the private key from unauthorized use.
There is no way to recover a passphrase if you forget it.
9.
Save the private key of the key pair. Depending how you work with the private
key in the future, you need one saved in the PuTTY PPK format. You also need a
saved key in OpenSSH format.
To save the key in the PuTTY PPK format, click Save private key to save the
private key of the key pair.
You can name it anything you want, although you want to use the same name
as you used for the key comment. The private key is saved in PuTTY Private
Key (PPK) format, which is a proprietary format that works only with the
PuTTY toolset.
To save the key in OpenSSH format, open the Conversions menu and select
Export SSH key. This key is the same key, but saved in a different format.
You can name it anything you want, but is recommended you give it the same
name as the key you saved in PPK format. You can also use any extension (or
no extension), but let's use .ssh, to make it clear what format it is.
You can use this key whenever you use OpenSSH to perform SSH actions
using ssh utilities that support OpenSSH. For example, when using Linux in a
command shell.
10. Now you have to create the public key to be paired with the private keys you
created. However, clicking the Save public key button creates a public key that
cant work with Oracle Cloud services in certain cases. Instead, proceed as
follows:
In the PuTTY Key Generator, select all the characters under Public key for
pasting into OpenSSH authorized_keys file.
Make sure that you select all the characters, not just the ones you can see in the
narrow window. If a scroll bar is next to the characters, you aren't seeing all the
characters.
Right click somewhere in the selected text and select Copy from the menu.
Open a text editor and paste the characters, just as you copied them. Start at
the first character in the text editor, and do not insert any line breaks.
Save the key as a text file, using the same root name as you used for the private
key. Add a .pub extension. You can give it any extension you want, but .pub
is a useful convention to indicate that is a public key.
Write down the names of your public and private keys, and note where they
are saved.
Review how to Connect a Cloud VM on Windows with PuTTY.

Creating an SSH Key Pair on the Command Line
To create an SSH key pair on the command line using ssh-keygen:
1.
Open a shell for entering the commands.
2.
At the prompt, enter the following:

ssh-keygen -t rsa -N "" -b "2048" -C "key comment" -f path/root_name
where the arguments are as follows:

-t rsa Use the RSA algorithm.
-N "passphrase" Passphrase to protect the use of the key (like a password).
If you don't want to set a passphrase, don't enter anything between the quotes.
Note:
While a passphrase is not required, you specify one as a security measure to

protect the private key from unauthorized use.
-b "2048" Generate a 2048-bit key. The 2048 value is acceptable, as 2048 is
the default.
Note:
A minimum of 2048 bits is recommended for SSH-2 RSA.

-C "key comment" A name to identify the key.
-f path/root_name The location where the key pair is saved and the root
name for the files. For example, if you give the root name as id_rsa, the name
of the private key is id_rsa and the public key is id_rsa.pub.
3.
Alternatively, you can simply enter ssh-keygen and then enter responses when
prompted for a name and a passphrase. The keys are created with default values:
RSA keys of 2048 bits.
4.
To see that the files were created, type ls path/root_name*.
Backup and Restore

Oracle GoldenGate Cloud Service backup and restore strategy allows you to keep
your data safe.
You have the facility of optionally backup/restore of config/trail data at any point of
replication.
Through backup and restore, you can back up the files located in /u02/data/
ggdata/*. This directory has trail and config files, that can be restored to known
backup point. If you had saved information (like your ssh key), under any other
directory, like /home/opc, the information on there is not being restored.
Disk partition and storage block
Partition
Description
100 Gb (/u02/data)
GoldenGate Cloud Service config and install partition.
50 Gb (/u01/backup)
Partition for backup and restore functionality.
5 Gb (/u01/app/
oracle/tools)
VM Partition (default root partition).
Now when the disk storage is lost, GGCS is able to recover from the backup or the
other cluster node to resume replication process.
Configuring the backup storage details

1.
You purchase the storage container for using the backup and restore facility. You
can create your container before or during the database provisioning using the
wizard.
2.
During the provisioning wizard, you also configure backup and restore. This
action is optional, if you dont need Backup and Restore, then you can mark the
Backup/Restore NONE (NO backup/Restore for instance). If you need Backup
and Restore you can use the Both Remote and Disk Storage option. By now, this
option means Cloud Only for Oracle Database Cloud Service.
3.
If you decide to use Backup and Restore, then you provide the storage container
user name and password during this provisioning. The storage container format
is: <storage service name>-<identity domain name>/<container name>
eg:-Storage-ggcs/ggcs
4.
Once provisioning is done, overview of the related instance has the Additional
Administration section with all available backups and the restore history.
Creating a backup
Before creating a backup:
1.
Make sure all your GoldenGate Cloud Service processes are shut down, otherwise
your pre-check fails.
2.
Review if your backup partition (/u01/backup)

has enough free space to create the archive file.
Note:
If running out of space, you can remove old backup files in local storage
(/u01/backup).
From 16.4.1 onwards, there isnt /u01/backup mount point.
Backup archive is stored locally at /u02/data/backup and then is
uploaded to the provided cloud storage. Temporary archive is removed at the
end of backup/restore operation. This process is applicable for older instances
also once GGCS 16.4.1 deployed in system.
The backup steps include the followings:
Back up Oracle GoldenGate set up (parameter files, defgen files, checkpoint files).
Back up trail files within the defined time window.
In the Backup tab, of the Administration section, click on the Backup Now button to
crate a backup of user data in /u02/data/ggdata/*. This action creates an archive
file in format backup_<backupID>.zip in backup partition /u01/backup/. For
example: /u01/backup/backup?b85e22d2-1af5-4c32-8897fbec50be0b9c.zip
Restoring
Before attempting to restore:
1.
Make sure all your GoldenGate Cloud Service processes are shut down, otherwise
your pre-check fails.
2.
Your backup archive exists locally (/u01/backup)

else check for the backup archive existing in cloud Storage Container. If archive is
inexistent, the restore fails.
Note:
Backup partition (/u01/backup) should have enough space to download the

archive file from cloud Storage Container. This action is performed only in
case the local archive file is not present.
3.
Restore removes all user data in /u02/data/ggdata/* and restore archives file
content. The restore steps include only the service instances.
When clicking in the right menu of the Available Backups section, you have the
options of Restore and Delete. When selecting Restore, a popup window comes for
confirmation along with tracking notes.
Note:
When GoldenGate Cloud Service virtual machine recovers, it preserves the

same IP, virtual machine name, and data under /u02/data folder on the
virtual machine.
Note:
If GoldenGate on the target is lag behind, Oracle GoldenGate pump is able to

resent the trail file. This action includes VM lost or disk storage lost
On cloud, after restoring the backup of the user trail data on target.
To write to a new trail seqno, you have to follow next steps, before proceed with the
data replication:
1.
Start mgr process on cloud.
2.
Alter pump to write to a new trail seqno.

alter pump-name ETROLLOVER
ETROLLOVER causes the extract to increment to the next trail file in the trail
sequence when it restarts.
3.
Start Pump.
4.
When the pump was started, a new Trail file is created on target
5.
Alter Replicat to read from the new trail generated by the pump.
Alter replicat rep-name, extrba 0, extseqno <new-pump-seqno>
6.
Start Replicat.
On cloud, after restoring the backup of the user trail data on source.
To write to a new trail seqno, you have to follow next steps, before proceed with the
data replication:
1.
Restore the backup on source, Start source mgr.
2.
Alter Ext to write to a new trail seqno.

alter Ext-name ETROLLOVER
3.
Start Ext.
4.
Alter pump to write to a new trail seqno.

alter pump-name ETROLLOVER
5.
Alter pump to read from the new trail generated by the Ext.
6.
Start Pump.
7.
Alter Replicat to read from the new trail generated by the pump
Alter replicat rep-name, extrba 0, extseqno <new-pump-seqno>
8.
Start Replicat.
Deleting backups
On existing backup file, you can select the Delete option by clicking in the right menu
of the Available Backups section. Once a delete is requested, the backup archive file is
removed from the local storage (/u01/backup) and the cloud Storage Container.
Note:
See Provision an Oracle GoldenGate Cloud Service Instance
Upgrade and Patch

Oracle GoldenGate Cloud Service allows you to upgrade versions and apply patches
to get all your instance services working with the latest features.
Upgrade of GoldenGate Cloud Service instances created during 16.1.5 version to 16.3.3
is not possible. Any GoldenGate Cloud Service instances created 16.2.5 onwards can
be upgraded to 16.3.3.
The reason is related to the next situations:
1.
GoldenGate Cloud Service 16.1.5 has the service version "16.1.5" which got changed
to "12.1" during GoldenGate Cloud Service 16.2.5.
2.
GoldenGate Cloud Service 16.1.5 has the release version "16.1.5.0" which got
changed to "12.1.2.1.10" during GoldenGate Cloud Service 16.2.5.
GoldenGate Cloud Service 16.4.1 is now supporting GoldenGate Version 12.2.0.1.2,

with this upgrade, Oracle GoldenGate 12.2 features are available for GoldenGate
Cloud Service such as:
Metadata in Trail: No Defgen is needed for heterogeneous replications. This greatly
simplifies the configuration of the heterogeneous data replications.
Automatic Heartbeat Table: provides built-in mechanism to monitor end-to-end

replication lag time.
See Oracle GoldenGate 12.2 documentation for more information about new
features.
This product version is available to previous GoldenGate Cloud Service instances
through patching.
New instances created post GoldenGate Cloud Service 16.4.1 deployment has
GoldenGate product version 12.2.0.1.2.
If you have instances created with previous version, after an upgrade you have
different version numbers related to your instances. For example, you can have
"12.1.2.1.10-X" for new instances, while existing instance versions are "12.1.2.1.10".
Once a patch is registered:
1.
Click on the One or more patches available link, in the overview of the old
instances.
2.
Make sure that all processes are shut down (else pre-check fails), by clicking on
the Precheck option of the menu. Precheck also reviews if data partition (/u02/
data) has at least 2 Gb of space.
3.
Once the pre-check is passed, it shows the summary with the message of no
conflicts found.
4.
You can proceed with patching, by clicking the Patch button. The instance is
shown as under maintenance.
5.
Once patching is completed, the old instance is shown up to new service version,
and no more patches available.
Note:
Rollback is unsupported, attempting this action, would end with

Unsupported message.
Note:
From the Activity tab, you can find status messages if there is a failed attempt
to upgrade.
Rollback
GGCS 16.4.1 supports the rollback functionality. If you want to rollback to older
version of GoldenGate (that is, 12.1.2.1.10), you can click on the Rollback button of
patch applied for older instances. Then it will roll back the instance GoldenGate
version.
Start, Stop, and Restart a GoldenGate Cloud Service Instance

You can keep any unused instance in a shutdown status. With this feature, youre not
billed for this instance in that period.
When you click on the

and Restart options.
on the right top of the detail page, you have the Start, Stop,
Stop
When you click on the Stop option, a confirmation pop-up window is displayed.
Accepting by clicking on the OK button, the verification of the readiness of stopping
the VM is attempted. The verification includes the following:
If all processes related to the instance are shut down.
Review if an older instance (before 16.3.3 release) is upgraded with patch available
in 16.3.3 (This action is to make sure no loose of root partition).
Once these checks are passed, the VM is stopped. After the VM is stopped, the service
status changes to STOPPED.
Testing Stop failures
The verification of possible failures includes the following:
If all processes related to the instance are shut down, otherwise attempt fails.
If it is an older instance (before 16.3.3) and is not upgraded, then the stop attempt
fails. This review is mainly to make sure that there is no data loss. Since older
instances (before 16.3.3) use root partition for installation.
Start
When you click on the Start option of the top right menu, the instance is started
without any additional review.
Once your VM is started, the service status changes to READY.
Restart
When you click on Restart option, the attempt of stop the VM followed by the start
action are performed. The testing for the Stop option is applicable for this attempt.
Restart the SOCKS proxy, after stop/restart VM operation
When you perform the restart/stop operation, the VM, the mgr, and the Extract/
Replicat process goes down.
As the mgr is stopped, the SOCKS proxy connection fails, and the Pump abends.
Once the VM is started/restarted, you have to start all the GG process (mgr, Extract/
Replicat) on target. Then you have to restart the SOCKS proxy and pump on source.

Use access rules to define sources, destinations and ports to control network access, to
or from Oracle GoldenGate Cloud Service components.
To define where traffic is allowed, configure sources, destinations, and ports that
applies for each rule.
From the Services page, click the actions menu for a specific service instance that you
want to create an access rule for.
Next rules are default rules that you cant delete, but you're allowed to enable or
disable as needed.
1.
ora_permit_ggcsrep_ssh, that defines the access allowed from the public Internet
to the GoldenGate Cloud Service VM through port 22 (SSH port). This rule allows
you to connect to the VM for this service instance, for example, with PuTTY,
through port 22.
2.
ora_permit_ggcsrep_ahttps, that define the access allowed from the public

Internet to the WebLogic Server Administration console, where you manage users
and roles and start and stop your GoldenGate Cloud Control services. Each
GoldenGate Cloud Service instance has a menu option to access this console with
the address of http://<IP address of the GGCS instance>:7001/
console.
3.
ora_permit_ggcsrep_bhttps, that define the access allowed from the public

Internet to the GoldenGate Cloud Control dashboard, a cloud based dashboard
for monitoring, analyzing, creating rules, and sending notifications regarding the
data integration and replication of your GoldenGate Cloud Service instances. Each
GoldenGate Cloud Service instance has a menu option to access this dashboard
with the address of http://<IP address of the GGCS instance>:
8001/ggcc.
4.
ora_permit_ggcsrep_chttps, that is reserved for Secure Sockets Layer (SSL) access

to the GoldenGate Cloud Service instance through port 9001. With SSL, you get an
encrypted private communication between the web server and your browser and
instead of http, you use https. So first you have to enable SSL on the GoldenGate
Cloud Control server through the WebLogic Server Administration console, and
then use https://<IP address of the GGCS instance>:9001/
console to access the Cloud Control dashboard.
5.
ora_ggcs2db_dbport, that defines the access allowed from the GoldenGate Cloud
Service VM to its associated database, Oracle Database Cloud Service VM through
port 1521 on that database.
6.
ora_ggcs2dbrepo_repodbport, that defines the access allowed from the

GoldenGate Cloud Service VM to the database containing the schemas for
GoldenGate Cloud Control, through port 1521 on that database.
Access rules variables:
Holds the value of:
PUBLIC_INTERNET
Variable that represents the public Internet.
GGCSRep_GGCS_SERVER
Variable that represents the specific

GoldenGate Cloud Service VM that youre
writing the access rule for.
DB
Variable for the target database. Holds the

value of the target database you selected
when you created the instance.
In addition to default existing rules, you can define custom access rule providing the
information listed.
The following table describes key information about the Oracle GoldenGate Cloud
Service Access Rules that can be created.
Element
Status
Description
indicating that the rule is enabled.
indicating that the rule is disabled.
Rule Name
Unique identification for your rule.
Source
Host from where the TCP access is being allowed.

Available options are:
<Type of Database Cloud Service such as DBaaS or
Exadata>:<Associated Database Cloud Service Name>: DB: Access is
allowed from the database VM associated to this instance. This
database was selected when this service instance was created.
PUBLIC-INTERNET: Access being allowed from public Internet,
which means allowing anyone to connect to the TCP port.
GGCSRep_GGCS_SERVER: The GoldenGate Cloud Service
replication server which is the VM for this replication service and the IP
is provided in the instance detail page for this instance.
GGCSREP_ADMIN_HOST: The WebLogic Administration Server for
this service.
<custom>: Access is allowed either for one IP address, or a range of IP
addresses defined by a slash for the range section.
Destination
The Destination Server/VM to which traffic should be allowed for this

access rule. The available destinations are:
GGCSRep_GGCS_SERVER
GGCSREP_ADMIN_HOST
Destination Ports
The TCP destination port specified for this access rule.
Note:
Only one port can be specified for the destination of
GGCSRep_GGCS_SERVER.
To find out if a port is taken, for example, port 7023, in your VM, use the
netstat command to find out what process or program is using this port.
If the port is taken, then assign a different port for the destination.
$ netstat -na | grep 7023
Protocol
Can either be Transmission Control Protocol (TCP) or User Datagram

Protocol (UDP). TCP is based on connections and can be used for
bidirectional data communication. UDP is for sending data through
packets in chunks.
Description
Notes to identify the purpose of the rule.
Rule Type
Indicates if the rule is a DEFAULT one or a custom created, tagged as

USER.
Includes the enable, disable or delete action, for a custom rules.
For creating a new rule, from the Services page, click the actions menu for a specific
service instance that you want to create an access rule for and then click Access Rules.
On the Access Rules page, click

. This operation takes some time and you
can either continue creating the rule or cancel if needed.
Note:
After you click Create Rule, a window pops with the message that
the Creation of [Name_of_the_rule] access rules is in progress. When the
message disappears, refresh your browser to have the new rule included in
your list.
You can follow this steps through the tutorial: Create Access Rules for Oracle
GoldenGate Cloud Service .

Its possible to replace the SSH public key for your service with a new one.
To update your key, you:
Select a file that contains the new SSH public key by choosing the Upload a new
SSH Public Key value from file option. To choose the file that contains the new
key, click the Browse button.
Introduce a new key value by choosing the Key value option and pasting the
content of the new SSH public key file.
After uploading the SSH key file or pasting the key value, click the Add New Key
button to apply the new key. Or click the Cancel button to keep the previous key.
Note:
The user name that connects with this SSH key to the GoldenGate Cloud
Service VM is opc
Review the steps in the tutorial Update Public/Private Key Pairs of Oracle Public
Cloud Services
Search Activity Log

Its possible to have a summary of the activity log of your service.
To go to the Search Activity utility, you click the Services tab on the GoldenGate
Cloud Service Instance Detail page.
To generate an activity log, you can use different settings combinations.
Start Time Range - You can select a range of time from Start Time to End Time.
Status - Select the status you want to use for the search. Only services with the
selected status are shown.
Service Name - Search for a specific active service name.
Service Type - You can search for GoldenGate Cloud Service or Database Cloud
Service.
Operation - There is a different set of available operations you can choose for
example: Backup or Disable Component.
After selected the options you want to use for the Activity Log, click the Search button
to apply the criteria. Or you can click the Reset button to clear the selections.
You get a table with the Service Names that matches your selected criteria. You get for
each service, its Service Type, Operation, Status, Start, End Time and who Initiated
it.

From the Oracle My Services Dashboard page, you can:
Get details for all your services in the same identity domain.
Get details about the total resources allocated across all Oracle GoldenGate Cloud
Service instances.
Get details for each service instance.
To filter the list to include only the service instances that contain the string in their
service name, use the search field.
To view all Oracle GoldenGate Cloud Service instances in an identity domain:
1. Go to the Oracle Cloud Service Console
a. Sign into the My Services application at http://cloud.oracle.com.
your location.
Then sign into My Services.
b. In the Oracle GoldenGate Cloud Service section, click Oracle GoldenGate
Cloud Service.
The Oracle GoldenGate Cloud Service Console is displayed, showing all Oracle
GoldenGate Cloud Service Instances.

From the Oracle GoldenGate Cloud Service Instance Detail page, you can:
Get a summary of details for the Oracle GoldenGate Cloud Service instance, such
as its description or subscription mode.
Get details and status information for each service instance.
To get detailed information about an Oracle GoldenGate Cloud Service instance:
1. Once in the Oracle GoldenGate Cloud Service console, after you had created one or
more instances.
a. Click on the name of the instance you want to see details.

b. Expand information by clicking in the
triangle icon of each section.
You can also manage this service by selecting any of the following options from the
GoldenGate Cloud Control Console To monitor the instance, manage policies,

notifications and related tasks. For more information, review Getting Started with
Oracle GoldenGate Cloud Control
WebLogic Server Administration Console Makes management tasks more
efficient, for example administer the users.
Start, stop, restart and healthcheck icons For the administration of the VM state.
Access Rules To define where traffic is allowed, configure sources, destinations,
and ports for your service. For more information, review Configure Access Rules.
SSH Access To upload a new SSH Key for your service. For more information,
review Update the SSH Access Key
View Activity Goes to the Activity tab in which you can search and review the
operation log of your service.

When you no longer require an Oracle GoldenGate Cloud Service instance, you can
delete it. Your account is no longer charged for the service instance.
Only a GoldenGate Cloud Service administrator can delete a service instance.
When you delete an Oracle GoldenGate Cloud Service instance:
Compute resources such as block storage volumes and IP addresses are removed.
The Oracle Database Cloud Service instance isnt deleted when you delete the
service instance, only the database repository and schemas are deleted. Your
account remains charged for the database service instance. You probably want to
retain this database service instance for use with other service instances. For more
information, see Deleting an Oracle Database Cloud Service Instance in Using
The Oracle Storage Cloud Service container isnt deleted when you delete the
Oracle GoldenGate Cloud Service instance. Your account remains charged for the
storage container. You probably want to retain this storage container for use with
other service instances. For more information, see Deleting Containers in Using
Oracle Storage Cloud Service.
To delete an Oracle GoldenGate Cloud Service instance:
1. Go to the Oracle GoldenGate Cloud Service console:
a. Sign in to the My Services application at http://cloud.oracle.com.
your location.
Then sign into My Services.
b. In the Oracle GoldenGate Cloud Service section, click Oracle GoldenGate
Cloud Service.
2. Select the service instance you want to delete from the service instance list.
3. From the
menu for the service instance, select Delete.
4. In the Delete Service dialog, click Delete to confirm deleting this service instance.
After deletion, the Oracle GoldenGate Cloud Service is removed from the list of
service instances displayed on the Oracle GoldenGate Cloud Service Console.
Sometimes, the service instances arent deleted properly and the associated resources
arent cleaned up completely. In this case, the Retry Delete displays. Click Retry
Delete to clean up the remaining resources and delete the service instance completely.
The Retry Delete button is displayed for as long as the failed resources exist. Repeat
this process until the Retry Delete button is no longer displayed.
4
Getting Started with Oracle GoldenGate
Cloud Control
Oracle GoldenGate Cloud Control, is a real time, high performance, monitoring
solution. A supporting tool for GoldenGate Cloud Service that provides statistics,
policies, and monitoring tools to control the functionality of GoldenGate Cloud
Service.
You create and configure an Oracle GoldenGate Cloud Service environment without
having to set up any infrastructure or platform details yourself. By using the Oracle
GoldenGate Cloud Control, you can monitor the GoldenGate Cloud Service
environment in the cloud.
Topics:
About Oracle GoldenGate Cloud Control
Oracle GoldenGate Cloud Control Agent
Setup An Oracle GoldenGate Cloud Control Agent

Oracle GoldenGate Cloud Control is a dashboard for cloud reporting and analytics of
cloud and non-cloud GoldenGate environments.
GoldenGate Cloud Control console summarizes current status and different statistics
of registered GoldenGate Cloud Service instances with drill-down to key metrics.
Monitoring works whether databases installed in the cloud or on-premises. Drill down
metrics includes the service status, and the table-level status details. With GoldenGate
Cloud Control you can have answers to questions like: How many operations has
done in the past? Whats the throughput? Which table takes most of the replication
traffic?
How to access Oracle GoldenGate Cloud Control
You can access GoldenGate Cloud Control console from the GoldenGate Cloud
Service detail page. You click on the , and select the GoldenGate Cloud Control
Console option. Users with appropriate groups assigned using the WebLogic Server
console are able to log in after provide username and password.
Getting Started with Oracle GoldenGate Cloud Control 4-1
What are the components of the Oracle GoldenGate Cloud Control.

Component
Description
Connection
Active connections related to the GoldenGate Cloud Service instances that

are active and running.
Task
Any activity related to an active GoldenGate Cloud Service instance
Policy
Criteria definition used for the detection of any kind of activity, conflict,
status, or value based on the configuration of the policy metric.
Notification
Alerts
What You Can Do from the Oracle GoldenGate Cloud Control Console
Use Oracle GoldenGate Cloud Control Console to perform the tasks described in the
following topics:
Monitor your connections, tasks, and notifications.
Create a catalog of tasks and connections.
Create and administer policies.
Administer notifications.
How to configure a Policy
You can create new policies or edit any existing by clicking on the Create Policy
button.
For creating a Policy you enter:
Name (of the Policy)
Description
Priority
Policy Enabled (checkbox)
And a set of Policy Metrics.
The Policy Metrics are composed by:
1.
The Metric that can be selected from the drop-down menu.
2.
Sign of equality or inequality.
3.
A comparative value.
The Policies are the default policies available at the stock policies, and any created by
you.
The default Policy requirements are:
Service Unavailable: status !=RUNNING and Status != REGISTERED
DDL Changed: deltaExecuteDdls >0
Data Discarded: deltaDiscards>0

Conflict Detected: deltaConflictsDetected >0
Lag Exceed the Limite: lastOperationLag > 2s
Then you have to click the Save button to confirm the Policy creation, otherwise you
can click Cancel.
If you want to edit any of the templates, the Edit menu option doesnt have values for
the specified policy. Instead, click the policy name, edit the policy, and save it from
there. If a policy rule doesnt show up when you click its name, then refresh the
Policies page. The policies are still working, even if the policy rule doesnt display
before the refresh.

The primary goal of the GoldenGate Cloud Service Agent is to serve as an
independent layer above the GoldenGate instance. With its architecture, the agent can
provide management and monitoring services irrespective of the GoldenGate instance
version.
Next image shows the GoldenGate Agent General Architecture.
As described in the image, the agent interacts with GoldenGate Instance layer and
GoldenGate Cloud Control service layer. The agent acquires knowledge about these
two layers through a configuration file. The agent is managed with the help of a
command-line interface.
GGCC agent is primarily targeted for Linux and Windows platforms.
Supported GoldenGate Instance versions
GoldenGate Cloud Control Agent can be configured to support the following
GoldenGate Instance versions:
GoldenGate 12.2.0
GoldenGate 12.1.2
Installation of the GoldenGate Cloud Control Agent

Prerequisites for the GoldenGate Cloud Control Agent Set Up
Oracle GoldenGate Cloud Control Agent Properties File
Oracle GoldenGate Cloud Control Agent Commands
Prerequisites for the GoldenGate Cloud Control Agent Set Up

Fulfill the prerequisites, before attempt to set up your GoldenGate Cloud Control
Agent.
Prerequisites
1. Oracle Database installed, follow the instructions Installing and Upgrading Oracle
Database 12c Release 1 (12.1)
2. Oracle GoldenGate Core installed.

3. Set up a sample replication configuration.
4. Make the core manager webservice to start.
a.
Stop manager if it is in started condition.
b.
Create a file named GLOBALS in the OGG_HOME directory, if this file does
not exist.
c.
Edit the GLOBALS file, by adding ENABLEMONITORING on a new line.
d.
Close and save the file.
e.
Create the datastore using the CREATE DATASTORE command: GGSCI$>

CREATE DATASTORE
f.
Start manager.

This section contains the necessary information to get through the installation of the
GoldenGate Cloud Control Agent.
Creating and running GoldenGate Cloud Control Agent is a two-step process:
1.
GoldenGate Cloud Control Agent product/binaries installation.
2.
GoldenGate Cloud Control Agent instance creation.
Due to previous steps, before intend to install, is necessary to know two locations:
Location
Description
$AGENT_HOME
Location where GoldenGate Cloud Control

Agent product or binaries are installed
Location
Description
$AGENT_INSTANCE_HOME
Location where the GoldenGate Cloud

Control Agent Instance is created and all the
configuration and logs are stored.
Note:
Several GoldenGate Cloud Control Agent instances can be created from a

single $AGENT_HOME.
Understanding $AGENT_INSTANCE_HOME
$AGENT_INSTANCE_HOME is the location where agent configuration and logs are
stored. This location identifies a unique GoldenGate Cloud Control Agent.
The following table describes the content of this location.
Location
Description
$AGENT_INSTANCE_HOME/conf
Agent configuration directory.
$AGENT_INSTANCE_HOME/logs
Agent logs directory.
$AGENT_INSTANCE_HOME/conf/
agent.properties
Agent configuration properties file.
$AGENT_INSTANCE_HOME/conf/
logging-config.xml
Oracle Diagnostic Logging (ODL)

configuration file.
$AGENT_INSTANCE_HOME/
demoAgentId.jks
Sample Agent Keystore file.
$AGENT_INSTANCE_HOME/
demoAtentTrust.jks
Sample Agent Truststore file.
GoldenGate Cloud Control Agent Configuration

Once the GoldenGate Cloud Control Agent agent installation and Instance creation is
completed, the agent has to be configured to run according to feature objectives. The
main objective is to configure the GoldenGate core that this agent has to connect. Also
to the GoldenGate Cloud Control Agent Service to which the data has to be pushed.
Connection to server security must be addressed. Hence this configuration files. The
configuration file is located at: $AGENT_INSTANCE_HOME/conf/
agent.properties.
This file must be valued properly before attempting to start GoldenGate Cloud
Control Agent agent. You can review the detailed configuration of the properties file
at:
GGSCI Integration
GoldenGate Cloud Control Agent can integrate with the GGSCI command of the
GoldenGate Instance. Once the agent instance is created, we can run the following
command to integrate the GoldenGate Cloud Control agent with GGSCI:
$AGENT_HOME/bin/ggccAgent $AGENT_INSTANCE_HOME/conf/
agent.properties intgGGSCI <$GG_HOME>
Where$GG_HOME is the location of the GoldenGate Instance. This command integrates
the GoldenGate Cloud Control agent identified by $AGENT_INSTANCE_HOME with
GoldenGate instance identified by $GG_HOME.
After the integration, the following GGSCI commands can be used to start/stop the
GoldenGate Cloud Control Agent:
GGSCI Command
Description
START JAGENT
Initiate the GoldenGate Cloud Control Agent
STOP JAGENT
Stops the GoldenGate Cloud Control Agent
INFO JAGENT
Shows appropriate message weather

GoldenGate Cloud Control Agent is running
(Up! Or Down!)

The following table lists and describes agent properties in the context of Oracle
GoldenGate Cloud Control.
Property
Definition and commands
Default Value
agentPort
Port at which the GGCC agent is

running.
7005
ggInstanceHost
HostName of the machine where

GoldenGate is running.
gghost.example.com
Use the hostname command to get

yours
ggInstancePort
Manager Port of the GoldenGate

instance that you want to connect
7809
You can get it from your GGSCI

interface, through the info mgr
command.
ggCoreVersion
Version of the GoldenGate Instance

that you are connecting.
The following versions with the values
as bellow are supported:
V_12_2_0
V_12_1_2
You can get the version when invoking
the GGSCI through the ggsci
command.
Oracle GoldenGate Command
Interpreter for Oracle
Version 12.2.0.1.2 OGGCORE
12.2.0.1.0
V_12_2_0
Property
Default Value
ggccServiceHost
HostName of the machine where

GoldenGate Cloud Control Service is
running.
ggcchost.example.com
You can get it from the url of your

running service, for example:
1.1.1.1:8001/ggcc/app/
catalog/instances
ggccServicePort
Port number where GoldenGate Cloud

Control Service is running.
8080
Otherwise you can get it from the url

of your running service, for example:
1.1.1.1:8001/ggcc/app/
catalog/instances
ggccServerConnectTi
meout
Connection Time out to GGCC Server

in milliseconds.
60,000 milliseconds = 1
minute.
ggccServerReadTimeo
ut
Read Timeout to GGCC Server in

milliseconds.
60,000 milliseconds = 1
minute.
ggccServerConnectPo
olSize
Connection Pool Size to GGCC server.
agentUseProxy
Set to true if Proxy is to be used for

this agent.
False
proxyHost
HostName where Proxy Server is

configured.
ggccProxy.example.co
m
proxyPort
Proxy Port configured in Proxy Server.
3128
proxyUsingAuth
Check if authentication is required.
False
agentUseSSL
Set to true if SSL is used between

GGCC agent and Sever.
False
agentSSLAlgoName
SSL Algorithm name to be used.

Standard Algorithm Name
Documentation for JDK 8.
TLSv1.2
agentUse2WaySSL
Set to true and

configure agentIDStorePath if GGCC
server is using 2 way SSL.
False
agentIDStorePath
Path to the agent ID store file.
demoAgentId.jks,
located in agent conf
directory.
agentTrustStorePath
Path to the agent ID store file.
demoAgentTrust.jks,
located in agent conf
directory.
agentIDStoreType
Type of the agent ID keystore.Creating

a KeyStore in JKS Format.
JKS
Property
Default Value
agentIDStoreKeyMana
gerFactoryAlgorithm
Store Key Manager Factory algorithm

name. KeyManagerFactory
Algorithms.
SunX509
Enumerate Proxy's used

for remote output trails in
the following format:
proxy<proxyHost>=<actual
Host>
proxyHost - is the IP/hostname of the

proxy used for the remore trail
configuration.
proxymyproxy.example.com
=host.example.com
actualHost - is the actual remote IP/

host of the output trail configuration.
Oracle GoldenGate Cloud Control Agent Commands

The following table lists and describes the Agent commands used in the context of
Oracle GoldenGate Cloud Control.
Command
Usage
More Information
start
Starts the GoldenGate Cloud

Control Agent.
Usual command to start
stop
Stops the Running GoldenGate

Cloud Control Agent.
Usual command to stop
createServerCred
Create the Server Credential

for this agent to connect to
Server.
The User configured

should have
GGCCServiceInvoker
Role.
See Also:
ggccServiceHost,
ggccServicePort in
Oracle GoldenGate
Cloud Control Agent
Properties File
updateServerCred
Update the Server Credential

for this agent to connect to
Server.
See Also: WebLogic

Server Administration
Console
viewServerCred
View the configured Server

Credential for this agent to
connect to GoldenGate Cloud
Control Server.
See Also: WebLogic

Server Administration
Console
createProxy
Create the Proxy credential for

this Agent.
See Also:
agentUseProxy,
proxyHost,
proxyPort,
proxyUsingAuth in
Oracle GoldenGate
Cloud Control Agent
Properties File
Command
Usage
More Information
updateProxy
Update Proxy credential for

this Agent.
See Also:
agentUseProxy,
proxyHost,
proxyPort,
proxyUsingAuth in
Oracle GoldenGate
Cloud Control Agent
Properties File
viewProxy
View the configured Proxy

credential for this Agent.
See Also:
agentUseProxy,
proxyHost,
proxyPort,
proxyUsingAuth in
Oracle GoldenGate
Cloud Control Agent
Properties File
createIDStoreUnlockPass
word
While using SSL, create the ID

store and unlock password to
be used.
See Also:
agentIDStorePath
and agentUseSSL in
Oracle GoldenGate
Cloud Control Agent
Properties File
updateIDStoreUnlockPass
word
Update the ID Store unlock

password created using
createIDStoreUnlockPass
word
See Also:
agentIDStorePath
and agentUseSSL in
Oracle GoldenGate
Cloud Control Agent
Properties File
createTrustStoreUnlockP
assword
While using SSL, create the

Trust store and unlock
password to be used.
See Also:
agentIDStorePath
and agentUseSSL in
Oracle GoldenGate
Cloud Control Agent
Properties File
updateTrustStoreUnlockP
assword
Update the Trust Store unlock

password created using
updateTrustStoreUnlockP
assword command.
See Also:
agentIDStorePath
and agentUseSSL in
Oracle GoldenGate
Cloud Control Agent
Properties File
ggccAgent <path to properties file> [ start / stop /

createServerCred / updateServerCred / viewServerCred /
createProxy / updateProxy / viewProxy ]
Example 1 - Starting the Agent:
ggccAgent ./conf/agent.properties
start
Example 2 - Stopping the Agent:

stop
Example 3 - Creating the Agent Proxy Credentials:

createProxy
Example 4 - Updating the Agent Proxy Credentials:

updateProxy
Example 5 - View the Agent Proxy user details:

viewProxy

This section contains the set of instructions to be followed when setting up
GoldenGate Cloud Control Agent.
As prerequisite, you have one on-premises GoldenGate 12.1.2 or 12.2.0 plus Oracle
Database 12c or a GoldenGate Cloud Service instance as source of the replication
process.
Also, you have one GoldenGate Cloud Service instance as the target of the replication
process.
1.
Install JDK 1.8. Please note that most developer machines come with JRE installed,
but that is not sufficient for development work.
a.
You can download the JDK 1.8 installer from http://www.oracle.com/

technetwork/java/javase/downloads/jdk8-downloads-2133151.html
b.
Please note the installation location for the JDK. You need it when you set the
environment variable JAVA_HOME to latest JDK.
2.
Set the agent parameters on your on-premises environment and confirm that the
AGENT_HOME and AGENT_INSTANCE_HOME are both set.
3.
Unzip your installer (this installation is already done for GoldenGate Cloud
services) and run the GoldenGate Cloud Control installer (ggcc_agent_generic.jar
file).
Note:
If you are accessing your on-premises environment with a client that doesn't
provide the GUI feature, then you need an X server. For example, with
TigerVNC, you don't need an X server.
Follow detailed steps of how to install through the Setup an Agent for
GoldenGate Cloud Control tutorial.
4.
Once your installation is done, on the Services page, go to the GoldenGate Cloud
Control Console by clicking on the right icon
5.
In the login page, enter the IP address and the port number that is shown in the
browser url, for example, http://00.000.000.000:port/ggcc/login.html.
6.
Only in case you have an on-premises environment:
7.
8.
a.
Find the version of GoldenGate and the manager port through the GGSCI.
b.
Find a port for the GoldenGate Cloud Control agent to run on. The default
port number is 7005. First check if this port is taken. If it is, then assign a
different port.
c.
Navigate to $AGENT_INSTANCE_HOME/conf folder. To save the original

version, make a copy of the agent.properties file, and then open it for editing.
Find the Cloud GoldenGate version and the manager port.

a.
On your VM, start GGSCI to find out the version of GoldenGate and the
manager port.
b.
Find a port for the GoldenGate Cloud Control agent to run on. The default
port number is 7005. First check if this port is taken. If it is, then assign a
different port.
c.
Navigate to /u02/data/ggcc/agent/conf folder. This folder contains the

agent.properties file. To save the original version, make a copy of the
agent.properties file, and then open it for editing.
Configure the Cloud Agent Properties File.

agentPort: Port on the host machine that GoldenGate is installed and you
want the GoldenGate Cloud Control agent to run on.
ggInstanceHost: The host name or IP address of the machine that
GoldenGate is running on and the GoldenGate Cloud Control agent crawls on.
ggInstancePort: Manager port for the ggInstanceHost machine.
ggCoreVersion: GoldenGate version for the ggInstanceHost machine. It
is either V_12_2_0 or V_12_1_2.
ggccServiceHost: IP address or host name of the GoldenGate Cloud
Control Service where the dashboard is.
ggccServicePort: Port number for the URL to log in to GoldenGate Cloud
Control on ggccServiceHost.
Note:
To set up new agents on any other cloud or non-cloud machines, all you
change is the ggInstanceHost, ggInstancePort, and ggCoreVersion.
As long as they all point to the same ggccServiceHost and
ggccServicePort, they are discovered on the same GoldenGate Cloud
Control service.
9.
For every agent.properties file that you have setup, go to the machine with the IP
address set for its gginstancehost and start GGSCI.
10. Edit the GLOBALS file, by entering ENABLEMONITORING.

11. With the GGSCI command, create a data store and then start or restart
manager, so the GLOBALS file can take effect.
12. Add the GoldenGate Cloud Control login Information when you create a
GoldenGate Cloud Service instance, in the Details step of the wizard.

Note:
Find the login information for the GoldenGate Cloud Control dashboard,
which is the same as the WebLogic Server Administration Console, from
whomever created the instance.
13. In the Services page of GoldenGate Cloud Service, click the menu option for your
GoldenGate Cloud Service instance, and click GoldenGate Cloud Control

Console.
14. Log in to the dashboard and ensure that the login information works.
15. Now that the login information works, you add the same login information to
your agent. Navigate to the host of every machine that you've setup in your
agent.properties file as the ggInstanceHost.
a.
For on-premises agent, enter: $AGENT_HOME/bin/ggccAgent.sh

$AGENT_INSTANCE_HOME/conf/agent.properties
createServerCred
b.
For cloud agent, $AGENT_HOME and $AGENT_INSTANCE_HOME are not

defined, so instead, enter:
$ sudo su oracle
$cd $GGHOME
$ /u01/app/oracle/middleware/ggccagent/bin/ggccAgent.sh /u02/data/ggcc/
agent/conf/agent.properties createServerCred
Note:
If someone has already created the server credentials and you're not sure that
it is correct, you can use the updateServerCred instead of
createServerCred.
16. Start the Agents.
17. Integrate Agent with GGSCI.
18. Start JAgent on GGSCI. To control the Java agent that sends information to
the Oracle GoldenGate Cloud Control server, start the jagent through GGSCI
19. To have detailed steps for perform a Replication, refer to the Replicate Data from
On-Premises to Cloud with Oracle GoldenGate Cloud Service tutorial.
20. Observe Replication in Cloud Control Dashboard.

This section contains the description of the functionality of the Weblogic Server
You configure the WebLogic Server Administration Console access in the Details
Configuration step of the provisioning wizard for Oracle GoldenGate Cloud Service.
After you can access the WebLogic console from the GoldenGate Cloud Service Detail
page by clicking the
From the WebLogic console, you can perform your administering activities in an
easier way. You can start and stop your managed servers or you can manage your
users, for detailed information you can review: Managing Users from the WebLogic
5
Frequently Asked Questions
This section presents answers to frequently asked questions about Oracle GoldenGate
Cloud Service.
Topics:
What's the Data Replication Scope for Oracle GoldenGate Cloud Service?
What are the supported topologies for GGCS replication?
Why Is Oracle GoldenGate Cloud Service set up with Oracle Database Cloud
Service?
What are the benefits of using your current Oracle GoldenGate installation with
Oracle GoldenGate Cloud Service?
Can I use my existing GoldenGate deployments with GoldenGate Cloud Service?
Is there any additional charge for support?
What's the Data Replication Scope for Oracle GoldenGate Cloud Service?
Now Oracle GoldenGate replication works with only the following settings:
For non-cloud to cloud replication:
Non-cloud source: Oracle Databases 11g and 12c, DB2 z/OS On-Premises and
MySQL 5.6.
Cloud target: Oracle 12c Release 12.1.0.2.0 - 64 Bit Production and Oracle Database
11g Release 11.2.0.4.0 - 64 Bit Production.
For cloud to cloud replication:
Cloud source: Oracle 12c Release 12.1.0.2.0 - 64 Bit Production.
Cloud target: Oracle 12c Release 12.1.0.2.0 - 64 Bit Production.
For cloud to non-cloud replication:
Cloud source: Oracle 12c Release 12.1.0.2.0 - 64 Bit Production.
Non-cloud target: Oracle Databases 11g and 12c, and MySQL 5.6.
Note:
All Database Cloud Service editions are supported and using SOCKS5 proxy,
Corente and SSH connection.
Frequently Asked Questions 5-1

Now Oracle GoldenGate Cloud Service supports the following topologies:
One-to-one replication of on-premises to cloud where local data is replicated in the
cloud.
One-to-one, one-to-many (broadcast) and bi-directional replication of cloud data in
the cloud.
One-to-one replication from cloud to on-premises.
Cloud to on-premises replication.
Note:
Bi-directional replication of cloud data in the cloud now includes the Conflict
Detection and Recovery (CDR) feature of GoldenGate.
Why Is Oracle GoldenGate Cloud Service set up with Oracle Database

Cloud Service?
Oracle Database Cloud Service is an ideal fit for:
Maintaining synchronized Oracle standby or Replicat databases for disaster
recovery and/or query offloading using Oracle Active Data Guard or Oracle
Quickly provisioning high-performance Oracle databases for dynamic business
reasons such as feature development, functionality testing, application certification,
proof of concept, and try before buy.
Executing time-sensitive large-scale business applications such as launching a webbased marketing campaign, running loyalty programs, and rolling out new
business initiatives.
What are the benefits of using your current Oracle GoldenGate

installation with Oracle GoldenGate Cloud Service?
Oracle GoldenGate installation is used to support mission-critical systems for data
availability and integration. Oracle GoldenGate also addresses your requirements for
ensuring your data is consistent between cloud and on-premises instances.
Can I use my existing GoldenGate deployments with GoldenGate Cloud

Service?
Yes, you can use your existing non-cloud GoldenGate Extract and data pump to
deliver data to GoldenGate Cloud Service.
The Replicat in GoldenGate Cloud Service instance delivers the data to Oracle
Database Cloud Service.
Do I have to subscribe Oracle Database Cloud Service?

Yes you do. As a prerequisite for using GoldenGate Cloud Service you need:
Oracle Database Cloud Service for in cloud delivery.

No, support is included in the subscription price for this service.
Frequently Asked Questions 5-3
6
Troubleshooting Oracle GoldenGate Cloud
Service
This section describes common problems that you might encounter when using Oracle
GoldenGate Cloud Service and explains how to solve them.
Topics:
I Cant Create Service Instances
Problems with Scaling
Why I Can't Login To My Remote Server With My Private Key After Typing
Correct Passphrase?
I Cant Create Service Instances

I can't create a service when I have many service instances.
Your account might not have enough compute quota to create the service instance.
If you have service instances that you don't need, then delete them. If you need all
your service instances, then contact Oracle Sales and Services to buy more quota for
your account.
I can't create a service instance, even after waiting for an hour.
If service creation fails after one hour, then the system will be experiencing a heavy
load, and resources arent yet available.
Wait before you try again to create the service. If the problem persists, then contact
Oracle Support Services.
I can't create a service instance when the service instance name isnt unique.
If the name for the new service instance is identical to another GoldenGate Cloud
Service instance, Oracle GoldenGate Cloud Service instance creation can fail. This rule
includes even failed service instance. Also, the Oracle GoldenGate Cloud Service
instance name can't be the same as the name of an Oracle Database Cloud Service
instance.
After an Oracle GoldenGate Cloud Service instance creation fails, Oracle GoldenGate
Cloud Service requires some time to remove items that were created during the
attempt. If the new and failed service instance names are identical, then a naming
conflict occurs and the attempt to create the new service instance fails.
Troubleshooting Oracle GoldenGate Cloud Service 6-1
Note: Always ensure that your Oracle GoldenGate Cloud Service instance
names are unique.

Problems that can occur when you attempt a scaling operation.
The following solutions apply to problems with scale-up with Oracle GoldenGate
Cloud Service.
The scaled up storage volume size shown in the summary is different from the
actual volume size in the VM
Scale up the storage to 200 GB using Scale Up/Down option.
Check the summary, it shows the value as 205 GB.
The output of "df -h /u02/data" on the VM gives 197 GB.
This situation is expected due to that some blocks are reserved for inodes and some for
root.
The virtual machine does not show it as scaled up
If you have old instances 16.3.1/16.3.3/16.3.5 and you attempt to scale up, sometimes
your virtual machine does not show it as scaled up.
This issue is due to that the storage scale up is not working for 16.3.5 instances before
upgrade and for 16.3.1 instances after upgrade.
To work around this situation, run below command in VM using oracle user.
#sed -i 's/du -sk/du -sb/' /u01/app/oracle/tools/ggcs/
GGCSRep/vm-scripts/restart-service.sh.
After, you can restart the VM from your user interface to get the issue fixed, or next
scale up attempt, will fix automatically.
My scale up operation does not start
Your scale up operation has been placed in the request queue, and it can be a few
minutes before the operation is performed.
Wait before you try to scale out again. If the problem persists, then contact Oracle
Support Services.
My service is too busy to allow scaling
Your service has a pending maintenance operation such as backup or patching.
Wait until maintenance has completed before you try scaling again.
Why I Can't Login To My Remote Server With My Private Key After Typing
Correct Passphrase?
Problems that can occur when the private key is in the wrong format.
Why I Can't Login To My Remote Server With My Private Key After Typing Correct Passphrase?
After enter a passphrase for a private key I get the Permission denied
message
When using PuTTY, I can get the error message like this:
Unable to use key file "D:\oracle_dbaas.sshkey" (OpenSSH SSH-2
private key)
This is because the PuTTY private key and the OpenSSH private key are in different
format. Please use PuTTYGen to convert to a correct format, for detailed steps review:
Change Private Key Format to Use with PuTTY.
Troubleshooting Oracle GoldenGate Cloud Service 6-3
Why I Can't Login To My Remote Server With My Private Key After Typing Correct Passphrase?

Using Oracle GoldenGate Cloud Service

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Using Oracle GoldenGate Cloud Service

Transféré par

Droits d'auteur :

Formats disponibles

Oracle Cloud

Using Oracle GoldenGate Cloud Service

Oracle Cloud Using Oracle GoldenGate Cloud Service,

1 Getting Started with Oracle GoldenGate Cloud Service

About the Components of Oracle GoldenGate Cloud Service...........................................................

About the Interfaces to Oracle GoldenGate Cloud Service ................................................................

Replication Configuration Templates....................................................................................................

Before You Begin with Oracle GoldenGate Cloud Service.................................................................

Create and Configure Your Account on Oracle Cloud...............................................................

Create an Oracle Database Cloud Service Instance................................................................... 1-10

2 Administering Oracle GoldenGate Cloud Service

Understanding the Default Access Ports...............................................................................................

Scaling an Oracle GoldenGate Cloud Service Block Storage .............................................................

Keeping Your Oracle GoldenGate Cloud Service Instances Manageable ........................................

Software Components Installation Directory Structure......................................................................

3 Managing the Life Cycle of Oracle GoldenGate Cloud Service Instances

Provision an Oracle GoldenGate Cloud Service Instance ..........................................................

Backup and Restore........................................................................................................................ 3-10

4 Getting Started with Oracle GoldenGate Cloud Control

Oracle GoldenGate Cloud Control Agent.............................................................................................

Prerequisites for the GoldenGate Cloud Control Agent Set Up................................................

Installation of the GoldenGate Cloud Control Agent .................................................................

Oracle GoldenGate Cloud Control Agent Properties File..........................................................

Oracle GoldenGate Cloud Control Agent Commands ...............................................................

Setup An Oracle GoldenGate Cloud Control Agent ......................................................................... 4-10

5 Frequently Asked Questions

What are the supported topologies for GGCS replication? ................................................................

GoldenGate Cloud Service?...............................................................................................................

Can I use my existing GoldenGate deployments with GoldenGate Cloud Service?......................

Is there any additional charge for support?..........................................................................................

6 Troubleshooting Oracle GoldenGate Cloud Service

I Cant Create Service Instances..............................................................................................................

Problems with Scaling..............................................................................................................................

Oracle Storage Cloud Service

Indicates graphical user interface elements associated with an

Indicates book titles, emphasis, or placeholder variables for

Indicates commands within a paragraph, URLs, code in

About Oracle GoldenGate Cloud Service

Getting Started with Oracle GoldenGate Cloud Service 1-1

About Oracle GoldenGate Cloud Service

Using Oracle GoldenGate Cloud Service, you can do the following:

1-2 Using Oracle GoldenGate Cloud Service

About the Components of Oracle GoldenGate Cloud Service

About the Components of Oracle GoldenGate Cloud Service

Getting Started with Oracle GoldenGate Cloud Service 1-3

About the Components of Oracle GoldenGate Cloud Service

The following image illustrates the replication from cloud to on-premises.

1-4 Using Oracle GoldenGate Cloud Service

About the Components of Oracle GoldenGate Cloud Service

Getting Started with Oracle GoldenGate Cloud Service 1-5

About the Interfaces to Oracle GoldenGate Cloud Service

For more information see, Accessing Oracle GoldenGate Cloud Service

About the Interfaces to Oracle GoldenGate Cloud Service

1-6 Using Oracle GoldenGate Cloud Service

Replication Configuration Templates

The Enterprise Manager Plug-in for Oracle

Oracle GoldenGate Plug-in

The GoldenGate Cloud Control Console for

Getting Started with Oracle

WebLogic Server Administration Console with a

In the WebLogic Server Administration Console

Supported browsers include:

Accessing Oracle GoldenGate

To create service instances and perform lifecycle