Error 25588 : IDS 7.31UD1 on Solaris8

Hello, We installed IDS 7.31UD1 on a solaris 8 machine. Most off the time all works fine but sometimes we can't connect to the database anymore: error "25588: The appl process cannot connect to OnLine server ol_hziv600T" is given. There are no special messages in the onlinelog. After a restart off the instance (onmode -k, oninit) we can connect again. In the sqlhosts file, the nettype for this server "ol_hziv600T" is set to "onipcshm", an alias "ol_hziv600TR" has been declared too, his nettype is set to "ontlitcp". In the onconfig-file however, there is no line "NETTYPE icpshm" defined! There is only a line "NETTYPE tlitcp,1,300,NET". Can this cause the problem? If not, what can be wrong? Thanks in advance, Kurt Van Gompel.

No, that should be fine. You need to have entries for both servers in your sqlhosts.. if you are= going to connect via both = "KURT VAN GOMPEL" = <kvangompel@caami = -hziv.fgov.be> = To Sent by: ids@iiug.org = ids-bounces@iiug. = cc org = Subj= ect Error 25588 : IDS 7.31UD1 on = 09/05/2007 09:13 Solaris8 [9901] = AM = = = Please respond to = ids@iiug.org = = = Hello, We installed IDS 7.31UD1 on a solaris 8 machine. Most off the time all works fine but sometimes we can't connect to the database anymore: error "25588: The appl process cannot connect to OnLi= ne server ol_hziv600T" is given. There are no special messages in the onlinelog. After a restart off the= instance (onmode -k, oninit) we can connect again. In the sqlhosts file, the nettype for this server "ol_hziv600T" is set = to "onipcshm", an alias "ol_hziv600TR" has been declared too, his nettype = is set to "ontlitcp". In the onconfig-file however, there is no line "NETTYPE icpshm" defined= ! There is only a line "NETTYPE tlitcp,1,300,NET". Can this cause the problem? If not, what can be wrong? Thanks in advance, Kurt Van Gompel. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

Hello, I did some more tests and I found out that after 50 connections, the next one cannot connect anymore!!! Kurt.

Many of us follow this forum on email, so there's not neccessarily any threading. PLEASE don't delete the entire msg history when replying or extending a thread. What's this about? Details. What are the NETTYPE settings which NETTYPE is referenced in the INFORMIXSERVER or connect statement? Art S. Kagel ----- Original Message ----- From: Kurt Van Gompel <ids@iiug.org> To: ids@iiug.org At: 9/05 11:08:07 Hello, I did some more tests and I found out that after 50 connections, the next one cannot connect anymore!!! Kurt. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

If there is no NETTYPE for a protocol the default is equivalent to: NETTYPE ipcshm,1,50,<vp> Where <vp> is CPU if the protocol is defined in DBSERVERNAME and NET if it is defined in DBSERVERALIASES. For shared memory connections, the number of connections per poll thread times the number of poll threads fixes the maximum number of shared memory connections that the server will allow, in your case, since you are using the defaults, that's 50 - exactly what you are experiencing. To get more connections add an explicit NETTYPE for ipcshm which should specify CPU class polling with one poll thread for each CPU VP that's configured and the number of connections configured for your needs. Art S. Kagel ----- Original Message ----- From: Kurt Van Gompel <ids@iiug.org> To: ids@iiug.org At: 9/05 10:14:12 Hello, We installed IDS 7.31UD1 on a solaris 8 machine. Most off the time all works fine but sometimes we can't connect to the database anymore: error "25588: The appl process cannot connect to OnLine server ol_hziv600T" is given. There are no special messages in the onlinelog. After a restart off the instance (onmode -k, oninit) we can connect again. In the sqlhosts file, the nettype for this server "ol_hziv600T" is set to "onipcshm", an alias "ol_hziv600TR" has been declared too, his nettype is set to "ontlitcp". In the onconfig-file however, there is no line "NETTYPE icpshm" defined! There is only a line "NETTYPE tlitcp,1,300,NET". Can this cause the problem? If not, what can be wrong? Thanks in advance, Kurt Van Gompel. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Thank you Art for your quick response. First of all sorry for dropping the threat in the second message I posted! I thought the number specified in the parameter NETTYPE was the maximum of concurrent connections of that type. We are having the problem after 50 sequential connections! Do I misunderstand the functioning of NETTYPE? I read somewhere that it is not necessary to specify the number of concurrent users for a shared memory connection in the config-file, is that true? Kurt.

This extract from the manual might make things bit more clear for you..= . Basically that number is no. of connections per poll thread.... NETTYPE connection_type,poll_threads,c_per_t,vp_class connection_type, identifies the protocol-interface combination to which the poll threads are assigned. You typically set this field to match the connection_type field of a dbservername entry that is in the sqlh= osts file or registry. poll_threads is the number of poll threads assigned to the connection type. Se= t this value to no more than NUMCPUVPS for any connection type. c_per_t is the number of connections per poll thread. Use the following f= orm ula to calculate this number: c_per_t =3D connections / poll_threads connections is the maximum number of connections that you expect the indicated connection type to support. For shared-memory connections (ipcshm), double the number of connections for = best performance. vp_class is the class of virtual processor that can run the poll threads. Specify CPU if you have a single poll thread that runs on a CPU V= P. For best performance, specify NET if you require more than one po= ll thread. If you are running Windows, specify NET in all cases. The= default value for this field depends on the following conditions:= If the connection type is associated with the dbservername = that is listed in the DBSERVERNAME parameter, and no previous NETTYPE parameter specifies CPU explicitly, the default VP class is CPU. If the CPU class is already taken, the defaul= t is NET. If the connection type is associated with a dbservername th= at the DBSERVERALIASES parameter specifies, the default VP cla= ss is NET. = "KURT VAN GOMPEL" = <kvangompel@caami = -hziv.fgov.be> = To Sent by: ids@iiug.org = ids-bounces@iiug. = cc org = Subj= ect Re:Error 25588 : IDS 7.31UD1 on = 09/05/2007 01:10 Solaris8 [9906] = PM = = = Please respond to = ids@iiug.org = = = Thank you Art for your quick response. First of all sorry for dropping the threat in the second message I post= ed! I thought the number specified in the parameter NETTYPE was the maximum= of concurrent connections of that type. We are having the problem after 50= sequential connections! Do I misunderstand the functioning of NETTYPE? I read somewhere that it is not necessary to specify the number of concurrent users for a shared memory connection in the config-file, is that true? Kurt. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

You have shared memory (shm) connections confused with tcp connections. For shared memory, you specify a "ceiling". It will not exceed it. For tcp connections, it will exceed the "ceiling"; however, you should still specify what you deem to be the "average" high ceiling for connections. Take care. Clifton M. Bean Informix DBA / AIX System Admin Currency Technics & Metrics Phone: (972) 812-1411 x244 -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of KURT VAN GOMPEL Sent: Wednesday, September 05, 2007 1:10 PM To: ids@iiug.org Subject: Re:Error 25588 : IDS 7.31UD1 on Solaris8 [9906] Thank you Art for your quick response. First of all sorry for dropping the threat in the second message I posted! I thought the number specified in the parameter NETTYPE was the maximum of concurrent connections of that type. We are having the problem after 50 sequential connections! Do I misunderstand the functioning of NETTYPE? I read somewhere that it is not necessary to specify the number of concurrent users for a shared memory connection in the config-file, is that true? Kurt. **************************************************************************** *** Forum Note: Use "Reply" to post a response in the discussion forum.

You do not have to specify a NETTYPE setting for any connection protocol type, however, if you do not you get the defaults: 1 poll thread and 50 connections. As I said, and this is in the Administrator's Reference as well, shared memory connections configured in NETTYPE are the maximum number of connections of that type that can be handled concurrently. For other connection types the NETTYPE configuration is used as a starting point and the actual number of concurrent connections can exceed the setting, but not for shared memory connections. Art S. Kagel ----- Original Message ----- From: Kurt Van Gompel <ids@iiug.org> To: ids@iiug.org At: 9/05 14:10:42 Thank you Art for your quick response. First of all sorry for dropping the threat in the second message I posted! I thought the number specified in the parameter NETTYPE was the maximum of concurrent connections of that type. We are having the problem after 50 sequential connections! Do I misunderstand the functioning of NETTYPE? I read somewhere that it is not necessary to specify the number of concurrent users for a shared memory connection in the config-file, is that true? Kurt. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

I disagree with this statement Manoj: > For best performance, specify NET if you require more than one poll > thread. If you are running Windows, specify NET in all cases. That used to be the advice and I've always disagreed with it. A couple of years ago I finally got the IDS folk to look at my recommendations versus theirs and to test them out. The results were that the docs were change to match fairly closely to my own recommendations. Those being: Shared memory connections ONLY in CPU VPs and the number of poll threads must be equal to the number of CPU VPs for best responsiveness if you will be actively using the shared memory connections for more than occassional maintenance connections. TCP connections ONLY in NET VPs and there should only be a few of those configured sufficient to limit the number of connections managed by a single poll thread to fewer than 200 which IBM considers to be efficient. For a full explanation of why I make these recommendations, see the entry on NETTYPE in the IDS FAQ. Art S. Kagel ----- Original Message ----- From: Manoj Mohan <ids@iiug.org> To: ids@iiug.org At: 9/05 14:19:22 This extract from the manual might make things bit more clear for you..= .. Basically that number is no. of connections per poll thread.... NETTYPE connection_type,poll_threads,c_per_t,vp_class connection_type, identifies the protocol-interface combination to which the poll threads are assigned. You typically set this field to match the connection_type field of a dbservername entry that is in the sqlh= osts file or registry. poll_threads is the number of poll threads assigned to the connection type. Se= t this value to no more than NUMCPUVPS for any connection type. c_per_t is the number of connections per poll thread. Use the following f= orm ula to calculate this number: c_per_t =3D connections / poll_threads connections is the maximum number of connections that you expect the indicated connection type to support. For shared-memory connections (ipcshm), double the number of connections for = best performance. vp_class is the class of virtual processor that can run the poll threads. Specify CPU if you have a single poll thread that runs on a CPU V= P. For best performance, specify NET if you require more than one po= ll thread. If you are running Windows, specify NET in all cases. The= default value for this field depends on the following conditions:= If the connection type is associated with the dbservername = that is listed in the DBSERVERNAME parameter, and no previous NETTYPE parameter specifies CPU explicitly, the default VP class is CPU. If the CPU class is already taken, the defaul= t is NET. If the connection type is associated with a dbservername th= at the DBSERVERALIASES parameter specifies, the default VP cla= ss is NET. = "KURT VAN GOMPEL" = <kvangompel@caami = -hziv.fgov.be> = To Sent by: ids@iiug.org = ids-bounces@iiug. = cc org = Subj= ect Re:Error 25588 : IDS 7.31UD1 on = 09/05/2007 01:10 Solaris8 [9906] = PM = = = Please respond to = ids@iiug.org = = = Thank you Art for your quick response. First of all sorry for dropping the threat in the second message I post= ed! I thought the number specified in the parameter NETTYPE was the maximum= of concurrent connections of that type. We are having the problem after 50= sequential connections! Do I misunderstand the functioning of NETTYPE? I read somewhere that it is not necessary to specify the number of concurrent users for a shared memory connection in the config-file, is that true? Kurt. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. = ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Thanks.. I will look at the FAQ.. Good to know such facts... Manoj = "ART KAGEL, = BLOOMBERG/ 731 = LEXIN" = To <kagel@bloomberg. ids@iiug.org = net> = cc Sent by: = ids-bounces@iiug. Subj= ect org Re:Error 25588 : IDS 7.31UD1 on = Solaris8 [9911] = = 09/05/2007 02:53 = PM = = = Please respond to = ids@iiug.org = = = I disagree with this statement Manoj: > For best performance, specify NET if you require more than one poll > thread. If you are running Windows, specify NET in all cases. That used to be the advice and I've always disagreed with it. A couple = of years ago I finally got the IDS folk to look at my recommendations vers= us theirs and to test them out. The results were that the docs were change= to match fairly closely to my own recommendations. Those being: Shared memory connections ONLY in CPU VPs and the number of poll thread= s must be equal to the number of CPU VPs for best responsiveness if you will b= e actively using the shared memory connections for more than occassional maintenance connections. TCP connections ONLY in NET VPs and there shou= ld only be a few of those configured sufficient to limit the number of connecti= ons managed by a single poll thread to fewer than 200 which IBM considers t= o be efficient. For a full explanation of why I make these recommendations, = see the entry on NETTYPE in the IDS FAQ. Art S. Kagel ----- Original Message ----- From: Manoj Mohan <ids@iiug.org> To: ids@iiug.org At: 9/05 14:19:22 This extract from the manual might make things bit more clear for you..= =3D ... Basically that number is no. of connections per poll thread.... NETTYPE connection_type,poll_threads,c_per_t,vp_class connection_type, identifies the protocol-interface combination to which the poll threads are assigned. You typically set this field to match the connection_type field of a dbservername entry that is in the sqlh=3D osts file or registry. poll_threads is the number of poll threads assigned to the connection type. Se=3D t this value to no more than NUMCPUVPS for any connection type. c_per_t is the number of connections per poll thread. Use the following f=3D orm ula to calculate this number: c_per_t =3D3D connections / poll_threads connections is the maximum number of connections that you expect the indicated connection type to support. For shared-memory connections (ipcshm), double the number of connections for =3D best performance. vp_class is the class of virtual processor that can run the poll threads. Specify CPU if you have a single poll thread that runs on a CPU V=3D P. For best performance, specify NET if you require more than one po=3D ll thread. If you are running Windows, specify NET in all cases. The=3D default value for this field depends on the following conditions:=3D If the connection type is associated with the dbservername =3D that is listed in the DBSERVERNAME parameter, and no previous NETTYPE parameter specifies CPU explicitly, the default VP class is CPU. If the CPU class is already taken, the defaul=3D t is NET. If the connection type is associated with a dbservername th=3D at the DBSERVERALIASES parameter specifies, the default VP cla=3D ss is NET. =3D "KURT VAN GOMPEL" =3D <kvangompel@caami =3D -hziv.fgov.be> =3D To Sent by: ids@iiug.org =3D ids-bounces@iiug. =3D cc org =3D Subj=3D ect Re:Error 25588 : IDS 7.31UD1 on =3D 09/05/2007 01:10 Solaris8 [9906] =3D PM =3D =3D =3D Please respond to =3D ids@iiug.org =3D =3D =3D Thank you Art for your quick response. First of all sorry for dropping the threat in the second message I post= =3D ed! I thought the number specified in the parameter NETTYPE was the maximum= =3D of concurrent connections of that type. We are having the problem after 50= =3D sequential connections! Do I misunderstand the functioning of NETTYPE? I read somewhere that it is not necessary to specify the number of concurrent users for a shared memory connection in the config-file, is that true? Kurt. ***********************************************************************= =3D ******** Forum Note: Use "Reply" to post a response in the discussion forum. =3D ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. ***********************************************************************= ******** Forum Note: Use "Reply" to post a response in the discussion forum. =

