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
Attempting to Cleanup after ABORT raised
Moderators: chulett, rschirm, roy
-
- Premium Member
- Posts: 133
- Joined: Tue Nov 23, 2004 11:24 pm
- Location: India
-
- Premium Member
- Posts: 385
- Joined: Tue Oct 07, 2003 4:55 am
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
-
- Premium Member
- Posts: 133
- Joined: Tue Nov 23, 2004 11:24 pm
- Location: India
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
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
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
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.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.