ODBC connect in ERWin

But When I am trying to forward engineer that to my Remote PostgreSQL db I
am getting ODBC error saying:
'Could not connect to the Server'
'Could not connect to remote socket'

Now, I have already added 'host' line in 'pg_hba.conf' file to give access
to the db from my machine as follows:

Have you added the -i option to the postmaster startup to tell it to use
TCP/IP sockets, rather than just the local sockets it sets up by default?

See: http://www.postgresql.org/docs/faq-english.html#3.7

Sincerely, Warren

Not sure about your pg_hba/ODBC setup, but ERwin takes pg_dump output in
as Ingres 1.x script and does pretty well (of course, it doesn't
recognize PL/pgSQL, etc), maybe with a few minor tweaks. I didn't have
any RI in my dump, so I wrote a perl script to add it so that I'd get the
relationships (I had hundreds of tables and a very standardized naming
convention), but I think it can infer from indices or names in some
manner.

Regards,
Ed Loehr

Niral Trivedi wrote:

But When I am trying to forward engineer that to my Remote PostgreSQL db I
am getting ODBC error saying:
'Could not connect to the Server'
'Could not connect to remote socket'

Oh, and I do recognize those error messages as the same that occur when
you are configured for SSH port forwarding but forgot to connect the SSH
session first.

Regards,
Ed Loehr

I'm going to ask the obvious, but . . .

Can you ping the Unix box from the ER workstation?

Did you start the postmaster with -i to allow remote connections?

Does the same ODBC DSN work from another program? (i.e. linking a Pg table
to an Access DB)

--rob

----- Original Message -----
From: "Ed Loehr" <eloehr@austin.rr.com>
Cc: "Niral Trivedi" <niral.trivedi@insage.com>;
<pgsql-general@postgresql.org>; <pgsql-admin@postgresql.org>
Sent: Friday, January 12, 2001 7:13 PM
Subject: Re: Re: [ADMIN] ODBC connect in ERWin

But When I am trying to forward engineer that to my Remote PostgreSQL

db I

All,

Thank you all for your response to my previous post. And You were right. I
had now our postgreSQL started with -i option and I am able to connect to it
from my local NT machine.

But now I am getting another problem.. When I go for 'Forward Engineer' the
current physical model, I am getting following error:

Connection is readonly, only select statements are allowed.;
Unrecognized key passed to SQLGetInfo.
Execution Failed!

I have tried to connect using the postgres superuser as well. But no luck. I
have also tried to change my 'pg_hba.conf' file to allow connection as
'trust' so anybody can connect from the specified IP address. But still
getting the same error.

Anybody has any idea??

Thanks again for your continuing support.

Niral

-----Original Message-----
From: Warren Vanichuk [mailto:pyber@street-light.com]
Sent: Friday, January 12, 2001 6:11 PM
To: Niral Trivedi
Cc: pgsql-general@postgresql.org; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] ODBC connect in ERWin

But When I am trying to forward engineer that to my Remote PostgreSQL db I
am getting ODBC error saying:
'Could not connect to the Server'
'Could not connect to remote socket'

Now, I have already added 'host' line in 'pg_hba.conf' file to give access
to the db from my machine as follows:

Have you added the -i option to the postmaster startup to tell it to use
TCP/IP sockets, rather than just the local sockets it sets up by default?

See: http://www.postgresql.org/docs/faq-english.html#3.7

Sincerely, Warren

You have set in your pgsql ODBC driver to open databases in readonly
mode. You should change it to do the 'forward engineer'.

Nelio

Niral Trivedi wrote:

All,

Thank you all for your response to my previous post. And You were right. I
had now our postgreSQL started with -i option and I am able to connect to it
from my local NT machine.

But now I am getting another problem.. When I go for 'Forward Engineer' the
current physical model, I am getting following error:

Connection is readonly, only select statements are allowed.;
Unrecognized key passed to SQLGetInfo.
Execution Failed!

I have tried to connect using the postgres superuser as well. But no luck. I
have also tried to change my 'pg_hba.conf' file to allow connection as
'trust' so anybody can connect from the specified IP address. But still
getting the same error.

Anybody has any idea??

Thanks again for your continuing support.

Niral

-----Original Message-----
From: Warren Vanichuk [mailto:pyber@street-light.com]
Sent: Friday, January 12, 2001 6:11 PM
To: Niral Trivedi
Cc: pgsql-general@postgresql.org; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] ODBC connect in ERWin

But When I am trying to forward engineer that to my Remote PostgreSQL db I
am getting ODBC error saying:
'Could not connect to the Server'
'Could not connect to remote socket'

Now, I have already added 'host' line in 'pg_hba.conf' file to give access
to the db from my machine as follows:

Have you added the -i option to the postmaster startup to tell it to use
TCP/IP sockets, rather than just the local sockets it sets up by default?

See: http://www.postgresql.org/docs/faq-english.html#3.7

Sincerely, Warren

--
Nelio Alves Pereira Filho
IFX Networks - www.ifx.com.br
+55 11 3365-5863
nelio@ifx.com.br

Thank you for such a quick response..

That worked for me..

Niral

-----Original Message-----
From: Nelio Alves Pereira Filho [mailto:nelio@ifx.com.br]
Sent: Monday, January 15, 2001 11:41 AM
To: Niral Trivedi
Cc: 'Warren Vanichuk'; 'Sandeep Joshi'; pgsql-general@postgresql.org;
pgsql-admin@postgresql.org
Subject: Re: [GENERAL] RE: [ADMIN] ODBC connect in ERWin

You have set in your pgsql ODBC driver to open databases in readonly
mode. You should change it to do the 'forward engineer'.

Nelio

Niral Trivedi wrote:

All,

Thank you all for your response to my previous post. And You were right. I
had now our postgreSQL started with -i option and I am able to connect to

it

from my local NT machine.

But now I am getting another problem.. When I go for 'Forward Engineer'

the

current physical model, I am getting following error:

Connection is readonly, only select statements are allowed.;
Unrecognized key passed to SQLGetInfo.
Execution Failed!

I have tried to connect using the postgres superuser as well. But no luck.

I

have also tried to change my 'pg_hba.conf' file to allow connection as
'trust' so anybody can connect from the specified IP address. But still
getting the same error.

Anybody has any idea??

Thanks again for your continuing support.

Niral

-----Original Message-----
From: Warren Vanichuk [mailto:pyber@street-light.com]
Sent: Friday, January 12, 2001 6:11 PM
To: Niral Trivedi
Cc: pgsql-general@postgresql.org; pgsql-admin@postgresql.org
Subject: Re: [ADMIN] ODBC connect in ERWin

But When I am trying to forward engineer that to my Remote PostgreSQL db

I

am getting ODBC error saying:
'Could not connect to the Server'
'Could not connect to remote socket'

Now, I have already added 'host' line in 'pg_hba.conf' file to give

access

to the db from my machine as follows:

Have you added the -i option to the postmaster startup to tell it to use
TCP/IP sockets, rather than just the local sockets it sets up by default?

See: http://www.postgresql.org/docs/faq-english.html#3.7

Sincerely, Warren

--
Nelio Alves Pereira Filho
IFX Networks - www.ifx.com.br
+55 11 3365-5863
nelio@ifx.com.br