ORDS Instance API Not Showing Pools After Upgrade To 22.1
(Doc ID 2910068.1)
Last updated on NOVEMBER 17, 2022
Applies to:
Oracle REST Data Services - Version 22.1 and laterInformation in this document applies to any platform.
Symptoms
1. Enable ORDS Instance API. See instructions below.
(Note that the instance.api.enabled setting must be set as a global setting, not a pool setting)
https://docs.oracle.com/en/database/oracle/oracle-rest-data-services/22.3/ordig/deploying-and-monitoring-oracle-rest-data-services.html#GUID-116149DE-01E1-4056-A723-0EFB96737377
https://krisrice.io/2021-01-19-Instance-API/
2. Make a request to http://<host>:<port>/ords/_/instance-api/stable/status using Basic Auth with the user configured.
Expected:
Result should show valid pools count and links to each pool
Actual:
Result shows no pools:
{
"invalid_pools_count": 0,
"valid_pools_count": 0,
"links": [
{
"rel": "self",
"href": "http://<host>:<port>/ords/_/instance-api/stable/status" },
{
"rel": "describedby",
"href":
"http://<host>:<port>/ords/_/instance-api/stable/metadata-catalog/"
},
{
"rel": "related",
"href":
"http://<host>:<port>/ords/_/instance-api/stable/database-pools-cache/"
}
]
}
Changes
Upgraded to ORDS 22.x.
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 |