User guide

8.24 File and Directory access Requirements
• RDB$JDBC_HOME
• RDB$JDBC_COM
• RDB$JDBC_LOGS
There are certain file and directory access requirements that must be met to successfully use
Oracle JDBC for Rdb servers, drivers and the controller.
The controller and servers require access to the directories pointed to by the following logical
names
During installation a command procedure will be created for you that you can use to set up
these logical names for your system pointing to the installation directory. It is your decision
whether to add these logical names to your startup command procedure or require some other
mechanism such as a login setup command procedure to set these up for JDBC users.
The logical names may be placed in any of your logical name tables, the normal OpenVMS
logical translation precedence will be followed when any of the JDBC components try to
access files using these logical names. This allows you to have system-wide, group level or
private copies of the JDBC kits each using their own set of directories.
It is important that the appropriate access be granted to users that require to startup servers or
use the JDBC jar files.
During installation the three directories will be created under the installation directory, and
be given the following protection.
(S:RWE, O:RWE, G:RE, W:RE)
This allows the world read/execute access to all the directories and contents. If this does not
comply with your organizational requirements then you should alter these protections
appropriately.
Users of the controller, or those that startup servers manually will also require WRITE access
to both the RDB$JDBC_COM and RDB$JDBC_LOGS directory to successfully startup
servers, as the server process needs to be able to write log and temporary files to these
directories.
If a server is started up using the SQL/Services JDBC dispatcher then the account under
which the dispatcher runs needs WRITE access to these directories.
If you redirect these logical names to other directories you must ensure that the file and
directory protections comply with the above requirements.
139