Are there any third party tools that allow Progress customers to do a cross-platform "backup"/restore? The intermediate "backup" file(s) would not need to be a standard format. They could be in any format (perhaps simply consisting of a package of regular OE dump files). The reason I ask is because Progress has left a big gap where this backup/restore feature should exist. I was hoping that somebody had something to fill the gap. (I'm thinking of vendors like riverside, roundtable, bravepoint, or any other vendor).
Another obvious option is to dump/load but that is soooo much work. It involves numerous and very error-prone steps to be done manually by the DBA. Moreover it is very time consuming from the a DBA's point of view and, depending on how good the DBA is, the process can under-utilize the available hardware (ie. CPU and disk can remain largely unused on either the source machine, target machine, or both if the DBA is busy organizing their manual work, or they are neglecting to operate on multiple tables concurrently). If hardware is under-utilized then it can cause the outage window to be far longer than it needs to be.
Long ago we had asked Progress about a product of theirs, "PRO D&L", but they said that wasn't used for the same purpose (ie. simply automating a dump/load). I think that product was for hooking into replication triggers and allowing a cross platform migration to be performed over several days without any database outages. We are looking for a much more *simple* (but fast) operation that moves data from one platform to another during an outage window that is as short as possible.
I found an enhancement idea that is a couple years old now, and was wondering if this might be completed before HP-UX comes to its end-of-life date in 2025.
It will be nice to move out of HP-UX one day. We'd go to another Progress platform like Windows or Linux. But the prospect of doing the dump and load is not something we look forward to. Long ago we did these dump/loads on a yearly basis, but these days we are a bit out of practice.
Speaking of migrating HP-UX databases, I thought I would point out that there was once a time when we ran the OE database on HP-UX PA-RISC. When that architecture stopped being supported by Progress, they were able to waive a magical wand and allowed the OE database to be migrated from PA-RISC to Itanium *without* requiring a dump and load (see KB: https://knowledgebase.progress.com/articles/Article/P132598 ). Is it reasonable to hope that they will do a similar thing when the time comes once again to stop supporting Progress on Itanium? (Eg. OE 12 no longer supports Itanium)
It would be really nice if Progress would consider doing all the heavy lifting for us. Using their dump/load process is not a very happy prospect at all.
The only adequate solution today for migrating large databases from one platform to another is Pro2Pro. it's really not difficult, and, most importantly, efficiently without long downtime.
IMHO, something else, most likely, will not be implemented taking into account various architectural constraints.
Entire dump / create / load can be scripted quite easily with pct.
> On Aug 29, 2018, at 7:31 PM, dbeavon wrote:
> It sounds like there is an opportunity for someone to create a tool to facilitate the migration of a database away from HP-UX.
How much would you be willing to pay for such a tool ?
>> How much would you be willing to pay for such a tool ...?
@gus ... to me it would probably be worth the equivalent of 1-3 years of maintenance on a PDSOE license. It might be worth as much as hiring a consultant (to work on a home-grown/custom database migration). A tool is something that we could use repeatedly. On the other hand we probably wouldn't want to hire a consultant for the same type of work repeatedly. And we wouldn't need to if we had a good tool.
Let me ask you a similar question... how much would a pro2pro engagement (and rental) be if the goal is to simply migrate a 500 GB database in production from HP-UX to Windows? How would that compare to hiring a consultant who would do a home-grown migration?
One point of Clarity. Pro2 Version 5 includes a CDC license for use with Pro2 only.
But OE CDC is an ADD-ON license. For example, the client has 100 OpenEdge RDBMS licenses, which means that we need 100 OE CDC licenses, right?How many CDC licenses are provided with Pro2?
Russian Progress User Group
Valeriy, we have a Customer of me has a license for Pro2, but the menuepoint for CDC is disabled. Is that because they do not have a RDBMS CDC license?
For use Pro2 + OE CDC, you need :
1. Enable CDC on the database (Need CDC license).
2. In the predefs.i file, set ENABLE_OE_CDC parameter to Yes to enable the CDC menu.