This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
rpm5 [2012-12-11 23:36] baggins cosmetics |
rpm5 [2012-12-13 00:38] baggins update |
||
---|---|---|---|
Line 5: | Line 5: | ||
Changes in rpm operation that should interest both users and developers. | Changes in rpm operation that should interest both users and developers. | ||
- | ==== Upgrading from rpm4 and/or older BDB ==== | + | ==== Upgrading from rpm4 and/or older BDB or downgrading from BDB 5.3 ==== |
- | Rpm database upgrade is done automatically during package installation, so there is need to do anything.\\ //But//, in case that upgrade did not happen for some reason, here is the command to do it manually: | + | Rpm database upgrade/downgrade is done automatically during package installation, so there is need to do anything.\\ //But//, in case that upgrade/downgrade did not happen for some reason, here is the command to do it manually: |
<code> | <code> | ||
- | /usr/lib/rpm/bin/dbconvert --rebuilddb | + | /usr/lib/rpm/bin/dbupgrade.sh |
</code> | </code> | ||
+ | |||
+ | Remember to **back up** rpm database before running this script. | ||
==== Fixing database problems ==== | ==== Fixing database problems ==== | ||
Line 34: | Line 36: | ||
==== DB_BUFFER_SMALL error messages ==== | ==== DB_BUFFER_SMALL error messages ==== | ||
- | You may see errors like this: | + | If running rpm built with BDB 5.3 you may see errors like this: |
<code> | <code> | ||
Line 42: | Line 44: | ||
It appears to be some type of a bug in the BerkleyDB 5.3.x. In an attempt to workaround the problem, when we encounter this situation we attempt to adjust the size of the mmap buffer until the call works, or we end up trying 10 times. | It appears to be some type of a bug in the BerkleyDB 5.3.x. In an attempt to workaround the problem, when we encounter this situation we attempt to adjust the size of the mmap buffer until the call works, or we end up trying 10 times. | ||
- | If DBI debugging is enabled, additional diagnostics are printed, otherwise a basic retry and success message is added to show that the failure was resolved. | + | If DBI debugging is enabled, additional diagnostics are printed, otherwise a basic retry and success message is added to show that the failure was resolved. |
===== Vserver maintanance ===== | ===== Vserver maintanance ===== |