Hopefully the DbDump and DbLoad utilities willl help you recover and reload your data. Start http://docs.oracle.com/cd/E17277_02/html/GettingStartedGuide/commandlinetools.html#DbDump, or with DbDump at http://docs.oracle.com/cd/E17277_02/html/java/com/sleepycat/je/util/DbDump.html, and try first the -r and then the -R options.
You are using a really old release of JE (3.3.82). Although upgrading to a new release won't fix this problem in the database, once you recover your data (using DbScavenger as my colleague Linda suggested), you should still upgrade to help prevent this from occurring in the future. But first, you'll have to recover your data from the disk corruption that has occurred.
To add to what Charles and Linda have said, I see that file 00000000.jdb has at least two corrupt locations. This indicates you had a storage device or file system failure of some kind. If you can recover your data, you should restore to a disk that you know is working properly.
As an alternative to using DbDump as Linda suggested, you could try restoring file 00000000.jdb from a backup, if it is the only file that is corrupt. But first be sure that the backup and other .jdb files are not corrupt by running DbPrintLog to read these files and check for errors. You can discard the output to stdout from DbPrintLog, since any exceptions (such as the DbChecksumException) will be printed to stderr. (In later releases, DbVerifyLog should be used instead of DbPrintLog.)
The way you said, I have successfully repaired it. Thank you very much! Steps are as follows:
1./usr/local/jdk/bin/java -cp "/godbk/deploy/crawler-war/WEB-INF/lib/je-3.3.82.jar" com.sleepycat.je.util.DbDump -h . -r -s wm_cyolcn
2.Clear the old files(*.jdb,*.lck),in addition to the dump file.
3./usr/local/jdk/bin/java -cp "/godbk/deploy/crawler-war/WEB-INF/lib/je-3.3.82.jar" com.sleepycat.je.util.DbLoad -c dupsort=false -h . -s wm_cyolcn -f wm_cyolcn.dump -v