DB2 - Problem description
Problem IT16272 | Status: Closed |
ADMIN_GET_TAB_COMPRESS_INFO TABLE FUNCTION RETURNED SQL0901N ERROR WITH LOAD PENDING TABLESPECE HAVING PARTITIONED TABLE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When a tablespace was in load pending state and sysproc.admin_get_tab_compress_info() was called, it returned SQL0901N error. SQL0901N is not appropriate error number for this case. This happenes when a partitioned table exists on the tablesapace. If the tablespace does not have partitioned table in it, SQL0668N is returned. The following is an example. $ db2 "create table test_tab (col1 char(5) not null , col2 char(5) not null ) distribute by hash (col1) partition by range (col2) (part part0 starting('1') ending('2'))"  $ db2 "load from /dev/null of del method P (1) replace into test_tab nonrecoverable" * Aborting load with pressing Ctrl+C. db2 "SELECT VARCHAR(TABSCHEMA,30) TABSCHEMA,VARCHAR(TABNAME,30) TABNAME, LOAD_STATUS, NO_LOAD_RESTART FROM SYSIBMADM.ADMINTABINFO WHERE LOAD_STATUS <> 'NULL'" TABSCHEMA                      TABNAME                        LOAD_STATUS  NO_LOAD_RESTART ------------------------------ ------------------------------ ------------ --------------- E105Q7A                        TEST_TAB                       PENDING      N $ db2 "select * from table(sysproc.admin_get_tab_compress_info(NULL,NULL))" TABSCHEMA                                                        TABNAME  <snippet> HMON_COLLECTION                                                  0               0 DATA                                        0  0                    0                 0                      0  0 SQL0901N  The SQL statement or command failed because of a database system error. (Reason "".)  SQLSTATE=58004 | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * User using DPF * **************************************************************** * PROBLEM DESCRIPTION: * * See error description * **************************************************************** * RECOMMENDATION: * * Upgrade to V10.5 Fix Pack 9. * **************************************************************** | |
Local Fix: | |
None. SQL0901N can be safely ignored. | |
Solution | |
This problem is first fixed in DB2 V10.5 Fix Pack 9. | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.07.2016 27.09.2017 27.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |