Oracle REST Data Services 23.1.0.086.1423

Release Notes

Date: March 2023

Support

  • You are supported by Oracle Support under your current Oracle 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.

Note - Autonomous Database Shared Subscribers

If you are running a customer-managed ORDS for your Autonomous Transaction Processing, Autonomous Data Warehouse, or Autonomous JSON Database, you must upgrade your customer-managed ORDS to the version used in your Autonomous Database Shared environment. Failure to do so could lead to service disruptions.

To determine the version of ORDS in your Autonomous Database Shared database run this query:

select ords.installed_version from dual;

Documentation

General

  • Documentation for this release is provided on the oracle.com web site. Click here to view the documentation and related information.
  • Documentation on using SODA for REST is provided on the oracle.com web site. Click here, navigate to the documentation section and access the book titled 'SODA for REST'.

Getting Started

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

Feedback

  • At Oracle REST Data Services on oracle.com you will find links to forums and social media channels where you can discuss topics with the ORDS community around the world and leave feedback for the development team.
    • In 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 Concepts to Keep In Mind

Revised Command Line Interface and Configuration Directory Structure

Command Line Interface

The java commands serviced from the WAR file are no longer supported. Attempting to run the following:

java -jar ords.war standalone
Will result in an error message, referring you to the docs. Instead you would run:
ords --config /path/to/config serve

Installation & Configuration

The ORDS program or script in the bin directory can be used to perform installs, changes to your configuration, changing the database passwords for your connection pools, and for creating ORDS users. To see a list of commands:

ords --help

Configuration Files Directory Layout

If upgrading from a previous version of ORDS, your existing configuration directory for ORDS and the files contained therein will be migrated to a new layout for versions 22.1 and higher.

You may migrate your settings using the ORDS migrate command, or you may perform a 22.1 install which will prompt ORDS to migrate your existing ORDS configuration to the new mapping for you.

ORDS standalone and default pool configuration settings are in a settings.xml file in a global subdirectory.

Connection pools are in a databases subdirectory. The intital database pool is named 'default' and has a '/' mapping pattern.

Subsequent pools will created such that the name of the pool also defines the mapping pattern.

Migration of Oracle APEX Restful Service Modules

Oracle APEX 22.1 and onwards no longer natively supports the serving of APEX Based Restful Service Modules. Existing APEX Based Restful Service Modules must be migrated to ORDS Resource Modules in order to avoid loss of service.

As migration will replace any previously migrated (and possibly further developed) APEX Based Restful Service Modules from an APEX Workspace, it is the responsibility of the customer to manually initiate the migration. To help with this, Oracle has provided a number of SQL scripts that can be found in the "migrate" folder in the top-level "scripts" folder of the ORDS distribution ZIP file. These scripts must be run as either a DBA or an ORDS "Installation" user.

  • ords_migrate_report.sql - Reports on the migration status of all APEX Workspaces that have one or more APEX Based Restful Service Modules (excluding oracle.example.hr). e.g.
    @ords_migrate_report.sql
    APEX SCHEMA APEX VERSION APEX STATUS ------------------------------------------------ --------------- --------------- APEX_210200 21.2.0 VALID WORKSPACE NAME MIGRATED MODULES --------------------------------------------------------------- -------- ------- APEX_WS_2 NO 6 APEX_WS_1 YES 1
  • ords_manual_migrate_workspace.sql - Manually migrates a single APEX Workspace e.g.
    @ords_manual_migrate_workspace.sql ~/logs/ APEX_WS_2
  • ords_manual_migrate.sql - Manually migrates all APEX Workspaces e.g.
    @ords_manual_migrate.sql ~/logs/

SQL Developer Web

SQL Developer Web (SDW) is an ORDS hosted web application giving Oracle Database users the SQL Developer desktop experience in their browser.

