Ubuntu 20.04 running multiple databases running with different version numbers in a project in Neo4j Desktop 1.2.7 and need to move them over to a newly installed machine with the latest version of Neo4j Desktop (not sure which version that is because on the SSD that's unplugged right now!).
Tried:
bin/neo4j-admin dump --database="MYDATABASENAME" --to=/dumps/MYDATABASENAME-.dump"
Which gives error "Database does not exist" error as I understand the default database is "neo4j" and that this somehow contains the other databases? Makes no sense to me.
Tried:
bin/neo4j-admin dump --database=neo4j --to=/dumps/DougiDatabases.dump"
...Thinking that the neo4j database may contain all the other databases and that did dump. but the file was only 5Mb or so, where my databases are a number of Gb, so clearly not correct.
In system database I do SHOW DATABASES and it shows me the neo4j and system databases, but nothing else.
I've seen some mention of a dump button in the three dots by a database in Neo4j Desktop, but I don't have that (regardless of DB running or not). I only have a clone option.
Previously I have copied the database files from the /home/MYNAME/.config/Neo4j Desktop/Application/neo4jDatabases folder and then updated the databases listed in the /home/MYNAME/.config/Neo4j Desktop/Application/persist/databases.json, but it seems that the folder structure in the latest version of Neo4j Desktop has a different structure, so I wasn't sure if I could still do this. Not tried.
Driving me mad. This should be so easy.
What do I do please?
I worked it out. For databases 3.x you need to use "graph.db" as the database name. For databases 4.x you always use "neo4j" as the database name.
e.g.
bin/neo4j-admin dump --database="graph.db" --to="/dumpsFolder/myDatabase.dump"
bin/neo4j-admin dump --database="neo4j" --to="/dumpsFolder/myDatabase.dump"
You need to to into the admin area for each database, launch the terminal and execute these commands. In the latest version of Neo4j Desktop you can then copy the dump files into the root of the project. e.g.
/home/USERNAME/.config/Neo4j Desktop/Application/projects/project-XXX
Then click the ... next to the dump name in Neo4j Desktop and "create from dump file" or similar. You select the database version, name it, set a password and continue. The database will restore.
Related
I have a db backup folder that I'm trying to load into a new db in Neo4J Desktop.
You'll need to use the neo4j-admin tool
From Neo4j desktop, go to your database/create a new one, then open the Terminal for that database (in older versions, it was in the Manage menu, in newer versions, you'll find it in the 3 ... menu)
Once you have the terminal open, cd bin and follow the manual to restore
I am upgrading my local machine from Ubuntu 16.04 to 20.04. I run Neo4j Desktop (version 1.2.7) on my 16.04 and have installed it on the 20.04 machine and want to move the databases over.
I'm sure that in the past I just copied and pasted the database folders in /home/dougi/.config/Neo4j Desktop/Application/neo4jDatabases from one computer to the other and started Neo4j Desktop. However, when I do that no database show in the project.
I tried doing a dump and load, but couldn't see how I would load the database into Neo4j Desktop on the 20.04 machine as you have to "create" a database for it to show in the project and the database version when creating is limited to 4.0.3 and all of my databases are earlier versions than that (I don't want upgrade them right now).
I tried creating a database, deleting the files in the folder created in /home/dougi/.config/Neo4j Desktop/Application/neo4jDatabases and pasting the database folder from the 16.04 machine into it (i.e. replacing the files it created). I just get a message saying that the database files have been moved or corrupted when I load Neo4j Desktop.
I tried running a load from a dump I had made and had an error saying WARNING: Max 1024 open files allowed, minimum of 40 000 recommended.. I did find some google articles on that, but this felt like a really messy way of doing the restore so I didn't go any further with that.
What is the easiest way to move Neo4j Desktop databases from one computer to another please?
Thank you!
OK, so the answer to this is that there is a file /home/dougi/.config/Neo4j Desktop/Application/persist/databases.json which contains the list of databases that display in Neo4j Desktop.
Create a new database to add an entry to the file and then copy and paste that entry, replacing the database ID and version with those of the new databases you are adding files for to create an entry for each of the databases.
Restart your computer and delete the temporary database you created.
Or you could just copy the file from your previous version of Neo4j Desktop, assuming there are no formatting changes between versions of Neo4j Desktop.
HI i am using a aws ec2 to run a neo4j server. Before that I test in my local machine (Mac OS). everything works fine. But when I uploaded the same graph.db to ec2 and call db.schema(), there are some non-exists relationships. I acknowledge these relationships exist in my old graph.db. but I already deleted the whole graph.db file before load again. So I am wondering there are may be cached by neo4j? I run some queries for the relationships, there are do have some nodes show up. How can I fix this?
This is a long-standing issue that has was reported in version 3.2.2 and still apparently exists in 4.0.0.
I am trying to get the Paradise Papers running on an AWS cloud server. I installed Neo4j Desktop on my mac, and commissioned a server by deploying the AMI from https://aws.amazon.com/marketplace/pp/B071P26C9D.
I then copied the data from the Desktop install to the cloud install, updated the neo4j.template file to point to the new directory, and restarted the service.
The problem is that I can no longer connect to the server. In the log files I can see the following lines (along with a lot of diagnostic information).
2018-09-30 07:41:59.920+0000 INFO [o.n.k.i.f.CommunityEditionModule] No locking implementation specified, defaulting to 'community'
2018-09-30 07:42:00.104+0000 INFO [o.n.k.AvailabilityGuard] Requirement makes database unavailable: Database available
I suspect that there may be some kind of licensing or version constraint that is preventing the database from running. Could this be possible? Or is it something else?
Your issue is not related with a licensing or version problem.
In your debug.log, I don't see any message that can explained your issue.
Is there something useful in the neo4j.log file ?
Can you try to start neo4j after after removing all your plugins (apoc) ?
Can you try to start Neo4j on an empty database ?
Cheers
So I just need to direction on understanding a postgres installation better, because clearly I only know enough to be dangerous.
I had an app that was my project with a postgres DB installed via homebrew
Then I started collaborating on a project with other people
There was some difficulty getting my existing prostgres install to work with the new project so I installed the postgres app with the gui interface to start stop the db.
That new project is finished and I wanted to get back to work on my other project
When I started the first app up, it couldn't find a db. I tried drop the db, and recreating it, but when I run the migrations it says the tables already exist.
What can I do to get around this?
A good approach would be using Docker so everyone have the same environment. This would mean even you, across your machines or your working colleagues or collaborators would have the same environment. You could have many containers running (watching exposing different ports for Postgres, i.e: 5433...) and when a project finishes just get rid of the container.
This approach saves you the overhead of having to maintain multiple databases locally or depending on a running Postgres process (which I sometimes forget to start).
If you need to solve this locally, try starting your postgres service, connecting to your localhost instance and running:
> psql
psql (9.6.2)
Type "help" for help.
> \l
and you should see all of your databases and debug them. Perhaps deleting and creating the conflicting database (if you don't need your local data) could help.