Analyzing an Oracle database without rebuilding the application
Many industrial ERPs and in-house developments store their data on Oracle. The database can usually answer more than the application on top of it shows. Onagero reads directly, read-only, and builds the missing analyses as a tool of its own.
- Read only
- No change to your ERP
- Connection included in the pilot
- GDPR ready
In short
Onagero connects to an Oracle database through a user that may only read, and creates an analysis copy in which names are masked. This produces internal tools on your server. This applies to ERP systems on Oracle as well as to in-house developments. Nothing is written.
Possible ways to the data
Which one fits for you we clarify with your IT before the contract.
Read-only database user
A dedicated user with read rights on the required tables or views. With Oracle this is the usual and cleanest route.
Read-only copy
Where the load on the production database is a concern, Onagero reads from a copy or a standby, if one exists.
Views instead of tables
Your IT can create views that show only what the workflow needs. This keeps access narrow.
What your IT provides
- a database user with read rights on the agreed tables or views
- network access from the Onagero server to the database
- an agreement on the times when larger queries may run
Good to know
We align large queries on a production database with your IT beforehand. Onagero reads in defined time windows and afterwards works on its own copy.
Turning Oracle data into a foundation to build on
What stays with you, what Onagero makes of it, and what the language model gets to see.
Onagero creates an analysis copy of the needed data on your server and describes it in the data map: the meaning of each column, relationships, origin and review status. Your people build on that.
In development, the copy holds no personal data. Released applications read from a live view only what their roles allow.
Questions about connecting to Oracle
Does Onagero put load on our database?
Fetching the data creates load, which is why it runs in agreed time windows. Afterwards the tools work on their own copy.
Do you know our data model?
Onagero works it out with you: it describes the required tables and columns in the data map, and your IT and department confirm what is correct. This knowledge is retained for every later application.
Does Onagero write into the database?
No. The user may only read.
What about licenses?
Whether additional database access matters under your license terms, clarify it with your license manager. This is not legal advice.
Which problem would
your team solve first?
Show us a real process. We will show you how it could look with Onagero.
Book a demo →