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

Similar Messages

  • Grid Control access issue after ip change

    Hi
    The ip address of the server was changed. In this server there was repisotory database and OMS.
    After that, I couldnt manage to start oms.
    When I try:
    opmnctl start all , I notice that it is hanging.
    I also cannot display Grid Control url, however I can start repisotory database successfully.
    Any recommendation?

    I had the same problem, logged a TAR and waited several weeks, only to be told to resinstall OMS. That was 2 years ago with 10.2.0.3. There may be an article now on metalink which has the process. But I agree with the previous posts, the IP address is everywhere, so it's a real pain in the proverbial.

  • Grid Control jobs issue

    Hi,
    AIX, EMR3
    Hi,
    I'm testing a job scheduling from OEM - startups and shutdowns of monitored databases.
    Immediate job execution works always, scheduled execution never works....
    Any suggestions, troubleshooting ....
    Thx,
    Dobby

    What errors do you get in the job status and what scheduled time does it show after the time has elapsed?

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

  • Switchover in a data guard environment using Grid Control 10.2.0.3

    I've tested switchover in a data guard environment using Data Guard Broker in Grid Control.
    However, at times, i receive the message "RemoteOperationException: failed to establish input streaming thread". It looks like it has problems connecting to the remote node using the host credentials supplied. I know the credentials are ok because this worked before. If i test preferred credentials, it's ok too..
    The workaround has been to restart the database and this seems to work.
    Has anyone experienced this?

    Thanks for All for replying.
    *1. How can I upgrade my Grid control 10.2.0.3 to 10.2.0.4?*
    I have upgraded the Grid Control Agent and OMS from 10.2.0.3 to 10.2.0.4
    When we upgrade the OMS which also upgrade the Repository database.
    Apply the patchset p3731593_10204_Linux-x86-64.zip (Which comes with Grid_Control_10.2.0.4.0_Linux-x86-64.zip)
    su - oracle
    cd 3731593/Disk1
    ./runInstaller (Run two times for Agent and oms upgrade)
    Agent upgrade_
    During upgrade
    Specify Home Details: Select the Agent Home to upgrade Grid Control Agent.
    Ex: /u01/app/oracle/OracleHomes/agent10g
    OMS upgrade+
    Specify Home Details: Select the oms home to upgrade oms
    Ex: /u01/app/oracle/OracleHomes/oms10g
    *2. How can I monitor/Connect my Existing database 10.2.0.4 from Grid Control 10.2.0.3?*
    Install Grid Agent on the existing database server 10.2.0.4
    Download Linux_x86_64_Grid_Control_agent_download_10_2_0_4_0.zip from OTN http://www.oracle.com/technology/software/products/oem/htdocs/agentsoft.html
    su - oracle
    cd /u01/software/GridAgent/linux_x64/agent
    ./runInstaller
    Refer:
    [To Install an Additional Management Agent Using OUI|http://download.oracle.com/docs/cd/B16240_01/doc/install.102/e10953/installing_em.htm#sthref318]
    Oracle® Enterprise Manager Grid Control Installation and Basic Configuration
    10g Release 4 (10.2.0.4)
    Part Number E10953-05
    3 Installing Enterprise Manager
    Thanks
    Mukarram Khan
    Edited by: Mukarram Khan on Feb 6, 2009 11:04 PM

  • 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

  • Would Grid Control be able to initiate a switchover ?

    Hi,
    I want to install and use 10g Grid Control. I have a Dataguard Configuration with an primary and a standby physical, managed by a Data Guard Manager.
    I would like to know if Grid Control would be able to make a switchover to the standby if the primary fails unexpectedly.
    Regards,
    Christian.

    Please follow the doc
    http://www.oracle.com/technology/deploy/availability/pdf/MAA_WP_10gR2_EnterpriseManagerBestPractices.pdf

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

  • 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

  • Weblogic 10.3.2 Smart Update / Grid Control 11.1.1

    I'm implementing a new Grid 11.1 environment on a linux x86_64 platform. I've installed everything including weblogic 10.3.2 with the default options. (required for grid control installation). The problem is.... now I have to patch the 10.3.2 weblogic server.. BUT it doesn't have the smart update utility installed... in other words .. there isn't any BEA_HOME/utils directory. Much less a bsu.sh script to launch the patching process.
    Has anyone ran into this before? I am new to weblogic and have never used the product. Thanks

    Somehow the installation got split. Part when in the /u01 and the other went in the home path of the user. never had that to happen before. I ended up uninstalling and reinstalling to correct the issue. Thanks

  • Want Access Data Grid control in SharePoint 2013?

    Hello everyone!
    Recently we noticed something funny in SharePoint 2013. While quite many people were hoping to have the datasheet view like those in SP2007 and 2010, Microsoft has chosen a different interface to display datasheet view.
    Now, if you try to create a sub site under a publishing site, and use the
    Publishing Site template then try to create a datasheet view in the sub site, SharePoint will try to use the Access data grid control to display the view. In some situations the view will display and other situations it will not, and will show this
    error:
    The list is displayed in Standard view. It cannot be displayed in Datasheet view for one or more of the following reasons: A datasheet component compatible with Microsoft SharePoint Foundation is not installed, your browser does not support ActiveX controls,
    a component is not properly configured for 32-bit or 64-bit support, or support for ActiveX controls is disabled.
    If you create a sub site using Publishing Site with Workflow instead, then the datasheet view will be created properly using SP2013 interface.
    Using PowerShell, we can see that both Publishing Portal and
    Publishing Site With Workflow are using the BLANKINTERNET 53 template. The
    Publishing Site on the other hand is using the CMSPUBLISHING 39 template.
    Want to try it out and let me know if that happens to your SharePoint too?

    Hi Conway,
    I tested the issue in my environment per your description and it returned the results as below:
    I created a subsite using Publishing site under a team site in SharePoint server 2013, the datasheet view in a list displayed as pic1
    I reproduced the issue in SharePoint server 2010, the datasheet view in a list displayed as pic2
    It turns out by design the datasheet view in the subsite based on Publishing site template displays as your situation. Here is an article which explains this:
    http://www.sharepointblues.com/2010/03/31/data-sheet-view-not-working/
    Regards,
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
    [email protected] .
    Rebecca Tu
    TechNet Community Support

  • Listener & grid control after upgrade to 11.1.0.7

    going from 10.2.0.2 to 11.1.0.7 on aix 5.3
    On our test server we have about 8 databases that are all currently using the 10.2 listener. I've upgraded one of our very basic test databases to 11g this morning, and for the time being just created a new listener11g that listens to different port. when I start it, the log file is being created in ORACLE_BASE/diag/tnslsnr/<server>/<lsnrname>/alert/ instead of the default ORACLE_HOME/network/logs I didn't tell it to create the listener log there, anyone else have this issue?
    Also, my databases are all currently being monitored by OEM Grid Control and NOT DB Control. What steps should I take to get that running correctly again after the upgrade? Delete the target database and add it back after the upgrade? Sorry ahead of time if there is a meta-link doc for this, I've searched briefly and came up empty handed.
    Thanks,
    Ben Alvey

    well, from what I read about the ADR architecture it wasn't clear that the listener log would move. the metalink documents for the listener log still state that the default log directory is ORACLE_HOME/network/log as well.
    And seeing how I supplied a different value for diagnostic_dest during the upgrade of said database it didn't make much sense to me how it came to the decision to stick it where it did. I'd say it is using the value from $ORACLE_BASE during the install.
    It would be helpful if their docs didn't contradict themselves constantly.

Maybe you are looking for