>>Haven't thought of this, but I fixed the problem after I posted this message.
>And where was the problem?

It looks like someone copied the table from another location (same DBC) to the different location. So, the file was already there, but it was pointing to the wrong database. I first freed this table, then deleted the files, now the problem seems to be corrected.