<div>Hello,</div>
<div> </div>
<div>Since upgrading to RT 3.6.3, I've noticed that all of our tickets are incrementing their ticket numbers/IDs by n+10 - </div>
<div> </div>
<div>From show table status:</div>
<div> </div>
<div>| Tickets  | InnoDB |10 | Compact  |  14823 | 248 | 3686400 |   0 |  1146880 | 0 | 24632 | 2007-04-30 09:35:08 | NULL | NULL | latin1_swedish_ci | NULL |               </div>
<div> </div>
<div> </div>
<div>And the table itself (sorry for the mangling....):</div>
<div> </div>
<div>mysql> describe Tickets;<br>+-----------------+--------------+------+-----+--------------+----------------+<br>| Field           | Type         | Null | Key | Default      | Extra          |<br>+-----------------+--------------+------+-----+--------------+----------------+
<br>| id              | int(11)      | NO   | PRI | NULL         | auto_increment | <br>| EffectiveId     | int(11)      | NO   | MUL | 0            |                | <br>| Queue           | int(11)      | NO   | MUL | 0            |                | 
<br>| Type            | varchar(16)  | YES  |     | NULL         |                | <br>| IssueStatement  | int(11)      | NO   |     | 0            |                | <br>| Resolution      | int(11)      | NO   |     | 0            |                | 
<br>| Owner           | int(11)      | NO   | MUL | 0            |                | <br>| Subject         | varchar(200) | YES  |     | [no subject] |                | <br>| InitialPriority | int(11)      | NO   |     | 0            |                | 
<br>| FinalPriority   | int(11)      | NO   |     | 0            |                | <br>| Priority        | int(11)      | NO   |     | 0            |                | <br>| TimeEstimated   | int(11)      | NO   |     | 0            |                | 
<br>| TimeWorked      | int(11)      | NO   |     | 0            |                | <br>| Status          | varchar(10)  | YES  |     | NULL         |                | <br>| TimeLeft        | int(11)      | NO   |     | 0            |                | 
<br>| Told            | datetime     | YES  |     | NULL         |                | <br>| Starts          | datetime     | YES  |     | NULL         |                | <br>| Started         | datetime     | YES  |     | NULL         |                | 
<br>| Due             | datetime     | YES  |     | NULL         |                | <br>| Resolved        | datetime     | YES  |     | NULL         |                | <br>| LastUpdatedBy   | int(11)      | NO   |     | 0            |                | 
<br>| LastUpdated     | datetime     | YES  |     | NULL         |                | <br>| Creator         | int(11)      | NO   |     | 0            |                | <br>| Created         | datetime     | YES  |     | NULL         |                | 
<br>| Disabled        | smallint(6)  | NO   |     | 0            |                | <br>+-----------------+--------------+------+-----+--------------+----------------+</div>
<div> </div>
<div>Have I missed something simple?  The version of RT I upgraded from also used InnoDB tables, so it doesn't seem to me to be an issue with auto_increment strangeness with InnoDB tables (which I've read a little about).  Any clues?
</div>
<div> </div>
<div>Thanks!</div>
<div>Mike</div>
<div> </div>
<div> <br>--<br>One way or another, everyone stops bleeding. </div>