Installation and Upgrade › Upgrade Tips

Upgrade Tips

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

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, you must create it before upgrading. Contact CA Support if your CA Clarity PPM 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, that effort adds to database size and affects performance.

• Clear the Datamart and recreate the data post-upgrade to improve the processing time of the upgrade. 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.
• Run the CSA Health Report to verify that all components are installed and functioning before and after the upgrade.
• Remove all CA Clarity PPM services before running the upgrade using the following command: niku remove all.
• Verify that no files or folders in the installation folder are in use anywhere.

Post Upgrade

• 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 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 is required to be running always for Release 13.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 customizations: Customer-added database triggers, custom indexes and constraints, file system changes, and custom interfaces. Review anything that did not come out-of-the-box with CA Clarity PPM. Adjustments can be required for customizations to work with this release.