IV60484: TEMA SERVER CANNOT CONNECT TO DB2 DATABASE "THERE IS NOT ENOUGH STORAGE AVAILABLE TO PROCESS THE STATEMENT"

APAR status

• Closed as program error.

Error description

• After installation of TEMA server we cannot connect to IEM DB2
  database. The following error is being thrown:
  com.ibm.db2.jcc.am.SqlException: There is not enough storage
  available
  to process the statement.. SQLCODE=-930, SQLSTATE=57011,
  DRIVER=4.14.111
  
  Log is attached to this PMR:
  ...
  2014-05-09 12:23:20 / [INFO] NativeException:
  com.ibm.db2.jcc.am.SqlException: There is not enough storage
  available
  to process the statement.. SQLCODE=-930, SQLSTATE=57011,
  DRIVER=4.14.111:         select Sitename as sitename,
                 ID       as id,
                 case when Sitename = 'ActionSite' then
  dbo.fn_ExtractField('CustomSiteName', 0, Fields) else null end
  as
  custom_sitename,
                 Name     as name,
                 0        as is_retrieved_property,
                 0        as is_reserved,
                 Fields   as fields,
                 case when ParentID = 1 then 1 else 0 end as
  deleted
          from BES_OBJECT_DEFS
          where Sequence  > 0
            and Sequence <= 1326833
            and dbo.fn_ExtractField('Fixlet Type', 0, Fields) =
  'Analysis'
          union all
          select 'ActionSite' as sitename,
                 ID           as id,
                 null         as custom_sitename,
                 Name         as name,
                 1            as is_retrieved_property,
                 case when dbo.fn_ExtractField('IsReserved', 0,
  Fields) =
  'Yes' then 1 else 0 end as is_reserved,
                 Fields       as fields,
                 case when ParentID = 1 then 1 else 0 end as
  deleted
          from BES_OBJECT_DEFS
          where Sequence     > 0
            and Sequence    <= 1326833
            and ContentType  = 5
            and dbo.fn_ExtractField('SMIME', 0, Fields) is not
  null
  

Local fix

• Allocate an unnecessarily large amount of memory in DB2, so that
   even
  when using the problematic function, it still has enough runway
  to complete.
  

Problem summary

• The relevance for the SQL Server AGent appears to be failing
  when the
  SQLSERVERAGENT does not exist as a service. The customer is
  getting the
  following message on his health check panel:
  
  Relevance evaluation failed. Singular expression refers to
  non-existent object.
  
  The customer has the database installed locally but does not
  have the
  SQLSERVERAGENT installed.
  
  I was able to reproduce this on my test system as well. When I
  run the
  following relevance on my test system in the fixlet debugger, I
  get "Remote
  Database" returned as an answer..it is incorrect...as the
  database is local and
  is SQL Express (the database we ship imbedded).
  
  I will attach the screen shot of the issue that the customer
  sent. I will also
  open up an APAR for this.
  

Problem conclusion

• There were two things going on:
  1. The status field for the "SQL Server Agent Status" is
  dependent on an old
  property that does not exist anymore. Like Brian mentioned in
  comment #20, it
  indeed was a result of a name change. This has been fixed.
  
  2. Errors for the "FillDB Log File Size" and "Actionsite Size"
  happen when
  there are multiple properties of the same name. An ambiguous
  call can lead to
  the Console error-ing out in the relevance used in the
  dashboard. Mike helped
  me modify these relevance statements to remove the ambiguity.
  
  Both changes have been propagated to BES Support DEV version 76.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  TV EP MG SEC CF

• Fixed component ID

  5725C43SM

Applicable component levels

• R820 PSY

     UP