Knowledge Partner
Knowledge Partner
777 views

609 error preventing sync ok driverset partition

Two server tree, one with IDM, the other just a replica.

Two partitions, tree and IDM driverset

IDM server is master for both.
Other server is read/write replica for both.

eDir 9.0.3

Deleted and recreated thousands of roles, resources and group objects) all role/resource actions performed via approved SOAP calls. All operations performed against master.

Suddenly the replication between the two serves is stuck for the driverset partition only. Says -609 which is missing mandatory.

Change Log says there are 4 objects stuck master to replica, driverset itself plus three roles that should have been deleted.

Replica to master has lots more objects.

I’m thinking I should just zap the replica’s copy of this partition and then re-add it. Will this break anything? Is there maybe a better approach? There are 30k objects under the driverset (mostly roles and resources).

The replica is supposed to just be a dumb copy in case the master goes down. No changes are made directly towards it.
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
Labels (1)
0 Likes
2 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: 609 error preventing sync ok driverset partition

On 08/05/2018 05:24 PM, alexmchugh wrote:
>
> Two server tree, one with IDM, the other just a replica.
>
> Two partitions, tree and IDM driverset
>
> IDM server is master for both.
> Other server is read/write replica for both.
>
> eDir 9.0.3
>
> Deleted and recreated thousands of roles, resources and group objects)
> all role/resource actions performed via approved SOAP calls. All
> operations performed against master.
>
> Suddenly the replication between the two serves is stuck for the
> driverset partition only. Says -609 which is missing mandatory.


That's a bit unusual; what changed between when, presumably, these roles
were created, and now? Repairs, reboots, power surges, antivirus
scanning, other?

> Change Log says there are 4 objects stuck master to replica, driverset
> itself plus three roles that should have been deleted.


Have you tried comparing the servers' schema via iMonitor to make sure
they match properly? They should, of course, but sometimes things happen.

> Replica to master has lots more objects.


Do you mean there are many more objects stuck in the eDirectory change
cache going the other way? That is also strange. Is it possible somebody
reverted a backup of the replica holder or something?

> I�m thinking I should just zap the replica�s copy of this partition and
> then re-add it. Will this break anything? Is there maybe a better
> approach? There are 30k objects under the driverset (mostly roles and
> resources).


That's an option, sure. Normally cleaning up should not be too hard, but
I would probably do that as a last resort since without understanding this
might just happen again.


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
Knowledge Partner
Knowledge Partner

Re: 609 error preventing sync ok driverset partition

ab;2485222 wrote:
That's a bit unusual; what changed between when, presumably, these roles
were created, and now? Repairs, reboots, power surges, antivirus
scanning, other?


The roles are deleted and recreated each year (stupidness of source data, they create new objects and disable the old ones once a year).
Last year this was done-semi manually, this year the deletion was automated. Creation has always been automated.

No AV, repair only after the problem occurred. Reboots and shutdowns, nothing abnormal recently.


ab;2485222 wrote:
Do you mean there are many more objects stuck in the eDirectory change
cache going the other way? That is also strange. Is it possible somebody
reverted a backup of the replica holder or something?


Yes that is the secnario, no revert of backups or such (that I know of). However the master did get shutdown (cleanly) and restarted a few times in that period.

Got the servers talking again by deleting 50+ "unknown" objects that were previously roles from the replica. Most were name conflicts, but not all. My theory is that the delete didn't replicate before the new role that replaced it (same object name, different config) was replicated.

--

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
Alex McHugh - Knowledge Partner - Stavanger, Norway
Who are the Knowledge Partners
If you appreciate my comments, please click the Like button.
If I have resolved your issue, please click the Accept as Solution button.
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.