5.6 Checking Results and Error Files

Input Agent has a retry mechanism to allow it to reattempt processing the input file in the event of a recoverable error. An example of this type of error is when the repository is not yet available and needs to finish initializing. When Input Agent detects a recoverable error, it puts the filing back on the JMS queue. The queue has a configurable retry wait timer that prevents the input file from being reprocessed immediately. You can also set the InputAgentRetryCount MBean to control how many times a job can be retried. The default is 3, after which the job is placed in the failed directory.

To troubleshoot any input file errors, do the following:

  1. Determine if the input file was a complete or partial failure by locating whether the file is in the Failed or Processed directory.

    The directory structure can be used by finding the input file under the appropriate date directory in the Processed or Failed directory. If the file is under the Failed directory, none of the indexes have been saved to Oracle I/PM and the error file should be examined for an exception from InputFilingMDB to determine why it was rejected. If the file is under the Processed directory, then at least one file was successfully indexed into Oracle I/PM.

  2. Check the Errors directory for the input file's error report. For every input file that had indexing issues, a matching file with the format of <original file name>.<MM-DD-YYYY>.<HH-mm-SS>.txt is created in the Errors directory. For example, the input file invoices.dat could have an error entry of invoices.dat.05-21-2009.16_36_07.txt. If no error report exists for the input file, a higher level issue such as a repository error could be the problem.

    If an error report does exist and the file shows a list of all lines for the original input file with an additional column at the end of the file displaying the error message. So, an original line of:

    C:\IBPM Data\WorkFiles\Filer\input\Images\C885|Identifier 165|27/06/2008|28215|495.75|

    would be listed in the error file as the following:

    C:\IBPM Data\WorkFiles\Filer\input\Images\C885|Identifier 165|27/06/2008|28215|495.75|Could not find file C:\IBPM Data\WorkFiles\Filer\input\Images\C885

    The error file also gives the results of a filing if information or a better logging level is enabled for Oracle I/PM. If the filing was placed in the processed directory, a log entry is created stating:

    Filing <Input Name> completed successfully with <indexed doc count> documents processed successfully out of <total doc count> documents.

    If the filing failed, then a log entry is created that states:

    An error occurred while completing a batch.

    Common causes of errors on a line by line basis are problems with proper formatting of metadata to be loaded, or invalid value ranges and truncation of data.

  3. Refer to the server's Oracle Diagnostic Logging (ODL) framework logs. The most common way to check this is via the Enterprise Managers's Log viewer for the imaging application. Typical problems here are from underlying repository or file permissions issues.