6 Maintain Your GoldenGate Cloud Instances

Learn how to perform maintenance tasks, such as reviewing the activity log, updating the SSH access key, managing access rules, scaling, performing back and restore procedures, and upgrading your service instance.

Best Practices to Keep Your Instances Manageable

Use these best practices to 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.

To keep your Oracle GoldenGate Cloud Service instances manageable, follow these guidelines:

  • Don’t 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.
  • Don’t 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 Oracle GoldenGate Cloud Offerings.

  • Don’t 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: View the SSH Access Page.

View Instance Details

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 a variety of tasks.

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.

Element Description

Administration section

Displays if there are patches available for the service instance and the status of the last successful backup, if exists.

Menu icon

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 View the SSH Access Page

  • Access Rules — To define where traffic is allowed, configure sources, destinations, and ports for your service. For more information, review Enable Access to Service Components

  • 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.

Start icon

Starts the service.

Stop icon

Stops the service.

Restart icon

Re-starts the service.

Monitoring information icon

Opens the Healthcheck section.

Healthcheck results (retrieving date)

Displays monitoring information:

  • Memory utilization percent

  • File system usage percent

  • CPU utilization percent

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

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 clicking the Triangle icon it shows:
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 you’re using.

  • 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.

Resources when clicking the Triangle icon it shows:
The summary of the following details
  • Host Name

  • Public IP

  • Instance

  • OCPUs

  • Memory

  • Storage

Associated Services when clicking the Triangle icon it shows:

  • 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 there’s an in-progress operation, a message section appears at the bottom with:
  • Service Name

  • Operation

  • Status

  • Start and End times

Review Activities on Your Instance

Use this page to search and review activities of Oracle GoldenGate Cloudservice instances in your identity domain. You can restrict the list of activities displayed using search filters.

What You Can Do From the Activity Page

Use the Activity page to view operations for all Oracle GoldenGate Cloud service instances in your identity domain.

You can use the page’s Search Activity Log section to filter the list of displayed operations based on:

  • The time the operation was started

  • The status of the operation

  • The name of the service instance on which the operation was performed

  • The type of the operation

In the table of results, you can:

  • Click any column heading to sort the table by that column.

  • Click the triangle at the start of an operation’s row to see more details about that operation.

What You See on the Activity Page

The following table describes the key information shown on the Activity page.

Element Description

Start Time Range

Filters activity results to include only operations started within a specified time range. The range defaults to the previous 24 hours.

Status

Filters operations by status of the operation:

  • All

  • Scheduled

  • Running

  • Succeeded

  • Failed

You can select any subset of status types. The default value is All.

Service Name

Filters the activity results to include operations only for the specified service instance. You can enter a full or partial service instance name.

Service Type

Filters the activity results to include operations only for instances of the specified service type. The default value is the current cloud service.

Operation

Filters the activity results to include selected types of operations. You can select any subset of the given operations. The default value is All.

Search

Searches for activities by applying the filters specified by the Start Time Range, Status, Service Name, Service Type and Operation fields, and displays activity results in the table.

Reset

Clears the Start Time Range and Service Name fields, and returns the Status and Operation fields to their default values.

Results per page

Specifies the number of results you want to view per page. The default value is 10.

expansion arrow

Displays status messages for the given operation. Clicking on the resulting downward arrow hides the status messages.

Service Name

Shows the name of the service instance and its identity domain: service_instance:identity_domain.

You can sort the column in ascending or descending order.

Service Type

Shows the type of cloud service for this instance.

You can sort the column in ascending or descending order.

Operation

Shows the type of operation performed on the service instance.

You can sort the column in ascending or descending order.

Status

Shows the status of the operation performed on the service instance.

You can sort the column in ascending or descending order.

Start Time

Shows the time the operation started.

You can sort the column in ascending or descending order.

End Time

Shows the time the operation ended, if the operation is complete.

You can sort the column in ascending or descending order.

Initiated By

Shows the user that initiated the operation. The user can be any user in the identity domain who initiated the operation or, for certain operations such as automated backup, System.

You can sort the column in ascending or descending order.

