Good day,

Worked with my customer on an issue with an OES 2 SP3 server that had a corrupt RPM Database. We followed TID 7004708, to restore the DB to a working condition, we followed the section below the recommended steps to fix, using a backup copy of the RPM Database from October to bring it back to a working state.

A question arose however; how do we (or is there ) a method to sync the RPM DB with the rpm's that were recently installed? For example: we added some new Apache patches that we received from Development, however; running an "rpm -qa <package name> showed an older version.

Is there a method to sync the RPM DB, with the rpm's that are currently on the system, or should we just go ahead and run the updates again on that Server?

Thank you,