Skip to main content
Answer

Cannot deploy after renaming database

  • May 31, 2023
  • 6 replies
  • 77 views
Nick Janssen
Captain
Forum|alt.badge.img+5

Hi,

 

We have a project where multiple versions have been deployed already. We cleaned up the database names and did all the adjustments in the runtime configuration to ensure the right database is used. Everything is working fine (SF & application), except I am not able to do a new deploy. After establishing a connection to the correct database, the following scripts are automatically checked:

Screenshot of deployment scripts

I cannot un-check the db script, where it tries to create the database. Obviously, the database already exists and I want to perform an upgrade rather than creating a new database.

Anyone able to help?

Best answer by Nick Janssen

Thanks for all the help, I managed to solve the problem.

Lately, we have been doing some network routing changes to improve the performance of all Thinkwise applications. An incorrect domain name was configured in the runtime configuration and it could there not find the database. It was a coincidence that I discovered the issue after the database rename.

This topic has been closed for replies.

6 replies

Anne Buit
Community Manager
Forum|alt.badge.img+5
  • Anne Buit
  • Community Manager
  • May 31, 2023

Hi, when you hit the ‘Connect’ button you can see the database server and name it is attempting to deploy on. This information is stored in a runtime configuration.

You can update the runtime configuration to match the renamed database name.

Nick Janssen
Captain
Forum|alt.badge.img+5
  • Nick JanssenCaptain
  • Author
  • Captain
  • May 31, 2023

Hi, when you hit the ‘Connect’ button you can see the database server and name it is attempting to deploy on. This information is stored in a runtime configuration.

You can update the runtime configuration to match the renamed database name.

Hi Anne,

Thanks for your quick reply.

The information in the runtime configuration is correct: both the server and the database → Also, it is working in the end application where the same runtime configuration is used.

FYI: the IAM database is also renamed. I am not sure if this has anything to do with it?

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Nick,

Could it be that Indicium does not have sufficient rights to open or connect to that database?

"Wake me up before you low-code"
Nick Janssen
Captain
Forum|alt.badge.img+5
  • Nick JanssenCaptain
  • Author
  • Captain
  • May 31, 2023

Hi Nick,

Could it be that Indicium does not have sufficient rights to open or connect to that database?

Hi Mark,

That should not be possible as it is the same database, but only renamed.

However, in IIS our application pool was also renamed. Could this have something to do with it?

Normally we have a Thinkwise support engineer available, but I know he is on holiday. Is there someone else available for support?

Mark Jongeling
Administrator
Forum|alt.badge.img+23

Hi Nick,

Feel free to create a support ticket. The Indicium log may also hold valuable information. Can you look into the error log and see if anything stands out?

"Wake me up before you low-code"
Nick Janssen
Captain
Forum|alt.badge.img+5
  • Nick JanssenCaptain
  • Author
  • Captain
  • Answer
  • May 31, 2023

Thanks for all the help, I managed to solve the problem.

Lately, we have been doing some network routing changes to improve the performance of all Thinkwise applications. An incorrect domain name was configured in the runtime configuration and it could there not find the database. It was a coincidence that I discovered the issue after the database rename.

Terms & ConditionsCookie settingsAccessibility statement