problem with onload

I am in the process of moving my informix instance from local drives attached to our server to some disk space on our SAN. I've gotten the dbspaces and associated chunks set up based on the raw disk files on the SAN drives, and the instance is up and running. Root dbspace seems to be fine and I've loaded one database (an audit database) into a dbspace names dbs1. I got that database unloaded and loaded using the Informix onunload and onload commands. But when I try to use the onload utility to load my main database it's not working. It runs and slowly increments the space used on the dbspace dbs1, and I can see where the database has been created. Of course it's locked during the load process so I can't look any closer than that. But at some point the process just stops and the dbspace emtpies back out. The fristrating thing is that it's close to being finished when it does that. The newly used space in dbs0 nearly matches the size of the onunload file. But then it just stops, no error message. Like it thinks it's finished successfully, but then drops the database. Any thoughts? Thanks in advance, John

"John W" <jwalchle@mvnu.edu> wrote in message news:1154172121.522127.275350@m73g2000cwd.googlegroups.com... >I am in the process of moving my informix instance from local drives > attached to our server to some disk space on our SAN. I've gotten the > dbspaces and associated chunks set up based on the raw disk files on > the SAN drives, and the instance is up and running. Root dbspace seems > to be fine and I've loaded one database (an audit database) into a > dbspace names dbs1. I got that database unloaded and loaded using the > Informix onunload and onload commands. > > But when I try to use the onload utility to load my main database it's > not working. It runs and slowly increments the space used on the > dbspace dbs1, and I can see where the database has been created. Of > course it's locked during the load process so I can't look any closer > than that. But at some point the process just stops and the dbspace > emtpies back out. The fristrating thing is that it's close to being > finished when it does that. The newly used space in dbs0 nearly matches > the size of the onunload file. But then it just stops, no error > message. Like it thinks it's finished successfully, but then drops the > database. Sorry, no ideas on your onunload problem. Did you have the same problem in testing? But a much better way of doing this is to use Informix mirroring. Do a Google group search and you'll find that the procedure has been described in detail in the past by me, by Paul Watson, and others.