Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Changetype Incorrect for ADCD?

14 views
Skip to first unread message

Flash

unread,
Feb 1, 2012, 8:03:20 PM2/1/12
to
Hi there,

I'm using TDI V7.1 and using the ADCD to populate a TAM repository.

I am getting variable behaviour with the changetype attribute which
the connector should be setting.

I am of the understanding that when ADCD detects a new key the
changetype should be "add", as in I need to "add" this object to the
destination. Ie,

2012-02-02 09:18:15,847 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- [ActiveDirectoryChangeDetectionConnector] CTGDIZ904I DELTA: new
entry, key = CN=thisoneworks,DC=test.
2012-02-02 09:18:16,009 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- ---------------Start Entry Dump--------------
2012-02-02 09:18:16,009 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- CTGDIS003I *** Start dumping Entry
2012-02-02 09:18:16,009 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- Operation: add
2012-02-02 09:18:16,009 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- Entry attributes:
2012-02-02 09:18:16,009 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- name (replace): 'thisoneworks'

2012-02-02 09:18:16,009 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- $dn (replace): 'CN=thisoneworks,DC=test'
2012-02-02 09:18:16,010 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- sAMAccountType (replace): '268435456'

2012-02-02 09:18:16,010 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- groupname (replace): 'thisoneworks'

2012-02-02 09:18:16,010 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- cn (replace): 'thisoneworks'
2012-02-02 09:18:16,010 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- uSNChanged (replace): '277966388'
2012-02-02 09:18:16,010 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- changeType (replace): 'add'

}'
2012-02-02 09:18:16,010 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- CTGDIS004I *** Finished dumping Entry

Occasionally, I am getting a changetype of "modify". This does not
make sense to me.

2012-02-02 09:36:15,758 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- [ActiveDirectoryChangeDetectionConnector] CTGDIZ904I DELTA: new
entry, key = CN=thisonedoesnot,DC=FAIL.

2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- ---------------Start Entry Dump--------------
2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- CTGDIS003I *** Start dumping Entry
2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- Operation: add
2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- Entry attributes:
2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- name (replace): 'thisonedoesnot'
2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- $dn (replace): 'CN=thisonedoesnot,DC=FAIL'
2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- sAMAccountType (replace): '268435456'

2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- groupname (replace): 'thisonedoesnot'

2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- cn (replace): 'thisonedoesnot'
2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- uSNChanged (replace): '304150653'

2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- sAMAccountName (replace): 'thisonedoesnot'

2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- changeType (replace): 'modify'

2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- objectGUIDStr (replace): '{E3175293-89B2-49F6-
BBD0-C299FEF8C459

}'
2012-02-02 09:36:15,759 INFO [AssemblyLine.AssemblyLines/groupSync.1]
- CTGDIS004I *** Finished dumping Entry

In both cases, the Connector is reporting a new key. Is there any
specific behaviour which I am missing here which would cause the
change detector to set the changetype to modify?

Eddie Hartman

unread,
Feb 9, 2012, 7:51:24 AM2/9/12
to
There is some 'magic' going on in the AD CDC to differentiate new and
modified USNs (the keys that you have to use to figure out what has
changed in AD). It could be the component is not always successful. If
so, please raise a PMR with our support gurus and see if we can
tighten up the logic here.

Regardless, I assume you are using an Update mode Connector to write
to TAM (?), in which case this mode will handle add/modify for you.
And if you have 'add' specific logic then it can be applied in the
Before Add Hook (or Before Modify if it is 'modify' logic).

Hope this helps!
-Eddie
0 new messages