Kbase P131518: The sequence value drops to NULL intermittently when application is run against MS SQL Server DataSe
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
1/6/2010 |
|
Status: Verified
SYMPTOM(s):
The sequence value drops to NULL intermittently when application is run against MS SQL Server DataServer
The current value of a sequence suddenly drops to NULL
FACT(s) (Environment):
Running in a multi-user environment
No special actions have been noted before the problem occurs
Windows
OpenEdge 10.1B
OpenEdge 10.1C
MS SQL 2005
CAUSE:
Bug# OE00172741
FIX:
Upgrade to 10.1C03 or later. And then recreate the schema holder from scratch using protoMSS process. If performing protoMSS is not possible use the following steps to correct the existing sequence on the MS SQL Server:
1. Connect to OE database and dump out the sequence.df so it contains all the sequences on the .df file. The dump .df file name is by default _sequence.df.
2. Create an empty database and load the _sequence.df to load the sequence.
3. Fake out protoMSS process while you are connected to the DB created in step 2. Leaving the *load sql* unchecked (by default it is checked. You do not even have to have the real odbc dsn name. If the sql server tables are owned by dbo, you just have to enter "dbo" with out the double quotes on the user name.
4. This will dump the .sql file with all the sequences.
5. Edit the .sql file to strip out all the create table for sequence information. But do not delete "drop procedure ...
6. Run the .sql file on the t-sql on the sql server 2005 to drop and create the new stored.
If upgrading is NOT possible, add 'SET XACT_ABORT ON' at the beginning of the stored-procedure body for the sequence on the MS SQL Server.