Oracle Technologies Blog

By ASKM

Archive for the ‘Cloud Control 12c’ Category

Edit Add Modify Delete Oem 12c Agent Registration Password

Posted by Srikrishna Murthy Annam on January 19, 2013

Advertisements

Posted in Cloud Control 12c, OEM | Tagged: , , , , , | 1 Comment »

Blocking And Unblocking OEM Agent in OEM 12c

Posted by Srikrishna Murthy Annam on December 31, 2012

In this present short demo, i am going to show you how to block and unblock an oem agent manually in oem 12c. There might be various reasons an oem agent may into a blocked state and this demo shows you how to unblock it.

The reasons that the agent may go into blocked state are ..
If there is any network break between oem agent and oms server
If there is any space issue on oms server and oem agent can’t upload the metrics data to oms server

This demo does not contain any voice and the navigations are self explanatory. Leave your comments if you have any doubts.

 

Thanks

SRI

 

Posted in Cloud Control 12c | Tagged: , , , | Leave a Comment »

12c oem template export and import using emcli

Posted by Srikrishna Murthy Annam on May 15, 2012

This demo explains the steps to export and import a template in oem 12c using emcli command line tool.

 

Thanks

SRI

Posted in Cloud Control 12c | Tagged: , , , , | Leave a Comment »

Oracle VM templates for Cloud Control

Posted by Srikrishna Murthy Annam on May 2, 2012

Oracle VM templates for Cloud Control oem 12c are now available for download from edelivery.

Oracle VM Template for Enterprise Manager Cloud Control 12c Media Pack for x86 (64 bit)

Oracle VM Template for Enterprise Manager Cloud Control 12c (Agent only) Media Pack for x86 (64 bit)

Hope it helps

SRI

 

Posted in Cloud Control 12c | Tagged: , , | Leave a Comment »

CLOUD CONTROL INTEGRATION WITH OVM

Posted by Srikrishna Murthy Annam on May 1, 2012

OEM 12C CLOUD CONTROL INTEGRATION WITH OVM

  1. Configure Oracle Software Library    2
  2. Setting up the infrastructure for Online mode    3
  3. Setup MOS(My Oracle Support) Credentials    6
  4. Deploying the Cloud Plug-ins    6
  5. Deploying the Cloud Plug-ins to the Management Server    9
  6. Deploying the Oracle Virtualization Plug-in to the Management Agent    11
  7. Oracle VM Manager 3.0 Registration Prerequisites    12
  8. Registering the Oracle VM Manager in oem 12c    13
  9. Synchronizing the OVM Manager Targets    15

 

 

 

 

 

 

 

 

 

 

  1. Configure Oracle Software Library

    Oracle Software Library (Software Library) is a repository that stores software patches, virtual appliance images, reference gold images, application software and their associated directive scripts.

    Verify whether you already have the Software Library configured. If not follow the below steps to configure:

    From the Enterprise menu, select Provisioning and Patching, then click Software Library.

    From there choose actions > administration.

    If there is nothing configured yet, click Add then choose OMS Shared Filesystem location.

 

 

Upon addition of the location, a job executes to configure the Software Library. Under this location, all required entities for EMs features like Provisioning, Patching, and Cloud Management are populated.

Once the job is successful, you will see the components configured in the Software Library.

To view the Software Library, navigate to: Enterprise Manager > Patching and Provisioning > Software Library


 

 

  1. Setting up the infrastructure for Online mode

    If the enterprise manager is configured to connect to MOS , plugins or patches can be automatically downloaded. Follow the following sequence of steps ..

    1. Set up connection to MOS (Online Mode)

      Check to see if the connection to My Oracle Support is set to “Online”. Navigate to

      Setup > Provisioning and Patching > Offline Patching.

       

    2. The connection setting has to be “Online”. If not set, set it to Online and click Apply.

       

    3. Select the adjacent tab My Oracle Support and Proxy Connection

       

    4. Configure your Proxy Connection to connect to My Oracle Support. Provide the required Proxy Server, Port and Realm details, then click Apply.

       

    5. Once the configuration is done, click Test to check if the connectivity works correctly.

  2. Setup MOS(My Oracle Support) Credentials

  3. Deploying the Cloud Plug-ins

    Plug-ins must first be downloaded to the OMS using Self Update before they can be deployed. To enable monitoring of virtualization targets, you must download the plug-ins and deploy them. The following plug-ins must be deployed on the Management Server:

  • Oracle Virtualization
  • Oracle Cloud Application
  • Oracle Chargeback and Capacity Planning
  • Oracle Exalogic


