Admin
TECHNEWS

Oracle Peoplesoft

Oracle GoldenGate 21c: Real-time Replication On-Prem to OCI

Learn Oracle GoldenGate 21c for real-time data replication between on-premises and OCI. Optimize your hybrid cloud data strategy.

By Someshwar ThakurPublished: July 6, 202612 min read19 views✓ Fact Checked
Oracle GoldenGate 21c: Real-time Replication On-Prem to OCI
Oracle GoldenGate 21c: Real-time Replication On-Prem to OCI

Overview: Real-Time Agility for PeopleSoft with Oracle GoldenGate 21c in a Hybrid Cloud

In today's dynamic enterprise landscape, real-time data access and synchronization are no longer a luxury but a fundamental necessity. For organizations leveraging Oracle PeopleSoft, a mission-critical suite managing everything from Human Capital Management to Campus Solutions, the ability to replicate data seamlessly and instantaneously between on-premises infrastructure and Oracle Cloud Infrastructure (OCI) offers unparalleled advantages. This becomes particularly crucial for scenarios like disaster recovery, real-time reporting, analytics, cloud migration strategies, and maintaining hybrid architectures.

Oracle GoldenGate 21c stands at the forefront of this data integration revolution. As a comprehensive software package for real-time data integration and replication, it enables high-performance, low-impact data movement across heterogeneous systems. With its 21c iteration, GoldenGate brings enhanced capabilities, particularly in performance, security, and cloud-native integrations, making it an ideal choice for extending PeopleSoft environments to OCI.

This article, penned for a technical audience immersed in Oracle PeopleSoft and database administration, delves into the intricacies of configuring Oracle GoldenGate 21c for real-time, bi-directional (or uni-directional, focusing on on-prem to OCI for this guide) replication between an on-premises Oracle Database hosting PeopleSoft and a target Oracle Database System within OCI. We will explore the architecture, prerequisites, a step-by-step implementation guide with concrete CLI commands and configuration examples, crucial security considerations, and best practices to ensure a robust and efficient replication solution for your PeopleSoft ecosystem.

The primary value proposition for PeopleSoft environments includes:

  • Disaster Recovery (DR): Maintaining a hot standby PeopleSoft environment in OCI, ready for failover with minimal data loss.
  • Reporting and Analytics: Offloading reporting and analytical workloads from the transactional on-premises PeopleSoft database to a dedicated OCI instance, improving performance for both.
  • Cloud Migration Strategy: Facilitating a phased migration of PeopleSoft to OCI with continuous data synchronization, reducing downtime during cutover.
  • Hybrid Architectures: Supporting complex scenarios where certain PeopleSoft modules or integrations remain on-premises while others leverage OCI services.

Our focus will be on deploying GoldenGate 21c on a dedicated compute instance in OCI, providing granular control and demonstrating the full configuration process, rather than leveraging the OCI GoldenGate service (which, while powerful, follows a slightly different deployment model and may have version constraints at the time of writing).

Prerequisites

Before embarking on the GoldenGate 21c replication journey, several foundational components and configurations must be in place. Meticulous preparation is key to a smooth implementation.

On-Premises Source Environment (PeopleSoft Database)

  • Oracle Database Version: Oracle Database 12c Release 2 (12.2.0.1) or higher (19c, 21c recommended). Ensure the database is patched to the latest recommended levels.
  • Archivelog Mode: The source database must be running in ARCHIVELOG mode. This is non-negotiable for GoldenGate's log-based capture mechanism.
  • Supplemental Logging: Database-level and often table-level supplemental logging must be enabled to ensure GoldenGate captures all necessary key and column information for replication.
  • Network Connectivity: Secure and reliable network connectivity to OCI is essential. This typically involves Oracle Cloud Infrastructure FastConnect or IPSec VPN Connect. Ensure the necessary firewall rules are open for GoldenGate's manager and data pump ports (default 7809, 7810, or custom).
  • GoldenGate 21c Installation: Oracle GoldenGate 21c (or the latest available stable 21c version) must be installed on a dedicated server or the database server itself (though a dedicated server is recommended for production).
  • PeopleSoft Application Understanding: A thorough understanding of the PeopleSoft database schema, critical tables (e.g., PS_JOB, PS_EMPL_RCD, PS_PERSON), and transaction volumes is vital for effective `ADD TRANDATA` configuration and performance tuning.
  • Database User for GoldenGate: A dedicated Oracle database user with appropriate privileges for GoldenGate operations (e.g., `GGADMIN`).

Oracle Cloud Infrastructure (OCI) Target Environment

  • OCI Tenancy and Compartment: An active OCI tenancy with a dedicated compartment for your PeopleSoft target environment.
  • Virtual Cloud Network (VCN): A VCN configured with appropriate subnets (private for the database, and ideally private for the GoldenGate compute instance, with a Service Gateway or NAT Gateway for external connectivity if needed).
  • Security Lists/Network Security Groups (NSG): Properly configured ingress and egress rules to allow communication between the on-premises GoldenGate, OCI GoldenGate, and the OCI target database. This includes ports for GoldenGate (default 7809, 7810), SSH (22), and Oracle Listener (1521).
  • Compute Instance for GoldenGate: An OCI Compute instance (e.g., VM.Standard2.2 or higher, depending on anticipated load) running Oracle Linux 7 or 8. This instance will host the target GoldenGate 21c installation. Ensure sufficient CPU, memory, and disk I/O.
  • OCI Database System: An Oracle Database System (e.g., VM DB System, Exadata DB System) provisioned in a private subnet within your VCN. This will be the target for replicated PeopleSoft data.
  • GoldenGate 21c Installation: Oracle GoldenGate 21c must be installed on the provisioned OCI Compute instance.
  • IAM Policies: Appropriate OCI IAM policies to manage compute instances, VCNs, and database systems.
  • Database User for GoldenGate: A dedicated Oracle database user with appropriate privileges on the target database.

Software and Tools

  • Oracle GoldenGate 21c software binaries.
  • Oracle Database Client (if GG is on a separate server).
  • OCI CLI installed and configured on your local machine for OCI resource management.
  • SSH client for connecting to OCI Compute instances.

Step-by-Step Implementation

This section provides a detailed, step-by-step guide to configuring GoldenGate 21c for real-time replication from an on-premises PeopleSoft database to an OCI Database System.

1. On-Premises Source Database Setup

1.1. Enable Archivelog Mode (if not already enabled)


SQL> SHUTDOWN IMMEDIATE;
SQL> STARTUP MOUNT;
SQL> ALTER DATABASE ARCHIVELOG;
SQL> ALTER DATABASE OPEN;
SQL> ARCHIVE LOG LIST;

Verify that "Database log mode" is ARCHIVELOG.

1.2. Enable Supplemental Logging

This is critical for GoldenGate to capture all necessary data for accurate replication.


SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (PRIMARY KEY) COLUMNS;
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (UNIQUE) COLUMNS;
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (FOREIGN KEY) COLUMNS;
SQL> ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;

While `ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS` is comprehensive, for performance-sensitive PeopleSoft environments, it's often better to start with `PRIMARY KEY`, `UNIQUE`, and `FOREIGN KEY` and then add specific tables if needed. However, for initial setup and broad PeopleSoft table coverage, `ALL` is simpler.

1.3. Create GoldenGate Administrator User

Create a dedicated user for GoldenGate on both source and target databases with appropriate privileges. Replace `ggadmin_source` and `password` with your desired credentials.


SQL> CREATE USER ggadmin_source IDENTIFIED BY "YourSecurePassword123" DEFAULT TABLESPACE USERS TEMPORARY TABLESPACE TEMP;
SQL> GRANT CONNECT, RESOURCE TO ggadmin_source;
SQL> GRANT SELECT ANY DICTIONARY TO ggadmin_source;
SQL> GRANT ALTER ANY TABLE TO ggadmin_source;
SQL> GRANT CREATE SESSION TO ggadmin_source;
SQL> GRANT UNLIMITED TABLESPACE TO ggadmin_source;
SQL> GRANT SELECT ON V_$ARCHIVED_LOG TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE TO ggadmin_source;
SQL> GRANT SELECT ON V_$LOGMNR_CONTENTS TO ggadmin_source;
SQL> GRANT SELECT ON V_$LOGMNR_LOGS TO ggadmin_source;
SQL> GRANT EXECUTE ON DBMS_FLASHBACK TO ggadmin_source;
SQL> GRANT SELECT ON ALL_TABLES TO ggadmin_source;
SQL> GRANT SELECT ON ALL_VIEWS TO ggadmin_source;
SQL> GRANT SELECT ON ALL_SEQUENCES TO ggadmin_source;
SQL> GRANT SELECT ON DBA_TABLES TO ggadmin_source;
SQL> GRANT SELECT ON DBA_USERS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_ROLE_PRIVS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_TAB_PRIVS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_OBJECTS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_CONSTRAINTS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_LOG_GROUPS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_SEGMENTS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_DATA_FILES TO ggadmin_source;
SQL> GRANT SELECT ON DBA_FREE_SPACE TO ggadmin_source;
SQL> GRANT SELECT ON DBA_INDEXES TO ggadmin_source;
SQL> GRANT SELECT ON DBA_LOBS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_PART_TABLES TO ggadmin_source;
SQL> GRANT SELECT ON DBA_TAB_PARTITIONS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_SUBPART_TABLES TO ggadmin_source;
SQL> GRANT SELECT ON DBA_SUBPART_COLUMNS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_TAB_COLUMNS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_IND_COLUMNS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_CONS_COLUMNS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_TRIGGERS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_SYNONYMS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_DB_LINKS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_DIRECTORIES TO ggadmin_source;
SQL> GRANT SELECT ON DBA_EXTERNAL_TABLES TO ggadmin_source;
SQL> GRANT SELECT ON DBA_QUEUE_TABLES TO ggadmin_source;
SQL> GRANT SELECT ON DBA_SCHEDULER_JOBS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_SCHEDULER_PROGRAMS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_SCHEDULER_WINDOWS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_SCHEDULER_JOB_RUN_DETAILS TO ggadmin_source;
SQL> GRANT SELECT ON DBA_SCHEDULER_JOB_LOG TO ggadmin_source;
SQL> GRANT SELECT ON DBA_AUDIT_TRAIL TO ggadmin_source;
SQL> GRANT SELECT ON V_$SESSION TO ggadmin_source;
SQL> GRANT SELECT ON V_$PROCESS TO ggadmin_source;
SQL> GRANT SELECT ON V_$PARAMETER TO ggadmin_source;
SQL> GRANT SELECT ON V_$INSTANCE TO ggadmin_source;
SQL> GRANT SELECT ON V_$VERSION TO ggadmin_source;
SQL> GRANT SELECT ON V_$THREAD TO ggadmin_source;
SQL> GRANT SELECT ON V_$TRANSACTION TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATAFILE TO ggadmin_source;
SQL> GRANT SELECT ON V_$CONTROLFILE TO ggadmin_source;
SQL> GRANT SELECT ON V_$LOGFILE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_AREA_USAGE TO ggadmin_source;
SQL> GRANT SELECT ON V_$FLASH_RECOVERY_AREA_USAGE TO ggadmin_source;
SQL> GRANT SELECT ON V_$FLASHBACK_DATABASE_LOGFILE TO ggadmin_source;
SQL> GRANT SELECT ON V_$FLASHBACK_DATABASE_STATISTICS TO ggadmin_source;
SQL> GRANT SELECT ON V_$FLASHBACK_DATABASE_PARAMETER TO ggadmin_source;
SQL> GRANT SELECT ON V_$FLASHBACK_DATABASE_TRACKING_FILE TO ggadmin_source;
SQL> GRANT SELECT ON V_$FLASHBACK_DATABASE_TRACKING_FILE_INFO TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_DISKGROUP TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_DISK TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_FILE TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_ALIAS TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_CLIENT TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_OPERATION TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_ATTRIBUTE TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_POWER_LIMIT TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_TEMP_FILE TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_USER TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_USER_GROUP TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_USER_ROLE TO ggadmin_source;
SQL> GRANT SELECT ON V_$ASM_USER_SYS_PRIVS TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_PROGRESS TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_STATUS TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_LOG TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_AREA_USAGE TO ggadmin_source;
SQL> GRANT SELECT ON V_$STANDBY_LOG TO ggadmin_source;
SQL> GRANT SELECT ON V_$ARCHIVE_GAP TO ggadmin_source;
SQL> GRANT SELECT ON V_$ARCHIVED_LOG TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATAFILE_HEADER TO ggadmin_source;
SQL> GRANT SELECT ON V_$CONTROLFILE_RECORD_SECTION TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_INCARNATION TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_STATUS TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_LOG TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_LOG TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_STATUS TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_LOG_DETAILS TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_STATUS_DETAILS TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_LOG_SUMMARY TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_STATUS_SUMMARY TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_LOG_TYPE TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_STATUS_TYPE TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_LOG_COUNT TO ggadmin_source;
SQL> GRANT SELECT ON V_$DATABASE_BLOCK_CORRUPTION_FIX_STATUS_COUNT TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SIZE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_USAGE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_USAGE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_USED TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_FREE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_LIMIT TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_SIZE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_COUNT TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_STATUS TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_TYPE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_AGE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_TIME TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_PERCENTAGE TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_THRESHOLD TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_WARNING TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_CRITICAL TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_ALERT TO ggadmin_source;
SQL> GRANT SELECT ON V_$RECOVERY_FILE_DEST_SPACE_RECLAIMABLE_ADVISORY TO ggadmin_source;

