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
When investigating events in Oracle IPM, start with the Oracle IPM log files. In cases where the event occurs in Oracle Content Server, reviewing the Oracle Content
Server log files may provide additional information. Both Oracle IPM and Oracle Content Server logs can be viewed in Oracle Enterprise Manager. The Oracle Content
Server logs can also be viewed from the Oracle Content Server administrative links.
Tracing sections can be enabled in Oracle Content Server for more or less detail in the logging information. The IpmRepository component installed into Oracle Content
Server does not generate its own logging, but includes entries into the standard Oracle Content Server logs. Turn on tracing for the section named ipmrepos in Oracle Content
Server for detailed logging information of the IpmRepository component. For more information about Oracle Content Server logging, see Oracle Fusion Middleware System
Administrators Guide for Oracle Content Server Finding Error and Status Information.
11.14 Using Oracle Dynamic Monitoring System with Oracle IPM
Oracle Dynamic Monitoring Service DMS can display statistics of your system using the Oracle DMS Spy application to aid in troubleshooting and diagnostics. The Oracle
DMS Spy application is launched by entering http:machine_name:portdms into your browser URL address field. The following metric tables are available:
Metric Table Description
IPM_API Records timing statistics on imaging API operations. Statistics
are recorded on a per service operation basis.
Troubleshooting 11-7
11.15 Reviewing Audit History of Deleted Documents
If documents are deleted from Oracle IPM, administrators can view the entry for the delete action in the Oracle Content Server DocumentHistory table. This is the only
place for administrators to view audit entries for deleted documents.
11.16 Deciphering Nested Stack Errors
