Results 1 to 2 of 2
  1. #1
    Join Date
    Jul 2005

    Unanswered: possible monitor event?

    SAP BW
    DB2 9.5.7
    AIX 6.1

    Below is part of an application snapshot:

    Application handle = 266
    Application status = UOW Executing
    Status change time = Not Collected
    Application code page = 1208
    Application country/region code = 1
    DUOW correlation token =
    Application name = disp+work
    Application ID =
    Sequence number = 03231
    TP Monitor client user ID = BWREMOTE
    TP Monitor client workstation name = abcdefg
    TP Monitor client application name = ptype DIA
    TP Monitor client accounting string = CL_RSDD_STATOLAP==============CP

    On occasion, a scheduled task/job holds a transaction log open, preventing it from being archived. As activity continues on the system, seconday logs get used and, if unnoticed, the logs become full. Forcing the offending application handle alleviates the problem and all becomes swell again.

    I have not yet found anything helpful in the application log, so is there some monitor event via DB2 that would shed some more insight to what is happening?

    Thanks in advance...

  2. #2
    Join Date
    Jan 2003
    Provided Answers: 5
    I would think to look at the scheduled job and figure out why it holds the transaction so long and fix it.


Posting Permissions

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