IBM Support

Image Services: How can I terminate the INX_export process ?

Question & Answer


Question

When federating metadata from FileNet Image Services to FileNet Content Engine, it is possible to generate a long query on the Index Database that does not return. The long queries are caused by federating too many documents at one time. This causes the INX_export process to run until the FileNet Image Services software is recycled. To prevent the Image Services software from being restarted, a new option, -t, has been added to the INX_export process that allows for the process to be terminated The FileNet Image Services sofware has seen this type of behavior since Oracle switched from Rules Based Optimization to Cost Based Optimiztion. Sites that federated 5 millions rows at once reported a full table scan on the Index database occurring. The issue was resolved by scripting the INX_export process and federating 1 million rows at a time.

[{"Product":{"code":"SSNVUD","label":"FileNet Image Services"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Component":"Image Services","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"4.2;4.1.2","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:
29 April 2025

UID

swg21620768

Page Feedback