This article makes the following assumptions. - You have a functioning ORDS installation and are familiar with how it was deployed. - You have a backup of the application server running ORDS. - You have a backup of the database(s) ORDS connects to. - The paths used in this article match those for the ORDS installation on Tomcat described here . If not, adjust to be consistent with your paths.

Stop the ORDS instance that is to be upgraded. The method of stopping and starting ORDS depends on the deployment method you have used. You can see how this is done in Tomcat and standalone mode below. - Starting/Stopping ORDS Under Tomcat - Starting/Stopping ORDS in Standalone Mode Either unzip the new ORDS software into a new folder, or unzip it over the top of the existing installation. The latter is safe as the config is held in a separate directory to the software. Update the "ords.war" file with the location of the existing config directory. You can actually miss out this step and you will be prompted for it when you start the installation, but I prefer to set it first. Run the installation, just like you would for a new installation. Since you've specified an existing config directory, the new version of ORDS will connect to the configured databases and check the version of ORDS installed. It will then prompt for the SYS password for each database so it can perform an upgrade of the ORDS objects, without affecting the existing metadata. These upgrades are typically very quick and don't require additional prompts. If you want to make it silent, use the same properties file you would for a conventional silent installation. If you specified a new config directory you will be prompted for the database connection details, just like a conventional installation, but ORDS will still upgrade any database objects that are already present. If you are running ORDS under an application server, you will have to redeploy the "ords.war" file before starting the application server. For Tomcat you would do the following. The upgrade and deployment is now complete, so start ORDS in the manner appropriate for your installation. - Starting/Stopping ORDS Under Tomcat - Starting/Stopping ORDS in Standalone Mode You can now test your existing applications and try any of the new functionality associated with the new ORDS release.

1
2
3
4
5
6
7
8
9

$ cd /u01/ords
$ unzip /tmp/ords-18.4.0.354.1002.zip

$ $JAVA_HOME/bin/java -jar ords.war configdir /u01/ords/conf

$ $JAVA_HOME/bin/java -jar ords.war

$ cd /u01/ords
$ cp ords.war $CATALINA_BASE/webapps/

If you have any problems after an ORDS installation or upgrade, it's always worth running an ORDS validate . For more information see: - Upgrading Oracle REST Data Services - Oracle REST Data Services (ORDS) : All Articles Hope this helps. Regards Tim...