Oracle Integration
Start by reading. Writing into an Oracle system deserves more caution.
What is oracle?
Oracle integration means connecting to Oracle databases and applications, environments that are typically long established, carefully controlled and expensive to disturb, which makes a read only starting position the sensible default.
Oracle systems are usually old in the good sense. They have been running for years, they hold the data the organisation genuinely depends on, and a great deal of accumulated logic sits inside them rather than in application code.
That logic is the risk. Triggers, stored procedures and constraints built over a decade will act on anything you write, and the person who understands why one of them exists may have left in 2019.
So the sensible starting position is reading rather than writing. A read only integration delivers most of the value in most cases, and it cannot break a system nobody fully understands any more.
Why we prefer to read rather than write
Duara integrates with Oracle environments from Nairobi, and starts read only unless there is a strong reason not to.
We prefer not to write into Oracle systems early. Writing is where the expensive mistakes live, the accumulated logic inside these systems is rarely fully documented, and reading first delivers most of the value with almost none of the risk.
Who this is for
- Oracle holds data other systems need
- Reporting requires manual extraction
- The system is old and lightly documented
- A previous integration caused problems
Industries we serve
- Banking and financial services
- Telecommunications
- Manufacturing
- Public sector
- Large distribution
- Utilities
Problems this solves
These are the conditions around long established systems holding data everything else needs.
- Undocumented logic inside the database. Triggers and procedures built over years will act on anything written, and the people who wrote them have frequently moved on.
- Data locked in extraction cycles. Getting information out means a manual export somebody runs, which is slow and produces a copy that immediately ages.
- Licensing considerations. Oracle commercial terms can affect how systems connect, and that is worth establishing before design rather than after.
- Fear of touching it. The system works, nobody fully understands it, and that combination makes any change feel unreasonably risky.
What we deliver
Read only integration as the starting position, careful assessment of existing database logic where writing is genuinely needed, licensing checked early, and change kept minimal.
Read only integration as the default position
An assessment of existing triggers and procedures
Licensing position established before design
Data available to other systems without manual export
Any write access proved in a test environment
Documentation for whoever maintains it next
Features
- Read only unless justified. Reading delivers most of the value in most cases and cannot break a system nobody fully understands any more.
- Existing logic assessed. Triggers and procedures built over a decade act on anything written, and finding them beforehand is far cheaper than discovering them afterwards.
- Licensing checked early. Oracle commercial terms can affect how systems connect, and establishing that before design avoids an expensive redesign.
- Change kept minimal. The smallest possible footprint inside a system that works, since the risk is in what you disturb rather than what you add.
- Writes proved in test first. Where writing is genuinely needed, it happens in a test environment before anywhere near production data.
Benefits
- Data becomes available. Other systems reach Oracle data without somebody running a manual export that ages immediately.
- Risk stays proportionate. Read only integration provides most of the value with almost none of the exposure.
- No licensing surprises. Establishing the commercial position early prevents a design that turns out to be unavailable.
- The old system keeps working. Minimal change to something that has run reliably for years is the correct instinct rather than an overcautious one.
Technologies we use
- Read only data access. Reading Oracle data for other systems without altering anything.
- Database logic assessment. Identifying triggers, procedures and constraints that would act on any write.
- Licensing review. Establishing what your commercial terms permit before design assumes an approach.
- Change data capture. Detecting what changed without polling heavily against a production system.
- Test environment validation. Proving any write path away from production before it goes near real data.
The accumulated logic inside a long running Oracle database is the real hazard. It is rarely fully documented, it acts on writes regardless of where they came from, and its authors are frequently no longer available to explain it.
How the process works, step by step
Oracle integration usually takes four to nine weeks, and read only work is considerably faster than anything involving writes.
-
Step 1
Free environment review
We look at what the system holds, how well documented it is and what your licensing permits.
-
Step 2
Read only scoped first
What can be delivered without writing anything, which is usually most of what was wanted.
-
Step 3
Existing logic mapped
Where writing is genuinely needed, triggers and procedures are identified before anything is designed.
-
Step 4
Proved in test
Any write path is validated away from production, since production is where mistakes become expensive.
-
Step 5
Documented for continuity
Written for whoever inherits it, since these systems outlast the people who work on them.
Quality assurance and how we work
The commitments attached to touching a system the organisation depends on.
- We start read only unless there is a strong reason not to. Reading delivers most of the value and cannot break a system nobody fully understands any more.
- We map existing database logic before writing. Triggers built over a decade act on anything written, and their authors have frequently moved on.
- We check licensing before designing. Oracle commercial terms can rule out an approach, and finding that after design means doing it twice.
- Writes are proved in test first. Production is where mistakes become expensive, and there is no reason to make them there.
- We keep our footprint small. The risk in an established system is what you disturb rather than what you add.
Frequently asked questions about oracle
Why start read only?
Because reading delivers most of the value in most cases and cannot break a system that nobody fully understands any more.
What makes writing risky here?
Accumulated logic. Triggers and procedures built over a decade act on anything written, and the people who wrote them have frequently left.
Can you write into Oracle at all?
Yes, where it is genuinely needed, after mapping the existing logic and proving the path in a test environment first.
Does licensing affect the approach?
It can, and we establish the position before design. Finding out afterwards means doing the design twice.
Can other systems get Oracle data?
Yes, and that is usually the actual requirement. Manual exports produce copies that age from the moment they are taken.
Will it slow the production system?
Not if designed carefully. Change data capture avoids repeatedly querying a production database heavily.
What if the system is undocumented?
That is the normal case rather than an exception, and it is precisely the argument for reading rather than writing.
How soon can other systems read the data?
Four to nine weeks, and read only work is considerably faster than anything involving writes.
Can it feed a reporting system?
Yes, and that is one of the most common and lowest risk requests we see for these environments.
Does it work with Oracle applications as well as the database?
Yes, and where published application interfaces exist we prefer them to reaching the database directly.
Who should be involved from our side?
Whoever administers the database, since they know things about the environment that no assessment surfaces quickly.
What if we plan to replace the system?
Worth saying early. Read only integration suits a system with a limited remaining life far better than deeper work.
Can it run alongside a migration?
Yes, and reading from the old system while a new one is built is a common and sensible arrangement.
Does data leave the environment?
Only what the integration is designed to move, and it stays within your infrastructure.
Will it survive an Oracle upgrade?
Read only access on published interfaces generally does. Anything relying on internal structure is more fragile.
Can our DBA maintain it?
Yes, and documentation is aimed at them, since these systems outlast the people who work on them.
Is this suitable for a bank?
Yes, and read only starting positions suit regulated environments particularly well since the risk profile is easy to explain.
What about very old Oracle versions?
Common, and workable. Available interfaces differ and we establish what exists rather than assuming a modern release.
Who can access the database?
A dedicated account with the narrowest permissions that work, which for read only work is genuinely narrow.
What does Oracle integration cost?
Read only work is quoted lower than anything involving writes, both estimated after the environment review.
Glossary of terms
Oracle environment terms in plain language.
- Stored procedure
- Logic held inside the database, which acts regardless of what triggered it.
- Trigger
- Database logic that fires automatically on a change, including changes an integration makes.
- Read only access
- Permission to read without altering, which is the safest starting position.
- Change data capture
- Detecting what changed without repeatedly querying a production system heavily.
- Constraint
- A database rule that rejects data not meeting it, including from integrations.
- Environment
- A copy of the system, where test environments exist so production does not have to be experimented on.
Related services in Integrations
Talk to us about oracle
Ask who in your organisation could explain what the database triggers do. If nobody can, start read only.
Start your project