Hi,
in most situations an "add log volume" does not solve
a log full situation, because the added logvolume is
accessible first at the moment, when the write position
on the log is at the end of the old logvolume.
If a LOGFULL occurs, the save log!
All "parts" of the LogVolume are numbered and each one
has stored the identifying number of it's predecessor and
it successor in it's header-page. The message
"Linkage missmatch between volume"
means, that these values does not match any more.
Did you somehow changed the contents of this file/device?
If so: can you revert the change? Then the restart should
work again. do a logbackup and your database will run again.
If this doesn't work for you, you could patch the
header pages of the logvolume (I assume you do not really
want this).
Another way to solve the situation is to do a data backup
in admin-mode, reinstall the database and recover the
databackup, because the removal of a logvolume is not
supported.
kind regards, Martin
> -----Urspr�ngliche Nachricht-----
> Von: Helmut [mailto:[EMAIL PROTECTED]
> Gesendet: Sonntag, 14. November 2004 23:05
> An: [EMAIL PROTECTED]
> Betreff: Corrupt LOG Files MaxDB 7.5
>
>
> At the Installation the LOG went full. LOG-Mode = SINGLE.
> Then I have added a new LOG File. Nothing happens. After rebooting the
> maschine,
> the database doesnt come up, in krnldiag there is following:
>
> 2004-11-14 22:46:30 7579 11000 vattach
> '/sapdb/XI3/sapdata/DISKD0001'
> devno 1 T58 succeeded
> 2004-11-14 22:46:30 7520 11597 IO Open
> '/sapdb/XI3/saplog/DISKL001' successfull, fd: 16
> 2004-11-14 22:46:30 7633 12821 TASKING Thread 7633 starting
> 2004-11-14 22:46:30 7632 11565 startup DEVi started
> 2004-11-14 22:46:30 7520 11597 IO Open
> '/sapdb/XI3/saplog/DISKL001' successfull, fd: 17
> 2004-11-14 22:46:30 7634 12821 TASKING Thread 7634 starting
> 2004-11-14 22:46:30 7633 11565 startup DEVi started
> 2004-11-14 22:46:30 7579 11000 vattach
> '/sapdb/XI3/saplog/DISKL001'
> devno 2 T58 succeeded
> 2004-11-14 22:46:30 7520 11597 IO Open
> '/data2/sapdb/XI3/DISKL002' successfull, fd: 19
> 2004-11-14 22:46:30 7635 12821 TASKING Thread 7635 starting
> 2004-11-14 22:46:30 7634 11565 startup DEVi started
> 2004-11-14 22:46:30 7520 11597 IO Open
> '/data2/sapdb/XI3/DISKL002' successfull, fd: 20
> 2004-11-14 22:46:30 7636 12821 TASKING Thread 7636 starting
> 2004-11-14 22:46:30 7635 11565 startup DEVi started
> 2004-11-14 22:46:30 7579 11000 vattach
> '/data2/sapdb/XI3/DISKL002'
> devno 3 T58 succeeded
> 2004-11-14 22:46:30 7579 ERR 30 IOMan Log volume configuration
> corrupted: Linkage missmatch between volume 1 and 2
> 2004-11-14 22:46:30 7579 11000 vdetach
> '/sapdb/XI3/sapdata/DISKD0001'
> devno 1 T58
> 2004-11-14 22:46:30 7520 12822 TASKING Thread 7631 joining
> 2004-11-14 22:46:30 7636 11565 startup DEVi started
> 2004-11-14 22:46:30 7631 11566 stop DEVi stopped
> 2004-11-14 22:46:30 7520 12822 TASKING Thread 7632 joining
> 2004-11-14 22:46:30 7579 ERR 16 Admin
> RestartFilesystem failed with
> 'I/O error'
> 2004-11-14 22:46:30 7579 ERR 8 Admin ERROR
> 'disk_not_accessibl'
> CAUSED EMERGENCY SHUTDOWN
> 2004-11-14 22:46:30 7579 12696 DBSTATE Change DbState to
> 'SHUTDOWN'(25)
>
>
> Is there any way to delete the corrupt LOG files in order to
> add new one?
> The data file is ok.
> Thanks
> Helmut
>
--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
