DIBMIG.NLM phases and how to recover from each phase

  • 10068440
  • NOVL72498
  • 21-Feb-2002
  • 07-Feb-2003

Archived Content: This information is no longer maintained and is provided 'as is' for your convenience.

Goal

DIBMIG.NLM phases and how to recover from each phase

Fact

Novell NetWare 4.11

Novell NetWare 5.0

Novell NetWare 5.1

Novell NetWare 6

Novell Directory Services

Symptom

DIBMIG.NLM hangs or fails during any of the 5 phases.

Fix

DIBMIG.NLM is what converts or upgrades RECMAN versions of Novell Directory Services (NDS 6.x/7.x) to FLAIM versions (NDS 8 or higher).  The following is a list of the 5 phases that DIBMIG.NLM goes through.  If DIBMIG.NLM fails or hangs during any of these 5 phases, you will see instructions on the best way to recover.  

NOTE:  All results of the DIBMIG process are recorded to SYS:SYSTEM\DSMISC.LOG.

PHASE 1:  Calculation\Initialization
-Calculates the number of entries in the database
-The DIB Initializes.  Use SET DSTRACE = +INIT to see errors. 
-The database is locked.

RECOVERY FROM FAILURE DURING PHASE 1
-Reboot the server and try the upgrade/migration again.  No conversion has occurred yet.


PHASE 2: Schema and Entry collection and Allocation
-Memory is allocated for all of the EIDs for Entries\Partitions and Schema
-Entries are placed into memory
-Save entries to disk (if NLM only)  SYS:\_NETWARE\IDS.FIL

RECOVERY FROM FAILURE DURING PHASE 2
-Reboot the server and try the upgrade/migration again.  No conversion has occurred yet.


PHASE 3: Conversion
-Converts schema
---Converts attributes
---Converts classes
---Must have healthy schema
---DSREPAIR should fix issues (default options)
-Converts entries  

RECOVERY FROM FAILURE DURING PHASE 3
-This is the critical stage.  Most likely if DIBMIG fails during this stage, your database will need to be restored from an archived DIB.  It is important to take a backup of the database before attempting any type of upgrade or migration.  The easiest way is to run DSREPAIR -RC from the server console.  This file can only be restored with the help of Novell Support.  The only way to continue forward is if when the server reboots, the database opens up and begins communicating with other servers.  If the database doesn't open, you have to restore the DIB.


PHASE 4: Switching Trustee IDs on volume
-Disables logins
-If error on volume info for whatever reason (not mounted, corrupted info, abort)
-Switch IDs from old to new  (from arrays in memory or from IDS.FIL)

RECOVERY FROM FAILURE DURING PHASE 4
-At this point the database has already been converted.  The only thing that hasn't happened at this point is the conversion of volume file system trustees.  Hopefully these trustees have been backed up before the upgrade/migration.  Most backup solutions have the option to restore file system trustees.  See the following for more information on other file system backup solutions:

TID #10066145 - Using TRUSTBAR.NLM to backup file system trustees"  TRUSTBAR only works on with NetWare 5.x or higher.  For NetWare 4.11, use TBACKUP.  
TID #10062363 - How to use TBACKUP.EXE to backup and restore file system trustees.

At this point, if the server is rebooted, the database should open back up.  You should be able to map drives to mounted volumes with no problems.  If communication is up, TIMESYNC should establish.  In some cases, if an inplace upgrade or migration is attempted again, once the GUI loads and right before the screen where NDS authentication occurs, you'll see an error such as "Failure updating NDS database error code 1"  See TID #10068442 - Failure updating NDS database error code 1 - For more information on recovering from this error.

If you don't get the "error code 1" and the install completes with no problems, restore file system trustees for all volumes and you are done.


PHASE 4.5:  Connections are cleared
-Most likely this phase won't even show up, but all that happens during this phase is all connections to the server are cleared.  

RECOVERY FROM FAILURE DURING PHASE 4.5
-Reboot the server and start the inplace upgrade or migration again.


PHASE 5: Dismount and remount volumes

RECOVERY FROM FAILURE DURING PHASE 5
-Reboot the server and start the inplace upgrade or migration again.


.

For additional information on eDirectory 8.6, please see the following solution.  TID #10066455 - eDirectory 8.6.1 Readme Addendum

For additional information on eDirectory 8.7, please see the following solution.  NOVL81742 - Novell edirectory 8.7.x Readme Addendum

For additional information on NetWare 6, please see the following solution.  TID #10064501 - NetWare 6 Readme Addendum

Feedback service temporarily unavailable. For content questions or problems, please contact Support.