[Oracle-l] Solution to 100's of Oracle clients installed with Net8 and local tnsnames.ora, sqlnet.ora

Comments in line
On Wed, 15 Sep 2004 10:56:22 -0400, paula_stankus_at_doh.state.fl.us
wrote:
I asked a very similar question a while back, before I start with
where I got to I'm going to make a wild assumption since you refer to
AD that you mean windows clients.

First of all I discovered that Directory naming for 9i using Windows
2003 Active Directory naming is broken. It supposedly works if you
install a 10g client to create the Oracle Naming context. Once you've
done that 9i clients can use the Oracle context correctly. However in
the course of the conversation with the support analyst - who
certainly knew a shedload more about ldap, directories and naming than
I do - it became somewhat apparent to me that really if we went down
the directory naming route it would probably be better to just go with
OID (which I think answers one of your above questions).

As far as 9.2 goes the relevant tar extract reads

Niall,

There are currently unresolved problem in NetCA 92. The recommended
workaround is to use 10g NetCA to create t
he context. After that you should be able to manage the context with 92 tools l
ike NetMgr. If you do not have a local install of 10g you can download teh clie
nt install from OTN.

See Note.273440.1 NETca Unable to Create Oracle Schema in Active Directory

As far as cost goes then you get a limited license for OID FAC with
the database for naming purposes only, so the answer to what does it
cost depends on whether you want to do any more with it than replace
tnsnames.ora

However once I'd got this far, it did seem appropriate to wonder if it
might not be better just to set TNS_ADMIN to a central location and
just have the one copy.

I'm fearing file locking issues with this approach. Multi-platform is =
another issue, although a SAMBA/NFS combo on the "central location" =
should take care of that.

Or are my fears unfounded? We're in the same boat, wondering what to do =
about replacing the functionality of our replicated ONAMES servers for =
the future. OiD 9.0.1 was not mature/stable enough to be production. =
We haven't tested future versions and I don't plan to until the damnable =
thing is at least free (i.e. included with our EE license).

Rich

Paula, Niall, Rich,

If you are using Windows based clients and Windows based network
authentication you may want to consider using the Microsoft Distributed
File System technology (DFS) in tandem with the Oracle TNS_ADMIN
environment variable. With this method, the Oracle client networking
files (tnsnames.ora, sqlnet.ora,..etc.) are stored on one file server (
the root of the Distributed File System ) and replicated automatically
to other servers defined to the DFS. At network authentication, the
customer receives the TNS_ADMIN environment variable with a UNC path to
the DFS domain. DFS locates the nearest server for each customer and
delivers the Oracle client files to him or her (upon request). If the
assigned DFS server becomes inaccessible due to network, hardware, or
other issues, the DFS will automatically roll the customer to the next
available DFS server in the list. We are currently doing this with over
700 clients (Windows XP Professional) without an issue. When I make a
change to tnsnames on DFS root, the change is reflected on every
connected client within one minute with no file locking issues.
prerequisites include Windows 2000 Server at a minimum (Windows 2003
Server is preferred) and a savvy Windows SA.

Here are several URL's from the Microsoft web site if you are still
interested:

Simplifying Infrastructure Complexity with Windows Distributed File
System
This document introduces you to the many improvements to Distributed
File System (DFS) that help administrators manage their distributed
resources in all the editions of Windows Server 2003.
http://www.microsoft.com/windowsserver2003/techinfo/overview/dfs.mspx
Distributed File System: Simplifying Complexity
In this demo, you'll learn about DFS, a strategic storage management
solution that helps you manage distributed resources more easily.
http://www.microsoft.com/windowsserver2003/evaluation/demos/dfs.html
Distributed File System: Frequently Asked Questions
This article contains frequently asked questions and answers about the
Distributed File System (DFS) for the Windows Server 2003 family.
http://www.microsoft.com/windowsserver2003/techinfo/overview/dfsfaq.mspx

Distributed File System White paper
This white paper describes the Microsoft distributed file system
technology, including the version for Microsoft Windows 2000 operating
system.
http://www.microsoft.com/windows2000/techinfo/howitworks/fileandprint/dfsnew.asp

Distributed File System (DFS): Best Practices and Troubleshooting
Guide
This guide is designed for administrators to supplement existing
Distributed File System (DFS) documentation. It contains important
information about DFS that has not been adequately addressed in other
places.
http://www.microsoft.com/windows2000/techinfo/administration/fileandprint/dfsbp.asp

