Unreachable Agent
I'm new to the tool and have OEM installed on 1 server.
The status of the 1 host I have an agent is "Agent Unreachable". I have ensured that an agent is running on the server. The agent appears to be running on port 1831. When doing emctl status agent, the Agent URL is http://hostname:1831/emd/main.
On the Host targets page in OEM, I see a name called db1p:3872.
I'm new to this, but it appears that the DBconsole is looking for the agent on prot 3872 and its really on 1831.
Am I reading this right. If so, how do I change the port in the DBconsole or agent.
Any other thoughts would help me sleep better this afternoon.
Thanks,
John
I'm sure that I have this configured wrong, but here goes. I'm on an HP UX server. At the present time I am supposed to 1 agent on DB1t and OEM on the same server. The server has 3 oracle instances: HSI1, HSI2, and HSI3.
I have 5 emd.property files. They are located in the following directory:
$ORACLE_BASE/sysman/config/emd.properties
$ORACLE_BASE/db1t_HSI1/sysman/config/emd.properties
$ORACLE_BASE/db1t_HSI2/sysman/config/emd.properties
$ORACLE_BASE/db1t_HSI3/sysman/config/emd.properties
$ORACLE_BASE/oms10g/sysman/config/emd.properties
I modified both the first and last files, but not the middle 3.
Also, this is troubling to me. I shut down OEM using emctl stop dbconsole. Yet I can still call it up from a Web browser. It says that it is stopping, but I can still display the 10g console. I'm using the Grid Control page from the Web, but I'm not sure how to bounce it.
Here is the Emd_properties file. The fifth one:
# perl executable directory
perlBin=/u01/app/oracle/product/oms10g/perl/bin
# script directory
scriptsDir=/u01/app/oracle/product/oms10g/sysman/admin/scripts
# emd Root directory(read-only location). Metrics should not create files
# under this directory
emdRoot=/u01/app/oracle/product/oms10g
# agent Root directory(writeable).
# Use this property to base any temporary file creation.
agentStateDir=/u01/app/oracle/product/oms10g
# Chronos root directory
chronosRoot=/u01/app/oracle/product/oms10g/sysman/emd/chronos
# OMS Upload URL
# if there is no receiving OMS or if you wish to disable the UploadManager
# please set this value to empty or comment out below line
#REPOSITORY_URL=http://db1p:4889/em/upload/
# Proxy settings used for fetchlets. not applicable for uploader.
#proxyHost=www-proxy.us.oracle.com
#proxyPort=80
#dontProxyFor=.us.oracle.com
# If it is necessary to go through an http proxy server to get to the
# repository, uncomment the following two lines
#REPOSITORY_PROXYHOST=
#REPOSITORY_PROXYPORT=
#REPOSITORY_PROXYREALM=%EM_REPOS_PROXYREALM%
#REPOSITORY_PROXYUSER=%EM_REPOS_PROXYUSER%
#REPOSITORY_PROXYPWD=%EM_REPOS_PROXYPWD%
# This string is used by the agent to connect to remote targets
# ***IMPORTANT*** Do not change the contents of this setting. Only the
# install should modify this value.
agentSeed=182537376
# This string is used by the agent to determine which algorithm to use for encrypted data
# The string value will be same as the release version
agentVersion=10.1.0.4.2
# How long, in minutes, collector will wait until next load.
UploadInterval=15
# If an upload fails, we want to backoff by UploadFailBackoff
# percentage more each time for each successive upload failure
# e.g. if we start the retry at 1 minute. If we fail in our next
# upload attempt, we try again 1minute 12 seconds later etc.
UploadFailBackoffPct= 20
# Maximum amount of time, in seconds, upload will wait for response from
# repository before timing out.
# 0 means infinite.
UploadTimeout=1800
# Timeout for upload a file, HealthMonitor will abort the EMD process if
# UploadManager does not finish uploading one file within this time
# Unit is minite, the default value is 1 hour ( 15 Min)
#UploadMaxTime=15
# How big the file the collector will upload (in KB)
# the actual file size could be slightly bigger.
# This is only a guidance.
UploadFileSize=2048
# The maximum number of megabytes(MB) the upload manager will support in the
# upload directory before temporarily being disabled
UploadMaxBytesXML=50
# The maximum number of files the upload manager will support in the
# upload directory before temporarily being disabled
UploadMaxNumberXML=5000
# The maximum amount (%) of disk space that can be used on the EMD filesystem
# before the following is disabled:
# - Collection of data (upload manager)
# - Logging and tracing
UploadMaxDiskUsedPct=98
# The amount (%) of disk space that can be used on the EMD filesystem
# before the following is re-enabled after being disabled previously:
# - Collection of data (upload manager)
# - Logging and tracing
UploadMaxDiskUsedPctFloor=95
# Time out for the Agent to think that the access to the database could be
# hung. The Agent would not allow more threads to go and hang with a database
# if any one access to the database does not return within DbHangTimeout
# seconds.
# The more the timeout more the possibility of allowing more threads
# to be hung in the EMD with a bad database.it is specified in seconds.
#DbHangTimeout=200
# The script to run if disk space usage exceeds parameters or if certain other
# error conditions occur.
#emdFailureScript=emdfail.command
# The location of the file that contains the root certificate.
emdRootCertLoc=/u01/app/oracle/product/oms10g/sysman/config/b64LocalCertificate.txt
internetCertLoc=/u01/app/oracle/product/oms10g/sysman/config/b64InternetCertificate.txt
# The download URL for the EMD Oracle Wallet and its local file location.
# Note: Ensure that this URL references a valid port number at which the
# console is available on http
emdWalletSrcUrl=http://db1p:4889/em/wallets/emd
emdWalletDest=/u01/app/oracle/product/oms10g/sysman/config/server
# The email address for out-of-band notifications
emd_email_address=
emd_email_gateway=
# The return email address for out-of-band notifications
emd_from_email_address=
# EMD main servlet URL
# EMD_URL=http://db1p:1157/emd/main/
EMD_URL=http://db1p:1831/emd/main/
# Whether the EMD should listen on all NICs on the current host (the default)
# or just the NIC associated with the hostname in EMD_URL
AgentListenOnAllNICs=TRUE
# This parameter indicates the thread model to use. uncomment one of the
# following ThreadPoolModel line to indicate the model, agent need to use.
# SMALL if number of targets is less than 11.
# MEDIUM if number of targets is from 11 to 50.
# LARGE if number of targets is greater than 50.
# This parameter can be overriden by 'MaxThreads' which indicates the maximum
# number of threads that CEMD can have running at any point of time. User can
# mostly use the other parameter ThreadPoolModel to indicate what model for the
# agent to use.
# ThreadPoolModel = SMALL
# ThreadPoolModel = MEDIUM
# ThreadPoolModel = LARGE
# This parameter indicates the stack size, threads have to be created with.
# we can set it to 0 to use the OS default value.
# In some version of solaris(such as 2.9 ) specify a stack size may cause Java Hotspot warning
# when JVM is used.
NormalThreadStackSize=0
#Signals that users want to ignore.
#It can be one or combination of SIGTERM, SIGINT
# The signals can listed with ',' as delimiter.
#IgnoreSignals=
# This property is NO LONGER USED for host config collection (instead, hostConfigClasspath is used).
# If noone else uses it, it can be removed.
ouiLoc=/u01/app/oracle/product/oms10g/oui
# Classpath for host config collection
# VERY IMPORTANT NOTE: If you change the host config classpath entries in this section, you HAVE
# to change the HOST_CONFIG_TEST_CLASSPATH entry in the utl/emdwqaenv file too.
# NOTE: if the location of emd_java.jar and/or log4j-core.jar is changed
# make sure that appropriate changes are also made
# to the CLASSPATH variable in this file if necessary
# PORTING NOTE: Check OUI-required jar files for OUI APIs to work. They could be different on your platform.
# Also, our version of xmlparserv2.jar must be compatible with the one OUI expects (both OUI and ECM use XML parser).
hostConfigClasspath=/u01/app/oracle/product/oms10g/oui/jlib/xmlparserv2.jar:/u01/app/oracle/product/oms10g/oui/jlib/OraInstaller.jar:/u01/app/oracle/product/oms10g/oui/jlib/srvm.jar:/u01/app/oracle/product/oms10g/oui/jlib/share.jar:/u01/app/oracle/product/oms10g/sysman/jlib/emd_java.jar:/u01/app/oracle/product/oms10g/sysman/jlib/log4j-core.jar
# JAVA HOME required for JavaExt metric calls
JAVA_HOME=/u01/app/oracle/product/oms10g/jdk/jre
# CLASSPATH required for JavaExt metric calls
CLASSPATH=/u01/app/oracle/product/oms10g/sysman/jlib/emd_java.jar:/u01/app/oracle/product/oms10g/opmn/lib/ons.jar:/u01/app/oracle/product/oms10g/lib/xmlparserv2.jar:/u01/app/oracle/product/oms10g/sysman/jlib/log4j-core.jar:/u01/app/oracle/product/oms10g/j2ee/home/lib/http_client.jar:/u01/app/oracle/product/oms10g/lib/dms.jar:/u01/app/oracle/product/oms10g/lib/dmsEmd.jar:/u01/app/oracle/product/oms10g/jlib/share.jar:/u01/app/oracle/product/oms10g/jdbc/lib/ojdbc14dms.jar:/u01/app/oracle/product/oms10g/jlib/jssl-1_1.jar:/u01/app/oracle/product/oms10g/jlib/javax-ssl-1_1.jar:/u01/app/oracle/product/oms10g/jlib/ojmisc.jar:/u01/app/oracle/product/oms10g/lib/em_test.jar:/u01/app/oracle/product/oms10g/jlib/ojmisc.jar:/u01/app/oracle/product/oms10g/jlib/repository.jar:/u01/app/oracle/product/oms10g/opmn/lib/optic.jar
# this is the java option
#JAVA_OPTIONS=-Xmx128m
# These are the optional Java flags for the in-process Java
# Native Interface (JNI)
agentJavaDefines=-Doracle.dms.refresh.wait.time=1000 -DUrlTiming.UseJSSE=true
# When set to true, the emd.log and emd.trc file will be appended by a pid
# For example:
# emd_15789.log
# emd_15789.trc
# By default, it is not set for regression test purpose.
# After installed, please uncomment this line because when EMD is restarted,
# previous log information will be lost if not set to true.
#LogFileWithPID=true
# Default log file maximum size before rolling in Kilobytes
LogFileMaxSize=4096
# Maximum number of log file roll files to maintain before deletion
LogFileMaxRolls=4
# Default trace file maximum size before rolling in Kilobytes
TrcFileMaxSize=4096
# Maximum number of trace file roll files to maintain before deletion
TrcFileMaxRolls=4
# To enable the metric browser, uncomment the following line
# This is a reloadable parameter
#enableMetricBrowser=true
# To disable Remote operations (non-reachable agent) uncomment the following
# line:
#disableRemoteOperations=true
# add an additional admin path from which the agent will read additional
# target metadata. The specified path should have the mandatory 4 directories
# under it. 1. metadata 2. scripts 3. default_collection 4. discover
#altAdminPath=<additional admin path>
# The health monitor executes callbacks in a separate thread. if for some
# reason the threads spawned from health monitor to execute callbacks are
# hung, the agent could run out of resource and freeze.
# so when the current thread count spawned from the Health monitor reaches
# this limit, the agent is bounced. the default is set to 5.
#MaxHealthMonitorThreads=5
# dynamicPropsComputeTimeout default to 30s
dynamicPropsComputeTimeout=60
# emagent perl tracing levels
# supported levels: DEBUG, INFO, WARN, ERROR
# default level is ERROR
EMAGENT_PERL_TRACE_LEVEL=ERROR
# other optional parameters for perl tracing
# EMAGENT_PERL_TRACE_DIR default to $ORACLE_HOME/sysman/log
#EMAGENT_PERL_TRACE_DIR=
# EMAGENT_PERL_TRACE_FILESIZE default to 5M
#EMAGENT_PERL_TRACE_FILESIZE=5
# this section define the logging level for each component,
# it is "reloadable", you can change the level at runtime to reset
# the logging level, but if you remove the line, it will not be
# changed.
tracelevel.main=WARN
tracelevel.emSDK.xml=WARN
tracelevel.emSDK.utl=WARN
tracelevel.ResMonitor=WARN
tracelevel.Dispatcher=WARN
tracelevel.ThreadPool=WARN
tracelevel.pingManager=WARN
tracelevel.collector=WARN
tracelevel.http=WARN
tracelevel.ssl=WARN
tracelevel.ssl.io=WARN
tracelevel.blackouts=WARN
tracelevel.upload=WARN
tracelevel.command=WARN
tracelevel.reload=WARN
tracelevel.scheduler=WARN
tracelevel.Authentication=WARN
tracelevel.metadata=WARN
tracelevel.targets=WARN
tracelevel.TargetManager=WARN
tracelevel.engine=WARN
tracelevel.javaproc=WARN
tracelevel.vpxoci=WARN
tracelevel.javavm=WARN
tracelevel.fetchlets=WARN
tracelevel.fetchlets.os=WARN
tracelevel.fetchlets.osline=WARN
tracelevel.fetchlets.oslinetok=WARN
tracelevel.fetchlets.UDM=WARN
tracelevel.fetchlets.sql=WARN
tracelevel.fetchlets.url=WARN
tracelevel.fetchlets.urllines=WARN
tracelevel.fetchlets.urllinetoken=WARN
tracelevel.fetchlets.URLTiming=WARN
tracelevel.fetchlets.propEcho=WARN
tracelevel.fetchlets.readFromFile=WARN
tracelevel.fetchlets.readMultFromFile=WARN
tracelevel.fetchlets.throwable=WARN
tracelevel.fetchlets.resourceGrab=WARN
tracelevel.fetchlets.emSDK=WARN
# The following three properties are for HTTP timeout
# Timeout value for reading Http primary header, default is 30 seconds.
httpTimeoutPrimaryHeader=30
# Timeout value for reading http secondary headers, default is 30 seconds
httpTimeoutSecondaryHeaders=30
# Timeout value for reading http body, default is 60 seconds.
httpTimeoutBody=60
agentTZRegion=America/Chicago
Here are the first bunch of lines in Emagent.trc.
2006-09-10 19:32:03 Thread-43741 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:32:07 Thread-5 ERROR command: nmejcn: received no status header from repository at http://db1p:5501/em/upload/
2006-09-10 19:32:34 Thread-43743 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:32:35 Thread-43743 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:33:05 Thread-43746 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:33:06 Thread-43746 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:33:36 Thread-43747 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:33:37 Thread-43747 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:34:08 Thread-43749 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:34:08 Thread-43749 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:34:39 Thread-43750 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:34:39 Thread-43750 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:35:10 Thread-43753 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:35:11 Thread-43753 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:35:41 Thread-43754 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:35:42 Thread-43754 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:36:13 Thread-43756 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:36:13 Thread-43756 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:36:24 Thread-5 ERROR command: nmejcn: received no status header from repository at http://db1p:5501/em/upload/
2006-09-10 19:36:44 Thread-43757 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:36:44 Thread-43757 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:37:15 Thread-43759 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:37:16 Thread-43759 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:37:46 Thread-43761 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10 19:37:47 Thread-43761 ERROR pingManager: nmepm_pingReposURL: Did not receive a response header from repository
2006-09-10
Thanks
John
Similar Messages
-
Agent is up but targets are showing
Hi
My agent is up and running. But target databases are showing Current Status Agent Unreachable
Agent Unreachable Since Nov 26, 2008 9:51:51 PM
I don't want to remove the targets and re add them back here. This will affect our
regular monthly database availability reports which we take. As scheduled
standard exports and other jobs are on hanging situation in Grid.
In the Grid what could be the reason it is showing on
databases status pending since Nov 26 2008. I have done more than 3 times agent clean restart. Agent is coming up but databases are showing not available. I configured using dbsnmp password in the Grid. Physically databases and listener is up and running.
At the emagent.trc file
Thread-636 WARN http: 4200 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
2007-09-30 16:30:51 Thread-5952 WARN http: 3968 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
2007-09-30 16:32:01 Thread-5120 WARN http: 4088 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
2007-09-30 16:33:11 Thread-1632 WARN http: 4088 Agent key mismatch for request, agentKeyLen =32,reqAgentKeyLen=32
How to generated a new key with out removing the target in the Grid?
RaoThanks bazza. Here is the output.
C:\Documents and Settings\oracle>set oracle_home=C:\Oracle\agent10g
C:\Documents and Settings\oracle>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
Protocol Version : 10.2.0.2.0
Agent Home : C:\Oracle\agent10g
Agent binaries : C:\Oracle\agent10g
Agent Process ID : 1688
Agent URL : https://SHADBWEB1.shacadd.ad.mdot.mdstate:3872/emd/main/
Repository URL : https://SHAOEMG1.shacadd.ad.mdot.mdstate:1159/em/upload
Started at : 2007-09-28 19:38:22
Started by user : SYSTEM
Last Reload : 2007-09-28 19:44:29
Last successful upload : 2007-10-01 12:24:31
Total Megabytes of XML files uploaded so far : 193.11
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 75.56%
Last successful heartbeat to OMS : 2007-10-01 12:24:35
Agent is Running and Ready
C:\Documents and Settings\oracle>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 completed successfully
C:\Documents and Settings\oracle>emctl unsecure agent
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Checking Agent for HTTP... Done.
Agent successfully stopped... Done.
Unsecuring agent... Started.
OMS Upload URL - http://SHAOEMG1.shacadd.ad.mdot.mdstate:4889/em/upload/ is lock
ed or unavailable.
Unsecuring Agent... Failed.
Agent successfully restarted... Done.
C:\Documents and Settings\oracle>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
Protocol Version : 10.2.0.2.0
Agent Home : C:\Oracle\agent10g
Agent binaries : C:\Oracle\agent10g
Agent Process ID : 2008
Agent URL : https://SHADBWEB1.shacadd.ad.mdot.mdstate:3872/emd/main/
Repository URL : https://SHAOEMG1.shacadd.ad.mdot.mdstate:1159/em/upload
Started at : 2007-10-01 12:27:22
Started by user : SYSTEM
Last Reload : 2007-10-01 12:27:22
Last successful upload : 2007-10-01 12:28:30
Total Megabytes of XML files uploaded so far : 0.13
Number of XML files pending upload : 1
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 75.56%
Last successful heartbeat to OMS : 2007-10-01 12:27:51
Agent is Running and Ready
C:\Documents and Settings\oracle>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 completed successfully
C:\Documents and Settings\oracle>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.
The Oracleagent10gAgent service is stopping...
The Oracleagent10gAgent service was stopped successfully.
C:\Documents and Settings\oracle>emctl secure agent jaibajrangbal1
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
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 C:\Oracle\agent10g/sysman/config/emd.properties
Securing agent... Successful.
C:\Documents and Settings\oracle>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.
The Oracleagent10gAgent service is starting............
The Oracleagent10gAgent service was started successfully.
C:\Documents and Settings\oracle>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
Protocol Version : 10.2.0.2.0
Agent Home : C:\Oracle\agent10g
Agent binaries : C:\Oracle\agent10g
Agent Process ID : 3008
Agent URL : https://SHADBWEB1.shacadd.ad.mdot.mdstate:3872/emd/main/
Repository URL : https://SHAOEMG1.shacadd.ad.mdot.mdstate:1159/em/upload
Started at : 2007-10-01 12:30:23
Started by user : SYSTEM
Last Reload : 2007-10-01 12:30:23
Last successful upload : 2007-10-01 12:31:15
Total Megabytes of XML files uploaded so far : 0.10
Number of XML files pending upload : 1
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 75.56%
Last successful heartbeat to OMS : 2007-10-01 12:30:49
Agent is Running and Ready
C:\Documents and Settings\oracle>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 completed successfully
Agent is showing up in the Grid. But target databases it shows as following.
Status Agent Unreachable
Status Pending Since Nov 26, 2008 9:51:51 PM EST
Last Known State
I do not understand why this Nov 26, 2008 9:51:51 PM EST is coming here.
emagent.trc file shows the following message.
Thread-5972 DEBUG TargetManager: Computing dynamic property SystemTablespaceNumber of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:40 Thread-5972 DEBUG TargetManager: Computing dynamic property SysauxTablespaceNumber of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:40 Thread-5972 DEBUG TargetManager: Computing dynamic property GetDBVersion of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:40 Thread-5972 DEBUG TargetManager: Computing dynamic property ComputeVC of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:40 Thread-5972 DEBUG TargetManager: Computing dynamic property CheckRAC of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:40 Thread-5972 DEBUG TargetManager: Computing dynamic property GetDataGuardStatus of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:40 Thread-5972 DEBUG TargetManager: Computing dynamic property instanceProps of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:41 Thread-5972 DEBUG TargetManager: Computing dynamic property esa_db_dynamic_prop of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:42 Thread-5972 DEBUG TargetManager: Computing dynamic property Config of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:42 Thread-5972 DEBUG TargetManager: Computing dynamic property PlatformLimitations of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:42 Thread-5972 DEBUG TargetManager: Computing dynamic property ServerManageability of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:42 Thread-5972 DEBUG TargetManager: Computing dynamic property GetBanner of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:42 Thread-5972 DEBUG TargetManager: Computing dynamic property MonitorConfigStatus of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:42 Thread-5972 DEBUG TargetManager: Computing dynamic property GetDumpDestination of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:42 Thread-5972 DEBUG TargetManager: Computing dynamic property GetArchiveDestination of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:42 Thread-5972 DEBUG TargetManager: Computing dynamic property DeduceAlertLogFile of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:44 Thread-5972 DEBUG TargetManager: Computing dynamic property GetCPUCount of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:44 Thread-5972 DEBUG TargetManager: Computing dynamic property EnabledFeatures of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:44 Thread-5972 DEBUG TargetManager: Computing dynamic property GetOSMInstance of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:44 Thread-5972 DEBUG TargetManager: Computing dynamic property GetNLSParam of oracle_database,OREMS.PROD.SHA
2007-10-01 12:30:44 Thread-5972 DEBUG TargetManager: Done with dynamic property evaluation for {OREMS.PROD.SHA,oracle_database}
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: nmedt_waitDynPropertyFinish for OREMS.PROD.SHA, ret=0
2007-10-01 12:30:44 Thread-2408 INFO TargetManager: save to targets.xml success
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: In getTypeAndNameForHostTarget
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: getTypeAndNameForHostTarget found host, SHADBWEB1.shacadd.ad.mdot.mdstate
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: In getTypeAndNameForHostTarget
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: getTypeAndNameForHostTarget found host, SHADBWEB1.shacadd.ad.mdot.mdstate
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: In getTypeAndNameForHostTarget
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: getTypeAndNameForHostTarget found host, SHADBWEB1.shacadd.ad.mdot.mdstate
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: In getTypeAndNameForHostTarget
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: getTypeAndNameForHostTarget found host, SHADBWEB1.shacadd.ad.mdot.mdstate
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: In getTypeAndNameForHostTarget
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: getTypeAndNameForHostTarget found host, SHADBWEB1.shacadd.ad.mdot.mdstate
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: In getTypeAndNameForHostTarget
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: getTypeAndNameForHostTarget found host, SHADBWEB1.shacadd.ad.mdot.mdstate
2007-10-01 12:30:44 Thread-2408 INFO TargetManager: TargetManager initialized
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: In getTypeAndNameForHostTarget
2007-10-01 12:30:44 Thread-2408 DEBUG TargetManager: getTypeAndNameForHostTarget found host, SHADBWEB1.shacadd.ad.mdot.mdstate
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Authentication Request Containing Allow Federation Creation by Identity Provider" is too long, truncating to "Authentication Request Containing Allow Federation Creation by I"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Authentication Request Containing Allow Federation Creation by Service Provider" is too long, truncating to "Authentication Request Containing Allow Federation Creation by S"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Federation Termination Response Sent Successfully by Identity Provider" is too long, truncating to "Federation Termination Response Sent Successfully by Identity Pr"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Signed Federation Termination Request Received by Identity Provider" is too long, truncating to "Signed Federation Termination Request Received by Identity Provi"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Federation Termination Response Received Successfully by Identity Provider" is too long, truncating to "Federation Termination Response Received Successfully by Identit"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Signed Federation Termination Response Received by Identity Provider" is too long, truncating to "Signed Federation Termination Response Received by Identity Prov"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Name Registration Response Sent Successfully by Identity Provider" is too long, truncating to "Name Registration Response Sent Successfully by Identity Provide"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Name Registration Response Received Successfully by Identity Provider" is too long, truncating to "Name Registration Response Received Successfully by Identity Pro"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Federation Termination Response Sent Successfully by Service Provider" is too long, truncating to "Federation Termination Response Sent Successfully by Service Pro"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Signed Federation Termination Request Received by Service Provider" is too long, truncating to "Signed Federation Termination Request Received by Service Provid"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Federation Termination Response Received Successfully by Service Provider" is too long, truncating to "Federation Termination Response Received Successfully by Service"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Signed Federation Termination Response Received by Service Provider" is too long, truncating to "Signed Federation Termination Response Received by Service Provi"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Name Registration Response Received Successfully by Service Provider" is too long, truncating to "Name Registration Response Received Successfully by Service Prov"
2007-10-01 12:30:44 Thread-2408 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Received By Service Provider(%)" is too long, truncating to "Successful Federation Termination Request Received By Service Pr"
2007-10-01 12:30:45 Thread-2408 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Sent By Service Provider(%)" is too long, truncating to "Successful Federation Termination Request Sent By Service Provid"
2007-10-01 12:30:45 Thread-2408 WARN collector: MESSAGE_NLSID "Successful Name Registration Request Received By Service Provider(%)" is too long, truncating to "Successful Name Registration Request Received By Service Provide"
2007-10-01 12:30:45 Thread-2408 WARN collector: MESSAGE_NLSID "Successful Authentication Request Received By Identity Provider(%)" is too long, truncating to "Successful Authentication Request Received By Identity Provider("
2007-10-01 12:30:45 Thread-2408 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Received By Identity Provider(%)" is too long, truncating to "Successful Federation Termination Request Received By Identity P"
2007-10-01 12:30:45 Thread-2408 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Sent By Identity Provider(%)" is too long, truncating to "Successful Federation Termination Request Sent By Identity Provi"
2007-10-01 12:30:45 Thread-2408 WARN collector: MESSAGE_NLSID "Successful Name Registration Request Received By Identity Provider(%)" is too long, truncating to "Successful Name Registration Request Received By Identity Provid"
2007-10-01 12:30:45 Thread-2408 WARN collector: MESSAGE_NLSID "Successful Name Registration Request Sent By Identity Provider(%)" is too long, truncating to "Successful Name Registration Request Sent By Identity Provider(%"
2007-10-01 12:30:49 Thread-2408 INFO TargetManager: save to targets.xml success
2007-10-01 12:30:50 Thread-1784 ERROR upload: Error in uploadXMLFiles. Trying again in 60.00 seconds or earlier. -
Availability tab of notification rule
Hello
When I create a notification rule, there are some options under the Availability tab like the following:
Do these stuff have any relation with my selected metric ? When should I choose them ?
I mean lets say I am monitoring broken jobs, what would be the advantage of choosing one of the below options?
Select the availability states for which you would like to receive notifications. You will receive notifications when there is a transition from another state to the selected state.
up
down
Corrective Actions on Target Down
problem Succeeded
Agent Unreachable
Agent Unreachable Resolved
Metric Error Detected
Metric Error Resolved
Blackout Started
Blackout EndedThanksThese are not related to the metrics you selected.
They mean do you want to be notified whenever:
- Agent Unreachable
- Agent Unreachable Resolved
- Metric Error Detected
- Metric Error Resolved
- Blackout Started
- Blackout Ended
So the metrics you have selected can be on top of these availability events
Regards
Rob
http://oemgc.wordpress.com -
Hi,
I have installed agent 10g on unix machine(HPUX-11.1) agent runs for 6-8 hrs
after that it dies out and when i see the db through grid control it says agent unreachable but when grep for agent it shows up and running , iam not sure whats happening here.
[oracle:leopard:NOSID] /oracle/product/agent10g/sysman/log > ps -ef|grep agen>
root 2661 1 0 May 20 ? 0:00 /etc/opt/resmon/lbin/emsagent
root 2617 1 0 May 20 ? 2:38 /usr/sbin/swagentd -r
oracle 23822 23690 0 Nov 20 ? 13:24 /oracle/product/agent10g/bin/emagent
oracle 23690 1 0 Nov 20 ? 2:54 /oracle/product/agent10g/perl/bin/perl /oracle/product/agent10g
aduaslq 16850 22944 0 Nov 23 ? 4:58 /amuaslq01s/app/amuaslqdb/10.2.0/bin/emagent---->agent is for OAM
[oracle:leopard:NOSID] /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 is Not Running
[oracle:leopard:NOSID] /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 ....... failed.
Failed to start HTTP listener.
Consult the log files in: /oracle/product/agent10g/sysman/log
[oracle:leopard:NOSID] /oracle/product/agent10g/bin > ps -ef|grep agent
root 2661 1 0 May 20 ? 0:00 /etc/opt/resmon/lbin/emsagent
root 2617 1 0 May 20 ? 2:38 /usr/sbin/swagentd -r
oracle 23822 23690 0 Nov 20 ? 13:23 /oracle/product/agent10g/bin/emagent
oracle 3913 15344 0 21:42:27 pts/7 0:00 grep agent
oracle 23690 1 0 Nov 20 ? 2:53 /oracle/product/agent10g/perl/bin/perl /oracle/product/agent10g
aduaslq 16850 22944 0 Nov 23 ? 4:57 /amuaslq01s/app/amuaslqdb/10.2.0/bin/emagent
/oracle/product/agent10g/sysman/log :vi emagent.trc
2007-11-27 17:48:44 Thread-189993 ERROR util.files: ERROR: nmeufos_new: failed i
n lfiopn on file: /oracle/product/agent10g/sysman/emd/agntstmp.txt.error = 24 (T
oo many open files)
2007-11-27 17:48:44 Thread-189993 ERROR pingManager: Error in updating the agent
time stamp file
2007-11-27 17:48:48 Thread-189994 ERROR util.fileops: ERROR: snmeuf_dirlist can'
t list directory: /oracle/product/agent10g/sysman/emd/upload: Too many open file
s (errno=24)
2007-11-27 17:48:51 Thread-189995 ERROR engine: Failed when generating a new ECI
D.
2007-11-27 17:48:51 Thread-189995 ERROR fetchlets.healthCheck: GIM-00104: file n
ot found
LEM-00031: file not found; arguments: [lempgmh] [lmserr]
LEM-00033: file not found; arguments: [lempgfm] [Couldn't open message file]
LEM-00031: file not found; arguments: [lempgmh] [lmserr]
2007-11-27 17:48:51 Thread-189995 ERROR engine: [oracle_database,leopard-amuaslq
.am,health_check] : nmeegd_GetMetricData failed : Instance Health Check initiali
zation failed due to one of the following causes: the owner of the EM agent proc
ess is not same as the owner of the Oracle instance processes; the owner of the
EM agent process is not part of the dba group; or the database version is not 10
g (10.1.0.2) and above.
Please Any suggestions.As per note_id:430805.1
3. We now need to focus also on the monitored database side. This section takes place in the monitored RDBMS Oracle Home:
If the monitored database is 10gR1 (10.1.x):
10.1.0.4: you need to apply Patch 5868695 on the RDBMS Oracle Home, otherwise the Healthcheck metric will still fail, despite the code fix applied on the Agent side.
10.1.0.5: At this moment, this specific one-off patch is not available on top of RDBMS 10.1.0.5. Please contact support if you need this fix for RDBMS 10.1.0.5 on HP-UX.
10.1.0.3, 10.1.0.2: consider patching / upgrading
If the monitored database is 10gR2 (10.2.x):
10.2.0.3 (and above): nothing to be done. The fix is already included.
10.2.0.2: Apply the Patch 4559294 in the RDBMS Oracle Home by following instructions given in the README.
My concern is what if we have 8i and 9i monitored databases?Please let me know. -
Oracle Management Console 10g - Job Status - Suspended on Agent Unreachable
Recently we updated our RDMS from 10.2.0.1 to 10.2.0.4.0 PATCH 25.
Ever since we upgraded, we have had trouble with our RMAN backups. Now when a scheduled backup begins it never ends. Now whenever we schedule a job, from a backup to any simple system command, the status immediately returns "Suspended on Agent Unreachable".
We can start and stop the dbconsole successfully, and I can use the OEM to monitor the database, and make changes to that. However, I cannot run any scheduled database jobs through the OEM. However, I can run the rman jobs via the command line.
The database server, and the OEM console is on the save server. I am not running RAC. Everything database related is on this one server.
Here are the results for emctl status agent:
E:\oracle\product\10.2.0\db_1\BIN>emctl status agent
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.1.0.6.0
OMS Version : 10.1.0.6.0
Protocol Version : 10.1.0.2.0
Agent Home : E:\oracle\product\10.2.0\db_1\content.mydomain.com_ORCL
Agent binaries : E:\oracle\product\10.2.0\db_1
Agent Process ID : 34372
Agent URL : http://content.mydomain.com:3938/emd/main
Started at : 2010-01-11 14:58:24
Started by user : SYSTEM
Last Reload : 2010-01-11 14:58:24
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 5016
Size of XML files pending upload(MB) : 42.77
Available disk space on upload filesystem : 37.94%
Agent is Running and ReadyHere are the results for emctl status agent:
E:\oracle\product\10.2.0\db_1\BIN>emctl upload
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
EMD upload error: uploadXMLFiles skipped :: OMS version not checked yet..I think the EMD upload error may be the problem, but I'm unsure how to resolve this.
What do I need to do in order to resolve this issue?
If any more info would be useful, please let me know and I will post it immediately.
thanks.Rondeyli,
Thanks, that was it. I followed your instructions, and was able to get the system to work. I had to alter the commands a bit to get them to work on my system, so here is what I did.
I performed the following steps:
1. Ran the following command:
emctl stop dbconsole
2. deleted all files in $AGENT_HOME/sysman/emd/upload and $AGENT_HOME/sysman/emd/state
3. Ran the following command:
emctl clearstate dbconsole
4. Ran the following command:
emctl secure dbconsole
5. Ran the following command:
emctl start dbconsoleThis got everything running for me.
thanks. -
EM 10g Database Control - Status: Agent Unreachable
Hi,
OS: AIX 5L
Database: Oracle Database 10g Enterprise Edition Release 10.1.0.2.0 - 64bit
We have installed 2 instances with EM 10g database control option.
At the end EM was running over the second database.
Then we switch it to look over the first one by reconfiguring these files:
$ORACLE_HOME/sysman/config/emd.properties;
$ORACLE_HOME/sysman/config/pref/dbastudio-oradba.crd.
Now EM seems to work fine except for this error: Agent Unreachable.
oradba@aix09(:SIGP)/u01/apps/oradba/product/10.1.0/aix09_SIGP/sysman/log > emctl status agent
Oracle Enterprise Manager 10g Database Control Release 10.1.0.2.0
Copyright (c) 1996, 2004 Oracle Corporation. All rights reserved.
Agent Version : 10.1.0.2.0
OMS Version : 10.1.0.2.0
Protocol Version : 10.1.0.2.0
Agent Home : /u01/apps/oradba/product/10.1.0/aix09_SIGP
Agent binaries : /u01/apps/oradba/product/10.1.0
Agent Process ID : 4284428
Parent Process ID : 3399760
Agent URL : http://aix09:1830/emd/main
Started at : 2004-08-09 12:24:29
Started by user : oradba
Last Reload : 2004-08-09 12:24:29
Last successful upload : (none)
Last attempted upload : 2004-08-09 14:29:51
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 1955
Size of XML files pending upload(MB) : 50.12
Available disk space on upload filesystem : 4.60%
Agent is Running and Ready
/aix09_SIGP/sysman/log/ emagent.trc:
2004-08-09 14:31:53 Thread-1910 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2004-08-09 14:31:53 Thread-1910 WARN upload: FxferSend: received http error in header from repository: http:/
/aix09:5500/em/upload/
ERROR-400|ORA-04020: deadlock detected while trying to lock object 30x700000021709BF80x700000021B01D200x700000
0267473A8
2004-08-09 14:31:53 Thread-1910 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2004-08-09 14:31:53 Thread-1910 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
2004-08-09 14:31:53 Thread-1910 ERROR upload: Error in uploadXMLFiles. Trying again in 300.00 seconds.
After connecting as sysman Ive ran these statements:
SQL> SELECT emd_url
2 FROM mgmt_targets t
3 WHERE t.target_name = 'aix09'
4 AND t.target_type = 'host';
EMD_URL
http://aix09:1830/emd/main
SQL> SELECT t.target_name, t.target_type,
2 TO_CHAR(t.load_timestamp,'DD-MON-YYYY HH24:MI:SS') "discovery_time
3 TO_CHAR(t.last_updated_time,'DD-MON-YYYY HH24:MI:SS') "last_metada
ta_load",
4 TO_CHAR(a.marker_timestamp,'DD-MON-YYYY HH24:MI:SS') "last_severit
y_load",
5 TO_CHAR(t.last_load_time,'DD-MON-YYYY HH24:MI:SS') "last_metric_lo
ad"
6 FROM mgmt_targets t, mgmt_availability_marker a
7 WHERE t.target_guid = a.target_guid
8 AND t.target_name = 'aix09'
9 AND t.target_type = 'host';
TARGET_NAME
TARGET_TYPE discovery_time
last_metadata_load last_severity_load last_metric_load
aix09
host 03-AUG-2004 14:47:55
05-AUG-2004 18:28:45 05-AUG-2004 18:30:42 05-AUG-2004 17:13:55
Does any one know what do I have to do to solve this problem ?
Thanks in advance,
VitorCan you start a browser on the client machine?
(netscape/mozilla) and try to load
http://aix09:1830/emd/main
Make sure both the client and the OMS server can resolve aix09 hostname
Make sure the client can resolve the OMS server name. -
Backup Suspended on Agent Unreachable - 11GR2 Windows
Hi as the title suggests an RMAN backup has gone into a state of Suspended on Agent Unreachable.
I have a 2 node RAC and have run emctl status dbconsole on each node. On node 1 I get a message: EM Daemon is running. On node 2 I get a message: Oracle enterprise Manager 11g is running.
Why are these messages different? and could this be the reason why the job has gone into the state it has?
Thanks in advanceI strongly suggest to not using RMAN via OEM, but with the good old command line.
The messages are different because on one node there is the real web app (oc4j...) while on the other one there is only the agent running so it is expected.
Alessio -
DBConsole says 'Agent Unreachable' after database restore & recovery
Hi,
Last week our server crashed and I had to completely re-install oracle and then restore/recover our database. Now everything is back up, but when I try to access the online DBConsole (http://localhost:5500/em), the status says 'Agent Unreachable'.
I checked the status of the agent and it said Agent is Running and Ready.
I was told that if the agent was not restored, it may be out of sync -- but I don't know how to sync it.
Does anybody know how I can resolve this problem?
Thanks in advance,
NoraAs per note_id:430805.1
3. We now need to focus also on the monitored database side. This section takes place in the monitored RDBMS Oracle Home:
If the monitored database is 10gR1 (10.1.x):
10.1.0.4: you need to apply Patch 5868695 on the RDBMS Oracle Home, otherwise the Healthcheck metric will still fail, despite the code fix applied on the Agent side.
10.1.0.5: At this moment, this specific one-off patch is not available on top of RDBMS 10.1.0.5. Please contact support if you need this fix for RDBMS 10.1.0.5 on HP-UX.
10.1.0.3, 10.1.0.2: consider patching / upgrading
If the monitored database is 10gR2 (10.2.x):
10.2.0.3 (and above): nothing to be done. The fix is already included.
10.2.0.2: Apply the Patch 4559294 in the RDBMS Oracle Home by following instructions given in the README.
My concern is what if we have 8i and 9i monitored databases?Please let me know. -
OMS showing agent unreachable but agent is up
Greetings !!!!!!!!!!!!!
When I open the targets I see that for this particular host it is showing agent unreachable but if I do following on hte machine where agent is running I get:
$ /u01/app/oracle/product/10.2/agent/agent10g/bin/emctl status agent -secure
Oracle Enterprise Manager 10g Release 3 Grid Control 10.2.0.3.0.
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Checking the security status of the Agent at location set in /u01/app/oracle/product/10.2/agent/agent10g/sysman/config/emd.properties... Done.
Agent is secure at HTTPS Port 3872.
Checking the security status of the OMS at http://grid:4889/em/upload/... Done.
OMS is secure on HTTPS Port 1159
oracle : dg01 : @test : /u01/app/oracle
$
MAy I know why grid is showing hte agent is not reachable even thought the agent is running and can talk to OMS:
The following is the output from the agent installation machine:
$ /u01/app/oracle/product/10.2/agent/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
Protocol Version : 10.2.0.2.0
Agent Home : /u01/app/oracle/product/10.2/agent/agent10g
Agent binaries : /u01/app/oracle/product/10.2/agent/agent10g
Agent Process ID : 10105
Parent Process ID : 10062
Agent URL : https://dg01:3872/emd/main/
Repository URL : https://grid:1159/em/upload
Started at : 2008-06-26 00:36:00
Started by user : oracle
Last Reload : 2008-06-26 00:36:00
Last successful upload : 2008-06-26 06:46:03
Total Megabytes of XML files uploaded so far : 34.76
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0.00
Available disk space on upload filesystem : 40.38%
Last successful heartbeat to OMS : 2008-06-26 06:54:47
Agent is Running and Ready
oracle : dg01 : @test : /u01/app/oracle
$
Thanks in Advance
RegardsMohammed, thanks for your time and reply and showing consideration to this thread.
I bounced the agent and got the following:
$ /u01/app/oracle/product/10.2/agent/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.
oracle : dg01 : @test : /u01/app/oracle
$ /u01/app/oracle/product/10.2/agent/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.
oracle : dg01 : @test : /u01/app/oracle
$ /u01/app/oracle/product/10.2/agent/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
Protocol Version : 10.2.0.2.0
Agent Home : /u01/app/oracle/product/10.2/agent/agent10g
Agent binaries : /u01/app/oracle/product/10.2/agent/agent10g
Agent Process ID : 11692
Parent Process ID : 11649
Agent URL : https://dg01:3872/emd/main/
Repository URL : https://grid:1159/em/upload
Started at : 2008-06-26 14:32:46
Started by user : oracle
Last Reload : 2008-06-26 14:32:46
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 15
Size of XML files pending upload(MB) : 6.06
Available disk space on upload filesystem : 40.30%
Last successful heartbeat to OMS : 2008-06-26 14:32:50
Agent is Running and Ready
oracle : dg01 : @test : /u01/app/oracle
$ date
Thu Jun 26 10:04:41 PDT 2008
oracle : dg01 : @test : /u01/app/oracle
$
But even now grid is showing me agent not reachable......
Here are the files that you requested. Can you please tell me the location of emoms.trc, couldn't find it.
$ ls -lart
total 1964
-rw-r----- 1 oracle dba 0 Jun 23 03:05 emdctl.log
drwxr-xr-x 12 oracle dba 4096 Jun 23 03:05 ..
-rw-r----- 1 oracle dba 0 Jun 23 03:11 emagentfetchlet.trc
-rw-r----- 1 oracle dba 0 Jun 23 03:11 emagentfetchlet.log
-rw-r----- 1 oracle dba 0 Jun 23 03:11 nfsPatchPlug.log
drwxr-xr-x 2 oracle dba 4096 Jun 23 07:37 .
-rw-r----- 1 oracle dba 1086 Jun 23 13:21 agabend.log.lr
-rw-r----- 1 oracle dba 11132 Jun 26 02:21 secure.log
-rw-r----- 1 oracle dba 1327 Jun 26 10:02 agabend.log
-rw-r----- 1 oracle dba 348790 Jun 26 10:02 emdctl.trc
-rw-r----- 1 oracle dba 70426 Jun 26 10:02 emagent.nohup
-rw-r----- 1 oracle dba 32998 Jun 26 10:02 emagent.log
-rw-r----- 1 oracle dba 31408 Jun 26 10:03 emctl.log
-rw-r----- 1 oracle dba 42996 Jun 26 10:04 emagent_perl.trc
-rw-r----- 1 oracle dba 1425694 Jun 26 10:05 emagent.trc
oracle : dg01 : @test : /u01/app/oracle/product/10.2/agent/agent10g/sysman/log
$
========================================================
$ tail -200 emagent.trc
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_timeout does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_total can't define table_name: umsg_pop_connections_count
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_total does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric network_transmit can't define table_name: umsg_pop_network_transmit
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric network_transmit does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric network_receive can't define table_name: umsg_pop_network_receive
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric network_receive does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric Function calls can't define table_name: mail_pop_functions
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_sarm_overview can't define table_name: siebel_component_sarm_overview
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_task_overview can't define table_name: siebel_component_task_overview
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_overview can't define table_name: siebel_component_overview
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_resource_overview can't define table_name: siebel_component_resource_overview
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_database_overview can't define table_name: siebel_component_database_overview
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_component_group_overview can't define table_name: siebel_component_group_overview
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelSales can't define table_name: SiebelSalesBusinessMetrics
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelESales can't define table_name: SiebelESalesBusinessMetrics
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelService can't define table_name: SiebelServiceBusinessMetrics
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelSelfService can't define table_name: SiebelSelfServiceBusinessMetrics
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelMarketing can't define table_name: SiebelMarketingBusinessMetrics
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelPartnerManagement can't define table_name: SiebelPartnerManagementBusinessMetrics
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelUniversalCustomerMaster can't define table_name: SiebelUniversalCustomerMasterBusinessMetrics
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric SiebelFinancialServices can't define table_name: SiebelFinancialServicesBusinessMetrics
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_server_database_overview can't define table_name: siebel_server_database_overview
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_server_resource_overview can't define table_name: siebel_server_resource_overview
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric siebel_server_overview can't define table_name: siebel_server_overview
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric uptime can't define table_name: mail_imap_health
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric uptime does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric uptime can't define table_name: mail_smtpi_health
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections can't define table_name: mail_mta_connections
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_current can't define table_name: smtpin_connections_current
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_current does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmit can't define table_name: mail_mta_transmit
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric receive can't define table_name: mail_mta_receive
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_received can't define table_name: umsg_smtpin_messages_received
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_received does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgsize can't define table_name: umsg_smtpin_messages_avgsize
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgdeliverytime can't define table_name: umsg_smtpin_messages_avgtime
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmission_response can't define table_name: umsg_smtpin_transmission_reponse
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric network_connection_total can't define table_name: umsg_smtpin_network_connection_total
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric network_connection_total does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric network_receive_bytes can't define table_name: umsg_smtpin_network_receive_bytes
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric network_receive_bytes does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_receive_dl can't define table_name: umsg_smtpin_message_receive_dl
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_receive_dl does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_deferred can't define table_name: umsg_smtpin_messages_deferred
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_deferred does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgreceip can't define table_name: umsg_smtpin_message_avgreceip
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_avgreceip does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric uptime can't define table_name: mail_smtpo_health
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections can't define table_name: mail_mta_connections
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmit can't define table_name: mail_mta_transmit
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_current can't define table_name: umsg_smtpout_connections_current
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_current does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_transmitted can't define table_name: umsg_smtpout_messages_transmitted
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric messages_transmitted does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgsize can't define table_name: umsg_smtpout_messages_avgsize
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgdeliverytime can't define table_name: umsg_smtpout_messages_avgtime
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgdeliverytime_local can't define table_name: umsg_smtpout_messages_avgtime_local
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgdeliverytime_remote can't define table_name: umsg_smtpout_messages_avgtime_remote
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric messages_avgrelay_time can't define table_name: umsg_smtpout_messages_avgtime_relay
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric delivery_performance can't define table_name: umsg_smtpout_delivery_performance
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric relay_performance can't define table_name: umsg_smtpout_messages_avgtime_relay
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric relay_performance does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_outbound can't define table_name: umsg_smtpout_connections_outbound
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_outbound does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_outbound_local can't define table_name: umsg_smtpout_connections_outbound_local
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_outbound_local does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric connections_outbound_remote can't define table_name: umsg_smtpout_connections_outbound_remote
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric connections_outbound_remote does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmitted_bytes can't define table_name: umsg_smtpout_transmitted_bytes
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric transmitted_bytes does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: TABLE metric transmission_rate can't define table_name: umsg_smtpout_transmission_rate
2008-06-26 14:32:48 Thread-3086935744 WARN metadata: Metric transmission_rate does not have any data columns
2008-06-26 14:32:48 Thread-3086935744 INFO TargetManager: nmeetm_setDynPropReComputeParam: Values have been retrieved dynamicPropReComputeInterval = 120 dynamicPropReComputeMaxTries = 4
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: call nmedt_waitDynPropertyFinish for dg01:3872
2008-06-26 14:32:48 Thread-28801952 DEBUG TargetManager: Computing dynamic properties for {dg01:3872, oracle_emd}
2008-06-26 14:32:48 Thread-28801952 DEBUG TargetManager: Computing dynamic property VersionAndLocation of oracle_emd,dg01:3872
2008-06-26 14:32:48 Thread-28801952 DEBUG TargetManager: Done with dynamic property evaluation for {dg01:3872,oracle_emd}
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmedt_waitDynPropertyFinish for dg01:3872, ret=0
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent> Entering function
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: for target {host:dg01} assocName:cluster_instance, assocType:cluster
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {oracle_emd:dg01:3872} for inclusion as assoc instance for {host:dg01}
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type oracle_emd do not match ignoring
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {host:dg01} for inclusion as assoc instance for {host:dg01}
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type host do not match ignoring
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {oracle_listener:LISTENER_dg01} for inclusion as assoc instance for {host:dg01}
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type oracle_listener do not match ignoring
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {oracle_database:test} for inclusion as assoc instance for {host:dg01}
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type oracle_database do not match ignoring
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: Examining target {osm_instance:+ASM_dg01} for inclusion as assoc instance for {host:dg01}
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmeetm.c:<nmeetm_constructAssocInstancesUsingParent>: assocTgType cluster and type osm_instance do not match ignoring
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: call nmedt_waitDynPropertyFinish for dg01
2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic properties for {dg01, host}
2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property from_cluster of host,dg01
2008-06-26 14:32:48 Thread-32218016 WARN TargetManager: Query returned 0 rows (only one expected) for the dynamic property from_cluster
2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property getCRSVCategory of host,dg01
2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property Config of host,dg01
2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property HardwareInfo of host,dg01
2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Computing dynamic property esa_dyn_prop of host,dg01
2008-06-26 14:32:48 Thread-32218016 DEBUG TargetManager: Done with dynamic property evaluation for {dg01,host}
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmedt_waitDynPropertyFinish for dg01, ret=0
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: call nmedt_waitDynPropertyFinish for LISTENER_dg01
2008-06-26 14:32:48 Thread-49335200 DEBUG TargetManager: Computing dynamic properties for {LISTENER_dg01, oracle_listener}
2008-06-26 14:32:48 Thread-49335200 DEBUG TargetManager: Computing dynamic property esaMaxRowCount of oracle_listener,LISTENER_dg01
2008-06-26 14:32:48 Thread-49335200 DEBUG TargetManager: Done with dynamic property evaluation for {LISTENER_dg01,oracle_listener}
2008-06-26 14:32:48 Thread-3086935744 DEBUG TargetManager: nmedt_waitDynPropertyFinish for LISTENER_dg01, ret=0
2008-06-26 14:32:48 Thread-3086935744 ERROR TargetManager: Skipping target {test, oracle_database}: Missing properties - password
2008-06-26 14:32:48 Thread-3086935744 ERROR TargetManager: Skipping target {+ASM_dg01, osm_instance}: Missing properties - password
2008-06-26 14:32:48 Thread-3086935744 INFO TargetManager: save to targets.xml success
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
2008-06-26 14:32:50 Thread-3086935744 INFO TargetManager: TargetManager initialized
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: In getTypeAndNameForHostTarget
2008-06-26 14:32:50 Thread-3086935744 DEBUG TargetManager: getTypeAndNameForHostTarget found host, dg01
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Authentication Request Containing Allow Federation Creation by Identity Provider" is too long, truncating to "Authentication Request Containing Allow Federation Creation by I"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Authentication Request Containing Allow Federation Creation by Service Provider" is too long, truncating to "Authentication Request Containing Allow Federation Creation by S"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Federation Termination Response Sent Successfully by Identity Provider" is too long, truncating to "Federation Termination Response Sent Successfully by Identity Pr"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Signed Federation Termination Request Received by Identity Provider" is too long, truncating to "Signed Federation Termination Request Received by Identity Provi"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Federation Termination Response Received Successfully by Identity Provider" is too long, truncating to "Federation Termination Response Received Successfully by Identit"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Signed Federation Termination Response Received by Identity Provider" is too long, truncating to "Signed Federation Termination Response Received by Identity Prov"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Name Registration Response Sent Successfully by Identity Provider" is too long, truncating to "Name Registration Response Sent Successfully by Identity Provide"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Name Registration Response Received Successfully by Identity Provider" is too long, truncating to "Name Registration Response Received Successfully by Identity Pro"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Federation Termination Response Sent Successfully by Service Provider" is too long, truncating to "Federation Termination Response Sent Successfully by Service Pro"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Signed Federation Termination Request Received by Service Provider" is too long, truncating to "Signed Federation Termination Request Received by Service Provid"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Federation Termination Response Received Successfully by Service Provider" is too long, truncating to "Federation Termination Response Received Successfully by Service"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Signed Federation Termination Response Received by Service Provider" is too long, truncating to "Signed Federation Termination Response Received by Service Provi"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Name Registration Response Received Successfully by Service Provider" is too long, truncating to "Name Registration Response Received Successfully by Service Prov"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Received By Service Provider(%)" is too long, truncating to "Successful Federation Termination Request Received By Service Pr"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Sent By Service Provider(%)" is too long, truncating to "Successful Federation Termination Request Sent By Service Provid"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Name Registration Request Received By Service Provider(%)" is too long, truncating to "Successful Name Registration Request Received By Service Provide"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Authentication Request Received By Identity Provider(%)" is too long, truncating to "Successful Authentication Request Received By Identity Provider("
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Received By Identity Provider(%)" is too long, truncating to "Successful Federation Termination Request Received By Identity P"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Federation Termination Request Sent By Identity Provider(%)" is too long, truncating to "Successful Federation Termination Request Sent By Identity Provi"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Name Registration Request Received By Identity Provider(%)" is too long, truncating to "Successful Name Registration Request Received By Identity Provid"
2008-06-26 14:32:50 Thread-3086935744 WARN collector: MESSAGE_NLSID "Successful Name Registration Request Sent By Identity Provider(%)" is too long, truncating to "Successful Name Registration Request Sent By Identity Provider(%"
2008-06-26 14:32:50 Thread-3086935744 INFO TargetManager: save to targets.xml success
2008-06-26 14:32:50 Thread-32218016 ERROR upload: Error in uploadXMLFiles. Trying again in 60.00 seconds or earlier.
2008-06-26 14:33:15 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:15 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:15 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:15 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:15 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:15 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:15 Thread-28801952 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
2008-06-26 14:33:15 Thread-28801952 ERROR upload: Error in uploadXMLFiles. Trying again in 72.00 seconds or earlier.
2008-06-26 14:33:34 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:34 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:35 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:35 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:35 Thread-28801952 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:35 Thread-28801952 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:35 Thread-28801952 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
2008-06-26 14:33:35 Thread-28801952 ERROR upload: Error in uploadXMLFiles. Trying again in 86.00 seconds or earlier.
2008-06-26 14:33:50 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:50 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:50 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:50 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:51 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:51 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:51 Thread-32218016 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
2008-06-26 14:33:51 Thread-32218016 ERROR upload: Error in uploadXMLFiles. Trying again in 103.00 seconds or earlier.
2008-06-26 14:33:52 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:52 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:53 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:53 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:53 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:33:53 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:33:53 Thread-32218016 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
2008-06-26 14:33:53 Thread-32218016 ERROR upload: Error in uploadXMLFiles. Trying again in 123.00 seconds or earlier.
2008-06-26 14:35:57 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:35:57 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:35:57 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:35:57 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:35:58 Thread-32218016 WARN upload: FxferSend: received http error in header from repository: https://grid:1159/em/upload
ERROR-100|No space left on device
2008-06-26 14:35:58 Thread-32218016 ERROR upload: Failed to upload file A0000001.xml, ret = -2
2008-06-26 14:35:58 Thread-32218016 ERROR upload: 3 Failures in a row for A0000001.xml, we give up
2008-06-26 14:35:58 Thread-32218016 ERROR upload: Error in uploadXMLFiles. Trying again in 147.00 seconds or earlier.
oracle : dg01 : @test : /u01/app/oracle/product/10.2/agent/agent10g/sysman/log
$ -
OEM 10g - Job Status - Suspended on Agent Unreachable
Hi,
I have checked out a few post on this forum which is similar to my problem.
But could not get the exact workaround.
The scheduled backup is not getting failed / successful since 29th January 2010.
We have not made any changes on the database level. But there was a patching activity at application level.
and as soon as I try to schedule a backup it shows the same status "suspended on agent unreachable"
I have checked the emctl status and dbconsole status.
E:\oracle\product\10.2.0\db_1\BIN>emctl status agent
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
Agent Version : 10.1.0.6.0
OMS Version : 10.1.0.6.0
Protocol Version : 10.1.0.2.0
Agent Home : e:\oracle\product\10.2.0\db_1\content.mydomain.de_aeb
Agent binaries : e:\oracle\product\10.2.0\db_1
Agent Process ID : 6104
Agent URL : http://content.mydomain.de:3938/emd/main
Started at : 2010-02-01 21:55:19
Started by user : SYSTEM
Last Reload : 2010-02-01 21:55:19
Last successful upload : 2010-02-17 06:12:10
Last attempted upload : 2010-02-17 06:12:25
Total Megabytes of XML files uploaded so far : 323.40
Number of XML files pending upload : 1
Size of XML files pending upload(MB) : 0.01
Available disk space on upload filesystem : 9.36%
Agent is Running and Ready
E:\oracle\product\10.2.0\db_1\BIN>emctl status dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
http://content.mydomain.de:1158/em/console/aboutApplication
Oracle Enterprise Manager 10g is running.
Logs are generated in directory e:\oracle\product\10.2.0\db_1/scontent.mydomain.de_AEB/sysman/log
Upload also seems to be working fine.
E:\oracle\product\10.2.0\db_1\BIN>emctl upload
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
EMD upload completed successfully
What should I do ? Will restarting the agent help ? Will restarting the agent have any adverse effect on DB ?
Any help would be a great help.
RushabhHi,
This is urgent.. Please help..
I am not able to start the emctl...
Below is the error that I am getting..
E:\oracle\product\10.2.0\db_1\BIN>emctl stop agent
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
This will stop the Oracle Enterprise Manager 10g Database Control process. Conti
nue [y/n] :y
The OracleDBConsoleaeb service is stopping..........
The OracleDBConsoleaeb service was stopped successfully.
E:\oracle\product\10.2.0\db_1\BIN>emctl clearstate agent
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
EMD clearstate completed successfully
E:\oracle\product\10.2.0\db_1\BIN>emctl secure agent
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.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... Failed.
The OMS is not set up for Enterprise Manager Security.
E:\oracle\product\10.2.0\db_1\BIN>emctl start agent
Oracle Enterprise Manager 10g Database Control Release 10.2.0.4.0
Copyright (c) 1996, 2007 Oracle Corporation. All rights reserved.
The service name is invalid.
More help is available by typing NET HELPMSG 2185.
When I try to secure agent it is asking for a password, but it is already saved I think..
When I press enter it is showing the above error.
What should I do now ?
Regards,
Rushabh
Edited by: user650383 on Feb 16, 2010 10:44 PM -
Status: Agent Unreachable
Hi,
I have installed 10g. I could access the EM very easily, once all the required services were started. it was http://host:5500/em
Then I installed another database, other than the default which was orcl.
Then the port number changed (I do not know why, but when I looked in portlist.ini) just to try different ports, I figured out, it was not
http://host:5502/em
when I hit it, it prompts for userid and password. I was so happy looking at this screen, but once I enter the userid and password, what is get is
Status: Agent Unreachable with Startup/Shutdown option. When I click on it, I get error "500 Internal Server Error" in my browser.
Thanks in advanceIf you have done two different Oracle Installations that will use different Standalone DB Console and two different Agents, your system may have had a problem starting the two agents.
If you are using Windows, have a look at Services to see the Agents which has the name of the new ORACLE_HOME as part of the name. Start the Agent. If you have a problem starting thet new one, stop the first one you installed, then start the new one. -
One of the monitored SuSE Linux host in my Grid OEM has status "Agent unreachable". As such the host has not been monitored. It was ok before and I am not sure why (and from when) it has the problem. I have checked and the dbsnmp agent on the Linux host is up and running. I have restarted the agent but it does not help.
Below is the output from "emctl status agent" command issued on the Linux host.
What do I need to check and try?
Many thanks.
Checking Agent status, please wait...
The Oracle base for ORACLE_HOME=/opt/app/oracle/product/agent/agent11g is /opt/app/oracle
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 : 10.2.0.5.0
Protocol Version : 10.2.0.5.0
Agent Home : /opt/app/oracle/product/agent/agent11g
Agent binaries : /opt/app/oracle/product/agent/agent11g
Agent Process ID : 4684
Parent Process ID : 4572
Agent URL : https://romulus.it.csiro.au:3872/emd/main/
Repository URL : https://oraserv.it.csiro.au:1159/em/upload
Started at : 2011-01-26 20:22:05
Started by user : oracle
Last Reload : 2011-01-26 20:22:05
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0.00
Number of XML files pending upload : 2
Size of XML files pending upload(MB) : 0.29
Available disk space on upload filesystem : 1.97%
Last successful heartbeat to OMS : 2011-01-26 20:22:25
Agent is Running and ReadyI issued the "emctl upload agent" command and got some error message about not enough space. I noticed that the /opt/app file was 99% full (it still had few GB free), and I did some clean up and got it down to 93% full (120 GB free now). I then issued "emctl upload agent" again and it gev the output
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
I then checked my Grid Control OEM and the agent unreachable problem is no longer there. :-)
I will check the log files under sysman/log to investigate the original problem further.
Many thanks for your help.
Cheers. -
Agent Unreachable, collection status: file handles exhausted
Hi, I have a problem with management agent. Status of agent in grid control is Agent Unreachable. Here is an output of emctl status agent:
Oracle Enterprise Manager 10g Release 5 Grid Control 10.2.0.5.0.
Copyright (c) 1996, 2009 Oracle Corporation. All rights reserved.
Agent Version : 10.2.0.5.0
OMS Version : 10.2.0.5.0
Protocol Version : 10.2.0.5.0
Agent Home : /opt/oracle/agent10g
Agent binaries : /opt/oracle/agent10g
Agent Process ID : 26832
Parent Process ID : 26821
Agent URL : https://bs11.xxxx.lan:3873/emd/main/
Repository URL : https://gridcontrol.xxxx.lan:1159/em/upload
Started at : 2010-07-06 14:24:30
Started by user : oracle
Last Reload : 2010-07-06 14:31:50
Last successful upload : 2010-07-06 15:11:47
Total Megabytes of XML files uploaded so far : 51.87
Number of XML files pending upload : 4
Size of XML files pending upload(MB) : 0.01
Available disk space on upload filesystem : 60.35%
Collection Status : File handles exhausted
Last successful heartbeat to OMS : 2010-07-06 15:11:52
I wonder what does this message mean Collection Status : File handles exhausted I can't find any solution to my problem, I tried restarting agent, clearstate, upload, resynchronization... all of this did nothing.Did you already check: Master Note for 10g Enterprise Manager Grid Control Agent Performance & Core Dump issues [ID 1087997.1]
On http://support.oracle.com
https://support.oracle.com/CSP/ui/flash.html#tab=KBHome%28page=KBHome&id=%28%29%29,%28page=KBNavigator&id=%28bmDocTitle=Master%20Note%20for%2010g%20Enterprise%20Manager%20Grid%20Control%20Agent%20Performance%20&%20Core%20Dump%20issues&bmDocDsrc=KB&bmDocType=BULLETIN&bmDocID=1087997.1&viewingMode=1143&from=BOOKMARK%29%29
Regards
Rob
http://oemgc.wordpress.com -
CloudControl 12c shows "Agent Unreachable" for Cluster Database
Hello ,
when clicking on "Targets -> Databases" our RAC database shows up as follows:
Name Type Status
PROD02 Cluster Database symbol for "Agent Unreachable"
PROD021 Database Instance symbol "green arrow" for "Up"
PROD022 Database Instance symbol "green arrow" for "Up"
I don't understand why the symbol for the Cluster Database is not a green arrow, too. The agent on each node is up and running - and when either clicking on "PROD02" or "PROD021" (or PROD022) Cloud Control offers the full functionality. Therefore the status "Agent Unreachable" is missleading (from my point of view). I don't want to remove the complete Cluster Database and discover it once again - several jobs have already been defined and I don't want to do that once again.
Did anybody else experience the same behaviour?
Any help will get appreciated...
Rgds
JH... seems like if I'm hitting bug "BUG 13865299".
=> "12c Cluster database or Cluster ASM in Pending or "Agent unreachable" for undetermined time [ID 1463196.1]" -
Rman backup job Suspended on Agent Unreachable
Hi,
I have Oracle 10.2.0 installed on windows 2003 server. i configure oracle suggested rman backup which works fine till now. but now it shows
Suspended on Agent Unreachable message and backup doesn't happen.
if check like
C:\Documents and Settings\Administrator>emctl status agen
Oracle Enterprise Manager 10g Database Control Release 10
Copyright (c) 1996, 2005 Oracle Corporation. All rights
Agent is Not Running
C:\Documents and Settings\Administrator>emctl start agent
Oracle Enterprise Manager 10g Database Control Release 10
Copyright (c) 1996, 2005 Oracle Corporation. All rights
These Windows services are started:
Application Experience Lookup Service
Application Management
Automatic Updates
COM+ Event System
COM+ System Application
Computer Browser
Cryptographic Services
DCOM Server Process Launcher
DefWatch
Distributed File System
Distributed Transaction Coordinator
DNS Client
DNS Server
Error Reporting Service
Event Log
File Replication Service
FTP Publishing Service
HTTP SSL
IIS Admin Service
Indexing Service
Intel PDS
Intersite Messaging
IPSEC Services
Kerberos Key Distribution Center
Logical Disk Manager
LogMeIn
LogMeIn Maintenance Service
Net Logon
Network Connections
Network Location Awareness (NLA)
NT LM Security Support Provider
OracleDBConsoleneo
OracleOraDb10g_home1iSQL*Plus
OracleOraDb10g_home1TNSListener
OracleServiceNEO
Plug and Play
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Procedure Call (RPC)
Remote Registry
Secondary Logon
Security Accounts Manager
Server
Shell Hardware Detection
SQL Server (MSSQLSERVER)
SQL Server Agent (MSSQLSERVER)
SQL Server Analysis Services (MSSQLSERVER)
SQL Server FullText Search (MSSQLSERVER)
SQL Server Integration Services
SQL Server Reporting Services (MSSQLSERVER)
Symantec AntiVirus Server
System Event Notification
Task Scheduler
TCP/IP NetBIOS Helper
Telephony
Terminal Services
Windows Management Instrumentation
Windows Search
Windows Time
Workstation
World Wide Web Publishing Service
The command completed successfully.means my agent was stop but now i start it.
i find on Google that this type of error happen when you change in database like ip address, sid etc but i haven't do any change.
i am facing same problem so many times.
Now how to reschedule the existing backup job so that it starts work again.
thanks
umeshthanks for reply
i do it.
C:\Documents and Settings\Administrator>emctl status dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://Techwave:5500/em/console/aboutApplication
EM Daemon is not running.
Logs are generated in directory C:\oracle\product\10.2.0\db_1/Techwave_neo/sysman/log
C:\Documents and Settings\Administrator>emctl stop dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://Techwave:5500/em/console/aboutApplication
The OracleDBConsoleneo service is stopping.....
The OracleDBConsoleneo service was stopped successfully.
C:\Documents and Settings\Administrator>emctl start dbconsole
Oracle Enterprise Manager 10g Database Control Release 10.2.0.1.0
Copyright (c) 1996, 2005 Oracle Corporation. All rights reserved.
http://Techwave:5500/em/console/aboutApplication
Starting Oracle Enterprise Manager 10g Database Control ...The OracleDBConsoleneo service is starting................
The OracleDBConsoleneo service was started successfully.now it is working fine.
now issue is how i reschedule my suspended job.
i got this error.
Edit is not supported for this job type, only general information about the job can be updated No scheduled executions - this job can not be modified.
Maybe you are looking for
-
Question reg. how to get a field from a table
What is EIN? (I think it is employer identification number). My functional consultant told me to get this value from company code. Can you tell me from which table and field I can get this value? Thanks, Krishen
-
How to open .rar files and .exe files on mac
HI I'm new user on mac and would like to know how to open .rar files and .exe files on MAC OS X Thanks
-
Hi Friends, What could be the reason, for the application error jre.exe and message is "The instruction at "0x4f7f4cc" referenced memory at "0x00000011". The memory could not be "read". This message is displayed by Windows NT machine when we are ente
-
IMac and MacBook Pro have difficulties to recognize a Toshiba USB3 HD
Hi, I've a external USB3 HD Toshiba (Alu store 2S - 500MB) and correctly formatted with Mac OS extended (journaled). when I connect it on my Imac (27") or my Mac Book Pro, I see the message that the HD connote be read with 2 selection "Ignore" or " d
-
Can`t paly any video qith quick time pro
I want to export videos to my mobile and I have register Quick Time Pro but can't even play any video in mpeg or avi format. I have installed codecs for windows and so; really, I don't understand qhat is happening. Any idea? Thanks