DAL: How to Access Database on Remote VAX

We have some VAX systems running VAX/VMS. What logical names are required for DAL on one VAX to access an ORACLE RDBMS on the other VAX? We were able to run SQLPlus, but we've customized it so the access required a few logical names.
If the VAX systems are part of a VAXcluster, you must connect to a node that is running the DAL Server and AppleTalk for VMS. If the DAL Server and AppleTalk for VMS has been licensed for each node on the VAXcluster, then you may access a shared database via DAL from any node running the DAL Server and AppleTalk for VMS.

If the VAX systems aren't part of a VAXcluster, you still can access the remote database, if the database is set up for remote access. ORACLE, Ingres, and Sybase all have mechanisms to support remote database access.

For example, if you have the DAL Server and AppleTalk for VMS installed on VAX A and the ORACLE database installed on VAX B, you can allow users on VAX A to access the database on VAX B in this way:

1) Select either the Async Driver, the DECnet Driver, or the TCP Driver for SQL*Net during ORACLE installation.

2) Create a database link for each database. This database link contains enough information to uniquely identify a path to the remote database. It normally contains the following information:

- Network protocol
- Nodename
- Dbname
- Username/password
- Protocol options

If the users on VAX A can access the database on VAX B, then the DAL Server has access, too. The database application handles the Async, DECnet or, TCP/IP communications between VAX A and VAX B, not DAL.
Published Date: Feb 18, 2012