![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi all...quick question: we're thinking of applying build 2299 to our current version of SQLAnywhere 11.0.1.2044. If the setup program for 2299 goes awry for some reason, I'm assuming we will have to re-install SQLAnywhere 11.0.1.2044, that is, go back to our old build? The reason I ask this is because we have had some problems applying Sybase builds in the past to our system. Also, if 2299 goes awry for some reason, is there any way to de-install it? Any info would be greatly appreciated |
#3
| |||
| |||
|
|
Mark, If something goes wrong during the installation, then the installer should roll back all changes and exit, leaving the state as it was before attempting to apply the EBF. Before applying the EBF, all SQL Anywhere components need to be shut down. |
#4
| |||
| |||
|
|
Just to add: If you have installed any EBF and then want to go back to an older EBF (say, because the newer EBF contains a new bug or an undesired change in behaviour), then you will have to de-install and re-install the whole SA 11 product up to the previous EBF - AFAIK, there's no way to "rollback" just the EBF. HTH Volker Josh Savill [Sybase] wrote: Mark, If something goes wrong during the installation, then the installer should roll back all changes and exit, leaving the state as it was before attempting to apply the EBF. Before applying the EBF, all SQL Anywhere components need to be shut down. |
#5
| |||
| |||
|
|
Yes, Volker is correct. When the EBF installs correctly, the only way to revert the EBF is to uninstall SQL Anywhere and re-install with the GA version. |
#6
| |||
| |||
|
|
Let me step back a second. You could prevent the scenario of having to re-install if you were to backup the files of the current SQL Anywhere install before applying the EBF. Meaning, make a copy of the C:\Program Files\SQL Anywhere 11 directory before applying the EBF. This gives you the ability to revert to the backed up version of the files if you want to revert. |
#7
| |||
| |||
|
|
Not sure about this, but would the SQL Anywhere .NET providers that are registered in the GAC also end up being reverted in this scenario, or would they still be the newer file versions? Josh Savill [Sybase] wrote: Let me step back a second. You could prevent the scenario of having to re-install if you were to backup the files of the current SQL Anywhere install before applying the EBF. Meaning, make a copy of the C:\Program Files\SQL Anywhere 11 directory before applying the EBF. This gives you the ability to revert to the backed up version of the files if you want to revert. |
#8
| |||
| |||
|
|
Let me step back a second. You could prevent the scenario of having to re-install if you were to backup the files of the current SQL Anywhere install before applying the EBF. Meaning, make a copy of the C:\Program Files\SQL Anywhere 11 directory before applying the EBF. This gives you the ability to revert to the backed up version of the files if you want to revert. |
![]() |
| Thread Tools | |
| Display Modes | |
| |