2468117 - Frequent "SQLCA has already been built" and sqlcode: -1060 entries in DB2diag.log

• The DB2diag.log shows many entries for  "SQLCA has already been built" and this entry can be ignored.  
• The real issue pertains to the SQLCODE - 1060 (SQL1060N -User authorization-ID does not have the CONNECT privilege)
• You may see examples like those below from the db2diag.log  The important information from the example is AUTHID : ROOT and  sqlcode: -1060
  
  PID     : XXXXX                    TID : PROC : db2sysc 0
  INSTANCE: db2XXX              NODE : 000            DB   : XXX
  APPHDL  : 0-XXXX                APPID: *LOCAL.db2XXXXXXX
  AUTHID  : ROOT                   HOSTNAME: XXXX
  EDUID   : XXX                      EDUNAME: db2agent XXX
  FUNCTION: DB2 UDB, base sys utilities, sqeApplication::AppStartUsing,
  RETCODE : ZRC=0x8012006D=-2146303891=SQLR_CA_BUILT
            "SQLCA has already been built"
  
  
  PID     : XXXXX                    TID : PROC : db2sysc 0
  INSTANCE: db2XXX               NODE : 000            DB   : XXX
  APPHDL  : XXXXXX             APPID: *LOCAL.db2XXXXXX
  AUTHID  : ROOT                 HOSTNAME: XXX
  EDUID   : XXX                EDUNAME: db2agent XXXX
  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: 8
  sqlerrmc: ROOT

• DB2 (LUW) databases for Linux, Unix and Windows
• Any database version

 SAP HOST AGENT, Alert, sapdbctrl, SQL1060N, authorization, , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , BC-CCM-HAG , Host Agent , Problem