View Access Rules

Use the Access Rules page to control network access to Oracle GoldenGate Cloud Service instances. From this page you can view, manage, and create Oracle Compute Cloud Service access (or security) rules.

What You Can Do From the Access Rules Page

Use the Access Rules page to perform the tasks described in the following topics:

What You See on the Access Rules Page

This table describes the key information shown on the Access Rules page.

Element Description

Results per page

Specifies the number of results you want to view per page. The default value is 10.

Create Rule

Click to create a new rule. See Enabling Access to Service Components..

Status

Displays an icon that indicates whether a rule is enabled or disabled.

access rule enabled

Indicates the rule is enabled.

access rule disabled

Indicates the rule is disabled.

Rule Name

Name of the rule. When creating a rule, this must start with a letter, followed by letters, numbers, hyphens, or underscores. The name cannot start with ora_ or sys_.

Source

Hosts from which traffic is allowed. Possible values are:

  • <Type of Database Cloud Service such as DBaaS or Exadata>:<Associated Database Cloud Service Name>: DB

  • PUBLIC-INTERNET

  • GGCSRep_GGCS_SERVER

  • GGCSREP_ADMIN_HOST

  • Custom value in the form of an IP address.

Destination

Destination Server/VM to which traffic is allowed. Possible values are : GGCSRep_GGCS_SERVER or GGCSREP_ADMIN_HOST

.

Ports

Port or range of ports for the rule.

To find out if a port is taken in your VM, use the netstat command to find out what process or program is using this port. For example, $ netstat -na | grep 7023. If the port is taken, then assign a different port for the destination.

Note:

Only one port can be specified for the destination of GGCSRep_GGCS_SERVER.

Description

Description of the rule.

Protocol

Possible values are:

  • TCP Transmission Control Protocol — Based on connections and used for bidirectional data communication.

  • UDP User Datagram Protocol — Used for sending data through packets in chunks.

Rule Type

Type of rule. Rule types are:

  • DEFAULT — Rules created automatically when the database deployment was created. Can be enabled or disabled, but not deleted. See TBD.

  • SYSTEM — Rules created by the system. Cannot be enabled, disabled, or deleted.

  • USER — Rules created by you or another user. Can be enabled, disabled, or deleted.

Menu icon (for rule)

Menu that provides the following options:

  • Enable — Enable the rule.

  • Disable — Disable the rule.

  • Delete — Delete the rule (USER rules only).

Enable Access to Service Components

You use access rules in Oracle GoldenGate Cloud Service to control access to the service components that make up your service instance.

Oracle GoldenGate Cloud Service configures a set of default access rules when it creates a service instance. Some of these are system access rules, which cannot be disabled. These rules control which nodes can be accessed from the Internet, which nodes can access other nodes, and which nodes can access other cloud services. With the exception of SSH access on port 22, the default access rules created for an Oracle GoldenGate Cloud Service instance are disabled to ensure the instance is secure by default. To open access to service components, you need to enable one of these default access rules or create a custom access rule of your own. You cannot edit an existing access rule; you must delete and recreate it.

Default Access Rules
  • ora_permit_ggcsrep_ssh: controls access to port 22, the port used by SSH.

  • ora_permit_ggcsrep_ahttps: controls access to port 7001, the port used by the WebLogic Server Administration console. This is where you manage users and roles and start and stop your Oracle GoldenGate Cloud Control services. Each service instance has a menu option to access this console with the address of http://<IP address of the GGCS instance>:7001/console.

  • ora_permit_ggcsrep_bhttps: controls access to port 8001, the port used by the Oracle GoldenGate Cloud Control dashboard. This is a cloud based dashboard you use for monitoring, analyzing, creating rules, and sending notifications regarding the data integration and replication of your service instances. Each service instance has a menu option to access this dashboard with the address of http://<IP address of the GGCS instance>:8001/ggcc.

  • ora_permit_ggcsrep_chttps: controls access to port 9001, the port used for HTTPS connections to Oracle GoldenGate Cloud Service. First, you must 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.

  • ora_ggcs2dbrepo_repodbport: controls access to port 1521 to allow communication from the GoldenGate Cloud Service VM to the database containing the schemas for GoldenGate Cloud Control.

  • ora_ggcs2dbreporac_repodbportrac: controls access to port 1522 to allow communication from the GoldenGate Cloud Service VM to the RAC database associated with this instance.

