Kbase 13122: Differences between 6.2N 6.2N03
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Differences between 6.2N 6.2N03
Differences between PROGRESS 6.2N and 6.2N03
--------------------------------------------
Differences between PROGRESS 6.2N and 6.2N03
Description: Rdb 5.1 and deadlocks
When running the Progress Dataserver for Rdb against 5.1
of Rdb you may want to consider disabling adjustable lock
granularity. This may be helpful in cases where you may
experience deadlocks. To disable adjustable lock granu-
larity use the SQL alter schema command. The example
of this command is as follows:
alter schema filename customer adjustable lock granularity
is disabled;
when the filename is customer.
For more information on this command refer to your Rdb
documentation.
Description: PROGRESS Server Hanging
The PROGRESS Server occassionally hangs because of
the PROGRESS locking mechanism.
Description: Protection on .r files
Protection mask is now inherited from existing
PROGRESS compiled procedure object (.r) files.
Description: Maximum open file limit
The maximum open file limit is now 99.
Description: PROGRESS Subprocess Creation
PROGRESS now uses the User Identification Code
(UIC) of the user and not the USERNAME for
subprocess creation.
Description: CTRL-C during Database Shutdown
The PROGRESS server hangs when you press CTRL-C
during Database Shutdown operations.
Description: Logical PRO$DISCONNECT_WAIT_TIME
You can alter the Connecting/Disconnecting time by
defining the VMS logical PRO$DISCONNECT_WAIT_TIME before
you start a server, as shown in the following command example.
The default value is 1 second and the maximum value is 99.
If you alter this logical, PROGRESS might generate
Socket Errors on high activity networks.
$ DEFINE PRO$DISCONNECT_WAIT_TIME 3
Description: Error condition with Remote Clients
For PROGRESS releases lower than 6.2N03, remote
client processing signals, such as Hangup and
CONTROL_C, can cause remote client server (not
broker) crashes. This issue can cascade into a
full database crash.
Description: WorkFile with Two Parts
The template of a work file is a concatenation of two
parts. If the second part has more than 16 fields,
it has a skip table. You must remove the skip
table before you concatenate the two parts.
Description: MTUNLKDB inservice counter
Occasionally during the backing out of TRANSACTIONS, our
inservice counter would not decrement properly.
The end result is an ABNORMAL SHUTDOWN of the
Database, posting in log file would include MTUNLKDB .
Progress Software Technical Support Note # 13122