Re: invalid byte sequence for encoding "UNICODE":0xa1

Hello,

For my database ( PostgreSQL 8) I made a backup (
using pgAdmin ). Now when I try to restore the data (
again using pgAdmin ) at some point the process is
aborted:

-----------
pg_restore: ERROR: invalid byte sequence for
encoding "UNICODE":0xa1
CONTEXT: COPY ...............
pg_restore: [archiver(db)] error returned by
PQendcopy: invalid byte sequence for encading
"UNICODE":0xa1
CONTEXT: COPY ...............
pg_restore: *** aborted because of error
Process returned exit code 1
-----------

If I delete the database and restore only the
schema I get this message:

-----------
"WARNING: errors ignored on restore:21
Process returned exit code 1"
-----------

The designer of database has told me that this last
message is OK, and this is the message which should I
get after restoring the schema and data.
I have asked him why I can restore the data but
unfortunatelly he doesn't now where the problem is.
The database is installed on a server with Windows
2003 .

Can you please help me?

____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

Am Freitag, 4. Januar 2008 15.58:23 schrieb Popovici Alexandru:
> Hello,
>
> For my database ( PostgreSQL 8) I made a backup (
> using pgAdmin ). Now when I try to restore the data (
> again using pgAdmin ) at some point the process is
> aborted:
>
> -----------
> pg_restore: ERROR: invalid byte sequence for
> encoding "UNICODE":0xa1
> CONTEXT: COPY ...............
> pg_restore: [archiver(db)] error returned by
> PQendcopy: invalid byte sequence for encading
> "UNICODE":0xa1
> CONTEXT: COPY ...............
> pg_restore: *** aborted because of error
> Process returned exit code 1
> -----------

There are serveral possible reasons for this issue.
-Restoring on a newer server then the backup was taken from. The servers got
pickier regarding encoding over several versions.
-Restoring on a server with diverent encoding then the encoding of the server
where the backup came from.
-Restoring with a differen client encoding at the pgAdmin (probably different
version or setting).
-Corruptet data file.
-...

If you need more assistance we need to know the platform, versions and
parameters you used for the process.

Best regards
Ivo
>
> If I delete the database and restore only the
> schema I get this message:
>
> -----------
> "WARNING: errors ignored on restore:21
> Process returned exit code 1"
> -----------
>
> The designer of database has told me that this last
> message is OK, and this is the message which should I
> get after restoring the schema and data.
> I have asked him why I can restore the data but
> unfortunatelly he doesn't now where the problem is.
> The database is installed on a server with Windows
> 2003 .
>
> Can you please help me?
>
>
>
> ___________________________________________________________________________
>_________ Be a better friend, newshound, and
> know-it-all with Yahoo! Mobile. Try it now.
> http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Have you searched our list archives?
>
> http://archives.postgresql.org

Thank you for your answer.

I tryed to restore the dump file ( some data was
deleted an need it to be restored ) on the same server
on which was made (windows 2003 ), using the same
software ( pgAmin ) used at backup. I have not change
any settings for PostgreSQL server or pgAdmin.

The data is not corupted because I succeded to
restore it on a different computer on which I have
installed the PostgreSQL and PgAmin 1.2. But I can do
this on production server.

> There are serveral possible reasons for this issue.
> -Restoring on a newer server then the backup was
> taken from. The servers got
> pickier regarding encoding over several versions.
> -Restoring on a server with diverent encoding then
> the encoding of the server
> where the backup came from.
> -Restoring with a differen client encoding at the
> pgAdmin (probably different
> version or setting).

> -Corruptet data file.
> -...
>

____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