Skip to main content
Information Mgmt
New to Lotus
How to buy
Live demos
Technical library
Forums & community
Java™ technology
Open source
SOA and Web services
Web development
My developerWorks
About dW
Submit content

developerWorks  >  Lotus  >  Forums & community  >  Enterprise Integration Forum

Enterprise Integration Forum



Sign in to participate PreviousPrevious NextNext

Dan Droppa4 16.Jan.13 02:31 AM a Web browser
LEI LEI - 8.0 Windows


Domino/LEI 8.5.3 64Bit
MySQL 5.5 via ODBC


I am trying to calculate the text value of a rich text field as part of the Data Transformation in a Replication Job from Notes to SQL via ODBC. This is so we don’t have to stuff a new text field LEIPRScan on all documents with a text representation of the Rich Text field that already exists.

I was able to get the data (Text) from a Notes rich text field into a SQL text field using the Notes Connection: Data Transformation: Formula to Execute During Select field when referenced from a *Direct Transfer* job, and it worked, populating the target SQL field LEIPRScan with the text of the field:

FIELD LEIPRScan := @Trim(@Text(PRScan));

I copied that same code over to the Replication Job and it runs fine the first time, populating the new field on all the rows:

Error: *Replication Conflict* Action: Update at Connector B;
Mismatch in field 'LEIPRScan';
Record key values: LEIUnid = "00062FB052F3D1D288256AFF000D9EFC"

This is great. The records get updated. But the second time it runs, it errors out:

Activity started
Trace Statement: <SELECT LEIUnid, LEIForm, DealID, PRScan FROM press_release ORDER BY LEIUnid>, Connector 'SQL Target Press Release', Method -Select-
Trace Statement: <SELECT * FROM press_release WHERE 0=1>, Connector 'SQL Target Press Release', Method -Update-
Trace Statement: <UPDATE press_release SET LEIForm = ?, DealID = ?, PRScan = ? WHERE LEIUnid = ?>, Connector 'SQL Target Press Release', Method -Update-
Error: Update at Connector B affected no records (check for key precision mismatch)
Error: *Replication Conflict* Action: Update at Connector B;
Mismatch in field 'LEIPRScan';
Record key values: LEIUnid = "11A8E9BE105C3E0E8825663500777707"
Current record key values at the time of the replication error --
- Connector A record key values: LEIUnid = "11A8E9BE105C3E0E8825663500777707"
- Connector B record key values: LEIUnid = "11A8E9BE105C3E0E8825663500777707"
Activity Ended With An Error

If I drop and recreate the table from scratch, the job runs again and populates the data. If I remove the data from the target LEIPRScan field on the SQL side, the job runs and populates the data again. If I remove the Data Transformation commands, the job runs and removes the data from the LEIPRScan field on the SQL side, as expected. If I run the job again when data is populated in LEIPRScan on the SQL , it fails.
I am sure I am missing something obvious and there is a trivial way to make this happen within the Data Transformation of a Replication job.


1. I am using Sort Order Meta Connectors on the LEIUnid field at both ends.
2. I am not using Timestamp Replication, but I think I may want to in the future.
3. I have the Notes Connection: Selection Options: Selected View: (LEIIndexView0) configured as a static with "Select By View with Allow View Creation/Overwrite (Replication Activity only)" checked.


I have tried selecting the"Reduced precision comparison" setting on the Replication job | Data Options | Data Comparison and Trimming section as suggested in this thread:

I have entered a Selected View: (LEIIndexView0) and have selected the Allow View Creation/Overwrite (Replication Activity only) option. I checked the design of the (LEIIndexView0) view and it is using the Field not a formula to populate the one LEIUnid column, both as suggested in this thread:

This thread has an interesting idea, that the key field value is null on either end and it's causing a problem. I found that there were docs that had a Null or nonexistent LEIUnid. I excluded those, reset the SQL database and got the same behavior on only the subset of docs that do have a LEIUnid defined:

Same error here, also using meta connectors and replication job, but no suggestions:

Same error here, also using meta connectors, and replication job, suggestion was to remove the delete the reference to the view in the notes connection document and uncheck the box that allows overwrite of the view in the field selection tab, which I can’t do with my current setup, I need LEI to reference the view:

This is the same error going the other direction (Informix to Notes), but no suggestions:

Here is the same error that was only happening when a Sybase trigger was in place, removed it and the job ran fine:

Error: Update at Connector B affect... (Dan Droppa4 16.Jan.13)
. . Solution: Install IBM Lotus OEM MyS... (Dan Droppa4 6.Feb.13)

  Document options
Print this pagePrint this page

 Search this forum

  Forum views and search
Date (threaded)
Date (flat)
With excerpt
Advanced search

 Sign In or Register
Sign in
Forgot your password?
Forgot your user name?
Create new registration

 RSS feedsRSS
All forum posts RSS
All main topics RSS
More Lotus RSS feeds


Forum use and etiquette
Native Notes Access
Web site Feedback

Lotus Support

 Lotus Support
IBM Support Portal - Lotus software
Lotus Support documents
Lotus support by product
Lotus support downloads
Lotus support RSS feeds


IBM Composite Applications
IBM Mashup Center
IBM Connections
IBM Connections Cloud Developers
IBM Docs
IBM Forms
IBM Mobile Connect
IBM Sametime
IBM SmartCloud for Social Business
IBM Web Experience Factory
Lotus Domino
Lotus Domino Designer
Lotus Expeditor
Lotus Foundations
Lotus iNotes
Lotus Instructor Community Courseware
Lotus Notes
Lotus Notes & Domino Application Development
Lotus Notes Traveler
Lotus Protector
Lotus Quickr
Lotus Symphony
IBM Web Content Manager
WebSphere Portal

Lotus Forums

 Lotus Forums
Notes/Domino 9.0
Notes/Domino 8.5 + Traveler
Notes/Domino XPages development forum
Notes/Domino 8
Notes/Domino 6 and 7
IBM Connections
IBM Mobile Connect
IBM Sametime
IBM SmartCloud Notes
Lotus Enterprise Integration
Lotus Protector
Lotus Quickr
Lotus SmartSuite