Most Database Administrators are used to the occasional crisis—it comes with the job. The level of stress involved can vary greatly depending on the frequency of the issue, how well you remember the fix, and/or how quickly can you find a resolution using a Google search. Hopefully, this wasn’t too hard to find on Google.

Oracle Enterprise Manager (OEM) is a vital tool for any Oracle DBA to properly manage and monitor the operational environment. OEM helps identify issues and measure database performance in an accessible format providing an enterprise-wide view of their databases with the ability to zoom in for detailed information, as needed.

Like any piece of software, it is important to keep OEM up to date through patches and version releases. In this blog post, we will tackle one of the more challenging scenarios when it comes to upgrading OEM – Upgrading from 13.2 to 13.4 using the silent upgrade option.

Tuning SQL statements and databases can be intimidating to Database Developers and DBAs alike. If you take too long, say something is “good enough,” or declare that something cannot be fixed, it may hurt your reputation or even have you looking for a new employer! But if done well, the benefits of resolving a performance issue range from helping your coworker to improving the lives of the operational community.

Ensuring secure application and system deployments in a cloud environment for the Department of Defense (DOD) can be a difficult task. However, the Defense Information System Agency’s (DISA) provides guidance in the form of the Secure Cloud Computing Architecture (SCCA). The SCCA serves as a framework to ensure “Mission Owner” cloud deployments safely work with other DOD systems. This post will answer your questions about what SCCA is, what it is not, and the importance of developing within the SCCA model.