Shared Temp Directory in Linux Causes Display Failure Shifting Redaction and Other Annotations Logging of ImagingException

Troubleshooting 11-5 1. Look at the Errors directory in which the input file was placed and see if an error file was created. If an error file exists, then open it and examine the last column of the file to determine the specific error. 2. Examine the input file and verify that the path to the image file is accessible to the user that is running the Oracle IPM managed server and that the user has permissions to the path and image files. 3. Copy one of the failing input files to the samples directory and load it into the input definition editor UI. Verify that the mappings are correct and that one of the columns has not shifted. 4. Finally, look at the Oracle IPM log file and examine the errors that are listed for the individual lines to determine the exact cause of the problems. Once you have determined the cause of the error and are able to correct it, copy the corrected input file back into the input directory. For additional information, see Section 9.5, Checking Results and Error Files.

11.8 Advanced Viewer Transformation Errors

In cases where the advanced viewer applet experiences transformation errors, the first response is to delete temporary files on the users workstation. Doing so will remove the distribution of Oracle Outside In files which will cause a new deployment next time the applet is used.

11.9 Problems with TIFF Display in Viewer

The Advanced Viewer mode renders Group 6 and Group 7 TIFFs, while the Basic Viewer mode supports Group 7 but not Group 6 TIFFs. Group 7 TIFFs must conform to the TIFF standard for JPEG compression. Color images should use YCbCr for photometric interpretation or the image will be treated as a grayscale image. YCbCr is the standard color for JPEG images.

11.10 Shared Temp Directory in Linux Causes Display Failure

When using Oracle IPM in a multi-user Linux environment, ensure that individual temp directories are set up for each user. Using a temp directory shared among several users can cause the Advanced Viewer to delete temp files for one user that are necessary for another, causing a problem with documents not displaying. Ensure that each user has a temp directory created and configured as recommended by the operating system documentation.

11.11 Shifting Redaction and Other Annotations

Annotations are placed based on coordinates, and in some circumstances, content underneath the annotation may shift. This can be a particular problem when a redaction annotation shifts, potentially exposing sensitive information. For example, if a document contains text data and the font used in a document is not available to the Oracle Outside In rendering engine, then a suitable substitute will be used. Font substitutions can cause a document to be unreadable, create incorrect text formatting, or cause shifting of data and repagination on text documents, including potentially exposing redacted content. 11-6 Administrators Guide for Oracle Imaging and Process Management If annotations become misaligned and expose text they originally covered, ensure that a consistent set of fonts is being used across the servers and clients. For information on font errors, see Section 11.6, Font Errors.

11.12 Logging of ImagingException

By default, not all exceptions caught within Oracle IPM are logged. In the event that all exceptions need to be monitored, the following steps will help identify all exceptions thrown. Oracle IPM exception handlers do not inherit a log level from a parent logger oracle.imaging.service. To get exceptions from the core Oracle IPM services, you must explicitly set the logger named oracle.imaging.service.exceptions. To enable some degree of flexibility, it uses the following log levels: ■ ERROR 1SEVERE: Logs SYSTEM and DATABASE ImagingExceptions ■ NOTIFICATIONINFO: Logs SYSTEM, DATABASE, and SECURITY ImagingExceptions ■ TRACEFINE: Logs SYSTEM, DATABASE, SECURITY, and USAGE ImagingExceptions For example, all ImagingExceptions would be logged at throw time by setting oracle.imaging.service.exceptions to TRACE:32.

11.13 Tracking Events in the Oracle IPM and Oracle Content Server Log Files