Denis, I guess that the only way to help you on this is to provide: 1. the external DB schema (as SQL) 2. the DBTable connector configuration 3. the DB resource mapping
Please open an issue on JIRA with such information attached. Regards. On 24/10/2012 14:27, Denis Signoretto wrote: >> -----Messaggio originale----- >> Da: Francesco Chicchiriccò [mailto:[email protected]] >> Inviato: mercoledì 24 ottobre 2012 14:12 >> A: [email protected] >> Oggetto: Re: Problem syncing user using a Long schema attribute >> >> >> On 23/10/2012 18:09, Denis Signoretto wrote: >>> Hi Francesco, >>> so did I. >>> >>> I have deleted all users, redefined the user attribute in >> Syncope as Long resetted the synchronization token of the >> external resource and launch a Sync Task manually, but the >> problem persist. >> >> I guess you have also updated the schema mapping for the DB >> resource in >> order to set this Long attribute in Syncope as AccountId, right? > Yes you are right, I did. >>> 17:59:07.175 DEBUG >>> org.connid.bundles.db.table.DatabaseTableConnector.getLatestSyncToken New >>> token value 1,351,187,890 >>> >>> This sounds strange: is this log message appearing *after* the >>> synchronization has actually take place or before? > after (just after clicking on "Execute" icon in the synchorinization tasks) > >>> [...] >>> >>> -- correct a null value here ? -->> 17:59:07.227 DEBUG >> org.identityconnectors.framework.api.operations.ValidateApiOp. >> validate Return: null >> >> Yes. >> >>> [...] >>> Do you have any suggestion ? >>> >>> Thanks, >>> Denis. >>> >>> -----Messaggio originale----- >>> Da: Francesco Chicchiriccò [mailto:[email protected]] >>> Inviato: martedì 23 ottobre 2012 17:21 >>> A: [email protected] >>> Oggetto: Re: Problem syncing user using a Long schema attribute >>> >>> >>> On 23/10/2012 16:31, Denis Signoretto wrote: >>>> Hello, >>>> >>>> I'm syncing user attributes FROM a resource TO Syncope using DBTable >>>> connector. The attribute used as "Column Key" is a number(10) (it's an >>>> Oracle DB). >>>> If I define the attribute on Syncope as String it works well and when the >>>> sync starts, all updated entries are found and triggered for the update. >>>> After deletions of all users and redefining the attribute in Sycope as >>>> Long the sync don't match on the attribute and no update operation occur. >>> Denis, >>> I guess that what you're seeing is just the expected behavior: if your >>> external resource (in Syncope) is not configured for full reconciliation, >>> then Syncope will invoke the SYNC operation on the >>> underlying connector that will return only entries in the DB that were >>> modified AFTER last synchronization. >>> >>> After deleting all users and redefining the user attribute in Syncope as >>> Long, don't forget to also reset the synchronization token of the external >>> resource. >>> >>> Regards. -- Francesco Chicchiriccò ASF Member, Apache Cocoon PMC and Apache Syncope PPMC Member http://people.apache.org/~ilgrosso/
