D
dbeavon
Guest
I would like to load some production data locally into my own PDSOE-licensed database on my workstation. I have a big SSD and lots of space. Performance will not be an issue (I expect I'll probably get better performance on my local SSD than what we have on the production EMC disk, even after many years of tuning - type II areas by size, etc). I'm not a Progress DBA. I'm more of an OE/ABL developer. The production data lived on an HP-UX/IA64 server; it was already backed up and restored on a staging/development HP-UX/IA64 server and I already deleted half of the data to make sure it should only be in the 100-200 GB range. But it turns out that getting data into a local database on my Windows workstation is not going smoothly. It should be a *lot* easier than this... I'm not sure why the dump/load has to be managed on a table-by-table and area-by-area and extent-by-extent basis. What a lot of micro-management... To make matters worse, I get half-way thru my binary load only for it to fail, telling me my variable-length extent has filled up and shutting down my database! I do some research, find a way to enable large files for my variable-length extents, only to find that it won't let me. So now I have to pre-allocate a ton of tiny 2GB "fixed" extents for each storage area, just to move over the data . This is like a multi-day effort and I'm almost ready to go hire an OE DBA/expert to work on my laptop for me. Before attempting this work, I was aware it wouldn't be just a backup/restore. I knew that moving data from an HP-UX server to a Windows desktop requires binary dump/load. But I guess I wasn't prepared to be jumping so many hoops. Micro-managing extents is especially annoying. If *any* database license allows for simple, variable lenth extents, with large files (>2 GB), it should be the PDSOE license. That would make this process quite a bit less painful than it is. Is there a back-door way to enable that feature? Am I going about this stuff all wrong? Does my experience sound typical for setting up a local copy of the production database?
Continue reading...
Continue reading...