LDAP services

Question

I have ldap services running on one server (A), which accesses a
database on another server (B). I now want to create an exact
copy of the database on server A to server B. I then want to
upgrade the db kernel and oid version to the latest. My
question is, how do you get the ldap services running for 2
databases. I know the connect= part, but how do you distinguish
between the 2 when issuing an ldap check ??
Has anyone experianced any problems doing this ??
Thanks in adbvance.
Steve

Answer 1

You want to run 2 ldap services on the same server, accessing
the 2 different databases on the other servers, right?
What version of OID are you running?
Oracle says that OID doesn't support running multiple directory
services on the same server until 3.0.1.
Having said that, I have been doing this running under 2.1.1.0
for a while, not knowing that it was a bad thing.
Under 2.1.1, the multiple ldap services will come up, but they
share the same shared memory segment. So far, I haven't seen
any problems, but Oracle says that problems can occur, and they
won't answer my other support questions until I isolate my
directories onto separate servers, or until I upgrade to 3.0.1.
Here is what I do under 2.1.1.0.
I am running the directory services and the databases on the
same server.
The basic idea is that you use a different port and instance
number for each directory instance. Also, since my databases
are local, I can define ORACLE_SID and exclude the CONNECT
option on the oidctl command. This causes the directory use a
BEQ connection to the database. I don't have to start a listener
at all. In your case, you will need to include the
connect=clause, and make sure that the instances are defined in
your tnsnames.ora file.
Start up service on port 389, instance 'abc'
export ORACLE_SID=abc
oidmon start
sleep 10
oidctl server=oidldapd instance=1 start
Start up service on port 390, instance 'xyz'
export ORACLE_SID=xyz
oidmon start
sleep 10
oidctl server=oidldapd instance=2 flags='-p 390' start
I have not looked at the 3.0.1 documentation yet, so I don't
know if this is the recommended process under that version.
Bob