IBM Support

Extraneous indexes using rawtohex() degrade Content Engine performance.

Troubleshooting


Problem

Creating Oracle indexes on any column using rawtohex() is never necessary for the Content Engine (any version), and having them present only reduces ingestion, and update and delete performance. At SQL execution time, the CE binds ID data using setBytes() so that Oracle is passed the same datatype as the underlying column. The default indexes created by the CE will be used by the CE for any eligible ID predicate without any need for an index to include rawtohex(). The reason such indexes may have been erroneously added is explained here, as well as the proper method to issue direct SQL.

Symptom

Slow ingestion performance.

[{"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":"5.2.1;5.2.0;5.1.0;5.0;4.5.1;4.0.1;3.5.2","Edition":"All Editions","Line of Business":{"code":"LOB76","label":"Data Platform"}},{"Product":{"code":"SSGLW6","label":"IBM Content Foundation"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Content Engine","Platform":[{"code":"","label":""}],"Version":"","Edition":"","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

swg21469817