Thread: pgdump error "Could not open file pg_clog/0B8E: No such file or directory"
pgdump error "Could not open file pg_clog/0B8E: No such file or directory"
From
jesse.waters@gmail.com
Date:
I am receiving an error when running a pg_dump. These are older legacy systems and upgrading them is not in plan. Any help will be appreciated. CentOS 5.3 (64bit) psql (PostgreSQL) 8.3.11 full error message: pg_dump: SQL command failed pg_dump: Error message from server: ERROR: could not access status of transaction 3101708884 DETAIL: Could not open file pg_clog/0B8E: No such file or directory. pg_dump: The command was: COPY blob_store.blobs (blob_id, mime_type, binary_data, create_ts) TO stdout; Command used, pretty standard pg_dump -Fc <dbname> -f <outfile> TIA, Jesse Waters
Re: pgdump error "Could not open file pg_clog/0B8E: No such file or directory"
From
Adrian Klaver
Date:
On 04/24/2013 03:35 AM, jesse.waters@gmail.com wrote: > I am receiving an error when running a pg_dump. These are older legacy > systems and upgrading them is not in plan. > Any help will be appreciated. > > > CentOS 5.3 (64bit) > psql (PostgreSQL) 8.3.11 > > full error message: > pg_dump: SQL command failed > pg_dump: Error message from server: ERROR: could not access status > of transaction 3101708884 > DETAIL: Could not open file pg_clog/0B8E: No such file or directory. Does the above file actually exist in the pg_clog directory? > pg_dump: The command was: COPY blob_store.blobs (blob_id, mime_type, > binary_data, create_ts) TO stdout; > > Command used, pretty standard > pg_dump -Fc <dbname> -f <outfile> > > > TIA, > > Jesse Waters > > -- Adrian Klaver adrian.klaver@gmail.com
Re: pgdump error "Could not open file pg_clog/0B8E: No such file or directory"
From
jesse.waters@gmail.com
Date:
Sorry for the delay. No it does not exist. ls -l /var/lib/pgsql/data/pg_clog/0B8E ls: /var/lib/pgsql/data/pg_clog/0B8E: No such file or directory Have 92 files in directory which are all 262144 in size. On Wed, Apr 24, 2013 at 9:23 AM, Adrian Klaver <adrian.klaver@gmail.com> wrote: > On 04/24/2013 03:35 AM, jesse.waters@gmail.com wrote: >> >> I am receiving an error when running a pg_dump. These are older legacy >> systems and upgrading them is not in plan. >> Any help will be appreciated. >> >> >> CentOS 5.3 (64bit) >> psql (PostgreSQL) 8.3.11 >> >> full error message: >> pg_dump: SQL command failed >> pg_dump: Error message from server: ERROR: could not access status >> of transaction 3101708884 >> DETAIL: Could not open file pg_clog/0B8E: No such file or directory. > > > Does the above file actually exist in the pg_clog directory? > > >> pg_dump: The command was: COPY blob_store.blobs (blob_id, mime_type, >> binary_data, create_ts) TO stdout; >> >> Command used, pretty standard >> pg_dump -Fc <dbname> -f <outfile> >> >> >> TIA, >> >> Jesse Waters >> >> > > > -- > Adrian Klaver > adrian.klaver@gmail.com
Re: pgdump error "Could not open file pg_clog/0B8E: No such file or directory"
From
Merlin Moncure
Date:
On Thu, Apr 25, 2013 at 5:13 AM, <jesse.waters@gmail.com> wrote: > Sorry for the delay. > No it does not exist. > > ls -l /var/lib/pgsql/data/pg_clog/0B8E > ls: /var/lib/pgsql/data/pg_clog/0B8E: No such file or directory > > Have 92 files in directory which are all 262144 in size. This file records if transactions committed or were aborted. If it is missing, this signifies corruption. You can force a file in, but chances are things will not be as they should be. When is your last good backup? If it's fairly recent you can force a file with all 'commit' values and compare vs backup and attempt to repair any damage if things don't look too bad I'd start with 'reindex' and/or full database restore assuming you could pull a dump). Take a full filesystem backup before doing anything though. merlin