WLP Upgrade to Latest Versions Cause Too Many Database Calls For Content Selector Or Content Search Query (Doc ID 1312701.1)

Last updated on JANUARY 06, 2025

Applies to:

Symptoms

After upgrading WLP to 10.3.x versions and whilst running a content search query or using content selector, the resulting SQL query produced is being executed in the database several times for a single request. Under heavy load the performance of the database is adversely affected by these additional SQL executions.

To illustrate this: the following content query, when executed once using the API below, will result in 3 hits on the database:

String queryString = "(toProperty('WLP Repository/File', 'Name') == 'FileTest') && (toProperty('WLP Repository/File', 'production') == 'true')&& (toProperty('WLP Repository/File', 'startDate') == toDate('yyyy-MM-dd HH:mm:ss z', '2011-02-16 08:00:00 GMT')) && (toProperty('WLPRepository/File', 'endDate') == toDate('yyyy-MM-dd HH:mm:ss z', '2011-02-16 20:00:00 GMT')) &&(toProperty('Standard', 'cm_isContent') == true)";

com.bea.content.expression.Search search = newcom.bea.content.expression.Search(-1, expression);
com.bea.content.federated.ISearchManager searchManager =com.bea.content.federated.ContentManagerFactory.getSearchManager();com.bea.content.paging.ISortableFilterablePagedList<com.bea.content.Node>nodePagedList = null;
nodePagedList = searchManager.search(context, search);

Sample multiple DB Queries generated while using default WLP Repository::
=======================================================================
SELECT DISTINCT CM_NODE, NODE_ID FROM CM_NODE, CM_PROPERTY A1 WHERE CM_BODE,NODE_ID AND CM_NODE.LIFECYCLE...

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.