When restoring the Change Management model, it is imperative that you do not deviate from the recommended workflow.
Before you restore the catalog, catalog schema, and model databases, make sure that you have used the to restore the site and site schema databases. See Restore a site database.
-
Click Tools > Restore Command to open the Restore Wizard.
-
Select Restore one or more model databases from backup, and then click Next.
-
In the Backup configuration file to restore box, specify the location of the backup configuration .bcf file. If you are running Oracle on a Linux computer, the .bcf file must be on a Windows-based computer.
-
In the Models to restore section, select the model to restore.
-
For SQL databases, verify or redefine the server and file path where the database backup files are in the Server and Database Backup Files Path columns.
For Oracle databases, verify or redefine the Oracle net service connection and file path where the database backup files are in the Service and Database Backup Files Path columns. When using an Oracle Linux environment, the database backup location must be on the Linux computer where the Oracle service is running. You must also type the Linux folder location. Browse (...) is not available for navigating to Linux folder locations.
-
In the Paths for new databases section, select the database type in the Type column. You must restore the catalog database before you restore the model database.
-
For SQL Server databases, specify values for Server, Database Path, and Log Path.
For Oracle databases, specify values for Server, Database Path, and Index Tablespace Path.
The software automatically displays the database default paths on the selected server/service.
-
Specify the path for Symbol and custom file location. If you are running Oracle on Linux, the SharedContent folder must be on a Windows-based computer.
-
Specify the server for Name generator server for model.
-
Click Finish.
The software displays a warning that a catalog database with the name that you have specified already exists in the server location. You can leave the existing catalog in place (that is, link it to the restored model) or restore the catalog database from the backup.
-
Click No to also restore the catalog from backup.
-
When the restore is complete, click OK and view the log file.
-
The software names each restored database with the same name that the database had before you backed up the files.
-
After restoring, you can check the name generator server on the Databases tab of the Model Properties Dialog.
If you are using Oracle databases, run the Oracle Role Creation Utility to define specific user roles for each schema or collection of schemas if needed.