Help with Ascii Dump and Load

I am so confused - we have a Progress DB 64 bit.

We have never done the Ascii Dump and Load since we went live in 2011.

We have Progress 64 Bit - our main server is Server 2008 - 64 bit.

The app server is 2003 R2 - x64 Edition.

The directions says to “You will then need to copy the backup file over to the system that
has the OpenEdge 10.2A 32-bit install. You will restore it using the 32-bit
OpenEdge. Then follow the steps listed in the document. When done with the
dump and load process you will reverse the previous steps by backing up the
database with the 32-bit OpenEdge 102.A, copy the backup file to the system that
has the 64-bit OpenEdge 10.2A and restore it there.”

How do I do this?

Every Epicor 9.05 customer who has x64 bit install of OpenEdge needs to have what we refer to as an “Admin Workstation” that has x32bit OpenEdge components for certain activities like admin tools/conversions.

When Epicor sent out the original install media for Epicor 9.05, we sent two discs–one with x32bit OpenEdge the other with x64 OpenEdge.

You can tell if the install of OpenEdge on a machine is x32 by looking in the Start Menu > OpenEdge 10.2a–if you see the Progress Explorer Tool (icon looks like a golden sprocket) it is a x32bit install.

If you need the x32bit install media, you can contact Epicor Customer Service and request the media be sent out.

If you are on current Epicor maintenance, Support does have a webex recording that goes through the entire ASCII dump and load process that you can request that will help with the process.

Our Progress Explorer Tool is a Sprocket.

I will ask for the webex recording.

Thanks Much

One more question - since the Progress Explorer is 32 bit - does this mean it is a 32 bit workstation?

I am just not good with stuff.

If you have the Progress Explorer Tool sprocket, that is a x32bit workstation the way that Epicor uses the term even if your Windows OS is x64bit.

Where can I find the Ascii Dump and Load Kit that is suppose to free

It can be provided by Epicor Support.

1 Like

If’ it’s ok to ask, what is the motivation for completing the dump and load at this point in time? Did someone in Support recommend it to resolve a particular issue?

When we did this years ago after going live on E9 we found that running this on a standalone pc with a fast ssd turned the process time from days to hours. Our progress database is about 40-50gig

If the motivation is only to defrag the database for performance reasons, then the binary dump and load would be a much faster option than an ASCII d&l. The ASCII dump and load is only needed if one suspects there is data corruption as it validates that the data being inserted into a column matches the data type whereas a binary doesn’t do any data validation.

Or… one could just migrate to Epicor 10.x and the need for dump and loads of any variety goes away :slight_smile:

I do suspect corruption - when they went live - they bought over some data is a funky way. We have records in our PartBin Table with 0 on hand - etc.