400 Bad Request - ORDS Get Handler While Using LIMIT and OFFSET parameter in URL (Doc ID 2859715.1)

Last updated on APRIL 06, 2022

Applies to:

Symptoms

On : 21.1 version, All Issues

ORDS get handler call not working : 400 Bad request.

A PL/SQL block is created and executed using VBCS or "postman" or "browser". It fails with 400 bad request.

Not Working for example :

https://hostname/ords/bpe/bpe/oracleBillingTxnHdr?accFromDate=2022-03-01&accToDate=2022-03-29&billingNum=&billingStatus=All&custAccount=&legalEntity=852&pricingFlag=All&type=BILLING&limit=25&offset=0

Working example :

https://hostname/ords/bpe/bpe/oracleBillingTxnHdr?accFromDate=2022-03-01&accToDate=2022-03-29&billingNum=&billingStatus=All&custAccount=&legalEntity=852&pricingFlag=All&type=BILLING

When -----> limit=25 and offset=0 is removed in the URL, it works.

How to allow these parameters in PL/SQL exposed REST service.

This offset is for pagination and the number of rows to fetch.

Why PL/SQL block exposed as a rest service not allowing the query string which appends "&limit=25&offset=0"

Note: Same works fine with ORDS rest service which is exposed by select query.

This is a Autonomous Database Shared Environment
ORDS is created from ATP database.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.