Problem to create a replica on IBM Tivoli Directory server 5.2

[cscubla]

Hi,

I have a problem when I want to create a replica.

Context :
I have two servers "server1" and "server2".
Theses two servers match very well.
The suffix is o=eavs
all is OK.

I want to replicate the suffix o=eavs.
I had followed the instructions which I have found on the admin_gd.htm
(chapter Replication - creating a master-replica topology), but I have an
error message (impossible d'ajouter l'accord) when I click OK to create the
replica.

Have you an idea to resolve my problem ?


here, the error message that I had found on the log file :

[Error] Thu Oct 16 16:34:42 CEST 2003
javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
Unwilling To Perform]; remaining name
'cn=ASALI,cn=ratp-sdc-33,ibm-replicaGroup=default,O=EAVS'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2823)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2696)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2502)
at com.sun.jndi.ldap.LdapCtx.c_bind(LdapCtx.java:348)
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_bind(ComponentDirContext.java
:292)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.bind(PartialCompositeDir
Context.java:213)
at
javax.naming.directory.InitialDirContext.bind(InitialDirContext.java:173)
at
com.ibm.ldap.admin.replication.common.ReplicationAction.bind(ReplicationActi
on.java:2184)
at
com.ibm.ldap.admin.replication.common.ReplicationAction.addAgreement(Replica
tionAction.java:335)
at
com.ibm.ldap.admin.replication.topology.ReplicaDetailsBean.verifyChanges(Rep
licaDetailsBean.java:575)
at
com.ibm.ui.framework.UIRendererListener.actionPerformed(UIRendererListener.j
ava:438)
at
com.ibm.mdr.DrRenderer.fireActionPerformedEvent(DrRenderer.java:762)
at
com.ibm.mdr.DrStateMgr.dequeueAndFireEvents(DrStateMgr.java:3427)
at com.ibm.mdr.DrStateMgr.eventFromUser(DrStateMgr.java:1847)
at com.ibm.mdr.DrRenderer.eventFromWeb(DrRenderer.java:2022)
at
com.ibm.webnav.servlet.WnTransactionManager.processTransaction(WnTransaction
Manager.java:644)
at
com.ibm.webnav.servlet.WnTransactionThread.run(WnTransactionThread.java:111)


thanks for your answer.

Cédric.

[cscubla]

I had found a solution to create a replica (add an entry manually under
master entry) and it's work.
Now, I have a problem during replication :
---------------------------------
Echec Ldif :
dn: id=293068,o=eavs
changetype: modify
replace:libelle
libelle:: mdaty2ftzxjhie5vaxn5lunmlumwmdegbglizwxsw6kgmq==
libelle:: qtawlwnhbwvyysbob2lzes1dtc1dmdaxigxpymvsbmopidi=
-
control: 1.3.18.0.2.10.19 false::
miqaaabkmiqaaaancgecmiqaaaaeba1tb2rpzmllcnnoyw1lmyqaaaajbaddtj1st09umiqaaa
axcgecmiqaaaaoba9tb2rpznluaw1lc3rhbxaxhaaaabeedziwmdmxmde3mdg1ndu0wg
---------------------------------

I think it's because the value of 'libelle' attribut have accent ???
How to do to resolve this problem ? where can I find detail documentation on
replication ?

If somebody has an idea ...

thanks

Cédric

Post by cscubla
Hi,
I have a problem when I want to create a replica.
I have two servers "server1" and "server2".
Theses two servers match very well.
The suffix is o=eavs
all is OK.
I want to replicate the suffix o=eavs.
I had followed the instructions which I have found on the admin_gd.htm
(chapter Replication - creating a master-replica topology), but I have an
error message (impossible d'ajouter l'accord) when I click OK to create the
replica.
Have you an idea to resolve my problem ?
[Error] Thu Oct 16 16:34:42 CEST 2003
javax.naming.OperationNotSupportedException: [LDAP: error code 53 -
Unwilling To Perform]; remaining name
'cn=ASALI,cn=ratp-sdc-33,ibm-replicaGroup=default,O=EAVS'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2823)
at

com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2696)

Post by cscubla
at

com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2502)

Post by cscubla
at com.sun.jndi.ldap.LdapCtx.c_bind(LdapCtx.java:348)
at

com.sun.jndi.toolkit.ctx.ComponentDirContext.p_bind(ComponentDirContext.java

Post by cscubla
:292)
at

com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.bind(PartialCompositeDir

Post by cscubla
Context.java:213)
at
javax.naming.directory.InitialDirContext.bind(InitialDirContext.java:173)
at

com.ibm.ldap.admin.replication.common.ReplicationAction.bind(ReplicationActi

Post by cscubla
on.java:2184)
at

com.ibm.ldap.admin.replication.common.ReplicationAction.addAgreement(Replica

Post by cscubla
tionAction.java:335)
at

com.ibm.ldap.admin.replication.topology.ReplicaDetailsBean.verifyChanges(Rep

Post by cscubla
licaDetailsBean.java:575)
at

com.ibm.ui.framework.UIRendererListener.actionPerformed(UIRendererListener.j

Post by cscubla
ava:438)
at
com.ibm.mdr.DrRenderer.fireActionPerformedEvent(DrRenderer.java:762)
at
com.ibm.mdr.DrStateMgr.dequeueAndFireEvents(DrStateMgr.java:3427)
at com.ibm.mdr.DrStateMgr.eventFromUser(DrStateMgr.java:1847)
at com.ibm.mdr.DrRenderer.eventFromWeb(DrRenderer.java:2022)
at

com.ibm.webnav.servlet.WnTransactionManager.processTransaction(WnTransaction

Post by cscubla
Manager.java:644)
at

com.ibm.webnav.servlet.WnTransactionThread.run(WnTransactionThread.java:111)

Post by cscubla
thanks for your answer.
Cédric.

[j***@us.ibm.com]

What is the error you are seeing during replication? There should be
messages in the server log; look in both the supplier and consumer
server's logs. Web admin should be able to show you failure information
by connecting to the supplier server and using the "manage queues" task
under "replication management". Look at the queue (replication agreement)
between the supplier and consumer that you believe is failing.


John

[cscubla]

When I force Replication,
I have the message Replication forced - task success (green icon on the
left) and
I have this message on ibmslapd.log (on the server) :
******
Oct 20 18:46:34 2003 Error Critical extension not supported occurred for
replica 'CN=ASALI,CN=FRAMARTI,IBM-REPLICAGROUP=DEFAULT,O=EAVS': add failed
for entry 'IdVisioWave=test7,Station=POVA,ou=eqts,o=eavs' change ID 8.
*****



On the web administration, on the queue details (Last attempted details), I
have this message :

***
Replica asali
Subtree o=eavs
Entry DN idvisiowave=test7,station=pova,ou=eqts,o=eavs
Last replicated at Oct 20, 2003 4:46:34 PM GMT
Update type add
Last result Failed
Failed LDIF dn: idvisiowave=test7,station=pova,ou=eqts,o=eavs
idvisiowave: test7
objectclass: canal
objectclass: top
canaltype: 01
ipeav: 100
numcanal: 02
porttcp: 5025
ibm-entryuuid: ab34e1a4-d3b6-47a4-9928-a98a6255ff48
control: 1.3.18.0.2.10.19 false::
miqaaadhmiqaaaamcgeamiqaaaadbaxjcmvhdg9yc05hbwuxhaaaaakeb0nopvjpt1qwhaaaad
ekaqawhaaaacged2nyzwf0zvrpbwvzdgftcdgeaaaaeqqpmjawmzewmjaxnjq2mzramiqaaaancg
eamiqaaaaeba1tb2rpzmllcnnoyw1lmyqaaaajbaddtj1st09umiqaaaaxcgeamiqaaaaoba9tb2
rpznluaw1lc3rhbxaxhaaaabeedziwmdmxmdiwmty0njm0wg==
Additional error messages

***


I have no recent log on the consumer on ibmslapd.log


cedric

Post by j***@us.ibm.com
What is the error you are seeing during replication? There should be
messages in the server log; look in both the supplier and consumer
server's logs. Web admin should be able to show you failure information
by connecting to the supplier server and using the "manage queues" task
under "replication management". Look at the queue (replication agreement)
between the supplier and consumer that you believe is failing.
John

[cscubla]

Since this afternoon, the replication try to update the replica... on the
web administration, each minute, I have the same message as I had in my
precedent mail (when I click on Refresh button). I have no recent log (on
the comsumer and supplier).

Have you an idea ?

Cedric

Post by cscubla
When I force Replication,
I have the message Replication forced - task success (green icon on the
left) and
******
Oct 20 18:46:34 2003 Error Critical extension not supported occurred for
replica 'CN=ASALI,CN=FRAMARTI,IBM-REPLICAGROUP=DEFAULT,O=EAVS': add failed
for entry 'IdVisioWave=test7,Station=POVA,ou=eqts,o=eavs' change ID 8.
*****
On the web administration, on the queue details (Last attempted details), I
***
Replica asali
Subtree o=eavs
Entry DN idvisiowave=test7,station=pova,ou=eqts,o=eavs
Last replicated at Oct 20, 2003 4:46:34 PM GMT
Update type add
Last result Failed
Failed LDIF dn: idvisiowave=test7,station=pova,ou=eqts,o=eavs
idvisiowave: test7
objectclass: canal
objectclass: top
canaltype: 01
ipeav: 100
numcanal: 02
porttcp: 5025
ibm-entryuuid: ab34e1a4-d3b6-47a4-9928-a98a6255ff48
miqaaadhmiqaaaamcgeamiqaaaadbaxjcmvhdg9yc05hbwuxhaaaaakeb0nopvjpt1qwhaaaad

ekaqawhaaaacged2nyzwf0zvrpbwvzdgftcdgeaaaaeqqpmjawmzewmjaxnjq2mzramiqaaaancg
eamiqaaaaeba1tb2rpzmllcnnoyw1lmyqaaaajbaddtj1st09umiqaaaaxcgeamiqaaaaoba9tb2

Post by cscubla
rpznluaw1lc3rhbxaxhaaaabeedziwmdmxmdiwmty0njm0wg==
Additional error messages
***
I have no recent log on the consumer on ibmslapd.log
cedric

Post by j***@us.ibm.com
What is the error you are seeing during replication? There should be
messages in the server log; look in both the supplier and consumer
server's logs. Web admin should be able to show you failure information
by connecting to the supplier server and using the "manage queues" task
under "replication management". Look at the queue (replication agreement)
between the supplier and consumer that you believe is failing.
John

[j***@us.ibm.com]

Sorry. This is out of my depth -- wrong platform and release for me to
dig into any more. I have to suggest IBM service or hope that someone
from the IDS team sees this message.

The error message appears to indicate the the consumer didn't support a
control that was present in the replicated operation. The LDIF shows a
control used to replicate some operational attributes, but it is marked
non-critical, so I'd expect the server to ignore it if it didn't recognize
it. If the consumer is also IDS 5.2 it should recognize the control.


John

[cscubla]

Thank you John.
For information, the supplier and comsumer are in version IDS 5.2.
I will try to install the 5.1 version instead of 5.2 and test again.

Cédric

Post by j***@us.ibm.com
Sorry. This is out of my depth -- wrong platform and release for me to
dig into any more. I have to suggest IBM service or hope that someone
from the IDS team sees this message.
The error message appears to indicate the the consumer didn't support a
control that was present in the replicated operation. The LDIF shows a
control used to replicate some operational attributes, but it is marked
non-critical, so I'd expect the server to ignore it if it didn't recognize
it. If the consumer is also IDS 5.2 it should recognize the control.
John

[cscubla]

For Information, it's work very well with the 5.1.
My platform is Windows 2000 pro.

Cédric

Post by cscubla
Thank you John.
For information, the supplier and comsumer are in version IDS 5.2.
I will try to install the 5.1 version instead of 5.2 and test again.
Cédric

Post by j***@us.ibm.com
Sorry. This is out of my depth -- wrong platform and release for me to
dig into any more. I have to suggest IBM service or hope that someone
from the IDS team sees this message.
The error message appears to indicate the the consumer didn't support a
control that was present in the replicated operation. The LDIF shows a
control used to replicate some operational attributes, but it is marked
non-critical, so I'd expect the server to ignore it if it didn't recognize
it. If the consumer is also IDS 5.2 it should recognize the control.
John