Error 5291 when connecting to a database.

Clients failing to connect to a database with error 5291
Shared memory clients or remote clients are getting error 5291 when trying to connect to a database.
_progres client session fails with error 5291
Appserver and Webspeed  Agents get stuck in STARTING state on Broker startup 
Appserver and Webspeed startup fails with error (5291) in the Server log 
PROMON or PROSHUT on the database may fail with error 49.
PROMON or PROSHUT on the database generates the below stack trace
 
PROGRESS stack trace as of Tue Mar 19 13:27:28 2013
Command line arguments are
/app/dlc/101b/bin/_mprshut /data1/sharp 
 
(0)  0x4000000000169ba0  uttraceback + 0x60 [/app/dlc/101b/bin/_mprshut]
(1)  0x400000000014ce50  utcore + 0x3a0 at /vobs_prgs/src/ut/utbuf.c:587 [/app/dlc/101b/bin/_mprshut]
(2)  0x400000000014c160  drexit + 0x550 at /vobs_prgs/src/drsys/drsetup.c:931 [/app/dlc/101b/bin/_mprshut]
(3)  0x40000000003d4660  drSigFatal + 0xc0 at /vobs_rkt/src/glue/drsig.c:1255 [/app/dlc/101b/bin/_mprshut]
(4)  0xe000000120757420  ---- Signal 11 (SIGSEGV) delivered ----
(5)  0x400000000014d551  __milli_memset + 0x331 [/app/dlc/101b/bin/_mprshut]
(6)  0x4000000000226cf0  dbGetUsrctl + 0x790 at /vobs_rkt/src/dbmgr/db/dbuser.c:370 [/app/dlc/101b/bin/_mprshut]
(7)  0x4000000000216c40  dbenv2 + 0x700 at /vobs_rkt/src/dbmgr/db/dbopen.c:1555 [/app/dlc/101b/bin/_mprshut]
(8)  0x4000000000213410  dbenv + 0x190 at /vobs_rkt/src/dbmgr/db/dbopen.c:203 [/app/dlc/101b/bin/_mprshut]
(9)  0x40000000002778b0  dsmUserConnect + 0x3b0 at /vobs_rkt/src/dbmgr/dsm/dsmuser.c:128 [/app/dlc/101b/bin/_mprshut]
(10) 0x400000000041c450  drmain_doit + 0x430 at /vobs_rkt/src/dbadmin/drshut.c:1702 [/app/dlc/101b/bin/_mprshut]
(11) 0x40000000000f3fc0  main + 0x160 at /vobs_rkt/src/dbadmin/drshut.c:1202 [/app/dlc/101b/bin/_mprshut]
(12) 0xc000000000044450  main_opd_entry + 0x50 [/usr/lib/hpux64/dld.so]


 

Client processes may be connecting to one or multiple databases.
Database may or may not have multiple database login brokers configured.
When connecting to multiple databases, the databases may or may not have the same -n startup parameter for each database.

System Error 5291 will be displayed when:

1. The -n (Maximum Number of Users) database startup parameter is too low based on the number of clients/processes connecting to a database concurrently.
2. If a client is connecting to more than one database, this error can occur if one of those databases have a -n value that is too low for the number of  clients/processes connecting to it.
3. If using multiple Login Brokers (-m3), this error can occur if the sum of the (-Ma * -Mpb) parameters for the multiple brokers exceeds the -n parameter for a database.

1.  Increase the -n (Maximum Number of Users) parameter for the database to accommodate the total number of clients/processes that will be connecting  to the database.
2. If the database is configured to start multiple login brokers, then validate that the values for -Ma * -Mpb are less than -n.  For additional information on  how to configure secondary brokers and -Ma and -Mn, refer to Articles:

•  How to set up a secondary login broker for SQL-92 connections for Progress 9.1D and above 
•  How to set the values for the startup parameters -Ma, -Mn and -n.

 

References to Other Documentation:

Progress Articles: