The reason you are getting 25588 for shm server demo_on and -908 for
tcp server demo_on_tcp is because your server is not up. You need to
be able to bring up server first to attempt any connection. What does
the online.log file says? It could be a memory allocation issue or
something else.

Perform the steps as Martin has explained taking one protocol at a time.

FYI: Dont use port number value greater than 65535 as that's the
limit; but use something way higher than 1024.

--
Ravi

On 4/13/05, Martin Fuerderer <MARTINFU@de.ibm.com> wrote:
> Hi again,
>
> try to do one thing at a time.
>
> First:
>
> a) Configure your server with SHM connection only.
> Remove the other server name for TCP/IP connection from
> your $ONCONFIG file (DBSERVERALIASES in your case).
> Then bring up the server and make sure that you can connect
> to it (e.g. using dbaccess and $INFORMIXSERVER env variable
> set to "demo_on") via the SHM connection protocol.
>
> After that try the other thing:
>
> b) Configure your server with TCP/IP connection only.
> Put your "demo_on_tcp" as DBSERVERNAME and leave
> DBSERVERALIASES still empty.
> You may have to change the port number in your /etc/services file.
> 1528 is a very low number. It could be in use already. Try a number
> that is much higher and at the same time unlikely to be used already.
> My guess, out of the blue (no pun intended , would be 82171/tcp.
> Whatever number you choose, check that it is not already listed
> in /etc/services.
> Bring the server up and try to connect to it using the TCP/IP protocol.
> You now have to change the client's $INFORMIXSERVER env variable
> to "demo_on_tcp".
> You first may want to do the connect locally (i.e. on the same machine).
> Then you may try from a remote machine. Here make sure that the
> service name in the client's sqlhosts file translates to the same port
> number as it does on the server (in above example 82171/tcp; the name
> of the service can be different; important is the port number "behind
> it",
> so that a connection request from the client can reach the correct port
> where the server is listening).
>
> Only after all this was successful:
>
> c) Combine the two configurations to have both, SHM connections and
> TCP/IP connections enabled, then check that everything is still working.
>
> Doing things one at a time will help immensely to find out where a problem
> is, have a clearer view of things and thus more easily spot and fix
> problems.
>
> Regards,
> Martin
> --
> Martin Fuerderer
> IBM Informix Development Munich, Germany
> Information Management
>
> owner-informix-list@iiug.org wrote on 13.04.2005 05:27:00:
> > my sqlhosts set :
> > demo_on onipcshm linux linux_c
> > demo_on_tcp onsoctcp linux sqlexex
> > onconfig set :
> > DBSERVERNAME demo_on
> > DBSERVERALIASES demo_on_tcp
> > NETTYPE ipcshm,1,8,CPU
> > NETTYPE soctcp,1,8,NET
> >
> > services set:
> > linux_c 1527/tcp
> > sqlexex 1528/tcp
> >
> > --
> > Message posted via http://www.dbmonster.com
>
> sending to informix-list
>

sending to informix-list