My Oracle Support Banner

Process for manually copying the vcroot from one instance to another (Doc ID 1039755.1)

Last updated on NOVEMBER 30, 2019

Applies to:

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

Symptoms

The Dictionary objects are stored in a SVN called vcroot.  The location of the vcroot in dev is different from staging and production.  The supported process for doing dictionary work is to do it in dev, using testdrive for testing, and then to move the vcroot from dev to staging for additional testing through the propagation process.  There are times when someone modifies something in another environment and that modification needs to be moved back to dev.  The vcroot can be moved and copied over another vcroot.  However other changes in that target environment will be lost.

Process for manually copying the vcroot from one instance to another can be used in recovery or abnormal situations.  If you cannot propagate using a system manager job, then we also recommend that a manual propagation be used.  This procedure should only need to be done in very limited situations of recovery.

Because changes are made in Dev and the propagated and tested in staging when they are propagated to production the old version of the dictionary (vcroot) will no longer exist.  Before propagating to production it may be desirable to back up the vcroot on production in case it needs to be restored.  This can be done by copying the following directory and all of its subdirectories to a safe place of backup. 

These instructions define to to restore a backup or a dictionary from another system.

Cause

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
Symptoms
Cause
Solution
References

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