Greetings folks.
Bottom line on top:
An Informix server on a Linux host (which requires Socket protocols) needs to connect to a server on a Solaris host, which only supports tli protocols.
Disclaimer/warning: I'm back in my usual form. π
We are trying to set a Linux box for informix and it seems OK for local connection. But when I try dbaccess <database>@<solaris server> I get this:
25507: Unknown error message -25507
Well, actually, finderr on that number has 3 semi-coherent messages, which I will take on one at a time:
The value of the NETTYPE configuration parameter in the ONCONFIG file is not
the same as the NETTYPE setting in the sqlhosts file.
Let's see: My onconfig NETTYPE settings are:
ipcshm,1,50,CPU
soctcp,32,500,NET
While on sqlhosts, the entry for that solaris host is:
<server> ontlitcp <host> <port#> # Hiding actual server names & ports
Indeed, my onconfig has no NETTYPE for the Solaris protocol, tli. So lemme add such a parameter on the Linux side:
NETTYPE tlitcp,32,500,NET # Copied from Solaris prod server.
Now we need to bounce the Linux Informix server:
The specified service name or protocol is unknown. Error -25507.
OUCH! Referring to this IBM article, we see that adding that tli NETTYPE was a mistake; Linux will not support tli in any manner. So let's take it out of $ONCONFIG... And the server comes up. This is consistent with the third paragraph in that finderr output:
The protocol entry in the ONCONFIG file or sqlhosts file is not supported by
the operating system on your computer.
HMMmm... Let's see about editing that sqlhosts entry for the tli, substituting soc for tli. Sounds counter-intuitive to me but..
<server> ontsoctcp <host> <port#>
Nope: I still get that 25507 error, though no crash, of course. But it makes sense: My target server is still under Solaris and uses tli for for connections.
BTW, since I'm using port numbers, there is no issue of "service name not found"; I'm not using a service name. So the 2nd paragraph from finderr is not relevant.
Another BTW: I am able to connect to the target host via telnet using the target host name and port number. So I think I've eliminated two suggestions I would otherwise be sure to get.
So there we have the short and long of it. We are open to suggestions here.
Thanks much!
------------------------------
+-------------------------------------------------+
| If you're a bird, be an early, early bird |
| and catch a fat for for your breakfast plate. |
| Yes, if you're a bird, be an early, early bird. |
| But if you're a worm, sleep late! |
+--------------------------- Shell Silverstein ---+
------------------------------