Separation of Replicated and Custom Data

The replicated application data is held in read-only schemas (one per source application schema). The ORDS and APEX workspaces have access to a read-write schema which can view the read-only schema's database objects. In the read-write schema, you are free to create any database objects you need to create, and you have read privileges to the replicated application data. When new database objects are created in the read-only schema (for example when a patch is applied to the source application), a scheduled database job in the RDS database grants the appropriate read permissions for those objects to the read-write schema. This job runs hourly.

Example

For Merchandising Foundation Cloud Service, an ORDS workspace is available that grants access to the MFCS_RDS_CUSTOM schema. This schema is initially empty, but allows creation of database objects, APEX applications, etc. This schema also has read permissions to database objects in the MFCS_RDS schema, which is where the actual replicated data resides. A customer can use the ORDS workspace to create REST data services that can read the tables with replicated data, or can read and write any custom tables that have been created. A customer can also build APEX applications on top of the custom tables; the read-only replicated tables can be read by the APEX application, but cannot be modified.

Each Retail application controls what data it replicates to the RDS database. Refer to each application's product documentation for details about the data that is made available in RDS.