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 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. Recovery checkpoint data will be lost.

What to do if dropping a Db2 for z/OS application fails

When you issue a DROP APPLICATION for a Db2 for z/OS application, if there are any issues that prevent objects in Db2 from being dropped (for example, the Striim Agent for Db2 for z/OS is waiting for a response from a locked-up or unresponsive Db2 mainframe subsystem for a process that Striim has already stopped), the drop will fail, agent still believes the process/source/target components are active on its side. To recover from this state:

  1. Force drop the application:

    DROP APPLICATION <app_name> FORCE;

    This clears the application, source, and target metadata from Striim's repository, even though the Striim Agent for Db2 for z/OS still holds a reference to the orphaned process.

  2. Manually clean up the orphaned process/components on the Striim Agent for Db2 for z/OS's Linux server.

    Striim's DROP ... FORCE clears only Striim's own metadata and cannot reach into the Striim Agent for Db2 for z/OS's internal process tracking: from the agent's point of view, the source/target/process components still exist. The orphaned process must be removed directly. Without this step, the same process reference may resurface and cause conflicts on subsequent redeploys of an app using the same name.

    1. Use ps -ef and look for a process that is named <NAMESPACE>.<COMPONENT_NAME>_P.

    2. Note the process ID (PID) and attempt kill <PID>. If that does not work, try kill -9 <PID>.

    3. Optionally, if you expect to repeat setup of the Db2 for z/OS external source component from scratch, check the <RDRS_HOME_DIRECTORY>/tmp directory for <NAMESPACE>.<COMPONENT_NAME>_P files and delete them.

  3. Optionally, recreate and redeploy the application.