Organization Name (Required - If you are an Oracle Partner, please provide the organization you are logging the idea on behalf of):

University of California San Diego

Description (Required):

In OBIEE 12c, the "Path not found" error text no longer shows the path/object that can't be found.

In OBIEE 11g, the error text was much more informative and listed the broken path.

Oracle Development's reply on why it changed: "This is done for security reason where the path cannot be exposed to unauthorized user to access".

It is puzzling how providing the broken path in the error text is a "security issue" since user access is sufficiently controlled by folder/object permissions and application roles.

Oracle Development also suggests to use the NQQUERY log to find the broken path. However, this is an unreasonably cumbersome task, especially when in a time-contrained troubleshooting situation in a production environment.

PLEASE RESTORE how the "Path not found" error text was displayed in 11g. The new 12c error text is too generic and offers little help to support staff.

Use Case and Business Need (Required):

To know the broken path is extremely helpful when supporting users and troubleshooting issues.

Enhancement Request / Service Request:

SR 3-28427488201 : 22A SOAK - OTBI - Error Text Unspecific