On Oracle Big Data Appliance , bdachecksw/bdacheckcluster report 'cannot open Packages database in /var/lib/rpm'
(Doc ID 1928158.1)
Last updated on NOVEMBER 06, 2019
Applies to:Big Data Appliance Integrated Software - Version 2.1.2 and later
On Oracle Big Data Appliance (BDA) executing bdachecksw or bdacheckcluster commands may report errors like below:
error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages index using db3 - (-30974)
error: cannot open Packages database in /var/lib/rpm
rpmdb errors can be accompanied with prelink errors. These prelink warning messages can be ignored.
In some cases continuous rpm database corruptions may occur. Continuous rpm database corruptions i.e. rpm database corruptions that re-appear after rebuilding them, may be caused by multiple applications/agents concurrently accessing the database.
In may also be the case that "Required package <package> is not valid" messages are reported along with rpm database corruptions. If the rpm database is already corrupted, running bdachecksw may cause a corrupted rpm database to show up as: "Required package <package> is not valid" errors. No package is corrupt in this case but the corrupted rpm database can cause the messages to be thrown.
Note that the rpm database is a database of metadata about installed packages, it has no direct link to the packages themselves. Therefore messages reported as above are not due to a corrupt package and a corrupt/invalid package installation should not corrupt the rpm database.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document