What instance number and config set number am I supposed to use for ODISRV?

Question

I'm trying to get one way sync working from ADS to OID using the OID that comes with Collaboration Suite 10.1.2 on Windows. The sync works fine if I run it manually (I forget the command I used for that). I can see user accounts show up in the DIT. The problem is that the sync never happens on a scheduled basis and it looks like it is due to ODISRV not running even after I did what the docs said and attempted to start it. It started with no errors but I guess the log file contained all the actual errors.
The docs say to specify an instance number > 0 and a config set. Well, it's clear as mud as to which number to actually use. I assmed the configset value happened to match the nubmer in the Directory Manager GUI under the Integration Server entry (which was configset1 for me). I've tried to specify 1 2 and 3 for the instance numbers and I don't know what I'm supposed to use (and some of them are already being used so the command fails). How many instances are there running by default for ODISRV and how many for OID itself? What number should I be using based on that?
Here are some entries in my logs:
oidldap01s1304.log- OpName=search, duplicate while inserting in Hash Table.
My comment on that snippet is a duplicate what? and what the hell hash table is it trying to use? The info isn't helpful at all.
odisrv02.log- port 389/profile grp 999: registration failure, config set 1 already being executed by instance 0
odisrv01.log- port 636/profile default: config set 0 already being executed by instance 2.
oidmon.log - retry counts exceeded are listed for both odisrv01 and 02
In all those logs the those errors keep repeating. I don't need OID on port 636 so is there a way I can stop/delete that while I'm fixing the sync issue? I saw nothing in the OEM website that allowed me to remove the SSL configuration.
If I try stopping either instance 0 or 1 and try to restart I can't because the instance number is already used. What the hell am I supposed to do then? That means I can stop everything and not be able to start anything back up, does it not?
any ideas how to make sense of this mess oracle developed?

Answer 1

There are two configsets by default. Configset 1 is
for synchronization and Configset 0 is used by
provisioning (again, these are default settings).
You cannot have two odisrv (Provisioning and Synch)
with the same instance #.
So, instance 1 could be Provisioning and instance 2
could be Synch.
Have you setup your synchronization mapping files?
I would suggest you use the DIPTester utility to
setup the synch. It might also be helpful to post the
commands and the odisrv* logs (not the full dump, but
the last snippet).Well I was trying to use ConfigSet 1 for synchronization but it either wouldn't let me because of how it is designed or I had screwed it up at that point since I didn't know what numbers to use for anything and it prevented me from using Set1 because of that. In the end I created a ConfigSet 2 and was able to get another instance of ODISRV running with that. That finally got the sync working on a scheduled basis. I'm now trying to get SSO working between OID and ADS and it seems that OID is too stupid to know that a user exists. I log onto the Windows PC into the domain and attempt to go to http://ssoServer.com:7778/pls/portal and login and I get an authorization denied message.
I have debugging turned on as much as I can and the defaultIsland log file (forget the full filename but its an OC4J file in $ORACLE_HOME\opmn\logs directory). It says that I was denied access because the user could not be found and yet I see the user in the directory tree and it comes back in a search as well. The krbprinicipalname, uid, and orclcommonprinicipalname (I think that's what it's called) are all the same ([email protected]) and the orclusersearchbase is set to dc=mycompany,dc=com so I don't know why the account can't be found.
ANy ideas on that issue?