Error 15517 : Can not execute as the database principal because the principal <user> does not exist - When Restoring SQL*Server for a GoldenGate Setup
(Doc ID 1633767.1)
Last updated on JULY 18, 2023
Applies to:
Oracle GoldenGate - Version 11.1.1.1.2 and laterInformation in this document applies to any platform.
Symptoms
You are setting up bi-directional replication between 2 SQL*Server databases using GoldenGate 11.1.
You have followed these steps -
1. The database of Sql Server A (2008 R2) was backed up and restored to the empty database on Sql Server B (2008 R2)
2. Using the backup recovery of Sql Server 2008 r2 the backup set from Server A is copied to Server B.
3. When Goldengate extract is not installed on Server A the restore is successful.
4. After Goldengate extract is installed on Server A there is an error during the restore of data to Server B.
The error returned is -
Processed 21% .
Processed 31% .
Processed 42% .
Processed 52% .
Processed 60% .
Processed 70% .
Processed 81% .
Processed 91% .
Processed 100% .
The database has been '<db_name>', file '<file1>' (1 located on file ) processed 3624 .
The database has been '<db_name>', file '<file2>' (1 located on file ) processed 3 .
Message 22831 , Level 16, State 1, Procedure sp_cdc_disable_db_internal, line 231
Could not update the metadata to indicate not enabled for change data capture database <db_name>. Run '[sys]. [Sp_MScdc_ddl_database triggers]' when drop'' failed. The error returned was 15517 : 'Can not execute as the database principal because the principal "<user>" does not exist, this type of principal can not be impersonated , or you do not have the required permissions. ' . Please use this action and error to determine the cause of the failure and resubmit the request.
Message 266 , Level 16, State 2, Procedure sp_cdc_disable_db_internal, line 0
The number does not match the transaction count after EXECUTE indicates BEGIN and COMMIT statements. On a count = 0 , current count = 1.
Message 266 , Level 16, State 2, Procedure sp_cdc_restoredb_internal, line 0
The number does not match the transaction count after EXECUTE indicates BEGIN and COMMIT statements. On a count = 0 , current count = 1.
Message 266 , Level 16, State 2, Procedure sp_cdc_restoredb, line 0
The number does not match the transaction count after EXECUTE indicates BEGIN and COMMIT statements. On a count = 0 , current count = 1.
Message 266 , Level 16 , State 2, Line 1
The number does not match the transaction count after EXECUTE indicates BEGIN and COMMIT statements. On a count = 0 , current count = 1.
Location: execsql.cpp: 344
Expression: exception = se_OK!
SPID: 60
Process ID: 3080
Message 3165 , Level 16, State 1, Line 1
Database '<db_name>' has been restored , but the error in the reduction / delete replication . The database is left offline. See the SQL Server Books Online topic MSSQL_ENG003165.
Message 3167 , Level 16, State 1, Line 1
RESTORE unable to start database '<db_name>'.
Msg 3013, Level 16 , State 1 , Line 1
RESTORE DATABASE is terminating abnormally .
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |