Postgres Pro
Downloads
Home   >   mailing lists

Re: DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error. - Mailing list pgsql-general

From raghu ram
Subject Re: DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error.
Date
Msg-id CALnrrJSDMCedy24MW1V10_CvjSYdfARYB0tJi2-bA6C=xKN8GA@mail.gmail.com
Whole thread Raw
In response to DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error.  (Olga Vingurt <olgavi@checkpoint.com>)
Responses Re: DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error.
Re: DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error.
List pgsql-general
Tree view


On Mon, Jul 16, 2012 at 5:44 PM, Olga Vingurt <olgavi@checkpoint.com> wrote:

Hi,

 

We are using PostgreSQL 8.3 on Windows Server.

The db crashed and now it fails to start up.

 

The error is:

FATAL:  could not access status of transaction 4020264

DETAIL:  Could not read from file "pg_clog/0003" at offset 212992: No error.

 

Additional log from event viewer:

LOG:  database system was interrupted; last known up at 2012-07-12 11:35:00 CEST

 

 

How can we recover from the current state?

 



Please perform below steps:

1. Backup the current pg_clog/0003 file in different directory

2. Create a file by assumption of  make the uncommitted record as they haven't been committed. command as follows:

dd if=/dev/zero of=<data directory location>/pg_clog/0003   bs=256K count=1 

3. Start the Cluster


--

Thanks & Regards,

Raghu Ram

EnterpriseDB Corporation

Blog:http://raghurc.blogspot.in/



pgsql-general by date:

Previous
From: Nicolau Roca
Date:
Subject: Replication terminated by primary server
Next
From: Raghavendra
Date:
Subject: Re: DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error.