One of the more interesting tables is the SUMMARY table. It contains 1
record for almost every event/command. There is a record for each
backup/archive/restore/retrieve session. One for each BACKUP STG,
reclamation, DB Backup,... It is controlled by the SET SUMMARYRETENTION
command. I believe the default it 30-days. I use Crystal Reports to produce
some interesting stats using this table. It's almost like the accounting
data on steroids. You may want to look at setting this to a lower number of
days retention if you have a lot of activity.
Bill Boyer
DSS, Inc.
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Tim Williams
> Sent: Tuesday, April 18, 2000 8:11 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: (New tables in 3.7 DB to answer?) Re: Database Utilisation
> zooming up after upgrading from ADSM to Tivoli 3.7 on AIX 4.3
>
>
> Could be some new tables that are in the 3.7 DB that seem to be session
> related...
> Did you open a pmr/etr (a problem management) record with Tivoli?
> see note from 3/9 that I sent to 'adsm-l.'
> Thanks Tim
>
>
> From: Tim Williams on 03/09/2000 11:20 AM
>
> To: ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject: 3 New tables in TSM's DB
>
> There seems to be 3 new tables: backupsets, events and summary,
> when you upgrade
> to TSM 3.7.
> (compared table listings, pre and post TSM 3.7 upgrade)
> My specific upgrade was on the AIX server platform and I went
> from ADSM 3.1.2.42
> to TSM 3.7.0 (then
> onto TSM 3.7.2).
> I did want to share that answer....and, of course, once YOU have
> TSM 3.7 on...
> you can do the
> select * from syscat.columns where tabname='EVENTS' (for example)
> to further
> understand
> what's kept in those tables.....etc...
> FYI Thanks Tim Williams Frito-Lay/Pepsico
>
> supporting data........:
> 'OLD days' of adsm:
> adsm> select * from events
> ANR2939E The reference 'EVENTS' is an unknown SQL table name.
>
> |
> ..............V.....
> select * from events
>
> ANS8001I Return code 3.
>
> adsm> select * from summary
> ANR2939E The reference 'SUMMARY' is an unknown SQL table name.
>
> |
> ..............V......
> select * from summary
>
> ANS8001I Return code 3.
>
> adsm> select * from backupsets
> ANR2939E The reference 'BACKUPSETS' is an unknown SQL table name.
>
> |
> ..............V.........
> select * from backupsets
>
> ANS8001I Return code 3.
>
> adsm>
>
>
> NEW days with TSM
> adsm> select * from events
>
> SCHEDULED_START: 2000-02-29 01:00:00.000000
> ACTUAL_START:
> DOMAIN_NAME: SRVR_PD
> SCHEDULE_NAME: INTRANET_SRVR
> NODE_NAME: INTRAPRO
> STATUS: Missed
> RESULT:
> REASON:
>
> SCHEDULED_START: 2000-02-29 01:00:00.000000
> ACTUAL_START:
> DOMAIN_NAME: SRVR_PD
> SCHEDULE_NAME: INTRANET_SRVR
> NODE_NAME: US504I01
> STATUS: Missed
> RESULT:
> REASON:
>
> SCHEDULED_START: 2000-02-29 01:30:00.000000
> ACTUAL_START:
> DOMAIN_NAME: ORCL_PD
> more... (<ENTER> to continue, 'C' to cancel) c
>
> Output to screen cancelled. Please wait for the 'adsm>' prompt.
>
> adsm> select * from summary
> ANR2034E SELECT: No match found using this criteria.
> ANS8001I Return code 11.
>
> adsm> select * from backupsets
> ANR2034E SELECT: No match found using this criteria.
> ANS8001I Return code 11.
>
> adsm>
>
> adsm> select * from syscat.columns where tabname='SUMMARY'
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: START_TIME
> COLNO: 1
> INDEX_KEYSEQ: 1
> INDEX_ORDER: A
> TYPENAME: TIMESTAMP
> LENGTH: 0
> SCALE: 0
> NULLS: FALSE
> REMARKS: Start time
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: END_TIME
> COLNO: 2
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: TIMESTAMP
> LENGTH: 0
> SCALE: 0
> more... (<ENTER> to continue, 'C' to cancel)
>
> NULLS: TRUE
> REMARKS: End Time
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: ACTIVITY
> COLNO: 3
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: VARCHAR
> LENGTH: 64
> SCALE: 0
> NULLS: FALSE
> REMARKS: Process or Session Activity Name
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: NUMBER
> COLNO: 4
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: INTEGER
> more... (<ENTER> to continue, 'C' to cancel)
>
> LENGTH: 0
> SCALE: 0
> NULLS: TRUE
> REMARKS: Process or Session Number
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: ENTITY
> COLNO: 5
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: VARCHAR
> LENGTH: 64
> SCALE: 0
> NULLS: TRUE
> REMARKS: Associated user or storage pool(s) associated with
> the activity
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: COMMMETH
> COLNO: 6
> INDEX_KEYSEQ:
> more... (<ENTER> to continue, 'C' to cancel)
>
> INDEX_ORDER:
> TYPENAME: VARCHAR
> LENGTH: 8
> SCALE: 0
> NULLS: TRUE
> REMARKS: Communications Method Used
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: ADDRESS
> COLNO: 7
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: VARCHAR
> LENGTH: 64
> SCALE: 0
> NULLS: TRUE
> REMARKS: Communications Address
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: SCHEDULE_NAME
> more... (<ENTER> to continue, 'C' to cancel)
>
> COLNO: 8
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: VARCHAR
> LENGTH: 30
> SCALE: 0
> NULLS: TRUE
> REMARKS: Schedule Name
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: EXAMINED
> COLNO: 9
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: DECIMAL
> LENGTH: 18
> SCALE: 0
> NULLS: TRUE
> REMARKS: Number of objects (files and/or directories) examined by the
> process/session
>
> more... (<ENTER> to continue, 'C' to cancel)
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: AFFECTED
> COLNO: 10
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: DECIMAL
> LENGTH: 18
> SCALE: 0
> NULLS: TRUE
> REMARKS: Number of objects affected (moved, copied or deleted) by the
> process/session
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: FAILED
> COLNO: 11
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: DECIMAL
> LENGTH: 18
> SCALE: 0
> more... (<ENTER> to continue, 'C' to cancel)
>
> NULLS: TRUE
> REMARKS: Number of objects that failed in the process/session
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: BYTES
> COLNO: 12
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: DECIMAL
> LENGTH: 18
> SCALE: 0
> NULLS: TRUE
> REMARKS: Bytes processed
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: IDLE
> COLNO: 13
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: INTEGER
> more... (<ENTER> to continue, 'C' to cancel)
>
> LENGTH: 0
> SCALE: 0
> NULLS: TRUE
> REMARKS: Seconds that the session/process was idle
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: MEDIAW
> COLNO: 14
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: INTEGER
> LENGTH: 0
> SCALE: 0
> NULLS: TRUE
> REMARKS: Seconds that the session/process was waiting for
> access to media
> (volume mounts)
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: PROCESSES
> COLNO: 15
> more... (<ENTER> to continue, 'C' to cancel)
>
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: INTEGER
> LENGTH: 0
> SCALE: 0
> NULLS: TRUE
> REMARKS: Number of processes used for process
>
> TABSCHEMA: ADSM
> TABNAME: SUMMARY
> COLNAME: SUCCESSFUL
> COLNO: 16
> INDEX_KEYSEQ:
> INDEX_ORDER:
> TYPENAME: ENUMERATED(YESNO_TYPE)
> LENGTH: 3
> SCALE: 0
> NULLS: TRUE
> REMARKS: Successful ?
>
>
>
>
>
> Roy Lake <RLake AT AXIAL-TBG DOT COM>
> 04/18/2000 12:48 AM
>
> To: ADSM-L AT VM.MARIST DOT EDU@SMTP@Exchange
> cc:
> Subject: Database Utilisation zooming up after upgrading from
> ADSM to Tivoli
> 3.7 on AIX 4.3
>
> Any ideas as to why my TSM database would suddenly whizz up from
> around 60% to
> over 80% after upgrading from ADSM to TSM 3.7 ????....
>
> It appears to go up and down whilly nilly but stabilizes at 80%
> ...and its still
> rising???..
>
> Any suggestions greatly appreciated.
>
> Regards,
>
> Roy.
>
>
>
> ** IMPORTANT INFORMATION **
> This message is intended only for the use of the person(s) ("the Intended
> Recipient")
> to whom it is addressed. It may contain information which is
> privileged and
> confidential
> within the meaning of applicable law. Accordingly any dissemination,
> distribution, copying
> or other use of this message or any of its content by any person
> other than the
> Intended
> Recipient may constitute a breach of civil or criminal law and is strictly
> prohibited.
>
> The views in this message or it's attachments are that of the sender.
>
> If you are not the Intended Recipient please contact the sender
> and dispose of
> this email
> as soon as possible. If in doubt contact the Axial System Support Desk
> on +44 208 592 6666 x 296 (UK).
>
|
