Bugzilla – Bug 141931
cannot update to Java 1.4.2
Last modified: 2006-01-25 16:01:13 UTC
When trying to update, I get this error report. The actual report is 124 pages long. too long to put here. ERROR(InstTarget:E_RpmDB_subprocess_failed) warning: /usr/lib/jvm/java-1.4.2-sun-1.4.2.10/jre/lib/security/cacerts created as /usr/lib/jvm/java-1.4.2-sun-1.4.2.10/jre/lib/security/cacerts.rpmnew warning: /usr/lib/jvm/java-1.4.2-sun-1.4.2.10/jre/lib/security/java.policy created as /usr/lib/jvm/java-1.4.2-sun-1.4.2.10/jre/lib/security/java.policy.rpmnew warning: /usr/lib/jvm/java-1.4.2-sun-1.4.2.10/jre/lib/security/java.security created as /usr/lib/jvm/java-1.4.2-sun-1.4.2.10/jre/lib/security/java.security.rpmnew rpmdb: PANIC: Invalid argument rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_put: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) storing record LC_MESSAGES into Basenames rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "es" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "LC_MESSAGES" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "fr" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "LC_MESSAGES" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "it" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "LC_MESSAGES" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "ja" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "LC_MESSAGES" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "ko" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "ko.UTF-8" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "LC_MESSAGES" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "LC_MESSAGES" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery error: db4 error(-30978) from dbcursor->c_get: DB_RUNRECOVERY: Fatal error, run database recovery error: error(-30978) getting "sv" records from Basenames index rpmdb: PANIC: fatal region error detected; run recovery
Thank You for your time, People do not say "thank You" enough anymore. :-)
Seems like the rpm database is corrupt. Try 'rpm --rebuilddb'.
Scott: Did that solve your problem? As I guess it did, I will close this bug as invalid. If not, please feel free to re-open it again. Regards, Daniel