Results 1 to 8 of 8

Thread: DB2 Performance

  1. #1
    Join Date
    Jun 2006
    Posts
    4

    Unanswered: DB2 Performance

    Hi All,

    I'm having a doubt abt the db2syscs.exe process.We can find the performance of the process by executing the perfmon command. When any insert/update/delete/select manipulations are done, the handle count for the process increases. Why does the handle count increase for this process?
    Does it relate to the Connections opened or Statements opened or Resultsets using in the application?
    Does it impact with the overall performance of the system? Can anyone please tell me.

    Thanks in advance,
    Mary

  2. #2
    Join Date
    Jan 2003
    Posts
    1,605
    Hi,
    don't understand. What is the performance problem?
    Grofaty

  3. #3
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    I don't understand the problem either ..

    But, for info, db2sysc.exe is the process that does work on behalf of the database - You will be able to find a number of them and the number you can see at an instant is dependet on a number of config parms ..

    HTH

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

  4. #4
    Join Date
    Jun 2006
    Posts
    4
    Thank you.

    Can you please tell me abt another problem which i'm facing in our application. While inserting 10000 records at a time. I'm getting an error
    after inserting 8000 records, DB2 SQL error: SQLCODE: -964, SQLSTATE: 57011, SQLERRMC: null (MON_HEAP_SZ ).

    Thanks in advance,
    Mary

  5. #5
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    SQL0964C The transaction log for the database is full.
    Explanation:
    All space in the transaction log is being used.
    If a circular log with secondary log files is being used, an
    attempt has been made to allocate and use them. When the file
    system has no more space, secondary logs cannot be used.
    If an archive log is used, then the file system has not provided
    space to contain a new log file.
    The statement cannot be processed.
    User Response:
    Execute a COMMIT or ROLLBACK on receipt of this message (SQLCODE)
    or retry the operation.
    If the database is being updated by concurrent applications,
    retry the operation. Log space may be freed up when another
    application finishes a transaction.
    Issue more frequent commit operations. If your transactions are
    not committed, log space may be freed up when the transactions
    are committed. When designing an application, consider when to
    commit the update transactions to prevent a log full condition.
    If deadlocks are occurring, check for them more frequently.
    This can be done by decreasing the database configuration
    parameter DLCHKTIME. This will cause deadlocks to be detected
    and resolved sooner (by ROLLBACK) which will then free log
    space.
    If the condition occurs often, increase the database
    configuration parameter to allow a larger log file. A larger log
    file requires more space but reduces the need for applications to
    retry the operation.
    If installing the sample database, drop it and install the
    sample database again.
    sqlcode : -964
    sqlstate : 57011
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  6. #6
    Join Date
    Jun 2006
    Posts
    4
    Thanks a lot it worked. I'll get back if there is anyother query.

  7. #7
    Join Date
    Jun 2006
    Posts
    4
    Hi, I got the same MON_HEAP_SZ problem while deleting 10000 records from the Control Center. How to solve the problem?

  8. #8
    Join Date
    Mar 2005
    Posts
    108
    Try to delete only 1000 records ...

Posting Permissions

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