Run the commands in the right hand panel.

In this step, the data will be inserted into the two temporary tables and the static table again. This will result in an error when the insert attempts to write to the DGTT, this is because we've created a new connection since the DGTT was defined and has since been lost.

The CGTT does continue to allow data to be inserted because the table still exists because we're in the same session, just using a different connection. A simple SELECT statement will show that before we inserted this new data, there was no data previously in the table. This is because the data is private between connections.

While the regular table will continue to allow data to be inserted, it is ineffective as a temporary work area for the application. Note that the data inserted from one of the previous steps is still there and depending on the calculation, this can yield incorrect results. This table cannot be cleaned up easily if the application is multi-threaded. A DELETE issued from one thread will remove all application data from the table including those used by another thread.

  Isolation Automatic cleanup Application Object Support Performance
Static Table
DGTT
CGTT

You should see two failure messages followed by success statements in the lower right. Also in the lower right panel, there should be additional result set tabs.