Oracle Fusion Data Extraction Using Read-Only Replicated Database (RORD)

Share it

Oracle released 26B, and a new feature has been announced. Oracle is providing a new way to extract data from Oracle Fusion.

The feature is labelled as both Read-Only Replicated Database and Read-Optimized Data Store depending on the context. Think of it as a replacement for Oracle Business Intelligence Cloud Connector (BICC)

How Does It Work?

Oracle Fusion Data Extraction Using Read-Only Replicated Database (RORD)

The users will be able to configure data extracts from Oracle Fusion from pre-configured business views at a schedule that users require.

Files will be created on the Oracle Universal Content Management (UCM) server as comma-separated files. Other applications can download these files using their own integration and get this data out as files.

That Sounds Like BICC: So What is Different?

Technically yes, but here are the key differences. 

HTML

What Is It Used For?

Read Optimized Replicated Database (RORD) can have 2 use cases broadly.

Data Extraction to External Data Warehouses

RORD can be used to extract data for downstream reporting and analytics platforms such as Oracle Autonomous Data Warehouse, Microsoft SQL Server, or any other enterprise data warehouse.

Data extraction typically involves additional integration to connect to UCM file server and load the extracted data into the target warehouse.

Note: Integration requires identifying and downloading files from UCM, processing the contents, and loading them into the external system. Incremental load handling must also be implemented, which can add complexity.
Data Integration With External Applications

RORD can act as a reliable data source for applications integrated with Oracle Fusion. Instead of building custom SQL queries or BI Publisher reports, you can use scheduled extracts to feed data into external systems.

For example, if you are developing an application using Oracle APEX on Oracle Autonomous Transaction Processing, you can consume RORD extracts to simplify data access and reduce development effort.

Note: RORD approach will take care of only data out of Oracle Fusion. Developers will still have to call

Also Read: Datafusing CloudSQL vs SQLConnect

Do I Need a Separate License For This?

The Oracle Read-Only Replicated Database feature is included with the Oracle Fusion license and does not require any additional licensing.

Is the Read-Only Replicated Database Fully Available?

Read-Only Replicated Database  is  available in 26B ,but with limitations. But as an Opt-in feature. This requires configuration of roles and profile options to start. There are limitations as well 

  • Language support is only english
  • DFFs (Descriptive Flexfields) not included yet 
  • Business object coverage is still evolving 

All in all, this is usable, but not all functionalities are available.

Will This Replace BICC? What Does Oracle Say?

Yes. Oracle is being quite explicit. Read-Only Replicated Database  (RORD) will eventually replace:

  • Business Intelligence Cloud Connector (BICC) 
  • BI Publisher (for extract use cases) 

Oracle’s Position: “This approach is recommended for all new data extracts and will eventually replace BICC and BI Publisher extracts.”

What Does This Means in Practice?

  • ✅ New implementations → Use RORD instead of BICC
  • ⚠️ Existing BICC → Plan migration to Read Only Optimized Datastore in the future
  • ❌ BICC is effectively legacy now 

Also Read: ROI of CloudSQL Desktop for Oracle Fusion Development Teams

Can We Get Direct Database Connection to Read-Only Replicated Database for Quering Oracle Fusion?

No. Read only data store can be accessed through scheduled reports and extracted data. Oracle Fusion Developers still have to use CloudSQL to work with BI reporting, Integration development. Checkout How to run SQLs in CloudSQL in under 5 minutes 

Is There a Migration Path From BICC to Read-Only Replicated Data?

No, Oracle has not yet provided a migration path for existing BICC users. Migration will require mapping BICC data stores to the BI Views available in RORD.

Oracle Guidance: Refer to “Map BICC Data to Business Object Data”

Practical Implication: The practical implication is that the migration effort is expected to be medium to high. The migration process will require a strong functional understanding of the existing and target data models, detailed data mapping between BICC data stores and BI Views, and thorough testing to validate the migrated reports and integrations.

In addition, any target systems that currently consume BICC-generated data from UCM will need to be rewritten or modified to support the new integration method.

Also Read: HZ_PARTIES Table in Oracle Fusion

Picture of Binuraj Somanathan Nair

Binuraj Somanathan Nair

Since 2006, Binuraj Nair has been driving successful Oracle ERP projects worldwide, progressing from software developer to project leader on complex, high-value implementations. Drawing on this deep end-to-end experience, he co-founded DataFusing to create powerful tools that streamline Oracle ERP deployments and deliver measurable value to both implementation partners and Oracle’s clients.

