Domino 9 und frühere Versionen > Administration & Userprobleme

BTree structure ist beschädigt

(1/5) > >>

Gerhard:
Hallo zusammen!

Aus dem Urlaub zurück und schon wieder Probleme !  >:(

Folgende Fehlermeldung im Logfile:
07.06.2004 02:12:43   Fehler bei der Aktualisierung der Ansicht 'ToDelete' in funder\Produktion\TCAL_NEU.NSF: B-tree structure is invalid

Habe Fixup versucht, bringt aber nix. Kann alte Dokumente nicht mehr herauslöschen. Fehlermeldung: Hash-Index kann nicht verwendet werden da Index beschädigt !

Was tun ?

Sollte ich Strg-Shift-F9 betätigen um die Ansichten zu aktualisieren ?

Danke für die Hilfe !

koehlerbv:
Strg-Shift-F9 schadet nie - gib' dem eine Chance.
Ansonsten UPDALL. Falls das auch nicht greift, geht es ganz schnell über den Designer: Öffne dort die Ansicht mit dem defekten Index, mach irgendeine kleine Änderung (und nimm sie wieder zurück) und speichere die Ansicht. Der alte Index wird dafür komplett verworfen und ein neuer aufgabut.

HTH,
Bernhard

Gerhard:
Hallo Bernhard !

Er meldet beim Fixup Ansicht 574 BTree defekt, aber im Designer finde ich keine Ansicht mit dem Namen 574 !

Was meint er damit ?

Glombi:
Ich habe was in der KBASE gefunden - welche Notes Version hat der Server?

Enabling Soft Deletions Results in Database Corruption - Typically in Mail Files

Problem:

Database corruption in some Notes/Domino R5 releases has been observed, typically in mail files.  The following Fixup errors may be observed:

Database fixup process started
Performing consistency check on mail\filename.nsf...
Document NT00000AAA in database <path\filename.nsf> is damaged: Field length stored in document is incorrect (Field Body, Datatype 0001)
Document NT00000AAA in database <path\filename.nsf> has been deleted

or

Document NT00000AAA in database <path\filename.nsf> is damaged: Document has invalid structure
Document NT00000AAA in database <path\filename.nsf> has been deleted

or

Database is corrupt -- Cannot allocate space

When running Compact the following errors may be observed:

<path\db name> is damaged: Document has invalid structure
**** DbMarkCorrupt(DbFixup: invalid slot found, could not be repaired), DB=<path\db name> TID=[0458:0002-05A8] ***
Error compacting database <path\db name> 03:F5

Once the database is corrupted the following may also be observed:

NIF: DETECTED STORAGE CORRUPTION ERROR 'B-tree structure is invalid'

NIF: DETECTED STORAGE CORRUPTION ERROR 'Attempt to use an invalid database pointer'

Error updating view '($All)' in mail\filename.nsf: B-tree structure is invalid

NSFDbOpen: File '<path\db name>' is CORRUPT - Now Read-Only!

Clustering is not relative to this issue.  The issue has appeared in both clustered and non-clustered environments.

Solution:

This issue has been observed on a number of Domino Servers, release 5.0.5 and later.  Research has found that the issue occurs when the 'Allow Soft Deletions' option within the 'Advanced Database Properties' InfoBox is enabled.  'Allow Soft Deletions' will corrupt the database if soft deletions are enabled and an inplace compaction moves non-summary data to another location in the database.

This issue was reported to Lotus Quality Engineering, and was resolved in Domino 5.0.9 Server.

Excerpt from the Lotus Notes and Domino Release 5.0.9 MR fix list (available at http://www.notes.net):

Server - Database
SPR# IGOS4W6KD8 - Soft-deletions were causing inplace compaction to corrupt databases. This has been fixed in 5.0.9.


Workaround:
In some cases running Updall -R on the mail database, and then Fixup -F -J, does repair the existing corruption.  To prevent the issue from occurring again disable the Soft Deletions feature for the database.

To access the 'Allow Soft Deletions' setting, select File, Database, Properties.  When the InfoBox appears, switch to the Advanced tab (the "beanie" icon).  The 'Allow Soft Deletions' checkbox is located half way down the list of settings.

In some cases where this issue has occurred the mail database had a background LotusScript agent which deleted documents.   Further research is being done to review these agents.   The issue may not be limited to cases where a background agent is deleting documents, but knowing whether or not a customer has such an agent may be helpful in troubleshooting this issue.

One example of the debug output when such an agent was running:

AMgr: Agent ('Purge Agent' in 'jdoe.nsf') printing: mail\jdoe.nsf
AMgr: Agent ('Purge Agent' in 'jdoe.nsf') printing: Deleting from mail\jdoe.nsf
**** DbMarkCorrupt(NoteOpenExtended: NoteID 000048EE NS (000033E9) or slot (00002D94) length invalid; Bucket 00000047 Slot 00000002), DB=F:\Lotus\Data\mail\jdoe.nsf  TID=[012E:0002-012D] ***

Gerhard:
Server Notes 5.07a for Windows/32

Navigation

[0] Themen-Index

[#] Nächste Seite