This topic focuses on the required and recommended statements specific to Oracle CDC. To perform a database row test on the extraction map, you must define at least the ORACLEID and ORAD CAPI_CONNECTION statements.
CAPT_PATH
Required. The path to the directory on the Linux, UNIX, or Windows system that contains the following control files for CDC:
CCT file, which contains capture registrations
CDEP file, which contains application names for PowerCenter extractions that use ODBC extractions
CDCT file, which contains information about PowerExchange Logger for Linux, UNIX, and Windows log files
Default is the PowerExchange root installation directory.
Informatica recommends that you use a unique directory name to separate these CDC files from the PowerExchange code. This practice makes migrating to a another PowerExchange version easier.
CAPT_XTRA
Required. The path to the local directory on the Linux, UNIX, and Windows system that stores extraction maps for CDC.
Default is the PowerExchange root installation directory.
ORACLE_CAPTURE_TYPE
Recommended. Indicates whether you use PowerExchange Express CDC for Oracle or PowerExchange Oracle CDC with LogMiner. You cannot use both of these Oracle CDC solutions in the same PowerExchange installation. This setting must be consistent with the Oracle CAPI_CONNECTION type.
ORACLE_CAPTURE_TYPE={D|L}
D
. For PowerExchange Express for Oracle.
L
. For PowerExchange Oracle CDC with LogMiner.
No default value is provided.
In this scenario, enter
D
.
ORACLEID
Required. The Oracle source instance, database, and connection information that is used for CDC. This scenario uses only the required parameters because the capture process runs on the source system.
ORACLEID=(
collection_id
,
oracle_db
)
Required. A user-defined identifier for this ORACLEID statement. This value must match the ORACOLL parameter value in the ORAD CAPI_CONNECTION, the collection ID that you specified for the registration group, and the DBID value in the PowerExchange Logger pwxccl.cfg configuration file. Maximum length is eight characters.
This scenario uses a
collection_id
value of ORACOLID.
Required. The name of the Oracle database that contains the source tables that you registered for change data capture.
This scenario uses a name of ora1cdc.
ORACLE_UNHANDLED_NUMASCHAR
Optional. Controls whether or not capture registration processing for PowerExchange Express CDC or PowerExchange Oracle CDC with LogMiner sources handles NUMBER columns that have a precision greater than 28 or an undefined length as variable length strings, and handles FLOAT columns that have a precision greater than 15 as variable length strings.
ORACLE_UNHANDLED_NUMASCHAR={Y|
N
}
N.
PowerExchange uses its default processing of Oracle NUMBER data. If you have NUMBER columns that have a precision greater than 28 or an undefined length, or if you have FLOAT columns with a precision greater than 15, change data loss might occur.
Y.
PowerExchange handles NUMBER and FLOAT data in a manner that prevents data loss.
This scenario assumes that
N
is acceptable.
ORAD CAPI_CONNECTION
Required. A named set of parameters that the Consumer API (CAPI) uses to connect to the change stream and control PowerExchange Express CDC for Oracle processing for Oracle data sources. This scenario assumes that you use only the required parameters.
CAPI_CONNECTION=(NAME=
capi_connection_name
,TYPE=(ORAD,ORACOLL=
collection_id
,...)
)
NAME=
capi_connection_name
Required. A unique user-defined name for this CAPI_CONNECTION statement. Maximum length is eight alphanumeric characters.
TYPE=(ORAD,ORACOLL=
collection_id
,...)
Required. The type of CAPI_CONNECTION statement. For PowerExchange Express CDC for Oracle sources, this value must be
ORAD
.
In this parameter, you must include the
subparameter to specify the
user-defined
collection ID for the Oracle instance. This value must match the collection ID that is specified in the ORACLEID statement. This value should also match the value that is displayed in the
Instance
field for the registration group in the PowerExchange Navigator. This scenario uses a collection ID of ORACOLID.
Do not also specify ORCL CAPI_CONNECTION statements for PowerExchange Oracle CDC with LogMiner in the same DBMOVER configuration file.
CAPX CAPI_CONNECTION
Required for continuous extraction mode with the PowerExchange Logger. If you want the CAPI to use continuous extraction mode for the extraction of change data from PowerExchange Logger log files, you must define a CAPX CAPI_CONNECTION statement. This scenario uses only the required parameters.
CAPI_CONNECTION=(NAME=
capi_connection_name
,TYPE=(CAPX,DFLTINST=
instance_name
,...)
)
NAME=
capi_connection_name
Required. A unique user-defined name for this CAPI_CONNECTION statement. Maximum length is eight alphanumeric characters.
TYPE=(CAPX,DFLTINST=
instance_name
,...)
Required. Type of CAPI_CONNECTION statement. For continuous extraction mode with the PowerExchange Logger, this value must be
CAPX
.
In this parameter, you must include the
subparameter to specify the source instance identifier. For Oracle sources, enter the value that is displayed in the
Instance
field for the registration group in the PowerExchange Navigator. This value must also match the DBID value that is specified in the PowerExchange Logger configuration file. This scenario uses an
instance_name
of ORACOLID.
For additional information about these and other DBMOVER statements, see the
PowerExchange CDC Guide for Linux, UNIX, and Windows
and
PowerExchange Reference Manual
.
This scenario uses the following example statements:
ORACLEID=(ORACOLID,ora1cdc)
ORACLE_CAPTURE_TYPE=D
CAPI_CONNECTION=(NAME=CAPIXPRS,TYPE=(ORAD,ORACOLL=ORACOLID))
CAPI_CONNECTION=(NAME=ORACONT,TYPE=(CAPX,DFLTINST=ORACOLID))
ORACLE_UNHANDLED_NUMASCHAR=Y
/*
CAPT_PATH=//data/auser/pwx961/cdc_control_files
CAPT_XTRA=//data/auser/pwx961/extract_maps
