Fixes are available
Closed as fixed if next.
If you use a DB2 database as the recovery database for an InfoSphere Streams instance and a DB2 database error occurs while InfoSphere Streams operations are in progress, the operations fail. After the cause of the DB2 database error is fixed and the InfoSphere Streams services are back to normal, however, the state of certain services might be inconsistent with the state of the service in the recovery database. This situation does not affect the InfoSphere Streams instance immediately, but might introduce problems when the services are later restarted. For example, this problem can occur with the Streams Application Manager (SAM) service. When this happens, you might see some unexpected data (such as an already canceled job showing up again) or state information (such as a PE going from stopped state into running).
To work around the problem, immediately restart the InfoSphere Streams services after DB2 database errors are fixed.
Users Affected: Users who use a DB2 database as the recovery database for InfoSphere Streams. Problem Description: See Error Description. Problem Conclusion: This problem is fixed in Version 3.1 Fix Pack 1 and later fix packs.
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels