ERROR: permission denied for relation pr_data_admin
Hi,
I've followed recommendations (Pega721_Install_Tomcat_PostgreSQL.pdf) by creating two users for my pega database:
- base user
- admin user
Here are the grants:
grant usage on schema pegadata to pega_appli;
grant usage on schema pegarules to pega_appli;
grant all on all tables in schema pegarules to pega_appli;
grant all on all tables in schema pegadata to pega_appli;
grant execute on all functions in schema pegarules to pega_appli;
grant execute on all functions in schema pegadata to pega_appli;
After the installation, I've started PRPC but I've got errors like:
SEVERE: Unable to connect to database. Will only use properties from file.
org.postgresql.util.PSQLException: ERROR: permission denied for relation pr_data_admin
I've re-executed the grants and it works. Can you tell me if it's the right way to proceed? Thanks
***Updated by Moderator: Marissa to update categories***
Accepted Solution
Capgemini
FR
Hi,
Here's the SR number : SR-B13619 and the answer:
"prconfig" is missing from the beginning of the Environment element's name attribute. May be this needs changes in document we will work on that as well. Can you incorporate these changes in context.xml and confirm us if this fixes the issue.
We will try these changes today.
Regards
Capgemini
FR
Hi,
I've got also same errors when I've imported the LSFoundation (PegaLSIFCore_v0721.jar) on Designer Studio (in attachment).
When using admin user, it works.
So, do I need to use admin user when importing any application (in this case, I will need to update the datasource of my tomcat instance and restart...) or is it only for the first installation of Pega and his components? Thanks
Pegasystems Inc.
US
Do you want to maintain two users? If not, an admin user is all you need. Base user is needed for environments where stricter access limits must be enforced.
Pegasystems Inc.
US
If the package you are importing requires privileges that only admin user has such as schema changes then yes you'll need to use admin user. base user will be used for running Pega application. E.g A RAP import that doesn't have schema changes will not require Admin user.
Capgemini
FR
Ok, I understand. Thanks for your answer DHEEV. It's a little bit restrictive when I'll need to import a package: depending on the impact on the schema (admin privileges or not?), I'll have to switch between base user and admin user when I will import the package (it means that I'll need to restart all Pega instances when changing the user in my tomcat datasource...)
Maybe I can use the prpcUtils.sh script for importing packages with the admin user...
Pegasystems Inc.
US
If you configure your tomcat with two datasources - jdbc/PegaRULES and jdbc/AdminPegaRULEs, Pega should automatically use the Admin datasource for operations that require additional privileges.
Using prpcUtils.sh to perform imports is certainly a good idea and you can automate your migration using scripting. Even better option is to use prpcServiceUtils - https://github.com/pegasystems/service-utilities
Capgemini
FR
It's exactly what I've done :
<Resource name="jdbc/PegaRULES"
auth="Container"
type="javax.sql.DataSource"
driverClassName="org.postgresql.Driver"
url="jdbc:postgresql://pegadb:5432/pega"
username="pega_appli"
password="XXXXXXX"
maxActive="100"
maxIdle="30"
maxWait="10000"
/>
<Resource name="jdbc/AdminPegaRULES"
auth="Container"
type="javax.sql.DataSource"
driverClassName="org.postgresql.Driver"
url="jdbc:postgresql://pegadb:5432/pega"
username="pega_admin"
password="XXXXXXX"
maxActive="10"
maxIdle="5"
maxWait="5000"
/>
So I don't understand why... I will see tomorrow with our Pega architect.
And of course, it will be nice to automate all these imports but I'm a newbie and it will take a long time before it works.
But thanks for yours answers ;)
Capgemini
FR
Hi,
Pega team told us that it's a bug from Pega. They will create a case for that (we can't do it by ourself because we don't have access to the support right now). I will give you the case ID when Pega team will send to me.
Pegasystems Inc.
IN
Hi PandourangamA,
It would be very helpful if you could share the SR number here for us to track the issue better.
Thank you for your cooperation.
~Vidyaranjan A V | Community Moderator | PegaProductSupport | Pegasystems Inc.
Accepted Solution
Capgemini
FR
Hi,
Here's the SR number : SR-B13619 and the answer:
"prconfig" is missing from the beginning of the Environment element's name attribute. May be this needs changes in document we will work on that as well. Can you incorporate these changes in context.xml and confirm us if this fixes the issue.
We will try these changes today.
Regards
Pegasystems Inc.
IN
Hello!
Thanks for the update. I have updated your original post to reflect this information.
Regards,
Lochan | Community Moderator | Pegasystems Inc.
Pegasystems Inc.
US