When you use an SAP ECC source with an SAP Mass Ingestion connector for the first time, perform the following steps before you configure an

application ingestion and replication

task for the source:

You must install the latest version of the SAP transport file on the SAP machine you want to access.
For more information about accessing the SAP transport file, contact Informatica Global Customer Support.
The following table describes the transport on the SAP development system:
Data and Cofile Names	Data and Cofile Names	Transport Request	Functionality
R<number>.EP6 K<number>.EP6	Required	EP6K<number>	Install the transports to read from SAP transparent tables, cluster tables, pool tables, and views.
For more information about installing the transport files, see Installing transport files.
Verify that the appropriate SAP Notes are available in the SAP server. For more information, see the
SAP Connector Guide
.
Download the SAP Java Connector (SAP JCo) library from the SAP website, and perform the followintg tasks:
Copy the native and JAR files from the downloaded SAP JCo library to the following directory:
<Secure_Agent>\ext\connectors\thirdparty\informatica.sapami\
Restart the Secure Agent.

To use the SAP ECC with the underlying Oracle source database in

application ingestion and replication

tasks, define the following system environment variables on the Linux or Windows system where the Secure Agent runs:

ORACLE_HOME environment variable. Points to the Oracle client installation directory, one level up from the bin directory on Windows or lib directory on Linux. This environment variable is not required. However, if you do not define it, you'll need to specify the full Oracle client installation path when you define other environment variables or Secure Agent properties that specify a path to a subdirectory.
TNS_ADMIN environment variable. If you specify a TNS name in the
Database Connect String
property in the Oracle database properties in the SAP Mass Ingestion connection, use this environment variable to point to the directory location of the tsnnames.ora file when the file is not in the default $ORACLE_HOME/network/admin directory. The tnsnames.ora file, along with the Oracle Call Interface (OCI), is used to communicate with the Oracle source database.

Make sure the

Application Ingestion and Replication

user has the Oracle privileges that are required for the

application ingestion and replication

load type to be performed. For more information, see Oracle privileges.

If you use an Amazon RDS for Oracle, make sure the

Application Ingestion and Replication

user has the required privileges. For more information, see Oracle privileges for Amazon RDS for Oracle.

If you use Oracle 11.2.04, set the Oracle COMPATIBLE initialization parameter to 11.2.04 to ensure that Oracle has all of the most current redo logs fixes for that release.

Ensure that the Oracle Database Client or Instant Client is installed and configured on the Secure Agent server for the Secure Agent to communicate with Oracle. If you do not already have an Oracle client installed, you can download a client and access installation information from the Oracle web site, or ask your Oracle DBA to download and configure an Oracle client.

For incremental load or combined initial and incremental load operations that use log-based CDC, perform the following prerequisite tasks in Oracle:

Enable ARCHIVELOG mode for the Oracle database. If the database is not in an Amazon RDS environment, issue the following SQL statements:
SHUTDOWN IMMEDIATE;
STARTUP MOUNT;
ALTER DATABASE ARCHIVELOG;
ALTER DATABASE OPEN;
SHUTDOWN IMMEDIATE;
STARTUP;
Enable Oracle minimal global supplemental logging on the source database.
For incremental load operations with the source,
Application Ingestion and Replication
provides alternative capture methods for capturing change data from the source and applying the data to a target.
Application Ingestion and Replication
reads data changes from Oracle redo logs. This method requires users to have extended privileges.
Because
Application Ingestion and Replication
expects each source table row to be unique, Informatica recommends that each source table have a primary key.
Application Ingestion and Replication
does not honor unique indexes in place of a primary key. If no primary key is specified,
Application Ingestion and Replication
treats all columns as if they are part of the primary key.

Your jobs must be able to access transaction data in Oracle online and archive redo logs. For more information, see Oracle archive log retention considerations.

Application ingestion and replication

jobs that use log-based CDC require read access to Oracle online and archive redo logs to read incremental change data. If the redo logs are remote from the on-premises system where the Secure Agent runs, make sure that read access to the logs is provided, for example, by using Oracle Automatic Storage Management (ASM), mounting the logs to a network file system (NFS).

To access the redo logs by using Oracle directory objects with BFILEs, see Configuring BFILE access to Oracle redo logs in the Oracle file system.

When the Oracle database for SAP ECC source contains CHAR or VARCHAR columns contain nulls, the

application ingestion and replication

job does not delimit the null values with double-quotation (") marks or any other delimiter when writing data to a Amazon S3, Flat File, Microsoft Azure Data Lake, or Microsoft Azure Synapse Analytics target.

Application Ingestion and Replication

can process data across a RESETLOGS boundary. To avoid the source and targets becoming out of sync, Informatica recommends that you stop capture processing before performing a RESETLOGS and then restart capture processing after the RESETLOGS event. Otherwise, the capture process might send data to the target that is subsequently reverted by the RESETLOGS event, causing the source and target to become out of sync.

Alternative strategies for accessing the Oracle redo logs are available.

If an

application ingestion and replication

incremental load or combined initial and incremental load task contains a source table name or one or more column names that are longer than 30 characters, Oracle suppresses supplemental logging for the entire table, including primary keys and foreign keys. As a result, most operations on the table fail. This problem is caused by an Oracle restriction. In this situation, exclude the table from capture processing or rename the long table and column names to names of 30 characters or less.

Do not use custom data type mapping rules to map a RAW column from the source to a target CHAR or VARCHAR column. Otherwise, the deployment of the

application ingestion and replication

task might fail.

Application Ingestion and Replication

does not support invisible columns in the source columns, regardless of the target type. For these columns,

application ingestion and replication

incremental load jobs and combined initial and incremental load jobs propagate nulls to the corresponding target columns.

Application ingestion and replication

combined initial and incremental load jobs that have SAP ECC sources with Oracle database can read changes from copies of the archive redo logs. You must set the

Reader Mode

property to ARCHIVECOPY in the SAP Mass Ingestion connection properties for the Oracle database and also set the source custom property pwx.cdcreader.oracle.reader.additional with the dir and file parameters. The dir parameter points to the name of the base directory that the CDC log reader scans for the archive log copies, and the file parameter specifies a mask that is used to filter the log copies.

Application Ingestion and Replication

does not propagate fields of the following obsolete SAP data types:

D16S
D34S
PREC
VARC

Additionally,

application ingestion and replication

jobs do not propagate fields of the RSTR data type.

An SAP ECC source with an SAP Mass Ingestion connector doesn't support schema drift.