I'm getting this error
RelationshipRecord[22] not in use
executing this command
start r=relationship(22)
delete r
when trying to delete a broken realtionship. With a broken relationship I mean with a deleted start node or destination node. For example I had this reltionship
(10)--->(11)
I deleted the node 11.
(10)--->
Now I want to delete the relationship but I'm getting the error mentioned above.
How can I fix this problem ?
Thanks
Neo4j won't keep around hanging relations- so there will not be a case where you have
(10)--->
The relationship would have been deleted already, hence you get that error while trying to delete it again.
The next day I started working with that the problem dissapeared... May be a cache in the webadmin ... or something similar.
Thanks for all!
Related
I have archive(tar.gz) which was dumped from production neo4j server. Now I want to get this db locally in my computer. I did it in several steps:
I was maked this command: neo4j-admin load --from=<archive-path> --database=<database> [--force](I did it correct, set path to my archive and gave name for database)
2.When I maked previous command then folder in data/databases appeared, that's cool, I thought
Next I was change active db I changed this value:
dbms.active_database=graph.db.test
And when all must work I typed "./neo4j console" it started in localhost:7474 I see that db is my,for example "test" db but all was empty. No node labels, no relations and when I used simple command "MATCH(n) RETURN n" there are no records. But I totally sure that it's must to be not empty.
Question:
What I did incorrect and what I need to do to make it works?
I believe that you are having problems with the param database and the value of dbms.active_database property.
Try using the same value for both:
bin/neo4j-admin load --from=/backups/graph.db/2016-10-02.dump --database=graph.test.db --force
and
dbms.active_database=graph.test.db
after it, restart Neo4j.
You may try refreshing and re-entering your credentials. Also, it may be the case that your file might not be unzipped properly.
I have a small problem in kettle. These are the steps I'm using.
kettle rocks http://imageshack.com/a/img22/7915/ffk9.png
The error is at the second step saying that it's unable to get fields from the previous step because of an error, but the sql in "Table input" step works fine.
Any ideas?
Try this version of mysql java connector(mysql-connector-java-5.1.31-bin.jar). This worked for me, hope will work for you.
I get this when I try to save my test either from QC (ALM connection) or locally.
"Sequence Contains more than one matching element"
I cannot Save As neither.
I use UFT 11.51 on XP.
Question is if anybody else had had this. And if there is any solution or workaround to it.
Thanks in advance,
Mateo
I'm using the Latest 12.02 version of UFT, I faced the same issue, one possible reason for this issue is the Action Name.
In my case I had used an action name as "ArticlePullQuote", called it from another action within the same test and try to save it, QTP throws error "Sequence Contains more than one matching element".
I changed the action name to "ArtPullQuote", and tried to save, it worked fine.
This might not be the solution for all, but give a try.
I am getting the followinge error while cherry-picking a gerrit...does anyone have info on what this means and why would anyone see it?
error: addinfo_cache failed for path 'ROE/NAS/src/abc.c
Looks like this has something to do with the whitespace and EOL. I also got the same issue today and just used the git-->mergetool to resolve the issue based on the following thread - http://git.661346.n2.nabble.com/error-addinfo-cache-failed-during-merge-tp6840473p6840622.html.
The only cause of concern, I now see the entire file modified instead of just the two lines which were part of my cherry-pick changeset.
Run git stash before cherry-picking. It helped at least in my case.
Our Application is an MVC Application. We are using Entity Framework. When I am updating the model to add a table from the database. I am recieving an exception and it says
"An exception of type 'System.ArgumentException' occured while attempting to update from the database. The exception message is: 'An entry with the same key already exists'."
I am not able to figure out what is the problem. Can I have a solution to get over the problem.
I had it just as you did. You probably have two identical nodes: EntitySetMapping. You should remove one and everything will be ok.
I ran into this issue today. It means that you have two definitions of some sort with the same name. In my case, it was a duplicate EntitySetMapping. It happened as a result of me migrating some customizations from an old version of my model into a new version. I copied an EntitySetMapping with custom insert/delete/update mappings, but I didn't think to delete the mapping that had been previously auto-generated by the model designer.
Unfortunately, you won't know you have this problem until the next time you attempt to update from the database, meaning there's potential for this one to go undetected for some time.
In the future, when making significant changes to the model via the XML editor, I would recommend that you do a test database update just to make sure that all is well.
I recently ran into a similar issue with EF6 where this error was occurring and there was no duplicate key anywhere... That were visible in the edmx. What I had to do was right-click in the edmx and select Model Browser. In the Model Browser view and under Model/Entity Types, some lingering entities were there. For some reason, deleting all the entities in the edmx actually didn't do what you would think. Removing these lingering Entities in the Model Browser solved my problem. Hopefully this will solve some people's problems because this type of solution is easy to fix but hard to find.
Probably, there is another table with the same key exists. Can we see the code? Read more on this exception here.
Well, it seems I figured out a fix for my case.
Step 1: I deleted the table from the edmx model that contained the reference or what ever that was causing the error.
Step 2: I right clicked the designer and click "Update Model from Database" again and all was fixed.
FYI, the only way I knew which table to delete was because it was the last one modified since the "Update Model from Database" worked last.
Taken From Here
This is a more detailed answer based on Tazos333's answer.
Finding the actual duplicate is the hardest part. Using Powershell it can be done by:
Get-Content .\models.edmx | Group-Object | Where-Object { $_.Count -gt 1 } | Select -ExpandProperty Name
In order to get as few false positive results as possible, run this only for the <!-- C-S mapping content --> section (copy-pasted in other text file).
Besides scalar properties duplicates (quite normal, since tables might contain the same column names), the duplicate <EntitySetMapping Name="..."> will be very obvious.