So it's not hung as such, it's just taking longer? What has changed? Do you have more data than you had before? Do you maintain your statistics and indexes with the same frequency as you did before (that may or may not make a difference to DBCC run duration)? Is there any other activity on the database or server or disks at the same time as the job runs? Do you have plenty of free space on the drives on which your database files reside in case of any growth in the files for the internal snapshot that the DBCC process creates?