A fix is available
APAR status
Closed as program error.
Error description
STP job using Teradata as database : The Stored Procedure acts on a table which is in a different database than the user logon database When this job aborts, sometimes the session is not getting closed.
Local fix
Problem summary
**************************************************************** USERS AFFECTED: All users of Stored Procedure stage connecting Teradata database. **************************************************************** PROBLEM DESCRIPTION: STP job triggering Teradata Stored Procedure is not closing the database session when the job aborts with some error within the stored procedure. The logon database and the table that the Stored Procedure acts on are in two different databases. **************************************************************** RECOMMENDATION: Apply this APAR. ****************************************************************
Problem conclusion
Disconnect is being made properly so that the session wouldn't be locked when a Stored Procedure raises some error.
Temporary fix
Comments
APAR Information
APAR number
JR35876
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-03-10
Closed date
2010-03-22
Last modified date
2010-03-22
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