on 12-06-2005 1:41 PM
Hello,
the LOG backup of the database crashes with following error:
ERR
-24988,ERR_SQL: sql error
-8888,connection broken [183]
KNLDIAG
2005-12-06 14:18:56 0x370 19633 CONNECT Connect req. (T4, Node:'', PID:3008)
2005-12-06 14:18:56 0x370 19651 CONNECT Connection released, T4
2005-12-06 14:18:56 0x370 19633 CONNECT Connect req. (T4, Node:'', PID:3008)
2005-12-06 14:18:56 0x370 19651 CONNECT Connection released, T4
2005-12-06 14:19:57 0x370 19633 CONNECT Connect req. (T4, Node:'', PID:3008)
2005-12-06 14:19:59 0x370 19615 VOLUMEIO Attaching volume 'F:\sapdb\EXI\saplog\DISKL001'
2005-12-06 14:19:59 0x9C8 19613 DBSTATE I/O thread for 'F:\sapdb\EXI\saplog\DISKL001' started
2005-12-06 14:19:59 0x370 19617 VOLUMEIO Single I/O attach, 'F:\sapdb\EXI\saplog\DISKL001', UKT:3
2005-12-06 14:19:59 0xCB4 19625 IO Async I/O thread started, 'H:\Sicherung_XI\logs\EXI_LOG.017
2005-12-06 14:19:59 0xEE0 52101 SAVE Filetype: file
2005-12-06 14:19:59 0xEE0 52024 SAVE 200 pages -> "erung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:04 0xEE0 52024 SAVE 10800 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:09 0xEE0 52024 SAVE 20000 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:14 0xEE0 52024 SAVE 29400 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:19 0xEE0 52024 SAVE 39000 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:24 0xEE0 52024 SAVE 48200 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:29 0xEE0 52024 SAVE 57600 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:34 0xEE0 52024 SAVE 66800 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:39 0xEE0 52024 SAVE 76400 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:44 0xEE0 52024 SAVE 85400 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:49 0xEE0 52024 SAVE 94800 pages -> "ung_XI\logs\EXI_LOG.017"
2005-12-06 14:20:54 0xEE0 52024 SAVE 104000 pages -> "ng_XI\logs\EXI_LOG.017"
2005-12-06 14:20:59 0xEE0 52024 SAVE 113200 pages -> "ng_XI\logs\EXI_LOG.017"
2005-12-06 14:21:04 0xEE0 52024 SAVE 122600 pages -> "ng_XI\logs\EXI_LOG.017"
2005-12-06 14:21:09 0xEE0 ERR 0 SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer pagebuffer contains no endOfLogDevice failed!
2005-12-06 14:21:09 0xEE0 ERR 18196 DBCRASH vabort:Emergency Shutdown, Log_SaveIterator.cpp: 222
-
current write position -
KNLDIAG.ERR
2005-12-06 14:18:41 --- Starting GMT 2005-12-06 13:18:41 7.5.0 Build 031-123-104-253
2005-12-06 14:21:09 0xEE0 ERR 0 SAPDBErr Assertion of state Log_SaveIterator::CheckPageBuffer pagebuffer contains no endOfLogDevice failed!
2005-12-06 14:21:09 0xEE0 ERR 18196 DBCRASH vabort:Emergency Shutdown, Log_SaveIterator.cpp: 222
in online mode the database works fine, also a full backup...
Regards,
Domi
Hi,
the reason for the problem might be a partially written logpage on a logvolume, or a non-written, but expected logpage. If this page is not found, the logbackup throws the error you received. This should be a very rare error.
In order to solve this, you could try the following:
1. Then bring the database instance to mode <b>online</b>
2. Then bring the database instance to mode <b>admin</b>
3. Clear the log:
dbmcli -d <SID> -u <controluser>,<controlpasswd> -uUTL <controluser>,<controlpasswd> util_execute clear log
4. Perform full data backup
5. Perform log backup
Regards,
Roland
P.S.: the clear log command is a 'dangerous' command, please don't use it otherwise.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
9 | |
9 | |
7 | |
7 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.