The Notification Server log shows the following error: "Attempt to fetch logical page in database 'DBName' belongs to object 'TableName1', not to object 'TableName2."
This happens when selecting one of the tabs in the Altiris console. Selecting the tab gives a blank pane and a error message in Internet Explorer.
The SQL error log also show the error above followed by "Error: 605, Severity: 21, Stat: 1."
Execute DBCC CHECKTABLE on the second table specified in the error message (DBCC CheckTable ('TableName2')). Next step is to perform a repair on the specified table. If the error involves a data page, it may be necessary to use the REPAIR_ALLOW_DATA_LOSS clause (see below). In the likely event that you cannot allow the loss of data, you will need to restore from a known clean backup.
To determine the full extent of the corruption, execute DBCC CHECKDB as soon as possible. If the 605 error is not transient, the problem is severe and you must run DBCC CHECKDB with one of the repair clauses. If the error involves an index page, use the REPAIR_REBUILD clause. If the error involves a data page, it may be necessary to use the REPAIR_ALLOW_DATA_LOSS clause. In the likely event that you cannot allow the loss of data, you will need to restore from a known clean backup.
Before performing any actions on the database it is recommended to consult you database administrator and to backup your database.
Repair a data page:
Notification Server 6.0