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.

Similar Messages

Grid control design and agent deployment

To give you a brief overview of the setup here, it is currently an agent per instance instead of an agent per host. This was done to allow an agent to be moved along with an instance to another host in a cluster (we are using IBM AIX LPAR, and Sun Clustering) thereby allowing a seamless transition between hosts and history retention for the instance. We would like to change this to an agent per host, however, we need to keep the historical information of the instance should it change hosts. So my questions are:
1. Is it possible using some sort of script or process to have an instance/target move between hosts and retain its previous historical information?
2. Is it possible to have a single, summarized availability report for all instances? The report per instance works, however, doing a single summary report for all instances does not display the correct information (it only shows PIT, i.e. the current state of the instances not historical over x period of time).
Any help is appreciated.
Thanks.

Let me provide some details as to the environment as to the deployment which I am doing in a HA environment:
- There is a physical 'myhost1' with virtual hosts names oradev1, oratst1. Note I am not referring to virtual machines, just virtual host names, or virtual IP.
- Each VIP hosts a listener and database instance. For example, oradev1 -> lsnr-oradev1 + orad1, and oratst1 -> lsnr-oratst1 + orat1
In this design each database and listener can be moved to another physical host separate from the other, say the entire oradev1 stack moves to 'myhost2'.
How would the agents be deployed in such a design? I think an agent per physical host, with the VIP used to monitor the virtual stacks, such has as each virtual host containing the listener and database instance. This way when a virtual stack moves we can just switch the agent monitoring that stack to the new host and retain the history of the targets.
Is my thinking correct? Is there a better way to retain the history when moving the virtual stacks perhaps doing an agent per instance instead of physical target?
I hope this provides more details. Thanks.

Issues after upgrading to 10.2.0.4 ( both OMS and Agent)

All,
we are observing this error quite a lot after upgrading to 10.2.0.4 ( both oms and agent)
2008-07-31 15:08:19,088 Thread-228 ERROR : (nmevrr.c,328):Memory 0x0 encountered, expect struct_id=12201
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:snmeuctx_setGenCtx+0x912
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nme_class_error+0x184
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmevrr_Recvlet_refreshState+0x264
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmevrg_RegisteredRecvlet_refreshState+0x228
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmevrm_RecvletManager_init+0x5544
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmecmgr_discardState+0x1792
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmecmgr_discardState+0x376
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmemdisp_GetMetric+0x10212
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmemdisp_GetMetric+0x15664
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmehl_disabled_remote_ops+0x2600
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmttprutc_reconfigUsingTargetCount+0x448
/u1/app/oracle/product/10.2.0/agent10g/lib32/libnmemso.so:nmttprutc_reconfigUsingTargetCount+0x596
/lib/libc.so.1:_thr_slot_offset+0x1132
we have these patches 7012242,7031906,5961654,5632264 installed on the agent home.
I have also disabled the instance health metrics for all the 10g target db on this host.
Anybody has any idea how to resolve this . This is becoming quite annoying .
thanks in advance
pk

Hi,
Just to comfort you, and yes we do monitor 10.2.0.3 instances. This comes from the emagent.trc on one of many rdbms server. The same is not found on other servers running 10.2.0.3 instances. The time coincide with an agent crash on this server. Keeping an eye on this thread while trying to find out what it is related to.
EDIT: This is due to bug 7012242, see metalink docId: 579137.1
2008-08-15 05:30:03,081 Thread-689845 ERROR : (nmevrr.c,328):Memory 0x0 encountered, expect struct_id=12201
/oracle/product/agent10g/lib32/libnmemso.so:snmeuctx_setGenCtx+0x912
/oracle/product/agent10g/lib32/libnmemso.so:nme_class_error+0x184
/oracle/product/agent10g/lib32/libnmemso.so:nmevrr_Recvlet_refreshState+0x264
/oracle/product/agent10g/lib32/libnmemso.so:nmevrg_RegisteredRecvlet_refreshState+0x228
/oracle/product/agent10g/lib32/libnmemso.so:nmevrm_RecvletManager_init+0x5544
/oracle/product/agent10g/lib32/libnmemso.so:nmecmgr_discardState+0x1792
/oracle/product/agent10g/lib32/libnmemso.so:nmecmgr_discardState+0x376
/oracle/product/agent10g/lib32/libnmemso.so:nmebb_uploadTargetState+0x928
/oracle/product/agent10g/lib32/libnmemso.so:nmebb_updateBlackoutInfo+0x384
/oracle/product/agent10g/lib32/libnmemso.so:nmesse_executeWork+0x132
/oracle/product/agent10g/lib32/libnmemso.so:nmttprutc_reconfigUsingTargetCount+0x448
/oracle/product/agent10g/lib32/libnmemso.so:nmttprutc_reconfigUsingTargetCount+0x596
/lib/libc.so.1:_thr_slot_offset+0x1128
Message was edited by:
ivirnig

OMS and Agent Communication Problem?

Hi
All
I have installed OMS that have version 10.2.0.2 on windows server and Agent with version 10.1.0.4 on AIX.
Is it any problem with version of OMS and Agent?
Thanks,
Vishal

Sorry To ask question again. but I have read 412431.1 doc and it satisfy requirement. After reading that I proceed with installation but somehow I m getting this output
$ emctl status agent
Oracle Enterprise Manager 10g Database Control Release 10.2.0.2.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
Agent Version : 10.1.0.4.1
OMS Version : Unknown
Protocol Version : 10.1.0.2.0
Agent Home : /u07/app/oracle/product/10.2.0/moe.wsi_OWSIDEV
Agent binaries : /u07/app/oracle/product/10.2.0
Agent Process ID : 290972
Parent Process ID : 458882
Agent URL : http://moe.wsi.:3938/emd/main
Started at : 2007-10-10 14:58:20
Started by user : oracle
Last Reload : 2007-10-10 14:58:20
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 2459
Size of XML files pending upload(MB) : 24.56
Available disk space on upload filesystem : 36.92%
Agent is Running and Ready
and Here it's says OMS version is unknown So I dont' know what's going on here.
Thanks,
Vishal

Reg oms and agent versions

Hi,
I have enteprise grid 10.2.0.5
what my question can the oms and agent can be different versions
like oms is 10.2.0.5
agent is 10.2.0.3
thanks

Use metalink article: 412431.1 as a reference to know which versions are certified.
If you OMS is 10.2.0.5, you shold upgrade your agent to 10.2.0.5 as well.

ORACLE GRID OMS and agent service issue..

Dear all,
i am a solaris admin..please help me .. I am facing problem in discover oracle database through oracle agent...
We installed oracle DB 10g R2 in solaris standalone server ..we have install OMS .. hostname is hostname01
We have install OMS client at windows server in some domain host.domain.com
Is it possible to install and configure OMS and Client in non domain [dns] environment?
because we can able ping ip address from windows to solaris and vice vesa...
but i can't able to nslookup..because sun server not in that domain... nslookup only search at DNS server ...
it wouln't resolve hostname to ip address...
what is procedure to configure in OMS and client in non -DNS environment??

update the hosts file on all (client, OMS server, db server) sides to be able to ping by name from any server.
eg.
solaris /etc/hosts
10.121.121.3 <servername>.<domian> <alias>
retry your ping test by name.

How do you change Host Domain in Grid Control (OMS)

Background:
Grid control is all installed on one server (AGENT, REPOSITORY, and OMS).
Beside reintalling Grid Control, is there another method of changing the host domain in OMS?

Recreate the Grid Control repository, update required config files.

Database Grid Control 10g and Oracle 8i v.3....

Hi ,
Is it possible for Database Grid Control 10g to administer and monitor the Oracle 8i v.3, namely Oracle 8.1.7. database ...?????
Many thanks ,
Simon

Yes, that is possible. We are using OMS 10.2.0.2, Agents 10.2.0.2 to monitor 8.1.7.4 Databases.
Also check MetaLink Notes:
377462.1 - ORA-00942 When Trying To View Tablespaces For An 8.1.7.4 Database
373394.1 - Receiving ORA-1031 When Gathering Metrics Against 8.1.7.4 Database From Grid Control 10.2
Regards,
Martin

10gR2 Grid Control with previous Agents?

I have 10gR2 Grid Control installed on a Linux Server. I want to use it to create a DataGuard standby database. The issue is that the primary database is 10gR2 on a HP-UX server using ASM and the standby database will also be 10gR2 on a HP-UX server using ASM. Will the 10gR2 Linux Grid Control be able to handle this since the agent on the primary will be 10.1.0.4? Note: 10gR2 is available for HP-UX but 10gR2 Grid Control is not yet available so that is why I have 10.1.0.4 agent.

Yes , it is able to handle

Grid Control 11GR1 and Weblogic Server

Am looking doing a new install of grid control 11gR1 on windows server 2008. I'm not all that familiar with the weblogic server. Can this be installed on the same server that Grid Control is running from?

Hello,
I'm not all that familiar with the weblogic server. Can this be installed on the same server that Grid Control is running from?Yes, you can. For OEM Grid Control 11gR1, you'll have to install WLS 10.3.2 and apply the Patch WDJ7.
You'll have more details on the following Notes of My Oracle Support:
How to Install Web Logic Server 10.3.2 for Installing 11g Grid Control [ID 1063762.1]
How to Download and Apply recommended WLS patch (WDJ7) on WLS home for 11g Grid Control Install/Upgrade [ID 1072763.1]Hope this help.
Best regards,
Jean-Valentin

How much Maximum Distance I would keep between Oracle EM OMS and Agent ?

Hello There,
Here I am asking little curious question which come in my mind ?
Actually We have many client geographically located in different cities.And we are remotely managing their databases on VPN.
I just wanted to Install One Enterprise Manager Grid control for all these databases.
Here I assume we have 10Mbps Line between our head quater and Clients.
And regular agent upload max 1.5GB per month for each client.
Is it possible ?
If possible how much max distance(miles) do you recommended.
Thanks
Hemesh.
Edited by: Hemss on Jan 28, 2011 5:14 PM

Hi Hemesh,
are you sure that 2 GB of data are uploaded with every heartbeat? The best idea to figure out would be - from my point of view - just to test
it. Otherwise you will not get any feeling for the upload amount and upload time...

Grid Control 10g and Ports

Hi,
Using EM Grid Control 10g, what ports are required to be opened on a firewall to enable communication between the GC Agent and the Management Server (for either insecure or secure mode)?
Thanks in advance
regards
Manoj

Have a look at $ORACLE_HOME\install\portlist.ini for the ports in use for your installation.
By Default, it uses the non-secure port of 4889 which I do not think requires opening.

Grid Control 12c and high availability databases

Hello,
In the context of high availability databses, my configuration is as follow:
2 AIX servers on 2 sites with shared storage -> Site1 and site2.
During normal operations databases are on site1. In case of disaster, databases can fallover on site2.
On my Grid Control, 2 agents are installed: One for AIX on site1 and one for AIX on site2.
Databases have been discovered on AIX:site1
Listener is a virtual address and can also fallover.
What are the possibility on the grid side ?
Do I have to discover also the databases on site2 ?
Actually, Listener is seen down on the site who has not the databases.
Is there a way to only configure the Listener virtual address on the Grid ?
Regards

Hi,
Basically you have to relocate the targets to the new agent (the one installed on site2). I haven't done that, but I expect to work fairly easy and smooth. Refer to the following section of Cloud Control 12c manual:
Configuring Targets for Failover in Active/Passive Environments
Regards,
Sve

Dreamweaver CC fluid grid controls disappearing and other info

Hi All,
I have finally completed my first commercial fluid grid design in Dreamweaver CC and it was a bit of a mission.
One disconcerting thing about the program is that the fluid grid controls keep disappearing. You know, the ones where you can hide the div, duplicate it, move it up or down, or delete it.
I have found that when this happens, I need to close the html file I am working on in DW CC and then open it again. The controls then appear again, so you can rearrange your various layouts as demonstrated in those breezy demo videos about DW CC fluid grid layouts.
So don't just conclude you have broken the code when these controls disappear, try closing and opening the file again first.
Also you need to insert all the divs you need for all layouts in the mobile phone layout, as that is the main layout, governing all the others because of the way the media queries are set up in the CSS file that is created when you start your fluid grid layout.
I could not work out how to reorder divs in the different layouts, this may not be possible at the moment. Instead I created divs in the phone layout to cover all of the divs needed in the three layout sizes and switched them off and on in the various layouts. This works really well, but I found that DW behaved strangely if I switched a div off in the mobile layout and then tried to style it in one of the other layouts. So I suggest styling all of the divs first for all the layouts before switching any of them off in the mobile layout.
Also you can't copy the contents of one div and put them in another without freaking the program out, especially if you are working in a div that is hidden in the mobile layout.
I suggest saving regularly as you add new divs and style them and view live in a browser immediately, as the preview in DW CC is not reliable. It can't show rounded div corners or shadows for example.
Keep an eye on the code as it is built by your use of the CSS Properties panel. If it starts going wrong, close the html file without saving it or the attached CSS file. Then go back in and try what you want to do again.
If you save weird code errors, your work could be so compromised that you need to start all over again. So quit out without saving if you notice this.
After much experimentation I now insert images into a div, rather than make them a background image, as the background image will not completely show if the content of the div is not long enough. This may require a rethink of your design.
Doing any absolute sizes in a div will make the responsive design very hard to style and possibly break the code, so I don't suggest it.
Adding padding to a div can make it stick out of right edge of the design, I am not sure why this is the case and could not work out how to stop it. So use low pixel numbers in the padding of a div.
Also control z seems to be a sudden death move, so I stopped doing that.
So my first job has been a bit of a ride, but I seem to be nearly there on my first design.
I think DW CC is still a work in progress and I look forward to further updates of the software.

Hi Top Ten,
You can't get them back once they go. You now need to edit the css code manually to do the same thing.
For instance if you want divs to sit beside each other you put this in the css for that div:
clear: none;
This css means that div will allow other divs to sit beside it.
Then put in a width in percentages. For example if you have three divs that need to sit beside each other put:
width: 33%;
in each of them. Or maybe:
width: 31%;
margin-right: 2%;
Fortunately in DWCC it is now robust enough for you to do those code changes by hand. My original question in this thread was posed when DW CC fluid grid had just come out and crashed easily. A year later all is well, so you can do those changes in the css code without problems now.
Regards,
Mary

Grid Control compatibility with Agent

Hi
I have Oracle Enterprise Manager version 10g Grid Control (10.2.0.5.0), will I be able to install Oracle Management Agent 11.1.0.1.0?
Thanks in advance.

user10898027 wrote:
Hi
I have Oracle Enterprise Manager version 10g Grid Control (10.2.0.5.0), will I be able to install Oracle Management Agent 11.1.0.1.0?Yes ... you can do this .. It is certified.
MOS note :
Oracle Enterprise Manager Grid Control Certification Checker *[ID 412431.1]*
Regards
Rajesh

Patching Grid Control OMS and Agent to 10.2.0.5 issue

Similar Messages

Maybe you are looking for