DB2 - Problem description
Problem IC91939 | Status: Closed |
LOAD COMMAND USING THE ADMIN_CMD PROCEDURE DOES NOT SHOW ROWS_SK IPPED, ROWS_LOADED, ROWS_DELETED, AND ROWS_COMMITTED WITH DPF | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When using the ADMIN_CMD procedure to load data, the ROWS_SKIPPED, ROWS_LOADED, ROWS_DELETED, AND ROWS_COMMITTED columns are not displayed for partitioned databases. To demonstrate, please review the following reproduction: db2 "connect to sample" db2 "select count(*) from employee" 1 ----------- 42 1 record(s) selected. $ db2 "export to tb1.del of del messages msgs.txt select * from employee" Number of rows exported: 42 db2 "CREATE TABLE db2inst1.test (EMPNO CHAR(6) NOT NULL , FIRSTNME VARCHAR(12) NOT NULL , MIDINIT CHAR(1) , LASTNAME VARCHAR(15) NOT NULL , WORKDEPT CHAR(3) , PHONENO CHAR(4) , HIREDATE DATE , JOB CHAR(8) , EDLEVEL SMALLINT NOT NULL , SEX CHAR(1) , BIRTHDATE DATE , SALARY DECIMAL(9,2) , BONUS DECIMAL(9,2) , COMM DECIMAL(9,2) ) DISTRIBUTE BY HASH(EMPNO) IN USERSPACE1" db2 "ALTER TABLE db2inst1.test ADD CONSTRAINT PK_EMPLOYEE PRIMARY KEY (EMPNO)" DB20000I The SQL command completed successfully. db2 "load from /home/hotel53/db2inst1/tb1.del of del replace into db2inst1.test partitioned db config partitioning_dbpartnums(1)" Agent Type Node SQL Code Result ________________________________________________________________ ______________ LOAD 000 +00000000 Success. ________________________________________________________________ ______________ LOAD 001 +00000000 Success. ________________________________________________________________ ______________ LOAD 002 +00000000 Success. ________________________________________________________________ ______________ PARTITION 001 +00000000 Success. ________________________________________________________________ ______________ PRE_PARTITION 000 +00000000 Success. ________________________________________________________________ ______________ RESULTS: 3 of 3 LOADs completed successfully. ________________________________________________________________ ______________ Summary of Partitioning Agents: Rows Read = 42 Rows Rejected = 0 Rows Partitioned = 42 Summary of LOAD Agents: Number of rows read = 42 Number of rows skipped = 0 Number of rows loaded = 42 Number of rows rejected = 0 Number of rows deleted = 0 Number of rows committed = 42 db2 "select count(*) from db2inst1.test" 1 ----------- 42 1 record(s) selected. db2 "load from /home/hotel53/db2inst1/tb1.del of del insert into db2inst1.test partitioned db config partitioning_dbpartnums(1)" Agent Type Node SQL Code Result ________________________________________________________________ ______________ LOAD 000 +00000000 Success. ________________________________________________________________ ______________ LOAD 001 +00000000 Success. ________________________________________________________________ ______________ LOAD 002 +00000000 Success. ________________________________________________________________ ______________ PARTITION 001 +00000000 Success. ________________________________________________________________ ______________ PRE_PARTITION 000 +00000000 Success. ________________________________________________________________ ______________ RESULTS: 3 of 3 LOADs completed successfully. ________________________________________________________________ ______________ Summary of Partitioning Agents: Rows Read = 42 Rows Rejected = 0 Rows Partitioned = 42 Summary of LOAD Agents: Number of rows read = 42 Number of rows skipped = 0 Number of rows loaded = 42 Number of rows rejected = 0 Number of rows deleted = 42 Number of rows committed = 42 db2 "select count(*) from db2inst1.test" 1 ----------- 42 1 record(s) selected. db2 "call admin_cmd('load from /home/hotel53/db2inst1/tb1.del of del insert into db2inst1.test partitioned db config partitioning_dbpartnums(1)')" Result set 1 -------------- ROWS_READ ROWS_SKIPPED ROWS_LOADED ROWS_REJECTED ROWS_DELETED ROWS_COMMITTED ROWS_PARTITIONED NUM_AGENTINFO_ENTRIES ---------------------------------------------------------------- ---------------------------------------------------------------- ------------------------------------------ 42 - - 0 - - 42 5 1 record(s) selected. Result set 2 -------------- DBPARTITIONNUM SQLCODE TABSTATE AGENTTYPE -------------- ----------- -------------------- -------------------- 0 0 NORMAL LOAD 1 0 NORMAL LOAD 2 0 NORMAL LOAD 1 0 NORMAL PARTITIONING 0 0 NORMAL PRE_PARTITIONING 5 record(s) selected. Return Status = 0 db2 "select count(*) from db2inst1.test" 1 ----------- 42 1 record(s) selected. db2 "call admin_cmd('load from /home/hotel53/db2inst1/tb1.del of del insert into db2inst1.test partitioned db config partitioning_dbpartnums(1)')" Result set 1 -------------- ROWS_READ ROWS_SKIPPED ROWS_LOADED ROWS_REJECTED ROWS_DELETED ROWS_COMMITTED ROWS_PARTITIONED NUM_AGENTINFO_ENTRIES ---------------------------------------------------------------- ---------------------------------------------------------------- ------------------------------------------ 42 - - 0 - - 42 5 1 record(s) selected. Result set 2 -------------- DBPARTITIONNUM SQLCODE TABSTATE AGENTTYPE -------------- ----------- -------------------- -------------------- 0 0 NORMAL LOAD 1 0 NORMAL LOAD 2 0 NORMAL LOAD 1 0 NORMAL PARTITIONING 0 0 NORMAL PRE_PARTITIONING 5 record(s) selected. Return Status = 0 $ db2 "select count(*) from db2inst1.test" 1 ----------- 42 1 record(s) selected. The above demonstrates that the user will be unable to determine which call to the admin_cmd procedure succeeded. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v9.7 fix pack 9 * **************************************************************** | |
Local Fix: | |
Use the LOAD command instead. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 v9.7 fix pack 9 | |
Workaround | |
See local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC97601 IC97830 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 26.04.2013 17.12.2013 17.12.2013 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP9 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.9 | |
9.7.0.9 |