From Ingres Community Wiki

Ingres supports different network protocols, the most common one being good old TCP/IP. Sys admins often want to know what ports Ingres is/will use on a machine for all sorts of reasons; traffic shaping, firewalls, etcs.

Ingres clients will use a random socket allocated by the OS.

Ingres server processes such as the DBMS will use a random socket allocated by the OS.

The Ingres Name Server processes will use a random socket allocated by the OS but this port number is published in the Ingres Symbol Table under the variable II_GCNxx_PORT where xx is the Ingres Installation ID.

Ingres server processes that need to communicate across the network such as the [Ingres Communication Server] use a user supplied port as does the Ingres Data Access Server. The port used is controlled via CBF or VCBF and can either specified as a numeric port number or based on an Ingres Installation ID (which then of course gets hashed into a numeric port number).

You can determine the hashed number (or reverse map the hashed number to the symbolic value) using the attached C program listen2port.c.

Default GCC listen address/port:

# listen2port II
II maps to socket 21064

# listen2port -r 21064
socket 21064 maps to II

Default DAS (and the older JDBC) listen address/port:

# listen2port II7
II7 maps to socket 21071

# listen2port -r 21071
socket 21071 maps to II7