Error 8998

Question

Error 8998

bshaw

Right there with Babe

Points: 750
More actions
January 30, 2007 at 1:14 pm

#61097

Maintenance, Full and Transaction log backups have failed due to Error 8998. Appears that an Alter Database, increase data file size is in order.
Database is just shy of 16g. Have not executed this command before. I was going to schedule this job tonight, but don't want it to bump heads with any other scheduled job.
About how long should this take.

Thanks

Viewing 5 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic. Login to reply

JDixon-385826 SSCrazy Points: 2723 More actions · Answer 1

If setup to do so the data file will grow with out a scheduled alter db cmd.

IF you do need to set the auto file growth (you should) then Open Enterpirse Manager, Open the server, right click the database, choose properties, Click on data file tab, Check Automatically grow file, Set file growth in MB or %, Click OK.

BUT

The error code sounds more like a database page file problem. Try running DBCC CHECKDB against the database and see if it returns any errors.

I am guessing you most likely will have to recreate a table or index but may have to run the DBCC check DB with REPAIR_ALLOW_DATA_LOSS, REPAIR_FAST, or REPAIR_REBUILD.

bshaw Right there with Babe Points: 750 More actions · Answer 2

Maintenance log states the following....

[1] Database Image: Check Data and Index Linkage...

[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 8998: [Microsoft][ODBC SQL Server Driver][SQL Server]Page corruptions on the GAM, SGAM, or PFS pages do not allow CHECKALLOC to verify database ID 8 pages from (1:2044928) to (1:2044928). See other errors for cause.

[Microsoft][ODBC SQL Server Driver][SQL Server]Table Corrupt: GAM page (1:2044928) (object ID 99, index ID 0) is out of the range of this database.

[Microsoft][ODBC SQL Server Driver][SQL Server]Table Corrupt: SGAM page (1:2044929) (object ID 99, index ID 0) is out of the range of this database.

[Microsoft][ODBC SQL Server Driver][SQL Server] The repair level on the DBCC statement caused this repair to be bypassed.

[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 1 allocation errors and 0 consistency errors not associated with any single object.

[Microsoft][ODBC SQL Server Driver][SQL Server] The repair level on the DBCC statement caused this repair to be bypassed.

[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 2 allocation errors and 0 consistency errors in table 'ALLOCATION' (object ID 99).

[Microsoft][ODBC SQL Server Driver][SQL Server]CHECKDB found 3 allocation errors and 0 consistency errors in database 'Image'.

[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC execution completed. If DBCC printed error messages, contact your system administrator.

I figured this was my situation

http://search.support.microsoft.com/kb/264041

JDixon-385826 SSCrazy Points: 2723 More actions · Answer 3

It could be but to be safe you could run

SELECT * FROM sysobjects where ID = 99

Which should give you the object that is corrupted per your maintenance logs.

Then you could try to run the below (if it is a table). But no user can be accessing the datbase at the time.

USE master

EXEC sp_dboption 'databaseName', 'single user', 'TRUE'

GO

USE databaseName

DBCC CHECKTABLE ('ObjectNameforID99', REPAIR_REBUILD)

GO

USE master

EXEC sp_dboption 'databaseName', 'single user', 'FALSE'

GO

OR RUN

USE master

GO

DBCC CHECKDB ('databasename', REPAIR_REBUILD)

GO

Either way you will need to have it in Single user mode.

If the above does not work you can run the same statement but with REPAIR_ALLOW_DATA_LOSS replacing the REPAIR_REBUILD.

Or you could export the data from the table to a new table the same as the old with a name like TableName2 then once in the new table drop the old table and rename the new table to the old table name. To do this all relationships will have to be disabled.

bshaw Right there with Babe Points: 750 More actions · Answer 4

Thanks. I did look in sysobjects, but there is no 99. Don't know if it is a system table or what.

Think I'll try to alter the data file first. If that doesn't work, then I'll try to create a new table and migrate data.

Thanks for the tips.