Thats cool
----- Original Message ----- From: "Manu Fernandes" <>
To: "U2 Users List" <>
Sent: Sunday, April 28, 2013 2:45 AM
Subject: Re: [U2] [UV] RESIZE INPLACE


Given the risk of manipulating a file of this size, I recommend the use of distributed files (DEFINE.DF). Just as effective, if not better, each part file is administered individually (backups, resizing, indexing, !accessing, locking,...)

Procedure :

1 - analyse the keys to build a distribution algorythm ; at worst use hashing algorythm ; don't forget a elsewhere partnumber (1 )

2 - create part files (define how many, size, ..., by analysing number key-records, time growing ,...)

3 - define distributed file ; DICT adress the original DICT

4 - copy all record from orig.file to df.file (do it one time before live to check if all keys can be processed by your algorythm)

5 - edit VOC orig.file to adress df.file as data file

6 - resize all part file individually.

7 - delete the orig.DATA file &index from os ; to get back your 144gb

My two pence

-----Message d'origine-----
De : [mailto:u2-users-] De la part de Perry Taylor
Envoyé : jeudi 25 avril 2013 22:10
À : U2-Users List

Before I go and resize a 144GB file has anyone had any experiences with the
INPLACE option of RESIZE in UniVerse?  Good, bad, ugly???


Perry Taylor
Senior MV Architect
888 West Market Street, Suite 400
Louisville, KY 40202<>

CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. ZirMed, Inc. has strict policies regarding the content of e-mail
communications, specifically Protected Health Information, any
communications containing such material will be returned to the originating party with such advisement noted. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
U2-Users mailing list

U2-Users mailing list

U2-Users mailing list

Reply via email to