What is Different
| Area | DAS | RDS |
|---|---|---|
| DB Platform | ADW (recommended) or ATP | ADW |
| Service Level | SLA determined by Customer and OCI PaaS SLA | TSA, RTO, RPO based on SaaS SLA |
|
Data Schemas |
MFCS, SIOCS, CE | MFCS, SIOCS, CE, OB, XO, SE, BC, RICS, RSCH, OM |
| Database Ownership | Customer provisions and manages the target database. | Oracle provisions and manages an Autonomous Data Warehouse. |
| Users & Schemas | Customer can create new users/schemas. | Schema set is predefined and immutable. Customers cannot create new users or schemas. |
| Subscription | PaaS (storage, compute), GoldenGate additional | SaaS (storage, compute), GoldenGate included |
| Included Tools | APEX, ORDS, SQL Dev Web, SQL Dev Desktop | APEX, ORDS |
|
DB Connection |
Web Access, others with supported database connection | Web Access Only, Private Endpoint (additional) |
| Integration | ORDS, APEX, ADW Adapter, others with supported database connection. | ORDS, APEX, Export/Import through Object Storage |
| GoldenGate Management |
Customer manages GoldenGate replication on the target, including the initial load. |
Oracle manages GoldenGate end-to-end, including the initial load and synchronization of source and target. |
| Object Set | Customers can configure which objects to replicate. | Fixed set of objects replicated; not configurable. |
| Data Access Model | Tables and views are both exposed. | Only views are exposed, with naming like
RDS_WV_<view>. The precise naming convention is
cloud service specific but expect the names to differ from those in
DAS.
|
|
Schema Structure |
Replicated data and extensions may coexist in the same schema. | Replicated data and extensions are segregated: read-only application
schemas vs. read/write extension schemas. Three auxiliary schemas (
RDS_CUSTOM_1 , RDS_CUSTOM_2 ,
RDS_CUSTOM_3) are also provided with no default
access.
|
| Security & Privileges | Customer controls user accounts, roles, and grants. Security posture varies by implementation. | Oracle defines a static, least-privilege model. Customers have limited security responsibilities. Custom objects are not accessible outside the owning schema unless privileges are explicitly granted. |
| Move Support | N/A. | Oracle may provide recommendations, but customers are responsible for moving from DAS to RDS. |
| Capacity Planning | Fully managed by customer. | Oracle manages infrastructure, but customers must monitor storage and CPU consumption and request capacity increases. |
| Replication Scope & Integration | Customer-owned database can act as a GoldenGate source or target; customers can also integrate other pipelines (ETL, database links, flat files). | RDS cannot be a GoldenGate target or source. External data can be brought in only through Object Store + DBMS_CLOUD, REST services, or OIC with Private Endpoint, and only into the extension schema. |
|
Customer Role |
Customers act as both DBA and developer — responsible for patching, backups, replication management, security model. | Customers act primarily as developers. Oracle handles DBA functions: patching, upgrades, replication, backups, security baseline. |