Space Statistics Collector

The Space Statistic Collector collects data for the space monitor in the DBA Cockpit.

Integration

A standard background job, SAP_COLLECTOR_FOR_PERFMONITOR, starts the collector. The data is physically stored in cluster table MONI.

Prerequisites

You must make sure that the collector is set up as described in SAP Note 868063.

Features

The collector is based on program RSORACOL. This report must be included in table TCOLL as one of the components of standard SAP job SAP_COLLECTOR_FOR_PERMONITOR with the following parameters:

RNAME: RSORACOL
RENUM: 1
SYTYP: S (or C if 620)
ALTSY
DAYOW: XXXXXXX
TIMOD: XXXXXXXXXXXXXXXXXXXXXXXX

The setup process as described in “Prerequisites” above creates at least one entry in table ORA_MON_DBCON and many entries in table DB02_COLL_PLAN:

The table ORA_MON_DBCON provides a list with the connection names of the databases to be monitored. The databases can be local or remote, running SAP or not. The only requirement is that the connection names must match those stored in table DBCON. The local database is always called DEFAULT.
The table DB02_COLL_PLAN provides a list of collector modules – ABAP function modules that collect data – with their specific settings such as module name, module_id, schedule, MONI key where data is stored, dependencies, and so on.
All these function modules currently belong to SAP function group SDBORA3. There is normally one collector module for each submonitor in the DBA Cockpit.

Example
The collector module US-GE-MD (SMON_ID=200) collects the data displayed in sub-monitor Space Statistics User Overview .

End of the example.

A normal collection job runs as follows:

The standard SAP job SAP_COLLECTOR_FOR_PERMONITOR runs hourly and starts the program RSORACOL.
The program RSORACOL reads the table ORA_MON_DBCON to:
1. Get the connection names of the databases to be monitored.
2. Check whether the database connection is active or inactive
For each database, RSORACOL executes a set of collector modules according to their schedules and according to settings stored in table DB02_COLL_PLAN.

If required, RSORACOL establishes a native connection to remote databases.
As collector modules finish, they store collected data in cluster table MONI under a specific monikey. Program RSORACOL then immediately writes a log entry to table DB02_COLL_LOG.
The previous two steps are repeated for each database to be monitored.

There is a logging mechanism in the collector program. Every time a collection module completes a collection and exports it to MONI a log entry is written to table DB02_COLL_LOG. The log entry contains a time stamp, submonitor ID, return code, and other information.

Activities

Configuration

You can configure the space statistics collector as follows:

You add databases to the monitoring list or delete them as described in SAP Note 868063. The local database is always called DEFAULT and does not appear in the F4 help.

You can change database settings in the table ORA_MON_DBCON except CON_NAME:

Column	Description
`CON_NAME`	Database connection name, as stored in table DBCON
`STATUS`	Status of the database monitoring
`MAX RUNTIME`	Maximum runtime in seconds desired for collector modules Default: 1800 seconds
`MAX UPLOAD`	Maximum size in KB desired to be written to MONI per collector module Default: 1,000,000 KB
`LOG LIFE`	Time in days desired to retain logs Default: 100 days
`DESCRIPTION`	Short text

We recommend that you do not normally modify table DB02_COLL_PLAN, which contains the collector module settings. If required, you can modify certain fields like MONIFILL, SCH_DATE, SCH_TIME, or PARAM but we recommend you to raise an SAP support message before doing so.

The table DB02_COLL_PLAN looks as follows:

Column	Description
`CON_NAME`	Database connection name, as stored in table DBCON
`SMON_ID`	Sub-monitor ID for this collector module
`SMON_NAME`	Sub-monitor name for this collector module
`FUNCNAME`	Function module name
`MONIFILL`	MONI filler, part of the MONI key
`RANK`	Rank Relevant for sub-monitors that are organized hierarchically.
`STATUS`	Collector module status
`SCH_DATE`	Schedule date
`SCH_TIME`	Schedule time
`PROCESS_TYPE`	Process type This differs according to the data source. For example, data from Oracle views is process type snapshot, `S`.
`SOURCE_SMON`	Source sub-monitor id Some collector modules gather data from other collector modules, which means there can be dependencies between monitors.
`PARAM`	Some collector modules accept or require parameters. For example, the collector module for top table sizes sets the length of the ranking.

Remote Monitoring

So that you can use the space monitor to monitor Oracle databases remotely, the collector program can also collect data from remote databases using a native connection.

Make sure that you meet the following prerequisites to enable data collection from remote databases:

The tnsnames.ora files attached to local Oracle clients contain a specific entry for the remote database.

If your local system does not run Oracle, you need to at least install the Oracle client software and then adapt the tnsnames.ora files.
The native connection to the remote database exists in table DBCON and it works without problems.
The database connection exists in table ORA_MON_DBCON.

Do not make this entry manually. For more information about setting up collectors for new databases, see “Prerequisites” above.

Troubleshooting

If the space monitor in the DBA Cockpit is not up-to-date or contains no data, see SAP Note 1002840. For further support, you can create a message in component BC-CCM-MON-ORA.