User guide

correctly specified thus details of the appropriate command procedures will be provided
below.
-RDMS-F-ROOTMAJVER, database format 71.0 is not compatible with
software version 72.1:S1000
Step 1 Install Oracle JDBC for Rdb
The Oracle JDBC for Rdb Release Notes describe the steps required to install Oracle
JDBC for Rdb. These steps should be followed to install the product on the OpenVMS
node that will be used as server for you Oracle Rdb database.
The server machine requires JAVA to be installed prior to installing the Oracle JDBC for
Rdb kit.
Once you have installed the kit you must set up your system so that it can use the JDBC
kit. Several configuration files may have to be created or altered. Details of these steps
follow.
Step 2 Decide on the versions of Rdb and JAVA
The Oracle JDBC for Rdb Release Notes will tell you the minimum versions of Rdb and
JAVA supported by Oracle JDBC for Rdb. You may however have several versions of
both Rdb and JAVA on your server that meet the minimum requirements. When the thin
servers run they will need to have the environment they are running within set up so that
the correct version of Rdb and JAVA will be used depending on your organization
requirements, and which Oracle Rdb databases you wish the thin servers to access.
If you do have multiple versions of Rdb on your system, it is important that the server
runs within the correct version of Rdb for the databases it will access. The Rdb
environment is set up at the process level and cannot be changed for that server while the
server is actually running. This means that a single running instance of a thin server may
only be able to access databases for a single Rdb version.
If you try to connect to a database that does not match the version of Rdb you have set up
for the thin server execution instance you will get an exception similar to:
SQLException: Failed to connect : in <rdbjdbcsrv:connect failure>
%RDB-F-WRONG_ODS, the on-disk structure of the database file is not
supported by this version
You may have different version of JAVA on your system as well. In addition you can
choose different JAVA VMs to run under. The VM version and type must be decided for
a single thin server instances as once JAVA has been invoked and the server is running it
cannot be changed for that server instance.
144