Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hana Schema ServiceBinding creation fails because of 'no procedure with name UPDATE_USER_IDENTITY' #491

Open
mdudushka opened this issue Dec 13, 2024 · 3 comments

Comments

@mdudushka
Copy link

mdudushka commented Dec 13, 2024

Hello,

We have a Hana Cloud DB(hana-cloud-tools in BTP) and a Kyma cluster. We are trying to deploy an app to Kyma that utilizes a service binding for Hana Schema but the creation of the service instance fails because of an error in the database.

Error:

ServiceBinding create failed: Fail to add x509 identify to the user USR_<redacted>, because of: SAP DBTech JDBC: [328]: invalid name of function or procedure: no procedure with name UPDATE_USER_IDENTITY

We updated the Hana Cloud version but that didn't solve the issue.

For more context:
We have an automated Jenkins pipeline that deploys an app to Kyma and runs certain tests. The app in particular uses hana schema service instance. The service instance is created successfully but the service binding creation fails.

Any idea how to solve this issue?

@kerenlahav
Copy link
Contributor

Hi @mdudushka
The error is returned from the Hana broker, you need to check with them.
Thanks

@mdudushka
Copy link
Author

Hi, The hana broker colleagues fixed the service binding creation.

But now when the service binding is created the user field is empty.

Image

Any idea why that is?

@kerenlahav
Copy link
Contributor

the operator is not responsible for the credentials content and does not manipulates it, any issues with the credentials should be forwarded to the broker's team

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants