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'

Similar Messages

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

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
KSG

KSG,
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

Open telnet session using PL/SQL

Dear all
I have made a function that returns a value when a remote server runs a specific process. In order to find this, I would like to run a telnet command along with some grep parameters. This can be done using a Java class, but it is not very functional! Is this a way to do using only PL/SQL?
Thanx in advance

I know there are a couple of Java telnet clients out there, I'm not sure whether they support the JDK in your database. What version of Oracle are you using? The other option would be to write a script that does whatever you want to do and just call the batch file.
Justin
Distributed Database Consulting, Inc.
http://www.ddbcinc.com/askDDBC

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

Problem in grid control

Hi all,
I am facing below problem in our grid control
Target Name=emrep
Target type=Database Instance
Host=tfoisapp2
Occurred At=Jan 20, 2012 3:11:50 PM IST
Message=Failed to connect to database instance: ORA-12519: TNS:no appropriate service handler found (DBD ERROR: OCIServerAttach).
Severity=Critical
Acknowledged=No
Notification Rule Name=TEST
Notification Rule Owner=SYSMAN
Our management repository database is up & running. Unable to stop OMS services
With Regards,
Jenny John

Hi;
After hid & trail solved the problem.. thank uYour welcome If you think you have your answer for your theard; please change thread status to answered if it possible, it pretend to lose time of other forums user while they are searching open question which is not answered,thanks for understanding
Regard
Helios

Dgutil.pl line 99 ERROR when creating 11.2.0.3 data guard via GRID CONTROL

Oracle Grid Control 11g Release 1 (11.1.0.1.0)
(64bit)
Oracle Enterprise Linux Server release 5.4 x86_64
Oracle Database 11.2.0.3 (64bit)
1. Grid Control>Targets>Databases
2.Click on pc01prmy (Primary)
3.Availability > Data Guard > Setup and Manage
4.Add Standby Database
5.Create a new physical standby database.
Fails with message:
38706 at /u01/app/oracle/agent11g/sysman/admin/scripts/db/dg/dgutil.pl line 99.
I can create a standby with a rman script without problems, but via the Grid Control page fails.
Have you seen this before?

I contact Oracle Support on this issue, here are the details.
Generic Note
Hi Marcelo, the note you sited Creating Standby Database With Enterprise Manager Failing [ID 1400482.1
Says something a little different than what you tried.
You did RECOVER DATABASE for manual recover and the error says use backup control file.
For a standby to do manual recovery it's
*alter database recover standby database ;*
It may behave better.
But the note implies to just apply enough redo to have the standby consistent enough to turn on flashback.
This can be done by starting managed recovery and applying some redo log sequences.
So the flashback being turned on is too soon, but should have worked anyway. I think it would turn on managed recovery though.
This also happens since the job doesn't use dorecover since recovery can be done with managed recovery.
So most likely there isn't enough activity on the primary and the online redo has not been archived yet.
So some log switches on the primary will send enough redo to get consistent so you can turn on flashback and finish it.
*So why did it happen?*
Possibly
Bug 13250486 - ADD STANDBY DATABASE FOR TARGET WITH FLASHBACK ON FAILS WITH ERROR
Base bug 12923814 FLASHBACK AND ARL DELETION OPTIONS IGNORED IN ADD STANDBY DATABASE WIZARD
fixed in Grid Control 12.1c
There is currently no patch available for 11.1.0.1 Grid Control. We would have to open a bug to confirm you hit this in 11.1.0.1 and get a patch.
*A workaround would be to turn off flashback at the primary then try to create the standby.*
*Once the standby is created you can turn flashback back on for the primary and if required, the standby.*
You can try again to see, or finish the standby manually as I stated above.
I will still need the diagnostic information below.
Action Plan
=========
The product verion in this SR is for 12.1.0.1 Grid Control. I assume it should be 11.1 since you stated it is.
Grid Control job log that shows the errors.
alert logs from the primary and standby.
Please run these two diagnostic scripts and upload the output.
Script to Collect Data Guard Primary Site Diagnostic (Doc ID 241374.1)
Script to Collect Data Guard Physical Standby Diagnostic (Doc ID 241438.1)
Edited by: Marcelo Marques - ESRI on Mar 24, 2012 9:51 AM

Installing 10g and Grid control together on Windows Server 2003

Hi all,
I've been having some trouble installing both the Grid Control and Oracle 10g together on a Windows Server 2003 box.
Here's the steps I've followed (if im stepping away from the norm, please tell me.. i REALLY need to do this properly without any hacks.. right now im on a test box.. but soon enough I have to do it in a live production environment and I really need a clean install).
I had a copy of Oracle 9i installed - my databases are pretty small.. 1.5Gb at most and I have been advised to just do an export and import them back in later.. which is fine by me..
I uninstalled Oracle 9i, making sure to check all the environment variables were clear and the registry settings were gone.
I ran the grid control setup
Set Home name = Ora10gGC
Set home path = C:\Oracle\Ora10gGC
I selected Enterprise Manager 10g Grid Control Using a New database 10.1.3.0
I set my passwords, and then set the global database name as emrep (the default)
All the optional configuration assistants ran successfull
Once this was all done and the install was finished, I restarted the server
Then I inserted the Oracle 10g cd
I ran 10g setup
Click Advanced installation
Set home name = Ora10g
Set home path = C:\Oracle\Ora10g
I selected Enterprise edition
Selected General purpose database
I got the following message:
The ORACLE_HOME environment variable is current set. This will prevent proper use of Multiple Oracle Homes and since it is not required for any Oracle products to function, it will be unset in your environment.
I set the global database name on my starter database to STARTER, I selected Use Grid Control for Database Management and set my paths and passwords, then I clicked install.
The install worked up till it tried to create the starter database, then it failed with an ORA-12560 error.
I checked the environment variables and it seems that ORACLE_HOME wasn't unset after all. I deleted it from my environment variables and restarted the server, but I still get the ORA-12560 error when i try to create a new database.
I'd really appreciate it if someone could tell me how to install these 2 products together properly.. Thanks!

I suggest you to read Metalink Note:344537.1 "Installing EM 10g Grid Control Fails to Start the TNSListener Due to Environment Settings"
Additionaly could you post the fragment from alert.log and listener.log files, so more diagnostic information can be provided on this issue.
~ Madrid.

Suggested concept for Grid Control with DataGuard solution

Hello,
I want a Disaster Recovery solution for OEM Grid Control with DataGuard but with only one OMS running. (11.1)
I have figured out the following.
Installation OEM Grid control om host A. Repository is created on Host A. Connection to database is done thru servicename DBGRDSRV on Host A
Installation OEM Grid control om host B. Repository is created on Host B. Connection to database is done thru servicename DBGRDSRV on Host B
I stop OMS on host B and I drop the database on Host B
Then....
I create a Dataguard configuration for DBGRDSRV, the prim database run on Host A en secondary on Host B
In case of a failure i switch the database. On host B i will have DBGRDSRV as the primary database
I start OMS on host B and the agent.
In case the failure is resolved i switch back eveything
Will thos concept work?
Do i get some troubles with the emkey, and if so, does anybody has a solution for this?
Any help is appreciated
Regards,
Jaap
Edited by: user9956284 on 28-jul-2011 10:44

Hi,
Please follow the document provided below:
How to Configure the OMS Connect String when Repository is in a Dataguard setup (Doc ID 1328768.1)
Let me know, if you are looking for the same document.
Best Regards,
Venkat

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

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

11g Grid Control - Host Configuration Collection Problems

Hi Guys,
I just installed Oracle 11g Grid Control and it has been running for 2 weeks until I recently tried to walk through the parts of it.
My intention was to clear off all the error messages, critical warnings, alerts, and policy warnings.
When I arrived at the development summary box, on the home tab, I can see that there is 1 collection problem.
When I clicked it, I saw that apparently the problem is with the host where I installed the grid control.
Problem type: Warning during collection of Oracle Software
message: Unknown WLS Home Location or WLS Version in Middleware Home /u01/app/oracle/product/middleware
I tried clicking on the "Refresh Host" button, but it didn't solve the problem at all.
I have also tried to take a look at the targets.xml however it seems the configuration in there are already pointing to the correct path to the weblogic home.
Please let me know if anyone has a suggestion for this.
Searching from google doesn't really return anything closely matched to this.
Thanks,
Adhika

What is the intent/timeline for fixing this bug? On MOS, it appears to have a status of "Status 33 - Suspended, Req'd Info not Avail". We are encountering this bug also and I would glady provide information from our systems in order for the issue to be resolved.
Thanks.
PostScript: FWIW, Google yielded a blog referencing this error and Doc ID 1433113.1. I am unable to access that document (as was the blogger). Because of this, and another major caveat (our machines with this collection error do not have WLS installed on them), I'm thinking this probably needs to be an SR rather than a forum discussion.
Edited by: JeriF on Feb 4, 2013 12:00 PM

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

Oracle 10.2 Grid Control – Adding Database residing on different hosts

I used to work with Oracle 9.2 Enterprise Manager. Now I have installed Oracle 10.2.0.2 Grid Control on Windows 2000. I want to do database administrator from Oracle Grid Control for Oracle 9i, Oracle 10.1 and 10.2 databases. I do not want to install any agents on my database servers because they are production servers,
All of I am interested in to have nice user interface of Oracle 10g grid control, so I can do database administration such as adding a database file, looking at database users, sessions etc. I was able to do all of that with Oracle9i enterprise manager. IN Oracle9i EM, one can manually add a database instance if it cannot be discovered using an agent. Is it possible to do that in Oracle 10g grid control?
When I start Grid Control, go to targets tab and then database tab and want to add a database, it asks for host name. When I enter hostname (which is accessible from the network), it says host not found. Is an agent required on the host before Grid Control can recognize it. In Oracle 9i enterprise manager, there was an option to manually add a database (i.e. automatic discovery was not successful), is it possible to do that with Oracle 10g grid control.

Over the years, working with Oracle, I've found tremendous value in reading the docs. You might find similar value doing that too.
The only issue you seem to have is an unwillingness to learn the architecture and concepts behind the product you are trying to install. You get rid of the error by deleting the entry and doing it correctly.
There is no way to drop a brick on your foot and not have it hurt. <g>

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

EM Grid-Control - Targets - Hosts - HOME - Open Telnet Session

Similar Messages

Maybe you are looking for