Update stats failures due to schema PUBLIC_ACCESS_SCHEMA

[Weishiun Tsai]

Starting from the v1218_0830 build, update statistics are seeing wide-spread failures complaining about not being able to create objects in the PUBLIC_ACCSES_SCHEMA. This might have something to do with the ANSI schema change that went in in the v1218_0830 build. The ANSI schema change requires any schema to be physically created before it can be used.

Here is an example of such failure:

SQL>update statistics for table trafodion.g_tpcds1x.customer_address on every column sample;
*** ERROR[9214] Object TRAFODION.PUBLIC_ACCESS_SCHEMA.SQLMX_157679540284239117_1418926426_841447 could not be created. [2014-12-18 18:14:02]
*** ERROR[1003] Schema TRAFODION.PUBLIC_ACCESS_SCHEMA does not exist. [2014-12-18 18:14:02]
*** ERROR[9201] Unable to DROP object TRAFODION.PUBLIC_ACCESS_SCHEMA.SQLMX_157679540284239117_1418926426_841447. [2014-12-18 18:14:02]
*** ERROR[1389] Object TRAFODION.PUBLIC_ACCESS_SCHEMA.SQLMX_157679540284239117_1418926426_841447 does not exist in Trafodion. [2014-12-18 18:14:02]

[Roberta Marton (roberta-marton)]

Change was added that if the PUBLIC_ACCESS_SCHEMA does not exist, the temporary sample table will be created in the same schema as the source table.

[Weishiun Tsai (wei-shiun-tsai)]

Was able to run through the global table creation with update stats on the v0113 build without having to apply the workaround of manually creating the PUBLIC_ACCESS_SCHEMA schema first. This problem is now fixed.