The deployment depends on the Exadata options. There are primarily three options which include, Exadata, Exadata Cloud@Customer, and Exadata Cloud Service. Out of these, Cloud Service requires the minimum effort. The deployment takes around two to three weeks to complete. For the deployment purpose, we need information on the user base where the access is going to happen. We would also require around four to five engineers and admins for the solution’s deployment and maintenance. This estimation is based on the workflow.

I wasn't involved in setting up Oracle Exadata because there's a dedicated team responsible for the setup.

The deployment process took a bit of time because my company switched gradually from other technologies to Oracle Exadata, and at the moment, some of the databases are still being moved to the solution. It's a big installation because I work for a big company.

The initial setup depends upon the use cases, but the professional services from Oracle are very costly. If you have knowledgeable people within your organization who understand how things need to be built for an enterprise, then the initial setup becomes easier. If you don't have people and depend upon Oracle, they will sell you things you will never use in a thousand years. They will put everything into the system, saying they are required, but will never be used in a real vault.

The initial setup of Oracle Exadata is very complex. It has steps that need someone with qualifications to be completed.

The initial setup is not straightforward at all. It's very complex and extremely difficult.

It's not easy to explain the entire process overall as there's a lot of criteria. We start working on the requirements, and the first implementation was not exactly what we spec'd it for. We had to start over, and we were complimenting these requirements. However, the functionality and scope ended up not being agreed upon by two partners. The users also did not take into account that they needed to be a part of the process. There were just so many moving parts that never lined up properly.

We've realized that a good solution must also be easy to use as the users will end up being the ones accessing the information, and, if they are confused, they'll never use the technology. On top of that, the requirements and scope need to be clear upfront.

I'm not sure how much staff has been needed for deployment and maintenance.

While I never did it myself, the setup is straightforward, once the initial configuration is defined.

It was a vendor team who did the bare-bones setup and then we did the actual deployment and migrations in-house. Our team is very seasoned. The vendor team was quite good and we had no issues with installation and initial configuration.

Setup is straightforward. You just fill out a deployment form that Oracle sends you. By filling out this deployment form, you actually give all the necessary inputs for the deployment (such as IP addresses, host names, NTP server IP addresses, DNS server names, etc.)

Most of the time, Oracle field engineers, who are well-trained for deploying Exadata, do the setup on-site. After the initial setup, any experienced admin who knows Oracle RAC and Oracle RDBMS, can go further to provision databases (create databases, do performance related configurations and so on) on Exadata or they can even further migrate databases to Exacta.

After the first setup, Oracle still answers your questions and supports you to make sure that deployment meets the customer requirements.

The initial setup is straightforward. The deployment was done by a consultant and took one hour.

There is a definite learning curve initially. We had to learn about migration options, shared mount point options, how to integrate with Cloud Control, patching, health check, how to optimize, and how to harden the Exadata environment. Since we went live, many more folks use Exadata so there's more how to's and best practice documents available so the learning curve isn't nearly as steep. We learned a lot in the process and now have a tremendous amount of expertise in setting up, configuring, optimizing and maintaining the Exadata.

Oracle Exadata's initial setup is easy. Installing the solution on our system in the data center takes less than one day.

I would rate the initial setup of Oracle Exadata a four out of five.

The initial setup for Oracle Exadata was quite complex, so it's a six out of ten for me.

Deploying Oracle Exadata took several hours. I organized it in advance, so I was well prepared for it. I had to migrate from the previous hardware to the new hardware or appliance, and the organization in both databases was different, so the task could have been more straightforward. You need to know what you're doing to deploy Oracle Exadata successfully.

The initial setup was done by my infrastructure team and I don't think that they found any difficulty in it. They are knowledgeable in Oracle, so they didn't have any problems.

The setup requires proper security groups if you want to use it. I rate the setup an eight out of ten. Most of the users we've worked with use Oracle Exadata, but we've worked with major banks which prefer to own the solution for security purposes.

The initial installation is not difficult, it took two to three days to complete.

The installation is easy because it comes out-of-the-box and you just start using it.

The product's setup takes around two to three days to complete. 

The initial setup of Oracle Exadata is difficult, particularly if you want to repair the discs. 

Initial setup is complicated and you need to engage Oracle to do that. Obviously, nobody else can do that. It's complicated, but it's a part of the process.

I would describe the initial setup as being of medium complexity. We're a financial insurance company, so we always want to put in a lot of rigor, in terms of security and compliance. At times, it's not our own fault, but it's our devices, but at the same time, the price of being exploited is bigger than what it takes to ensure security and compliance. The issue has been really more of the rigor that we put in ourselves, and finding a way to allow those new products and solutions to work as they were expected through our hardening that we've done on our environment.

The solution is already reconfigured but not the system, only the semantics. Our network cables and the valves, the main areas such as the connectivity part, that's the network. Once they are completed and databases are accessible the configuration part has to be done. Overall the initial setup is straightforward and according to the manager's words, it's convenient to be able to reconfigure the system on the solution.

The ease of setup is an eight out of ten.

The deployment is not done overnight. In order to ensure our system management has little impact on the business area, the deployment is done in stages. Bringing on a new version update would only take a few days to test and test the environment. We have to verify and extract some information in order to improve the environment. Once all the testing is complete, we can move into the live environment. Full deployment will take one and a half to two months.

The initial setup is clear but you have to be careful while filling out the OEDA (Oracle Exadata Deployment Assistant) tool as it will generate an XML file that contains all of the required configurations for everything, like networks, storage, clusters, etc.. This file will be used during the initial setup.

Initial setup was very much straightforward. Not as much manpower is required as we used to need. Before, if you wanted to manage a server, you had to have a server administrator, the storage administrator, and a DBA administrator. Now all three functions are combined into one person. A data administrator can perform the role of storage administrator, your host administrator, platform administrator, as well as database administrator. It's like several persons reduced to one.

It is called an engineered system, but there are options that Oracle offers to its customers. Customers need to complete a configuration generator tool called Oracle Exadata Deployment Assistant (OEDA). Based on the selection made on the tool, configuration file is generated and this will be a 'binding contract' between customers and field engineers who will do the initial setup. The problem is that it is the customer's responsibility to make the right options and some of them are not easy to understand. I suggest the customer not to hesitate to get assistance from Oracle Pre-sales and to go through each of possible options in detail and to understand all consequences.

Oracle sends professional installers for installation and deployment. So it was fairly simple. However, as I mentioned earlier, we do have a deep technical expertise base so it worked in our favor. Without that expertise, I can't be sure if would not have been complex.

The setup is straightforward but there can be issues during implementation. 

The initial installation took around a week.

Nope. it was quite easy.

See the switch issue mentioned above.

The initial setup is straightforward with the Exadata X5-2. We have to re-image the factory Exadata and leverage OneCommand for configuring the compute and storage nodes.

The initial setup for Oracle Exadata is straightforward and user-friendly because it has a great feature called OneCommand, which makes installation automated.

We had very complex situation, actually, with our Exadata migrations. Due to the shortage of our manpower, one of our engineers and one and also Oracle did migrations. During the migration phase, they have a lot of discussion and talks and deviation. But, they had someone help us migrate excellently. Because we have a data that's set up and also because it is not one-to-one relationships. End-to-end relationships, we had it over there. Database level, not table level. Database level, we have physical data within some other machine. The secondary data will be here. The data guard will be inside the Exadata, and the Exadata itself have the data guards and it's really nurtured relationships further, but some start up guys also have come back to the preparatory work center. 

All in all, in Oracle, you need a skill set for implementation. I don't say it is difficult, but you need a skill set for it.

There is a certain degree of complexity with respect to the initial design of the Exadata storage cell disks and grid disks to meet the customer’s application needs. This especially true when migrating from an existing setup. Care has to be taken with regard to the initial domain configurations since this will determine the LDOM and zone-level virtualization. The Exadata disks have to be exposed to both the DB LDOMS and DB Zones.

Documents are very clear, and there were many software and hardware engineers available to provide assistance and guidance along the way. The most difficult piece was the ASR system set up with the jump gate, password vault and set up in OEM. The other difficulty was the network, and some of that was due to my lack of experience in that area.

We are an integrator of the solution. Our clients are sizeable companies, and there are several providers involved in different projects with Exadata. We're not the only administrators. 

I personally haven't handled an installation. We're mostly focused on projects related to BI and analytics. Someone else handles the setup and we just use the product or have our clients use it. I don't have a sense of whether the implementation is difficult or complex or how long deployments take.

Initial setup was very simple, actually. Getting all of the right network information was really the critical path for it, but once that was done, the actual install and configuration was very simple.

The initial setup is not complex and it can be installed in just a few hours.

The initial setup isn't too complex. However, in the present, the initial setup of Exadata isn't made by Oracle partners or the client. There is an advanced ACS department, Oracle Advanced Customer Support, that handles the implementation. In this team, there are very good specialists on Exadata. These specialists from the ACS department are the guys who will install Exadata for the first time for the client. 

It's not something very complex and something which cannot be done by others, however. Our team, for example, was installing Exadata. It's possible to be done by other teams with, of course, the appropriate competencies. The implementation sits somewhere between simple and complex. The machine is complex. We cannot set up a machine like this with more components and different components like a laptop, for example. 

The initial setup is not so complex as it is done by Oracle Experts and is validated by the senior engineers.

We brought Oracle in to set it up, so it still is with Oracle. We didn't go through the entire setup process because Oracle was part of it. Oracle itself did it, so it was pretty easy for us. Again, one good thing is, we don't have to really worry about the patching, OS levels, and other stuff. It is pretty easy for us.

The initial implementation is quite simple and straightforward. It's not difficult or too complex for someone to handle. A company should have no trouble with the setup process. 

For us, the deployment process took around three days. That was just to have all of the planning and other stuff in line and ready to go. Everything all together - including the migration, et cetera, should be three to five days, or something in that ballpark.

We have about 35 people in IT that can handle any maintenance tasks required.

The initial infrastructure setup is straightforward because it is delivered in a box. It's all pre-configured for the most part. Again, I think it boils down to how each company does it after it's deployed at their site. That's where it gets a little bit challenging and that's where you have to put a little bit of effort in to make sure you lay it down right.

The intital implmentaion of Oracle Exadata is difficult.The data is complicated. We have multiple queries and multiple processes pulling this data. There is complete logic inside.

I didn't handle any aspect of the initial setup. That said, it's my understanding that the initial setup is a bit complex and difficult.

The initial setup always comes with some complexity because it needs a lot from the customer to prepare the site, network, firewalls, and the rest. The deployment is always complex.

Preparing for deployment can take a couple of months, again depending on the requirements. There are standard things that have to take place, such as allocating space in the data center and making sure that the power, cabling, and switches are there. Once everything is in place, the software installation will take two or three days.

The setup was straightforward.

The initial setup was straightforward.

The bare metal setup is done by Oracle professionals and managed by them. Though, customers can manage this on their own, depending on the skill set of their team.

It was a bit complex to fit in with our business requirements initially, but post-implementation it was great. It will work as the most stable and scalable database ever run on Linux with various complex workloads.

The installation was straightforward with Oracle support.

I have a huge background in UNIX hardware, networking and database. For me, it was extremely straightforward. For someone who has just one job function, for example, just a DBA, it would be very challenging. I work with some people for whom it is extremely challenging because they don't have the other aspects; they only understand database and that's a problem if you want to work in Exadata.

The initial setup of Oracle Exadata is done by well-trained engineers. I have to prepare the environment with all the systems, active environments, and IoT networks. After the preparation, the engineers can do the scripting. Once installed from the scripts we can work with it.

The whole implementation process can take between two and three hours.

The setup was not too complicated. We followed the standards install and we didn't see any big issues. We did try a few different versions and some of the migration can be a little bit labouring but we didn't face any data challenges.

Setup was straightforward.

The initial setup was complex, but it was well planned by Oracle ACS.

There were some complexities because a lot of departments were involved, and there were some communication gaps, but generally speaking, it went smoothly.

It depends on who does the initial setup. The process is definitely straightforward and not that complex at all. For example, the Accenture Enkitec Group is strongly specialized in these types of setups.

We actually contracted the initial setup out, as part of Oracle Platinum Support. We also have another third-party company that did more of the operations on it. When my team finally got to it, everything was set up. It's really a matter of deploying our application on there and then tuning it to be more Exadata specific; not a whole lot. Anything will run on it, but we take advantage of the high columnar compression and the flash cache storage.

At this moment in time, it is pretty much a straightforward, almost-manual installation. We're looking for some automation around it.

The setup was simple, however, the database migration was a bit challenging, but there was no show stopper anywhere.

Nowadays, it's easier. In the first years of implementation of Exadata it was a bit more difficult, but now it's easier. If you have a team that knows Exadata well, and knows the limits of Exadata, then the setup and implementation is easy. If, on the other hand, you don't have an experienced team, then it's really difficult.

For Oracle Exadata, there are two main profiles that you have to take care of. One is the installation itself, like assembling the machines, which need some kind of expertise. The other is the installation of the software and creating the database, which need other kinds of equipment. From our perspective, our main goal within all of this is not about these two profiles. It's about the database engineering. Because we are coming from using an old machine, which is running an old version of Oracle, you will need to properly create not only the environment to host the database, you will also need to migrate from an old version of Oracle, like 11g, to 19c. This is another challenge that we have during implementation of these projects.

I can say that from acquisition it took at least, but not more than, five months to implement.

At acquisition we need to design the tenders and the rules of the company. The tender goes out, then it is published, then we evaluate all the tenders, then someone must win the tender. All this takes a lot of times. Then you go to the implementation phase. We did a workshop to design the solution. It took at least three weeks. Then it starts implementing the infrastructure. Migrating the database is another point because one database can take at least two days. That's the situation. But start to finish takes five months.

The initial setup was very easy and took two to four hours working on it because this is an engineer system. So the Oracle engineer and the ACS team worked on it and on the on-premises database to migrate to Oracle Exadata.

The setup was straightforward as Oracle was involved in the setup from the very outset. We did not face any issues during the setup.

Initial setup is complex. You need Oracle technical support to do your initial setup.

It is quite difficult, but again since we're a services company, we're pretty well versed in it. We actually help customers do that end-to-end. Not only do we help bring Exadata in, we help do the installation and configuration and migration to the Exadata, as well as sustainability for future.

It takes a lot of planning depending on your downtime for conversion, depending where [platform] you're coming from. All those things play a big part in what tools you use and how you use them.

Initial set-up was a bit complex, but everything was resolved pretty quickly.

We didn't set it up, Oracle set up Exadata. It's not permitted to set up Exadata by yourself. They bring it to you. It's ready for use.

It was straightforward for us because we used an integrator partner to put it all in for us, and then our administrators stepped in and took over.

The setup was straightforward, but porting applications to Exadata was complex.

Initial setup was straightforward for us because we used an integrator partner to put it all in for us, and then our administrators step in and take over.

The initial setup was straightforward. But this particular situation is different because we are not talking about putting it on and going into production. We have to move the initial systems to these environments. 

We need to convert some systems to be compatible with those environments. The main challenge is the IT infrastructure. It is not like we buy it, open it, create and edit it. We need to move, and that is the challenge. Right now, we are in the middle of finalizing this movement with migration from legacy to the new environment.

From a technical point of view, it didn't take long because it's straightforward. We started and went step by step until the end or until the machine was available for migration. It was very simple.

It was a normal Oracle database setup.

The initial setup depends on the technical team. The ACS team at Oracle can help, but it depends on which engineer you get on board. If the engineer is new on the team, doesn’t completely understand it, and is simply following instructions according to a script, there is every possibility that it could go wrong, if we don’t have a core team at our end verifying each step.

It is very important that you be prepared, and that you know every single change that goes into it end-to-end, including the monitoring and enabling the ASR service if you are going to use the platinum service.

Exadata is pretty much set up when it ships. Afterwards, you just have to copy data over and it's ready to go. So the setup is fairly easy and straightforward.

The installation took around one month.

Yes, straightforward.

The documentation is clear. The time to implement is really short. You put the CD in there, and you just kind of follow the prompts and you're done pretty much. I like that aspect of it.

Straightforward

If you know what you’re doing, initial setup is no big deal.

The initial setup was pretty smooth and straightforward.

The initial setup and deployment of an Exadata rack is straightforward it has been well engineered to be a very quick initial setup.

I was allowed to help with some of the initial setup. Most of it was handled by the DBA core team; what I did was give some ideas on how we ought to do some things.

As a DBA, we usually use it for the database upgrade which is straightforward. For the OS upgrade, it's mainly up to the Oracle support and the platform support to carry out the upgrade. We don't do it. We're even afraid to install any third-party/ other vendor's application on it, as it may be harmful.

The deployment of the solution could be made easier.

It's complex. We integrated an existing solution to Exadata.

We needed Oracle support for all of the setup steps.

Oracle comes in and does the initial setup.

The initial setup takes time and is complex. Implementation is generally carried out by the vendor. 

The installation is a medium level of difficulty. You need a skilled person to do the installation.

Exadata comes pre configured, just need to create your databases and load your data.

It was a complex setup because we were implementing the online application as well as data warehousing on the same machine. Lots of planning took place before moving to Exadata, and we did regression testing for each application on an Oracle provided Exadata machine. After verification from our application team and management, we verified our test results.

It was straightforward.

The vendor does the setup.

The initial setup required a lot of planning from all stack parties. All
features and configuration need to be discussed upfront. However, with
detail planning, the execution and deployment, via “OneCommand” process, was fairly straightforward.

For setup, we had a consultant come in. They trained us initially and helped us with the set up. Then, after that, we started working on everything.

It was straightforward using the OneCommand tool that is designed for Exadata deployment.

The initial setup is quite complex because it's an appliance. It's a big box with all the processing power and storage that you need to order and get installed. It's pretty complex.

You need to do the installation which is done by Oracle. It's not just software, it's an appliance. When customers want to buy it, I need to order it. They want it a lot faster and it's actually quite expensive. If Oracle or Oracle partners have this appliance in stock it can be quick but if it's ordered through a manufacturer it can be lengthy. 

Setting up Exadata is complex. You need an Oracle vendor or someone who is Oracle-certified to set it up.