远程Sybase数据库技术支持,联系手机:13811580958,QQ:289965371!

 

随着Sybase被完全整合到SAP下,Sybase原来的支持网站被SAP Support Portal取代。
只有购买了SAP服务的用户才能使用账号登录SAP Support Portal进行介质下载、补丁升级、报Incident等。
考虑到Sybase数据库的初学者或者没有购买原厂服务的Sybase客户情况,现提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息。
在SAP Support Portal网站或者google上搜索Targeted CR List for ASE,可以看到针对不同版本的CR(CR表示Change Request)简单描述信息列表。
需要注意的是:Targeted CR List for ASE列出的CR虽然绝大多数是BUG,但有一些是更改需求。
以下提供SAP ASE/IQ/RS/SDK/SQL Anywhere/PB等产品的BUG信息!

如有问题,请联系我!

QQ :289965371 点击这里给我发消息
Email:
不仅仅包括BUG的详细描述信息,还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程;有些BUG还提供了Workaround来临时解决该BUG带来问题。

 

CR:409529
CR Number:   409529
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3228 11 Nov 2005 Fixed
10.0.0 1884 11 Nov 2005 Fixed
Description
When tens of thousands of messages were directed to a QAnywhere JMS connector (bridge), the connector would have processed the messages very slowly; for example, depending on hardware, OS, and other software, the connector might have handled only one message every few seconds. This has been fixed, resulting in approximately a 10-fold improvement in QAnywhere JMS connector performance in sending QAnywhere messages into JMS. This fix requires a schema change to existing ASA consolidated databases. To implement this schema change, start the QAnywhere server dbmlsrv9 with the additional command line parameters:



-sl java { -Dianywhere.qa.db.upgradeDeliveryColumns=true }



During start-up, the QAnywhere server will change the schema. Note that the schema change should be considered irreversible. That is, it will not be possible to go back to an earlier version of the software. Once the schema change has completed, it is no longer necessary to start the QAnywhere server with the additional command line parameters.



CR:409599
CR Number:   409599
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Windows CE 2.11
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3229 25 Nov 2005 Fixed
9.0.1 2100 25 Nov 2005 Fixed
Description
When starting a database with a writefile that required recovering, the server could have crashed or failed with the error "Assertion failed: 102300 File associated with given page id is invalid or not open". This has now been fixed.

Note, the database is not corrupt and will recover correctly when started with a server with this fix.



CR:409734
CR Number:   409734
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2313 04 Jan 2006 Fixed
9.0.2 3295 04 Jan 2006 Fixed
Description
It was possible for a call to an external function or procedure to have failed without generating a SQL error. This was very unlikely and would only have occurred when all other database request tasks (as set by the -gn server switch) were internally blocked at the time the call was issued. In these cases, the request that issued the call was terminated by the server to prevent deadlock, but the SQLSTATE_THREAD_DEADLOCK error was not set for that connection. This has been fixed by setting SQLSTATE_THREAD_DEADLOCK when this failure arises. Additionally, under these circumstances, there was a very small window of opportunity where an external function call failure could cause the server to crash, most likely when being shutdown. This has also been fixed.



CR:409768
CR Number:   409768
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3207 14 Nov 2005 Fixed
Description
Support has now been added for 32-bit Itanium clients on HP-UX 11i v2 (HP-UX 11.23) IPF.



Note that starting with this build, HP-UX 11i IPF versions prior to HP-UX 11i v2 (HP-UX 11.23) are no longer supported.



For details on HP's HPUX 11i support, see:

http://www.hp.com/products1/unix/operating/oeurjuly05.html



CR:409772
CR Number:   409772
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1894 18 Nov 2005 Fixed
9.0.2 3225 18 Nov 2005 Fixed
9.0.1 2098 18 Nov 2005 Fixed
8.0.3 5325 18 Nov 2005 Fixed
Description
The server may have crashed when executing a query with a subselect, if the subselect caused an error when describing the result set. This has been fixed.



CR:409773
CR Number:   409773
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1890 14 Nov 2005 Fixed
9.0.2 3223 14 Nov 2005 Fixed
8.0.3 5323 14 Nov 2005 Fixed
Description
If an error occurred while executing a subquery, then there is a chance that the server would have left heap unfreed. This has now been fixed.



CR:409857
CR Number:   409857
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1892 15 Nov 2005 Fixed
9.0.2 3224 15 Nov 2005 Fixed
Description
The QAnywhere Agent incremental upload option (-iu) did not work well when the network connection was lost during an upload. If there was a large amount of message data to be uploaded, and the network connection was lost any time before all of the data was committed on the server, all of the data would have been re-uploaded in the next synchronization with the server. This has been fixed so that now QAnywhere synchronizes approximately the amount of data specified by the incremental upload option in the upload of each synchronization. This means that if the network connection is broken, the messages that were uploaded in successful synchronizations before the break do not have to be re-uploaded in the next synchronization. This option may also be set by a QAnywhere application using the message store property "ias_MaxUploadSize".



Note that at least 1 message will be in each upload (if there are messages queued) and the QAnywhere Agent does not split messages. Therefore, the incremental upload size is an approximation, and it will be a poor approximation if there is a message to be uploaded that is many times larger than the incremental upload size.



Example: The default incremental upload size is 256K, so if the average message size is 256 bytes and the maximum message size is not too large, then approximately 1000 messages will get transferred to the server per synchronization. The synchronizations will continue until all queued messages are transferred to the server, or until the connection is broken. The batches of messages that were successfully transferred to the server will not be transferred again.



CR:409861
CR Number:   409861
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3239 24 Nov 2005 Fixed
9.0.1 2109 24 Nov 2005 Fixed
8.0.3 5337 24 Nov 2005 Fixed
Description
The server could have failed with the error - "Assertion failed : 101412 Page Number on page does not match the page requested" or possibly crashed. This has been fixed.



CR:409958
CR Number:   409958
Product Name:   UltraLite
Product Component:   HotSync Conduit
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 5324 16 Nov 2005 Fixed
8.0.3 18 Nov 2005 Fixed
Description
When synchronizing with the Palm HotSync conduit, the HotSync connection could have been timed out if the UltraLite application (with record-based data store) required a long synchronization. The error: -309 - 'Memory error -- transaction rolled back' would then be signalled. This has been fixed. Now the worker thread handles all communication between HotSync and MobiLink, which prevents any device timeouts due to the long communication between HotSync and the MobiLink server.



In addition, the HotSync dialog is now properly updated - the "Exchange" arrows indicator is kept progressing while the connection is kept alive.



CR:410007
CR Number:   410007
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1891 18 Nov 2005 Fixed
9.0.2 3224 18 Nov 2005 Fixed
Description
The QAManagerBase.GetQueueDepth methods could have returned incorrect values for the QueueDepthFilter.ALL and QueueDepthFilter.OUTGOING arguments. These methods may not have counted outgoing messages that were in the process of being uploaded. If the upload then failed, the GetQueueDepth methods could have indicated fewer outgoing messages in the queue than were actually there. This has been fixed so that now outgoing messages are counted until they have been successfully transferred to the server.



CR:410109
CR Number:   410109
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3226 17 Nov 2005 Fixed
Description
The next M-Business Anywhere release, version 6.0, will begin supporting UTF8-encoded webpages on Windows platforms (PocketPC and XP Desktop). This will cause incompatibility problem with UltraLite for M-Business Anywhere (ULPod) 9.0.2, as ULPod assumes the webpage is encoded with the local codepage of the device (ISO encoding), when it converts strings passed from the PODS engine into Unicode strings, and then pass it to the UltraLite runtime. If the string is UTF8 encoded, the conversion will be wrong and the data will be lost.



A new feature has been implemented which will allow ULPod to tell how the string coming from the PODS engine is encoded, and use the correct conversion parameters to convert it to, or from, Unicode. This new feature is only enabled on Windows platforms, as M-Business Anywhere for Palm OS does not yet support UTF8.



