APT_CombinedOperatorController(6)

tanaya.deshpande@tieto.co · Mon Oct 18, 2010 1:00 am

I am getting these errors in a job where I am inserting and updating records in MS SQLserver stage

D_Employee,1: Failure during execution of operator logic.

Fatal Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Incorrect syntax near '@P7'.

Player 30 terminated unexpectedly.

APT_PMsectionLeader(2, node2), player 30 - Unexpected exit status 1.

Join,1: Failure during execution of operator logic.

Join,1: Fatal Error: Unable to allocate communication resources

node_node2: Player 18 terminated unexpectedly.

2: Fatal Error: Caught unknown exception in parallel process: terminating.

The Section Leader on node node2 has terminated unexpectedly.

can anyone help...whats the meaning of "Incorrect syntax near '@P7'".

ray.wurlod · Post by **ray.wurlod** » Mon Oct 18, 2010 1:16 am

No idea. For diagnostic purposes start by disabling operator combination, to learn which stage is throwing the error. Then it might make more sense.

tanaya.deshpande@tieto.co · Mon Oct 18, 2010 1:18 am

u mean deleting each stage one by one

ArndW · Post by **ArndW** » Mon Oct 18, 2010 2:27 am

No, we mean to define and set the environment variable $APT_DISABLE_COMBINATION to "true" in your job's parameters.

ray.wurlod · Post by **ray.wurlod** » Mon Oct 18, 2010 4:26 am

APT_DISABLE_COMBINATION

ArndW · Post by **ArndW** » Mon Oct 18, 2010 6:07 am

Ray - I corrected the original post, but you slipped in earlier

mk_ds09 · Post by **mk_ds09** » Mon Oct 18, 2010 7:03 am

May be something that worth checking :-

1. Whether connectivity is working fine or not !

You can select some other table and check for the connectivity and giving the results as expected..

2. You can enable the APT_DUMP_SCORE true, to get the detailed logs so that you can Trace the data.

3. You can also check whether data is in proper format

4. Whether lengh of all the columns are defined correclty and your input/output is compatible with that..

Hope this helps!