System Access Rules

  • sys_infra2gg_admin_ssh: permits PSM to SSH to admin host.

Note:

You cannot delete or disable system access rules.

Enabling or Disabling an Access Rule

You can enable or disable access rules to control access to specific port numbers on specific nodes. Make sure you consider the possible security implications before you open ports to external access.

  1. Open the Oracle GoldenGate Cloud Service console.

  2. Click the Manage this service menu icon menu for the service instance you want to modify, and then select Access Rules.

  3. Locate the rule you want to enable or disable.

    Note:

    You can enable or disable USER and DEFAULT type rules only. You cannot disable SYSTEM type rules.
  4. Click the Actions menu icon menu for the located rule, and then select Enable or Disable.

  5. When prompted for confirmation, click Enable or Disable.

To return to either the Instances page or the Overview page for the selected service instance, click the locator links at the top of the page.

Creating an Access Rule

You create an access rule to enable ports not associated with the default and system access rules, or to restrict access to ports by permitting connections from specific IP addresses only.

For example, you can create rules that:

  • Enable an Oracle Database node to access multiple ports on the WebLogic Server nodes

  • Enable public internet access to a specific port on the WebLogic Administration Server node

Make sure you consider the possible security implications before you open ports to external access.

  1. Open the Oracle GoldenGate Cloud Service console.

  2. Click the Manage this service menu icon menu for the service instance you want to modify, and then select Access Rules.

  3. From the Access Rules page, click Create Rule.

  4. In the Rule Name field, enter a name for the access rule. Name must start with a letter, followed by letters, numbers, hyphens, or underscores. Cannot start with ora_ or sys_.

  5. In the Description field, enter the purpose for the access rule.

  6. In the Source field, select a source from where access needs to be permitted. The available source options depend on the topology of your service instance, and may include:
    • <Type of Database Cloud Service such as DBaaS or Exadata>:<Associated Database Cloud Service Name>: DB: Choose this option to permit access from the database that was selected when this instance was created.

    • PUBLIC-INTERNET : Choose this option to permit public internet access.

    • GGCSRep_GGCS_SERVER : Choose this option to permit access from the GoldenGate Cloud Service replication server which is the VM for this instance.

    • GGCSREP_ADMIN_HOST : Choose this option to permit access from the WebLogic Administration Server for this instance.

    • custom : Choose this option to define a custom list of addresses from which traffic should be allowed. In the field that displays when you select this option, enter a comma-separated list of IP addresses for which you want to permit access.

  7. In the Destination: field, select the service component to which access needs to be allowed. The available options are GGCSRep_GGCS_SERVER and GGCSREP_ADMIN_HOST.

  8. In the Destination Port(s): field, enter the port or range of ports through which the source will be granted access to the destination. Specify a single port, such as 1521, or a range of ports separated by a hyphen, such as 1520–1530.

  9. In the Protocol field, select the TCP or UDP transport for this rule.

  10. Click Create.

    The new rule is displayed in the list of rules. New rules are enabled by default.

    Tip:

    If necessary, adjust the number of results displayed on the Access Rules page so you can see the newly created rule.

    To return to either the Instances page or the Overview page for the selected service instance, click the locator links at the top of the page.

Deleting an Access Rule

You delete an access rule to disable access to the specified port number. You can delete only user-created access rules. You cannot delete system-generated access rules.

Also, cannot modify the configuration of an existing access rule. However, you can delete the rule and recreate it.

  1. Open the Oracle GoldenGate Cloud Service console.

  2. Click the Manage this service menu icon menu for the service instance you want to modify, and then select Access Rules.

  3. On the Access Rules page, locate the rule you want to delete.

  4. Click the Actions menu icon menu for the located rule, and then select Delete .

  5. When prompted for confirmation, click Delete .

To return to either the Instances page or the Overview page for the selected service instance, click the locator links at the top of the page.

Oracle GoldenGate Cloud Service Default Access Ports

You can access Oracle GoldenGate Cloud Service resources by using the default ports. In the following table, you find the default ports used by Oracle GoldenGate Cloud Service.

Source Use Default Port

Oracle GoldenGate in the Cloud Manager Process

Default Manager port

7744

Oracle GoldenGate Cloud Service Instances

Secure Shell (SSH) Connection

22

View the SSH Access Page

Use the SSH Access page to view and add SSH public keys to Oracle GoldenGate service instances in your identity domain. You can restrict the list of instances displayed using search filters.

What You Can Do From the SSH Access Page

Use the SSH Access page to view and add SSH public keys to Oracle GoldenGate service instances in your identity domain.

You can use the page’s Search section to filter the list of displayed deployments based on deployment name.

In the table of results, you can:

  • Click any column heading to sort the table by that column.

  • Click the triangle at the start of a deployment’s row to see more details.

What You See on the SSH Access Page

The following table describes the key information shown on the SSH Access page.

Element Description

Service Name

Filters the results to include SSH keys only for the specified service instance. You can enter a full or partial instance name.

Service Type

Filters the results to include SSH keys only for service instances of the specified service type. The default value is the current cloud service.

Search

Searches for SSH keys by applying the filters specified by the Service Name and Service Type fields, and displays the results in the table.

Results per page

Specifies the number of results you want to view per page. The default value is 10.

expansion arrow

Displays a description of an item in the results table. Clicking on the resulting downward arrow hides the description.

Service Name

Shows the name of the service instance.

Service Type

Shows the type of cloud service for this service instance.

Last Update

Shows the most recent time the SSH keys for this service instance were updated.

Actions

Click Add New Key to add a new SSH public key to this service instance.

The Add New Key dialog is displayed with its Key value field displaying the most recent SSH public key for this service instance.

Specify the new public key using one of the following methods:

  • Select Upload a new SSH Public Key value and click Choose File to select a file that contains the public key.

  • Select Key value. Delete the current key value and paste the new public key into the text area. Make sure the value does not contain line breaks or end with a line break.

Add an SSH Public Key to Your Instance

You can add Secure Shell (SSH) public keys to an Oracle GoldenGate Cloud Service instance.

You might need to add a new SSH public key to an Oracle GoldenGate Cloud Service instance if the SSH private key that you use to access the service instance becomes lost or corrupted. Or, you might need to comply with your organization’s security policies or regulations.

To add an SSH public key to your Oracle GoldenGate Cloud Service instance, perform the following steps:

  1. Access your service console.
  2. Click the SSH Access tab.
  3. Optional: To locate a specific service instance, complete the fields in the Search area, and then click Search.
    By default, this page displays all Oracle XYZ Service instances.
  4. Click Add New Key for the service instance to which you want to add a new SSH public key.
    The dialog box displays the value of the most recently added public key.
  5. Specify the new public key, by completing one of the following:
    • Select Upload a new SSH Public Key value from file and then use your browser to upload a public key file from your local computer.
    • Select Key Value. Delete the previous public key value from the input field and then enter or paste the new value. Be sure not to include other characters that aren’t part of the key, such as spaces.
  6. Click Add New Key.

Scale Your Instance Block Storage

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.

  • 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

Scale Your Instance

You can scale Up/Down an Oracle GoldenGate Cloud Service instance to change its compute shape, adjusting its capacity in response to changes in workload.

About Changing the Compute Shape of an Instance

The compute shape specifies the number of Oracle Compute Units (OCPUs) and amount of memory (RAM) that you want to allocate to the node.

  • To meet the demands of heavier workloads, scale up the compute shape of a node by choosing a larger compute shape.

    For example, changing the compute shape from OC3 to OC4 doubles the capacity of the node from one OCPU to two OCPUs and doubles the amount of RAM allocated to the node.

  • To save costs if the workload is lightened, scale down the compute shape of a node by choosing a smaller compute shape.

    For example, changing the compute shape from OC4 to OC3 reduces the capacity of the node by half from two OCPUs to one OCPU and reduces the amount of RAM allocated to the node by half.

