When working with a client reporting frequent slowdowns in copying of data between schemas, we asked the DBAs to investigate, as well as the UNIX team. Both teams reported that the individual database servers were performing fine, with plenty of resources available to them. However, after a number of conference calls, we overheard one of the team members say their HOST server was at or near 100% CPU usage and had been for some time. As the host was an Exadata 3 server, we had not anticipated we would be subject to shortages of system resources. Unfortunately, without visibility on the host server, we had to rely on reports from the teams maintaining the individual instances. Without us asking specifically for a screenshot of the host server’s performance statistics, we would not have been able to certify the issue was with the database server after all. As always, trust, but verify.