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.

Tag: OEM13c

Schedule daily RMAN backup report using 13c Cloud Control

This blog explains the step by step process by which you can create and schedule your Daily RMAN Backup report through Oracle Enterprise Manager 13c Cloud Control. Please note the process will remain same even if you are on any previous release of Cloud Control or Grid Control.

Recently came requirement in my team, where I have to send daily report of scheduled RMAN backups. I have documented all the steps so that I can share with all users on my blog.

NOTE:-  If your database is registered in Catalog, you can always use catalog database to get this information about daily RMAN backup. But if that’s not the case you can follow below steps to generate your own report.

Step 1: Login to OEM console and navigate to “Information Publisher Reports” page.

Step 2: Click on “Create” button as highlighted to start creating a new report.

Step 3: Building Report Definition

As shown in the above screenshot enter the details like Report Name, Category, Sub-Category etc. Since we will be using the OEM repository database to fetch all the details make sure you use “Use the specified target” and select the Repository database.

You can set the “Priviledges” and “Time Period” as per your need.

Next Step is to add the elements in your report, which is nothing but actual formating of your report. We will add just one Heading “Styled Text” and one “SQL Table”  which will have all detailed information.

Click on “Add” button on the “Elements” page to add multiple elements as shown in the below screenshots.

 

You can set the “elements” parameters as per your requirement. Select the “Table from SQL” radio button as highlighted and click on “Continue” button.

 

Step 4: Use SQL to generate report.

select database_name as “Database Name”,

       start_time as “Start Time”,

       end_time as “End Time”,

       status as “Completion Status”,

       input_type as “Backup Type”,

       output_device_type as “Device”,

       output_bytes_display as ” Backup Size”

from mgmt$ha_backup

where –input_type like ‘%FULL’ AND

END_time > (TO_DATE(sysdate, ‘DD-MON-RR’) – 1)

order by End_TIME desc ;

 

I have commented the “input_type” in where clause, you can modify the query as per your requirement.

Click on “Set Parameters” icon to update elements for “Table from SQL”.

For more information about the mgmt$ha_backup view you can use the below  specified link.

http://docs.oracle.com/cd/B16240_01/doc/em.102/b40007/views.htm#sthref1288

 

Step 5: Scheduling the Report.

As shown below in the screenshot, you can modify the settings for Scheduling the report as per your requirement. Once you are done with all settings, you can either click on “Preview” button to see your report or can click on “OK” button to save it.

Note:-  Do not forget to check “Schedule Report” check box on the top of the page. I have by mistake forgot in this screenshot.

You will get the confirmation message once your report has been created successfully without any errors. Like the one in the below screenshot.

Just like this you can use the same process to generate as many custom reports as per your requirement.

Thanks

ADDKS

emctl command failed -“agent_13.2.0.0.0/perl/bin/perl: Argument list too long”

[Stack Guard Vulnerability in Red Hat Enterprise Linux 7]

Yesterday I came across incident where the agent did not start as the “emctl” command got failed with a new error message. This happened after recent Infrastructure Maintenance Activity where OS patching was scheduled by our Infrastructure team on all servers. The host on which this issue occur had OS Version RHEL 7 “Red Hat Enterprise Linux Server release 7.3 (Maipo)”.

So all emctl commands whether it was “emctl start agent”, “agent stop agent” even “emctl help” failed. The error returned was “agent_13.2.0.0.0/perl/bin/perl: Argument list too long”. Check the screenshot below explains the entire scenario.

ERROR Message:- “agent_13.2.0.0.0/perl/bin/perl: Argument list too long

Cause:- Why are applications failing to start with error message “Argument list too long” after applying the fix for Stack Guard Vulnerability in Red Hat Enterprise Linux 7 ?

https://access.redhat.com/security/vulnerabilities/stackguard?sc_cid=70160000000gzltAAA&

https://access.redhat.com/solutions/3098341

Solution:-  Change the commonenv file found in agent_13.2.0.0.0/bin to hash out this line

After making this change the issue got fixed and emctl command was running successfully without any issue.

Thanks

ADDKS

OEM13c – The page has expired. Click OK to continue.

If you are getting an error message or Pop-UP which says “The page has expired. Click OK to continue.” This means that your Cloud Control session has expired or timeout as there was no activity in your session.

The default value for session timeout is 45 minutes. Can we increase this session timeout frame, YES! You can. You set this value as per requirement of your company’s security policy. It may vary for different clients or companies.

As per your requirement you can increase the Session Timeout time by changing the value of “oracle.sysman.eml.maxInactiveTime” parameter. Also note that the value for this parameter is always defined in Minutes. In-my case the requirement was to keep the session active unless the user itself does not logs out from the application. So I set the value of oracle.sysman.eml.maxInactiveTime” parameter to -1. But if let’s say you want the session to be active for 10 hours you can set the value to 600. However if you want your session be active forever like in my case, you can set its value to -1.

NOTE: Zero means that the value is set to default than 45 minutes.

To check which session timeout is currently active, you can deduct the following command.

[oracle@hanoemap1 bin]$ cd –

/app/oracle/product/middleware13C/bin

[oracle@hanoemap1 bin]$ ./emctl get property -name oracle.sysman.eml.maxInactiveTime

Oracle Enterprise Manager Cloud Control 13c Release 2

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

SYSMAN password:

Value for property oracle.sysman.eml.maxInactiveTime at Global level is -1

[oracle@hanoemap1 bin]$

clip_image001

NOTE: This change will need your OMS to restart, if you have multi-OMS environment, you may need to bounce both OMS.

You can also change this property from EM Console if you want. Navigate to Setup -> Manage Cloud Control -> Management Servers.

clip_image003

From Management Servers Home Page, Drop Down Management Servers and click on “Configuration properties”

clip_image004

On Management Server Configuration Properties Page, you can see all the properties listed, along with “oracle.sysman.eml.maxInactiveTime” in our case, highlighted in Yellow.

clip_image006

Click on the property Name, for whom you want to change the value. It will take you to “Set Property” page where you can make the changes.

clip_image008

Make the change in the property value and Click on Save.

Thanks

Deepak

OEM13cR2 migration from RHEL 6 to RHEL 7

OEM13cR2 migration from RHEL 6 to RHEL 7

In this Blog I have documented all the steps you need to follow if you are planning to migrate your “OEM13cR2” from RHEL 6 to RHEL 7. In my environment I had my production OEM12cR4 on RHEL 6, which I upgraded to OEM13cR2. Since we were in process of migrating all our database and application servers to RHEL 7, there comes the requirement when I have to migrate my OEM13cR2 as well to RHEL 7. In My environment I have having both OMS and OMR {Repository Database} on same machine.

Make sure you have below mentioned Passwords with you before you start the migration process.

  • Sysman
  • Weblogic
  • Agent Registration Password
  • Administration Server Password
  • Node Manager

 

Note:  Before performing the migration of OEM13cR2 to RHEL 7 makes sure you have valid backups of OMS_Home, Software Library & Repository Database. The Repository database can be migrated before OMS migration or after OMS migration.  

 

 

Below mentioned Bug has reported for the first time with Oracle during this migration of OEM13cR2 to RHEL7. Oracle has provided Patch 24903006 make sure to apply the patch after the “Software Only” install of OMS on RHEL 7.

Note: This is INTERNAL ONLY research. No action should be taken by the customer on this information. This is research only, and may NOT be applicable to your specific situation.
Bug 25211101 : OMS recovery on a diff host fails during OMS Secure
Bug 24903006
: EM 13.1: OMS RECOVER FAILED AT SECURE OMS STEP

Perform these steps on source server [houoemap1]

Step: 1 Check source OMS details 

[oracle@houoemap1 bin]$ cd $OMS_HOME/bin

[oracle@houoemap1 bin]$ ./emctl status oms –details

 

Oracle Enterprise Manager Cloud Control 13c Release 2

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

Enter Enterprise Manager Root (SYSMAN) Password:

Console Server Host        : houoemap1.dksharma.com

HTTP Console Port          : 7788

HTTPS Console Port         : 7802

HTTP Upload Port           : 4889

HTTPS Upload Port          : 4903

EM Instance Home           : /app/oracle/product/middleware/gc_inst1/em/EMGC_OMS1

OMS Log Directory Location : /app/oracle/product/middleware/gc_inst1/em/EMGC_OMS1/sysman/log

OMS is not configured with SLB or virtual hostname

Agent Upload is locked.

OMS Console is locked.

Active CA ID: 1

Console URL: https://houoemap1.dksharma.com:7802/em

Upload URL: https://houoemap1.dksharma.com:4903/empbs/upload

 

WLS Domain Information

Domain Name            : GCDomain

Admin Server Host      : houoemap1.dksharma.com

Admin Server HTTPS Port: 7102

Admin Server is RUNNING

 

Oracle Management Server Information

Managed Server Instance Name: EMGC_OMS1

Oracle Management Server Instance Host: houoemap1.dksharma.com

WebTier is Up

Oracle Management Server is Up

JVMD Engine is Up

 

BI Publisher Server Information

BI Publisher Managed Server Name: BIP

BI Publisher Server is Up

 

BI Publisher HTTP Managed Server Port   : 9701

BI Publisher HTTPS Managed Server Port  : 9803

BI Publisher HTTP OHS Port              : 9788

BI Publisher HTTPS OHS Port             : 9851

BI Publisher is locked.

BI Publisher Server named ‘BIP’ running at URL: https://houoemap1.dksharma.com:9851/xmlpserver

BI Publisher Server Logs: /app/oracle/product/middleware/gc_inst1/user_projects/domains/GCDomain/servers/BIP/logs/

BI Publisher Log        : /app/oracle/product/middleware/gc_inst1/user_projects/domains/GCDomain/servers/BIP/logs/bipublisher/bipublisher.log

[oracle@houoemap1 bin]$

 

Step 2: Note down all OMS parameters for future reference. 

 

Login as sysman user in the repository database and execute the below mentioned SQL.

SQL> select * from mgmt_oms_parameters; 

HOST_URL

NAME

VALUE

TIMESTAMP

select * from mgmt_oms_parameters;

houoemap1.dksharma.com:4889_Management_Service

SERVER_SSL_PORT

7301

08-OCT-16

houoemap1.dksharma.com:4889_Management_Service

ORACLE_HOME_INSTALL

/app/oracle/product/middleware/middleware13c

08-OCT-16

houoemap1.dksharma.com:4889_Management_Service

TIMESTAMP_PBS

22-12-2016 08:31:15

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

CONTEXT_ROOT_PBS

/empbs

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

TIMESTAMP

22-12-2016 08:31:57

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

OMS_URL

http://houoemap1.dksharma.com:4889/em

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

HOST_NAME

houoemap1.dksharma.com

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

EM_SERVER_NAME

EMGC_OMS1

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

OMS_ID

1

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

ORACLE_HOME

/app/oracle/product/middleware/middleware13c

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

INSTANCE_HOME

/app/oracle/product/middleware/gc_inst1/em/EMGC_OMS1

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

EM_DOMAIN_NAME

GCDomain

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

UNIQUE_OMS_NAME

GCDomain#EMGC_OMS1#13.2.0.0.0

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

IS_ADMIN_HOST

true

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

EM_RELEASE_VERSION

13.2.0.0.0

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

OMS_STARTUP_MODE

 

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

TIMESTAMP_CONSOLE

22-12-2016 08:31:57

28-MAY-14

houoemap1.dksharma.com:4889_Management_Service

CONTEXT_ROOT_CONSOLE

/em

28-MAY-14

 

 

From the source OMS machine, copy the EMKEY to the repository [houoemap1]: 

oracle@houoemap1 bin]$ ./emctl config emkey -copy_to_repos

Oracle Enterprise Manager Cloud Control 13c Release 2
Copyright (c) 1996, 2016 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
The EMKey has been copied to the Management Repository. This operation will cause the EMKey to become unsecure.
After the required operation has been completed, secure the EMKey by running “emctl config emkey -remove_from_repos”.
[oracle@houoemap1 bin]$

Step 3: Take a backup of OMS Configuration from the Source OMS host [houoemap1]: 

$ <OMS_HOME>/bin/emctl exportconfig oms -dir /backup/ [provide the sysman password when requested]

[oracle@houoemap1 bin]$ ./emctl exportconfig oms -dir /backup/

 

Oracle Enterprise Manager Cloud Control 13c Release 2

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

Enter Enterprise Manager Root (SYSMAN) Password :

ExportConfig started…

Backup directory is /backup/OEMTST_OMS_BACKUP

Machine is Admin Server host. Performing Admin Server backup…

Exporting emoms properties…

Exporting secure properties…

 

Export has determined that the OMS is not fronted

by an SLB. The local hostname was NOT exported.

The exported data can be imported on any host but

resecure of all agents will be required. Please

see the EM Advanced Configuration Guide for more

details.

 

Exporting configuration for pluggable modules…

Preparing archive file…

Backup has been written to file: /backup/OEMTST_OMS_BACKUP/opf_ADMIN_20161222_084714.bka

 

The export file contains sensitive data.

 You must keep it secure.

 

ExportConfig completed successfully!

[oracle@houoemap1 bin]$

Step 4: Check plugins on source OMS using the following query 

Connect to the Management Repository as SYSMAN and run the below mentioned query. Download all plugins using the returned links by the query, if they are non default plugin’s, DO rename all *.zip to *.opar

SELECT
epv.display_name,
epv.plugin_id,
epv.version,
epv.rev_version,decode(su.aru_file, null, ‘Media/External’,    ‘https://updates.oracle.com/Orion/Services/download/’||aru_file||’?aru=’||aru_id||chr(38)||’patch_file=’||aru_file) URL
FROM
em_plugin_version epv,

  em_current_deployed_plugin ecp,

  em_su_entities su
WHERE
epv.plugin_type NOT IN (‘BUILT_IN_TARGET_TYPE’, ‘INSTALL_HOME’)
AND ecp.dest_type=’2′
AND epv.plugin_version_id = ecp.plugin_version_id
AND su.entity_id = epv.su_entity_id;

 

 

DISPLAY_NAME

PLUGIN_ID

VERSION

REV_VERSION

URL

Systems Infrastructure                                          

oracle.sysman.si                                        

13.2.1.0.0                                

0

https://updates.oracle.com/Orion/Services/download/p24746686_112000_Generic.zip?aru=20652625&patch_file=p24746686_112000_Generic.zip

Oracle Fusion Middleware

oracle.sysman.emas

13.2.1.0.0

0

https://updates.oracle.com/Orion/Services/download/p24746666_112000_Generic.zip?aru=20652284&patch_file=p24746666_112000_Generic.zip

Oracle Database

oracle.sysman.db

13.2.1.0.0

0

https://updates.oracle.com/Orion/Services/download/p24746640_112000_Generic.zip?aru=20652282&patch_file=p24746640_112000_Generic.zip

Oracle Exadata

oracle.sysman.xa

13.2.1.0.0

0

https://updates.oracle.com/Orion/Services/download/p24746691_112000_Generic.zip?aru=20652626&patch_file=p24746691_112000_Generic.zip

Oracle Cloud Framework

oracle.sysman.cfw

13.2.1.0.0

0

https://updates.oracle.com/Orion/Services/download/p24746646_112000_Generic.zip?aru=20652289&patch_file=p24746646_112000_Generic.zip

Apache Tomcat

oracle.em.satc

13.2.1.0.0

0

https://updates.oracle.com/Orion/Services/download/p24746715_112000_Generic.zip?aru=20652291&patch_file=p24746715_112000_Generic.zip

 

As already mentioned the above query returns the list of plug-ins along with the URLs to download them if they were downloaded through self-update. 

 

Once you have downloaded the plugin’s move them to new server [target – houoemap2]

 

[oracle@houoemap2 oem13c_plugins]$ pwd

/backup/OEM13cR2_linuxX64/oem13c_plugins

 

[oracle@houoemap2 oem13c_plugins]$ mv p24746640_112000_Generic.zip p24746640_112000_Generic.opar

[oracle@houoemap2 oem13c_plugins]$ mv p24746646_112000_Generic.zip p24746646_112000_Generic.opar

[oracle@houoemap2 oem13c_plugins]$ mv p24746666_112000_Generic.zip p24746666_112000_Generic.opar

[oracle@houoemap2 oem13c_plugins]$ mv p24746691_112000_Generic.zip p24746691_112000_Generic.opar

[oracle@houoemap2 oem13c_plugins]$ mv p24746715_112000_Generic.zip p24746715_112000_Generic.opar

[oracle@houoemap2 oem13c_plugins]$ mv p24746686_112000_Generic.zip p24746686_112000_Generic.opar

[oracle@houoemap2 oem13c_plugins]$

 

 

Perform these steps on source server [houoemap2]

Step 5: Install OMS 13c home on new target host in Software only mode

ORACLE_HOME path exactly should match with source host. Do not run ConfigureGC.sh after software only installation. 

clip_image002[6]

 

 

Step 6: Install plugins if you installed non default plugins and additional plugins. 


Also once the installation of OMS is done, make sure, if you have applied any patches on source OMS those need to apply on new OMS home. 

 $ORACLE_HOME/sysman/install/PluginInstall.sh -pluginLocation <Plugins downloaded locations> 

./PluginInstall.sh -pluginLocation /app/oracle/product/oem13c_plugins/

                     

 

 

clip_image004[6]

 

clip_image005[6]

 

Step 7: Copy Software Library from source to target host, also copy the Inventory folder from source OMS to target OMS server.

Note: If the inventory folder exists on target server then take a backup of original folder on target server then copy from source to target.

Note: If BIP publisher was already configured, all BIP shared locations (sharedLoc) should also be accessible.

[ tar the swlib file then untar on target server in the same path. ]

e.g: running from target OMS server

scp -r oracle@houoemap1: /data2/oms12cr3/omsshared/ /data2/oms12cr3/omsshared/

scp -r oracle@houoemap1:/app/oracle/oraInventory /app/oracle/oraInventory

 

Step 8: Copy OMS backup file to target host [houoemap2]

 

Copy the backup file to the target host which was generated in step 2.

[oracle@houoemap1 emcc]$ scp  /backup/OEMTST_OMS_BACKUP/opf_ADMIN_20161222_084714.bka oracle@houoemap2/backup/OEMTST_OMS_BACKUP/opf_ADMIN_20161222_084714.bka

Step 9: Check if emInstanceMapping.properties and gc_inst directory exists 

Login to target machine [houoemap2] and make sure “emInstanceMapping.properties” file and “gc_inst” directory does not exists. If it exists the make sure you delete/move/rename them.

 

 /u01/app/oracle/product/13.2.0
[oracle@emcc oms]$ ls sysman/config/emInstanceMapping.properties
ls: cannot access sysman/config/emInstanceMapping.properties: No such file or directory
 

 

 

Apply Patch 24903006  before starting the recovery of OMS.

 

[oracle@houoemap1 OMSPatcher]$ find /app/oracle/product/middleware/middleware13c/ -name java
/app/oracle/product/middleware/middleware13c/oracle_common/lib/java
/app/oracle/product/middleware/middleware13c/oracle_common/jdk/jre/bin/java
/app/oracle/product/middleware/middleware13c/oracle_common/jdk/bin/java
[oracle@houoemap1 OMSPatcher]$

 

[oracle@houoemap1 OMSPatcher]$ cd /app/oracle/product/middleware/middleware13c/oracle_common/jdk/jre/bin
[oracle@houoemap1 bin]$ ./java -version

java version “1.7.0_111”
Java(TM) SE Runtime Environment (build 1.7.0_111-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.111-b13, mixed mode)
[oracle@houoemap1 bin]$

 

[oracle@houoemap1 bin]$/app/oracle/product/middleware/middleware13c/oracle_common/jdk/jre/bin/java -jar /app/oracle/product/6880880/opatch_generic.jar -silent oracle_home=/app/oracle/product/middleware/middleware13c

 

 

[oracle@houoemap1 24903006]$ omspatcher apply -analyze
OMSPatcher Automation Tool
Copyright (c) 2016, Oracle Corporation. All rights reserved.

OMSPatcher version : 13.8.0.0.1
OUI version : 13.8.0.0.0
Running from : /app/oracle/product/middleware/middleware13c
Log file location : /app/oracle/product/middleware/middleware13c/cfgtoollogs/omspatcher/opatch2017-02-04_18-11-22PM_1.log

OMSPatcher log file: /app/oracle/product/middleware/middleware13c/cfgtoollogs/omspatcher/24903006/omspatcher_2017-02-04_18-11-29PM_analyze.log

Please enter OMS weblogic admin server URL(t3s://houoemap1.dksharma.com:7102):>
Please enter OMS weblogic admin server username(weblogic):>
Please enter OMS weblogic admin server password:>

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) “24903006” and Oracle Home “/app/oracle/product/middleware/middleware13c”…
Sub-patch(es) “24903006” are successfully analyzed for Oracle Home “/app/oracle/product/middleware/middleware13c”

Complete Summary
================

All log file names referenced below can be accessed from the directory “/app/oracle/product/middleware/middleware13c/cfgtoollogs/omspatcher/2017-02-04_18-11-22PM_SystemPatch_24903006_1”

Prerequisites analysis summary:
——————————-

The following sub-patch(es) are applicable:

Featureset Sub-patches Log file
———- ———– ——–
oracle.sysman.top.oms 24903006 24903006_opatch2017-02-04_18-11-29PM_1.log

Log file location: /app/oracle/product/middleware/middleware13c/cfgtoollogs/omspatcher/24903006/omspatcher_2017-02-04_18-11-29PM_analyze.log

OMSPatcher succeeded.
[oracle@houoemap1 24903006]$

 

Step 10: Run omsca in recovery mode specifying the export file taken earlier to configure the OMS.

[oracle@houoemap2 middleware]$ cd middleware13c/bin/

 

[oracle@houoemap2 bin]$ ./omsca recover -as -ms -nostart -backup_file /backup/opf_ADMIN_20170224_064743.bka -EM_BIP_PORT 9701 -EM_BIP_HTTPS_PORT 9803 -EM_BIP_OHS_PORT 9788 -EM_BIP_OHS_HTTPS_PORT 9851

 

Oracle Enterprise Manager Cloud Control 13c Release 13.2.0.0.0

Copyright (c) 1996, 2016, Oracle. All rights reserved.

 

log4j:WARN No appenders could be found for logger (emctl.secure.oms.SecureOMSCmds).

log4j:WARN Please initialize the log4j system properly.

OS check passed.

OMS version check passed.

Performing Admin Server Recovery…

Retrieved Admin Server template.

Source Instance Host name where configuration is exported : houoemap1.dksharma.com

instHost name retrieved from local host name : houoemap2.dksharma.com

Populated install params from backup…

Enter Administration Server user password:

Confirm Password:

Enter Node Manager Password:

Confirm Password:

Enter Repository database user password:

Enter Agent Registration password:

Confirm Password:

Doing pre requisite checks ……

Pre requisite checks completed successfully

 

Checking Plugin software bits

Proceed to recovery

Setting up domain from template…

Setup EM infrastructure succeeded!

Admin Server recovered from backup.

Now performing cleanup of OMS EMGC_OMS1…

Now launching DeleteOMS…

OMS Deleted successfully

 

Delete finished successfully

Now launching AddOMS…

Infrastructure setup of EM completed successfully.

 

Doing pre deployment operations ……

Pre deployment of EM completed successfully.

 

Deploying EM ……

Creating Data source first !!

Deployment of EM completed successfully.

 

Configuring webtier ……

Configuring webTier completed successfully.

 

Importing OMS configuration from recovery file…

 

If you have software library configured

please make sure it is functional and accessible

from this OMS by visiting:

 Setup->Provisioning and Patching->Software Library

 

Importing configuration for pluggable modules…

Warning: Could not import files for module ocm: ocm: OCM Import Failed: could not find deriveCCR(/app/oracle/product/middleware/middleware13c/ccr/bin/deriveCCR)

Securing OMS ……

Adapter already exists: emgc_USER

Adapter created successfully: emgc_GROUP

Post “Deploy and Repos Setup” operations completed successfully.

 

Performing Post deploy operations ….

Total 0 errors, 85 warnings. 0 entities imported.

pluginID:oracle.sysman.core

Done with csg import

pluginID:oracle.sysman.core

Done with csg import

pluginID:oracle.sysman.core

Done with csg import

pluginID:oracle.sysman.core

Done with csg import

No logging has been configured and default agent logging support is unavailable.

Post deploy operations completed successfully.

 

EM configuration completed successfully.

EM URL is:https://houoemap2.dksharma.com:7802/em

 

Add OMS finished successfully

Recovery of server EMGC_OMS1 completed successfully

OMSCA Recover completed successfully

[oracle@houoemap2 bin]$

Step 11: Migrate OMR to target machine [houoemap2]

Once the OMS has been recovered successfully now you can Migrate OMR database target host. You can use the below mentioned document to do the database migration but step may vary.

https://docs.google.com/document/d/1CPjAXzNGui-XR8IfpNxzpt99T1cc7j6vvQXInqH05kg/edit

Step 12: Configure OMS for new migrated Repository database.  [Target Host]

 

[oracle@houoemap2 bin]$ ./emctl config oms -store_repos_details -repos_port 1521 -repos_sid OEMTST -repos_host houoemap2.dksharma.com -repos_user SYSMAN -repos_pwd formula1

 

Oracle Enterprise Manager Cloud Control 13c Release 2

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

Successfully updated datasources and stored repository details in Credential Store.

If there are multiple OMSs in this environment, run this store_repos_details command on all of them.

And finally, restart all the OMSs using ’emctl stop oms -all’ and ’emctl start oms’.

It is also necessary to restart the BI Publisher Managed Server.

 

[oracle@houoemap2 bin]$ ./emctl stop oms –all

 

Oracle Enterprise Manager Cloud Control 13c Release 2

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

Stopping Oracle Management Server…

WebTier Successfully Stopped

Oracle Management Server Already Stopped

Oracle Management Server is Down

JVMD Engine is Down

Stopping BI Publisher Server…

BI Publisher Server Already Stopped

AdminServer Failed to be Stopped

Check Admin Server log file for details: /app/oracle/product/middleware/gc_inst1/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out

BI Publisher Server is Down

[oracle@houoemap2 bin]$ vi /app/oracle/product/middleware/gc_inst1/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out

[oracle@houoemap2 bin]$ cp /app/oracle/product/middleware/gc_inst1/user_projects/domains/GCDomain/servers/EMGC_ADMINSERVER/logs/EMGC_ADMINSERVER.out /tmp/EMGC_ADMINSERVER.out

[oracle@houoemap2 bin]$ chmod -R 775 /tmp/EMGC_ADMINSERVER.out

[oracle@houoemap2 bin]$ ./emctl start oms

Oracle Enterprise Manager Cloud Control 13c Release 2

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

Starting Oracle Management Server…

WebTier Successfully Started

Oracle Management Server Successfully Started

Oracle Management Server is Up

JVMD Engine is Up

Starting BI Publisher Server …

BI Publisher Server Successfully Started

BI Publisher Server is Up

[oracle@houoemap2 bin]$

 

 

Step 13: Secure OMS on the new target server.  [houoemap2]

 

Run the below mentioned command and secure the OSM, provide the SYSMAN password and AGENT REGISTRATION PASSWORD when prompted.

 

[oracle@houoemap2 bin]$ pwd

/app/oracle/product/middleware/middleware13c/bin

[oracle@houoemap2 bin]$ ./emctl secure oms

 

Oracle Enterprise Manager Cloud Control 13c Release 2

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

Securing OMS… Started.

Enter Enterprise Manager Root (SYSMAN) Password :

 

Enter Agent Registration Password :

 

Securing OMS… Successful

Restart OMS

[oracle@houoemap2 bin]$

 

You need to re-start the OMS after you have ran the above command.

Step 14: Configure Agent on the OMS host. [TARGET HOST “HOUOEMAP2”]

 

OEM agent is installed by default when you did the software only installation of OEM13c on the target machine but now you need to configure this agent for new OMS now. Use the below mentioned command to configure the agent.

 

 [oracle@houoemap2 install]$ pwd

/app/oracle/product/agent12cr3/agent_13.2.0.0.0/sysman/install

 

[oracle@houoemap2 install]$ ./agentDeploy.sh AGENT_BASE_DIR=/app/oracle/product/agent12cr3/ AGENT_INSTANCE_HOME=/app/oracle/product/agent12cr3/agent_inst ORACLE_HOSTNAME=houoemap2.dksharma.com AGENT_PORT=3872 -configOnly OMS_HOST=houoemap2.dksharma.com EM_UPLOAD_PORT=4903 AGENT_REGISTRATION_PASSWORD=formula123

Validating the OMS Host and Port completed.

AGENT_BASE_DIR=/app/oracle/product/agent12cr3

AGENT_INSTANCE_HOME=/app/oracle/product/agent12cr3/agent_inst

AGENT_PORT=3872

-configOnly

OMS_HOST=houoemap2.dksharma.com

EM_UPLOAD_PORT=4903

AGENT_REGISTRATION_PASSWORD=formula123

/app/oracle/product/agent12cr3/agent_13.2.0.0.0/oracle_common/jdk/jre/bin/java -classpath /app/oracle/product/agent12cr3/agent_13.2.0.0.0/oui/modules/OraInstaller.jar:/app/oracle/product/agent12cr3/agent_13.2.0.0.0/oui/modules/emCfg.jar:/app/oracle/product/agent12cr3/agent_13.2.0.0.0/jlib/agentInstaller.jar oracle.sysman.agent.installer.AgentFreshInstaller /app/oracle/product/agent12cr3/agent_13.2.0.0.0 /app/oracle/product/agent12cr3/agent_inst /app/oracle/product/agent12cr3 RESPONSE_FILE=/app/oracle/product/agent12cr3/agentInstall.rsp  $args

The AgentFreshInstaller is starting now

Oraclehome : ../app/oracle/product/agent12cr3/agent_13.2.0.0.0

InstanceHome : /app/oracle/product/agent12cr3/agent_inst

Agent Base Directory : /app/oracle/product/agent12cr3

The oraclehome /app/oracle/product/agent12cr3/agent_13.2.0.0.0

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: /app/oracle/product/agent12cr3/agent_13.2.0.0.0

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: /app/oracle/product/agent12cr3/agent_inst

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: /app/oracle/product/agent12cr3

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: RESPONSE_FILE=/app/oracle/product/agent12cr3/agentInstall.rsp

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: AGENT_BASE_DIR=/app/oracle/product/agent12cr3/

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: AGENT_INSTANCE_HOME=/app/oracle/product/agent12cr3/agent_inst

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: ORACLE_HOSTNAME=houoemap2.dksharma.com

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: AGENT_PORT=3872

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: -configOnly

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: OMS_HOST=houoemap2.dksharma.com

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: EM_UPLOAD_PORT=4903

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: ORACLE_HOME=/app/oracle/product/agent12cr3/agent_13.2.0.0.0

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: AGENT_PORT=3872

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: EM_UPLOAD_PORT=4903

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: OMS_HOST=houoemap2.dksharma.com

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: AGENT_INSTANCE_HOME=/app/oracle/product/agent12cr3/agent_inst

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: AGENT_BASE_DIR=/app/oracle/product/agent12cr3

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: b_doDiscovery=true

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: START_AGENT=true

startAgent is:true

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: b_forceConfigure=false

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: b_sharedAgents=false

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: b_secureAgent=true

seci is :true

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: b_noUpgrade=true

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: b_agentupgrade=false

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: PLUGIN_RSPFILE=/app/oracle/product/agent12cr3/agent_13.2.0.0.0/sysman/install/plugins.txt

Feb 27, 2017 5:10:13 AM oracle.sysman.agent.installer.AgentInstaller parseResponseFile

INFO: ORACLE_HOSTNAME=houoemap2.dksharma.com

Writing the following contents into /app/oracle/product/agent12cr3/agent_13.2.0.0.0/install/oragchomelist

/app/oracle/product/agent12cr3/agent_13.2.0.0.0:/app/oracle/product/agent12cr3/agent_inst

Creating directory /app/oracle/product/agent12cr3/agent_13.2.0.0.0/install/tmp completed successfully.

File /etc/oragchomelist exists.

File /etc/oragchomelist is writable.

Index :-1 for line : /app/oracle/product/middleware/middleware13c

Index :0 for line : /app/oracle/product/agent12cr3/agent_13.2.0.0.0:/app/oracle/product/agent12cr3/agent_inst

Overwriting the contents since oracle home:/app/oracle/product/agent12cr3/agent_13.2.0.0.0 entry already exists.

The value of chainInstall : false forceConfigure : false skipValidation : false

Validating oms host & port with url: https://houoemap2.dksharma.com:4903/empbs/genwallet

Validating oms host & port with url: http://houoemap2.dksharma.com:4903/empbs/genwallet

The status is 0

Validated the oms host and port :- houoemap2.dksharma.com—-4903

Getting Inet Addresses for host houoemap2.dksharma.com

** Agent Port Check completed successfully.**

Validated the agent port :- —-3872

shared agent value is :false

Agent Mode is None

Agent Configuration completed successfully

The following configuration scripts need to be executed as the “root” user. Root script to run : /app/oracle/product/agent12cr3/agent_13.2.0.0.0/root.sh

Waiting for agent targets to get promoted…

Successfully Promoted agent and its related targets to Management Agent

[oracle@houoemap2 install]$ pwd

/app/oracle/product/agent12cr3/agent_13.2.0.0.0/sysman/install

 

Step 15: Check Status of Agent on target host [houoemap2]

 

[oracle@houoemap2 install]$ cd  ../../../agent_inst/bin/

[oracle@houoemap2 bin]$ ./emctl status agent

Oracle Enterprise Manager Cloud Control 13c Release 2

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

—————————————————————

Agent Version          : 13.2.0.0.0

OMS Version            : 13.2.0.0.0

Protocol Version       : 12.1.0.1.0

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

Agent Log Directory    : /app/oracle/product/agent12cr3/agent_inst/sysman/log

Agent Binaries         : /app/oracle/product/agent12cr3/agent_13.2.0.0.0

Core JAR Location      : /app/oracle/product/agent12cr3/agent_13.2.0.0.0/jlib

Agent Process ID       : 29038

Parent Process ID      : 28972

Agent URL              : https://houoemap2.dksharma.com:3872/emd/main/

Local Agent URL in NAT : https://houoemap2.dksharma.com:3872/emd/main/

Repository URL         : https://houoemap2.dksharma.com:4903/empbs/upload

Started at             : 2017-02-27 05:12:11

Started by user        : oracle

Operating System       : Linux version 3.10.0-327.22.2.el7.x86_64 (amd64)

Number of Targets      : 8

Last Reload            : (none)

Last successful upload                       : 2017-02-27 05:15:45

Last attempted upload                        : 2017-02-27 05:15:45

Total Megabytes of XML files uploaded so far : 0.38

Number of XML files pending upload           : 2

Size of XML files pending upload(MB)         : 0.08

Available disk space on upload filesystem    : 65.45%

Collection Status                            : Collections enabled

Heartbeat Status                             : Ok

Last attempted heartbeat to OMS              : 2017-02-27 05:15:17

Last successful heartbeat to OMS             : 2017-02-27 05:15:17

Next scheduled heartbeat to OMS              : 2017-02-27 05:16:17

—————————————————————

Agent is running and Ready

Step 16: Upload metric data and Ping OMS to verify agent is working fine.

 

[oracle@houoemap2 bin]$ ./emctl upload agent

Oracle Enterprise Manager Cloud Control 13c Release 2

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

—————————————————————

EMD upload completed successfully

 

[oracle@houoemap2 bin]$ ./emctl pingOMS

Oracle Enterprise Manager Cloud Control 13c Release 2

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

—————————————————————

EMD pingOMS completed successfully

Step 17: Verify status to check data has been uploaded.

 

[oracle@houoemap2 bin]$ ./emctl status agent

Oracle Enterprise Manager Cloud Control 13c Release 2

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

—————————————————————

Agent Version          : 13.2.0.0.0

OMS Version            : 13.2.0.0.0

Protocol Version       : 12.1.0.1.0

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

Agent Log Directory    : /app/oracle/product/agent12cr3/agent_inst/sysman/log

Agent Binaries         : /app/oracle/product/agent12cr3/agent_13.2.0.0.0

Core JAR Location      : /app/oracle/product/agent12cr3/agent_13.2.0.0.0/jlib

Agent Process ID       : 29038

Parent Process ID      : 28972

Agent URL              : https://houoemap2.dksharma.com:3872/emd/main/

Local Agent URL in NAT : https://houoemap2.dksharma.com:3872/emd/main/

Repository URL         : https://houoemap2.dksharma.com:4903/empbs/upload

Started at             : 2017-02-27 05:12:11

Started by user        : oracle

Operating System       : Linux version 3.10.0-327.22.2.el7.x86_64 (amd64)

Number of Targets      : 13

Last Reload            : (none)

Last successful upload                       : 2017-02-27 05:27:33

Last attempted upload                        : 2017-02-27 05:27:33

Total Megabytes of XML files uploaded so far : 0.71

Number of XML files pending upload           : 0

Size of XML files pending upload(MB)         : 0

Available disk space on upload filesystem    : 65.42%

Collection Status                            : Collections enabled

Heartbeat Status                             : Ok

Last attempted heartbeat to OMS              : 2017-02-27 05:28:17

Last successful heartbeat to OMS             : 2017-02-27 05:28:17

Next scheduled heartbeat to OMS              : 2017-02-27 05:29:17

 

—————————————————————

Agent is Running and Ready

Step 18: Verify all the targets on new host are detected by Agent [Houoemap2]

 

[oracle@houoemap2 bin]$ ./emctl config agent listtargets

Oracle Enterprise Manager Cloud Control 13c Release 2

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

[houoemap2.dksharma.com, host]

[houoemap2.dksharma.com:3872, oracle_emd]

[houoemap2.dksharma.com:4889_Management_Service, oracle_oms]

[houoemap2.dksharma.com:4889_Management_Service_CONSOLE, oracle_oms_console]

[houoemap2.dksharma.com:4889_Management_Service_PBS, oracle_oms_pbs]

[agent13c1_3_houoemap2.dksharma.com_1475, oracle_home]

[oms13c1_2_houoemap2.dksharma.com_3222, oracle_home]

[houoemap2.dksharma.com/server_os, oracle_si_server_os]

[OEMTST_1, oracle_database]

[LISTENER_houoemap2.dksharma.com, oracle_listener]

[OraDB12Home1_1_houoemap2.dksharma.com_306, oracle_home]

[Management Services and Repository, oracle_emrep]

[EM Management Beacon, oracle_beacon]

[oracle@houoemap2 bin]$ pwd

/app/oracle/product/agent12cr3/agent_inst/bin

[oracle@houoemap2 bin]$

[oracle@houoemap2 bin]$

 

Step 19: Re-configure master agent with management repository on HOUOEMAP2.

 

[oracle@houoemap2 install]$ cd –

/app/oracle/product/middleware/middleware13c/bin

[oracle@houoemap2 bin]$ ./emcli login -username=sysman

Enter password

 

Login successful

[oracle@houoemap2 bin]$ ./emcli sync

Synchronized successfully

 

[oracle@houoemap2 bin]$ ./emctl config emrep -agent houoemap2.dksharma.com:3872

Oracle Enterprise Manager Cloud Control 13c Release 2

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

Please enter repository password:                                                                                 Enter password :                                               Login successful

Moved all targets from houoemap1.dksharma.com:3872 to houoemap2.dksharma.com:3872

Command completed successfully!                                                                                   Enter password :                                               Login successful

Moved all targets from houoemap1.dksharma.com:3872 to houoemap2.dksharma.com:3872

Command completed successfully!

[oracle@houoemap2 bin]$

 

Step to be executed on other agents as target in OEM

 

(EMPTY) (~)

oracle@houpsdb2 $ cd /app/oracle/product/agent13c/agent_inst/bin/

 

(EMPTY) (/app/oracle/product/agent13c/agent_inst/bin)

oracle@houpsdb2 $ ./emctl status agent

Oracle Enterprise Manager Cloud Control 13c Release 2

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

—————————————————————

Agent Version          : 13.2.0.0.0

OMS Version            : 13.2.0.0.0

Protocol Version       : 12.1.0.1.0

Agent Home             : /app/oracle/product/agent13c/agent_inst

Agent Log Directory    : /app/oracle/product/agent13c/agent_inst/sysman/log

Agent Binaries         : /app/oracle/product/agent13c/agent_13.2.0.0.0

Core JAR Location      : /app/oracle/product/agent13c/agent_13.2.0.0.0/jlib

Agent Process ID       : 75397

Parent Process ID      : 75293

Agent URL              : https://houpsdb2.dksharma.com:1830/emd/main/

Local Agent URL in NAT : https://houpsdb2.dksharma.com:1830/emd/main/

Repository URL         : https://houoemap1.dksharma.com:4903/empbs/upload

Started at             : 2017-02-24 10:41:32

Started by user        : oracle

Operating System       : Linux version 3.10.0-514.6.1.el7.x86_64 (amd64)

Number of Targets      : 27

Last Reload            : (none)

Last successful upload                       : 2017-02-24 12:45:11

Last attempted upload                        : 2017-02-27 05:51:42

Total Megabytes of XML files uploaded so far : 0.82

Number of XML files pending upload           : 2,600

Size of XML files pending upload(MB)         : 16.1

Available disk space on upload filesystem    : 37.46%

Collection Status                            : Collections enabled

Heartbeat Status                             : OMS is unreachable

Last attempted heartbeat to OMS              : 2017-02-27 05:52:31

Last successful heartbeat to OMS             : 2017-02-24 12:46:43

Next scheduled heartbeat to OMS              : 2017-02-27 05:53:01

 

—————————————————————

Agent is Running and Ready

 

(EMPTY) (/app/oracle/product/agent13c/agent_inst/bin)

oracle@houpsdb2 $ ./emctl secure agent -emdWalletSrcUrl https://houoemap2.dksharma.com:4903/em

Oracle Enterprise Manager Cloud Control 13c Release 2

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

Agent successfully stopped…   Done.

Securing agent…   Started.

Enter Agent Registration Password :

Agent successfully restarted…   Done.

Securing agent…   Successful.

 

(EMPTY) (/app/oracle/product/agent13c/agent_inst/bin)

oracle@houpsdb2 $ ./emctl status agent

Oracle Enterprise Manager Cloud Control 13c Release 2

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

—————————————————————

Agent Version          : 13.2.0.0.0

OMS Version            : 13.2.0.0.0

Protocol Version       : 12.1.0.1.0

Agent Home             : /app/oracle/product/agent13c/agent_inst

Agent Log Directory    : /app/oracle/product/agent13c/agent_inst/sysman/log

Agent Binaries         : /app/oracle/product/agent13c/agent_13.2.0.0.0

Core JAR Location      : /app/oracle/product/agent13c/agent_13.2.0.0.0/jlib

Agent Process ID       : 98478

Parent Process ID      : 98296

Agent URL              : https://houpsdb2.dksharma.com:1830/emd/main/

Local Agent URL in NAT : https://houpsdb2.dksharma.com:1830/emd/main/

Repository URL         : https://houoemap2.dksharma.com:4903/empbs/upload

Started at             : 2017-02-27 05:55:02

Started by user        : oracle

Operating System       : Linux version 3.10.0-514.6.1.el7.x86_64 (amd64)

Number of Targets      : 27

Last Reload            : (none)

Last successful upload                       : 2017-02-27 05:55:31

Last attempted upload                        : 2017-02-27 05:55:31

Total Megabytes of XML files uploaded so far : 0.87

Number of XML files pending upload           : 2,082

Size of XML files pending upload(MB)         : 15.58

Available disk space on upload filesystem    : 37.47%

Collection Status                            : Collections enabled

Heartbeat Status                             : Ok

Last attempted heartbeat to OMS              : 2017-02-27 05:55:13

Last successful heartbeat to OMS             : 2017-02-27 05:55:13

Next scheduled heartbeat to OMS              : 2017-02-27 05:56:14

 

—————————————————————

Agent is Running and Ready

 

(EMPTY) (/app/oracle/product/agent13c/agent_inst/bin)

oracle@houpsdb2 $ ./emctl upload

References

The Repository Database can be migrated before OMS migration or after OMS migration.

Please follow the below doc to perform the Repository Database migration. [21.6.2.3 Full Recovery on a Different Host]

https://docs.oracle.com/cd/E73210_01/EMADV/GUID-08F7F2DA-7439-4FA9-9727-B18D68B90D19.htm#EMADV10751 

Transfer OMS to another host (with change of ip and hostname)

Dosc – Backup and recovery EM [21.6.4.2 Single OMS, No SLB, OMS Restored on a Different Host]

 

https://docs.oracle.com/cd/E73210_01/EMADV/GUID-08F7F2DA-7439-4FA9-9727-B18D68B90D19.htm#EMADV10752

Regards

ADDKS

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

image0

clip_image002

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

image0_1clip_image004

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.

image0_2clip_image006

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.

image2

Step 5: View Contents of Package

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

image3clip_image012

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.

image4clip_image014

 

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.

image5

image6clip_image016

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.

image7clip_image018

image8clip_image020

 

Stay connected for more stuff on OEM13c…

 

Thanks

ADDKS

Oracle Enterprise Manager Cloud Control 13c Release 2 (13.2.0.0) 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.

 

Thanks

ADDKS

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.

oem13c_upgrade_checklist

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.

Regards

ADDKS

 

 

Say Hello! to Oracle Enterprise Manager 13c

In this blog I have shared one of my recent presentations with you on “Introduction to new features in OEM13c”. I delivered this session in one of our Tech-Day named as OTNYathra2016. It covers small Introduction of Oracle Enterprise Manager, Architecture of Enterprise Manager and What are all the components involved. As far as New & Enhanced features are concerned I have included “Infrastructure & Framework”,  “Enterprise Monitoring & Incident Management” and few “Database Management” features.
I have just started exploring this new release and will soon be posting more stuff on OEM13c.

 OEM13c_Intro_Blog

Thanks

Deepak Sharma

© 2017 ORACLE EM DBA

Theme by Anders NorenUp ↑