Sidebar
public:5315_failed_to_commit_journal
Table of Contents
[V7] ISSUE: Failed to commit journal. Not all data can be written to blocks available
Article ID:
5315
Reviewed:
2018-03-07
Product Version:
AhsayACB / AhsayOBM: 7.3.0.0 to 7.x
OS: All platforms
ATTENTION 1st January, 2022: v7 officially End-of-Life [details]
Problem Description
When performing a backup of any type, the following error message is received in the backup report:
| No. | Type | Timestamp | Log |
| * | ... | ... | ... |
| * | info | ... | Start running post-commands |
| * | ... | ... | ... |
| * | erro | YYYY/MM/DD hh:mm:ss |
[g] [BlockDB.init][BlockFileCorruptedExpt] Error initializing bptree, temp_path\index\
index.b2b, Error=[BlockFile.commitFromJournal] Failed to commit journal, caused by [g] [BlockFile.commitFromJournal] Failed to commit journal, caused by [RuntimeException] [CommitJournal.run] error, caused by [f] [BlockFile.saveForJournal] Not all data can be written to blocks available |
| * | ... | ... | ... |
Cause
The message suggests that there was an issue writing to the allocated data block.
Resolution
To resolve the issue, perform the following steps:
- Patch the AhsayOBM / ACB application to version 7.15.2.2 or above. The instructions can be found by Clicking Here.
- Perform a Data Integrity Check for the affected backup set afterward. Refer to the following KB articles for details on how to start the check:
FAQ: How to run a Data Integrity Check for backup data stored in backup destination
FAQ: How to run a Data Integrity Check on AhsayOBM version 7 on Linux (CLI) machine - Perform the backup again to see if the problem persists.
Keywords
BlockDB, init. BlockFileCorruptedExpt, initializing, bptree, index.b2b, BlockFile, commitFromJournal, journal, RuntimeException, saveForJournal
public/5315_failed_to_commit_journal.txt · Last modified: 2021/12/16 06:37 by anna.olalia