As DBA I freqeuently use SETUSER to impersonate other users or to impersonate a role that owns a schema (often "dbo", as we have used that for user-defined objects out ot MS SQL compatibility).

With a database running on, I often (but not always) get an error message when issuing SETUSER dbo - claiming SQLCODE -121 ("Permission denied: you do not have permission to set user "dbo"). It does also fail for some other users.

Of course the DBA user does have that privilege, as the following query reveals:

select * from sp_displayroles ('DBA', 'expand_down') where role_name = 'SET USER';

I don't notice that behaviour with and have never noticed that in previous versions...

What could cause this effect?

asked 17 Nov, 06:41

Volker%20Barth's gravatar image

Volker Barth
accept rate: 34%

edited 17 Nov, 06:42

Re: What could cause this effect?

A bug was introduced in a recent change. It can be caused by executing grant/revoke statements on a separate connection. It is corrected in an upcoming release.

permanent link

answered 20 Nov, 11:12

JBSchueler's gravatar image

accept rate: 19%

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 17 Nov, 06:41

question was seen: 83 times

last updated: 20 Nov, 11:12