Select one of the above plugins (list specified above) , then click Download. The Schedule Download dialog appears. In this example, “Oracle Virtualization” plug-in is selected.


Then it changes the status from “Available” to “Downloaded”

Repeat the same step to all the other plugins (Oracle Cloud Application, Oracle Chargeback and Capacity Planning, Oracle Exalogic)

Once an entity has been downloaded to the Software Library, it is ready to be applied to your installation. Select an update from the list whose status is Downloaded, then click Apply.

 


You will be redirected to the plug-in deployment page.


  1. Deploying the Cloud Plug-ins to the Management Server

    Complete the below steps to all the plugins mentioned in step 4.

    Select the plugin and deploy it on OMS. Right click the plugin ->Deploy on->Management server


     

    Plugin pre-requisites will be executed. After successful pre-requisite checks, click on deploy.

    NOTE : OMS will be bounced now.

    Once the OMS is up, navigate to Setup->Extensibility->Plug-in . The Plugin version on OMS is now 12.1.0.2.

 

  1. Deploying the Oracle Virtualization Plug-in to the Management Agent

Click on Add to add the management agent where plugin will be deployed

Once you have selected the agents, click continue

It runs the plugin pre-requisites and click next

Click Deploy, to deploy the plug-in on the agents

  1. Oracle VM Manager 3.0 Registration Prerequisites

    The following prerequisites must be meet before Oracle VM Manager can be registered in Oracle Enterprise Manager 12c Cloud Control.

    1. The Oracle Virtualization plug-in must be install and enabled on the Oracle Management Service.
    2. The Oracle VM Manager host must have the Oracle Management Agent (OMA) and be a monitored target in Oracle Enterprise Manager 12c Cloud Control.
    3. The Oracle VM Manager host must have the Oracle Virtualization plug-in.
    4. The preferred credentials for the Oracle VM Manager host must be configured in Oracle Enterprise Manager 12c Cloud Control.
    5. The Oracle Management Service and the Oracle VM Manager host must have consistent name resolution using DNS with both forward and reverse lookups.
  2. Registering the Oracle VM Manager in oem 12c

     

     

Table 1

Oracle VM Manager Registration Page Title

Entry Selections and Entry Syntax

  1. Name

The name entered in the “Name” text box is displayed on the Infrastructure Cloud page.

  1. EM Agent URL

The EM Agent URL is selected by clicking the magnifying glass icon. A pop-up window will appear, select the Oracle VM Manager agent from the list. The EM Agent URL syntax is: “https://<AGENT-FQDN&gt;:3872/emd/main/”

Note: The Oracle VM Manager host can be selected as long as the host is managed target by OEM with the Oracle Virtualization plug-in.

  1. Oracle VM Manager Core

Enter “http://<ORACLE VM MANAGER HOST FQDN>:7001” in the
Oracle VM Manager Core URL text box.

  1. Automatic Synchronization

Select the Automatic Synchronization check box to enable automated synchronization between OEM and the Oracle VM API Core.

  1. Monitoring Credentials for Oracle VM Manager

Enter the Oracle VM Manager admin user name and the admin
password in the Monitoring Credentials for Oracle VM Manager text fields.

  1. Administration Credentials for Oracle VM Manager / Use Administration Credentials

Enter the Oracle VM Manager admin user name and the admin password in the Administration Credentials for Oracle VM Manager text fields.

 
 

Select the Use Administration Credentials check box.

  1. Oracle VM Manager Console URL

Enter the non-SSL Oracle VM Manager URL, i.e.http://<ORACLE VM MANAGER HOST FQDN>:7001/ovm/console/faces/login.jspx in the Oracle VM Manager Console URL text box.

  1. Submit

