Sybase Business Intelligence Solutions - Database Management, Data Warehousing Software, Mobile Enterprise Applications and Messaging
Sybase Brand Color Bar
delete

Search for    in all of Sybase.com
view all search results right arrow
  blank
 
 
 
 
 
 
 
 
 
 

 
 
CLICK TO EXPAND NAVIGATION
CLICK TO EXPAND NAVIGATION
 
 
 
 
Support > Technical Documents > Document Types > Technote > SQL Anywhere Studio/Adaptive Server Anywhere Patch...

SQL Anywhere Studio/Adaptive Server Anywhere Patches and Upgrades FAQ

This document explains some of the terminology and recommended practices for upgrading SQL Anywhere Studio and Adaptive Server Anywhere.
 
RSS Feed
 
 
 

What is GA?

GA means Generally Available. It refers to a major release or maintenance release with no Express Bug Fixes (EBFs) applied. Any software installed from a CD or an install found on the Software Product Download Center;is considered GA.

What is a maintenance release/maintenance patch?

A maintenance release is a point release or incremental upgrade. For example, 10.0.1 is a maintenance release of SQL Anywhere (SA) 10. Maintenance releases include all bug fixes to date and may introduce subtle changes in behavior, which are documented in the New Features/Behavior Changes section of the manual. A maintenance patch updates the version stamp of all files, with the exception of a few libraries included for backwards compatibility.

Maintenance releases undergo our full suite of tests before release.

What is an EBF?

EBF stands for Express Bug Fix. It is intended to correct bugs that are considered serious enough to warrant an interim release. They are intended for use by customers affected by a specific problem for which there is no workaround.

Only files that have been modified are included in an EBF. Only these files will have an updated version stamp.

EBFs undergo a subset of testing only. Customers are discouraged from distributing these files with their application unless they verify the suitability of the software themselves.

What does it cost to upgrade?

Sybase iAnywhere periodically posts maintenance patches and EBFs to our website, which can be downloaded free of charge.

Upgrading to a new major release, for example from version 9 to version 10, requires a separate purchase or an upgrade subscription. You should contact your Sales Representative if you have one. Otherwise, call 1-800-8SYBASE (1-800-879-2273) and ask for Sales, or visit http://eshop.sybase.com/eshop.

Where can I download the free Updates and EBFs?

  1. Open the following URL in your web browser: http://www.sybase.com/downloads
  2. Choose Maintenance Releases and Bug Fixes (EBFs). If you already have a Sybase Web account, enter your Username and Password. If you don't have a Sybase Web account, click Sign Me Up! to create an account with MySybase.com.
  3. Click SQL Anywhere in the list of Product Families.
  4. If you don't see the download you are looking for, change the Time Frame from 6 months to All.
  5. Click the name of the update to download it, or click the document icon to the left of the link to view the ReadMe file.
32-bit Windows are in the section marked Windows x86 except for Windows CE. Windows Itanium and Windows x64 have their own section. The sections marked Windows 95, and Windows NT contain archived postings from versions 5, 6, 7, 8.0.1, and 9.0.0 when each platform had a separate installation.

Which builds are GA?

At the time of this writing, the following (Windows) GA builds are in wide distribution. NetWare releases have the same build numbers as Windows. However, Unix releases generally trail a few builds behind. Note that Engineering support for version 5 and 6 ended in June 2002.
  • 5.5.04.1867
  • 5.5.05.2509
  • 6.0.0.643
  • 6.0.1.1165
  • 6.0.2.2188
  • 6.0.2.2288
  • 6.0.3.2747
  • 6.0.4.3594
  • 7.0.0.313
  • 7.0.1.918
  • 7.0.2.1402
  • 7.0.3.2046
  • 7.0.4.2788
  • 8.0.0.2063
  • 8.0.0.2065
  • 8.0.1.2600
  • 8.0.2.3601
  • 9.0.0.1108
  • 9.0.1.1751
  • 9.0.2.2451
  • 10.0.0.2465
  • 10.0.1.3415
 

What changes have been made in the latest patch? The latest EBF?

Each EBF and Update on our website has an associated readme file that can be viewed prior to downloading. Click the document icon to the left of the download you are considering. This lists all the bug fixes and behavior changes since the previous maintenance release.

If you have reported a bug and are waiting for the fix, you should ask your technical support representative for the Engineering Case Number or "Change Request" (CR) number. You can then search the readme file for that number to see if the fix is included in a given patch or EBF.

I was told I need build 10.0.1.3604, but the closest build available on the web site is 10.0.1.3609. What should I do?

All EBFs and maintenance releases are cumulative. If you have been waiting for a given fix, you should download the latest EBF to take advantage of all the latest fixes. If you are running third-party software and the vendor states that only a specific build has been tested and is warranted, then the vendor should be able to provide that build.

If a bug is fixed in a 10.0.0 EBF, will the fix also be in the 10.0.1 maintenance release? The 10.0.1 GA release?

When a fix is made, it is included in all future versions of the software unless an underlying code change makes the fix irrelevant. When a new maintenance patch or major version is released, it includes all fixes to date. However, EBFs may continue to be released on a given version after the subsequent maintenance release has been rolled out. This means, for example, that a late EBF of 10.0.0 may have been released after the 10.0.1 patch. In this case, upon upgrading to 10.0.1, you would also need to apply the latest 10.0.1 EBF to avoid inconsistencies.

How can I tell what build I am running?

When you type dbengN -v or dbsrvN -v at a command prompt, where N is your major version, a popup window appears with the version of the server. Or, you can view the version number in the first line of the database server window when you start a server normally.

