Create a 6.2 Test Environment
The test area should correspond as closely as possible to the live deployment environment and to the OpenROAD 6.0 test environment. When you are testing your changes with either the Ingres DBMS or Enterprise Access, we recommend that you use a separate test installation so that you do not adversely impact your development environment.
Migrations from OpenROAD 6.0 to OpenROAD 6.2 remaining in ANSI mode require no additional changes to the environment. They just need to be set up carefully so that they are identical to but separate from the OpenROAD 6.0 environment.
Migrations from OpenROAD 6.0 Unicode to OpenROAD 6.2 remaining in Unicode require no additional changes to the environment. They only need to be set up carefully so that they are identical to but separate from the OpenROAD 6.0 environment.
Migrations from OpenROAD 6.0 ANSI to OpenROAD 6.2 utilizing the transparent Unicode feature require some additional changes to your environment. If you are planning to run in a UTF8/Unicode environment, some extra steps are necessary, explained below, to ensure a successful upgrade.
As you are testing your changes with either the Ingres DBMS or Enterprise Access, we recommend that you use a separate test installation so that you do not adversely impact your development environment.
• Be aware that if you install a new installation with II_CHARSET set to UTF8 to take advantage of the transparent Unicode feature, all client applications also must utilize a UTF8 character set.
• Create your Unicode-enabled database with the createdb utility, specifying the –i flag, which is the default if your installation character set is UTF8.
• Data exported from a non-Unicode-enabled database targeted to the new Unicode-enabled database must have been successfully converted to a new encoding. Failure to accomplish this task will result in data corruption in the Unicode-enabled database.
• Guidance on how to do this data conversion project is outside the scope of this guide. If you need help converting your data, we recommend that you contact Actian Support Services to assist with the conversion project (http://supportservices.actian.com/support-services/support#contacts).
• You must be using an Ingres 10.1.1 or later database server to use the UTF8 character set with the underlying DDL unchanged, as the UTF8 character set support allows you to store Unicode data in char, varchar, and long varchar data types.
The following checklist may be helpful in creating a proper test environment for the upgrade project, whether you plan to run in an ANSI or Unicode environment. These elements, or their absence, will impact the speed and success of your upgrade.
• OpenROAD installation, local or file-served. This includes:
– Ingres and operating system environment variables
– ingres\files area, especially config.dat and appedtt.ff, apped.ctb, and any variants
– ingres\w4glapps area, which contains all referenced application images
– Any globals redefinition files
– Any other files and file areas the applications reference, including 3GL library files, registered where necessary, with appropriate permissions
• The same test data that the OpenROAD 6.0 environment is working with, in a test database configured to match the live database, including any II_EMBED_SET or ING_SET settings. If you are copying the data using copydb, ensure that any contents of II_STORED_STRINGS and II_STORED_BITMAPS are copied as well.
• The test database needs to be Unicode-enabled and populated with test data converted correctly from the OpenROAD 6.0 environment.
• If you plan to migrate to a UTF8/Unicode environment, set the II_CHARSET to UTF8 for the all the installations in the 6.2 test environment.
– If you plan to migrate to a UTF8/Unicode environment, modify the DDL in Enterprise Access 2.7 or 3.0 installations to utilize Unicode data types.
• Ingres Net nodes that are redirected to up-to-date test or training databases
• Startup and other batch files, changed to reference the relevant databases, file systems, and so on, which are redirected as appropriate
• Shortcuts, as these may contain explicit parameters or settings
• User accounts, passwords, and permissions necessary to run the applications successfully
• Network connectivity where it affects OpenROAD application use
• Operating system, drivers, and settings, for example, monitor, regional, and language settings in particular
• Citrix settings, where applicable
• Any referenced non-Actian software, where its absence may prevent navigating to or displaying parts of the OpenROAD application
• A display monitor set to client specifications
Ensure that you can access this test environment through an account with sufficient rights to issue commands such as ingsetenv.