Progress 6.2 L runtime

S

Sedso

New Member
Hi,

I want to migrate a database, which is on Progress 6.2 L runtime, SCO Unix 386 platform. (It has appr 150 tables and 8 million posts)

What I have in my hand are the .db and .df files. There is no problem with the .df (data dictionary) file - using notepad is enough to read it. However, the .db file is not very promising; i.e., notepad is not enough.

Is there a easy or relatively quick way to get the data in ASCII-files?

[Here is the longer version of my question:
1. Is there a way to convert this .db file to an ASCII-file?
2. Using some data integration programs might help, then I will need ODBC. Which version of it will be helpful for Progress 6.2?
3. Or will it be easier to use the dbms itself to get the data? and how?]

Any ideas?

Sedso.
 
Does this mean that you have no Progress to run it with? The only way I can imagine that you are going to get the data out is with a dictionary export.
 
Actually I have access to the progress db , but since it is a runtime version, it doesn't have all the features, which makes things complicated.

S.
 
Migrate to what?

If this is a commercial application it is possible that the vendor provided data extract tools. You might want to look for those. You could get lucky.

If you just want to change platforms and upgrade Progress then you can use the conversion tools in $DLC/bin/83dbutils, 91dbutils and 101dbutils to get you all the way to OpenEdge 10.1.

If, on the other hand, you want to extract the data so that you can load it into some other database then you need to be able to write 4gl queries. You won't be able to do that with a runtime license.

Forget ODBC. It doesn't exist for a v6 database and even if it did the drivers would be hopelessly out of date, broken, unavailable and nobody would remember how to install them.

You might be able to find someone with the necessary licenses who would be willing to either:

1) Provide v6 r-code compiled against your schema (you say that you have a .df file). This is unlikely as a) there aren't that many people who still have v6 and b) r-code compatibility in v6 is "touchy".

2) Do the conversion using the tools above and extract the data for you.

In any case you'll probably find more people willing to do this as a consulting engagement than as a freebie. It's a non-trivial task which will involve some serious effort.
 
actually, i still have a 6.2 development version.

i can possibly do the job for you but it would not be free.
 
You must log in or register to reply here.
Back
Top