Kbase 16060: Symix Application Hangs Between 8:00 and 8:30 on Connect
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/05/1998 |
|
Symix Application Hangs Between 8:00 and 8:30 on Connect
We have investigated some reports from Symix customers where their
database application seems to hang when users are trying to connect
to the database usually between 8:00am and 8:30am. The users
that are already connected continue working without being affected.
The problem is that any user trying to connect at that time will stay
hung for several minutes and then will be freed up to connect to the
database.
This is a Symix application issue. See below for the official
information from Symix regarding what is causing this issue and how to
resolve it. For further information on this issue please contact
your Symix Support Representative.
[[ slowlogn.txt : 2276 in slowlogn.txt ]]
Excerpt from Symix Regarding Slow Logins
Relevant for Symix customers on Symix version 2.5, 2.5a, 2.6,
2.6i, 2.7, 3.0, 4.0, 5.0 and SL2 (SyteLine Ver. 2) .
Always slow; particularly in the morning
If the login process is slow on an ongoing basis,
particularly at the beginning of the day, it is probably
due to having a large number of stranded records in the
database's tmp-sum file. These records are probably a result
of the server being terminated with users in the database.
Running crash recovery from the administration menu will
empty the tmp-sum file and alleviate the problem.
When a user logs into SYMIX, the system assigns the
user a cur-sum-id equal to the current time and then attempts
to create a record in the tmp-sum file with that id, with
all of the other fields being blank. If a tmp-sum record
already exists with that id (i.e. someone else is in the
database with that cur-sum-id), the system continues setting
cur-sum-id to the current time and checking for a matching
tmp-sum record until none is found. When the user logs out of
SYMIX or goes into the PROGRESS editor, his tmp-sum record is
deleted.
If the server terminates or is shutdown while users
are in the database, their tmp-sum record is not deleted. If
this happens many times without crash recovery being run
before restarting the server, hundreds of tmp-sum records may
accumulate with the id field holding different login times
(exact second of login). If most users enter the system early
in the morning, there may be tmp-sum records for a large
percentage of the seconds within the busy login time. This may
cause the system to perhaps set cur-sum-id hundreds of times
before finding a second that does not have a matching tmp-sum
record which results in the slow login.
August 1996
Progress Software Technical Support Note # 16060