Kbase P127801: Share locks appear in promon on the _sequence table in 10.1B when using NEXT-VALUE
Autor |
  Progress Software Corporation - Progress |
Acesso |
  Público |
Publicação |
  12/20/2007 |
|
Status: Unverified
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1B
SYMPTOM(s):
Share locks appear in promon on the _sequence table in 10.1B when using NEXT-VALUE
CAUSE:
In 10.1B, when the NEXT-VALUE is used on a sequence in a database migrated from a previous release which doesn't have 64 bit sequences enabled, share locks will appear for the _sequence VST table. This was done because of an underlying issue and is intended to protect 32 bit sequences from inheriting 64bit values.
FIX:
To get around this issue enable 64 bit sequences in the database using the following command:
proutil <dbname> -C enableseq64