ECC DataLoads Are Failing With Error Message: "SolrException: Could not find a healthy node to handle the request"
(Doc ID 2984724.1)
Last updated on JANUARY 09, 2025
Applies to:
Oracle Enterprise Command Center Framework - Version 12.2.9 and laterInformation in this document applies to any platform.
Symptoms
While performing Full Data loads after the EBS database is refreshed from production to non-production, loads fail with error message "SolrException: Could not find a healthy node to handle the request"
The following error messages were reported in the solr.log file:
2023-10-20 21:52:59.305 ERROR ([ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)') [ ] o.a.s.s.SolrDispatchFilter Could not start Solr. Check solr/home property and the logs
2023-10-20 21:52:59.323 ERROR ([ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)') [ ] o.a.s.c.SolrCore null:org.apache.solr.common.SolrException: Error occurred while loading solr.xml from zookeeper
Caused by: org.apache.solr.common.SolrException: Unknown configuration value in solr.xml: allowPaths
at org.apache.solr.core.SolrXmlConfig.fillSolrSection(SolrXmlConfig.java:279)
2023-10-24 11:55:03.750 ERROR ([ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)') [ ] o.a.s.s.SolrDispatchFilter Error processing the request. CoreContainer is either not initialized or shutting down.
The issue can be reproduced at will with the following steps:
1. In Non-production, EBS database is refreshed from production.
2. After EBS application started, Invoke ECC concurrent data loads to load fresh data
3. It is failing with solr services startup
Changes
The EBS database is refreshed from production environment.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |