Following teched : [ERROR] [cds.deploy] - Service key is missing mandatory field 'schema'.

[LaurensSteffers]

Hi everybody,

I'm following the DAT160 workshop. Unfortunately, although I checked everything regarding the trial environment, hana db, npm modules etc, I still keep getting the following error.

[ERROR] [cds.deploy] - Service key is missing mandatory field 'schema'. Make sure you are not using a managed service.

Anyone got an idea? DB is up and running and I've connected with the CF environment. Hope you can help!

Thanks!

Laurens

[iwona_hahn]

Maybe the session owners thomas.jung or rich.heilman can help here?

[thomas_jung]

Are you using HANA Cloud Trial? And not the HANA As A Service? If you do a cf services from the terminal in the Business Application Studio, what do you see as the results? If you are following the workshop with HANA Cloud trial and have the matching trial org and space; no additional configuration should be needed and the standard cds deploy command is what we are using here to perform this step.

[LaurensSteffers]

Hello Thomas,

I'm following it to the letter (famous last words, I know). I even recreated the Dev space for the Studio but no result. Running cf services results in the following (where I use the dat160 db)

Any ideas are welcome. I'll try it again tomorrow morning.

Kind regards

Laurens

[thomas_jung]

I think we might be missing a screenshot or something from the above. You said results in the following..., but I don't see anything in the comment.

Are you seeing dat160 as a service instance in the results? That would seem to mean that the cds deploy at least partially worked and created the service instance. You might try deleting the dat160* service-key and service instance and then running the cds deploy command again.

[LaurensSteffers]

Sorry Thomas, somehow the picture didn't get through. Here was the response:

- dat160 hana-cloud-trial hana update succeeded

I deleted the gen folder again. and executed the different commands. The npm run hana failed again. This is the final message I get:

Service dat160 already exists

[ERROR] [cds.deploy] - Service key is missing mandatory field 'schema'. Make sure you are not using a managed service. at HanaDeployer._validateServiceKey (/home/user/.node_modules_global/lib/node_modules/@sap/cds-dk/node_modules/@sap/cds/bin/deploy/to-hana/hana.js:188:15)

I'm not sure what you mean with deleting the service key and instance of dat160. Is that on the CF environment or the BAstudio?

All the best and thanks for the help!

Laurens

[LaurensSteffers]

And btw: let me start all over 🙂 Maybe I missed a step.

[LaurensSteffers]

Well, I'm a little bit further but still clueless why this is:

Instead of executing cds deploy --to hana:dat160 i used cds deploy --to hana-cloud-trial:Dat160

Note the different name (dat160 vs Dat160) and the fact that I used the hana-cloud-trial addition. I think both hana:... and hana-cloud-trial work btw because I got two.

So I think the dat160 conflicts with the previous dat160 name we used. Naming it differently did the trick.

Now lets continue with the rest of the tutorial 🙂

Thanks!

[LaurensSteffers]

well, I think I solved it. Did the following (in short):

- Created the dev space, hana db, bamodeller space.

- used cds deploy --to hana:dat160_somethingelse

I DID NOT specify hana:dat160. This caused the problem because there is already a service running with the dat160 name (that is the sap hana cloud service). When you leave this out, it will generate a dat160-db and it will show two services

All works fine now 🙂

Kind regards

Laurens

[thomas_jung]

Oh yes - because you named your database itself dat160 you can’t also have a container named the same. The HANA database itself is larger than this one example and can contain many projects/containers. But the actual names here aren’t really important as long as they are unique.

[LaurensSteffers]

Thank you Thomas!

[gadirov]

Hi thomas.jung ,

I have a similiar issue with the small difference that I have to provide the key before deploying to hana cloud since hana cloud already exists but is not accessible directly to us developers by the customer. I just have the name and the corresponding key which I have to reference. This is what I am getting after npm run hana or when I try to deploy to cloud foundry:

Service broker error: Service broker hana-broker failed with: Failed to select a database for instance XX, because of: Multiple databases are available, exact id needs to be specified via parameter 'database_id' (available ids: [8485f48c-0753-48c7-b51e-eef988192cc2, 44ddcccf-5f73-4d5c-8b97-f107e1716271]) FAILED [ERROR] [cds.deploy] - Create request failed at Function.createService (/home/user/projects/app-39818-arbeitskleidung/node_modules/@sap/cds/bin/deploy/to-hana/cfUtil.js:96:33) at process._tickCallback (internal/process/next_tick.js:68:7)

In mta.yaml I provided:

config: database_id: "47ddcccf-5f73-4d5c-9b97-g107e1716271"

schema: app-XXX-schema

Still no success...

BR
Rufat

[thomas_jung]

I don't think the cds deploy will read that from the mta.yaml. You need to pass it in direct to the cds deploy command (or create a script in the package.json). The database id needs to be supplied via the database specific parameters on the cds deploy --to hana:<database specific parameters>. See cds help deploy. Or create the HDI container service instance manually before you run the cds deploy and pass the database id in via parameters there like so: cf create-service hana hdi-shared hana-opensap-cloud-2020-db -c '{"database_id": "XXXX"}'

[LaurensSteffers]

So the answer is: make sure to have unique names regarding hana db, schema's etc etc. Thanks!