** Could not connect to server for database <DATABASE>, errno <ERRNO>. (1432)

[Kishor Chari]

Dear All,

A client is up against a strange issue. After upgrade from PROGRESS 91d to 91e. The user PC's flash the message ** Could not connect to server for database <DATABASE>, errno <ERRNO>. (1432) when starting MFG/PRO client session. It can be simulated by starting simultaneous client sessions and error will come up at 3-4 session.

There were no changes scripts.

Client PC: WinXp
OS: CentOS release 5.4 (Final)
Kernel: 2.6.18-164.11.1.el5


Parameter file:


-db mfglive
-ld qaddb -H dutec2 -S mfglive -N TCP
-znotrim -trig triggers
-db hlplive
-ld qadhelp -H dutec2 -S hlplive -N TCP
-db admlive
-ld qadadm -H dutec2 -S admlive -N TCP
-d dmy -yy 1920 -Bt 350 -c 30 -D 100 -mmax 3000 -nb 200 -s 63 -p mf.p


DB Startup Script:


#!/bin/sh
# file: start.tpl
# Script to start database servers.

# tokens:
# &DLC = Progress Directory
# &LOOP-DB-START = start of database loop
# &LOOP-DB-END = end of database loop
# &START-SERVER = command line to start current DB in database loop

DLC=/opt/dlc91e;export DLC
PATH=$PATH:$DLC;export PATH
PROMSGS=$DLC/promsgs;export PROMSGS
PROTERMCAP=$DLC/protermcap;export PROTERMCAP

#loop-db-start
$DLC/bin/proserve /data/live/mfglive -S mfglive -H dutec2 -N TCP -Mn 30
$DLC/bin/proserve /data/live/hlplive -S hlplive -H dutec2 -N TCP -Mn 30
$DLC/bin/proserve /data/live/admlive -S admlive -H dutec2 -N TCP -Mn 30
$DLC/bin/_mprshut /data/live/mfglive -C apw
$DLC/bin/_mprshut /data/live/hlplive -C apw
$DLC/bin/_mprshut /data/live/admlive -C apw
# $DLC/bin/_mprshut /data/live/mfglive -C watchdog
#loop-db-end



TIA..

 

[vinod_home]

Do you have any value for ERRNO in the message
** Could not connect to server for database <DATABASE>, errno <ERRNO>. (1432)

 

[Kishor Chari]

The errno value is Zero - 0.

 

[Kishor Chari]

Friends any lead on this? Please assist.

 

[RealHeavyDude]

Dear friend,

your database startup parameters seem odd to me. You specify -Mn (maximum number of servers) but you skip -n (maximum number of processes that can connect to the database). Therefor you are running the multi-user defaults - and I doubt they will suit your needs.

You don't tell your friends what kind of database license you're running. There is a limit on -n on the workgroup database license of 63 regardless of your parameter settings. Only the enterprise database license will lift this limit.

Generally you should have a look into the startup parameters: -n, -Mn, -Ma and -Mi. With these parameters you specify how many processes can connect to the database and how remote clients are served with individual servers. -n should be greater than -Mn x -Ma. In the documentation you'll find a detailed description on how to use this parameters and what their multi-user defaults are.

Since you've posted this question in the DataServers and ODBC forum: Does your problem occur on both 4GL and SQL92 connections or is it tied to one client type?

Regards, RealHeavyDude.

 

[kishorchari]

Apologies off radar . Thanks and -Mn -Mi -Ma -n did the trick.