Pivotal Knowledge Base

Follow

Fatal- Database is not accepting commands to avoid wraparound data loss in database XXX

Environment

  • Pivotal Greenplum 4
  • Pivotal Greenplum 5

Symptom

Greenplum stops accepting connections and the following error is displayed when a connection is attempted:

Database is not accepting commands to avoid wraparound data loss in database "XXXX"

Cause

This error means that the database age has gotten too close (over the xid_stop_limit) to the wraparound limit and all connections to this or any other database in the cluster are refused to protect it from a potential xid wraparound scenario. This article explains in detail why and when can this error message be seen.

Resolution

In order to regain access to the database and run VACUUM FREEZE, the xid_stop_limit will have to be momentarily lowered. This is described in the section "Recovering from a Transaction ID Limit Error" on the following page from our official documentation.

To find the tables or databases which need to be vacuumed, refer to the following article.

 

Comments

Powered by Zendesk