Last updated on SEPTEMBER 16, 2016
Applies to:Oracle Knowledge - Version 8.2 to 8.4.6 [Release 8.2 to 8.4]
Information in this document applies to any platform.
This article provides tips on what you should check before running propagation to avoid failure in releases prior to 8.5. In version 8.5 on the propagation bugs have been fixed. These steps are not needed in 8.5.
Always just ensure that no crawl jobs are running before the propagation is performed.
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)
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms