How to migrate a VCM 7.6 configuration to another database server

* This procedure works for Content Suite 7.6

* The procedure applies in general to all databases but only tested on Oracle 10g. Please refer to the
database server documentation for instructions on exporting and importing
schemas/databases.

* This procedure assumes that you're relocating all the schemas from one host
to another, single host, not to multiple hosts.

* The steps also assume that you can change the listener port, SID (aka "instance"), hostname and schema name, password.

* Make sure you have a complete backup of the database and the file system
before performing any of these steps.

* Do not restart the VCM Server or any other VCM process while making these
changes until directed to do so in the last step.

OVERVIEW OF STEPS
–––––––––––––––––
This is the general sequence of steps you will follow:


1. In the VCM Configuration Console, change the database server settings to the
new values.

2. In the Runtime Services Admin Console, update the URL values for the
VgnPool and VgnPoolXA connection pools in "Services > JDBC > Connection
Pools".

 

3. Create a tablespace and user in the target database, export the user's
schema from the source database, and import it into the target database.

 

4 Update DBSchemaName in table VGNASRELATION if you change schema name.

MIGRATION PROCEDURE
–––––––––––––––––––
Follow these steps (please make sure that you follow the KB item recommended in
the Content Installation Guide to set up the new database):

1. In the source database, take note of the user's default and temporary
tablespace names and sizes. Be sure to include the user's role settings
(usually CONNECT, RESOURCE, and SELECT_CATALOG_ROLE). Please follow the KB
item recommended in the Content Installation Guide to set up the
appropriate database.

2. Create a tablespace and user in the target database.

3. Log in to the Configuration Console and navigate to Vignette Content >
Vignette Content Management Services > VCM Server > JDBC > Settings. These
are the settings for the VCM system database. Update the following
variables to match the new database coordinates:

* DATABASE_HOST
* DATABASE_PORT
* DATABASE_INSTANCE
* DATABASE_NAME
* DATABASE_USERNAME
* DATABASE_PASSWORD

4. Perform the following steps only if you have a split content database set
up against the Management Stage:

a) Navigate to the following node:

Vignette Content > Vignette Content Delivery Services > Content
Management Stage > Content Delivery Services – mgmt > Resources >
Resource Type – Databases > Resource – Appsvcs Resource > JDBC >
Settings

b) Update the following variables to match the new content database
coordinates:

* DATABASE_HOST
* DATABASE_PORT
* DATABASE_INSTANCE
* DATABASE_NAME
* DATABASE_USERNAME
* DATABASE_PASSWORD

5. Push configuration changes, and log out from the Configuration Console.

6. Log in to the Runtime Services Console and navigate to > JDBC > Connection
Pools settings:

a) Update the database information in the VgnPool and VgnPoolXA connection
pools.

b) If you have a split content database, update the database settings in
the Content Database Connection Pool.

 

7. Verify the settings in the configuration space in the Configuration Console
and the Runtime Services Console.

 

8. Export the user's schema from the source database, and import it into the
target database. If there are any errors, correct them before continuing
with this procedure.

9. If you have a split content database, export the database from your source
database and import it to the target database server.

10. If database schema has been changed, login to target database schema, update DBSCHEMA value in table VGNASRELATION.

11. If all the changes look right, restart the Admin Server, Node Manager,
VCM Server, and all the Configuration Agents.

 

This migratioin process has been tested on platform Oracle 10g, VCM 7.6.