Consultor Eletrônico



Kbase P17361: What to do when replacing Progress 32 bits with a Progress 64 bits product.
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   10/15/2010
Status: Verified

GOAL:

Can I replace a Progress HP-UX 11 32-bit by a Progress HP-UX 11 64-bit product?

GOAL:

Can I replace a Progress Solaris 32-bit with a Progress Solaris 64-bit product?

GOAL:

Considerations when upgrading Progress 32 bits to a Progress 64 bit product

GOAL:

How to replace the 32-bit Progress Installation with the 64-bit Progress Installation?

GOAL:

How to install 64-bit Progress?

FACT(s) (Environment):

All Supported Operating Systems
Progress 9.1x
OpenEdge 10.x

FIX:

Progress 32/64 bit products are compatible for the Progress database, there are no structure differences, it is only the Progress executables that are built differently. It is therefore not necessary to dump and load a database when migrating the OS from 32-bit to 64-bit mode.

Progress does not run any certification of its 32-bit product in the 64-bit environment when there is a 64-bit Progress version. However, the 64 bit Progress product within the 64 bit environment should give better performance than using the 32 bit Progress product, provided that the kernel is appropriately tuned.

Progress recomends that proutil dbanalys is issued against the database on the original and the new installation to compare the number of records in each table to confirm the success of the operation. Always have a valid backup of the database before starting the migration process.

The following steps assume that the 32-bit version of Progress is no longer required:

1) truncate bi files of database
2) probkup the database on 32bit/32bit machine as usual
3) backup the current 32-bit intstallation
4) uninstall the current 32-bit intstallation
5) Boot the machine in 64 bit mode
6) ensure that the correct java -version is installed and is listed in the $PATH
7) install Progress 64-bit to same dlc as the 32-bit
7a)Optional but recommended: recompile the source code
8) proserve the database.