[TRAFODION-1948] Scan returns duplicate rows after drop schema cascade

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.0-incubating
• Assignee: Unassigned
• Reporter: Prashanth Vasudev
• Created: 21/Apr/16 13:53
• Updated: 29/Apr/16 05:39
• Resolved: 28/Apr/16 21:17

Description

After a series of statements followed by drop schema cascade, scan of objects table returns duplicate rows.

>>drop schema "t4sch" cascade;

• • • ERROR[1069] Schema TRAFODION.t4sch could not be dropped. Reason: schema t4sch is not empty.
      ObjectsInSchema: SB_HISTOGRAMS SB_HISTOGRAMS

• • • ERROR[1073] Schema TRAFODION.t4sch was partially dropped, call CLEANUP SCHEMA to remove remaining entries.

— SQL operation failed with errors.
>>

>>drop implicit volatile schema cleanup cascade;

• • • ERROR[1069] Schema TRAFODION.VOLATILE_SCHEMA_MXID110000275952123279425519710010000000002 could not be dropped. Reason: schema VOLATILE_SCHEMA_MXID110000275952123279425519710010000000002 is not empty.
      ObjectsInSchema: T4TAB2 T4TAB2

• • • ERROR[1073] Schema TRAFODION.VOLATILE_SCHEMA_MXID110000275952123279425519710010000000002 was partially dropped, call CLEANUP SCHEMA to remove remaining entries.

— SQL operation failed with errors.