makeblastdb error: Error: (803.7) [makeblastdb] Blast-def-line-set.E.seqid.E.local.str Bad char [0xC3] in string at byte 45
1
2
Entering edit mode
6.9 years ago
m.rhodes ▴ 50

I'm trying to make a blastdb out of fungal ITS sequences from UNITE (https://unite.ut.ee/index.php). I downloaded the general fasta file and edited the fasta headers so they look like this:

GQ280590|Calonectria_leucothoës

DQ675574|Epichloë_sibirici

e.t.c.

However, when I run this makeblastdb command:

./makeblastdb -in unite_fungi.fasta -out UNITE_ITS.fasta -dbtype nucl -parse_seqids

I am getting the following error for all entries:

Error: (803.7) [makeblastdb] Blast-def-line-set.E.seqid.E.local.str

Bad char [0xAB] in string at byte 46.

Initially I thought it could be something to do with tabs/spaces at the end of the header, so I tried removing them using (please correct me if I'm wrong):

sed 's/[[:blank:]]*$//'

However, this did not work either.

Does anyone know why this might be happening?

Thanks in advance.

makeblastdb blast ncbi • 6.7k views
ADD COMMENT
0
Entering edit mode

Wonder if the issue is using non-US character set.

ADD REPLY
0
Entering edit mode

could you please elaborate?

ADD REPLY
1
Entering edit mode

Do you know what unicode character set you are using on this machine? The error you have posted above seems to be referring to this character.

ADD REPLY
0
Entering edit mode

No, but that link helped solve my problem! Turns out it was the 'ë' characters in the fasta headers that were causing the problem. Thanks for the help!

ADD REPLY
2
Entering edit mode
3.9 years ago
flyingfinger ▴ 20

I had the same error but with a different special char.

You can get rid of any/all non-ascii chars by doing something like this:

cat my_file.fasta | perl -ne 's/[^\x00-\x7F]+/ /g; print;' > tmp.fasta

Running makeblastdb on the temp file ran without the errors for me.

ADD COMMENT

Login before adding your answer.

Traffic: 1483 users visited in the last hour
Help About
FAQ
Access RSS
API
Stats

Use of this site constitutes acceptance of our User Agreement and Privacy Policy.

Powered by the version 2.3.6