Page 1 of 1

Match Designer match pass run process failed

Posted: Tue Aug 15, 2017 11:19 pm
by ecclesr
First time running Match Designer Test All passes

##E IIS-DSEE-TDOD-00007 16:58:53(000) <APT_CombinedOperatorController(0),0> [IBM(DataDirect OEM)][ODBC DB2 Wire Protocol driver][UDB DB2 for Windows, UNIX, and Linux]ERROR FOUND IN APPLICATION PROGRAM INPUT PARAMETERS FOR SQL STATEMENT. REASON 106. 87 485 1376256 INPUT
##E IIS-DSEE-TFOR-00089 16:58:53(001) <ODBC_Enterprise_0,0> The runLocally() of the operator failed.
##E IIS-DSEE-TFOR-00089 16:58:53(006) <APT_CombinedOperatorController(0),0> The runLocally() of the operator failed.
##E IIS-DSEE-TFPM-00040 16:58:53(007) <APT_CombinedOperatorController(0),0> Operator terminated abnormally: runLocally() did not return APT_StatusOk
##E IIS-DSEE-TFIO-00032 16:58:54(000) <buffer(0),0> Error in writeBlock - could not write 127168
##E IIS-DSEE-TFOR-00001 16:58:54(001) <buffer(0),0> Failure during execution of operator logic.
##F IIS-DSEE-TFIO-00054 16:58:54(004) <buffer(0),0> Fatal Error: APT_BufferOperator::writeAllData() write failed. This is probably due to a downstream operator failure.
##E IIS-DSEE-TFPM-00192 16:58:54(000) <node_node1> Player 10 terminated unexpectedly.
##E IIS-DSEE-TFPM-00338 16:58:54(000) <main_program> APT_PMsectionLeader(1, node1), player 10 - Unexpected exit status 1.
##E IIS-DSEE-TFPM-00192 16:58:54(001) <node_node1> Player 12 terminated unexpectedly.
##E IIS-DSEE-TFPM-00339 16:58:54(001) <main_program> APT_PMsectionLeader(1, node1), player 12 - Unexpected termination by Unix signal 9(SIGKILL).
##E IIS-DSEE-TFSC-00011 16:58:59(000) <main_program> Step execution finished with status = FAILED.

Thanking you all in advance

Posted: Wed Aug 16, 2017 7:30 am
by qt_ky
DB2 error given with reason code 10: Invalid data length for output variable. (not sure what it means).

It also looks like it failed to write something to disk. Any chance you are short on disk space on your server? Perhaps it reached 100% full while you were running.

Also check all the ulimit settings on your server.

Posted: Sun Aug 20, 2017 6:04 pm
by ecclesr
Solution was to update the ODBC drivers