9 Replies Latest reply on Jun 12, 2019 3:28 AM by Nick Caulfield

    Discovery - Automatic DB2 Query?

    James Wyatt
      Share:|

      Hi All,

       

      One of our DB engineers has advised that Discovery is causing issue's! Yep... we've all heard that!

       

      On investigation, he advises that whenever Discovery contacts one of his servers (Unix I think), it discovers the host and then tries to get into the DB. As Discovery is not allowed into the DB, this results in a stack of errors in his logs.

       

      Now, from the documents I have read, no DB should be getting scanned, unless credentials are available for a DB connection. We have no such credentials set up and were therefore expecting Discovery to limit itself to OS related Discovery only.

       

      Can anyone advise if this is standard? I guess what I'm asking: Is there a switch to prevent unwanted DB2 connections from Discovery and why is Discovery attempting to connect to something it hasn't been programmed to do?

       

      From the DB2 Engineer:

       

      Issue: Attempt to connect to DB2 database by BMC ADDM tool resulting in Errors in the db2diag.log. (We are trying to monitor for significant errors in the db2diag.log and these are triggering false alerts)

       

      Issue is caused because the user account has no permission to connect to the database/s. (We don't routinely grant DB connect or other permissions to users who do not require access)

       

       

       

      Example db2diag.log errors

      2017-06-02-14.04.21.817641+060 I89337A977           LEVEL: Error
      .....
      MESSAGE : ZRC=0x801A006D=-2145779603=SQLZ_CA_BUILT
                "SQLCA has already been built"
      DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
      sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1060   sqlerrml: 15
      sqlerrmc: WADDMGA1SERVICE
      sqlerrp : SQLRR003
      sqlerrd : (1) 0x801A006D      (2) 0x00000000      (3) 0x00000000
                 (4) 0x00000000      (5) 0xFFFFFE2A      (6) 0x00000000
      sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
                 (7)      (8)      (9)      (10)        (11)
      sqlstate:

      2017-06-02-14.04.21.818069+060 I90315A885           LEVEL: Error

      .....
      EDUID   : 12118                EDUNAME: db2agent (WBPSL1D) 0
      FUNCTION: DB2 UDB, relation data serv, sqlrr_appl_init, probe:480
      DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
      sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1060   sqlerrml: 15
      sqlerrmc: WADDMGA1SERVICE
      sqlerrp : SQLRR003
      sqlerrd : (1) 0x801A006D      (2) 0x00000000      (3) 0x00000000
                 (4) 0x00000000      (5) 0xFFFFFE2A      (6) 0x00000000
      sqlwarn : (1)      (2)      (3)      (4)        (5)       (6)
                 (7)      (8)      (9)      (10)        (11)
      sqlstate:

      2017-06-02-14.04.21.818466+060 I91201A557           LEVEL: Severe

       


      EDUID   : 12118                EDUNAME: db2agent (WBPSL1D) 0

       

       

      FUNCTION: DB2 UDB, base sys utilities, sqeApplication::AppStartUsing, probe:140
      RETCODE : ZRC=0x8012006D=-2146303891=SQLR_CA_BUILT