Matthew Cheung wrote: > I will try it later. > And below is the console debug output: > VListEntryModel.getSize() > VListEntryModel.getSize()=17 > VListEntryModel.getElementAt: need entry 16 > VListEntryModel.getElementAt: _top=0 _entries.size()=17 > VListEntryModel.getElementAt: success for element=16 > VListEntryModel.getElementAt: object=DSEntryObject for This entry could not > be read.
So, the VLV search says there are 17 entries, but there are really only 16. It would be nice to know which entry it thinks is there. > > > Thanks. > "Rich Megginson" <[EMAIL PROTECTED]> ���g��l�� > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > Matthew Cheung wrote: > > > > > yes, exactly the same in console but cannot see the unknown entry. > > > > > > May i just right click the replication agreement on the normal directory > > > server and select initialize consumer to solve this problem? > > > > You could try it, but I don't know if it will fix the problem because I > don't know what the problem is. > > > > > > > > "Rich Megginson" <[EMAIL PROTECTED]> ���g��l�� > > > [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > > > > Matthew Cheung wrote: > > > > > > > > > The unknown entry cannot be searched by your suggested command. > > > > > > > > So, when you did the command line search, you saw exactly the same > entries > > > as you see in the console? You didn't see any extra > > > > entries? > > > > > > > > The last resort is to turn on heavy console debugging. Do > > > > startconsole -D 9 > > > > and redirect the output to a file. The log file should tell you why > it is > > > getting the unknown entry. > > > > > > > > > As this server instance have this unknown entry, my multi-master > > > replication cannot > > > > > be performed now, so may i just delete the replication agreement on > both > > > > > master server, delete all files in both change log directory, > recreate > > > > > change log directory on both server, recreate the multi-master > > > replication > > > > > agreement and do the initialization to this problem server from the > > > normal > > > > > server? > > > > > > > > > > Thanks > > > > > "Matthew Cheung" <[EMAIL PROTECTED]> ���g��l�� > > > > > news:abcis2$[EMAIL PROTECTED]... > > > > > > Thanks~~ > > > > > > "Rich Megginson" <[EMAIL PROTECTED]> ���g��l�� > > > > > > news:[EMAIL PROTECTED]... > > > > > > > Matthew Cheung wrote: > > > > > > > > > > > > > > > Is my database corrupted? > > > > > > > > > > > > > > Probably not. This just means the entry could not be read for > some > > > > > > reason. > > > > > > > > > > > > > > > any tool can i use to check or fix this problem? > > > > > > > > > > > > > > Check the access log. If you want to perform the same search > for > > > > > yourself > > > > > > from the command line, do this: > > > > > > > ldapsearch -s one -b "your suffix" -D "cn=directory manager" -w > > > password > > > > > > '(|(objectclass=*)(objectclass=ldapsubentry))' dn > > > > > > > > > > > > > > Then you can see which entry did not show up. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Thanks > > > > > > > > > > > > > > > > [Image] > > > > > > > > > > > > > > > > > > > > > > > > >
