Re: onunload/onload yields error 312

Hi, I often use onunload and onload (tables are not 'so' big, the biggest is 17mln rows). I use write in a tape unit in other server: onunload -t <hostname>:/dev/rmt0 -s 8000000 -b 1024 <database>:<table> And, in this server that is mentioned in 'hostname', I run: ondblog nolog <database> onbar -b -F (this 'onbar' command really 'put' your database nolog) onload -l -t /dev/rmt0 -s 8000000 -b 1024 -d <dbspace> <database>:<table>ondblog unbuf <database> onbar -b -F Look: You don't mentionate that you run 'onbar -b -F'. If I'm not wrong, constraints are not transported from one to other. You have to recreate it. It works well. Regards, R. Ferronato RudyFernandes@yahoo.com (Rudy) wrote in message news:<3d531325.0403131616.11456a51@posting.google.com>... > This could be related to the use of onload. If you can, try HPL's > express ascii load/unload instead - it usually is as fast as > onunload/onload. Also, since the intermediate stage is ascii, unlike > onload's binary, its likely to be less prone to error. > > Rudy