SOURCEDB

Valid For

Manager, Extract, DEFGEN

Description

Use the SOURCEDB parameter for databases or data sets that require a data source name or identifier to be specified explicitly as part of the connection information. This option is required to identify one of the following:

  • The source login database for heterogenous databases.

  • The data source name (DSN) for supported databases that use ODBC

  • The source SQL/MX catalog, valid when Extract will process data from only one catalog in the SQL/MX database

  • The default DB2 for i database.

Tables specified in TABLE statements that follow SOURCEDB are assumed to be from the specified data source.

You might need to use the USERID or USERIDALIAS parameter in the SOURCEDB parameter statement, depending on the authentication that is required for the data source.

For databases that allow authentication at the operating-system level, you can specify SOURCEDB without USERID or USERIDALIAS.

For Manager, use SOURCEDB only when using Oracle GoldenGate parameters that cause Manager to interact with a source database, such as PURGEOLDEXTRACTS. You can use SOURCEDB for Manager on the source or target database.

For DB2 LUW, the SOURCEDB statement must refer to the database by its real name, rather than by any alias.

See USERID or USERIDALIAS for more information.

Default

None

Syntax

SOURCEDB data_source[, SESSIONCHARSET character_set]
data_source

The name of the database, catalog, or data source name as applicable for the database.

For MySQL databases, you can use the format of SOURCEDB database_name@host_name to avoid connection issues caused by the incorrect configuration of localhost in the local hosts file. If running MySQL on a port other than the default of 3306, you must specify the port number in the connect string: SOURCEDB database_name@host_name:port.

SESSIONCHARSET character_set

Supports Sybase, Teradata and MySQL. Sets the database session character set for the process login session. This parameter overrides any SESSIONCHARSET that is specified in the GLOBALS file.

To display the language information in the process report file when using this option for a Sybase database, make certain that locale.dat is set properly in the Sybase installation directory. If the character set is not found in the supported Sybase database character set, then it is validated against the Oracle GoldenGate supported character set list. The character-set information is displayed with the LOCALE INFORMATION entry in the report output.

Examples

Example 1   

This example shows SOURCEDB without the USERIDALIAS parameter.

SOURCEDB mydb
Example 2   

This example shows SOURCEDB with the USERIDALIAS parameter.

SOURCEDB mydb, USERIDALIAS tiger1