Dear List I have been investigating the usage of the db2adutl command switches verify and extract, with the following observations: 1) db2adutl verify full taken at 'timestamp' database xxxxx a) the full file is not traversed with only a percentage of the buffers accessed - at the end of the verification the following message is issued: WARNING only partial image read, bytes read: 28672 of 4194304 Read 0 bytes, assuming we are at the end of the image Image Verification Complete - successful. b) the occasional error messages are displayed (which appear not to be too serious, given that success is still proclaimed) ================== BUFFER 36 ================== ERROR: Unknown object type detected Read in type 12 and 2) db2adutl extract full taken at 'timestamp' database xxxxx This obviously requires space on disk somewhere to hold the entire backup file .. is there an algorithm relating to the amount of "TSM clutter" wrapped around the database backup, so that an accurate estimate for space requirements can be made.
Generally: do any of my fellow List'ers use either of these to verify the validity of the backups, or do they believe the RC=0, therefore the backup is OK! (?) David Green For more information on Standard Life, visit our website http://www.standardlife.com/ The Standard Life Assurance Company, Standard Life House, 30 Lothian Road, Edinburgh EH1 2DH, is registered in Scotland (No. SZ4) and regulated by the Financial Services Authority. Tel: 0131 225 2552 - calls may be recorded or monitored. This confidential e-mail is for the addressee only. If received in error, do not retain/copy/disclose it without our consent and please return it to us. We virus scan and monitor all e-mails but are not responsible for any damage caused by a virus or alteration by a third party after it is sent. - ::: When replying to the list, please use 'Reply-All' and make sure ::: a copy goes to the list ([EMAIL PROTECTED]). *** To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED] *** For more information, check http://www.db2eug.uni.cc
