The Upgrade Process › Review the Upgrade Tips

Review the Upgrade Tips

To ensure that your upgrade to this release works as planned, read the following preupgrade and postupgrade tips.

Preupgrade

• You must have the standard base calendar available in your CA Clarity PPM application before you upgrade. If you deleted the shipped calendar named Standard, create it before upgrading. Contact CA Support if your instance is missing the Standard base calendar.
• Process all "In progress" transactions into WIP.

  Verify the following conditions:

  • imp_transactionimport and ppa_transcontrol are clear.
  • WIP adjustments are approved.

  Review and fix all invalid transactions.

• Review Time Slices.

  Verify that the table is slicing out only the data that is required. If extra data is getting sliced, the database size increases and affects performance.

• Clear the Datamart and recreate the data post-upgrade to improve the processing time of the upgrade.

  Note: For Release 14.1, the Datamart is automatically cleared for Oracle.

  Use NBI_Clean_Datamart_sp to clear the Datamart. The script does not clear the following tables:

  • The configuration table (NBI_CFG%)
  • Time facts tables that contain historical information (NBI_PM_PT_FACTS and NBI_FM_PT_FACTS)

  After the upgrade, run the following jobs to repopulate the Datamart tables:

  • Datamart Extraction job
  • Datamart Rollup job
• Complete and put all processes on hold.
• Remove or delete process history, notifications, jobs, or logs. Look for items that you do not need to retain.
• Pause all scheduled jobs. Take special note of the Time Slicing job. Pause it before stopping the CA Clarity PPM services before the upgrade.
• To verify that all components are installed and functioning before and after the upgrade, run the CSA Health Report.
• Remove all CA Clarity PPM services before running the upgrade using the following command: service remove all.
• Verify that no files or folders in the installation folder are in use anywhere.
• See "Known Issues for 14.1" for conditions that can affect the success of your upgrade. Take any required corrective actions.

Post Upgrade

• Review the post upgrade report that the checkinstall utility generates.

  The files are zipped into an archive that has a timestamp-encoded name (for example, checkinstall-results_2014-08-17_16-48-31.zip). This file is located in the checkinstall/check-logs directory, and if possible, the file is copied into the <target runtime dir>/logs/checkinstall directory.

• Verify the performance metrics. During the upgrade, performance metrics are collected and the following files are written to the Logs folder:
  • ScriptMetrics.xml
  • Bootstrap.xml

  The files contain the following information:

  • A list of all upgrade scripts executed
  • The row count of every table that is processed by preupgrade and postupgrade processing
  • The execution time and results for each script or object
• Verify that Beacon is running to manage services and view logs.

  Note: Beacon must always run for Release 14.1.

• Ask your functional experts to review your upgraded test system side-by-side with a working preupgrade system.

  Tip: Use dual monitors for side-by-side comparison.

• Review the app-ca.log after the functional experts have used the test environment and look for new errors.
• Review any customizations: Customer-added database triggers, custom indexes and constraints, any file system changes, and custom interfaces. Review anything that did not come out-of-the-box. Adjustments may be necessary for customizations to work with this release.
• Review the system log file sizes. The log file size for all service system log files is set to 5 MB and to keep five rolling logs (for example, app-system.log, app-system.log.1). For more information, see the section named "Upgrade Considerations for Release 13.1."
• GEL Tag Restrictions: Release 13.1 gave the ability to restrict certain GEL tags in an environment. For more information, see the section named "Upgrade Considerations for Release 13.1."
• The Java Runtime Environment (JRE) is no longer available from the Clarity Software Downloads link. Review the supporting documentation and training materials you provide to your users. Wherever these materials direct users to download the JRE from within CA Clarity PPM, update the reference. Direct your users to download the JRE (Version 7) from www.java.com.
• Register any Portfolio Investment attributes that you want to display in portfolio pages. Although the required attributes display by default, you must register any other attributes (stock or custom) that you want to display.
• Remove the Resource - Edit Financial access right.
• The product supports Microsoft Project 2010 and 2013. If you upgrade and use one of these versions, update your Microsoft Project Desktop to ensure that data populates appropriately in Microsoft Project. Set the scheduling option to Automatic when you want to open the schedule in Microsoft Project.
• If your company policy does not allow resource managers access to the Financial Properties subpage for the resources they manage, you can remove that capability.

  Run a post installation script to perform the following actions:

  • Remove the Resource - Edit Financial access right from all current resource managers.
  • Clear the setting for the financial option that automatically grants the access right to new resource managers.

  Note: To maintain existing behavior, this right is granted during the upgrade. This right replaces the automatic right that was removed as part of the Financially Enabled Roles feature.

  Upgrade Action: (Optional) Run the script to remove the access right.

  Follow these steps:

  1. At the command line on the CA Clarity PPM server, change to the <clarity_home>/bin directory.

     The directory contains the dbpatch script.

  2. Run the following command:

     Windows:

     dbpatch -install -file ../upgrade/ppm/schema/postupgrade/RevokeResEditFinRightFromResourceMgrs.xml -apply
     

     UNIX:

     ./dbpatch -install -file ../upgrade/ppm/schema/postupgrade/RevokeResEditFinRightFromResourceMgrs.xml -apply