CR:410139
CR Number:   410139
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1893 18 Nov 2005 Fixed
9.0.2 3225 18 Nov 2005 Fixed
Description
Attempting to send a message using QAnywhere Central while connected to a client message store did not work. Right-clicking the client message store tree icon, and selecting "Send Message", would have opened a dialog for authoring a message, but nothing would have happened when clicking the "Send" button to send the message. The dialog would not have gone away, and the message would not have been sent. This has now been fixed so that messages can be sent as normal.



CR:410251
CR Number:   410251
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1905 22 Nov 2005 Fixed
9.0.2 3226 22 Nov 2005 Fixed
1905 16 Dec 2005 Not a Bug
Description
If the MobiLink Client's DownloadReadSize extended option was specified, it would report an error like the following:



Invalid option "<value>"



where <value> was the value the option was set to, (i.e. -e drs <value>). The drs option was being treated as a boolean value, when in fact it is a numeric value. This has been corrected, and the error will no longer be reported



CR:410259
CR Number:   410259
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3221 18 Nov 2005 Fixed
Description
Microsoft has recently released Visual Studio 2005, which includes version 2.0 of the .NET Framework and the .NET Compact Framework. A new driver for SQL Anywhere support of ADO.NET 2.0 is now available, which consists of the following new files:



<install dir>\win32\VS8\iAnywhere.Data.AsaClient.dll

<install dir>\win32\VS8\iAnywhere.Data.AsaClient.dll.config

<install dir>\win32\VS8\policy.9.0.iAnywhere.Data.AsaClient.dll



<install dir>\ce\VS8\iAnywhere.Data.AsaClient.dll

<install dir>\ce\VS8\iAnywhere.Data.AsaClient.gac



The ADO.NET reference manual has also been updated to describe the new features of ADO.NET 2.0. The new documentation files are:



<install dir>\docs\dbpaen9.chm

<install dir>\docs\pdf_en\dbpaen9.pdf



Compact Framework version 2.0 programs cannot be built with assemblies built with version 1.0. The following new files are versions of the existing .NET assemblies built with Compact Framework version 2.0.



<install dir>\ce\VS8\iAnywhere.QAnywhere.Client.dll

<install dir>\ce\VS8\iAnywhere.QAnywhere.Client.gac

<install dir>\ce\VS8\iAnywhere.QAnywhere.Client.xml



<install dir>\UltraLite\UltraLite.NET\ce\VS8\iAnywhere.Data.UltraLite.dll

<install dir>\UltraLite\UltraLite.NET\ce\VS8\iAnywhere.Data.UltraLite.xml

<install dir>\UltraLite\UltraLite.NET\ce\VS8\iAnywhere.UltraLite.dll

<install dir>\UltraLite\UltraLite.NET\ce\VS8\iAnywhere.UltraLite.xml



CR:410263
CR Number:   410263
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3221 18 Nov 2005 Fixed
Description
Microsoft's Visual Studio integration has been extended with the release of the SQL Anywhere Explorer. The Explorer allows you to create connections to SQL Anywhere databases and browse the contents of tables and columns within the Visual Studio environment, in a manner similar to the Server Explorer. The accompanying toolbar can be used to launch Sybase Central and Interactive SQL from within Visual Studio. The Explorer supports browsing of the database structure and allows drag-and-drop operations to populate forms with controls. The SQL Anywhere Explorer supports both Visual Studio 2003 and Visual Studio 2005. The explorer is installed within Visual Studio by default when running the setup program. Both the explorer and the toolbar can be started by selecting them from the View menu in Visual Studio. There is no documentation yet for the SQL Anywhere Explorer, but Visual Studio users who are already familiar with the Server Explorer will find that it works in a very similar manner.



New files include



<install dir>\win32\iAnywhere.VSPackage.AsaClient.dll

<install dir>\win32\SetupVSPackage.exe

<install dir>\win32\1033\iAnywhere.VSPackage.AsaClientUI.dll



<install dir>\win32\VS8\iAnywhere.VSPackage.AsaClient.dll

<install dir>\win32\VS8\SetupVSPackage.exe

<install dir>\win32\VS8\1033\iAnywhere.VSPackage.AsaClientUI.dll



CR:414410
CR Number:   414410
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3226 21 Nov 2005 Fixed
9.0.2 23 Nov 2005 Not reproducible with latest version of the product available as of Resolution Date
9.0.1 2099 21 Nov 2005 Fixed
Description
Executing CREATE INDEX and DROP INDEX statements with Dynamic SQL could have caused databases to become corrupt. This has been fixed.



CR:414454
CR Number:   414454
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1898 21 Nov 2005 Fixed
9.0.2 3226 21 Nov 2005 Fixed
Description
Attempting to create and populate a table using SELECT ... INTO could have failed if the table owner of the new table was different than the current user. The table would have been created but not populated, and a "table not found" error would habe been returned. This has been fixed.



CR:414939
CR Number:   414939
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1906 25 Nov 2005 Fixed
9.0.2 3229 25 Nov 2005 Fixed
Description
It was possible, although very unlikely, for the server to crash if cache warming was enabled. This has now been fixed.



CR:415025
CR Number:   415025
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1920 29 Nov 2005 Fixed
9.0.2 3230 29 Nov 2005 Fixed
1920 16 Dec 2005 Not a Bug
Description
When the Dbmlsync Integration Component was used if a synchronization ended because of an error, or because the stop method was called, the EndDownload event may have been fired and the values passed to it for the number of rows deleted and upserted by the download would have been incorrect. This problem was transient and would usually not reproduce consistently. This has now been fixed.



CR:415161
CR Number:   415161
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1909 30 Nov 2005 Fixed
9.0.2 3231 30 Nov 2005 Fixed
9.0.1 2102 30 Nov 2005 Fixed
Description
Attempting to start the server on NetWare 6.5 with Service Pack 3 installed would have caused the message "In LibC, NXSemaInit reports attempt to reinitialize lock from DBSRV9.NLM" to be displayed, and then the server would have hung. This has been fixed. Note that other versions of NetWare are not affected. NetWare 6.5 with SP 4 installed does not experience the problem.



CR:415245
CR Number:   415245
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   4.3.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2022 07 Feb 2006 Fixed
9.0.2 3261 07 Feb 2006 Fixed
Description
On some systems running Windows XP, the graphical administration tools (i.e. Sybase Central, Iteractive SQL, the MobiLink Monitor and the Console utility) could have crashed on startup if the Windows desktop was configured to use the "Windows XP style" for the "Windows and buttons" setting. While it is still unclear as to the cause, a work-around for this problem is being provided.



After installing the EBF, create a file called "temp.reg", and paste the following lines into it:



Windows Registry Editor Version 5.00



[HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\Sybase Central\4.3\VMArgs]

"-Dswing.noxp"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\Adaptive Server Anywhere\9.0\DBISQL\VMArgs]

"-Dswing.noxp"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\Adaptive Server Anywhere\9.0\DBConsole\VMArgs]

"-Dswing.noxp"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\Sybase\Adaptive Server Anywhere\9.0\DBMLMon\VMArgs]

"-Dswing.noxp"="1"



and then run the file. If the "Fast Launcher" feature of Sybase Central or DBISQL has been enabled, log out and then log back in again for the changes to take effect.



While this procedure will prevent the programs from crashing, there will be some visual anomalies, such as an incorrect background color for the menu bar. These defects aside, the programs will function normally.



CR:415425
CR Number:   415425
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1929 02 Dec 2005 Fixed
9.0.2 3232 02 Dec 2005 Fixed
Description
There were problems with the Java administration tools when they were run on a secondary monitor. When the application window was run on the secondary monitor, context menus would have appeared on the primary monitor. For dbisql and dbconsole only, if the application window was last closed on a secondary monitor, it would always have appeared on the primary monitor, rather than on the secondary monitor, the next time they were run. These problems have now been fixed.



CR:415537
CR Number:   415537
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3235 05 Dec 2005 Fixed
9.0.2 05 Dec 2005 Presently Not Targeted For Any Future Release Of This Product
Description
Changes have been made to UltraLite.NET to allow it to integrate with Visual Studio 2005 (VS2005).

- In Smart Device and Windows projects, a reference to the iAnywhere.Data.UltraLite.dll is available in the "Add References" dialog box.

- The SyncProgressDialog can be added to a project by selecting Project, Add New Item.

- The ULConnectionParms controls are available, but must be added manually as described below due to a problem in Visual Studio 2005. If a Compact Framework DLL is added to the GAC before one of its controls is added to the VS2005 toolbox, the control will be permanently greyed out.



In the instructions below, <VS2005InstallDir> refers to the installation directory of Visual Studio 2005. For example, "C:\Program Files\Visual Studio 2005\"



To add the ULConnectionParms controls to the toolbox, do the following after the install:

1. Open the Visual Studio 2005 program.

2. Go to Tools, Choose Toolbox Items.

3. Note that there is already an iAnywhere.Data.UltraLite DLL with "Global Assembly Cache" as its Directory.

4. Add the following DLL by clicking Browse:

<VS2005InstallDir>\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\iAnywhere.Data.UltraLite.dll

5. Check ULConnectionParms for the two iAnywhere.Data.UltraLite DLLs from steps 3 and 4. Press OK.

6. Finally, in a command prompt (or the <Start>, Run dialog) , run

<VS2005InstallDir>\SDK\v2.0\Bin\gacutil.exe -i <VS2005InstallDir>\SmartDevices\SDK\CompactFramework\2.0\v2.0\WindowsCE\iAnywhere.Data.UltraLite.dll



CR:415756
CR Number:   415756
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1939 08 Dec 2005 Fixed
9.0.2 3236 08 Dec 2005 Fixed
Description
If the server was running a database without a transaction log, and a request was cancelled (or closed by the client) during a commit, the server could have started running at 100% CPU usage. If this happened, the server would also have hung on shutdown. This could also have happened when running with a transaction log, if a CREATE DBSPACE, ALTER DBSPACE or DROP DBSPACE was cancelled. This has now been fixed.



CR:415767
CR Number:   415767
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 5335 06 Dec 2005 Fixed
9.0.1 2105 06 Dec 2005 Fixed
9.0.2 3235 06 Dec 2005 Fixed
10.0.0 1937 06 Dec 2005 Fixed
Description
If the MobiLink client was running on a schedule, and had successfully synchronized, in very rare circumstances, it was possible for a failed synchronization to result in the section of transaction log that was scanned during the failed synchronization to not be scanned again in the next synchronization. This has now been fixed.



CR:415776
CR Number:   415776
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1938 08 Dec 2005 Fixed
9.0.2 3235 08 Dec 2005 Fixed
Description
On UNIX platforms, if the locale (environment variables LC_ALL, LC_MESSAGES, LC_TYPE, or LANG) was set to something invalid or unrecognized, the server, or one of the client tools, may have crashed on startup. In particular, all locale names ending with ".UTF-8" and all locale names ending with ".utf8" except for ko_KR.utf8, mk_MK.utf8, se_NO.utf8, tr_TR.utf8 and univ.utf8 were affected. This has now been fixed.



CR:415787
CR Number:   415787
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 19i26 06 Dec 2005 Fixed
9.0.2 3231 06 Dec 2005 Fixed
Description
The QAnywhere Agent Stop utility was missing a usage message. This has been fixed. The usage is displayed with the command "qastop -?".



CR:415859
CR Number:   415859
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3225 07 Dec 2005 Fixed
9.0.1 2098 07 Dec 2005 Fixed
Description
The server may have crashed while running the Java VM Garbage Collector. The crash would have occurred if some time before a very long array or string was allocated and during the allocation of pieces of that array or string the Garbage Collect ran more than once. This has been fixed.



CR:415862
CR Number:   415862
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3245 03 Jan 2006 Fixed
9.0.1 2117 03 Jan 2006 Fixed
Description
It was possible for a small amount of cache memory to not have been freed if the Java VM's garbage collector ran for a request that used the VM, and that request has been cancelled. This has now been fixed.



CR:415863
CR Number:   415863
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3243 19 Dec 2005 Fixed
9.0.1 2113 19 Dec 2005 Fixed
Description
The server may have crashed while running the Java Virtual Machine's garbage collector, if multiple connections run the garbage collector at the same time. This problem was more likly to have occurred on Unix systems and multi-cpu machines. This problem has been fixed.



CR:415877
CR Number:   415877
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3241 15 Dec 2005 Fixed
10.0.0 1964 15 Dec 2005 Fixed
3241 16 Dec 2005 Not a Bug
Description
If the authenticate_parameters method was being used as the only method of authentication for the MobiLink server, and users were automatically being added to the ml_user table during synchronization with the -zu+ command line option, and an error occurred when authenticate_parameters was called, or authenticate_parameters returned an authentication status indicating failure, then the MobiLink user would still have been added to the ml_user table. The MobiLink user is now removed from the ml_user table if the authenticate_parameters fails to authenticate the user.



CR:415893
CR Number:   415893
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3235 08 Dec 2005 Fixed
Description
On UNIX platforms, locale names ending with ".utf8", with the exception of ko_KR.utf8, mk_MK.utf8, se_NO.utf8, tr_TR.utf8 and univ.utf8, were not being correctly recognized as UTF-8 locales and were instead treated as ISO8859-1 locales. Locale names that instead ended with ".UTF-8" were recognized correctly. This has been fixed.



CR:415894
CR Number:   415894
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3235 08 Dec 2005 Fixed
Description
The DLLs in <install dir>\ultralite\UltraLite.NET\ce\x86 were version 9.0.2.3211 in all EBFs from build 3212 on, and hence were unusable. UltraLite.NET would have reported an error like "Unable to load dll ulnet9.0.2.3221" (where 3221 was the build of the EBF). Other CE platforms were not affected. These DLLs are now properly updated.



CR:415897
CR Number:   415897
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1938 08 Dec 2005 Fixed
9.0.2 3235 08 Dec 2005 Fixed
Description
On HP-UX, a non-threaded ODBC application using the ODBC driver could have hung, or crashed at start-up, if the application was linked against a third library that was in turn linked against the libpthread library. This has been fixed by changing the method for detecting the threading model.



CR:415899
CR Number:   415899
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Solaris
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1944 14 Dec 2005 Fixed
9.0.2 3239 14 Dec 2005 Fixed
Description
If there was an .odbc.ini file in the current directory, the Data Source utility would always have used it, regardless of any environment variable settings. This has been fixed.



CR:415979
CR Number:   415979
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1939 08 Dec 2005 Fixed
9.0.2 3236 08 Dec 2005 Fixed
9.0.1 2106 08 Dec 2005 Fixed
8.0.3 5336 08 Dec 2005 Fixed
8.0.2 4543 08 Dec 2005 Fixed
Description
When the server was using a database file that was located on another machine via Windows file sharing, or was located on the local machine but referenced using a UNC name (such as \\mymachine\myshare\mydb.db), it could have failed with one of the following errors (and possibly other assertion failures and fatal errors, including OS error 58):

I/O Fatal error: Unknown device error

Assertion failed: 201125 Read Error with OS error code: 64



The problem only occurs on certain machines with certain patches and/or hardware and/or drivers, the specifics of which have not been completely identified. The problem is related to scattered reads (aka "group reads") -- see the documentation to determine when the server may use scattered reads. The server now works around this OS problem by disabling scattered reads for files accessed by remote file sharing, or by UNC reference.



CR:415985
CR Number:   415985
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   7.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3242 16 Dec 2005 Fixed
8.0.3 5339 16 Dec 2005 Fixed
3242 16 Dec 2005 Not a Bug
Description
The documented order of events in the prepare_for_download transaction has been incorrect since the feature first appeared in 7.0.1. The correct order is:



------------------------------------------------------

prepare_for_download

