ended.
(42AEA2E5.001B-6:ko4crtsq.cpp,5547,"IBInterface_refreshIB") Hub is not there
Tue Jun 14 04:27:01 2005 KO41036 Monitoring for situation UADVISOR_OMUNX_SP2OS
started.
(42AEA3C3.0000-6:kdssqrun.c,2995,"Fetch") QueryRowset error. status 302
Tue Jun 14 04:30:43 2005 KO41039 Error in request Notify. Status= 1105.
Reason= 302.
(42AEA3C3.0001-6:ko4async.cpp,4744,"IBInterface::completeRequest") Close failed
request <55BE90>
(42AEA53C.0000-6:ko4ibstr.cpp,1090,"IBStream::insertDef")
Ret code 155 indicates hub connection lost.
Attempting to switch hubs o
r reconnect.
(42AEA53C.0001-6:kdcgbin.c,118,"KDCG_Bind") Using GLB at ip:#9.48.157.26[1918]
(42AEA53D.0000-6:ko4crtsq.cpp,6456,"IBInterface::restartAllObjects")
No access list records changed
(42AEA53D.0001-6:ko4mxque.cpp,97,"MutexQueue::~MutexQueue") Reply store <FcO798B8>
still associated with request <503D98>: info.re
ply <FC0798B8> info.oType <5546> info.oName <INSERTO4SRV.TNODESTS> info.sitName
<*noname*>
info.reqState <-1> info.physicalIO <1>
info.logIt <0> info.reqGen <412>
Tue Jun 14 04:37:01 2005 KO41034 Monitoring for situation UADVISOR_OMUNX_SP2OS
ended.
Tue Jun 14 04:37:02 2005 KO41036 Monitoring for situation UADVISOR_OMUNX_SP2OS
started.
(42AEA61B.0000-6:kdssqrun.c,2995,"Fetch") QueryRowset error. status 302
Tue Jun 14 04:40:43 2005 KO41039 Error in request Notify. Status= 1105.
Reason= 302.
(42AEA61B.0001-6:ko4async.cpp,4744,"IBInterface::completeRequest")
Close failed request <61D5E0>
The Platform view in the Manage Tivoli Enterprise Monitoring
Services panel shows the Tivoli Enterprise Monitoring Server
as running as a 32 bit application, but my agents are shown
as running as 64 bit applications
The Tivoli Enterprise Monitoring Server is a 32 bit application that runs on both 32
and 64 bit operating systems.
Tivoli Enterprise Monitoring Server does not release memory
after running a large SQL query
Running a query for data beyond a 24-hour period consumes high CPU and
memory because the data is not stored on the server and must be retrieved from
the endpoints. All users might experience low system performance while a large
amount of data is retrieved from endpoints.
SQL queries with more than 200 OR predicates do not
complete
If an SQL query to the hub monitoring server contains more than 200 OR
predicates, a limit is reached and the query does not complete. An example of this
is if the tacmd listSystems command is run specifying a remote monitoring server
that contains universal agents that contain more than 200 subnodes, the query will
OR together all of the subnodes.
164 IBM Tivoli Monitoring: Troubleshooting Guide
To Next Page
Loading...
Need help?
General
