Overview

A Pervasive Status 132 error means that the BLOBDATA file has reached its maximum storage capacity and can no longer store records without archiving information. We recommend restoring from backup to before you received the 132 error to successfully run the archive utility.

The users with supervisor security [48.1] in System Five may also have received a "Warning archive needed" message as seen below before the status 132 error. No restoration is required if running from the archive needed message.

Typically you would receive this error from an invoice screen, adding comments or document attachments.

Solutions

This procedure can take time to complete depending on the size of database files and the speed of network/server. Everyone will need to be signed out for this operation to succeed successfully.

Create a GETOUT!.NOW to ensure users do not attempt to sign in while the rebuild is in progress.

Option 1: Archive using 6.2.4.625 or later

Ensure a backup of the database has been completed before executing these steps. If something goes wrong such as a power outage or network disruption, the restoration of the backup would be the solution.

Run the new Toolbox Routine to archive old BLOBDATA records

IMPORTANT

This Toolbox Routine is available on released version 6.2.4.625 and later.

Steps

Go to Setup Tools > Utilities > Tool Box > Misc Routines
Picture / Blobdata Utils
Switch to the "Create Archive File" tab and click on the "Create Archive Directory" button
- This will create a new folder inside _datafiles called "BlobArchive"
- This will now be the storage place for all records prior to the date you specified
Set Prior date - defaults to 7 years but you can adjust this
Enable Data Types & File Attachments
Then click on the "Move to Archive" button below
- This routine will move all records starting prior to "Prior to Date" and retain all records moving forward.
- so the current BLOBDATA.BTR, BLOBHEAD.BTR & SIGDATA.BTR files should reduce in size