GDS Networks
Global Data Services (GDS) networking supports high availability, workload management, and scalable sharding by orchestrating network communication between distributed Oracle Database environments.
GDS networking components include GDS management, registration, event notifications, connection forwarding, workload routing, and cross-sharding connections. Cross-sharding connections are communications that occur between different database shards within a sharded Oracle database environment.
Networking Components
- GDS: Global Data Services
Enables workload balancing and high availability across distributed, replicated database environments..
- GSM: Global Service Manager
The GDS component that manages services, provides load balancing, routes client connections, and monitors database/service health.
- ONS: Oracle Notification Service
Mechanism for broadcasting Fast Application Notification (FAN) and load balancing events to clients and services across the GDS environment.
- OCI: Oracle Call Interface
A low-level API for interacting with database services, used by applications and middleware to access databases.
- AQ: Advanced Queuing
Oracle Message queuing service, sometimes used internally for database notifications and inter-process communication.
- NSGR: Namespace Global Registration (Listener Registration)
Internal Oracle protocol for registering service information with listeners (such as GSM listeners), supporting dynamic service discovery.
- IPC: Inter-Process Communication
Mechanism for communication between processes on the same server, used for internal component operations.
- JDBC: Java Database Connectivity
Standard Java API for database connections, used by Java applications to connect to Oracle databases (including for administration).
- RPC: Remote Procedure Call
Protocol enabling a program on one server to execute code on another server, used for some inter-component operations.
GDS and Oracle Processes
- gsmoci: GSM Oracle Call Interface process
- lreg: Database (instance) registration process
- tnslsnr: Oracle TNS listener process
- gsmopxy: GSM proxy process
- gsmonsc: GSM ONS client process
- gsmmon: GSM monitor process
- pinger: Network performance measurement process within GSM
The following table explains how GDS networking components are used within the Global Data Services environment.
Table 2-1 Network Communication Configuration
| Purpose | Client | Server | Protocol | Default Port |
|---|---|---|---|---|
| GDS Management | GSM ( GDSCTL ) | Database (foregrounds) | OCI/AQ | 1521 |
| Catalog and global services registration | Database ( lreg ) | GSM ( tnslsnr ) | NSGR | 1521 |
| Service/database/sharding events | GSM ( gsmopxy, gsmonsc ) | Clients | ONS Notifications | 6234 |
| Connection forwarding | Clients | GSM ( tnslsnr ) | SQL*Net | 1522 |
| Workload | Clients | GSM Pool (databases) | driver | 1521 |
| Cross-sharded | Clients | GSM Pool (databases) | driver | 1521 |
| Status/start/stop | GDS | GSM ( gsmmon ) | IPC (same server) | No default (private ports) |
| GDS Management | GDS | GSM Catalog | JDBC/OCI | 1521 |
| Status/validate | GDS | GSM pool (databases) | JDBC/OCI | 1521 |
| Network performance measure | GSM (pinger) | GSM (pinger) | RPC | No default (private ports) |
| ONS subscription | GSM ( gsmmonsc ) | GSM Pool (databases) | ONS notifications | 6234 |
Parent topic: Global Data Services Components