This section covers frequent problems encountered with SCPM. Learn how they can arise and how you can solve these issues.
Sometimes SCPM stops working during a switch procedure. This may be caused
by some outside effect, such as a user abort, a power failure, or even an
error in SCPM itself. If this happens, an error message stating SCPM is
locked appears the next time you start SCPM. This is for system safety,
because the data stored in its database may differ from the state of the
system. To resolve this issue, run scpm
recover. SCPM performs all missing
operations of the previous run. You can also run scpm
recover -b, which tries to undo all already
performed operations of the previous run. If you are using the YaST
profile manager, get a recover dialog on start-up that offers
to perform the commands described above.
To modify the configuration of the resource
group when SCPM is already initialized,
after adding or removing groups. In this way, new resources
are added to all profiles and the removed resources are
deleted permanently. If the deleted resources are configured
differently in the various profiles, this configuration
data is lost, except for the current version in your system,
which SCPM does not touch. If you modify the configuration
with YaST, the rebuild command does not need to be entered,
because this is handled by YaST.