Results 1 to 4 of 4
  1. #1
    Join Date
    Jun 2017
    Posts
    1

    Unhappy Unanswered: Slowness in fetching data from DB2

    Hi,

    Currently we are facing one issue in which there is slowness in fetching the data from DB2.We have configured reports in cognos to fetch the data from DB2 which is taking approx 12-14 hours to fetch one day data from table which contains 45 days of data.

    During the preliminary investigation I found that the table is containing approx 9Cr rows. Could it be the reason for the slowness ??

    If yes,than what are the best possible alternatives can be implemented to overcome this slowness.(Pls keep in mind that this is customer data so cant delete it).

    Is it feasible to rename this table or to move whole data from one table to another table???

    Pls advice.

    Thanks,
    Saurabh

  2. #2
    Join Date
    Apr 2012
    Posts
    1,143
    Provided Answers: 27
    Get the access plan for the query (or queries) analysed and optimised. When asking for help, use international numbering and post the DB2-server version+fixpack and operating-system details,

  3. #3
    Join Date
    Jun 2017
    Posts
    9
    Provided Answers: 1
    Quote Originally Posted by coolsaurabh View Post
    Hi,

    Currently we are facing one issue in which there is slowness in fetching the data from DB2.We have configured reports in cognos to fetch the data from DB2 which is taking approx 12-14 hours to fetch one day data from table which contains 45 days of data.

    During the preliminary investigation I found that the table is containing approx 9Cr rows. Could it be the reason for the slowness ??

    If yes,than what are the best possible alternatives can be implemented to overcome this slowness.(Pls keep in mind that this is customer data so cant delete it).

    Is it feasible to rename this table or to move whole data from one table to another table???

    Pls advice.

    Thanks,
    Saurabh
    Do you know how to get an explain and read it? Do you know how to use the index advisor? Chances are you are getting bad plans and need some indexes.

    Steve

  4. #4
    Join Date
    Oct 2007
    Posts
    161
    Provided Answers: 9
    Also, the SQL written by COGNOS, is not always the most efficient. After reviewing the access path, you may want to review the SQL for possible changes as well.

Tags for this Thread

Posting Permissions

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