Limitations and considerations

You should be aware of the following limitations and considerations when using an Oracle source.

Limitations and considerations for all data tasks

• When landing from a CHAR column, any trailing spaces will be truncated.
• Function-based indexes are not supported.
• If you are managing supplemental logging and you carry out transformations on any of the columns, you must be sure that supplemental logging is activated for all fields and columns.

• Capturing changes from a pluggable Oracle database (PDB) requires the source endpoint to connect to that PDB instance. Capturing changes from multiple PDB instances by connecting to the container database (CDB) is not supported.

• Deferred Constraints are not supported.
• Changes made by the Oracle DBMS_REDEFINITION package -( e.g. table metadata and the OBJECT_ID) - will not be captured by Qlik Cloud Data Integration.
• During Change Processing, columns without supplemental logging (e.g. LOB columns) that are not updated will be inserted as NULL in the Change Table.

• During Change Processing, batch updates to numeric columns defined as a Primary Key are not supported.

  Example of an unsupported UPDATE command:

  UPDATE tableX set ID=ID+1;

  Where tableX is the table name and ID is a numeric column defined as a Primary Key.

• Data in LONG and LONG RAW columns cannot exceed 64k. Any data that exceeds 64k will be truncated.
• Tables whose names contain apostrophes cannot be moved.
• Change Data Capture (CDC) is not supported from dynamic views.
• Index-organized tables with an overflow segment are not supported in Change Processing (CDC) tasks.
• Changes to Index-organized tables with key compression are not supported.
• Landing of tables or views of type BIN$ or DR$ is not supported.

• Oracle Flashback Database and restore points are not supported as the related operations affect the consistency of Oracle redo log files.

• When using the escape character '\' to search for a table in the Select Tables window, you need to write '\\' (2 backslashes) instead of '\' (1 backslash). For example, to search for all tables that include '_', you would need to enter %\\_%.
Information note
• When adding a pattern for include or exclude, 2 backslashes are not required (for example, *%\_%).

• When using '$’ for the escape character, there is no limitation.
• When using Oracle 19.0 as the source, the following Oracle features are not supported:
  • Data-guard DML redirect
  • Schema-only Oracle accounts

• When landing from Oracle 21c, the following limitations apply:

  • Immutable tables are not supported

  • Blockchain tables are not supported

• Object names exceeding 30 characters are not supported. Consequently, tables with names exceeding 30 characters or tables containing column names exceeding 30 characters will not be moved.

• Landing from Application Containers is not supported.

• Cascading standby database is not supported.

• Failover configuration is supported only when changes are captured from the primary node.

Limitations and considerations for replication tasks only

• The rename table <table name> to <new table name> syntax is supported by Qlik Cloud Data Integration when using Oracle version 11 and higher.
• Data changes resulting from partition/sub-partition operations (ADD, DROP, EXCHANGE and TRUNCATE) will not be moved and may cause the following errors:
  • For ADD operations, updates and deletes on the added data may return a "0 rows affected" warning.
  • For DROP and TRUNCATE operations, new inserts may result in "duplicates" errors.

  • For EXCHANGE operations, both a "0 rows affected" warning and "duplicates" errors may be encountered.

  To Land changes resulting from partition/sub-partition operations, you need to reload the tables in question. When adding a new empty partition, operations on the newly added partition will be moved to the target as normal.

• When Replicate limited LOB columns (KB) is enabled, empty BLOB/CLOB columns on the Oracle source are moved as NULL values. For more information on Limited-size LOB mode, see Metadata.

• The Allow unlimited LOB size option is not supported when loading LONG and LONG RAW columns into Oracle target.

  Workaround: Use the Replicate limited LOB columns (KB) option instead.

• Table clusters are not supported.
• Only table-level SHRINK SPACE operations are supported. These include the full table, partitions, and sub-partitions.
• Implementing online redo logs on raw devices is not supported.
• The following Oracle features are not supported when using Amazon RDS for Oracle:
  • ASM
  • TDE

• Direct-load INSERT procedure with the parallel execution option is not supported in the following cases:

  • Uncompressed tables with more than 255 columns

  • Row size exceeds 8K

  • Exadata HCC tables

Unsupported data types

The following data types are not supported:

• BFILE
• ROWID
• REF
• UROWID
• ANYDATA
• SDO_GEOMETRY
• User-defined data types