Automatically create Service Request on MOS from OEM13c

This is step by step document to create Service Request on My Oracle Support for any open problem in Oracle Enterprise Manager. The Service Request will be created from within OEM itself and all required details and log files etc. will automatically be uploaded.

Note: I assume that you already have “Oracle Configuration Manager” configured for OEM environment.

Step 1: Navigate to Incident Manager

Login to the OEM13c console and Navigate to Incident Manager. Under Incident Manager as shown in the screenshot in the left panel Click on “All Open Problems”. Select the problem for which you want to open the “Service Request”. In the detail window on the bottom half of the screen under “Actions” click on “Support Workbench Package Diagnostic



Step 2: Login to Support Workbench

Next step is to provide the credentials of “Weblogic Host” {OMS Host} and “Weblogic Server”. As shown in the screenshot please use your PRV account named credentials to login to weblogic host. “Weblogic Server” credentials are already saved, please use the same credentials. “WLS_EMGC_GCD


Step 3: Select Packaging Mode.

In this step please select the type package {Quick or Custom} you want to upload on My Oracle Support. It is preferred to use “Quick Packaging”, it will upload all the required files together as one package.


Step 4: Create Package

Enter the required details as mentioned in the screenshot for the package. This includes “Package Name, description, MOS option, Create new SR, CSI, and SR Summary”. Once all the details are filled click on “Next”.

image1clip_image008Once you click on Next it will compile up all the logs and other information in the single package to upload on My Oracle Support.


Step 5: View Contents of Package

This step simply lists the Incidents which are included in this package. Click on “Next” to proceed.


Step 6: View Contents of Manifest file.

It lists all the details of the manifest file to be uploaded on the My Oracle Support. If you want you can review the contents and then click on “Next” to proceed.



Step 7: Schedule the package.

In this step, you can select the schedule for generating an upload file and send it to “My Oracle Support”. You can either do it “Immediately” or schedule it for later time. Click on “Submit” to finish the process.



Step 8: Confirmation

This screen shows that SR has been successfully created on MOS, but please note that this is a “DRAFT” service request. You have to login on MOS with your account and submit this SR manually.




Stay connected for more stuff on OEM13c…




Please follow and like us:
Follow by Email

OEM13c Release 2 Step by Step Upgrade

This is the step by step document to upgrade OEM12cR4 to OEM13cR2. Mentioned below are some important prerequisites, make sure to you do not skip anyone of them before starting your upgrade.


· Check the certification matrix to make sure your existing environment is certified for this upgrade. I have already gather the required details.

· EM13cR2 OMS requires Oracle as repository database.

· EM13cR2 agents don’t support Enterprise Linux earlier than version 6.

· Back up your repository database and OMS.

· Another important point to take is the timezone of Repository Database and OMS machine. Since in our case we have both OMS and Database on the same machine so it does not matter. However if the timezone is not same then, Upgrade will fail at ‘Plug-ins Perquisites check’ step.


Certification Matrix


Since our Existing environment is on RHEL Linux 6 so the certification matrix is based on that.


There are few plugin’s which have been obsoleted in new release 13c. Check if there are any obsolete plug-ins in your current system. Un-deploy obsolete plugins if exists both from OMS and Agent before proceeding with upgrade to EM13.2:

  • EMC Symmetrix Array (oracle.em.sesy)
  • EMC Celerra Storage (oracle.em.secs)
  • EMC CLARiiON Array (oracle.em.secl)
  • Microsoft Biz Talk Server (oracle.em.smbs)
  • Exalogic Elastic Cloud Infrastructure (oracle.em.soee)


Upgrade Process.

Step 1: Copy EMKey to the Management Repository.

Note: EMKey is used during upgrade, EM13c will need to access EMKey. { secret key to encrypt password}

$OMS_HOME/bin/emctl config emkey -copy_to_repos

Step 2: Make sure you have “optimizer_adaptive_features” disabled in your repository database, if not run the below mentioned SQL command.

SQL> alter system set optimizer_adaptive_features=false scope=spfile;


Step 3: If you have upgraded your database recently, make sure that database compatibility parameter equal to the database version.

SQL> alter system set compatible=”″ scope=spfile

To make the new changes take effect, please restart your database.

Step 4: Download the OEM13cR2 Setup from Oracle Website. Use the below mentioned URL to download 6 files included in setup.

Step 5: Copy Software on the installation server.

Make you copy all 5 files in one single folder. NOTE: Please do not unzip any file, EM13c installation doesn’t need you to unzip the files. In EM13c we have “em13200_linux64.bin” as executable we have to run this file as “oracle” user.


Step 6: Run the Setup and enter MOS Details.



The first screen that pops-up will request your credentials for MOS. This is optional not mandatory if you want to receive updates from Oracle you can put your credentials or you can leave it blank as well. “CLICK NEXT” to proceed.

Step 7: Software Update (Optional)

Next step is the software update window, here you will be prompted if you want to check for any new updates available for your new release on which you ware upgrading. Since 13c is released recently so it already contains all latest updates, still if you want to check you can do that by simply providing your MOS credentials as shown below in the screenshot.



Step 8: Pre-requisite Checks

At this step setup performs a check to make sure all the pre-requisites are passed successfully. Make sure you do not have Warning or Failed status for any one of the pre-requisites. Some warnings can be ignored but make you fix the “Failed” pre-requisites before proceeding to the next step as it can FAIL you upgrade later.



Step 9: Installation Types

In this step you will be prompted to select the “Installation Type”, since we are doing the upgrade we will select “Upgrade as existing Enterprise Manager System”. For upgrade there is only one option available “One-System Upgrade”.

Select the radio button as shown in the screenshot below and click on “NEXT”.



Step 10: Installation Details.

In this step you will be prompted to enter the middleware home location for new Oracle Enterprise Manager 13c. Make sure you provide the correct location as this is the directory where all binaries for OEM13c going to be stored.



Step 11: Database Connection Details.

Here you have to provide the connection details for your OMR database. Since we are doing the upgrade of our existing environment, “Connect Descriptor” field is already filled. You have to provide “SYS and SYSMAN” passwords.


EM13c gives as option to disable DDMP during the upgrade.

If you are planning to stop your EM for POST upgrade maintenance then it is recommended to DISABLE DDMP jobs. Deferred Data Migration (DDMP) is a post-upgrade activity to migrate the historical data of your old Enterprise Manager. Depending on how much data stored, it may take same time.

Also, before proceeding to next step make you have you have already backed-up your OMR. Select the check-box and click on “NEXT”.

Before you proceed, make sure you have applied latest PSU on your database to avoid failure during your repository upgrade.

Note: If you haven’t stopped the OMS and agent running on your OMS and OMR server (if OMS and database are on separate machines) , please stop them now. Once OMS and Agent are down then click on NEXT.

Run the below mentioned commands to stop OMS and Agent respectively.

$OMS_HOME/bin/emctl stop oms -all
$AGENT_HOME/agent_inst/bin/emctl stop agent

Although you stop the agents, you may still get a warning about them. Ignore it and continue to upgrade.


Step 12: Database Configuration Check.

When you click on “NEXT” in “Database Connection Details” window in the last step, it performs come checks for the existing database.




You may or may not receive warning depending on your database configuration.


Some of the warnings can be fixed automatically by the installer when you click “YES”, some of them you have to fix manually. In-order to avoid your upgrade to FAIL in middle make sure you fix all the warnings and then click “NEXT”.



Step 13: Plug-in Upgrade, select additional Plug-in’s if you want to install any of them during this installation..

This displays all your existing plug-ins which will be upgraded during this process. Please read thoroughly and click on “NEXT”. Also if you want to install and additional plugin’s in this install, select from the list.



Step 15: Enter Weblogic Details

Please enter the details of Weblogic server for your OEM13c installation. Make sure you choose new location for your OMS instance outside your Middleware home. Also enter your weblogic password.



Step 16: Shared Location Details for BI Publisher

If you already had BI Publisher installed and configured in your existing environment then BI Publisher automatically gets upgraded during upgrade to OEM13c. The checkbox shown in the below screenshot will be checked and grayed out by default only if BI Publisher is already configured.



Step 17: Ports Configuration

Do not make any changes until the mentioned ports are already being used. Accept the default ports and click on NEXT.



Step 18: Review Details

Review the information you entered, and then click the upgrade button to start upgrade process. The time for this upgrade will depend on hardware of your system.






Step 19: Run script as ROOT user to complete the installation. [ script is located in the middleware home]



Step 20: Final & Final Details



Step 21: POST Upgrade Steps.

Login to your 13c console using the sysman user and perform the POST-upgrade tasks. Navigate to the “upgrade agents” page under the “setup menu” to upgrade your agents.







Please follow and like us:
Follow by Email

Oracle Enterprise Manager Cloud Control 13c Release 2 ( available now

I am not now sure how many of you are aware that Oracle Enterprise Manager 13c Release 2 is available now for those who are not I have mentioned few of the Important URL’s for OEM13cR2 which might help you if you are planning to install or upgrade to this new release.

Certification Matrix of OEM13cR2 for RHEL 6

Download Link for OEM13cR2

OEM Cloud Control Upgrade Guide

Prerequisites for Upgrading to Enterprise Manager Cloud Control 13c Release 2


Soon I’ll be publishing new post Step by Step Upgrade guide to Cloud Control 13c Release 2.




Please follow and like us:
Follow by Email

Moved WordPress blog to my website “”


I have moved my WP blog to my new website “”, I am publishing all my new posts over there, hope you will like this. Need you support and suggestions are always welcome.


Deepak Sharma

Please follow and like us:
Follow by Email

Offline Database Patching in OEM12c


This is the step by step document of how you do database patching from OEM. Before we start I’ll just give small introduction about Patching in OEM.

There are two different methods by which we can do patching in OEM:

● Out-Of-Box Patching

● In-Place Patching

Out-Of-Box patching is the recommended method by Oracle, the advantage of using this method is that it reduces your downtime. On the contrary you need to have some extra (almost double to you ORACLE_HOME) space on your disk as this method CLONE your ORACLE_HOME so that in case of failure revert back is easily possible.

In-Place patching is also known as Offline patching, in this method downtime is more as compare to Out-Of-Box patching. So if you have planned maintenance window you can easily adopt this method.

In this blog we will be performing In-Place patching. So let’s see what are some prerequisites required before patching your database.


Required Roles and Permission:





Step 1: Create Normal and Privilege Credentials for Host

Before we start with the patching process make sure we have “Normal and Privilege” credentials set. Login to OEM console and create Normal and Privilege credentials if already not created.

Navigate to “Setup -> Security -> Named Credentials ”


Click on Create and put the required Details.



Make sure you TEST credentials before you SAVE them. So that the credentials are validated.




Step 2: Download Patches and Upload them to Software Library.

Download the patches to be applied from MOS and upload them to Software Library. Navigate to “Enterprise -> Provisioning and Patching -> Saved Patches” and follow the below mentioned steps.








Step 3: Check Recommended Patches and their details.

In order to check the recommended patches and details about them. Login to OEM using your credentials and Navigate to “Patching” Home Page as shown in the screenshot below. (Enterprise -> Provisioning and Patching -> Patches & Updates)




Patch Recommendations Details are shown on this homepage in the bottom left corner. (Classification View)




You can either see the details by selecting Classification View as shown in the above screenshot or by Target View as shown below. Else we also have “All Recommendations” link as well which will show all details together.

(Target View)



Click on “Database Instance” to check recommended patches. Patches are displayed in the form of table with details like Patch Name, Description, Release, Platform etc.

If you further want to check information for specific patch, select the particular patch row and further details like SPU’s include, Bugs resolved will be displayed below. You will also get the option to download the patch or add to Patch Plan.




If you click on “All Recommendation” link on the “Patches & Updates” Home page you will get something like this . All patches for different targets clubbed together in single table.




Particular Patch Details

Click on single row to check the details about that patch.




Step 4: Create a Patch Plan and add patches

After we have confirm the patches to be applied and their details. Next step is to add particular patch to a Patch Plan. Select a particular row and Click on “Add to Plan” followed by “ Add to New ” as shown in the below screenshot.




Create New Plan pop-up window will open, please enter a meaningful name and click on “Create Plan” button.




Now Click on “View Plan” to check the Plan details.




Step 5: Deploy Patch

Patch deployment is a 5-step process,

1. Plan Information

2. Patches

3. Deployment Options

4. Validations

5. Review & Deploy

Once you have created a Patch Plan, follow the above mentioned process and step by step and at last deploy the patch.


Plan Information

This step involved Plan description and the permissions, Enter the plan information details followed by granting permissions to existing users.





In this step you can add multiple patches to existing Patch Plan.


You can search the patches in three different ways, using Patch Number, using Advanced Method or by Recommended Patch Advisor.


Deployment Options

This is further multi-step process. Screenshot for each step is show below.

How to Patch {In Place or Out-Of-Box method}

What to Patch {Database Instance Targets details}

Where to Stage {Location of staging directory}

Credentials Information {Host Credentials with sudo permissions}


Notification {Email notifications phase}

Rollback {Rollback option in-case of failure}

Conflict Check {If any existing patch is conflicting}



Select the tested Named Credentials and Privilege Credentials for the host on which you are deploying the Patch. Do not forget to Validate them.

Make sure “Named Credentials and Privilege Credentials” are different if your OEM is as there is BUG reported in OEM12cR4.



Verify effected Database Instance Targets and Staging Directory by default it goes to “%emd_emstagedir%” directory.




Verify Customization, Notification, Rollback and Conflict Options before proceeding further.




Click on the “Analyze” button to start the Validation process, this process can take time depending on the Patches and Targets involved.



Check if any Issue remains even after Validation, Review them and then resolve them before proceeding further.


In-case there is some failures like I got the one shown below during the Review Process, make sure you fix them and then proceed with the “Deployment” process.



Review & Deploy

This is the last option, this page will display all information make sure you review the information thoroughly and if everything looks good click on “Deploy” button to start the deployment process.




Please follow and like us:
Follow by Email

Back to OEM Basics – Agent12c Blocked by OMS [Agent Resynchronization]

This blog is a part of my “Back to OEM Basics” series. In this I have explained in details how easily you can solve your “Agent blocked by OMS” issue. With the help of logs and screenshots I have made it more simple to understand.

Lets got step by step and see how you can fix your problem and can Unblock an blocked agent.

Oracle Agent usually gets blocked when it is Out-Of-Sync with the OMR repository database.


Step 1: How to check if agents are blocked, this can be simply done by login-in to OEM.


Please login to OEM and navigate to “Setup-> Manage Cloud Control –> Agents” as shown in the screenshot.




The “Manage Cloud Control” AGENTS home page will give you list all of the installed agents, you can sort the list using the “STATUS” column as shown in the below screenshot.




Step 2: Login to Agent server and check the logs to verify the cause.


I checked agent logs on the server where agent was BLOCKED and this is what I found.


Agent Logs:-

2016-09-20 10:13:04,906 [9825:547A0FF8:GC.SysExecutor.1036 (Ping OMS)] INFO - attempting initial heartbeat

2016-09-20 10:13:04,919 [9825:547A0FF8] INFO - The agent has been blocked by the OMS.

2016-09-20 10:13:04,919 [9825:547A0FF8] INFO - Reason the OMS blocked the agent: Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console.

2016-09-20 10:13:41,530 [9743:2F24D3F3] WARN - Subsystem (Ping Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@21a09189

2016-09-20 10:13:41,531 [9743:2F24D3F3] WARN - Subsystem (Upload Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@653b1740

2016-09-20 10:14:41,530 [9822:669C9195] WARN - Subsystem (Ping Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@354632cf

2016-09-20 10:14:41,531 [9822:669C9195] WARN - Subsystem (Upload Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@6cde3ddf

2016-09-20 10:15:41,532 [9836:6A4F37D3] WARN - Subsystem (Ping Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@39af50a4

2016-09-20 10:15:41,532 [9836:6A4F37D3] WARN - Subsystem (Upload Manager) returned bad status of oracle.sysman.gcagent.tmmain.lifecycle.AgentSystemMonitor$TaskStatus@9bce0a

2016-09-20 10:16:04,938 [9759:755A5435:GC.SysExecutor.1028 (Ping OMS)] INFO - attempting initial heartbeat

2016-09-20 10:16:04,948 [9759:755A5435] INFO - The agent has been blocked by the OMS.

2016-09-20 10:16:04,948 [9759:755A5435] INFO - Reason the OMS blocked the agent: Agent is out-of-sync with repository. This most likely means that the agent was reinstalled or recovered. Please contact an EM administrator to unblock the agent by performing an agent resync from the console.


Step 3: Check status of agent by running “emctl status agent” command.


D:oracleproductagent12cr3agent_instbin> emctl status agent

Oracle Enterprise Manager Cloud Control 12c Release 2

Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.


Agent Version     :

OMS Version       : (unknown)

Protocol Version  :

Agent Home        : D:/oracle/product/agent12cr3/agent_inst

Agent Binaries    : D:oracleproductagent12cr3core12.

Agent Process ID  : 3416

Parent Process ID : 2524

Agent URL         :

Repository URL    :

Started at        : 2016-09-16 22:43:30

Started by user   : HANHRRP3$

Last Reload       : (none)

Last successful upload                       : (none)

Last attempted upload                        : (none)

Total Megabytes of XML files uploaded so far : 0

Number of XML files pending upload           : 690

Size of XML files pending upload(MB)         : 1.13

Available disk space on upload filesystem    : 47.09%

Collection Status                            : Collections enabled

Heartbeat Status                             : Agent is blocked

Last attempted heartbeat to OMS              : 2016-09-20 10:43:05

Last successful heartbeat to OMS             : (none)

Next scheduled heartbeat to OMS              : 2016-09-20 10:46:05


Agent is Running and Ready


Step 4: Navigate to Agent home page in Oracle Enterprise Manager Console to verify and rectify issue.




The error message in console as well clearly shows that agent is Blocked and need to “unblock” it manually.


Step 5: Navigate to “Resynchronization” under “Agent” on the home page as show in the screenshot below.




Step 6: Select unblock agent Under “Agent Resynchronization” make the checkbox is checked and click on “Continue”.





Step 7: This confirms that “Agent Resynchronization” job has been executued successfully.


You can monitor the progress of the job by clicking the Job Name {eg. RESYNC_20160920104720}




Step 8: Check RESYNC Job Details and verify  if it is completed.




Step 9: Navigate back to agent home page and verify Agent status.

It should be “UP & RUNNING” after the RESYNC job has completed successfully.




This way you can easily un-block all of your Blocked agents and make them again fit for monitoring your targets.

Stay tuned for more “BACK TO OEM BASICS” Topics.




Please follow and like us:
Follow by Email

EM12c login FAILED for all users after database upgrade from to

Two days back I ran into an issue where I was not able to login to my OEM12c test environment using any of the account. This happened after OEM database upgrade. Recently I did upgrade of my OEM database from to followed by upgrade to

After upgrade was done successfully I tried to login to OEM using my account “dksharma” it gave me error, then I tried using the “sysman” but login failed again. All other users also  reported the same issue.

I have document all  my findings and solution to that in the attached document. If you also face the same Issue you use to document to fix your problem.





Please follow and like us:
Follow by Email

Prerequisite for OEM12cR4 to OEM13cR1 upgrade

If you have Oracle Enterprise Manager 12cR3/12cR4/12cR5 running on either RHEL or OEL and you are planning to upgrade your OEM to new release of 13c you must make sure that you meet below mentioned requirements.

I have shortlisted few mandatory and minimum requirements which you should keep in mind  while planning to upgrade to Oracle Enterprise Manager 13c or fresh installation of OEM13cR1.


In my next blog I’ll put the complete step by step document for OEM13cR1 upgrade.

Share your feedback and stay connected for next blog.





Please follow and like us:
Follow by Email

Upgrade your OEM12c to OEM13c -WHY?

In this blog I  have shared my recent webinar on Upgrade to OEM13c  -WHY?”. In this video I have explained few important features with example {screenshot} of Oracle Enterprise Manager 13c. These explained features are the one which were either missing or have been updated with some additional stuff.

This Webinar was done for AIOUG-North India Chapter for their monthly tech meet. This video is also shared on our Youtube channel as well. You can also find videos of all our previous webinar held in this year and last year.

G+ Link:

Youtube Link:

Do share your feedback as it will help me do the improvement in my future posts.






Please follow and like us:
Follow by Email

Silent Installation of Oracle 12C Agent on Linux Server

I know its very late but it was pending from my side since long. This is step by step silent installation of Oracle12c Agent on any linux machine. I have tried by best to make your job easy.

Please follow the below mentioned steps to Install Oracle 12c agent.


Step 1: Login to OEM server and then swtich to “oracle” user, using “sudo su – oracle“. Navigate to OMS home.

cd “/app/oracle/product/middleware/OMS12CR4/oms/bin”.


Step 2: Create a temporary directory {setup} under “tmp” where agent setup will be downloaded.

“mkdir -p /tmp/setup”


Step 3: Download Agent setup using below mentioned procedure.

Procedure is mentioned below:-


[oracle@testdb1 bin]$ pwd


[oracle@testdb1 bin]$ ./emcli login -username=sysman -password=formula1

Login successful


[oracle@testdb1 bin]$ ./emcli sync

Synchronized successfully


[oracle@testdb1 bin]$ ./emcli get_supported_platforms


Version =

Platform = Linux x86-64


Version =

Platform = Linux x86-64


Platforms list displayed successfully.


[oracle@testdb1 bin]$ ./emcli get_agentimage -destination=/tmp/setup -platform=”Linux x86-64″ -version=


=== Partition Detail ===

Space free : 3 GB

Space required : 1 GB

Check the logs at /app/oracle/product/middleware/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/get_agentimage_2016-08-05_00-57-38-AM.log

Downloading /tmp/setup/

File saved as /tmp/ setup /

Downloading /tmp/ setup /

File saved as /tmp/ setup /

Downloading /tmp/ setup /unzip

File saved as /tmp/ setup /unzip

Agent Image Download completed successfully.

[oracle@testdb1 bin]$ pwd


Step 4:  Copy setup from OEMAP1 server to LOCAL machine where agent needs to be installed. You can do this using WINSCP or any other file transfer.




Step 5:  Login to server as “oracle” user and create folder of Agent Installation.

mkdir – /app/oracle/product/agent12cr3



Step 6:  Navigate to location where agent setup was copied and run the below mentioned command.


[oracle@testdb1 agent_sw]$ ./ AGENT_BASE_DIR=/app/oracle/product/agent12cr3 EM_UPLOAD_PORT=4904 AGENT_REGISTRATION_PASSWORD=formula123


Validating the OMS_HOST & EM_UPLOAD_PORT

Executing command : /app/oracle/product/agent12cr3/core/ -classpath /app/oracle/product/agent12cr3/core/ oracle.sysman.agent.installer.AgentInstaller /app/oracle/product/agent12cr3/core/ /app/oracle/product/agent_sw /app/oracle/product/agent12cr3 -prereq

Validating oms host & port with url:

Validating oms host & port with url:

Return status:3-oms https port is passed

Unzipping the to /app/oracle/product/agent12cr3 ….

Executing command : /app/oracle/product/agent_sw/unzip -o /app/oracle/product/agent_sw/ -d /app/oracle/product/agent12cr3

Executing command : /app/oracle/product/agent12cr3/core/ -classpath /app/oracle/product/agent12cr3/core/ oracle.sysman.agent.installer.AgentInstaller /app/oracle/product/agent12cr3/core/ /app/oracle/product/agent_sw /app/oracle/product/agent12cr3 /app/oracle/product/agent12cr3/agent_inst AGENT_BASE_DIR=/app/oracle/product/agent12cr3


Executing agent install prereqs…

Executing command: /app/oracle/product/agent12cr3/core/ -debug   -ignoreSysPrereqs -prereqchecker -silent -ignoreSysPrereqs -waitForCompletion  -prereqlogloc /app/oracle/product/agent12cr3/core/ -entryPoint -detailedExitCodes PREREQ_CONFIG_LOCATION=/app/oracle/product/agent12cr3/core/  -J-DAGENT_BASE_DIR=/app/oracle/product/agent12cr3

Prereq Logs Location:/app/oracle/product/agent12cr3/core/<timestamp>.log

Agent install prereqs completed successfully


Cloning the agent home…

Executing command: /app/oracle/product/agent12cr3/core/ -debug   -ignoreSysPrereqs -clone -forceClone -silent -waitForCompletion -nowait ORACLE_HOME=/app/oracle/product/agent12cr3/core/   AGENT_BASE_DIR=/app/oracle/product/agent12cr3 AGENT_BASE_DIR=/app/oracle/product/agent12cr3 EM_UPLOAD_PORT=4903 AGENT_REGISTRATION_PASSWORD=formula123 -noconfig  ORACLE_HOME_NAME=agent12c4 -force b_noUpgrade=true AGENT_PORT=-1

Clone Action Logs Location:/app/oracle/oraInventory//logs/cloneActions<timestamp>.log

Cloning of agent home completed successfully


Attaching sbin home…

Executing command: /app/oracle/product/agent12cr3/core/ -debug   -ignoreSysPrereqs -attachHome -waitForCompletion -nowait ORACLE_HOME=/app/oracle/product/agent12cr3/sbin ORACLE_HOME_NAME=sbin12c4 -force

Attach Home Logs Location:/app/oracle/product/agent12cr3/core/<timestamp>.log

Attach home for sbin home completed successfully.


Updating home dependencies…

Executing command: /app/oracle/product/agent12cr3/core/ -debug   -ignoreSysPrereqs -updateHomeDeps -waitForCompletion HOME_DEPENDENCY_LIST={/app/oracle/product/agent12cr3/sbin:/app/oracle/product/agent12cr3/core/} -invPtrLoc /app/oracle/product/agent12cr3/core/ -force

Update Home Dependencies Location:/app/oracle/product/agent12cr3/core/<timestamp>.log

Update home dependency completed successfully.


Performing the agent configuration…

Executing command: /app/oracle/product/agent12cr3/core/ ORACLE_HOME=/app/oracle/product/agent12cr3/core/ RESPONSE_FILE=/app/oracle/product/agent12cr3/core/ ACTION=configure MODE=perform COMPONENT_XML={} RERUN=true

Configuration Log Location:/app/oracle/product/agent12cr3/core/<timestamp>.log

Agent Configuration completed successfully


The following configuration scripts need to be executed as the “root” user.


#Root script to run


To execute the configuration scripts:

  1. Open a terminal window
  2. Log in as “root”
  3. Run the scripts

Agent Deployment Successful.

Agent deployment log location:


Agent deployment completed successfully.




Step 7:  Secure Agent using below mentioned command.


[oracle@testdb1 agent_sw]$ cd /app/oracle/product/agent12cr3/agent_inst/bin/

[oracle@testdb1 bin]$ ./emctl secure agent

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.

Agent successfully stopped…   Done.

Securing agent…   Started.

Enter Agent Registration Password :

Agent successfully restarted…   Done.

EMD gensudoprops completed successfully

Securing agent…   Successful.




Step 7:  Add internal targets existing on the server and upload.

[oracle@testdb1 bin]$ ./emctl config agent addinternaltargets

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.


[oracle@testdb1 bin]$ ./emctl upload

Oracle Enterprise Manager Cloud Control 12c Release 3

Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.


EMD upload completed successfully

[oracle@testdb1 bin]$





Please follow and like us:
Follow by Email