SAP Knowledge Base Article - Preview

2938063 - sp_dbcc_deletehistory may raise a 567 error - SAP ASE

Symptom

  • When granular permissions are disabled, a user who wants to run sp_dbcc_deletehistory on a specific database must be the owner of the database or must have sa_role.
  • A user does not have sa_role, but it is aliased as dbo in a database.
  • When the user executes sp_dbcc_deletehistory on the database, sp_is_valid_user called by sp_dbcc_deletehistory raises a 567 error.

$ isql -UuserA -P<password> -S<ASE name>
1> use dbccdb
2> go
1> exec sp_dbcc_deletehistory "<date>", "<database name>"
2> go
(1 row affected)
Msg 567, Level 16, State 1:
Server '<ASE name>', Procedure 'sp_is_valid_user', Line 97:
You must have the following role(s) to execute this command/procedure:
'sa_role'. Please contact a user with the appropriate role for help.
No history information to delete.
(return status = 1)
1>


Read more...

Environment

  • SAP Adaptive Server Enterprise(ASE) 15.7
  • SAP Adaptive Server Enterprise(ASE) 16.0

Product

SAP Adaptive Server Enterprise 15.7 ; SAP Adaptive Server Enterprise 16.0

Keywords

CR#821967, #821967, 821967 , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Bug Filed

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.