In Oracle iProcurement With ECC Enabled, Error Appears On the iProcurement Home Page - 400 Bad Request - Could not find a healthy node to handle the request - org.apache.solr.common.SolrException (Doc ID 2924558.1)

Last updated on JUNE 13, 2023

Applies to:

Symptoms

In Oracle iProcurement, with Enterprise Command Center (ECC) enabled, Release 12.2.4 and higher, an error appears on the iProcurement Home Page.



Error

400 Bad Request: {"title":"Could not find a healthy node to handle the request.","errorKey":"org.apache.solr.common.SolrException","stackTraceStr":"org.apache.solr.common.SolrException: Could not find a healthy node to handle the request.\n\tat org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1101)
..
..



The error also appears when running the full load for the iProcurement ECC Data Load process (Purchasing Super User responsibility > Reports > Run).
The following error can be seen in the concurrent request log file:

16:18:52.305 [pool-4-thread-2] DEBUG 6.o.e.i.u.s.i.IRDataLoadServiceImpl - startJob --> job 6040128 application icx, collection null was being served by pool-4-thread-2 for load type FULL_LOAD16:18:52.319 [pool-4-thread-2] DEBUG 6.o.e.i.u.s.i.IRDataLoadServiceImpl - true loadType FULL_LOAD -- null--604012816:18:52.319 [pool-4-thread-2] DEBUG 6.o.e.i.u.s.i.DataLoadControllerServiceImpl - loadDataForDataset --> application icx, collection icx-my-reqs was being served by pool-4-thread-2 for load type FULL_LOAD16:18:52.328 [pool-4-thread-2] ERROR 6.o.e.i.u.s.i.DataLoadControllerServiceImpl - Collection icx-my-reqs failed with error  There is an error while registering the collection  Collection icx-my-reqs Deletion -> Dataset icx-my-reqs deletion failed with error No live SolrServers available to handle this request, icx-my-reqs Collection  -> Dataset icx-my-reqs registration failed with error No live SolrServers available to handle this request16:18:52.339 [pool-4-thread-2] ERROR 6.o.e.i.u.s.i.DataLoadControllerServiceImpl - Error while rollbacking due to issue in collection registration org.apache.solr.common.SolrException: Could not find a healthy node to handle the request. at org.apache.solr.client.solrj.impl.CloudSolrClient.sendRequest(CloudSolrClient.java:1101) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:884) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:994) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:994) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:994) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:994) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.impl.CloudSolrClient.requestWithRetryOnStaleState(CloudSolrClient.java:994) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.impl.CloudSolrClient.request(CloudSolrClient.java:817) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.SolrRequest.process(SolrRequest.java:194) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.SolrClient.deleteByQuery(SolrClient.java:895) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at org.apache.solr.client.solrj.SolrClient.deleteByQuery(SolrClient.java:858) ~[solr-solrj-7.5.0.jar:7.5.0 b5bf70b7e32d7ddd9742cc821d471c5fabd4e3df - jimczi - 2018-09-18 13:07:58] at oracle.ecc.index.retrieve.solr.util.QueryExecuter.deleteByQuery(QueryExecuter.java:196) ~[ecc-ir-1.0.0.jar:na] at oracle.ecc.index.update.services.impl.IndexerImpl.rollback(IndexerImpl.java:141) ~[ecc-ir-1.0.0.jar:na] at oracle.ecc.index.update.services.impl.DataLoadControllerServiceImpl.loadDataForDataset(DataLoadControllerServiceImpl.java:582) ~[ecc-ir-1.0.0.jar:na] at oracle.ecc.index.update.services.impl.IRDataLoadServiceImpl.startJob(IRDataLoadServiceImpl.java:928) [ecc-ir-1.0.0.jar:na] at oracle.ecc.index.update.services.impl.IRDataLoadServiceImpl.tryToStartJob(IRDataLoadServiceImpl.java:540) [ecc-ir-1.0.0.jar:na] at oracle.ecc.index.update.services.impl.IRDataLoadServiceImpl.lambda$runLoadDataForApplicationWorkFlow$23(IRDataLoadServiceImpl.java:2146) [ecc-ir-1.0.0.jar:na] at java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1626) ~[na:1.8.0_141] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) ~[na:1.8.0_141] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) ~[na:1.8.0_141] at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_141]16:18:52.339



Steps To Reproduce

The issue can be reproduced at will with the following steps:
1. Log in to Oracle Applications.
2. Navigate to an iProcurement responsibility > iProcurement Home Page.
3. On the iProcurement Home Page, the error appears instead of displaying the iProcurement ECC-related information.

Changes

The issue occurs after having implemented ECC.

Cause

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