Ingres Corporation |
2.0 Operating System Support
2.1 Preprocessor and Compiler Support
4.0 Installation Considerations
4.1 New Installer on Windows
4.2 Install Now Capable as Any User
4.3 Some Binaries Have Changed Names
4.4 Multiple Ingres Instances on a Windows Machine
4.5 Additional Functionality When Starting Ingres as a Windows Service
4.6 Safeguarding Passwords During Response File Creation
4.7 Installation on Vista and Windows 2008
4.8 High Availability Option
4.9 Visual Tools
4.10 Protocols Supported
4.11 Requirements for the Ingres C# Demonstration Application
4.12 ODBC Data Source Administrator on 64-bit Windows
5.0 General Considerations
5.1 Protocol tcp_ip Replaces wintcp
5.2 High Availability Option for Windows Clustering
5.3 Performance Enhancements in Ingres on Windows
5.4 TCP_NODELAY Option for Ingres Protocol tcp_ip on Windows
5.5 Community Tools
This readme contains information specific to Ingres running on Windows platforms.
The following operating systems are supported (as of the publishing of this document):
Both 32- and 64-bit versions of the above operating systems are supported.
The Ingres product support life cycle policy determines the duration of support for Ingres on these operating systems unless the operating system's manufacturer drops support on a prior date. For the latest information about supported operating systems, visit http://www.ingres.com/support.
Ingres supports the following preprocessors and compilers:
Disk space requirements for Windows are as follows:
System Configuration | Space Required |
---|---|
Client Only (Ingres Net) Install | 125 MB |
DBMS Server with Ingres Net Install | 410 MB |
Full installation plus documentation | 470 MB |
The Ingres installer on Windows is based upon the Microsoft Windows Installer. For more information, please refer to the Ingres for Windows Quick Start Guide.
The Ingres server install can now be installed as any Administrator who has the “Act as Part of the Operating System” Operating System privilege. This person then becomes the “owner” of the Ingres instance, replacing the historical “ingres” user.
There have been some changes to the names of Ingres binary files from previous versions of Ingres. These are mostly DLL names to match more closely with Linux and UNIX naming conventions; for example, OICLFNT.DLL and OIGLFNT.DLL have been combined into IILIBCOMPAT.DLL. Also, upgradef.exe is now shipped as upgradefe.exe, oiapi.lib has become iilibapi.lib, and ingres.lib has become libingres.lib. These are the most notable changes.
Ingres enables the installation of multiple copies of Ingres on a single Windows machine. Each Ingres instance is identified by a unique installation identifier (II_INSTALLATION). This installation identifier is included in the program group name and the service name, to avoid confusion. We strongly recommend that you start Ingres programs from the Windows Start Menu so that you can clearly identify which installation a given program belongs to.
When working in a Windows Command Prompt environment, you must ensure that the value of II_SYSTEM is set correctly for that environment, and that the search, include, and lib paths list the Ingres directories in the desired order. For convenience, a shortcut to a proper Windows Command Prompt will be installed.
When Ingres is started as a Windows service, users other than the instance owner will be able to execute certain DBA commands. This list of DBA commands are as follows: ALTERDB, AUDITDB, CKPDB, FASTLOAD, INFODB, LOCKSTAT, LOGDUMP, LOGSTAT, RCPCONFIG, RCPSTAT, RELOCATEDB, ROLLFORWARDDB, UPGRADEDB, and VERIFYDB.
Note: If Ingres is started as a service as a local system account, the Interactive Performance Monitor can only be started by the local system account user and will not work under any other user, including the user that executed “ingstart -service.”
Note: If you do not check the box labeled “Start Ingres Service Automatically At System Startup” on the Ingres Configuration dialog box during the install, the Ingres service will be installed with no password set for its logon credentials. You must properly set the password for the Ingres service before using it.
Warning! Selecting the option to configure Ingres as a service will save user credentials into the response file in clear text. Specifying a standard or well known password for service credentials is not recommended. Use a placeholder password that is manually changed after the batch installation has completed.
Ingres should be started as a service on Windows Vista and Windows 2008.
Ingres will work with UAC either ON or OFF as determined by site requirements.
To install the High Availability Option for Windows, you must provide the appropriate information in the Ingres for Windows setup wizard.
Ingres on Windows is capable of operating as both a client and server for the Visual DBA tools.
Note: Versions of Visual DBA prior to Ingres 2006 require a patch to work against this release of Ingres.
Ingres supports the following network protocols:
Note: The new protocol driver tcp_ip is recommended over the obsolete wintcp, which is provided for backward compatibility and will be dropped in the future.
The following software is required to run the demonstration application:
The following software is required to compile the application from source:
Note: The demonstration application contains Unicode characters that may not display properly with a default Windows installation. To view the Unicode characters, select “Install files for East Asian languages” from the Regional and Language Options settings in the Windows Control Panel.
On 64-bit Windows, when creating a new data source using the ODBC Data Source Administrator, the Ingres ODBC driver does not appear in the list of drivers on the User DSN or System DSN tab.
The Ingres ODBC driver is a 32-bit driver and appears only in the 32-bit ODBC Data Source Administrator. The ODBC Data Source Administrator shortcut in the Control Panel is a 64-bit shortcut and will bring up 64-bit ODBC Data Source Administrator and only display the 64-bit drivers.
To bring up the 32-bit ODBC Data Source Administrator, which will list the Ingres ODBC driver, run c:\windows\SysWow64\odbcad32.exe.
The “wintcp” protocol is a deprecated feature and will be removed in a future release of Ingres. Its functionality is superseded by the Ingres Net protocol "tcp_ip". The tcp_ip provides improved performance, stability, and IPv6 support. Protocol tcp_ip is completely interoperable with wintcp and with all Ingres TCP/IP implementations on other platforms and releases.
Switching to tcp_ip involves modifying vnode definitions and optionally Ingres Net protocol configuration (status and port). For details, see the Connectivity Guide.
Using parallel accessed SCSI disks as cluster storage, while supported on Windows Server 2003, should not be used on Windows Server 2008. Make sure you have a NAS, SAN, or iSCSI storage solution before upgrading your Windows Server 2003 Failover Cluster to Windows Server 2008.
If you use an iSCSI attached storage device, problems can occur with the disk arbitration during Ingres installation. Restarting the cluster service should solve them, in most cases.
For example, if Ingres installation fails during creation of the log file or the system databases, restart the cluster service by running net stop clussvc and net start clussvc.
Do not start multiple nodes at the same time. There should be a 30 second delay between the startup of each node. (See http://support.microsoft.com/kb/249194/en-us.)
Ingres performance on Windows is significantly improved in this release. While most of the improvements are automatic, some tuning options are added to the “tcp_ip” network protocol driver that may provide additional improvements in the following environments: JDBC or .Net applications, Ingres Net, or Ingres Bridge. The current defaults work well in most cases, although Option #3 below (setting winsock2_concurrent_threads to zero) has provided the best overall performance in some cases—particularly on machines with few processors.
These configuration settings are not available in the CBF or VCBF configuration utilities, but can be modified as follows:
iisetres –v ii.%computername%.gcX.*.configparm value
where
While the above configuration parameters can be used in various combinations, there are four basic options, summarized in the following chart:
ii.machine.gcX.*.winsock2_recv_buffer_size | |
(for 1-read recv) (for 2-read recv) unset or >0 0 |
|
ii.machine.gcX.*.winsock2_concurrent_threads | |
(for IO Completion Port) unset or >0 | #1 #2 |
(for Alertable IO) 0 | #3 #4 |
Option #1 is the default. Option #3, which uses AIO and 1-read receives, has demonstrated the best overall performance in some environments. The other options will likely show a negligible performance difference in most environments.
Network response time through Ingres Net, DAS, or the Bridge on Windows can be improved in some environments by enabling TCP/IP socket option TCP_NODELAY. This is configured in Ingres as follows:
ingsetenv II_WINSOCK2_NODELAY ON # for all gcX servers
or
iisetres ii.hostname.gcX.*.winsock2_nodelay on # for specific gcX server
where
The default is off (not enabled). This only affects Ingres protocol tcp_ip on Windows; for UNIX and Linux, TCP_NODELAY is used automatically when appropriate.
A number of community development and administration tools are available for Windows for download from esd.ingres.com. These include: