No emails being issued by grid control

I am trying to configure GC to send emails. From the preferences page I have added an email address. I have also added an email in the setup, notification methods page.
When I test these I get an email as expected.
I then set up a test with the archive metric. I set the threshold down to 2%
I then set up the relevent notification rule and check the email tab.
then I force the archive area over the 2% threshold and wait for an email. I can see the error on the database page on grid control but do not get an email.
I have set the metric to email on critical and warning
regards
Alan

Check the plan action
Go to Grid control and select the database target
In the home page of databse go down and search Metrics and Polycy settings . Select this
In the page of metrics enable ALL METRICS and search the metric of ARCHIVE AREA used or ARCHIVE AREA FREE % . Put values in CRITICAL and WARNING THERESHOLDS.
When you finish apply the changes
Go to the PREFERENCES page and CREATE A NOTIFICATION RULE
Give NAME to rule and description -- Archiver Rule
In the targets select the database of first step
In the metrics section press the add button
Select the metrics of ARCHIVE AREA monitoring and enable the CRITICAL and WARNING checkbox if yo want notifications for both events
Not select jobs and in the last page enable the checkbox of mail sender
Remember that the metrics in the database must be critical and warning thresholds. The rule not send mail of metrics that not have values . But if you see the alert in grid control console and you dont receive mail, the procedure is create a rule or edit any that exists and add the metrics for archiver monitoring
Regards

