IBM Support

Enabling Oracle Date Index Use in the FileNet Content Engine

Troubleshooting


Problem

Creating an index on a DateTime property in the FileNet Content Engine 4.x requires some additional steps to be taken when using an Oracle database. The Content Engine creates DateTime properties using the Oracle Date data type and, in the CE version 4.x, accesses the database using JDBC. However, due to a bug in the Oracle JDBC driver introduced in Oracle 9, indexes on date columns are not used by the Oracle query optimizer. This technote details a workaround by setting a JDBC connection property. The issue may also be resolved according to Oracle by patching both the Oracle server and the Oracle JDBC driver to version 11.2.0.2 or higher, which testing has confirmed.

Symptom

Indexes on date properties are not used in a query plan by the Oracle query optimizer, resulting in slow searches on those properties for a large table.

[{"Product":{"code":"SSNVNV","label":"FileNet Content Manager"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Content Engine","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.5.1;4.5;4.0.1;4.0","Edition":"All Editions","Line of Business":{"code":"LOB76","label":"Data Platform"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
28 April 2025

UID

swg21397282

Page Feedback