B-Tree and C013 errors in POA logs on several user databases.

Each time you reinstall Datasync server you see a lot of users being listed with the B-Tree and C013 errors.

There can be other situations when you see some user database physical file being extremely large in a size compared to amount of data in a user mailbox.

 

Reason behind errors on a user database is any application like Datasync that syncs user mailbox data via the SOAP protocol. Having said that, there might be users affected who uses Blackberry 5.x application.

Whenever you add a user to, let us say, Datasync server, there is a part of a user database called "GWEvent Notification Container" is populated with info like where to send user`s data (server`s IP address), what kind of data (user`s mail, contacts ..). With larger mailbox these data can be large as it almost "doubles" original user data.

Now, if you delete or reinstall existing Datasync server, old data inside the GWEvent Container do not get removed and you add the same data again in this part of user Database.

Or, something goes wrong with the user database and Datasync and his event container keeps growing which could bring a database beyond Flaim database physical size of 2GB for GroupWise.

 

If you see users being reported in POA logs with B-TRee errors and you know they use Datasync or Blackberry (or they were using it in a past as a part of any pilot lab project), you will need to clean their users databases, a part of this process is described in the TID 710256:

 

1. Enable HTTP interface on the POA where the user exist.An access must be configured with user / pwd otherwise you will see less options.

 

2. Click on Configuration tab.

 

3. Here find Event Configuration List that shall list all accounts that were configured and synced with the Datasync server.

 

4. Click on (any if more than one listed) user link.Here enable "Delete Events" and also "Delete Event Configuration" checkboxes and click on Submit. Repeat this step for any instance of this account listed in the list.

Shall the user have a valid Datasync account and you cannot comprehend which of listed records in the HTTP interface of POA is valid and which is obsolete, you might perhaps go for all steps that the KB 710256 describes. Alternatively you can make an educated guess and add some dummy user to the Datasync server and see with what records he gets recorded on the HTTP web site and compare it with existing users and their records.