ORACLE EM DBA

Problems, Solutions, Test Cases from my professional and personal experience in technologies like Oracle Enterprise Manager 13 c,Oracle Enterprise Manager 12c, Oracle Configuration Manager and some other stuff.

Month: December 2015

12c Agents compatibility with OMS 13c…

Last time when I performed upgrade from 11g Grid Control to 12c Cloud Control, I had to replace all existing 11g Oracle Agents to Agent 12c. Oracle stated that 11g Oracle Agents are not compatible with OEM 12c, so it left me with no other option than to install Oracle Agent 12c on all monitoring hosts.

Even though multiple Agent installation on different hosts is available in 12c cloud Control but for one time when you have to do install and configure Agent 12c on more than 150 hosts, you really do not want to do that and could there have been shortcut it could have ease your life.

The same question came to my mind again, do I have to replace all my existing 12c Agents if I upgrade to this new release.  The answer is “NO” I do not have to replace my old Oracle Agent 12c.

Thanks to Oracle you do not have to do it but only if you have Oracle Management Agent 12c Release 3 or higher installed on your hosts.

YES, that’s true. Oracle Agent 12c is compatible with new release of Oracle Management Service 13c.

Mentioned below is the Compatibility table across OMS13c and Agent 12c.

Releases Oracle Management Agent 12c Release 3 (12.1.0.3) Oracle Management Agent 12c Release 4 (12.1.0.4) Oracle Management Agent 12c Release 5 (12.1.0.5) Oracle Management Agent 13c
Oracle Management Service 13c Yes Yes Yes Yes

There are some important points which you have to keep in mind before you begin Installing OEM 13c.

  • Ensure that you have the latest Enterprise Manager Cloud Control software. {13c}
    • You can refer to the Oracle Enterprise Manager Cloud Control Advanced Installation and Configuration Guide.” for more information.
  • Oracle Management Service 13c can communicate only with the above listed versions of Management Agents.
  • Another important point to remember is while you download and run the OEM 13c software making sure there are no white spaces in the name of the directory.
    • Example: do not download and run the software from a directory titled “EM Software” because there is a white space between the two words of the directory name.
  • Through installation wizard, installation of OEM 13c Cloud Control can be done only on a single host, that is, locally on the server from where the wizard is invoked. Installation cannot be done on multiple or remote hosts.
  • Do not set the ORACLE_HOME and ORACLE_SID environment variables, also you must ensure that the Oracle directories do NOT appear in the PATH.
  • OEM13c onwards preinstalled JDK or Oracle WebLogic Server is no more supported.
  • Java Development Kit (JDK) 1.7.0_80 and Oracle WebLogic Server 12c Release 1 (12.1.3.0) are installed as the part of EM13c Cloud Control.
  • Dedicated Weblogic Server 12c.
    • You must ensure that the Oracle WebLogic Server 12c Release 1 (12.1.3.0) installed by the Enterprise Manager Cloud Control Installation Wizard is dedicated for Enterprise Manager Cloud Control.
    • You must not have any other Oracle Fusion Middleware product installed in that Middleware home.
  • OEM 13c Cloud Control cannot coexist with any Oracle Fusion Middleware product in the same Middleware home because the ORACLE_COMMON property is used by both the products.
  • As a prerequisite, you must have an existing Oracle Database {can also have the Automatic Memory Management (AMM) feature enabled} to configure the Management Repository.
  • Manual Startup required for OMS and OMA.
    • If you install the OMS and the Oracle Database, which houses the Management Repository, on the same host, then when you reboot the host, the OMS and the Management Agent installed with it will not automatically start up. You will have to manually start them.

I have listed few of the important ones, you can find detailed information in Oracle Documentation.

Hope this will help you setting up your new environment.

You can reach out to me on my personal email id: sharma.deepak345@gmail.com

Thanks

Deepak Sharma

2015 in review

The WordPress.com stats helper monkeys prepared a 2015 annual report for this blog.

Here’s an excerpt:

A San Francisco cable car holds 60 people. This blog was viewed about 3,500 times in 2015. If it were a cable car, it would take about 58 trips to carry that many people.

Click here to see the complete report.

Hardware Requirement for OEM13c

In my last blog I mentioned “Step by step installation of OEM13c on Windows server”.

