Cannot execute UNLISTEN during recovery

Follow

Michal Becher

July 29, 2019 12:18

The error message that im experiencing is coming from the Postgres . 

I tried to overcome the issue by adding the parameter to the connection string while connecting to the Postgres. i tried-

 pooling=false  

and also

No Reset On Close=true

 to overcome the issue but it didnt work.

i submitted a ticket but  I need help ASAp.

 

Thank you

0

• 

  Kobbi Gal July 29, 2019 12:30

  It seems that the DB is currently in recovery mode (called 'hot standby') and therefore querying (or LISTEN/UNLISTEN/NOTIFY events) are not possible in this state according to PostgreSQL documentation.

  Try to run the build when the DB is finished its recovery or standby mode.

   

   

   

   

  0

  Comment actions Permalink
• 

  Michael Becker July 29, 2019 12:33

  In most cases you can't switch off hot standby and there is no real window to connect to get around that. I'd suggest creating a mirror of this database on PostGres, which will have hot standby disabled.

  0

  Comment actions Permalink
• 

  Pep Masoliver February 04, 2020 10:07 (Edited February 04, 2020 10:07)

  Hello,

  Any update on how did you solve it? We're suffering the same situation after upgrading to Sisense 8.1 :-(

  Thanks in advance!

  0

  Comment actions Permalink
• 

  Shawn Hilditch March 23, 2020 16:24

  I was able to resolve using the Web ECM and adding the Additional parameter: NoResetOnClose=true

  to all DB connections to the read replica databases we used. No issue with the UNLISTEN error after that.

  There is no way to configure DB parameters in the Desktop ECM, so all cubes had to be updated using Web. When editing tables with custom queries, copy the current query using Edit Table option. Then choose Edit Connection, add the parameter, then select database then add new Custom Query and paste the query from earlier. Click OK the connection will be updated.

  0

  Comment actions Permalink

Please sign in to leave a comment.