1. Global Data Services Concepts and Administration
  2. GDS Configuration Best Practices

GDS Configuration Best Practices

In accordance with Oracle Maximum Availability Architecture (MAA), Oracle recommends that you follow these best practices.

  • Each client communicates using an Oracle-integrated connection pool, such as UCP, OCI, or ODP.NET. Connection pools will receive notifications about any service failovers and load balancing advisory events through -Fast Application Notification events.
  • Run three global service managers in each region. Oracle recommends that you create three global service managers in each region so that if one global service manager goes down, then you have two remaining global service managers to provide redundancy. Each global service manager should reside on separate hardware. Global service managers enable connection routing among replicated databases. A global service manager is a stateless, lightweight, and intelligent listener that can repopulate its metadata from the GDS catalog.
  • Protect the GDS catalog database with Oracle Data Guard. The GDS catalog is a small (less than 100 GB) repository that hosts the metadata of the GDS configuration, regions, global service managers, global services, databases, and so on. MAA recommends that you set up a local Oracle Data Guard standby database configured with Maximum Availability database protection mode, Data Guard Fast-Start failover, and a remote physical standby database. All GDS catalog standby databases should use Oracle Active Data Guard for the best data protection, and they should reside on separate hardware and storage.

Parent topic: Global Data Services Configuration