Prinergy System Admin Guides 9.5

Space shortcuts

Page tree

Before beginning the upgrade, ensure that your system meets the requirements.
Do not attempt the upgrade if your system does not meet all of the following requirements:

  • Your current Prinergy version is 7.5.0 or later.
  • If upgrading from 7.0.1 or earlier, you have your Prinergy software-based License ID (used for retrieving your new license during the upgrade installation).

    • Note: If you are upgrading from Prinergy 7.0.1 or earlier, then two migrations of your Oracle database will be required. First, to go from the Oracle 11 integrated with the earlier version of Prinergy to Oracle 12.1 integrated with Prinergy 7.5 up to 8.2, and then to the Oracle 12.2 integrated with Prinergy 8.4. Oracle 19 is integrated with Prinergy 9.5, but allows for an in-place upgrade of 12.2, rather than requiring the Prinergy database to be exported and reimported during upgrade.

  • Your operating system is Windows 2016.
  • The system has been backed up within the last 24 hours; or, for virtualized systems, you have made a VM snapshot of the system within the last 24 hours.
  • You are able to allow sufficient down time for the upgrade.
  • Your setting for Language for non-Unicode programs in Region and Language > Administrative tab is set to English (United States).
  • No rule sets are stored in the system group folders Prinergy System, Sample Rule Sets, and OPS Sample Rule Sets. The upgrade overwrites these folders.
  • The system has sufficient free disk space on the System and Data drives. Use the Preinstallation Check (Precheck) tool to check for disk space requirements. The new Prinergy Workflow installer also checks if sufficient disk space is available before beginning the upgrade.

  • No external USB drives (including Kodak service drives) or additional internal drives are connected to the server during the installation. Having additional drives connected to the server may affect the installation of Prinergy’s Oracle 12.2 database. The only drives that should be configured on the server before the upgrade starts are C and J.