Sunday, December 20, 2015

Oracle Enterprise Manager 13c: New and Exciting Features

Oracle Enterprise Manager 13c: New and Exciting Features

Oracle Enterprise Manager 13c: What’s New
We just announced the release of Oracle Enterprise Manager 13c. Well, if the number 13 makes you jittery, rest assured that this new release is an improvement on Oracle Enterprise Manager 12c which has witnessed unprecedented adoption among customers worldwide. Oracle Enterprise Manager 12c rests on the key themes of enterprise grade management, stack management and cloud lifecycle management. The 13c version simply bolsters those pillars.

Our first goal in this release has been to make monitoring cloud scale and resilient. Oracle Enterprise Manager today is the nerve center of IT operations among thousands of enterprises, our very own public cloud operations being one among them. Millions of assets in Oracle’s SaaS and PaaS public cloud operations are managed by Enterprise Manager round the clock, which requires that Oracle Cloud’s own Oracle Enterprise Manager instance stays up and running during unplanned and planned downtime windows. Oracle Enterprise Manager 13c therefore introduces “always on” monitoring, where a small companion monitoring application continues to receive critical alerts from the agents out-of-band while the management server is down. One can start the application, take Oracle Enterprise Manager down for patching and continue to be alerted on critical events. Speaking of planned downtime windows, another exciting feature being introduced is “notification blackouts”, which lets administrators monitor their targets during their maintenance windows, while notifications from critical alerts are still turned off.
When it comes to stack management, the BIG news for our customers is the unification of hardware and software management. Ever since Oracle acquired Sun, we have promised a converged systems management, but current customers have been managing hardware through a separate tool called Ops Center. In Oracle Enterprise Manager 13c, some of the important hardware management features have been assimilated into the Cloud Control product. This not only benefits platform administrators in that they can now drill down into the infrastructure problems easily, this also benefits system and storage administrators because they can enjoy the scalability, availability and security framework features of Cloud Control. As an example, critical incidents in the hardware layer can now be published to a 3rd party ticketing system using the connector framework, something that Oracle hardware customers have asked for a long time. As part 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, including the ability to patch a complete Exadata and Exalytics stack. 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). Another enhancement that should thrill Engineered Systems customers is the integration of Exacheck into the Compliance framework of Enterprise Manager; this would let them generate automated notifications and reports for any violation in their Exadata configurations.

One request we always received from our database customers was to enable fine grain access control. Most organizations have multiple personas (Central DBAs, application DBAs, Developers, etc) and would like segregation of duties among these personas. For example, a Developer may be allowed to tune the application but not patch the underlying database. Oracle Enterprise Manager 13c enables fine grained privileges for controlling access to specific features.
In terms of cloud management, the release focuses on three key aspects: the ability to perform database consolidation planning for various scenarios, the ability to manage configuration drifts at scale and improved data lifecycle management across production and test instances.
The new Consolidation Workbench provides an end-to-end workflow that provides three distinct steps:
· What-if analysis on various consolidation scenarios: commodity to engineered systems, non-multitenant to multitenant databases and on-prem to Oracle Cloud.
· The actual enactment of the consolidation by integrating with the provisioning features
· Post-consolidation testing using the SQL Performance Analyzer
The new configuration drift management feature enables administrators to proactively spot the “needle in the haystack” among the hundreds and thousands of members that can constitute a cloud or even across multiple clouds. And last but not the least, Snap Clone customers would be benefited by the ability to keep the test databases in sync with their production.
It would be an incomplete disclosure to limit Oracle Enterprise Manager 13c’s capabilities to the above features. There are many more new features (see the full list) as well as hundreds of enhancements introduced into the existing features. I am certain that IT administrators and consultants would be looking for a top-12 feature list. For them, here’s the summary:
1. Gold image based agent lifecycle management (view screenwatch)
2. “Always on” monitoring (view screenwatch)
3. Notification blackouts for managing target downtime windows (view screenwatch)
4. Cloud-scale configuration drift management
5. Hardware and infrastructure management  (view screenwatch)
6. Engineered Systems patching
7. Exadata and Exalogic-Nimbula VM provisioning
8. Exacheck integration into the compliance framework
9. Flexible access control for database management (view screenwatch)
10. Database Consolidation workbench (view screenwatch)
11. Continuous data refresh between production and test databases
12. Unification of Middleware Consoles into Enterprise Manager 13(view screenwatch)
To summarize, Enterprise Manager 13c reinforces its ability to manage along two dimensions: vertically across the stack, and horizontally, within and across clouds. So, number 13 indeed sounds lucky for Enterprise Manager customers, right?

