Known issues

Database ingestion and replication jobs that use the Log-based CDC method and have an Oracle source with only LOB columns selected and no primary key do not create subtasks on the tables. As a result, the jobs cannot capture change data from the tables. Messages such as the following are written to the log:

Workaround: In the task, select some non-LOB source columns, in addition to the LOB columns, for replication if you want to continue using the table without a primary key.. (July 2024)

Database ingestion and replication tasks that that are configured to not include LOBs in capture processing but have source tables with unsupported Oracle BFILE or LOB columns, incorrectly add table-level Exclude rules that specify conditions with the unsupported column names on the Source page of the task wizard.

Workaround: None. (July 2024)

Database ingestion and replication jobs that have a Db2 for i source and Amazon Aurora PosgreSQL target might fail when copying data trom the local .csv file to the target table or to the LOG table (for an incremental load) if the default Secure Agent installation directory path contains spaces. This problem is caused by a known Progress JDBC driver for PostgreSQL issue. The driver does not preserve spaces in the directory path, causing the database ingestion job to not be able to find the .csv file.

Workaround: Configure the Secure Agent installation directory path without spaces. (February 2024)

Database ingestion and replication jobs that have an SAP HANA source table with a multiple-column primary key and that use a custom data-type mapping to map a source TIMESTAMP column to a Snowflake target VARCHAR column replicate data to the target incorrectly, which results in invalid data in the target column.

Workaround: None. (November 2023)

Database ingestion and replication incremental load jobs that have an SAP HANA Cloud source with a DECIMAL column that has no precision fail with the following error message:

Workaround: None. (August 2023)

The Oracle Database Ingestion connection properties page includes no property for entering JDBC connection properties, such as EncryptionLevel, when they're needed.

Workaround: In the Service Name field, you can add JDBC connection properties after the Oracle SID value, using a semicolon (;) as the separator. (April 2023 release)

Database ingestion and replication jobs with a SAP HANA source might replicate data from REAL columns of 16 or more significant digits with a loss of precision on the target, causing data corruption.

Workaround: None. (April 2023 release)

If you create custom data type mappings for Oracle source binary_double and binary_float columns in a database ingestion task, the custom mappings are ignored. Instead, the target table is generated using the default mappings of binary_double > float and binary_float > real. When the database ingestion and replication job runs, nulls are written to the target float and real columns.

Workaround: None. (February 2023 release)

For database ingestion and replication tasks that include custom data type mapping rules, the Metadata Manager log incorrectly reports nullable columns as NOT NULL and reports not-nullable columns as NULL. However, the target columns corresponding to the mapped source columns are generated with the correct nullability.

Workaround: None. (February 2023 release)

If database ingestion and replication incremental load or combined initial and incremental load jobs replicate LOB source data to an Amazon S3, Google Cloud Storage, or Microsoft Azure Data Lake Storage Gen2 target and use the CSV format for the target output file, the LOB data appears as empty strings in the target file.

Workaround: None. (November 2022 release)

Database ingestion and replication initial load jobs that use the Informatica-supplied Progress DataDirect JDBC driver for SQL Server to connect to a SQL Server source fail.

Workaround: Download the Microsoft JDBC Driver for SQL Server. (September 2022 release)

Oracle source columns with the TIMESTAMP WITH TIME ZONE data type are supported only for initial load jobs. (July 2022 release)

Database ingestion and replication incremental load or combined initial and incremental load jobs that have a SQL Server source with binary, decimal, or datetimeoffset columns and an Oracle target fail if a DML update operation is followed by an insert.

Workaround: None. (May 2022 release)

The Resume With Options command is not available for jobs in the Running with Warning state if one or more of the tables were excluded from replication because of the Stop Table schema drift option.

Workaround: Stop the job and then click Resume with Options in the Actions menu to resume the job. (July 2020 release)

Although the Amazon S3 connection properties allow users to specify an IAM role, you cannot use temporary security credentials generated by the AssumeRole method of the AWS Security Token Service API to authorize user access to AWS Amazon S3 resources.

Workaround: None. (April 2020 release)