Similar Messages

  • Grid Control 10.2.0.1.1 Silent Installation Problem

    I seem to be having issue installing Grid Control 10.2.0.1.1; I am using the silent install with existing database method and for some reason, the installation process is not using some variable I have specified in the response file.
    My operating environment is as follows
    Redhat Enterprise Linux 5.2 [Tikanga] - 32bit
    Repository: Oracle Database 11gR2Variables that I have specifed in the response file and are not being used are below.
    >
    s_mgmtTbsName="/u02/oradata/emrep/oradata/mgmt.dbf"
    s_ecmTbsName="/u02/oradata/emrep/oradata/mgmt_ecm_depot1.dbf"
    >
    slientInstall log has the following entries
    silentInstall2010-08-18_01-15-29-PM.log
    *** Error Dialog: OUI-10150:Error: The file system location /u01/app/oracle/product/oms10g/oradata does not exist. Please enter the path of an existing directory. in component Oracle Enterprise Manager Grid Console 10.2.0.1.1 . Installation cannot continue for this component. ***
    User Selected: S&top installation of this component only.
    The file system location /u01/app/oracle/product/oms10g/oradata does not exist. Please enter the path of an existing directory.
    This silent installation was unsuccessful.installActions log file has the following entries
    INFO: Setting variable 's_mgmtTbsName' to '/u01/app/oracle/product/oms10g/oradata/mgmt.dbf'. Received the value from the variable calculation.
    INFO: Calling Query fileQueries10.1.0.3.0  exists
    filename = /u01/app/oracle/product/oms10g/oradata
    INFO: Query Returned: false
    User Selected: S&top installation of this component only.
    The file system location /u01/app/oracle/product/oms10g/oradata does not exist. Please enter the path of an existing directory.
    This silent installation was unsuccessful.Regard,
    Phiri

    [oracle@oracledba Disk1]$ cat response/em_using_existing_db.rsp
    ## copyright (c) 1999, 2004 Oracle. All rights reserved.          ##
    ## Specify values for the variables listed below to customize     ##
    ## your installation.                                             ##
    ## Each variable is associated with a comment. The comment        ##
    ## identifies the variable type.                                  ##
    ## Please specify the values in the following format:             ##
    ##         Type         Example                                   ##
    ##         String       "Sample Value"                            ##
    ##         Boolean      True or False                             ##
    ##         Number       1000                                      ##
    ##         StringList   {"String value 1","String Value 2"}       ##
    ## The values that are given as <Value Required> need to be       ##
    ## specified for a silent installation to be successful.          ##
    ## This response file is generated by Oracle Software             ##
    ## Packager.                                                      ##
    RESPONSEFILE_VERSION=2.2.1.0.0
    #Name       : UNIX_GROUP_NAME
    #Datatype   : String
    #Description: Unix group to be set for the inventory directory. Valid only in Unix platforms.
    #Example: UNIX_GROUP_NAME = "install"
    UNIX_GROUP_NAME="oinstall"
    #Name       : FROM_LOCATION
    #Datatype   : String
    #Description: Complete path to the products.xml.
    #Example: FROM_LOCATION = "../stage/products.xml"
    FROM_LOCATION="/u02/orasoft/gc_10201/Disk1/rdbms/Disk1/stage/products.xml"
    #Name       : FROM_LOCATION_CD_LABEL
    #Datatype   : String
    #Description: This variable should only be used in multi-CD installations. It includes the label of the compact disk where the file "products.xml" exists. The label can be found in the file "disk.label" in the same directory as products.xml.
    #Example: FROM_LOCATION_CD_LABEL = "CD Label"
    #FROM_LOCATION_CD_LABEL="EM10g"
    #Name       : BASEDIR
    #Datatype   : String
    #Description: Directory where the ORACLE_HOMES gets created
    #Example: BASEDIR = "C:\OHOME1" or BASEDIR = "/scratch/OracleHomes"
    BASEDIR="/u01/app/oracle/product"
    #Name       : INSTALLATION_NAME
    #Datatype   : String
    #Description: Oracle Home Name. Used in creating folders and services.
    #Example: INSTALLATION_NAME = "OHOME1"
    INSTALLATION_NAME="oms10g"
    #Name       : NEXT_SESSION
    #Datatype   : Boolean
    #Description: Set to true to allow users to go back to the File Locations page for another installation. This flag also needs to be set to true in order to process another response file (see NEXT_SESSION_RESPONSE).
    #Example: NEXT_SESSION = true
    NEXT_SESSION=true
    #Name       : NEXT_SESSION_ON_FAIL
    #Datatype   : Boolean
    #Description: Set to true to allow users to invoke another session even if current install session has failed. This flag is only relevant if NEXT_SESSION is set to true.
    #Example: NEXT_SESSION_ON_FAIL = true
    NEXT_SESSION_ON_FAIL=true
    #Name       : DEINSTALL_LIST
    #Datatype   : StringList
    #Description: List of components to be deinstalled during a deinstall session.
    #The following choices are available. The value should contain only one of these choices.
    #The choices are of the form Internal Name, Version : External name. Please use the internal name and version while specifying the value.
    #    oracle.sysman.top.agent, 10.2.0.0.0 : Oracle Management Agent 10.2.0.0.0
    #    oracle.sysman.top.em_seed, 10.2.0.0.0 : Oracle Enterprise Manager Repository Database 10.2.0.0.0
    #    oracle.sysman.top.oms, 10.2.0.0.0 : Oracle Enterprise Manager Grid Console 10.2.0.0.0
    #Example: DEINSTALL_LIST = {"oracle.sysman.top.agent","10.2.0.0.0"}
    DEINSTALL_LIST={"oracle.sysman.top.oms","10.2.0.1.1"}
    #Name       : SHOW_DEINSTALL_CONFIRMATION
    #Datatype   : Boolean
    #Description: Set to true if deinstall confimation is needed during a deinstall session.
    #Example: SHOW_DEINSTALL_CONFIRMATION = true
    SHOW_DEINSTALL_CONFIRMATION=true
    #Name       : SHOW_DEINSTALL_PROGRESS
    #Datatype   : Boolean
    #Description: Set to true if deinstall progress is needed during a deinstall session.
    #Example: SHOW_DEINSTALL_PROGRESS = true
    SHOW_DEINSTALL_PROGRESS=true
    #Name       : REMOVE_HOMES
    #Datatype   : StringList
    #Description: List of the homes to be removed during a deinstall session. Each home is represented by its full path.
    #Example: REMOVE_HOMES = {<full_path_of_home1>,<full_path_of_home2>, ...}
    REMOVE_HOMES=<Value Unspecified>
    #Name       : ACCEPT_LICENSE_AGREEMENT
    #Datatype   : Boolean
    #Description: By setting this variable to true, you are accepting the license agreement. This variable is used only for silent installations.
    #Example: ACCEPT_LICENSE_AGREEMENT = true
    ACCEPT_LICENSE_AGREEMENT=true
    #Name       : TOPLEVEL_COMPONENT
    #Datatype   : StringList
    #Description: The top level component to be installed in the current session.
    #The following choices are available. The value should contain only one of these choices.
    #The choices are of the form Internal Name, Version : External name. Please use the internal name and version while specifying the value.
    #    oracle.sysman.top.agent, 10.2.0.0.0 : Oracle Management Agent 10.2.0.0.0
    #    oracle.sysman.top.em_seed, 10.2.0.0.0 : Oracle Enterprise Manager Repository Database 10.2.0.0.0
    #    oracle.sysman.top.oms, 10.2.0.0.0 : Oracle Enterprise Manager Grid Console 10.2.0.0.0
    #Example: TOPLEVEL_COMPONENT = {"oracle.sysman.top.agent","10.2.0.0.0"}
    TOPLEVEL_COMPONENT={"oracle.sysman.top.oms","10.2.0.1.1"}
    #Name       : SELECTED_LANGUAGES
    #Datatype   : StringList
    #Description: Languages in which the components will be installed.
    #The following choices are available. The value should contain only one of these choices.
    #The choices are of the form Internal Name : External name. Please use the internal name while specifying the value.
    #    en,   : English
    #    de,   : German
    #    es,   : Latin American Spanish
    #    es_MX,   : Mexican Spanish
    #    es_ES,   : Spanish
    #    fr,   : French
    #    fr_CA,   : Canadian French
    #    it,   : Italian
    #    iw,   : Hebrew
    #    ja,   : Japanese
    #    ko,   : Korean
    #    pt_BR,   : Brazilian Portuguese
    #    zh_CN,   : Simplified Chinese
    #    zh_TW,   : Traditional Chinese
    #Example: SELECTED_LANGUAGES = {"en"}
    #SELECTED_LANGUAGES={"en"}
    #Name       : COMPONENT_LANGUAGES
    #Datatype   : StringList
    #Description: Languages in which the components will be installed.
    #The following choices are available. The value should contain only one of these choices.
    #The choices are of the form Internal Name : External name. Please use the internal name while specifying the value.
    #    en,   : English
    #    de,   : German
    #    es,   : Latin American Spanish
    #    es_MX,   : Mexican Spanish
    #    es_ES,   : Spanish
    #    fr,   : French
    #    fr_CA,   : Canadian French
    #    it,   : Italian
    #    iw,   : Hebrew
    #    ja,   : Japanese
    #    ko,   : Korean
    #    pt_BR,   : Brazilian Portuguese
    #    zh_CN,   : Simplified Chinese
    #    zh_TW,   : Traditional Chinese
    #Example: COMPONENT_LANGUAGES = {"en"}
    #Component  : oracle.sysman.top.oms
    COMPONENT_LANGUAGES={"en"}
    #Name       : s_reposHost
    #Datatype   : String
    #Description: Hostname of the Repository database
    #Component  : oracle.sysman.top.oms
    #Example    :s_reposHost="stadv26.us.oracle.com"
    s_reposHost="oracledba"
    #Name       : s_reposPort
    #Datatype   : String
    #Description: Port on which the Repository database is running
    #Component  : oracle.sysman.top.oms
    #Example    :s_reposPort="1521"
    s_reposPort="1521"
    #Name       : s_reposSID
    #Datatype   : String
    #Description: SID or Service name  of the Repository database
    #Component  : oracle.sysman.top.oms
    #Example    :s_reposSID="emrep"
    s_reposSID="emrep"
    #Name       : s_reposDBAPwd
    #Datatype   : String
    #Description: Password of DBA user used to create repository schema
    #Component  : oracle.sysman.top.oms
    # Example   : s_reposDBAPwd="password"
    s_reposDBAPwd="emgc10g"
    #Name       : s_mgmtTbsName
    #Datatype   : String
    #Description: Mgmt tablespace name
    #Component  : oracle.sysman.top.oms
    #This will get created on the machine where the database is present
    #So make sure that the directory given here is present in the machine where the database exists
    #ORACLE_HOME/oradata/mgmt.dbf
    #Example   : s_mgmtTbsName=/scratch/OracleHomes/oradata/mgmt.dbf
    s_mgmtTbsName="/u02/oradata/emrep/oradata/mgmt.dbf"
    #Name       : s_ecmTbsName
    #Datatype   : String
    #Description: ECM tablespace name
    #Component  : oracle.sysman.top.oms
    #This will get created on the machine where the database is present
    #So make sure that the directory given here is present in the machine where the database exists
    #ORACLE_HOME/oradata/mgmt_ecm_depot1.dbf
    #Example    : s_ecmTbsName=/scratch/OracleHomes/oradata/mgmt_ecm_depot1.dbf
    s_ecmTbsName="/u02/oradata/emrep/oradata/mgmt_ecm_depot1.dbf"
    #Name       : b_emailSelected
    #Datatype   : Boolean
    #Description: Whether to receive automatic threshold notification email
    #Component  : oracle.sysman.top.oms
    #Example    : b_emailSelected=false/true
    b_emailSelected=<Value Unspecified>
    #Name       : s_emailAddress
    #Datatype   : String
    #Description: Address to receive threshold notification email, this will be effected only when b_emailSelected=true
    #Component  : oracle.sysman.top.em_seed
    s_emailAddress=<Value Unspecified>
    #Name       : s_emailServer
    #Datatype   : String
    #Description: SMTP gateway used to send threshold notification email, this will be effected only when b_emailSelected=true
    #Component  : oracle.sysman.top.em_seed
    s_emailServer=<Value Unspecified>
    #Name       : b_metalinkSelected
    #Datatype   : Boolean
    #Description: Whether MetaLink connection was configured
    #Component  : oracle.sysman.top.em_seed
    #Example    : b_metalinkSelected=false/true
    b_metalinkSelected=<Value Unspecified>
    #Name       : s_metalinkUser
    #Datatype   : String
    #Description: user name for MetaLink access, this will be effected only when b_metalinkSelected=true
    #Component  : oracle.sysman.top.em_seed
    s_metalinkUser=<Value Unspecified>
    #Name       : s_metalinkPassword
    #Datatype   : String
    #Description: password for MetaLink access, this will be effected only when b_metalinkSelected=true
    #Component  : oracle.sysman.top.em_seed
    s_metalinkPassword=<Value Unspecified>
    #Name       : b_proxySelected
    #Datatype   : Boolean
    #Description: Whether proxy connection was configured
    #Component  : oracle.sysman.top.em_seed
    #Example: b_proxySelected=false/true
    b_proxySelected=<Value Unspecified>
    #Name       : EM_PROXYUSER
    #Datatype   : String
    #Description: User name for proxy access,this will be effected only when b_proxySelected=true
    #Component  : oracle.sysman.top.em_seed
    EM_PROXYUSER=<Value Unspecified>
    #Name       : EM_PROXYREALM
    #Datatype   : String
    #Description: Server providing proxy access, this will be effected only when b_proxySelected=true
    #Component  : oracle.sysman.top.em_seed
    EM_PROXYREALM=<Value Unspecified>
    #Name       : EM_PROXYPASSWORD
    #Datatype   : String
    #Description: Password for proxy access, this will be effected only when b_proxySelected=true
    #Component  : oracle.sysman.top.em_seed
    EM_PROXYPASSWORD=<Value Unspecified>
    #Name       : EM_PROXYHOST
    #Datatype   : String
    #Description: Server providing proxy access, this will be effected only when b_proxySelected=true
    #Component  : oracle.sysman.top.em_seed
    EM_PROXYHOST=<Value Unspecified>
    #Name       : EM_DONTPROXYFOR
    #Datatype   : String
    #Description: Domains which should not use proxy access, this will be effected only when b_proxySelected=true
    #Component  : oracle.sysman.top.em_seed
    EM_DONTPROXYFOR=<Value Unspecified>
    #Name       : EM_PROXYPORT
    #Datatype   : String
    #Description: Port for proxy access, this will be effected only when b_proxySelected=true
    #Component  : oracle.sysman.top.em_seed
    EM_PROXYPORT=<Value Unspecified>
    #Name       : s_securePassword
    #Datatype   : String
    #Description: Password for secure communication with Management Server
    #Component  : oracle.sysman.top.oms
    #Example    : s_securePassword="password"
    s_securePassword="emgc10g"
    #Name       : s_securePasswordConfirm
    #Datatype   : String
    #Description: Confirmation of password for secure communication with Management Server
    #Component  : oracle.sysman.top.oms
    #Example    : s_securePasswordConfirm="password"
    s_securePasswordConfirm="emgc10g"
    #Name       : b_lockedSelected
    #Datatype   : Boolean
    #Description: Whether agent communication should be locked
    #Component  : oracle.sysman.top.oms
    #Example    : b_lockedSelected=true/false
    b_lockedSelected=false
    #Name       : s_reposPwd
    #Datatype   : String
    #Description: Password of repository schema owner
    #Component  : oracle.sysman.top.oms
    #Example    : s_reposPwd="password"
    s_reposPwd="emgc10g"
    #Name       : s_reposPwdConfirm
    #Datatype   : String
    #Description: Password for repository schema owner
    #Component  : oracle.sysman.top.oms
    #Example    : s_reposPwdConfirm="password"
    s_reposPwdConfirm="emgc10g"
    #Please Don't change the values of these variables
    n_firstInstanceValidation=2
    n_firstReposValidation=1
    n_firstReposPwdValidation=2
    n_firstSecureValidation=2
    n_firstVldnEmailSer=2
    #Name       : b_upgrade
    #Datatype   : Boolean
    #Description: To Specify whether it is Normal Install or Upgrade
    #Component  : oracle.sysman.top.oms
    #PLEASE DON'T CHANGE THIS VALUE
    b_upgrade=false
    #Name       : b_showOptConfigPage
    #Datatype   : Boolean
    #Description: whether to perform optional configuration
    #Component  : oracle.sysman.top.oms
    #PLEASE DON'T CHANGE THIS VALUE
    b_showOptConfigPage=TRUE
    #Name       : s_installType
    #Datatype   : String
    #Description: Type of Grid Control install being performed
    #Component  : oracle.sysman.top.oms
    #PLEASE DON'T CHANGE THIS VALUE
    s_installType="NOSEED"
    [oracle@oracledba Disk1]$

  • Cloning-Grid control

    Hi,
    we have grid control setup to monitor our production database,we have some issues with grid control and we want clone to replicate the issues in test environment.Can we clone Grid setup. If so ,please let us know the procedure.
    Our Grid env details
    ==========
    ORACLE_HOME=/u01/oracle/db10g
    GRID_HOME=/u01/oracle/oms10g
    AGENT_HOME=/u01/oracle/agent10g
    can we clone all the 3 three?
    Regards,
    Mannu

    Hello,
    I've not seen any documentation to clone grid control i.e. OMS, db home, and agent home. However, if i had to do it, I would use the procedure to migrate Grid Control to a new machine and make some changes along the way.
    1. Install 2nd OMS in test environment pointing to existing repository.
    This will install OMS home and agent home on your test machine.
    2. Install db software on test machine and copy existing repository to test machine.
    3. Update OMS to point to this new repository.
    At this point, you have everything running in your test environment. However, the production OMS is "aware" of this OMS so you need to clean up the targets on your production OMS that points to your test environment and repeat the same thing for the test OMS so it's not "aware" of the production targets.
    If you need more details, let me know.
    HTH

  • Old emails on grid control being sent

    ah ok so I was able to resolve email alerts not being sent but then I got flooded with old alerts
    how do I clean these up from grid control?

    try this method, it has worked for me in the past. There maybe more efficient ways to complete the task your are asking about but this I know works.
    login to the repository database as the SYSMAN user
    SELECT 'EXEC EM_SEVERITY.DELETE_CURRENT_SEVERITY('''||TARGET_GUID||''','''||METRIC_GUID||''',''' ||KEY_VALUE||''');' MCS
    FROM MGMT_CURRENT_SEVERITY;
    this will produce a list of alerts
    run each script manually, it can take a little while for the alerts to go.regards
    Alan

  • Grid Control stops sending emails?

    Hello everyone. Interesting thing happened today. For whatever reasons, Grid Control stopping sending out email alerts that we have configured. Let me give some details.
    We have customized some rules so we can receive email alerts if something goes wrong with our production databases. It has worked great until today.
    We have setup an alert to let us know the 'state' of the database. This worked extremely well on our dataguard box, which would change status to 'MOUNT" twice a day as we applied redo logs from the primary database. Each time this happened, Grid Control would fire off an email alert stating the database was in the 'MOUNT' stage.
    Once all the logs were applied and the database would return to 'OPEN', we could get a email saying the database was 'CLEAR' and now 'OPEN'.
    This worked great, until our 17:00 log applies happened.
    We did not receive anything at all and now I am trying to figure out why.
    To my knowledge, nothing has changed on the Grid Control server.
    I logged in and checked everything out, and it seemed ok.
    I did restart some of the services and restarted the DB instance.
    Doing some testing, I stopped a database to check the rule. It took a while for Grid Control to recognize that the database was down and it eventually fired off a email alert stating the database was unreachable. But this was after at least 3-5 minutes, where as before, it was almost instant.
    My guess is that for whatever reasons, is that when the database status changes, Grid Control is not finding out right away. Due to the latency of the issue, by the time all the logs have applied (no more than 5 minutes), the database is back 'OPEN' and the database looks good to grid control.
    I'm a little baffled by this because Grid Control has worked great for months.
    Does anyone have any idea on what could be wrong?
    Any ideas on where to start looking?
    Any additional information I can post to help troubleshoot? Logs?
    I appreciate it.
    Jason

    hi,
    Has a schedule been set-up for the user. This normally happens when a user is created.
    Does the user have access to the rule set that has been created.
    For example, in my system SYSMAN creates all the rules and then makes them public. Individual users then subscribe to the public rules to get the alerts.
    regards
    Alan

  • Grid control switchover issue

    Hi,
    I have carried out the following
    a 10g database install on 2 servers
    enabled dataguard between them so I have a primary and a standby database.
    I then installed Grid Control onto each server using the opetion to install into an existing database. this worked.
    On the standby server opmnctl is shutdown and the database is a PHYSICAL STANDBY.
    when I do a dataguard switchover I see the standby database is now the primary. I restart opmnctl and go to the web browser to look at Grid Control.
    The issue I have is that Grid Control, even though it is on the standby server, points to the primary server. How can I change this behaviour
    When I first started Grid Control I had to perform the following actions
    [oracle@griddg bin]$ ./emctl status emkey
    Oracle Enterprise Manager 10g Release 3 Grid Control
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Please enter repository password:
    The Em Key exists in the Management Repository, but is not configured properly or is corrupted in the file system.
    Configure the Em Key by running "emctl config emkey -repos".
    [oracle@griddg bin]$ ./emctl config emkey -repos
    Oracle Enterprise Manager 10g Release 3 Grid Control
    Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
    Please enter repository password:
    The Em Key has been configured successfully.
    after this gridcontrol was able to start but points to the wrong host.
    rgds
    alan

    hi,
    the steps I took are as follows
    1 - precreate a database on the primary and standby.
    2 - configure the tnsnames and listener files so that the databases can talk to each other
    3 - create a standby control file from the primary database.
    4 - copy all database files from the primary to the standby
    5 - copy the standby controlfile to the standby
    6 - start the primary database
    7 - start the standby database but only mounted, check database_role from v$database; it should be physical standby
    8 - install Grid Control on the primary server with the option to install onto an existing database. Complete this installation.
    9 - Install Grid Control onto the standby server with the option to install onto an existing database. Complete the installation and then carry out an 'opmnctl stopall'
    10 - all being well Grid Control should now show both hosts and databases.
    11 - create a dataguard configuration from within GC
    The standby database cannot be discovered correctly in GC and this must be because it is in a mount state, not sure what to do about this. This then meant that I had to carry out a switchover from the command line. I am just testing this now and will post back when complete.
    regards
    Alan

  • RHEL4U4 EM64T Grid Control agent install issue

    I've installed a 2 node Oracle 10G R2 RAC on RHEL4 U4 EM64T and it is working fine on Dell PE2850 servers. But I couldn't get the grid control agent installed on these RHEL4U4 EM64T PE2850 servers. The OMS server is running 32 bit Oracle 10g R2 on RHEL4. The issue is with the OMA (agent) install on EM64T and I've tried several different options (local install and push from the OMS server). I end up with the following error. Any feedback is appreciated. Thanks.
    Raj
    <<installActions2006-12-07_11-22-39AM.log>>
    This is error we got from both the install on the local node and tried a push from the OMS server as well.
    INFO: Start output from spawned process:
    INFO: ----------------------------------
    INFO:
    INFO: /opt/oracle/product/10.2.0/agent10g/bin/genclntsh
    INFO: /usr/bin/ld: skipping incompatible /opt/oracle/product/10.2.0/agent10g/lib/libxml10.a when searching for -lxml10
    /usr/bin/ld: cannot find -lxml10
    INFO: collect2: ld returned 1 exit status
    INFO: genclntsh: Failed to link libclntsh.so.10.1
    INFO: make: *** [client_sharedlib] Error 1
    INFO: End output from spawned process.
    INFO: ----------------------------------
    INFO: Exception thrown from action: make
    Exception Name: MakefileException
    Exception String: Error in invoking target 'client_sharedlib' of makefile '/opt/oracle/product/10.2.0/agent10g/network/lib/ins_net_client.mk'. See '/opt/oracle/oraInventory/logs/installActions2006-12-07_11-22-39AM.log' for details.
    Exception Severity: 1

    Hi,
    Did you run cvu to check if all OS Patches are installed ??
    Best Regards,
    Paulo.

  • Patching Grid Control OMS and Agent to 10.2.0.5 issue

    Oracle 11gR1 RHEL5 - Grid Control 10.2.0.5
    Hi All,
    I have been stuck on this issue for over a month (was relying on Oracle supports help and they just would not reply) and I can't figure it out. Basically, what happened is that my 10.2.0.5 patch set failed partiallty when I was applying it to the OMS. Here is what is going on right now:
    Database Repository (EMREP) - 11gR1 (11.1.0.6) - /opt/app/oracle/product/11.1.0/db_1
    OMS - 10.2.0.5 - /opt/app/oracle/product/10.2.0/grid_1/oms10g
    Agent - 10.2.0.5 - /opt/app/oracle/product/10.2.0/grid_1/agent10g
    When I was almost done with the 10.2.0.5 patch on the OMS, OUI gave me the following error:
    SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly recommended that you retry the configuration
    assistants at this time. Not successfully running any "Recommended" assistants
    means your system will not be correctly configured.
    *1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the*
    failures.
    *2. Fix the errors causing these failures.*
    *3. Select the failed assistants and click the 'Retry' button to retry them*
    When I checked the logs I found the following messages (Here is a part of it...I think before it started to fail):
    Finished deleting the above files...
    INFO: Configuration assistant "OMS Oneoff Patch Application" succeeded
    INFO: Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
    Repository Upgrade is failed with errors. Restore the database, rectify the errors and retry the install.
    For more details :
    -For configuration issues, look at the log files present in following location:
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/cfgfw
    -For repository failures, look at the log files
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.
    2.0.5.0
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors
    -If not able to identify the repository issues, contact ORACLE Support.
    -After the Repository issues are rectified and upgraded successfully, execute the below runConfig command to run remaining config tools.
    Goto /opt/app/oracle/product/10.2.0/grid_1/oms10g/oui/bin directory and run below command.
    For UNIX :
    ./runConfig.sh ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
    For Windows :
    runConfig.bat ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
    Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade has failed
    Exception : java.lang.Exception: Command: /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/admin/emdrep/bin/RepManager -connect (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=rhel-grid)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=emrep))) -action upgrade -no_transx -no_verify -verbose -repos_user sysman -output_file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0 failed. Exit code: expected [0 ], but got 45
    INFO: Configuration assistant "Repository Upgrade" failed
    *** Starting OUICA ***
    Oracle Home set to /opt/app/oracle/product/10.2.0/grid_1/oms10g
    Configuration directory is set to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs. All xml files under the directory will be processed
    Parsing configuration file config.xml ....
    Ended Parsing configuration file config.xml
    Start Processing configuration tool Oracle Internet Directory Patch Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Buffer size for copying file is set to 2048
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/patchca.log could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Oracle Internet Directory Patch Configuration Assistant
    Start Processing configuration tool Directory Integration Platform Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/ldap/log/oidca.log could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Directory Integration Platform Configuration Assistant
    Start Processing configuration tool OC4J Instance Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/home_default_island_1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/operations from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/log.xml from the file path expanding...
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/j2ee/home/log/log.xml to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/log.xml
    Number of file(s) copied is 1
    Number of directories copied is 0
    End Processing configuration tool OC4J Instance Configuration Assistant
    Start Processing configuration tool OPMN Configuration Assistant - start HTTP server....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCacheAdmin~1 from the file path expanding...
    Number of directories copied is 0
    End Processing configuration tool OPMN Configuration Assistant - start OCA Instance
    Start Processing configuration tool Wireless Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Wireless Configuration Assistant
    Start Processing configuration tool Wireless Metadata Repository Update....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/wireless/logs/upgrade_CA.out could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Wireless Metadata Repository Update
    Start Processing configuration tool Portal Metadata Repository Update....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log from the file path expanding...
    WARN: Source file /opt/app/oracle/product/10.2.0/grid_1/oms10g/portal/upg/plsql/upgrade.log could not be found. Nothing will be copied for this file
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool Portal Metadata Repository Update
    Start Processing configuration tool OPMN Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCacheAdmin~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EM~default_island~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/dcm-daemon~dcm-daemon~dcm~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ons.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCache~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EMPROV~default_island~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/states from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~home~default_island~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/opmn.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/HTTP_Server~1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ipm.log from the file path expanding...
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCacheAdmin~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/WebCache~WebCacheAdmin~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EM~default_island~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/OC4J~OC4J_EM~default_island~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/dcm-daemon~dcm-daemon~dcm~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/dcm-daemon~dcm-daemon~dcm~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ons.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/ons.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/WebCache~WebCache~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/WebCache~WebCache~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~OC4J_EMPROV~default_island~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/OC4J~OC4J_EMPROV~default_island~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/OC4J~home~default_island~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/OC4J~home~default_island~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/opmn.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/opmn.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/HTTP_Server~1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/HTTP_Server~1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/opmn/logs/ipm.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/ipm.log
    Number of file(s) copied is 10
    Number of directories copied is 0
    End Processing configuration tool OPMN Configuration Assistant
    Start Processing configuration tool Application Server Control Configuration Assistant....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.10 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.trc from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.4 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.7 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/nfsPatchPlug.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-application.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.9 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.8 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.trc from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emctl.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/server.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/secure.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.6 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em.nohup from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-web-access.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/pafLogs from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emias.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.5 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0.errors from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.3 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.trc from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/rmi.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.2 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emca_repos_out_of_box12_56_33.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.log from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log.1 from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.transx from the file path expanding...
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.10 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.10
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emdctl.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.4.0
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagentfetchlet.trc
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.4 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.4
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.7 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.7
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/nfsPatchPlug.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/nfsPatchPlug.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-application.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/em-application.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.9 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.9
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.8 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.8
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.5.0
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emdctl.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emdctl.trc
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emctl.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emctl.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/server.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/server.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/secure.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/secure.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.6 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.6
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em.nohup to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/em.nohup
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.5.0.errors
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/em-web-access.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/em-web-access.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emias.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emias.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.5 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.5
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.4.0.errors to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.4.0.errors
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.3 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.3
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.trc to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagent.trc
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/rmi.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/rmi.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagent.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagent.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.trc.2 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.trc.2
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emca_repos_out_of_box12_56_33.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emca_repos_out_of_box12_56_33.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emagentfetchlet.log to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emagentfetchlet.log
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emoms.log.1 to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emoms.log.1
    Completed copying file /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.transx to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/emrepmgr.log.10.2.0.5.0.transx
    Number of file(s) copied is 34
    Number of directories copied is 0
    End Processing configuration tool Application Server Control Configuration Assistant
    Start Processing configuration tool DCM Repository Update Assistant ....
    Preparing for copying /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/* to /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs
    Expanding source path /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/*
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/dcmctl_logs from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/emd_logs from the file path expanding...
    Adding the file /opt/app/oracle/product/10.2.0/grid_1/oms10g/dcm/logs/daemon_logs from the file path expanding...
    Number of file(s) copied is 0
    Number of directories copied is 0
    End Processing configuration tool DCM Repository Update Assistant
    INFO: The "/opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/configToolFailedCommands" script contains all commands that failed, were skipped or were cancelled. This file may be used to run these configuration assistants outside of OUI. Note that you may have to update this script with passwords (if any) before executing the same.
    INFO: Since the option is to overwrite the existing /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/configToolFailedCommands file, backing it up
    INFO: The backed up file name is /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/configToolFailedCommands.bak.1
    SEVERE: OUI-25031:Some of the configuration assistants failed. It is strongly recommended that you retry the configuration assistants at this time. Not successfully running any "Recommended" assistants means your system will not be correctly configured.
    1. Check the Details panel on the Configuration Assistant Screen to see the errors resulting in the failures.
    2. Fix the errors causing these failures.
    3. Select the failed assistants and click the 'Retry' button to retry them.
    INFO: User Selected: Yes/OK
    INFO: Starting to execute configuration assistants
    INFO: Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
    Repository Upgrade is failed with errors. Restore the database, rectify the errors and retry the install.
    For more details :
    -For configuration issues, look at the log files present in following location:
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/cfgtoollogs/cfgfw
    -For repository failures, look at the log files
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0
    /opt/app/oracle/product/10.2.0/grid_1/oms10g/sysman/log/emrepmgr.log.10.2.0.5.0.errors
    -If not able to identify the repository issues, contact ORACLE Support.
    -After the Repository issues are rectified and upgraded successfully, execute the below runConfig command to run remaining config tools.
    Goto /opt/app/oracle/product/10.2.0/grid_1/oms10g/oui/bin directory and run below command.
    For UNIX :
    ./runConfig.sh ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
    For Windows :
    runConfig.bat ORACLE_HOME=/opt/app/oracle/product/10.2.0/grid_1/oms10g ACTION=patchsetConfigure MODE=perform COMPONENT_XML=oracle.sysman.top.oms.10_2_0_5_0.xml
    Command = oracle.sysman.emcp.oms.RepositoryPatchUpgrade has failed
    Exception : java.lang.Exception:
    REPOSITORY UPGRADE STATUS : 3
    INFO: Configuration assistant "Repository Upgrade" failed
    I would appreciate any help on this as I have been stuck on it since April :( Not too happy with Oracle Support.
    Thanks much to all!
    JrOraDBA

    Here is the output for when I applied the patch:
    opatch apply
    Invoking OPatch 10.2.0.3.0
    Oracle interim Patch Installer version 10.2.0.3.0
    Copyright (c) 2005, Oracle Corporation.  All rights reserved..
    Oracle Home       : /opt/app/oracle/product/10.2.0/grid_1/db10g
    Central Inventory : /opt/app/oracle/oraInventory
    from           : /etc/oraInst.loc
    OPatch version    : 10.2.0.3.0
    OUI version       : 10.2.0.3.0
    OUI location      : /opt/app/oracle/product/10.2.0/grid_1/db10g/oui
    Log file location : /opt/app/oracle/product/10.2.0/grid_1/db10g/cfgtoollogs/opatch/opatch2009-04-22_12-07-14PM.log
    ApplySession applying interim patch '4329444' to OH '/opt/app/oracle/product/10.2.0/grid_1/db10g'
    Invoking fuser to check for active processes.
    Invoking fuser on "/opt/app/oracle/product/10.2.0/grid_1/db10g/bin/oracle"
    OPatch detected non-cluster Oracle Home from the inventory and will patch the local system only.
    Please shutdown Oracle instances running out of this ORACLE_HOME on the local system.
    *(Oracle Home = '/opt/app/oracle/product/10.2.0/grid_1/db10g')*
    Is the local system ready for patching?
    *Do you want to proceed? y*
    y
    User Responded with: Y
    Backing up files and inventory (not for auto-rollback) for the Oracle Home
    Backing up files affected by the patch '4329444' for restore. This might take a while...
    Backing up files affected by the patch '4329444' for rollback. This might take a while...
    Patching component oracle.rdbms, 10.1.0.4.0...
    Updating archive file "/opt/app/oracle/product/10.2.0/grid_1/db10g/lib/libserver10.a"  with "lib/libserver10.a/qerix.o"
    ApplySession adding interim patch '4329444' to inventory
    Verifying the update...
    Inventory check OK: Patch ID 4329444 is registered in Oracle Home inventory with proper meta-data.
    Files check OK: Files from Patch ID 4329444 are present in Oracle Home.
    Running make for target ioracle
    The local system has been patched and can be restarted.
    OPatch succeeded.
    However, the weird thing is that I don't see it in the lsinventory:
    */opt/app/oracle/product/10.2.0/grid_1/db10g/OPatch/opatch lsinventory*
    Invoking OPatch 10.2.0.3.0
    Oracle interim Patch Installer version 10.2.0.3.0
    Copyright (c) 2005, Oracle Corporation.  All rights reserved..
    Oracle Home       : /opt/app/oracle/product/10.2.0/grid_1/db10g
    Central Inventory : /opt/app/oracle/oraInventory
    from           : /etc/oraInst.loc
    OPatch version    : 10.2.0.3.0
    OUI version       : 10.2.0.3.0
    OUI location      : /opt/app/oracle/product/10.2.0/grid_1/db10g/oui
    Log file location : /opt/app/oracle/product/10.2.0/grid_1/db10g/cfgtoollogs/opatch/opatch2009-06-09_09-37-54AM.log
    Lsinventory Output file location : /opt/app/oracle/product/10.2.0/grid_1/db10g/cfgtoollogs/opatch/lsinv/lsinventory2009-06-09_09-37-54AM.txt
    Installed Top-level Products (2):
    Oracle Database 10g Patch Set 3                                      10.1.0.5.0
    Oracle Enterprise Manager Repository Database                        10.2.0.3.0
    There are 2 products installed in this Oracle Home.
    Interim patches (1) :
    Patch  5632264      : applied on Thu Apr 23 12:23:10 CDT 2009
    Created on 8 Feb 2007, 00:38:09 hrs PST8PDT
    Bugs fixed:
    *5632264*
    OPatch succeeded.
    Do you think I should restore the backup (and I only have the database backup, not the Oracle Home backup)?
    THanks.

  • Linux OEM Grid Control 10.2.0.1.0 installation issue

    Just a heads up to anyone installing Linux OEM Grid Control 10.2.0.1.0
    If you are doing a full install, the "product specific prerequisite checks" page will show an error on the following packages even if you have them installed.
    compat-libstdc++-296-2.96-132.7.2 (failed)
    libstdc++devel-3.4.3-22.1 (failed)
    openmotif-21-2.1.30-11 (failed)
    Note that the installation works fine if you ignore the "missing" prerequisites. I believe the check itself is flawed. The openmotif check should be openmotif21-**** (extra hyphen incorrect in check - the old install was openmotif, now openmotif21), the libstdc++ needs a hypen added before the devel, and the compat-libstdc++ has yet another issue.
    This is something the developers at oracle will have to fix.
    Steve

    Yes, you must download and install the 10.2.0.1 version and then patch it up to the 10.2.0.4 version.
    http://www.oracle.com/technology/obe/obe10gem/install/index.html
    The above link shows you the install routine when using a new database, the steps for the existing database are only slightly different, all you need are the connection details for that existing database and you should be ok.
    As for taking full backups of the Grid Control repository, I know many choose not to, space is always a big concern, but this depends on how critical your repository is to you. If you need it for the auditors, well then I'd suggest acquiring some more hard disks to up your space.

  • Issue with OEM grid control.

    I created a stream replication for scott schema on 10gR2 using maintain_tables.
    Everything is working fine and for initail two days there was no issue when i checked the diffrent processes using OEM grid control. After two days, OEM is not showing anything under the "propagation" process and instead showing "no data found". I checked the dba_propagation and there is a propagation process in that. Even the replication is working fine. So is that an issue/Bug in OEM? Any cure for this?
    Kapil

    I created a stream replication for scott schema on 10gR2 using maintain_tables.
    Everything is working fine and for initail two days there was no issue when i checked the diffrent processes using OEM grid control. After two days, OEM is not showing anything under the "propagation" process and instead showing "no data found". I checked the dba_propagation and there is a propagation process in that. Even the replication is working fine. So is that an issue/Bug in OEM? Any cure for this?
    Kapil

  • There are unauthorised emails being sent from my emails accounts. This started recently following my iOS update to 5.0.1. Is this an iCloud hacking issue?

    There appears to be emails being sent out to random contacts from my shared address book with dubious content none of which were sent by me. I believe this was sent by unauthorised hacker from iCloud as the contacts are not even in my personal contact list, but came from my wife's contact list which have been shared via iCloud. Is there security breach issue with iCloud?

    I have the same situation (there seems to be lots of emails sent through my Icloud account. I don't see those emails in my "sent" folder, but I can see plenty of email (Chinese spam emails) bounced back into my account stating that I have exceded the sending limits. I cannot send anything either from my account (of course, the sending limit is alwasy exceeded). I have also changed twice my password, but the issue remains.
    Any clues?
    I am really surprised at this. I was from the begining with .Mac, and never had any issue during all these years. This is now with Icloud, which should be safer and better  :-(

  • Grid Control emails

    Hi there,
    I need to be able to send emails from Grid Control, depending on different things that may be happening.
    Right now, emails from grid control can only be sent from one email address. Then it is not possible to differenciate what is a critical alert and what is not.
    What are my other options or can I choose more than 1 email address?
    Thanks for your time in advance!

    user13286861 wrote:
    Hi there,
    I need to be able to send emails from Grid Control, depending on different things that may be happening.
    Right now, emails from grid control can only be sent from one email address. Then it is not possible to differenciate what is a critical alert and what is not.
    What are my other options or can I choose more than 1 email address?
    Thanks for your time in advance!You can't send emails from more than one address in GC, at least not that I've been able to discern. However, the subject line will contain the word "Critical" for critical events. You can set up email filters to handle critical alerts differently than Warning alerts.
    Cheers,
    Brian

  • Grid Control 11g - OMS configuration issue

    I am installing Grid Control 11g on Linux 5. on the configuration step - OMS configuration failed. The log shows:
    INE: NMProcess: weblogic.nodemanager.common.ConfigException: The domain 'GCDomain' at '/opt/Oracle/Middleware/oms11g/user_projects/do
    mains/GCDomain' was not registered in the nodemanager.domains file and dynamic domain registration is not supported. Please register the d
    omain in the nodemanager.domains file.
    But I looked at the file: nodemanager.domains, there is an entry:
    #Domains and directories created by Configuration Wizard
    #Fri Jan 20 14:28:37 MST 2012
    GCDomain=/opt/Oracle/Middleware/oms11g/user_projects/domains/GCDomain
    So how to register GCDOMAIN?
    Please shed some lights. Thanks
    S.

    Hi Ski,
    Well the cause of this issue may vary depending on the WLS, EM GC and Oracle Critical Patch Update (CPU) that you have.
    But in general terms, you could try the following:
    1. Stop WLS
    2. copy nodemanager.domains from Middleware/wlserver_10.3/common/nodemanager to Middleware/wlserver_10.3/common/emnodemanager
    3. Start WLS (gc_inst/user_projects/domains/GCDomain/bin/startWebLogic.sh)
    4. Start nodemanager (Middleware/wlserver_10.3/server/bin/startNodeManager.sh)
    5. connect('<username>','<password>',t3://<ip address>:port')
    connect('weblogic','weblogic','t3://localhost:7001')
    6. nmEnroll([domainDir], [nmHome])
    nmEnroll('/u01/app/oracle/product/Grid11g/gc_inst/user_projects/domains/GCDomain','/u01/app/oracle/product/Grid11g/Middleware/wlserver_10.3/common/nodemanager')
    7. start OMS (Middleware/oms11g/bin> emctl start oms)
    Make sure to backup the mentioned directories accordingly before proceding with the steps mentioned above.
    Thanks,
    Cris

  • Grid control notification cannot send email for alert message.

    We have grid control work fine in sending out email. But we cannot receive it lately. I followed the note 285093.1 for trouble shooting. I found that in the file <OMS HOME>/sysman/log/emoms.log or emoms.trc of the following repeated error:
    ========================================================
    2009-03-04 16:29:40,605 [DeliveryThread-EMAIL3] ERROR threadPoolManager.WorkerThread run.281 - Exception message: null
    java.lang.NullPointerException
    2009-03-04 16:29:41,097 [DeliveryThread-EMAIL6] ERROR em.notification run.595 - Delivery.run: java.sql.SQLException: ORA-01017: inva
    lid username/password; logon denied
    java.sql.SQLException: ORA-01017: invalid username/password; logon denied
    at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:315)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:276)
    at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
    ==========================================================
    I am wondering which login of what user has the logon problem. How can I fix it?
    Thanks for any help!

    Yes, I did that in following up the metalink note 285093.1 and 356774.1. There is not broken job in the repository database for sysman. There was one before. Then I checked the emoms.trc file and saw the error ORA-01017: invalid username/password; logon denied.
    I think the problem is likely due this error, as so far I did not see any other error. On grid control, I also did repository operation => notification check and the email sending test. They are all fine without any error.
    Thanks.

  • Grid control 10g password issue

    grid control 10.2.0.5
    linux redhat 5
    I shut down grid control for a full back up.
    now when i navigate to the opening page I get:(before getting prompted for a password)
    503 Service Unavailable
    Servlet error: Service is not initialized correctly. Verify that the repository connection information provided is correct.
    so I looked in the logs at:
    $OMS_HOME/sysman/log/emoms.log
    I tested this and it happens every time I go to the page. What configuration file are passwords kept in for grid control?
    java.sql.SQLException: ORA-01017: invalid username/password; logon denied
            at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)
            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:315)
            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:276)
            at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271)
            at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:647)
            at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:312)
            at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:429)
            at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:152)
            at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:31)
            at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:608)
            at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:217)
            at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:113)
            at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPooledConnection(OracleConnectionPoolDataSource.java:76)
            at oracle.jdbc.pool.OracleImplicitConnectionCache.makeCacheConnection(OracleImplicitConnectionCache.java:1361)
            at oracle.jdbc.pool.OracleImplicitConnectionCache.getCacheConnection(OracleImplicitConnectionCache.java:439)
            at oracle.jdbc.pool.OracleImplicitConnectionCache.getConnection(OracleImplicitConnectionCache.java:334)
            at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:285)
            at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:253)
            at oracle.sysman.util.jdbc.ConnectionCache._getConnection(ConnectionCache.java:336)
            at oracle.sysman.util.jdbc.ConnectionCache._getConnection(ConnectionCache.java:322)
            at oracle.sysman.util.jdbc.ConnectionCache.getUnwrappedConnection(ConnectionCache.java:575)
            at oracle.sysman.emSDK.svc.conn.FGAConnectionCache.getFGAConnection(FGAConnectionCache.java:218)
            at oracle.sysman.emSDK.svc.conn.ConnectionService.getPrivateConnection(ConnectionService.java:1158)
            at oracle.sysman.emSDK.svc.conn.ConnectionService.getPrivateConnection(ConnectionService.java:1192)
            at oracle.sysman.eml.app.SessionObjectManager.sessionDestroyed(SessionObjectManager.java:116)
            at oracle.sysman.eml.app.SessionListener.sessionDestroyed(SessionListener.java:114)
            at com.evermind.server.http.HttpApplication.invalidateSession(HttpApplication.java:683)
            at com.evermind.server.http.EvermindHttpSession.invalidate(EvermindHttpSession.java:272)
            at com.evermind.server.http.SessionAsyncInvalidateHandler.invalidateSession(SessionAsyncInvalidateHandler.java:173)
            at com.evermind.server.http.SessionAsyncInvalidateHandler.run(SessionAsyncInvalidateHandler.java:133)
            at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
            at java.lang.Thread.run(Thread.java:534)
    2009-06-08 08:37:32,140 [AJPRequestHandler-ApplicationServerThread-14] ERROR conn.ConnectionService verifyRepositoryEx.911 - Invalid Connection Pool. ERROR = ORA-01017: invalid username/password; logon denied

    Looks like you are running GC 10.2.0.5 and I had exact same issue with it when my SYSMAN account got expired. The previous GC SYSMAN password change process didn't work for me - change sysaman's password on DB and update it on emoms.properties.
    This worked for me though:
    For 10.2.0.5 / 11.1 OMS:
    cd <OMS_HOME>/bin
    emctl config oms -change_repos_pwd -change_in_db
    Check Metalink Doc ID# 270516.1 for more details.

Maybe you are looking for