Suppress database/listener/agent unreachable if host unavailable
Hi,
When a host becomes unavailable due to network issues we receive a deluge of agent/database/listener/host unreachable notifications. Is there a clean way to make sure that when a host is unreachable via ping for example other unreachable target notifications are suppressed?
Thanks for any help in advance
Phil
Edited by: user10912727 on 11-Apr-2011 04:01
Edited by: user10912727 on 11-Apr-2011 04:02
Hi Rob,
Thanks for taking the time to reply. Shame these is no way of doing this but I understand why.
Regards
Phil
Similar Messages
-
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
Alanhi,
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 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. -
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. -
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]" -
EM Event: Warning: Database Instance - Agent Down
Hello,
while upgrading plugins for the OMS 12 Bundle Patch and applying the BP on the agents, I get a lot of mails with the above subject - namely, one mail by every database instance and every listener running on the host.
Content of the mail is as follows:
Host=<hostname>
Target type=Database Instance
Target name=<database name>
Categories=Availability
Message=Agent Down
Severity=Warning
Availability status=Agent Down
Rule Name=Database Availability and Critical States,Target Availability Event Rule
Rule Owner=SYSMAN
Blackout on the host leads to the OMS not being able to do the upgrades - obviously a blacked-out agent is not able to do that. What puzzles me that in the Rule mentioned in the mail, incidents should only be created for the target type being down (i.e. for database instance when database is down, and so on) as one would expect.
I would rather not blackout all targets on a host EXCEPT the agent as this gets old with our number of hosts and dbs, does anyone know which rule is responsible for the mails and how they could be suppressed temporarily in an efficient way?I think Jay was referring to selecting availability events by severity. So in the rule create/edit "Select Events" step you can do the following:
1. select (event) Type= Target Availability
2. Leave the radio button in the sub-section at "All events of type Target Availability"
3. select the check box next to "Severity" right below the Type field
4. When a subsequent drop down shows up for severity - select "Fatal"
5. Optionally, check the box next to "Target type" and choose "Database Instance" if your target set includes other targets - this step should not be needed.
6. Everything else should remain the same.
Essentially, the "target down" events come with "Fatal" severity and these "agent down" events come with a "Critical" severity. So this is a way to avoid getting the agent down notifications on databases (or any other targets) while getting the genuine target down notifications. Hope this helps. -
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. -
Agent Connection to Instance Unavailable
Win2k3 64 bit
Oracle Database 10g Release 10.2.0.5.0 - 64bit Production
I brought up a new 10.2.0.5.0 db on Win2k3 64 bit server. Everything is working fine, at least it seems so. This server has been running for 2 months now and this issue kept coming up in the last 2 months.
Database Instance status is Open
Listener status is Up
General status is Up
Agent Connection to Instance is Unavailable.
Users SYSMAN and DBSNMP are OPEN.
This will be the 3rd time in the last 2 months if I rebuild EMCA again.
Is anyone else besides me experiencing this issue? Why is this happening and how do I fix it permanently?1.Post the output of :
SQL> select global_name from global_name;
SQL> show parameter db_domain;
2.lsnrctl service
3.lsnrctl status
4.Did you change the hostname?
5.Is timezon of agent and console the same?
6.In the file $AGENT_HOME/sysman/config/emd.properties, make sure the following parameters are correct. Obtain the values from $OMS_HOME/sysman/config/emd.properties
1. REPOSITORY_URL
2. emdWalletSrcUrl
3. emdWalletDest (ensure that this destination is present on your management server).
7.If you're using Data Guard in 11g for primary/standby configuration, you may want to check the Data Guard configuration status. With this type of error, it's usually caused by the database parameter setting for log archive that differs with the Data Guard config for log transport and apply. For example, if the local archive log destination on the primary is pointing to the standby site instead of local archive directory (or local flash_recovery_area), The GC will generate this error and blank out the options for database instance in GC.
I am just pasting the above texts from different forum link when I just said "Agent Connection to Instance Unavailable" to google.
Regards
Girish Sharma -
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. -
Hi Friends,
I have created a database in 10g. The same machine has 9i instance of DB running in it.
After creating the 10g DB i could see a red arrow pointing downward for all the three divisions (DB instance, Listener, Agent connection to database) in this URL of my oracle server http://localhost:1158/em/
Someone guide me on how to start the DB instance and activate the DB listenerPlease follow my next article which use :
I need a second listener because the node that I worked has two oracle software one for oracle9i and for oracle10g. I leave the listener LISTENER for the oracle9i software and I create a new one LISTERNER10G for oracle10g software.
I create the second listener via netca and I statically configure the database sid via netmgr .After that I made the following changes in init<SID>.ora and tnsnames.ora file.
tnsnames.ora
LISTENER10G=
(DESCRIPTION=
(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.40.250)(PORT=1526)))
alter system set LOCAL_LISTENER= LISTENER10G scope=both;
Some very importand database parameters are the following.
service_names=DB_SISII
db_name=DB_SISII
instance_name=DBSISII
Note that when I create the database I set database name as DB_SISII and SID as DBSISII
Lsnrctl>set current_listener LISTENER10G
Lsnrctl>services
Service "DB_SISII" has 2 instance(s).
Instance "DBSISII", status UNKNOWN, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0
LOCAL SERVER
Instance "DBSISII", status READY, has 1 handler(s) for this service...
Handler(s):
"DEDICATED" established:0 refused:0 state:ready
LOCAL SERVER
I can access the database via the following tnsnames.ora entry
DBSISII =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.40.250)(PORT = 1526))
(CONNECT_DATA =
(SERVICE_NAME = DB_SISII)
Some issues exist for database console and may be able to be solved by:
/home/oracle10g/product/10.2.0/netudevsrv1_DBSISII/sysman/emd
Edit the target.xml
<Targets AGENT_SEED="279319488">
<Target TYPE="oracle_emd" NAME="netudevsrv1:3938"/>
<Target TYPE="host" NAME="netudevsrv1"/>
<Target TYPE="oracle_database" NAME="DB_SISII">
<Property NAME="MachineName" VALUE="netudevsrv1"/>
<Property NAME="Port" VALUE="1526"/>
<Property NAME="SID" VALUE="DBSISII"/>
<Property NAME="OracleHome" VALUE="/home/oracle10g/product/10.2.0"/>
<Property NAME="UserName" VALUE="76469754bb6a6e14" ENCRYPTED="TRUE"/>
<Property NAME="password" VALUE="6250d1bedd187e98" ENCRYPTED="TRUE"/>
</Target>
<Target TYPE="oracle_listener" NAME="LISTENER10G_netudevsrv1">
<Property NAME="Machine" VALUE="netudevsrv1"/>
<Property NAME="LsnrName" VALUE="LISTENER10G"/>
<Property NAME="Port" VALUE="1526"/>
<Property NAME="OracleHome" VALUE="/home/oracle10g/product/10.2.0"/>
<Property NAME="ListenerOraDir" VALUE="/home/oracle10g/product/10.2.0/network/admin"/>
</Target>
</Targets>
/home/oracle10g/product/10.2.0/netudevsrv1_DBSISII/sysman/config
Edit the following line in emoms.properties
oracle.sysman.eml.mntr.emdRepConnectDescriptor=(DESCRIPTION\=(ADDRESS_LIST\=(ADDRESS\=(PROTOCOL\=TCP)(HOST\=netudevsrv1)(PORT
\=1526)))(CONNECT_DATA\=(SERVICE_NAME\=DB_SISII)))
emctl stop dbconsole
emctl start dbconsole -
12c Cloud Control - Agent Unreachable
Hello,
I am quite new to 12c cloud control and I am unable to resolve an "Agent Unreachable" issue.
I could find Agent does not upload to OMS in OEM 12c as relevant
but nothing in that worked for me.
The setup is as follows:
1) 12c cloud control is installed on a box and is up and running (both OMS and agent)
2) The agent on the same host as OMS can talk to OMS and the agent status is shown as "available" in OMS console
3) There is another box that has a 11.2 database installed as well as 12c agent installed (called as DEVBOX for convenience)
4) DEVBOX has database up and running and 12c agent also up and running. In the past, it was probably being able to "talk" to OMS but I can't remember
However, at present, on OMS console, this agent is shown as "unreachable". I tried few things but only possible issue I could find is
when I try to use Setup -> Add Target -> Add Targets Manually -> Add non-Host targets using guided process, on the "specify Host" page
when I click on "Select Host" option, the hostname in the agent URL for the DEVBOX is different than the actual host name.
As the agent URL for DEVBOX is not reachable (because the hostname is invalid), I can't do anything with this agent.
Can somebody please help?Loc Nhan wrote:
To remove an agent from the console:
- Go to the homepage of the host where the agent reside
- From the Host menu under the host name, select Related Targets
- Remove all non-agent targets
- Remove the host target by selecting Host > Target Setup > Remove Target
- Stop the agent
- Remove the agent target by going to the agent homepage and selecting Agent > Target Setup > Remove TargetLoc,
Once again thanks for looking into this. I followed your advice above and removed the host and the agent from OMS console.
Now, with the 12c agent already running on the DEVBOX, I was hoping that OMS will automatically detect the agent but I
can't find it in OMS console.
On DEVBOX:
[oracle@devbox agent_inst]$ ./bin/emctl status agent
Oracle Enterprise Manager 12c Cloud Control 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
Agent Version : 12.1.0.1.0
OMS Version : 12.1.0.1.0
Protocol Version : 12.1.0.1.0
Agent Home : /u01/app11g/oracle/agentHome12c/agent_inst
Agent Binaries : /u01/app11g/oracle/agentHome12c/core/12.1.0.1.0
Agent Process ID : 8945
Parent Process ID : 8893
Agent URL : https://devbox.dev.abc.com:3872/emd/main/
Repository URL : https://gridbox.prd.abc.com:4901/empbs/upload
Started at : 2012-08-17 09:47:30
Started by user : oracle
Last Reload : (none)
Last successful upload : (none)
Last attempted upload : (none)
Total Megabytes of XML files uploaded so far : 0
Number of XML files pending upload : 0
Size of XML files pending upload(MB) : 0
Available disk space on upload filesystem : 17.52%
Collection Status : Collections enabled
Last attempted heartbeat to OMS : 2012-08-17 09:48:51
Last successful heartbeat to OMS : 2012-08-17 09:48:51
Agent is Running and Readyon OMS box:
[oracle@gridbox middleware]$ ./oms/bin/emctl status oms -details
Oracle Enterprise Manager Cloud Control 12c Release 12.1.0.1.0
Copyright (c) 1996, 2011 Oracle Corporation. All rights reserved.
Enter Enterprise Manager Root (SYSMAN) Password :
Console Server Host : gridbox.prd.abc.com
HTTP Console Port : 7789
HTTPS Console Port : 7801
HTTP Upload Port : 4890
HTTPS Upload Port : 4901
OMS is not configured with SLB or virtual hostname
Agent Upload is locked.
OMS Console is locked.
Active CA ID: 1
Console URL: https://gridbox.prd.abc.com:7801/em
Upload URL: https://gridbox.prd.abc.com:4901/empbs/upload
WLS Domain Information
Domain Name : GCDomain
Admin Server Host: gridbox.prd.abc.com
Managed Server Information
Managed Server Instance Name: EMGC_OMS1
Managed Server Instance Host: gridbox.prd.abc.comAs I mentioned earlier, gridbox and devbox can communicate with each other on necessary ports.
I would prefer to resolve this issue without having to re-install the agent.
Would appreciate some help.
Thanks. -
Unable to auto start database/listener/EM on Oracle Enterprise Linux 5
All Experts
I have install oracle 11g on Oracle Enterprize Linux 5 successfully.
done all post installating steps, but when i restart server oracle listener/database/EM not automatically start.
Please guide what is wron (server dbora error: /bin/sh: :No such file or directory).
1. Log in as the root user
2. Edit the oratab file (SID=Y)
3. Create a file called dbora
4.Run chmod and chgrp on the dbor file
# chgrp dba dbora
# chmod 750 dbora
6.Creat symbolic links to the dbora script
# ln -s /etc/init.d/dbora /etc/rc.d/rc0.d/K01dbora
# ln -s /etc/init.d/dbora /etc/rc.d/rc3.d/S99dbora
# ln -s /etc/init.d/dbora /etc/rc.d/rc5.d/S99dbora
7. add service
# chkconfig --add dbora
# chkconfig –list dbora
0:off 1:off 2:off 3:on 4:off 5:on 6:off
# ls -l /etc/rc*.d/*dbora
# !/bin/sh -X
# chkconfig: 35 99 10
# description: Start and stop the Oracle database, listener, EM, and iSQLPlus
# Change the value of ORACLE_HOMe to specify the correct Oracle Home Firectory for your installation.
# Change the value of ORACLE to the login name of the oracle owner at your site
ORACLE_HOME=/oradisk/app/oracle/product/11.1.0/db
ORACLE=oracle
PATH=${PATH}:$ORACLE_HOME/bin
HOST="hostname"
PLATFORM="uname"
export ORACLE_HOME PATH
if [ ! -f $ORACLE_HOME/bin/dbstart ]
then
echo "Oracle startup: cannot start"
exit
fi
case $1 in
'start')
su - $ORACLE -c "$ORACLE_HOME/bin/dbstart $ORACLE_HOME"
'stop')
su - $ORACLE -c "$ORACLE_HOME/bin/dbshut $ORACLE_HOME"
echo "usage: $0 {start|stop}"
exit
esac
exitdoes the script work when you log on to your freshly started system, logon as root and execute /etc/init.d/dbora start?
the script does not have to have group membership of the dba group.
also, do not create symlinks yourself.
by adding the service using chkconfig the script is started and stopped as indicated by chkconfig --list, no need to do additional steps like creating symlinks. -
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. -
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
Maybe you are looking for
-
Quicktime Does Not Work...Striped yellow/black bar or Q with ?
Hi, I have read the previous posts about similar problems with quicktime but the posted fixes have not resolved my issue. I have three computers. Quicktime quit working on two of them. Before upgrading to the latest version, I got the yellow/black st
-
Which epson wireless printer will work with airport extreme (can not find out from epson)
three systems in use Win 7, Mac lion and vista. Former epson printer WF 600 would not link with my new airport extreme router despite multiple attempts through epson. Does anyone know of a wireless printer that will work? Thanks.
-
Project server 2007 - users amount in reporting services
Hi! I wanted to know how/where can i found information about how many users defined as reporting services users (users that can access reports from SSRS) Thank you Ofir Ofir Marco , MCTS P.Z. Projects
-
Trying to download adobe reader XI, it is asking for a default application to run
I am trying to install adobe reader XI on a fresh copy of windows 7 32 bit, it downloads but i do not have an option to run, just to save or open
-
Post Author: Jadero CA Forum: General The preview in the designer fails with:Prompting failed with the following error message: 'Unexpected error.'.Error source: prompt.dll Error code: 0x80043800The runtime version of the reports just fail silently