Qlik Fix: How To Check For Missing Database Listeners in Qlik Sense on Windows
This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.
Qlik Sense Enterprise on Windows relies on database listeners to notify nodes when changes have occurred. It is possible for these connections to be silently closed in the environment, so this video will show how we can identify if a listener has been closed.
Here is a link to more information in the Support Knowledge Base:
Hi and welcome to Qlik Fix! Qlik Sense Enterprise on Windows relies on database listeners to notify nodes when changes have occurred. It is possible for these connections to be silently closed in the environment, so this video will show how we can identify if a listener has been closed. First, we want to make sure that all nodes are showing as “Online” in the QMC. Otherwise this will affect the result of the query we will run later in the video. In this environment, there are currently four nodes including the central, and they all show as “Online” with all services running properly. Now to run the query, we open PGadmin and connect to the QSR database. Right-click on it and select the “Query Tool” Next copy the SQL query from the Qlik Community knowledge base article on “How To Check For Missing Database Listeners...”, and paste it in PGAdmin's query editor. After running the query the output will show the list of node IPs with an associated listener. It will also show how many nodes you have in total and how many listeners are opened. Normally there should be one listeners per node. However in this case, we can see that there are only three listeners for a total of four nodes. This means one database listener is missing. A quick fix is to restart the Qlik Sense Repository Service on the affected rim node. However, for a more permanent fix, open the QlikSenseUtil.exe program under this location (C:\Program Files\Qlik\Sense\Repository\Util\QlikSenseUtil) Then select “Connection String Editor” and then the Read button. Next, add the parameter Keep Alive=30 at the end of these two connection string. This will ensure that these database connections remain open by sending periodic keep alive packets. Now we can restart the Qlik Sense Repository Service for the change to take effect. Remember to repeat these steps on all remaining rim nodes. If you’d like more information, Take advantage of the expertise of peers, product experts, and technical support engineers by asking a question in a Qlik Product Forum on Qlik Community. Or search for answers using the new SearchUnify tool. It searches across our Knowledge Base, Qlik Help, Qlik Community, Qlik YouTube channels and more, all from one place. Also check out the Support Programs space. Here you can learn directly from Qlik experts via a Support webinar, like Techspert Thursdays. And don’t forget to subscribe to the Support Updates Blog. Thanks for watching. Nailed it!
Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.