Target Discovery Loop Forever - OEM10g R2 Grid Control Solaris

I have installed GC 10g R2 on a Solaris 64 bits.
The OEM got installed ok, but in near the end the agent gets hung in the target discovery step of the configuration.
I stoped the assitant, clear al the info in sysman/emd, clearstate de agent, started it and force de upload.
Whith this actions I got the agent configured in the OEM, then I go to the page for the discovering the targets... but again it enter in a non ending loop.
I tried also de agentca -d, again.. it get hung.
Did someone have had this problem? Any Help?
Message was edited by:
jotawolf

I have 8i and 9i databases, 9ias, etc. on a windows box. I have 10g R2 grid control on my linux server. I wish to install the windows 10g R2 agent on the windows box (during install windows agent found oms under linux after I supplied host/connect info) and I assumed when the agent started up (first time) under windows that it would auto-discover the 9i and 8i services on the windows box then forward that data to the oms under linux, but it didn't... I didn't even see the windows agent registered under the linux oms.
Did I miss something? Do I need to install an oms (and agent) under windows as well. Thought I just needed the 10g R2 (windows) agent only.
Any advice is appreciated.

Similar Messages

Installing Grid Control - Solaris - Containers - VM(Veritas)

I need to know how and where I can start to learn how to install Grid Control using Solaris with containers, and Veritas VM to create and mantain filesystems.
Please help.
Paola.
@}-->-->>-----

Hi Paola,
Check this link....
http://download-east.oracle.com/docs/cd/B16240_01/doc/nav/portal_booklist.htm

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

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é Carlos

Grid 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

Error Configuring Database Instance Properties on Grid Control

Hi All,
My Grid Control is 11.1.0.1.0. I have installed and configured agents on other nodes and the OMS and the monitored Hosts are able to communicate. My problem is when I go to targets/Databases, when I select any database and click configure, I get an error "Error occurred while getting information for the specified target. Possible reasons include: the target doesn't exist; connection to the target failed."
I do not know why I'm getting this error because the agent on the OMS server is running, the agents on the monitored targets are all running and when I check the status, I see the agent is uploading data to OMS. Also When i go to targets/hosts, all the hosts are up.
How can I resolve this problem?
Thank you.

Eric S,
Could be a Firewall issue. See http://download.oracle.com/docs/cd/E11857_01/install.111/e16847/firewalls.htm#i1005951
Firewalls Between the Grid Control and a Managed Database Target
When you are using the Grid Control Console to manage a database, you must log in to the database from the Grid Control Console in order to perform certain monitoring and administration tasks. If you are logging in to a database on the other side of a firewall, you will need to configure the firewall to allow Oracle Net firewall proxy access.
Specifically, to perform any administrative activities on the managed database, you must be sure that the firewall is configured to allow the Oracle Management Service to communicate with the database through the Oracle Listener port.
You can obtain the Listener port by reviewing the Listener home page in the Grid Control Console.
You can check if Listener port 1521 (if that's the port you are using) is open by:
OMS_HOME/bin/tnsping "(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=hostname)(PORT=1521)))(CONNECT_DATA=(SID=sid)))"
If the database in a DMZ runs on Windows you may want to check note: Oracle Connections and Firewalls [ID 125021.1]
From the OMs-server you can ping the target server by FQDN and short name?
Eric

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

How does Grid Control Application Management Pack (AMP) discover targets?

I have Grid Control 10.2.0.4 install and am trying to discover Oracle 11i applications. I have applied the patches required to the OMS and the agents and can see the Application Management tab at the top of the targets page. I am able to discover the individual components of the application (i.e. Apache, listeners, database, agents, hosts, forms, etc) but when I go under the Application Management tab and try to discover the Oracle applications I get the following error message:
Error creating Node target for ctx file /ssan/ap00/appl/admin/ssan_ssan.xml; Error:Refresh EMDClient for
ssan.rtd-denver.com
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTDiscovererPreFusion.discoverTargetsForNode; Waited for five minutes, but unable to find
Targetssan-Forms_ssan_ssan(oracle_apps_forms_svlt) in Reposiotry Possible reason - agent: https://ssan.rtd-denver.com:3872/emd/main/ has not uploaded
this target in repository
I have the following in the ebsDiscovery.log
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.saveTargetWithAgent - Host=ssan.rtd-denver.com 7 targets Found to be saved.
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.saveTargetWithAgent - Host=ssan.rtd-denver.com Convert to Target Isnatnce Name = ssan-Forms_ssan_ssan,oracle_apps_forms_svlt
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.saveTargetWithAgent - Host=ssan.rtd-denver.com Convert to Target Isnatnce Name = ssan-Apache_ssan_ssan,oracle_apps_apache
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.saveTargetWithAgent - Host=ssan.rtd-denver.com Convert to Target Isnatnce Name = ssan-JServ_ssan_ssan,oracle_apps_jserv
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.saveTargetWithAgent - Host=ssan.rtd-denver.com Convert to Target Isnatnce Name = ssan-Forms_ssan_ssan,oracle_apps_forms_svlt
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.saveTargetWithAgent - Host=ssan.rtd-denver.com Convert to Target Isnatnce Name = ssan-Apache_ssan_ssan,oracle_apps_apache
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.saveTargetWithAgent - Host=ssan.rtd-denver.com Convert to Target Isnatnce Name = ssan-JServ_ssan_ssan,oracle_apps_jserv
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.saveTargetWithAgent - Host=ssan.rtd-denver.com Convert to Target Isnatnce Name = ssan-Discoverer_ssan_ssan,oracle_apps_discoverer
oracle.apps.fnd.oam.em.sdk.targetData.discovery.ProxyTarget.registerWithEMAgent _methodAccess = 4 Calling lEMDC.saveTarget
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.saveTargetWithAgent - Host=ssan.rtd-denver.com Out
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTDiscovererPreFusion.discoverTargetsForNode refreshSubsystems for node = ssan-:Infrastructure ssan_ssan:APPL_TOP Context
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.checkTragteUplodedFromAgent ssan-Forms_ssan_ssan(oracle_apps_forms_svlt) is Uploaded in Rep=false
oracle.apps.fnd.oam.em.sdk.targetData.discovery.AppsTargetsDiscoverer.checkTragteUplodedFromAgent Waiting for target ssan-Forms_ssan_ssan(oracle_apps_forms_svlt) to be uploaded in repository. (wait itme 10 sec)
I have the white paper explaining how Grid Control discovers databases, listeners, application servers, etc. But I am not able to find a paper that tells how the Application Manager discovers the Oracle applications. Does anyone know of such a paper or which perl scripts are run?

One of the biggest problems I have run into when doing these discoveries is that the agent and iAS and/or Oracle are owned by different users and the agent does not have permissions to read the configuration files.
You situation may be a bit different.
If the host is real busy, it sometimes takes a long time to load the gathered information into the repository. From looking at your log file, this may be your issue.
How busy is the server(s) and database for you OMS and OEM database?

Grid Control performance tab not available when on the target home of ASM

I noticed recently that the "Performance" tab/link is not available when you are using 10g Grid Control and you are on the home page of an ASM instance. Can this be explained?

Hi MarGur
I try to help you. The OEM Grid Control in some times not discover the Oracle 9i databases and you must to add manually.
First, check in your target machine that the user owner of agent software have rights of read and write in the ORACLE_HOME directories of Oracle 9i databases.
Go to Grid Control Console
Select Targets ---> Databases
Press Add --> Select the host ebisdb2.oneshield.com and press continue
The automatic discover process begin. When finished is very normal that nor discover the Oracle 9i databases. You press the Add manually button
in the page that appear you must entry all the configuration information of database:
ORACLE_HOME directory
DBSNMP USER
DBSNMP PASSWORD
HOSTNAME
PORT
SID
Check that the dbsnmp user in your database is unlock and press the TEST button to verify the connection work fine.
After this many windows appear of configuration process, and you will put the sys password and host credentials.
If you have problems, tell me
Regards

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]

What does "remove target" do in Grid Control?

I have some targets that got created during agent installation that aren't real databases. I was wondering what removing the target does. Does it just remove the meta data about the target or if the target is a database will it try to delete the database? Does it modifiy the listener.ora file?

It only deregisters the target and it won't show up in GC.
For e.g. if you remove a database, you won't be able to manage it in Grid Control. It will NOT drop the database on your managed target.

Reg a user set up in grid control who can view properties of one target

Hi,
I am trying to set up a user for grid control who can view only properties of one target. I have tried some options which were suggested but didnt help.when we login i should be able to view only one target to which i am giving view access. but whenever i create a administrator it can view all targets though i give permission to view only one target.does any one have any input on this???
Thanks and regards,
Hema

Hallo Hema,
I've just quickly tried myself and have no issues creating such a limited user. Do you have any roles granted on the user? Is the "PUBLIC" role modified in your company to have some permissions granted?
Can you give a quick overview of what information is displayed on the page when you click "View" for the selected user on the Setup -> Administrators page?
Best regards,
Robert

DB target status shows "Up" in Grid Control console, but actually "Down"

We've recently installed Grid Control 10.2.0.5. We recently noticed issue regarding false status indicators for several db targets monitored. From GC console, db target show status "Up" (Green Arror) when db is actually down. Should show status as being down (Red Arrow). Is this a known bug? Has anybody experienced this behavior? Can anybody please advise and/or provide solution to this issue?
Thank you in advance.
Best,
Doin

It seems that properties are missing..
Follow the steps,
Login to EM Grid-->Targets > Databases--> Select the radio buttion for PROD Database --> click configure --> Provide dbsnmp password --> click 'Test connection' --> finish
Please reward good answers by marking them correct or helpful...

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
Frank

Sorry, Simple answer 'No'

Why 12C Grid Control shows Target status down/Unavailable?

Hello,
The grid control 12.0.2 on Oracle Linux 5.9 shows that status of target /EMGC_GCDomain/GCDomain/EMGC_ADMINSERVER as down where as it is up and running and I can log into admin console.
Please note that repository, OMS, weblogic all components are on same server.
It is also showing that following are unreachable where as these are up on same server
EM Website System
Management Services and Repository
How can I diagnose and fix this? Where to start?
Thanks.

Have you checked the agent status with emctl status agent? Is the OMS available there and when was the last upload time?
You can also try emctl upload agent and see if this helps.
Is the dbsnmp account unlocked with correct password in the target database?
rgds
Kjell

Batch remove all default policys on all targets monitored by Grid Control.

Hi all,
I have been searching for a way on how to remove all default policy's that are attached to the target after they have been added into the Grid Control.
I have been trying with monitoring templates, but without any luck. Yes it changes values but it does not remove non template listed policy's.
There must be a way to do this, without manually do it on all 400+ targets.
All ideas of interest.
Best regz,
/Robban

Nice it worked just fine.
Thanks for the input.
Dont know why I didn't think of disabling the policy's, but i guess that i goy snowed in on the removal part.
Also ran into a new problem. (Unable to apply a monitoring template to a group with more then 100 targets)
Found the solution on metalink: Note:455279.1
Its a bug and there is a OneOff for it: "Patch 5573244"
After applying that patch it worked fine.
Best regz,
/Robban

Target Discovery Loop Forever - OEM10g R2 Grid Control Solaris

Similar Messages

Maybe you are looking for