SQL Developer Web provides a development interface for building and maintaining your ORDS based REST APIs, AUTOREST Enabled database objects, OAuth3 Clients, ORDS Privileges and Roles, as well as a SODA for REST graphical interface. For the best possible experience developer REST APIs for ORDS, we reccommend you use SQL Developer Web.

For consistent representation of date values in SQL Developer Web, ORDS should be run in the UTC timezone. This is set automatically when using the

ords
command line interface. When deploying ORDS to Apache Tomcat or WebLogic Server the user.timezone may have to be set explicitly before starting the container.
-Duser.timezone=UTC

SQL Developer Web requires the Database API be enabled.

SQL Developer Web's DBMS_SCHEDULER interface requires database version 12.2 or higher.

Metadata Catalog

The default output for openapi-catalog is Swagger V2. In a future release the default output will be OpenAPI V3.

Upgrading ORDS in the database

If you have previously executed script, ords_installer_privileges.sql, to grant your administrator user privileges to perform the install or upgrade, then you must execute the script again on that same user that you provided because additional grants have been added to this script. Note: This script does not apply to the SYS user account.

Supported Java Version

Oracle REST Data Services requires Java 11 or 17. Java 8 is no longer supported. Please consult the documentation for the minimum supported Application Server versions for ORDS.

Changes in 23.1.0

The following changes have been made since 22.4.4:

Issues Fixed in 23.1.0

  • 29253065 - POST and PUT on REST Enabled table with "GENERATED ALWAYS AS IDENTITY" columns results in ORA-32795 error
  • 34816442 - Sign-in flow not working when a REST Enabled schema is not involved
  • 34762861 - Database Actions - Data loading from file not working
  • 34846031 - Database Actions - Cannot load a local file in SQL Worksheet from table context menu
  • 35135762 - Database API - Invalid URL when server and path combined

New Features in 23.1.0

  • Uptake JDBC/UCP 21.10.0.0.230302
  • Uptake Apache Commons FileUpload 1.5
  • Uptake antlr4-runtime 4.11.1
  • Uptake Oracle Mongo DB Listener 230302.1319
  • Include Auto PL/SQL paths in OpenAPI document
  • Database API - Export and import APEX Applications
  • Database Actions: Sign-In/Out optimized UI/UX
  • Database Actions: REST workshop, Export Schema
  • Database Actions: Multilingual Engine (MLE) support in Oracle Database 23c
  • ORDS: AutoREST support extended to JSON Relational Duality Views in Oracle Database 23c

Changes in 22.4.4

The following changes have been made since 22.4.3:

Issues Fixed in 22.4.4

  • 35042641 - Charts page is not showing Redwood Brown Theme
  • 34985733 - Fix "Expiring Passwords" widget(monitoring)
  • 35022665 - Inconsistent sort options while creating a composite index
  • 35002206 - --wallet option throws an error in ORDS ADB Install CLI
  • 34465167 - ADB-S Service Console: Show only MongoDB connection string that contains port 27017
  • 33997668 - JSON Workshop: Index is dropped while editing it

New Features in 22.4.4

  • Uptake JDBC/UCP 21.9.0.0.230123

Changes in 22.4.3

The following changes have been made since 22.4.2:

Issues Fixed in 22.4.3

  • 35033730 - Data Studio update to color theme

Changes in 22.4.2

The following changes have been made since 22.4.0:

Issues Fixed in 22.4.2

  • 34824962 - Database Actions Data Pump import fails for various DMP files
  • 34943125 - procedure.rest.preHook is executed for PL/SQL Gateway calls

New Features in 22.4.2

  • Database Actions: Self Service Schema - A semi-automated flow to allow users to request database schemas
  • Database Actions: Migration to Oracle's Redwood styling
  • Database Actions: Data Pump import is now enabled on ADB-S environments

Changes in 22.4.0

The following changes have been made since 22.3.3:

Issues Fixed in 22.4.0

  • 34762861 - Database Actions: Data Loading from file not working
  • 34724735 - Setting db.invalidPoolTimeout not working to retry an invalid default pool
  • 34693771 - Incorrect path in Linux Support scripts and documentation
  • 34685239 - Pool not marked as stale for oracle.net.ns.NetException error scenarios 'TNS:listener could not find instance appropriate for the client connection' and 'Mismatch with the server cert DN'. '
  • 34669593 - Minimum Java version checks in ORDS shell script not working
  • 34664606 - Get PDB Snapshot by name not working with 18c database
  • 34643474 - HTTP 500 Internal Server Error response if APEX is installed in CDB
  • 34571360 - PL/SQL Gateway allow list view not visible to ORDS_ADMINISTRATOR_ROLE
  • 34570720 - DBAPI Creating new pluggable database fails
  • 34488953 - Instance API does not show pools in revised configuration
  • 34014229 - Running PL/SQL Gateway without ORDS installed in database blocked by missing privileges
  • 34003124 - Hostnames mapping overrides paths mapping in the same pool
  • 33859693 - Install fails when execute privilege on DBMS_SQL is not granted to PUBLIC

New Features in 22.4.0

  • Switch from using javax.* APIs to their jakarta.* equivalents
  • Uptake Jakarta Servlet API 4.0.3
  • Uptake Jakarta Inject API 2.0.0
  • Return HTTP 403 response when client not in ADB-S Access Control List
  • Return HTTP 429 response when database server returns ORA-00018 maximum number of sessions exceeded
  • Add Data Tool endpoints to Database API
  • Export OAUTH Client
  • Support order by NULLS first/last in Object Filter query parameters
  • Database Actions: Make 'Run as SQL script' the default operation for Run Statement button

Changes in 22.3.3

The following changes have been made since 22.3.2:

Issues Fixed in 22.3.3

  • Bug 34162245 - ORDS: Symbolic links can not be used to provide static content in standalone mode
  • Bug 34752871 - Database Actions: Failure to get Cloud Storage Bucket in Data Pump

New Features in 22.3.3

  • ORDS: Uptake Jetty 10.0.12

Changes in 22.3.2

The following changes have been made since 22.3.1:

Issues Fixed in 22.3.2

  • Bug 34723764 - ORDS: Silenty ignore query parameters which do not match plsql parameters
  • Bug 34728229 - ORDS: Uptake Jackson 2.13.4 and Jackson Databind 2.13.4.2

Changes in 22.3.1

The following changes have been made since 22.3.0:

Issues Fixed in 22.3.1

  • Bug 34709325 - ORDS: APEX Social Authentication recieving 404 NOT FOUND

Changes in 22.3.0

The following changes have been made since 22.2.2:

Issues Fixed in 22.3.0

  • Bug 34151810 - Database Actions: Alter session not working in SDW
  • Bug 34457888 - ORDS: ORDS does not pass through parameters retrieved via OWA_IMAGE.GET_X(IMAGE)
  • Bug 34356953 - ORDS: Batch POST fails with NullPointerException
  • Bug 34077953 - ORDS: ORDS 500 Internal Server Error inserted value too large for column
  • Bug 34036798 - ORDS: Command Line Interface fixed option values should be case insensitive
  • Bug 33649799 - ORDS: ORDS does not invoke overloaded PL/SQL procedures correctly
  • Bug 34327673 - ORDS: Command Line Interface --db-pool option not accepting values using underscore

New Features in 22.3.0

  • ORDS: Uptake Jetty 10.0.11
  • ORDS: Update SODA 1.1.13
  • ORDS: Uptake Oracle JDBC and UCP drivers 21.0.0.0_220912
  • ORDS: Provide PL/SQL API to force ORDS into debug mode
  • ORDS: Provide Customer Managed ORDS for Autonomous Database installation process in the command line interface
  • ORDS: Set db.serviceNameSuffix by default on CDB installs
  • ORDS: Make PL/SQL Gateway allow list ready for custom procedures
  • ORDS: Serve MongoDB Listener in standalone mode
  • ORDS: Support jdbc.ConnectionWaitTimeout in pool settings
  • ORDS: Database API - PDB Lifecycle Management: Do not close wallet during cloning
  • ORDS: Database API - PDB Lifecycle Management: Support PDB Snapshots
  • Database Actions: Data Loader - Add support for filtering data loading slider by schema
  • Database Actions: Data Pump - Add Import Job Wizard

Changes in 22.2.2

The following changes have been made since 22.2.1:

Issues Fixed in 22.2.2

  • Bug:34072949 - ORDS: Default value(900) of jdbc.statementtimeout parameter doesn't work
  • Bug:34448170 - Database Actions: Show card for "Graph Studio" in launchpad
  • Bug 34370563 - ADP: Support multiple addins on one excel
  • Bug 33948244 - ADP: Lineage/impact ui does not correctly render odi lineages with 3-deep node nesting
  • Bug 34390875 - ADP: Changing dblink source does not update navigator tree

Changes in 22.2.1

The following changes have been made since 22.2.0:

Issues Fixed in 22.2.1

  • Bug:34057582 - ORDS: Requests with additional trailing slashes should result in HTTP 404 response
  • Bug:34179622 - ORDS: Include owa.docTable in config info
  • Bug:34304646 - ORDS: Have configurable jdbc.connectionWaitTimeout used by PL/SQL Gateway
  • Bug:34354741 - ORDS: Improvements to Oracle Transactional Event Queues services
  • Bug:34358681 - ORDS: Remove APP_VM_OPTS variable from RPM definition

New Features in 22.2.1

  • ORDS: Uptake Jetty 9.4.48.v20220622
  • ORDS: Uptake SODA 1.1.11

Changes in 22.2.0

The following changes have been made since 22.1.1:

Issues Fixed in 22.2.0

  • Bug:32047436 - ORDS: ORA-65011 Pluggable Database does not exist error when installing to EBS database 19c
  • Bug:32438722 - ORDS: Database API PDB Lifecycle Management does not allow special characters in administrator password
  • Bug:32471712 - ORDS: Not reloading passwords from wallet after failed database connection attempt
  • Bug:34110230 - ORDS: Remove Jersey support
  • Bug:34175379 - ORDS: SEVERE log message displayed for making connection even though database mapping succeeds
  • Bug:34178022 - ORDS: Standalone certificates not migrated
  • Bug:34219177 - ORDS: Do not use reserved words as schema alias
  • Bug:34223707 - ORDS: NoClassDefFoundError oracle/xdb/XMLType reported for certain REST Enabled SQL scripts

New Features in 22.2.0

  • ORDS: Uptake Oracle JDBC and UCP drivers 21.0.0.0_220509
  • ORDS: OpenAPI v3 is the default specification for open-api-catalog (formerly Swagger v2)
  • ORDS: Provide method for resetting client secret
  • ORDS: Metadata catalog representation in Swagger/OpenAPI format for AutoREST indicates attributes comprise the primary key
  • ORDS: Provide command to extract the ORDS install, upgrade, validate and uninstall scripts.
  • ORDS: Provide command to generate web application for deployment to Apache Tomcat or Oracle WebLogic Server
  • Database Actions: Support the Multilingual Engine (MLE) syntax in Oracle Database 21c
  • Database Actions: Generate, View, & Download Automatic Workload Repository (AWR) reports

Changes in 22.1.1

The following changes have been made since 22.1.0:

Issues Fixed in 22.1.1

  • Bug:31078322 - ORDS: Client closing socket can result in HTTP 500 error
  • Bug:34070049 - ORDS: Prevent use of / in paths file
  • Bug:34092368 - ORDS: OutOfMemoryError can occur when starting in standalone mode
  • Bug:34062151 - Database Actions: Not possible to set timezone for start date and end date of job

New Features in 22.1.1

  • Bug:34156033 - ORDS: Uptake Jetty 9.4.46.V20220331
  • Bug:34096129 - ORDS: Automatically link to MySQL Connector/J jar installed through OCI RPM
  • Bug:33995066 - Database Actions: Implement liquibase deployment reporting

Changes in 22.1.0

The following changes have been made since 21.4.3:

Issues Fixed in 22.1.0

  • Bug:31584096 - ORDS: Swagger V2 payload definition is incorrect for POST handler
  • Bug:31797961 - ORDS: Invalid timestamp value in AutoREST PUT parameter causes HTTP 500 Internal Server Error
  • Bug:33014274 - ORDS: Using boolean parameter out on AutoREST PL/SQL causes HTTP 500 Internal Server Error
  • Bug:33111572 - ORDS: Traditional Chinese not represented correctly
  • Bug:33812677 - Database Actions: Roles are mandatory when creating an OAuth3 client
  • Bug:33812695 - Database Actions: Roles created by SYS not listed when creating an OAuth3 client
  • Bug:33542000 - Database Actions: Explain Plan is caching previous executions
  • Bug:33610732 - Database Actions: Table properties unique keys text cropped
  • Bug:33631559 - Database Actions: Wrong color for string quote
  • Bug:33669845 - Database Actions: Missing labels on Charts page
  • Bug:33680494 - Database Actions: The unexpected token symbol shown when a token is followed by a quoted string
  • Bug:33816710 - Database Actions: OpenAPI documentation fails with parser error - duplicated mapping key

New Features in 22.1.0

  • Bug:30717389 - ORDS: Swagger V2 and OpenAPI V3 representation of Metadata Catalog to include authentication information
  • Bug:31391518 - ORDS: Revised Command Line Interface and Configuration Directory structure
  • Bug:33416453 - ORDS: Make Java 11 the minimum Java Runtime Environment version
  • Bug:33744175 - ORDS: Uptake Oracle Jet 11.1.6
  • Bug:33947345 - ORDS: Use REST Enabled SQL Service with MySQL database
  • Bug:34002527 - ORDS: Rotate a client secret
  • Bug:33784519 - ADP: Support renaming and deleting an ingest job
  • Bug:33841574 - ADP: Running data ingest jobs are listed with job name
  • Bug:31018220 - Database Actions: Use offline help when online help not available
  • Bug:33417651 - Database Actions: User friendly global search
  • Bug:33532066 - Database Actions: Generate CURL snippets for Windows
  • Bug:33631074 - Database Actions: Improve performance of standalone Charts view
  • Bug:33655971 - Database Actions: Disable refresh for Charts
  • Bug:33817138 - Database Actions: File system access in SQL Worksheet
  • Bug:33850965 - Database Actions: Import REST Module from swagger definition
  • Bug:33867119 - Database Actions: Enhanced support for PL/SQL object editing
  • Bug:33886602 - Database Actions: Uptake performance hub plugin 1.0.0-20220219112340-MASTER
  • Bug:33952777 - Database Actions: Create PL/SQL object from scratch
  • Bug:33792443 - Database Actions: Add support for full screen in SQL Worksheet

Changes in 21.4.3

The following changes have been made since 21.4.2:

Issues Fixed in 21.4.3

  • Bug:34020594 - ORDS: Uptake Jackson 2.13.2 and Jackson Databind 2.13.2.2
  • Bug:33837693 - ORDS: A second call to the same rest enabled procedure with date in parameter fails with unable to marshall date

Changes in 21.4.2

The following changes have been made since 21.4.1:

Issues Fixed in 21.4.2

  • Bug:33502385 - ORDS: PL/SQL Gateway not accepting parameter names with special characters

New Features in 21.4.2

  • Bug:33839193 - ORDS: Uptake SODA 1.1.10
  • Bug:33871448 - ORDS: Uptake Rappid 3.4.1
  • Bug:33915916 - ORDS: Jersey repackaged with Jackson 2.13.1
  • Bug:32386554 - ORDS: Provide new scripts to report on non-migrated workspaces and to individually migrate them
  • Bug:33488849 - ORDS: Check that ORDS can dispatch both /ords/r/... and /ords/{schema}/r/...

Changes in 21.4.1

The following changes have been made since 21.4.0:

Issues Fixed in 21.4.1

  • Bug:33684760 - ORDS: OAuth token empty response in Database Actions
  • Bug:33727577 - ORDS: PDB mapping not working. 404 + SQLException: ORA-01005
  • Bug:33739947 - ORDS: Error trying to export a module with a handler's source bigger than 32kb
  • Bug:33583853 - ORDS: Error using Windows path to TNS folder

Changes in 21.4.0

The following changes have been made since 21.3.2:

Issues Fixed in 21.4.0

  • BUG:33138576 - Database Actions: Table properties dialog window cannot scrolldown
  • BUG:33599211 - ORDS: Plugin examples not working in Getting Started guide

New Features in 21.4.0

  • BUG:33535164 - ORDS: Uptake Jackson 2.13.0
  • BUG:33535164 - ORDS: Uptake Jetty 9.4.44.v20210927
  • BUG:33535164 - ORDS: Uptake Guava 31.0.1-jre
  • BUG:33580638 - ORDS: Uptake AutoAV 20.1.3.41
  • BUG:33132127 - ORDS: Schema level configuration
  • BUG:33146922 - Database Actions: User Interface to job scheduler
  • BUG:33271364 - Database Actions: APEX workspace management
  • BUG:33651611 - ADP: Data Analysis in data tools

Changes in 21.3.2

The following changes have been made since 21.3.1:

Issues Fixed in 21.3.2

  • BUG:33489973 - Database Actions: Public properties - Empty DIVS to DOM when response is empty
  • BUG:33574935 - Database Actions: REST Workshop: REST called is failed when the module is accessed
  • BUG:33406824 - Database Actions: Chart Tour/ Dashboard Tour is left even after the tour is over
  • BUG:33498260 - ORDS: Update jdbc/ucp cumulative patch jars

Changes in 21.3.1

The following changes have been made since 21.3.0:

Issues Fixed in 21.3.1

  • BUG:33278709 - Database Actions: The output of query results is with commas if the column type is number

New Features in 21.3.1

  • BUG:33323698 - Database Actions: Add auto refresh to report component
  • BUG:33408583 - Database Actions: Add customisable banner to all Sign In, OAuth and Database Actions pages
  • BUG:33449736 - ADP: Update AutoAVGen to 20.3.1.39

Changes in 21.3.0

The following changes have been made since 21.2.4:

Issues Fixed in 21.3.0

  • BUG:33103628 - Database Actions: Vertical scroll missing in chart definition in Firefox
  • BUG:32917191 - ORDS: Instance API OpenAPI V3 document specifies incorrect path
  • BUG:31892227 - ORDS: Swagger V2 representation of metadata catalog returns HTTP 200 for modules without a handler

New Features in 21.3.0

  • BUG:33166641 - ADP: Use cards based statistics histogram
  • BUG:33094472 - Database Actions: Data visualizations dashboard
  • BUG:33136055 - ORDS: Database API Data Pump support for Oracle Cloud Object Storage
  • BUG:32028571 - ORDS: Database API Data Pump available to non administrator database users
  • BUG:32372554 - ORDS: Uptake UCP DRIVER (21.0.0.0-p32464841-p32376643-p33041374-p33199445)
  • BUG:32372554 - ORDS: Uptake JDBC DRIVER (21.0.0.0-p32205381-p33094923)
  • BUG:33297723 - ORDS: Uptake jakarta.json JSON-P 2.0.1 and Eclipse Parsson 1.0.0
  • BUG:33307363 - ORDS: Upgrade to SODA 1.1.8

