Anonymous_User Absent Member.
Absent Member.
166 views

Funky: Synthetic Add dropping attributes.

See this small trace excerpt. It is at the point when a query returns
as a result of a synthetic add being created.

The query returns "Given Name" but then it is dropped in the add document.

Merge Authority on Given Name is "correct" as I understand it. Set to
IDV, since this is an add going to the SQL DB. The synch is set
PUB=Reset/SUB=Synchronize.

Thoughts? Any chance this is related to JDBC Shim issues going from
3.6.1 to 4.0.2? Trying to think of ofther options.
========

Drivers\BADGES : Calling free on tempContext = 1610612808
[03/06/14 11:57:25.794]:$$$ ST:Read result:
[03/06/14 11:57:25.795]:$$$ ST:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Advanced" version="4.0.2.0">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<output>
<instance class-name="User"
qualified-src-dn="O=data\OU=usr\OU=edu\CN=1lenet"
src-dn="\CCPSIDV\data\usr\edu\1lenet" src-entry-id="396403">
<attr attr-name="ccpsUID">
<value timestamp="1394125045#58" type="string">1000490317</value>
</attr>
<attr attr-name="CN">
<value naming="true" timestamp="1394125430#33"
type="string">1lenet</value>
</attr>
<attr attr-name="Given Name">
<value timestamp="1394125430#4" type="string">Test</value>
</attr>
<attr attr-name="nspmDistributionPassword"><!-- content
suppressed -->
</attr>
<attr attr-name="preferredName">
<value timestamp="1394125045#70" type="string">Test</value>
</attr>
<attr attr-name="Surname">
<value timestamp="1394125430#12" type="string">1Lenel</value>
</attr>
</instance>
<status level="success"></status>
</output>
</nds>
[03/06/14 11:57:25.800]:$$$ ST:Synthetic add:
[03/06/14 11:57:25.801]:$$$ ST:
<nds dtdversion="4.0" ndsversion="8.x">
<source>
<product edition="Advanced" version="4.0.2.0">DirXML</product>
<contact>Novell, Inc.</contact>
</source>
<input>
<add cached-time="20140306165725.710Z" class-name="User"
event-id="IDV-02-DS#20140306165322#1#3:131f077e-1592-43e4-09bd-7e071f139215"
qualified-src-dn="O=data\OU=usr\OU=edu\CN=1lenet"
src-dn="\CCPSIDV\data\usr\edu\1lenet"
src-entry-id="396403" timestamp="1394125045#95">
<add-attr attr-name="ccpsUID">
<value timestamp="1394125045#58" type="string">1000490317</value>
</add-attr>
<add-attr attr-name="CN">
<value naming="true" timestamp="1394125430#33"
type="string">1lenet</value>
</add-attr>
<add-attr attr-name="nspmDistributionPassword"><!-- content
suppressed -->
</add-attr>
<add-attr attr-name="preferredName">
<value timestamp="1394125045#70" type="string">Test</value>
</add-attr>
</add>
</input>
</nds>
[03/06/14 11:57:25.807]:$$$ ST:Applying object matching policies.
[03/06/14 11:57:25.808]:$$$ ST:Applying policy: %+C%14CMatching Rule%-C.
[03/06/14 11:57:25.808]:$$$ ST: Applying to add #1.
Labels (1)
0 Likes
3 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Funky: Synthetic Add dropping attributes.

Rob S. wrote:

> See this small trace excerpt. It is at the point when a query returns as a result of a synthetic add being created.
>
> The query returns "Given Name" but then it is dropped in the add document.
>
> Merge Authority on Given Name is "correct" as I understand it. Set to IDV


https://www.netiq.com/support/kb/doc.php?id=7000905


"By default values that are newer than the modify that triggered the synthetic add are intentionally excluded from the add, with the expectation that they will come through in a subsequent modify"

So this is not a bug. The subsequent paragraph explains how to bypass this if desired.

--
If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below...
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Funky: Synthetic Add dropping attributes.

On 3/6/2014 11:53 AM, Alex McHugh wrote:
> Rob S. wrote:
>
>> See this small trace excerpt. It is at the point when a query returns as a result of a synthetic add being created.
>>
>> The query returns "Given Name" but then it is dropped in the add document.
>>
>> Merge Authority on Given Name is "correct" as I understand it. Set to IDV

>
> https://www.netiq.com/support/kb/doc.php?id=7000905
>
>
> "By default values that are newer than the modify that triggered the synthetic add are intentionally excluded from the add, with the expectation that they will come through in a subsequent modify"
>
> So this is not a bug. The subsequent paragraph explains how to bypass this if desired.
>

Turns out there's a funky timesync issue. Server pointing to ntp.pool
clocks is 11 minutes out of synch. Likely a VM issue, but it explains
the timestamp differential.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Funky: Synthetic Add dropping attributes.

On 3/6/2014 11:53 AM, Alex McHugh wrote:
> Rob S. wrote:
>
>> See this small trace excerpt. It is at the point when a query returns as a result of a synthetic add being created.
>>
>> The query returns "Given Name" but then it is dropped in the add document.
>>
>> Merge Authority on Given Name is "correct" as I understand it. Set to IDV

>
> https://www.netiq.com/support/kb/doc.php?id=7000905
>
>
> "By default values that are newer than the modify that triggered the synthetic add are intentionally excluded from the add, with the expectation that they will come through in a subsequent modify"
>
> So this is not a bug. The subsequent paragraph explains how to bypass this if desired.
>

Turns out there's a funky timesync issue. Server pointing to ntp.pool
clocks is 11 minutes out of synch. Likely a VM issue, but it explains
the timestamp differential.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.