Good to know. Thank you!
I keep getting errors on the following command:
blastdbcheck -db nt.00
Writing messages to <stdout> at verbosity (Summary) ISAM testing is ENABLED. Legacy testing is DISABLED. By default, testing 200 randomly sampled OIDs. Testing 1 volume(s). /home/envdev/data/blast/db/nt.00 / MetaData: [ERROR] caught exception. Result=FAILURE. 1 errors reported in 1 volume(s). Testing 0 alias(es). Result=SUCCESS. No errors reported for 0 alias(es). Total errors: 1
I downloaded via the update script, checked the md5 checksum, and unzipped the file.
Anyone seen this?
The box has 48 GB of memory.
Thanks!
Matt
2 answers
I have never used the blastdbcheck command before, but I just tried it with all my blast databases (some from the NCBI, some custom made) and different tests (random, ends) and got the same error message. So it seems to be a general problem with blastdbcheck.
I agree, I just tested with the native ncbi nr blastdb ang got the same error
Still getting this error when running blastdbcheck on the native NCBI nt database, over a year later. This page is currently the top google result for "blastdbcmd"
Are you doing
blastdbcheck -db nt.00
or
blastdbcheck -db nt
The first isn't a database whereas the second is..
Years after but error still persists. In the following link you can find a solution provided by user "carlosproca", which just worked for me. It is something related to taxon id files.
Log in to answer this question.
the same error