Knowledge is power.
Being able to self-audit your Oracle portfolio on your own schedule is the best way to stay on top of any compliance issues. Whether they stem from poor documentation of virtual environments, impromptu hardware refreshes, a lapse in project tracking where new software was installed, simple human error, or other miscellaneous issues, the last thing that your company needs are costly slowdowns and fines.
Being proactive when dealing with issues of non-compliance allows you to make changes to architecture, workloads, or project distribution. All of these are preferable solutions to having Oracle perform an audit and “hoping for the best.”
The compliance piece of MAS provides you with a snapshot of everything that is currently running within your environment. However, even more, valuable than the ability to see what’s in your environment at the present time is the ability to get a historical record of everything that has ever run within it and compare it to present day. MAS gives you that ability. The logging ability within the MAS compliance piece enables you to easily see changes within your environment and make sure that you are in compliance, and if not, make the necessary changes to get there.
MAS Oracle Auditing allows for:
- Server by server analysis of hardware and software
- Differentiates environments running Enterprise Edition vs Standard Edition
- Core counts associated with the overall Oracle architecture
- Detailed analysis of Enterprise Edition options in use (Diagnostics, Tuning, etc.)
- Analysis of the underlying VCenter architecture for license exposure