GDSCTL Connections

Some GDSCTL commands require a connection to the shard catalog, and for ceratin operations, GDSCTL must connect to a shard director.

• GDSCTL Catalog Connections
  If you run GDSCTL commands that require a connection to the catalog database, then you must run the GDSCTL CONNECT command before the first command that requires the connection.
• GDSCTL Global Service Manager Connections
  For certain operations, GDSCTL must connect to a global service manager (GSM) instance.

GDSCTL Catalog Connections

If you run GDSCTL commands that require a connection to the catalog database, then you must run the GDSCTL CONNECT command before the first command that requires the connection.

The CONNECT command only needs to be run once in a GDSCTL session.

GDSCTL uses Oracle Net Services to connect to the catalog database or another database in the GDS (or distributed database) configuration. For these connections you can run GDSCTL from any client or host that has the necessary network configuration.

Unless specified, GDSCTL resolves connect strings with the current name resolution methods (such as TNSNAMES).

The GDSCTL operations that require a connection to a catalog database are noted in the usage notes for each command.

See also: connect

GDSCTL Global Service Manager Connections

For certain operations, GDSCTL must connect to a global service manager (GSM) instance.

Unless specified, GDSCTL resolves connect strings with the current name resolution methods (such as TNSNAMES). However, to resolve the GSM name, GDSCTL queries the gsm.ora file.

To connect to a GSM, GDSCTL must be running on the same host as the GSM instance. When connecting to a GSM, GDSCTL looks for the gsm.ora file associated with the local GSM.

The following are the GDSCTL operations that require a connection to a GSM.

• ADD GSM adds a GSM instance.

• START GSM starts the GSM instance.

• STOP GSM stops the GSM instance.

• MODIFY GSM modifies the configuration parameters of the GSM instance.

• STATUS GSM returns the status of a GSM instance.

• SET INBOUND_CONNECT_LEVEL sets the INBOUND_CONNECT_LEVEL listener parameter.

• SET TRACE_LEVEL sets the trace level for the listener associated with the specified GSM instance.

• SET OUTBOUND_CONNECT_LEVEL sets the timeout value for the outbound connections for the listener associated with a specific GSM instance.

• SET LOG_LEVEL sets the log level for the listener associated with a specific GSM instance.