------------------------------------------------------



modify_last_download_timestamp

prepare_for_download

if( modify_last_download_timestamp script is defined

or prepare_for_download script is defined ) {

COMMIT

}



Previous documentation had the order of the scripts reversed. The above order was chosen because the last-download timestamp (LDT) affects the content of the download. If the LDT is being modified, it must be modified before the download logic kicks in (ie. in the prepare_for_download script or in the download scripts).



CR:415999
CR Number:   415999
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1939 09 Dec 2005 Fixed
9.0.2 3241 09 Dec 2005 Fixed
Description
When there were tens of thousands of messages directed to a QAnywhere JMS connector (bridge), the connector would have processed these messages very slowly. For example, depending on your hardware, OS, and other software, the connector may have handled only one message every three seconds. This has been fixed, which should result in a roughly 10-fold improvement in QAnywhere JMS connector performance in sending QAnywhere messages into JMS. A schema change to the Oracle consolidated database is also required. To make this schema change, start the QAnywhere server dbmlsrv9 with the following additional command line parameters:



-sl java { -Dianywhere.qa.db.upgradeDeliveryColumns=true }



During start-up the QAnywhere server will change the schema. Note that the schema change should be considered irreversible. That is, it will not be possible to go back to an earlier version of the software. Once the schema change has completed, it is no longer necessary to start the QAnywhere server with the additional command line parameters.



CR:416088
CR Number:   416088
Product Name:   MobiLink
Product Component:   scripts
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1938 09 Dec 2005 Fixed
9.0.2 3236 09 Dec 2005 Fixed
9.0.1 2107 09 Dec 2005 Fixed
8.0.3 5337 09 Dec 2005 Fixed
Description
The MobiLink server's .Net scripting only supported version 1 .NET CLR. The MobiLink server would have failed to start if it attempted to load version 2 .NET CLR. The error reported in the log was: " [-10192] Could not create domain 'DefaultMobiLinkDNetScriptingDomain' ". The -clrVersion option could have been used to force the loading of a version 1 .NET CLR, if the fix for Engineering case 409377 had been included in the version of the software, (i.e. -sl dnet(-clrVersion=v1.0.3705 ... ). Now support has been added for .NET CLR version 2 as well.



CR:416223
CR Number:   416223
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1943 13 Dec 2005 Fixed
9.0.2 3239 13 Dec 2005 Fixed
Description
The literals TRUE and FALSE can be used in client-side transmission rules, however, the client-side rule processing code was treating these literals no differently than a message property reference. Hence, unless the message being evaluated happened to have a property TRUE or FALSE, TRUE or FALSE was being evaluated to NULL. That is, if there was a rule "myboolprop = TRUE", where myboolprop was a boolean typed message property, the rule would never evaluate to TRUE. The work-around is to use the literal 1 in place of TRUE and 0 in place of FALSE. This has now beeen fixed so that TRUE and FALSE are correctly recognized as boolean literals.



CR:416233
CR Number:   416233
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1943 13 Dec 2005 Fixed
9.0.2 3239 13 Dec 2005 Fixed
Description
The literals TRUE and FALSE can be used in server-side transmission rules, however, the server-side rule processing code was treating these literals as invalid literals. Hence, an error would have occurred while processing the rule indicating that TRUE or FALSE was not valid syntax. This has now beeen fixed so that TRUE and FALSE are correctly recognized as boolean literals.



CR:416332
CR Number:   416332
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1944 14 Dec 2005 Fixed
9.0.2 3241 14 Dec 2005 Fixed
Description
If a call was made to SQLColAttribute, SQLColAttributeW, SQLGetDescField or SQLGetDescFieldW ( and the deprecated ODBC 2.0 functions SQLColAttributes and SQLColAttributesW) with a NULL pointer value, no error would have been reported and the function would have returned SQL_SUCCESS. This is illustrated by the following code fragment:



SQLRETURN res = SQLColAttribute(hstmt, SQLUSMALLINT(i), SQL_DESC_COLUMN_TYPE, 0, 0, 0, 0);

switch ( res ) {

case SQL_SUCCESS:

case SQL_SUCCESS_WITH_INFO:

break;

default:

ODBC_error(henv,hdbc,hstmt);

break;

}



This problem has been fixed.



CR:416428
CR Number:   416428
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1946 15 Dec 2005 Fixed
9.0.2 3241 15 Dec 2005 Fixed
Description
When using a secure (i.e. https) web services client function, if the https connection to the remote host failed, the error message said simply "The secure connection to the remote host failed". This same error message would also have been returned if the certificate file could not be found or was corrupt. The error message now contains more information as to why the connection failed (eg. certificate file not found, certificate expired, server closed connection, handshake failed, etc.) library to the error message.



CR:416442
CR Number:   416442
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1971 14 Dec 2005 Fixed
9.0.2 3248 14 Dec 2005 Fixed
9.0.1 2120 14 Dec 2005 Fixed
Description
When running the 64 bit version of the driver, a call to SQLColAttributes or SQLColAttributesW would have returned invalid datatypes for SQL_COLUMN_TYPE. The results would have been either -1 or a large number such as 2147482128. A 32 bit pointer was being returned instead of a 64 bit pointer. This has been corrected.



CR:416461
CR Number:   416461
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3241 15 Dec 2005 Fixed
Description
The QAnywhere JMS connector was doing more processing of messaging incoming from JMS than was necessarily. Although this problem did not affect correctness, it could have affected performance. If an incoming message had many properties, the performance impact of the problem may have been noticable, with the larger the number of properties the larger the performance impact. This has now been fixed so that there is no longer a performance impact with respect to the number of properties in the incoming message.



CR:416564
CR Number:   416564
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Solaris
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1944 15 Dec 2005 Fixed
9.0.2 3239 15 Dec 2005 Fixed
Description
Two new commandline options have been added to the Data Source utility.



The ODBCINI and ODBCHOME environment variables are used to tell the ODBC driver and Data Source utility where to find the .odbc.ini file. If these environment variables were set to files that did not exist, a search for the .odbc.ini file was done in the user's home directory, and if not found, the path was searched. If a file was found, that file was used. If no file is found, one was created in the user's home directory. The -ns option now tells the Data Source utility not to search for the .odbc.ini file, but to use the existing environment variables to determine where the file should be. This is only useful when (a) the file specified by one or more of the environment variables does not exist, AND (b) a DSN is being created.



The -f option tells the Data Source utility to display the name of the .odbc.ini file that is being used. For example, "dbdsn -f -l" will display the name of the .odbc.ini file being used, and then list the DSNs in that file.



CR:416625
CR Number:   416625
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1973 12 Jan 2006 Fixed
9.0.2 3249 12 Jan 2006 Fixed
Description
The M-Business client would have crashed on File | Sync. If ulpod9.dll was removed from the client machine, the crash no longer occurred. When the client performs a sync, it sends a PODS_NOTIFY_PRESYNC event to the ULPod component. ULPod uses this chance to close the current UltraLite database connection, so that the same database can be opened later by ulconnect.exe for one-button-sync. The connection was closed by calling the Close() method on the Connection pods object, which in effect destroyed the Connection pods object. The has been fixed by adding an internal method to the Connection object that does the same thing as Close(), except it does not destroy the Connection object itself. The PODS_NOTIFY_PRESYNC event handler now calls this function instead of Close().



CR:416729
CR Number:   416729
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3246 05 Jan 2006 Fixed
9.0.1 2118 05 Jan 2006 Fixed
Description
When creating proxy tables using an ASAJDBC server class, some memory was not released from the Java heap. This has been fixed.



CR:416755
CR Number:   416755
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2297 24 Apr 2006 Fixed
9.0.2 3295 24 Apr 2006 Fixed
9.0.1 2157 24 Apr 2006 Fixed
Description
A complex query in a recursive union could have caused predicate inference problems in the optimizer. The reported symptom was an infinite loop. The exact conditions are difficult to characterize, but the minimum complexity that produces the problem involves a derived table in one of the branches of the recursive union that itself contains a subquery and a join that uses both an ON condition and a WHERE clause. The problem is now fixed.



