Oracle Database Reviews

It is our core for bank processes.

The scalability is very good, and it is stable.

The interface is not reliable because the GUI is old.

It needs to be more attractive.

It is very stable.

The scalability is very good.

We have about 120 users.

It was implemented by a vendor.

We have a yearly license.

For us as a bank, the price is not too high, but for a small business, it would be an expensive solution.

I would rate Oracle Database at nine on a scale from one to ten.

As a database, the solution has been number one from the beginning, in my experience, because of the features and the performance. The solution has a number of Features including , Maximum Availability Architecture for  zero downtime and Zero Data lost.

The only issue is the speed that Oracle is going with the technology transformation. The marketplace is not adapting. As a whole, Oracle innovation is very fast as an organization, but end users are not so much in a hurry to go.

An area that could be improved is information. Everything is going on containerization architecture now. Oracle is also coming up with data Shards with their Multitenancy Architecture to support this containerization. The gap is in marketing the features and the knowledge that the end users are having. The end users must be educated about the current features, and that is what is lacking with Oracle.

Additional features that could be added in the future need Real Time Analytics features and multi-cloud support. But I have seen Oracle is coming up with the Lakehouse and the delta Lake concepts.  Oracle is heading in the right direction, but the features should be communicated to end-users in the proper way.

I've been working with Oracle for over twenty years.

Overall, the technical support is a little bit lacking, and they should improve. Especially the team who is deployed to handle these tickets. Around 50% of the team itself is lacking some knowledge on handling texting and knowledge. They are very good superior resources, that I understand, but in the APEC region, a little bit of lacking. Especially in India and Singapore, because those are not well handled. But in the US, they handle those things.

Positive

I believe Oracle has reduced the pricing.

Every thing starts with a proper foundation , so as with Oracle Database Architecture. Any one with solid architectural foundation will have a life long journey with Oracle Database. 

This knowledge includes conceptual understanding hands-on with scenario and solutions basis which will allow the DBA  to get through with the product. This What I am doing in the trainings that I conduct - https://www.youtube.com/c/tech...

I would give the solution a nine out of ten.

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 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. 

My use case is a lot of banking solutions. Data sometimes is static in nature, but in a majority of the cases, it is dynamic as well. Oracle database is a focalization database.

Oracle Database has good performance dynamics with respect to oncoming data and fetching of data which gets loaded. All of the same processes are done by a system database administrator or even user initiated financials.

I've found performance streaming to be a valuable feature.

It is also a stable and scalable solution.

It is easy to install and easy to use as well.

They need to work on non-relational data a bit more. If Oracle Database can support non-relational data streaming, it would be great.

Pricing could be improved as well.

I've been using it for more than 10 years.

As for the stability of this solution, it's a hundred percent reliable.

Scalability differs depending on the schema created in Oracle Database to access the database artifacts. For example, in a normal recessional database, which does not have much centralized or decentralized schema, scalability can be very high. However, in cases where there is a centralized schema, the scalability has to be defined by the database administrator.

Our whole engineering team currently uses this solution.

On a scale from 1 to 10, I would rate technical support at 9.5.

The initial setup is very straightforward, and Oracle Database is very easy to use.

The licensing is on a monthly basis. Improvement in pricing would be nice.

When you are into domains such as NIC, BFSI, retail, and account switching, then Oracle Database is definitely your best option. There are some aspects of Oracle Database that need improvement, but it can still be considered a good solution.

All in all, I would rate it at nine on a scale from one to ten.

We are primarily using it for software. We have a lot of software applications that are connected to this database.

Scalability, reliability, and performance are what we are getting with this solution. It is highly scalable and has very good performance. It also has in-built monitoring and optimized optimizer.

It is quite stable and secure. When it comes to integration, you can integrate it with other tools as well. However, we have been using Oracle Database within our own premises. So, it is kind of difficult for us to basically do a kind of integration with the outside software. We prefer to do things within our own premises.

There are SQL plan flips that are happening with version 12c. We would basically like to have the next version wherein we don't see such plan flips because they create performance issues. There are quite a lot of features that I would like to see, but this is the main one for now.

It has been over 20 years since we have been using Oracle Database.

