Informix Client on Solaris 8
A user installed the Informix Client SDK on Solaris 8 (SPARC) and got SQLCODE -25572 ("Network driver cannot bind a name to the port") when connecting via dbaccess and SDK-based programs, while the identical setup on Solaris 2.6 worked fine. Respondents suggested checking /etc/services entries, the sqlhosts file (especially correct hostname/service fields), INFORMIXSERVER, and name resolution (uname -n, /etc/hosts, DNS); another noted Informix had not yet certified any products for Solaris 8. The poster verified these settings without success, and the thread ends with a request for diagnostic output rather than a recorded fix.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
Has anyone successfully installed the Informix Client SDK on a Solaris 8 (SPARC) machine? I get errorcode -25572 when I try to connect to the database server - the same installation on a Solaris 2.6 host does not cause any problems. Thanks Sent via Deja.com http://www.deja.com/ Before you buy.
Have you checked /etc/services, $INFORMIXDIR/etc/sqlhosts, $INFORMIXSERVER? How did you try to connect to the server? walther@my-deja.com wrote: > Has anyone successfully installed the Informix Client SDK on a Solaris > 8 (SPARC) machine? > > I get errorcode -25572 when I try to connect to the database server - > the same installation on a Solaris 2.6 host does not cause any problems. > > Thanks > > Sent via Deja.com http://www.deja.com/ > Before you buy.
In article <39194595.CDDBE442@mail.ru>,
maratkotik@mail.ru wrote:
> Have you checked /etc/services, $INFORMIXDIR/etc/sqlhosts,
$INFORMIXSERVER and $INFORMIXDIR/etc/sqlhosts are the same as on the
(working) Solaris 2.6 clients.
We've never modified /etc/services on any client-machine during the
informix-installation. We use port-numbers in the sqlhosts file
instead. After reading your message I replaced the number with a new
servicename in the sqlhosts-file and inserted a new line into
the /etc/services file. Same result.
SQLCODE=-25572
Network driver cannot bind a name to the port.
> How did you try to connect to the server?
dbaccess and some client-programs (compiled on 2.6 and 8), which use
the Informix Client SDK
Thanks for your time.
>
> walther@my-deja.com wrote:
>
> > Has anyone successfully installed the Informix Client SDK on a
Solaris
[...]
Sent via Deja.com http://www.deja.com/
Before you buy.
walther@my-deja.com wrote: > > Has anyone successfully installed the Informix Client SDK on a Solaris > 8 (SPARC) machine? I was talking with Informix telesales toward the end of April, and they said that as of that time no Informix products had been certified for Solaris 8. That may have changed by now. Walt. -- Walt Hultgren Manager, Information Technology Yerkes Research Center of Emory University Mailto:walt@rmy.emory.edu -- 404-727-0648
Did you remember to change the appropriate entries in sqlhosts? I
recall receiving this error after inattentively copying a sqlhosts file
over from another (functional) informixserver to a fresh install and not
correctly editing the hostname field.
walther@my-deja.com wrote:
> In article <39194595.CDDBE442@mail.ru>,
> maratkotik@mail.ru wrote:
> > Have you checked /etc/services, $INFORMIXDIR/etc/sqlhosts,
> $INFORMIXSERVER and $INFORMIXDIR/etc/sqlhosts are the same as on the
> (working) Solaris 2.6 clients.
>
> We've never modified /etc/services on any client-machine during the
> informix-installation. We use port-numbers in the sqlhosts file
> instead. After reading your message I replaced the number with a new
> servicename in the sqlhosts-file and inserted a new line into
> the /etc/services file. Same result.
>
> SQLCODE=-25572
> Network driver cannot bind a name to the port.
>
> > How did you try to connect to the server?
> dbaccess and some client-programs (compiled on 2.6 and 8), which use
> the Informix Client SDK
>
> Thanks for your time.
>
> >
> > walther@my-deja.com wrote:
> >
> > > Has anyone successfully installed the Informix Client SDK on a
> Solaris
> [...]
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
Ok. Then you should check sometthing else:
uname -n, /etc/hosts or DNS or NIS (ping `uname -n`),
$INFORMIXDIR/etc/$ONCONFIG.
I think that something may be inconsistent.
walther@my-deja.com wrote:
> In article <39194595.CDDBE442@mail.ru>,
> maratkotik@mail.ru wrote:
> > Have you checked /etc/services, $INFORMIXDIR/etc/sqlhosts,
> $INFORMIXSERVER and $INFORMIXDIR/etc/sqlhosts are the same as on the
> (working) Solaris 2.6 clients.
>
> We've never modified /etc/services on any client-machine during the
> informix-installation. We use port-numbers in the sqlhosts file
> instead. After reading your message I replaced the number with a new
> servicename in the sqlhosts-file and inserted a new line into
> the /etc/services file. Same result.
>
> SQLCODE=-25572
> Network driver cannot bind a name to the port.
>
> > How did you try to connect to the server?
> dbaccess and some client-programs (compiled on 2.6 and 8), which use
> the Informix Client SDK
>
> Thanks for your time.
>
> >
> > walther@my-deja.com wrote:
> >
> > > Has anyone successfully installed the Informix Client SDK on a
> Solaris
> [...]
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
In article <39196472.6DBBE5F9@rmy.emory.edu>, Walt Hultgren <walt@rmy.emory.edu> wrote: > I was talking with Informix telesales toward the end of April, and they > said that as of that time no Informix products had been certified for > Solaris 8. That may have changed by now. Hmm, on the other hand Sun claims "binary compatibility with previous releases". Walther Sent via Deja.com http://www.deja.com/ Before you buy.
In article <391A5D72.CAF0C0AA@mail.ru>, maratkotik@mail.ru wrote: > Ok. Then you should check sometthing else: > uname -n, /etc/hosts or DNS or NIS (ping `uname -n`), DNS, /etc/hosts, uname -n resolv all to the same name (and to same IP) > $INFORMIXDIR/etc/$ONCONFIG. onconfig on a client-machine? I thought this was the configuration file of the server. Thanks, Walther Sent via Deja.com http://www.deja.com/ Before you buy.
I suppose that all of software on the server side and client side
compiled exactly for the platform they used on.
If so I think it's time to post necessary files & outs of some
commands to get the TRUTH (in one letter for convenience).
1. from the server side:
uname -a
traceroute <server_name> (or smth like $ping -s sun 1 1|grep icmp_seq)
traceroute <client_name> (or smth like $ping -s sun 1 1|grep icmp_seq)
onstat -V
/etc/services (ALL entries (if several) about informix)
$INFORMIXDIR/etc/sqlhosts
cat $INFORMIXDIR/etc/$ONCONFIG|grep SERVER
2. fromthe client side:
uname -a
traceroute <server_name> (or smth like $ping -s <server_name> 1 1|grep
icmp_seq)
traceroute <client_name> (or smth like $ping -s <client_name> 1 1|grep
icmp_seq)
/etc/services (ALL entries (if several) about informix)
$INFORMIXDIR/etc/sqlhosts
env|grep INFORMIXSERVER
walther@my-deja.com wrote:
> In article <391A5D72.CAF0C0AA@mail.ru>,
> maratkotik@mail.ru wrote:
> > Ok. Then you should check sometthing else:
> > uname -n, /etc/hosts or DNS or NIS (ping `uname -n`),
> DNS, /etc/hosts, uname -n resolv all to the same name (and to same IP)
>
> > $INFORMIXDIR/etc/$ONCONFIG.
> onconfig on a client-machine? I thought this was the configuration file
> of the server.
>
> Thanks,
> Walther
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.