Drop schema cascade returns error 20123 complaining about user-defined transaction

[Weishiun Tsai]

The QA regression tests have run into this problem several times. Drop schema cascade would returns error 20123 complaining that a user-defined transaction has been started. When this occurred, any statements run after that would continue to see this error until a new trafci session is started.

There is no certain way to reproduce this problem, but it does occur every now and then to cause test failures. This bug report is created to document this problem. Some analysis needs to do be done from the implementation of drop schema cascade to see what could have caused this problem to happen.

Here are two occurrences seen on the v1125_0830 build:

fullouterjoins/fullouterjoins:
SQL>drop schema trafodion.fullouterjoins_test_sql8 cascade;
*** ERROR[20123] A user-defined transaction has been started. This DDL operation cannot be performed. [2014-11-26 09:24:53]

dmls_rollback/r23fix:
SQL>drop schema trafodion.dmls_rollback_r23fix cascade;
*** ERROR[20123] A user-defined transaction has been started. This DDL operation cannot be performed. [2014-11-26 08:24:50]

[Weishiun Tsai (wei-shiun-tsai)]

It's believed that the following 3 bug reports have the same root cause:

https://bugs.launchpad.net/trafodion/+bug/1396801 'Drop schema cascade returns error 20123 complaining about user-defined transaction'
https://bugs.launchpad.net/trafodion/+bug/1401683 'DDL operations see error 8841 about transaction started by SQL'
https://bugs.launchpad.net/trafodion/+bug/1404442 'Random create schema failures due to inaccessible _MD_ tables'

The fix for 1404442 was put in on 1/16. Ran through both the v0116 (v1.0.0rc1) and the v0117 build. Did not see any of the aforementioned problems. This bug report will now be closed.