SQL0668N Operation not allowed for reason code “3” on table “TEST”. SQLSTAT…

 

Problem Description:

Query, operation table report the following error

SQL0668N Operation not allowed for reason code “3” on table “TEST”. SQLSTATE=57016

operation steps:

first, the following error occurred when executing the reorg unlock table

[test@TEST-DB1 ~]$ db2 "reorg table test"
SQL0668N Operation not allowed for reason code "3" on table "test". 
SQLSTATE=57016

Second: the following error occurs when the load empty file terminates the table

[test@TEST-DB1 ~]$ db2 load from/of del terminate into test

Agent Type Node SQL Code Result
______________________________________________________________________________
LOAD 001 +00000000 Success.
______________________________________________________________________________
LOAD 002 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 003 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 004 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 005 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 006 +00000000 Success.
______________________________________________________________________________
LOAD 007 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 008 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 009 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 010 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 011 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 012 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 013 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 014 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 015 -00027902 Init error. Table unchanged.
______________________________________________________________________________
LOAD 016 -00027902 Init error. Table unchanged.
______________________________________________________________________________
RESULTS: 2 of 16 LOADs completed successfully.
______________________________________________________________________________

Summary of LOAD Agents:
Number of rows read = 0
Number of rows skipped = 0
Number of rows loaded = 0
Number of rows rejected = 0
Number of rows deleted = 0
Number of rows committed = 0

SQL27902N LOAD RESTART/TERMINATE is not allowed on a table that is not in 
LOAD PENDING state.

Generally, the above two steps can basically solve the problem that the table can’t be operated, but some can’t be completed as this time

Analysis may be that some partitions are not terminated or are forcibly killed when loading

Third: query partition table status 

[test@TEST-DB1 ~]$ db2 -x "SELECT DBPARTITIONNUM FROM TABLE(SYSPROC.ADMIN_GET_TAB_INFO('TEST','TEST')) AS T where load_status='PENDING' "

Terminate the partition number one by one

[test@TEST-DB1 ~]$db2 load from /dev/null of del terminate into TEST.TEST  partitioned db config OUTPUT_DBPARTNUMS('分区号')

Execution complete

Similar Posts: