db3 error while installing RPM package

[Budhia, Ravi]

Hi,

I'm running RPM 4.0.2 on a ppc-linux machine. When I try to install an RPM
package, I get the following errors:

error: error(-30989) storing record libsvcping.so into Basenames

error: db3 error(-30989) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error,
run
database recovery

error: db3 error(-30989) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error,
run
database recovery

error: error(-30989) storing record libtesttrans.so into Basenames

error: db3 error(-30989) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error,
run
database recovery

error: db3 error(-30989) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error,
run
database recovery

Is there some way to figure out what caused this error, say maybe by looking
into the RPM database.
I have a tar file of the rpm database, if someone knows how to look into the
db.

Thanks in advance!

Ravi

_______________________________________________
Rpm-list mailing list
Rpm-...@redhat.com
https://listman.redhat.com/mailman/listinfo/rpm-list

[Jeff Johnson]

On Mon, Jun 25, 2001 at 11:36:14PM -0700, Budhia, Ravi wrote:
> Hi,
>
> I'm running RPM 4.0.2 on a ppc-linux machine. When I try to install an RPM
> package, I get the following errors:
>
>
>
> error: error(-30989) storing record libsvcping.so into Basenames
>
> error: db3 error(-30989) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error,
> run
> database recovery
>
> error: db3 error(-30989) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error,
> run
> database recovery
>
> error: error(-30989) storing record libtesttrans.so into Basenames
>
> error: db3 error(-30989) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error,
> run
> database recovery
>
> error: db3 error(-30989) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error,
> run
> database recovery
>
>
> Is there some way to figure out what caused this error, say maybe by looking
> into the RPM database.

Not easily, as rpm database problems are very hard to reproduce, and too
much history is required to analyze.

> I have a tar file of the rpm database, if someone knows how to look into the
> db.

Here's basically what's needed (from a similar problem, bugzilla #46025)

------- Additional comments from j...@redhat.com 2001-06-26 13:05:34 -------

You can repair damage in a db3 based rpm database using tools
found in the db3-utils package. For example,
cd /var/lib/rpm
for i in [A-Z]* ; do
echo $i --
db3_verify $i
done
should exhibit the same failure modes. Then you can repair the
damage by doing (assuming Packages is damaged)
cd /var/lib/rpm
mv Package Packages-SAVE
db3_dump Packages-SAVE | db3_load Packages
and verifying as above.

Someday, probably soon, now that db-3.3.4 is part of rpm-4.0.3 librpmdb.a, I'll
figger some way to run recovery from the rpm CLI. Meanwhile, use the db3
utilities to repair.

73 de Jeff

--
Jeff Johnson ARS N3NPQ
j...@jbj.org (j...@redhat.com)
Chapel Hill, NC