Re: TEP not showing any data in workspace

Our environment is small with only one HTEMS and 150 agents. 
TEPS log shows following entryKfwServices: Sat 12 Jan 2013 05:18:50 PM IST: TDS_HTEMS(122): SELECT KLZSYS.ORIGINNODE, KLZSYS.CSWSEC, KLZSYS.RATECSW, KLZSYS.PROCSEC, KLZSYS.RATEPROC, KLZSYS.CURUSRS, KLZSYS.LOAD1MIN, KLZSYS.LOAD5MIN, KLZSYS.LOAD15MIN, KLZSYS.SYSUPTIME, KLZSYS.PGPGIN, KLZSYS.PGPGINPS, KLZSYS.PGPGOUT, KLZSYS.PGPGOUTPS, KLZSYS.PGSWAPIN, KLZSYS.SWAPINPS, KLZSYS.PGSWAPOUT, KLZSYS.SWAPOUTPS, KLZSYS.PGFLTPS, KLZSYS.MAJFLTPS, KLZSYS.TOTPROCS, KLZSYS.ZOMBCNT, KLZSYS.TIMESTAMP FROM KLZ.KLZSYS AT( 'TDS_HTEMS' ) WHERE (KLZSYS.ORIGINNODE = ?) AND SYSTEM.PARMA("TIMEOUT","600",3)
KfwServices: Sat 12 Jan 2013 05:18:50 PM IST: TDS_HTEMS(122): Values: 'ctmapxl23prnoi:LZ'
 
But it is not showing entry for rows returned . When I restart HTEMS and TEPS able to see data on workspaces for around 10 mints. After that workspace shows blank.
Anything to figureout from this?
 
Regards
Sebastian


________________________________
From: "[email protected]" <[email protected]>
To: saby <sabyantony2001-/[email protected]>; Discussion list for Tivoli product and Tivoli Ready products. <tme10-33AaDErTWvD2/[email protected]> 
Sent: Wednesday, January 9, 2013 11:05 PM
Subject: Re: [TME10] TEP not showing any data in workspace


Depending on your architecture, Saby, it is most likely a bottleneck at the RTEMS level rather than with the TEPS or TEP rendering itself.  The queries which drive the discrete views have the quality that until all the rows have returned they don't start to paint, so it is probably that you're dealing with timeouts from agents due to either:  a) a smattering of OFFLINE agents in the mix of targets for the views' queries; or b) one or more RTEMS themselves are having trouble pulling the data back due either to something local or just a few misbehaving agents.

This can be particularly pronounced with ITCAM and DataPower data since there's a separate table which is referenced to know which D4 agents to pull data for (KD4TCORE's COMPSYS table).  Having defunct or OFFLINE agents in there can cause great delay in ITCAMfSOA data pulls.

Anyway, there's a nice trace that shows the rows returned to the TEMS's proxy (remote or hub) from its agents, which you can use to see what the delay might be at the TEMS/RTEMS level:

(UNIT:kpxrpcrq,Entry="IRA_NCS_Sample" ST, ER)

It's actually the same trace that John Alvord uses in his TEMS audit tool out on ISML.  I would recommend using the simplest workspace you can that exhibits the problem, preferably one with one view whose query targets agents that are only on one TEMS.  Then setup the trace on the remote and hub TEMS's, as well as use "(UNIT:ctsql IN,ER)" on the TEPS, and maybe "(UNIT:kra IN,ER,ST)" on one of the target agents, and see how the data flow looks from end to end.  Perhaps something stands out...

Toben



On Wed, Jan 9, 2013 at 9:46 AM, saby <[email protected]> wrote:

Hi List,
>
>I'm facing an issue with TEP console. While accessing workspaces it takes long time to load data or sometimes comes up with blank workspace. This is the case for all agents. TEP log doesn't show  any error message..  Can anyone help wih troubleshooting tips ?
>ITM 623 FP1 ,RHEL 6.2
>Issue facing on Desktop as well as web client
>
>ThanksSaby
>
>_______________________________________________
>TME10 mailing list
>[email protected]
>mailto:Unsubscribe%[email protected]
>
>


-- 
"Sometimes I think that's the only right thing to do:
To dream. to live in the world of dreams.
But it doesn't last forever--wakefulness always comes to take me back..."

_______________________________________________
TME10 mailing list
[email protected]
Unsubscribe:[email protected]