Migrating OpenROAD 3.5 to any release prior to OpenROAD 12.0 is straightforward in most respects, provided it is properly prepared for and carefully executed. Much of the migration work involves the automated correction of known migration issues covered later in this chapter. In most other cases, minimal code changes should suffice. However, certain issues need careful attention, and one may require significant work (the move away from database drivers for installations that use non-Ingres databases). It is unlikely that a completely manual migration will be either cost-effective or of sufficient quality.

The application is unintentionally corrupted by this process. For example, all button labels in the application are now missing. Unless a backup of the original OpenROAD 3.5 exported application was preserved before importing it into OpenROAD 12.0, the changes are irretrievably lost. This is why Actian Corporation strongly recommends that you migration OpenROAD 3.5 applications to OpenROAD 5.1 as an intermediate step before moving the applications to OpenROAD 12.0. Then the following procedure can be performed, if necessary, without corrupting the application:

This chapter focuses on the known issues specific to migrating from OpenROAD 3.5 to any version prior to OpenROAD 12.0 and their resolution. If your intent is to ultimately move from OpenROAD 3.5 to OpenROAD 12.0, you should break the migration process into two parts: