is the reason it wants an existing tape...because when you set dbbackuptrigger you specified numincremental (indicating incrementals instead of fulls 6 is the default for this 0 (full) would have to be specified... FYI
-----Original Message----- From: Frank Kruse [mailto:[EMAIL PROTECTED]] Sent: Monday, April 15, 2002 9:13 AM To: [EMAIL PROTECTED] Subject: Database backup trigger spits out tape over and over again. Let me try this problem again. I have my dbbackuptrigger defined to backup to devclass "8mmdb". When I enable the logmode to rollforward, the db wants to do a full backup. When the process kicks off, the tape drive (manual) reads the tape and immediately spits it out. If I query the processes, I see the process for the db backup. If I query the requests, I see that TSM is requesting me to mount volume "DBBK.1" I do not have this volume anymore, I can't re-label a volume dbbk.1 because it is already in the volhist. Is there any way I can keep this from happening? My dbbackuptrigger is pretty much useless at this time. I can't get a tape to stay in the drive. I was finally able to label a tape (with logmode normal only), then do a manual db backup to the new volume. Do I need to delete the dbbackuptrigger and recreate? -- ****************************************************** * Frank Kruse [EMAIL PROTECTED] * * IBM Austin 512-823-7475 * ******************************************************
