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.

Author: sharmadeepak345 (page 1 of 7)

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

Manage Partner Agent in Oracle Enterprise Manager using “emcli”

Recently I fixed Partner Agent issue for one of my production Target Agent, which had a partner agent assigned  but was on development server. This ideally should not be the case as partner agent plays a very important role in monitoring. When primary agent is unavailable, it is very important to pick correct Partner agent to make sure monitoring is not affected.

Partner Agent is an agent which in addition to performing its regular functions, also remotely monitors the status of its assigned Management Agent and its host. OMS automatically assigns Partner Agent using built-in algorithm.

Partner Agent can be changed anytime, by using emcli verbmanage_agent_partnership“.

Few common alerts from Partner Agent.

 “Partner Agent could not connect to Host. Host might be down“.

Host=HANTESTAP5.dksharma.com 
Target type=Host
Target name=
HANTESTAP5.dksharma.com 
Categories=Availability
Message=
Partner Agent could not connect to Host. Host might be down. Refer to MOS Note (Doc ID 2101383.1) for additional information if you see the alert for more than few minutes. 
Severity=Fatal
Event reported time=Sep 4, 2017 1:02:25 AM CDT
Target Lifecycle Status=Production
Line of Business=BI
Department=DBA
Operating System=Linux
Platform=x86_64
Associated Incident Id=
99071
Associated Incident Status=New
Associated Incident Owner=
Associated Incident Acknowledged By Owner=No
Associated Incident Priority=None
Associated Incident Escalation Level=0
Event Type=Target Availability
Event name=Status
Availability status=Down
Root Cause Analysis Status=Neither Cause Nor Symptom
Causal analysis result=Neither a cause nor a symptom
Rule Name=RuleSet for all Production Targets,Incident creation Rule for target down.
Rule Owner=DKSHARMA
Update Details:
Partner Agent could not connect to Host. Host might be down. Refer to MOS Note (Doc ID 2101383.1) for additional information if you see the alert for more than few minutes.

Warning: – Host Up (Monitored) – Detected by Partner Agent

Host=hanpap1.dksharma.com 
Target type=Host
Target name=
hanpap1.dksharma.com 
Incident creation time=Apr 9, 2017 12:52:22 AM CDT
Last updated time=Apr 9, 2017 3:05:00 AM CDT
Message=Host Up (Unmonitored) – Detected by Partner Agent 
Severity=Warning
Incident ID=90359
Event count=1
Incident Status=New
Escalated=No
Priority=None
Incident owner=DKSHARMA
Incident Acknowledged By Owner=Yes
Categories=Availability
Rule Name=RuleSet for all Production Targets, Acknowledgement Rule
Rule Owner=DKSHARMA
Root Cause Analysis Status=Neither Cause Nor Symptom
This incident has an event that is neither a cause nor a symptom.
Update Details:
Acknowledged by DKSHARMA

You can check the associated partner agent by either using SQL statement or from the Console.

select target_agent.target_name "Target Agent", 
partner_agent.target_name "Partner Agent"
from 
EM_AGENT_BUDDY_MAP eabm, 
mgmt_targets target_agent, 
mgmt_targets partner_agent 
where 
eabm.buddy_target_guid = partner_agent.target_guid and
eabm.agent_target_guid = target_agent.target_guid and
target_agent.target_name = 'mention_agent_name';

 

Steps to change Partner Agent for any of the Target Agent.

Step 1:  Log into Enterprise Manager Command Line Interface “emcli”.

Step 2:  Run emcli sync.

Step 3: Crosscheck and Remove the old partnership.

$ ./emcli manage_agent_partnership –remove_agent_partnership -monitored_agent= hanproddb1.dksharma.com:3872 -partner_agent=hanprodap1.dksharma.com:3872
 $ Manage Agent Partnership operation completed successfully

 

Step 4: Add a new partner agent

