client encoding mismatch help!

Hi All,

I have installed 8.1 server on a FC4 system and loaded my
7.3.2 database data (not too many problems) all is working well
except the odbc driver won't connect !
The database was built with no encoding options set, the driver
is psqlodbc-08_01_0102 with default options (but I have tryed many)

The Driver Log file follows :=
picking_pg 330-130 ENTER SQLAllocEnv
HENV * 01644484

picking_pg 330-130 EXIT SQLAllocEnv with return code 0
(SQL_SUCCESS)
HENV * 0x01644484 ( 0x016614f0)

picking_pg 330-130 ENTER SQLAllocConnect
HENV 016614F0
HDBC * 01640FC4

picking_pg 330-130 EXIT SQLAllocConnect with return code 0
(SQL_SUCCESS)
HENV 016614F0
HDBC * 0x01640FC4 ( 0x01661598)

picking_pg 330-130 ENTER SQLDriverConnectW
HDBC 01661598
HWND 001A01FC
WCHAR * 0x1F7C4AA0 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x1F7C4AA0
SWORD 8
SWORD * 0x00000000
UWORD 3

picking_pg 330-130 EXIT SQLDriverConnectW with return code -1
(SQL_ERROR)
HDBC 01661598
HWND 001A01FC
WCHAR * 0x1F7C4AA0 [ -3] "******\ 0"
SWORD -3
WCHAR * 0x1F7C4AA0
SWORD 8
SWORD * 0x00000000
UWORD 3

DIAG [22003] client encoding mismatch (214)
------------------------------------------------------------ -------------------------------------

Please help, I need to get this system up an running in production pronto ;)

TIA,
Frank.


---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Re: client encoding mismatch help!

> I have installed 8.1 server on a FC4 system and loaded my
> 7.3.2 database data (not too many problems) all is working well
> except the odbc driver won't connect !
> The database was built with no encoding options set, the driver
> is psqlodbc-08_01_0102 with default options (but I have tryed many)
>
> The Driver Log file follows :=

It seems you are trying psqlodbc on Windows. Am I right?
It is more helpful when you post us mylog output (both - Global and
DataSource settings).

Do you try ANSI or Unicode driver? Does problem exist with both types
of psqlODBC driver?

> Please help, I need to get this system up an running in production
> pronto ;)

I hope you don't mean in 5 minutes ...

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Re: client encoding mismatch help!

Thanks for the very fast reply Luf,

On Tuesday 13 December 2005 1:42 pm, Ludek Finstrle wrote:
> > I have installed 8.1 server on a FC4 system and loaded my
> > 7.3.2 database data (not too many problems) all is working well
> > except the odbc driver won't connect !
> > The database was built with no encoding options set, the driver
> > is psqlodbc-08_01_0102 with default options (but I have tryed many)
> >
> > The Driver Log file follows :=
>
> It seems you are trying psqlodbc on Windows. Am I right?
Yes Win2000 at the moment - Xp, 98 & ME to follow)
> It is more helpful when you post us mylog output (both - Global and
> DataSource settings).
I can't generate a log file as I don't have a C-Drive
and the logpath seems to be hard wired!
>
> Do you try ANSI or Unicode driver? Does problem exist with both types
> of psqlODBC driver?
I only saw one stable msi driver ! (but I guess I looked in the wrong place)
>
> > Please help, I need to get this system up an running in production
> > pronto ;)
>
> I hope you don't mean in 5 minutes ...
No, 2 days (luxury)
>

I have solved the connect problem by rebuilding the database with
--encoding=SQL_ANSII, I guess the database default to some other
encoding schema - I bet it's in the documentation somewhere :) this
allows the windows ODBC drivers to work (mostly) but now
fails with my datawindow objects :( it seem the from ODBC 2 -> 3
the TIMESTAMP field has changed some how, and the datawindow
can't deal with it (first guess)!

Is there some way to force the driver/database to use the old 2.0 ODBC
format ?

Cheers,

Frank

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Re: client encoding mismatch help!

> > It seems you are trying psqlodbc on Windows. Am I right?
> Yes Win2000 at the moment - Xp, 98 & ME to follow)

Ok.

> > It is more helpful when you post us mylog output (both - Global and
> > DataSource settings).
> I can't generate a log file as I don't have a C-Drive
> and the logpath seems to be hard wired!

Could you specify drive letter? I'll prepare special DLLs with that
path.

> > Do you try ANSI or Unicode driver? Does problem exist with both types
> > of psqlODBC driver?
> I only saw one stable msi driver ! (but I guess I looked in the wrong place)

This msi is only install kit which contains two drivers:
1) psqlodbca.dll (ANSI one)
2) psqlodbcw.dll (Unicode one)
and other stuff.

You can see this drivers in ODBC Data Source Administrator in tab Drivers.
When you create new Data Source you have to choose one of drivers you have
installed in the system.
Is it clear now?

> > I hope you don't mean in 5 minutes ...
> No, 2 days (luxury)

Not so much ;-)

> I have solved the connect problem by rebuilding the database with
> --encoding=SQL_ANSII, I guess the database default to some other

It's strange. I have W2k too and database encoding is Unicode. I have
no problem with connect.

> allows the windows ODBC drivers to work (mostly) but now

I wonder what I'll see in mylog output.

> fails with my datawindow objects :( it seem the from ODBC 2 -> 3
> the TIMESTAMP field has changed some how, and the datawindow
> can't deal with it (first guess)!

I don't know about such change in psqlodbc. Don't you change backend?
What does it mean "can't deal with it". Could you describe your process
and point where does your expectation differ from reality?
I'm sorry I can't help you without mylog output.

> Is there some way to force the driver/database to use the old 2.0 ODBC
> format ?

I don't know. I don't take a look at this part yet.

Luf

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend