Schema Upgrade Guidelines

Upgrading a copy of the existing schema is a useful option if you are installing 25.1 on a new server machine. Creating a copy of the existing schema and then upgrading the copy enables you to work with new and upgraded projects.

Example:

If your OpenText Application Quality Management 12.00 schema contains a project called my_project, by creating a copy of the Site Administration 12.00 schema and then upgrading it to 25.1, the my_project project is available in Site Administration in both 12.00 and 25.1.

Oracle database servers: The new database schema is created in the same tablespace as the existing Site Administration database.

When you upgrade a copy of the existing Site Administration database schema, the copy that is created is independent of the existing schema. Any changes subsequently made to the original schema through updates in your previous version are not reflected in the upgraded copy of the Site Administration database schema that 25.1 uses.

Therefore, consider the following guidelines:

Users	After you install 25.1, if you add or delete users or update user details in your previous version, you must make the same changes in 25.1.
Configuration parameters	After you install 25.1, if you modify configuration parameters in your previous version, you must make the same changes in 25.1.
Server node configuration	If you are working with server nodes, in the Servers tab in Site Administration for 25.1, you must reconfigure the settings for the log file and the maximum number of database connections.
Repository path	The repository path in your previous version must be defined as a network path, so that it can be accessed by both the previous installations and by 25.1. Make sure that the project is active on one server but not on both.