APAR status
Closed as program error.
Error description
Bind variables should always be used when firing database queries. The way the Oracle shared pool operates is predicated on developers using bind variables in most cases. However it seems like many core product queries, some that get fired multiple times are not using bind variable.
Local fix
Circumvention: None
Problem summary
Users Affected: All Problem Description: Bind variables not used in SFG code is causing reparse of the same SQL and Oracle memory overhead. Platforms Affected: All
Problem conclusion
Resolution Summary: Used bind variables for some of most frequently used SQL queries in Sterling File Gateway. Delivered in: 5020500_3
Temporary fix
Comments
APAR Information
APAR number
IT05669
Reported component name
STR B2B INTEGRA
Reported component ID
5725D0600
Reported release
524
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2014-11-19
Closed date
2015-03-18
Last modified date
2015-03-20
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
STR B2B INTEGRA
Fixed component ID
5725D0600
Applicable component levels
R525 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS3JSW","label":"IBM Sterling B2B Integrator"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2.4","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Document Information
Modified date:
20 March 2015