Обсуждение: ODBC connect in ERWin

All,

Yesterday, I have seen some postings regarding connecting to Remote
PostgreSQL DB using ERWin. And I am having similar question here.

We have PostgreSQL DB on UNIX box. And it is running fine without any
problem. Now, I have ERWin and PostgreSQL ODBC driver from Insight Dist
installed on my local WinNT machine.

Now, I have created a sample reverse engineered an access DB using 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:

host    niral   MY_IP_ADDR   MASKING_ADDR   password
test_niral_users.dat

I have also checked out the 'greatbridge.com' site but couldn't find any
solutions.

So, if anybody has any idea, please help me..

Thanks in advance...

Niral

> 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:
>
> All,
>
> Yesterday, I have seen some postings regarding connecting to Remote
> PostgreSQL DB using ERWin. And I am having similar question here.
>
> We have PostgreSQL DB on UNIX box. And it is running fine without any
> problem. Now, I have ERWin and PostgreSQL ODBC driver from Insight Dist
> installed on my local WinNT machine.
>
> Now, I have created a sample reverse engineered an access DB using 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:
>
> host    niral   MY_IP_ADDR   MASKING_ADDR   password
> test_niral_users.dat
>
> I have also checked out the 'greatbridge.com' site but couldn't find any
> solutions.
>
> So, if anybody has any idea, please help me..
>
> Thanks in advance...
>
> Niral

> > 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
> > > 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
>