 <p>Most likely, the sequence of save and restore was incorrect. The table had attributes that shouldn't have been saved and should have been removed before saving. The restore has resulted in a database catalog on the new system with inconsistent elements.</p> <p>If not, then the next likelihood (and just about the only other possibility) is that the database catalog had inconsistencies already before the restore was done. Those could have been introduced by improper shutdowns or other actions.</p> <p>First step should be:</p> <pre><code>RCLDBXREF OPTION(*CHECK) </code></pre> <p>If problems are reported, run:</p> <pre><code>RCLDBXREF OPTION(*FIX) </code></pre> <p>If the system is too old for the RCLDBXREF command, use:</p> <pre><code>RCLSTG SELECT(*DBXREF) </code></pre> <p>No "*CHECK" option is available for the older version.</p> <p>Depending on size and complexity of your database, number of resynchronizations needed and general performance characteristics of your server, either of those can run from 10 minutes to a few hours. Most unexplained database catalog problems (other than those needing PTFs) can be cleared by either of those.</p> <p>The RCLDBXREF command is usually preferred, but some problems will require the RCLSTG alternative. Significant restrictions exist for RCLSTG, so be sure to read the command [Help].</p>