Re: dbexport to disk & 2GB limit question

Five Cats wrote: > > A customer using IDS 7.31.UD4 on SOLARIS will need to export their > database soon to copy it to the test instance. (no second machine > sadly). Obviously we want to export to disk, but the largest table > *might* produce a .unl file larger than 2GB. > > Does anyone know if are we likely to have a problem with this table > exporting to disk, or if it will be OK should the .unl exceed 2GB? > > We really do not want to have to export to tape.... > > -- > Five Cats > Email to: cats_spam at uk2 dot net Use the HPL. There never was a 2GB limit unloading to pipe (this way you avoid the seek, which may or may not be compiles in a 32bit version on your copy) Or use (untested garbage follows!) mkfifo this_is _my_named_pipe # lets read in a background process # whatever appears in the fifo (one can/should # use a compress utility here - saves plenty of disk space) cat this_is _my_named_pipe > unlfile.unl & dbaccess my_database <<-EOF >my_rotten_log.log 2>&1 -- now one pulls the chair under my a$$ LOCK my_tble IN EXCLUSIVE MODE; UNLOAD to 'this_is _my_named_pipe' SELECT * FROM my_table; EOF HTH dic_k -- Richard Kofler SOLID STATE EDV Dienstleistungen GmbH Vienna/Austria/Europe