nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

How to suppress inaccessible column error in OBIEE?

3923818

Hi All,

I have changed the setting 'PROJECT_INACCESSIBLE_COLUMN_AS_NULL as YES' in NQSConfig.INI file. Inspite of this setting, some of the reports results in inaccessible column error.

Please help me to suppress this error either as a long term solution or a workaround solution.

Thanks,

Muthukumar

Find more posts tagged with

Accepted answers

All comments

Gianni Ceresa

3923818 wrote:I have changed the setting 'PROJECT_INACCESSIBLE_COLUMN_AS_NULL as YES'

Why was it at "NO" before? Because 'Yes' is the default value...

And would be good if you could post some more info, right now you don't give much. (More efforts put into writing a thread result in better answers)

3923818

Hi,

Thank you for the reply. Please help me to understand better with your question as the default value for this setting is NO.

I have made the presentation folder for certain application roles to 'No Access'. As well as set the PROJECT_INACCESSIBLE_COLUMN_AS_NULL as YES'. Hence as per the presentation folder setting due to No Access for the particular user. when the same set of users login to OBIEE, it is expected that the user would end up in Inaccessible Column error. My understanding is the setting 'PROJECT_INACCESSIBLE_COLUMN_AS_NULL as YES'. would help to resolve the problem. Hence posted a thread in community to find out of whether there is anything else that I need to set it up.

Currently as a workaround solution, for suppressing the error, I have created a separate report to show a message(as User does not have permissions to view this report) and this report will be shown based on the section condition applied.

Hope this information helps or please let me know if you require additional information.

Thanks,

Gianni Ceresa

What exact version of the tool are you talking about?

An official doc says this:

The default value is YES

3923818

Hi,

The Version is OBIEE 11.1.1.9.160119 and please find the settings that I copied over from the file.

[SECURITY]

DEFAULT_PRIVILEGES = READ;

PROJECT_INACCESSIBLE_COLUMN_AS_NULL = YES; # default is no

Thanks,

Muthukumar

[Deleted User]

3923818 wrote:The Version is OBIEE 11.1.1.9.160119

Before Gianni continues:

That's a 3-year old version. The last update for 11.1.1.9 was 11.1.1.9.190416 and 11g as a whole product family is out of error correction since December 2018.

See MOS Doc Id 1488475.1

3923818

Hi,

Please let me know if there is a solution for this version. We are in the mid of OBIEE 12c upgrade which will conclude by end of third quarter. Till then I need a solution for an ongoing OBIEE security project which I am currently working on. Hence please recommend any solutions, if any.

Thanks,

Muthukumar

Gianni Ceresa

3923818 wrote:Hi,Thank you for the reply. Please help me to understand better with your question as the default value for this setting is NO.

https://docs.oracle.com/middleware/11119/biee/BIESG/configfileref.htm#i1076541

Oracle seem to disagree with you ...

A.6.2 PROJECT_INACCESSIBLE_COLUMN_AS_NULL

Controls how security-sensitive columns are displayed to unauthorized users. If this parameter is set to YES, then a NULL expression replaces the original column expression in the query and secured columns are hidden from unauthorized users in analyses.

If this parameter is set to NO, then when a user attempts to run a report that contains a secured column the user is not authorized to see, an unresolved column error occurs.

The default value is YES.

Example: PROJECT_INACCESSIBLE_COLUMN_AS_NULL = YES;

Even ignoring that aspect (which could lead to a fairly unknown history of that system and whatever has been changed already over time), the doc talk about security on columns, you set security on a folder. So doesn't shock me that you don't get what you expect.

Set security on the column only and see what happen.

As Christian pointed out 11.1.1.9 is so old that I don't have one for ages, so no chances to even look at that practically ...

3923818

Hi Gianni,

Thank you for the explanation. I will set up at the column level and confirm if it is a working solution.

Thanks,

Muthukumar