EXP Computer ThinConnect4 Uživatelská příručka stáhnout pdf (Strana 102)

$ DEFINE/SYSTEM RDB$JDBC_SQSTYPE_1888 MP

$ MCR SQLSRV_MANAGE71

SQLSRV> CONNECT SERVER;

SQLSRV> CREATE DISPATCHER JDBC_DISP NETWORK_PORT TCPIP PORT_ID 1888

PROTOCOL JDBC;

This will create a server with type

RdbThinSrvMP.

7.1.3 Starting a JDBC Dispatcher

Once you have defined a JDBC dispatcher, it can be started like any other Oracle SQL/Services

dispatcher:

Example

SQLSRV> start dispatcher jdbc_disp;

SQLSRV> show disp jdbc_disp;

Dispatcher JDBC_DISP

State: STARTING

Autostart: on

Max connects: 100 clients

Idle User Timeout: <none>

Max client buffer size: 5000 bytes

Network Ports: (State) (Protocol)

TCP/IP port 1880 Inactive JDBC clients

Log path: SYS$MANAGER:

Dump path: SYS$MANAGER:

SQLSRV> show disp jdbc_disp;

Dispatcher JDBC_DISP

State: RUNNING

Autostart: on

Max connects: 100 clients

Idle User Timeout: <none>

Max client buffer size: 5000 bytes

Network Ports: (State) (Protocol)

TCP/IP port 1880 Inactive JDBC clients

Log path: SYS$MANAGER:

Dump path: SYS$MANAGER:

Log File: SYS$SYSROOT:[SYSMGR]SQS_DECRDB_JDBC_DISP06O71.LOG;

Dump File: SYS$SYSROOT:[SYSMGR]SQS_DECRDB_JDBC_DISP06O.DMP;

The Oracle SQL/Services monitor will attempt to start the server associated this dispatcher and

create a log of the dispatcher events in the SYS$MANAGER directory in a log file named:

SYS$MANAGER:SQS_<nodename>_JDBC_DISP<nnnnn>.LOG

The <nodename> depends on the node the dispatcher is started up on.

The <nnnnn> is the unique id given to this dispatcher instance by Oracle SQL/Services

102

1 2 ... 97 98 99 100 101 102 103 104 105 106 107 ... 162 163

Žádné komentáře

EXP Computer ThinConnect4 Uživatelská příručka Strana 102