I am experiencing problems on a database running at one of out customers.
The database transaction log keeps on growing although it is supposed to
maintain itself with tresholds etc. It got to a point that the database
locked up because the tran log was full. This is the point where I was
Using DBCC i discovered several allocation errors, most of which the fix
option sorted out. By the way this problem existed several backups back but
no proper dba function exists at the site to pick up these problems early
When i try to do a manual dump tran i receive the following error
Attached are the output from several dbcc. As you can see the problem is
with page nr 709545. This page is not currently allocated to any object,
neither is the extent on which it is located or the allocation unit for that
However the page header for this page still indicate that it is allocated to
objid 8 (syslogs). I believe this to be the reason that checkallocation and
checktable dbcc's do not report a error before executing a dump tran, since
they propbably check linkage from the objid level and objid 8 does not have
any extents allocated to it at this stage. It seems however that dump tran
scans the page headers and picks up this page, attempts to dump it but can
not get to it due to the fact that no linkage exists to it from the object.
I urgently require a method by which to change the objid on page 709545 to
zero (0) so that the transaction log can be dumped as normal.
Any and all suggestion will be greatly appreciated