What You See Is What You Get Element

Release Notes

Date: December 2017

Oracle REST Data Services on OTN | Downloads | Forum



  • You are supported by Oracle Support under your current Oracle Database or Oracle NoSQL Database Support license for Oracle REST Data Services production releases.
  • Log Oracle REST Data Services bugs and issues using My Oracle Support.

    • For problems specific to SODA for REST, file a service request using "Oracle XML Developers Kit" as the product.
    • For all other problems, use "Oracle REST Data Services" as the product.


  • Documentation for this release is provided on the OTN web site. Click here to view the documentation.
  • Documentation on using SODA for REST is provided on the OTN here.

Getting Started

  • A tutorial on getting started with developing RESTful Services is included in the product documentation, in the book titled 'Oracle® REST Data Services Quick Start Guide'.


  • You can discuss issues on the forums.
    • Be sure to use clear subject lines to initiate a thread. Provide a complete and clear description of the issue, including steps to reproduce the issue.
    • Try to avoid using old, unrelated threads for a new issue.

Important Changes to Note

Change in Product Versioning Scheme

Oracle REST Data Services is aligning with the release numbering scheme used for Oracle Cloud Services. Going forward, releases will be numbered by Year.Quarter.PointVersion. Expect a new release each quarter.

Supported Java Version

Oracle REST Data Services requires Java 8. Java 7 is no longer supported. See the note in the known issues section about Java 9 support. Please consult the documentation for the minimum supported Application Server versions.

REST Enabled SQL

It is now possible to POST SQL and JSON payloads to ORDS (restricted to appropriately authorized users), these scripts are parsed and executed by the same engine that powers Oracle SQL Developer and Oracle SQLcl, and the output is returned in a rich JSON document

Note: Enabling the REST Enabled SQL service enables authentication against ORDS enabled database schemas. This makes the database schemas accessible over HTTPS using the database password. Oracle strongly recommends that you use unguessable secure database passwords.

Open API 2.0 Support

In ORDS 3.0.x a propietary format was used to describe Resource Module and AutoREST enabled resources. In 17.4 and later this format has been superceded by resources using the Open API 2.0 (aka Swagger) syntax.

Deprecation of Glassfish Support

While 17.4 continues to support Glassfish (4.1.2 and later), support for Glassfish will be removed in a future release. Use of Oracle WebLogic , ORDS Standalone Mode or Apache Tomcat is recommended instead.

Changes in 17.4.1

The following changes and enhancements have been mae since 17.4.0:

Issues Fixed in 17.4.1

  • BUG: 27282496 - Fix error during install: ERROR DURING COMPILATION: PACKAGE ORDS_MIGRATE ORA-24344


Changes in 17.4.0

The following changes and enhancements have been made since 3.0.11:


Issues Fixed in 17.4.0


  • BUG:27153303 - Change installer to prompt for SYS user password, instead of misleading prompt for any SYSDBA user, which only works on 11.2 or earlier
  • BUG:27122800 - Rework OAuth UI to use Oracle JET
  • BUG:26992910 - Include APEX REST Services migration logic in schema install
  • BUG:26839669 - Address handling of CLOB strings in REST Enabled SQL
  • BUG:26830673 - Ensure error message is displayed on startup if a pool is misconfigured
  • BUG:26800638 - Fix regression introduced in 17.3 Beta that prevented PDF functionality in APEX working
  • BUG:26790372 - Fix issue with result values in REST Enabled SQL
  • BUG:26731570 - Upgrade to Apache XML Graphics 2.2
  • BUG:26731475 - Upgrade to Apache FOP 2.2
  • BUG:26718269 - Address ORA-01000: Maximum Open Cursors Exceeded when using Application Express 4.2
  • BUG:26720712 - Fix regression introduced in 17.3 Beta that caused a stacktrace to be displayed when shutting down ORDS in standalone mode
  • BUG:26735250 - Fix regression introduced in 17.3 Beta that caused some describes links in metadata-catalog to give 404 Not Found status
  • BUG:26735352 - Fix regression introduced in 17.3 Beta that caused describedby links in resources to give 404 Not Found status
  • BUG:26723675 - Fix regression introduced in 17.3 Beta that caused an empty document to be produced for describedby link of AutoREST enabled table/view items

New Features in 17.4.0

  • ENH:26718429 - REST Enabled SQL Service. Provides a secure mechanism to POST SQL scripts to be executed in the context of an ORDS enabled database schema
  • ENH:26718645 - Open API (aka Swagger) support for metadata catalog.

Known Issues


  • None

JDK Support

  • ORDS will run on JDK 9 and is supported on Application Servers that are certified to support JDK 9.
  • However when running ORDS from the command-line, ORDS will require additional arguments to the java command.

    On JDK 8 and earlier to launch an ORDS command one would type:

    java -jar ords.war <command-name>
    On JDK 9 this must become:
    java --add-modules java.xml.bind -jar ords.war <command-name>
    For example to launch ORDS in standalone mode on JDK 9 you must do as follows:
    java --add-modules java.xml.bind -jar ords.war standalone
    • ORDS relies on the java.xml.bind module, but this module is not switched on by default in JDK 9 and so it must be explicitly enabled using the --add-modules java.xml.bind argument
    • We hope to eliminate the need for this additional argument in a future version of ORDS and/or JDK 9. At this time we do not recommend or support the use of Standalone Mode with JDK 9 in production environments.


Weblogic Support

  • Weblogic 12 deployments require the following workaround to avoid a Java class conflict that causes a 500 response when invoking ORDS:

    Override Weblogic 12 to use the RI JAXP providers shipped with the JDK

    Use the System Property values in Table 5-15 to force the JDK version to be used.

    You can set these System Properties in a number of ways, but the way we recommend this is done is update the settings for the server instance where ORDS is deployed. In the WebLogic Admin Console navigate to:

    Servers -- server-name-where-ords-is-deployed -- Server Start

    Then enter the following in the Arguments field, then Save and restart that Server:
    -Dcom.sun.xml.ws.spi.db.BindingContextFactory=com.sun.xml.ws.db.glassfish.JAXBRIContextFactory -Djavax.xml.bind.JAXBContext=com.sun.xml.bind.v2.ContextFactory

Autogenerated REST Endpoints

  • AutoRest resources support the OAuth 2.0 Client Credentials flow only.

RESTful Services

  • Application Express workspaces do not support first party authentication, and therefore do not support the /sign-in/ interactive sign in form. Accessing /sign-in/ in APEX workspaces will produce a 404 status.


  • It is not currently possible to access secured NoSQL REST Endpoints with OAuth 2.0, only first party cookie authentication is supported.