Skip to main content

Db2 for z/OS operational considerations

Limitations for Db2 for z/OS

  • Tables without primary keys cannot be read.

  • Tables with names beginning with DB2_GENERATED_ cannot be read.

  • Primary key updates are not supported if the table contains an LOB or XML column. The application may halt or terminate, and data may be corrupted. However, this limitation does not apply when using a PartialRecordPolicy, which skips LOB/XML fields during processing.

  • Dropping a Striim application containing a Kafka-persisted stream being written to by Striim Agent for Db2 for z/OS will delete the associated Kafka topic. Before dropping such an application, stop the Striim Agent for Db2 for z/OS pipeline and anything else that is writing to the associated Kafka topic.

Handling schema evolution for Db2 for z/OS

Schema evolution must be handled manually. See Handling planned DDL changes.

Reading the Striim Agent for Db2 for z/OS Agent log

The log file is in the Striim Agent for Db2 for z/OS directory at <Striim Agent for Db2 for z/OS directory>/log/tcAgent.log.

Backing up Striim Agent for Db2 for z/OS

To be able to restore Striim Agent for Db2 for z/OS in the event of a failure, back up the Striim Agent for Db2 for z/OS directory and the PostgreSQL or Oracle repository.