permission denied on sp_thresholdaction

Post by unknown
Hi Everyone,
I am getting a strange error when the thresholdaction
procedure is run. The error msg is below. Pls help
Error: 10330, Severity: 14, State: 1
00:00000:00078:2008/12/30 17:36:09.74 server EXECUTE
permission denied on object sp_thresholdaction, database
sybsystemprocs, owner dbo 00:00000:00078:2008/12/30
17:36:09.74 server Threshold procedure 'sp_thresholdaction'
Thanks

Did you create this proc with any other user id other than dbo ? Check
the results of sp_helprotect for sp_thresholdaction proc

-HTH
Manish Negandhi
[TeamSybase]

unknown

2008-12-31 08:44:13 UTC

Did you create this proc with any other user id other than
dbo ? Check the results of sp_helprotect for
sp_thresholdaction proc
-HTH
Manish Negandhi
[TeamSybase]

Actually its not a user or permission issue because the user
threshold is executing but the lct one is not.
The sp_thresholdaction just prints a warning msg in the
errorlog at a user threshold but on lct it actually dumps
the transaction log. It is failing on the second step.

unknown

2008-12-31 10:14:36 UTC

EXECUTE

Post by unknown
permission denied on object sp_thresholdaction,
database sybsystemprocs, owner dbo
00:00000:00078:2008/12/30 17:36:09.74 server
Threshold procedure 'sp_thresholdaction' returned

Post by unknown
Thanks

Did you create this proc with any other user id other
than dbo ? Check the results of sp_helprotect for
sp_thresholdaction proc
-HTH
Manish Negandhi
[TeamSybase]

Actually its not a user or permission issue because the
user threshold is executing but the lct one is not.
The sp_thresholdaction just prints a warning msg in the
errorlog at a user threshold but on lct it actually dumps
the transaction log. It is failing on the second step.

Hey guys,
Thanks for your help. Actually it was indeed a permission
issue . The owners were different for the thresholds. I
hadn't expected the LCT to be owned by some app user id. I
have changed it back. Still investigating why it was so but
this error should be resolved by now.

Thanks

Derek Asirvadem

2009-01-01 05:39:38 UTC

Post by unknown
Actually it was indeed a permission
issue . The owners were different for the thresholds. I
hadn't expected the LCT to be owned by some app user id. I
have changed it back. Still investigating why it was so but
this error should be resolved by now.

That's exactly why I stated what I did.
This is often the result of poor security (permissions, aliases)
practices anyway. Eg you have soome_user aliased to dbo. Works for a
while, but when you drop the user ...

You are best advised to drop/create all thresholds as "sa" not the dbo
or any other user. Changing the dbo of all databases to something
consciously determined (and never dropped) is also a good idea.

--
Cheers
Derek
Senior Sybase DBA / Information Architect
Copyright © 2008 Software Gems Pty Ltd
Quality Standards = Zero Maintenance + Zero Surprises
Performance Standards = Predictability + Scaleability

unknown

2010-01-04 18:43:38 UTC

Post by unknown
Hi Everyone,
I am getting a strange error when the
thresholdaction procedure is run. The error msg is

below. Pls help >

Post by unknown
Error: 10330, Severity: 14, State: 1
00:00000:00078:2008/12/30 17:36:09.74 server

EXECUTE

Post by unknown
permission denied on object sp_thresholdaction,
database sybsystemprocs, owner dbo
00:00000:00078:2008/12/30 17:36:09.74 server
Threshold procedure 'sp_thresholdaction' returned

Post by unknown
Thanks

Did you create this proc with any other user id other
than dbo ? Check the results of sp_helprotect for
sp_thresholdaction proc
-HTH
Manish Negandhi
[TeamSybase]

Actually its not a user or permission issue because the
user threshold is executing but the lct one is not.
The sp_thresholdaction just prints a warning msg in the
errorlog at a user threshold but on lct it actually
dumps the transaction log. It is failing on the second

step.
Hey guys,
Thanks for your help. Actually it was indeed a permission
issue . The owners were different for the thresholds. I
hadn't expected the LCT to be owned by some app user id. I
have changed it back. Still investigating why it was so
but this error should be resolved by now.
Thanks

Derek Asirvadem

2008-12-31 06:09:53 UTC