Hello Art, I understand that in the line NETTYPE ipcshm, the number of sessions indicates the maximum number of concurrent sessions allowed. But I have created a small script that makes a connection to the database (with isql), then selects the numer of rows in a table and quits. When I execute this script over and over again, at the 51the run, it hangs and after a while the error 25588 is given. These are not 50 concurrent sessions. When running "onstat -u" or "onstat -g ses", I don't see any connection! Kurt.

Ahh, sorry, that wasn't clear. I was convinced you were talking about concurrent connections. You are correct, sequential connections with only a single, or a small number of concurrent connections, should not hit the ceiling at the concurrent connection limit. I seem to remember an old bug affecting earlier 7.31 and 9.30 releases with similar properties. Look into upgrading, the latest IB is 7.31xD8 or xD9, but certainly scan the CDI posting history on the IIUG web site for similar problems to get details. There may be a work around. Art S. Kagel ----- Original Message ----- From: Kurt Van Gompel <ids@iiug.org> To: ids@iiug.org At: 9/06 4:12:46 Hello Art, I understand that in the line NETTYPE ipcshm, the number of sessions indicates the maximum number of concurrent sessions allowed. But I have created a small script that makes a connection to the database (with isql), then selects the numer of rows in a table and quits. When I execute this script over and over again, at the 51the run, it hangs and after a while the error 25588 is given. These are not 50 concurrent sessions. When running "onstat -u" or "onstat -g ses", I don't see any connection! Kurt. ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.