User guide

Caution:
Do not use the SET VERIFY command within these command procedures. As the method
Runtime.exec() may be used by the servers to create processes, the use of the SET VERIFY
command within the command procedure may hang the server. This is a documented
limitation of using Runtime.exec() on Open VMS Java. The logical name
JAVA$EXEC_TRACE is available to help debug Runtime.exec() calls on OpenVMS. Refer
to the OpenVMS Java documentation for more details.
The
srv.execStartup and srv.onExecStartCmd options are only valid within the XML-
Formatted configuration file server section for a multi-process server.
Contents
8.19 Server/Client Protocol Checking
To ensure that the protocol between the Oracle JDBC for Rdb thin driver and servers
correctly align, the Oracle JDBC for Rdb servers check versioning information transmitted
by the client. This allows the quick trapping of problems that may occur because of a
mismatch between the server instance and the thin driver.
Example
The following is an example of the type of error message that will be seen if the client and
server mismatch:
oracle.rdb.jdbc.common.RdbException: Io exception :
Io exception : Server Protocol error : received 1 : expected 2
@rdb.Client.FetchBlobSeg
To prevent these protocol errors, all the Oracle JDBC for Rdb driver JAR files should be
replaced at the same time whenever a new kit is installed.
To check that the server/clients instances match enable @tracelevel=-1 on the connection
URL for your client application. See Trace
for more details.
Near the start of the log there will be messages indicating the instance values for both the
client and the server. If these two numbers do not match then protocol errors are likely.
An example of the log messages showing Instance information:
>> main [e-mail] msg : Rdb nativeInstance=20030508
>> main [e-mail] msg : Rdb serverInstance=20030508
Contents
8.20 Using OpenVMS FailSAFE IP.
132