Are you running single or cluster mode? Do you still have the messages.log file and the tx logs from when it happened?
Can you drop the indexes ? Otherwise delete the schema/index directory and they should be rebuild. It can be that you have to reissue the create index/constraint statements. Michael > Am 14.05.2015 um 07:02 schrieb Mike Holdsworth <[email protected]>: > > > Looking at the schema for this node, there are duplicate internal indexes. I > tried dropping the apiKey and the code key indexes under separate operations > and both times Neo4j said there was an internal error and I then had to > restart it to recover. FWIW these indexes are annotated on SDN classes and I > have no idea how this situation occurred. Neo4j 2.1.5 > > > Is there any corrective action I can take here short of trashing the > database? > > neo4j-sh (?)$ schema -l :FDCompany > Indexes > ON :FDCompany(apiKey) ONLINE > ON :FDCompany(name) ONLINE > ON :FDCompany(apiKey) ONLINE > ON :FDCompany(apiKey) ONLINE > ON :FDCompany(code) ONLINE (for uniqueness constraint) > ON :FDCompany(code) ONLINE (for uniqueness constraint) > ON :FDCompany(code) ONLINE (for uniqueness constraint) > > Constraints > ON (fdcompany:FDCompany) ASSERT fdcompany.code IS UNIQUE > > > > -- > You received this message because you are subscribed to the Google Groups > "Neo4j" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "Neo4j" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
