Node Activity workspace reports time stamps as "00:00:00" within Tivoli Enterprise Portal (TEP).
Time stamp for different activities carried out at the node level are shown as "00:00:00" in the 'Node Activity' Workspace on the Tivoli Storage Manager Reporting (TEP) Workspace.
Time stamp of "00:00:00" shown for different activities carried out at the node level in the workspace 'Node Activity' is as per the product design. Explained in detail as below.
Resolving the problem
The default workspaces of "Node Activity" show the summarized information for one day, but will not show for each activity. This display of the data is due to the manner in which it is handled, as explained in the following three steps:
Step One: The activity information is read from the "summary" table of the Tivoli Storage Manager server for XX number of days. The SQL statement is as below:
select entity, start_time, end_time, activity, schedule_name, examined, affected, failed, bytes,
(end_time-start_time) from summary where (activity = 'BACKUP' or activity = 'RESTORE' or activity =
'RETRIEVE' or activity = 'ARCHIVE' or activity = 'FULL_DBBACKUP') and end_time > '<Current time> -
The condition "end_time > '<Current time> - KSK_APIHRLIMIT days'" indicates the number of rows saved during "KSK_APIHRLIMIT" days.
- The parameter "KSK_APIHRLIMIT" can be changed in the Tivoli Storage Manager agent configuration file. Its default value is "1", which means that the data is read from the Tivoli Storage Manager server for one day in the past.
- When the parameter "KSK_APIHRLIMIT" is used in the attribute group "Client Missed Files", it means that the data is read from the Tivoli Storage Manager Server for some number of hours in the past. For "Node Activity", this parameter means "days".
Step Two: The activity information is saved into the DERBY database.
The "start_time" and "end_time" are trimmed to be in the format "YMD" and the time information is lost. This is for calculating the statistical information in step #3. The data in the DERBY database is retrieved from the Tivoli Storage Manager server every 30 minutes (this parameter can also be altered).
Step Three: When the data is viewed from with the Tivoli Enterprise Portal, the summarized information is calculated based on the data saved within the DERBY database. The SQL statement is as below:
select servername, serverver, serverrel, nodename, starttime, endtime, nodeactivity, schedulename,
sum(filesexamined) as filesex, sum(filesaffected) as filesaff, sum(filesfailed) as filef,
sum(cast(totalbytes as bigint)) as totbytes, sum(cast(elapsedtime as bigint)) as elapsedt from
nodeactivity group by servername, serverver, serverrel, nodename, starttime, endtime, nodeactivity,
schedulename order by nodename, starttime
Note: Setting the historical data query conditions will determine what data can be viewed.