Synchronization Step Fails When Running the Crawl Because Indexer Can Not Connect to a Runtime
Last updated on JUNE 27, 2018
Applies to:Oracle Knowledge - Version 8.6 and later
Information in this document applies to any platform.
Sometimes the indexer cannot complete a synch task because one of the runtimes is in a bad state and cannot be synched to. This runtime could be down and not processing requests correctly. Other runtimes might be up and running correctly. The business impact is that the crawl cannot put out a new index and the runtime is offline.
The runtime connection is defined in the env.xml when the runtime is installed. From the indexer ice prompt you should be able to connect to the runtime port through a telnet command.
The connection for the synch is defined in the env.xml file. There is also a gateway connection string in each installation.xml file that is used internally by the components of the software on that machine. This xml is used to set up gateway logging for request response processing. There is no other connection information for the search code. The runtime url is also in the IM / IC config.properties file for connecting to the runtime for a search request.
These files can be change and the instances restarted.
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