A verified, consultant-focused breakdown of Oracle's 26C release cycle — the Fusion Cloud Applications quarterly update and the separate Oracle Integration Cloud monthly releases that land around it. Covers release dates by cohort, the Data Extraction feature replacing BICC/BI Publisher, OIC's new native CI/CD, and how to actually read Oracle's readiness documentation.
"Oracle 26C" almost always means one specific thing — the third quarterly update of Oracle Fusion Cloud Applications in 2026 (Financials, HCM, SCM, CX, EPM, Projects, Risk & Compliance, Platform). Test environments update August 7, 2026 for Cohort A, with production following August 21; Cohort B follows in September, Cohort C in October. But there's a second "26" numbering system people conflate with it: Oracle Integration Cloud ships its own monthly releases (26.04, 26.07, and so on) on a completely separate cadence from Fusion's quarterly letters. If you're trying to figure out "what's new in OIC for 26C," you're actually looking for the OIC monthly release that lands closest to your Fusion cohort's update — not a release literally called "26C." This guide covers both, and the single most consequential change for technical consultants: the new Data Extraction feature that's positioned to replace BICC and BI Publisher-based extracts.
First: Untangle the Two "26" Numbering Systems
This trips up even experienced consultants, so it's worth being explicit before anything else.
Fusion Cloud Applications uses a quarterly letter cadence: 26A, 26B, 26C, 26D — roughly February, May, August/September, and November each year. This is what "26C" means on its own, without qualification: the third quarterly update of 2026, rolling out to test environments in August.
Oracle Integration Cloud (OIC) ships on its own monthly cadence, numbered YY.MM — 26.04 (April 2026), 26.07 (July 2026), and so on. OIC does not follow Fusion's A/B/C/D letters at all. There is no "OIC 26C." When someone asks "what's new in OIC for 26C," what they actually mean is: whichever OIC monthly release happens to be current around the time their Fusion 26C update lands.
Why this matters practically: a Fusion quarterly update can change application behaviour your OIC integrations depend on, even though OIC itself is on an entirely independent release schedule. Testing your integrations after a Fusion quarterly update isn't optional, and it isn't covered just because your OIC instance auto-updated on its own monthly schedule. They're two separate change streams that happen to intersect.
Fusion Cloud Applications 26C: Dates, Cohorts, and Scale
Oracle's standard quarterly update mechanics apply: test environments update on the first Friday of the update month; production follows two weeks later, on the third Friday. For 26C specifically:
| Cohort | Test environment update | Production update |
|---|---|---|
| Cohort A | August 7, 2026 | August 21, 2026 |
| Cohort B | September 4, 2026 | September 18, 2026 |
| Cohort C | October 2, 2026 | October 16, 2026 |
Check the Oracle Cloud Console if you're unsure which cohort your tenant belongs to — it's not something to assume from memory of a prior release.
On scale: independent release-tracking firms that monitor Oracle's quarterly Feature Listing report have published different aggregate counts for 26C — one tracker citing roughly 811 features (with close to 60% flagged for Redwood UI and 139 involving AI capabilities), another citing 634 changes across 86 modules with 359 flagged High/Critical. These numbers disagree because each vendor applies its own counting methodology to Oracle's published Feature Listing — neither is Oracle's own headline figure, and Oracle doesn't publish a single canonical "total feature count" the way these trackers do. Treat both as directional evidence that 26C is a large release, not as a number to quote precisely. For the authoritative, module-by-module list, go to Oracle's own readiness pages — What's New, Feature Summary, and Opt-In Features — for each product family.
The two cross-cutting themes both trackers agree on, and that Oracle's own readiness docs confirm:
- Continued Redwood UI migration. A large share of 26C features carry a Redwood flag — new pages or redesigned experiences built on Oracle's current design system, often controlled by a profile option so you can revert to the classic page if you're not ready to adopt it yet.
- Expanding AI agent capabilities. AI-related features span multiple product families this cycle, continuing a build-out that started in earlier 2026 updates.
26C also includes compliance-relevant changes — Oracle's Feature Listing for this cycle includes an Applications Security change and multiple Local Compliance & Reporting features requiring setup. For any Financials tenant under SOX or similar compliance scope, these deserve dedicated review, not just functional regression testing.
How to Actually Read Oracle's Readiness Documentation
This is worth covering because most consultants skim the What's New PDF without understanding the classification system Oracle uses — and that system tells you exactly where to focus testing effort.
Every feature in Oracle's readiness docs is tagged with an impact level:
| Impact Level | What it means |
|---|---|
| Large scale | Higher potential impact due to complex design — this is where your acceptance testing time should concentrate |
| Small scale | Minor impact, typically field/validation/program-level changes |
| Report | Minimal impact; new or modified Oracle-delivered, ready-to-run reports |
| None | Not delivered enabled; you control if and when to enable it |
Separately, features may show "Potential Setup" in their Actions to Enable — meaning there's prerequisite or optional configuration to consider, which can itself change how much the feature affects your business processes even if its impact level looks small on paper.
The practical workflow this enables: don't read the What's New document front to back. Filter directly to Large scale items in the modules you actually run, cross-reference against Opt-In Features to see what's auto-enabled versus what requires a deliberate decision, and build your regression test plan from that filtered list — not from the full feature count.
The Feature That Actually Matters Most for Technical Consultants: Data Extraction via ADW
Buried in the Projects/PPM readiness notes (though it applies platform-wide) is the change with the biggest long-term implication for anyone doing integration or reporting work: Oracle is moving data extraction off the transactional instance entirely.
What's changing: Fusion now supports automatic, near real-time replication of Fusion Cloud data into a dedicated, read-only data store within Oracle Autonomous Data Warehouse (ADW). Extracts are built against predefined business views that provide a functional perspective over the replicated data, rather than against raw transactional tables — and data extraction runs against the replicated ADW instance, not the live transactional database.
Why Oracle is doing this: it explicitly decouples reporting/extraction load from the transactional system that's actually running your business — a genuine architectural improvement over hitting production tables directly.
The line that matters most for anyone who's built extraction pipelines: Oracle states this approach "will eventually replace data extracts using BI Cloud Connector (BICC) and BI Publisher." This isn't a minor addition — it's a signalled direction of travel for how Fusion data leaves the platform going forward. If you're building new extraction integrations today, this is the approach to evaluate first, not BICC.
Setup isn't zero-touch. Getting access requires the ORA_ASE_SAS_INTEGRATION_ENABLED profile option set to Yes (don't change it if it's already set), assigning the duties under Access Requirements, and granting the specific role for uploading/downloading extract files. Worth flagging to any client planning to adopt this in 26C: it's a genuine setup project, not a switch you flip.
What this means practically, right now: BICC and BI Publisher extracts aren't being turned off in 26C — "will eventually replace" is Oracle's own phrasing, not a deprecation notice with a date attached. But for any new extraction work being scoped today, this is the direction to build toward, and it's worth raising proactively with clients who are still defaulting to BICC out of habit.
A Smaller but Real Example of Why Naming Changes Matter to Integrations
SCM's 26C readiness notes include a case worth knowing purely as a pattern: the Routings page has been renamed to Operations, to align with Fusion Manufacturing terminology. Existing page layouts referencing the Routings table are preserved, and drill-to actions continue working — but you'll see "Operations" referenced in the UI going forward instead of "Routings."
This is a small change in isolation, but it's a useful reminder of a broader discipline: quarterly updates rename, restructure, and relabel UI elements more often than they change underlying data structures, and an integration or report that hardcodes a UI label somewhere (rather than the underlying object) is the kind of thing that breaks silently after an update with nobody quite sure why. Worth a specific line item in any 26C testing plan: check for hardcoded labels, not just broken functionality.
Oracle Integration Cloud: What's Actually Shipped Around 26C's Timeframe
Since OIC runs on its own monthly cadence, here's what's landed in the releases bracketing Fusion's 26C window — verified against Oracle's own OIC release notes.
OIC 26.04 (April 2026)
- Human-in-the-Loop (HITL) for agentic workflows — deliberate placement of human oversight at key decision points in otherwise autonomous agent workflows. You can now model deterministic approval workflows and embed them directly in Agents, adding approval checkpoints before high-stakes tool executions or for exception handling. Built natively within OIC Projects, exposed to agents as tools.
- New adapters: BigQuery (native connectivity for loading, extracting, querying Google BigQuery), Databricks (SQL warehouses, schemas, tables), ActiveMQ (message consumption and publish via Artemis brokers), RabbitMQ (certified for both cloud and on-prem instance versions), and a Shopify GraphQL adapter with broad API version certification.
- AI Agent Invoke Native Action — integrations can now directly invoke OIC AI Agents from a standard integration flow.
- OIC File Server improvements — support for the
ecdh-sha2key exchange algorithm (stronger secure file transfer), plus a new OCI Console metric specifically for monitoring concurrent connections consumed by the File Server — genuinely useful for anyone who's had to guess at File Server load during an incident. - AI-assisted editing with auto-checkpointing — the AI Assistant now auto-saves progress while making AI-driven changes, so an unwanted generated change can be rolled back without having to have manually saved beforehand.
OIC 26.07 (July 2026)
- Native end-to-end CI/CD for OIC — this is the standout feature of the cycle for anyone doing serious DevOps around integrations. It covers managing project artifacts, Terraform configuration, deployment execution, and post-deployment updates — supporting initial seeding, project upgrades, credential rotation, lookup changes, rollback, version tracking, retry logic, and async status monitoring. For teams that have been hand-rolling promotion scripts around OIC's REST lifecycle APIs, this is a meaningful native alternative to evaluate.
- AI Assistant best-practices validation — the assistant can now check whether your integration design adheres to OIC design best practices and, in some cases, offer to directly apply its recommendation.
- Agent-to-agent (A2A) connectivity — the first native action for the Oracle Agentic AI ecosystem, specifically enabling OIC to invoke Fusion AI Agent Studio agents directly.
- Activity stream viewing audit — OIC now audits who views the activity stream of integration flows, which matters specifically for OIC for Healthcare customers, where this is a HIPAA compliance requirement.
One practical caveat on 26.07 specifics: Oracle's own 26.07 What's New page carries an explicit disclaimer that it's a working document subject to change closer to the actual release — treat the details above as directionally accurate but verify against the live release notes once 26.07 is generally available in your instance.
Preparing for 26C: A Practical Checklist for Technical Consultants
- Confirm your cohort in the Oracle Cloud Console — don't assume it's the same as last quarter.
- Capture a configuration baseline of your test environment before it updates, so you can distinguish genuine 26C changes from pre-existing environment drift during testing.
- Filter the What's New document to Large scale items in the modules you actually run — that's where testing time belongs, not a full read-through.
- Cross-check Opt-In Features against Large scale items — a feature can be Large scale impact and off by default, which changes your timeline for adopting it versus just being aware of it.
- Explicitly test integration behaviour, not just Fusion functionality. A clean functional test inside Fusion doesn't guarantee your OIC integrations still behave correctly — Application changes can affect downstream integration behaviour that only surfaces in the connected system, not in Fusion's own UI.
- Check for hardcoded UI labels or navigation paths in custom reports, training material, or documentation that might reference a renamed object (the Routings → Operations case is exactly this pattern).
- If you're building new extraction pipelines, evaluate the ADW-based Data Extraction feature before defaulting to BICC — it's the direction Oracle has explicitly signaled.
- Remember OIC updates independently of Fusion — don't assume your integration platform and your applications changed together, or that testing one covers the other.
- For compliance-scoped tenants, give the Applications Security and Local Compliance & Reporting changes dedicated review rather than folding them into general regression testing.
FAQ
What does "Oracle 26C" mean? By default, it refers to the third quarterly update of 2026 for Oracle Fusion Cloud Applications (Financials, HCM, SCM, CX, EPM, Projects, Risk & Compliance, Platform). It is a separate release stream from Oracle Integration Cloud, which updates monthly under its own YY.MM numbering.
When does Oracle Fusion 26C go live? Test environments update August 7, 2026 for Cohort A, with production following August 21. Cohort B follows in September (test September 4, production September 18), Cohort C in October (test October 2, production October 16). Confirm your own cohort in the Oracle Cloud Console.
Is there an "OIC 26C" release? Not as a literal release name. OIC ships monthly (26.04, 26.07, etc.) on a schedule independent of Fusion's quarterly letters. People asking about "OIC in 26C" generally mean whichever OIC monthly release is current when their Fusion 26C update lands.
Does 26C replace BICC and BI Publisher for data extraction? Not immediately. 26C introduces a new Data Extraction feature built on near real-time replication into Autonomous Data Warehouse, which Oracle explicitly states will eventually replace BICC- and BI Publisher-based extracts. It's the recommended direction for new extraction work now, but existing BICC/BIP extracts aren't being deprecated with a fixed date as of this release.
How many features are actually in 26C? Oracle doesn't publish a single official total; independent release-tracking vendors have cited different counts (roughly 634 to 811, depending on methodology) because they apply their own criteria to Oracle's Feature Listing report. For authoritative detail, use Oracle's own What's New and Feature Summary documents per product family.
What's the single most important thing to test after a Fusion quarterly update? Integration behaviour specifically — not just Fusion's own functionality. A Fusion update can change application behaviour your OIC integrations depend on even when your integration platform itself hasn't changed, and that kind of failure often doesn't surface until it shows up in the connected downstream system.
Closing Thoughts
The most common mistake with any Oracle quarterly update isn't missing a feature — it's treating "Oracle 26C" as a single, monolithic thing to read about once. It's actually two independent release streams (Fusion's quarterly letters and OIC's monthly numbers) that happen to land in the same general window, a large and genuinely varied feature set best navigated through Oracle's own impact classifications rather than a vendor's aggregate count, and at least one architectural signal — the ADW-based Data Extraction feature — worth acting on well before it becomes the only option. Read the readiness docs filtered to what you actually run, test integrations explicitly rather than assuming functional testing covers them, and you'll get more out of 26C than most teams treating it as a checkbox exercise.