cancel
Showing results for 
Search instead for 
Did you mean: 

Algorithm execution failed for mining run in Rule Mining App

av101986
Explorer

am getting Algorithm execution failed for mining run while running Rule Mining App for Product Master in SAP MDG DQM

Accepted Solutions (0)

Answers (2)

Answers (2)

ashish0770
Participant
0 Kudos

Hi

Run below queries in your sap data base or ask your basis to run it. DB user authorizations is needed.

SELECT * FROM "SYS"."AFL_AREAS" WHERE AREA_NAME = 'AFLPAL';

SELECT * FROM "SYS"."AFL_PACKAGES" WHERE AREA_NAME = 'AFLPAL';

SELECT * FROM "SYS"."AFL_FUNCTIONS" WHERE AREA_NAME = 'AFLPAL';

If you get the output of the PAL, AFL packages name .. something like below:

If you do not get below packages names as output. that means AFL and PAL is not installed.

Please install AFL using below link. Additionally, please check product version pre-requisite for installation.

https://help.sap.com/viewer/aa94b47610d545f28dd90711580350d6/2.0.00/en-US/1075a25a03c349d18b36be9ab6...

I039655
Advisor
Advisor
0 Kudos

In order to do rule mining, SAP PAL (Predictive Analysis Library) is called.

Enable Script Server

To use the PAL procedures, you must enable the Script Server in the SAP HANA instance, See SAP Note 1650957 Information published on SAP site for further information.

Authorizations for ABAP Database User.

The database user for the ABAP system is used to execute the functions provided by PAL. Therefore, the system user SAP<SID> in SAP HANA database for the ABAP system needs to have the role AFL__SYS_AFL_AFLPAL_EXECUTE granted to get authorization to execute the algorithms. See the document Security of the SAP HANA Predictive Analysis Library (PAL) for more information.

Use SAP HANA Studio to grant the role AFL__SYS_AFL_AFLPAL_EXECUTE to the HANA DB user SAP<SID>.

Please check whether these 2 points are configured correctly, if yes and still issue exists, then please raise SAP incident to require further support

thunermay
Explorer
0 Kudos

I had the same problem but the solution didn’t fix it for me at first. The scriptserver was one part of the solution and worked accordingly but the role granting not. Our HANA DB user was not called SAP<SID> but instead SAPABAP1. The name is only a best-practise not mandatory. Creating a user that is called SAP<SID> also obviously does not work. To find out what the right user is called (if the SAP<SID> is not in HANA Studio) you have to go in the SAP GUI and log on to the desired system. From there you go to "System->Status…" and then under “database data” the field “User” (see attached Screenshot)