Notes/Domino Fix List
 |  |
| SPR # JPAI5MBH9R | Fixed in 6.0.3 release |  |
Product Area: Server Technical Area: Database Transaction Logging/Recovery Platform: Cross Platform
SPR# JPAI5MBH9R - Fixed a Panic when running Fixup.
Technote Number: 1148465
Problem:
This issue was reported to Lotus software Quality Engineering and has been
addressed in Domino 6.0.3.
Excerpt from the Lotus Notes and Lotus Domino Release 6.0.3 QMU fix list:
SPR #JPAI5MBH9R - Fixed a Panic when running Fixup.
Supporting Information::
Log Excerpt:
05/06/2003 03:29:56 PM Database Fixup: Started
05/06/2003 03:30:01 PM Performing consistency check on admin4.nsf...
05/06/2003 03:38:19 PM Completed consistency check on admin4.nsf
05/06/2003 03:38:23 PM Recovery Manager: Assigning new DBIID for g:\notefile\ad
min4.nsf (need new backup for media recovery).
Thread=[0144:0002-0143]
Stack base=0x0012ECF0, Stack size = 5908 bytes
PANIC: LookupHandle: null handle
Stack Trace:
600050D8 nnotes! Panic +344
600090E4 nnotes! LockHandle +324
60008667 nnotes! OSMemGetSize +23
60723E74 nnotes! IDTableValidate +84
60B815DC nnotes! DbWriteIDTable +28
60BCB922 nnotes! DbWriteLoggedIDT +562
609785A0 nnotes! NSFDbWritePurgedNoteIDTable +144
60B56E4F nnotes! DbFlushExtended +2639
60A354BB nnotes! RmSetDbLogging +1563
60B49C69 nnotes! DbLoad +11993
609ADE6D nnotes! NSFDbOpenExtended3 +26717
0040159B nfixup! AddInMain +1435
00401E5F nfixup! NotesMain +47 More >
Last Modified on 05/18/2007
Go back
|