Connectivity protocols
The connectivity protocols that you can use to connect client products to the database server depend on the operating system.
The following table uses these abbreviations for protocol names:
- BSTP - Berkeley sockets using TCP/IP
- IPSP - IPC using stream pipe
- IPSM - IPC using shared memory
- IPNM - IPC using a named pipe
- TLTP - TLI using TCP/IP
- TLIX - TLI using IPX/SPX
| Platform/OS | BSTP | IPSP | IPSM | IPNM | TLTP |
|---|---|---|---|---|---|
| AIX | onsoctcp drsoctcp |
onipcstr | onipcshm | ||
| HP Itanium™ 64 | onsoctcp drsoctcp |
onipcstr | onipcshm | ||
| HPUX | onsoctcp drsoctcp |
onipcstr | onipcshm | ||
| Linux™ 32-bit | onsoctcp drsoctcp |
onipcstr | onipcshm | ||
| Linux AMD 64 | onsoctcp drsoctcp |
onipcstr | onipcshm | ||
| Linux Power | onsoctcp drsoctcp |
onipcstr | onipcshm | ||
| Linux Power Little Endian | onsoctcp drsoctcp |
onipcstr | onipcshm | ||
| Linux zSeries | onsoctcp drsoctcp |
onipcstr | onipcshm | ||
| Linux ARM | onsoctcp drsoctcp |
onipcstr | onipcshm | ||
| Solaris | onsoctcp drsoctcp |
onipcstr | onipcshm | ontlitcp | |
| Windows | onsoctcp drsoctcp |
onipcnmp |
Notes:
- If you are using 64-bit servers: Remote 32-bit applications/tools (example: ESQL/C) can only connect to HCL OneDB™ using the TCP/IP protocol. Local 32-bit applications/tools can connect to the 64-bit server using either TCP/IP protocols or IPC stream pipe protocols. Local 32-bit applications/tools cannot connect to the 64-bit server using IPC shared memory protocol.
- If you are using a NUMA system and have several IP addresses configured
on the same physical interface: The HCL OneDB TCP
listener thread binds to a particular IP address/port. It listens
for incoming calls addressed to only one IP address. If there are
multiple IP addresses configured on the system, a TLI client is not
able to connect to the server. (If DNS is configured to resolve the
host name on a rotary of the four IP addresses, you do not know which
of those addresses has been selected by the HCL OneDB TCP
listener). The solution is that in the
$ONEDB_HOME/etc/sqlhostsfile, use "*hostname" instead of "hostname". It will make the HCL OneDB TCP listener bind to INADDR_ANY instead of a particular address. - For additional information, see the HCL OneDB machine notes.