Copy the upgrade tools and files to each server before you start the upgrade.
The Prinergy Update tools and files are available on the Prinergy Upgrade DVD, or from Partner Place at https://partnerplace.kodak.com/ .
Make sure you have the installation files as well as the Oracle upgrade files.

Tip: Visit the Kodak services and support portal regularly for new and revised Prinergy documentation and downloads. If you are not yet a registered user, you can register online at https://partnerplace.kodak.com/.

1. On a local drive with at least 10 GB of free space, create a folder called Updates.
   The Data drive (typically drive J) usually has adequate space. If the Data drive does not have enough space, or a Data drive does not exist on the server, you can use the System drive (typically drive C).
   Tip: You can use the Disk Cleanup Tool to free up space on Prinergy system drives. It is available on the primary server at Start > Kodak > Prinergy Support Tools > Prinergy Disk Cleanup Tool. If you do not have this tool, you can download it from the Kodak services and support portal.
2. Download the installation files from the Kodak services and support portal to the Updates folder. The files include:
   • PreCheck.exe
     Note: Unzip the PreCheck tool ZIP file to access the two files: PreCheck.exe and PreCheck.py.
   • PreCheck.py
     Note: Unzip the PreCheck tool ZIP file to access the two files: PreCheck.exe and PreCheck.py. 
   • The Prinergy upgrade .exe file (for example, Prinergy_9.0.0.BLD123.exe)
   • The Prinergy upgrade ZIP file (for example, Prinergy_9.0.0.BLD123_part2.zip) which needs to remain zipped and in the same location as the .exe file
   • The Oracle 19 installer folder named Oracle_19.0.0_x64 which contains two folders: OracleClient_19.0.0.0_x32 and OracleServer_19.0.0.0_x64
     Note: The downloaded Oracle ZIP file must be unzipped to provide the Prinergy installer access to the Oracle install files.
3. Repeat steps 1 and 2 for each server in your system.
   Important: When upgrading a secondary server, upgrade the primary server first. This is particularly important for a secondary server configured as a Hot Standby (EPM+) failover server.
   Ensure that you copy the installer files to each server. Do not copy them to the primary server and then map a drive from each secondary server to connect to the shared folder. If you do this, and the primary is restarted or disconnected during the upgrade of a secondary, the upgrade will fail.