CR:416772
CR Number:   416772
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1966 04 Jan 2006 Fixed
9.0.2 3246 04 Jan 2006 Fixed
8.0.3 5343 04 Jan 2006 Fixed
Description
The Unload utility may not have properly unloaded a remote database that was involved in synchronization, causing the reload file generated to contain syntax errors. This would have occurred if any of the options for synchronization users or synchronization subscriptions in the remote database had been completely dropped with:

ALTER SYNCHRONIZATION USER ml_username DELETE ALL OPTION

or

ALTER SYNCHRONIZATION SUBSCRIPTION

TO publication-name

[ FOR ml_username, ... ]

DELETE ALL OPTION

This problem has now been fixed.
Workaround Description
 Edit reload.sql, remove the trailing word OPTION in CREATE SYNCHRONIZATION statement



CR:416876
CR Number:   416876
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.1 2113 21 Dec 2005 Fixed
Description
Attempting to add ASA.Net Data objects ( AsaConnection, AsaCommand, AsaDataAdapter ) to the Visual Studio .NET toolbox would have resulted in an error dialog. This was due to some required .NET attributes being missing. This has been fixed by adding the attributes.



CR:416906
CR Number:   416906
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1968 09 Jan 2006 Fixed
9.0.2 3247 09 Jan 2006 Fixed
Description
Starting the MobiLink server with an invalid connection parameters would have caused the service to hang. The only way to remove the hung process was to use the Task Manager. A semaphore which signaled that initialization had completed was not being set in this particular error case. This has now been corrected.



CR:417129
CR Number:   417129
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Novell NetWare
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3245 03 Jan 2006 Fixed
Description
The Idle Timeout value was being ignored when the server was running on NetWare or Unix systems, other than 32-bit Linux. This would have caused idle connections to stay connected indefinitely. This has been fixed.



CR:417130
CR Number:   417130
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1953 03 Jan 2006 Fixed
9.0.2 3245 03 Jan 2006 Fixed
Description
The fix for Engineering Case 416089 exposed a bug in the iAnywhere JDBC driver which caused the Interactive SQL utility, and other applications, to crash when fetching result sets. Note that this problem only happened with 64-bit clients. This problem has been fixed.



CR:417145
CR Number:   417145
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1953 03 Jan 2006 Fixed
9.0.2 3245 03 Jan 2006 Fixed
Description
When tens of thousands of messages were directed to a QAnywhere JMS connector (bridge), the connector would have processed the messages very slowly; for example, depending on hardware, OS, and other software, the connector might have handled only one message every few seconds. This has been fixed, resulting in approximately a 10-fold improvement in QAnywhere JMS connector performance in sending QAnywhere messages into JMS. This fix requires a schema change to existing Microsoft SQL Server consolidated databases. To implement this schema change, start the QAnywhere server dbmlsrv9 with the additional command line parameters:



-sl java { -Dianywhere.qa.db.upgradeDeliveryColumns=true }



During start-up, the QAnywhere server will change the schema. Note that the schema change should be considered irreversible. That is, it will not be possible to go back to an earlier version of the software. Once the schema change has completed, it is no longer necessary to start the QAnywhere server with the additional command line parameters.



CR:417335
CR Number:   417335
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3257 30 Jan 2006 Fixed
Description
The Lithuanian translation of error -100, Server not found, was improved.



CR:417411
CR Number:   417411
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3246 03 Jan 2006 Fixed
9.0.1 2117 03 Jan 2006 Fixed
Description
When using a moving window aggregate specified with a RANGE (not ROWS) clause, an incorrect value of the aggregate was possible in rows following a row where the RANGE specification resulted in an empty window. This has now been fixed.



CR:417414
CR Number:   417414
Product Name:   UltraLite
Product Component:   UltraLite Schema Painter
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1966 05 Jan 2006 Fixed
9.0.2 3246 05 Jan 2006 Fixed
Description
Changing the MobiLink Script Version field in the "Generate Consolidated Database and MobiLink Scripts" dialog did not update the actual script version in the generated MobiLink scripts. This has been corrected.

Workaround: After generating scripts with a new MobiLink script version, use File|Save to save the schema. This will update the underlying meta information file. Then generate the scripts again, the new MobiLink script version field will now be used.



CR:417496
CR Number:   417496
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1966 05 Jan 2006 Fixed
9.0.2 3246 05 Jan 2006 Fixed
Description
Negative integer values exported to an Excel spreadsheet were exported incorrectly (the values were incorrect). DOUBLE, FLOAT, NUMERIC, and REAL values were not affected. The INTEGER record in the Excel BIF format is implicitly unsigned, but signed numbers were being written. This has been fixed by writing negative integers as NUMBER records instead.



CR:417500
CR Number:   417500
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1966 04 Jan 2006 Fixed
9.0.2 3246 04 Jan 2006 Fixed
8.0.3 5343 04 Jan 2006 Fixed
Description
When an array of parameters was used as input to an ODBC execute (for example, to insert more than one row with one SQLExecute), some of the parameter values could have be sent to the server incorrectly. It was possible for this to have occurred if CHARACTER or BINARY data was used, and the data size for a particular column was slightly larger in subsequent rows than previous rows within a single array of parameters (for example, if the first row in the array had a value of length 1000, and the second row in the array had a value of length 1050 for the same column). This has now been fixed so that the data is correctly sent to the server in this situation.



CR:417512
CR Number:   417512
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1966 04 Jan 2006 Fixed
9.0.2 3246 04 Jan 2006 Fixed
Description
An outer reference from a derived table to an alias should always give an error. If the derived table was a UNION, INTERSECT or EXCEPT, the server would have crashed instead. This has now been fixed.



CR:417598
CR Number:   417598
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1966 05 Jan 2006 Fixed
9.0.2 3247 05 Jan 2006 Fixed
Description
If a web service procedure received an HTTP status of 300, 303, 405, or 406 from the remote web server, the error status would have been displayed as "<status number> Unused". For example, if the error code 405 was returned from the web server, the error displayed would have been "405 Unused" instead of "405 Method Not Allowed". This has now been corrected by adding meaningful strings for these errors.



CR:417622
CR Number:   417622
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1966 06 Jan 2006 Fixed
9.0.2 3246 06 Jan 2006 Fixed
8.0.3 5343 06 Jan 2006 Fixed
Description
The OLE DB schema rowsets (e.g., INDEXES) are supported by stored procedures like sa_oledb_indexes (and others). They return result sets that allow for table names and other identifiers up to 128 characters in length. However, the input parameters to these stored procedrues only allowed for identifiers of up to 80 characters in length. This problem has been fixed so that parameters can now be up to 128 characters in length.



CR:417837
CR Number:   417837
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1974 12 Jan 2006 Fixed
9.0.2 3250 12 Jan 2006 Fixed
9.0.1 2121 12 Jan 2006 Fixed
8.0.3 5348 12 Jan 2006 Fixed
Description
When the ADO methods AddNew() or Update() were called, a memory leak would have occurred in the OLE DB provider. This problem has been fixed by appropriately freeing the allocated memory.



