Warehouse Release 3.00.4500
11/19/2004
The enhancement in the 3.00.4500 release are:
- Network connections now have keep alive (SO_KEEPALIVE) set.
This should help keep DataBridger Studio sessions active over a long period of time. In prior release DataBridger Studio sessions left inactive over a long period of time (such as overnight) would stop working.
- On Windows systems, the Warehouse server may now be directed to listen to a specific port by indicating the port number in the service name when installing the service with INSTSRV. The default Warehouse port is 1610 and is installed using something like:
INSTSRV Warehouse "C:\Program Files\Taurus\Warehouse\WhStart.exe"
To indicate a specific port number, append _p#### to the service name, where #### is the port number you wish to use. For example, if you wished to use port 11610, you would install the Warehouse service as follows:
INSTSRV Warehouse_p11610 "C:\Program Files\Taurus\Warehouse\WhStart.exe"
Port numbers are controlled by the Internet Assigned Numbers Authority. See:
http://www.iana.org/assignments/port-numbers
NOTE: This applies on to Microsoft Windows based systems. On other systems, the Warehouse server may be run with the -port ### parameter to specify a port. For example, on Unix : nohup /usr/local/Taurus/whii/whserv port 20001 &
- For Warehouse servers, the listen() backlog has been changed to 20 from 1. In earlier releases, this may have prevented Warehouse server connections opened at the same instant.
- The data type passed to Oracle when an ORACLE TIMESTAMP is in the FOR condition is now passed as a timestamp. In prior releases the value was converted to a date before being passed to Oracle. This could cause incorrect rows being selected.
Release 3.00.4500 is available now on all supported platforms.