No.

Deployment wasn't difficult and we had no issues with it. Oracle had a bad rap in the past with customers who had bigger systems. They didn't provide them with enough assistance in order to assimilate new products and tools. But now, they've done a pretty good job of creating a very thorough cookbook, which has helped a lot with issues they we and my peers at other companies have had. Some of the issues was in the way we set up our enterprises which made it difficult to bring in and assimilate new products, but Oracle has lately done a good job of smoothing that out.

Some steps failed during the deployment by using one command utility to do all deployment steps by one command; so, we divided the deployment steps, then solved each issue separately until we successfully finished the development.

As in any technology deployment, software bugs and misconfiguration are possible. I have dealt with a few bugs and misconfigurations that have caused application downtime in the past.

Yes; mostly due to the database version being different. We were upgrading from 10g to Exadata which ran 11g; so there were some issues we had to overcome; but those were expected. Quite honestly, our deployment was smooth in Exadata itself due to our deep understanding of the technology. Without it, I am not sure if it would have been that smooth.

Nnope. It is usually we forget to mention the Schema names before the deployment and it fails when DBA's runs with Super user.

Yes, Cisco switch is not a standard within our company. Need to deploy with Oracle switch, after initial validation and setup, un-plug all network, replace the Cisco switch, and recable. This is time consuming and should not be required if Oracle would simply put in a different Cisco switch.

For new DBA's trying to understand the Exadata infrastructure, they struggle initially trying to understand all the components between ILOM, ASR, and OEM (what they manage, what they support, and what problem area that they detect) and which does what since they are overlapping. Consolidation management across the Exadata is another common issue on the Exadata. OEM is good at managing individual targets but not so great yet on identifying culprits across environments with heavily consolidated databases. When you look at the compute wholistically, it is difficult to identify what database is consuming most CPU and most I/O resources. Doing any kind of showback is difficult to do across instances.

We had few issues while deploying DB zones. This virtualization has to be carried out differently when compared to DB LDOM virtualization.

Just the normal software bugs, nothing major. In fact considering the complexity, there are very few bugs at hardware/software level. The ASR system with the jump gate was more problematic than the Exadata setup.

We had no deployment issues.

We've had no issues with deployment.

There were deployment issues, but the dev team fixed them.

We didn't have an issue with deployment.

No issues encountered.

Only during the first month or so of new generation Exadata machines, when the initial scripts have not been properly modified to reflect the new generation machine. Often, when proper sizing isn't done in advance, or even worse when sizing hasn't been done at all, the load can been too much for the servers. This is however an extreme case and has nothing to done with the Exadata frames.

We didn't have any deployment issues.

We've not had many issues with deployment, except for the minor issues involving moving databases.

There were no real deployment issues.

There were no deployment issues. However, the process of configuring with OEDA requires a lot of information beforehand.

The deployments have been issue-free.

No

I have deployed OEM 11g and 12c in High availability mode and was not too complicated to implement. I have not tried HA with 13c. However, installation for all the releases have been fine.

Issues encountered tend to business process problems or people problems. The issues tend not to be technical.

I did not encounter any issues with deployment.

There were deployment issues with the upgrade process. There was conflicting documentation and varying responses from Oracle support.

During migration, we approached transportable tablespace and Oracle database along with GoldenGate.

No issues encountered.

We've had no issues with deployment.

No issues encountered.