One of the customers had a delivery failure (PROD) due to a DB connection issue. There weren't any issues in non-prod delivery installation. The error shows (!!!Error, no database connection exists).
The customer is asking whether there are any corrective actions that could be taken in order to avoid the same error in the future for the same environment followingly other environments as well and also asking the reason for this connection timeout.
Solved
What are the reasons for the error: "(!!!Error, no database connection exists)" in a delivery failure?
Best answer by Charith Epitawatta
The error is pretty much self explanatory, and suggests that the database went down or there was a connectivity issue. Therefore, we can conclude that this is not an issue with the delivery as the delivery got installed on other environments as well, without any issue.
To avoid this kind of issues, there is a step in the IFS installer to enter the IFSSYS password to validate the connection before the delivery installation. However, if any database connectivity or availability issues occur during the database deployment phase of the delivery, this kind of errors can still occur.
Therefore we can advise customers to perform activities such as this during proper maintenance windows so that there will be minimal interruptions and make other personnel informed of the activity so that there won’t be any conflicts. Also it would be a good practice to prepare a check-list that includes some pre-checks that need to be done before installing a delivery so that they will be able to find out if there is a chance of getting any database connection or any other issues such as this.
Other than this, I can’t think of any technical corrective actions that can be taken to avoid this kind of issues.
Hope this helps!
+31The error is pretty much self explanatory, and suggests that the database went down or there was a connectivity issue. Therefore, we can conclude that this is not an issue with the delivery as the delivery got installed on other environments as well, without any issue.
To avoid this kind of issues, there is a step in the IFS installer to enter the IFSSYS password to validate the connection before the delivery installation. However, if any database connectivity or availability issues occur during the database deployment phase of the delivery, this kind of errors can still occur.
Therefore we can advise customers to perform activities such as this during proper maintenance windows so that there will be minimal interruptions and make other personnel informed of the activity so that there won’t be any conflicts. Also it would be a good practice to prepare a check-list that includes some pre-checks that need to be done before installing a delivery so that they will be able to find out if there is a chance of getting any database connection or any other issues such as this.
Other than this, I can’t think of any technical corrective actions that can be taken to avoid this kind of issues.
Hope this helps!
I’m getting the same error over and over during Deployment of a fresh installation. Build Home is on the same server like database and nobody than me is working on that VM. The VM was freshly prepared for me.
Other customer VMs does not have this issue.
+7HI
I have the same fenomen, by an upgrade installation. Did you find out what was the cause of the issue?
/Theo
HI
I told the customer to completely deactive any Anti-Virus measurement. Even if they deactivated the software it was still some kind of active and let me run into this error.
After the software was removed properly the installed was done without an error.
Regards
Bernd
1 person likes this
+7Hi
thanks for sharing!
My Customer has the database on Linux, but it could be the antivirus software on the management server, I’ll check that.
BR
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.