SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Check Catalog Msg 3857, State 1: The attribute (owning_principal_id=NULL) is required but is missing...


Check Catalog Msg 3857, State 1: The attribute (owning_principal_id=NULL) is required but is missing for row (principal_id=9) in sys.database_principals...

Author
Message
Staggerlee
Staggerlee
SSCarpal Tunnel
SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)SSCarpal Tunnel (4.6K reputation)

Group: General Forum Members
Points: 4608 Visits: 1189
Hi,

We've had a vm crash which has caused a lot of corruption. all my errors seem to be in sys.database_principals.. which seemed easy to fix!

I thought dropping the principal id user and recreating would resolve it but now it looks like I have possible made it worse.. when i run dbcc checkdb i now get

Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

Is there way back from this? Any ideas on how you should clear up the orginal error (I still have a few databases with it, so hoping there is a nice clean way to do it)

Thanks for any advice.
Lincoln Burrows
Lincoln Burrows
SSCoach
SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)SSCoach (17K reputation)

Group: General Forum Members
Points: 17248 Visits: 2282
Staggerlee - Wednesday, April 26, 2017 1:34 AM
Hi,

We've had a vm crash which has caused a lot of corruption. all my errors seem to be in sys.database_principals.. which seemed easy to fix!

I thought dropping the principal id user and recreating would resolve it but now it looks like I have possible made it worse.. when i run dbcc checkdb i now get

Msg 0, Level 11, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.
Msg 0, Level 20, State 0, Line 0
A severe error occurred on the current command. The results, if any, should be discarded.

Is there way back from this? Any ideas on how you should clear up the orginal error (I still have a few databases with it, so hoping there is a nice clean way to do it)

Thanks for any advice.
You can try to repair database by using inbuilt feature Repair_Allow_Data_Loss. But this will delete your data and that's why recommended not to use this. Or if you have a recent clean backup available. you may try to restore it from this. IF not best is to use
this option to repair your SQL Server database using SQL Server database recovery tool. As, to save your crucial data from deletion this is the best recommended option.

Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum









































































































































































SQLServerCentral


Search