Skip to Content
0

SAP Hana Express Edition 2.0 : Error building Core_db

Oct 17, 2017 at 02:40 AM

403

avatar image
Former Member

Hi All,

I am stuck with exercise 2.5 of the Open SAP course Software Development on SAP HANA (Update Q4/2016).

Please find the content of the my mta.yaml file below.

mtayaml.png

a user defined service to provide access to the SFLIGHT schema is defined with the command line as attached:

cups.png

and sflight.hdbgrants to grant the permission for hdi container users

{

"hdi-sflight-service": { "object_owner" : { "schema_privileges":[ { "reference":"SFLIGHT", "privileges_with_grant_option":["SELECT", "SELECT METADATA"] } ] }, "application_user" : { "schema_privileges":[ { "reference":"SFLIGHT", "privileges_with_grant_option":["SELECT", "SELECT METADATA"] } ] } }

}

and when i build the core_db, i received the following error message

[INFO] Creating MTA archive
[INFO] Saving MTA archive MYHANA2_0.0.1.mtar

10:15:28 PM (DIBuild) ********** End of /MYHANA2 Build Log ********** 10:15:28 PM (DIBuild) Build results link: https://hxehost:53075/che/builder/workspace83hcke65oyjgj4fx/download-all/7?arch=zip 10:15:29 PM (DIBuild) Cannot get report for the build 10:15:30 PM (Builder) Build of /MYHANA2 completed successfully. 10:16:04 PM (Builder) Build of /MYHANA2/core_db started. 10:16:07 PM (DIBuild) Build of /MYHANA2/core_db in progress 10:16:07 PM (DIBuild) [INFO] Injecting source code into builder...
[INFO] Source code injection finished
[INFO] ------------------------------------------------------------------------10:16:09 PM (DIBuild) + EXIT=1
+ npm install10:16:16 PM (DIBuild)
> deploy@ start /hana/shared/HXE/xs/app_working/hxehost/executionroot/8d213a2e-01f5-4692-b00f-c933a6984b8d/app/META-INF/.sap_java_buildpack/tomcat/temp/builder/hdi-builder/builds/build-2449043790622864348/core_db
> node node_modules/@sap/hdi-deploy/deploy.js

@sap/hdi-deploy, version 3.2.0 (mode default), server version 2.00.020.00.1500920972 (2.0.20.0), node version 6.11.1
Using service replacements from environment variable "SERVICE_REPLACEMENTS" with 1 replacements
Collecting files...
Collecting files... ok (0s 29ms)
6 directories collected
15 files collected
0 reusable modules collected
Processing grants files...
Processing "cfg/sflight.hdbgrants"...
Error: service CROSS_SCHEMA_SFLIGHT_V as replacement for service hdi-sflight-service not found; either the service definition does not exist or it is not tagged with the tag "hana"
(2s 619ms)


npm ERR! Linux 4.4.74-92.35-default
npm ERR! argv "/hana/shared/HXE/xs/app_working/hxehost/executionroot/8d213a2e-01f5-4692-b00f-c933a6984b8d/app/META-INF/resources/nodejs/vendor/node6.11/bin/node" "/hana/shared/HXE/xs/app_working/hxehost/executionroot/8d213a2e-01f5-4692-b00f-c933a6984b8d/app/META-INF/resources/nodejs/vendor/node6.11/lib/node_modules/npm/bin/npm-cli.js" "start"
npm ERR! node v6.11.1
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! deploy@ start: `node node_modules/@sap/hdi-deploy/deploy.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the deploy@ start script 'node node_modules/@sap/hdi-deploy/deploy.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the deploy package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node node_modules/@sap/hdi-deploy/deploy.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs deploy
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls deploy
npm ERR! There is likely additional logging output above.10:16:19 PM (DIBuild) npm ERR! Please include the following file with any support request:
npm ERR! /hana/shared/HXE/xs/app_working/hxehost/executionroot/8d213a2e-01f5-4692-b00f-c933a6984b8d/app/META-INF/.sap_java_buildpack/tomcat/temp/builder/hdi-builder/builds/build-2449043790622864348/core_db/npm-debug.log10:16:19 PM (DIBuild) Build of /MYHANA2/core_db failed. 10:16:19 PM (Builder) Check console logs for details 10:16:19 PM (Builder) Build of /MYHANA2/core_db failed. 10:16:19 PM (DIBuild) Cannot get report for the build

mtayaml.png (25.2 kB)
cups.png (10.5 kB)
10 |10000 characters needed characters left characters exceeded

Quick questions:

- Did you get any error when you tried to create the user provided service?

- Are you working in the same organization/space when you use the Web IDE and the CLI?

0
Former Member

Hi Florian,

Thank you for your reply and I had no error to create user provided service and I always work in "development" space which come from express virtual machine for all my exercises.

Daniel

0

I would agree with what Florian said: double check the space the service was created it. Its easy to be in the wrong space from the command line when you issue the create command. That seems the most likely reason to get this error.

0
Former Member
Thomas Jung

Hi Thomas,

It was very frustrated and I still got the error to compile the code. But this time error message display as authentication failed. I have checked around everything I could. The user provided service has been created in the same space as project.

Thanks in advance.

@sap/hdi-deploy, version 3.3.0 (mode default), server version 2.00.021.00.1507025078 (2.0.21.0), node version 6.11.1
Using service replacements from environment variable "SERVICE_REPLACEMENTS" with 1 replacements
Collecting files...
Collecting files... ok (0s 8ms)
8 directories collected
13 files collected
0 reusable modules collected
Processing grants files...
Processing "cfg/sflight.hdbgrants"...
Error: authentication failed
grantor service: hdi-sflight-service, granting user: SYSTEM

file name: /hana/shared/HXE/xs/app_working/hxehost/executionroot/8e432316-7c30-42e4-9d8f-b24f87772037/app/META-INF/.sap_java_buildpack/tomcat/temp/builder/hdi-builder/builds/build-2239309648132428048/core_db/cfg/sflight.hdbgrants

(0s 324ms)

0

Authentication failed tells me you put the incorrect password in the user provided service.

0
Former Member
Thomas Jung

Hi Thomas,

I found after I changed to single container and import sflight catalog into HXE, also grant select & select metadata to SYSTEM. I got the different error message as follow. but it looks like It is getting there.... can you take a look this?


5:34:33 PM (Builder) Build of /openSAPHANA5/core_db started. 5:34:37 PM (DIBuild) Build of /openSAPHANA5/core_db in progress

5:34:38 PM (DIBuild) [INFO] Injecting source code into builder...
[INFO] Source code injection finished
[INFO] ------------------------------------------------------------------------
5:34:40 PM (DIBuild) + EXIT=1
+ npm install
+ npm start
5:34:42 PM (DIBuild) > deploy@ start /hana/shared/HXE/xs/app_working/hxehost/executionroot/7f545f34-1328-4263-8e86-bea61db2e493/app/META-INF/.sap_java_buildpack/tomcat/temp/builder/hdi-builder/builds/build-2257431521290585531/core_db
> node node_modules/@sap/hdi-deploy/deploy.js

@sap/hdi-deploy, version 3.3.0 (mode default), server version 2.00.021.00.1507025078 (2.0.21.0), node version 6.11.1
Using service replacements from environment variable "SERVICE_REPLACEMENTS" with 1 replacements
Collecting files...
Collecting files... ok (0s 5ms)
8 directories collected
13 files collected
0 reusable modules collected
Processing grants files...
Processing "cfg/sflight.hdbgrants"...
Error: Error executing: GRANT "SELECT","SELECT METADATA" ON SCHEMA "SFLIGHT" TO "OPENSAP_HANA5_1#OO" WITH GRANT OPTION;
(nested message: invalid user name: OPENSAP_HANA5_1#OO: line 1 col 57 (at pos 56))

grantor service: hdi-sflight-service, granting user: SYSTEM
file name: /hana/shared/HXE/xs/app_working/hxehost/executionroot/7f545f34-1328-4263-8e86-bea61db2e493/app/META-INF/.sap_java_buildpack/tomcat/temp/builder/hdi-builder/builds/build-2257431521290585531/core_db/cfg/sflight.hdbgrants
(0s 361ms)

Thanks again

Daniel

0

This error indicates that your user provided service is pointing to a different tenant that the HDI Space itself. This is why the technical user is not found to perform the grant upon.

0

Have you had any luck with this? I see you mention that you changed to a single tenant. If you used the tenant mapping tool for your XSA space to be pointed to a new HANA tenant, please note that this doesn't alter existing container instances. You would have to manually delete those from the command line with the xs delete-service command for them to pickup the new tenant configuration of the space.

0
* Please Login or Register to Answer, Follow or Comment.

0 Answers