RE: 2 gb file limit [SUMMARY]

Neil, you are probably right. I would not have a clue about onunload. I apologise for being frivolous in thy generalisations. I will clarify what I was babbling about. The object of the exercise is export and import the database, as all my extents are SUPER high. (How or why they got this way does not matter) If I wanted to do a dbexport to tape I would have to use several tapes, as it will only write 2 GB per tape. This for me would be a PITA. (Informix support advised me of this; I also tried with a 40gb dlt. This is apparently a Unix constraint) I cannot consider using unonload as I want to change the initial extent size. Alter fragment is also not an option, as I just don't have the disk spacespare. Purchasing disk is also out of the question. So the bind it be. Dump and reload. I will be doing unload, by criteria for my large tables and when the database is small enough I will be exporting the remainder. I hope this clears everything up... Regards Suze. -----Original Message----- From: Neil Truby [SMTP:ntruby@netcomuk.co.uk] Sent: Friday, 16 October 1998 12:34 To: informix-list@iiug.org Subject: Re: 2 gb file limit [SUMMARY] Susan Elliott (ISG) wrote: > > Quite right. Informix support advised me that it was a limitation of > Informix. > > You also can't use a dlt / tape as there is also a 2 gb limitation from the > unix side. > Thanks everyone. No, that simply isn't true Susan. I have, in the past week, done an onunload of a database whose size is well in excess of 8GBytes to tape. I've also onunloaded the same database to raw disk (using HP's volume manager) without any problems. Neil