Oracle FAQ Your Portal to the Oracle Knowledge Grid

Home -> Community -> Mailing Lists -> Oracle-L -> (Fwd) Oracle tips [Netware/NDS]

(Fwd) Oracle tips [Netware/NDS]

From: Eric D. Pierce <>
Date: Tue, 20 Jun 2000 11:45:26 -0700
Message-Id: <>

Hi everyone,

It seems quite a few would like my tips on Oracle, so here they are:

First of all: Oracle on Netware runs fine without any NDS integration. So do that for a start: install Oracle - and make sure it works. The important test is to install the server and a client, and make sure the client can connect to the server. The best test is to use SQL Plus to connect and browse a little around, however, Net8 Easy Config will allow you to setup a connection and test it directly.

Next, you need to be able to load the NWAdmin Oracle snapin. This is no fun, it took me a long time. There's some old versions around, and the setup is not obvious. So:

You'll need three files: nwora80.dll, zna80us.dll, and zna80us.hlp. With NWAdmin32, nwora80 must be in sys:public\win32\snapins, and the two zna80us files in sys:public\win32 - or whatever path you have to your NWA.

The versions that works for me are:

nwora80.dll	Feb. 16, 1998
zna80us.dll	Oct. 3, 1996
zna80us.hlp	Sep. 27, 1996

The final thing to be aware of is that you must have Oracle's client software installed and working for the snapin to load. In other words: If you copy the snapin to your server, be prepared to have a load error from the snapin every time you run NWA on a machine without the Oracle client installed.

Oracle/NDS integration is not one, but _two_ things! Takes a while to figure out...

As if we didn't have enough name services around, Oracle has invented their own. It's called TNS. There's nothing magic about it, it's just yet another name service. Configuring it, though, requires quite a few steps.

The Oracle client must be able to lookup the server in some way; you'd think you could just supply the IP and of you go, but this is not the case. On the contrary, you must supply a name that can be resolved in some way.

For the client, this is configured in the file sqlnet.ora, which can be found in the subdir net80\admin under the base directory. This file has a line like

NAMES.DIRECTORY_PATH=3D (NOVELL, TNSNAMES, HOSTNAME) which means: Use NDS first, then TNS, then DNS. Hostname is the usual mix of a hostfile and DNS, TNS is Oracle's native system, and Novell is, you guessed it, NDS. TNS is just a 'host' file like the one known from IP, however, it's pretty complex and easiest setup using Net80 Easy Config. It's physical location is net80\admin\tnsnames.ora (still under the client base directory). It can be distributed like a host file.

TNS uses a DNS like naming system - with a default 'domain' of '.world'. This means that if you create a database reference called 'myserver', it's real name will be '', but as '.world' is default, you can connect to it using the name 'myserver' as well as the name ''. If you can't, you have a basic problem with you setup that has nothing to do with NDS.

Whilst I'm going into details about TNS, you really don't want to use it. The charm of NDS integration is, among other things, that you won't need it - the Oracle client can lookup the nescessary details directly in NDS. You'll only need it for the initial connect before you have NDS integration running.

Asuming you can now connect without NDS, lets start the fun:

Using NWAdmin, you should now create an NDS object for your database instance. Open NWAdmin, and create an 'Oracle Instance' object. You'll have to answer a few basic questions, with the host NW server beeing one of the most important. When you've created you object, you're done for now. It _won't_ work at the moment - if you go into the tab named 'Connect Address', the fiels 'NDS Naming Adapter Connection Information' is empty.

If you want a little testing at this stage, though, you can fill in the edit box called 'Service Name' with a valid TNS name known to work. Save this, reopen your object, and you should be able to test the connection using the status button found on the 'Identification' tab. After a little while, it should say 'Available, Running'.

But now you should stop your Oracle server (not Netware) and restart it. The Oracle software will find the database object, you've created in NDS, and fill in the NDS naming adapter information. Verify this by going to the 'Connect Address' tab. Set a check mark next to 'Enable NDS Naming', and you're almost through.

Close the object (saving your changes) and reopen it, you should now be able to get the status of the server without using TNS names at all.

NDS works now, but you still have to tell your client software to use NDS. You do this by editing the sqlnet.ora file mentioned above to include NOVELL in the statement below:

NAMES.DIRECTORY_PATH=3D (NOVELL, TNSNAMES, HOSTNAME) Received on Tue Jun 20 2000 - 13:45:26 CDT

Original text of this message