ORDS configured to access mod_pls modules only gives: "An Unexpected Error With The Following Message Occurred: Null"
(Doc ID 2396187.1)
Last updated on SEPTEMBER 15, 2022
Applies to:
Oracle REST Data Services - Version 18.1.1 to 21.4.3Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
On ORDS 18.1.1 version,
When attempting to configure ORDS to run a mod_pls procedure only (no APEX involved) the following error occurs:
SEVERE: null
java.lang.NullPointerException
at java.util.Objects.requireNonNull(Objects.java:203)
at oracle.dbtools.url.mapping.db.DatabaseURLMappingImpl.addServices(DatabaseURLMappingImpl.java:332)
at oracle.dbtools.url.mapping.URLMappingBase.doFilter(URLMappingBase.java:80)
at oracle.dbtools.url.mapping.filter.URLMappingFilter.doFilter(URLMappingFilter.java:127)
The issue can be reproduced at will with the following steps:
1.Configure a new ORDS mapping using
- java -jar ords.war setup --database my_db
(Supply the relevant database information here....)
If using Oracle Application Express or migrating from mod_plsql then you must enter 1 [1]:2
...
- java -jar ords.war map-url --type base-path /mydb my_db
(To supply the URL mapping information for the call)
2. Use URL http://<HOST>:<PORT>/ords/mydb/procedure.run_report
3. The error 500 error occurs.
Changes
Users have moved to ORDS from Oracle HTTP Server (OHS) and mod_plsql.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |