Sorry, although I know this is the mongodb section and I use tokumx, I checked online that tokumx and mongodb are actually the same, so I can only ask questions here.
I have a station group website program that uses the tokumx database. The database has about 6 million data. Recently, because the server is unstable, I want to move the database. I used the dump backup command and restored it with mongorestore. , I kept encountering errors and failed to recover successfully. The problems encountered are as follows:
Every time you restore to a certain program, the following error message will appear:
INVALID OBJECT - going try and pring out
size: 3077
name : _id 18
_id: 1495819
name : body 2
body: "
<h1> Fix ajscaxs2m75.js
error</h1>
<p>ajscaxs2m75.js
Description :</p>
<p>ajscaxs2m75.js
is a process from unknown product, unknown co..."
name : cahegoryidA 18
cahegoryidA: 7138414316591513600
Mon Oct 10 13:03:34.102 Assertion: 10320:BSONElement: bad type 111
0xe86096 0xad16bd 0xacd88c 0x6ceba7 0x719983 0x6d6ec0 0x6d6d6b 0x6d6d6b 0x6d8b03 0x71a09e 0x6af30d 0x6aeb2d 0x7fda07542b45 0x6c8b32
mongorestore(_ZN5mongo15printStackTraceERSo 0x26) [0xe86096]
mongorestore(_ZN5mongo10logContextEPKc 0xfd) [0xad16bd]
mongorestore(_ZN5mongo11msgassertedEiPKc 0x9c) [0xacd88c]
mongorestore(_ZNK5mongo11BSONElement4sizeEv 0x197) [0x6ceba7]
mongorestore(_ZN5mongo8BSONTool11processFileERKN5boost10filesystem4pathE 0x5c3) [0x719983]
mongorestore(_ZN7Restore9drillDownEN5boost10filesystem4pathEbbb 0x1170) [0x6d6ec0]
mongorestore(_ZN7Restore9drillDownEN5boost10filesystem4pathEbbb 0x101b) [0x6d6d6b]
mongorestore(_ZN7Restore9drillDownEN5boost10filesystem4pathEbbb 0x101b) [0x6d6d6b]
mongorestore(_ZN7Restore5doRunEv 0x613) [0x6d8b03]
mongorestore(_ZN5mongo8BSONTool3runEv 0x18e) [0x71a09e]
mongorestore(_ZN5mongo4Tool4mainEiPPc 0x6cd) [0x6af30d]
mongorestore(main 0x2d) [0x6aeb2d]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main 0xf5) [0x7fda07542b45]
mongorestore() [0x6c8b32]
assertion: 10320 BSONElement: bad type 111
I changed 3 servers and got the same error under the same debian 64-bit system. I began to suspect that there was something wrong with the original database. I wanted to try to use the robomongo tool to connect to the database to delete it, but the problem I encountered now is that the database It can be connected, and the website opens normally, but after using robomongo to connect, search or delete the code to delete ajscaxs2m75.js article, and found that the information returned is the same error code assertion: 10320 BSONElement: bad type 111, how to solve this situation?
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
I can’t solve the problem you encountered, but I think it is necessary to explain some problems.
First of all, MongoDB and TokuMX are two companies. The latter is independently maintained and operated by forking the community version of MongoDB 2.4, and has no direct connection with MongoDB. Although most of the commands are still the same, the internal mechanism is very different. So asking questions about tokumx in the mongodb forum is likely to get no answers.
Besides, there are not many users using TokuMX. Now this company has been acquired by Percona due to operational problems. If you want professional help, you can ask Percona for help.