812487 - Overview of DFS in Windows 2000
This article describes the Microsoft Distributed File System (DFS) in
Windows 2000 and provides information about how to administer DFS.
http://support.microsoft.com/default.aspx?scid=kb;en-us;812487
Designing and Deploying File Servers
Visit Microsoft TechNet for detailed information on designing a DFS
Namespace and FRS replication, which can be found in the Planning Server
Deployments guide.
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/SDCCC_FSV_OVERVIEW.asp

Good Luck!

Chris

Chris Welton
Database Administrator
System Services Unit
Department of Information Technology
New York State Thruway Authority
200 Southern Blvd
Albany, NY 12209-2098
Phone: (518) 436-3105
Chris_Welton_at_thruway.state.ny.us
I'm fearing file locking issues with this approach. Multi-platform is
=
another issue, although a SAMBA/NFS combo on the "central location" =
should take care of that.

Or are my fears unfounded? We're in the same boat, wondering what to
do =
about replacing the functionality of our replicated ONAMES servers for
=
the future. OiD 9.0.1 was not mature/stable enough to be production.
=
We haven't tested future versions and I don't plan to until the
damnable =
thing is at least free (i.e. included with our EE license).

Rich

Wouldn't OID assist here?
greg

-----Original Message-----
From: Chris Welton
Sent: Wednesday, September 15, 2004 2:25 PM
To: Rich.Jesse_at_quadtechworld.com
Cc: oracle-l_at_freelists.org
Subject: RE: Solution to 100's of Oracle clients installed with Net8 and
local tnsnames.ora, sqlnet.ora

Paula, Niall, Rich,

If you are using Windows based clients and Windows based network
authentication you may want to consider using the Microsoft Distributed
File System technology (DFS) in tandem with the Oracle TNS_ADMIN
environment variable. With this method, the Oracle client networking
files (tnsnames.ora, sqlnet.ora,..etc.) are stored on one file server (
the root of the Distributed File System ) and replicated automatically
to other servers defined to the DFS. At network authentication, the
customer receives the TNS_ADMIN environment variable with a UNC path to
the DFS domain. DFS locates the nearest server for each customer and
delivers the Oracle client files to him or her (upon request). If the
assigned DFS server becomes inaccessible due to network, hardware, or
other issues, the DFS will automatically roll the customer to the next
available DFS server in the list. We are currently doing this with over
700 clients (Windows XP Professional) without an issue. When I make a
change to tnsnames on DFS root, the change is reflected on every
connected client within one minute with no file locking issues.
prerequisites include Windows 2000 Server at a minimum (Windows 2003
Server is preferred) and a savvy Windows SA.

Here are several URL's from the Microsoft web site if you are still
interested:

Simplifying Infrastructure Complexity with Windows Distributed File
System
This document introduces you to the many improvements to Distributed
File System (DFS) that help administrators manage their distributed
resources in all the editions of Windows Server 2003.
http://www.microsoft.com/windowsserver2003/techinfo/overview/dfs.mspx
Distributed File System: Simplifying Complexity
In this demo, you'll learn about DFS, a strategic storage management
solution that helps you manage distributed resources more easily.
http://www.microsoft.com/windowsserver2003/evaluation/demos/dfs.html
Distributed File System: Frequently Asked Questions
This article contains frequently asked questions and answers about the
Distributed File System (DFS) for the Windows Server 2003 family.
http://www.microsoft.com/windowsserver2003/techinfo/overview/dfsfaq.mspx

Distributed File System White paper
This white paper describes the Microsoft distributed file system
technology, including the version for Microsoft Windows 2000 operating
system.
http://www.microsoft.com/windows2000/techinfo/howitworks/fileandprint/dfsnew
.asp

Distributed File System (DFS): Best Practices and Troubleshooting
Guide
This guide is designed for administrators to supplement existing
Distributed File System (DFS) documentation. It contains important
information about DFS that has not been adequately addressed in other
places.
http://www.microsoft.com/windows2000/techinfo/administration/fileandprint/df
sbp.asp

812487 - Overview of DFS in Windows 2000
This article describes the Microsoft Distributed File System (DFS) in
Windows 2000 and provides information about how to administer DFS.
http://support.microsoft.com/default.aspx?scid=kb;en-us;812487
Designing and Deploying File Servers
Visit Microsoft TechNet for detailed information on designing a DFS
Namespace and FRS replication, which can be found in the Planning Server
Deployments guide.
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/SDCCC_FSV_OVERVIEW.asp

Good Luck!

Chris

Chris Welton
Database Administrator
System Services Unit
Department of Information Technology
New York State Thruway Authority
200 Southern Blvd
Albany, NY 12209-2098
Phone: (518) 436-3105
Chris_Welton_at_thruway.state.ny.us
I'm fearing file locking issues with this approach. Multi-platform is
=
another issue, although a SAMBA/NFS combo on the "central location" =
should take care of that.

Or are my fears unfounded? We're in the same boat, wondering what to
do =
about replacing the functionality of our replicated ONAMES servers for
=
the future. OiD 9.0.1 was not mature/stable enough to be production.
=
We haven't tested future versions and I don't plan to until the
damnable =
thing is at least free (i.e. included with our EE license).

Rich

Not a possibility here. Our LDAP infrastructure is developed,
maintained, and controlled by another group that is Microsoft centric.
2:29:46 PM >>>
Wouldn't OID assist here?
greg

-----Original Message-----
From: Chris Welton
Sent: Wednesday, September 15, 2004 2:25 PM
To: Rich.Jesse_at_quadtechworld.com
Cc: oracle-l_at_freelists.org
Subject: RE: Solution to 100's of Oracle clients installed with Net8
and
local tnsnames.ora, sqlnet.ora

Paula, Niall, Rich,

If you are using Windows based clients and Windows based network
authentication you may want to consider using the Microsoft
Distributed
File System technology (DFS) in tandem with the Oracle TNS_ADMIN
environment variable. With this method, the Oracle client networking
files (tnsnames.ora, sqlnet.ora,..etc.) are stored on one file server
(
the root of the Distributed File System ) and replicated automatically
to other servers defined to the DFS. At network authentication, the
customer receives the TNS_ADMIN environment variable with a UNC path
to
the DFS domain. DFS locates the nearest server for each customer and
delivers the Oracle client files to him or her (upon request). If the
assigned DFS server becomes inaccessible due to network, hardware, or
other issues, the DFS will automatically roll the customer to the next
available DFS server in the list. We are currently doing this with
over
700 clients (Windows XP Professional) without an issue. When I make a
change to tnsnames on DFS root, the change is reflected on every
connected client within one minute with no file locking issues.
prerequisites include Windows 2000 Server at a minimum (Windows 2003
Server is preferred) and a savvy Windows SA.

Here are several URL's from the Microsoft web site if you are still
interested:

Simplifying Infrastructure Complexity with Windows Distributed File
System
This document introduces you to the many improvements to Distributed
File System (DFS) that help administrators manage their distributed
resources in all the editions of Windows Server 2003.
http://www.microsoft.com/windowsserver2003/techinfo/overview/dfs.mspx
Distributed File System: Simplifying Complexity
In this demo, you'll learn about DFS, a strategic storage management
solution that helps you manage distributed resources more easily.
http://www.microsoft.com/windowsserver2003/evaluation/demos/dfs.html
Distributed File System: Frequently Asked Questions
This article contains frequently asked questions and answers about the
Distributed File System (DFS) for the Windows Server 2003 family.
http://www.microsoft.com/windowsserver2003/techinfo/overview/dfsfaq.mspx

Distributed File System White paper
This white paper describes the Microsoft distributed file system
technology, including the version for Microsoft Windows 2000 operating
system.
http://www.microsoft.com/windows2000/techinfo/howitworks/fileandprint/dfsnew

.asp

Distributed File System (DFS): Best Practices and Troubleshooting
Guide
This guide is designed for administrators to supplement existing
Distributed File System (DFS) documentation. It contains important
information about DFS that has not been adequately addressed in other
places.
http://www.microsoft.com/windows2000/techinfo/administration/fileandprint/df

sbp.asp

812487 - Overview of DFS in Windows 2000
This article describes the Microsoft Distributed File System (DFS) in
Windows 2000 and provides information about how to administer DFS.
http://support.microsoft.com/default.aspx?scid=kb;en-us;812487
Designing and Deploying File Servers
Visit Microsoft TechNet for detailed information on designing a DFS
Namespace and FRS replication, which can be found in the Planning
Server
Deployments guide.
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy

guide/en-us/SDCCC_FSV_OVERVIEW.asp

Good Luck!

Chris

Chris Welton
Database Administrator
System Services Unit
Department of Information Technology
New York State Thruway Authority
200 Southern Blvd
Albany, NY 12209-2098
Phone: (518) 436-3105
Chris_Welton_at_thruway.state.ny.us
PM
>>>
I'm fearing file locking issues with this approach. Multi-platform is
=
another issue, although a SAMBA/NFS combo on the "central location" =
should take care of that.

