EXP Computer ThinConnect4 Betriebsanweisung PDF herunterladen (Seite 96)

To be able to start and stop Oracle JDBC for Rdb servers using Oracle SQL/Services, a

dispatcher with protocol JDBC must be defined using the Oracle SQL/Services management

console.

You must provide the new dispatcher with a unique name and network_port. It is important

to ensure that the use of the POR_ID is unique as the port provided will be used by the

associated Oracle JDBC for Rdb server and only one server at a time may listen on a single

TCPIP port.

CREATE DISPATCHER <dispatcher name> NETWORK_PORT TCPIP PORT_ID <port>

PROTOCOL JDBC;

Where:

<dispatcher name> is a unique name for this dispatcher instance

Example

$ MCR SQLSRV_MANAGE71

SQLSRV> CONNECT SERVER;

The existing version of the Oracle SQL/Services Management GUI does not recognize

dispatchers of the type JDBC.

This means that you will no longer be able to use the GUI once a JDBC dispatcher has been

defined.

Format

<port> is the port number the associated server will listen on

SQLSRV> CREATE DISPATCHER JDBC_DISP NETWORK_PORT TCPIP PORT_ID 1880

PROTOCOL JDBC;

SQLSRV> SHOW DISPATCHER;

Dispatcher JDBC_DISP

State: UNKNOWN

Autostart: on

Max connects: 100 clients

Idle User Timeout: <none>

Max client buffer size: 5000 bytes

Network Ports: (State) (Protocol)

TCP/IP port 1880 Unknown JDBC clients

Log path: SYS$MANAGER:

Dump path: SYS$MANAGER:

Caution:

7.1.2 Associating an Oracle SQL/Services JDBC Dispatcher to a Server

1 2 ... 91 92 93 94 95 96 97 98 99 100 101 ... 162 163

Keine Kommentare

EXP Computer ThinConnect4 Betriebsanweisung Seite 96