Answered by:
EXECUTE permission was denied in sysdb database, schema 'ssma_oracle'.

Question
-
Hello,
I have migrated a database from oracle to SQL server.
After migration when I run a script on the migrated database,
I get following error . The user with which I have migrated the database and I am running this script are same.
Also I have given these 3 permissions on sysdb database to this user - public, db_datareader db_datawriter.
Please let me know what am I missing?
Msg 229, Level 14, State 5, Server SERVER5009\SQLEXPRESS, Procedure PROC_LOADTEST , Line 303
The EXECUTE permission was denied on the object 'db_error_get_oracle_exception_i
d', database 'sysdb', schema 'ssma_oracle'.
Msg 229, Level 14, State 5, Server SERVER5009\SQLEXPRESS, Procedure ssma_rethr
owerror, Line 1
The EXECUTE permission was denied on the object 'ssma_rethrowerror', database 's
ysdb', schema 'ssma_oracle'.Thanks a lot.
Thursday, April 2, 2015 6:53 AM
Answers
-
Hi ManiC24,
Msg 59999, Level 16, State 1, Procedure PROC_LOADTEST, Line 324
SSMA Oracle exception emulation for [ORA-00001]
As other post, the issue is related to Oracle. The number 59999 is used for all Oracle system, user-defined, or predefined exceptions.
Based on my research, ORA-00001 is common when: "a program tries to insert a "duplicate" row in a table," and that, "when a unique constraint is violated the row is NOT added to the table. To overcome this error, either remove the unique restriction or do not insert duplicate key.
Reference:
http://www.dba-oracle.com/sf_ora_00001_unique_constraint_violated.htm
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support- Edited by Lydia ZhangMicrosoft contingent staff Friday, April 3, 2015 2:35 AM
- Proposed as answer by Lydia ZhangMicrosoft contingent staff Wednesday, April 8, 2015 1:58 AM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Thursday, April 9, 2015 10:55 AM
Friday, April 3, 2015 2:34 AM
All replies
-
Try:
USE sysdb
GO
GRANT EXECUTE ON PROC_LOADTEST TO user
GO
GRANT EXECUTE ON ssma_rethrowerror TO userRefer:
Thursday, April 2, 2015 7:11 AM -
Hi dave_gona,
I executed the above commands and run the procedure again.
Then I got this message -
Msg 59999, Level 16, State 1, Procedure PROC_LOADTEST, Line 324
SSMA Oracle exception emulation for [ORA-00001]Please suggest.
Thursday, April 2, 2015 11:41 AM -
This is not looking SQL issue, looks like something to do with oracle.Thursday, April 2, 2015 1:05 PM
-
Hi ManiC24,
Msg 59999, Level 16, State 1, Procedure PROC_LOADTEST, Line 324
SSMA Oracle exception emulation for [ORA-00001]
As other post, the issue is related to Oracle. The number 59999 is used for all Oracle system, user-defined, or predefined exceptions.
Based on my research, ORA-00001 is common when: "a program tries to insert a "duplicate" row in a table," and that, "when a unique constraint is violated the row is NOT added to the table. To overcome this error, either remove the unique restriction or do not insert duplicate key.
Reference:
http://www.dba-oracle.com/sf_ora_00001_unique_constraint_violated.htm
Thanks,
Lydia Zhang
Lydia Zhang
TechNet Community Support- Edited by Lydia ZhangMicrosoft contingent staff Friday, April 3, 2015 2:35 AM
- Proposed as answer by Lydia ZhangMicrosoft contingent staff Wednesday, April 8, 2015 1:58 AM
- Marked as answer by Lydia ZhangMicrosoft contingent staff Thursday, April 9, 2015 10:55 AM
Friday, April 3, 2015 2:34 AM