Discrepancy between DBACOCKPIT Collector and DB02_COLL_PLAN

[martin_E]

The customer system is BW7 on SAP EHP 1 for SAP NetWeaver 7.0

SAPKB70108

SAPKA70108

SAPKW70108

While dealing with space issues on the BW side of things, we realised that Database Monitoring was not correctly configured, so we worked through the Service Market Place Note 1002840 - No data or obsolete data in DB Space Statistic Monitor.

However, the output from DBACOCKPIT / DB02 -> Space -> Additional functions -> Collector logs -> "Modules" tab shows most monitors as INACTIVE even though they are turned on in DB02_COLL_PLAN

For example,

A) the output from DBACOCKPIT / DB02 -> Space -> Additional functions -> Collector logs -> "Modules" tab shows the DB* monitors as INACTIVE.

See DBACOCKPIT_Collector_Logs_DB.txt

B) When I look in transaction SE16 table DB02_COLL_PLAN,

SMON_NAME = DB*

these monitors show as ACTIVE - See DB02_COLL_PLAN_DB.txt

C) When I look in transaction SE16 table DB02_COLL_LOG

COLL_DATE = 09/27/2015

SMON_NAME = DB*

I see that they are running regularly, with either a return code of blank (presumably 00) or 02. See DB02_COLL_LOG_DB-0927.txt

For reference, according to Note 1002840, the return codes mean:

00 Successful execution

01 Successful execution: no data collected

02 Successful execution: dataset was already up-to-date

10 Database connection not possible

20 Monitor deactivated: Oracle release < 9

30 Submonitor deactivated: source submonitor was inactive

31 Submonitor deactivated: data upload exceeded fixed limit

32 Submonitor deactivated: runtime exceeded fixed limit

In short, the monitors are running, but I can't work out why they are showing up as inactive in DBACOCKPIT / DB02. I suspect that the code behind the DBACOCKPIT / DB02 -> Space -> Additional functions -> Collector logs -> "Modules" tab is incorrect, however I haven't found any fix for this in the Service Market Place. Does anyone have any ideas ?

[Former Member · Accepted solution]

Can you check entries in DB02_COLL_PLAN table for existence of SMON_ID=901 (SMON_NAME=AD_GE_CM) and its status?

[martin_E · Accepted solution]

My apologies for the delay in replying;

An entry of SMON_ID ==> 901 did  exist in DB02_COLL_PLAN; details are as follows...

CON_NAME	DEFAULT
SMON_ID	901
SMON_NAME	AD-GE-CM
FUNCNAME	ORA_COLL_AD_COLLECTOR_MOD
MONIFILL	DEF901
RANK	9
STATUS	A
SCH_DATE	XXXXXXX
SCH_TIME	X              X
PROCESS_TYPE	S
SOURCE_SMON
PARAM

However, without any further intervention, the modules in DBACOCKPIT / DB02 -> Space -> Additional functions -> Collector logs -> "Modules" tab are now showing as ACTIVE. We are not sure of what "fixed" it, but have a suspicion it may have been a matter of a particular job getting scheduled and run, but we can't confirm this.

Thanks for your help.

[Former Member · Accepted solution]

You can read SAP Note 1002840 - No data or obsolete data in DB Space Statistic monitor to find information about all required steps to collect statistics. In your case try to check DB02_COLL_LOG for SMON_ID 901 for affected period of time. SMON_ID 901 is responsible for updating information on Modules tab in Collector logs.