Required Oracle Patches

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    COMPONENT:

    AR System


    APPLIES TO:

    ARServer ITSM Suite 9.x, 18.xx, 19,xx, 20.xx



    QUESTION:

    Are there any Oracle patches that are required to properly run AR System?


    ANSWER:

    Yes. At the time this article was written there are 3 important fixes to Oracle Database that we recommend that you apply.

    1. Patch 24926999  12.1.0.2 VIEW PUSHED PREDICATES LEADING TO BAD ESTIMATES, BAD EXECUTION PLAN 

      
      Description: Bad execution plan with join predicate pushed down in materialized WITH query block.  
    Bugs Resolved by This Patch 
      
      24926999    12.1.0.2 VIEW PUSHED PREDICATES LEADING TO BAD ESTIMATES, BAD EXECUTION PLAN 
      
      Versions confirmed as being affected: 
      
      12.1.0.2 (Server Patch Set) 
      
      Symptom Noticed in ARSystem:  High Database CPU 
         
       
       2.  Patch 16777441: WRH$_SQL_BIND_METADATA IS NOT PURGED BY AUTO PURGE / DEEP PURGE  
       
       https://support.oracle.com/epmos/faces/DocumentDisplay?id=16777441.8&displayIndex=1   
    Description:     AWR deep purge does not remove rows from WRH$_SQL_BIND_METADATA    
        Bugs Resolved by This Patch   
        
        16777441    WRH$_SQL_BIND_METADATA IS NOT PURGED BY AUTO PURGE / DEEP PURGE.   
    Versions confirmed as being affected:    
        12.1.0.2 (Server Patch Set)    
    11.2.0.4    
    11.2.0.3   
    Symptom Noticed in ARSystem: Slow Email Engine Performance   
    The fix is included in the following:        
    3.  Patch 27416997 - CASE INSENSITIVE QUERIES FAILING DUE TO NULL IS NOT NULL PREDICATE      
      
       
       Description:  
       
       Wrong result in presence of case insensitive comparison,   
     check constraints   
        
    Simplified  case :   
    CREATE TABLE TB_1   
      (   
        ID_DATA  NUMBER NOT NULL,   
        IN_DATA_VALID CHAR(1 CHAR) NOT NULL ,   
        CONSTRAINT uno CHECK (IN_DATA_VALID ='N') ENABLE   
      );   
        
    INSERT INTO TB_1 VALUES (1, 'N');   
        
    alter session set NLS_SORT=BINARY_CI;   
    alter session set NLS_COMP=LINGUISTIC;   
        
    SELECT /*+ no_merge(v) */ t.IN_DATA_VALID   
    FROM tb_1 t,   
         (select 1 ID_DATA from dual) v   
    WHERE t.ID_DATA=V.ID_DATA AND t.IN_DATA_VALID = 'n';   
        
    no rows returned due to FALSE predicate:  
       
       Bugs Resolved by This Patch  
       
       Bug 27416997  case insensitive queries failing due to null is not null predicate  
       
       Versions confirmed as being affected:  
       
       12.1.0.2 (Server Patch Set)  
       
       Symptom Noticed in ARSystem: Wrong results returned from a Case-Insensitive search   
    Work around: ALTER SESSION SET "_optimizer_generate_transitive_pred" = FALSE;   
    The fix is included in the following:        
      

     


    Article Number:

    000175886


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles