My Oracle Support Banner

SETWORKSPACELOCKMODEON Gives Error Even If User Have WM_ADMIN_ROLE Role (Doc ID 1525378.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Workspace Manager - Version 10.2.0.5 and later
Information in this document applies to any platform.

Goal

User with name BPEL_USER calls procedure from AR user schema that should create workspace and set lockmode to the new workspace:

DBMS_WM.CREATEWORKSPACE(‘workspace’, TRUE);
DBMS_WM.SETWORKSPACELOCKMODEON (‘workspace’, 'S');

Workspace is created, but set lockmode gives error:

  ORA-20020: 'WM_ADMIN_ROLE' or ownership is required to set workspace lock mode

To BPEL_USER and AR users is granted WM_ADMIN_ROLE.

Both users form their schema connection can execute SETWORKSPACELOCKMODEON to all workspaces, but exactly in case when one schema calls other to create workspace and set them lockmode, lockmode gives error.

This happens in Oracle 10.2.0.5.0 but does not reproduce in 10.2.0.4
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.