What else did you do? HistoryLost means that there had never
been a databackup made for this database-instance. Have a look
into your backup-history.

Yes there have never been a data or log backup BEFORE the crash, the backup is made after the crash to migrate the instance to other and be able to start it and recover the data partially (not logs).


The log is not corrupted, but it seems to be an software-error,
which is recognized by a move-check.

Which release on which platform do you use?

I USE EXT3 on Linux 2.4.xx if its important ....btw the fix u gave me is for SAPDB 7.4 so i think that it is not this case .... since its fixed in later (7.5) it says.


2004-06-11 10:18:01 17328 12781 INFO Version: '32BIT Kernel'
2004-06-11 10:18:01 17328 12781 INFO Version: 'X32/LINUX 7.5.0 Build 008-121-061-548'
2004-06-11 10:18:01 17328 12780 INFO DBROOT: '/var/opt/sdb/data/wrk/SGA'
2004-06-11 10:18:01 17328 12780 INFO LD_LIBRARY_PATH: '/opt/sdb/7500/lib:/opt/sdb/7500/sap'


So - what error do you get.

Recovering from LOG backup made from the bad LOG/instance to other instance the error i get is....


-71 connection broken server state 6 and the instance goes down and I am no able to recover the LOG

FROM KNLDIAG:
----------------------
2004-06-11 10:30:09 21287 32 Admin Kernel state: 'ADMIN' reached
2004-06-11 10:30:09 21287 54003 dynpool DYNP_A51_CACHE : 264
2004-06-11 10:30:09 21287 54003 dynpool AK51SIZES user + 1 : 11
2004-06-11 10:30:09 21287 54003 dynpool AK51SIZES headlist all : 44
2004-06-11 10:30:09 21287 54003 dynpool AK51SIZES headlist elem: 4
2004-06-11 10:30:09 21287 54003 dynpool AK51SIZES list all : 220
2004-06-11 10:30:09 21287 54003 dynpool AK51SIZES list element : 20
2004-06-11 10:30:09 21287 54003 dynpool INDEX FileListItemSize : 8
2004-06-11 10:30:09 21287 54003 dynpool INDEX NumFileListItems : 2048
2004-06-11 10:30:09 21287 54003 dynpool INDEX FileListSizeAll : 16384
2004-06-11 10:30:09 21287 54003 dynpool INDEX FunnelItemSize : 8
2004-06-11 10:30:09 21287 54003 dynpool INDEX QueueItemPtrSize : 4
2004-06-11 10:30:09 21287 54003 dynpool INDEX QueueItemSize : 36
2004-06-11 10:30:09 21287 54003 dynpool INDEX SortItemSize : 16
2004-06-11 10:30:09 21287 54003 dynpool INDEX NumFunnelItems : 2048
2004-06-11 10:30:09 21287 54003 dynpool INDEX FunnelSizeAll : 131072
2004-06-11 10:30:09 21287 54003 dynpool DYNP_B49_IDXSIZE : 147456
2004-06-11 10:30:09 21287 12600 VERSION 'Kernel 7.5.0 Build 008-121-061-548'
2004-06-11 10:30:09 21287 54003 dynDATA DYND_K57_KB_PAGES : 11
2004-06-11 10:30:09 21287 54003 dynDATA BACKUP RESTART REC (8K): 1
2004-06-11 10:30:09 21287 54003 dynpool BACKUP TASK LIST : 192
2004-06-11 10:30:09 21287 54003 dynpool BACKUP TAPE LIST : 352
2004-06-11 10:30:09 21287 54003 dynpool BACKUP DEVSP LIST : 176
2004-06-11 10:30:09 21287 54003 dynpool BACKUP SRR QUEUE : 656
2004-06-11 10:30:09 21287 54003 dynpool DYNP_K38_SAVE_GLOB : 1376
2004-06-11 10:30:09 21287 54003 dynDATA DYND_K38_SAVE : 217
2004-06-11 10:30:09 21287 54003 dynDATA BACKUP RESTART REC (8K): 1
2004-06-11 10:30:09 21287 54003 dynpool BACKUP TASK LIST : 32
2004-06-11 10:30:09 21287 54003 dynpool BACKUP TAPE LIST : 688
2004-06-11 10:30:09 21287 54003 dynpool BACKUP DEVSP LIST : 16
2004-06-11 10:30:09 21287 54003 dynpool BACKUP SRR QUEUE : 128
2004-06-11 10:30:09 21287 54003 dynpool DYNP_K38_AUTOSAVE : 864
2004-06-11 10:30:09 21287 54003 dynDATA DYND_K38_AUTOSAVE : 41
2004-06-11 10:30:09 21287 54003 dynpool KB50 mdesc item size : 232
2004-06-11 10:30:09 21287 54003 dynpool KB90 mdesc items : 33
2004-06-11 10:30:09 21287 54003 dynpool KB90 mdesc list size : 7656
2004-06-11 10:30:09 21287 54003 dynpool KB90 mdesc list aligned: 7664
2004-06-11 10:30:09 21287 54003 dynpool KB90 packet items : 21
2004-06-11 10:30:09 21287 54003 dynpool KB90 packet desc size : 16
2004-06-11 10:30:09 21287 54003 dynpool KB90 packet desc list : 336
2004-06-11 10:30:09 21287 54003 dynpool KB90 packet size : 36656
2004-06-11 10:30:09 21287 54003 dynpool KB90 packetsize aligned: 36656
2004-06-11 10:30:09 21287 54003 dynpool KB90 packet list : 769776
2004-06-11 10:30:09 21287 54003 dynpool KB90 parent list : 736
2004-06-11 10:30:09 21287 54003 dynpool KB90 kbfunction_task : 32
2004-06-11 10:30:09 21287 54003 dynpool KB90 parent items / 0.7: 45
2004-06-11 10:30:09 21287 54003 dynpool KB90 parent desc size : 16
2004-06-11 10:30:09 21287 54003 dynpool KB90 parentdesc aligned: 720
2004-06-11 10:30:09 21287 54003 dynpool KB90 parent hash list : 180
2004-06-11 10:30:09 21287 54003 dynpool KB90 parenthash aligned: 192
2004-06-11 10:30:09 21287 54003 dynpool KB90 maxservertasks : 20
2004-06-11 10:30:09 21287 54003 dynpool KB90 server desc size : 24
2004-06-11 10:30:09 21287 54003 dynpool KB90 server list : 480
2004-06-11 10:30:09 21287 54003 dynpool KB90 serverlist aligned: 480
2004-06-11 10:30:09 21287 54003 dynpool DYNP_K90_DISTRIB : 779168
2004-06-11 10:30:09 21289 12929 TASKING Task T3 started
2004-06-11 10:30:09 21288 12929 TASKING Task T2 started
2004-06-11 10:30:09 21288 ERR 13900 RTEHSS RTEHSS_API [RTEHSS_API(COPY):RTEHSS_GetMapping]
2004-06-11 10:30:09 21288 ERR 13900 RTEHSS RTEHSS_API [ValidateOrCreateShare cannot stat volume directory symlink /var/opt/sdb/data/wrk/SGAZ3E0Z3EZ3E`]3Eo\3E
2004-06-11 10:30:09 21288 ERR 13900 RTEHSS p@(]
2004-06-11 10:30:09 21288 ERR 13900 RTEHSS RTEHSS_API [Failed to create or validate share for volume DAT_0001 entry 0 ]


FROM KNLDIAGERR:
---------------------------
2004-06-11 10:29:23 --- Starting GMT 2004-06-11 08:29:23 7.5.0 Build 008-121-061-548
2004-06-11 10:29:26 18891 ERR 13900 RTEHSS RTEHSS_API [RTEHSS_API(COPY):RTEHSS_GetMapping]
2004-06-11 10:29:26 18891 ERR 13900 RTEHSS RTEHSS_API [ValidateOrCreateShare cannot stat volume directory symlink /var/opt/sdb/data/wrk/SGAZ3E0Z3EZ3E`]3Eo\3E
2004-06-11 10:29:26 18891 ERR 13900 RTEHSS p@(]
2004-06-11 10:29:26 18891 ERR 13900 RTEHSS RTEHSS_API [Failed to create or validate share for volume DAT_0001 entry 0 ]
2004-06-11 10:29:46 18925 ERR 8 Admin ERROR 'log_error' CAUSED EMERGENCY SHUTDOWN
2004-06-11 10:30:04 --- Starting GMT 2004-06-11 08:30:04 7.5.0 Build 008-121-061-548
2004-06-11 10:30:09 21288 ERR 13900 RTEHSS RTEHSS_API [RTEHSS_API(COPY):RTEHSS_GetMapping]
2004-06-11 10:30:09 21288 ERR 13900 RTEHSS RTEHSS_API [ValidateOrCreateShare cannot stat volume directory symlink /var/opt/sdb/data/wrk/SGAZ3E0Z3EZ3E`]3Eo\3E
2004-06-11 10:30:09 21288 ERR 13900 RTEHSS p@(]
2004-06-11 10:30:09 21288 ERR 13900 RTEHSS RTEHSS_API [Failed to create or validate share for volume DAT_0001 entry 0 ]



Hope it helps, thanx, Josu.

From: "Brunzema, Martin" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: "'gollum sss'" <[EMAIL PROTECTED]>
Subject: AW: Corrupt Log Volume (maybe...)
Date: Fri, 11 Jun 2004 10:05:56 +0200

>
> Hi all,
>
> my maxdb instance is giving me this error in knldiag after a
> power line
> crash/recovery on linux :
>
> 2004-06-10 11:06:19 15846         2 Log      Expected ioseq
> 840517, found
> 558353-558368 on off 10641
> 2004-06-10 11:06:19 16170     11565 startup  DEVi started
> 2004-06-10 11:06:19 15846         6 Log      1 queues, flushmode is
> 'MinimizeSpace', devstate is 'HistoryLost'
What else did you do? HistoryLost means that there had never
been a databackup made for this database-instance. Have a look
into your backup-history.


> 2004-06-10 11:06:19 15846 7 Log Oldest not saved > is ioseq > 840517 @ off 10641 > 2004-06-10 11:06:19 15846 8 Log First known on > LogVolume is > ioseq 558353 @ off 10641 > 2004-06-10 11:06:19 15846 5 Log Restart from > ioseq 839685 @ off > 10500 to ioseq 840516 @ off 10640 > 2004-06-10 11:06:19 15846 10 Log Result after > checking the log > device: 'Ok' > 2004-06-10 11:06:19 15826 3 Restart recovering log > from log_volume > from IOSeq: '839685' > 2004-06-10 11:06:19 15838 ERR 54111 MOVE UpdMap.2: > 16[26]->43[2380] > len:2338 > 2004-06-10 11:06:19 15838 ERR 5 Restart REDO: T1324867 > (committed) > redoresult: 3, TrError: -9111 > 2004-06-10 11:06:19 15826 WNG 4 Restart REDO: Aborted > 2004-06-10 11:06:19 15826 WNG 4 Restart REDO: Aborted > 2004-06-10 11:06:19 15846 WNG 21 Admin Redo error > '-9111' occured > 2004-06-10 11:06:19 15846 ERR 8 Admin ERROR > 'move_error' CAUSED > EMERGENCY SHUTDOWN > 2004-06-10 11:06:19 15846 12696 DBSTATE Change DbState to > 'SHUTDOWN'(25)

The log is not corrupted, but it seems to be an software-error,
which is recognized by a move-check.

Which release on which platform do you use?

This is http://www.sapdb.org/webpts?wptsdetail=yes&ErrorType=0&ErrorID=1119247
>
>
> Somebody can help? I am able to recover DATA backup but NO
> LOG backup of the
> existing DB info as there arent any previous backups, if i
> try to recover
> log backup it gives me an error retrieving the log data.


So - what error do you get.

regards, Martin

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



_________________________________________________________________
Visita MSN Latino Noticias: Todo lo que pasa en el mundo y en tu pa�n, �en tu idioma! http://latino.msn.com/noticias/



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



Reply via email to