Re: Onunload/onload to raw disk?

I've used it. It's fine. In fact, if you're going to do an onunload to disk (and why not? - this obsession with tape beats me) then it's a better way than cooked disk to do it. For large databases you're going to be constrained by the physical size of your disks (or logical units if you're using some sort of storage array). To avoid messing around with "end-of-tape" conditions you should use a logical volume manager to create a volume of sufficient size to accept your unload. I use a block size of about 1MByte generally. Neil Truby aracnet Limited Weybridge, UK Stefanie Vario wrote in message <36662B83.449@speedlink.net>... >Has anyone ever performed onunloads/onloads of databases to raw disk? >If so, what types of problems/issues were encountered? What block size >would be good to use in the onunload/onload command? >Thanks for any info. > >Stefanie Vario >svario@roush-ind.com