Re: onunload/onload

my experience with onload/onunload is that your destination database has to have corresponding dbspaces that your original database used. In other words, let's say your original database was in db0. However, you had some tables that you fragmented out to db1 and db2. You onunload the database, and you onload it to another machine. What I've seen is that it blows up when it tries to onload if the new machine doesn't have dbspaces by the name of db1 and db2 for your fragmented tables. Neil Truby wrote: > My initial tests suggest that it's prevalent in IDS 9.20 as well. If this > proves to be so I'll be mightily pissed off, as I reported the problem in > v7.24 in March 1999. > > >> Version: Informix 7.23.UC4 > Platform: Sun Sparc Solaris > > We unloaded a database that had the indexes fragmented in a separate > database space from the tables. When we onunloaded it and then attempted to > onload it into one database space we received an error. A call to Informix > notified us that this was an existing bug that is fixed in 7.3, well I was > wonder if it is also fixed in 7.24.UC5. If you know that it is please let > me know. > > TIA -- Phillip Tien Database Administrator Whole Foods Market, Inc. "I always wanted to be the last guy on Earth just to see if all those women were lying to me."