Cdc Error 15517
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home20122008 R2200820052000LibraryForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: CDC in RC0 - cannot enable DB SQL Server > SQL Server Data Warehousing Question 0 Sign in to vote
Could Not Update The Metadata That Indicates Database Is Not Enabled For Change Data Capture
Restored a SQL2005 DB (Standards) to SQL2008. When try to enable CDC (USE Standards; GO could not update the metadata that indicates table is enabled for change data capture EXEC sys.sp_cdc_enable_db; GO), receive following message: Msg 22830, Level 16, State 1, Procedure sp_cdc_enable_db_internal, Line 186Could not update the metadata the specified '@server' is invalid (valid values are returned by sp_helpserver) that indicates database Standards is enabled for Change Data Capture. The failure occurred when executing the command 'SetCDCTracked(Value = 1)'. The error returned was 15517: 'Cannot execute as the database principal because the principal "dbo"
Sp_changedbowner
does not exist, this type of principal cannot be impersonated, or you do not have permission.'. Use the action and error to determine the cause of the failure and resubmit the request.Msg 266, Level 16, State 2, Procedure sp_cdc_enable_db_internal, Line 0Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.Msg 266, Level 16, State 2, Procedure sp_cdc_enable_db, Line 0Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1.Msg 3998, Level 16, State 1, Line 1Uncommittable transaction is detected at the end of the batch. The transaction is rolled back. I am sysadmin. I have tried running under SQL service account with is also sysadmin. Same result. When i build a 'test' database from scatch in SQL2008, i can enable CDC. Had similar inconsistant experience using CPT5 and trying to enable. But that is not real world. I have to bring many 2005 DBs up to 2008. fyi - we are using LiteSpeed 4.8x for restore. Friday, June 20, 2008 4:11 PM Reply | Quote Answers 0 Sign in to vote HMCSharon wrote: Unfortunetly our databases are too big to be using the SQL Server tools for movement. too big to be using sql server tools? both the copy database wizard and the ssis transfer database task can implement attach/detach...which should be much faster than backup and restore. no? hth Monday, June 30, 2008 3:45 AM Reply | Quote Moderator All replies 0 Sign in to vote i'm not sure about this, but it seems that CDC doesn't work on DBs that aren't cre
you are trying to enable CDC feature on a particular database which has "DBOwner" value of NULL. Msg 22830, Level 16, State 1, Procedure sp_cdc_enable_db_internal, Line 186 Could not update the metadata that indicates database CDC_AdventureWorks is enabled for Change Data Capture. The failure occurred when executing the command 'SetCDCTracked(Value = 1)'. The error returned was 15517: 'Cannot execute as the database principal because the principal "dbo" does not exist, this type https://social.technet.microsoft.com/Forums/sqlserver/en-US/547764d2-31ff-4d01-8bce-9239e83c37fa/cdc-in-rc0-cannot-enable-db?forum=sqldatawarehousing of principal cannot be impersonated, or you do not have permission.'. Use the action and error to determine the cause of the failure and resubmit the request. Msg 266, Level 16, State 2, Procedure sp_cdc_enable_db_internal, Line 0 Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1. http://pranavkumarsql.blogspot.com/2013/03/sql-server-2009-r2-error-returned-was.html Msg 266, Level 16, State 2, Procedure sp_cdc_enable_db, Line 0 Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 0, current count = 1. Msg 3998, Level 16, State 1, Line 1 Uncommittable transaction is detected at the end of the batch. The transaction is rolled back. Let's take "AdventureWorks" as our sample database. Run following script in SSMS SELECT name ,database_id ,USER_NAME(owner_sid) as DBOwner FROM sys.databases WHERE name ='AdventureWorks' IF you see 'DBOwner' as NULL value, change this to 'sa'. To do this run following script Use AdventureWorks GO Exec sp_changedbowner 'sa' GO Even we are saying to change it to 'sa' which is not our loginID or userAccount, what this does is that it assign the "DBOwner" to "dbo" over which we can implement CDC. Now you are all set to get rid of this error. Note: More to come... Posted by Lost in SQL World at 9:59 AM Email ThisBlogThis!Share to TwitterShare to Fac
SERVER - Fix - Error - 22830 - Could not update the metadata that indicates database %s is enabled for Change DataCapture. https://raresql.com/tag/cannot-execute-as-the-database-principal-because-the-principal-dbo-does-not-exist/ Posted in Errors, SQL SERVER, tagged Cannot execute as the database http://dba.stackexchange.com/questions/39500/why-is-cdc-capture-failing-due-to-a-missing-dbo-principal principal because the principal "dbo" does not exist, Msg 15517, Msg 22830 Level 16 State 1, raresql, SQL, SQL Server, SQL Server 2012 on March 11, 2014 | Leave a Comment » Change Data Capture (CDC) is one of the best features shipped with SQL Server could not 2008. We usually use CDC to record the change of the tables using DML operations for audit purpose. Today, I configured CDC for one of my clients. In order to configure the CDC, first of all, you need to enable it. However, once I tried enabling it but it gave me an error. Let me explain the could not update error and its solution in detail. Message Number: 22830 Severity : 16 Error Message: Could not update the metadata that indicates database %s is enabled for Change Data Capture. The failure occurred when executing the command ‘%s'. The error returned was %d: ‘%s'. Use the action and error to determine the cause of the failure and resubmit the request. Error Generation: Let me enable the CDC to generate the error. USE AdventureWorks2012 GO EXEC sys.sp_cdc_enable_db GO --OUTPUT Msg 22830, Level 16, State 1, Procedure sp_cdc_enable_db_internal, Line 193 Could not update the metadata that indicates database AdventureWorks2012 is enabled for Change Data Capture. The failure occurred when executing the command ‘SetCDCTracked(Value = 1)'. The error returned was 15517: ‘Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission.'. Use the action and error to determine the cause of the failure and resubmit the request. Ooopps…… I am unable to enable the CDC. What is the
log in tour help Tour Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Database Administrators Questions Tags Users Badges Unanswered Ask Question _ Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Why is CDC capture failing due to a missing dbo principal up vote 2 down vote favorite I am having a problem running the CDC change capture job against some of my test databases. The error message I'm getting is the following: Executed as user: NT AUTHORITY\NETWORK SERVICE. Cannot execute as the database principal because the principal "dbo" does not exist, this type of principal cannot be impersonated, or you do not have permission. [SQLSTATE 42000] (Error 15517). How can I fix this? sql-server sql sql-server-2008 change-data-capture share|improve this question edited Aug 19 '15 at 23:22 Paul White♦ 29.1k11162260 asked Apr 8 '13 at 12:48 meh-uk 1136 migrated from stackoverflow.com Apr 8 '13 at 14:43 This question came from our site for professional and enthusiast programmers. add a comment| 1 Answer 1 active oldest votes up vote 3 down vote accepted dbo is mapped to an invalid login. Re-map it to a valid one: ALTER AUTHORIZATION ON DATABASE::[