Grid DBA

Just a short post linking to my presentations at Oracle OpenWorld 2014 and St. Louis Oracle User Group (SLOUG) Big Bash. Oracle Enteprise Manager Cloud Control 12c - Setting Up Metrics and Monitoring (Top 10 Features for DBAs v1.1) from Leighton Nelson A Second Look at Oracle RAC 12c from Leighton Nelson

The information technology industry has been a tremendous growth in Cloud delivery models for IT services in the past couple of years. More recently, the PaaS service model including Database-as-as-Service (DBaaS) has been gaining traction rapidly. Amazon's RDS public DBaaaS service supports Oracle, MySQL and SQL Server and enable rapid development lifecycles by giving end-users the ability to provision databases on demand in a very short period. Security and control are two drawbacks seen in public cloud environments. How can this be overcome while delivering the same level of rapid provisioning, elasticity and multi-tenancy for databases? Oracle Enterprise Manager Cloud Control 12c provides a complete lifecycle management framework for databases - from provisioning to patching. The Database Cloud plug-in enables DBaaS for users on premise without the drawbacks of public clouds. If developers want copies of schemas then the Schema-as-a-Service sub-model can enable them to sel...

In previous versions of Oracle Enterprise Manager you would call the EMD_MAINTENANCE package to execute certain maintenance tasks such as partition maintenance and statistics gathering. EMD_MAINTENANCE.ANALYZE_EMD_SCHEMA EMD_MAINTENANCE.PARTITION_MAINTENANCE In OEM12c these procedures are replaced by: EMD_MAINTENANCE.GATHER_SYSMAN_STATS EMD_MAINTENANCE.DAILY_MAINTENANCE The daily_maintenance procedure actually calls gc_interval_partitions and gathers stats on Saturday. Not quite sure why that was hardcoded but I guess they figured that monitoring was least likely to be impacted on that day. If the OEM DBMS jobs are down you can also submit them by logging in the to the repository database as SYSMAN and execute the package: Begin      emd_maintenance.submit_em_dbms_jobs(); End; / Note that these procedures are automatically run through scheduled jobs once the job_queueue_ processes parameter is set to a value greater than 0.

The third release of Oracle Enterprise Manager Cloud Control is now available. It includes numerous enhancements such as updated user interface, improved EMCLI with scripting options, Administration Group enhancements, OMS Disaster improvements among others. For the complete list see the New Features page. For users still running on pre-12c or 12.1.0.1, it is a highly recommended upgrade. If you are running EM 12.1.0.2 you may see some benefits of upgrading but I personally wouldn't rush off unless there were some compelling features/fixes that would be of benefit. That said, if you do decide on going full speed with the new release, here is a step-by-step document on how I upgraded a POC environment with a single OMS and repository on the same server from 12.1.0.2 with PSU3 to 12.1.0.3. The official Oracle documentation lists the detailed steps for the upgrade here . The pre-requisite steps needed for the upgrade are listed below: 0. Allocate additional space (14GB on Linux...

Thanks to @BrianPardy for tweeting the availability of the first patch set update for Oracle Enterprise Manager 12.1.0.2.0. Brian also blogged about it. The PSU Readme lists quite a number of bugs fixed in the PSU. Surprisingly the application of the patch is quite easy. I applied it to my 12.1.0.2.0 lab environment without any issues. Just to test for real application on test and production servers. Download the patch  14840279  from My Oracle Support to your OMS server. Extract the zip file Make sure opatch is in your PATH. [oracle@oem3 14840279]$ which opatch /usr/bin/which: no opatch in (/u01/app/oracle/Middleware/oms/bin:/usr/lib64/qt-3.3/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/oracle/bin) [oracle@oem3 14840279]$ export PATH=$OMS_HOME/OPatch:$PATH [oracle@oem3 14840279]$ which opatch /u01/app/oracle/Middleware/oms/OPatch/opatch  Set your ORACLE_HOME environment variable to your OMS Home. [oracle@oem3 14840279]$ echo ...