APAR status
Closed as fixed if next.
Error description
Running fixup -f to recover a database fails to resolve corruption. Below are details related: types of errors generated during fixup: 01/20/2011 08:34:58 PM BTVerifyNode: ERROR in 2920:0, cardinality is 28 - expected 30 01/20/2011 08:34:58 PM BTVerifyNode: ERROR in 2920:0, cardinality is 28 - expected 30 01/20/2011 08:34:58 PM BTVerifyNode: ERROR in 2920:0, maximum key value is wrong 01/20/2011 08:34:58 PM BTVerifyNode: ERROR in 2920:0, maximum key value is wrong err_invalid_btree ERROR: Invalid btree entry [c:\aaa\lotus\Domino\data\mail\XXXXXXX.nsf] err_invalid_btree ERROR: B-tree structure is invalid [c:\aaa\lotus\Domino\data\mail\XXXXXXX.nsf]\ After fixup completed, indexing of the same database resulted in the following types of errors generated **** DbMarkCorruptAgain(NoteOpenExtended: NBNS signature invalid), DB=c:\aaa\lotus\Domino\data\mail\tkman18.nsf TID=[0C48:0002-0620] F
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
This APAR is associated with SPR# JSTN8DHKA4. does not meet triage criteria for 8.53.
APAR Information
APAR number
LO58433
Reported component name
DOMINO SERVER
Reported component ID
5724E6200
Reported release
851
Status
CLOSED FIN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2011-02-11
Closed date
2011-02-23
Last modified date
2011-02-23
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
R802 PSN
UP
[{"Business Unit":{"code":"BU055","label":"Cognitive Applications"},"Product":{"code":"SSKTMJ","label":"Lotus Domino"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5.1","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
23 February 2011