Recovering and cleaning up after a migration failure

  • 7008355
  • 12-Apr-2011
  • 27-Apr-2012


SUSE Linux Enterprise Server 10 Service Pack 2
SUSE Linux Enterprise Server 10 Service Pack 3
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 2
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3


The OES2 or SLES migration failed or moving from OES2-SP2 to OES2-SP3 goes wrong and the upgrade takes longer than expected due to dependency issues and old packages, it is best to start over, you can do so by doing the following:



Instead of trying to fix ZMD and the Repositories and dependency issues, you may perform an OFFLINE update via



1.  Remove the move-to-oes2-sp3 patch (rug rm -t patch

2.  If it complains about any patches coming from the
make sure that you are no longer subscribed to that channel in 'rug
AND, make sure you don't have it as an installation source in Yast.

3.  Once that was done, remove the migration product marker, this can be done via:
(x86_64) /usr/lib64/zmd/query-pool products @system
(x86) /usr/lib/zmd/query-pool products @system

With the name resulting from the comamnd above, you may then remove the Migration product via

rug remove -t product MigrationProductName

If this is not succesful within /var/lib/zybb/db/products.  Please remove the
file that starts with 321. You can ensure it is the correct file by looking at the contents.

4.  Stop rug (rczmd stop), delete the rug database (rm
/var/lib/zmd/zmd.db), and rczmd start

5.  Once rug was finished refreshing it's new database file, run the
move-to-oes2-sp3 patch.
After it finishes make sure that you are unsubscribed from the OES2-SP2
channels and subscribed to the
OES2-SP3 channels.  Please verify with: rug ca and also check Yast2 -->
Software Management --> Installation Source

6.  After that run: rug up -t patch or Yast --> Software Management -->
Online Update to install patches.


If the update from OES2-SP2 to OES2-SP3 seemed to update okay, but still
experience issues with old repositories and old patches, perform the


1. Make sure that no older repositories are subscribed to from rug.

rug ca

2. If you have older OES2-SP2-Updates, OES2-SP2-Pool or
OES2-SP2-Online, you want to remove them from rug by doing the

rug unsub OES2-SP2-Updates

3. Next, go into Yast2 --> Software Management --> Installation Source
and check and remove any old repositories that are showing up.

4. Try running Yast2 --> Software Management --> Online Update and see
if the correct patches are listed now.

5. If they are not, verify that all the catalogs are subscribed to: The
catalogs you should have for OES2 are OES2-SP3-Updates and OES2-SP3-Pool
and for SLES10 are SLES10-SP3-Updates and SLES10-SP3-Pool.

6. If these are not listed in Yast2 --> Software Management -->
Installation Source, you can edit an existing repository and copy it's
information and add a new one.