Oracle Database Reviews

We use Oracle Database for automatic banking systems to store the information about the accounts, the card being used, and all the other customer profile information.

The performance and reliability are the best features of the Oracle Database.

The client-side of Oracle Database could improve. The client graphic user interface works on Java and sometimes it freezes, these should be fixed.

I have been using Oracle Database for approximately 10 years.

The solution is stable.

Oracle Database is scalable, it is one of the most scalable solutions.

We have approximately 1,000 users using this solution. We plan to increase usage in the future.

The support is very good, they have done some presentations in Armenia and we are working very closely with them.

The installation is easy for a person who knows how to do it and for a person who is not familiar with this kind of tool it is difficult. However, generally, it is okay for me because I have worked with a DBA before.

The solution is expensive.

I would advise others this is a stable and scalable product, which you need to use in case you have, for example, huge data. If you would like to have more transactions and a secure platform, this is a good choice.

I rate Oracle Database an eight out of ten.

We use version 12c, but are planning to migrate to 19c. 

The solution is suitable for enterprise applications. We use it for trade systems and a betting system. We use it with applications that need a huge amount of data, such as SQL enterprise applications.

The licensing could be cheaper and clearer. It is not clear how it applies to certain options. The licensing of the solution for only several virtual servers is a big issue which should be addressed. 

I have been using Oracle Database for many years, perhaps since 2001. 

The solution is stable. 

I have not had direct contact with tech support, although my colleagues have. 

I cannot comment on the initial installation, as it is handled by the Database Administrator, not I. He possesses the skill to install the solution and has never mentioned any issues with this. Perhaps my colleagues would be in a position to give a more comprehensive answer. 

In respect of the deployment and maintenance, we have two administrators, developers, an architect and a tester who are in charge of four applications. 

The licensing could be cheaper and clearer. It is not clear how it applies to certain options. The licensing of the solution for only several virtual servers is a big issue which should be addressed. 

The license is yearly. 

Although I would recommend the solution for certain applications, as there are licensing issues, I would prefer to use PostgreSQL where possible. 

There are many people making use of the solution in my organization, including developers, testers, end users and end application users. We may be talking about thousands. But when it comes to those with personal experience using the solution, we are talking about 40 or 50 people. 

We plan to continue using the solution, as there are certain applications of ours which must remain on Oracle Database. 

The solution is stable and has good performance. Licensing is the big issue we encounter. 

Were I to rate Oracle Database strictly on its technical capabilities, I would have to give it a rating of nine out ten. However, its licensing issues bring this rating down to seven. 

We are using the Oracle E-Business Suite ERP system and the backend of that application is Oracle Database. We are using the customer care and billing application and the backend of that application is also Oracle Database. 

The customer care and billing capabilities are very good.

It is very stable. We are getting good performance from it. The reliability is excellent. 

It's one of the leading databases on the market.

We get good support on the database side. 

The cloud setup is very simple. 

The solution works well for enterprise-level organizations.

We've used the solution for so long, it would be hard to switch off of it. 

On the ERP side, they do not seem to be improving the on-premises version. They seem to want to push the cloud option on users. The roadmap for each seems to be diverting, and the on-premises side simply isn't getting the same amount of attention.

The pricing could be high.

In our company, we've been working with the solution here for 15 years.

The solution is quite stable. There are no bugs or glitches. We do not find that it crashes or freezes. It's reliable.

The scalability is very good. They are providing the structure, the architecture, and everything you need to scale. It's very easy to scale to whatever size you need. Usually, we can do scalable sites with no issue.

Technical support is okay for the most part. On the database sites, things are okay. However, if we talk about the application sites, sometimes we are getting a response time that is delayed.

The initial setup, for the cloud implementation, is very straightforward. Companies won't have any issues with the deployment. 

The solution is very expensive as they are charging their products in different categories. For example, we have to pay on the application side, on the technology side, and on the licensing. On an enterprise level, if we compare with other solutions, there are a lot of open-source options which would be cheaper.

We're just a customer and an end-user.

I'd rate the solution at a nine out of ten. I'd rate it at a perfect ten if the could and on-premises versions we treated with equal weight, and they didn't try to simply push cloud on users. 

On the enterprise level, it's very stable and reliable. It's great if users are looking for enterprise quality. However, there are options available in the Unix and Linux systems as well. 

We use it internally for some small odds and ends. Two of our biggest clients use this solution. One client has more or less a data warehousing application. Another one has more of a transactional and pseudo accounting application.

