首页 > 其他分享 >IT24765: TIMING ISSUE IN PACKAGE CACHE WORKSPACE MAY CAUSE PANIC

IT24765: TIMING ISSUE IN PACKAGE CACHE WORKSPACE MAY CAUSE PANIC

时间:2024-03-25 10:26:16浏览次数:23  
标签:__ IT24765 PACKAGE DATA bytes sqlra sqlW FP8sqlrr PANIC

IT24765: TIMING ISSUE IN PACKAGE CACHE WORKSPACE MAY CAUSE PANIC

https://www.ibm.com/mysupport/s/defect/aCI0z0000004vGZ/dt076912?language=fi

  • There is a timing issue where there is a brief moment in time   
    that the state of a sibling entry in package cache workspace can
    be set to a particular state outside of latch control, so the   
    entry might be reused or freed up from the lru lists in the     
    cache by someone else, as a result, panic may happen due to     
    memory corruption.                                              
                                                                    
    The stack can be vary:                                          
                                                                    
    Stack 1:                                                        
     sqle_panic                                                     
     sqloCrashOnCriticalMemoryValidationFailure                     
     SQLO_MEM_POOL::diagnoseMemoryCorruptionAndCrash                
     sqloDiagnoseFreeBlockFailure                                   
     sqlofmblkEx                                                    
     sqlra_sqlW_mem_free_sibling_list                               
     sqlra_sqlW_mem_freespace                                       
     sqlra_sqlW_check_for_cleanup                                   
     sqlra_sqlW_get_dynamic_section_new                             
     sqlra_load_var                                                 
     sqlra_get_var                                                  
     sqlrr_execimmd                                                 
     sqlrr_execimmd                                                 
                                                                    
    Stack 2:                                                        
                                                                    
    PID     : 1704972              TID : 79974          PROC :      
    db2sysc 0                                                       
    INSTANCE: db2inst1             NODE : 000           DB   :      
    SAMPLE                                                          
    APPHDL  : 0-360                APPID:                           
    *LOCAL.db2inst1.180203112927                                    
    AUTHID  : DB2INST1             HOSTNAME: MYHOST                 
    EDUID   : 79974                EDUNAME: db2agent (SAMPLE) 0     
    FUNCTION: DB2 UDB, SQO Latch Tracing,                           
    SQLO_SLATCH_CAS64::getConflictComplex, probe:210                
    MESSAGE :                                                       
    ZRC=0x870F00FD=-2029059843=SQLO_SLATCH_ERROR_HELDS_WITH_SHARED_W
    AITER                                                           
              "A latch with X starvation policy should StarveX latch
    should not be held shared and have a shared waiter."            
    CALLED  : OS, -, unspecified_system_function                    
    DATA #1 : String, 13 bytes                                      
    invalid latch                                                   
    DATA #2 : File name, 16 bytes                                   
    sqloLatchCAS64.C                                                
    DATA #3 : Source file line number, 8 bytes                      
    592                                                             
    DATA #4 : Codepath, 8 bytes                                     
    0                                                               
    DATA #5 : String, 136 bytes                                     
    0xFAB0A00020002EA0:                                             
       held X: 0                                                    
       reserved for X: 0                                            
       shared holders: 11936                                        
       firstSharIndex: 0x200                                        
       firstExclIndex: 0x1D5850                                     
                                                                   
    DATA #6 : LatchMode, PD_TYPE_LATCH_MODE, 8 bytes                
    0x10000 (SQLO_LATCH_MODE_EXCLUSIVE)                             
    DATA #7 : String, 397 bytes                                     
                                                                   
       state         = 0xFAB0A00020002EA0                           
                     =                                              
                           held X: 0                                
                           reserved for X: 0                        
                           shared holders: 11936                    
                           firstSharIndex: 0x200                    
                           firstExclIndex: 0x1D5850                 
                                                                    
       starve X mode = true                                         
       xWaitCount    = 0                                            
       requestCount  = 0                                            
       identity      = NO_IDENTITY (0)                              
                                                                   
    DATA #8 : Pointer, 8 bytes                                      
    0x0a00020002ede448                                              
    DATA #9 : Hexdump, 16 bytes                                     
    0x0A00020002EDE448 : FAB0 A000 2000 2EA0 0A00 0200 02ED E108    
    .... ...........                                                
    CALLSTCK: (Static functions may not be resolved correctly, as   
    they are resolved to the nearest symbol)                        
      [0] 0x090000000DC8088C                                        
    dumpDiagInfoAndPanic__17SQLO_SLATCH_CAS64CFCPCcCUiCUlT3ClT3CiT1T
    3T7 + 0x2FC                                                     
      [1] 0x090000000CA0C814                                        
    getConflictComplex__17SQLO_SLATCH_CAS64FCUl + 0xE8C             
      [2] 0x090000000CE80D54 getConflict__17SQLO_SLATCH_CAS64FCUl + 
    0x118                                                           
      [3] 0x090000000B8D9F2C                                        
    sqlra_sqlW_mem_freespace__FP8sqlrr_cbUlPUli + 0x1C4             
      [4] 0x090000000B8A561C                                        
    sqlra_sqlW_check_for_cleanup__FP8sqlrr_cbUlP7OSSTick + 0x264    
      [5] 0x090000000B899D7C                                        
    sqlra_sqlW_get_dynamic_section_new__FP8sqlrr_cbP16sqlra_cached_v
    ar + 0x14B8                                                     
      [6] 0x090000000B89ADF8                                        
    sqlra_load_var__FP8sqlrr_cbP16sqlra_cached_varP14SQLP_LOCK_INFOP
    b + 0xAC                                                        
      [7] 0x090000000B89AA8C sqlra_get_var__FP8sqlrr_cbiT2bPbT5 +   
    0x884                                                           
      [8] 0x090000000C587808                                        
    sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x114            
      [9] 0x090000000C587B10                                        
    sqlrr_execute__FP14db2UCinterfaceP9UCstpInfo + 0x41C            
    Show less

  •  

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

    * USERS AFFECTED:                                              *

    * N/A                                                          *

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

    * PROBLEM DESCRIPTION:                                         *

    * See Error Description                                        *

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

    * RECOMMENDATION:                                              *

    * Upgrade to Db2 v10.5 FP10 or later.                          *

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

     

  • The problem is firstly fixed on Db2 v10.5 FP10.                 

 

Status

Closed

Programming Error - Fix provided (PER)

A fix is available

DB2 Version 10.5 Fix Pack 11 for Linux, UNIX, and WindowsDB2 Version 10.5 Fix Pack 10 for Linux, UNIX, and Windows

Fixed Version(s) :

Subscribe

By subscribing, you receive periodic emails alerting you to the status of the known issue, along with a link to the fix after it becomes available.

Notify me when a known issue for this product changes

Manage my notifications
  • Product

    Db2 Linux, Unix and Windows

    Software version

    10.5

    Document number

    DT076912

    Last modified

    2024年2月26日 GMT+8 14:38

  • APAR Number

    IT24765

    Reported component id

    DB2FORLUW

    Reported component release

    A50

    Status

    Closed

    PTF in error

    NoPE

    HIPER:

    NoHIPER

    Special attention

    NoSpecatt

    -Product Specific

    Submitted date:

    2018年4月17日 GMT+8 11:00

    Closed date:

    2018年7月12日 GMT+8 11:00

    Last modified date:

    2024年2月26日 GMT+8 14:38

     

    ------------------------------------------------------------------------------------------
    如果你觉得文章有用,欢迎打赏

     

标签:__,IT24765,PACKAGE,DATA,bytes,sqlra,sqlW,FP8sqlrr,PANIC
From: https://www.cnblogs.com/z-cm/p/18093801

