Connecting to Non-default Database Instance in SQL Developer for REST Development Fails with HTTP 404
(Doc ID 2385300.1)
Last updated on FEBRUARY 15, 2023
Applies to:
Oracle REST Data Services - Version 3.0.9 and laterOracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle SQL Developer - Version 4.2.0 and later
Information in this document applies to any platform.
Symptoms
A REST enabled has been created in two different database instances. The intent is to create ORDS based REST services and run Application Express (APEX) for both of these instances.
It is possible to connect to the schema in the default database (defined in defaults.xml) when running APEX and when connecting using SQL Developer.
ORDS based REST services can be accessed, as well.
The non-default database instance and schema can be reached via the APEX URL:
http://<HOST>:<PORT>/ords/newdb
However, it is not possible to connect to the non-default (newdb) via SQL Developer's Rest Development interface.
When attempting to connect through SQL Developer, the error shown is:
HTTP 1.1/ 404 not found.
Configuration
______________
Oracle REST Data Services: 3.0.9.348.07.16
Sql Developer Version: 4.2.0.17.089
Sql Developer Build: 17.089.1709
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 |
| Cause |
| Solution |