How do you recover a corrupted document in IBM FileNet Image Services after a failed MSAR Conversion?

Answer

The example below is using Doc_id 100023

Doc ID=100023 is corrupt on the surface 3006.

There are three surfaces referenced in this procedure:

• Original Optical Surface
• Converted MSAR Surface
• Current Write MSAR Surface

1. Start MKF_tool.
   >MKF_tool
2. Select the document in the docs table to see if there are surfaces the document was migrated to.
   <MKF_tool> se docs doc_id=100023
3. The surface_id_1 is the Primary Surface and the surface_id_2 is the Tranlog.
   If the surface_id_1 = 1002, there is not a Primary surface.
   If the surface_id_2 = 0, there is not a Tranlog surface.
   Continue if you have a Primary or Tranlog surface
4. The document originally came from optical surface 3002.
   Insert the old surface into the Optical Library.
5. Check to see if the surface is enabled for Read Only for this Original Optical Surface.
   Choose Enable/Disable Media from the Storage Library Control’s (from Xapex - Application Executive) Media menu
6. Disable the converted MSAR Surface containing the document that is corrupt for Reads and Writes
7. Change the Surface ID in the MKF Tables to use the original surface.
   <MKF_tool>se docs doc_id=100023
   doc_id.............100023 pages...................1
   contig_sectors..........1 surface_id_1.........3006
   offset_1.............4000 surface_id_2.........3004
   offset_2.............4188
   <MKF_tool>allowupdates
   
   Password? (Enter the monthly password: request password from support or use the current password.)
   Updates now allowed
   <MKF_tool>update docs doc_id=100023 set surface_id_1=3002
   
   Total of 1 records updated
   <MKF_tool>se docs doc_id=100023
   doc_id.............100023 pages...................1
   contig_sectors..........1 surface_id_1.........3002
   offset_1.............4000 surface_id_2.........3004
   offset_2.............4188
   <MKF_tool>quit
8. Use the stdoccpy utility to copy the document.
   Place the Doc ID in a text file in the path of the \tmp directory and from the command line go to the path of the \tmp directory.
   The file specified by <docidfile> contains a list of the documents to copy. Each line in the file contains one document ID. The stdoccpy program uses the database to locate and copy each specified document.
   
   UNIX: /fnsw/local/tmp
   Windows: <Drive Letter>:\FNSW_loc\tmp
9. From a command line, run the stdoccpy command.
   The file name (Recover_doc.txt) given in the following example, contains the doc_id. (Note: If you specify “–docidfile <docidfile>”, and then using “–altsurf”, the document is read from the Transaction log surface.)
   
   It is necessary to know the Family that the document is to be written to. In this example, the Family for the Doc Class currently being used is MSARFam1.
   
   Use the updatedb option to update the MKF tables with the location of the new copy of the document.
   
   >stdoccpy – family MSARFam1 – filename Recover_doc.txt -updatedb
10. Check the CpyLog.xxxxxx in Background Job Control to verify that the Job completed without errors. Be sure to scroll through the whole log
11. Verify that the MKF tables were updated correctly. The surface_id_1 should now reflect the Current Write MSAR Surface
    
    >MKF_tool
    
    Type '?' for help
    
    <MKF_tool>se docs doc_id=100023
    doc_id.............100023 pages...................1
    contig_sectors..........1 surface_id_1.........3008
    offset_1.............4002 surface_id_2.........3004
    offset_2.............4188
    <MKF_tool>
12. Enable the Converted MSAR Surface for Reads again. This will allow the other good documents to be loaded from it
13. Disable the Original Optical Surface for Reads and Writes, and then eject the surface from the Optical Library, if desired