Verifying the Upgrade

To verify the installation, perform the following tasks:

1. Open the ppm_upgrade.log file (located in the <PPM_Home>/upgrade_960 directory) and check for error messages at the end of the file.

   If your review of the ppm_upgrade.log file reveals errors, do the following. Otherwise, continue to the next step.

   1. Run the kSupport.sh script to gather information useful to Software Support in diagnosing system problems, and create a Zip file with a timestamp in the support/zipfiles directory. For information about the kSupport.sh script and how to run it, see the Installation and Administration Guide.

   2. Contact Software Support Web site (https://softwaresupport.softwaregrp.com/) and provide them with the Log.txt file produced by the kSupport.sh script run.

2. Open the DBChangeReport.html file (located in the <PPM_Home>bin\support\upgrade\output\etc\DBChangeCheck directory).

   The screenshot below is an example of the DBChangeReport.html file.

   

   After the upgrade process is finished, the system calls the supersupport tool and generates this DB change check report automatically. The report shows comparison results for triggers, indexes, and constraints. The comparison result table for each of the objects contains Missing and Custom parts. The Custom part for all tables can be ignored safely. In the Missing part, the lines with green background are also safe, which is for your reference only.

   If there are lines with white background in the Missing part, you may need to contact Software Support Web site (https://softwaresupport.softwaregrp.com/) for support. The lines with white background could cause potential issues, such as performance issue.

3. Log on to PPM.

4. Start the PPM Workbench.

5. Run a report.

6. Create a request.

7. Test the graphical view of the request.

If you encounter any problems, or have questions about the upgrade, visit the Software Support Web site (https://softwaresupport.softwaregrp.com/)