I am currently using 12c, but I have also done some work with version 18. This July, we're going to upgrade most of our main databases from version 12 to version 18, which is fairly current. I believe they have version 20 available at this point.

The thing that probably stands out the most about Oracle Database is reliability. I have been working with Oracle Databases for over 25 years, and I have never lost any data due to a machine going down or any events that were not stupid human tricks. I've never lost anybody's data using Oracle. It gets the job done and doesn't fail. 

It does what I want it to do. It has got a lot of features. Anytime I need a feature, I am able to find it in Oracle Database. It has never happened that I found a feature in any other database, but I was not able to find it in Oracle.

There is a lot of room for improvement. It is not meant for dilettantes. It is not meant for people who don't work on it day in and day out. Ease of use is probably the biggest complaint. They're getting somewhat better, but it is not as easy or intuitive as it could be in terms of maintaining and managing the database. The day-to-day maintenance and the ability to easily do things and keep things up to date can be painful.

Their support portal requires a person to become well-trained in how to use it. I'm sure it has lots of features and capabilities but to try and get support is somewhat painful. They are pretty good at handling absolute critical emergencies, but with the exception of absolute critical emergencies, getting problems solved from their support system is difficult and takes a long time. I had to do an update, and it was not straightforward to get the right patch kit. I'm getting to the point now where I somewhat understand how to use their support website, but it is not intuitive.

Probably about 80% of their online documentation is useless. When I have a question about what to do or how to do something, the things that come up on top when I do a search, of course, are Oracle websites. I always skip right past those and go to other websites. There's an old expression from my youth, "I want to know what time it is. I don't want to know how to build the clock." When you go to the Oracle documentation, you have to plow through page after page of stuff to get to anything that looks anything like an example of what it is that you might actually do. There are lots of other people who have filled that gap, and there are also websites where you can easily find the answers to most of your questions.

I have been working with Oracle Databases for over 25 years. The first time I started using Oracle Database was around 1995. It was probably version 3 or 6.

It is one of the robust products from a stability point of view. I have not really found bugs or glitches. However, on a test database, I had an issue the other night where Oracle decided to behave badly when I was trying to do a query. The solution was to get the latest patches and install the latest patches. Everything worked fine after that. I did all of that without contacting Oracle support. I needed to get what I was working on done. So, I had to plow through to find the answers. I had found some people making some oblique references to what the problem might be. I then took a chance on doing the update. I found the patch kit, but it was not easy to find the right patch kit on their website. 

In the data warehousing database or application, we have tens of millions of rows in different tables, and we have no problems there. However, in that particular application, we're not dealing with transaction processing. So, I can't answer the scalability in terms of transaction processing. On the hardware platform that I've put together for the main database of this one customer, I am very pleased with the performance of the data warehousing aspects and being able to query data quickly and do bulk inserts and things of that nature. For data warehousing scalability, I can attest to the fact that it is great, but for transaction processing, I don't have the experience to be able to provide information.

Two of our biggest clients are quasi-governmental in the sense that their business is based on government funding. One has 60 users who use the application day in and day out, and their database is relatively small. The other application has about 20 dedicated internal users, and then there is a web interface. It has around 3,000 to 5,000 users, but typically, there are about 20 concurrent users. 

Their support portal requires a person to become well-trained in how to use it. Getting support is somewhat painful. They are pretty good at handling absolute critical emergencies, but getting other problems solved from their support system is difficult. It takes a long time. I had to do an update, and it was not straightforward to get the right patch kit.

I am the technical resource of last resort for our clients. I work with a number of technical people. When it gets to the point that it wasn't an easy problem to solve, they come to me, and I end up getting all of the tough problems to solve. I like that, and I would rather do that than just working on the same thing day in and day out. I am always trying to solve problems, and that's why I end up having to interface with Oracle support. The ability to solve problems better by using Oracle's support tools would be beneficial for me.

Its initial installation and setup have become better. You can set up something fairly easily these days. If you need to do anything that is not straight out of the box, figuring out how to do it is not easy. If you want to just set up your average everyday database, you can get it up and running with a few mouse clicks.

As a consultant for the last 40 years of my life, the conversation with anyone who wants to use a product would be a lot more in-depth and detailed where I'd be asking, "What is it you want to do? How do you want to do it? Where do you want to go?" It isn't the kind of thing for which I'd say, "Yeah, Oracle's a Swiss army knife, the best thing since sliced bread."

