Nothing like jumping into the deep end, eh, Perry?
144GB. More by the time this thread is finished.
If RESIZE INPLACE fails, what is the typical kind of failure to expect?
What's the worst that can happen? What has happened to others?
If you do this, please let us know the result, good or bad, including
the activity level on that file while the resize was happening.
It's all very interesting, but as dearly as I love you all at ZirMed, I
am happy to watch from a distance.
This is my typical approach for resizing big files. It avoids the
RESIZE command & requires some, but little, downtime.
I am certain Perry knows all this, but there are always new people
listening in.
It requires being able to identify which records have been updated
recently, (e.g. indexes).
That may mean a little planning ahead, anticipating future needs, such
as resizes.
1. Create a new empty file the proper size and copy the entire old file
into the new.
2. Create a list of all records updated since the copy began.
3. Recopy those. Repeat 2&3 as needed.
4. Shut off all other access to the file. (No one has it open, can open
it.)
5. Create a list of all records update since last iteration of #2-3.
6. Recopy those.
7. Set.index to null on the original file <-- dont forget to do this!
8. Rename to original file
9. Rename to new file to be live file
10. Set.index on the new live file. attach original indexes to new file.
11. Let users at the file.
Warm regards,
Chuck
On 4/25/2013 3:09 PM, Perry Taylor wrote:
Before I go and resize a 144GB file has anyone had any experiences with the
INPLACE option of RESIZE in UniVerse? Good, bad, ugly???
Thanks.
Perry
Perry Taylor
Senior MV Architect
ZirMed
888 West Market Street, Suite 400
Louisville, KY 40202
www.zirmed.com<http://www.zirmed.com/>
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
