Oracle Data Relationship Management provides metadata management, flexible integration, and hierarchy customization, supporting continuous operation through reliability and security.
| Product | Mindshare (%) |
|---|---|
| Oracle Data Relationship Management | 3.3% |
| Semarchy xDM | 11.2% |
| TIBCO EBX | 9.2% |
| Other | 76.3% |
| Type | Title | Date | |
|---|---|---|---|
| Category | Master Data Management (MDM) Software | Jun 23, 2026 | Download |
| Product | Reviews, tips, and advice from real users | Jun 23, 2026 | Download |
| Comparison | Oracle Data Relationship Management vs TIBCO EBX | Jun 23, 2026 | Download |
| Comparison | Oracle Data Relationship Management vs SAP Master Data Governance | Jun 23, 2026 | Download |
| Comparison | Oracle Data Relationship Management vs Qlik Talend Cloud | Jun 23, 2026 | Download |
| Title | Rating | Mindshare | Recommending | |
|---|---|---|---|---|
| Ataccama ONE Platform | 3.9 | 8.3% | 100% | 15 interviewsAdd to research |
| SAP Master Data Governance | 3.9 | 7.9% | 91% | 32 interviewsAdd to research |
Oracle Data Relationship Management is designed for enterprise data needs, offering tools to integrate with Oracle EBS and Hyperion while managing hierarchies with version control. It automates processes using simple scripts and JavaScript for formulas, ensuring robust customization and flexibility for diverse applications. Although it offers efficient solutions for reference data management, improvements could enhance integration with non-Oracle products, expand automation and AI features, and improve handling of hard-coded values.
What Are the Key Features?In finance, enterprises use Oracle Data Relationship Management for synchronization and customization of hierarchies, managing enterprise and finance reference data, as well as supporting ERP systems for finance, payroll, and human resources. It integrates seamlessly within companies' operations, promoting efficient data management and self-service assistance.
MTN, SITA
| Author info | Rating | Review Summary |
|---|---|---|
| Senior DRM Architect at a financial services firm with 10,001+ employees | 4.5 | We use Oracle Data Relationship Management for managing enterprise and finance reference data. While DRG features are beneficial, improvement is needed in automation and AI capabilities, as well as better external connections and APIs. We haven't seen an ROI yet. |
| Coordinador de Sistemas Operativos y Bases de Datos at a educational organization with 501-1,000 employees | 4.0 | In my organization, we use Oracle Data Relationship Management primarily for its robust and secure ERP capabilities. Although we haven't fully developed many solutions with it, we're evaluating other options. Improvements are needed in its fees and licensing. |
| Senior DRM Architect at a financial services firm with 10,001+ employees | 5.0 | I rate this flexible solution 10/10, valuing its JavaScript formulas for automating manual entry. Cloud setup was complex, and exports need improvement, but stability is good. Note its 2030 sunset. |
| Business Process and Strategy Specialist Advisor at NTTData | 5.0 | I find this a great, stable solution for centralized metadata and hierarchy management, offering valuable features and top-notch support. Just avoid hard-coding values and using it for SKU-level data for optimal performance. |
| Business Process and Strategy Specialist Advisor at NTTData | 4.5 | I find DRM excellent for managing hierarchies and syncing applications, with DRG drastically improving governance meetings. Its flexibility and stability are great. However, it's very expensive with a slow ROI, and better, cheaper alternatives like EPMware exist. |
| Solution Architect at a comms service provider with 10,001+ employees | 3.5 | This product integrates well with Oracle EBS/Hyperion, effectively managing reference data and improving reporting consistency. However, I find its integration with non-Oracle systems limited, and wish it had better combination and cross-validation mastering. |
We use Oracle Data Relationship Management for enterprise reference data and finance reference data. Additionally, we utilize it for master data management in our industry.
It has been fine for what we need it for, adapting to changes in regulations and compliance requirements. It supports our data management processes by providing the ability to have validations over data and set up workflow processes that follow business approval processes.
There is a scope for improvement in automation and AI capabilities within Oracle Data Relationship Management. Better external connections and API integrations are needed.
We have been using Oracle Data Relationship Management for about 20 years.
The product is scalable enough for our needs. We have found it scalable enough as approximately four to five hundred people are using it in our company.
Technical support by Oracle is very difficult. It takes a long time to communicate when we have issues and to come up with a mutual understanding of what the issue is, and then actually get the issue addressed.
Negative
The initial setup was straightforward, however that was 20 years ago, so it was very different from what it is today.
We have not observed a return on investment with Oracle Data Relationship Management.
I am not privy to pricing information, but we have a very good deal with Oracle, having an enterprise license.
We haven't actively been looking for other options on the market, so I couldn't say.
I would recommend Oracle Data Relationship Management for what it can do for our organization. However, it could be too expensive for very large companies to purchase and maintain.
I'd rate the solution nine out of ten.
I use the solution in my company as an SIS system. My organization uses an ERP system, and we use Oracle DB for the ERP part. My organization manages systems, finance, payroll, human resources, and self-service assistance with Ellucian Banner ERP.
The solution's most valuable feature is its continuity. We trust that our systems can work continuously, and it is a robust solution with great security.
At the moment, we are using the tool only as an ERP. We have not developed many of our solutions with Oracle Data Relationship Management. We are in the process of transitioning and evaluating many solutions apart from the ones offered by Oracle. We try to evaluate the solutions to find the best tools for our requirements.
Improvements are needed in the fees and the licensing part. The tool's price can be made lower.
I have been using Oracle Data Relationship Management for twenty years. My company is planning to move from Oracle 12c to Oracle Database 18c and then to Oracle Database 19c. I am a customer of Oracle.
It is a stable solution. Stability-wise, I rate the solution a ten out of ten.
It is a scalable solution. We don't use the tool's scalability part in our company, but we are trying to use RAC to put the database on many servers, and such an option makes scalability very easy. We don't need more than one server for our operations. In twenty years, we have only one problem with the product, and I think it's a good product.
If one is difficult and ten is easy, I rate the product's initial setup phase a nine.
The solution is deployed on an on-premises model.
Deploying a new database or a new server with a database takes two hours. Since we are programming the deployment of the new server with Oracle Instant Client, it takes at least two hours.
My company is able to solve many of the problems with the help of an in-house team.
The price of the solution is very, very high. The commercial part from Oracle is its worst part. It is very difficult to negotiate with Oracle. My company has had some bad experiences with Oracle in the past. It's difficult to translate my experience right now. Oracle indulges in bad practices to obligate users to buy more licenses. When I bought licenses from Oracle for databases, I saw how email software was included as a part of the negotiations even though it was not software that Oracle supported. My company had to continue paying for the email software as it was a part of our contract with Oracle, and the price was high.
Technically, it is a very good product.
I recommend the tool to others.
I rate the tool an eight out of ten.
We use the solution extensively across our organization.
With this application, if data was entered manually with a system whose data we migrated onto the DRM system, we can automate 90% of that manual entry.
The feature I find most valuable is the ability to use JavaScript in formulas because it's a lot more flexible in the way that you can program it.
One area of the solution that has room for improvement is the export capabilities.
An additional feature the solution could include is more flexibility in the workflow capabilities and the way that it is displayed.
I've been using the solution for seventeen years.
The stability of the solution is very good.
The scalability of the solution is good to very good.
From a read-only perspective, we have thousands of users. From people that actually maintain data, it's probably 100 users, our data modelers. We use the solution extensively and have plans to increase usage.
The initial setup of the solution was complex. We're a highly regulated industry that requires a lot of security, so that is quite typical.
When we first implemented the solution seventeen years ago, it was a lot smoother operations, but when we moved to the cloud, it was extremely complicated.
We used a consultancy firm for the deployment. They were very good and helped us out a lot.
We did evaluate other options before choosing this solution seventeen years ago. The real selling point of this system was that it could be programmed and managed by business people, not technical people. That was really the selling point of it.
The thing people need to look at when considering this solution is that the DRM application has a sunset of 2030.
I would give this solution a ten out of ten, because it is an extremely flexible tool that you can customize to your business needs.
Having a central place to maintain hierarchies that are pushed to multiple applications reduces the headache of the business user chasing their tail trying to figure out what the difference is. Since you have hierarchies centrally maintained, everyone is working from the same starting point.
The last area that needed to be improved has gone through major renovations with the latest release. DRM now comes with a workflow capability that rivals most workflow that you have to pay for separately if you use other metadata applications.
If you hard-code values into the properties, you'll get customer complaints that DRM is "running slow."
I've been using it for 10 years.
DRM is one of the most stable metadata applications if, as with any other tool, you use it correctly. Don't hard-code values into the properties as this is the largest culprit of customers saying that DRM is "running slow."
Another stability issue is what we call "cliff hierarchies" where you have a parent node and an excessive number of children. Once you get to a number of children that doesn't fit on a screen, maybe it's time to add another parent to break up that section of the hierarchy.
They only issue that I have had with scalability was when a client insisted having SKU-level information in DRM. DRM is not a SKU-level tool, so please use the proper Oracle tools to manage at that level.
Customer Service:
DRM customer service is top notch since it is a small set of people that use it. The people who answer the questions are knowledgeable.
Technical Support:
Technical support is top notch. I have never had an SR come to the point of, "I don't know how to fix this issue." It's always, "here is a workaround" and/ or "we will have the patch shortly."
Most people move from a home-grown Java process. We made the switch because the person who originally created the process was leaving or had left the company or planned to retire, putting them in a high-risk position.
Just follow the prompts for the basic setup. The API is slightly more complex, but if you need help, just look at the admin guide.
I have installed and upgraded both in-house and with a vendor. Honestly, if you have a good DBA who can read and make themselves knowledgeable with the product, you will be OK with the basic install and setup. When it comes to more advanced setup, that's when you need a vendor.
This is a pay-by-node software, so it really depends on you corporation.
DRM is an all-around great solution for managing your metadata. It not only gets all your hierarchies in one central location, it also gets your business more involved with the management of metadata.
You have multiple hierarchies and downstream applications that need to be kept in sync. There is a need for alternative hierarchies and customization of the outputs to the downstream applications.
Have you ever been in those Governance meetings that are always to long already and always run over that obnoxiously long time? I have. I just got through implementing the workflow in DRM at a client that this issue was prominent at. People were not showing up to meeting because they simply didn't have FOUR hours to burn in a meeting where most of the time was spent looking for missing approvals and supporting documents.
Implementing the workflow portion of DRM which is called Data Relationship Governance(DRG) the client cut that time down to an hour. This brought attendance to a all time high of 100% participation, this also meant that they had time to talk about more important things like the what was going on in the company, bringing them closer together and more efficient as a team.
What makes DRM valuable to a Company? Well, Its Agnostic! That right, sure it has some direct integrations with some specific EPM tools, which are super sweet, but it can write directly to a Database table, File, or even XML. Imagine a life where all your hierarchy/metadata information is can be accessed and maintained in one central location. Wouldn't that be great!
Automation is handled by a very simple batch script, which if variables are done properly are super flexible and will reduce maintenance.
The ability to customized properties in DRM help went adding new member to the hierarchy. Lets say you have an organizational hierarchy and you get a new employee. Just think of some of the things that you could Dictate about that employee biased on what his manager is? Have you thought about all the manual things that you are going to have to define about him or her? What if I told you that you could create properties that when you add an employee it would tag that said employee with all of that information. Now this is a interesting example of how DRM can work, but its not limited to your employees. Think about your down stream applications. Do those applications have a hierarchy? Yes
The only area that I could see that DRM could need improvement is well...nothing. Knowing where DRM/MDM/Razza/BankOne came from, I like it just the way it is.
They only time that we had issues with Stability was back when it was 11.1.1, since going to 11.1.2 the stability has been outstanding.
DRM is a metadata tool, however I have seen companies try to put information that DRM was never intended to manage. That would be the only scalability problem that you would have. Basically know the person implementing it. make sure they are asking all the right questions.
Customer Service:
Oracle customer service it top notch.
Technical Support:
When you need tech support you will get someone knowledgable.
Database tables. Switched too DRM to save time, frustration, Money. Using a customized solution is never good for governance as there are very little actual governance taking place.
Initial setup is very straight forward, just follow the wizard.
Vendor team. DRM needs a person with some expertise to make sure that you aren't creating something that is unmanageable. DRM comes with very little actually in it. Mostly custom.
The ROI will be a few years. DRM/DRG is really expensive. There are other options out there for less money and you get more. EPMware comes to mind they have an unlimited node count and direct connections to up and downstream systems.
DRM can be a little bit expensive. Negotiate with the sales person and hold out of a reasonable price.
I did but that was a long time ago so I don't remember what other tools were in the running. I think one of the other tools that we evaluated was EPMware. EPMware actually beat DRM in every category but the client was so invested in Oracle we HAD to use DRM/DRG. That client has since moved off DRM and DRG to EPMware.
Design before you build. Take everything into consideration. Implement DRM and force your business users to get involved in the conversations as they are going to be the people entering information into DRM or DRG.
Give those Business users the power to do what they should be able to, they do know the most about the business anyway.
As a product that integrates out of the box with Oracle EBS and Hyperion the product has proved to be a great step forward in allowing us to manage reference data across multiple platforms and something that we were able to deploy quite easily. Key has been the standard integration with the other Oracle products. The ability to manage hierarchies with various versions has also proved useful as has the what if capabilities.
It has enabled us to replaced existing legacy custom built solutions whilst at the same time providing greater functionality and flexibility. We are now able to produce hierarchical reporting at a much greater consistentcy.
Integrating with non-Oracle Products needs improvement, it only provides a text output file. Another area that would be useful is in mastering combinations and with Cross validations rules. That would make integration and translation from legacy systems easier to manage.
This has been in use with us for 18 months.
Nothing substantial. Once we understood the scope of the capabilities it was fairly straightforward.
No.
Not yet.
We switched from a very old custom solution.
We used OCS who had full knowledge of the system.
