validate catalog

Cross checks the Global Data Services catalog, global service manager run-time status, and pool databases, and reports inconsistencies and errors.

Syntax

validate [catalog] 
         [-gsm gsm_name]
         [ {-config | -database db_name} ] 
         [-catpwd cpwd]
         [-dbpwd dpwd]

Options

Table 2-121 GDSCTL validate catalog Options

Option Description
-catpwd cpwd

Provides the GSMCATUSER password, otherwise it is read from the local wallet file by default.

-config

Indicates that the validation should be performed on the Global Data Services catalog configuration only.

-database db_name

Indicates the name of the database for which the cross-check validation should be performed.

-dbpwd dpwd

Provides the pool database password directly if there is only one database in the pool, or if multiple databases in the pool share the same password.

-gsm gsm_name

Specify the global service manager name. If the name is not specified, then GDSCTL uses the current global service manager name for the session (specified with the command set gsm).

Usage Notes

Because the execution of this command involves accessing all databases in a Global Data Services configuration, the GSMCATUSER password is required run it. The password is stored in the wallet of any global service manager that is part of the Global Data Services configuration. Therefore, if you run the command from the ORACLE_HOME of any of the global service managers, the password is automatically extracted from the wallet and does not have to be provided. Otherwise, you must provide the GSMCATUSER password using the -catpwd command option. Alternatively, if all databases in the Global Data Services configuration have the same GSMUSER password, you can specify the password instead of the GSMCATUSER password by using the -dbpwd option.

Example

Validate the catalog:

GDSCTL> validate

The output should be similar to the following:

Validation results:
VLD2: Region "regionora" does not have buddy region
VLD11: GDS pool "marketing" does not contain any databases
VLD12: GDS pool "marketing" does not contain any global services
VLD11: GDS pool "sales" does not contain any databases
VLD12: GDS pool "sales" does not contain any global services
VLD11: GDS pool "mkt" does not contain any databases
VLD12: GDS pool "mkt" does not contain any global services