I don't do this a lot myself but I suspect if you remove the --exit-on-error flag from your command line the whole thing will work out.
The import process is trying to grant some sort of permission to the owner "jacobsegv7_analytics" which probably does not exist. However I don't think that particular piece is particularly important to the schema and the kinds of things you want to do.
Alternatively, you could define an account jacobsegv7_analytics in the DB you are importing into (I think)
Unfortunately when I don't have the exit-on-error in the command, the query will run until it eventually times out and freezes my server.
I tried to "create user jacobsegv7_analytics" first to see if that would make any difference, and instead then i just get a different error.
Do you know if there's any way I can connect my reports to JCA itself so I don't have to use PostgreSQL to restore the dmp files at all? I'm trying to run weekly analytics reports for my community and I'm trying to make it as seamless a process as possible.
(by the way, not to totally fangirl, but I was in a couple of your sessions at JiveWorld this year, Josh!)
We don't allow direct access to the analytics DB for query purposes for performance reasons - which is why we require you to download and import the analytics DB.
You also have the option to get cloud analytics set up and potentially use the data export service rather than getting a DB dump - depends a bit on what other infrastructure you have for querying the DB once you get it imported.
I am going to mention Ed Snajder who is a Jiver that may have more insight into the problem you are experiencing to see if he can offer any tips.
I think you you need to add a couple of flags to the restore -O -c this will clean and remove any owner conflicts.
If you want to fully automate this process you can use this thread as a starting point: Re: Script JCA Downloads *shameless plug*
You can also add your weekly queries to the batch script for a set it and forget it experience.
Hello! I'll pull down a copy from JCA and see if I can reproduce the issue. It looks like the expanded DB is almost 75GB, I don't think a clean restore would be that large, but that sort of hanging could be symptomatic of a disk space issue. One thing we could look at is what it is hanging on, the query (while it is hanging):
SELECT now()-query_start, pid, state, waiting, query FROM pg_stat_activity WHERE state != 'idle' ORDER BY query_start;
Another thought, can you add --no-owner to your restore command? I am thinking that it exited on this user error, but this isn't why it is hanging. It's also possible it will hang anyway, and not error out, but let's see what happens. I will let you know how my restore goes as soon as I get it downloaded. Thanks! Ed