Skip to main content

Db2 for z/OS troubleshooting

Scenario

Solution

Striim Agent for Db2 for z/OS pipeline and Striim application are running but no events are appearing in the output of the external source.

Check the Striim Agent for Db2 for z/OS dashboard and the Striim Agent for Db2 for z/OS Agent log.

Striim Agent for Db2 for z/OS is having connection failures.

Check the Striim Agent for Db2 for z/OS Agent log.

Striim Agent for Db2 for z/OS pipeline does not work after stop and restart.

Rename the Striim Agent for Db2 for z/OS process and delete the files in the RDRS/tmp directory for the old process.

Events are not appearing in the Kafka topic.

Verify that the TOPIC property in the Striim Agent for Db2 for z/OS configuration file matches the fully qualified Kafka topic name created by the Striim application. Ensure the SSL properties are configured correctly in the configuration file.

Striim Agent for Db2 for z/OS cannot connect to Kafka or the schema registry.

Verify that the IP address of the Striim Agent for Db2 for z/OS machine is allow-listed in the Striim Cloud console on the Kafka for Stream Persistence tab. Check network connectivity using telnet to the Kafka Bootstrap Server and Schema Registry URL endpoints.

No data is received in the Striim application.

Check the Striim Agent for Db2 for z/OS tcAgent.log file for errors. Verify that the source tables in Db2 have primary keys and data capture enabled.

Certificate errors when connecting to Kafka.

Verify that the ca.crt, client.crt, and client.key files are correctly referenced in the Striim Agent for Db2 for z/OS configuration file. If the certificates have expired, download renewed certificates from the Striim Cloud console. If the ca.crt file was lost, contact Striim support.