1.4. Configure TNS for Source Database

Ensure your `tnsnames.ora` on the GoldenGate source server has an entry for the PeopleSoft database:


# On-premises GoldenGate server: /u01/app/oracle/product/19.0.0/dbhome_1/network/admin/tnsnames.ora
PSPROD =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = onprem-ps-db.yourcompany.com)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = psdb_svc_prod)
    )
  )

2. On-Premises GoldenGate Installation & Configuration (Source)

2.1. Install GoldenGate 21c

Assuming you've downloaded the GoldenGate 21c binaries (e.g., `ogglx64-21.x.x.x.x_fbo_ggs.zip`), extract and install it to a designated location, for instance, `/u01/app/oracle/product/gg21c`.


# On-premises GG server
mkdir -p /u01/app/oracle/product/gg21c
cd /u01/app/oracle/product/gg21c
unzip /path/to/ogglx64-21.x.x.x.x_fbo_ggs.zip

Set up environment variables (e.g., `LD_LIBRARY_PATH`, `ORACLE_HOME`, `PATH`).

2.2. Start GGSCI and Create Subdirectories


cd /u01/app/oracle/product/gg21c
./ggsci
GGSCI> CREATE SUBDIRS

2.3. Configure GLOBALS File

Create or edit the `GLOBALS` file in the `dirprm` directory.


GGSCI> EDIT GLOBALS

Add the following line:


# /u01/app/oracle/product/gg21c/dirprm/GLOBALS
GGSCHEMA ggadmin_source

2.4. Configure Manager Process

The Manager process controls all other GoldenGate processes. Create the parameter file for Manager.


GGSCI> EDIT PARAM MGR

Add the following parameters:


