Hi Kiran,

If you set an error stream with DbEnv::set_errfile or
DbEnv::set_error_stream, is there any output before the panic?

If not, can you try editing env_open.c and adding some output before
each "goto err" in __dbenv_open? That would tell us give us some more
information about where the error is occurring.

Regards,
Michael.

Hi Kiran,

For support with critical problems, please contact
support (AT) sleepycat (DOT) com. You will get a quicker response that way than
you will through the newsgroup.

That said, the problem here appears to be that you have two different
environment directories: DB1 and DB2. Does your application rename
directories for some reason (as part of a backup strategy, for
example)?

It appears from the logs that you use absolute path names for databases
in your calls to DB->open. Is that correct?

If you want to be able to rename or copy the contents of an environment
directory to another location, be sure to only use relative path names
for the databases (relative to the environment directory, or any
directories configured with DB_ENV->set_data_dir).

If this does not resolve the problem, please send mail to support AT
sleepycat.com with more details.

Regards,
Michael.