CR:417847
CR Number:   417847
Product Name:   SQL Anywhere
Product Component:   SNMP Extension Agent
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1971 09 Jan 2006 Fixed
9.0.2 3248 09 Jan 2006 Fixed
Description
The rdbmsSrvLimitedResourceTable.rdbmsSrvLimitedResourceID entry was returning an OID that was either invalid or referred to an unrelated entry in the MIB. This entry should return the OID of the limited resource in question (which in ASA's case, is either licenses or processors), but the OID that was returned referred to the asaSrvStat subtree rather than the asaSrvProp subtree. This has been fixed.



CR:417863
CR Number:   417863
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3251 16 Jan 2006 Fixed
Description
Calling a stored procedure that referenced a user-defined function in the search-condition of an IF statement could have crashed the server if the function called a procedure with OUTPUT or INOUT parameters defined as NUMERIC, and then called another procedure. This has been fixed. A workaround is to move the function call to an assignment statement preceding the IF.



CR:417977
CR Number:   417977
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 5350 18 Jan 2006 Fixed
Description
If an ASA process (such as dbremote, dbmlsync or dbmlsrv8) had been started as a service, it was possible for the process to hang when the service was shut down. This has been corrected so that these services now shutdown correctly.
Workaround Description
 downgrade to 5212 or lower.



CR:417998
CR Number:   417998
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1972 10 Jan 2006 Fixed
9.0.2 3249 10 Jan 2006 Fixed
Description
If the Interactive SQL utility, when launched from Sybase Central, was closed by clicking its close button after the server to which it was connected had already been stopped, Sybase Central could have crashed. This has now been fixed.



CR:418073
CR Number:   418073
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 3247 11 Jan 2006 Fixed
Description
If a new default SecurityManager for Java was installed in the database, and the class for it had not been installed in the database, all queries that included java columns would have failed with the error "Exception occured while loading Java SecurityManager". A query of the catalog table dbo.JAVAUSERSECURITY would also have failed for the same reason. This has now been fixed by adding, or updating, a new Java SecurityManager only if its class has already been installed. The above error may still occur if a user installs their own Java SecurityManager that cannot be loaded for some reason. In this case the user supplied SecurityManager would have to be deleted manually from JAVAUSERSECURITY and the server restarted.



CR:418255
CR Number:   418255
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3249 13 Jan 2006 Fixed
9.0.1 2121 13 Jan 2006 Fixed
Description
Using Dynamic SQL with the Palm OS Emulator (POSE), could have caused an exception during the execution of a CREATE INDEX statement. This was been corrected.



CR:418264
CR Number:   418264
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2013 30 Jan 2006 Fixed
9.0.2 3252 19 Jan 2006 Fixed
9.0.1 2124 19 Jan 2006 Fixed
Description
It was possible, although very unlikely, for the server to crash, or for connections to deadlock and appear to hang, in the presence of concurrent DDL statements. For one of these failures to have occurred, these concurrent statements would generally have to refer to the same database object (i.e.,table, column or stored procedure, etc), either directly or indirectly. A workaround is to serialize all DDL requests that references the same object. This has been fixed.



CR:418346
CR Number:   418346
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1983 18 Jan 2006 Fixed
9.0.2 3251 18 Jan 2006 Fixed
8.0.3 5350 18 Jan 2006 Fixed
Description
If two or more users with DBA authority granted the same column update permission to a user, these column permissions could then only have been revoked by revoking the table update permission. Any attempt to revoke the column update permission would have failed with the error "You do not have permission to revoke permissions on <table>". This has been fixed.



CR:418500
CR Number:   418500
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1979 17 Jan 2006 Fixed
9.0.2 3251 17 Jan 2006 Fixed
Description
If the Interactive SQL utility encountered an error while fetching the results of a statement, it could have left the "Execute" toolbar button disabled indefinitely, even after it reported the error to the user. This has been fixed.



The workaround for this problem is to interrupt the statement by clicking the "Stop" toolbar button.



CR:418909
CR Number:   418909
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1980 19 Jan 2006 Fixed
9.0.2 3252 19 Jan 2006 Fixed
9.0.2 30 Jan 2006 Not a Bug
Description
A new method has been added to the SyncParms pods object:

setMBAServerWithMoreParms( String host, String port, String url_suffix, String additional )



This new feature came from requests to specify a proxy server's host/port with ULPod one-button-synch. This new method augments the existing SyncParms.setMBAServer() method by adding the new string argument "additional".



The new "additional" argument gives user a chance to specify additional stream parms, such as proxy host, proxy port, or other security-related parameters.



CR:418929
CR Number:   418929
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2003 30 Jan 2006 Fixed
9.0.2 3253 20 Jan 2006 Fixed
Description
The QAnywhere .NET assembly for Compact Framework 2.0 was not strongly named. This has been fixed. It is now strongly named with the same public key as the QAnywhere .NET assembly for Compact Framework 1.0.



CR:419140
CR Number:   419140
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2002 30 Jan 2006 Fixed
9.0.2 3256 30 Jan 2006 Fixed
Description
When the MESSAGE statement was called with the TO CLIENT clause, the registered event handlers of AsaConnection.InfoMessage were not called. This problem has been fixed so that registered event handlers are now correctly called.



CR:419146
CR Number:   419146
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3254 23 Jan 2006 Fixed
Description
If a QAnywhere server operating against an ASE consolidated database, was terminated unexpectedly while a QAnywhere JMS connector was processing a QAnywhere message destined for JMS, it was possible that when the QAnywhere server was restarted the QAnywhere JMS connector would not be able to process any subsequent messages. The problem was with the message that was being processed during the crash. It can be worked around using the GUI administration tool QAnywhere Central. Using QAnywhere Central, determine which message is causing the problem (The address of the message will be the connector address, and the state of the message will be "receiving"), select and export the message, cancel the message, wait for the message to be deleted, then use the exported message to create a new message containing the same content, headers and address. There is a simpler work-around involving the use of the tool dbisql. This work-around involves deleting the record indicating the "receiving" state for the message, but this should only be attempted with the assistance of Technical Support. This problem has now been fixed so that neither of these the work-arounds are needed.



Note that this problem does affect QAnywhere server running against ASA, Oracle, DB@ or Microsoft SQL Server.



CR:419165
CR Number:   419165
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3255 26 Jan 2006 Fixed
Description
The documentation indicates that server-side transmission rule times could be like '1:00am'. In fact, the default time format is hh:mm:ss, where hh uses the 24 hour clock. Hence, using an AM or PM suffix is not valid, but the error reporting and detection did not always report an error. If, for example, the time '1:00:00 PM' was used, the PM portion of the time was ignored, and the time was treated as 1:00:00 AM. This has been corrected so that such a time is now reported as an error.



The documentation also did not indicate indicated how a user can change the default time and date formats used by the QAnywhere server. To set the time format, set the property ianywhere.qa.server.scheduleTimeFormat to a value describing the time format. This property can be set in several different ways. If the server uses a configuration file (using the -m <file-name> MobiLink command line option), then a line can be added to the file as follows:



ianywhere.qa.server.scheduleTimeFormat = hh:mm:ss a



This property can also be set using the GUI tool QAnywhere Central, by clicking on the server properties tab and adding the property. The time format values are identical to those used in Java by the java.text.SimpleDateFormat class (the default time format is HH:mm:ss):



Letter Time Component

a Am/pm marker (AM/PM)

H Hour in day (0-23)

k Hour in day (1-24)

K Hour in am/pm (0-11)

h Hour in am/pm (1-12)

m Minute in hour (0-59)

s Second in minute (0-59)



Time Format Example Time

HH:mm:ss z 12:08:56

h:mm a 12:08 PM

K:mm a 0:08 PM

hh:mm aaa 12:08 PM

HH:mm:ss 12:08:56

HHmmss 120856



To set the date format, set the property ianywhere.qa.server.scheduleDateFormat to a value describing the date format. This property can be set in several different ways. If the server uses a configuration file (using the -m <file-name> MobiLink command line option), then a line can be added to the file as follows:



ianywhere.qa.server.scheduleDateFormat = yy:MM:dd



This property can also be set using the GUI tool QAnywhere Central, by clicking on the server properties tab and adding the property. The date format values are identical to those used in Java by the java.text.SimpleDateFormat



class (the default date format is yyyy-MM-dd):



Letter Date or Time Component

y Year

M Month in year (ie July, Jul or 07)

d Day in month



Date Format Example Date

yyyy.MM.dd 2001.07.04

yyyy.MMMMM.dd 02001.July.04

d MMM yyyy 4 Jul 2001

yyMMdd 010704



Note that the software does not need to be upgraded your to use the two date and time formatting properties.



CR:419284
CR Number:   419284
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1994 24 Jan 2006 Fixed
9.0.2 3255 24 Jan 2006 Fixed
Description
The iAnywhere JDBC Driver can be used to fetch blobs from a server, but if the underlying ODBC driver returned an unexpected error code when fetching the blob, then the JDBC driver may have crashed or run out of memory. Note that this problem was more likely to occur with ODBC drivers for servers other than SA. This has been fixed by having the JDBC driver throw a SQL Exception when the ODBC driver returns an unexpected error.



CR:419347
CR Number:   419347
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1996 25 Jan 2006 Fixed
9.0.2 3255 25 Jan 2006 Fixed
9.0.1 2127 25 Jan 2006 Fixed
10.0.0 30 Jan 2006 Not a Bug
Description
Using Dynamic SQL could have caused an exception during the execution of a SQL query. For this to occur, the SELECT statement must have contained an ORDER BY clause, and no index could be used to achieve the ordering. The statement must also have contained a GROUP BY clause whose items all occur in at the start of the ORDER BY clause, in some order, and must also contains a HAVING clause. This problem has now been fixed.



CR:419399
CR Number:   419399
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3254 25 Jan 2006 Fixed
Description
There have been circumstances where the QAnywhere JMS connector would receive a RuntimeException from either the JDBC driver or the 3rd party JMS driver. The default behaviour of the JMS connector when it received this kind of exception was to terminate execution. Such exceptions have often been found to be transient or spurious, and that retrying the same operations often results in the problem going away. Because of this experience, the behaviour of the QAnywhere JMS connector has been changed to backoff and retry when receiving this exception. The backoff is exponential, increasing in time with each consecutive exception up to one minute (this default maximum can be configured using the connector property ianywhere.connector.pollingFrequency value in milliseconds).



Note that RuntimeExceptions are logged to the QAnywhere Server (MobiLink) console and log file. Typically, RuntimeExceptions represent bugs, and probably indicate that you need a fix for the component issuing the exception, for example, the JDBC driver or JMS driver.



CR:419414
CR Number:   419414
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1999 26 Jan 2006 Fixed
9.0.2 3255 26 Jan 2006 Fixed
9.0.1 2127 26 Jan 2006 Fixed
Description
If a nested transaction was started with a BEGIN TRANSACTION statement, and two or more COMMITs were done one after the other to commit the nested transaction, the transaction may not have been committed. This has been fixed so that the transaction is now committed.



CR:419563
CR Number:   419563
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1991 26 Jan 2006 Fixed
9.0.2 3256 26 Jan 2006 Fixed
9.0.2 01 Feb 2006 Fixed
Description
UltraLite now supports Windows Mobile 5.0 devices. If using Embedded Visual C++ 3.0 or 4.0, the existing runtimes can continue to be useed. However, new runtimes (installed under ultralite\ce\arm.50) are required when using Visual Studio 2005 to build an application.



Visual Studio 2005 compilers define the wchar_t type as the internal __wchar_t type, instead of unsigned short*, which is what was used in the previous CE compilers. Because of this, apps compiled with Visual Studio 2005 would trigger unresolved external errors when linked against the UltraLite runtime. As a work-around, an application can cast all wchar_t, ul_wchar, and TCHAR variables passed into the runtime to unsigned short* explicitly. Another work-around is to use the -Zc:wchar_t- compiler option, which will cause wchar_t to be defined as unsigned short *, though, this won't work if the app links against other libraries such as the MFC library that are compiled with Visual Studio 2005 without this option.



Note that the Visual Studio 2005 compatible runtimes do not support sync encryption on 9.0.2.



CR:419668
CR Number:   419668
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Solaris 2.9
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2023 30 Jan 2006 Fixed
9.0.2 3261 08 Feb 2006 Fixed
Description
In the presence of many undelivered messages in the QAnywhere server, message synchronization performance would have declined. This was largely due to poor performance of a number of three SQL operations being executed against the server message store. Two of these operations, that involved message delivery confirmation and message download preparation, were re-structured to dramatically improve performance. Applying the fix to the server is all that is required to get these benefits. The final SQL operation requires a schema change, and only is available for an Oracle consolidated database. These schema changes can be made in two different ways. The first is to run the QAnywhere server with the additional command arguments -sl java { -Dianywhere.qa.db.upgradeDeliveryColumns=true } successfully at least once. The second is to execute the following SQL against your Oracle database using SQL*Plus:



create global temporary table ml_qa_clients

( client varchar(255) not null ) on commit preserve rows

/

create index ml_qa_clients_index on ml_qa_clients( client )

/

drop index ml_qa_delivery_client

/

create index ml_qa_delivery_client on ml_qa_delivery(client,syncstatus,maxstatus,status)

/

create or replace trigger ml_qa_delivery_before_trigger

before insert on ml_qa_delivery

for each row

begin

insert into ml_qa_clients (client) values( :new.client );

select substr(:new.address,2,instr(:new.address,'\')-2) into :new.clientaddress from dual;

select :new.status into :new.maxstatus from dual;

begin

select seqno, priority into :new.seqno, :new.priority

from ml_qa_repository where msgid = :new.msgid;

exception

when NO_DATA_FOUND then

select 0, 4 into :new.seqno, :new.priority from dual;

end;

end;

/



Note that this must be executed under the same database user initially used to create the MobiLink QAnywhere schema.



CR:419708
CR Number:   419708
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2021 07 Feb 2006 Fixed
9.0.2 3261 07 Feb 2006 Fixed
8.0.3 5359 07 Feb 2006 Fixed
Description
Subqueries with an ANY or ALL condition, that also contained both a DISTINCT and a TOP n clause (where n > 1), could have returned incorrect results. The server was incorrectly eliminating the DISTINCT, which meant that some rows could have been missed from the subquery. This has now been fixed.



CR:419782
CR Number:   419782
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3261 07 Feb 2006 Fixed
8.0.3 5359 08 Feb 2006 Fixed
Description
If a query contained an alias in the SELECT list, with the aliased expression containing an IF or CASE expression, where the predicate in the IF or CASE contained an EXISTS, ANY, or ALL predicate, and the aliased expression was used as an outer reference in another subquery, and the execution plan contained a materializing operator such as Hash Join, then incorrect results could have been returned for the IF/CASE expression and the referencing subquery.



The following query demonstrates the problem using the demo database:



select T2.dept_id,

( if exists ( select 1 from sys.dummy T4 where T2.dept_head_id <> -1 ) then 1 endif ) as S2,

( select 1 from sys.dummy T5 where S2 > 0 ) as S3

from

rowgenerator T0 with ( no index )

join department as T2 with ( no index )

on T0.row_num*100 = T2.dept_id



This has been fixed.



CR:419802
CR Number:   419802
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2011 31 Jan 2006 Fixed
9.0.2 3258 31 Jan 2006 Fixed
9.0.1 2129 31 Jan 2006 Fixed
Description
Attempting to use Sybase Central to create a proxy table for a Microsoft Excel or Access database would have failed with the following error:



[Sybase][ODBC Driver][Adaptive Server Anywhere]Server '<server-name>': [Microsoft][ODBC Driver Manager] Driver does not support this function (-660)



The Sybase Central plug-in was calling the ODBC function SQLPrimaryKeys() to determine which columns in the table were part of the primary key. Some ODBC drivers (such as Access and Excel) do not support this call. Now, if the remote server is of type

"generic", any failures when this call is made are ignored, and no primary key information is displayed.



CR:419832
CR Number:   419832
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2009 31 Jan 2006 Fixed
9.0.2 2427 31 Jan 2006 Fixed
Description
The "Browse" buttons associated with the "ODBC Data Source file" and the "Database file" fields in the "Connect" dialog would have done nothing if "C:\" (or any other root folder) had first been entered in the field. This has been fixed.



Note, this problem also affected the Console utility, and the plug-in for Sybase Central.



CR:419848
CR Number:   419848
Product Name:   UltraLite
Product Component:   Utilities
Status:   Open
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3259 02 Feb 2006 Fixed
3259
Description
The UltraLite Interactive SQL utility should be able to connect to databases created on the desktop, Windows CE (i.e. Unicode databases) and Palm OS (either in the record store or on the VFS). However, it was failing to open an UltraLite database created by a Palm application on the VFS, returning a database not found error (sqlcode -954). This has been fixed.



Note, when attempting to connect to an UltraLite database created by a Palm OS application, and stored on the VFS, remember to include "palm_fs=vfs" in the connection string. This tells UltraLite that this Palm database uses the file store instead of the record store.



CR:419897
CR Number:   419897
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2011 31 Jan 2006 Fixed
9.0.2 3258 31 Jan 2006 Fixed
9.0.1 2129 31 Jan 2006 Fixed
Description
When the server was running on NetWare, casting a string representing an overly-large number to a double or float could have returned the value '1.#INF', rather than setting error -158 (Value ... out of range for destination). This has been corrected.



CR:419923
CR Number:   419923
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2023 09 Feb 2006 Fixed
Description
If a parameter to a procedure or function had the same name as a connection global variable, and the procedure was called from within a batch that passed the global variable as an argument, the value of the parameter would have been incorrectly set to NULL. This has now been fixed. A workaround is to change the parameter or global variable names to avoid duplication.



CR:420042
CR Number:   420042
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2028 13 Feb 2006 Fixed
9.0.2 3263 13 Feb 2006 Fixed
8.0.3 5361 13 Feb 2006 Fixed
Description
An INSERT, UPDATE or DELETE statement may have incorrectly returned the error "Invalid statement", if the execution of the statement caused a trigger to fire, or an RI action was executed, and a subsequent statement then failed with a deadlock error. This has been fixed.



CR:420137
CR Number:   420137
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2016 03 Feb 2006 Fixed
9.0.2 3259 03 Feb 2006 Fixed
9.0.1 2130 03 Feb 2006 Fixed
8.0.3 5357 03 Feb 2006 Fixed
Description
On Unix systems, if an application autostarted a server, used ASA's embedded SQL function db_start_engine(), or used the Spawn utility to start a server, and the application was terminated abnormally by SIGINT, SIGQUIT, SIGTERM or some other unhandled signal (SEGV, etc), the server that had been started would shutdown unexpectedly, although cleanly. This has been fixed.



A work-around is to specify -ud on the server command line, although this has the side effect that the controlling application (e.g. dbspawn) will return/continue immediately before the server has fully started all of its databases, etc.



CR:420171
CR Number:   420171
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 5364 28 Feb 2006 Fixed
9.0.2 3266 21 Feb 2006 Fixed
9.0.1 2138 21 Feb 2006 Fixed
Description
A failed UPDATE statement, for example due to a deadlock error, could have resulted in a corrupted index. It is likely that only databases involved in replication would have been affected by this problem. A database validation with 'full check' would have detected that the index had missing values. This has been fixed, but dropping and re-creating an index in such a state will fix the corruption.



CR:420179
CR Number:   420179
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2024 09 Feb 2006 Fixed
9.0.2 3262 09 Feb 2006 Fixed
9.0.1 2133 09 Feb 2006 Fixed
2024 28 Nov 2007 Not a Bug
Description
Dynamic SQL could have produced incorrect results for comparisons, when the following conditions were true:

- a nullable column was being compared

- the nullable column occurred first in an index or foreign key

- the expression being compared was of a different type than the collumn and could be casted to the type of the column

- the index or foreign key could have been used as part of the plan to execute the query

This has now been corrected.



CR:420382
CR Number:   420382
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3260 07 Feb 2006 Fixed
9.0.1 2144 10 Mar 2006 Fixed
9.0.0 1411 10 Mar 2006 Fixed
Description
There are situations where passwords used in Sybase Central, running on Unix systems, could be at risk of being discovered. Selecting the password field text and pasting it into another field, would have allowed the clear text password to be viewed. This has been fixed.



A full description of this problem is available at http://www.sybase.com/detail?id=1040117



CR:420462
CR Number:   420462
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2022 07 Feb 2006 Fixed
9.0.2 3261 07 Feb 2006 Fixed
Description
If a zero-length file was opened, the status bar text would continue to read "Loading <file name>", and a progress bar control would remain. This has been fixed so that the status text is cleared, and the progress bar is not present. Behavior for files with nonzero lengths is unchanged.



CR:420496
CR Number:   420496
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Open
OS:   Generic
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 5363 17 Feb 2006 Fixed
9.0.2 3265 20 Feb 2006 Fixed
5363
Description
On Palm T|X devices running the latest Palm OS v5.4.9, the OS can leave the record busy bit turned on when the device is reset. This could have caused UltraLite applications to fail on startup in the call ULAppLaunch(). A work around has now been implemented.



CR:420588
CR Number:   420588
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2032 17 Feb 2006 Fixed
9.0.2 3266 17 Feb 2006 Fixed
Description
The Data Source utility now supports encrypting the password when creating ODBC data sources. When the -pe command line option is specified, and a PWD entry is provided, the password in the PWD entry is encrypted and replaced by an ENP entry in the resulting data source.



CR:420633
CR Number:   420633
Product Name:   UltraLite
Product Component:   Analyser Java Classes
Status:   Open
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3263 09 Feb 2006 Fixed
9.0.1 2134 09 Feb 2006 Fixed
3263
Description
The Java code generated by the UltraLite Generator, could have contained a compilation error when a query contained both DISTINCT and ORDER BY clauses, and where a temporary table was required to satisfy the query. A extra semicolon was being generated following a RETURN statement. This \was then detected as a compilation error by some Java compilers. This has been fixed by eliminating the extra semicolon.





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具:ReadASADB。
此工具支持ASA v5.0,v6.0,v7.0,v8.0,v9.0,v10.0,v11.0,v12.0等版本。
恢复Sybase SQL Anywhere的工具在国内应该算首创。

ReadASADB功能
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具

  1. 适用于所有的SQL Anywhere版本    包括:5.x,6.x,7.x,8.x,9.x,10.x,11.x,12.x
  2. 适用于所有的UltraLite版本
  3. 能够恢复出来表结构和数据
  4. 能够恢复自定义数据类型
  5. 能够恢复存储过程等对象的语法
  6. 能够导出到目标数据库
  7. 能够导出到SQL文件并生成导入脚本
  8. 支持多种字符集  包括:cp850、cp936、gb18030、utf8等
  9. 能够恢复未加密或者简单加密类型的数据
  10. 简单易用
  11. 限制:不支持AES加密的数据文件
请参考:研发成功了从Sybase SQL Anywhere的DB文件上恢复数据的工具
            SQL Anywhere数据库非常规恢复工具ReadASADB使用介绍

ReadASADB适用场景

各种误操作:

  1. 误截断表(truncate table)
  2. 误删除表(drop table)
  3. 错误的where条件误删数据
  4. 误删除db或log文件
  5. 误删除表中的字段

本工具的应用场景:

1.因为物理磁盘故障、操作系统、系统软件方面或者掉电等等原因导致的Sybase SQL Anywhere数据库无法打开的情况;
2.误操作,包括truncate table,drop table,不正确的where条件导致的误删除等;
Sybase SQL Anywhere无法打开时,比较常见的错误是:Assertion failed。
如:
1、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Checkpoint log: invalid bitmap page -- transaction rolled back
2、Internal database error *** ERROR *** Assertion failed:201819 (8.0.1.2600) Page number on page does not match page requested -- transaction rolled back
3、Internal database error *** ERROR *** Assertion failed:200502 (9.0.2.2451) Checksum failure on page 23 -- transaction rolled back
4、File is shorter than expected
5、Internal database error *** ERROR *** Assertion failed: 201116 Invalid free list index page found while processing checkpoint log -- transaction rolled back
6、*** ERROR *** Assertion failed: 51901 Page for requested record not a table page or record not present on page等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------