If you are accessing the same Ingres instance in OpenROAD 12.0, you may copy the database connection profiles from the OpenROAD 6.2 storage location to the OpenROAD 12.0 location.

You can obtain this location from the OR_CONFIG environment variable in your particular Windows environment. To do so, open an OpenROAD Command Prompt and enter:

The location of your profiles is returned. For example, on Windows 10:

Copy the files from the OpenROAD 6.2 location to the OpenROAD 12.0 location.

If you want to connect to a new Ingres instance, at the end of installation or the first time you start Workbench, the OpenROAD 12.0 Startup Assistant will guide you through the process of creating a default database connection profile.

For more information about creating database connection profiles, see “Define a Database Connection Profile” in the Workbench User Guide.

ISSUE: Problems result when you build *.c files from *.sc files that contain EXEC SQL (ESQL/C) commands using esqlc. If you use esqlc, it could produce C code incompatible with OpenROAD. This is why esqlcor is shipped with OpenROAD 5.0 and later.

RESOLUTION: Use esqlcor to build your *.c files instead of esqlc to pre-process ESQL/C applications.

For more information and instructions to use esqlcor in building C files, see the Readme_4GLsample.txt file in $II_SYSTEM/ingres/w4glsamp/esqlc.