User guide

ubcode

Description

disk or directory is write protected , check the

disk/directory pointed to by rdb$jdbc_com

65530

process terminated prematurely

65531

problem reading termination mailbox

65532

problem during call to CREPRC

65533

problem getting information about termination

mailbox

65534

problem creating termination mailbox

Note:

It is important that the server process has appropriate access rights to the directories specified

by JDBC$RDB_HOME, RDB$JDBC_COM and RDB$JDBC_LOGS logical names, see File

and Directory access Requirements for more details.

Contents

3.3 Oracle JDBC for Rdb Pool Server

The Oracle JDBC for Rdb pool server is a server-side component that accepts connection

requests from the thin driver and redirects the requests to the next available Oracle JDBC

for Rdb server for processing,

Using the pool server you can designate a single Port ID that can be used by your client

side applications to connect to the next available server. The pool server selects the next

available server from a table of candidate servers in a round-robin fashion.

Once the connection request has been redirected, the thin driver and the designated server

communicate directly with each other.

A pool server is installed and invoked on each node from which you wish to direct the

access to Oracle JDBC for Rdb servers. Oracle Rdb need not be present on these nodes as

the pool server does not communicate directly with Oracle Rdb. The pool server and its

pooled servers do not need to be on the same node.

The pool server communicates with the thin driver using Java sockets over TCP/IP with the

default Port ID 1702.

Note:

The thin pool server carries out server pooling NOT connection pooling. Connections are

created in each connection request and are not reusable.