• Download ORDS version 20.2.1 or later from Oracle REST Data Services Downloads.
• Extract the ORDS SQL scripts.
• To obtain the ORDS SQL scripts, execute the following commands:

  
  unzip ords.version.number.zip ords.war 
  unzip ords.war 'WEB-INF/lib/ords-installer-*.jar'    
  unzip  'WEB-INF/lib/ords-installer-*.jar' 'db/*'    
  mv db scripts

1. Connect to the application root container.
2. Run /path/to/scripts/install/core/ords_app_con_install.sql command using the following parameters:
   • Log folder (must include the forward slash at the end)
   • Default tablespace for ORDS schema
   • Temporary tablespace for ORDS schema
   • Default tablespace for ORDS proxy user
   • Temporary tablespace for ORDS proxy user
   • ORDS proxy user password
   • Scripts path (requires the fully qualified path to the ORDS scripts)

   Note:

   The tablespaces must already exist in the database.

• The ORDS schema, ORDS_METADATA
• The ORDS proxy user, ORDS_PUBLIC_USER and
• The related database objects in the application container

1. Ensure that the current container is in the CDB$ROOT.
2. Alter session and set container to the application root.
3. Use the AS SEED clause of the CREATE PLUGGABLE DATABASE statement to create an application seed.
4. Sync the ORDS application with the application seed.
5. Compile invalid objects.
6. Open the application seed in a read only mode.

ALTER SESSION SET CONTAINER = ords_app_root1;
CREATE PLUGGABLE DATABASE AS SEED ADMIN USER admin IDENTIFIED BY <admin_password> 
FILE_NAME_CONVERT=('pdbseed', 'ords_app_root1_seed');
ALTER PLUGGABLE DATABASE ords_app_root1$seed open;
ALTER SESSION SET CONTAINER = ords_app_root1$seed;
ALTER PLUGGABLE DATABASE application ORDS sync;
begin
  sys.dbms_utility.compile_schema('ORDS_METADATA', FALSE);
end;
/
ALTER PLUGGABLE DATABASE ords_app_root1$seed close immediate;
ALTER PLUGGABLE DATABASE ords_app_root1$seed open read only;

1. Ensure that the current container is in CDB$ROOT.
2. Alter session and set the container to the application root.
3. Use the CREATE PLUGGABLE DATABASE command to create a PDB from the application seed.

ords --config <configuration folder> config set plsql.gateway.mode proxied

• Standalone Mode
• Deploy on Oracle WebLogic Server
• Deploy Oracle REST Data Services on Apache Tomcat

• ORDS must already be installed in the application container.
• Upgrading ORDS from an earlier release to a new release.

1. In SQLcl or SQL*Plus, connect to the application root.
2. Run /path/to/scripts/upgrade/ords_app_con_upgrade.sql with the following parameters:
   • Log folder (must include the forward slash at the end)
   • Scripts path (requires the fully qualified path to the ORDS scripts)

   Note:

   The ords_app_con_upgrade.sql script upgrades ORDS in the application root container to the release that you are using. For example, if the ORDS application version is 20.2.1.r2121800, and the ORDS upgrade script is 20.3.0.r2601900, then the script upgrades ORDS to release 20.3.0.r2601900 in the application root container.

1. In SQLcl or SQL*Plus, connect to the application root.
2. Run /path/to/scripts/uninstall/core/ords_app_con_uninstall.sql with the following parameters:
   • Log folder (must include the forward slash at the end)
   • Scripts path (requires the fully qualified path to the ORDS scripts)

1. In SQLcl or SQL*Plus, ensure that the current container is the application PDB.
2. Run the ALTER PLUGGABLE DATABASE APPLICATION statement specifying the ORDS application with the SYNC clause.

• Manually inspect the following log files for any errors:
  • Install - ordsinstall_<timestamp>.log
  • Upgrade - ordsupgrade_<timestamp>.log
  • Uninstall - ordsuninstall_<timestamp>.log
• Query dba_applications to verify if the ORDS application exists and its application version is the same as the ORDS product version.

  SQL> select app_name, app_version, app_status from dba_applications where app_name = 'ORDS';
      
      APP_NAME     APP_VERSION         APP_STATUS
      --------     ---------------     ------------
      ORDS         20.2.1.r2121800     NORMAL

• Query dba_app_errors to check for any errors:

  SQL> select app_name, app_statement, errornum, errormsg from dba_app_errors where app_name = 'ORDS';

  no rows selected

  If you are uninstalling ORDS from the application container, the APP_STATUS contains the value UNINSTALLED.