Skip to Content
author's profile photo Former Member
0
Former Member

SQL2310N the utility could not generate statistics: error "-911"

Posted on Jan 09, 2007 at 12:12 PM 1.6k Views

Hello,

we have a 46c system with DB V.8.2.2. Everytime we planned over db13 the runstat_all we get an error message.

Errormessage: Error -2310 in dmdb6upd.c(687):

SQL2310N the utility could not generate statistics: error "-911"

Regards,

Alexander Türk

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Best Answer
    author's profile photo Former Member
    Former Member
    Posted on Jan 09, 2007 at 12:21 PM
    2

    Here some more information:

    07.01.2007 13:00:31 Ausführung des logischen Kommandos REORGCHK_ALL auf Rechner b0d0m102

    07.01.2007 13:00:31 Parameter: -t all -n PH0 -z 3600 -m b -l 1800

    07.01.2007 20:01:09 pct_long_lob has been set to 10 percent

    07.01.2007 20:01:09 Checking for old entries in db6treorg/db6ireorg ...

    07.01.2007 20:01:09 Reading table names for runstats ...

    07.01.2007 20:01:09 Tables to process: 26350 ...

    07.01.2007 20:01:09 ERRORMESSAGE: Error -2310 in dmdb6upd.c(687):

    07.01.2007 20:01:09 SQL2310N The utility could not generate statistics. Error "-911"

    07.01.2007 20:01:09 was returned.

    07.01.2007 20:01:09

    07.01.2007 20:01:09 table: SAPR3.DB6PMHT

    07.01.2007 20:01:09 ERRORMESSAGE: Error -2310 in dmdb6upd.c(687):

    07.01.2007 20:01:09 SQL2310N The utility could not generate statistics. Error "-911"

    07.01.2007 20:01:09 was returned.

    07.01.2007 20:01:09

    07.01.2007 20:01:09 table: SAPR3.DB6PMHT_HD

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member
      Jan 09, 2007 at 12:39 PM

      Hi Alexander,

      the problem is an SQL0911, i.e. a lock situation. The table affected is DB6PMHT_HD. This is a table used to write history of tablespace growth. And this table is exclusively locked, when the history is collected. As I can see at the timestamp, the runstats_all was scheduled on sunday at 20:00. This is exactly the time, when the history is collected by the SAP system. That's the reason for the lock

      Best regards

      Ralf

  • author's profile photo Frank-Martin Haas
    Frank-Martin Haas
    Posted on Jan 09, 2007 at 12:37 PM
    0

    Hi Alexander,

    it would help to see what causes the lock wait or deadlock situation.

    Could you please run

    db6util -sl

    in the while the runstats job is running? db6util can be run periodically, e.g.:

    db6util -sl 10 -o /dev/null -w locks.out

    Regards

    Frank

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.