My Oracle Support Banner

Tips On What To Check Before Running Propagation To Avoid Failure (Doc ID 1436053.1)

Last updated on JUNE 28, 2019

Applies to:

Oracle Knowledge - Version 8.2 and later
Information in this document applies to any platform.


This article provides tips on what you should check before running propagation to avoid failure.  In version 8.5 on the propagation bugs have been fixed. 

1. Always just ensure that no crawl jobs are running in the source or target environment before the propagation is performed.  Make sure that both indexers are up and running without errors.  If there have been errors then the indexers may need to be restarted.

2. When propagating from staging to production you want to ensure that the changes made are fully tested with a crawl and runtime activity in staging.

3. When propagating changes to production you will no longer have a copy of the old dictionary.  It can be good to first create a backup propagation bundle for the production system that can be restored if there are issues.  If there are extensive changes done and something was missed in prior environment testing then this can be a wise practice.  Then the dictionary and config changes can be quickly reverted.  There is no way to restore the old dictionary without a propagation bundle.  Some of the files can be looked at from a physical runtime backup, but a dictionary cannot be restored from these files.

How do I run a manual propagate? (Doc ID 1363077.1)

4. In general here are some things you can check to make sure that each instance is in good working order and the propagation will work.  If it does not work check these things.

a - The changes are made in dev and then a crawl is run to the index is tested to make sure that everything is in working order and the revisions are good and the config is good.
There are some config changes that need to have a crawl run before they are propagated. Dictionary changes just need to be tested.

b - The indexer has to be set up to propagate to the next environment and that connection has to work.
You can test this with a telnet from the source indexer ice prompt.
How do I configure Propagation from dev or staging to production? (Doc ID 1039371.1)
Check what is defined in the dev indexer staging directory env.xml file for the staging indexer host and port.
If you can telnet from the dev indexer than the connection should work.

c - Make sure that the staging indexer can run a crawl and is not having any issues. The staging indexer has to be in good working order.

d - If there is still a problem restart the indexers and make sure there are no errors in the indexer instance logs.

e - Make sure that any new passwords are accounted for in production in the custom.xml file.  A new password may need to be created if the keystore is different in each environment.

Rules concerning custom.xml, installation.xml, #.xml and their treatment in Synchronization and Propagation (Doc ID 1040808.1)


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

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