Overview of the GDS Catalog – Configuring and Administering Oracle GDS
Overview of the GDS Catalog
A GDS catalog is a repository that is created in a separate Oracle database. This repository stores the metadata information for a single GDS configuration and all its provided services. Each catalog is associated with only one GDS configuration. The minimum version of Oracle Database that can be used to create the GDS catalog is
12.1. This catalog database can reside on the same servers where the global database configuration database resides, or it can run on a completely different server. Since this catalog database is the central repository for the entire GDS configuration, it is advisable to create this database on a separate host and use Oracle high-availability features such as Oracle RAC and Oracle Data Guard to protect the catalog database from a single point of failure.
In our case, we created a catgds database on the same server, called prim01, where our primary database is running. We will use this database to create the GDS catalog later in the chapter. We also created a physical standby database for the catalog database with the name catgdsdr on the server stbyh01.localdomain. The following is the catalog database information.
Primary Catalog Database Details
Here are the details:
SQL> @/home/oracle/database_info.sql

Standby Catalog Database Details
Here are the details:
SQL> @/home/oracle/database_info.sql

The following is the TNS entry for the primary catalog database in our environment. This entry needs to be added to the tnsnames.ora file of ORACLE_HOME in all the database servers where the gdspool databases and GSMs are running.
CATGDS =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = prim01.localdomain)(PORT = 1521)) (CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = catgds)
)
)