Tuesday Sep 27, 2016

Oracle Database 12c STIG Compliance Standard sample code is here!

One of the most requested features in the compliance management area has been a compliance standard for Oracle Database 12c. We can now announce the availability of not one but TWO Oracle Database 12c STIG compliance standards as sample code – one is for standard architecture and the other is for multitenant architecture.  

Sample code, of course, does come with some provisos. As listed on the OTN sample code page, it is provided for educational purposes or to assist your development or administration efforts. Your use rights and restrictions for each sample code item are described in the applicable license agreement. Except as may be expressly stated in the applicable license agreement or product documentation, sample code is provided “as is” and is not supported by Oracle.  

For all the details of the sample code, see the full announcement here.

Friday Jan 08, 2016

Enterprise Manager 13c: What’s New in Database Lifecycle Management

Enterprise Manager 13c: What’s New in Database Lifecycle Management

A month back, we announced the release of Enterprise Manager 13c. Enterprise Manager 13c includes several improvements over Enterprise Manager 12c, which was itself had witnessed pretty successful adoption over the last four years. Enterprise Manager 12c rested on the key themes of enterprise grade management, stack management and cloud lifecycle management. The 13c version simply bolsters those pillars.

In the area of database lifecycle management, we have delivered some key features that span both the depth and the width of the data center. In terms of depth, it leverages the unification of hardware and software management to manage Exadata better. In terms of width, it offers simpler and more scalable cloud management. Over the next few paragraphs, I will touch upon few features that highlight the above.

Exadata Patching:

The patching of Exadata has been laborious process for our key customers. It involves multiple components across multiple nodes and often multiple administrators in the process. In Enterprise Manager 13c, some of the important hardware management features have been assimilated into the Cloud Control product. In course of developing the hardware aka the infrastructure management features, we have modeled the infrastructure target types: servers, storage, network, VMs in Enterprise Manager. This also enables us to have a more sophisticated management of Engineered Systems. For example, Enterprise Manager can now patch an Exadata stack- storage servers , Infiniband drivers, compute nodes, grid infrastructure and as before, the databases on top. The patching application offers the facility to run the pre-flight checks and monitor the logs from a single place (imagine having to manually monitor the patch execution logs for grid infrastructure, operating system, storage for all the compute and storage cells in a rack).

Enhancements in Database Compliance Management:  

There have been some significant enhancements in database compliance management. These include:

a) Integration of Oracheck: A long-standing requirement that should thrill Exadata customers is the integration of Oracheck (including Exacheck) into the Compliance framework of Enterprise Manager. Exacheck had formerly existed as a standalone utility, but customers have asked for at-scale execution over all the Exa’s in a data center, with the ability to flag, suppress or escalate any violation. They can also generate reports on overall health and share with other administrators and IT Managers.

b) Integration with corrective action: Another much sought-after feature has been to integrate the compliance violations with corrective action. For example, a DBA may want to lock an account with default username and password. Enterprise Manager 13c makes this a reality.

Configuration Drift and Consistency Management:

When it comes to managing a cloud horizontally at scale, the configuration comparison feature of Enterprise Manager has always been a DBA’s favorite. The new configuration drift management feature evolves the feature further by enabling administrators to proactively spot the “needle in the haystack” among the hundreds and thousands of members that can be a part of a cloud or even span multiple clouds (example, on-prem and Oracle Cloud). The DBA can set up a golden standard with a selected list of configuration parameters and make sure that all the members of a cloud or a pool of databases subscribe to that standard. In case of any deviation, the DBA will be automatically notified. The consistency management can be applied across the different phases of lifecycle (for example, the test database should be the same as production) or across the different members of a system (for example, all the nodes of an Exadata should be exactly alike).

Additional Info

Tuesday Apr 28, 2015

EM Compliance ‘Required Data Available’ flag – Understanding and Troubleshooting

Overview

Starting in release 12.1.0.3 of Enterprise Manager a new column was added to the top level Compliance Standard Results page named ‘Required Data Available’. This column is meant to convey whether the data required for proper compliance evaluation of all of the rules within the Compliance Standard for each associated target is available in the repository. If the value for a given target is ‘No’ then the compliance results for that target should not be considered valid. A value of ‘Yes’ indicates the required configuration data is being collected and results valid; at least from a data availability perspective.

One challenge facing customers is the lack of understanding of the column and how to correct the cause of the ‘No’ status. The goal of this guide is to explain how this column’s value is derived and provide some tools to correct the situation.

Read More


Monday Apr 13, 2015

New Enterprise Manager STIG Compliance Standards for Oracle Database 11gR2 Now Available

Last Friday, Oracle released new Enterprise Manager compliance standards based on DISA’s Security Technical Information Guide ( STIG ) for Oracle Database 11.2g Version 1 Release 2. These standards are specifically for use with Oracle Database 11g Release 2, both single instance and RAC.

This is actually the second compliance content update since February. The previous one included an update to the Oracle Database 11g STIG standard bringing support from Release 8 to 11.

Read More

Friday Oct 24, 2014

Get Compliant with Oracle Java VM Database PSU OCT 2014 using EM12c

Check for compliance and automate patching of Oracle Database fleet using EM12c

Oracle along with its regular Quarterly Database PSU/SPU/CPU update this October 2014 released Oracle JAVA VM PSU patch, the patch is recommended to be applied to all databases in your fleet (esp. the ones that uses JAVA).  (For more information, support Note- 1929745.1 explains it in detail).
The mandate primarily is to apply the patches against the databases that use JAVAVM option. Ideally, you would need to apply it against all databases, so in case a new database is created in the ORACLE_HOME it is covered.

Oracle Enterprise Manager 12c provides support features of Compliance Management and automated Patching of databases. Using both these features you could identify the databases in your fleet that needs the patch and automate applying them.  

To get started, download the starter kit here. It contains utilities to jump start on your compliance, the kit contains a readily importable Compliance Standard and a step-by-step guide.

[Read More]
About

Latest information on Oracle Enterprise Manager and Oracle Management Cloud.

Related Blogs




Search


Archives
« March 2017
SunMonTueWedThuFriSat
   
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
 
       
Today