Informix Error 25588
error from shared memory dbservernames when more than one are defined for an instance. 25588; shm; shared mem; local connection Technote (troubleshooting) Problem(Abstract) You bring an instance of IDS (Informix Dynamic Server) online with multiple dbservernames configured for shared memory connections. All but the first return 25588 error when trying to connect. Resolving the problem PROBLEM Using the DBSERVERNAME and DBSERVERALIASES configuration file parameters you have defined two or more database server names (dbservernames) in your ONCONFIG configuration file. Two or more of these dbservernames are associated with a shared memory communication protocol in the sqlhosts file, so two or more dbservernames represent shared memory connections. Only the first shared memory dbservername defined in the ONCONFIG file functions correctly. When you try to connect using any of the other shared memory connections the database server returns: "25588 The appl process cannot connect to Dynamic Server ." server-name The name of your database server. Tip: If you are unfamiliar with dbservernames and how they are defined and used see the "Client/Server Communications" chapter of the IBM Informix Administrator's Guide. SCOPE The following products and operating systems are affected: Product Name Product Version(s) Hardware Vendor Operating System IBM Informix Dynamic Server All All All IBM Informix Extended Parallel Server All All All CAUSE The database server supports one shared memory dbservername. The database server does not give a warning if more than one is configured. Important: This is only one possible cause of the problem. If this document does not give you what you need then search for other documents with the same problem. SOLUTION This is expected behavior. HOW TO AVOID THIS PROBLEM Use at most one shared memory dbservername. Cross reference information Segment Product Component Platform Version Edition Information Management Informix Extended Parallel Server Not Applicable UNIX All Versions All Editions Document information More support
shm; connect; connecting; connects Technote (troubleshooting) Problem(Abstract) This document explains how to resolve error 25588 when attempting to connect to Informix Dynamic Server (IDS) using a shared memory connection. Symptom You are attempting to connect to an IBM Informix Dynamic Server (IDS) instance using a shared memory connection and you receive the following error : 25588: http://www-01.ibm.com/support/docview.wss?uid=swg21111903 The appl process cannot connect to Dynamic Server . No such file or directory Cause Each time an IDS instance is started, a file is created in the /INFORMIXTMP directory. The format of the filename is .inf.servicename where servicename is the name of the service used by the http://www.ibm.com/support/docview.wss?uid=swg21264764 instance as defined in the sqlhosts file. If the file .inf.servicename is removed or renamed, any attempt to connect to the instance using a shared memory connection will fail with the error 25588. Important: This is only one possible cause of the problem. If this document does not provide you with a solution to your problem, you should search for other documents that refer to this topic. Resolving the problem You will need to restart the database instance to resolve this problem. Document information More support for: Informix Servers Software version: 7.3, 9.4, 10.0, 11.1 Operating system(s): AIX, DYNIX/ptx, Digital Unix (OSF1)(TRU64), HP-UX, IRIX, Linux, Reliant UNIX, Sinix, Solaris Reference #: 1264764 Modified date: 2007-10-03 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
sqlhosts file. A system failure can informix error 25588 also produce this message. If you can find no immediate cause for the failure, note the circumstances and contact your database server administrator for assistance. The shared memory communication subsystem is down or not functioning. Contact the database server administrator to report the problem.
Copyright Privacy