Information Steward access to SLT schema for temp tables

[patrickbachmann]

Hi folks,

NOTE: I posted this in HANA IN MEMORY topic area prior to discovering this Information Steward area.

I have a colleague working on an Information Steward proof of concept for pulling master data from HANA.  He asked me to setup a HANA user for Information Steward to connect and read from our default schema that contains all tables replicated from SAP via SLT.  Let's call this SAP_SCHEMA.  Let's call the Information Steward user and schema INFO_STEWARD.  The INFO_STEWARD user has full access to it's own INFO_STEWARD schema and I also gave him SELECT_USER role against the SLT schema named SAP_SCHEMA.  But when they run their job they get error that they can not CREATE temporary table against SAP_SCHEMA.

Normally we never allow any user except SLT user to create tables in the SAP_SCHEMA.  All users have SELECT only.  But as a test I humored him and gave POWER_USER role against SAP_SCHEMA, had him run his load job and then I monitored M_TEMPORARY_TABLES.  Suddenly his job started working and I watched 500+ temporary tables fill up M_TEMPORARY_TABLES, however they all listed the temp table schema as INFO_STEWARD schema.  So I'm completely puzzled; if all the temp tables are created in it's own INFO_STEWARD schema then why does it need CREATE against SAP_SCHEMA??  My only theory is that it truly created a single temp table in SAP_SCHEMA but it happened and dropped so fast that I could not see it with my own eyes.  Whereas the other 500+ I could see sitting there for several minutes before they were dropped.

Are there any Information Steward users out there whom can explain to me why it would need CREATE against the SLT schema where our source tables live?  I'm hoping it's some sort of configuration problem on the Information Steward side as we do not want to doll out create access.  Other system users we have such as MicroStrategy only have read access to the SLT schema and create temp tables fine in their own MicroStrategy schema.

Thanks for any insight you can provide!

-Patrick

[patrickbachmann]

Folks has nobody experienced this issue?

We have tried two separate profile loads in Info Steward.  First against a table in SLT derived schema and second against a view in "_SYS_BIC".  In both cases the job errored something like this;

SQL submitted to database <> resulted in error <[SAP AG][LIBODBCHDB DLL][HDBODBC] General error;258 insufficient privilege: Not

                                                     authorized>. The SQL submitted is <CREATE TYPE "_SYS_BIC"."DS_TT_2C5B1" AS TABLE

It's trying to put the temp table into whichever schema it's querying rather than it's own schema.

-Patrick

[former_member187605]

The HANA CREATE TYPE command does not create a table, but a user-defined type. A type does not require any storage, so that won't be a problem.

But I agree, it doesn't look correct you need extra privileges for a profiling task. That might be just a "feature" of the tool.

[patrickbachmann]

Hi Dirk,

We created an SAP message and this is what they had to say below but this did not work.  Based upon what they say I assume we can disable this 'feature'.

-Patrick

I believe this is by design due to the changes that were make to

optimizer which can result in Data Services creating temp tables or

views on HANA to increase performance since Data Services 4.2 SP1.

Try this and check if the read only works:

(1) Go to %DS_COMMON_DIR%\conf

(2) Edit DSConfig.txt and add the following option under the

[al_engine] section:

HANA_CALCVIEW_OPTIMIZER = FALSE

(3) Restart DS Job Service.

[former_member187605]

I assume they checked compatibility between your IS and HANA versions (as detailed in SAP Note 1600140), correct?

[patrickbachmann]

Hi Dirk,

Well looking at this matrix is an eye opener!  For SPS 8 rev 82 I'm seeing lots of NOT AVAILABLE, NOT CERTIFIED, NOT RECOMMENDED.  I'm confirming versions of DS and IS but this looks to be the issue.  Will close this thread as soon as I confirm.

Many thanks!

-Patrick