Related Posts

Oracle Fusion Reporting

Oracle Fusion Data Extraction Using Read-Only Replicated Database (RORD)

Datafusing CloudSQL vs SQLConnect: Which Is Better Oracle Fusion SQL Editor?
Oracle Fusion Reporting

Datafusing CloudSQL vs SQLConnect: Which Is Better Oracle Fusion…

What Is the ROI of CloudSQL Desktop for Oracle Fusion Development Teams?
Oracle Fusion Reporting

What Is the ROI of CloudSQL Desktop for Oracle…

Image showing all the new features in CloudSQL Desktop

Join CloudSQL Community

Linkedin Youtube X-twitter Facebook

Stay Updated!

Still Writing Oracle Fusion SQL the Hard Way?

Try CloudSQL Editor for Oracle Fusion Developers Today

  • Single-click SQL execution
  • Powerful SQL editor with intelligent auto-complete
  • AI instantly detects and fixes Oracle SQL error
  • No setup required - download and get started in under 5 minutes

Save upto

1 hours

per SQL query!

Start Free CloudSQL Trial
Explore CloudSQL’s features

Manage Consent

To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.

Accept
Privacy Policy

DataFusing CloudSQL License Agreement

IMPORTANT: PLEASE READ THIS LICENSE AGREEMENT CAREFULLY BEFORE DOWNLOADING OR USING THE SOFTWARE. BY DOWNLOADING OR USING THE SOFTWARE, YOU AGREE TO BE BOUND BY THE TERMS OF THIS AGREEMENT.

1. Introduction
This License Agreement (“Agreement”) is made and entered into by and between JXB Software Limited, trading as DataFusing (“JXB”), and you, the end user (“You” or “User”). This Agreement governs your use of the DataFusing CloudSQL software (“Software”).

2. License Grant
Subject to the terms and conditions of this Agreement, JXB grants You a non-exclusive, non-transferable license to download and install the Software on a single personal computer for your own use. The license is per user per computer.

3. Trial Period
The Software is offered for a fixed trial period as specified on the DataFusing website. At the end of the trial period, you must either purchase a license or stop using the Software. You agree not to use any workaround, time manipulation, or software modification to extend the trial beyond its designated duration.

4. User Responsibilities
• You are responsible for backing up any data stored within the Software, including SQL history and connection details.
• You are solely responsible for ensuring your access to Oracle Fusion Cloud is authorized and compliant with Oracle’s terms of service. JXB will not be held responsible for any illegal access attempts using CloudSQL.
• You are liable for any damages caused by your misuse of the Software. JXB shall not be liable for damages resulting from misuse, including unauthorized access or data loss.

5. Third-Party Dependencies
CloudSQL relies on Oracle Fusion Cloud APIs. Changes to these APIs may disrupt Software functionality. While JXB will attempt to provide timely updates or alternatives, no refunds will be issued for such disruptions.

6. License Transfer
The license is not transferable to another user. Any attempt to sublicense, assign, or transfer the license shall be void.

7. Subscription and Payment
• The Software requires a monthly subscription fee.
• You are responsible for timely payment of the subscription fee.
• The subscription will automatically renew at the end of the term unless cancelled before the renewal date.Failure to receive payment on or before the subscription end date shall result in the automatic cancellation of the licence without the requirement of further notice to either party.
• All fees are non-refundable once paid, unless required by applicable law.

8. Software Updates
You agree to upgrade the Software as and when notified by JXB through emails or notifications within the software. JXB is not obligated to support older versions. Failure to install updates may limit functionality or cause the Software to stop working. JXB is not responsible for issues arising from outdated versions.

9. Data Collection and Use
JXB may connect to Datafusing.com to validate your license, collect anonymized error event data for software improvement, and collect anonymized usage data to understand user patterns and enhance the user experience. No personal data will be collected or shared with third parties. Both error and usage data will be stored for a maximum of 24 months before deletion.

10. Confidentiality.