$ ./emcli manage_agent_partnership -add_agent_partnership -monitored_agent= hanproddb1.dksharma.com:3872 -partner_agent=hanprodap1.dksharma.com:3872
$ Manage Agent Partnership operation completed successfully

For more information on “emcli” verbs check: http://docs.oracle.com/cd/E24628_01/em.121/e17786/cli_verb_ref.htm#EMCLI200

 

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

Error : TNS-4404: File error caused by: TNS-04605: Invalid syntax error

Yesterday itself I came across this error when I was creating a new database for “Always On Monitoring” for my OEM13c production environment.

The error message was simple enough to understand that there was some syntax problem in my “tnsnames.ora” file which caused this Error message to pop-up before DBCA can start its cloning process.

 

As mentioned in the error message the database name “ENGTST”, and it says that an unexpected char or LITERAL before or at ENGTST.  So it became easy for me to troubleshoot.  I search for the entry in tnsnames.ora file and found that there was an extra space in the very beginning. After removing that extra space, I re-ran the process and it did not fail again at the same step.

Very small issue yet, I came across it for the first time to thought to share it with everyone.

Other possibility for error “TNS-04404” can also be

  • Running the Network Configuration Assistant (NETCA) on the database server, to modify the Local Service Name settings that are stored within the TNSNAMES.ORA configuration file.

Usually if you receive this error, the particular TNS entry that is problematic will be always indicated in the error message. Example in my scenario the “ENGTST” was the problematic entry.

To solve this error, make the necessary changes in the “tnsnames.ora” file and you should be good to go.

Thanks

Deepak

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

Host Monitoring using Oracle Enterprise Manager 13c [Webinar]

In this blog I have shared the recent webinar which I did for “AIOUG-North India Chapter“. This webinar is related to the “Host Monitoring” using 13c Cloud Control. More details about this session is mentioned below. In-case you have missed it, you can watch the recorded session on YouTube Page of “AIOUG-North India Chapter”.

Session Details:-

Abstract: In this session we will learn how effectively you can monitor servers/hosts in your organization through new “Oracle Enterprise Manager 13c Cloud Control”. Some New features which were missing in previous release 12c Cloud Control.

Profile: Deepak Sharma is working as Sr. Application Administrator I, with experience of 7+ years. He has worked on technologies like Oracle Enterprise Manager 11g Grid Contol, Oracle Enterprise Manager 12c Cloud Control, Oracle Enterprise Manager 13c, Oracle Database, Oracle Configuration Manager and Sql Server. He is currently working with “Oceaneering International Inc.” from last 5 years and before that he has been employee of “Bebo Technologies” for 2 years. He is Co-Founder of AIOUG-North India Chapter and core team member of AIOUG.

Webinar URL: https://www.youtube.com/watch?v=58s_Mf-k7m0

Demo URL: https://www.youtube.com/watch?v=ECNOpfQTCn8

 

AIOUG NI Chapter-Over The WWW

Youtube: https://www.youtube.com/user/aiougnic

Official Website: http://www.aioug.org/NorthIndiaChapter.php

Facebook: https://www.facebook.com/AIOUG.NIC

Twitter: https://twitter.com/nichapter_aioug

Blog: https://aiougnic.wordpress.com/

Google+ : https://plus.google.com/+AIOUGNorthIndiaChapter/

Do subscribe to our pages for regular updates.

Thanks

ADDKS

Step by Step document to Apply PSU to OEM12c

In this document I have mentioned the step by step process which you have to follow in order to apply PSU to OEM12c. The example shown in this document is for OEM12cR4 which is my current environment. I have documented this process as the step involved are slightly different that normal steps for database patching, OMS patching involves some additional steps.

 

Step 1: Check OMS Details as it will be needed in later steps.

Download the latest PSU from Oracle Support and move it to OEM Server.

Step 2: Check OMS Details as it will be needed in later steps.

[oracle@hanoemap1 bin]$ ./emctl status oms -details

Oracle Enterprise Manager Cloud Control 12c Release 4

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

Enter Enterprise Manager Root (SYSMAN) Password :

Console Server Host : hanoemap1.emdeepaksharma.com

HTTP Console Port : 7790

HTTPS Console Port : 7803

HTTP Upload Port : 4890

HTTPS Upload Port : 4904

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

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

OMS is not configured with SLB or virtual hostname

Agent Upload is unlocked.

OMS Console is unlocked.

Active CA ID: 1

Console URL: https://hanoemap1.emdeepaksharma.com:7803/em

Upload URL: https://hanoemap1.emdeepaksharma.com:4904/empbs/upload

 

WLS Domain Information

Domain Name : GCDomain

Admin Server Host : hanoemap1.emdeepaksharma.com

Admin Server HTTPS Port: 7103

Admin Server is RUNNING

 

Oracle Management Server Information

Managed Server Instance Name: EMGC_OMS1

Oracle Management Server Instance Host: hanoemap1.emdeepaksharma.com

WebTier is Up

Oracle Management Server is Up

 

BI Publisher Server is Up

BI Publisher Server named ‘BIP’ running at local URL: https://hanoemap1.emdeepaksharma.com:7803/xmlpserver

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

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

[oracle@hanoemap1 bin]$

 

Step 3: WebLogic encrypted configuration and key files.

Create directory to store property file.

[oracle@hanoemap1 ~]$ cd /app/oracle/product/middleware/oms12cr4/oms/

[oracle@hanoemap1 oms]$ mkdir -p oms_encr

Run the following script to create the WebLogic encrypted configuration and key files.

<OMS_HOME>/OPatch/wlskeys/createkeys.sh –oh <full path of platform OMS Oracle Home> -location <location to put the encrypted files>

[oracle@hanoemap1 bin]$ cd /app/oracle/product/middleware/oms12cr4/oms/OPatch/wlskeys

[oracle@hanoemap1 wlskeys]$ ./createkeys.sh -oh /app/oracle/product/middleware/oms12cr4/oms -location /app/oracle/product/middleware/oms12cr4/oms/oms_encr

Please enter weblogic admin server username: weblogic

Please enter weblogic admin server password: formula1

Creating the key file can reduce the security of your system if it is not kept in a secured location after it is created. Creating new key…

Trying to get configuration and key files for the given inputs…

This operation will take some time. Please wait for updates…

User configuration file created: /app/oracle/product/middleware/oms12cr4/oms/oms_encr/config

User key file created: /app/oracle/product/middleware/oms12cr4/oms/oms_encr/key

‘createKeys’ succeeded.

[oracle@hanoemap1 wlskeys]$

Step 4: Create the property file with the following entries:

Enter the details of the WebLogic Administrator Server URL retrieved in STEP 1

WLS Domain Information

Domain Name : GCDomain

Admin Server Host : hanoemap1.emdeepaksharma.com

Admin Server HTTPS Port: 7103

Admin Server is RUNNING

 

The output displayed contains the WebLogic Adminstrator Server details. Here is an example on how to construct the URL with these output details. Property file should contain below mentioned information and should look similar to the following once completed:

AdminServerURL=t3s://<host address from where admin server is running>:<port of the admin server>

AdminConfigFile=<‘config’ file location>

AdminKeyFile=<‘key’ file location>

 

Following is the example of how a property file (constructed by the above mentioned guidelines) should appear:

AdminServerURL= https://hanoemap1.emdeepaksharma.com:7103

AdminConfigFile=/app/oracle/product/middleware/oms12cr4/oms/oms_encr/config

AdminKeyFile=/app/oracle/product/middleware/oms12cr4/oms/oms_encr/key

 

Create directory for property file followed by creation of text file as mentioned below

mkdir –p  /app/oracle/product/middleware/property_file

cd /app/oracle/product/middleware/property_file

vi property_file.txt

 

Add below mentioned entries in “property_file.txt”

AdminServerURL= https://hanoemap1.emdeepaksharma.com:7103

AdminConfigFile=/app/oracle/product/middleware/oms12cr4/oms/oms_encr/config

AdminKeyFile=/app/oracle/product/middleware/oms12cr4/oms/oms_encr/key

 

Step 5: Analyze the PSU

Make sure you have the latest OPatch for your OMS. The analyze process will fail with error if the OPatch is not latest.

Run the following command on OMS instance home to ensure that you do not have any issues with configuration and binary prerequisite checks. Please note: the OMS should be online when you do this step only.

export ORACLE_HOME=$OMS_HOME

export PATH=$ORACLE_HOME/OPatch:$ORACLE_HOME/bin:$PATH:

Navigate to the patch folder and analyze the patch.

[oracle@hanoemap1 middlware]$  cd /app/oracle/product/middleware/oms12cr4/oms/22132672

While Installing the System patch

$ opatchauto apply -analyze  [–property_file <location of property file>]

[oracle@hanoemap1 22132672]$$ opatchauto apply -analyze -property_file “/app/oracle/product/middleware/property_file/property_file.txt”

[oracle@hanoemap1 22132672]$ opatchauto apply -analyze -property_file /app/oracle/product/middleware/property_file/property_file.txt -invPtrLoc /app/oracle/product/middleware/oms12cr4/oms/oraInst.loc  OPatchAuto.OMS_DISABLE_HOST_CHECK=true

 

OPatch Automation Tool

Copyright (c) 2014, Oracle Corporation.  All rights reserved.

OPatchauto version : 11.1.0.12.9

OUI version        : 11.1.0.12.0

Running from       : /app/oracle/product/middleware/oms12cr4/oms

Log file location  : /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/opatch2017-01-20_16-45-34PM_1.log

OPatchauto log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatchauto/22132672/opatch_oms_2017-01-20_16-45-36PM_analyze.log

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) “22132672” and Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”…

Please monitor OPatch log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/22132672_Jan_20_2017_16_45_34/ApplyPrereq2017-01-20_16-46-55PM_2.log

Sub-patch(es) “22132672” are successfully analyzed for Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”

Complete Summary

================

All log file names referenced below can be accessed from the directory “/app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/2017-01-20_16-45-34PM_SystemPatch_22132672_1”

Prerequisites analysis summary:

——————————-

The following sub-patch(es) are applicable:

  Oracle Home Name   Sub-patches                                     Log file

  —————- ——–  ———–                                          ——–

           oms12c3            22132672                                         22132672_ApplyPrereq2017-01-20_16-46-55PM_2.log

Log file location: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatchauto/22132672/opatch_oms_2017-01-20_16-45-36PM_analyze.log

OPatchauto succeeded.

[oracle@hanoemap1 22132672]$

 

Step 6: On Successful analysis, Apply PSU. If not, address the errors, then proceed with next steps.

Stop OMS

[oracle@hanoemap1 22132672]$ emctl stop oms

Oracle Enterprise Manager Cloud Control 12c Release 4

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

Stopping WebTier…

WebTier Successfully Stopped

Stopping Oracle Management Server…

Oracle Management Server Successfully Stopped

Oracle Management Server is Down

 

Apply Patch

[oracle@hanoemap1 22132672]$ opatchauto apply -property_file /app/oracle/product/middleware/property_file/property_file.txt

 

OPatch Automation Tool

Copyright (c) 2014, Oracle Corporation. All rights reserved.

OPatchauto version : 11.1.0.12.9

OUI version : 11.1.0.12.0

Running from : /app/oracle/product/middleware/oms12cr4/oms

Log file location : /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/opatch2017-01-20_17-04-10PM_1.log

OPatchauto log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatchauto/22132672/opatch_oms_2017-01-20_17-04-11PM_deploy.log

Configuration Validation: Success

Running apply prerequisite checks for sub-patch(es) “22132672” and Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”…

Please monitor OPatch log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/22132672_Jan_20_2017_17_04_10/ApplyPrereq2017-01-20_17-05-37PM_2.log

Sub-patch(es) “22132672” are successfully analyzed for Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”

To continue, OPatchauto will do the following:

[Patch and deploy artifacts] : Apply sub-patch(es) [ 22132672 ] to Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”;

Apply RCU artifact with patch “/app/oracle/product/middleware/oms12cr4/oms/.patch_storage/22132672_Dec_16_2015_23_31_36/original_patch”;

Register MRS artifact “omsPropertyDef”;

Register MRS artifact “procedures”

Do you want to proceed? [y|n]

y

User Responded with: Y

Applying sub-patch “22132672” to Oracle Home “/app/oracle/product/middleware/oms12cr4/oms”…

Please monitor OPatch log file: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/22132672_Jan_20_2017_17_04_10/apply2017-01-20_17-07-53PM_4.log

Updating repository with RCU reference file “/app/oracle/product/middleware/oms12cr4/oms/.patch_storage/22132672_Dec_16_2015_23_31_36/original_patch”

Registering service “omsPropertyDef” with register file “/app/oracle/product/middleware/oms12cr4/oms/sysman/metadata/omsProperties/definition/BIPHAPropDefinition.xml”…

Registering service “procedures” with register file “/app/oracle/product/middleware/oms12cr4/oms/sysman/metadata/procedures/linuxpatch/PatchLinux.xml”…

Registering service “procedures” with register file “/app/oracle/product/middleware/oms12cr4/oms/sysman/metadata/procedures/linuxpatch/ULNPatchLinux.xml”…

 

Complete Summary

================

All log file names referenced below can be accessed from the directory “/app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/2017-01-20_17-04-10PM_SystemPatch_22132672_1”

Patching summary:

—————–

Binaries of the following sub-patch(es) have been applied successfully:

Oracle Home Name Sub-patches Log file

—————- ———– ——–

oms12c3 22132672 22132672_apply2017-01-20_17-07-53PM_4.log

Deployment summary:

——————-

The following artifact(s) have been successfully deployed:

Artifacts Log file

——— ——–

SQL rcu_applypatch_original_patch_2017-01-20_17-08-57PM.log

MRS-omsPropertyDef emctl_register_omsPropertyDef_2017-01-20_17-10-38PM.log

MRS-procedures emctl_register_procedures_2017-01-20_17-10-43PM.log

MRS-procedures emctl_register_procedures_2017-01-20_17-10-48PM.log

Log file location: /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatchauto/22132672/opatch_oms_2017-01-20_17-04-11PM_deploy.log

OPatchauto succeeded.

 

Start OMS

[oracle@hanoemap1 22132672]$ emctl start oms

Oracle Enterprise Manager Cloud Control 12c Release 4

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

Starting Oracle Management Server…

Starting WebTier…

WebTier Successfully Started

Oracle Management Server Successfully Started

Oracle Management Server is Up

Starting BI Publisher Server …

BI Publisher Server Already Started

BI Publisher Server is Up

[oracle@hanoemap1 22132672]$

 

Step 7: Verify Applied Patches

 

[oracle@hanoemap1 22132672]$ opatch lsinventory

Oracle Interim Patch Installer version 11.1.0.12.9

Copyright (c) 2017, Oracle Corporation. All rights reserved.

Oracle Home : /app/oracle/product/middleware/oms12cr4/oms

Central Inventory : /app/oracle/oraInventory

from : /app/oracle/product/middleware/oms12cr4/oms/oraInst.loc

OPatch version : 11.1.0.12.9

OUI version : 11.1.0.12.0

Log file location : /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/opatch2017-01-20_18-29-52PM_1.log

OPatch detects the Middleware Home as “/app/oracle/product/middleware/oms12cr4”

