-25572: Network driver cannot bind a name to the port
James Beck
elicit any responses so I thought I'd try a subject that has
previously had responses. :-)
Our problem:
We had Informix (7.30UC9) successfully running on Solaris 6, and
were able to connect to it from a variety of other platforms,
including some esql/c (7.23) apps running on another Solaris 6 box.
The esql/c apps use esql/c libs and the informix libs (libixasf.so, I
believe).
We are doing a bunch of H/W reorg and ...
We shut down the instance on Solaris 6 and moved the databases to
another (7.30) instance running on Solaris 5. The esql/c apps still
work (after adjusting the INFORMIXSQLHOSTS and INFORMIXSERVER).
Next, we moved the apps (along with the libs) to a Solaris 8 box and
we get the following:
25572: Network driver cannot bind a name to the port.
Exec format error
I have played with this extensively and even installed the Informix
binaries etc. so that I could run dbaccess. I can get our apps (and
dbaccess) to work on Solaris 7 (& 6 & 5), but not Solaris 8. I am not
trying to run Informix on Solaris 8, but I presume this is related to
the same 25572 error that occurs when people try to run the 7.3x
Informix engine of Solaris-8.
We have to run this on Solaris 8 since the apps require direct access
to other S/W installed on that box. We don't want to recode to work
around the Informix issues. What are our options? How can I fix 7.30
Informix connectivity from Solaris 8 to ...
Thanks in anticipation,
James Beck
Murray Wood
There is a Solaris IP patch required. It should have been loaded with
Solaris (latest patches) when the machine was built, but if not contact Tech
Support for the patch number.
MW
Dirk Moolman
Do you have several nettypes running under different ports ? The first thing
I would do, it to start eliminating these by commenting out one at a time,
and trying to start up the database engine again. When it starts up you will
know which port is causing the problem. This is how I solved a similar
problem on my side. One of my servernames was running on a port already
being used by something else.
In my case I could change the port number (/etc/services) without much
difficulty (without affecting anything else), and the problem was solved !
I think you can also see if a port is in use by using the netstat command,
but I'm not too familiar with netstat. Someone else might be able to comment
on that.
Dirk
William Rice
I am pretty sure you need a newer version of the client. IIRC
Informix had issues when upgrading from 2.7 to 2.8 which required them
to patch their client software...
karlo reggiani
"Murray Wood" <mur...@quanta.co.nz> wrote in message
> There is a Solaris IP patch required. It should have been loaded with
> Solaris (latest patches) when the machine was built, but if not contact Tech
> Support for the patch number.
>
I'm looking for this patch on Sun web site but I', not able to find
it!
I'm trying to install the Sparc/Solaris 8 IDS 2.70.UC3-1 available on
www.informix.com/evaluate.
I'm having the "Network driver cannot bind a name to the port" error
as described on other post.
But which is this Solaris patch? Which is the number??????
Thanks
karlo
Tsutomu Ogiwara
Hi karlo.
If you use IDS 7.3x or IDS 9.2x, encountered BUG#124759 that
is ON SOLARIS 8, SERVER FAILS TO BUILD SYSMASTER BECAUSE BUILDSMI CONNECT TO
DATABASE FAILS WITH ERROR 25572 WITH "EXEC FORMAT ERROR" USING TLITCP.
Sounds like it is FIXED 9.21.UC4 and 7.31.UD1.
Regards.
--
Tsutomu / Japan.
_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com