相关文章

  • 「CF627C」 Package Delivery
    题意需要驾驶一辆汽车行驶\(d\)单位的距离,汽车的油箱最多装\(n\)个单位的油,出发时邮箱装满了油。路上有\(m\)个加油站,第\(i\)个加油站在距离起点\(x_i\)的位置,每个单位的油价值\(p_i\)。求到达终点的最小花费,如果无法到达输出-1。分析这题和CSP-J2023T2很像,只......
  • package-lock.json
    生成package-lock.json文件:1、运行npminstall命令,npm将自动生成package-lock.json文件。2、如果你已经安装了依赖,但是没有生成package-lock.json文件:运行npminstall--save命令,这将会更新package-lock.json文件,并确保所有依赖项都被正确记录。3、如果你想要使用package-lock......
  • Rust Package Manager:Cargo
    Cargo是Rust包管理器。Cargo下载您的Rust包的依赖项,编译您的包,制作可分发的包,并将它们上传到crates.io(Rust社区的包注册表)。类似于Python中的pip或Node.js中的npm。Cargo官方文档:TheCargoBook写的十分完美!cargo--list已安装命令:new在当前目......
  • 安装install.package("devtools")时报错 提示systemfonts,textshaping, ragg, gert依赖
    devtools可用conda,R的install.packages()以及wget等方式安装,这里我采用install.packages()安装,碰到systemfonts,textshaping,ragg,gert几个依赖包的安装错误。install.package("devtools")错误形式与解决,参考:https://www.cnblogs.com/shuaihe/p/17823059.html1.systemfonts解......
  • .NET项目轻松配置:掌握Packages.props和Build.props的利用
     概述:`Directory.Packages.props`和`Directory.Build.props`是.NET项目中的配置文件,分别用于统一管理NuGet包引用和自定义MSBuild构建过程。它们提高了解决方案的可维护性,通过集中配置,简化了项目文件,使团队协作更一致,同时避免了在每个项目中重复相同的配置,提高了开发效率。在......
  • 找不到包 Microsoft.NETCore.App.Crossgen2.win-x64。源 Microsoft Visual Studio Off
    问题找不到包System.IO.Packaging,源MicrosoftVisualStudioOffilinePackages中不存在具有此ID的包 解决打开工具-Nuget相关可以尝试再命令行里用 nugetrestore但是这种情况应该是没有设置源。在选项里面,新建一个程序包源,填写以下源地址(或者其他nuget源)就能修复。......
  • Jpackage-制作无需预装Java环境的Jar可执行程序
    JAR包要在预装JRE环境的系统上执行。如果没有预先安装JRE环境,又想直接运行Java程序,该怎么办呢?这篇文章我们会先学习如何将Java程序打包成一个可执行的JavaJAR文件。然后演示如何使用这个JAR文件生成Windows、Linux、MacOS上的可执行程序。我们将使用Java自带......
  • 【go】go错误,panic:assignment to entry in nil map 问题记录
    一个go的map相关的panic错误背景:在获取多个数据时,从数据库取到多条数据,需要把多条数据返回给前端,定义一个res返回值,为map[string]any类型,在赋值后运行发生panic:assignmenttoentryinnilmap原因:在声明map类型的变量后,直接进行赋值操作,此时未初始化该变量,所以它的值是nil,......
  • [Rust] Using .map_err instead of wrap which cause panic
    //Usingcatch-allerrortypeslike`Box<dynerror::Error>`isn'trecommended//forlibrarycode,wherecallersmightwanttomakedecisionsbasedonthe//errorcontent,insteadofprintingitoutorpropagatingitfurther.Here,we//defin......
  • npm 包 package.json 配置文件
    package.json文件每个前端项目中都有package.json文件,它是用于声明依赖的npm包配置文件。1.生成package.json文件yarninit-y{"name":"package.json文件","version":"1.0.0","main":"index.js","license":......