Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
1.0.2
-
None
-
While running a full regression to ensure I hadn't broken anything, I found that test105 sometimes failed.
The failure is caused by something having to do with an auto-increment column and the DBRM. a lock isn't released properly and the DBRM asserts and shuts down. Recovery doesn't work and a restart is needed.
I'm guessing that an alter table to add an auto-increment is what's causing the issue. It's also possible that this is masked by release code (I'm using debug), but that doesn't mean it isn't ready to pounce at a customer site.While running a full regression to ensure I hadn't broken anything, I found that test105 sometimes failed. The failure is caused by something having to do with an auto-increment column and the DBRM. a lock isn't released properly and the DBRM asserts and shuts down. Recovery doesn't work and a restart is needed. I'm guessing that an alter table to add an auto-increment is what's causing the issue. It's also possible that this is masked by release code (I'm using debug), but that doesn't mean it isn't ready to pounce at a customer site.
-
2016-19
Description
Copying Description that David Hall put in Environment field here
While running a full regression to ensure I hadn't broken anything, I found that test105 sometimes failed.
The failure is caused by something having to do with an auto-increment column and the DBRM. a lock isn't released properly and the DBRM asserts and shuts down. Recovery doesn't work and a restart is needed.
I'm guessing that an alter table to add an auto-increment is what's causing the issue. It's also possible that this is masked by release code (I'm using debug), but that doesn't mean it isn't ready to pounce at a customer site.
Attachments
Issue Links
- is part of
-
MCOL-280 Beta issues
- Closed