Psql DBC -08.02.0400 problem, only public schema can be viewed.

Psql DBC -08.02.0400 problem, only public schema can be viewed.

am 15.08.2007 12:50:41 von maya.govender

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7DF2A.0D2172C4
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Greetings,

=20

Current environment setup:

=20

OS - Solaris 9 Sparc 64 bit

Application - SAS 9

Odbc Driver - UNIX ODBC 2.2

Postgres driver - Psqlodbc-08.02.0400

=20

Problem situation :

=20

Requirements - Access postgres 8.1.3 database from sas ( CRM application
) using unixODBC and psqlodbc compiled as 64 bit because sas is
installed as 64 bit

Current situation - the above is in place , I can access all data/tables
in the public schema only, all other schema's cannot be accessed from
sas.

=20

Kindly advise as to a possible workaround or fix for this issue, please
see Comments below from SAS support regarding this issue,

=20

=20

"Development confirmed that the ODBC driver is the reason for the
behavior.=20

=20

SAS query the odbc driver regarding Schema usage and the PostgreSQL
driver comes back basically saying "no schema usage". Therefore tables
are not prefix'ed with the schema.

=20

ODBC: ENTER SQLGetInfo

=20 0x000000000033e530

=20 91

=20 0x0000000078024528

=20 4

=20 0x000000007307c0fe

=20

ODBC: EXIT SQLGetInfo with return code 0 (SQL_SUCCESS)

=20 0x000000000033e530

=20 91

=20 0x000000007307bf4c (0) <> <---- This is the
information returned from the PostgreSQL driver - no schema usage

=20 4

=20 0x000000007307c0fe (4)

=20

This is what the driver should return (exmple with oracle's odbc
driver):

=20

ODBC: EXIT SQLGetInfo with return code 0 (SQL_SUCCESS)

=20 0x049a1348

=20 91

=20 0x0495f028 (31) SQL_SU_PROCEDURE_INVOCATION | SQL_SU_TABLE_DEFINITION |
SQL_SU_INDEX_DEFINITION=20

| SQL_SU_PRIVILEGE_DEFINITION>

=20 4

=20 0x0495f2be (4)

=20

=20

I suggest that they contact the ODBC driver vendor with the issue. Maybe
there is an option to turn on the schema usage within the driver
configuration."

=20

=20

=20

=20

=20

=20

=20

Kind Regards

=20

Maya Govender

=20

Tel: 011 263 5009

Fax: 011 263 5131

Cell: 082 550 9180=20

email: maya.govender@ebucks.com

=20


This email is subject to a disclaimer, which is available at: https://www=
..ebucks.com/email/disclaimer.html

If you are unable to access the Disclaimer, send a blank e-mail to discla=
imer@ebucks.com and we will send you a copy of the Disclaimer.

------_=_NextPart_001_01C7DF2A.0D2172C4
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

schemas-microsoft-com:office:word" xmlns:x=3D"urn:schemas-microsoft-com:o=
ffice:excel" xmlns=3D"http://www.w3.org/TR/REC-html40">


>





=




:10.0pt;
font-family:Arial'>Greetings,



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'>Current environment setup:
>

:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'>OS         &nb=
sp;         –
Solaris 9 Sparc 64 bit



:10.0pt;
font-family:Arial'>Application        =

SAS 9



:10.0pt;
font-family:Arial'>Odbc Driver       –=
; UNIX
ODBC 2.2



:10.0pt;
font-family:Arial'>Postgres driver   - Psqlodbc-08.02.0400=



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'>Problem situation :



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'>Requirements – Access postgres 8.1.3 database fr=
om sas
( CRM application ) using unixODBC and psqlodbc compiled as 64 bit becaus=
e sas
is installed as 64 bit



