Diffrnce b/w Update Option and SQL

[Gopinath]

Hi,

Iam using Loading Job, which the update option as clear the table, then insert rows, with execution mode as 'Parallel' and it's two node config.
Array and trans size is 500.

If i run this Job, iam not getting any error or abort msgs, but is i run the same Job again it's getting aborted. This is continuing.

I have changed the execution mode into 'Sequential', now it's running fine without issues, but this will impact the performance..? Am i right here.

What shud be done for running in 'parallel' mode.

We have also tried another option like, update action is 'Insert rows without clearing' but in my 'Before SQL' i gave the query as "Delete from the table name".Here execution mode is 'Parallel'

But i beleive this two options remains the same, my question is, if this two option is same then i may get that abort msg any time as i got previously right..?

why it's running fine and also it's getting aborted in the next minute itself.
Is it anything because of Node config issues.
Expecting valuable suggesstions..

[chulett]

Not sure how anyone can help without knowing what "aborts" you are getting. Please post the actual error message(s) from the job's log.

[Gopinath]

Not sure how anyone can help without knowing what "aborts" you are getting. Please post the actual error message(s) from the job's log. ...

Hi,

Excuse for not mentioning th eabort msg, It says "Deadlock Time out error"