Hi Geoff, See Chapter 7 "Automating tasks", section "Return codes from the command line interface" in the client manual for an explanation of the return codes. After reading that, let me know if you have any other questions on this.
I cannot say what happened in your specific situation, but the most common reason for the message index errors is because the upgrade was performed while an instance of the client was running. Best regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 01/16/2007 04:23:25 PM: > I don't know what anyone else feels about the Failed 12 reports but to > me there are too many ways for this to be reported with little to no > information as to what is really wrong. Here is another in cases I have > seen. This node has been backing up just fine for months. It seems like > the update of the client software (Windows 2003) to 5.3.4 has something > to do with this but I have not tried to go into our CCD records to > compare to the TSM logs yet only because I just haven't had time. > > > > The activity log on the TSM server (AIX 5.3, TSM 5.3.3.0) shows > absolutely nothing except the Failed 12 report in the backup statistics > for the completed backup. So the only thing I see is this ANS0106E > message index not found on the client side. I don't see how that would > cause a Failed 12 report but maybe it is. > > > > Does anyone have any ideas? By the way I did see the ANS2820E message > but since the backups starts at 22:30 to me it is not relevant here, but > feel free to correct me if I'm wrong. > > > > 01/12/2007 16:43:03 TSM > > 01/12/2007 16:43:04 ANS0106E Message index not found for message 15314. > > 01/12/2007 16:43:05 TSM > > 01/12/2007 16:43:05 ANS0106E Message index not found for message 14969. > > 01/12/2007 17:09:43 TSM > > 01/12/2007 17:09:44 ANS0106E Message index not found for message 15314. > > 01/12/2007 17:09:44 TSM > > 01/12/2007 17:09:45 ANS0106E Message index not found for message 14969. > > 01/12/2007 18:46:36 ANS0106E Message index not found for message 1577. > > 01/12/2007 18:46:36 > > 01/12/2007 18:46:39 ANS0106E Message index not found for message 1577. > > 01/12/2007 18:46:39 > > 01/12/2007 18:46:39 ANS2820E An interrupt has occurred. The current > operation will end and the > > client will shut down. > > 01/12/2007 22:29:36 ANS0106E Message index not found for message 14965. > > 01/12/2007 22:29:36 ANS0106E Message index not found for message 14969. > > 01/12/2007 22:29:36 ANS1512E Scheduled event 'CLIENT2-INCREMENTAL' > failed. Return code = 12. > > 01/14/2007 22:29:43 ANS0106E Message index not found for message 14965. > > 01/14/2007 22:29:43 ANS0106E Message index not found for message 14969. > > 01/14/2007 22:29:43 ANS1512E Scheduled event 'CLIENT2-INCREMENTAL' > failed. Return code = 12. > > 01/15/2007 22:29:37 ANS0106E Message index not found for message 14965. > > 01/15/2007 22:29:37 ANS0106E Message index not found for message 14969. > > 01/15/2007 22:29:37 ANS1512E Scheduled event 'CLIENT2-INCREMENTAL' > failed. Return code = 12. > > > > > > Thank you for any help, > > Geoff Gill > TSM Administrator > PeopleSoft Sr. Systems Administrator > SAIC M/S-G1b > (858)826-4062 > Email: [EMAIL PROTECTED] > >
