Also in order to detect the problems in other permissions on other tables I ran this query:
SELECT *
FROM pg_tables t
WHERE t.tableowner <> ‘dhis’ – dhis is my DHIS2 db user
and schemaname = ‘public’;
I discovered there’s also the table public.spatial_ref_sys that was not under my dhis db user, so I altered its owner too.
Thanks for the help.
All the best,
Bernard
Bernard Sadaka
Information Management Advisor
Première Urgence - Aide Médicale Internationale
Nehmeh Building, Sanine Street, Chiyah, 3rd Floor
Ain el Remmaneh, Beirut, Lebanon
E-mail: lib.ima@pu-ami.org
Cell: +961 71 004 881 (208)
Skype: imapuami
Website: https://www.pu-ami.org
···
From: Stian Sandvold [mailto:stian@dhis2.org]
Sent: Monday, September 17, 2018 03:28 PM
To: Bob Jolliffe bobjolliffe@gmail.com
Cc: lib.ima@pu-ami.org; DHIS 2 Users list dhis2-users@lists.launchpad.net; DHIS 2 Developers list dhis2-devs@lists.launchpad.net
Subject: Re: [Dhis2-users] [Dhis2-devs] Error when upgrading DHIS2 from 2.29 to 2.30 - relationships
Did the sql fix your issues or are you still having issues? The superuser and ownership is a tricky challenge since we dont know the name of the user, but aside from the postgis extension, the upgradescript should be runnable as a non-superuser if I remember correctly.
On Mon, Sep 17, 2018 at 12:36 PM Bob Jolliffe bobjolliffe@gmail.com wrote:
Good point Bernard.
Interestingly this is the reverse problem to that of creating the postgis extension. You have to be a superuser role in the database to create the postgis extension in the database. But …
If you have run the upgrade script from https://github.com/dhis2/dhis2-releases/blob/master/releases/2.30/upgrade-230.sql as a superuser (eg postgres) then you are going to be left with two new tables (and a function?) owned by the postgres user.
So you should, in fact, have to do afterwards both:
ALTER TABLE public.relationshipitem OWNER to dhis;
ALTER TABLE public.relationshipconstraint OWNER to dhis;
Which is a little messy 
But hard to figure the neatest way around because we cannot know in advance the name of the dhis db user.
Cheers
Bob
On 17 September 2018 at 09:58, Bernard Sadaka (IM Advisor) lib.ima@pu-ami.org wrote:
I faced this same error before: “'permission denied for relation XXX”
and I fixed it using this query in the DB:
ALTER TABLE public.relationshipitem OWNER to dhis;
Replace dhis with your DB user
All the best,
Bernard
![cid:image002.png@01D36F50.572585A0]()
Bernard Sadaka
Information Management Advisor
Première Urgence - Aide Médicale Internationale
Nehmeh Building, Sanine Street, Chiyah, 3rd Floor
Ain el Remmaneh, Beirut, Lebanon
E-mail: lib.ima@pu-ami.org
Cell: +961 71 004 881 (208)
Skype: imapuami
Website: https://www.pu-ami.org
From: Dhis2-users [mailto:dhis2-users-bounces+lib.ima=pu-ami.org@lists.launchpad.net] On Behalf Of Em Le Hong
Sent: Monday, September 17, 2018 11:51 AM
To: Shurajit Dutta shurajitdutta@gmail.com; DHIS 2 Developers list dhis2-devs@lists.launchpad.net
Cc: DHIS 2 Users list dhis2-users@lists.launchpad.net
Subject: Re: [Dhis2-users] Error when upgrading DHIS2 from 2.29 to 2.30 - relationships
Hi all,
I got the same problem with Nick.
It says ‘permission denied for relation relationshipitem’,
![image.png]()
On Tue, Sep 11, 2018 at 11:18 PM Shurajit Dutta shurajitdutta@gmail.com wrote:
Hi everyone,
I am trying to upgrade a DHIS2 instance from 2.29 to 2.30. I have done this on a couple other instances successfully. The issue I seem to be having here is with the relationship types. In 2.29, I have the following relationships:
![image.png]()
This changes to the following (as per the release notes this is expected) in 2.30:
![image.png]()
There are a couple issues I seem to be running into.
- I can not seem to edit these relationship types at all (the log error says “permission denied for relation relationshipconstraint”
![image.png]()
- I can not seem to open any tracker programs in tracker capture (the log error says “permission denied for relation relationshipitem”)
![image.png]()
Has anyone encountered this error? Any suggestions on how to fix it?
Thanks
–
Shurajit Dutta (MPH, MHI)
Health Information Systems Adviser
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Em Le Hong
DHIS2 Implementation| **HISP Vietnam **
em.hispvietnam@gmail.com | Skype: em.hispvietnam@gmail.com
![Image removed by sender.]()
Mailing list: https://launchpad.net/~dhis2-devs
Post to : dhis2-devs@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-devs
More help : https://help.launchpad.net/ListHelp
Mailing list: https://launchpad.net/~dhis2-users
Post to : dhis2-users@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dhis2-users
More help : https://help.launchpad.net/ListHelp
–
Stian Sandvold
Software developer, DHIS2
University of Oslo
http://www.dhis2.org
But hard to figure the neatest way around because we cannot know in advance the name of the dhis db user.
But hard to figure the neatest way around because we cannot know in advance the name of the dhis db user.