Lost BLOBs are not processed correctly by the Integrity Check (Hotfix 1)
|Article:TECH24978|||||Created: 2006-11-08|||||Updated: 2007-03-19|||||Article URL http://www.symantec.com/docs/TECH24978|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
Lost BLOBs are not processed correctly by the Integrity Check job. Fragmented data chunks (that were partially in the missing BLOB and partially in the very next one) were left in the other BLOBs causing snapshots of some of the files to fail. Snapshot failures symptoms are addressed by article 29245.
Recovery Solution 6.2.2332
There is a problem with the LostBlobHandling stored procedure that is used to process all the broken references to the missing BLOBs during Integrity Check job.
A hotfix is attached to this article. It was designed to fix the root cause of the issue. In case you have snapshot failures as well please refer to article 29245.
Instructions how to apply the fix follow:
- Download the hotfix that has the updated LostBlobHandling stored procedure.
- It is not needed to stop the Recovery Solution Server service. Just make sure the Recovery Solution Server is not running the Integrity Check job at this moment.
- Go to Microsoft Query Analyzer* and load the downloaded script into it.
- Select the Recovery Solution database from the drop-down list on the top menu and execute it.
Article URL http://www.symantec.com/docs/TECH24978