We upgraded our ETL tool some 8 days ago and from that moment on the server is flooded with a sql.log file that grows like hell.
Code:
pmdtm.exe -s "T 77-234 ENTER SQLAllocEnv
HENV * 01D5AE84
pmdtm.exe -s "T 77-234 EXIT SQLAllocEnv with return code 0 (SQL_SUCCESS)
HENV * 0x01D5AE84 ( 0x041416c0)
pmdtm.exe -s "T 77-234 ENTER SQLAllocConnect
HENV 041416C0
HDBC * 01D59070
pmdtm.exe -s "T 77-234 EXIT SQLAllocConnect with return code 0 (SQL_SUCCESS)
HENV 041416C0
HDBC * 0x01D59070 ( 0x04141768)
pmdtm.exe -s "T 77-234 ENTER SQLSetConnectOption
HDBC 04141768
SQLINTEGER 1800 <unknown>
SQLPOINTER [Unknown attribute 1800]
pmdtm.exe -s "T 77-234 EXIT SQLSetConnectOption with return code 0 (SQL_SUCCESS)
HDBC 04141768
SQLINTEGER 1800 <unknown>
SQLPOINTER [Unknown attribute 1800]
According to the ETL vendor this is a DB2 file, but I have never seen it before. Anyone an idea what is causing this massive logging?