Database cleanup error | Community
Skip to main content
Level 3
June 17, 2021
Question

Database cleanup error

  • June 17, 2021
  • 1 reply
  • 1359 views

Recently, the database cleanup workflow always get failed every day. I checked the cleanup.log, There is an error "

PGS-220000 PostgreSQL error: could not receive data from server: Connection timed out\n (iRc=-2006)" after VACUUM ANALYZE, I suppose is there any connection timeout configrates between Adobe campaign server and the postgresql. Is there anyone know the reason of the issue?

 

2021-06-16 14:04:21.959+08      00004CF1        00004CF1          1     info    wdbc    Get: [57381216] SELECT GetDate(), iOptionId, iDataType, sStringValue, iLongValue, dDoubleValue, tsTimeStampValue, mMemoValue FROM XtkOption WHERE sName=:#(1)#

2021-06-16 14:04:21.959+08      00004CF1        00004CF1          2     info    wdbc      Param(0)=XtkCleanup_NoStats

2021-06-16 14:04:21.960+08      00004CF1        00004CF1          1     info    wdbc    ExecDirect: [27786272] VACUUM ANALYZE

2021-06-16 16:15:39.224+08      00004CF1        00004CF1          1     error   log     PGS-220000 PostgreSQL error: could not receive data from server: Connection timed out\n (iRc=-2006)

2021-06-16 16:15:39.224+08      00004CF1        00004CF1          1     error   log     WDB-200001 SQL statement 'VACUUM ANALYZE' could not be executed. (iRc=-2006)

2021-06-16 16:15:39.224+08      00004CF1        00004CF1          1     warning log     Failed to update RDBMS statistics.

2021-06-16 16:15:39.224+08      00004CF1        00004CF1          1     info    wdbc    Get: [57381216] SELECT Count(iTrackingUrlId) FROM NmsTrackingUrl WHERE iType = 2

2021-06-16 16:15:39.224+08      00004CF1        00004CF1          1     error   log     PGS-220000 PostgreSQL error: server closed the connection unexpectedly\n    This probably means the server terminated abnormally\n    before or while processing the request.\n (iRc=-2006)

2021-06-16 16:15:39.224+08      00004CF1        00004CF1          1     error   log     WDB-200001 SQL statement 'SELECT Count(iTrackingUrlId) FROM NmsTrackingUrl WHERE iType = 2' could not be executed. (iRc=-2006)

2021-06-16 16:15:39.228+08      00004CF1        00004CF1          1     info    wdbc    WDBC pool (nms:extAccount:PCDEXT7 prod): 1 connection(s) released, 0 left

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

1 reply

LaurentLam
Level 5
June 17, 2021

Hello,
It seems that ACC try to do a vacuum on a distant database configured with your external account "PCDEXT7 prod".

Check that the DB user account configured on the distant database have the right to do it.

If this is the case, try to set on this distant database a full vacuum as perhaps the performance on it are too downgraded to run the vacuum analyse

Level 3
June 24, 2021
ACC has full access to do the vacuum, this error comes and goes, but it has become more frequent recently