title: Run DB2 Runstats without activity but still get SQLSTATE=01650
body: <p>After reading many of articles from the internet, I am still not sure what is the actual purpose of <code>DB2 Runstats</code>.</p>
  
  <p>As my understanding, <code>DB2 Runstats</code> will "register" the table index to the DB2 catalog, so that next time when the related query run, it will use the index to increase the performance. (Please correct me if I am wrong)</p>
  
  <p>Meaning, if for a long period of time the <code>DB2 Runstats</code> is not run, the index will be removed from the DB2 catalog?</p>
  
  <p>I am creating a new index for a table. Originally that table already contained another index.</p>
  
  <p>After creating the new index, I ran <code>DB2 Runstats</code> on the table for the old index, but I hit the following error:</p>
  
  <blockquote>
    <p><code>SQL2314W</code>  Some statistics are in an inconsistent state. The newly collected 
    "INDEX" statistics are inconsistent with the existing "TABLE" statistics. <code>SQLSTATE=01650</code></p>
  </blockquote>
  
  <p>At first I was thinking it's cause by the activity to create the new index, and the table was still in the "processing" stage. I ran the <code>DB2 Runstats</code> command again the next day but still got the same error.</p>