OEM 12c OMS backup options

Hi everyone, all the documentation I find seems to suggest that the only way to back up the OMS configuration is to use the "emctl exportconfig" command from the OMS server command line. This command requires knowledge of the SYSMAN password which I do not have. Is there any way to back up the configuration from the OEM 12c console instead of the command line? Is there a way to use a Named Credential for the SYSMAN password if needed?

There is currently no way to circumvent passing sysman_pwd as a command linre parameter to emctl. Even if you create a job for this, the EM admin granted access to submit the job would still be able to see the full command line. We may consider enhancements in a future release such as a job type specifically for exportconfig.

Similar Messages

  • OEM 12C OMS can't start after applied virtulization plug-in in the OMS

    HI,
    I just applied a virtualization plug-in in OEM 12C OMS,
    Unfortunately, it can’t start now after applied, how can I resolve this error?
    Any help is highly appreciated!!
    [oracle@emdb bin]$ ./emctl start oms
    Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
    Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
    Starting WebTier...
    WebTier Successfully Started
    Starting Oracle Management Server...
    Oracle Management Server Could Not Be Started
    Oracle Management Server is Down
    This may be due to the following plugin being deployed/undeployed on the management server:
    Plugin name: : Oracle Virtualization
    Version: : 12.1.0.1.0
    ID: : oracle.sysman.vt
    Use 'emctl status oms -details' for details.
    Please check /u01/app/mid/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log for error details
    [oracle@emdb bin]$ ./emctl status oms -details
    Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
    Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
    Enter Enterprise Manager Root (SYSMAN) Password :
    Console Server Host : emdb.bea.com
    HTTP Console Port : 7788
    HTTPS Console Port : 7799
    HTTP Upload Port : 4889
    HTTPS Upload Port : 4900
    OMS is not configured with SLB or virtual hostname
    Agent Upload is locked.
    OMS Console is locked.
    Active CA ID: 1
    Console URL: https://emdb.bea.com:7799/em
    Upload URL: https://emdb.bea.com:4900/empbs/upload
    WLS Domain Information
    Domain Name : GCDomain
    Admin Server Host: emdb.bea.com
    Managed Server Information
    Managed Server Instance Name: EMGC_OMS1
    Managed Server Instance Host: emdb.bea.com
    [oracle@emdb bin]$ tail -50 /u01/app/mid/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log
    2012-03-28 01:53:31,756 [main] DEBUG oms.StatusOMSCmd processStatusOMS.246 - pbs header is null
    2012-03-28 01:53:31,757 [main] INFO wls.OMSController statusOMS.1354 - statusOMS finished with result: 0
    2012-03-28 01:58:19,430 [main] DEBUG wls.OMSController main.199 - Log location is /u01/app/mid/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log
    2012-03-28 01:58:19,433 [main] INFO wls.OMSController printWebTierStatus.1453 - Checking status of WebTier. WebTier host: emdb.bea.com upload port: 4889
    2012-03-28 01:58:19,602 [main] DEBUG wls.OMSController printWebTierStatus.1464 - rspCode when accessing over webtier upload port: 200
    2012-03-28 01:58:19,604 [main] DEBUG oms.StatusOMSCmd processStatusOMS.158 - HTTP port in emgc property file: 7202
    2012-03-28 01:58:19,605 [main] DEBUG oms.StatusOMSCmd processStatusOMS.159 - HTTPS port in emgc property file: 7301
    2012-03-28 01:58:19,605 [main] DEBUG oms.StatusOMSCmd processStatusOMS.165 - Webtier HTTP port in emgc property file: 7788
    2012-03-28 01:58:19,605 [main] DEBUG oms.StatusOMSCmd processStatusOMS.166 - Webtier HTTPS port in emgc property file: 7799
    2012-03-28 01:58:19,606 [main] DEBUG oms.StatusOMSCmd processStatusOMS.185 - Using https port.
    2012-03-28 01:58:19,606 [main] DEBUG oms.StatusOMSCmd processStatusOMS.202 - Using webtier https port.
    2012-03-28 01:58:19,627 [main] DEBUG oms.StatusOMSCmd pingOMSCheck.332 - Attempting to connect to https://emdb.bea.com:7301/em/faces/logon/core-uifwk-console-login
    2012-03-28 01:58:20,176 [main] DEBUG oms.StatusOMSCmd pingOMSCheck.332 - Attempting to connect to https://emdb.bea.com:7799/empbs/check
    2012-03-28 01:58:20,202 [main] DEBUG oms.StatusOMSCmd processStatusOMS.239 - console page status code is 200
    2012-03-28 01:58:20,236 [main] DEBUG oms.StatusOMSCmd processStatusOMS.241 - pbs page status code is 200
    2012-03-28 01:58:20,237 [main] DEBUG oms.StatusOMSCmd processStatusOMS.244 - console header is null
    2012-03-28 01:58:20,237 [main] DEBUG oms.StatusOMSCmd processStatusOMS.246 - pbs header is null
    2012-03-28 01:58:20,237 [main] INFO wls.OMSController statusOMS.1354 - statusOMS finished with result: 0
    2012-03-28 01:58:22,986 [main] DEBUG wls.OMSController main.199 - Log location is /u01/app/mid/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log
    2012-03-28 01:58:22,991 [main] INFO wls.OMSController printWebTierStatus.1453 - Checking status of WebTier. WebTier host: emdb.bea.com upload port: 4889
    2012-03-28 01:58:23,173 [main] DEBUG wls.OMSController printWebTierStatus.1464 - rspCode when accessing over webtier upload port: 200
    2012-03-28 01:58:23,175 [main] DEBUG oms.StatusOMSCmd processStatusOMS.158 - HTTP port in emgc property file: 7202
    2012-03-28 01:58:23,176 [main] DEBUG oms.StatusOMSCmd processStatusOMS.159 - HTTPS port in emgc property file: 7301
    2012-03-28 01:58:23,176 [main] DEBUG oms.StatusOMSCmd processStatusOMS.165 - Webtier HTTP port in emgc property file: 7788
    2012-03-28 01:58:23,176 [main] DEBUG oms.StatusOMSCmd processStatusOMS.166 - Webtier HTTPS port in emgc property file: 7799
    2012-03-28 01:58:23,176 [main] DEBUG oms.StatusOMSCmd processStatusOMS.185 - Using https port.
    2012-03-28 01:58:23,177 [main] DEBUG oms.StatusOMSCmd processStatusOMS.202 - Using webtier https port.
    2012-03-28 01:58:23,205 [main] DEBUG oms.StatusOMSCmd pingOMSCheck.332 - Attempting to connect to https://emdb.bea.com:7301/em/faces/logon/core-uifwk-console-login
    2012-03-28 01:58:23,836 [main] DEBUG oms.StatusOMSCmd pingOMSCheck.332 - Attempting to connect to https://emdb.bea.com:7799/empbs/check
    2012-03-28 01:58:23,871 [main] DEBUG oms.StatusOMSCmd processStatusOMS.239 - console page status code is 200
    2012-03-28 01:58:23,872 [main] DEBUG oms.StatusOMSCmd processStatusOMS.241 - pbs page status code is 200
    2012-03-28 01:58:23,872 [main] DEBUG oms.StatusOMSCmd processStatusOMS.244 - console header is null
    2012-03-28 01:58:23,872 [main] DEBUG oms.StatusOMSCmd processStatusOMS.246 - pbs header is null
    2012-03-28 01:58:23,873 [main] INFO wls.OMSController statusOMS.1354 - statusOMS finished with result: 0
    2012-03-28 01:58:28,258 [main] DEBUG wls.OMSController main.199 - Log location is /u01/app/mid/gc_inst/em/EMGC_OMS1/sysman/log/emctl.log
    2012-03-28 01:58:28,263 [main] INFO wls.OMSController printWebTierStatus.1453 - Checking status of WebTier. WebTier host: emdb.bea.com upload port: 4889
    2012-03-28 01:58:28,463 [main] DEBUG wls.OMSController printWebTierStatus.1464 - rspCode when accessing over webtier upload port: 200
    2012-03-28 01:58:28,465 [main] DEBUG oms.StatusOMSCmd processStatusOMS.158 - HTTP port in emgc property file: 7202
    2012-03-28 01:58:28,466 [main] DEBUG oms.StatusOMSCmd processStatusOMS.159 - HTTPS port in emgc property file: 7301
    2012-03-28 01:58:28,466 [main] DEBUG oms.StatusOMSCmd processStatusOMS.165 - Webtier HTTP port in emgc property file: 7788
    2012-03-28 01:58:28,466 [main] DEBUG oms.StatusOMSCmd processStatusOMS.166 - Webtier HTTPS port in emgc property file: 7799
    2012-03-28 01:58:28,467 [main] DEBUG oms.StatusOMSCmd processStatusOMS.185 - Using https port.
    2012-03-28 01:58:28,468 [main] DEBUG oms.StatusOMSCmd processStatusOMS.202 - Using webtier https port.
    2012-03-28 01:58:28,490 [main] DEBUG oms.StatusOMSCmd pingOMSCheck.332 - Attempting to connect to https://emdb.bea.com:7301/em/faces/logon/core-uifwk-console-login
    2012-03-28 01:58:29,027 [main] DEBUG oms.StatusOMSCmd pingOMSCheck.332 - Attempting to connect to https://emdb.bea.com:7799/empbs/check
    2012-03-28 01:58:29,083 [main] DEBUG oms.StatusOMSCmd processStatusOMS.239 - console page status code is 200
    2012-03-28 01:58:29,083 [main] DEBUG oms.StatusOMSCmd processStatusOMS.241 - pbs page status code is 200
    2012-03-28 01:58:29,084 [main] DEBUG oms.StatusOMSCmd processStatusOMS.244 - console header is null
    2012-03-28 01:58:29,084 [main] DEBUG oms.StatusOMSCmd processStatusOMS.246 - pbs header is null
    2012-03-28 01:58:29,084 [main] INFO wls.OMSController statusOMS.1354 - statusOMS finished with result: 0
    [oracle@emdb bin]$

    what is your OMS platform? have you applied BP1?
    Can you open an SR and send mee thee SR number ?

  • After OEM 12c installation, how to install more plugins?

    I just finished up installation of oem 12c OMS, but forgot to pickup db2 and sql server db as plugins, how to add those in?
    are those plugs ins installed can be used to monitor db2 /sqlserver dbs?

    You can deploy any plugin post install as well. Read this for instructions : http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm#CHDBGHFE

  • Email RMAN backup logs in OEM 12c

    I am scheduling my RMAN daily backups via OEM 12c. My goal is that the email notification includes the full log, rather than just the status of results. I was able to do this in 11g fairly easily. I have created a ticket with Oracle, to which they have responded that this may not be possible with 12c. I find that hard to believe. I am probably missing something silly. Any help is greatly appreciated.

    Here is the response to your question. If its useful, please mark it so.
    https://oracletechnologistblog.wordpress.com/2012/08/27/tip-of-the-week-resolving-12c-cloud-control-database-backup-notification-issues/
    In 12c CC, after scheduling database backup job and configuring email notification, system doesn’t successfully email the status of the backup jobs. Email notification within 12c would work otherwise. Interestingly, the notification would not work just for database backup jobs.
    Steps to diagnose the issue:
    1.Please ensure your database target ‘yourdb’ in issue has been listed in the ‘Job Events For Targets’ by navigating to EM 12c -> Setup -> Incidents -> Job Events
    2.If the above doesn’t help, then please do:
    2.1 Log on the repository db of EM 12c as SYSMAN user to query the following then upload the output.html file for checking
    SQL>set markup html on spool on
    SQL>spool output.html
    SQL>select * from mgmt_targets where target_name=’PRD1′;
    SQL>select * from mgmt_notification_log;
    SQL>spool off
    2.2 Set EM 12c OMS to DEBUG level
    cd <OMS_HOME>/bin
    emctl set property -name log4j.rootCategory -value ‘DEBUG, emlogAppender, emtrcAppender’ -module logging
    2.3 Then reproduce this issue.
    If you find below errors in <gc_inst>/em/EMGC_OMS1/sysman/log/emoms.trc, then perform the below mentioned Resolution to resolve the issue.
    2012-08-23 17:05:51,519 [DeliveryThread-EMAIL6] WARN notification.pbs logp.251 – Delivery.run: java.util.MissingResourceException: Can’t find bundle for base name oracle.sysman.db.rsc.rec.BackupJobMsg, locale en_US
    java.util.MissingResourceException: Can’t find bundle for base name oracle.sysman.db.rsc.rec.BackupJobMsg, locale en_US
    Resolution:
    As per the uploaded file emoms_pbs.trc, it shows the exactly same error messages described in the bug 13334194.
    Apply the EM 12c BP1( per Doc ID 1430518.1) patch to resolve this issue, as it has included the fix of bug 13334194.
    Reference:
    Mandatory Enterprise Manager Cloud Control 12c Release 12.1.0.1 Bundle Patch 1 (BP1) for all available platforms (Doc ID 1430518.1)
    Document 1395505.1 – Announcing Enterprise Manager Cloud Control 12c Release 12.1.0.1 Bundle Patch 1(BP1) and 12.1.0.2 Plug-ins.
    EM 12c How to Configure Notifications for Job Executions? (Doc ID 1386816.1)

  • OEM 12c SLB - Easy way to tell which OMS

    Hello,
    We are using OEM 12c and followed the HA guidelines to setup an SLB. The SLB is working as desired for logins and agent uploads. However, it is trivial to tell which OMS you are logged into (in a multi OMS environment) when using the SLB. In 10g, we were able to solve this by manually editing a banner gif file to include the OMS server name so it was always trivial to tell - very useful for troubleshooting. In 12c, this does not seem to be possible as the UI is very flash oriented. Is there any file I can change / has any one found a trivial way to accomplish the same in 12c?
    I'll try and post a picture of what our 10g banner looked like if it helps.
    thanks,
    danny

    Hi Danny,
    An EM Administrator can see which OMS they are connected to by navigating to the Management Services and Repository homepage (Setup | Management Services and Repository).
    The OMS they are connected to will be shown as the 'Management Service in Use'.
    Does this help?
    Thanks, Mark.

  • OEM 12c: addition oms failing

    I have installed oms (OEM 12c) on primary node but adding oms to another node using the console is failing with the error below.
    The nodes are set up with F5 SLB, everything is working okay on  the primary node including SLB console etc.
    My environment is RHEL6 (6.4) - Linux  2.6.32-358.el6.x86_64.
    Step: Execute Command  (Failed)
    onfig.java:666)
    at oracle.sysman.omsca.framework.OMSConfigAssistantDriver.main(OMSConfigAssistantDriver.java:240)
    OMSCA-ERR:Bounce OMS failed.
    OMSCA-ERR:Post "Deploy and Repos Setup" operations failed. Check the trace file:/opt/oracle/app/oracle/product/WLS11.1.1.6.0/wlserver_11.1/oms/cfgtoollogs/omsca/omsca_20130611103651.log
    Add OMS failed
    OMS CA recover failed
    Error:Can not recover destination oms.
      at /tmp/JOB_DEE235C8B339251BE0432A43600AE89B/implConfigDestOMS.pl line 96, <STDIN> line 7.
    I will appreciate your assistance.

    We see following error in logs-
    2013-06-10 16:57:42,481 [EMMetadataServiceDriver:Thread-14] ERROR swlib.txfr - There was an exception while uploading file to fileset with guid=DED4DE838BED4F47E0432A43600A2D55 for path=ouiOnlyPrereqs.pl. Setting the file entry status to ERROR.
    oracle.sysman.emSDK.swlib.storage.StorageException: *The filesystem for the library is not correctly configured, or the directory /omsshare/3 could not be accessed.*
    Suspecting software library some files are all 0 bytes - this was caused due to a problem with the NFS mount-point where software library is configured. This is a know issue Bug16374229 and fixed in next EM release. For now, support will be updating you how to move forward, also refer-1531166.1

  • Which patch to apply in OEM 12c 12.1.0.4 -  PSU or Bundle patch

    Hello All,
    Could you please help me to understand - which patch to apply in OEM 12c 12.1.0.4 -  PSU or Budle patch ?  Per doc id - Enterprise Manager 12.1.0.4.0 (PS3) Master Bundle Patch List for Agent and Plug-ins (OMS and Agent side) (Doc ID 1900943.1) -
    which of the below  mentioned patch to be applied in OMS ?
    1> System Patch 12.1.0.4.10 - Patch 20675595 (This is a single Sytem patch that includes all the OMS-Side Plug-in Bundles released this month as well as OMS-side Plug-ins released in previous months.)
    or
    2> For 12.1.0.4, this is Patch: https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1900943.1&id=20392036https://updates.oracle.com/ARULink/PatchDetails/process_form?parent=DOCUMENT&sourceId=1900943.1&aru=20392036 &patch_password=&no_header=020392036 (12.1.0.4.3 PSU).  Please refer to Note.1995267.1 for the latest PSU patches available for Oracle Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4).
    We recently upagraded our OEM from 12.1.0.2 to 12.1.0.4  with out using software updates option  during upgrade, hence none of the PSUs are applied to OEM. Now we want to apply latest OEM  patches which fixes all the fixes and bug/securities.
    I thought BP will include PSU as well but  why does DOC id - 1900943.1  says - NOTE: We recommend that you always apply the most recent quarterly PSU.  For 12.1.0.4, this is Patch: https://support.oracle.com/epmos/faces/BugDisplay?parent=DOCUMENT&sourceId=1900943.1&id=20392036https://updates.oracle.com/ARULink/PatchDetails/process_form?parent=DOCUMENT&sourceId=1900943.1&aru=20392036 &patch_password=&no_header=020392036 (12.1.0.4.3 PSU).  Please refer to Note.1995267.1 for the latest PSU patches available for Oracle Enterprise Manager Cloud Control 12c Release 4 (12.1.0.4). ??
    Please help .

    The answer is Yes.   
    The PSU is core OMS patches (think console, incident rules, notifications, etc.) This gets applied to your OMS ORACLE_HOME (i.e. /u01/app/oracle/mw/oms)
    The Plugin System Bundle is a compilation of all the latest plugin patch bundles (So for DB Plugin bundle it contains all the latest DB Plugin fixes).  The system patch will apply required patches as necessary, skip what's not.
    You can read more about the various patches here -
    Patching 101 - The User Friendly Guide to Understanding EM Patches - Courtney Llamas
    http://courtneyllamas.com/enterprise-manager-patching-faq/
    I highly recommend this note as well.  It will help identify exactly what should be applied to the entire EM env. 
    Applying Enterprise Manager 12c Recommended Patches (Doc ID 1664074.1)

  • Anyone using OEM for scheduling backups?

    I'd like to see a poll for the number of users using OEM for taking database backups. Had some interesting conversations with some colleagues via social media and it seems like some DBAs don't trust OEM for their backups even though the feature works IMO.
    Are you using OEM to do backups?
    Edited by: DBA on May 3, 2012 1:02 PM

    I have 91 scheduled recurring backup jobs running through OEM 12c BP1. They work quite well. I've only noticed a few problems and nitpicks:
    1) Occasionally, for unknown reasons, a backup job against a newly-added database target will fail stating that the backup cannot be run since the database is closed. The database is not closed, it's up and running fine. Changing the backup job to run using SYS as SYSDBA credentials resolves this problem.
    2) Identification of failed backups is not as customizable as I would like. For example, if I have a full "backup database plus archivelog" running, and during the course of that backup an archivelog backup runs and deletes archived logs, OEM will report that the backup job has failed since RMAN throws an error about not being able to backup an archivelog it expected to find. I dealt with this by adding SKIP INACCESSIBLE to the backup statement. I'm not totally comfortable about that but I monitor for offline datafiles so I consider this only a minimal risk. Our custom backup scripts used to catch this warning and ignore it.
    3) It's really annoying that, after creating a backup job through the target Availability -> Schedule Backup tool, I cannot then run a 'Create Like' against that backup job to create a nearly identical one against a different database target. You have to schedule each of them from the Schedule Backup tool. Clicky clicky clicky clicky.
    4) A backup job created through the 'Schedule Backup' tool has a job type of 'Database Backup', therefore when the job fails a high-availability incident is created, so you can configure incident rules to receive notification of this event. This is good. Unfortunately a backup job created from the Jobs page has a job type of 'RMAN Script' does NOT create an incident on job failure out of the box. I've had difficulty configuring incident rules to catch failures for RMAN Script job types. This is not good.
    5) The repeating schedule options for jobs are limited compared even to something like cron. I can schedule a job for a day of the week, or a day of the month, but cannot easily schedule a job for "the first Tuesday of each month". This can be worked around.
    6) After creating and submitting a backup job through the Schedule Backup tool, you cannot edit the RMAN script without recreating the job. You can only edit the RMAN script before submitting the job. I deal with this by having my backups run stored scripts in the recovery catalog, and make the changes there if I need to change something.
    7) It is very annoying that if I 'stop' a repeating job (instead of suspend), there is no way to resume that job. It has to be recreated. This is my own user error -- I just don't click the stop button. Not OEM's fault but I'd rather not even have that button.
    8) No ability to sequence jobs. You can sequence steps within a job, but then the entire job succeeds or fails as a unit. If you want to back up database A then immediately back up database B afterwards, you have to create a multi-task job. The multi-task job has the same problem as item #4 above such that it does not create a "backup failed" incident when the backup fails.
    Even with all of these gripes, I am quite pleased with the backups I have running through OEM.

  • How to tell if you have OEM 12c BP1 installed?

    I had OEM 12c installed and attempted to download/apply the Solaris OEM agent software. I ran into the "Below host metric patches are not applied to OMS." error. I discovered this was because I needed BP1.
    After 3 days of trying to uninstall OEM, finally got it uninstalled, downloaded OEM 12c w/BP1 and installed it.
    Once again, I tried to download/apply the Solaris OEM agent software...and I got the same error message. Very frustrating.
    I don't see anything in the "About" pop-up or "emctl status oms" output that actually says a BP has been installed though. Could I have just reinstalled the non-BP version? I got the installations zips directory from the Oracle website that says "Enterprise Manager Cloud Control 12c Release 1 (12.1.0.1) for Linux x86-64
    (With Bundle Patch 1)" so I don't think that's the issue. Is there something else I need to do to get BP 1 working??

    Few things:
    a) If you have linux oms with bp1 and want to deploy solaris agents ( with bp1) then you need to follow the steps from this doc:
    http://docs.oracle.com/cd/E24628_01/doc.121/e35229/aix_solaris.htm#CIHJJGDG
    You will be required to apply patches on OMS and plugin homes on OMS.
    b) If you want to find wether the OMS installed has bp1 or not follow the note: How to Determine if EM Cloud Control 12c with bp1 has Been Installed (Doc ID 1424439.1)

  • OEM 12c E-Business Suite Plugin Issue

    Hello All,
    I am currently new to OEM 12c, and I have the latest version installed and running, Version     12.1.0.2.0. So far everything has been running great, and agents have been downloaded and deployed with little to no issues. However, I am now trying to deploy the E-Business Suite Plug-in to the Management Server first, and I receive an error:
    Stop management server     
         Failed
         November 1, 2012 2:28:25 PM CDT     November 1, 2012 2:28:40 PM CDT     DeployPluginOnPrimaryOMS     emctl.log
    When I look further, I see this in the logs:
    Starting Prereq check..
    Performing Pre config module
    Performing Check required patch
    Checking mandatory patches for plugin : oracle.apps.ebs:12.1.0.1.0:0
    Performing Pre metadata registration
    Performing Pre SQL registration
    Registering plugin SQLs. Reg file is /u01/software/Middleware/oms/sysman/admin/emdrep/plugininfo/pluginDepList
    Completed Prereq check
    Starting Deployment
    Invoking pre deploy callbacks.
    OMS state could be found. It is up
    Stopping OMS.
    EM-04001: Server side Plug-in deployment failed with message Error while stopping Management Server on host <company.com>: Unable to stop OMS.. Contact Oracle Support*
    EM-04026: Server side Plug-in deployment failed due to previous errors. Check log file /u01/software/Middleware/oms/cfgtoollogs/pluginca/plugindeployment_33/configplugin_all_2012-11-01_14-28-12.log on host <company.com> for more details_*
    Performing Opss deconfig
    Performing Midtier deconfig
    Removing synonyms from EMRUNTIME schema
    Removing Plugin's DB objects.
    Stopping OMS
    Starting OMS
    OMS Started successfullyDiagnostic log file: /u01/software/Middleware/oms/cfgtoollogs/pluginca/plugin_deployment_33/configplugin_all_2012-11-01_14-28-12.log
    For help type emctl plugin deploy -help
    I can't seem to find any helpful info on the errors concerning EM-04001 and EM-04026. I did see that there was a bug fix which was required, bug number 13242773. But reading the ReadMe says this is only for OEM version 12.1.0.1.0.
    So, my question is, has anyone run into this problem, or have any suggestions on how to get this plug-in deployed successfully?
    Thanks in advance for your help.
    Edited by: 969006 on Dec 13, 2012 12:25 PM

    Hello,
    I haven’t run into the same errors you have reported but, let me share with you our recommended way of installing E-Business Suite Plug-in. Start by referencing our “Getting Start” MOS note 1434392.1it contains all the required patches, certification details, and related documentation. Once you are ready to perform the install start out by reviewing Chapter 2 - Installing the Oracle Application Management Pack for Oracle E-Business Suite of our Oracle Application Management Pack for Oracle E-Business Suite Guide Release 12.1.0.1.0. Here is a direct link -http://docs.oracle.com/cd/E24628_01/doc.121/e28715.pdf
    If after following the above steps you are still encountering errors then open a Service Request with Oracle Support.
    Regards,
    Product Management

  • Install OEM 12c fails on "start oracle management service". win2008

    Windows Server 2008 R2 Enterprise SP1 x64
    Oracle Database 11g release 11.2.0.3.0
    I install OEM 12c(12.1.0.3) following this manual: Installing Enterprise Manager System
    before start i've installed WebLogic Server 10.3.6 and aplied 2 patches specified in this manual
    installation type is advanced, small, so i have created database from the appropriate template
    i also installed cygwin and started ssh-service
    the installation of OEM process fails on 73% "start oracle management service" with this message:
    INFO: oracle.sysman.top.oms:Starting OMS ...
    INFO: oracle.sysman.top.oms:Executing command: cmd /c set NEED_EXIT_CODE=1&&C:\Oracle\Middleware\oms\bin\emctl.bat start oms
    INFO: oracle.sysman.top.oms:Oracle Enterprise Manager Cloud Control 12c Release 3 
    INFO: oracle.sysman.top.oms:Copyright (c) 1996, 2013 Oracle Corporation.  All rights reserved.
    INFO: oracle.sysman.top.oms:Windows service OracleManagementServer_EMGC_OMS1_1 failed to be started
    INFO: oracle.sysman.top.oms:Oracle Management Server is Down
    INFO: oracle.sysman.top.oms:Please check C:/Oracle/gc_inst/em/EMGC_OMS1\sysman\log\emctl.log for error details
    SEVERE: oracle.sysman.top.oms:Starting of OMS failed.
    in C:/Oracle/gc_inst/em/EMGC_OMS1\sysman\log\emctl.log i got this:
    2013-09-06 12:24:27,012 [main] ERROR commands.BaseCommand logAndPrint.620 - Oracle Management Server Could Not Be Started
    Check EM Server log file for details: C:\Oracle\gc_inst\user_projects\domains\GCDomain\servers\EMGC_OMS1\logs\EMGC_OMS1.out
    2013-09-06 12:24:27,012 [main] INFO  commands.StartCommand startOMS.337 - startOMS finished with result: 1
    2013-09-06 12:24:30,974 [main] INFO  commands.StartCommand startOMS.371 - net start return code is 2
    2013-09-06 12:24:30,974 [main] ERROR commands.BaseCommand logAndPrint.620 - Windows service OracleManagementServer_EMGC_OMS1_1 failed to be started
    2013-09-06 12:24:34,094 [main] INFO  commands.BaseCommand printMessage.404 - statusOMS finished with result: 8
    2013-09-06 12:24:34,094 [main] ERROR commands.BaseCommand logAndPrint.620 - Please check C:/Oracle/gc_inst/em/EMGC_OMS1\sysman\log\emctl.log for error details
    and in C:\Oracle\gc_inst\user_projects\domains\GCDomain\servers\EMGC_OMS1\logs\EMGC_OMS1.out this:
    <06.09.2013 12:24:01 ICT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 23.25-b01 from Oracle Corporation>
    <06.09.2013 12:24:01 ICT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 13349651 Thu May 24 10:18:28 IST 2012
    WebLogic Server Temporary Patch for BUG14482558 Fri Jan 11 11:20:16 IST 2013
    WebLogic Server 10.3.6.0  Tue Nov 15 08:52:36 PST 2011 1441050 >
    <06.09.2013 12:24:03 ICT> <Info> <Security> <BEA-090065> <Getting boot identity from user.>
    Enter username to boot WebLogic server:Error: Failed to get value from Standard Input
    Enter password to boot WebLogic server:
    <06.09.2013 12:24:04 ICT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: Booting as admin server, but servername, EMGC_OMS1, does not match the admin server name, EMGC_ADMINSERVER
         at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
         at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
         at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
         at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
         at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
         at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
         at weblogic.Server.main(Server.java:71)
    >
    <06.09.2013 12:24:04 ICT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    wlst:
    wls:/offline>
    what I did wrong? how to start WLS server?

    Hi,
    First of all with EM 12.1.0.x any version you are not required to install wls separately, we have single installer for em and wls. Is there any specific reason you installer wls separately?
    Coming back to your issue: can you check
    %OMS_HOME%\BIN>emctl istart oms completes successfully.
    %OMS_HOME%\BIN>emctl istop oms completes successfully.
    Also open an SR with Oracle support and share the number. We should debug such issue through SR so that we can share logs and come find a root cause.

  • "add_mp_to_mpa" is not recognized by OEM 12C Command line tool

    Hi,
    As per Oracle® Enterprise Manager Command Line Interface 12c Release 1 (12.1) document ( http://docs.oracle.com/cd/E24628_01/em.121/e17786/cli.htm ), after the EM CLI Client is installed basic operational verbs like 'add_mp_to_mpa " can be used to create managenment plug-in archive. But when i am using this command with OEM 12C EM CLI command line tool it throws following error
    +Error: The command name "add_mp_to_mpa" is not a recognized command.+
    +Run the "help" command for a list of recognized commands.+
    +You may also need to run the "sync" command to synchronize with the current OMS+.
    I also used sync command to sync with my OMS server. The sync command ran successfully with output "Synchronized successfully" .
    When i use help command("emcli help") to see the list of command it supports, it doesn't list this ('add_mp_to_mpa ') verb.
    Please tell me how can i use this particular verb to create my own management plug-in archive(.jar file) in 12 C.
    -Tripati

    "add_mp_to_mpa" verb is no longer an emcli verb in EM 12c. The plug-in framework has changed EM 12c. If necessary, please see the following doc for information on packaging and deploying a plug-in.
    http://docs.oracle.com/cd/E24628_01/doc.121/e25161/package.htm#CACDJJDA
    Regards,
    - Loc

  • Convert custom management plug-in in OEM 11g to OEM 12c compatible plug-in

    Hi All,
    We have a custom plug-in developed and deployed in OEM 11g. We are planning to move to OEM 12c(12.1.0.4) and installing OEM 12c(fresh install) in a new host instead of migrating existing 11g to 12c as part of upgrade process.
    Now question is what are the options if I want to use existing 11g custom plug-in in OEM 12c ? As I understand 11g plug-ins are jar file but OEM 12c plug-ins are OPAR files.
    Can we export plug-in from OEM 11g and import directly in OEM 12c or if there are any steps to conver 11g plugin to 12c plugin before importing it in 12c.
    Please suggest the options available without re-developing the plug-ins for OEM 12c.
    Thanks

    To overwrite and update your current custom plug-in update that is stored in a repository, use the overwrite option.
    $emcli create_custom_plugin_update
    -agent_name="agent_name"
    -plugin_id="plugin_id"
    [-overwrite]
    This command creates and imports a custom plug-in update from an existing Management Agent where the selected plug-in is deployed. The custom plug-in update will be used for all subsequent plug-in deployments on any Management Agent, in place of Oracle supplied versions.
    Custom plug-in update is created as per plug-in type. If a custom plug-in update is created, and after three days, a patch is applied, in order to include the patch, the custom plug-in update will have to be created again.
    $emcli list_custom_plugin_updates
    Please refer the below doc for more info..
    http://docs.oracle.com/cd/E24628_01/doc.121/e24473/plugin_mngr.htm#CJGCHGIH
    Regards
    Krishnan

  • OEM 12c : Deployed MS SQL Server Plug-in. Getting Error When Adding Target Manually

    Hi All,
    Request your help regards to Working with Plug-ins.
    I am using a Oracle linux 5.9 VM with OEM 12c v12.1.0.3.0 Installed.
    I need to work with Non-Oracle Database - specifically MS SQL Server for which I already downloaded and deployed the MS SQL Server Plug-in.
    However when trying to add targets manually, I am getting an error saying "Target Type Microsoft SQL Server is not support on selected monitoring agents em12c.localdomain:3872:Plug-in Microsoft SQL Server Database (12.1.0.3.0) or higher is certified on Enterprise Manager Cloud Control 12.1.0.3.0.
    Can you please guide as to where am i going wrong?
    Your help and guidance is highly appreciated.
    Regards.
    Nayan

    Hi Nayan,
    This seems to be a issue that a different version of MS SQL plugin was deployed on the Agent side.
    As per your description you have already downloaded and deployed the MS SQL Server Plug-in. I am assuming that the version of plugin is 12.1.0.3.
    If not you will need to deploy 12.1.0.3 MS SQL plugin on OMS first and then on the Agent which is monitoring the MS SQL targets.
    + Command to get the plugins deployed On OMS server currently,
    $ cd <OMS_HOME>/bin/
    $ ./emcli login -username=sysman
    Enter password
    Login successful
    $ ./emcli sync
    Synchronized successfully
    $./emcli list_plugins_on_server
    + Command to get the plugins deployed On Agent currently,
    $ cd <AGENT_HOME>/agent_inst/bin/
    $ ./emctl listplugins agent
    Ref: EM 12c: How to Verify the Plugins Deployed on the Enterprise Manager Cloud Control 12.1.0.1 OMS and Agent (Doc ID 1431103.1)
    You can review the below link for MS SQL plugin deploy on OMS and Agent,
    http://docs.oracle.com/cd/E24628_01/install.121/e35211/toc.htm
    Once the 12.1.0.3.0 MS SQL plugin is deployed on OMS and on Agent try to dicover the targets again from console. I hope it will help.
    Regards,
    Biplab

  • OEM 12c unable ot discover Weblogic 10.0.1.0

    I have OEM 12c grid installed and Agent 12c running on the remote host. I have weblogic 10.0.1.0 installed in the remote host. The agent is unable to discover the domain. It is failing with below error...
    "Failed to discover WebLogic. Check host,port,credentials,protocol and be sure the server is running and the same farm is not already added. This UI can not be used to discover WebLogic version 7.x to 8.x. Exception: No targets discovered"
    I can login to the console appication with the ip:port and credentials.. but failing while trying to discover thru the Grid Control.
    I get below error in the OMS log...
    2012-06-25T05:52:09.376-04:00] [EMGC_OMS1] [ERROR:32] [] [oracle.sysman.emas.model.discovery.AddWLStep1Model] [tid: Thread-38498] [userId: SYSMAN] [ecid: 0000DUEGUt_ADSqlcKU4V_0005hD0004kK,1:32596] [APP: emgc] [URI: /em/faces/as/discovery/addWeblogicStep1] Disocvery failed[[
    java.lang.Exception: No targets discovered.
    at oracle.sysman.emInternalSDK.sdkas.general.pojo.model.discovery.FMWDiscoveryBase.discoverTargets(FMWDiscoveryBase.java:588)
    at oracle.sysman.emas.model.discovery.AddWLStep2Model.discoverTargets(AddWLStep2Model.java:1101)
    at oracle.sysman.emas.model.discovery.AddWLStep1Model.discover(AddWLStep1Model.java:464)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at oracle.sysman.emInternalSDK.sdkas.general.pojo.progress.WorkWrapper.run(WorkWrapper.java:113)
    at java.lang.Thread.run(Thread.java:662)
    I then created a empty doman on the same remote host for the same weblogic version. I was able to attch this one and not the other domain.
    I am ruling out OM Grid Server - Agent connectivity issues, since the new empty domain I created can communicate to server.
    I tried to check what is different between domains...
    The WLD that has the issue is a clustered Domain , and has:
    - 9 Managed Servers
    - Not SSL enabled
    - Many Application deployed
    - JDBC connections
    - has a custom build authentication provider for Authentication. But i made sure the user id is valid and even can login to the console.
    ** The new Domain is an empty one - no applications deployed.
    Can you please help understand why I am not able to attach the domain?

    Hi,
    It is the problem in prasing the DTD of config.xml file
    It look like this
    <?xml version='1.0' encoding='UTF-8'?>
    <domain xmlns="http://www.bea.com/ns/weblogic/920/domain" xmlns:sec="http://www.bea.com/ns/weblogic/90/security" xmlns:xsi="http://www.w3.org/2001/XMLSchema-
    instance" xmlns:wls="http://www.bea.com/ns/weblogic/90/security/wls" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90/security/xacml http://www.bea.com/
    ns/weblogic/90/security/xacml.xsd http://www.bea.com/ns/weblogic/90/security http://www.bea.com/ns/weblogic/90/security.xsd http://www.bea.com/ns/weblogic/92
    0/domain http://www.bea.com/ns/weblogic/920/domain.xsd http://www.bea.com/ns/weblogic/90/security/wls http://www.bea.com/ns/weblogic/90/security/wls.xsd">
    Please change your DTD to this lines and start the server.
    Regards
    Ravi D

Maybe you are looking for