cancel
Showing results for 
Search instead for 
Did you mean: 

SQL Error : insufficient privilege: Not authorized at ptime/query.... HTTP Connection to HANA Analysis Office

Former Member
0 Kudos

Hi,

We currently have two environments which I will summarize below.  After a HANA db upgrade from version 95 to version 102 all views which have descriptions added to an attribute now produce an error about authorizations.

Environment Overview:

Non Prod:

  • HANA DB version 102
  • SBOP 4.1 SP7
  • Office Analysis 2.2 Sp3.1
  • Lumira 1.30

Prod:

  • HANA DB version 95
  • SBOP 4.1 SP7
  • Office Analysis 1.4 SP7
  • Lumira 1.30

It is worth noting that when making the move to Analysis 2.x and upgrading your hana system, you no longer can use ODBC to connect to HANA.  We have our non prod environment configured to use HTTP connection with SAML SSO through SBOP.  This is working great with no problems. The issue we are facing is that any attribute in a view which has a description mapped to it fails with the error: Caught exception : exception 42111: SQL Error : insufficient privilege: Not authorized at ptime/query/checker/query_check.cc:3389 (42014)

If I connect to our non prod hana database using the odbc connection method and analysis 1.4 SP7 not issues or errors are thrown and the descirptions are displayed as normal.  If I switch to Analysis 2.2 SP3.1 and use the HTTP connection I get the authorization error which I noted above. .

I have done further testing and found Lumira 1.30 connects to non prod hana ( direct connect not HTTP) and works fine producing the attributes and descriptions with out error. Has anyone else encountered this error?  I have not found any SAP notes or blogs with this problem.  I do have a case open with SAP but currently no traction.

View Entire Topic
Former Member
0 Kudos

After working with SAP this issue has been deemed a bug with our current hana db revision 102.02.  SAP noted that the issue is fixed in Rev 102.06 and Rev 112.

Former Member
0 Kudos

Hi,

so how to solve this issue, Shall we upgrade the database? and is it a big project?

Thanks

Former Member
0 Kudos

We implemented the patch of Rev 102.06 and that fixed the problem and we currently are seeing no issues.  In terms of "is it a big project" that depends on your environment and number of users.  For us the patch was a simple 4 hour outage.

former_member183326
Active Contributor
0 Kudos

@ Jalal Altarah

Your issue is not a bug. Your issue is that you haven't gotten the correct user to create the Role which has the select privilege on it. Please do this first.

Former Member
0 Kudos

Sorry, your wrong. This is a BUG and was fixed my SAP. We had the correct roles and such.

former_member183326
Active Contributor
0 Kudos

Excuse me Chuck, read my response again. I wasn't referring to you, I was referring to Jalal. Read it again.

Former Member
0 Kudos

Hi,

I contact SAP and they confirm the upgrade solution.

Thanks