Results 1 to 5 of 5

Thread: sql.log

  1. #1
    Join Date
    Jan 2003
    Location
    Zutphen,Netherlands
    Posts
    256

    Unanswered: sql.log

    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?
    Ties Blom
    Senior Application Developer BI
    Getronics Healthcare
    DB2,ORACLE,Powercenter,BusObj,Access,
    SQL, SQL server

  2. #2
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Check if your cli trace is switched on ..

    Config is in

    sqllib/cfg/db2cli.ini

    HTH

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  3. #3
    Join Date
    Jan 2003
    Location
    Zutphen,Netherlands
    Posts
    256
    This is the contents of the ini file:

    Code:
    
    ; Comment lines start with a semi-colon.
    
    [tstcli1x]
    uid=userid
    pwd=password
    autocommit=0
    TableType="'TABLE','VIEW','SYSTEM TABLE'"
    
    [tstcli2x]
    ; Assuming dbalias2 is a database in DB2 for MVS.
    SchemaList="'OWNER1','OWNER2',CURRENT SQLID"
    
    [MyVeryLongDBALIASName]
    dbalias=dbalias3
    SysSchema=MYSCHEMA
    
    [DWCTRLDB]
    DBALIAS=DWCTRLDB
    
    [PMREPO51]
    DESCRIPTION=PMREPO51
    DBALIAS=PMREPO51
    
    [PMREPOLD]
    DBALIAS=PMREPOLD
    
    [FINANCE]
    DESCRIPTION=FINANCE
    DBALIAS=FINANCE
    
    [PMTEST]
    DESCRIPTION=PMTEST
    DBALIAS=PMTEST
    
    [BIKE]
    DESCRIPTION=BIKE
    DBALIAS=BIKE
    
    [FISHING]
    DESCRIPTION=FISHING
    DBALIAS=FISHING
    
    [LOCATOR]
    DESCRIPTION=Archive database for Locator
    DBALIAS=LOCATOR
    
    [AS400]
    DBALIAS=AS400
    
    [LOCARCH]
    DBALIAS=LOCARCH
    
    [SLIM4]
    DESCRIPTION=Forecasting Bike Fishing
    DBALIAS=SLIM4
    I guess not?
    Ties Blom
    Senior Application Developer BI
    Getronics Healthcare
    DB2,ORACLE,Powercenter,BusObj,Access,
    SQL, SQL server

  4. #4
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    check in Control Panel ->Administrative -> ODBC Manager -> Tracing(tab) -> click on Stop Tracing
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  5. #5
    Join Date
    Jan 2003
    Location
    Zutphen,Netherlands
    Posts
    256
    Quote Originally Posted by sathyaram_s
    check in Control Panel ->Administrative -> ODBC Manager -> Tracing(tab) -> click on Stop Tracing
    Spot-on as usual
    I am dead sure we did not start the tracing though.

    Very kreepy.....
    Ties Blom
    Senior Application Developer BI
    Getronics Healthcare
    DB2,ORACLE,Powercenter,BusObj,Access,
    SQL, SQL server

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •