Question

7
Replies
1129
Views
Posted: 1 year agoUpdated: 1 month ago

There is no configuration (no Data-Admin-DB-Name instance) for database

I'm trying to create a Pega marketing application on Pega personal edition 7.3.1 - I have installed Pega Marketing and successfully completed all tasks mentioned on Pega marketing installation guide. When I'm trying to create a Pega marketing application, I'm facing 'There is no configuration (no Data-Admin-DB-Name instance) for database' - error. Please find the attachments for my tracer log, prconfig.xml and context.xml. Kindly identify any mistakes. TIA.

App server : TOMCAT.

DB : Postgres.

I have attached the XML files as txt files.

***Edited by Moderator Marissa to update platform capability tags****

Posted: 1 year ago

Hi Prathi, 


Given it's a configuration / installation related issue. Its difficult to give guidance without looking at environment etc.,


I would recommend you to create a support ticket / SR and work with Pega support to get more help on this.


 
Posted: 4 months ago

Hello Prathi,


I am facing the same issue and weird thing is it is working in one node and not working in other node in cluster environment. I compared both context.xml and prconfig.xml files both looks exactly same. please let me know if you got the resolution for your issue


Thanks in advance


Regards


Sai P Yakkali
Posted: 4 months ago

Hi,


Instead of the below entry in the prconfig.xml:



<env name="database/databases/ExternalMKTData/dataSource" value="java:comp/env/jdbc/PegaRULES"/>


Could you please try the below:


<env name="database/databases/ExternamMKTData/dataSource" value="jdbc/PegaRules"/>


After doing this please restart the cluster.


Thanks.
Posted: 1 month ago

Hello,


Please review all the instances of Data-Admin-DB-Name and rectify if any problems found there.


Thank you,

Pawan
Posted: 1 week ago

Hi, 

Is there any update on why this issue is coming up. We are facing this issue when the user tries to open the Campaign dashboard and view the campaigns. We are not able to replicate the scenario all the time, it occurs when we log in after a while or if a new operator logs in for the first time and tries to access the campaign dashboard.

 

Thanks