Or are my fears unfounded? We're in the same boat, wondering what to
do =
about replacing the functionality of our replicated ONAMES servers for
=
the future. OiD 9.0.1 was not mature/stable enough to be production.
=
We haven't tested future versions and I don't plan to until the
damnable =
thing is at least free (i.e. included with our EE license).

Rich

Yes, we did something very similar with SunOne (formerly iPlanet). The =
problem comes in with all those Support bux that we pay that don't do us =
squat when Oracle Networking takes a dump. Will it happen? I doubt it. =
But I'm not willing to bet my future paychecks on it. We're sticking =
with ONAMES -- for now. Maybe 10g will be (is!) different.

Rich

Chris, I take it that you don't have any Unix servers or =
workstations/desktops?

Rich

As for the OID, it can go in one direction only: for the better.
I believe that OID 9i has hit the bottom and that is impossible to
go the opposite direction. I'm not coming close to
that product until I hear some good references.

I have been running 9i OID on our corporate network for over a year
with no problems.

"Gogala, Mladen" wrote:


Do you Yahoo!?

Rich,
We have a mix of Unix (AIX) and Windows based RDBMS servers and
strictly Windows clients.

Chris
Chris, I take it that you don't have any Unix servers or =
workstations/desktops?

Rich

This (a shared, central TNSNAMES) is exactly what we've done since 7.3.
I've been told that Oracle doesn't support it, but we've never had a
problem. YMMV.

On the client: tns_admin=\\myserver\share_name

where \\myserver\share_name contains tnsnames.ora, sqlnet.ora. Has worked
quite well for us.

Thanks

Ed Stevens
IBM Global Services
- Nissan North America, Smyrna Manufacturing Plant

IBM E-mail: Ed_Stevens_at_us.ibm.com
Nissan E-mail: ed.stevens_at_nmm.nissan-usa.com

voice: 615.355.2988
fax: 615.223.3510
pager: 615-252-0845

After some pain, we recently have managed to make the directory naming
working with Microsoft AD (windows 2k) after opening a TAR.
Some notes:
1. Use 10G client to create Oracle schema and Oracle context in AD.After
the schema
and the context 've been created, you can use 9i client and don't need
10G any more .

2. If your AD login domain is a child domain, then you need to manually
create the ldap.ora file, because netmgr can't create this file
correctly.

in ldap.ora file, you must have these specified:
DIRECTORY_SERVER_TYPE = AD

DEFAULT_ADMIN_CONTEXT="DC=your_company, DC=...."
DIRECTORY_SERVERS=your_root_domain_server_hostname:your_port_no

3. And also make sure the security user setup is correct in the AD side
for you to create entry in the directory.

The pain we have is mainly due to our child domain config.

regards/Yerong

-----Original Message-----
From: Chris Welton
Sent: 16 September 2004 05:08
To: Rich.Jesse_at_quadtechworld.com
Cc: oracle-l_at_freelists.org
Subject: RE: Solution to 100's of Oracle clients installed with
Net8andlocal tnsnames.ora, sqlnet.ora

Rich,
We have a mix of Unix (AIX) and Windows based RDBMS servers and strictly
Windows clients.

Chris
Chris, I take it that you don't have any Unix servers or =
workstations/desktops?

Rich

We, too are looking for a replacement for shared TNSNAMES files and had come
across the paper listed below on using OpenLDAP. It sounded just like the
solution we were looking for but when we tried to follow the directions we
found that they were written for an Oracle 8.x environment, were using 9.2,
and Oracle has packaged LDAP differently in newer releases and we could not
find the files which were used in the directions. Has anyone tried to update
the directions in this paper using a 9.2 release?

What version of 9i? Are you using OiD multi master replication? Under =
9.0.1 on Linux, we could not make it stable, even after opening many =
TARs. In fact, our first TAR took a while to address because the OiD =
Support team needed to get an install of OiD on Linux before they could =
look at our problem. And it didn't help that the docs were scant and =
confusing. I'm sure they've since improved the docs.

Rich

9.2.0.4 on Windows, with OID multi-master replication.

"Jesse, Rich" wrote:


Do you Yahoo!?
New and Improved Yahoo! Mail - Send 10MB messages!
http://promotions.yahoo.com/new_mail

OID is an enormous piece of software, it requires its own database,
it's very hard to set up, requires replication and it doesn't support
any other LDAP software, despite the initial promises. I am not going
to run it, even if it means replicating tnsnames.ora over Samba and NFS.

--
Mladen Gogala
A & E TV Network
Ext. 1216
http://promotions.yahoo.com/new_mail

You expressed interest in hearing references. I gave one. I didn't
say you should use it; whether you do or not is entirely your concern.



Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com