GDS Administration
Overview of Global Data Services Administration
Global Data Services administration covers the catalog, GSM software, regions, pools, services, users, and monitoring, primarily through GDSCTL. Administrators install and upgrade GSMs, maintain the catalog, configure framework components, and manage regions, pools, databases, and services. Administrators require appropriate operating-system access, a catalog account with GSMADMIN_ROLE, and credentials for GSMCATUSER and GSMUSER connectivity. Pool administrators may manage databases and services within assigned pools, while GDSCTL operations update the catalog and propagate changes through GSMs to configuration databases.
Read More: Overview of Global Data Services Administration
Managing the GDS Stack
Managing the GDS stack requires controlled startup and shutdown of its dependent components. Startup proceeds from the catalog and GSMs through pool databases and services to applications, while shutdown follows the reverse order, beginning with clients and ending with the catalog.
Read More: Managing the GDS Stack
Starting Up the GDS Stack
A GDS environment should be started in dependency order: start the catalog database and listener, start GSMs and verify catalog connectivity, start pool databases and listeners, start global services, and finally start applications and clients.
Read More: Starting Up the GDS Stack
Shutting Down the GDS Stack
A safe GDS shutdown follows reverse dependency order: stop applications and clients, stop global services, shut down pool databases and listeners, stop GSMs, and then stop the catalog database and listener.
Read More: Shutting Down the GDS Stack
Monitoring the GDS Environment
GDSCTL provides services, databases, and status commands for monitoring global services, member databases, and GSMs. These commands show service instances and readiness, database registration and health, roles and regions, GSM connectivity to the catalog, mastership, endpoints, pending tasks, reconnections, and diagnostic log locations.
Read More: Monitoring the GDS Environment
Managing Global Data Services
Global Data Services administration includes managing regions and buddy relationships, creating and modifying pools and pool administrators, and adding, validating, modifying, or removing member databases. These activities are performed with GDSCTL while connected to the GDS catalog as required.
Read More: Managing Global Data Services
Managing GDS Regions
GDS regions can be added, modified, or removed with GDSCTL; a single-region configuration automatically receives the default REGIONORA region. Region names must be unique valid identifiers of up to 30 characters, and existing regions can be assigned buddy regions to support configuration relationships.
Read More: Managing GDS Regions
Managing GDS Pools
GDS pools are created and managed with GDSCTL while connected to the catalog. Administrators can add pools, assign pool administrators, modify membership or users, and remove pools. Pool names must be unique valid identifiers, and a default DBPOOLORA pool is created when the catalog is created if no additional pool is required.
Read More: Managing GDS Pools
Managing Member Databases
Managing member databases includes adding databases to pools, configuring valid node checking for registration, and integrating Oracle Data Guard Broker configurations. These procedures ensure databases can provide global services, register securely with GSMs, and participate in role-based service management.
Read More: Managing Member Databases
Adding a Database to a Global Data Services Pool
Before adding a database to a GDS pool, unlock and configure GSMUSER, ensure the database uses an SPFILE, and configure SCAN for RAC databases where applicable. Connect to the catalog and use GDSCTL add database with the database connect identifier, region, and pool; database software, release updates, and datapatch levels must exactly match existing members. Database attributes can later be modified or removed, and pool services are automatically created on newly added databases when applicable.
Read More: Adding a Database to a Global Data Services Pool
Valid Node Checking for Registration
Valid node checking for registration restricts GSM registration requests to approved IP addresses, host names, or subnets. Auto-VNCR normally adds the remote database host during add database operations when the name resolves consistently; otherwise, administrators must manually add invited nodes or subnets to the catalog with GDSCTL.
Read More: Valid Node Checking for Registration
Adding Oracle Data Guard Broker Managed Databases to a Database Pool
A Data Guard Broker configuration is managed as a single unit in GDS and must be added to or removed from one pool as a whole. Databases enter or leave the pool through DGMGRL broker membership changes, not individual GDSCTL operations. Broker configurations can be added only to empty pools, pools cannot mix broker-managed and unmanaged databases, and role-based global services require a broker-managed pool.
Read More: Adding Oracle Data Guard Broker Managed Databases to a Database Pool
Managing Global Services
GDSCTL supports the complete global-service lifecycle across pool databases, including creation, modification, startup, shutdown, enablement, disablement, and deletion. Administration also covers RAC instance placement, regional failover, and graceful application switchover, with service configuration and application connection behavior determining availability during planned or unplanned events.
Read More: Managing Global Services
Creating a Global Service
Create a global service with GDSCTL add service, associating it with a pool and optionally specifying preferred or available databases. Services can be created across all pool databases with preferred_all, while RAC services require a subsequent modify service operation to assign instances before startup.
Read More: Creating a Global Service
Starting a Global Service
GDSCTL start service starts an existing service on eligible pool databases according to preferred databases, role, replication-lag, cardinality, and database health criteria. Newly created services require an explicit initial start; automatic-management services can subsequently start when databases become eligible, whereas manual-management services require administrator-initiated starts on each target database.
Read More: Starting a Global Service
Stopping a Global Service
GDSCTL stop service stops a global service on selected databases or throughout a pool. User-initiated stopping temporarily reduces service cardinality without triggering failover, although the database remains a possible failover target. Automatically managed services may restart after database recovery or new database creation, so manual management is required to suppress automatic startup completely.
Read More: Stopping a Global Service
Enabling a Global Service
GDSCTL enable service reactivates a disabled service on a specified database or pool target. Automatically managed services start immediately when the database is eligible, while manually managed services require a separate start operation; enabling also makes the database eligible as a failover target.
Read More: Enabling a Global Service
Disabling a Global Service
GDSCTL disable service prevents a service from starting or failing over on specified databases. The service must first be stopped, and once disabled it cannot start or serve as a failover target until explicitly enabled again.
Read More: Disabling a Global Service
Modifying Global Service Attributes
GDSCTL modify service changes service properties such as role, replication-lag limits, load balancing, database placement, and RAC-specific settings. It can add, remove, or relocate services among databases and may create, delete, start, or stop service instances as configuration changes are applied.
Read More: Modifying Global Service Attributes
Deleting a Global Service
Delete a global service by stopping it and then using GDSCTL remove service. The operation removes the service definition from the GDS catalog and from every database where the service was created.
Read More: Deleting a Global Service
Adding a Service to a Global Data Services Pool
Use GDSCTL add service to create a service in a pool, optionally with preferred_all to target every pool database. For RAC databases, follow creation with modify service to select preferred instances. Service names must meet uniqueness and length rules, and domain-qualified names must be used in subsequent commands when initially specified with a domain.
Read More: Adding a Service to a Global Data Services Pool
Global Data Services Failover Across Regions Flow
Cross-region failover involves switching or failing over the production database, starting application servers at the secondary site, directing wide-area traffic to the secondary load balancer, and updating DNS as necessary. Automatic or manual DNS failover may require DNS NOTIFY propagation, authoritative and caching-server refreshes, local cache clearing, and eventual routing of clients through the secondary application tier.
Read More: Global Data Services Failover Across Regions Flow
Graceful Application Switchover
Graceful application switchover depends on correctly configured services and applications that obtain connections through those services. FAN-aware pools can drain short transactions efficiently, while long-running workloads or non-FAN connections may require additional quiescing time, planned disconnection, or Application Continuity. Configurations must be tested before production use to validate client, service, and failover behavior.
Read More: Graceful Application Switchover
GDS Patching and Upgrading
Safe GDS patching and upgrading requires validating service definitions and status before and after maintenance and following component versioning rules. Guidance covers rolling upgrades, catalog and GSM sequencing, pool database maintenance, out-of-place GSM updates, and active-environment patching procedures intended to preserve service availability.
Read More: GDS Patching and Upgrading
Overview of Patching and Upgrading GDS
Before and after patching, use GDSCTL configuration and status commands to verify that services are defined and running on the correct databases and instances. Rolling upgrades are possible because the catalog must be at least as new as GDSCTL, GSMs must meet catalog compatibility requirements, and pool databases may be upgraded independently; maintaining at least one compatible GSM supports zero service downtime.
Read More: Overview of Patching and Upgrading GDS
Upgrading Global Data Services
Upgrade operating systems before database and GSM software, preferably through validated out-of-place installations, and verify networking, security, connectivity, failover, and client operations. The recommended sequence is catalog database, GDSCTL-only GSM installations, GSM servers one at a time while keeping one running, and pool databases in administrator-selected order; platform-specific file permissions may be required for in-place GSM upgrades.
Read More: Upgrading Global Data Services
GSM Out-of-Place Update Examples
The example demonstrates a rolling 19.18 update from a 19.3 GDS environment by patching the catalog, alternating GSM mastership while upgrading GSM installations, then patching pool databases individually. It also illustrates moving GSM homes on the same host or to different hosts by copying configuration and wallet files, updating wallet and endpoint settings, restarting GSMs sequentially, refreshing passwords where required, and validating configuration, database, and service status.
Read More: GSM Out-of-Place Update Examples
Global Data Services Patching Example
This procedure patches an active Linux-based GDS environment by validating operating-system prerequisites and OPatch, staging the release update, patching the catalog first, running datapatch and invalid-object checks, and restarting listeners. GSMs are patched one at a time with at least one remaining online to preserve availability; datapatch is used for the catalog database but not for GSM installations.
Read More: Global Data Services Patching Example
Password Management in a GDS Environment
GSMCATUSER password changes require updating the database account with SQL*Plus, synchronizing the catalog through GDSCTL modify catalog, and updating each GSM with its new catalog password. GSMUSER credentials are encrypted in the catalog and can be re-encrypted with new keys. GSMCATUSER and GSMUSER are shared for GSM operations and must not be used for human connections, while GSMADMIN_INTERNAL must remain locked and reserved for GDS-owned objects; sharded environments require coordinated rotation of relevant GSM credentials.
Read More: Password Management in a GDS Environment