Changes in 21.2.4

The following changes have been made since 21.2.3:

Issues Fixed in 21.2.4

  • BUG:33238570 - ORDS: Uptake Jetty 9.4.43.V20210629
  • BUG:32983106 - Database Actions: Data load from cloud store folder with subfolders counts folders as loadable items

Changes in 21.2.3

The following changes have been made since 21.2.2:

Issues Fixed in 21.2.3

  • BUG:33008285 - ORDS: SQL Export endpoint response Content-Type: application/json regardless of the format of response body
  • BUG:33046417 - ORDS: Before showing the main result of script output button, two elapsed boxes are there

Changes in 21.2.2

The following changes have been made since 21.2.1:

Issues Fixed in 21.2.2

  • BUG:32860938 - ADP: Performance improvement for designer content in Business Model landing page
  • BUG:32860950 - ADP: Performance improvement for deployment state content in Business Model landing page
  • BUG:32997903 - ADP: Performance improvement for Data Insights page
  • BUG:33016115 - ADP: Live feed cloud store schema name is not required
  • BUG:33093313 - ORDS: Colons in simplified JSON syntax is incorrectly interpreted as bind variables
  • BUG:33101999 - ORDS: SQL Developer REST DATA SERVICES Administration view encountered 500 Internal Server Error on connection
  • BUG:32981951 - ORDS: Uptake UCP DRIVER (21.0.0.0-p32464841-p32376643-p33041374)

Changes in 21.2.1

The following changes have been made since 21.2.0:

Issues Fixed in 21.2.1

  • BUG:32988409 - Database Actions: Use correct username reference syntax for certain Database Actions/ADP services

Changes in 21.2.0

The following changes have been made since 21.1.3:

Issues Fixed in 21.2.0

  • BUG:32817733 - ORDS: Too many parse errors database alert logs for PLSQL_GATEWAY_CONFIG query
  • BUG:32703803 - Database Actions: Data loading to a different schema fails to create error logging table
  • BUG:31843537 - Database Actions: SODA syntax errors

New Features in 21.2.0

  • BUG:32935129 - ORDS: Metadata caching
  • BUG:32826282 - ORDS: Uptake UCP DRIVER (21.0.0.0-P32464841-P32376643)
  • BUG:33003755 - ORDS: Uptake Jetty 9.4.42.V20210604
  • BUG:32216752 - ORDS: Improve REST Enabled SQL performance
  • BUG:32924934 - Database Actions: Third Party Library updates - uptake Swagger UI 3.45.1
  • BUG:32861901 - Database Actions: Data Visualizations - Charts

Changes in 21.1.3

The following changes have been made since 21.1.2:

Issues Fixed in 21.1.3

  • BUG:32935381 - ORDS: Fix performance regression when checking patching status of APEX

Changes in 21.1.2

The following changes have been made since 21.1.1:

Issues Fixed in 21.1.2

  • BUG:32884510 - ORDS: Fix automatic layout resizing in worksheet

Changes in 21.1.1

The following changes have been made since 21.1.0:

Issues Fixed in 21.1.1

  • BUG:32631694 - ORDS: Unable to pass OBJECT TYPE variable when calling custom wrapper
  • BUG:32704322 - APD: In Database Actions "Data Tools" cards are not visible

New Features in 21.1.1

  • BUG:32794672 - ORDS: Uptake Jetty 9.4.40

Changes in 21.1.0

The following changes have been made since 20.4.3:

Issues Fixed in 21.1.0

  • BUG:32498488 - ORDS: Only return one x-frame-options header for APEX static resources
  • BUG:32471387 - ORDS: APEX workspace URL mapping cached even if schema subsequently REST-Enabled
  • BUG:32228741 - ORDS: Improve performance of named bind statement parsing
  • BUG:31614372 - ORDS: Open API JSON has uppercase response object property names
  • BUG:30376686 - ORDS: Error response should be JSON when client sends Accept: appplcation/json header
  • BUG:32112867 - SDW: Result Set out parameter missing from REST Workshop

New Features in 21.1.0

  • BUG:32459808 - ORDS: Add DVSYS and PYQSYS schema packages to the default PL/SQL Gateway exclusion list
  • BUG:32537360 - ORDS: Reject requests with Origin: null header
  • BUG:32474210 - ORDS: Uptake 21.1 UCP patch 32464841
  • BUG:32241814 - ORDS: Support Zip Archive (db.wallet.zip) which has only cwallet.sso
  • BUG:32222145 - ORDS: Support pluggable database service name suffix when Oracle Connect Descriptor is used
  • BUG:30560527 - ORDS: Support ICAP SSL/TLS connection
  • BUG:32430092 - SDW: Third Party Library updates - uptake Dexie 3.0.3
  • BUG:32430092 - SDW: Third Party Library updates - uptake AVSC 5.5.3
  • BUG:32430092 - SDW: Third Party Library updates - uptake Monaco 0.22.1
  • BUG:32483801 - SDW: Add autocomplete functionality to JSON QBE editor and document editor
  • BUG:31902012 - SDW: Support Monaco colorizer in code viewer component
  • BUG:31536036 - SDW: Allow User Management to work without access to ORDS metadata

Earlier versions

For information on Issues Fixed and New Features introduced for earlier versions please refer to the release notes for those versions.

Known Issues

Oracle Database may report 'ORA-01031: insufficient privileges' for queries that involve CURSOR expressions

In a number of cases, ORDS executes queries which include a CURSOR expression. An issue has been found executing these queries for some schemas in Oracle 18c and Oracle 19c databases. Depending on the roles and privileges involved, the issue does not occur for all schemas, which can give the impression that the issue is intermittent. Refer to RDBMS bug 29049673 for more information. The issue is manifest as follows in the exception returned:

ORA-00604: error occurred at recursive SQL level 1

ORA-01031: insufficient privileges

This is a problem with view-merging of nested cursors introduced in Oracle 18.1 database. Please use the following as a workaround:

alter system set "_fix_control"='20648883:OFF';

Oracle Database DATE and TIMESTAMP values

ORDS interprets Oracle Database DATE and TIMESTAMP values (which do not possess a time zone) into the time zone of ORDS. These values are then represented in the RFC3339 UTC format.

In a future release Oracle Database DATE and TIMESTAMP values will not by default be interpreted into any time zone. These values will be represented in the ISO 8601 "yyyy-mm-ddThh:mm:ss[.sss]" format. Oracle Database TIMESTAMP WITH TIME ZONE and TIMESTAMP WITH LOCAL TIME ZONE values will remain represented in the RFC3339 UTC format.

SQL Developer Web

  • DATE, TIMESTAMP, TIMESTAMP WITH TIMEZONE values downloaded from the Worksheet Query Result in the JSON format are not presented in the Internet Datetime format.

JDBC Array values

ORDS passes array values to the Oracle Database in a number of cases, for example arrays are used to pass the request headers and form fields during PL/SQL Gateway calls. Oracle JDBC Driver 18.3 and later supports an improved mechanism for passing array values, however this feature is only supported on Oracle Database 12c and later. Thus ORDS uses existing deprecated and less efficient APIs for passing array values when connecting to 11G databases, and the improved mechanism when connected to 12c and later. Customers experiencing problems with passing large array sets (for example OutOfMemory exceptions) are encouraged to upgrade from 11G to a newer database version to mitigate these issues.

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.

Support For mod_plsql logmeoff

  • The mod_plsql logmeoff mechanism is not supported reliably by modern browsers and it is not provided by ORDS. The only way to end a HTTP Basic Authentication session is to close the Browser.