This is part 3 of a multi-part blog post on using OpenLDAP for Net Service Name Resolution. Part 1 can be found here.
Configuration for Net Service Name Resolution
Ok, now that you have an OpenLDAP server installed and configured (optionally with master/slave replication configured), it’s time to “teach” it how to handle Oracle Net Service Names. The first thing you’ll want to do is create a directory under /etc/openldap, thus:
This is part 2 of a multi-part blog post on using OpenLDAP for Net Service Name Resolution. Part 1 can be found here.
Installing and configuring OpenLDAP on Oracle Linux 6 is a fairly simple and straightforward process. (Note that I’m working with Oracle Linux 6.4, this process may differ on other Linux distributions and/or versions.)
OID is Oracle’s official solution
Several years ago, I was struggling with a solution to managing hundreds of net service names across several dozen database servers and many hundreds of Oracle client machines. At the time, Oracle had just discontinued ONAMES (which I never had an opportunity to use), and the “official” Oracle solution was the OIM/OID software suite. Well, after weeks of struggling with OID, I decided it was an unwieldy beast, and was just plain painful to set up. (I don’t think I ever did get it completely working.) Just as things were looking down, I spotted a bit of sunlight, through the fog.
I’m embarrassed to see how long I’ve been neglecting this blog.
Today was the closing of Oracle Openworld 2013. I’ve just returned to my hotel from the It’s a Wrap party and a quick dinner. I’ll be spending the weekend in the San Francisco area, back home on Sunday, and back to work on Monday.
I’ve got some blogging ideas, starting with some work I’ve been doing w/ OpenLDAP, so, that’s probably where I’ll start. I should have part one of that series up by next weekend.
Until then, I wish safe travels to my friends returning home from OOW.
I try to be active on the OTN Forums, particularly the Database – General forum. Very often, I’ll see people asking about Oracle internals and X$ tables and where they can learn more. The answer is generally, that you can’t. It’s not possible to read up on stuff that’s largely undocumented. Further, you shouldn’t really care that much. While internals can be interesting, they rarely add a great deal of real, practical value.
My apologies for my extended absence. Well, I ran into something interesting today, and, I thought it would be appropriate for a blog post, and apparently, I got inspired. No startling revelation here, this is just a bit of a cautionary tale about the unintended consequences of using a new feature. A quick search of the Oracle Documentation confirms that the
skip locked directive of the
select for update statement was introduced in Oracle 11g, version 11.1. But, before we dive into that, let’s review the functionality of
select for update through versions of Oracle preceding 11g.
Or should I say ‘Brum’?
Well, I’ve just been notified that one of my abstract submissions, “Introduction to Locks and Enqueues”, has been accepted by the UKOUG for the 2008 Annual Conference, coming up in December. I’m really looking forward to it. This will be my 4th year attending. It’s also the first year the conference will be expanded to a full 5-day week. There’s bound to be a ton of great material. I have to say, even for someone coming from overseas, this conference is well worth your time and money.
See you in Birmingham, er, Brum!