DIP Reprocessing - Database Reference Guide - Foundation 23.1 - Foundation 23.1 - Ready - OnBase - external

Database Reference Guide

Platform
OnBase
Product
Database Reference Guide
Release
Foundation 23.1
License

For DIP, the decision to reprocess depends on whether the option to delete files (i.e., images) from the source was enabled prior to the failover. If the option was enabled when the database failover occurred, then the batch that was being processed—which now exists in the Incomplete Process batch status queue—may have had some files successfully processed into OnBase. These files will have been deleted from the source location. The original index file and remaining files will still exist in the source location.

The index file can be processed again after failover. This process will create a new batch that contains the remaining files and the index file from the original DIP batch process.

The batch in the Incomplete Process batch status queue and the new batch in the Awaiting Commit batch status queue should contain all files referenced in the index file. This can be verified by determining the number of documents that should have been processed from the index file and verifying that the two batches contain all of those files.

For example, if there were 100 documents listed in the index file and the batch in Incomplete Process batch status queue contained 32 documents, then the batch in the Awaiting Commit batch status queue would contain 68 documents. Once the total number of documents is verified, both batches can be committed.

Alternatively, the files from the batch in the Incomplete Process batch status queue can be exported from the OnBase Disk Group, renamed, and placed back in the source directory. Then, the entire batch can be processed. Once all files have been successfully processed and committed, the batch in the Incomplete Process batch status queue can be purged.

Note:

When DIP is configured to delete source files, each file is copied to the Disk Group and deleted from the source location before the document's metadata is written to the database. For this reason, there is a very small possibility that a document's file exists in the OnBase Disk Group, but an entry for the document does not exist in the database. Therefore, it is critical to ensure that the number of documents listed in a given DIP index file matches the number processed into OnBase. If this problem exists in an OnBase system after a database failover, please contact Hyland Software, Inc. Technical Support.

If the DIP was configured to not delete files from the source location, then those files still exist in the source location and the batch can simply be reprocessed. Once the batch has been verified and committed, the batch in the Incomplete Process batch status queue can be purged.