Once all of the information has been entered, click the Submit button to start the registration job.

  1. Synchronizing the OVM Manager Targets

Posted in Cloud Control 12c, OEM, Uncategorized | Tagged: , , | Leave a Comment »

Cloud Control OEM 12c Installation

Posted by Srikrishna Murthy Annam on April 28, 2012

OEM 12C CLOUD CONTROL INSTALLATION

1.Software    2

2.OS installation    2

3.Database Installation    2

4.Oem 12c Prerequisites    2

a.Hardware Requirements    2

b.Operating System Requirements    2

c.Package Requirements    2

d.Kernel Parameter Requirements    3

e.Library Requirements    3

f.Operating System Groups and Users Requirements    3

g.Unique Host Name and Static IP Address Requirements    4

h.Temporary Directory Space Requirements    4

i.Central Inventory Requirements    4

j.UMASK Value Requirements    4

k.File Descriptor Requirements    4

l.Existing Database Version Requirements    5

m.Host File Requirements    5

n.Port Requirements    5

o.Internet Connection Requirements    5

5.Oem 12c Installation Procedure    6

6.Verification Checks    16

7.Starting and Stopping oem 12c Services    17

 

  1. Software

The required software for the oem 12c cloud control are :

  1. Oracle Linux 6.1 (x86_64) Download
  2. Oracle Database 11gR2 (x86_64) Download
  3. Enterprise Manager Cloud Control 12c (12.1.0.1) (x86_64) with BP1 patch Download
  4. OS installation :

Oracle Linux 6.1 (x86_64) installation :

  1. Database Installation :

Oracle Database 11gR2 installation :

Below links help to install database

Documentation

OBE

Video

  1. Oem 12c Prerequisites :

 

  1. Hardware Requirements :

CPU, RAM, Heap Size, and Hard Disk Space requirements vary depending on the type of installation we are choosing. Please review the here to know the exact hardware requirements.

 

  1. Operating System Requirements :

Ensure that you install Enterprise Manger Cloud Control only on certified operating system as mentioned in the Enterprise Manager Certification Matrix.

  1. Package Requirements :

    make-3.81

    binutils-2.17.50.0.6

    gcc -4.1.1

    libaio-0.3.106

    glibc-common-2.3.4

    libstdc++ -4.1.1

    setarch-1.6

    sysstat-5.0.5

    rng-utils-2.0

    libXtst-1.0.1-3.1(x86_64)

    xorg-x11-utils (This package is required only for GUI-based interactive installation, and not for silent installation)

     

    In addition, install the 32-bit version as well as the 64-bit version of glibc-devel-2.5-49 to avoid any linking errors while installing the OMS. The installer checks for this package, so if this package is not installed, the installer displays an error.

     

  2. Kernel Parameter Requirements

For installing an OMS or a Management Agent on Unix operating systems (32-bit or 64-bit), set the kernel.shmmax parameter to a value 1 byte less than 4 GB or 4294967295.

 

To verify the value assigned to kernel.shmmax parameter, run the following command:

cat /proc/sys/kernel/shmmax

 

To set the value for kernel.shmmax parameter, run the following command:

sysctl -w kernel.shmmax=<new value>

 

 

  1. Library Requirements :

    Install glibc-2.5.12 package

 

  1. Operating System Groups and Users Requirements:

# /usr/sbin/groupadd oinstall

 

# /usr/sbin/useradd -g oinstall oracle

 

# passwd oracle

  1. Unique Host Name and Static IP Address Requirements :

Ensure that you check the network configuration to verify that the host on which you are installing resolves to a unique host name and a static IP address that is visible to other hosts in the network.

You must use a static IP address. If you use a dynamic IP address, the installation might fail.

Ensure that the host name specified in /etc/hosts file is unique, and that it maps to the correct IP address. Following is the recommended format of the /etc/hosts file:

<ip address> <fully_qualified_host_name> <short_host_name>

 

If the DNS server is configured, then it should resolve the host name for the OMS machine correctly. For example, all these command must return the same output:

nslookup host1

nslookup host1.foo.com

