Removing corrupt environment without losing database data?

Question

OK, I'm using Berkeley DB 4.3.28, Java API with no transactions or concurrency. We have several environments with multiple databases under them. Occasionally the environment gets corrupted. The original coder didn't understand this had to be coded for, so I'm trying to fix that.
Normally, all database environments are opened with the following settings:
setErrorPrefix(prefix);
setPanicHandler(new EmsPanicHandler(prefix));
setJoinEnvironment(true);
I've recreated the environment corruption and used the following code to remove and recreate the environment (as suggested here: http://www.oracle.com/technology/documentation/berkeley-db/db/ref/cam/fail.html)
          EnvironmentConfig env_config = new EmsEnvironmentConfig("CleanEnvironment");
          env_config.setAllowCreate(true);
                env_config.setErrorPrefix("string");
                env_config.setPanicHandler(new MyPanicHandler());
          Environment m_env_handle = null;
        try {
             File m_file = new File(environment);
             if (!m_file.exists())
                  System.err.println("Environment "+environment+" does not exist. Skipping");
                  return;
             System.out.println("Attempting to remove environment "+environment+" with recovery enabled");
              //m_env_handle = new Environment(m_file, env_config);
             Environment.remove(m_file, true, env_config);
             System.out.println("Attempting to recreate environment");
             m_env_handle = new Environment(m_file, env_config);
        } catch (Throwable t) {
            System.err.println("Exception trying to recover environment "+environment+": "+t.getLocalizedMessage());
        finally
             if (m_env_handle != null)
                  System.out.println("Closing environment "+environment);
                  try {
                       m_env_handle.close();
                       System.out.println("Environment "+environment+" closed successfully");
                  catch (Exception e)
                       System.err.println("Exception trying to close environment "+environment+": "+e.getLocalizedMessage());
        }This removes and recreates the environment without giving me an error message and apparently without touching any of the underlying databases.
Unfortunately, when I try using a database in the environment again, I can open the environment, but I get this error when trying to open the database:
java.lang.IllegalArgumentException: Invalid argument
        at com.sleepycat.db.internal.db_javaJNI.Db_open(Native Method)
        at com.sleepycat.db.internal.Db.open(Db.java:329)
        at com.sleepycat.db.DatabaseConfig.openDatabase(DatabaseConfig.java:478)
        at com.sleepycat.db.Environment.openDatabase(Environment.java:81)
        at com.nmss.db.berkeleydb.Name_Address_Map.open(Name_Address_Map.java:358)
        at com.nmss.db.berkeleydb.Name_Address_Map.retrieveAddress(Name_Address_Map.java:296)
        at com.nmss.framework.inventory.Command.add(Command.java:269)
        at com.nmss.framework.inventory.Command.processArgs(Command.java:59)
        at com.nmss.framework.inventory.Command.<init>(Command.java:39)
        at com.nmss.framework.inventory.Command.main(Command.java:483)The Environment config is the same one I posted at the start of the message:
setErrorPrefix(prefix);
setPanicHandler(new MyPanicHandler(prefix));
setJoinEnvironment(true);
The Database config is:
DatabaseConfig db_config = new DatabaseConfig();
db_config.setType(DatabaseType.BTREE);
db_config.setAllowCreate(true);
Can anyone tell why I would be getting this error? Or does removing the environment simply invalidate any database files that were underneath it?
db_verify used against the database returns 0.
Thanks,
Mike
Message was edited by:
msully
Message was edited by:
msully

Answer 1

So the latest - I totally removed my old databases and rebuilt my app, with the following environment config:
        setErrorPrefix(prefix.toUpperCase());
        setPanicHandler(new EmsPanicHandler(prefix));
        setInitializeCache(true);
        setTransactional(true);
        setInitializeLogging(true);
        setInitializeLocking(true);
        setAllowCreate(true);Now I am getting the error:
/var/tmp: no base system shared memory ID specified
java.lang.IllegalArgumentException: Invalid argument
        at com.sleepycat.db.internal.db_javaJNI.DbEnv_open(Native Method)
        at com.sleepycat.db.internal.DbEnv.open(DbEnv.java:235)
        at com.sleepycat.db.EnvironmentConfig.openEnvironment(EnvironmentConfig.java:714)
        at com.sleepycat.db.Environment.<init>(Environment.java:30)
        at com.nmss.db.berkeleydb.LogHandler.getEnvironment(LogHandler.java:226)
        at com.nmss.db.berkeleydb.LogHandler.open(LogHandler.java:197)
        at com.nmss.db.berkeleydb.LogHandler.store(LogHandler.java:235)
        at com.nmss.util.LogHandlerImpl.publish(LogHandlerImpl.java:45)
        at java.util.logging.Logger.log(Logger.java:452)
        at java.util.logging.Logger.doLog(Logger.java:474)
        at java.util.logging.Logger.logp(Logger.java:590)
        at com.nmss.util.Logger.log(Logger.java:87)
        at com.nmss.framework.inventory.Command.add(Command.java:306)
        at com.nmss.framework.inventory.Command.processArgs(Command.java:59)
        at com.nmss.framework.inventory.Command.<init>(Command.java:39)
        at com.nmss.framework.inventory.Command.main(Command.java:483)