Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Anonymous_User Absent Member.
Absent Member.
232 views

Schema not the same during Merge


I am merging a tree with 2 NW6.5 SP8 servers with a tree with a mix if
NW and OES11 servers.

When I am doing the Schema import I am seeing it show the following:

Modifying attribute :Novonyx:Use Quota
Flags changed to SF_SiINGLE_VALUED_ATTR, SF_STRING_ATTR,
SF_SYNC_IMMEDIATE
Schema successfully checked and extended.

I have done the Import in both directions many times and it still says
the same thing. I have tried to delete the attribute as we of course no
longer use NetMail but it says it is being used by an object but I don't
know what object.

Of course it fails when trying to do the merge saying that the Attribute
"Novonyx:Use Quota", Flag "DS_SIZED_ATTR" is set only in the target
tree.

Any way to delete all the Novonyx stuff from both schemas and get rid of
all that old stuff?


--
kbent
------------------------------------------------------------------------
kbent's Profile: https://forums.netiq.com/member.php?userid=5469
View this thread: https://forums.netiq.com/showthread.php?t=48231

Labels (1)
0 Likes
15 Replies
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge

On Thu, 18 Jul 2013 18:24:02 +0000, kbent wrote:

> I have done the Import in both directions many times and it still says
> the same thing. I have tried to delete the attribute as we of course no
> longer use NetMail but it says it is being used by an object but I don't
> know what object.


It's probably "in use" by the schema class definition. You might be able
to remove it from there, or update it via LDAP. Export the schema to an
LDIF file from one tree, then use that to delete/add the attribute in the
other tree. As long as it's all in one operation, it should work.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


Thanks for the reply. I was away for a few days and now back at it.

Time has helped. I was able to delete the old Novonyx attribute and
that error went away. However new ones have surfaced.

I run the Import Remote Schema from the old Tree and import the main
tree schema it is successful.

When I run it from the Main Tree and try to import the old tree schema I
get the following.


Import remote schema from another Tree
Operation performed by user: .admin.AVR11.AVR11-TREE.
Checking and extending schema from a remote tree
Making connection to IP address: "10.182.0.40"
Source server name: ".CN=MRH1.OU=MRH.O=Middle.T=MIDDLE."
Attribute definition cannot be merged. Attribute name: accountExpires
This operation cannot continue.
Error -699 merging attribute definitions from source server
Operation failed, Error: -699
*** END ***


--
kbent
------------------------------------------------------------------------
kbent's Profile: https://forums.netiq.com/member.php?userid=5469
View this thread: https://forums.netiq.com/showthread.php?t=48231

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


Why don't you export the definition of this attribute from both trees
and compare?


--
--
-eDirectory Rules!-

Peter
www.DreamLAN.com
------------------------------------------------------------------------
peterkuo's Profile: https://forums.netiq.com/member.php?userid=170
View this thread: https://forums.netiq.com/showthread.php?t=48231

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


I used ICE from iManager and exported both schemas to file then rant the
compare and got the following log file. Not much info.
Am I doing it wrong? I have no experience with ICE & LDIF files so if I
need to do something else I need some guidance.


Novell Import Convert Export utility for Novell eDirectory
version: 20215.04
Copyright 2000-2005 Novell, Inc. All rights reserved. U.S. Patent No.
6,915,287.
Source Handler: ICE LDIF handler for Novell eDirectory (version:
20215.04 )
Destination Handler: ICE LDIF handler for Novell eDirectory (version:
20215.04 )
Getting source schema...done.
Getting destination schema...done.
Starting schema compare...
Done.

Options Used:
-b -lsys:\tomcat\5.0\webapps\nps\WEB-INF\temp\ice32595\ice.log
-esys:\tomcat\5.0\webapps\nps\WEB-INF\temp\ice32595\error.ldf -C -c
sys:\tomcat\5.0\webapps\nps\WEB-INF\temp\ice32595\compare.ldf -SLDIF
-fsys:\tomcat\5.0\webapps\nps\tempFiles\ems1.ldf -c -DLDIF
-fsys:\tomcat\5.0\webapps\nps\tempFiles\avr011.ldf

Thanks,

Kevin


--
kbent
------------------------------------------------------------------------
kbent's Profile: https://forums.netiq.com/member.php?userid=5469
View this thread: https://forums.netiq.com/showthread.php?t=48231

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


Oh, don't use the compare feature, but a straight export of the schema
to file from each tree - and then selectively compare the attribute from
both files "by hand."


--
--
-eDirectory Rules!-

Peter
www.DreamLAN.com
------------------------------------------------------------------------
peterkuo's Profile: https://forums.netiq.com/member.php?userid=170
View this thread: https://forums.netiq.com/showthread.php?t=48231

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