nslookup 141.81.5.71

  1. Temporary Directory Space Requirements :

Ensure that you allocate 400 MB of space for a temporary directory where the executables can be copied.

  1. Central Inventory Requirements :

Ensure that you allocate 100 MB of space for the central inventory directory.

Also ensure that the central inventory directory is not on a shared file system. If it is already on a shared file system, then switch over to a non-shared file system by following the instructions outlined in My Oracle Support note 1092645.1.

To determine whether the Oracle Inventory group exists, enter the following command:

$ more /etc/oraInst.loc

If the oraInst.loc file exists, then the output from this command looks like:

inventory_loc=/u01/app/oracle/oraInventory

inst_group=oinstall

  1. UMASK Value Requirements:

Ensure that you set the default file mode creation mask (umask) to 022 in the shell startup file.

  1. File Descriptor Requirements :

If the current value is less than 4096, then as root user, update the /etc/security/limits.conf file as shown below:

<UID> soft nofile 4096

<UID> hard nofile 4096

  1. Existing Database Version Requirements :

Ensure that the database is patched with all the Patch Set Updates (PSU) or Critical Patch Updates (CPU) released for that release. Also ensure that you apply the patches.

If you use Oracle Database 11g Release 2 (11.2.0.1), then ensure that you apply the patches for bugs 10014178 and 8799099.

If you use Oracle Database 11g Release 1 (11.1.0.7), then ensure that you apply Patch Set Update 2 and the patches for bugs 8644757 and 7525072.

The database can also have the Automatic Memory Management (AMM) feature enabled.

  1. Host File Requirements :

Ensure that the host name specified in the /etc/hosts file is unique, and ensure that it maps to the correct IP address of that host. Otherwise, the installation can fail on the product-specific prerequisite check page.

The following is the recommended format of the /etc/hosts file:

<ip> <fully_qualified_host_name> <short_host_name>

  1. Port Requirements :

Ensure that the ports you assign (within the given range) to the following components are free and available:

 

Admin Server HTTP SSL Port = 7101 – 7200

Enterprise Manager Upload HTTP Port = 4889 – 4898

Enterprise Manager Upload HTTP SSL Port = 1159, 4899 – 4908

Enterprise Manager Central Console HTTP Port = 7788 – 7798

Enterprise Manager Central Console HTTP SSL Port = 7799 – 7809

Oracle Management Agent Port = 3872, 1830 – 1849

 

To verify if a port is free, run the following command:

On Unix:

netstat -anp | grep <port no>

  1. Internet Connection Requirements :

Oracle recommends that the host from where you are running the installer have a connection to the Internet so that the configuration information can be automatically collected and uploaded to My Oracle Support.

  1. Oem 12c Installation Procedure :

  1. Verification Checks :

    Access the following URL with sysman user and navigate to different pages to verify everything looks good.


https://<hostname with FQDN>:7803/em

  1. Starting and Stopping oem 12c Services :

Use the following commands to start all components :

$ export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1

$ export OMS_HOME=/u01/app/oracle/Middleware/oms

$ export AGENT_HOME=/u01/app/oracle/Middleware/agent/core/12.1.0.1.0

 

# Start everything

$ $ORACLE_HOME/bin/sqlplus ‘/as sysdba’

SQL> startup

 

$lsnrctl start listener

 

$ $OMS_HOME/bin/emctl start oms

 

$ $AGENT_HOME/bin/emctl start agent

 

Use the following commands to stop all components :

$ export ORACLE_HOME=/u01/app/oracle/product/11.2.0/db_1

$ export OMS_HOME=/u01/app/oracle/Middleware/oms

$ export AGENT_HOME=/u01/app/oracle/Middleware/agent/core/12.1.0.1.0

 

# Stop everything

$ $OMS_HOME/bin/emctl stop oms -all

 

$ $AGENT_HOME/bin/emctl stop agent

 

$ $ORACLE_HOME/bin/sqlplus ‘/as sysdba’

SQL> shut immediate

 

$ $lsnrctl stop listener


 

Posted in Cloud Control 12c, OEM, Uncategorized | Tagged: , , | Leave a Comment »

 
%d bloggers like this: