search cancel

Symantec Encryption Management Server cluster log shows "Error checking for local changes" and replication stops working


Article ID: 163168


Updated On:


Encryption Management Server


In a particularly busy environment, a warning may appear in the Symantec Encryption Management Server cluster log.

Replication stops working on the cluster member that displays the warning. The first part of the log entry is:

WARN   pgp/cluster[nnnn]: Error checking for local changes

where nnnn is a random number. 

The entry continues with:

ERROR: value "nnnnnnnnn" is out of range for type integer  Where: PL/pgSQL function "movelocalchanges"

where nnnnnnnnn is a number greater than 2147483647.

The warning is repeated several times per second in busy environments.

The full text of the warning is lengthy. Below is an example:


2016/04/18 06:00:36 +02:00  WARN   pgp/cluster[2002]: Error checking for local changes EXCEPTION STACK TRACE: org.postgresql.util.PSQLException: ERROR: value "2147484032" is out of range for type integer  Where: PL/pgSQL function "movelocalchanges" line 34 at assignment     at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(     at org.postgresql.core.v3.QueryExecutorImpl.processResults(     at org.postgresql.core.v3.QueryExecutorImpl.execute(     at org.postgresql.jdbc2.AbstractJdbc2Statement.execute(     at org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(     at org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(     at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)     at sun.reflect.DelegatingMethodAccessorImpl.invoke(     at java.lang.reflect.Method.invoke(     at org.postgresql.ds.jdbc23.AbstractJdbc23PooledConnection$StatementHandler.invoke(     at com.sun.proxy.$Proxy2.executeQuery(Unknown Source)     at com.pgp.ovid.rep.daemon.ChangeCache.moveLocalChanges(     at com.pgp.ovid.rep.daemon.ChangeCache.moveLocalChanges(     at     at


The maximum value of an integer data type in Postgresql is 2147483647. This maximum has been exceeded for the changeid field in the database.


To resolve this issue you must upgrade to Symantec Encryption Management Server 3.3.2 MP13 or above.