  | | | autosave doesn 't work | autosave doesn 't work 2006-09-06 - By Michael J?rgens
Back Brunzema, Martin schrieb: > > > >> -- --Original Message-- -- >> From: Michael J?rgens [mailto:michael@(protected)] >> > > >>> 2006-09-06 09:01:18 10 12822 TASKING Thread 303 joining >>> 2006-09-06 09:01:18 303 11566 stop DEVi stopped >>> 2006-09-06 09:01:19 16 52031 AUTOSAVE ready >>> >> It seems, that autosave don?t wakeup from standby mode. >> >> It is possible, that this is problem with system tables. >> I don?t know exactly if, I reinstall the system tables after upgrade >> from 7.5.0.24 to 7.5.0.30. >> > > Hi Michael, > > After switching autosave on it is checked whether there has log to be > saved. This is the output you see in the file knldiag. It shows, that > autosave in principle works. > Normally a task which is periodically running checks whether log > has to be saved and - if necessary - starts another task to do the job. > Could you please check with the dbmcli command "show tasks" in which > state the timeout-task T1 is. Normally you should see there a "sleep". > SERVERDB: PROD_R2
ID UKT UNIX TASK APPL Current Timeout Region Wait tid type pid state priority cnt try item T1 6 -1 Timer -1 Vsleep 0 0 13752753(s) T2 2 -1 ALogwr. -1 No-Work (255) 0 0 186896566(s) T3 1 -1 Tracewr -1 No-Work (255) 0 0 99999 1(s) T4 6 -1 Datawr. -1 No-Work (255) 0 0 5 13752753(s) T5 6 -1 Datawr. -1 No-Work (255) 0 0 36 13752753(s) T6 6 -1 Datawr. -1 No-Work (255) 0 0 2 13752753(s) T7 6 -1 Datawr. -1 No-Work (255) 0 0 180 13752753(s) T8 6 -1 Datawr. -1 No-Work (255) 0 0 5 13752753(s) T9 6 -1 Datawr. -1 No-Work (255) 0 0 58 13752753(s) > The only value, which could potentially be misleading is the number > of unsaved pages. You could load the systemtables to be sure that > they are up to date. > I?ve tried that without any change.
Kind regards, Michael
-- MaxDB Discussion Mailing List For list archives: http://lists.mysql.com/maxdb To unsubscribe: http://lists.mysql.com/maxdb?unsub=mysql@(protected)
|
|
 |