Re: Informix Network Connection

Michael Krzepkowski wrote: > If you have typed the below stuff, you're excused. > If it was pasted, see below: > > Thomas Ronayne wrote: > >> Please excuse me for being so stupid, but I've been through the >> administrators guide and all the helpful information provided here and >> I still don't quite get it. I beg your pardon - I forgot that you're still having trouble on Linux and was addressing a more general point - and I did not do enough spell checking. I also intended to change the subject to make it clear I wasn't directly answering the Linux issue; now I am, so the original subject is OK again. oltlitcp would work better than either oltlttcp or oltlitpc - and then only on a system such as Solaris (which is what I use by default) that uses TLI instead of sockets. On Linux, you need to use olsoctcp (or onsoctcp - the 'ol' and 'on' prefixes are interchangeable synonyms). I'm also not sure that Linux supports stream pipes - olipcstr - so I'd leave that out of your configuration, both sqlhosts and $ONCONFIG. >> Following your example below, I have onconfig like this (no NETTYPE >> entries): >> >> DBSERVERNAME fubar_23 # Name of default database server >> DBSERVERALIASES fubar_23_shm # Name of network database server >> DBSERVERALIASES fubar_23_str # Name of network database server >> DBSERVERALIASES fubar_23_tcp # Name of network database server>> >> and sqlhosts like this: >> >> fubar_23 oltlttcp fubar fubar_23 >> fubar_23_shm olipcshm fubar fubar_23_shm>> fubar_23_str olipcstr fubar fubar_23_str >> fubar_23_tcp oltlitpc fubar fubar_23_tcp >> > fubar_23 oltlitcp > fubar_23_tcp oltlitcp > > For Linux s/b onsoctcp anyways. > >> and /etc/services like this: >> >> # IBM Informix Software >> fubar_23 1625/tcp # IBM Informix 7.x engine shared >> fubar_23_tcp 1725/tcp # IBM Informix 7.x engine network >> >> and oninit does this: >> >> oninit: Fatal error in initializing ASF with 'ASF_INIT_DATA' flags; >> asfcode = '25507'. +25507 (error; should be negative!): The specified service name or protocol is unknown. This is probably because you are using oltlitcp instead of olsoctcp, and/or because you are using olipcstr on a platform where it is not supported. Have you looked at running 'oninit -v', or 'oninit -iv' if you are still initializing your system as I rather think you are. It might yield some extra information. There might also be some information in the file identified by MSGPATH in the $ONCONFIG file. >> What in the blue blazes am I doing stupid? > > BTW: Have you looked at your /etc/hosts ? > I had issues when "127.0.0.1 localhosts fubar" were in one line. > > HTH > > Michael > >> Jonathan Leffler wrote: >> >>> >>> I think I mentioned this in passing recently - I can't remember when, >>> so I'll repeat myself. >>> >>> With the shared memory (and stream - olipcstr) connections, there is >>> no need for the 'service name' (column 4) to be an entry in the >>> /etc/services file or its moral (or, more importantly, functional) >>> equivalent. The names do need to be unique across all servers on the >>> given machine. So, I routinely use: >>> >>> xyz_23 oltlttcp xyz xyz_23 >>> xyz_23_shm olipcshm xyz xyz_23_shm >>> xyz_23_str olipcstr xyz xyz_23_str >>> xyz_23_tcp oltlitpc xyz xyz_23_tcp>>> >>> Of these, only xyz_23 and xyz_23_tcp need to appear in /etc/services. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2003.04 -- http://dbi.perl.org/

Jonathan Leffler wrote: > > I beg your pardon - I forgot that you're still having trouble on Linux > and was addressing a more general point - and I did not do enough > spell checking. I also intended to change the subject to make it > clear I wasn't directly answering the Linux issue; now I am, so the > original subject is OK again. > > oltlitcp would work better than either oltlttcp or oltlitpc - and then > only on a system such as Solaris (which is what I use by default) that > uses TLI instead of sockets. On Linux, you need to use olsoctcp (or > onsoctcp - the 'ol' and 'on' prefixes are interchangeable synonyms). > I'm also not sure that Linux supports stream pipes - olipcstr - so I'd > leave that out of your configuration, both sqlhosts and $ONCONFIG. > > +25507 (error; should be negative!): The specified service name or > protocol is unknown. > > This is probably because you are using oltlitcp instead of olsoctcp, > and/or because you are using olipcstr on a platform where it is not > supported. > > Have you looked at running 'oninit -v', or 'oninit -iv' if you are > still initializing your system as I rather think you are. It might > yield some extra information. There might also be some information in > the file identified by MSGPATH in the $ONCONFIG file. > What I've done is give up -- the goal was to get Apache, PHP, and Informix talking nice to one another and by using only onsoctcp I can get that to happen (I've wasted enough of my and other generous peoples' time on this). I have discovered that I cannot mix onsoctcp and onipcshm and onsocimc (in any combination) on this system -- one would think that one could have a shared memory and sockets instance running on the same box, but, no joy. Why this is, well, I dunno. The chart in the release notes seems to indicate that mixing these is possible, but there you are -- not on a Slackware 9.1 release -- it appears to be pick one and be happy. So, thanks again to all and to all a good night.