Same OID on Two Objects
Articles and Tips: qna
01 Jul 2003
Q.
I have a strange problem. I have discovered that I have the same OID on two of the objects in my eDirectory Tree. I didn't think that this was possible, but apparently it is. My question is, how can I change the OID on one object so as to not have a potential problem lurking in my directory?
Olean "OID" Osmosis
A.
Dear Olean: The following comes from Novell's own Julie Powers. The following is an example of this change for an objectClass (change from 1.1.1.1 to 13.56.46.34.1.0). This can be done for an attribute as well, as it is the same structure. The only change in the delete and add is the OID. This same type of LDIF can be used to add/delete attributes from an object class.
The objectClass can already be instantiated in the directory, no need to remove the instances to make this change. Always make sure you test first in test environment.
dn: cn=schema changetype: modify delete: objectclasses objectClasses: ( 1.1.1.1 NAME 'MNDOCCATS' DESC 'MNDOC ObjectClass' AUXILIARY MAY ( mndocLocFacility $ ndocLocDesc $ mndocLocChangeTime $ mndocBadgeInfo $ mndocLockout $ mndocLockoutFacility ) X-NDS_NAME 'MNDOCCATS' X-NDS_NOT_CONTAINER '1' ) - add: objectclasses objectClasses: ( 13.56.46.34.1.0 NAME 'MNDOCCATS' DESC 'MNDOC ObjectClass' AUXILIARY MAY ( mndocLocFacility $ mndocLocDesc $ mndocLocChangeTime $ mndocBadgeInfo $ mndocLockout $ mndocLockoutFacility ) X-NDS_NAME 'MNDOCCATS' X-NDS_NOT_CONTAINER '1' )
* Originally published in Novell AppNotes
Disclaimer
The origin of this information may be internal or external to Novell. While Novell makes all reasonable efforts to verify this information, Novell does not make explicit or implied claims to its validity.