TCP/IP Port Utilization by TimesTen (Doc ID 1295539.1)

Last updated on SEPTEMBER 23, 2016

Applies to:

Oracle TimesTen In-Memory Database - Version 11.2.1 to 11.2.1 [Release 11.2]
Information in this document applies to any platform.
***Checked for relevance on 11-Sep-2012***
This Note is of interest to TimesTen DBAs and developers as well as system security specialists concerned with network security.


Goal

All processes spawned by TimesTen acquire TCP/IP ports for purposes of interprocess communication and synchronization. This is true for data store subdaemons, the cache agent, replication subdaemon, and for the primary instance daemon, instance server, and TimesTen clusterware agent. Direct connections (which attach directly to the data store shared memory segment)  acquire a port in order to communicate with the main daemon.  Client connections communicate to the server.  Configuring a daemon port is mandatory.  All other port configuration depends on if those features are utilized.

The instance daemon port is defined at instance installation time and is configurable via the ttmodinstall utility.

The replication port can be set to a static port by the PORT attribute of the replication scheme.  If no PORT is specified it will use a dynamic port.

The server port can be configured at installation time or can be viewed or modified in the ttendaemon.options file in the daemon home directory.  Change the port number after "-server ".

The TimesTen clusterware agent can be configured at installation time.  If clusterware for TimesTen was not installed originally, then user must use the ttmodinstall utility to add clusterware for TimesTen.  The port for TimesTen clusterware agent can be viewed or modified in the ttcrsagent.options file in the daemon home directory.  Change the port number after "-port ".

All other TCP/IP port assignments to TimesTen processes are completely random and based on the availability of ports at the time when the process is spawned. Customers with high network security concerns can restrict TCP/IP port availability without affecting TimesTen operations, as long as an adequate number of ports are available to accommodate all spawned TCP/IP processes.

 

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms