Same thing if your TSM DB is very nearly full, you can run out of space to
run complex SELECT queries  (which is what the Operational Reporter does).
.

Simplest thing to do is read carefully through your TSM activity log
starting at the point in time your daily report runs.

You should see each TSM SELECT query that is run to retrieve the
information.  When you get to the ones that pull activity log information,
look for errors back from the SELECT statement.



On 8/19/08, Virene, Rick <Rick.Virene AT jacobs DOT com> wrote:
>
>
> You might check your log file size/capacity/# of records. If it gets jammed
> up, you would get a partial report.
>
> Regards,
> Rick Virene
> Server Operations - Jacobs
> (desk) 720.359.3075
> (cell) 303.591.1144
> Please consider the environment before
> printing this e-mail
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Michael Riviello
> Sent: Tuesday, August 19, 2008 2:10 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] TSM Operational Reporting Problem
>
> I am running TSM 5.4 on a Windows 2003 environment.
>
> I recently started having an issue with my operational reporting.  My
> reports
> contain no detail in the Activity Log Details, Missed File Summary and
> Backup
> Archive Client Backup summary.
>
> I have searched many blogs and researched with IBM with out any luck.
>
> Does anyone have any ideas on how to correct this or where I may find some
> info?
>
> Thanks,
>
>
> Michael Riviello
>
> NOTICE - This communication may contain confidential and privileged
> information that is for the sole use of the intended recipient. Any viewing,
> copying or distribution of, or reliance on this message by unintended
> recipients is strictly prohibited. If you have received this message in
> error, please notify us immediately by replying to the message and deleting
> it from your computer.
>