Guide
Oracle Endpoint
Oracle endpoints connect Gateway to Oracle Database services for governed SQL access, metadata discovery, and enterprise migration planning.
Endpoint Kind
Use oracle as the endpoint kind when creating this endpoint through the API or dashboard.
What Gateway Uses This Endpoint For
- Run governed SQL against Oracle services through Gateway.
- Catalog schemas, tables, views, indexes, and stored program units for planning.
- Apply RBAC and audit controls before exposing Oracle data to users or agents.
- Plan Oracle-to-modern-platform migration and coexistence work.
Basic Endpoint Shape
json
{
"endpoint": "oracle-prod",
"kind": "oracle",
"config": {
"read_conn": {
"host": "oracle.internal",
"port": 1521,
"service_name": "ORCLPDB1",
"auth": {
"username": "app_user",
"password": "secret"
}
}
}
}Create it with the endpoint API:
bash
curl -sS -X POST "$EDEN/endpoints" \
-H "$AUTH_HEADER" \
-H "Content-Type: application/json" \
-d '{
"endpoint": "oracle-prod",
"kind": "oracle",
"config": {
"read_conn": {
"host": "oracle.internal",
"port": 1521,
"service_name": "ORCLPDB1",
"auth": {
"username": "app_user",
"password": "secret"
}
}
}
}'Configuration Fields
| Field | Purpose |
|---|---|
host | Oracle listener host |
port | Listener port, usually 1521 |
service_name | Service name or pluggable database name |
username | Database username |
password | Database password |
Operating Notes
- Confirm whether the deployment uses service names or SIDs before onboarding.
- Use a role with read-only catalog access for discovery workflows.
- Keep application credentials separate from administrative migration credentials.