10g & 11g Catalog Objects Under Catalog Folder With Read Permission Can Be Deleted But Cannot Be Renamed (Doc ID 2006633.1)

Last updated on JULY 07, 2015

Applies to:

Business Intelligence Suite Enterprise Edition - Version 10.1.3.4.2 [2405] and later
Information in this document applies to any platform.

Symptoms

Catalog folder with "Read" permission, catalog objects saved under the catalog folder can't be renamed, but can be deleted.

 

This issue is happening in OBIEE 11g and can be reproduced with the following steps.

10g

1. Create a user "test" and make it not a member of Administrators Group.

2. Connect to OBIEE as an Administrator.Create a new folder "TEST" and a new catalog object(folder or answer), place it in the folder "TEST".

3. Connect to OBI Catalog Manager as an Administrator.

   Set the permissions on folder "TEST" to be "Read" only for the user "test", and set the permissions on the catalog object to be "Full Control".

4. Connect to OBIEE as the user "test".

5. Navigate to Manage Catalog -> Select the catalog object and Edit Name and Description, you will receive a Access Denied error. (This is correct behaviour.)

    Or create a new catalog object and try to save it in the folder - you will receive a Access Denied error. (This is correct behaviour.)

6.Click on Delete button beside the catalog object , it can be deleted. (This is the errant behaviour).


11g


1. Create a user "test" and make it a member of the BI Author Group.

2. Connect to OBIEE as an Administrator. Create a new folder "TEST" and a new catalog object(folder or analysis., place it in the folder "TEST".

3. Set the permissions on the Folder to be "Open" for the user "test",and set the permissions on the catalog object to be "Full Control".

4. Connect to OBIEE as the user "test".

5. Navigate to the catalog object under "TEST" folder, click "More" on the catalog object, note that the "Rename" option is not available. (This is correct behaviour).

6. Note the "Delete" option is available, and clcik on "Delete", it can be deleted. (This is the errant behaviour).

 

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms