st03 not running no data....

[former_member190272]

Hello all

my NSP 7.00 database Maxdb have a problem with ST03 not show any data.

That give a information <b>No system data available</b>.The os collector is running The devloper trace file is blow.

-

---

trc file: "dev_disp", trc level: 1, release: "700"

-

---

sysno 00

sid NSP

systemid 560 (PC with Windows NT)

relno 7000

patchlevel 0

patchno 58

intno 20050900

make: multithreaded, ASCII, optimized

pid 2392

Mon Jan 08 10:26:30 2007

kernel runs with dp version 213(ext=109) (@(#) DPLIB-INT-VERSION-213)

length of sys_adm_ext is 360 bytes

• SWITCH TRC-HIDE on ***

Mon Jan 08 10:26:31 2007

***LOG Q00=> DpSapEnvInit, DPStart (00 2392) [dpxxdisp.c 1231]

shared lib "dw_xml.dll" version 58 successfully loaded

shared lib "dw_xtc.dll" version 58 successfully loaded

shared lib "dw_stl.dll" version 58 successfully loaded

shared lib "dw_gui.dll" version 58 successfully loaded

rdisp/softcancel_sequence : -> 0,5,-1

use internal message server connection to port 3900

Mon Jan 08 10:26:35 2007

• WARNING => DpNetCheck: NiAddrToHost(1.0.0.0) took 4 seconds

***LOG GZZ=> 1 possible network problems detected - check tracefile and adjust the DNS settings [dpxxtool2.c 5243]

MtxInit: 30000 0 0

DpSysAdmExtInit: ABAP is active

DpSysAdmExtInit: VMC (JAVA VM in WP) is not active

DpIPCInit2: start server >ko83_NSP_00 <

DpShMCreate: sizeof(wp_adm) 13200 (880)

DpShMCreate: sizeof(tm_adm) 3391272 (16872)

DpShMCreate: sizeof(wp_ca_adm) 18000 (60)

DpShMCreate: sizeof(appc_ca_adm) 6000 (60)

DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048

DpShMCreate: sizeof(comm_adm) 528048 (1048)

DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0

DpShMCreate: sizeof(file_adm) 0 (72)

DpShMCreate: sizeof(vmc_adm) 0 (1196)

DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)

DpShMCreate: sizeof(gw_adm) 48

DpShMCreate: SHM_DP_ADM_KEY (addr: 04D20040, size: 4020072)

DpShMCreate: allocated sys_adm at 04D20040

DpShMCreate: allocated wp_adm at 04D219D0

DpShMCreate: allocated tm_adm_list at 04D24D60

DpShMCreate: allocated tm_adm at 04D24D90

DpShMCreate: allocated wp_ca_adm at 05060CB8

DpShMCreate: allocated appc_ca_adm at 05065308

DpShMCreate: allocated comm_adm at 05066A78

DpShMCreate: system runs without file table

DpShMCreate: allocated vmc_adm_list at 050E7928

DpShMCreate: allocated gw_adm at 050E7968

DpShMCreate: system runs without vmc_adm

DpShMCreate: allocated ca_info at 050E7998

DpShMCreate: allocated wall_adm at 050E79A0

MBUF state OFF

Mon Jan 08 10:26:36 2007

• ERROR => ztta/cua_area is 180000. [sapinit.c 963]

• ERROR => ztta/cua_area adjusted to 250000. [sapinit.c 967]

EmInit: MmSetImplementation( 2 ).

MM diagnostic options set: 0

<ES> client 0 initializing ....

<ES> InitFreeList

<ES> block size is 1024 kByte.

Using implementation flat

<EsNT> Memory Reset disabled as NT default

<ES> 127 blocks reserved for free list.

ES initialized.

Mon Jan 08 10:26:37 2007

rdisp/http_min_wait_dia_wp : 1 -> 1

Mon Jan 08 10:26:38 2007

***LOG Q0K=> DpMsAttach, mscon ( ko83) [dpxxdisp.c 11485]

DpStartStopMsg: send start message (myname is >ko83_NSP_00 <)

DpStartStopMsg: start msg sent

Mon Jan 08 10:26:39 2007

CCMS: AlInitGlobals : alert/use_sema_lock = TRUE.

CCMS: Initalizing shared memory of size 40000000 for monitoring segment.

Mon Jan 08 10:30:04 2007

DpMsgAdmin: Set release to 7000, patchlevel 0

Mon Jan 08 10:30:07 2007

MBUF state PREPARED

Mon Jan 08 10:30:08 2007

MBUF component UP

DpMBufHwIdSet: set Hardware-ID

***LOG Q1C=> DpMBufHwIdSet [dpxxmbuf.c 1050]

DpMsgAdmin: Set patchno for this platform to 58

Release check o.K.

Mon Jan 08 10:30:44 2007

***LOG Q0I=> NiPGetHostByName: hostname 'ko83.kointranet.com' not found: gethostbyname (11004: WSANO_DATA: Valid name, no data record of requested type) [ninti.c 320]

Mon Jan 08 10:30:45 2007

MBUF state ACTIVE

Mon Jan 08 10:30:47 2007

DpModState: change server state from STARTING to ACTIVE

Mon Jan 08 10:32:10 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:32:21 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:32:45 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:32:53 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:33:08 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:34:02 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:34:12 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:34:28 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:35:24 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:36:53 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:36:54 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:36:55 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:36:56 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:36:57 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:36:58 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:36:59 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:37:00 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:37:17 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:37:36 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:37:45 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:37:46 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Mon Jan 08 10:37:47 2007

• WARNING => DpRqServiceQueue: timeout of HIGH PRIO msg, return DP_CANT_HANDLE_REQ

Thanks & Regards

Pankaj

[manu_susankar]

Hi Pankaj

Please check the sap* (most impotently please check update statistics job) standered jobs running periodically without error... also check DB13 jobs are scheduled periodically....jobs like UpdateStats, CheckDB etc...I guess these are could be causes for not updating the statistics...

Regards...

S.Manu