Cloning EBS Causes ‘No live SolrServers available’ Error

This specific `SolrServerException` often occurs after cloning because the ECC instance loses synchronization or trust with the newly cloned EBS database or configuration, especially if hostnames or database service names changed . To resolve this, you must first clear the ECC configuration details specific to the dataset statistics, which are often tied to the old environment . More importantly, you need to recreate the JNDI connection to the new EBS database .

To fix the JNDI connection post-cloning, you must follow the steps detailed under the section ‘Configuring the JNDI to Connect to Oracle E-Business Suite’ in the ECC documentation . This process typically involves regenerating the DBC file specifically for the ECC host system on the EBS application node, copying it to the ECC server as `connection.dbc`, and then running the appropriate configuration script (like `envSetup.sh` option 4) to update the `ebsDB` datasource , .

After successfully updating the JNDI configuration, you must bounce (restart) the ECC services . Restarting the ECC managed server ensures that the Weblogic domain picks up the updated database connection details and re-establishes the necessary connectivity to the cloned EBS environment, making the Solr servers available again .

If you are using RAC with SCAN listeners, it’s a known issue that they can cause problems during ECC setup . It is recommended to manually replace the SCAN entry with the Virtual IP (VIP) address in both the `EccConfig.properties` file and the generated `connection.dbc` file . This step circumvents potential SCAN resolution issues and ensures the JNDI creation is successful .