Upgrading to OES11 downgrades eDirectory to previous patch level

Prior to upgrading a server from OES2 SP3 to OES11, all March 2012 channel updates were applied, including eDirectory's.  Running a ndsstat resulted in the following version information.

 

OES2 SP3 fully patched:

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:  oes2sp3-64-svr.O=emg.OES2-3-32-TREETree Name: OES2-3-32-TREE
Tree Name: OES2-3-32-TREE

Server Name: .CN=oes2sp3-64-svr.O=emg.T=OES2-3-32-TREE.
Binary Version: 20606.01
Root Most Entry Depth: 0
Product Version: eDirectory for Linux x86_64 v8.8 SP6 [DS]

 

After upgrading to OES11:

[1] Instance at /etc/opt/novell/eDirectory/conf/nds.conf:  oes2sp3-64-svr.O=emg.OES2-3-32-TREETree Name: OES2-3-32-TREE

Tree Name: OES2-3-32-TREE
Server Name: .CN=oes2sp3-64-svr.O=emg.T=OES2-3-32-TREE.
Binary Version: 20605.00
Root Most Entry Depth: 0
Product Version: eDirectory for Linux x86_64 v8.8 SP6 [DS]

 

 eDirectory 8.8 SP6 Patch 5 (20606.01) was released for standalone versions of eDirectory 8.8 SP6 as well as for the OES2 SP3 channel in March 2012.  This patch has not yet been made available in the OES11 channel.  The previous patch, eDirectory 8.8 SP6 Patch 4 (20605.00), was the latest available release when OES11 shipped.  Therefore if the March 2012 updates are applied to an OES2 SP3 server prior to upgrading that server to OES11 the server will downgrade from eDirectory 8.8 SP6 Patch 5 to Patch 4 in the process.

 

If the March 2012 updates have not yet been applied: 

Novell recommends to NOT apply these updates to an OES2 SP3 server if that server is to be upgraded to OES11 in the short-term. 

 

If the March 2012 updates have been applied: 

There should be no problems experianced due to the one patch level regression.  No database changes have occurred. 

Novell hopes to have Patch 5 available in the OES11 channel as quickly as possible.