It is recommended to use the same version of oak:jar as your existing crx's oak version. If you're able to bring it up, then you should be able to create packages to export your content/configs. I'm not aware of any other way to restore it.
Thanks for your response. If I run oak-run 1.8.2 to check good revision. I could not find out the lastest good revision. So I tried with oak-run 1.10 and found it. For some instances lost the data, finally I had to build the new ones. There is no way to restore the data for them.
Thanks for your response smacdonald2008, I found that this error usually happened with AEM instances.
Then I tried to use a higher version of oak run package (oak-run v1.10 for AEM 6.4) to fix Inconsistence again, and found out the last good revision again. I removed some records in journal.log file and run compact command again. Finally the AEM instance can run back.
I have more than ten instances need to restore from this same error. Some instances were retored but they don't save any data or configuration. It look like the new AEM instance but some functions didn't work well. Is there any other way to restore the data and configuration settings of AEM instance?
Are you able to start the instance and check if any bundles are not 'Active' and either in 'Installed' or 'Resolved' state? Otherwise you may have to perform the same task via scripts while the server is offline.