OK I tried that. See my posts under the thread with dgersic.


--
kbent
------------------------------------------------------------------------
kbent's Profile: https://forums.netiq.com/member.php?userid=5469
View this thread: https://forums.netiq.com/showthread.php?t=48231

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


Okay dokay!


--
--
-eDirectory Rules!-

Peter
www.DreamLAN.com
------------------------------------------------------------------------
peterkuo's Profile: https://forums.netiq.com/member.php?userid=170
View this thread: https://forums.netiq.com/showthread.php?t=48231

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge

On Mon, 22 Jul 2013 18:24:02 +0000, kbent wrote:

> Thanks for the reply. I was away for a few days and now back at it.
>
> Time has helped. I was able to delete the old Novonyx attribute and
> that error went away. However new ones have surfaced.


Yeah, I've seen that before. It takes a while some times for it to decide
that it's not in use so that you can remove it.


> Import remote schema from another Tree Operation performed by user:
> .admin.AVR11.AVR11-TREE. Checking and extending schema from a remote
> tree Making connection to IP address: "10.182.0.40" Source server name:
> ".CN=MRH1.OU=MRH.O=Middle.T=MIDDLE." Attribute definition cannot be
> merged. Attribute name: accountExpires This operation cannot continue.


I'd export the schema to LDIF from both trees, then examine the
definitions of accountExpires to see what's different about them.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


I looked for accountExpires in both schema files but it was not found in
either. The file has a lot of encrypted data so maybe it is in there
somewhere.
Not sure why it is encrypted. I made sure it was set to no encryption
when I exported it.

Any other ideas?


--
kbent
------------------------------------------------------------------------
kbent's Profile: https://forums.netiq.com/member.php?userid=5469
View this thread: https://forums.netiq.com/showthread.php?t=48231

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


Just looked at them both in iManager Attribute Information

Main Tree

Syntax:Integer_64

ASN1 ID:1.2.840.113556.1.4.159

Attribute flags:
Single Valued
Sized (0..8)
Synchronize Immediately
Integer_64

Class using attribute:
BkupExec:JobServer BkupExec:JobServer
mSDS:Computer mSDS:Computer
msPKI-Key-Recovery-Agent msPKI-Key-Recovery-Agent
User User


Old Tree


Syntax: Octet String

ASN1 ID: 1.2.840.113556.1.4.159

Attribute flags:
Single Valued
Sized (0..8)
Synchronize Immediately

Class using attribute:
BkupExec:JobServer BkupExec:JobServer
mSDS:Computer mSDS:Computer
msPKI-Key-Recovery-Agent msPKI-Key-Recovery-Agent
User User


--
kbent
------------------------------------------------------------------------
kbent's Profile: https://forums.netiq.com/member.php?userid=5469
View this thread: https://forums.netiq.com/showthread.php?t=48231

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge

On Wed, 24 Jul 2013 14:44:01 +0000, kbent wrote:

> Syntax:Integer_64
> Syntax: Octet String


Well, those are interestingly different syntaxes. Are there any objects
in either tree using this attribute? If not, you may be able to force one
or the other to be redefined so that they match. Otherwise, I'm not sure
what you're going to be able to do. Will the tree merge carry on without
these two having to match schema definitions?

--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


It seemed all Attributes with the Integer_64 were a problem. I had no
luck with the ldif files so I just checked each attribute that showed in
the 699 error during a Schema Import. There were alot of them but I
just worked through the list and deleted each of them. The Schema
Import was successful after awhile and the merge completed successful.
Just letting it sync up now.


--
kbent
------------------------------------------------------------------------
kbent's Profile: https://forums.netiq.com/member.php?userid=5469
View this thread: https://forums.netiq.com/showthread.php?t=48231

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge

On Wed, 24 Jul 2013 14:44:01 +0000, kbent wrote:

> I looked for accountExpires in both schema files but it was not found in
> either. The file has a lot of encrypted data so maybe it is in there
> somewhere.


Let's see the exports to LDIF of the schema from both trees. I suspect
it's not encryption you're seeing, but base64 encoded data.


--
--------------------------------------------------------------------------
David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Schema not the same during Merge


> I suspect it's not encryption you're seeing, but base64 encoded data.


Me thinks he was looking at the actual attribute value and not the
schema definition of said attribute. And given the (old) tree has this
attribute defined using Octet String, B64 data is expected ....


--
--
-eDirectory Rules!-

Peter
www.DreamLAN.com
------------------------------------------------------------------------
peterkuo's Profile: https://forums.netiq.com/member.php?userid=170
View this thread: https://forums.netiq.com/showthread.php?t=48231

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.