UPDATE STATISTICS ends abruptly
Greetings,
I'm looking for some advice on the following problem. When running
'update statistics' the process just dies after updating a particular
table. This is run once a week and normally processes more tables than
this. There is no apparent error message as even piping the output to
a file only yeilds the last table updated (see below).
Should I drop and recreate the index for this table or the next
manually?
Is there any other place to find better error messaging (online.log
reports nothing)?
Any feedback would be appreciated.
------
update statistics high for table document (
access_level, cust_effectivity, discode_variant, dtd, import_path,
incode_item_loc, name, revision_date, sdc_chapnum,
sect_subsect_subj)
resolution 0.50000 ;------
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.
"Mr. E" wrote:
>
> Greetings,
>
> I'm looking for some advice on the following problem. When running
> 'update statistics' the process just dies after updating a particular
> table. This is run once a week and normally processes more tables than
> this. There is no apparent error message as even piping the output to
> a file only yeilds the last table updated (see below).
>
> Should I drop and recreate the index for this table or the next
> manually?
>
> Is there any other place to find better error messaging (online.log
> reports nothing)?
>
> Any feedback would be appreciated.
>
> ------
> update statistics high for table document (
> access_level, cust_effectivity, discode_variant, dtd, import_path,
> incode_item_loc, name, revision_date, sdc_chapnum,
> sect_subsect_subj)
> resolution 0.50000 ;
Well if it normally updates stats on other tables then this is not the
command you are running or it is not all of the script you run. What is
the command or script that is choosing tables to update look like? Have
you tried using my dostats.ec utility to do what you want? It has good
built-in diagnostics for reporting any errors that give it trouble.
Art S. Kagel