Tuesday, December 1, 2015

How to check for Database Option and Management Pack usage

How do you check for Database Option and Management Pack usage? There are two scripts available from Oracle for this purpose. They are :
1. option_usage.sql
This script outputs database option usage and management pack usage by a database target
2.  used_options_details.sql
This script will output the features used by each database option and management pack.
You can get these two scripts from Document ID 1317265.1 in My Oracle Support. The direct link for the document is here.
These scripts can be executed manually on database targets, or optionally they can be run on all targets via Enterprise Manager – which will be more convenient.
Note that the output of these scripts is for information purposes only. You need to talk to the Oracle Sales representative in your location to find out which options and packs your company is licensed for.
This is an example of running the script in Oracle SQL Developer on a particular database. In this database, only the Tuning pack is in use. Although this may be technically valid (the Diagnostics pack may never have been used), you still require the pre-requisite license of the Diagnostics pack to use the Tuning pack.
In the above case, running the second script tells you that the feature being used as part of the Tuning Pack is the “Automatic SQL Tuning Advisor”, and tells you the number of detected uses and the last usage date.     
This blog post was originally published at this link.

Thursday, October 15, 2015

Managing Oracle Database 12c with Enterprise Manager – Part XXI

We are discussing the management of Oracle Database 12c in Oracle Enterprise Manager 12c. In our previous blog post on this topic, we looked at the tablespace level Heat Map in Database 12c, showing which objects were accessed with a full table scan. We now move to the Policy tab.
Information about the Compression and Storage policies is displayed. There are 2 storage policies present. Only one object has a policy enabled.  Drill down to the enabled policy.
The object displayed is the table HR.EMPLOYEES. This object has the policy enabled. Click ok to go back to the policy tab. On the policy tab, select the policy and click on “Execute Policy”.
In the window that appears, confirm by clicking on Execute. The policy will be executed. You can also see the PL/SQL that you would have to write to perform this simple action, if it were not for Enterprise Manager.
The evaluation job is submitted. You can go back to the evaluations tab, select the policy, and click on execution history.
This history shows that the job has been created.
On the main Policy tab, there is another button called “Policy Details”. This shows further details of the policy.
Finally, there is the button “Default Execution Settings” on the main Policy tab. This displays information about when and how the policy will be executed.
This has been a quick introduction to what is available in Enterprise Manager 12c for Information Lifecycle Management (ILM) in Database 12c. For more information on Managing the ILM Heat Map and ADO with Enterprise Manager, please see the documentation here.
This blog post was originally published at this link.

Managing Oracle Database 12c with Enterprise Manager – Part XX

We are discussing the management of Oracle Database 12c in Oracle Enterprise Manager 12c. In our previous blog post on this topic, we used Enterprise Manager and added Automatic Data Optimization (ADO) policies that enforceInformation Lifecycle Management (ILM) in Database 12c.
To view all the ADO policies and the Heat Map, select Administration.. Storage.. Information Lifecycle Managementfrom the 12c Database (non-CDB) Home Page in Enterprise Manager:
This displays the Information Lifecycle Management page.  The information you want is in two tabs, the Heat Map tab and the Policy tab. The Heat Map is seen below.

On this page, you can see the Database level heat map or go down to the Tablespace level, and then to the Object level.  Here we have displayed the heat map for the EXAMPLE tablespace by clicking on the "Show Additional" button and selecting this tablespace.
We have then selected a date range, and view by “Last Full Table Scan Date”. This displays the tables that have experienced a full table scan in the date range we have selected. The green color specifies that the date range did not see a very heavy access of these tables; otherwise a different color would have been used for the object that was more heavily accessed.
In the table in the bottom half of the screen, we have searched for the HR schema. A list of objects belonging to the schema is displayed, along with the associated IML policies if any, and other information about the objects.
Let us move to the Policy tab.
This blog post was originally published at this link.

Managing Oracle Database 12c with Enterprise Manager – Part XIX

We are discussing the management of Oracle Database 12c in Oracle Enterprise Manager 12c. In our previous blog post on this topic, we started to look at how Enterprise Manager helps with Information Lifecycle Management (ILM)in Database 12c. We changed the database initialization parameter heat_map to ON.
As the next step, we can add an Automatic Data Optimization (ADO) Policy by editing an Existing Tablespace as shown in the following screenshot.
In this case, we have selected the USERS tablespace, and are specifying a segment level Storage Tiering policywhereby we move newly created (from here on) objects in the tablespace  to a second tier storage tablespace, if the object has not been modified upto a period of 3 months.
The second tier is built on a more economical storage system, as opposed to the first tier high performance storage system. After creating the ADO policy in this manner, if we create a new table in the same tablespace, it will inherit the tablespace ADO policy .
Or, we can add an ADO Policy by editing an Existing Database Object:
This allows you to add a new ADO Policy to an existing database object.

This blog post was originally published at this

Managing Oracle Database 12c with Enterprise Manager – Part XVIII

We are discussing the management of Oracle Database 12c in Oracle Enterprise Manager 12c. In our previous blog post on this topic, we looked at Information Lifecycle Management (ILM) in Database 12c, and we will now see how Enterprise Manager helps with that.
Enterprise Manager Cloud Control 12c allows the management of ILM in Database 12c. This was enabled via the DB Plug-in release released 4 months after Enterprise Manager PS2  i.e. Release 3 (released in July 2013).  The DB plug-in release was in October 2013.
The following was included in the Oct. 2013 release:
  • ILM Heat Map for DB & Tablespace
  • ILM Administration feature to setup ILM policy on Tablespace & Objects
Note that Automatic Data Optimization (ADO) is not supported currently on CDBs and PDBs. It only works on a non-CDB 12c database.
The first step is to change the database initialization parameter heat_map to ON as seen in the following screenshot:

This blog post was originally published at this link.

Managing Oracle Database 12c with Enterprise Manager – Part XVII - Information Lifecycle Management (ILM)

We are discussing the management of Oracle Database 12c in Oracle Enterprise Manager 12c. In our previous blog post on this topic, we were exploring the different tabs in the Performance Hub of Enterprise Manager Database Express 12c. Let us now look at Information Lifecycle Management (ILM) in Database 12c, and how Enterprise Manager helps with that.
Oracle Database 12c has an excellent feature known as Information Lifecycle Management (ILM) which is now fully automated in moving data between different storage, depending on data age and access. The Heat Map and Automatic Data Optimization (ADO) features of Database 12c can be used to implement your ILM strategy, along with the Partitioning, Advanced Compression, and Hybrid Columnar Compression (HCC) options/features of the Oracle Database.
The "Heat Map" feature automatically tracks access to segments (tables and partitions) and rows and blocks.  The ADO feature allows you to define policies at the tablespace, table, partition, or row level. The policies contain conditions and associated actions.
The conditions are based on the data collected by Heat Map, and the actions can either be storage tiering (move the segment to another tablespace) or compression tiering (move the segment or block to a different level of compression).
The actual syntax of setting these ADO policies is not complex, but in totality, setting up many different ADO policies for storage tiering or compression tiering manually at the command line, and keeping track of those policies manually by a DBA, would work out as a complex task.
To alleviate that kind of task, Enterprise Manager would be very useful. Database 12c DBAS would want to use Enterprise Manager for this purpose.
More on the use of Enterprise Manager for ILM in the next blog post.
This blog post was originally published at this link.


Opinions expressed in this blog are entirely the opinions of the writers of this blog, and do not reflect the position of Oracle corporation. No responsiblity will be taken for any resulting effects if any of the instructions or notes in the blog are followed. It is at the reader's own risk and liability.

Blog Archive