Kbase P100329: rfutil fails with 5291 message
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/01/2010 |
|
Status: Verified
SYMPTOM(s):
rfutil fails with 5291 message
You have attempted to connect to a database with too many users connected to it. Retry the connection later, or increase -n on the server. (5291)
FACT(s) (Environment):
OpenEdge 10.0B
Progress 9.1E
CAUSE:
The -n value was reached. When rfutil is run, it requires to connect to the database. If -n has been reached, then the connection cannot be made.
The following 9.1E on UNIX example illustrates the behaviour -
1. Create st file -
# sports.st
#
b
test/sports.b1
#
d "Schema Area":6,32
test/sports.d1
#
d "Info Area":7,32
test/sports_7.d1
#
d "Order Area":8,32
test/sports_8.d1
#
a
test/sports.a1
#
a
test/sports.a2
#
a
test/sports.a3
2. prodb sports sports
3. probkup sports sportsbak00
4. rfutil sports -C aimage begin
5. proserve sports -n 4
The 4260 message in the startup sequence reported in the lg will show -
Maximum Number of Users (-n): 5. (4260)
The specified -n is increased by 1 so that promon or proshut will always be able to connect to the database and thus shut it down.
6. Start 4 sessions against sports: mpro sports
7. rfutil sports -C aimage new returns the 5291
The same behaviour will be seen if probkup online is run against a database for which -n has been reached, or when attempting to start page writers.
FIX:
The 5291 is insofar expected behaviour.
Thus when specifying a value for -n, ensure to specify a value that includes not only the required number of users, but also the number of administration utilities that will run against the database.
Note that -n therefore does not necessarily reflect the number of licensed users (i.e. user sessions that can be started against the database).
Note that an ai switch during processing is not affected by -n being reached.