SAP HANA Express Edition 2.0 SP03 - Build Error

[Phillip_P]

Anyone else following the recent YouTube videos series by thomas.jung, at video 10 -Part 5.6 Non-Container Schema Access I get a build error after adding the SFLIGHT data.

Did others add SFLIGHT into their core_db or SYSTEMDB as the blog that is referenced in the video shows? I followed the blog, used Import Catalog Objects for SFLIGHT into a new SYSTEMDB not the core_db. I was unable to import SFLIGHT into core_db as I get an insufficient privileges error, same with creating the CUPS user in core_DB. So the CUPS user is created in SYSTEMDB.

I followed all other steps ok up to the first build in this video and my build fails. Any pointers on where i might have gone wrong or if others have the same issue.

The log doesn't show much that is useful:

-------

0 info it worked if it ends with ok 1 verbose cli [ '/hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/resources/nodejs/vendor/node8.11/bin/node', 1 verbose cli '/hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/resources/nodejs/vendor/node8.11/lib/node_modules/npm/bin/npm-cli.js', 1 verbose cli 'start' ] 2 info using npm@5.6.0 3 info using node@v8.11.4 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle deploy@~prestart: deploy@ 6 info lifecycle deploy@~start: deploy@ 7 verbose lifecycle deploy@~start: unsafe-perm in lifecycle true 8 verbose lifecycle deploy@~start: PATH: /hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/resources/nodejs/vendor/node8.11/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/.sap_java_buildpack/tomcat/temp/builder/hdi-builder/builds/build-6064181157259881905/openSAPHANA/db/node_modules/.bin:/hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/resources/nodejs/vendor/node8.11/bin:/usr/sap/HXE/HDB90/exe/krb5/bin:/usr/sap/HXE/HDB90/exe/krb5/sbin:/usr/sap/HXE/HDB90/hxehost:/usr/sap/HXE/HDB90:/usr/sap/HXE/HDB90/exe:/usr/sap/HXE/HDB90/exe/mdc:/usr/sap/HXE/HDB90/exe/Python/bin:/usr/sap/HXE/HDB90/exe/dat_bin_dir:/usr/sap/HXE/HDB90/exe:/hana/shared/HXE/xs/bin:/usr/sap/HXE/HDB90/exe/krb5/bin:/usr/sap/HXE/HDB90/exe/krb5/sbin:/usr/sap/HXE/HDB90/hxehost:/usr/sap/HXE/HDB90:/usr/sap/HXE/HDB90/exe:/usr/sap/HXE/HDB90/exe/mdc:/usr/sap/HXE/HDB90/exe/Python/bin:/usr/sap/HXE/HDB90/exe/dat_bin_dir:/usr/sap/HXE/home:/usr/sap/HXE/home/bin:/usr/local/bin:/usr/bin:/bin:/usr/games 9 verbose lifecycle deploy@~start: CWD: /hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/.sap_java_buildpack/tomcat/temp/builder/hdi-builder/builds/build-6064181157259881905/openSAPHANA/db 10 silly lifecycle deploy@~start: Args: [ '-c', 'node node_modules/@sap/hdi-deploy/deploy.js' ] 11 silly lifecycle deploy@~start: Returned: code: 1 signal: null 12 info lifecycle deploy@~start: Failed to exec start script 13 verbose stack Error: deploy@ start: `node node_modules/@sap/hdi-deploy/deploy.js` 13 verbose stack Exit status 1 13 verbose stack at EventEmitter.<anonymous> (/hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/resources/nodejs/vendor/node8.11/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16) 13 verbose stack at emitTwo (events.js:126:13) 13 verbose stack at EventEmitter.emit (events.js:214:7) 13 verbose stack at ChildProcess.<anonymous> (/hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/resources/nodejs/vendor/node8.11/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 13 verbose stack at emitTwo (events.js:126:13) 13 verbose stack at ChildProcess.emit (events.js:214:7) 13 verbose stack at maybeClose (internal/child_process.js:925:16) 13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5) 14 verbose pkgid deploy@ 15 verbose cwd /hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/.sap_java_buildpack/tomcat/temp/builder/hdi-builder/builds/build-6064181157259881905/openSAPHANA/db 16 verbose Linux 4.4.121-92.92-default 17 verbose argv "/hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/resources/nodejs/vendor/node8.11/bin/node" "/hana/shared/HXE/xs/app_working/hxehost/executionroot/368c809f-5b84-47e1-b300-f28d7baf35b6/app/META-INF/resources/nodejs/vendor/node8.11/lib/node_modules/npm/bin/npm-cli.js" "start" 18 verbose node v8.11.4 19 verbose npm v5.6.0 20 error code ELIFECYCLE 21 error errno 1 22 error deploy@ start: `node node_modules/@sap/hdi-deploy/deploy.js` 22 error Exit status 1 23 error Failed at the deploy@ start script. 23 error This is probably not a problem with npm. There is likely additional logging output above. 24 verbose exit [ 1, true ]

------------

[former_member188585]

Pre-requisite : SFLIGHT catalog should be imported to HXE multi-tenant DB in Database explorer.

[umberto_panico]

OK, I've HANA Express 2.0 SP03 rev35 on VM but still not work.

You can follow also comments stack in youtube (Part 5.6 Non-container schema access).
Thanks and happy build.
Umberto

[umberto_panico]

Hi Phillip Parkinson

have you solved? Please share your solution, have same problem.

Best Regards.

Umberto

[Phillip_P]

Hi umberto.panico,

Soon after this issue occurred, HANA Express 2.0 SP03 rev35 was released. So I set up a new VM with rev35, I will follow the development steps again and test the build this evening.

Regards

Phillip

[thomas_jung]

I would add that if you aren't sure what tenant your space is mapped to, you can see the mapping in the XS Advanced Admin Cockpit:

And if you need to find the SQL Ports of each tenant, then run this query in the SQL Console of the SYSTEMDB:

SELECT DATABASE_NAME, 
    SERVICE_NAME, 
    PORT, 
    SQL_PORT
FROM SYS_DATABASES.M_SERVICES;

[thomas_jung]

No the _1 has nothing to do with this. This is a mismatch between tenants. Perhaps the port specification in your user provided service is wrong. If you are matching my video, my space is pointing to my first tenant not the SYSTEMDB.

[thomas_jung]

You would never import a schema into a container. So don’t import into core_db. You need to import into a regular dB connection and the same tenant that you are creating your containers in.

[Phillip_P]

Thanks for the clarification Thomas.

I have imported into a regular db connection on the development tenant. I'm using the latest HXE VM.

I see in the logs my schema name has _1 at the end of it, perhaps this is the issue. The logs also show:

Processing grants files... Processing "cfg/SFLIGHT.hdbgrants"... Using grantor service "ServiceName_1" of type "sql"Error: Error executing: GRANT "SFLIGHT_CONTAINER_ACCESS" TO "OPENSAPHANA_OPENSAPHANA_HDI_CONTAINER_1#OO"; (nested message: invalid user name: OPENSAPHANA_OPENSAPHANA_HDI_CONTAINER_1#OO: line 1 col 37 (at pos 36))grantor service: "ServiceName_1", type: "sql", user: "CUPS_SFLIGHT"file name: cfg/SFLIGHT.hdbgrants

I've checked SFLIGHT.hdbgrants and the enternal SAP HANA Service are correct but the build still fails.