Re: Onunload/Onload

Milton J. Vidrine, Jr. wrote in message <3672BC58.34FAFE5A@hal-pc.org>... >I am setting up a second Informix (7.24.UC5/Solaris 2.6) instance on the >same box as an instance that is already running and can be shut down >only on a temporary basis. Although I am only transporting one database >to the new instance, it is the biggest part of its 86 gig instance. The >database has some 1,400 tables, the largest of which is 50,000,000 rows, >and I do not have large amounts of disk space available. I do have at my >disposal, however, a single DLT 4000 20 gig tape unit. Taking into >account all the Informix data migration tools available, I have decided >to use onunload/onload, especially since I am trying to minimize >operator/programmer intervention. > >However, I keep getting an error 4 after about 4 hours of unloading >(UNIX translation: "Interrupted System Call" ? ) Does anyone have any >experience with this tool? What gives? Is onunload not "smart" enough to >sense EOT and ask for another tape? It's certainly true that Informix products are not generally too hot on EOT. You should set your TAPESIZE parameter, or the tapeseize setting in your onunload, to a bit less than 40GBytes so that Informix propmpts for a new tape in a software-controlled fashion. My experience with DLTs on Solaris is that you might expect of the order of 8GBytes/hour, so the timing would be about right for EOT. All of the above begs the question "How do you archive your database server?" Neil Truby aracnet Limited Weybridge, UK