When an administrator upgrades their PowerDesigner client and then connects to an existing repository for the first time, they will be prompted to upgrade the repository. Until an administrator upgrades the repository, other users who have upgraded their PowerDesigner client will not be able to connect to the repository.
Context
Caution Always back up your repository database before upgrading it. Upgrading the repository typically creates many log entries, and you should consider increasing the log size to accommodate them.
Procedure
- If you have deployed PowerDesigner Web (see
Installing the PowerDesigner Web Server), you must stop the PowerDesigner Portal service before
upgrading the repository.
- If you have deployed the repository proxy (see Installing the Repository Proxy), we recommend that you stop the proxy
service before upgrading the repository.
- Open your upgraded PowerDesigner desktop
client and select to open the Connect dialog.
Only the PowerDesigner modules that are installed on your machine will be upgraded in the repository database. For example, if you do not have the Object Oriented Model installed on your machine, that part of the repository database will not be upgraded. For this reason, you should try to perform the upgrade from a machine that has all of the modules used by your organization installed.
- Select a direct repository definition from the list, enter your password, and click OK.
Note Upgrading the repository via the proxy is not supported.
- You are prompted to update the repository. Click Yes to continue and open the Repository Update Script dialog.
Depending on the size and complexity of your repository, this dialog may take several minutes to appear.
Note If you created your repository database with Microsoft SQL Server or SAP ASE before
PowerDesigner version 15.0, we recommend that you
select Rebuild clustered
indexes in this dialog to improve
performance, particularly for document check out. If
you do not select this option at upgrade time, you
can select at any time to perform the
rebuild.
- Click Execute to begin the repository upgrade.
The upgrade may take some time to complete. In the event of an upgrade failure due to network or permission problems, or insufficient disk space, you should restore the repository database from your backup version and retry an upgrade when problems are solved. If the upgrade fails because of the data in your database, then you should contact technical support for assistance.
- [when upgrading from a repository before v16.1] If your repository contains branches, you are prompted to update your branches to the new implementation (see Post-Upgrade Cleanup for a Repository Containing Branches). Click OK to continue.
Note Depending on the complexity of your branch structure and the size of your repository, upgrading your branches may take a considerable time. If you click Cancel at this point you will leave the repository in a stable state, and can relaunch the upgrade at a later point by reconnecting to the repository.
- [when upgrading from a repository before v16.1] If your current password does not comply with the default repository password policy, you will be prompted to change your password. Enter your new password (which must comply with all the rules listed in the dialog) and then click OK.
Note Administrators can control the restrictiveness of the password policy (see Core Features Guide > Administering PowerDesigner > Controlling Repository Access > Defining a Password Policy).
- The Library Synchronization dialog opens to prompt you to synchronize the contents of your local library. Make any appropriate selections and click OK to perform the synchronization and complete the repository upgrade.
For information about administering the library, see Core Features Guide > Administering PowerDesigner > Deploying an Enterprise Glossary and Library.
- If you are using the repository proxy, then you must upgrade it (see Installing the Repository Proxy).
- If you have deployed PowerDesigner Web, upgrade it using the
installer.
- If you have deployed the repository proxy, upgrade it using the installer.