A fix is available
APAR status
Closed as program error.
Error description
Oracle EE Lookup stage not failing for fetch errors and not printing query for this fatal message. When Lookup is set to CONTINUE, lookup stage should still fail for fatal fetch errors and not when 0 rows successfully returned from fetch.
Local fix
This fix is included in 8.0.1 fixpack 3
Problem summary
**************************************************************** USERS AFFECTED: Oracle EE Lookup **************************************************************** PROBLEM DESCRIPTION: Oracle EE Lookup stage not aborting for fatal fetch errors. When Lookup stage is set to CONTINUE, the Lookup stage should still abort for fatal errors and not for 0 rows successfully fetched. **************************************************************** RECOMMENDATION: Apply this patch to obtain the fix. ****************************************************************
Problem conclusion
Oracle EE Lookup stage will now abort for failures during fetch if Lookup set to CONTINUE mode. If Lookup is set to CONTINUE and 0 rows are fetched job will continue.
Temporary fix
Comments
APAR Information
APAR number
JR35531
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
810
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-02-02
Closed date
2010-02-05
Last modified date
2010-12-09
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WIS DATASTAGE
Fixed component ID
5724Q36DS
Applicable component levels
R810 PSN
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
12 October 2021