Cannnot remove host target in Grid Control 10.2

Chaps,
I'm trying to remove a agent discovered in grid. I've done:
1) agent is running
2) removed all database targets, listeners etc discovered in grid
3) shutdown agent
4) tried removing the host from either the hosts or all targets page, but the remove just hangs for ages and then comes up with:
"No Response from Application Web Server"
Grid is running ok as far as I can tell.
Anyone with any advice before I raise yet another SR?
Thanks,
Bazza

Sorry too lazy to search!! Apologies.
In the end I did (on oracle support advice):
exec mgmt_admin.delete_target ('<name o/t target>','<type o/t target>',0,0,1);
exec mgmt_admin.cleanup_agent('<name o/t agent>');
And that appears to have done the trick. Was that your script?
Neither script took long to run.
Thanks,
Bazza

Similar Messages

How add a host in EM Grid Control

Hi everybody !!
I am having problems at identifying like can add one host in the Enterprise manager grid control for monitoring a database that containg the host.
I have install EM grid control in VMware with SO windows XP.
was installed my repository in ORACLE_HOME, one service in OMS_HOME, one agent in AGENT_HOME, use the option "Installing Enterprise Manager 10g Grid Control Using a New Database".
i understand that automatic the oracle mangement service and oracle manegement agent communicate and can see other hosts in EM grid control.
all services is up
dont see other hosts, dont see other databases
can anybody help in this issue??

Install the Management Agent on the hsot you want to manage. it is stated in the documentation.
Oracle Database FAQs

How to add new host to 11g grid control

I have install silently oem agent 11g in a solaris system. The installation was successful and agent is up and running.
But the thing is I can't add this client and its database in my OEM Grid Control interface. When I try to add the target it shows the bellow error
Information
You cannot add a host target from Enterprise Manager Grid Control.
To add a host target, install the Oracle Management Agent on the host computer you want to manage. When the Management Agent begins communicating with the Oracle Management Service, the Management Agent target and the Host target will appear in the list of targets.
My Question is how i can the target's agent can communicate with OMS agent? and How this target can be incorporated?

Hi,
the host and agent targets should show up right after installation of the agent, if securing was successful. I assume the error happened somewhere there.
Can you please paste the output of following command:
$ORACLE_HOME/bin/emctl status agent
where ORACLE_HOME is set to your newly installed agent?
Also, please check if you see any errors in $ORACLE_HOME/sysman/log/emagent.log and emagent.trc about communication between the agent and your OMS.
Best regards,
Robert

Agent running but host unavailable in grid control

hi,
well yet another question, am having a bad day with grid control.
I have pushed an agent out to server xxx and the agent is now monitored through grid control however, the host remains unavailable. I have done agentca -d and -f, the agent is secure. Can anyone help out?
rgds
Alan

hi,
yes emctl status show everything is fine. Other targets have shown up in GC successfully.
At present I cannot find an emoms.trc file. I will post back if I can work out where it is.
rgds
Alan

Can we rename an exisiting target in Grid Control

Hello Gurus
We are upgrading a database from 10.2.0.5.0 to 11.2.0.2.0 and we are going to change the SID of the environment.
I wanted to know if it was possible to change the target name (so that we can keep all historical data of the previous database for example).
At the moment the target name is <sid>.****.co.uk
Thanks for any tips.
We are using Oracle Enterprise Manager 11g Release 1 Grid Control (11.1.0.1.0 )
Edited by: 869150 on 19-Sep-2012 07:16

Grid Control Target Maintenance: How to Change the Display Name of Targets in Grid Console? [ID 755630.1]

OMS unable to reach host in 10g grid control

Greetings Gurus:
I installed oracle 10g grid control r2 and agent on a windows xp machine. on another windows xp machine i installed the agent. i am able to see the host in grid control on the machine with the grid control installed but cannot see the remote machine with only the agent installed. i have reloaded and uploaded, started and stopped the agent using emctl and opmnctl without any issues(this is on the remote machine) but still cannot see the remote host. when i try to secure the agent on the remote machine i get the following:
Requesting an HTTPS Upload URL from the OMS... Failed.
The OMS is not set up for Enterprise Manager Security.
I am fairly new at using grid control and standby database and have had a torrid time trying to fix this problem. your assistance would be greatly appreciated

*1. Stop dbconsole*
emctl stop agent
OR
emctl stop dbconsole
*2. Secure it*
emctl secure dbconsole sysman_pwd agent_reg_pwd
*3. Start dbconsole*
emctl start dbconsole
*4. After some time when the dbconsole starts check the status*
emctl status
Ss

I can`t configure database target in GRID CONTROL

hi
i have grid control 10.2.0.4 on linux red hat 5. the installation are correct and i discover the first node that have a oracle database.
But when i try to configure the database , not appear the configuration page and only give me a error
The metalink team say to me the problem is that the nslookup not working, and this not there is comunication between the oms and the agent
its necessary a dns server??
how to make the configuration for nslookup working

Hi Andrea.
Yes. Only it's necessary to add the full qualified name and IP adress in /etc/hosts and to check that the /etc/nsswitch.conf file resolve in the order file hosts .
It was the Metalink Team that saw to me : "it's necessary to working the nslookup correctly to work good the communication between the oms and the agent"
But its not true. Not its necessary.
Thanks Andreas

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.

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

Oracle application related target not show in grid control 11g (11.1.0)

hi all
i insall grid contrlol on r12(12.1.1) and it work very fine detect all target r12 database plus oracle application server all target...
but my problem is, when i connect it to another system r12(12.1.3) by agent silent installation...it detect oracle r12 database but not detect any target related to oracle application server such as oracle ebusiness suit,http server or any target related to application server...
os linux 5.4.
acutally i want to configure plug in 4.0
i follow metalink doc 1224313.1( i apply all the patch that are mentained in this document..)
plz plz plz help me or refer me any doc any blog or any thig by which i can detect oracle application target in grid control..
grid control 11g(11.1.0)
os - linux 5.4
r12 - 12.1.3
thanks & regards
pritesh ranjan

ya i have installed all the patch that maintain in the plug-in 4.0 doc (1224313.1)
below are the details of the log file and agent of the host server and remote server............
This is the log file details of my remote machine which application server is not detected:-
[orainst1@erpdemo log]$ cat emagent.log
2013-02-21 11:46:56,936 Thread-3043985088 Starting Agent 11.1.0.1.0 from /data/PRODINST/agent111g/agent11g (00701)
2013-02-21 11:47:33,240 Thread-3043985088 EMAgent started successfully (00702)
[orainst1@erpdemo log]$
r::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
storage_report_metrics.pl: Thu Feb 21 11:48:04 2013: WARN: STORAGE_REPORTS:error::snmhsutl.c:executable nmhs should have root suid enabled
[orainst1@erpdemo log]$
[orainst1@erpdemo log]$ cat emagent.nohup
--- Standalone agent
----- Thu Feb 21 11:46:56 2013::Agent Launched with PID 24198 at time Thu Feb 21 11:46:56 2013 -----
----- Thu Feb 21 11:46:56 2013::Time elapsed between Launch of Watchdog process and execing EMAgent is 0 secs -----
(pid=24198): starting emagent version 11.1.0.1.0
(pid=24198): emagent started successfully
URLTiming: Using SunX509
[orainst1@erpdemo log]$
Emagent.trc
: nmehl_read_sock timed out, rsf = -5, setting read timeout flag2013-02-21 12:01:39,302 Thread-3028446096 WARN ssl.io: fd=32: nmehlssl_read, nzos_Read error = 28862 readTimed Out = 1
2013-02-21 12:01:39,302 Thread-3028446096 WARN http: <nmehl.c>:<nmehl_readline>: nmehlssl_read() timed out
2013-02-21 12:01:39,302 Thread-3028446096 ERROR pingManager: nmepm_pingReposURL: Error in request response. code = 400. text =
2013-02-21 12:02:09,368 Thread-3028446096 WARN ssl: <nmehlssl.c:nmehlssl_readcb>: nmehl_read_sock timed out, rsf = -5, setting read timeout flag
2013-02-21 12:02:09,368 Thread-3028446096 WARN ssl.io: fd=32: nmehlssl_read, nzos_Read error = 28862 readTimed Out = 1
2013-02-21 12:02:09,368 Thread-3028446096 WARN http: <nmehl.c>:<nmehl_readline>: nmehlssl_read() timed out
2013-02-21 12:02:09,368 Thread-3028446096 ERROR pingManager: nmepm_pingReposURL: Error in request response. code = 400. text =
2013-02-21 12:07:35,620 Thread-3032005520 WARN ssl: <nmehlssl.c:nmehlssl_readcb>: nmehl_read_sock timed out, rsf = -5, setting read timeout flag
2013-02-21 12:07:35,620 Thread-3032005520 WARN ssl.io: fd=35: nmehlssl_read, nzos_Read error = 28862 readTimed Out = 1
2013-02-21 12:07:35,620 Thread-3032005520 WARN http: <nmehl.c>:<nmehl_readline>: nmehlssl_read() timed out
2013-02-21 12:07:35,620 Thread-3032005520 ERROR command: nmejcn: error receiving response headers from https://pritesh.txis.com:4900/em/upload
[orainst1@erpdemo log]$
[orainst1@erpdemo log]$ cat emdctl.trc
2013-02-21 11:46:56,495 Thread-3043628736 WARN http: nmehl_connect_internal: connect failed to (erpdemo.txis.com:3872): Connection refused (error = 111)
2013-02-21 11:46:56,495 Thread-3043628736 ERROR main: nmectla_agentctl: Error connecting to https://erpdemo.txis.com:3872/emd/main/. Returning status code 1
[orainst1@erpdemo log]$
[orainst1@erpdemo log]$ cat emagentfetchlet.trc
[orainst1@erpdemo log]$ cat emagentfetchlet.trc
2013-02-21 11:47:37,597 [main] WARN track.OracleInventory collectInventory.937 - ECM: Oracle Home agent11g1 at location /data/PRODINST/agent11g/agent11g specified in inventory /data/PRODINST/oraInventory does not exist.
2013-02-21 11:47:38,452 [main] WARN track.OracleInventory collectInventory.937 - ECM: Oracle Home agent11g3 at location /data/PRODINST/pritesh_agent/agent11g specified in inventory /data/PRODINST/oraInventory does not exist.
2013-02-21 11:47:38,535 [main] WARN track.OracleInventory mineHomeInventory.2320 - ECM: Oracle Home : Independent Products at N/A is not readable, please check permissions ..
[orainst1@erpdemo log]$
[orainst1@erpdemo log]$ cat emagent.nohup.lr
[orainst1@erpdemo log]$ cat emagent.nohup.lr
--- Standalone agent
[orainst1@erpdemo log]$#######################################
[orainst1@erpdemo log]$ cat emctl.log
[orainst1@erpdemo log]$ cat emctl.log
24156 :: Thu Feb 21 11:46:56 2013::AgentLifeCycle.pm: Processing start agent
24156 :: Thu Feb 21 11:46:56 2013::AgentLifeCycle.pm: EMHOME is /data/PRODINST/agent111g/agent11g
24156 :: Thu Feb 21 11:46:56 2013::AgentLifeCycle.pm: service name is
24156 :: Thu Feb 21 11:46:56 2013::EM_SECURE_HOSTNME: erpdemo.txis.com
24156 :: Thu Feb 21 11:46:56 2013::EM_SECURE_PORT: 3872
24156 :: Thu Feb 21 11:46:56 2013::EM_LISTEN_ON_ALL_NICS: TRUE
24156 :: Thu Feb 21 11:46:56 2013::AgentLifeCycle.pm:status agent returned with retCode=1
24156 :: Thu Feb 21 11:47:34 2013::AgentLifeCycle.pm: Exited loop with retCode=3
25957 :: Thu Feb 21 12:12:33 2013::AgentLifeCycle.pm: Processing status agent
25957 :: Thu Feb 21 12:12:33 2013::AgentStatus.pm:Processing status agent
25957 :: Thu Feb 21 12:12:33 2013::AgentStatus.pm:emdctl status returned 3
[orainst1@erpdemo log]$
[orainst1@erpdemo bin]$ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
Agent Home : /data/PRODINST/agent111g/agent11g
Agent binaries : /data/PRODINST/agent111g/agent11g
Agent Process ID : 24198
Parent Process ID : 24178
Agent URL : https://erpdemo.txis.com:3872/emd/main/
Repository URL : https://pritesh.txis.com:4900/em/upload
Started at : 2013-02-21 11:46:56
Started by user : orainst1
Last Reload : 2013-02-21 11:46:56
Last successful upload : 2013-02-21 17:33:40
Total Megabytes of XML files uploaded so far : 36.47
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 15.60%
Last successful heartbeat to OMS : 2013-02-21 17:41:09
Agent is Running and Ready
[orainst1@erpdemo bin]$
[orainst1@erpdemo bin]$ ./emctl upload agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
EMD upload completed successfully
[orainst1@erpdemo bin]$
SQL> select release_name from apps.fnd_product_groups;
RELEASE_NAME
12.1.3
The below details is from on the machine where the grid control ,weblogic server and oms are installed and have not create any type of problem:-
Oms details on host machine
[oracle@pritesh bin]$ ./emctl status oms -details
Oracle Enterprise Manager 11g Release 1 Grid Control
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Console Server Host : pritesh.txis.com
HTTP Console Port : 7788
HTTPS Console Port : 7799
HTTP Upload Port : 4889
HTTPS Upload Port : 4900
OMS is not configured with SLB or virtual hostname
Agent Upload is unlocked.
OMS Console is unlocked.
Active CA ID: 1
[oracle@pritesh bin]$
[oracle@pritesh bin]$ ./emctl status agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
Agent Version : 11.1.0.1.0
OMS Version : 11.1.0.1.0
Protocol Version : 11.1.0.0.0
Agent Home : /home/oracle/Oracle/Middleware/agent11g
Agent binaries : /home/oracle/Oracle/Middleware/agent11g
Agent Process ID : 3795
Parent Process ID : 3775
Agent URL : https://pritesh.txis.com:3872/emd/main/
Repository URL : https://pritesh.txis.com:4900/em/upload
Started at : 2013-02-21 10:00:56
Started by user : oracle
Last Reload : 2013-02-21 10:17:45
Last successful upload : 2013-02-21 16:46:01
Total Megabytes of XML files uploaded so far : 42.29
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 23.91%
Last successful heartbeat to OMS : 2013-02-21 16:46:53
Agent is Running and Ready
[oracle@pritesh bin]$
[oracle@pritesh bin]$ ./emctl upload agent
Oracle Enterprise Manager 11g Release 1 Grid Control 11.1.0.1.0
Copyright (c) 1996, 2010 Oracle Corporation. All rights reserved.
EMD upload completed successfully
[oracle@pritesh bin]$
SQL> select release_name from apps.fnd_product_groups;
RELEASE_NAME
12.1.1
SQL>
thanks & regards
pritesh rnajan

Trying to monitor my sql servers in OEM Grid Control

Hello,
I have Oracle 10g OEM and I want to start monitoring my sql server databases. I've got the plug-in all setup but when it displays under my "Databases" it shows and status "down". My sql server host is running, listener running, and database is up but when I try to "configure" it gives the "Failed to connect to the database: Io exception: Connection reset The Connect Descriptor...." error. Can someone please help??? I would like to know....
1) under the monitor user name is says "dbsnmp" so do I have to create a dbsnmp user on the sql database side?
2) do I keep the same port number (1521) or do I put what the sql server db is listening on (1433)?????? - for the configuration in OEM
3) If i go to the "host" under "targets" it shows that the agent is "up" but the database instance is "down and the listener is "up.
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=FSPROLOG.portofsandiego.org)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC0ipc)))
Services Summary...
Service "PLSExtProc" has 1 instance(s).
Instance "PLSExtProc", status UNKNOWN, has 1 handler(s) for this service...
Service "PMDBSQL" has 1 instance(s).
Instance "PMDBSQL", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully
Thanks in Advance,,

Welcome to the forums !
Not sure what this has to do with database upgrades (the topic of this forum), but pl confirm that you have followed all of the steps in MOS Doc 359413.1 (How To Download and Deploy Microsoft SQL Server Plug-in To Monitor SQL Server Targets From Grid Control )
HTH
Srini

The configure database page not appear in grid control

hi
when i try to configure a database target in grid control appear a error . i know that the nslookup not working correctly because these machines not adding to dns server
it's possible communication between oms and agent whithout an dns server, only adding lines in the /etc/hosts
thanks

Which self Service function you are using to change the assignment ?
Their are two API to update asg values. Try to apply user hook on both of them and retry ur scenario.

Remove Host Manually in 12C...

Hi,
I want to remove some hosts in 12C grid control which were decommissioned in past but were never removed from grid control. If I try to remove from grid control it gives error host not reachable. I'm wondering is there any method to remove these hosts from repository using scripts.
Other question I have is:
I created host metric extension to take export of database. When I test the extension it fails with error metric collection timeout of 300 seconds occured. How can I increase the timeout for host metric extension. The export can take more than hour.
Thanks in advance.

Thanks Venkat. I'll give it a try and update you.
In the mean while can you or someone help me to answer following (Which I asked in my original post).
I created host metric extension to take export of database. When I test the extension it fails with error metric collection timeout of 300 seconds occured. How can I increase the timeout for host metric extension. The export can take more than hour.
Thanks.

Naming database inside Grid Control

Hi,
I have one question about database names in Database tab of Grid Control.
What is happening:
I have static definition of my services in the listener.ora file, and when I have installed Grid Control Agent on this node
Oracle registers name like this in my databases tab of Grid Control:
DBNAME_HOSTNAME.DBDOMAIN
I want to register my database like dbname.dbdomain. Is it possible? Can I have any control of naming of databases in Grid Control?
When I haven’t static definition of services in my listener.ora file, database is good registrated (*dbname.dbdomain*).
Thanks,
Best regards
Dragan

Yes you have control of naming databases in Grid Control.
When you add a database target to grid control, after chosing the host you'll see the databases on that host. Under the databases there is an option: "Manually add" If you chose this option you can name the database target however you want. so you can delete the database target from grid, and add again with manual option...

Microsoft plug in deployment errors on grid control

Hi,
I keep getting errors when deploy microsoft_sqlserver_Databse plug in to grid control server.
"The preferred credentials are not set for "server name"".
I set the credential for microsoft SQL server on preference page, however, i still get same error.
Have anyone encountered the same problem? Is there a better guide for Microsoft plus in deployment?
Thanks for your help,
~Amy

Thanks for the reply. I had this question before and the link for that is
Adding New Targets to Grid Control
Thanks.

Cannnot remove host target in Grid Control 10.2

Similar Messages

Maybe you are looking for