Re: BUG #5847: pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence for encoding "UTF8": 0x96

Lists: pgsql-bugs
From: "Vijayakumar" <mails4vijayakumar(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5847: pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence for encoding "UTF8": 0x96
Date: 2011-01-25 04:18:24
Message-ID: 201101250418.p0P4IOvv067349@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 5847
Logged by: Vijayakumar
Email address: mails4vijayakumar(at)gmail(dot)com
PostgreSQL version: 8.2
Operating system: windows
Description: pg_restore: [archiver (db)] COPY failed: ERROR: invalid
byte sequence for encoding "UTF8": 0x96
Details:

while restoring my database i am getting the error as

D:\EnterpriseDB\Postgres\8.2\bin\pg_restore.exe -i -h localhost -p 5432 -U
postgres -d asasas -v "E:\backupcsv\erode.backup"
pg_restore: connecting to database for restore
pg_restore: creating TABLE generalledgermaster_erode
pg_restore: restoring data for table "generalledgermaster_erode"
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 1624; 0 121663 TABLE DATA
generalledgermaster_erode postgres
pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence for
encoding "UTF8": 0x96
HINT: This error can also happen if the byte sequence does not match the
encoding expected by the server, which is controlled by "client_encoding".
CONTEXT: COPY generalledgermaster_erode, line 374
pg_restore: creating CONSTRAINT generalledgermaster_erode_pkey
pg_restore: setting owner and privileges for TABLE
generalledgermaster_erode
pg_restore: setting owner and privileges for CONSTRAINT
generalledgermaster_erode_pkey
WARNING: errors ignored on restore: 1

Process returned exit code 1.


From: Rodriguez Fernando <rodriguez(at)ort(dot)edu(dot)uy>
To: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5847: pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence for encoding "UTF8": 0x96
Date: 2011-01-25 11:50:18
Message-ID: 4D3EB8FA.70101@ort.edu.uy
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

El 25/01/2011 2:18, Vijayakumar escribió:
> The following bug has been logged online:
>
> Bug reference: 5847
> Logged by: Vijayakumar
> Email address: mails4vijayakumar(at)gmail(dot)com
> PostgreSQL version: 8.2
> Operating system: windows
> Description: pg_restore: [archiver (db)] COPY failed: ERROR: invalid
> byte sequence for encoding "UTF8": 0x96
> Details:
>
> while restoring my database i am getting the error as
>
>
>
> D:\EnterpriseDB\Postgres\8.2\bin\pg_restore.exe -i -h localhost -p 5432 -U
> postgres -d asasas -v "E:\backupcsv\erode.backup"
> pg_restore: connecting to database for restore
> pg_restore: creating TABLE generalledgermaster_erode
> pg_restore: restoring data for table "generalledgermaster_erode"
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
> pg_restore: [archiver (db)] Error from TOC entry 1624; 0 121663 TABLE DATA
> generalledgermaster_erode postgres
> pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence for
> encoding "UTF8": 0x96
> HINT: This error can also happen if the byte sequence does not match the
> encoding expected by the server, which is controlled by "client_encoding".
> CONTEXT: COPY generalledgermaster_erode, line 374
> pg_restore: creating CONSTRAINT generalledgermaster_erode_pkey
> pg_restore: setting owner and privileges for TABLE
> generalledgermaster_erode
> pg_restore: setting owner and privileges for CONSTRAINT
> generalledgermaster_erode_pkey
> WARNING: errors ignored on restore: 1
>
> Process returned exit code 1.
>
Hola a todos, la base de donde la respaldastes la tenias en utf-8,
win1252, sql_ascii o latin1?
Si aun tenes la base original proba pg_dump -Ft -EUTF8

saludos Fernando


From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Vijayakumar <mails4vijayakumar(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5847: pg_restore: [archiver (db)] COPY failed: ERROR: invalid byte sequence for encoding "UTF8": 0x96
Date: 2011-01-31 01:33:03
Message-ID: AANLkTi=OMxYVsUwS2spLOPAaFjPpH3h7=o3s2e+Kg-2m@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-bugs

On Mon, Jan 24, 2011 at 11:18 PM, Vijayakumar
<mails4vijayakumar(at)gmail(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference:      5847
> Logged by:          Vijayakumar
> Email address:      mails4vijayakumar(at)gmail(dot)com
> PostgreSQL version: 8.2
> Operating system:   windows
> Description:        pg_restore: [archiver (db)] COPY failed: ERROR:  invalid
> byte sequence for encoding "UTF8": 0x96
> Details:
>
> while restoring my database i am getting the error as
>
>
>
> D:\EnterpriseDB\Postgres\8.2\bin\pg_restore.exe -i -h localhost -p 5432 -U
> postgres -d asasas -v "E:\backupcsv\erode.backup"
> pg_restore: connecting to database for restore
> pg_restore: creating TABLE generalledgermaster_erode
> pg_restore: restoring data for table "generalledgermaster_erode"
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
> pg_restore: [archiver (db)] Error from TOC entry 1624; 0 121663 TABLE DATA
> generalledgermaster_erode postgres
> pg_restore: [archiver (db)] COPY failed: ERROR:  invalid byte sequence for
> encoding "UTF8": 0x96
> HINT:  This error can also happen if the byte sequence does not match the
> encoding expected by the server, which is controlled by "client_encoding".
> CONTEXT:  COPY generalledgermaster_erode, line 374
> pg_restore: creating CONSTRAINT generalledgermaster_erode_pkey
> pg_restore: setting owner and privileges for TABLE
> generalledgermaster_erode
> pg_restore: setting owner and privileges for CONSTRAINT
> generalledgermaster_erode_pkey
> WARNING: errors ignored on restore: 1
>
> Process returned exit code 1.

You haven't provided a whole lot of information to go on, here - but
apparently you have some invalidly encoded data in your dump file.
Older versions of PostgreSQL weren't as strict about preventing such
data from creeping into the database, which can lead to problems of
this type. Your best bet is to probably edit the dump before
restoring it.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company