首页 > 数据库 >IT25589: LIST HISTORY COMMAND FAILS WITH DB21018E ERROR WHEN THE HISTORY FILE CONTAINS A DROPPED TAB

IT25589: LIST HISTORY COMMAND FAILS WITH DB21018E ERROR WHEN THE HISTORY FILE CONTAINS A DROPPED TAB

时间:2022-11-10 15:23:54浏览次数:40  
标签:FAILS DB21018E LIST system DROPPED TABLE HISTORY

Known Issues

 https://www.ibm.com/mysupport/s/defect/aCI3p000000kF7p/dt159458?language=en_US

IT25589: LIST HISTORY COMMAND FAILS WITH DB21018E ERROR WHEN THE HISTORY FILE CONTAINS A DROPPED TABLE EVENT WITH LONGER TABLE NAME.

  • LIST HISTORY command fails with DB21018E error when the history 
    file contains a DROPPED TABLE event which the length of the     
    table name is longer than 128KB.                                
                                                                    
                                                                    
    $ db2 list history dropped table all for sample                 
                                                                    
                        List History File for sample                
                                                                    
    Number of matching file entries = 1                             
                                                                    
                                                                    
     Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log    
    Backup ID                                                       
     -- --- ------------------ ---- --- ------------ ------------   
    --------------                                                  
      D  T  20180628135510                                          
    000000000000253700040004                                        
                                                                    
    ----------------------------------------------------------------
    ------------                                                    
      "DB2INST1 "."TABLE1" resides in 1 tablespace(s):              
                                                                    
     00001 TS8K                                                     
                                                                    
    ----------------------------------------------------------------
    ------------                                                    
        Comment: DROP TABLE                                         
     Start Time: 20180628135510                                     
       End Time: 20180628135510                                     
         Status: A                                                  
                                                                    
    ----------------------------------------------------------------
    ------------                                                    
      EID: 5                                                        
                                                                    
    DB21018E  A system error occurred. The command line processor   
    could not                                                       
    continue processing.                                            
                                                                    
                                                                    
    The db2diag.log shows SQLO_QUE_BAD_HANDLE error as follows:     
                                                                    
    2018-06-28-14.11.52.809384-240 E82157A699           LEVEL: Error
    (OS)                                                            
    PID     : 29294808             TID : 1              PROC : db2bp
    INSTANCE: db2inst1             NODE : 000                       
    HOSTNAME: db2server                                             
    EDUID   : 1                                                     
    FUNCTION: DB2 UDB, oper system services, sqlowqueInternal,      
    probe:40                                                        
    MESSAGE : ZRC=0x870F003E=-2029060034=SQLO_QUE_BAD_HANDLE "Bad   
    Queue Handle"                                                   
              DIA8555C An invalid message queue handle was          
    encountered.                                                    
    CALLED  : OS, -, msgsnd                                         
    OSERR   : EINVAL (22) "A system call received a parameter that  
    is not valid."                                                  
    DATA #1 : system V message queue identifier.,                   
    PD_TYPE_SYSV_QUEUE_ID, 4 bytes                                  
    0x43544554                                                      
    DATA #2 : Pointer, 8 bytes                                      
    0x000000011088f080                                              
    DATA #3 : unsigned integer, 8 bytes                             
    65527                                                           
                                                                    
    Show less

  •  

    ****************************************************************

    * USERS AFFECTED:                                              *

    * ALL                                                          *

    ****************************************************************

    * PROBLEM DESCRIPTION:                                         *

    * See Error Description                                        *

    ****************************************************************

    * RECOMMENDATION:                                              *

    * Upgrade to Db2 11.1 Mod 4 Fixpack 5 or higher                *

    ****************************************************************

     

  • First fixed in Db2 11.1 Mod 4 Fixpack 5                         

  • Delete the problematic event by PRUNE HISTORY command.        

     

    --------------------------------------------------------

    ----

     如果你认为文章有用,欢迎打赏。

     

     

      
                                                                    

标签:FAILS,DB21018E,LIST,system,DROPPED,TABLE,HISTORY
From: https://www.cnblogs.com/z-cm/p/16877133.html

相关文章

  • k8s iptables 改造ipvs
    1.修改iptables为ipvs模式 ipvs采用的hash表,iptables采用一条条的规则列表。集群数量越多iptables规则就越多,而iptables规则是从上到下匹配,所以效率就越是低下......
  • 视频直播app源码,element表格table点击添加背景色
    视频直播app源码,element表格table点击添加背景色  cellclick(row,column){   this.row=row;   this.column=column;  },   tableCellStyl......
  • ElementNotInteractableException: Message: element not interactable
    ElementNotInteractableException:Message:elementnotinteractable 原因分析:1、未放鼠标在元素上,元素的标签:2、放了鼠标在元素上:元素的标签:3、从元素上移开鼠标,......
  • ant design vue table报错h is not defined
    报错原因使用table时由于columns数据太多,所以将columns中的数据拆分到一个单独的常量js文件中,又因为需要使用customRender,里面有<a-tag>之类的标签,需要使用jsx进行渲染,因......
  • QTableWidget 右键菜单
    头文件中:QMenu*m_pContextMenu;QAction*m_pActionDel;构造函数中:ui->tableWidget->setContextMenuPolicy(Qt::CustomContextMenu)voidCreateMenu(){......
  • iptables
    iptables-F//删除iptables现有规则iptables-L[-v[vv]-n]//查看iptables规则iptables-tnat-APOSTROUTING-s10.10.10.0/24-oeth1-jMASQUERADE......
  • elementUI 搜索条件、table、页脚封装
    一共分成了两个组件:组件一:搜索条件=>SearchParams.vue组件二:el-table和el-pagination=>TablePagintion考虑到业务的使用场景没用做过多的封装。(1)组件一:搜索条件代......
  • Vue技术之“关于sortable排序的使用”
    Vue关于sortable排序的使用方案1在使用sortable后要注意给el-table-column中加入prop="overdueDays"参数,不然会找不到需要排序的数据<el-table-columnprop="overdueDa......
  • ElementUI中Table和Switch组件中插槽scope应用使用场景
    ElementUI中Table和Switch组件中插槽scope应用使用场景ElementUI安装npmielement-ui-S引入Elementmain.js内容添加importElementUIfrom'element-ui';impo......
  • vue+element ui <el-table>中有多页数据,查看完详情,回到查看前的页码
    我们的查看里面有添加部分数据的功能,添加成功后,页面返回关闭,页面需要重新调取接口获取新的数据,但是客户的需求是,关闭后,还应回到当前页,而不是回到第一页。思路:将当前页面的接......