IBM Support

JR34554: JOB, DATASET ---> TRANSFORMER ---> NETEZZAEE, ABORTS WITH ERRORS.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • [Problem]
    Job, DataSet ---> Transformer ---> NetezzaEE, aborts with the
    following errors: (please see the detail in the job log, I
    uploaded it)
    
      Item #: 57
       Event ID: 402
       Timestamp: 2009-09-18 20:05:37
       Type: Information
       Username: S-SOAP-T-DOM|etl_ibm
       Message ID: IIS-DSEE-TFSU-00016
       Message: main_program: There are datasets in this step. 3
    datasets:
    ds0: {F:/etl_ibm_div/Datasets/TMT/W_PipeLine_Logistic_001.dst
          [pp] eSame=>eCollectAny
          op0[2p] (parallel
    APT_CombinedOperatorController:Dst_PipeLine_Logistic)}
    ds1: {op0[2p] (parallel
    APT_CombinedOperatorController:APT_TransformOperatorImplV0S226_V
    _TMP_PineLine_Logistic_TMT_020_L_Trf_UpdateYard in
    Trf_UpdateYard)
          [pp] eSame=>eCollectAny
          op1[2p] (parallel APT_DBExportOperator in
    Db_N_S_PIPELINE_LOGISTIC)}
    ds2: {op1[2p] (parallel APT_DBExportOperator in
    Db_N_S_PIPELINE_LOGISTIC)
          eAny=>eCollectAny
          op2[2p] (parallel APT_NZWriteSubOperator in
    Db_N_S_PIPELINE_LOGISTIC)}
    this has 3 operators:
    op0[2p] {(parallel APT_CombinedOperatorController:
          (Dst_PipeLine_Logistic)
    
    (APT_TransformOperatorImplV0S226_V_TMP_PineLine_Logistic_TMT_020
    _L_Trf_UpdateYard in Trf_UpdateYard)
        ) on Node (
          node1[op0,p0]
          node2[op0,p1]
        )}
    op1[2p] {(parallel APT_DBExportOperator in
    Db_N_S_PIPELINE_LOGISTIC)
        on Node (
          node1[op1,p0]
          node2[op1,p1]
        )}
    op2[2p] {(parallel APT_NZWriteSubOperator in
    Db_N_S_PIPELINE_LOGISTIC)
        on Node (
          node1[op2,p0]
          node2[op2,p1]
        )}
    execution is: 6 processes places 2 nodes.
    
       Item #: 58
       Event ID: 403
       Timestamp: 2009-09-18 20:05:37
       Type: Warning
       Username: S-SOAP-T-DOM|etl_ibm
       Message ID: IIS-DSEE-TFPM-00307
       Message: main_program: broadcastStepIR: Warning: Failed to
    delete score file of /F=/etl_ibm/temp/APTcs1814899e26fa9. errno
    = 26
    
       Item #: 59
       Event ID: 404
       Timestamp: 2009-09-18 20:05:37
       Type: Fatal
       Username: S-SOAP-T-DOM|etl_ibm
       Message ID: IIS-DSEE-TFPM-00281
       Message: Db_N_S_PIPELINE_LOGISTIC,0: Fatal Error: Caught
    unknown exception in parallel process: terminating
    
       Item #: 60
       Event ID: 405
       Timestamp: 2009-09-18 20:05:37
       Type: Fatal
       Username: S-SOAP-T-DOM|etl_ibm
       Message ID: IIS-DSEE-TFPM-00192
       Message: node_node1: Player 1 terminated unexpectedly.
    
       Item #: 61
       Event ID: 406
       Timestamp: 2009-09-18 20:05:37
       Type: Fatal
       Username: S-SOAP-T-DOM|etl_ibm
       Message ID: IIS-DSEE-TFPM-00338
       Message: main_program: APT_PMsectionLeader(1, node1)?Player
    1 - terminated unexpectedly. Status 1.
    APT_PMsectionLeader(1, node1)?Player 2 - terminated
    unexpectedly Status 1.
    
       Item #: 62
       Event ID: 407
       Timestamp: 2009-09-18 20:05:37
       Type: Fatal
       Username: S-SOAP-T-DOM|etl_ibm
       Message ID: IIS-DSEE-TFPM-00281
       Message: node_node1: Fatal Error: Caught unknown exception in
    parallel process: terminating
    
       Item #: 63
       Event ID: 408
       Timestamp: 2009-09-18 20:05:42
       Type: Fatal
       Username: S-SOAP-T-DOM|etl_ibm
       Message ID: IIS-DSEE-TFPM-00330
       Message: main_program: Section leader on Node node1
    terminated unexpectedly.
    
       Item #: 64
       Event ID: 409
       Timestamp: 2009-09-18 20:05:42
       Type: Fatal
       Username: S-SOAP-T-DOM|etl_ibm
       Message ID: IIS-DSEE-TFSC-00011
       Message: main_program: Execution of steps finished. Status =
    FAILED.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    IS 8.1 Windows
    ****************************************************************
    PROBLEM DESCRIPTION:
    Issue came up with Transformer stage .When used along with
    Netezza Stage the issue surfaced up in the customer job.
    ****************************************************************
    RECOMMENDATION:
    PX Engine patch provided.
    JR34082_PXEngine_Windows_81_V2
    
    Cumulative Netezza EE Stage patch (no fix done for this issue in
    Netezza EE Stage code) provided.
    
    patch_JR34554_server_windows_8100
    ****************************************************************
    

Problem conclusion

  • PX Engine fix done for Transformer.
    No fix done in Netezza EE Stage. So a cumulative Netezza EE
    Stage provided with all past fixes done.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR34554

  • Reported component name

    WIS DATASTAGE

  • Reported component ID

    5724Q36DS

  • Reported release

    810

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-10-15

  • Closed date

    2010-02-03

  • Last modified date

    2010-02-03

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • PXENGINE NETEZZA
    

Fix information

  • Fixed component name

    WIS DATASTAGE

  • Fixed component ID

    5724Q36DS

Applicable component levels

  • R810 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSVSEF","label":"IBM InfoSphere DataStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
03 February 2010