Known 6.0 Issues to Resolve
Copy Profiles to Connect to the Same Ingres Instance
If you are accessing the same Ingres instance in OpenROAD 12.0, you may copy the database connection profiles from the OpenROAD 6.0 storage location to the OpenROAD 12.0 location.
Note: Close OpenROAD before copying the files.
Copy files from the OpenROAD 6.0 location
For Windows Server 2008, Windows Vista, and Windows 7:
%ALLUSERSPROFILE%\OpenROAD\Profiles
For Windows Server 2003 and Windows XP:
%ALLUSERSPROFILE%\Application Data\OpenROAD\Profiles
To the OpenROAD 12.0 location
For Windows Server 2008, Windows Vista, and Windows 7:
%USERPROFILE%\AppData\Local\OpenROAD\Profiles\installation_ID
For Windows Server 2003 and Windows XP:
%USERPROFILE%\Local Settings\Application Data\OpenROAD\Profiles\installation_ID
Recreate Profiles to Connect to a New Ingres Instance
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.
Building C Code Containing EXEC SQL Commands
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.
Last modified date: 06/25/2024