Page 3 of 3
Posted: Thu Feb 01, 2007 1:42 pm
by DSguru2B
I told you Andy had an excellent find
followup - clean run Re: SIGKILL - possibly caused by JobMon
Posted: Mon Feb 05, 2007 1:15 pm
by jgreve
asorrell wrote:If this fixes your problem please post here to confirm...
The large load ran 100% without aborting, that
is over 200 invocations just fine (it used to abort
up every few dozen invocations).
John G.
Re: followup - clean run Re: SIGKILL - possibly caused by Jo
Posted: Mon Feb 05, 2007 2:45 pm
by DSguru2B
jgreve wrote:
The large load ran 100% without aborting, that
is over 200 invocations just fine (it used to abort
up every few dozen invocations).
John G.
You must be one happy fellow.
Glad to hear it worked
Posted: Tue Feb 06, 2007 8:59 am
by asorrell
Glad to hear it worked - I'll mark the topic "resolved"! Hopefully this won't be a problem in release 8 with the new monitoring / performance features.
HappyStage
Posted: Tue Feb 06, 2007 10:37 am
by jgreve
DSguru2B wrote:jgreve wrote:
The large load ran 100% without aborting, that
is over 200 invocations just fine (it used to abort
up every few dozen invocations).
John G.
You must be one happy fellow.
Ahh, you don't know the half of it
Each invocation ran about 6 to 8 mintues (closer
to 8 or 9 as the target tables had more history
to sort through).
Total runtime was a bit over 30 hours; plan-B to
handle the aborts involved bringing a sleeping
bag and an alarm clock to check on the damn
thing every hour or two.
Plan-C was coding it in something else.
John G.