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

Internal Server Error after deployed to HANA DB #1020

Open
iadc2005 opened this issue Apr 26, 2024 · 2 comments
Open

Internal Server Error after deployed to HANA DB #1020

iadc2005 opened this issue Apr 26, 2024 · 2 comments

Comments

@iadc2005
Copy link

dear experts, I tried many times but still have no clue why there is an internal server error issue as screenshot shows.
Screenshot 2024-04-26 at 16 51 09
Once I click "Go" (sorry for Chinese) and the error will come.
The same will come if I click "Create".
I already granted myself the required roles.

@iadc2005
Copy link
Author

iadc2005 commented Apr 26, 2024

I tried to ask ChatGPT and here is the reply for my logs(I have this table in my HANA DB and don't know why it will call draft table just for a simple Travel "GET" call):

This error message is similar to the previous one you posted. It indicates that there is an issue with the SQL query being executed. The database is unable to recognize the column name ALIAS_1.DRAFTADMINISTRATIVEDATA.INPROCESSBYUSER.

Here are some steps to troubleshoot this issue:

  1. Check the SQL Query: Ensure that the SQL query is written correctly. Make sure that the column ALIAS_1.DRAFTADMINISTRATIVEDATA.INPROCESSBYUSER exists in the TravelService_Travel_drafts table. If the column doesn't exist, you will need to correct the SQL query.

  2. Check the Table Structure: Make sure that the table TravelService_Travel_drafts has the column DRAFTADMINISTRATIVEDATA.INPROCESSBYUSER. If the column doesn't exist, you will need to add it to the table or modify your SQL query to remove references to it.

  3. Check the Database Schema: Ensure that the database schema is up-to-date and matches the schema expected by your application. If the schema is out of date, you may need to update it.

  4. Check the Application Code: If the SQL query is being generated by your application code, there may be a bug in the code that is causing the incorrect query to be generated. Check the code to make sure it is correctly generating the SQL query.

If you're still having trouble after trying these steps, you may need to seek help from a database administrator or a developer familiar with the database and application.

@iadc2005
Copy link
Author

iadc2005 commented Jun 5, 2024

Anyone here?

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

1 participant