This blog contains all the hardware requirements for all three components. “Oracle Management Service, Oracle Management Agent and Oracle Management Repository {Database}

Mentioned below are the three different tables which will help you understand what all ammo {Hardware} is required before you leave for war.{OEM13c Installation}

NOTE: If you wish to install OEM13c on single host {both OMS and OMR (database) on single machine} than make sure you meet hardware requirments mentioned in TABLE 1 and TABLE 2 together.

Minimum CPU, RAM, Heap Size, and Hard Disk Space Requirements Per OMS

TABLE 1

  Evaluation or Simple Installation Advanced Installation (SMALL) Advanced Installation (MEDIUM) Advanced Installation (LARGE)
Deployment Size Evaluation or Simple Small Medium Large
Configuration 1 OMS, <100 Targets, <10 Agents, < 3 Concurrent User Sessions 1 OMS, <1000 Targets, <100 Agents, <10 Concurrent User Sessions 2 OMSes, >=1000 but <10,000 Targets, >=100 but <1000 Agents,>=10 but <25 Concurrent User Sessions 2 OMSes, >=10,000 Targets, >=1000 Agents, >=25 but <=50 Concurrent User Sessions 4 OMSes, >=10,000 Targets, >=1000 Agents, >=25 but <=50 Concurrent User Sessions
CPU Cores/Host

(Can be shared with other processes)

2 4 6 12 6
RAM

(With Oracle BI Publisher and JVMD Engine)

10 GB 10 GB 12 GB 24 GB 12 GB
Hard Disk Space

(With Oracle Software Library, Oracle BI Publisher, and JVMD Engine)

24 GB 24 GB 24 GB 24 GB 24 GB
Temporary Directory Hard Disk Space 10 GB 10 GB 10 GB 10 GB 10 GB
Oracle WebLogic Server JVM Heap Size 1 GB 1.7 GB 4 GB 8 GB 4 GB

Note:  The physical memory {RAM} mentioned here includes 5 GB of RAM required for Oracle BI Publisher. At the time of installation.

If you choose not to configure Oracle BI Publisher, then the actual physical memory required can be 5 GB less than what is mentioned here.

Minimum CPU, RAM, and Hard Disk Space Requirements for Management Repository

TABLE 2

  Evaluation or Simple Installation Advanced Installation (SMALL) Advanced Installation (MEDIUM) Advanced Installation (LARGE)
Deployment Size Small Medium Large
Configuration 1 OMS, <100 Targets, <10 Agents, < 3 Concurrent User Sessions 1 OMS, <1000 Targets, <100 Agents, <10 Concurrent User Sessions 2 OMSes, >=1000 but <10,000 Targets, >=100 but <1000 Agents,>=10 but <25 Concurrent User Sessions > 2 OMSes, >=10,000 Targets, >=1000 Agents, >=25 but <=50 Concurrent User Sessions
CPU Cores/Host 4 6 12
RAM 7 GB 10 GB 18 GB
Hard Disk Space 23 GB

(SYSTEM: 600 MB, MGMT_TABLESPACE: 15 GB, MGMT_ECM_DEPOT_TS: 1 GB, MGMT_AD4J_TS: 3 GB, TEMP 3 GB, ARCHIVE LOG OFF)

147 GB

(SYSTEM: 600 MB, MGMT_TABLESPACE: 100 GB, MGMT_ECM_DEPOT_TS: 1 GB, MGMT_AD4J_TS: 10 GB, TEMP 10 GB, ARCHIVE LOG AREA: 25 GB)

455 GB

(SYSTEM: 600 MB, MGMT_TABLESPACE: 300 GB, MGMT_ECM_DEPOT_TS: 4 GB, MGMT_AD4J_TS: 30 GB, TEMP 20 GB, ARCHIVE LOG AREA: 100 GB)

649 GB

(SYSTEM: 600 MB, MGMT_TABLESPACE: 400 GB, MGMT_ECM_DEPOT_TS: 8 GB, MGMT_AD4J_TS: 50 GB, TEMP 40 GB, ARCHIVE LOG AREA: 150 GB

CPU, RAM, and Hard Disk Space Requirements for Oracle Management Agent, Hybrid Cloud Agent, Hybrid Cloud Gateway Agent

NOTE: Mentioned below in TABLE 3 are the different ways you can install Oracle Agent 13c, the hardware required will entirely depend on the method you adopt to install Oracle Agent. Please select accordingly.

TABLE 3

  CPU Cores Per Host

 

RAM Agent Base Directory Space Swap Space Temporary Directory Space Stage/Working Directory Space Agent Instance Home
Agent Installation Using the Add Host Targets Wizard or Any of the Silent Methods 2 512 MB 1.5 GB 500 MB 1 GB N/A Included as part of the Agent Base Directory space.  
Agent Cloning Using the Add Host Targets Wizard or Any of the Silent Methods 2 512 MB 1.5 GB 500 MB 500 MB N/A Included as part of the Agent Base Directory space.  
Agent Installation Using Agent Gold Images 2 512 MB 1.5 GB 500 MB 500 MB 750 MB Included as part of the Agent Base Directory space.  
Agent Gold Image Creation N/A N/A N/A N/A N/A 1 GB N/A  
Agent Gold Image Staging N/A N/A N/A N/A N/A 1 GB N/A  

 

I hope this will help you do design your server before you install Oracle Enterprise Manager 13c on that. Make sure you do meet minimum requirements as listed above in the three table, failing in same will result in Poor Performance and if unlucky your system might also get crash. It happened with me very first time. 😉

Play Safe…

Thanks

Deepak Sharma

 

 

 

OEM 13c Step by Step Installation on Windows

In this blog I have explained the step by step installation of Oracle Enterprise Manager 13c on Windows server.

 

Make sure you have sufficient resources on your laptop or server since OEM13c is really very heavy and might slow down performance of your machine if it does not get sufficient food {resources }.

Since I have done installation on my personal laptop so I have mentioned the resource requirement accordingly. So make sure your machine has below listed resources available.

 Minimum CPU, RAM, Heap Size, and Hard Disk Space Requirements Per OMS for Simple Installation

   Simple Installation
Deployment Size Evaluation or Simple
Configuration 1 OMS, <100 Targets, <10 Agents, <3 Concurrent User Sessions
CPU Cores/Host

(Can be shared with other processes)

2
RAM11The physical memory mentioned here includes .5 GB of RAM required for Oracle BI Publisher. At the time of installation, if you choose not to configure Oracle BI Publisher, then the actual physical memory required can be .5 GB less than what is mentioned here.

(With Oracle BI Publisher and JVMD Engine)

10 GB
Hard Disk Space

(With Oracle Software Library, Oracle BI Publisher, and JVMD Engine)

24 GB
Temporary Directory Hard Disk Space 10 GB
Oracle WebLogic Server JVM Heap Size 1 GB

I am assuming you already have a database created for your OEM. In my environment I have 12C database created.

Step 1: Download the software. {there are 5 files}

http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-windows-2823282.html

Step 2: Run the installer

image1

It will run for sometime and you can monitor the progress.

image2

Once the Installer is finished, it run the prerequisite system compatibility test to start the setup.

image3

Step 3: Enter your MOS account details (optional), if you want to receive security updates from Oracle.

image4

Just a warning will be displayed if you skip your “Support Details” part, you have to confirm that you do not wish to receive updates.

image5

Step 4: Software update search. It is recommended to run this step to ensure your environment is ready for this installation.

image6

If your machine is having all the updated required softwares it will prompt “No updates found”

image7

Step 5: Prerequisite Check. It will run a check to ensure you have sufficient resources available.

{Like in my case I got warning for in-sufficient RAM minimum required was 10 Gb and I had 8Gb of RAM, still I decided to continue with Installation. I was crazy to test this new release and lazy enough to increase my machine’s RAM to 10Gb.}

image8

Click NEXT to continue with Installation.

image9

Step 6: Installation Type. {Simple or Advanced}

If you are already familiar with previous releases and are EM DBA you can go for “Advanced” option.

image10

Step 7: Setting up Installation directories. Here you have configure you Middleware Home, Agent Base Directory and Hostname.

image11

Step 8: Set Administrator Password and put your database connection details.

[Informational message will pop-up with recommendation to setup AL32UTF8 character set for EM Repository database.]

image12

Click OK, it will execute some prerequisite checks.

image13

In next few steps you will be prompted for mismatch of you database settings if they already do not match with the recommended setting for OEM13c installation.

Prompted to check “optimizer_adaptive_features” parameter

image14

Prompted to check “parallel max and min servers” parameter

image15

Prompted to check “shared_pool_size” & “session_cached_cursors” parameter

image16

Step 9 :  Configure Software Library  and Enable BI Publisher.

OEM13c gives you option to configure and enable “BI Publisher” during Installation itself.

image17

Step 10: Review all details entered in all previous steps.

image18

image19

Step 11: Start the installation. 

[Now if you are installing it on your laptop with insufficient resources just like mine 😉 RAM 8Gb ,  believe me installation is going to take more than 4  hours it happened with me. So if you do not want to get irritated while setting this up make sure you have a very good machine with you for your installation ]

image20

image21

image22

image23

Once the Installation is finished, it will run a clean-up process.

image24

Now you are ready to use your OEM13c.

EXCITED… Believe me I was  very much eager to start using it. I have put some more screenshot of the “Login Console, Welcome Page, Incident Manager etc.. “ check out below.

login13c

Accessibility Preferences Page

accessibility13c

Disclaimer Page

messages_disclaimer

Incident Manager Page

incident_manager

I’ll be posting more stuff soon on this new release of OEM 13c. Hope this blog will help to install OEM13c easily on your machine.

Till next post, it me Signing Off, time to go to sleep now. Good Night Folks..

Oracle Enterprise Manager 13c Release 1

Hi Folks,

Finally the Oracle has released new version of Oracle Enterprise Manager” OEM13cR1.  Oracle has introduced a lot of new features in this release which you gonna like for sure. I have just installed it on my laptop and let me tell you I am liking it more than 12c. Totally new GUI, a lot new stuff at Infrastructure stack. If you just want to check the top 12 listed features of OEM13c, below is the list.

Top-12 feature list.

  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 13c (view screenwatch)

Oracle Enterprise Manager 13c: New and Exciting Features

Check out interesting facts about this new release “Oracle Enterprise Manager 13c: What’s New

You can easily download this new version from below mentioned URL.

http://www.oracle.com/technetwork/oem/enterprise-manager/downloads/index.html

OEM13cR1 is available for following platforms:

click on the hyperlink and it will navigate you to the download page for that platform.

Soon I’ll be posting more stuff on OEM13cR1.

 

Thanks

Deepak Sharma

 

OMS Log and Trace files in OEM12c.

Hi All,

I have mentioned few of the important log files which can help you guys troubleshoot Issues related to your OMS {Oracle Management Service.}

If we talk about the OMS log files you can easily find them under

<EM_INSTANCE_BASE>/em/<OMS_NAME>/sysman/log/‘  so in my environment the path is “/app/oracle/product/middleware/gc_inst/em/EMGC_OMS1/sysman/log/

where EM_INSTANCE_BASE = /app/oracle/product/middleware/gc_inst

and OMS_NAME= EMGC_OMS1

File names and their description is mentioned below:

  • emctl.log  – contains information about ’emctl’ commands execution
  • emoms.log – contains information of OMS actions and errors
  • emoms.trc – can be helpful in troubleshooting different issues
  • emoms_pbs.log – contains information about ‘platform background service’ application
  • emoms_pbs.trc – trace file for ‘platform background service’ application

Please keep in mind that just like in other application/databases in OMS as well the size of log is restricted. These logs files can be segmented into a configurable number of segments of a configurable size so they do not need to be manually deleted or managed. When the file reaches the pre-defined maximum size, the OMS rolls the logging information to a new file name and starts writing to a new log or trace file.  The settings is managed by parameter log4j.appender.emlogAppender.MaxFileSize  and log4j.appender.emtrcAppender.MaxFileSize respectively} in emomslogging.properties it is recommended to modify these parameters via the EMCTL utility.

This ability avoids the log files to grow large in size.

For more details on the location of the OMS log and trace files as well as the commands which can be used to modify the logging and tracing parameters, you can refer to MOS note

EM 12c: Steps to Locate and Manage the Various Logs/Trace files in a 12c OMS Installation [1448308.1]

Also the In built feature of checking log files from GUI of OEM12c makes it easier for user to troubleshoot and locate the files.

You can search file by navigating to “Enterprise < Monitoring < Logs“. Here you get the different search criteria using which you can search the log files for different targets.

In next blog I’ll publish in details how log files can be managed through GUI.

© 2017 ORACLE EM DBA

Theme by Anders NorenUp ↑