UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21. Read more.
UPDATE! The community will be go into read-only on April 19, 8am Pacific in preparation for migration on April 21.Read more.
Commodore
Commodore
811 views

IDM Sync Error -618

Jump to solution

Hello,

We are migrating IDM server from 4.5 to 4.6. When adding the new server to the existing driver set we are having following error 

iManager:

(Error -618)The server has detected an inconsistent database. Usually this means that the number of entries in a container does not match the number stored in the container's entry.

Any suggestions?

Thanks

Labels (2)
0 Likes
1 Solution

Accepted Solutions
Commodore
Commodore

Issue resolved.. we had couple of eDirectory objects got corrupted while migrating. 

Used following commands to repair the objects:

ndsrepair -E "ObjectID"

Thanks for your response guys

View solution in original post

0 Likes
5 Replies
Vice Admiral
Vice Admiral
Have you already done the IDM install on the new server you are wanting to
add to the driver set?

Did you make sure it has replicas of the partition that the driver set is
in?


Knowledge Partner Knowledge Partner
Knowledge Partner
I can suggest a "disable" driver (to prevent "fake" user ADD events).

Add replicas for all object containers, that driver will monitor.

If the issue still exists, please contact the official support channel.

NDSREPAIR, in theory, can help, but according to the latest instructions, you have to use Advanced switches only according to  NETIQ support personal instructions.



IMPORTANT:The advanced switch [-Ad] should be given as last argument. We recommend that the -Ad advanced switch option be enabled only when instructed by a NetIQ Support technician. If the config-file is provided as the argument, then it should be given before the advanced switch [-Ad].
Commodore
Commodore

Issue resolved.. we had couple of eDirectory objects got corrupted while migrating. 

Used following commands to repair the objects:

ndsrepair -E "ObjectID"

Thanks for your response guys

View solution in original post

0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Single object repair is great. Especially since the 618 often specifies the object in error.

 

Commodore
Commodore
Yes I did installed IDM on the new server.
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.