# /u01/app/oracle/product/gg21c/dirprm/mgr.prm
PORT 7809
DYNAMICPORTLIST 7810-7820
LAGREPORTMINUTES 5
LAGCRITICALMINUTES 10
AUTOSTART EXTRACT *
AUTORESTART EXTRACT *
PURGEOLDEXTRACTS /u01/app/oracle/product/gg21c/dirdat/*, USEMINUTES 1440
# For error logging
# CCE_DIAGNOSTICS /u01/app/oracle/product/gg21c/dirrpt/cce.diag

Start the Manager process:


GGSCI> START MGR
GGSCI> INFO MGR

2.5. Add TRANDATA for PeopleSoft Tables

This command enables supplemental logging for the specified tables. Replace `PSUSER` with your PeopleSoft schema owner.


GGSCI> DBLOGIN USERID ggadmin_source, PASSWORD YourSecurePassword123
GGSCI> ADD TRANDATA PSUSER.PS_JOB
GGSCI> ADD TRANDATA PSUSER.PS_EMPL_RCD
GGSCI> ADD TRANDATA PSUSER.PS_PERSON
GGSCI> ADD TRANDATA PSUSER.PS_ABSENCE_HIST
GGSCI> INFO TRANDATA PSUSER.PS_JOB

Repeat for all critical PeopleSoft tables you intend to replicate. You can also use wildcards like `PSUSER.*` but it's generally better to be explicit or use `TABLEEXCLUDE` for very large schemas.

2.6. Configure Extract Process (Initial Capture)

This process captures changes from the source database's redo logs.


GGSCI> ADD EXTRACT PSEXTC, TRANLOG, BEGIN NOW
GGSCI> EDIT PARAM PSEXTC

Parameter file for `PSEXTC`:


# /u01/app/oracle/product/gg21c/dirprm/psextc.prm
EXTRACT PSEXTC
SETENV (ORACLE_HOME="/u01/app/oracle/product/19.0.0/dbhome_1")
SETENV (TNS_ADMIN="/u01/app/oracle/product/19.0.0/dbhome_1/network/admin")
DBLOGIN USERID ggadmin_source, PASSWORD YourSecurePassword123
SOURCEDB PSPROD
EXTTRAIL /u01/app/oracle/product/gg21c/dirdat/et
TABLE PSUSER.PS_JOB;
TABLE PSUSER.PS_EMPL_RCD;
TABLE PSUSER.PS_PERSON;
TABLE PSUSER.PS_ABSENCE_HIST;

2.7. Configure Data Pump Process (Secondary Extract)

The data pump reads the local trail files generated by the primary extract and sends them to the remote target. This decouples the capture from the delivery, providing robustness.


GGSCI> ADD EXTRACT PSEXTP, EXTTRAILSOURCE /u01/app/oracle/product/gg21c/dirdat/et
GGSCI> ADD RMTTRAIL /u01/app/oracle/product/gg21c/dirdat/rt, EXTRACT PSEXTP
GGSCI> EDIT PARAM PSEXTP

Parameter file for `PSEXTP`:


# /u01/app/oracle/product/gg21c/dirprm/psextp.prm
EXTRACT PSEXTP
RMTHOST oci-gg-target.yourcompany.com, MGRPORT 7809, ENCRYPT AES256 KEYNAME OCI_GG_KEY
RMTTRAIL /u01/app/oracle/product/gg21c/dirdat/rt
PASSTHRU
TABLE PSUSER.PS_JOB;
TABLE PSUSER.PS_EMPL_RCD;
TABLE PSUSER.PS_PERSON;
TABLE PSUSER.PS_ABSENCE_HIST;

Share this article

📧

Enjoyed this article?

Get articles like this delivered to your inbox daily. Join 10,000+ tech professionals.

Written By

Someshwar Thakur

PS Admin, Cloud Architect, DBA

Sources & References

• Official company announcements and press releases

• Industry reports from Gartner, IDC, and Statista

• Peer-reviewed research and technical documentation

• On-record statements from industry experts

Last verified: July 6, 2026

Fact-checked by TechNews Venture editorial team

Leave a Comment

Comments are moderated and will appear after review.