It is one of the more robust products from a stability point of view. There is a bit of a learning curve. From a transaction point of view, if you have the right hardware, Oracle is probably as or more scalable than anybody else. If your application is going to be massively scalable, Oracle is probably your best tool. If you're just going to put together a small application for occasional users, there are easier tools to learn and use. Some of them are even by Oracle.

I would rate Oracle Database an eight out of ten. It is a great product.

In the last project, we had a big warehouse. It was a logistics company, and we had all company data stored in this. We also had insurance use cases. We had all contracts, customer data, and all kinds of stuff.

It is one of the most reliable database systems. 

With the new version, we never came across any important limitations. There was nothing that needed improvement. However, in versions 9 and 10, we sometimes had problems, and big and complicated queries did not get through. In versions 11 and 12, I did not experience any problem.

There could be some more information about load balancing and all these things. For me, it was just a part of the infrastructure maintained by other people. So, I cannot really say what they need.

I have been using this solution for decades. I worked for a company developing insurance software in the nineties, and we used Db2 and Oracle.

It is perfectly stable.

It is scalable. The number of users differed a lot. There were not that many who used it directly. It was mainly was used by programs written by me. There might be around 100 users who used these programs.

I have not interacted with them recently. I don't know whether our database administration team contacted Oracle. I just know it was usable from our layout or view.

We have used Oracle, SQL Server, and Db2, and all of them were okay for our purposes. In the new project, we will probably use Oracle, but we might also use SQL Server. I'm pretty neutral this way, as long as it works.

I am not the one who does the database administration and installation.

I would recommend this solution. It is certainly a valid option.

I would rate Oracle Database a ten out of ten. It is one of the best solutions.

We have 5 Oracle servers having 3 RAC and 2 Stand Alone servers.All using Oracle 12c R2 SE.

1 DR standalone server is also there .

Oracle was the first choice at the time of creating our application because of our very low load.

Now when our application has become mission-critical, Even with the SE version we are able to deal with a complete load very efficiently and effectively.

The most valuable features of this solution are the performance and its inbuilt services.

In Oracle we can find out most services are inbuilt. scalability, high availability, split brain handling , Null handling  ,it working of execution plan . All these features have helped us many times . 

As of Now Oracle has gained an image of Customer binding database.

Once some one opted for Oracle database , it becomes very difficult in many ways to move on other database.

As of now oracle can be considered as Top of the list and many of the database are not enough close to oracle concepts and it's standards so it's kind of responsibility to Oracle to bring a fair competition in market. 

In return ,it will help Oracle itself. Take an Example of Football. Consider Oracle a high level Club who have it's own Practice and playing Area but only his own rules are implemented. Any player who is a beginner and cannot afford such a high clubs will start practice in small arenas which have some what similar rules .Once Player's practice gave him confidence to go for a big club ,he will feel comfortable in choosing a club whose rules are known to him , Not someone for whom he has to change his playing technique. 

So Oracle should consider working in this direction so that he can keep the control over the wind of Market. 

I have been using this solution for two years.

We are currently using Oracle 12c SE Release 2.

In terms of stability, we know that Oracles releases quarterly batches but we have still been faced with many bugs over the last year.

I cannot say that it is stable.

This is an area that needs improvement.

It's a scalable solution.

As known to everyone, One of the best.

This is one of the portion where Oracle have to be little bit loose .I have raised only around 7-8 tickets including 2 P1 , but it always looks like I am talking to a bot with pre recorded  statements when the person is not able to answer. Most of the times information is attached , but they still insist very hardly to send it in there format so that there machine can read it .

Nope , Oracle was used from Starting.

All is easy, given that you must know what are you using it for.

Depending on the services included, it seems little bit expensive. 

In starting we didn't evaluate much, but giving the condition of ending support , we do not have any choice so we are looking for other options including upgradation as well.

Oracle is good for large scale environments.

New startups MUST always think of other options before going to Oracle.

We work in agriculture, and where we're located we have two sites in two separate cities in Canada. These are all transactional databases and they have information in them about the dairy industry in our country. We use it for storing data related to dairy cows, dairy farmers, or farmers in general, and we have all the information in the transactional database that holds everything from billing to individual animal data. We probably have about 12 terabytes of data on the Oracle databases.

The reliability and the ability to store all the information we need is how it helps us the most. I don't know the metrics of the top of my head, I just know it works. 

We decided to use Oracle from the start because of its reputation of robustness. It provided us with everything that we needed. 

The reliability is the solution's most valuable feature. We've had great success with the solution.

The ability to do all the programming we need in one solution is great.

The support has been very good over the years.

The main thing we find could use improvement is the licensing costs. It is quite expensive relative to other database vendors. Cost always comes up as an issue for us as we consider upgrade paths. It's not as easy as we would like it to be. 

While we really like Oracle, it's difficult sometimes to upgrade from version to version.

I'd like to see the high availability option become available in the standard edition. We have a couple of databases that are still in the standard edition, and we'd like to be able to back those up and have higher availability.

We've been using Oracle for a long time. We originally started using it in 1999 just before the Y2K crisis.

The stability is very good. I'd rate it ten out of ten. We have some databases that run for a year without rebooting or anything, so I would describe it as very stable.

We do have a couple of international projects for our users that will be accessed from other countries, but it's currently stable.

There's no problem with scalability. It's quite easy for an organization to expand if they need to.

We have many users on the solution, including myself, and I have an administrator role. We have five database administrators that manage the day to day operations of the database. Then we have about 20 developers that develop different applications or make changes to the database for us. There are also internal users. We probably have, I'd say, 500 employees that have access at any given time. Our customers also have access. In total, we have about 15,000 people on the solution.

Technical support, on a scale of one to ten, I would give a seven. There are some things that take a little bit longer to resolve than others, however, overall, I would say it's good. It's not very good. It's not excellent. It's good.

We haven't gone anywhere else and tried any other database software. We did previously use IBM's Mainframe 20 years ago.

The reason why we switched was because we were changing our data center. It's a little bit complicated, but there used to be four organizations that did the same thing we did. And due to the Y2K scare, we decided to merge all these organizations into one data center. It was more of consolidation from different technologies into one Oracle technology.

I was not really involved in that migration. I was there, however, I didn't have a role in it. Oracle was ultimately chosen based on the robustness and they had. 

It was a very big undertaking. We moved from an IBM mainframe. With regards to Oracle, the set up was, I would say, easy, however, when you're building a database, there's a lot of things to think of. That's not really the database's problem. You have to think of and plan out your table structure. You have to think of how you're going to set up your database. 

The deployment happened 20 years ago. It was a very big project. The implementation took a year to migrate our existing data into an Oracle database. It went well, although it did take about a year to implement.

You need about five people to handle maintenance on the solution.

We used a consulting firm to assist us in the implementation at the time. The experience was good at the time. Still, it was 20 years ago. They're actually out of business now. They may have gone out of business ten years ago, or merged with another company.

Our licensing costs are between $40,000 and $50,000 per year. Those are the costs that cover maintenance and licensing. 

We have an enterprise edition. We pay extra for features that are only available with this particular tier.

We did evaluate different databases, including IBM's Db2. And that was it at the time. Microsoft didn't exist back then for databases.

We started using version 7 of Oracle, and now, after so many years on the product, we are up to version 12.

We have six different main production databases that we use for various things. They're all on-premise. They either run in a Linux environment or IBM AIX Unix environment. And we also use a backup Oracle cloud for backing up some of those databases.

The main advice I would give other organizations would be to prepare for the costs. Oracle is kind of more expensive than in most other database software. It's also important to have a good understanding of how Oracle works and the programming. It's quite specialized. However, if you're implementing a big database environment, you need to know that anyway. 

Oracle is, I would say, probably the top database provider in the world. Having a big name, for us, was good because we've got other contracts from outside firms that trust us because we house our data with Oracle. 

At the end of the day, you get what you pay for, and we don't mind paying more for the peace of mind we get from this solution.

I would rate the solution nine out of ten mostly due to the fact that it's a very solid platform and it's robust and it's scalable. It's the Cadillac of the database world.

We primarily use the product to store textual data and support applications like our HR and case management systems.

The platform's security features and stability are commendable.

They could provide ease of migration and competitive pricing for the database.

We have been using Oracle Database since 2005.

I rate the product's stability a nine. We haven't encountered significant issues.

Around 500 users access Oracle Database regularly in our company. We haven't faced scalability issues; it's more than enough for our current needs. 

Once you're familiar with the product, setup becomes easier. Single-node setups are quick, but integrated configurations can take more time.

We get help from integrators to set up the database.

The platform is highly-priced. 

I rate the security features an eight or nine.

I would hesitate to recommend Oracle Database solely due to its high cost. If pricing were more competitive, I'd be more inclined to recommend it.

Overall, I rate the product a six out of ten.