Starting SES Fails With Error "Mid Tier not ready in 2 minutes. Retrying..."
Last updated on NOVEMBER 01, 2016
Applies to:Oracle Secure Enterprise Search - Version 10.1.8.4 to 10.1.8.4
Information in this document applies to any platform.
***Checked for relevance on 08-Aug-2013***
-- Problem Statement:
When using the searchctl startall command (or other variations) to start (or restart ) SES the job attempts to verify the midtier has started and indicates this failed after 2 minutes, then again after 6 minutes and then failed 1 retry attempt.
The error is as follows:
Search midtier started...
Administration Tool -> http(s)://<hostname>:<port>/search/admin/index.jsp
Search page -> http(s)://<hostname>:<port>/search/query/search
Checking whether the Mid Tier is in Ready state...
This might take some time.
Mid Tier not ready in 2 minutes. Retrying...
Mid Tier not ready in 6 minutes. Retrying...
Mid Tier is not ready in Attempt: 1Retrying...
Retry Attempt: 1 failed
Mid Tier is not ready in Attempt: 2Retrying...
Retry Attempt: 2 failed
Mid Tier is not ready in Attempt: 3Retrying...
Retry Attempt: 3 failed
oracle.search.config.OESException: Error while executing action: "startall"
Caused by: oracle.search.config.OESException: ... Unable to start Mid Tier or Mid Tier not in ready state
But, you can verify that the server is actually up because you can go to the admin URL as well as the search URL and retrieve the pages :
Admin Tool -> http://<hostname>:<port>/search/admin/index.jsp
Search page -> http://<hostname>:<port>/search/query/search
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms