Page 1 of 1

Match Specification run Error

Posted: Wed Mar 30, 2016 6:37 am
by dj
Hi,

After Server restart,we are encountering the below error in the match specification. Earlier it was running fine.

Code: Select all

#W IIS-DSEE-TFIP-00072 08:21:16(023) <APT_CopyOperator(2) in CA_Match_Freq> When checking operator: When binding output schema variable "outRec": When binding output interface field "qsMatchDataID" to field "qsMatchDataID": Implicit conversion from source type "uint64" to result type "int64": Possible range limitation.
##E IIS-QSEE-VOEV-00001 08:21:18(000) <QSM_MatOp in CA_Match_Freq,0> Unable to set the default locale

##E IIS-DSEE-TFOR-00089 08:21:18(001) <QSM_MatOp in CA_Match_Freq,0> The runLocally() of the operator failed.
##I IIS-DSEE-TFOR-00163 08:21:18(002) <QSM_MatOp in CA_Match_Freq,0> Input 0 consumed 0 records.
##I IIS-DSEE-TFOR-00163 08:21:18(003) <QSM_MatOp in CA_Match_Freq,0> Input 1 consumed 1 records.
##I IIS-DSEE-TFOR-00094 08:21:18(004) <QSM_MatOp in CA_Match_Freq,0> Output 0 produced 0 records.
##I IIS-DSEE-TFOR-00094 08:21:18(005) <QSM_MatOp in CA_Match_Freq,0> Output 1 produced 0 records.
##I IIS-DSEE-TFOR-00094 08:21:18(006) <QSM_MatOp in CA_Match_Freq,0> Output 2 produced 0 records.
##E IIS-DSEE-TFPM-00040 08:21:18(007) <QSM_MatOp in CA_Match_Freq,0> Operator terminated abnormally: runLocally() did not return APT_StatusOk
##E IIS-DSEE-TFPM-00192 08:21:19(000) <node_node2> Player 5 terminated unexpectedly.
##E IIS-DSEE-TFPM-00339 08:21:19(000) <main_program> APT_PMsectionLeader(2, node2), player 5 - Unexpected termination by Unix signal 9(SIGKILL).
##E IIS-DSEE-TFOR-00001 08:21:19(000) <APT_TSortOperator(2) in CA_Match_Freq,0> Failure during execution of operator logic.
##I IIS-DSEE-TFOR-00163 08:21:19(001) <APT_TSortOperator(2) in CA_Match_Freq,0> Input 0 consumed 0 records.
##I IIS-DSEE-TFOR-00094 08:21:19(002) <APT_TSortOperator(2) in CA_Match_Freq,0> Output 0 produced 0 records.
##F IIS-DSEE-TFIO-00126 08:21:19(003) <APT_TSortOperator(2) in CA_Match_Freq,0> Fatal Error: waitForWriteSignal(): Premature EOF on node ##ServerName## Bad file descriptor
Is it something to do with nls settings? Can someone help on how to resolve this error Thanks.

Posted: Wed Mar 30, 2016 4:11 pm
by ray.wurlod
Not directly. Somewhere the qsMatchID field is coming into a stage as uint64 but the output side maps it as int64. Look at the score; there is a Copy stage in the composite operator CA_Match_Freq, and it is here that the first problem is occurring.

Check the column definitions on your Match Frequency stage and, if you can't correct it there, then report a bug.

Unable to set the default locale error may or may not be related to the integer error.