Upgrading Oracle Hospitality Cruise Property Management
If you already have a previous installation, follow these steps to upgrade the program. You would need an Administrative privilege to perform this task.
-
Locate the
installer.propertiesfile in the previous installation folder. -
Copy the
installer.propertiesfile into the folder where latest CruisePropertyManagement_23.3.x installer is located. This is to ensure the previous settings like database connections, installation paths, and other configurations are retained. -
Start the installation program by right-clicking the CruisePropertyManagement_23.3.x.exe and select Run as Administrator. The data of previous setup will pre-populate when the condition above is met.
-
Click Upgrade to begin and follow the instructions on screen.
-
At the end of the installation, the previously installed version is replaced with the latest features, fixes, and updates included in this release.
Downgrade Prevention
Note:
SPMS 23.3.1 Oracle Hospitality Cruise Property Management installer provides integrated database scripts to upgrade all Cruise Property Management Web Applications, as long as your SPMS database is version 23.1.3.0 or higher. If you are running an earlier version, you must upgrade the database using the SPMS Desktop Application before proceeding.-
Database scripts are executed only when the API feature is selected during installation.
- Prior to running any scripts, the installer verifies database connectivity. If a connection cannot be established, the installation will be terminated.
- If the script fails or encounters error during execution, the installer logs the
error, notifies the user, and continues to execute the remaining scripts. Error logs
are stored at
C:\Users\Public\Documents\Oracle Hospitality Cruise\ErrorYYYYMMDDHHMMSS.txt. - Upon completion of the installation, the System, SPMS REST API Database Values Version parameter (refers to OHC Administration – Database Parameter) is updated to indicate the version of the executed scripts. This is used for tracking purposes only.
- During uninstallation, only the application components are removed; database changes made by previously executed scripts are not rolled back, consistent with the current OHC Database Installer behavior.