Access Error in HANA CV – DBTech JDBC: [258]: insufficient privilege: [2950] user is not authorized

Estimated read time 4 min read

Hi All, while working with security around HANA CVs, I faced the below error multiple times while retrieving data from the CV, it took a while to understand the root cause

Error: SAP DBTech JDBC: [258]: insufficient privilege: [2950] user is not authorized :

Even though the CV had Apply Privilege check maintained as Blank in View Properties, we got this error –

To understand more about the access errors while accessing data from CV, there are mainly two –

1. When we see the GUID in error –

This means the Analytic Privilege is being checked for the CV which you are previewing the data from.

Two ways to resolve this –

   Either create a analytic priv (SQL/Classic accordingly) and it to the user profile directly or through role.Or if not needed, mark apply privilege as blank in the view properties of CV.

2. When we see a generic error –

User faces this error when one of the underlying CVs (Z or standard ones generated through Data Modeling) has the Apply Privilege Check enabled. you can check all the views used in Scenario section of the CV. For example in this case, as you can see, there was only one, disable the check at the individual CV level (or enable the check and add it to the analytic priv). Just to add, there can be multiple Views being used in a CV.

You can hover over the nodes to see, in which package the CV is placed –

Objects created through data modeling like composite providers, BW characteristics are inside the package –

Few important points to note here – 

In the latest HANA versions, the default check applied on CVs is SQL Analytic Privileges.Even if you mark Apply Priv check as Blank for BW objects like Comp Provider etc. If regenerated, in modeling Perspective, the check will be applied again.SYS_BI_CP_ALL (default SAP_ALL priv for CVs) only work for CVs when the Apply priv check is set as Classic Analytic Priv.

Please comment if there are any questions on handling the security for HAAN Objects. thank you.

 

 

​ Hi All, while working with security around HANA CVs, I faced the below error multiple times while retrieving data from the CV, it took a while to understand the root causeError: SAP DBTech JDBC: [258]: insufficient privilege: [2950] user is not authorized :Even though the CV had Apply Privilege check maintained as Blank in View Properties, we got this error -To understand more about the access errors while accessing data from CV, there are mainly two -1. When we see the GUID in error -This means the Analytic Privilege is being checked for the CV which you are previewing the data from.Two ways to resolve this –   Either create a analytic priv (SQL/Classic accordingly) and it to the user profile directly or through role.Or if not needed, mark apply privilege as blank in the view properties of CV.2. When we see a generic error -User faces this error when one of the underlying CVs (Z or standard ones generated through Data Modeling) has the Apply Privilege Check enabled. you can check all the views used in Scenario section of the CV. For example in this case, as you can see, there was only one, disable the check at the individual CV level (or enable the check and add it to the analytic priv). Just to add, there can be multiple Views being used in a CV.You can hover over the nodes to see, in which package the CV is placed -Objects created through data modeling like composite providers, BW characteristics are inside the package -Few important points to note here – In the latest HANA versions, the default check applied on CVs is SQL Analytic Privileges.Even if you mark Apply Priv check as Blank for BW objects like Comp Provider etc. If regenerated, in modeling Perspective, the check will be applied again.SYS_BI_CP_ALL (default SAP_ALL priv for CVs) only work for CVs when the Apply priv check is set as Classic Analytic Priv.Please comment if there are any questions on handling the security for HAAN Objects. thank you.    Read More Technology Blogs by Members articles 

#SAP

#SAPTechnologyblog

You May Also Like

More From Author