A fix is available
APAR status
Closed as program error.
Error description
For large databases detecting lineage for database views can cause that max objects in memory limit is reached. It is caused by too many objects being loaded in a query.
Local fix
Problem summary
********************************************* APAR Users Affected: ********************************************* All users running lineage for database views ********************************************* APAR Problem Description: ********************************************* Due to inefficient query when database view was processed during lineage calculation, all the objects from the database where view existed were loaded. The new query changes this behavior and loads only required objects thus reducing memory footprint and improving performance of calculating lineage for database view ********************************************* APAR Recommendation: ********************************************* Apply the fix for JR60110 *********************************************
Problem conclusion
Apply the fix for JR60110
Temporary fix
Comments
APAR Information
APAR number
JR60110
Reported component name
INFO SRVR PLATF
Reported component ID
5724Q3612
Reported release
B50
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2018-10-07
Closed date
2018-11-15
Last modified date
2018-11-15
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
INFO SRVR PLATF
Fixed component ID
5724Q3612
Applicable component levels
RB50 PSY
UP
RB70 PSY
UP
[{"Line of Business":{"code":"LOB10","label":"Data and AI"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSZJPZ","label":"InfoSphere Information Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.5"}]
Document Information
Modified date:
02 September 2021