:10.0pt;
font-family:Arial'>Current situation – the above is in place , I ca=
n
access all data/tables in the public schema  only, all other schema&=
#8217;s
cannot be accessed from sas.



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'>Kindly advise as to a possible workaround or fix for t=
his
issue, please see Comments below from SAS support regarding this issue, :p>



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'> 



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>"Development co=
nfirmed
that the ODBC driver is the reason for the behavior. font>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>  pan>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>SAS query the odbc d=
river
regarding Schema usage and the PostgreSQL driver comes back basically say=
ing
"no schema usage". Therefore tables are not prefix'ed with the
schema.



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>  pan>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>ODBC: ENTER SQLGetIn=
fo



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;        
0x000000000033e530



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;           &nb=
sp;           &nbs=
p;
91 <SQL_SCHEMA_USAGE>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;        
0x0000000078024528



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;           &nb=
sp;           &nbs=
p; 
4



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;        
0x000000007307c0fe



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>  pan>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>ODBC: EXIT SQLGetInf=
o with
return code 0 (SQL_SUCCESS)



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;        
0x000000000033e530



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;           &nb=
sp;           &nbs=
p;
91 <SQL_SCHEMA_USAGE>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;        
0x000000007307bf4c (0) <>      <---- Th=
is is
the information returned from the PostgreSQL driver - no schema usage >



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;           &nb=
sp;           &nbs=
p; 
4



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;        
0x000000007307c0fe (4)



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>  pan>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>This is what the dri=
ver
should return (exmple with oracle's odbc driver): >



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>  pan>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>ODBC: EXIT SQLGetInf=
o with
return code 0 (SQL_SUCCESS)



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;        
0x049a1348



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;           &nb=
sp;    
91 <SQL_SCHEMA_USAGE>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;        
0x0495f028 (31) <SQL_SU_DML_STATEMENTS | SQL_SU_PROCEDURE_INVOCATION |=

SQL_SU_TABLE_DEFINITION | SQL_SU_INDEX_DEFINITION t>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>|
SQL_SU_PRIVILEGE_DEFINITION>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;           &nb=
sp;     
4



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>   &n=
bsp;        
0x0495f2be (4)



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>  pan>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>  pan>



"Courier New"> style=3D'font-size:10.0pt;font-family:"Courier New"'>I suggest that they =
contact
the ODBC driver vendor with the issue. Maybe there is an option to turn o=
n the
schema usage within the driver configuration." nt>



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'> 



:10.0pt;
font-family:Arial'> 



"#5f5f5f"
face=3DArial> F5F'>Kind
Regards
font-family:
"Tms Rmn";color:black'>



=3D"#5f5f5f"
face=3DArial> F5F;
font-weight:bold'> 



=3D"#5f5f5f"
face=3DArial> F5F;
font-weight:bold'>Maya Govender



=3D"#5f5f5f"
face=3DArial> F5F;
font-weight:bold'> 



=3D"#5f5f5f"
face=3DArial> F5F;
font-weight:bold'>Tel:      
=
size=3D2 color=3D"#5f5f5f" face=3DArial> ont-family:
Arial;color:#5F5F5F'>011 263 5009 >



=3D"#5f5f5f"
face=3DArial> F5F;
font-weight:bold'>Fax:     
ont
size=3D2 color=3D"#5f5f5f" face=3DArial> ont-family:
Arial;color:#5F5F5F'>011 263 5131 >



=3D"#5f5f5f"
face=3DArial> F5F;
font-weight:bold'>Cell:     
<=
font
size=3D2 color=3D"#5f5f5f" face=3DArial> ont-family:
Arial;color:#5F5F5F'>082 550 9180
ck
face=3DArial> k'>
size=3D2 color=3D"#5f5f5f" face=3DArial> ont-family:
Arial;color:#5F5F5F;font-weight:bold'>



or=3D"#5f5f5f"
face=3DArial> F5F;
font-weight:bold'>email:

face=3DArial> k;
font-weight:bold'>  
#a1a100"
face=3DArial> 100'>maya.govender@ebucks.com
size=3D1 color=3Dblack face=3DArial> amily:Arial;
color:black'>



'font-size:
12.0pt'> 






 


This email is subject to a disclaimer, which is available at: href=3D"https://www.ebucks.com/email/disclaimer.html">https: //www.ebucks.=
com/email/disclaimer.html


If you are unable to access the Disclaimer, send a blank e-mail to
href=3D"mailto:disclaimer@ebucks.com">disclaimer@ebucks.com
and we wi=
ll send=20
you a copy of the Disclaimer.






------_=_NextPart_001_01C7DF2A.0D2172C4--

Re: Psql DBC -08.02.0400 problem, only public schema can be viewed.

am 16.08.2007 03:24:26 von Hiroshi Saito

Hi.

> From: Govender, Maya
> To: pgsql-odbc@postgresql.org
> Sent: Wednesday, August 15, 2007 7:50 PM
> Subject: [ODBC] Psql DBC -08.02.0400 problem, only public schema can be viewed.
>
>
> Greetings,
>
> Current environment setup:
>
> OS - Solaris 9 Sparc 64 bit
> Application - SAS 9
> Odbc Driver - UNIX ODBC 2.2
> Postgres driver - Psqlodbc-08.02.0400
>
> Problem situation :
>
> Requirements - Access postgres 8.1.3 database from sas ( CRM application ) using unixODBC
> and psqlodbc compiled as 64 bit because sas is installed as 64 bit

Cool:-)

> Current situation - the above is in place , I can access all data/tables in the public
> schema only, all other schema's cannot be accessed from sas.

Does on the ShowSystemTables of odbc.ini help you?

Regards,
Hiroshi Saito


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster