Grid Control 에서 새 target node를 추가한 이후에 기존OMS와 새 Agent 간의 HeartBeat fail 해결방
Grid Control 에서 새 target node를 추가한 이후에 기존OMS와 새 Agent 간의 HeartBeat fail 해결방법
=========================================================================
다음은 Grid Control 을 설치한 이후에 node를 관리해 오다가 새로운 관리할 Target node를
추가한 이후에 Grid Control 이 있는 node의 OMS와 새로 추가한 node의 Agent가 HeartBeat 통신
실패 시에 해결책을 소개하고 있습니다.
Problem Description
Grid Control 에서 새로운 node를 추가한 다음에 그 새로운 node 에서
emctl status agent 명령 수행 시 다음과 같은 에러가 발생합니다.
Environment :
mesdev01 : 새로 추가한 Agent가 있는 node명
mesdev02 : 'Central Grid Agent' 존재 & 'Repository database가 존재하는 node'
새로 추가한 node에서 아래와 같이 emctl status agent 명령을 수행합니다.
그런데, OMS에 대한 HeartBeat fail 이 발생했음을 알 수 있습니다.
[mesdev01:/oracle/app/oracle/product/agent10g/bin] emctl status agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.3.0
OMS Version : 10.2.0.3.0
Proto Version : 10.2.0.2.0
Agent Home : /oracle/app/oracle/product/agent10g
Agent binaries : /oracle/app/oracle/product/agent10g
Agent Process ID : 10526
Parent Process ID : 10511
Agent URL : http://mesdev01:3872/emd/main/
Repository URL : http://mesdev02:4889/em/upload/
Started at : 2007-12-28 10:36:59
Started by user : oracle
Last Reload : 2007-12-28 10:36:59
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 287
Size of XML files pending upload(MB) : 26.40
Available disk space on upload filesystem : 40.44%
Last attempted heartbeat to OMS : 2007-12-28 14:13:36
Last successful heartbeat to OMS : unknown <===
여기서 주목할 만한 에러는 Last successful heartbeat to OMS 체크 시 status가
unknown 으로 보인다는 것입니다.
에러 증상
emctl status agent 수행 시 Last successful heartbeat to OMS : unknown
또는 agent 에서 OMS의 Status를 알 수 없다는 아래의 에러가 보이는 경우임.
Note: "The OMS status is Unknown"
Explanation
이러한 에러는 주로 agent가 node에 새로(newly) install 된 경우 발생합니다.
원래 communication 이 정상적으로 보인다면 다음과 같이 수행 결과가 나와야 합니다.
다음은 Repository database가 존재하는 mesdev02 node에서 emctl status agent를 수행한 결과
성공적으로 보이는 결과입니다.
mesdev02:/u01/app/oracle/OracleHomes/agent10g/bin$ emctl status agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.3.0
OMS Version : 10.2.0.3.0
Proto Version : 10.2.0.2.0
Agent Home : /u01/app/oracle/OracleHomes/agent10g
Agent binaries : /u01/app/oracle/OracleHomes/agent10g
Agent Process ID : 29307
Parent Process ID : 29300
Agent URL : https://mesdev02:3872/emd/main/
Repository URL : https://mesdev02:1159/em/upload
Started at : 2007-12-27 11:29:22
Started by user : oracle
Last Reload : 2007-12-27 17:57:18
Last successful upload : 2007-12-28 15:02:09
Total Megabytes of XML files uploaded so far : 48.78
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 38.29%
Last successful heartbeat to OMS : 2007-12-28 15:02:59 <====
Agent is Running and Ready
원인
이 에러가 발생하는 원인은 새로 추가한 database의 Agent process가 GRID Control 이
install된 main server의 OMS와 연결되지 않기 때문인데, 이렇게 새로운 node를 추가한 이후에
수행해줘야 할 절차가 있습니다.
OMS_HOME/sysman/log 의 secure.log 를 확인해 보면 OMS is "secure locked" 라는 에러가 보입니다.
The OMS is "secure locked", then the agent also needs to be secure.
[ 사전 check 사항 ]
1. 두 node 모두 DNS server에 등록되어 있는지 확인한다.
2. 두 node 모두 쌍방 간에 /etc/hosts file에 서로의 ip address와 hostname을 넣어준다.
위 두가지 check 사항이 충족된 경우에도 발생한다면 새로 추가한 node 쪽에서 자신의 정보를
OMS(즉, Repository node) 에게 정보를 upload하지 않았기 때문입니다.
Upload를 하는 방법은 간단하게 아래와 같은 emctl upload agent 라는 명령으로 가능합니다.
emctl upload agent
Upload를 하게 될 때 그 정보는 XML 형태로 중앙 Repository에 저장됩니다.
Solution Description
아래 절차 중에 1번만 Grid Control이 설치된 OMS server에서 수행을 하고,
2번~7번까지는 새로 추가한 Agent node에서 수행합니다.
1. On oms server: (Grid Control 이 설치된 서버에서 수행)
<OMS_HOME>/bin/emctl status oms -secure
OMS node인 mesdev02 node에서 우선 emctl status oms -secure 를 수행합니다.
mesdev02:/u01/app/oracle$$OMS_HOME/bin/emctl status oms -secure
Oracle Enterprise Manager 10g Release 3 Grid Control
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Checking the security status of the OMS at location set in /u01/app/oracle/OracleHomes/oms10g/sysman/config/emoms.properties... Done.
OMS is secure on HTTPS Port 1159
2. Stop Agent: Agent를 설치한 node에서 수행합니다.
<AGENT_HOME>/bin/emctl stop agent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl stop agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Stopping agent ... stopped.
3. Verify no residue emagent processes running:
이와 같은 명령으로 남아 있는 emagent process가 있는지 확인합니다.
ps -ef|grep emagent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]ps -ef|grep emagent
oracle 4353 3125 0 16:19:34 pts/tb 0:00 grep emagent
4. If running secure please resecure agent on :
<AGENT_HOME>/bin/emctl secure agent
emctl secure agent 를 수행하는 목적은 모든 agent에 대해서 secure communication 을
하기 위해 필요합니다.
[ 주의사항 ]
emctl secure agent 명령은 Grid Control installation 과정에서
--> 'Specify Security Options' 단계에서
--> Management Service Security 항목에서
--> OMS와 함께 Secure Communication을 하고자 하는 agent에 password 설정을 하는데,
--> Require Secure Communication for all agents 를 check 표시하였다면
install 이후에 아래와 같이 emctl secure agent 명령을 수행하여야 합니다.
(기본적으로 Require Secure Communication for all agents는 enable되어야 함).
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl secure agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Enter Agent Registration password :
Agent is already stopped... Done.
Securing agent... Started.
Requesting an HTTPS Upload URL from the OMS... Done.
Requesting an Oracle Wallet and Agent Key from the OMS... Done.
Check if HTTPS Upload URL is accessible from the agent... Done.
Configuring Agent for HTTPS in CENTRAL_AGENT mode... Done.
EMD_URL set in /oracle/app/oracle/product/agent10g/sysman/config/emd.properties
Securing agent... Successful.
5. 4번 단계가 정상적으로 완료되면 이제 Agent를 기동합니다.
Start Agent
<AGENT_HOME>/bin/emctl start agent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl start agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Starting agent ................................. started but not ready.
6. Then verify upload works
<AGENT_HOME>/bin/emctl upload agent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl upload agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
EMD upload error: Upload timedout before completion
==> timedout 메시지는 warning으로 보이며, 운영에는 지장이 없습니다.
7. 다시 확인 차 emctl status agent 명령을 수행해 봅니다.
Then run status of agent
<AGENT_HOME>/bin/emctl status agent
[mesdev01:/oracle/app/oracle/product/agent10g/bin]./emctl status agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.3.0
OMS Version : 10.2.0.3.0
Proto Version : 10.2.0.2.0
Agent Home : /oracle/app/oracle/product/agent10g
Agent binaries : /oracle/app/oracle/product/agent10g
Agent Process ID : 4618
Parent Process ID : 4609
Agent URL : https://mesdev01:3872/emd/main/
Repository URL : https://mesdev02:1159/em/upload
Started at : 2008-01-02 16:21:03
Started by user : oracle
Last Reload : 2008-01-02 16:21:03
Last successful upload : 2008-01-02 16:25:37
Total Megabytes of XML files uploaded so far : 54.28
Number of XML files pending upload : 40
Size of XML files pending upload(MB) : 0.97
Available disk space on upload filesystem : 37.22%
Collection Status : Disabled by Upload Manager
Last successful heartbeat to OMS : 2008-01-02 16:24:49 <== success!
Agent is Running and Ready
[mesdev01:/oracle/app/oracle/product/agent10g/bin]
8. 만약 Last successful heartbeat to OMS 에 위와 같은 success로 보이지 않으면
step 1부터 7까지 수행된 모든 output 을 수집하여 문의를 합니다.
9. 그리고, debugging을 위해 다음의 log 화일들을 보관하시기 바랍니다.
<OMS_HOME>/sysman/log
<OMS_HOME>/sysman/log 의 secure.log가 특히 중요합니다.
<AGENT_HOME>/sysman/log
References
Note 458033.1
Title:Problem: Agent Upload Fails: OMS Is Locked and Agent not Secured
Similar Messages
-
EM Grid-Control - Targets - Hosts - HOME - Open Telnet Session
Hello,
under
EM Grid-Control ->Targets -> Hosts -> HOME -> Open Telnet Session
i can possibly open a telnet session.
Can i change this to open a ssh session and how ?
regards
FrankSorry, Simple answer 'No'
-
Grid Control on SLES11, OMS fails
Hello,
I'm trying to get grid control 11g installed on SLES11. Here's the log portion for the OMS configuration part:
Jul 29, 2010 4:06:28 PM oracle.sysman.omsca.util.CoreOMSConfigAssistantUtil execCommand
INFO: error messages of the command :
Jul 29, 2010 4:06:28 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Done Executing the command...0
Jul 29, 2010 4:06:28 PM oracle.sysman.omsca.framework.OMSGenericAdapter deleteAddOnInventory
INFO: Invoking deleteAddOnInventory for oms EMGC_OMS1
Jul 29, 2010 4:06:28 PM oracle.sysman.omsca.framework.OMSGenericAdapter deleteAddOnInventory
INFO: Deleting plugin inventory for GCDomain_EMGC_OMS1
Jul 29, 2010 4:06:28 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Stopping WebTier
Jul 29, 2010 4:06:33 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Stopped WebTier successfully.
Jul 29, 2010 4:06:33 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Cleaning up instance directory: /home/oracle/Oracle/gc_inst/user_projects
Jul 29, 2010 4:07:32 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Cleaning up instance home directory: /home/oracle/Oracle/gc_inst/em
Jul 29, 2010 4:07:42 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Succesfully deleted the oms
Jul 29, 2010 4:07:42 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterCleanup
FINE: The value of infra setup completion is :true
Jul 29, 2010 4:07:42 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterCleanup
FINE: Cleaning the OMS from the repository
Jul 29, 2010 4:07:42 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterCleanup
FINE: Got the Host URL as: null
Jul 29, 2010 4:07:42 PM oracle.sysman.omsca.framework.OMSGenericAdapter postDeployAndReposSetup
SEVERE: OMSCA-ERR:Securing of OMS failed. Check the trace file:/home/oracle/Oracle/Middleware/oms11g/cfgtoollogs/omsca/omsca_20100729155723.log
Jul 29, 2010 4:07:42 PM oracle.sysman.omsca.framework.OMSCAFreshInstall execute
SEVERE: Securing of OMS failed.
Jul 29, 2010 4:07:42 PM oracle.sysman.omsca.framework.OMSConfigAssistantDriver main
FINE: Got resultfalse
I've seen a few posts with similar errors. I've also tried using WebLogic 10.3.2 as some of the posts have suggested, yet I'm getting the same errors.
I know during the GC install it states SLES11 is not "certified". Could this be the reason?
Should I try GC10g, or use RHEL to get this product to work?
Thanks,
-MikeHi rob ... its very confusing ....
that are the last lines from that logfile itself ..
tail -n 30 /opt/oracle/Middleware/oms11g/cfgtoollogs/omsca/omsca_20100805143916.log
Aug 5, 2010 4:08:11 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Done Executing the command...0
Aug 5, 2010 4:08:11 PM oracle.sysman.omsca.framework.OMSGenericAdapter deleteAddOnInventory
INFO: Invoking deleteAddOnInventory for oms EMGC_OMS1
Aug 5, 2010 4:08:11 PM oracle.sysman.omsca.framework.OMSGenericAdapter deleteAddOnInventory
INFO: Deleting plugin inventory for GCDomain_EMGC_OMS1
Aug 5, 2010 4:08:16 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Stopping WebTier
Aug 5, 2010 4:08:52 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Stopped WebTier successfully.
Aug 5, 2010 4:08:52 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Cleaning up instance directory: /opt/oracle/gc_inst/user_projects
Aug 5, 2010 4:09:29 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Cleaning up instance home directory: /opt/oracle/gc_inst/em
Aug 5, 2010 4:09:30 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterDeleteOMS
FINE: Succesfully deleted the oms
Aug 5, 2010 4:09:30 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterCleanup
FINE: The value of infra setup completion is :true
Aug 5, 2010 4:09:30 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterCleanup
FINE: Cleaning the OMS from the repository
Aug 5, 2010 4:09:32 PM oracle.sysman.omsca.adapter.wls.OMSWLSAdapter adapterCleanup
FINE: Got the Host URL as: null
Aug 5, 2010 4:09:32 PM oracle.sysman.omsca.framework.OMSGenericAdapter postDeployAndReposSetup
SEVERE: OMSCA-ERR:Securing of OMS failed. Check the trace file:/opt/oracle/Middleware/oms11g/cfgtoollogs/omsca/omsca_20100805143916.log
Aug 5, 2010 4:09:32 PM oracle.sysman.omsca.framework.OMSCAFreshInstall execute
SEVERE: Securing of OMS failed.
Aug 5, 2010 4:09:32 PM oracle.sysman.omsca.framework.OMSConfigAssistantDriver main
FINE: Got resultfalse
*T -
Grid Control 10.2.0.5 patchset fails for 11g repository database
Installing GridControl 10.2.0.5 on Windows 2003 Server SP2. Initial install successful of 10.2.0.2 using existing database 11.1.0.7. The database was created new to use for GC. Patchset no problems until Configuration Assitant step "Repository Upgrade" failed with errors:
rem Copyright (c) 1999, 2009, Oracle. All rights reserved.
oracle.sysman.emcp.oms.RepositoryPatchUpgrade -verbose
oracle.sysman.emcp.oms.OmsPatchUpgrade -configureOms
oracle.sysman.emcp.aggregates.ConfigPlugIn
oracle.sysman.emcp.oms.StartOMS -configureOms
oracle.sysman.emcp.oms.EMCLISetup
oracle.sysman.ccr.configCCR.ConfigCCRPlugIn
oracle.sysman.ccr.configCCR.ConfigRepeaterPlugIn
Tried to find cause of errors and cannot seem to understand why this step failed.
Considering uninstalling GC and Oracle 11g and reinstalling GC with "new database" option.
Anyone successful at installing GC 10.2.0.5 with an 11g database?
Thank you,
Curt Swartzlander
DBA10.2.0.5 Database is in extended support. Make sure to purchase the licensing.
You need to download the software by logging an SR with Oracle support to get delivered as DVD or through e-delivery.
But I would suggest you to upgrade to 11.2.0.3.
Upgrading 10g Grid Control repository database is doing a normal database upgrade.
References:
http://docs.oracle.com/cd/B19306_01/server.102/b14238/toc.htm
How to upgrade a 10.1.0.X or 10.2.0.X Repository Database for Grid Control 10.2.0.4/5 to a Version 11.1.0.X Database (Doc ID 399520.1)
HTH
Mani -
OEM Grid Control Release (not just agent) for Solaris x86?
I see management agents that can be downloaded off of OTN, but is there an official release of Grid Control for Solaris on x86?
"Oracle Enterprise Manager 10g Grid Control *Release 5* (10.2.0.5) for Solaris Operating System *(SPARC)*"
"Oracle Enterprise Manager 10g Grid Control *Management Agent Release 1* (10.1.0.3) for Solaris *x86*"Please throw me some more meat on that bone. I'm still waiting for my Metalink access. (i.e., can you cut and paste the note text onto this forum message.)Sharing(Cut&Paste) Metalink Notes is not legal.
Oracle has no plans for 10.2.0.4 and for 10.2.0.5 it's expected by Q3 on x86(32&64) -
Why Grid control will mis-judge agent state and send mail notifications?
Sometime grid control will send mail notifications while the agent is still up.No log about network problems occur.So what about the root cause for this kind of issue?Has anyone falled into the same situation?And how to resolve?
Thanks!Which alert are you getting?
-
Installing Grid Control 10g Release 1 - Memory Check Fails
Hi to all,
I'm trying to install the Grid Control 10g on a Red Hat Enterprise Linux AS release 4 . I have configured the Computer OK , but when I try to install the Grid Control, the OUI says that the system only has 1 MB of RAM. The computer has 2 GB and only 150 MB is being used, what is the problem? what can I do?
Thanx for all.
P.D.: Sorry for my English.Hi!
Those are my kernel parameters:
kernel.sem = 256 32000 100 142
kernel.shmmni = 4096
kernel.shmall = 2097152
kernel.shmmax = 2147483648
fs.file-max = 206067
net.ipv4.ip_local_port_range = 32768 65000
net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144
And those are the Kernel Parameters Requirements:
Red Hat Enterprise Linux 4.0
semmsl = 250
semmsl2 = 250
semmns = 32000
semopm = 100
semmni = 128
shmmax = 536870912
shmmni = 4096
shmall = 2097152
filemax = 65536
ip_local_port_range = 1024 65000
rmem_default = 262144
rmem_max = 262144
wmem_default = 262144
wmem_max = 262144
As you can see all the parameters are set correctly. -
11G Grid control - Target is temporarily in status pending state.
Hi,
I'm using 11G OMS, where at a point of time I can see many unknown targets with message "Target is temporarily in status pending state."
There are different databases running on different hosts are showing the same error.
Thanks
KSGKSG,
Can you try below commands on agent to get status & upload/reload , last upload time & target being monitored
Also have check in /etc/hosts of agent host should be in below format
<IP> hostname.domainname hostname
Check ping telnet for connectivity between agent & OMS
HTTP Console Port : 7789
HTTPS Console Port : 7800
HTTP Upload Port : 4890
HTTPS Upload Port : 4900
Agent Port : 3872
Repository Port : 1521
Enterprise Manager Central Console Port = 4889
Enterprise Manager Central Console Secure Port = 1159
emctl status agent
emctl upload
emctl reload
emctl config agent listtargets Thanks,
Ajay More
http://www.moreajays.com -
Grid control patching log locations
I looked on oracle support. I am looking for the grid control logs for when I patch through the grid control gui.
The agent deploy logs are here:
/opt/app/oracle/product/10.2.0/oms10g/sysman/prov/agentpush
Where are the logs for Deploy -> Patch Agent ?
When a job fails for either patching an agent or a database, the error messages I get in the GUI are not real useful. I need the logs. I have been hunting for them and can't find them.Check the job logs in the OMS since the real deploying/patching is done by a job.
See the tab Jobs. If you select Advanced Search, change Target Type to Targetless you may even see more jobs that ran on your OMS.
Select a job that ran. You can click Show All Details and even zoom in further, depending if it was multi step job.
Eric -
Status Pending on Grid Control
Hi,
On the Grid Control -> All Targets Type=Cluster
I have the "Status Pending" on my target Cluster.
All the nodes are up as also as all the agents, instances, etc...except the cluster that appears to be "Status Pending".
I tried to restart all the agents and refreshing the configuration, but the "status pending" remains.
Anyone has any idea?
Thanks.
Best regards,
José CarlosGrid Control server can connect to target database 1521(listener port)?
Grid Control server -> target database:1521
Grid Control server -> target database:agent port (3872)
target database -> Grid Control server: 4889 ; (upload agent file)
http://download.oracle.com/docs/html/B12013_03/firewalls.htm
Please check your connect
After that clear state
1. Stop the agent on the target node
emctl stop agent
2. Delete any pending upload files from the agent home
cd $AGENT_HOME/<hostname>/sysman/emd/
rm -r state/*
rm -r collection/*
rm -r md/upload/*
rm lastupld.xml
rm agntstmp.txt
rm blackouts.xml
3. Issue an agent clearstate
emctl clearstate agent
4 Start the agent
emctl start agent
5. Force an upload to the OMS
emctl upload agent
Good Luck -
Configuring Grid Control on 10g R2
Hi
Current Envt : Oracle 8.1.7/Win NT.
We are going migrate to 10g R2 ,
In the current 8i environment, we have a EM database which manages RMAN backups of a couple of Other databases.
And we monitor these backup jobs through this Enterprise Manager 2.2.
Also, using this OEM 2.2, iam able to monitor all the existing databases .
Coming to 10g R2 (10.2.0.1)
i realized that Enterpise Manager (web based) is only for a single instance.
And i read some where that 10g Grid Control would be helpful for multiple databases.
and how to access the Grid Control..and configure multiple databases on it.
Currently, i installed Grid Control 10.1.0.5 by giving the path as
E:\app\oracle\product\10.2\em_1
However, iam not able to figure as how to bring up the Grid Control.
I wanted to know if someone can provide the steps on how to install (if i have been doing anything wrong ?
Whether while installing i have to give the same $ORACLE_HOME as with the database ?
I also tried the same way as regular DBcosole ie., http://localhost:port/em
In addition, while creating the DB using DBCA, i selected the Grid Control Option.
Please suggest as how to proceed further.
ThanxSee comments below:
Coming to 10g R2 (10.2.0.1)
i realized that Enterpise Manager (web based) is only
for a single instance.Database control is for single instance and it gets when you install the database provided you pick the option to install it.
And i read some where that 10g Grid Control would be
helpful for multiple databases.Grid Control is the only way to manage multiple dbs.
and how to access the Grid Control..and configure
multiple databases on it.
Currently, i installed Grid Control 10.1.0.5 by
giving the path as
E:\app\oracle\product\10.2\em_1Install Grid Control on a separate server preferably one dedicated to management only. Then on each database server, you'll need to install an agent for OMS to talk to the target database.
However, iam not able to figure as how to bring up
the Grid Control.
I wanted to know if someone can provide the steps on
how to install (if i have been doing anything wrong
Whether while installing i have to give the same
$ORACLE_HOME as with the database ?Install as I said above. In a separate home if you want to install it on a server that has your target database.
I also tried the same way as regular DBcosole ie.,
http://localhost:port/em
You probably didn't install the DBconsole.
>
In addition, while creating the DB using DBCA, i
selected the Grid Control Option.
For this option to work, you need to have Grid Control operational. First start with selecting only DBConsole...this way you can manage your database. After you get Grid Control installed and the agent is working properly, you can stop the DBConsole service and use Grid Control to manage your target database. -
Grid control Installation.
Hello Everybody,
I have to immplement the 10g grid control and the scenario's goes like this.
I have database installed on HP-UX 11.11i and a Windows server.
Now can I install the grid agent on HP-UX(database server) and a OMS(repository) on Windows server 2003.
Is there any compatibility issues.
Eagarly waiting for your responses?
Thanks in advance.Hi,
What I understood out of the description is ...
You have 2 servers
1) HP UX ====> Already one database is running which you want to monitor after implementing grid control
2) Windows server =====> Here you are planning to install grid control 10g mean OMS repository as per your quote
First,
You can install Grid Control in any of the 2 servers it is available for HPUX as well as Windows.
Grid control monitors targets (i.e. databases, hosts, listeners etc.) through Agent software which is available for all the
flavours of unix and windows. So, you can install grid control on any of the box and monitor both the boxes. There will
be no compatibility issues.
Let me know if you have any questions or concerns.
Best Regards,
Nirav -
Hi,
I am using Oracle version 10.2.0.1.
I want to install GRID CONTROL on top of this installation. For this I will be installing OMA(Oracle Management Agent) first.
My query is, can I straighaway install OMA version 10.2.03 over Oracle database version 10.2.0.1? Or do i need to patch firstly the base oracle database version from 10.2.0.1 to 10.2.0.3 then only I can install OMA version 10.2.0.3 over it.
Thanks in advance.
Regards
Edited by: user12302569 on Sep 9, 2010 4:56 PMuser12302569 wrote:
Hi,
I am using Oracle version 10.2.0.1.
I want to install GRID CONTROL on top of this installation. For this I will be installing OMA(Oracle Management Agent) first.
My query is, can I straighaway install OMA version 10.2.03 over Oracle database version 10.2.0.1? Or do i need to patch firstly the base oracle database version from 10.2.0.1 to 10.2.0.3 then only I can install OMA version 10.2.0.3 over it.
Yes .. you can install OMA and I would suggest you to install 11G agents as they are available now and have more feature. Agent version doesn't depend on database version. An agent can monitor all supported versions of Oracle database(depends on agent version) .
For agent-monitored targets certification , please check MOS note:
Oracle Enterprise Manager Grid Control Certification Checker [ID 412431.1]
What is your OMS version by the way ?
OMA agent doesn't work standalone and you need to have OEM Grid control installed before installing agent on a target server.
For OEM Grid , please refer to :
http://www.oracle.com/technetwork/oem/grid-control/downloads/index.html
http://www.oracle.com/technetwork/oem/grid-control/documentation/index.html
Regards
Rajesh -
Oracle Grid Control 10.2.0.3 can´t configure databases
I installed the Grid Agent (10.2.0.5) in host1 for monitoring the database (10.2.0.5) inside him. I did the same in host2, that has Agent (11.1.0.1) and Database (11.2.0.2). Both Agents are pointing to the same Grid Control Management Server.
Grid control has a separated server with Grid Control OMS and Agent installed (10.2.0.3).
This host1 was added to the grid control target hosts, and the database too. The secure option is disabled.
First Problem: metrics collection error in Grid Control for database target.
My Solution: Deconfigured the Oracle DBControl in host1 and host2 (it was configured with a local repository) dropping the repository, and I used | emca -config agent | to create a link to the agent in local machine.
New state: Now the OEM show the targets apparently been monitored. When a target fall down the OEM send allerts normally.
Second Problem: When I click in a host, database, listener, or any of the targets, intending the log in the instance it take about 5 minutes and returns: "No Response from Application Web Server There was no response from the application web server for the page you requested. Please notify the site's webmaster and try your request again later. "
My solution: I didn´t find one. HELP!
For coincidence, all databases actually monitored (8) are 10.2.0.4 or down. All of these can be managed by click in target names by OEM. Could it be the version of the new databases?
See $OMS_HOME/SYSMAN/LOG/emoms.log in Management Server
2012-05-09 10:35:13,462 [EMUI_10_22_37_/console/monitoring/hostOverview$ctxType=Hosts$type=host$target=HOST1.MYDOMAIN] ERROR host.HostOverviewDataObject getLogonInfo.2343 - IOException in sending Request :: Connection timed out
oracle.sysman.emSDK.emd.comm.CommException: IOException in sending Request :: Connection timed out
at oracle.sysman.emSDK.emd.comm.EMDClient.getResponseForRequest_(EMDClient.java:1728)
at oracle.sysman.emSDK.emd.comm.EMDClient.getResponseForRequest(EMDClient.java:1624)
at oracle.sysman.emSDK.emd.comm.EMDClient.getResponseForRequest(EMDClient.java:1547)
at oracle.sysman.emSDK.emd.comm.EMDClient.getMetrics(EMDClient.java:915)
at oracle.sysman.eml.mntr.host.HostOverviewDataObject.getLogonInfo(HostOverviewDataObject.java:2285)
at oracle.sysman.eml.mntr.host.HostOverviewDataObject.getHostInfo(HostOverviewDataObject.java:2226)...Hello.
We already have Grid Control 10.2.0.4 and just installed AD4J 10.2.0.4. This version of AD4J is not integrated with Grid Control, and can be setup on any server by unzipping the downloaded file (no installer). I did find the installation/configuration documentation lacking, but worked through it with a little help from Oracle Support.
The AD4J console has the look and feel of Grid Control, but is totally separate app with its own Apache server, etc.
Daren -
Enterprise Manager Grid Control - SSH not working on Windows
Hi,
We tried the below steps to install EM Grid control on our Windows servers.
• Oracle Application Grid Control with Oracle Management Agent has been installed successfully on Server1.
• As part of prerequisites for Agent installation using Agent Deployment Wizard, we have installed Cygwin in both the boxes – SOA box (Server2) and Grid control box (Server1) for SSH communication. However, the agent installation failed and the service in SOA box failed to start. We tried re-installation of Cygwin but unable to bring up Cygwin service.
• We have installed SOA suite in another box (Server3) and then installed Cygwin. Cygwin installation was successful and all previous issues were resolved.
However, SSH communication is getting failed because of the error "User Authentication failed on remote nodes:Server3. Either the provided username and password is incorrect or Password Authentication is disabled for the sshd daemon on the remote nodes. To enable Password Authentication set the property PasswordAuthentication to "yes" in the SSHD Configuration File (sshd_config) on the remote nodes".
We are able to achieve SSH communication when we manually try it through Cygwin Bash Shell.
Any pointers in resolving this would be highly appreciated.
regards,
Satyajith
Edited by: 817555 on Dec 12, 2010 10:11 PMI couldn't get to work either so I left the ssh configuration out and went on with 'silent' installation which worked like a charm and oem discovered it right away. Be sure change the parameters according to your environment in 'additional_agent.rsp' file and use that to run the silent installation. You may have to add one additional parameter manually about agent home location, look in the documentation for the exact parameter name. Hope this helps, Viral.
Maybe you are looking for
-
Oracle Application Release 11 having error
Hi all, I'm having problem with our Oracle Application Release 11. When I create a new Responsibility in General Ledger, I follow the exact step to create responsibility. But when I use the responsibility to open a Form in AP>Setup>Payment>Format , i
-
Performance Impact for the Application when using ADFLogger
Hi All, I am very new to ADFLogger and I am going to implement this in my Application. I go through Duncan Mill's acticles and got the basic understanding. I have some questions to be clear. Is there any Performance Impact when using ADFLogger to slo
-
MBAM 2.5 ADMX files with MBAM 2.0
I am standing up a new MBAM 2.5 environment to integrate with ConfigMgr 2012 R2. We currently have MBAM 2.0 integrated with ConfigMgr 2007. I want to know if I will run into any problems if I copy the new ADMX files to the sysvol share? Will our
-
Connecting the third party softeare output to SAP
HI there, Suppose we are using MIMI (Manugistic Networks) for the planing instead of MRP , then how in SAP the output of MIMI can be connected to SAP ? Is there are number of ways for doing that & their respective Pros & cons... Please e
-
Falsche Syntax in der Nähe von '-'.
What happend? ** Workbench Repository : Oracle9i Lite ORDBMS 4.0.2.0.0 ** The following plugins are installed: ** Microsoft SQLServer 2000 Plugin, Release 9.2.0.1.3 Production ** Active Plugin : SQLServer2K java.sql.SQLException: [POL-5167] index doe