Fixes are available
APAR status
Closed as program error.
Error description
In case of chained aliases (duplicate aliases), as per the design, the expectation here is to describe/import the first alias (that has a direct reference to a table) and referenced table only. For example: Assume that we have chained aliases for a table test_sp exist like below : alias n -> ?>alias 3 -> alias 2 -> alias 1 -> test_sp With the fix in place (after removing duplicates), "alias 1" and the corresponding table (test_sp) will get described/imported.
Local fix
Problem summary
Duplicate assets are created when importing chained aliases from Oracle connector
Problem conclusion
In case of chained aliases (duplicate aliases), as per the design, the expectation here is to describe/import the first alias (that has a direct reference to a table) and referenced table only. For example: Assume that we have chained aliases for a table test_sp exist like below : alias n -> ?>alias 3 -> alias 2 -> alias 1 -> test_sp With the fix in place (after removing duplicates), alias 1 and the corresponding table (test_sp) will get described/imported.
Temporary fix
Comments
APAR Information
APAR number
JR61574
Reported component name
WIS DATASTAGE
Reported component ID
5724Q36DS
Reported release
B71
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-10-07
Closed date
2019-11-12
Last modified date
2019-11-12
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
RB71 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"InfoSphere DataStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"11.7","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
15 October 2021