Prior to migrating to another database, ensure that you have allowed enough table space for the database. Twenty data files
of 1 GB each is a good foundation. If the tablespace size is too small, the database continues to extend the tablespace, reducing
the performance.
Create a backup of the database you plan to migrate. Also ensure that you have backups of the files and folders in the server
configuration repository.
Ensure that the database to be migrated is still in good repair by doing one or both of the following:
Run Vault Verify.
Run any verification tools provided by your database vendor.
Do one of the following:
Manually create a database or schema user as the recipient of the migrated data. See the
StarTeam Installation Guide for details. Make sure that you note the names provided for the server name, and the user name and password for the database
or schema user. At a minimum, this user must have permission to create tables and stored procedures (if the database supports
stored procedures).
Use the
Server Administration tool to automatically create a database or schema user as the recipient of the migrated data.
Plan the database migration for a time at which it will inconvenience few users. A server configuration cannot be running
while the database is being migrated.
Advise team members ahead of time that you plan to make the transition, let them know the time at which it will take place,
and request that they check in their files.