Information Server DataStage operator logic error

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
arun123
Participant
Posts: 3
Joined: Mon Sep 21, 2015 5:45 am

Information Server DataStage operator logic error

Post by arun123 »

Hi ,

I have designed a job for ABAP stage in DataStage .
During the job execution i am facing operator logic error saying like "ABAP_Input,0: Failure during execution of operator logic."

For more error info ,
Here i am sharing detail job log.


Item #: 25
Event ID: 971
Timestamp: 2015-09-07 00:29:05
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFOR-00001
Message: ABAP_Input,0: Failure during execution of operator logic.

Item #: 26
Event ID: 972
Timestamp: 2015-09-07 00:29:05
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFOR-00094
Message: ABAP_Input,0: Output 0 produced 0 records.

Item #: 27
Event ID: 973
Timestamp: 2015-09-07 00:29:05
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSTAGE-ABAP-E-00206
Message: ABAP_Input,0: Fatal Error: Fatal: RFC server function 'rfc_getline' failed, returned '
RfcWaitForRequest, RFC_ERROR_INFO_EX: RFC_ERROR_COMMUNICATION.
CPIC-CALL: 'SAP_CMACCPTP : rc=20
LOCATION CPIC (TCP/IP) on local host Sap124
ERROR connection to partner '192.168.168.158:3310' broken
TIME Mon Sep 07 00:29:04 2015
RELEASE 720
COMPONENT NI (network interface)
VERSION 40
RC -6
MODULE nixxi.cpp
LINE 5082
DETAIL NiIRead: P=192.168.168.158:3310; L=192.168.0.124:49448
SYSTEM CALL recv
ERRNO 10054
ERRNO TEXT WSAECONNRESET: Connection reset by peer
COUNTER 2
'

Item #: 28
Event ID: 974
Timestamp: 2015-09-07 00:29:05
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFPM-00192
Message: node_node1: Player 1 terminated unexpectedly.

Item #: 29
Event ID: 975
Timestamp: 2015-09-07 00:29:05
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFPM-00338
Message: main_program: APT_PMsectionLeader(1, node1), player 1 - Unexpected exit status 1.

Item #: 30
Event ID: 976
Timestamp: 2015-09-07 00:29:05
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFIO-00223
Message: Sequential_File_op,0: APT_IOPort::readBlkVirt: read for block header, partition 0, [fd 4], returned -1 with errno 10,054 (Unknown error)

Item #: 31
Event ID: 977
Timestamp: 2015-09-07 00:29:10
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TOIX-00059
Message: Sequential_File_op,0: Export complete; 0 records exported successfully, 0 rejected.

Item #: 32
Event ID: 978
Timestamp: 2015-09-07 00:29:10
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFSC-00011
Message: main_program: Step execution finished with status = FAILED.

Item #: 33
Event ID: 979
Timestamp: 2015-09-07 00:29:10
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TCOS-00026
Message: main_program: Startup time, 0:07; production run time, 1:58:33.

Item #: 34
Event ID: 980
Timestamp: 2015-09-07 00:29:11
Type: Control
User Name: SAP124|dsadm
Message Id: IIS-DSTAGE-RUN-I-0075
Message: Job sap_pg1 aborted.

Need help to resolve the issue .

Thanks in advance .

Regards,
Arun
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Welcome aboard.

Tip #1 is to read the error messages in detail.

In this case the really important piece of information is ERROR connection to partner '192.168.168.158:3310' broken

You need to work out, possibly involving your network team, why the connection got broken.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
arun123
Participant
Posts: 3
Joined: Mon Sep 21, 2015 5:45 am

Post by arun123 »

Hi Ray

Thanks for the response .

I did few changes in the Datastage ABAP job to eliminate RFC connection issue . Still the error is same "OPERATOR LOGIC error " .


After gone through the JOB in details,

I assume the Program generated by Datastage ABAP job is causing the error .


Detail job log -


Item #: 22
Event ID: 1384
Timestamp: 2015-09-22 21:50:04
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSTAGE-ABAP-I-00191
Message: ABAP_Input,0: Info: sap_pg1.ABAP_Input: Run program: ZTEST_PG5

Item #: 23
Event ID: 1385
Timestamp: 2015-09-22 21:50:04
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSTAGE-ABAP-I-00322
Message: ABAP_Input,0: Info: sap_pg1.ABAP_Input: RFC data transfer in progress on Gateway 192.168.168.158, Program ID: Z1441013941, Gateway Service sapgw10

Item #: 24
Event ID: 1386
Timestamp: 2015-09-22 21:50:04
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFOP-00074
Message: ABAP_Input,0: Logging delayed metadata.

Item #: 25
Event ID: 1387
Timestamp: 2015-09-22 22:00:04
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFOP-00073
Message: ABAP_Input,0: Requesting delayed metadata.

Item #: 26
Event ID: 1388
Timestamp: 2015-09-22 22:03:18
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSTAGE-ABAP-I-00727
Message: ABAP_Input,0: Info: sap_pg1.ABAP_Input: New parallel engine functions detected.

Item #: 27
Event ID: 1389
Timestamp: 2015-09-22 22:03:18
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFOR-00001
Message: ABAP_Input,0: Failure during execution of operator logic.

Item #: 28
Event ID: 1390
Timestamp: 2015-09-22 22:03:18
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFOR-00094
Message: ABAP_Input,0: Output 0 produced 0 records.

Item #: 29
Event ID: 1391
Timestamp: 2015-09-22 22:03:18
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSTAGE-ABAP-E-00746
Message: ABAP_Input,0: Fatal Error: Fatal: ABAP background job time-out occurred as defined using BG_JOB_TIMEOUT property.

Item #: 30
Event ID: 1392
Timestamp: 2015-09-22 22:03:18
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFPM-00192
Message: node_node1: Player 1 terminated unexpectedly.

Item #: 31
Event ID: 1393
Timestamp: 2015-09-22 22:03:18
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFPM-00338
Message: main_program: APT_PMsectionLeader(1, node1), player 1 - Unexpected exit status 1.

Item #: 32
Event ID: 1394
Timestamp: 2015-09-22 22:03:18
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFIO-00223
Message: Sequential_File_op,0: APT_IOPort::readBlkVirt: read for block header, partition 0, [fd 4], returned -1 with errno 10,054 (Unknown error)

Item #: 33
Event ID: 1395
Timestamp: 2015-09-22 22:03:23
Type: Info
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TOIX-00059
Message: Sequential_File_op,0: Export complete; 0 records exported successfully, 0 rejected.

Item #: 34
Event ID: 1396
Timestamp: 2015-09-22 22:03:23
Type: Fatal
User Name: SAP124|dsadm
Message Id: IIS-DSEE-TFSC-00011
Message: main_program: Step execution finished with status = FAILED.


Any input will be helpful.


Best Regards,
Arun
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Again, read your errors carefully.

This time the main problem seems to be ABAP background job time-out occurred as defined using BG_JOB_TIMEOUT property.

Work with your SAP administrators to verify and probably suggest a better value for this property.
Last edited by ray.wurlod on Wed Sep 23, 2015 1:05 am, edited 1 time in total.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

You might also consult the Message Reference Guide to see whether IIS-DSTAGE-ABAP-E-00746 is there. I'm not currently at a location where version 11.3 manuals are available.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
arun123
Participant
Posts: 3
Joined: Mon Sep 21, 2015 5:45 am

Post by arun123 »

I have come across this error before .

As the JOB execution time is exceeding the time limit , it gives
BG_JOB_TIMEOUT error .

To resolve this error we need to increase the JOB execution time .
Then again "RFC connection time out" error will come up , As the program itself is missing something related to OPERATOR LOGIC , so the JOB can't be executed in time.

Now my only concern is , how to get rid of the first error i.e "OPERATOR LOGIC Failure" .

Anyone ,
Any suggestion regarding "OPERATOR LOGIC Failure" .


Regards,
Arun
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

That error will disappear when you resolve the job timeout error. The operator logic error simply informs you that it was a DataStage engine (Orchestrate) operator that detected the problem.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
oacvb
Participant
Posts: 128
Joined: Wed Feb 18, 2004 5:33 am

Post by oacvb »

Hi Arun,

We are facing the same network error, could you please let us know what exactly the change is carried out in ABAP Job.
Teej
Participant
Posts: 677
Joined: Fri Aug 08, 2003 9:26 am
Location: USA

Post by Teej »

ray.wurlod wrote:You might also consult the Message Reference Guide to see whether IIS-DSTAGE-ABAP-E-00746 is there. I'm not currently at a location where version 11.3 manuals are available. ...
http://www.ibm.com/support/knowledgecen ... me?lang=en

You are welcome. ;-)
Teej
Participant
Posts: 677
Joined: Fri Aug 08, 2003 9:26 am
Location: USA

Post by Teej »

As for the original issue - for the updated log, the original failure is within Item #27. But usually, the first failure message is just the Orchestrate engine going, "Woah, a player is dying" and usually get fed back to the logging mechanism long before the actual failure is reported.

Item #28 is just a few line of code after that, so can be ignored for the most part (it's useful to know if it's happening right away, or after a few records, just for further investigation).

The real error is Item #29 -

Message Id: IIS-DSTAGE-ABAP-E-00746
Message: ABAP_Input,0: Fatal Error: Fatal: ABAP background job time-out occurred as defined using BG_JOB_TIMEOUT property.

You will need to investigate why ABAP job took so long that the timeout is triggered. Maybe your timeout is unusually short (13 minutes doesn't seem short, but on a very busy server, it can be...)

Item #30 and below is more useful if you understand how Orchestrate works (turn on $APT_DUMP_SCORE and count from 1 the players on node1 -- which most likely is ABAP_Input.) But really, it's useless for this purpose, and is just a sign of the whole dominos falling down after a failure.

Item #32 used to be considered as a serious thing, but we discovered that during a failure, errno 10054 is really a Windows socket error message ("The other end of the socket died.") There are a few patches for this kind of error message, but most likely not helpful in your situation.

Focus on the server side for your ABAP with your ABAP administrator.

-T.J.
Post Reply