10.1. Definition. As used herein, “Confidential Information” means all confidential information disclosed by a party (“Disclosing Party”) to the other party (“Receiving Party”), or otherwise accessed by the Receiving Party, whether orally or written, that is designated as confidential or that reasonably should be understood to be confidential given the nature of the information and the circumstances of disclosure. User Confidential Information shall include the User Data; JXB’s Confidential Information shall include the Service and JXB proprietary technology and software; and Confidential Information of each party shall include the terms and conditions of this Agreement and all Orders, as well as business and marketing plans, technology and technical information, product plans and designs, and business processes disclosed by such party.

10.2. Exclusions. Confidential Information shall not include any information that (i) is or becomes generally known to the public without breach of any obligation owed to the Disclosing Party, (ii) was known to the Receiving Party prior to its disclosure by the Disclosing Party without breach of any obligation owed to the Disclosing Party, (iii) is received from a third party without breach of any obligation owed to the Disclosing Party, or (iv) was independently developed by the Receiving Party.

10.3. Protection of Confidential Information. Except as otherwise permitted in writing by the Disclosing Party, (i) the Receiving Party shall protect the Disclosing Party’s Confidential Information by using the same degree of care that it uses to protect the confidentiality of its own confidential information of like kind (but in no event less than reasonable care), and shall not disclose or use any Confidential Information of the Disclosing Party for any purpose outside the scope of this agreement, and (ii) the Receiving Party shall limit access to Confidential Information of the Disclosing Party to those of its employees, contractors and agents who need such access for purposes consistent with this agreement and who are bound by confidentiality agreements with the Receiving Party containing protections no less stringent than those herein.

10.4. Permitted Disclosure. The Receiving Party may disclose Confidential Information of the Disclosing Party if it is required to do so in connection with any judicial, governmental or administrative proceedings (by oral questions, interrogatories, requests for information or documents, subpoena, civil investigation, demand or similar process) or pursuant to any applicable law (including, without limitation, any securities laws or stock exchange regulations), provided that, to the extent permitted under applicable law, the Receiving Party shall provide prompt notice of such court order or requirement to the Disclosing Party to enable the Disclosing Party to seek a protective order or otherwise prevent or restrict such disclosure. The Receiving Party shall limit such disclosure to the minimum disclosure as required and shall take appropriate measures to avoid or minimize the release of such information in connection with the proceedings for which the Confidential Information is sought.

11. AI-Powered SQL Assistance (Deepseek)
As part of an optional feature, the Software may offer AI-based assistance for SQL analysis using third-party large language models (LLMs), such as Deepseek. This feature may send SQL queries, including instructions and code snippets, to the Deepseek API for analysis or suggestions. No personal data or stored user data will be transmitted.

This AI feature is provided as a complementary and optional service. If you do not wish to share your SQL queries or instructions with Deepseek, you may disable or choose not to use this feature.

You acknowledge and agree that:

• It is your sole responsibility to understand and review the data handling, privacy practices, and terms of service of Deepseek and any associated third-party AI providers.

• JXB does not control how Deepseek processes the information sent to it and disclaims any liability arising from the use or misuse of data by such third-party services.

• By using this feature, you accept any risks associated with sharing your code snippets with third-party AI systems.

12. Reverse Engineering
You are prohibited from attempting to reverse engineer, decompile, or disassemble the Software.

13. Termination
JXB may terminate this Agreement and your access to the Software at any time for any reason, with or without notice. The service will be terminated without notice upon license expiry unless renewed. Upon termination, you must immediately cease all use of the Software and delete all copies in your possession.

14. Governing Law
This Agreement shall be governed by and construed in accordance with the laws of England and Wales, United Kingdom. Any disputes shall be subject to the exclusive jurisdiction of the courts in England and Wales.

15. Entire Agreement
This Agreement constitutes the entire agreement between JXB and You regarding the Software and supersedes all prior or contemporaneous communications or agreements.

16. Severability
If any provision of this Agreement is held to be invalid or unenforceable, such provision shall be struck and the remaining provisions shall remain in full force and effect.

17. Force Majeure
JXB shall not be liable for any delay or failure to perform its obligations under this Agreement due to causes beyond its reasonable control, including natural disasters, power outages, and other similar events.

18. Contact Us
If you have any questions about this Agreement, please contact JXB at cloudsql@datafusing.com.
BY CLICKING “I AGREE” BELOW, YOU ACKNOWLEDGE THAT YOU HAVE READ AND UNDERSTAND THE TERMS OF THIS AGREEMENT AND AGREE TO BE BOUND BY THEM.

Get Started with CloudSQL for Oracle Fusion