APAR status
Closed as program error.
Error description
Run the job sequentially to eliminate Datastage parallelism issues. After execution, review the query plans recorded by the netezza query log, it was noted here that the plans generated for the netezza connector stage statements do not contain a sort-node that would be expected to appear, having in mind that there appears one if you run the same query against netezza using aginity workbench. Is issue related to the use of named pipes for transferring the data from the netezza box to the DataStage-server? It appears that the netezza box ignores the order by clause when transferring data via named pipes.
Local fix
Problem summary
When running a Netezza Connector source context job using a user-defined select statement that contains and ORDER BY clause with the intention to return the results in a sorted way, the connector seems to ignore the ORDER BY clause and return the rows unsorted.
Problem conclusion
Apply the patch to resolve the issue.
Temporary fix
Comments
APAR Information
APAR number
JR41761
Reported component name
WIS QUALITYSTAG
Reported component ID
5724Q36QS
Reported release
870
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-01-26
Closed date
2012-02-20
Last modified date
2012-02-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
WIS QUALITYSTAG
Fixed component ID
5724Q36QS
Applicable component levels
R850 PSY
UP
R870 PSY
UP
[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSVSBF","label":"InfoSphere QualityStage"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.7"}]
Document Information
Modified date:
17 October 2021