DSXchange

Hi,

Im working on migrating parallel jobs from DS7.5 to 8.5.
one of the jobs is to read a table from SQLSERVER DB using DRS stage.
It works fine in 7.5. However, when I ran the same job in 8.5, it got aborted due to warnings mentioned below.

I tested by replecing DRS stage with DRS connector in DS8.5, It worked fine. However, I should use only DRS stage. Do we need to concentrate
anything on environment settings to make DRS stage work fine in 8.5. If so, Could you guide me?

Regards,

My apology.

Here are warnings

tpgtable,0: 2b2c7c0f6000-2b2c7c3da000 r-xp 00000000 fd:17 2083039 /opt/IBM/InformationServer/Server/PXEngine/lib/liborchgeneralx86_64.so
tpgtable,0: 2b2c7c3da000-2b2c7c4d9000 ---p 002e4000 fd:17 2083039 /opt/IBM/InformationServer/Server/PXEngine/lib/liborchgeneralx86_64.so
tpgtable,0: 2b2c7c4d9000-2b2c7c4e9000 rw-p 002e3000 fd:17 2083039 /opt/IBM/InformationServer/Server/PXEngine/lib/liborchgeneralx86_64.so

Can anybody help?

Not with the sparse error information given. Are there no more messages or entries in the log?

Those are not necessarily warnings. What else is in the log with Warning severity?

Hi Ray/Arndw,

Here is to go more.
APT_CombinedOperatorController(1),0: 7fef50bfa000-7fef50bfb000 r--p 0001e000 68:03 40245 /lib64/ld-2.11.1.so
APT_CombinedOperatorController(1),0: 7fef50bfb000-7fef50bfc000 rw-p 0001f000 68:03 40245 /lib64/ld-2.11.1.so
APT_CombinedOperatorController(1),0: 7fef50bfc000-7fef50bfd000 rw-p 00000000 00:00 0
APT_CombinedOperatorController(1),0: 7fff22480000-7fff22481000 rw-p 00000000 00:00 0
APT_CombinedOperatorController(1),0: 7fff2252c000-7fff2252d000 r-xp 00000000 00:00 0 [vdso]
APT_CombinedOperatorController(1),0: ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

fatal error:

APT_CombinedOperatorController(1),0: Operator terminated abnormally: received signal SIGABRT
APT_CombinedOperatorController(0),0: Operator terminated abnormally: received signal SIGABRT
TERT_ML_S04_DEL,0: Caught exception from runLocally(): APT_Operator::UnControlledTermination: From: UnControlledTermination via exception...

TERT_ML_S04_DEL,0: The runLocally() of the operator failed.
TERT_ML_S04_DEL,0: Output 0 produced 0 records.
TERT_ML_S04_DEL,0: Operator terminated abnormally: runLocally() did not return APT_StatusOk
node_node1: Player 1 terminated unexpectedly.
main_program: APT_PMsectionLeader(1, node1), player 1 - Unexpected termination by Unix signal 9(SIGKILL).
main_program: APT_PMsectionLeader(1, node1), player 4 - Unexpected exit status 1.
main_program: Step execution finished with status = FAILED.

ajithaselvan wrote:...
main_program: APT_PMsectionLeader(1, node1), player 1 - Unexpected termination by Unix signal 9(SIGKILL)...

It looks a bit like another process issued a signal to the aborted one to terminate.

Could you add the parameter "APT_DISABLE_COMBINATION" and set it to "true" and re-run it, that might assist in locating the actual stage causing the error. It might not be the DRS stage as assumed in this case.

Hi Arndw,

Job is getting aborted. Below are the error message along with pervious one.

cs}}}(0),0: Fatal Error: waitForWriteSignal(): Premature EOF on node fcas1820 Interrupted system call
node_node1: Player 6 terminated unexpectedly.
main_program: APT_PMsectionLeader(1, node1), player 6 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 4 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 8 - Unexpected exit status 1.
APT_PMsectionLeader(1, node1), player 10 - Unexpected exit status 1.
main_program: Step execution finished with status = FAILED.

Regards,

is "TERT_ML_S04_DEL" your DRS Stage?

Your assumption is correct. It is TERADATA stage

Umm, but your original post stated

one of the jobs is to read a table from SQLSERVER DB using DRS stage.

yeah.... when I tested with DRS connector stage, the jobs works fine.
There is no issue with teradata stage. So I was under assumption that, It is a issue with DRS stage.

Regards,

What confuses me is that you mentioned SQL-Server initially and now it is Teradata.

My apology.

Let me explain you clearly.

My job is simple which extracts data from table A (SQL server DB) and do a look up with table B(TERADATA) and load it to Dataset.
SQL server DB is connected through DRS stage and TERADATA is connected through TERA DATA stage.

It works good, If I replace DRS stage with DRS connector in 8.5. whereas,
getting above warnings, if I execute with old one (DRS stage).

If you write a simple job with just the DRS stage reading data as in your original job and writing to a PEEK stage, does the error still occur?