RE: onunload/onload problem using tape

An update: For now to get this request done I specified the block size in the onunload/onload and that seems to be working. I'm not sure what changed to make the script I have been using 20 plus time, to fail this time. John -----Original Message----- From: informix-list-bounces@iiug.org [mailto:informix-list-bounces@iiug.org] On Behalf Of John Adamski Sent: Sunday, June 24, 2012 12:49 PM To: informix-list@iiug.org Subject: onunload/onload problem using tape HPUX B.11.31 U ia64 on HP BL870c IDS 11.50.FC6 We have two HP BL870c Integrity servers, one is the production the second is for testing and recovery if production server fails. The systems have been in place for about 6 years and share two lto2 tape drive via fiber. Today I was trying to move a test DB from the test server to production server using onunload (/opt/informix/bin/onunload -t /dev/rmt/c16t0d1BEST cars). Have done this numerous times in the past. It has been about 6 month since the developers needed me to do this. I know of no changes to the hardware, OS or tape drives. The onumload command seemed to have worked, but when I try to do the onload command on the production server (/opt/informix/bin/onload -t /dev/rmt/c16t0d1BEST -d dbs1 train), I'm getting the following Mismatch in tape block size -- tape block size = 32K. d press Return to continue ... I have a support call in to HP to see what's going on, but so far has not been helpful. My 10+ year old training on onload/unload is rusty and I am thinking the block size written to the tape is determined by the OS/tape drive and not Informix. Is this correct? I want to make sure this is a hardware/OS issue and really has nothing to do with Informix - other than is causing the onload to fail. John David Adamski, Sr. Network Specialist Graceland University, 1 University Place, Lamoni, IA 50140 _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list

On Sunday, June 24, 2012 4:24:47 PM UTC-5, jda wrote: > An update: > > For now to get this request done I specified the block size in the onunload/onload and that seems to be working. I'm not sure what changed to make the script I have been using 20 plus time, to fail this time. > > John > > -----Original Message----- > > HPUX B.11.31 U ia64 on HP BL870c > IDS 11.50.FC6 > > We have two HP BL870c Integrity servers, one is the production the second is for testing and recovery if production server fails. The systems have been in place for about 6 years and share two lto2 tape drive via fiber. > > Today I was trying to move a test DB from the test server to production server using onunload (/opt/informix/bin/onunload -t /dev/rmt/c16t0d1BEST cars). Have done this numerous times in the past. It has been about 6 month since the developers needed me to do this. I know of no changes to the hardware, OS or tape drives. > > The onumload command seemed to have worked, but when I try to do the onload command on the production server (/opt/informix/bin/onload -t /dev/rmt/c16t0d1BEST -d dbs1 train), I'm getting the following > > Mismatch in tape block size -- tape block size = 32K. > d press Return to continue ... > > I have a support call in to HP to see what's going on, but so far has not been helpful. > > My 10+ year old training on onload/unload is rusty and I am thinking the block size written to the tape is determined by the OS/tape drive and not Informix. Is this correct? I want to make sure this is a hardware/OS issue and really has nothing to do with Informix - other than is causing the onload to fail. > > John David Adamski, Sr. Network Specialist Graceland University, 1 University Place, Lamoni, IA 50140 > > > _______________________________________________