This Solution Provide by Mr. Uzzal Basak
DBA at UCBL :-)
During ASM configuration in RHEL
Problem
[root@Asm Rpm]# rpm -Uvh pdksh-5.2.13-3.i386.rpm
rpmdb: Thread/process 2374/3078154016 failed: locker has write locks
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: Thread/process 2374/3078154016 failed: locker has write locks
error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages database in /var/lib/rpm
Solution:
I tried Tip of chirpy
1. Check for processes holding the rpm database open (usually in MUTEX/FUTEX states):
lsof | grep /var/lib/rpm
If it finds any, kill -9 them all.
2. Delete any temporary DB files:
rm -fv /var/lib/rpm/__*
3. Rebuild your RPM database:
rpm --rebuilddb -v -v
DBA at UCBL :-)
During ASM configuration in RHEL
Problem
[root@Asm Rpm]# rpm -Uvh pdksh-5.2.13-3.i386.rpm
rpmdb: Thread/process 2374/3078154016 failed: locker has write locks
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: Thread/process 2374/3078154016 failed: locker has write locks
error: db3 error(-30974) from dbenv->failchk: DB_RUNRECOVERY: Fatal error, run database recovery
error: cannot open Packages database in /var/lib/rpm
Solution:
I tried Tip of chirpy
1. Check for processes holding the rpm database open (usually in MUTEX/FUTEX states):
lsof | grep /var/lib/rpm
If it finds any, kill -9 them all.
2. Delete any temporary DB files:
rm -fv /var/lib/rpm/__*
3. Rebuild your RPM database:
rpm --rebuilddb -v -v
No comments:
Post a Comment