Unity DBWalker Error Help...

Unanswered Question
May 12th, 2010
User Badges:

Received the following error. Subscribers say their accounts are working fine, but Unity says to delete and re-add the accounts...



0:(error) Internal dbWalker error:-2147467259 ([Microsoft][ODBC SQL Server Driver][SQL Server]I/O error (bad page ID) detected during read at offset 0x00000000a44000 in file 'e:\MSSQL\data\UnityDb.mdf'.) in procedure checkSubscribers of Form frmMain

1435:(error) No notificaiton devices found for this subscriber. This is an unusual error to encounter on a production system.

You will need to delete and recreate this subscriber.  If you cannot delete the subscriber in the SA directly you can remove this subscriber's row from the Subscriber table in the UnityDB database in SQL.

If you are uncomfortable editng SQL directly, please contact TAC.  Be sure to get a backup of your system using DiRT before editing anything in SQL on your own.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
lindborg Wed, 05/12/2010 - 13:18
User Badges:
  • Cisco Employee,

Well, the error means what it says - no notification devices were found for the user in quesiton (or all the users in question I guess) - this wont make their accounts stop working other than notificaitons wont be going out if that's expected.  It does, however, indicate your system is potentially in a very bad way.  The error coming back is being issued from the SQL Server - dbWalker is doing a very generic query for all notificaiton devices for a user and SQL is coming back and saying there's corruption of some kind and nothing is returned.


That's bad.  You need to make sure you have a backup in place sooner rather than later.


Lots of reasons for corruption are possible, hard to say what but it could be a hard drive sector bit the dust is could be a drive going south in a hurry - no way to know but corruption is never a good thing.


If you're users don't have notification devices configured for dialout (i.e. delivering a note to a page on new urgent messages or calling them at home etc...) then they probably wont notice anything wrong.  I'm curious what shows up in the SA when you open one of these users and try and access their notificaiton devices - I'm guessing some sort of error or empty page comes up.


Either way - dbWalker can't fix that kind of corruption - hence the indication that to get the user back into shape will require a delete/recreate.  But as noted, please be sure to get a backup of your system in place if you haven't already.

Brian Carscadden Thu, 05/13/2010 - 10:24
User Badges:

Jeff,


Thanks for the reply ... always appreciated.


You're right, blank page when checking out Message Notification ... with the following pop-up error:


LBL_SUBEMPTYTYPELIST


We're working PDQ on a complete image backup (Acronis) and working to build a box in parallel to migrate the data via DiRT.


Regards,


Brian Carscadden

Actions

This Discussion