ok - in that case if it only happens under load with concurrent executions of the SP, then I'd say it's definitely a bug. The index rebuild code is interacting with the new allocation code in tempdb (that my team wrote) that does temp table 'caching'. If you're really motivated, call into Product Support and tell them I think this is a bug. Get me an SR number and I'll help it get escalated past frontline support.

If you're not motivated, take out the DBREINDEX - I think it's completely superfluous.

Let me know which way you're going to go - I'll escalate directly to them dev team if you're not going to call support.

Thanks!