Default schema for table KxAdmin on HANA

[i033659]

Hello,

I tried to save a Predictive Analytics classification model to HANA. How can I control, in which HANA schema the table KxAdmin is created?

Is it possible to have more than one table KxAdmin in different schemas? How does PA "find" KxAdmin when I load a model?

Thanks,

Ingo

[abdel_dadouche · Accepted solution]

Hi,

This is documented in the ODBC Fine Tuning guideat section "6.3 Schema Definition".

You can edit your "KJWizard.cfg" and add the following line at the end:

    ODBCStoreSQLMapper.MyODBCDSN.defaultSchemaForMetadata=crm

where:

     - MyODBCDSN is my ODBC DSN

     - crm is the schema I want to store my metedata tables

Hope this helps.

@bdel

[achab · Accepted solution]

Hi,

The OBDC Fine Tuning Guide mentioned by Abdel can be found here: SAP Predictive Analytics 2.4 – SAP Help Portal Page

My 2 cents here,

Antoine

[i033659]

Hi Abdel,

This works fine if you use the desktop version of PA. Now I have the same question, if I use the server version of PA 2.4. There you also find a file KJWizard.cfg in a directory KJWizardJNI. However the same entry as above does not seem to work here.

Does the above mentioned ODBC fine tuning guide also apply for the server version?

Regards,

Ingo

[abdel_dadouche]

Hi,

Off course, you have a configuration available for the Server part.

It is located in:

    C:\Program Files\SAP Predictive Analytics\Server 2.4\EXE\Servers\CORBA

and the file is named:

     KxCORBA.cfg

it is the equivalent of the KJWizard.cfg but in a client/server mode.

All the configuration you have made can be transposed here as well.

Best Regards

@bdel

[i033659]

Hi Abdel,

Thanks!

However for date tables (kxdatelookup) it doesn't seem to work. kxdatelookup is created in the schema of the user who logs on to the (HANA) database. I created the table through the remote control panel, PA 2.4.

Regards,

Ingo

[abdel_dadouche]

Hi,

KxDateLookup is not considered as a Metadata table which explains why it is not created under the schema defined by the defaultSchemaForMetaData.

The user interface is not allowing to change the name nor the schema. I will raise this as a defect.

I wasn't able to find a workaround for this in the config or the UI (the KxDateLookup table name is hard coded). The only option is to move the table over to the desired schema via SQL as this table is/should only be created once.

Thanks for letting us know

Regards

@bdel

[achab]

Hi Ingo,

Can you please mark this as answered?

Thanks and regards,

Antoine

[achab]

Hi Ingo, any news?

Thanks & regards

Antoine

[achab]

Hi Ingo,

Screenshots of the flow you followed would help for the troubleshooting.

We have internal communities to support SAP employees, please shoot me an email and I'll guide you through.

Best regards,

Antoine