No data in Portal Database tables for Activity Report

[Former Member]

Hi experts,

I've developed an Activity Report application in SAP Portal 7.0, which went live but the report shows no data.

We are pulling data from 2 portal database tables: WCR_WEBCONTENTSTAT and WCR_USERPAGEUSAGE

In non production environment there is data in the report but there is no data in the production environment.

The Activity Report service is already activated/started and set to true.

What could have caused this? And what should we check now?

What other configurations/setup should be done?

Regards,

Greg

[Former Member]

Hello, activity report was set to false. Service properties were configured then restarted. Data is now being inserted in the DB tables. Thanks!

[Former Member]

Hi Greg,

Have you set the "Monitor Users"  property of the pages to "Yes".

BR,

Anurag

[michal_zilcha-lang]

Hi Greg,

Those are the aggregated tables. If they are not filled with data although the Portal Activity Report is activated, you should check whether the aggregation finished successfully.

In the older SPs there were some problems that were fixed in later SPs of 7.0.

In order to have the latest version of Portal Activity report, you can check SAP note 1084379 - Portal Activity Report - Latest Version (SDA file).

You can compare the SP via the MANIFAST file, as it contains the version and SP number.

In order to troubleshoot problems in Activity Report, you can follow SAP note: 1690023 - Portal Activity Report - Component-specific Note

Some basic checks that you can do:

Run query on the raw data tables to check since when there is data in those tables:

select min(timestamphour) from SAP<SystemID>DB.WCR_WEBCNODESTAT;

If there is too much data from long time ago, then you should delete the old data, and leave only the new data (there is anyways retention time for the data to be kept).

If there is no data, then it means that the Portal Activity Report does not collect data, and not really activated (usually this is not the case).

The aggregation runs every top of the hour, so you can check in the default traces for an error during that time.

In most of the cases something went wrong while aggregating the data.

As a result the aggregation is not finished, so the transaction is not being committed, and the aggregated tables stay empty.

If there is a DuplicateKeyException in the trace, you can follow SAP note 1054145 - Duplicate Key Exception.

If you have any more questions, please don't hesitate to ask.

I hope this information helps,

Thanks & regards,

Michal Zilcha-Lang