Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 PRADEEP CHOWDARY PYDI (PradeepPydi)
Anthem
Senior PEGA DEVOPS and Cloud Administrator
Anthem
US
PradeepPydi Member since 2017 240 posts
Anthem
Posted: Oct 2, 2018
Last activity: Oct 12, 2018
Posted: 2 Oct 2018 20:53 EDT
Last activity: 12 Oct 2018 9:46 EDT
Closed

Database server crash - Application JVM's auto switch to Disaster Recovery DB.

Hi Team,

Application Details : PRPC 731,Tomcat 8.5.13 and MSSQL.

In our production environment,Database server has been crashed recently and the application JVM's DB pointing has been changed manually to Disaster Recovery Database during which JVM's has been brought down which caused outage for the end user.

Please suggest any recommended solutions for the automated application JVM's switch over to Disaster Recovery Database without any user impact.

To see attachments, please log in.
Data Integration
System Administration

Posted: 6 years ago
Posted: 12 Oct 2018 5:23 EDT
Xavier Merlin (MERLX)
PEGA
Principal Software Solutions Engineer
PEG
GB

Pega should not be handling it. In fact I would argue you don't want Pega handling it.

Check Microsoft SQL server documentation about JDBC url.

Download the PDF available there:

https://docs.microsoft.com/en-us/sql/connect/jdbc/frequently-asked-questions-faq-for-jdbc-driver?view=sql-server-2017

There is plenty of information. Look at page 179 about url connection details and then for "failover".

This should be done by configuring JDBC url which is typically done in the application server you use.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice