返回
-
标题
SQL Optimizer for Oracle creates QUEST_SL_TEMP_EXPLAIN1 table with column OBJECT_NAME too small [table script provided]. -
说明
QUEST_SL_TEMP_EXPLAIN1 table is created by the tool, with column OBJECT_NAME varchar(30), the size is too small. Oracle now allows longer or bigger size object names. -
解决办法
STATUS:
Waiting for fix in a future release of SQL Optimizer for Oracle.
WORKAROUND:
Use the script below to drop and re-create the table with larger size column.
DROP TABLE QUEST_SL_TEMP_EXPLAIN1 CASCADE CONSTRAINTS;CREATE GLOBAL TEMPORARY TABLE QUEST_SL_TEMP_EXPLAIN1(STATEMENT_ID VARCHAR2(30 BYTE),PLAN_ID NUMBER,TIMESTAMP DATE,REMARKS VARCHAR2(4000 BYTE),OPERATION VARCHAR2(30 BYTE),OPTIONS VARCHAR2(255 BYTE),OBJECT_NODE VARCHAR2(128 BYTE),OBJECT_OWNER VARCHAR2(128 BYTE),OBJECT_NAME VARCHAR2(128 BYTE),OBJECT_ALIAS VARCHAR2(261 BYTE),OBJECT_INSTANCE INTEGER,OBJECT_TYPE VARCHAR2(30 BYTE),OPTIMIZER VARCHAR2(255 BYTE),SEARCH_COLUMNS NUMBER,ID INTEGER,PARENT_ID INTEGER,DEPTH INTEGER,POSITION INTEGER,COST INTEGER,CARDINALITY INTEGER,BYTES INTEGER,OTHER_TAG VARCHAR2(255 BYTE),PARTITION_START VARCHAR2(255 BYTE),PARTITION_STOP VARCHAR2(255 BYTE),PARTITION_ID INTEGER,OTHER LONG,OTHER_XML CLOB,DISTRIBUTION VARCHAR2(30 BYTE),CPU_COST INTEGER,IO_COST INTEGER,TEMP_SPACE INTEGER,ACCESS_PREDICATES VARCHAR2(4000 BYTE),FILTER_PREDICATES VARCHAR2(4000 BYTE),PROJECTION VARCHAR2(4000 BYTE),TIME INTEGER,QBLOCK_NAME VARCHAR2(128 BYTE))ON COMMIT PRESERVE ROWSNOCACHE; -
缺陷ID
SOFO-2645