Upgrading On a UNIX System

Perform the following steps to upgrade PPM to 9.60 on a UNIX system.

Note: "UNIX" is used to refer to all supported UNIX-based operating systems.

Note: (HP-UX only) Make sure that there is at least 2GB free disk space for the root directory. Otherwise you may receive a message similar to the following: "WARNING: / partition has insufficient space to install the items selected."

  1. (Documentum-based DMS only) If you use a Documentum-based document management system, make sure you upgrade your PPM to version 9.14 and then migrate the Documentum-based DMS to PPM Center Database DMS using the Administration Tool DMS Configuration before you upgrade PPM to version 9.20, then to version 9.30, 9.40, 9.50 and inally to version 9.60.

    For detailed instructions on how to migrate a Documentum-based document management system, see the Document Management Guide and Reference for version 9.20.

  2. Stop the PPM Server.

    Note: For information about how to start and stop the server, see the Installation and Administration Guide.

  3. Navigate to the <PPM_Home>/upgrade_960 directory:

    cd <PPM_Home>/upgrade_960
  4. Start an X Window session.

    Note: To run X Window System applications on a remote Unix or Linux system and have the graphics displayed on your Microsoft Windows workstation, you must run an X Window server on your workstation. If you need assistance with this, contact your system administrator.

  5. Run the upgrade script (as the SYSTEM user) and specify the upgrade mode.


    sh ./upgrade.sh [-swing|-console]

    where -swing represents the GUI-based mode (this requires an X Window session) and -console represents the interactive command-line mode.

    Note: Although the remaining steps describe the GUI-based upgrade steps, the information you are required to provide is the same.

    A language selection window opens.

  6. Select the language that you want the upgrade wizard to use to display steps, and then click OK.

    The upgrade wizard starts and displays basic requirements information.

  7. Click Next.

    The wizard asks if you want to check tablespace space availability before you continue.

  8. To check space availability for the tablespaces, in the Oracle System User Password field, type your Oracle system user password. To skip this check, leave the field empty.

  9. Click Next.

    If you provided your Oracle system user password, the upgrade tool displays information about the tablespaces created for the PPM schemas. If information about a tablespace is displayed in red text, that the available space is too small for this upgrade. We recommend that you quit the upgrade, resize the tablespace, and then restart the upgrade.

    Note: If any system tests fail, follow the prompts to fix the problem. After all temporary tables are reconciled, you can restart the upgrade. If you then encounter unexpected errors, visit the Software Support Web site (https://softwaresupport.softwaregrp.com/).

  10. Click Next.

  11. In the Password field, type the PPM schema password.

  12. Click Next.

  13. The wizard asks whether you want to run the prevalidation step. To perform prevalidation, leave Yes, I would like to run prevalidation step now selected, and click Next. To skip prevalidation, select No, I would like to skip the prevalidation step, and then click Next.

    Note: We strongly recommend that you perform this step as part of the upgrade. Prevalidation checks for data inconsistencies that might cause upgrade problems. For more detain, see About Prevalidation.

  14. If you run prevalidation:

    1. Review the PreValidationResultsIndex.html file, which is located in the <PPM_Home>/upgrade_960/logs/reports/html/integrity/validator directory.

      The report lists all issues that you must resolve before you can successfully upgrade to PPM 9.60.

    2. If prevalidation revealed problems, cancel the upgrade, resolve the problems, and then begin the upgrade again.

      Note: If you need assistance with this, consult your database administrator.

    3. If prevalidation revealed problems, click Next.

      Next, the upgrade utility:

      • Checks to ensure that the PPM Server is shut down.

      • Checks for old tables.

      • Determines the directories in <PPM_Home>/server to upgrade and lists these.

      • Lists the PPM Server or servers declared in the server.conf file, and which of these is to be upgraded.

      • Deletes records of services with both SERVICE_ID<10000 and history of exceptions from the PPM_SERVICE_RECORDS table.

        Note: Only records of customized services with history of exceptions are deleted from the PPM_SERVICE_RECORDS table as they can cause upgrade failure.

  15. Click Next.

  16. If the Directory Name field does not display the Java installation directory path, provide the path.

  17. Click Next.

    The system language selection step opens.

  18. From the list of supported languages, select your preferred system language.

    Note: The system language is the PPM default language for the installation. It is used as the default language setting for all regions (and by extension, all users). The system language is also the language used to generate system-level information such as server logs. For more information about the system language, see the Multilingual User Interface Guide.

  19. Click Next.

    The additional languages selection step opens.

  20. (Optional) Select the checkboxes for any additional languages you want to install.

    Note: If your organization includes staff in other countries who use this PPM instance, the additional languages you install enable them to work with PPM in their own languages (if supported). If you prefer not to install additional languages now, you can install them any time later. For more information about the session language, see the Multilingual User Interface Guide.

  21. Click Next.

    The wizard displays the current server mode (Stand-alone or Cluster) the PPM instance.

  22. Click Next.

    The wizard lists the current server configuration settings for the PPM Server and Tomcat server. The server configuration parameters listed for a stand-alone PPM Server are different (and fewer) than those listed for a PPM Server that is the primary node in a server cluster.

  23. If necessary, change the values for the listed parameter, and then click Next.

    Note: For descriptions of and valid values for these parameters, see the Installation and Administration Guide.

    The upgrade utility displays the directory path in which the upgrade is to be installed, and the total size (in MB) of the upgraded files.

  24. Click Next.

    The upgrade utility displays labeled indicators so that you can monitor the upgrade process.

    The PPM standard interface uses Java Server Page (JSP) technology to display dynamic content. Each page must be compiled the first time it is accessed, which results in a delay for users. This process can take several minutes

  25. To precompile all JSP pages now, leave Yes, I would like to compile all JSP files now selected. To skip this step, select No, I will let the server compile them at run-time.

    Note: We strongly recommend that you recompile the JSP pages during the upgrade.

  26. After the JSP files are all compiled, click Next.

    To improve system performance, the upgrade utility can generate statistics for the Oracle optimizer.

  27. To generate database statistics, leave Yes. Gather the statistics now selected. To skip this step, select No. I will gather the statistics myself later.

    The upgrade utility installs additional languages you selected (if any) in step 18.

  28. Click Next.

    After the upgrade is completed, the upgrade utility displays the upgrade log file path and asks you to check subsequent screens for information about what (if any) actions you need to take regarding the PPM Server.

  29. Click Next.

    The upgrade process checks the database tables and generates log files.

  30. After the upgrade is completed, click Finish.

  31. Start the PPM Server.

If you are upgrading a server cluster, see Upgrading a PPM Server Cluster for information on how to upgrade the remaining PPM Servers in the cluster.