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

From: raghu ram <raghuchennuru(at)gmail(dot)com>
To: Olga Vingurt <olgavi(at)checkpoint(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Ofer Israeli <oferi(at)checkpoint(dot)com>
Subject: Re: DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error.
Date: 2012-07-16 13:55:56
Message-ID: CALnrrJSDMCedy24MW1V10_CvjSYdfARYB0tJi2-bA6C=xKN8GA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jul 16, 2012 at 5:44 PM, Olga Vingurt <olgavi(at)checkpoint(dot)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/

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message postgresuser 2012-07-16 14:04:17 Create stored procedure from C#.net
Previous Message Olga Vingurt 2012-07-16 12:14:52 DB fails to start: "Could not read from file "pg_clog/0003" at offset 212992: No error.