It is absolutely stable.

It is highly scalable. It is scalable to the best of our needs. We have around 10,000 to 12,000 users.

We have three levels of technical support. The L1 level support is in-house. For L2 level support, we have an infrastructure team. For L3 level support, we have a contract with Oracle, and whenever we need it, we get their input.

We have been using Oracle since the time I have been working in this organization. I am not sure what was used previously. I am aware of 20 years, which is quite a long time.

It was very easy to install. It takes around two hours. This is a production database, so there have been a lot of validations. We do a lot of pre validations and post validations.  

For these kinds of installations, we have an infrastructure team. We have people here who do the installation. We have four trained Oracle Database administrators.

I would definitely recommend this solution. Oracle is already an established product. It doesn't depend on my recommendation. 

We will keep using this solution because we need to keep our data within our premises for our business model. As of now, we have no plans to go to the cloud and use any of the cloud services.

I would rate Oracle Database a nine out of ten.

I use this solution as a DBA on AIX and Linux.

This solution was great for a while until Oracle became adversarial with its customers and the professionals who support their products.

This solution has the best performance, bar none.

Oracle needs to stop suing users.

The documentation needs improvement because as it is now, providing support is a headache.

This is a stable solution.

This solution is extremely scalable.

The most valuable feature is the TDE advanced security as there are several options of different encryption algorithms. It's also easy to implement Tablespace Encryption.

We're able to go through and encrypt our database much faster using Tablespace Encryption versus using column encryption which requires you to identify each atomic piece of information to be encrypted. This ease-of-implementation gives us cost savings as we're able to get things done quickly.

I've heard rumors of an upcoming ability to get rid of ghost data. Here's an example: if I have a column in a database, say social security number, and a policy comes up and says encrypt social security number, and if there's an index on that column before you encrypt it, if you look at it, you can see the information in plain text. When you encrypt it, it does not encrypt the index. What it does is it marks the blocks available and creates a new index. Now you have ghost data -- plain text data.

We need an ability to shred that ghost data. Right now what I do is I advise people that when they encrypt something, manually move everything out of the old table space and then shred those data files. To be able to get rid of ghost data automatically would be great.

We've had no issues with deployment.

It's incredibly stable. There's a couple things you do need to be aware of, but it's not so much the stability issues, it's actually the data leakage issues. Because we're talking about encryption here, you have to be careful that data can leak out in third text, and I'll give you an example. If you take a data pump export of encrypted data and you do not specify encrypted in the command line, it will be saved in clear text. That's one issue.

Another issue is if you gather histogram information on encrypted data, that data will be stored in the statistics tables unencrypted so you have to use a product such as Database Vault to wall that off so you can protect it.

I don't think there's an issue with scalability. Most people are more concerned about performance because you have to encrypt and decrypt on the fly, but with hardware encryption modules that is really a null issue. There is very little performance impact. We've encrypted data out to 25 terabytes in one system and we had no performance issues.

I haven't had to contact technical support.

I was involved in the initial architecting setup of this. It's not difficult, but it's very precise. Simply, the easiest thing to think about is you have to store your encryption keys. If you lose your encryption key, you've lost your data. One of the first things you do once you've encrypted your data is back up your encryption keys. Actually, you want to back up your encryption keys before you start encrypting the data. We generally burn those off onto a DVD and store them in the safe and then we store them on another system offsite. That is the one thing that will really burn you if you're not careful.

It's not time-consuming at all. The encryption keys are minuscule. I have Word documents that are bigger than the encryption keys. It's just if you lose that encryption key, you're hosed.

We looked at SAN encryption, but we wanted a system that was native to Oracle so that we're not worried about whether everything is integrated properly.

If it's not implemented correctly, you can still have leakages of clear text data. Understand the product and it's limitations before you implement it. Understand where things can leak and plug those holes ahead of time.

You also want to be able to basically understand the product end to end because here's another little issue: if I encrypt the table space at AES 126 or AES 128 and a policy comes out, we're now going to encrypt everything AES 256, you cannot re-encrypt the table space. You would have to create another table space, encrypt it at AES 256 and then move that data over. Then you have the issue again where you can go back and shred the data.