isql/sperform/sacego and IDS 7.31
A Solaris 2.8 site running IDS 7.31 with old 7.20 tools (isql, ACE, PERFORM) found dbaccess could connect over both the shared-memory (onipcshm) and ontlitcp aliases, but the 7.20 tools failed on the TCP alias with error -25572, "Network driver cannot bind a name to the port." Suggestions included checking for a port clash, trying onsoctcp, and changing the sqlhosts service field; Jonathan Leffler noted ontlitcp is correct for Solaris. The answer offered was that the 7.20 tools predate Solaris 8 and their TCP libraries are incompatible, so shared memory must be used; the poster did not confirm back.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Our machine is Solaris 2.8, running IDS 7.31.UD6 and we are using the
tools (isql, ACE & PERFORM) 7.20.UE1. I'm aware these are old
versions, our previous attempts to use later versions of the tools
came unstuck on new 'features' which had developed somewhere along the
way.
The problem is using the tools with a TCP connection to the database:
/etc/services:
v6new 1532/tcp # inhouse informix
server
v6newtcp 1533/tcp # inhouse informix
server
$INFORMIXDIR/etc/sqlhosts:
v6new onipcshm testhse2 v6new
v6newtcp ontlitcp testhse2 v6newtcp
from onconfig -c:
DBSERVERNAME v6new # Name of default database server
DBSERVERALIASES v6newtcp # List of alternate dbservernames
dbaccess can happily connect to v6new and v6newtcp, but attempting to
use any of the v7.20 tools against v6newtcp results in a -25572 error
- "Network driver cannot bind a name to the port."
I'm not sure if this is a subtle configuration problem, or simply that
the old version of the tools won't connect to a TCP connection, just
to shared memory. Trying to find what the latest version of I-SQL is
on the IBM web site is driving me nuts!
Cats <ramwater@uk2.net> schrieb:
>The problem is using the tools with a TCP connection to the database:
>/etc/services:
>v6new 1532/tcp # inhouse informix
>server
>v6newtcp 1533/tcp # inhouse informix
>server
>
>$INFORMIXDIR/etc/sqlhosts:
>v6new onipcshm testhse2 v6new
>v6newtcp ontlitcp testhse2 v6newtcp
>dbaccess can happily connect to v6new and v6newtcp, but attempting to
>use any of the v7.20 tools against v6newtcp results in a -25572 error
>- "Network driver cannot bind a name to the port."
Since "v6new" is defined as a shared memory connection, TCP/IP doesn't
play any role in this context.
Have you made sure that port 1533 is not already in use by another
application or daemon?
Can you try changing the entry for "v6newtcp" in your sqlhosts file
to the following:
v6newtcp onsoctcp testhse2 v6newtcp
Are server and application running on the same machine?
HTH, Richard
Hi,
I think, the 4. parameter in sqlhosts is your problem.
You Informix-Server has for sure the same name
before
$INFORMIXDIR/etc/sqlhosts:
v6new onipcshm testhse2 v6newv6newtcp ontlitcp testhse2 v6newtcp <<<<< new
server ?
asume, online is DB-Server-Name
does does works Better ???
$INFORMIXDIR/etc/sqlhosts:
v6new onipcshm testhse2 online
v6newtcp ontlitcp testhse2 online <<<<<
Richard Spitz schrieb:
> Cats <ramwater@uk2.net> schrieb:
>> The problem is using the tools with a TCP connection to the database:
>> /etc/services:
>> v6new 1532/tcp # inhouse informix
>> server
>> v6newtcp 1533/tcp # inhouse informix
>> server
>>
>> $INFORMIXDIR/etc/sqlhosts:
>> v6new onipcshm testhse2 v6new
>> v6newtcp ontlitcp testhse2 v6newtcp>
>> dbaccess can happily connect to v6new and v6newtcp, but attempting to
>> use any of the v7.20 tools against v6newtcp results in a -25572 error
>> - "Network driver cannot bind a name to the port."
>
> Since "v6new" is defined as a shared memory connection, TCP/IP doesn't
> play any role in this context.
>
> Have you made sure that port 1533 is not already in use by another
> application or daemon?
>
> Can you try changing the entry for "v6newtcp" in your sqlhosts file
> to the following:
>
> v6newtcp onsoctcp testhse2 v6newtcp>
> Are server and application running on the same machine?
>
> HTH, Richard
On May 31, 7:38 pm, Richard Spitz <Richard.Sp...@med.uni-muenchen.de>
wrote:
> Cats <ramwa...@uk2.net> schrieb:
>
> >The problem is using the tools with a TCP connection to the database:
> >/etc/services:
> >v6new 1532/tcp # inhouse informix
> >server
> >v6newtcp 1533/tcp # inhouse informix
> >server
>
> >$INFORMIXDIR/etc/sqlhosts:
> >v6new onipcshm testhse2 v6new
> >v6newtcp ontlitcp testhse2 v6newtcp> >dbaccess can happily connect to v6new and v6newtcp, but attempting to
> >use any of the v7.20 tools against v6newtcp results in a -25572 error
> >- "Network driver cannot bind a name to the port."
>
> Since "v6new" is defined as a shared memory connection, TCP/IP doesn't
> play any role in this context.
But it's v6newtcp it can't connect to - v6new is no problem for I/SQL.
>
> Have you made sure that port 1533 is not already in use by another
> application or daemon?
Would dbaccess be able to connect to it if it was?
>
> Can you try changing the entry for "v6newtcp" in your sqlhosts file
> to the following:
>
> v6newtcp onsoctcp testhse2 v6newtcp
Have a feeling I started with onsoctcp and had to alter it to what it
is now due to what is and is not supported on that particular
platform.
>
> Are server and application running on the same machine?
Yes
>
> HTH, Richard
You are using tools (ISQL etc) that were created prior to Solaris 8 or
IPV6. The TCP libraries in 7.20 ISQL are not compatible with the
Solaris 8. You must use Shared memory to connect from those tools to
the engine.
MW
-----Original Message-----
From: informix-list-bounces@iiug.org
[mailto:informix-list-bounces@iiug.org] On Behalf Of Cats
Sent: Friday, 1 June 2007 7:56 a.m.
To: informix-list@iiug.org
Subject: Re: isql/sperform/sacego and IDS 7.31
On May 31, 7:38 pm, Richard Spitz <Richard.Sp...@med.uni-muenchen.de>
wrote:
> Cats <ramwa...@uk2.net> schrieb:
>
> >The problem is using the tools with a TCP connection to the database:
> >/etc/services:
> >v6new 1532/tcp # inhouse informix
> >server
> >v6newtcp 1533/tcp # inhouse informix
> >server
>
> >$INFORMIXDIR/etc/sqlhosts:
> >v6new onipcshm testhse2 v6new
> >v6newtcp ontlitcp testhse2 v6newtcp> >dbaccess can happily connect to v6new and v6newtcp, but attempting to
> >use any of the v7.20 tools against v6newtcp results in a -25572 error
> >- "Network driver cannot bind a name to the port."
>
> Since "v6new" is defined as a shared memory connection, TCP/IP doesn't
> play any role in this context.
But it's v6newtcp it can't connect to - v6new is no problem for I/SQL.
>
> Have you made sure that port 1533 is not already in use by another
> application or daemon?
Would dbaccess be able to connect to it if it was?
>
> Can you try changing the entry for "v6newtcp" in your sqlhosts file
> to the following:
>
> v6newtcp onsoctcp testhse2 v6newtcp
Have a feeling I started with onsoctcp and had to alter it to what it
is now due to what is and is not supported on that particular
platform.
>
> Are server and application running on the same machine?
Yes
>
> HTH, Richard
_______________________________________________
Informix-list mailing list
Informix-list@iiug.org
http://www.iiug.org/mailman/listinfo/informix-list
Richard Spitz wrote:
> Cats <ramwater@uk2.net> schrieb:
>> The problem is using the tools with a TCP connection to the database:
>> /etc/services:
>> v6new 1532/tcp # inhouse informix
>> server
>> v6newtcp 1533/tcp # inhouse informix
>> server
>>
>> $INFORMIXDIR/etc/sqlhosts:
>> v6new onipcshm testhse2 v6new
>> v6newtcp ontlitcp testhse2 v6newtcp>
>> dbaccess can happily connect to v6new and v6newtcp, but attempting to
>> use any of the v7.20 tools against v6newtcp results in a -25572 error
>> - "Network driver cannot bind a name to the port."
>
> Since "v6new" is defined as a shared memory connection, TCP/IP doesn't
> play any role in this context.
Agreed; it is important that the 'service' name for a shared memory
connection is unique across all the (shared memory) server names and
aliases on your machine, but there is no need for an entry in
/etc/services for it.
> Have you made sure that port 1533 is not already in use by another
> application or daemon?
>
> Can you try changing the entry for "v6newtcp" in your sqlhosts file
> to the following:
>
> v6newtcp onsoctcp testhse2 v6newtcp
Solaris uses ontlitcp - as shown in the original.
> Are server and application running on the same machine?
Almost certainly, though worth checking explicitly. If on another
machine, then there's a good chance that it would need onsoctcp instead
of ontlitcp (unless it is another Solaris box).
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2007.0226 -- http://dbi.perl.org/
Bernhard Gramberg wrote:
> I think, the 4. parameter in sqlhosts is your problem.
>
> You Informix-Server has for sure the same name
>
> before
>
> $INFORMIXDIR/etc/sqlhosts:
> v6new onipcshm testhse2 v6new> v6newtcp ontlitcp testhse2 v6newtcp <<<<< new
> server ?
>
>
> asume, online is DB-Server-Name
>
> does does works Better ???
>
> $INFORMIXDIR/etc/sqlhosts:
> v6new onipcshm testhse2 online
> v6newtcp ontlitcp testhse2 online <<<<<
Most unlikely to be the issue, sadly. All else apart, we'd have to
worry which service online maps too.
> Richard Spitz schrieb:
>> Cats <ramwater@uk2.net> schrieb:
>>> The problem is using the tools with a TCP connection to the database:
>>> /etc/services:
>>> v6new 1532/tcp # inhouse informix
>>> server
>>> v6newtcp 1533/tcp # inhouse informix
>>> server
>>>
>>> $INFORMIXDIR/etc/sqlhosts:
>>> v6new onipcshm testhse2 v6new
>>> v6newtcp ontlitcp testhse2 v6newtcp>>
>>> dbaccess can happily connect to v6new and v6newtcp, but attempting to
>>> use any of the v7.20 tools against v6newtcp results in a -25572 error
>>> - "Network driver cannot bind a name to the port."
>>
>> Since "v6new" is defined as a shared memory connection, TCP/IP doesn't
>> play any role in this context.
>>
>> Have you made sure that port 1533 is not already in use by another
>> application or daemon?
>> Can you try changing the entry for "v6newtcp" in your sqlhosts file
>> to the following:
>>
>> v6newtcp onsoctcp testhse2 v6newtcp>>
>> Are server and application running on the same machine?
>> HTH, Richard
--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2007.0226 -- http://dbi.perl.org/
Related threads
- HELP- database won't start !!
- Network driver cannot bind a name to the port.
- Solaris 8, IDSWE 7.31, WARNING: Network Down
- Error 25572 using ESQL/Cobol
- Identically named instances, different hosts