Version 2.9.00 introduces a new feature for Dbvisit Replicate. The dbvrep repository may now optionally be stored outside of the source database. Although this option (using external metadata repository) is available, it is recommended to use the default option of having the dbvrep repository in the source database whenever possible. The dbvrep repository may be stored in another Oracle database, this is typically done if there are license limitations on the source databases that you are replicating. An XE database would suffice. Dbvisit Replicate will then store all of the metadata regarding the source database within the dbvrep schema in the repository database. Connections will be made to both databases.
Please note that if this option is used the external repository MUST be a different database other than source and target, If the external repository is given as either source or target the ALL script will FAIL.
In Step 1 of the Setup Wizard there is an question regarding which database you want to have the repository in:
Dbvisit Replicate user dbvrep is recommended to store metadata. It is also possible to store metadata in another (non-source) database. Store Dbvisit Replicate metadata in unitsrc database? This is a typical / recommended configuration. (Yes/No) [No] Yes
After you have configured the source and target in Step 1 the output will look like this.
Following databases are now configured: 1: Oracle SOURCE_DB, SYS/***, SYSTEM/***, dbvrep/***, /, dbvrep/, ASM:No, TZ: -07:00, Metadata stored in REPOSITORY_DB#DBVREP 2: Oracle REPOSITORY_DB, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:No, TZ: +00:00, Metadata-only database for SOURCE_DB#DBVREP 3: Oracle TARGET_DB, SYS/***, SYSTEM/***, dbvrep/***, USERS/TEMP, dbvrep/, ASM:No, TZ: -07:00
There is now a third database, Repository_DB in this case, will be a metadata-only database for the purpose of storing the repository.