ADSM-L

Re: update sql query

2003-08-12 10:56:22
Subject: Re: update sql query
From: Otto Schakenbos <otto.schakenbos AT TELEFLEX DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 12 Aug 2003 16:55:55 +0200
funny thing is that most nodes are at 5.1 level or higher and that it
used to work before. W edidn't do a node or server upgrade or anything.
Plus that all nodes are not there not only older ones.
thnx anyway for your reaction

mvg

Otto Schakenbos

Oscar Kolsteren wrote:

Hi Otto,

we have got the same problem over here, and the only difference in the nodes I 
got info from and those I can't find is the level of the TSM clients. I know 
this was a problem in some client versions and should be solved in versien 5.1 
and up.


Gr. Oscar Kolsteren
Netherlands

-----Original Message-----
From: Otto Schakenbos [mailto:otto.schakenbos AT TELEFLEX DOT COM]
Sent: dinsdag 12 augustus 2003 12:01
To: ADSM-L AT VM.MARIST DOT EDU
Subject: update sql query


I played around a bit more and found out when issuing a "select * from
summary" i still don't get my nodes. (see org story below) So i'm pretty
sure now it is not a sql problem but a db problem. But in the actlog i
don't find any errors after a node has finished its backup. Anybody able
to give a pointer in the right direction.

thnx


ORG:
we have a tsm server 5.1.5.4 on aix  4.3.
Every day we run a sql query with the following statement
select ENTITY as Node_Name, ACTIVITY, BYTES as Bytes_Transferred,
START_TIME, END_TIME, IDLE as Idle_in_Sec, MEDIAW as meddia_wait_in_sec,
PROCESSES, AFFECTED as Files_backup, FAILED, EXAMINED as All from
summary where start_time>timestamp(current date -1 day, '12:20:00' )and
bytes>0

Resulting in an overview of the transferred bytes per day per node.
(clients, db backup, migrations, stgp backup)
This has been running since about 6 months without any problem but since
last sunday a weird thing is happening. The result from the query now
only shows migrations, db backup and storagepool backup. The client
nodes itself have gone from the result.
Since the script didn't change, the clients nodes are still backing up
as normally. I suspect  that a value the clients generate after
finishing a backup  is not written to the db anymore. Then when the sql
scripts runs it doesn't get the clients in the result because this valua
is not there.

things i have tried so far:
Checked if the clients are backing up properly, they are. ( in the act
log then it is), all other things run fine as well, like space recl,
stgp backup etc etc. We also run a script that only looks how long a
client has been backing up, is also still working correct and listing
the client nodes as ussual.
Checked if someone  changed something on the day it started, nothing has
changed on the tsm side of things.
When i run the sql statement over a longer period also covering a day or
2 before things went funny the clients show up in this period until
things went funny (till 11pm that day), so the sql statement appears to
be ok.
Taking away the bytes>0 , no luck. (accept i could see the tapemounts
now as well.)

I'm a bit low on idea's now so if someone has any hints where to look
for it would be great.


mvg

--
Otto Schakenbos
PC-Support

TEL: +49-7151/502 8468
FAX: +49-7151/502 8489
MOBILE: +49-172/7102715
E-MAIL: otto.schakenbos AT tis-ag DOT com

TFX IT-Service AG
Fronackerstrasse 33-35
71332 Waiblingen
GERMANY


-----------------------------------------------------------------
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------



<Prev in Thread] Current Thread [Next in Thread>