Hi Don,
 
you hit a bug in the statistics computation that gets triggered if a
column you are trying to determine statistics for has values that take
up more than 1022 bytes on a data page (the bug's status should turn up
at http://pts:1080/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1138672
within the next few days).
 
select * from tables where tableid = x'00000000000003e9' should show you
which table is the troublemaker. You cannot refresh statistics for this
table until the bug has been fixed. Unfortunately, this means, you will
not be able to run 'sql_updatestat *' successfully until then (you can
check the table 'SYSUPDSTATLOG' to see for which tables statistics were
already updated before the bug bit).
 
You have several options for a workaround:
 
- use sql_updatestat with a qualification that will exclude the
problematic table.
 
- check if the culprit is shown in the system table 'SYSUPDSTATWANTED';
if not, you can use the command 'Update Statistics As Per System Table'
as sysdba. This will only refresh statistics for tables of which the
system has noticed that they are outdated (with newer releases it will
also be possible to insert and remove entries from SYSUPDSTATWANTED for
administrators)
 
- write a script that calls Update Statistics for each and every table
except those that are problematic

HTH and sorry for the inconvenience,

Martin.
________________________________

From: Don Hayes [mailto:[EMAIL PROTECTED] 
Sent: Donnerstag, 3. November 2005 17:48
To: Kittel, Martin
Subject: RE: sql_updatestat error



         
         
        Don Hayes
        Database Administrator
        Tualatin Hills Parks & Recreation District
        Phone: (503) 614-1219
        FAX: (503) 629-5398>>> "Kittel, Martin" <[EMAIL PROTECTED]>
11/2/2005 11:37:00 PM >>>
        
        Hi Don,
        
        have you checked knldiag for any messages? And could you tell me
what's
        the setting for the database parameter
'UPDATESTAT_PARALLEL_SERVERS'?
        
        set to 0
         

        Maybe a vtrace of the problem could help as well...
        (http://sapdb.2scale.net/moin.cgi/VTrace)
        
         
        knldiag when attepting to update with 1%:
        2005-11-03 08:15:38    19        34 Data     Update statistic on
root 98092 canceled by task 18
        2005-11-03 08:15:38    22 ERR 51080 SYSERROR -9407 unexpected
error
        2005-11-03 08:15:38    22 ERR     9 Data
Data_PrimTreeStatisticsCoordinator.cpp:1426
        2005-11-03 08:15:38    22 ERR     9 Data     2005-11-03 08:15:38
Data Error 9
        2005-11-03 08:15:38    22 ERR     9 Data     Aborting statistics
computation due to system error
        2005-11-03 08:15:38    22 ERR     9 Data      +
SrvTasks_JobCollectTableStatistics.cpp:346
        2005-11-03 08:15:38    22 ERR     9 Data      + 2005-11-03
08:15:38 SrvTasks Error 42
        2005-11-03 08:15:38    22 ERR     9 Data      -   Error while
collecting statistics for table 00000000000003e9;  error illegal_key
        2005-11-03 08:15:38    22     11560 COMMUNIC Releasing  T148
        2005-11-03 08:15:38    22     12929 TASKING  Task T148 started
        2005-11-03 08:15:38    22     11007 COMMUNIC wait for connection
T148
         
        the trace attached as ZIP.
         
        This datasource was merely restored from a 7.5.0.5 source. I
noticed that I get the error "0" when I attempt to start the DS the
first time. But after a system table upgrade it is OK.
         
         
        A sidenote: knldiag and a few others do not appear in the GUI
for 7.6 like 7.5 does.
         

--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/[EMAIL PROTECTED]

Reply via email to