Sunday, September 30, 2012

EM12c: How to fix 'Job Purge' repository scheduler job when it shows as down, though its up (EM12cR2 upgrade issue)

Issue: After upgrading EM from BP1 to EM12cR2, EM reports 'Job Purge' repository scheduler job as down though it's actually up.

One can see the status of this Job, on the Repository page (Setup -> Manage Cloud Control -> Repository), in the Repository Scheduler Jobs Status section, the "Job Purge" job is shown as down with a red arrow and blanks for both Next Scheduled Run and Last Scheduled Run. All the other jobs look good and are running successfully.



Action:
Please run the following SQL as SYSMAN to correct the problem.

UPDATE MGMT_PERFORMANCE_NAMES SET display_name = NULL,
   dbms_jobname = NULL, is_dbmsjob = 'N', is_deleted = 'Y'
  WHERE UPPER(DBMS_JOBNAME) LIKE 'MGMT_JOB_ENGINE.APPLY_PURGE_POLICIES%';
COMMIT;

Now it should look like as given below:

Note: One can also refer to discussion at this Oracle forum or this blog

Friday, September 21, 2012

EM12c: How to discover a standalone OHS (Oracle HTTP Server)?


OHS(Oracle HTTP Server) can be discovered and monitored in EM12c. If an OHS is part of weblogic domain, it gets discovered during Weblogic Farm/domain discovery and monitoring automatically starts for that OHS. Details of metrics collected for an OHS that is part of weblogic domain can be found here.

However, if one has a standalone OHS. Its discovery and monitoring is bit different. Steps for discovering standalone OHS are given later in the article. One has to be aware that even after discovery of standalone OHS, all one gets is availability status metric for OHS. No other metrics are collected for standalone OHS.
Here are the steps to discover standalone OHS.

1. Go to Setup> Add Targets > Add Targets Manually
2. select Add Non-Host Targets by Specifying Target Monitoring Properties,
3. select Target Type as Oracle HTTP Server and the Monitoring Agent,
4. on the next page you will need to add the properties for OHS

Target Name - For example "Oracle_WT1"
Machine Name - fully qualified host name like "abc.xyz.com"
Oracle Home Path - /u01/Oracle/Middleware/Oracle_WT1
EM Target Type - oracle_apache
Port Number - 7777  (based on the opmnctl status -l  output ), 7777 is the default http port for OHS
Version of Apache Server - 2.2

There are many other mandatory fields, which are relevant only when OHS is registered with weblogic and can be ignored for standalone OHS discovery. So one can provide dummy values for them(e.g. "na"). These values are not used. Example is
given in following screenshot.

Tuesday, September 18, 2012

EM12c: Some interesting new features in Middleware Management with EM 12c R2(12.1.0.2) ?

With EM12c R2, FMW plugin version 12.1.0.3 has been released. With this release lot of new features have been introduced under Middleware Management and Application Performance Management areas. One can find complete list of features on MW mgmt and APM links.

Out of all features, I find following features somewhat more interesting:
1.    Business Application - A new target has been added called as Business Application target. This target combines capabilities of RUEI+BTM+JVM+ADP. The BA is associated with a system target, RUEI applications and Business Transactions.
The BA target enables a user to see and understands the health of the business application. The target represents a holistic view of the monitored application. It has its own dashboard.
Business Application has
•    Business Application Target
•    Business Application Dashboard
•    Business Applications List Page
•    Drill-down from Request Instance Diagnostics to RUEI Session Diagnostics
•    BTM Transaction to EMCC Target Association
•    Business Application Creation Wizard
•    Experience Monitoring in the Business Application Dashboard

For more details on Business Applications, click here.
Click here for demo.

2.    MWaaS (MiddleWare as a Service) – EM12cR2 cloud management has been enhanced for providing MiddleWare services along with IaaS and DBaaS. It allows administrators to create, monitor and manage a private or public MWaaS environment. MWaaS has a complete runtime env. comprised of all services necessary to deploy and run an enterprise-class java-j2ee application, including services such as application hosting, persistence store, application integration and APIs that enable programmatic access to additional computing services that might be required by an application.

MiddleWare as a Service has
•    Resource Pool
•    MWaaS Quotas
•    MWaaS Request Settings
•    Service Templates
•    Provision and De-provision Service Instance
•    Manage Application Lifecycle
•    Service Instance Scaling
•    Manage Data Sources

For more details on MWaaS, click here.

3.    Exalogic management enhancements – With EM12cR2 and Ops center, now one can see Exalogic Schematic views and manage Exalogic boxes well. These enhancements are:
•    Integrated hardware and software schematics
•    Hardware-software topology views
•    Hardware targets monitoring (Compute, ZFA appliance, Infiniband Fabric, ILOM)
•    OTD monitoring
•    Support for virtual and non-virtual configurations
•    Monitoring of Exalogic vServer guest VMs
•    Health checks
•    Trusted partition/vCPU licensing report
Click here for demo.

4.    Service Target Dashboard - With this new feature, administrators can quickly create "out of box" overviews of the health of related services. They can create templates that contain a group of services selected from the defined services in Enterprise Manager. Any Enterprise Manager user can use these defined dashboards to quickly correlate the health of services, the status of key metrics, incidents and related status of the service level agreements tied to the service.
For more details, see this demo .

Thursday, September 13, 2012

EM12c: Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2) Now Available!

Oracle Enterprise Manager Cloud Control 12c Release 2 (12.1.0.2) is now available on OTN on ALL platforms. Highlight of this release is simultaneous release of EM12c R2 on all platforms. This is primarily a stability release which incorporates many of issues and feedback reported by early adopters. In addition, this release contains many new features and enhancements in areas across the board.
New Capabilities and Features
  • Enhanced management capabilities for enterprise private clouds:
    • Introduces new capabilities to allow customers to build and manage a Java Platform-as-a-Service (PaaS) cloud based on Oracle Weblogic Server. The new capabilities include guided set up of PaaS Cloud, self-service provisioning, automatic scale out and metering and chargeback.
    • Enhanced lifecycle management capabilities for Oracle WebLogic Server environments: Combining in-context multiple domain, patching and configuration file synchronizations.
    • Integrated Hardware-Software management for Oracle Exalogic Elastic Cloud through features such as rack schematics visualization and integrated monitoring of all hardware and software components.
  • The latest management capabilities for business-critical applications include:
    • Business Application Management: A new Business Application (BA) target type and dashboard with flexible definitions provides a logical view of an application’s business transactions, end-user experiences and the cloud infrastructure the monitored application is running on.
    • Enhanced User Experience Reporting: Oracle Real User Experience Insight has been enhanced to provide reporting capabilities on client-side issues for applications running in the cloud and has been more tightly coupled with Oracle Business Transaction Management to help ensure that real-time user experience and transaction tracing data is provided to users in context.
  • Several key improvements address ease of administration, reporting and extensibility for massively scalable cloud environments including dynamic groups, self-updateable monitoring templates, bulk operations against many events, etc.
New and Revised Plug-Ins:
Several plug-Ins have been updated as a part of this release resulting in either new versions or revisions. Revised plug-ins contain only bug-fixes and while new plug-ins incorporate both bug fixes as well as new functionality.
Plug-In Name Version
Enterprise Manager for Oracle Database 12.1.0.2 (revision)
Enterprise Manager for Oracle Fusion Middleware 12.1.0.3 (new)
Enterprise Manager for Chargeback and Capacity Planning 12.1.0.3 (new)
Enterprise Manager for Oracle Fusion Applications 12.1.0.3 (new)
Enterprise Manager for Oracle Virtualization 12.1.0.3 (new)
Enterprise Manager for Oracle Exadata 12.1.0.3 (new)
Enterprise Manager for Oracle Cloud 12.1.0.4 (new)

Installation and Upgrade:
  • All major platforms have been released simultaneously (Linux 32 / 64 bit, Solaris (SPARC), Solaris x86-64, IBM AIX 64-bit, and Windows x86-64 (64-bit) )
  • Enterprise Manager 12.1.0.2 is a complete release that includes both the EM OMS and Agent versions of 12.1.0.2.
  • Installation options available with EM 12.1.0.2: User can do fresh Install or an upgrade from versions EM 10.2.0.5, 11.1, or 12.1.0.2 ( Bundle Patch 1 not mandatory).
  • Upgrading to EM 12.1.0.2 from EM 12.1.0.1 is not a patch application (similar to Bundle Patch 1) but is achieved through a 1-system upgrade.
Documentation:

Customer Webcast - EM 12c Installation and Upgrade: This webcast is for customers who are interested in learning how to successfully deploy or upgrade to EM 12.1.0.2.
Enterprise Manager 12c R2 Resources:

Thursday, September 06, 2012

EM12c: How to reset the OEM Session timeout (Login timeout)?


As per EM 12c, there are following OMS properties that can influence session time out:
1. oracle.sysman.eml.maxInactiveTime
This property is used for the UI to time out a logged in user session. Default value is 45 min.
emctl utility can be used to reset this parameter.
e.g.
$ ./emctl get property -name oracle.sysman.eml.maxInactiveTime
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
SYSMAN password:
Value for property oracle.sysman.eml.maxInactiveTime for oms host.abc.com:4890_Management_Service is 45

$ ./emctl set property -name oracle.sysman.eml.maxInactiveTime -value 60
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0 
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
SYSMAN password:
Property oracle.sysman.eml.maxInactiveTime for oms host.abc.com:4890_Management_Service has been set to value 60
OMS restart is required to reflect the new property value

After resetting the oracle.sysman.eml.maxInactiveTime, do stop and start oms.
$ ./emctl stop oms

$ ./emctl start oms

2. oracle.adf.view.rich.poll.timeout
The ADF framework uses this property for UI pages that use 'polling'. Default value is 10 min.

Resetting of this property also requires OMS restart.