Skip to main content

Issue:
Database errors when trying to abort a remote installing in the middle of the execution. There it is trying to stop the process in the middle using (ctrl + c). The installation stops there, but the java process started on the DB side does not stop.

 

Resolution:

 

It is possible to end the running Java process by killing the particular Java process through the task manager when the DB installation process has been started.

However, there is no way to roll back the work that has been carried out by the DB installer already. Depending on where you were in the DB installation process when you wanted to stop it you can rerun the same DB installation process from start without getting any errors. However, if the cre files have already been deployed, re-running the DB installer will result in errors. Therefore, it is best to start the DB installation process again on a freshly restored DB.

Hi,

Yes,  to be sure everything get deployed properly you need to restart from a fresh DB if the first db deployment fails mid-way. 
i assume you are doing a fresh install as you mention the cre scripts.

Normal deliveries are designed to be re-runnable, but not he fresh install or the upgrades.

If a normal delivery is aborted mid-way, the installer will sense this next time it is run and try to get in sync with the parameters that was stored before the previously aborted installation.

And yes - you need to kill the java process as well.


 

Reply


Terms & ConditionsCookie settings