Sandhya Sundaresan created TRAFODION-2735:
---------------------------------------------

             Summary: LOB: Drop table/schema returns 8616 error but the drop 
statement can't be retried
                 Key: TRAFODION-2735
                 URL: https://issues.apache.org/jira/browse/TRAFODION-2735
             Project: Apache Trafodion
          Issue Type: Bug
          Components: dtm, sql-exe
    Affects Versions: 2.2-incubating
         Environment: May need to run 2 streams to see the effect of this. But 
see how we handle the 8616 error with LOB objects may be a good place to start.
            Reporter: Sandhya Sundaresan


With the DDL in TRX feature  when a DDL returns the 8616 error, the statement 
is generally rolled back and it can be retried until it succeeds. This, 
however, is not the case for a table/schema with LOB columns. Drop a table or 
schema with internal LOB tables would often returns the 8616 error, and on the 
next retry, returns the 1031 or 1073 error with no further explanation. This is 
likely caused by the 8616 error not handling the internal LOB tables correctly. 
At that moment, using cleanup to clean up the tables and the schema becomes the 
only option.

This is often seen when SQL regression is run with multiple streams. It is 
causing a huge problem for running LOB tests since once a table/schema is not 
dropped cleanly, all tests afterwards get messed up.

Here are some of such failures seen on the AdvEnt2.2 1010 build:

SQL>drop table mytable cascade;
*** ERROR[8616] A conflict was detected during commit processing. Transaction 
has been aborted. [2016-10-12 12:53:54]

SQL>drop table mytable cascade;
*** ERROR[1031] Object TRAFODION.FEATURES_LOB.MYTABLE could not be dropped. 
[2016-10-12 12:54:01]


SQL>drop table mytable1 cascade;
*** ERROR[8616] A conflict was detected during commit processing. Transaction 
has been aborted. [2016-10-12 13:20:20]

SQL>drop table mytable1 cascade;
*** ERROR[1031] Object TRAFODION.FEATURES_LOB.MYTABLE1 could not be dropped. 
[2016-10-12 13:20:37]

*** MISMATCH *** expecting: '--- SQL operation complete.'


SQL>drop schema trafodion.features_lob_TEST007 cascade;
*** ERROR[8616] A conflict was detected during commit processing. Transaction 
has been aborted. [2016-10-12 12:59:48]

SQL>drop schema trafodion.features_lob_TEST007 cascade;
*** ERROR[1031] Object TRAFODION.FEATURES_LOB_TEST007.MYTABLE could not be 
dropped. [2016-10-12 13:00:01]
*** ERROR[1073] Schema TRAFODION.FEATURES_LOB_TEST007 was partially dropped, 
call CLEANUP SCHEMA to remove remaining entries. [2016-10-12 13:00:01]





--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to