Lsinventory Output file location : /app/oracle/product/middleware/oms12cr4/oms/cfgtoollogs/opatch/lsinv/lsinventory2017-01-20_18-29-52PM.txt

——————————————————————————–

Installed Top-level Products (1):

EM Platform (OMS) 12.1.0.4.0

There are 1 products installed in this Oracle Home.

Interim patches (1) :

Patch 22132672 : applied on Fri Jan 20 17:08:47 EST 2017

Unique Patch ID: 19559467

Patch description: “EMBP Patch Set Update 12.1.0.4.160119”

Created on 16 Dec 2015, 23:31:36 hrs PST8PDT

Bugs fixed:

20010360, 20346629, 18599481, 19459173, 20646440, 18830050, 18244680

19614772, 20492788, 18932882, 20646540, 19355307, 20263906, 20556489

20106145, 14301574, 18721562, 17714229, 19328391, 19535114, 19861538

19794113, 19604817, 20596437, 19892848, 19218456, 19978077, 18505219

17843191, 20345612, 20748748, 20024779, 18256983, 19329809, 19300103

17987955, 18351725, 18903783, 19430853, 19845101, 20870437, 20421152

20223681, 21437683, 20019184, 20263188, 19069940, 21545754, 19861412

19136663, 18446798, 19474685, 18765545, 18038059, 17783148, 19509780

20838602, 18041873, 19030447, 20861693, 20933667, 19574756, 19258481

18938561, 17812648, 20377474, 20251039, 19572261, 18945007, 20307428

18388324, 19500609, 20751948, 22324488, 17991694, 19137411, 20369347

19474929, 19592446, 18710124, 20536095, 21358443, 19352118, 19557054

18726708, 19595813, 19170861, 19685443, 18353162, 19289270, 19367214

18906451, 19458672, 20284029, 18490444, 19766881, 20021966, 18509136

20739088, 21450977, 18695961, 19511544, 19812966, 20093530, 20576148

20806405, 20623258, 19055251, 19586898, 20260177, 19323634, 21462217

19941819, 18725891, 19824587, 20672821, 19780847, 18359621, 21067380

19393211, 19211048, 20505155, 18476364, 18490468, 18247849, 19071602

19068674, 18490455, 19524568, 20616490, 19061168, 19077861, 20031287

18756725, 19281252, 21061986, 18977955, 18485889, 20695395, 18521731

18411036, 19775544, 18900197, 17834366, 20460507, 19545505, 21330117

19823996, 20645335, 20633770, 17407918, 18706824, 20568225, 18805935

19376082, 19146514, 21429472, 20985421, 18490432, 18230284, 19694744

18726208, 20044313, 18516298, 18391707, 20642633, 18999400, 20692416

19362386, 20392036, 21495795, 19452280, 20623344, 21093418, 22132672

18356966, 19055979, 20617058, 19830994, 20030493, 19823761, 18834216

19196979, 19785223, 18389542

——————————————————————————–

OPatch succeeded.

[oracle@hanoemap1 22132672]$

 

Hope this document will help you apply patches in your OEM12c environment.

 

Thanks

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

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.

Prerequisites

· 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 12.1.0.2 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

certification_matrix13cr2

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

certification_matrix13cr2_1

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=”12.1.0.2.0″ 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.

http://www.oracle.com/technetwork/oem/grid-control/downloads/oem-linux64-3237624.html

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.

image1

Step 6: Run the Setup and enter MOS Details.

image2

 

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.

image3

image4

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.

image5

 

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”.

image6

 

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.

image7

 

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.

image8

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.

image9

image10

 

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

image11

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”.

image12

 

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.

image13

 

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.

image14

 

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.

image15

 

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.

image16

 

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.

image17

image18

image19

image20

image21

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

image22

 

Step 20: Final & Final Details

image23

 

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.

13c_console

license

home_pagehome_page

 

Regards

ADDKS

Older posts

© 2017 ORACLE EM DBA

Theme by Anders NorenUp ↑