Results 1 to 7 of 7
  1. #1
    Join Date
    Apr 2011
    Posts
    14

    Unanswered: db2jcc_application with Client PID 0

    Greetings All,

    i work with DB2 for SAP(ABAP+JAVA) Servers.
    after 231 logs of usage i turned the infinity logging. i failed to kill the oldest application Hanlde.
    Please suggest how to force the oldest Application Handle/agent which is inactive.

    Thanks.
    Ravi

  2. #2
    Join Date
    Apr 2006
    Location
    Belgium
    Posts
    2,514
    Provided Answers: 11
    please be more specific - db2level - platform - problem description - error - ?
    db2 force application or have a look at infocenter for other commands
    Best Regards, Guy Przytula
    Database Software Consultant
    Good DBAs are not formed in a week or a month. They are created little by little, day by day. Protracted and patient effort is needed to develop good DBAs.
    Spoon feeding : To treat (another) in a way that discourages independent thought or action, as by overindulgence.
    DB2 UDB LUW Certified V7-V8-V9-V9.7-V10.1-V10.5 DB Admin - Advanced DBA -Dprop..
    Information Server Datastage Certified
    http://www.infocura.be

  3. #3
    Join Date
    Apr 2011
    Posts
    14
    Quote Originally Posted by przytula_guy View Post
    please be more specific - db2level - platform - problem description - error - ?
    db2 force application or have a look at infocenter for other commands
    Hi,
    thanks for reply.

    LOG primary is 200
    LOG second is 56

    we see almost 231 logs occupied, and i check to force the oldest transaction , but it is not moving to rollback state and in VOW executing in the snapshot.
    now i enabled infinity logging to allow it to go, but since two days it is in the same state, we have no option to kill the db2 and provide all the needed logs for the crash recovery.

    how to terminate such inactive agents.

    ofcourse no frequent commits cause the logn uncommited data. but how to terminate this to rollback state OR prevent this in future.

    version is 9.7.0.7

    Thanks

  4. #4
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    Quote Originally Posted by db2_dpf View Post
    Hi,
    ...but how to terminate this to rollback state OR prevent this in future.
    Thanks
    Use the SAP cockpit (or other tool, e.g. the command line, or db2top etc) to find out what is the owner of the connection you want to force off.
    If the connection is owned by a part of SAP , then refer to SAP for advice on how to handle that situation (most likely a known one).

    If the connection is NOT part of SAP (for example it is some script or some application the is only indirectly related to SAP) then post details, check if you are attempting the force whilst running as the instance-owner and doing it from the operating-system shell, check (for example with db2top) that code is running on that connection, what transaction-log space is being used by the connection, when was the last commit on that connection etc). Check db2diag.log for any indications after you attempt the force - as there may be other issues that contribute to this symptom.

  5. #5
    Join Date
    Apr 2011
    Posts
    14
    we are unable to see the process id in the dbacockpit, also we tried to cancel the job but failed.
    also we tried to force the app handle which also failed

    i under that lot of un-commited is there and it leads to increment of active log space.

    finally we need to proceed to db2_kill and crash recovery.

    is there any other way to cancel/kill from thread level with out having impact to system

  6. #6
    Join Date
    Apr 2012
    Posts
    1,035
    Provided Answers: 18
    You don't give hard-evidence or hard-facts ...and you don't answer specific questions, this limits the advice you can receive here...

    You should open a ticket with SAP directly before taking action (there's no info in your post as to whether or not you already did this).

    Most likely they will give specific PD-advice that will limit the damage or recovery actions that might happen otherwise.

    Without relevant facts, most likely this symptom will repeat after a bounce of the db2-instance.

    Relevant missing information:
    output of command: db2 list applications show detail
    output of command: db2 "force applications (...)"
    during the force, status of the application-handle concerned (maybe it's a huge UOW with a lengthy rollback...).
    what lines added to db2diag.log during force?
    output of commands like: db2pd -db... -application $apphandle (or -db ... -activestatements - apphdl=... )
    etc - basic problem determination that an experienced DBA would do

  7. #7
    Join Date
    Nov 2009
    Posts
    21
    Provided Answers: 1
    As added troubleshooting measure please check for indoubt transactions also..

    db2 connect to <dbname>

    db2 list indoubt transactions with prompting

    if there is any .. indoubt ones.. either commit or rollfoward.. and then issue same command with quit option..



    Surgeon

Posting Permissions

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