Attempting to Cleanup after ABORT raised

Pavan_Yelugula · Post by **Pavan_Yelugula** » Thu Jan 20, 2005 12:09 am

hi all

i have this error "Attempting to Cleanup after ABORT raised in stage jbRevenue..CalcVariance" as a warning and the job is getting aborted.
it was working fine in one run and it was aborting after that.

The stage it is refering is a transformer and some calc are being done in the transformer

any inputs will be really helpful

Thanks and regards
Pavan

Amos.Rosmarin · Post by **Amos.Rosmarin** » Thu Jan 20, 2005 12:48 am

Hi,

Look at this forun on howto use the &PH& directory.

You are probably doing some wrong operation on the data e.g. passing null to an operation that does not allow null or doing a mathmatical operation on a charachter.

HTH,
Amos

ray.wurlod · Post by **ray.wurlod** » Thu Jan 20, 2005 1:43 am

This message can be generated by many things, some of them outside of DataStage's control (such as disk full). Usually there are other warning messages in the log; if not, reset the job and look for a message with "From previous run..." as its first line - if present it will contain additional diagnostic information.

fridge · Post by **fridge** » Thu Jan 20, 2005 5:18 pm

I believe (but will prob get blasted by the likes of Ray) that this can also happen if deadlock daemon enabled and it found a deadlock.

Basically if 'deadly embrace' occurs on a hashfile record/group the daemon kicks in and nobbles one of the offenders

ray.wurlod · Post by **ray.wurlod** » Thu Jan 20, 2005 9:07 pm

No blast, the scenario described can happen, if the deadlock daemon is configured automatically to resolve the deadlock.

But, by default, the deadlock daemon does not resolve deadlocks; it only detects them so that the administrator can release them manually.

It's one of my favourite things in the product; the option on the DEADLOCK.MENU is "select victim for deadlock resolution"

"Resolving" a deadlock typically involves at the very least rolling back a supposedly active transaction, or even killing its owner process.

Pavan_Yelugula · Post by **Pavan_Yelugula** » Thu Jan 20, 2005 9:38 pm

hi all
i guess i got it. the calculation i said i was doing in the transformer is something like
((col1-col2)/col2)*100

what is happening is someof the values which are coming in col2 are blank
as soon as i changed it. it is working fine
The error which was given by DataStage couldn't point me to this but a couple of trail and error solutions got me it.

Thanks all for the help

Thanks and Regards
Pavan

ray.wurlod · Post by **ray.wurlod** » Thu Jan 20, 2005 11:33 pm

If col2 is blank your expression is effectively attempting to divide by zero which the DataStage or UniVerse documentation will tell you is an illegal operation and will cause the executing process to abort.