To scale an Oracle GoldenGate Cloud Service instance:

  1. On the console page, click the name of the service instance you want to scale.
  2. From the menu icon, choose Scale Up/Down.
  3. In the Scale Up/Down dialog box, specify the new compute shape of the instance, then click Yes, Scale Up/Down VM.

With the production Type account you can scale Up/Down your OCPUs.

For Enterprise Edition, this change would affect the metering usage since its HOST OCPU based metering.

For Trial account type, OC3 is the only shape supported and Scale Up/Down option can’t be used even though it appears on it.

Note:

You can't scale a service instance if the service instance is under maintenance such as during patching or backing up.

Perform Backup and Restore

Oracle GoldenGate Cloud Service backup and restore strategy allows you to recover from any data loss, or if you want to resume from a checkpoint of GGCS setup or configuration..

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, this for GGCS instances created before 17.2.1 release. For any instances created after GGCS 17.2.1 release, anything under boot volume (/), would be preserved or restored upon restart of the VM.

Disk partition and storage block

Partition Description

100 Gb (/u02/data)

GoldenGate Cloud Service config and install partition.

50 Gb (/u02/data/backup/ )

Partition for backup and restore functionality.

5 Gb (/u01/app/oracle/tools)

Default LCM tools partition.

Now when the disk storage is lost, GGCS is able to recover from the block storage (zfs) 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 don’t 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. 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 isn’t /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.

In the Backup tab, of the Administration section, click the Backup Now button to create 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-8897-fbec50be0b9c.zip

Note:

Backup archive is stored locally at /u02/data/backup and then is uploaded to the provided cloud storage.

Restoring

Before attempting to restore:
  1. 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.

  2. 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 cloud Storage Container.

Upgrade or Patch Your Instance?

Oracle GoldenGate Cloud Service allows you to upgrade versions and apply patches to get all your service instances 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.

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.

Note:

While applying patches to your Oracle GoldenGate Cloud Service, you must also ensure that the recommended patches are applied to Oracle Database Cloud Service instances. For detailed patching information, see Oracle GoldenGate/Database Recommended Patches and Oracle Database Server Recommended Patches.

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.

Delete Your Instance

Learn how to delete a service instance that is no longer required. Your account is not charged for any service instances that have been deleted.

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 isn’t 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 Oracle Database Cloud Service.

  • The Oracle Storage Cloud Service container isn’t 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:
    1. Sign in to the My Services application at http://cloud.oracle.com.

      In the Cloud Account box, from the Select Data Center drop-down list, select your location.

      Then sign into My Services.
    2. 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 icon 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 aren’t deleted properly and the associated resources aren’t 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.

Send Oracle GoldenGate Environment Data to Oracle Support

Oracle GoldenGate Cloud Service provides you with a Oracle GoldenGate architecture utility that you use to gather and package information about your Oracle GoldenGate environment in your Oracle GoldenGate Cloud Service instance to send to Oracle support team for troubleshooting or other services.

To run the Oracle GoldenGate architecture utility, perform the following steps:
  1. Connect to your Oracle GoldenGate Cloud Service instance.
    ssh -i private_key opc@IP_address_of_your_instance
  2. Once you are connected to your Oracle GoldenGate Cloud Service instance, change user to oracle.
    sudo su - oracle
  3. Add the Java binaries in the PATH environment variable.
    export PATH=$JAVA_HOME/bin:$PATH
  4. Navigate to the /u01/app/oracle/tools/ggcs/GGCSRep/OGGArcGather_v7_5 directory.
    cd /u01/app/oracle/tools/ggcs/GGCSRep/OGGArcGather_v7_5
  5. Execute the gather utility.
    ./gather.sh
  6. Enter the following details when prompted:
    • Customer name
    • Database
    • Location where Oracle GoldenGate is installed
    • Database connection details
The gather utility creates an archive containing all files and data required to perform an Oracle GoldenGate architecture review.

Note:

The data collected and packaged by the gather utility varies depending on your database.