Can I apply an Update or EBF to my server without bringing it down?

No. If your server is running when you apply an Update or an EBF, any files that are in use will not be updated. This can cause erratic behavior, and any fixes to the files in use will not be applied. Similarly, any client program running on the machine being updated may cause ODBC drivers, OLE DB drivers, the .NET managed client, etc., not to be updated.

Be aware that some of our utilities such as "Interactive SQL" and "Sybase Central" also have "fast launch" capabilities loaded by default.  These applications appear in the Windows Task manager as dbisqlg.exe and scjview.exe respectively. If you are having an issue applying an EBF, be sure to close these applications by highlighting them in the Task Manager and clicking "End Task", to ensure that the libraries they have loaded into memory are updated correctly.

The files in my SA directory are of more than one version. Is this a problem?

If you have applied an EBF, you should expect to see some files with the GA version, and others with the EBF build. There will also be a few files from earlier releases, included for backwards compatibility. These may include  dbl50t.dll, dbl50to.dll, wod50t.dll, w150ent.dll, dblg??7.dll, and dblib7.dll.

If you have more than 2 builds of the current release in your SA directory, it is possible that an EBF has been incorrectly applied. If you are experiencing erratic behavior under these conditions, you may want to reinstall the software. In rare cases, a vendor will choose to distribute files from various builds. In this case, you should report any problems to your vendor since Sybase iAnywhere does not support mismatched installations.

If you believe your files may be mismatched:

  • In Windows you can right-click any executable or DLL, and choose Properties and Version to get the version of the file. If you are running Windows 2000, in Explorer you can go to the View menu, select Choose Columns, and include Module Version in the list of columns that appears in Explorer. This allows you to see the version of all files bearing a version stamp. If you are running Windows XP, in Explorer you can go to the View menu, select Choose Details, and include File Details in the list of columns that appear in Explorer.
  • In UNIX, you can run dbversion -i from the ASA directory to get a text file listing the version of all files in the current installation. Running dbversion filename gives you the version information for the specified filename.
There is a tool called dbtsinfo. When you type dbtsinfo -i at a command prompt, you are provided with client-side information, including relevant environment variables, the location of the SQL Anywhere installation, the version of each executable file (.exe and .dll files on Windows), and any path inconsistencies, such as a dbinfo.exe that is in your path ahead of the installed one. The dbtsinfo tool allows you to make sure that the version of the installed software is what you expect.

I am running SA 10.0.0. Do I need to apply the 10.0.1 maintenance patch before applying a 10.0.1 EBF?

Yes.

Is there an upgrade patch to take me from version 9 to version 10?

No. Major upgrades require a separate installation, and must be purchased separately (see What does it cost to upgrade?).

Can I run multiple versions of ASA on the same machine?

Yes. Each major version has a distinct default installation directory, and relevant libraries have distinct naming conventions. One exception to this is the command-line utilities (dbinit, dbvalid, dbunload, etc.). They retain the same name from version to version, and if you run them in a batch file or from a command prompt, the first version encountered on the path is executed. If you have multiple versions of Adaptive Server Anywhere/SQL Anywhere on your machine, you must pay attention to your system path when using utilities. Since setup adds the most recently installed version executable directory to the end of your system path, it's possible to install a new version of the software, and still inadvertently be running the previously installed version. For example, if an Adaptive Server Anywhere version 9executable directory is ahead of the version 10 executable directory in your path and you use the dbinit command, you will use the version 9 utility, and consequently create a version 9 database.

To avoid problems, you can fully qualify the paths to your utilities, change to the appropriate directory beforehand, or edit your path to be sure that the correct version always executes.

You may also want to avoid installing the compatibility DLLs or remove the files listed above (in the section "The files in my ASA directory are of more than one version. Is this a problem?") if they are not needed. Occasionally, the C version of Sybase Central (scview.exe) can pick up a compatibility DLL by mistake and try to initialize a database of the wrong version.

Must my client and server software have the same version and build?

Not necessarily. In general, clients and servers from version 6 to 9 are compatible at a connection level. However, if you open a tech support case because of connection problems, it is likely that you will be asked to bring both the client and server to the same version to simplify troubleshooting.

I am running ASA 9.0.0. Do I have to apply the 9.0.1 patch before applying 9.0.2?

No.

Do I need to apply EBF 10.0.1.3599 before applying EBF 10.0.1.3609?

No.

Should I upgrade?

Any upgrade requires testing before use in production or deployment. Even bug fixes can break applications if the applications expect the bugs to be there. In general, apply an EBF if you have a specific problem and you have reason to believe the EBF will fix it. Apply maintenance patches and/or major upgrades if you wish to take advantage of new features or if you are having stability problems, and you have the resources to test the new version. If you are just beginning development, you should probably start with the most recent release available.

Eventually support ends for a given major release or maintenance release, known as the "End of Life" (EOL) date.  See http://www.sybase.com/detail_list?id=9790 for all Sybase EOL notices.  To obtain bug fixes after the EOL date, you need to upgrade to a supported release. For this reason, it is a good idea to periodically test new versions to be sure your software still operates correctly with it. If you are using third-party software, you should contact your vendor regarding future plans or required upgrades.


 

DOCUMENT ATTRIBUTES
Last Revised: Mar 06, 2008
Product: SQL Anywhere
Technical Topics: Migration, SQL Anywhere, Bug Information, Install/Upgrade, Troubleshooting
  
Business or Technical: Technical
Content Id: 1019567
Infotype: Technote
 
 
 

 
© Copyright 2014, Sybase Inc. - v 7.6 Home / Contact Us / Help / Jobs / Legal / Privacy / Code of Ethics