远程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:318952
CR Number:   318952
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1056 12 May 2003 Fixed
Description
If you chose a table, selected the Data tab and then right-clicked Table to choose "View Data in Interactive SQL" from the context menu, nothing would have happened. This has now been fixed.



CR:318954
CR Number:   318954
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jul 2003 Workaround
Description
Make sure you installed the Windows CE components when you installed ASA 8.0.



Launch the SimpleCE project by clicking on the "Samples\ASA\ADO.NET\SimpleCE\Simple.sln" or whatever is appropriate for your PC. Accept the Visual Studio conversion message if you see one.



If you see the message "The .net assembly 'iAnywhere.Data.Asaclient' could not be found" then perform step 1, otherwise go to step 2.



Step 1. Right-click on "Simple" in the Solution Explorer pane (in the top right part of the Visual Studio display). Select "Properties".



In the Simple Property Pages window, select "References Path" (as shown below). If you are running Visual Studio.NET, change the "C:\Program Files\Sybase\SQL Anywhere 8\ce\" to your ASA 8.0.2 "ce" directory. If you are running .NET.2003, point to the "ce\VSNet2003" folder instead of "ce" since there is an iAnywhere.Data.AsaClient.dll there for Visual Studio .Net 2003.



Get rid of any other paths (such as "E:\src80\db\...") that you might see since they do not apply.



Step 2. Try building the application.



If you see a "Resource transformation" error message about Form1.resx, then perform step 3, otherwise you should have an error-free build.



Step 3. Double-click on Form1.cs in the Solution Explorer window to open the form designer (or click on Form1.cs and select the "View Designer" button in the Solution Explorer window). Move the button on the form and this will cause a new and correct resx file to be generated. Try rebuilding now and there should be no more error messages.
Workaround Description
 None



CR:318985
CR Number:   318985
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1080 12 May 2003 Fixed
8.0.3 4686 12 May 2003 Fixed
8.0.2 4266 12 May 2003 Fixed
8.0.1 3118 21 May 2003 Fixed
Description
Database corruption, revealed by assertion messages, could have been possible when executing a "LOAD TABLE" statement that failed (eg. due to a duplicate primary key). This is now fixed.



CR:319085
CR Number:   319085
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4663 12 May 2003 Fixed
8.0.2 4254 12 May 2003 Fixed
7.0.4 3451 12 May 2003 Fixed
7.0.3 2150 13 May 2003 Fixed
7.0.2 1611 13 May 2003 Fixed
Description
If the first query referencing a table after a database was started contained an error in the WHERE clause, subsequent queries would return the error:

Cannot find an index for field '<column name>'.

Every field must have at least one index. Current IndexCount = 0.

The database would have needed to be restarted to correct the problem. This has been fixed.



CR:319109
CR Number:   319109
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1070 03 Jun 2003 Fixed
8.0.3 4675 03 Jun 2003 Fixed
Description
Running setup in Record mode would have listed Documentation as an option, but if selected the external install would not have been launched correctly. The external installs were not intended to be available when recording an installation. An external install must be run standalone to generate a silent install for that option. External installs are no longer an option when recording an install.



CR:319111
CR Number:   319111
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.4 3451 12 May 2003 Fixed
Description
Dbmlsync would sometimes have failed to identify ALTER TABLE operations that applied to tables being synchronized. This prevented dbmlsync from generating the error message "Table 'tablename' has been altered outside of synchronization.." when a table with operations that needed to be uploaded was altered. This has now been fixed and the error message will now be generated when needed.



CR:319165
CR Number:   319165
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4664 13 May 2003 Fixed
8.0.2 4254 13 May 2003 Fixed
8.0.1 3115 13 May 2003 Fixed
Description
Updating VARBINARY and LONG BINARY values in the Results panel of dbisql, or the Data tab of the Sybase Central Plug-in, was not being allowed. This has been fixed. As well the Table Editor is now more lenient of what can be typed in for BINARY, VAR BINARY and LONG BINARY values. The usual syntax of "0x" followed by pairs of hex values is still supported. However, anything else will now be sent to the server as a string which the server will convert into a BINARY value.



CR:319206
CR Number:   319206
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1060 20 May 2003 Fixed
Description
All the columns in SYS.SYSSYNC and SYS.SYSREMOTEOPTION, and their views, wre selectable by any user. This may have exposed sensitive data in the following :

SYS.SYSSYNC.server_connect

SYS.SYSSYNC."option"

SYS.SYSREMOTEOPTION."setting"

This has been fixed by revoking SELECT permission on the SYSSYNC and SYSREMOTEOPTION tables from SYS and only DBA is now granted SELECT permission. The following new views have been created for the PUBLIC group:

SYS.SYSSYNC2

SYS.SYSREMOTEOPTION2

These views select the same columns of the original table, except they hide sensitive columns dynamically based on whether the user is a DBA or not. When the value is hidden, a string equal '<hidden>' is returned.



The following views are also updated to perform the same dynamic hiding on the sensitive columns.

SYSSYNCS

SYSSYNCDEFINITIONS

SYSSYNCTEMPLATES

SYSSYNCSITES

SYSSYNCUSERS

SYSSYNCPUBLICATIONDEFAULTS

SYSSYNCSUBSCRIPTIONS

SYSREMOTEOPTIONS



The Sybase Central plugin has also been updated to use the views instead of selecting from the tables directly.



CR:319250
CR Number:   319250
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)
8.0.3 4665 20 May 2003 Fixed
8.0.2 4255 20 May 2003 Fixed
8.0.1 3115 20 May 2003 Fixed
Description
Calling the system function "property( 'PlatformVer' )" would have incorrectly returned 'Windows .Net build ...' on Windows 2003. Now it returns 'Windows 2003 build ...'.



CR:319257
CR Number:   319257
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4665 20 May 2003 Fixed
8.0.2 4255 20 May 2003 Fixed
Description
Starting the MobiLink Monitor with command-line option /? would have shown an error opening /? as a file, instead of showing the usage. This has been fixed.



CR:319280
CR Number:   319280
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)
9.0.0 1025 20 May 2003 Fixed
Description
The setting for the option Optimization_goal, was incorrectly being changed for some queries, from FIRST ROW to ALL ROWS. This has been corrected



CR:319282
CR Number:   319282
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.4 3451 20 May 2003 Fixed
Description
Calling the system function "property( 'platform' )", incorrectly returned 'Windows 2000' on Windows XP and Windows 2003. Now it returns 'Windows XP' and 'Windows 2003' respectively.



CR:319295
CR Number:   319295
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)
9.0.0 1025 20 May 2003 Fixed
Description
Queries with "= ANY (subquery)" or "<> ALL (subquery)" predicates may have returned incorrect results, if:

- the ANY or ALL subquery contained a table T1 that was flattened;

- there existed at least three tables, including T1, joining on the same column, (ie "T1.X = T2.X and T2.X = T3.X and T3.X = T1.X" )



This is now fixed.



CR:319381
CR Number:   319381
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1061 20 May 2003 Fixed
Description
If the command line switch -b (trim blank padding of strings) was used and a download_delete_cursor contained only the primary key columns in the "SELECT ..." statement, the MobiLink synchronization server could have crashed. This problem is now fixed.



CR:319383
CR Number:   319383
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)
9.0.0 1025 20 May 2003 Fixed
Description
When using the Index Consultant to analyze workloads containing statements with updates over multiple columns on a given table, the updates would have shown up as unanalyzable and would not have been included when optimizing the indexes. This has now been fixed.



CR:319387
CR Number:   319387
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   7.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4666 20 May 2003 Fixed
8.0.2 4255 20 May 2003 Fixed
8.0.1 3115 20 May 2003 Fixed
Description
On Win32 platforms, a client may have failed when closing a tcpip or http connection, with a system error 10093. This has now been fixed.



CR:319390
CR Number:   319390
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1027 20 May 2003 Fixed
8.0.3 4666 20 May 2003 Fixed
8.0.2 4255 20 May 2003 Fixed
Description
.NET application may not have worked properly if the version of native dll (dbdata8.dll) did not match the version of managed dll (iAnywhere.Data.AsaClient.dll). Now, when the managed dll loads the native dll, it checks the version. If the native dll's version is not the same as the managed dll's version, an error message is displayed.



CR:319428
CR Number:   319428
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4666 20 May 2003 Fixed
8.0.2 4255 20 May 2003 Fixed
Description
The database server, when run on NetWare, would have eventually stopped accepting SPX connections, and may have hung on shutdown. This was due to the server running out of memory and has been fixed.



CR:319445
CR Number:   319445
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)
9.0.0 1061 20 May 2003 Fixed
Description
If a parameter to a web service was longer than 250 bytes, it would have been truncated. The resulting length would have been the original length modulo 256. This is now fixed.



CR:319465
CR Number:   319465
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)
9.0.0 1062 20 May 2003 Fixed
Description
The server could have crashed when run on 64 bit platforms when executing a sort or hash-based operation. This crash has been fixed.



CR:319516
CR Number:   319516
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4666 20 May 2003 Fixed
8.0.2 4256 20 May 2003 Fixed
Description
On WindowsXP, the location numbers for the Sybase Central window were set incorrectly when the window was maximized and closed. This has now been fixed.



CR:319569
CR Number:   319569
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)
8.0.3 4685 04 Jun 2003 Fixed
Description
The -zs server option allows a size limit to be placed on the request level log file. This limit can now be adjusted dynamically, without restarting the server, by executing:

call sa_server_option('request_level_log_size',nnn)

where nnn is the size limit for the file in bytes.
Workaround Description
 Since this is the case, ct's must stop the db engine and restart it with the new parameters in order to start the db. Or the must run CALL sa_server_option('request_level_logging', 'NONE') and manually delete the file and restart it in order to keep size



CR:319655
CR Number:   319655
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1063 21 May 2003 Fixed
Description
Using the Table Editor could have cause an exception to be thrown. For example, editing a column and switching to another tree node or pressing 'F5' to refresh while on the Data tab of a table. This has been fixed.



CR:319724
CR Number:   319724
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1063 21 May 2003 Fixed
8.0.3 4668 21 May 2003 Fixed
8.0.2 4256 21 May 2003 Fixed
Description
When setting an unknown property at connection time, the JDBC-ODBC bridge would have throw an exception. The bridge now ignores the property, which is the behaviour of the Sun bridge.



CR:320016
CR Number:   320016
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)
9.0.0 1063 21 May 2003 Fixed
8.0.3 4672 21 May 2003 Fixed
Description
The syntax for 'ALTER DATABASE CALIBRATE TEMPORARY DBSPACE' has been changed to 'ALTER DATABASE CALIBRATE DBSPACE TEMPORARY' in order for the syntax to be consistent with other similar statements.



CR:320021
CR Number:   320021
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)
9.0.1 1697 12 Nov 2003 Fixed
9.0.0 1240 18 Nov 2003 Fixed
8.0.3 4842 18 Nov 2003 Fixed
8.0.2 4345 18 Nov 2003 Fixed
Description
The server maintains row counts for catalog and user tables in the system table SYSTABLE. The row count for the table system SYSATTRIBUTE could have become incorrect during database operation. The incorrect row count could have caused an error during database validate, in addition to causing other problems. This has been fixed, the server will now keep an accurate count of rows in SYSATTRIBUTE.



CR:320022
CR Number:   320022
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   8.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.1 1656 07 Oct 2003 Fixed
9.0.0 1223 07 Oct 2003 Fixed
7.0.4 3497 08 Oct 2003 Fixed
Description
Breakpoints could not be set in procedures or triggers owned by the user dbo. This has now been fixed so that dbo procedures and triggers created by the user are now debuggable. System procedures and triggers owned by dbo are still not available.



CR:320035
CR Number:   320035
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1069 26 May 2003 Fixed
Description
Using the Create Database wizard to create a database without a log file, would have created a database with a log file anyway. The log file would have had the same name as the database file. This has been fixed.



CR:320036
CR Number:   320036
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1037 27 May 2003 Fixed
Description
The Options dialog (selected from Tools>Options menu) can now be opened even when not connected to a database. The controls for options which are stored in the database are disabled.



CR:320043
CR Number:   320043
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1082 11 Jun 2003 Fixed
8.0.3 4686 11 Jun 2003 Fixed
8.0.2 4266 11 Jun 2003 Fixed
8.0.1 3118 11 Jun 2003 Fixed
Description
Calling the CSCONVERT function with a string larger than the database page size, would have crashed the server. CSCONVERT is called by some of the external system functions like XP_SENDMAIL. As a result, a call to XP_SENDMAIL with a message body larger than the size of a database page would likely have crashed the server. This has been fixed.



CR:320064
CR Number:   320064
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1063 21 May 2003 Fixed
Description
If dbisql was opened from Sybase Central and the mouse was moved over any of the Sybase Central toolbar buttons while it had focus, a tooltip appearing would have caused focus to move to the Sybase Central. This problem has been fixed.
Workaround Description
 Run all windows in maximized mode.



CR:320085
CR Number:   320085
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Linux
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4675 26 May 2003 Fixed
8.0.2 4294 25 Jul 2003 Fixed
8.0.1 3125 25 Jul 2003 Fixed
Description
Attempting to run dbisql -nogui on Unix platforms not running X, would have failed with an internal error. This has been fixed, dbisql -nogui can now be run without the need for an X server.



CR:320153
CR Number:   320153
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)
16 Jun 2003 Not a Bug
Description
ASA allows you to create a table and a procedure with the same name. The object_id procedure (and any procedure that uses it) requires a unique name. To avoid a conflict with this requirement, choose a different name for the table or procedure. Note also that other DMBS may not allow duplicate names for tables and procedures. This is how ASE behaves in this regard.

1> create table otto (a int)

2> go

1> create proc otto as begin select 1 end

2> go

Msg 2008, Level 16, State 1:

Procedure 'otto', Line 1:

The object 'otto' is not a procedure so you cannot create another procedure under that group name.



CR:320155
CR Number:   320155
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1068 21 May 2003 Fixed
8.0.3 4673 21 May 2003 Fixed
8.0.2 4258 21 May 2003 Fixed
8.0.1 3116 21 May 2003 Fixed
Description
Using REORGINIZE TABLE ... INDEX to reorganize a Compressed Btree index on a very large table would have crashed the server. This is now fixed.



CR:320187
CR Number:   320187
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1074 28 May 2003 Fixed
Description
Using the Upgrade Database wizard to upgrade a database and checking the "Shut down the database when the upgrade completes" check box (which is the default), would have failed when shutting down the server with the error message "The database '<name>' could not be

shut down". This has been fixed. Note that the upgrade would be completed successfully; it was only the shut down that would have failed.



CR:320239
CR Number:   320239
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.1 1577 07 Jul 2003 Fixed
9.0.0 1180 07 Jul 2003 Fixed
8.0.3 4708 07 Jul 2003 Fixed
8.0.2 4279 07 Jul 2003 Fixed
8.0.1 3121 07 Jul 2003 Fixed
Description
If remote function was defined (using CREATE FUNCTION ... AT ...), and it did not fully qualify the function name in the location string, then attempting to call the remote function would have crashed the server. This problem has now been fixed.
Workaround Description
 None.



CR:320245
CR Number:   320245
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)
9.0.0 1068 23 May 2003 Fixed
Description
Executing queries with aliases on uncorrelated subselects used in EXISTS, NOT EXISTS, ANY, ALL, IN or NOT IN subqueries, may have caused a server crash. This may have ocurred if the subquery had only one outer reference and this was the alias and the subquery was in a predicate which was considered for subquery optimization.



For example:

SELECT (SELECT c1 FROM t3 WHERE t3.akey='xyz') AS foo

FROM t1,t2

WHERE t1.c2=t2.c2

AND t1.pk NOT IN (SELECT t4.pk FROM t4 WHERE c4=foo)



This has now been fixed.



CR:320277
CR Number:   320277
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4674 26 May 2003 Fixed
8.0.2 4259 26 May 2003 Fixed
8.0.1 3116 26 May 2003 Fixed
Description
When installed on Windows 2003, the Services folder in the ASA and MobiLink plug-ins for Sybase Central would not be available. This has been fixed.
Workaround Description
 Customer can use command line to create services but this is not a long term solution.



CR:320339
CR Number:   320339
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1080 04 Jun 2003 Fixed
8.0.3 4685 04 Jun 2003 Fixed
8.0.2 4315 19 Sep 2003 Fixed
8.0.1 3131 19 Sep 2003 Fixed
Description
Executing a SELECT ... INTO ... would have crashed the server if it contained a single row aggregation which returned a string type and execution of the SELECT failed with an error. This is now fixed.



CR:320357
CR Number:   320357
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1069 26 May 2003 Fixed
8.0.3 4674 26 May 2003 Fixed
8.0.2 4259 26 May 2003 Fixed
8.0.1 3116 26 May 2003 Fixed
Description
Using the Embedded SQL syntax, the statements:

EXEC SQL GET DESCRIPTOR sqlda :hostvar = DATA

or

EXEC SQL SET DESCRIPTOR sqlda DATA = :hostvar

could have failed to copy the correct amount of data if the host variable type was DECL_DATETIME, DT_TIMESTAMP_STRUCT, DECL_LONGVARCHAR, DT_LONGVARCHAR, DECL_LONGBINARY or DT_LONGBINARY. The SQLDATETIME structure used by the TIMESTAMP_STRUCT structure is 14 bytes on platforms which do not require alignment, and 16 bytes on those that do. Code with the length of the structure appropriate for the current machine was being generated by sqlpp. Now sizeof(SQLDATETIME) is used in the generated code instead.



CR:320379
CR Number:   320379
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 26 May 2003 Fixed
Description
When running dbisql on a Japanese version of Windows 2000, the READ statement would misinterpret Japanese characters. This problem has been fixed.



CR:320389
CR Number:   320389
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1096 16 Jun 2003 Fixed
8.0.3 4273 16 Jun 2003 Fixed
8.0.2 4273 16 Jun 2003 Fixed
8.0.1 3120 16 Jun 2003 Fixed
Description
Index scans on databases create with a version prior to 5.0, (that may have been upgraded), could have returned too many rows. This problem only affected indexes that were not fully hashed. This problem has been fixed. The recommended work around would be to do an unload/reload of the database, but rebuilding the affected indexes would do as well.



CR:320516
CR Number:   320516
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1070 26 May 2003 Fixed
8.0.3 4675 26 May 2003 Fixed
8.0.2 4259 26 May 2003 Fixed
8.0.1 3116 26 May 2003 Fixed
Description
In a datasource file on Windows CE, the long form of a connection parameter could not have been specified, only the short form. For example, DATABASEFILE could have been specified, but not DBF. This has been fixed so that either form can now be specified for all parameters.



CR:320531
CR Number:   320531
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)
9.0.0 1073 26 May 2003 Fixed
Description
During analysis by the Index Consultant, certain complex queries could have caused the server to crash. This has now been fixed.



CR:320533
CR Number:   320533
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)
9.0.0 1092 26 May 2003 Fixed
Description
During analysis, the Index Consultant could have caused the server to exhaust memory. Immediately before doing so, the server would have gone to 100% CPU usage and the consultant client would appear to hang. This has been fixed.



CR:320534
CR Number:   320534
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)
9.0.0 1070 27 May 2003 Fixed
Description
At a random point during the capturing of an index tuning workload, the Index Consultant, and any client applications currently running, would have hung with no CPU usage. This has now beed fixed.



CR:320535
CR Number:   320535
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)
9.0.0 1070 26 May 2003 Fixed
Description
When given a very large workload of queries (greater than 15,000 in a typical case), and the number of captures topped a certain limit, the server and Index Consultant would have hung. When viewed in the Windows Task Manager, the server would have consumed almost all free memory on the machine. This has been fixed.



CR:320537
CR Number:   320537
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)
9.0.0 1070 27 May 2003 Fixed
Description
When used from dbisql, if given a query contained a statement terminator (ie. a semicolon) inside a string, the Index Consultant would have reported that only one query could be analyzed at a time, and refuse to analyze it.



For example:

select * from T1 where T1.X = ';' order by T1.X;



Aditionally, the error message displayed in this case referred to the statement in the "SQL Comments" window, when it meant the "SQL Statements" window. Both of these problems have now been fixed.



CR:320578
CR Number:   320578
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1070 26 May 2003 Fixed
8.0.3 4675 26 May 2003 Fixed
8.0.2 4259 26 May 2003 Fixed
Description
A new option, (under Tools>Options>General), "Prompt to connect on startup" has been added to open the Connect dialog on startup if no command line options are specified. The default is for the option to be on.



CR:320581
CR Number:   320581
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1070 26 May 2003 Fixed
8.0.3 4675 26 May 2003 Fixed
8.0.2 4259 26 May 2003 Fixed
8.0.1 3116 26 May 2003 Fixed
Description
When using SQLGetData on a SQL_WCHAR column, fetched from a UTF8 database, the resultant indicator value was incorrect if the data was obtained in chunks.



When using SQLGetData to convert binary data to a SQL_WCHAR column, the resultant indicator value was incorrect.



For binary to wide character conversions, if the data was fetched in chunks, the pieces would be placed in the wrong location in memory. The terminating NULL wide character was placed in the wrong location in memory.



For binary to wide character conversions, the call to the translation DLL passed the wrong type, SQL_CHAR instead of SQL_WCHAR, for wide characters. In some cases, it passed the wrong length as well.



These problems have been corrected.



CR:320615
CR Number:   320615
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)
9.0.0 1072 26 May 2003 Fixed
8.0.3 4677 26 May 2003 Fixed
8.0.2 4260 26 May 2003 Fixed
Description
Validate Index ensures that each referenced row exists in the index, but it did not ensure that each referenced row could be found. Now each row is looked up by value. Note that Validate Table does check for this.



CR:320616
CR Number:   320616
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)
9.0.0 1072 26 May 2003 Fixed
8.0.3 4677 26 May 2003 Fixed
8.0.2 4260 26 May 2003 Fixed
8.0.1 3117 26 May 2003 Fixed
Description
Reorganizing a comparison-based index with many entries (more than 3,000,000 in a database with a 2k page size) would have corrupted it. This is now fixed.



CR:320645
CR Number:   320645
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)
9.0.0 1085 06 Jun 2003 Fixed
8.0.3 4686 06 Jun 2003 Fixed
8.0.2 4267 06 Jun 2003 Fixed
8.0.1 3118 06 Jun 2003 Fixed
8.0.0 2360 06 Jun 2003 Fixed
Description
The server could have crashed when searching a trie-based index for long strings not in the column's domain. Typically for this to occur, the string would have to have been greater than 255 characters in length.



CR:320657
CR Number:   320657
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1073 26 May 2003 Fixed
8.0.3 4678 26 May 2003 Fixed
8.0.2 4260 26 May 2003 Fixed
Description
The Watch Manager was missing mnemonics for lists boxes. These have now been added.



CR:320659
CR Number:   320659
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4680 28 May 2003 Fixed
8.0.2 4263 28 May 2003 Fixed
8.0.1 3117 28 May 2003 Fixed
Description
If a remote database contains only one publication and dbmlsync is running in scheduling synchronization, dbmlsync will run in hover-mode. Whenever errors occur in an upload, dbmlsync should completely shut down the log scanning layer and restart it again. However, this would not have occurred. This problem is now fixed.



CR:320668
CR Number:   320668
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1087 11 Jun 2003 Fixed
8.0.3 4687 11 Jun 2003 Fixed
8.0.2 4269 11 Jun 2003 Fixed
8.0.1 3118 11 Jun 2003 Fixed
7.0.4 3463 11 Jun 2003 Fixed
Description
When an OleDbDataReader was open on a connection to a Japanese database (Default collation=932JPN), string values were truncated when fetched. The length of the returned strings was taken as the number of characters, when it should be the number of bytes. This has now been corrected.
Workaround Description
 None.



CR:320708
CR Number:   320708
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1074 27 May 2003 Fixed
8.0.3 4679 27 May 2003 Fixed
8.0.2 4261 27 May 2003 Fixed
8.0.1 3117 27 May 2003 Fixed
Description
The QueryEditor and the Expression Editor did not fit on the screen when the resolution was set to 800x600. These windows have been resized to fit an 800x600 screen.



CR:320753
CR Number:   320753
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1074 28 May 2003 Fixed
Description
After upgrading a database through Sybase Central, a dialog containing the error message "The database <dbname> could not be shut down" would appear, and the database would not have been shut down, although the upgrade was successful. This has been fixed.



CR:320876
CR Number:   320876
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Linux
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4721 16 Jul 2003 Fixed
8.0.2 4286 16 Jul 2003 Fixed
8.0.1 3123 16 Jul 2003 Fixed
Description
When using the Foreign Key wizard on Unix versions of Sybase Central, in some instances the last foreign column selection chosen by the user would be ignored. This has been fixed.



CR:320882
CR Number:   320882
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Linux
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1109 11 Jul 2003 Fixed
8.0.3 4720 11 Jul 2003 Fixed
8.0.2 4284 11 Jul 2003 Fixed
Description
Writing a message to the server window with the MESSAGE statement which contained Japanese characters, would not have displayed correctly on a Linux machine running in a Japanese environment. This has been fixed, the euc-jp code page is now supported.



CR:320912
CR Number:   320912
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1075 03 Jun 2003 Fixed
8.0.3 4680 03 Jun 2003 Fixed
8.0.2 4263 03 Jun 2003 Fixed
8.0.1 3116 03 Jun 2003 Fixed
Description
Computed columns that only consisted of "owner"."table"."column" were being truncated to just "column" in the Query Editor. This problem has been fixed.



CR:320929
CR Number:   320929
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   7.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1075 29 May 2003 Fixed
8.0.3 4680 29 May 2003 Fixed
8.0.2 4263 29 May 2003 Fixed
8.0.1 3117 29 May 2003 Fixed
7.0.4 3456 29 May 2003 Fixed
Description
An internal error would have been reported if:



- dbisql was running on a Windows operating system which was configured to use a multi-byte character set (MBCS), such as Japanese or Chinese, and



- an OUTPUT TO ... FORMAT EXCEL statement was executed, and



- an exported string, which was less than 255 characters, had a MBCS encoding which was greater than 255 bytes.



This problem has been fixed.



CR:320943
CR Number:   320943
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)
9.0.0 1075 30 May 2003 Fixed
Description
DBISQL was was unable to correctly read Japanese characters in script files when it was run from a command line (i.e. in batch mode). This problem has been fixed.



CR:320960
CR Number:   320960
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1076 04 Jun 2003 Fixed
8.0.3 4681 04 Jun 2003 Fixed
8.0.2 4263 04 Jun 2003 Fixed
8.0.1 3117 04 Jun 2003 Fixed
Description
It was not possible to open the Expression Editor to edit an ON condition using the keyboard, it required double-clicking the cell with the right mouse button. It was possible to TAB to the cell, but the keystrokes for editing (F2 or space) were being ignored. This is now fixed.



CR:320974
CR Number:   320974
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1076 29 May 2003 Fixed
8.0.3 4681 29 May 2003 Fixed
8.0.2 4263 29 May 2003 Fixed
8.0.1 3117 29 May 2003 Fixed
Description
When using the Erase Database wizard to erase a Write file, the Write file would not have been displayed when browsing for it, unless the file filter was changed to display all files. This has been fixed, the file filter now includes Write files.



CR:320976
CR Number:   320976
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1076 30 May 2003 Fixed
8.0.3 4681 30 May 2003 Fixed
8.0.2 4263 30 May 2003 Fixed
Description
When connecting to a database, the plug-in made a second superfluous connection. When disconnecting, this second connections was not closed. This has been fixed, the second connect is no longer made.



CR:321012
CR Number:   321012
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)
9.0.0 1076 30 May 2003 Fixed
Description
If a stored procedure consisting of a single select statement was called in the FROM clause of a query and one of the result columns was of type bigint, the server may have crashed. This has been fixed.



CR:321019
CR Number:   321019
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1091 18 Jun 2003 Fixed
Description
After creating a service using the Service wizard, the new service's status would be displayed as "(unknown)" until the tab page was refreshed . Now, the service's status is displayed immediately.



CR:321036
CR Number:   321036
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1070 30 May 2003 Fixed
Description
When using the Object Debugger and trying to step into a procedure where the source could not be found, a message was displayed twice that the source was not found. This has been fixed, the error is now only displayed once.



CR:321047
CR Number:   321047
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1076 30 May 2003 Fixed
Description
When connected to a database using jConnect, running the "Create Database" wizard would not have displayed the status messages (e.g. "Creating system tables", "Creating system views", etc). This would only have happened when connected using jConnect, and only if the "Create a database on the following server computer" option was checked in he "Create Database" wizard (which is the default). This problem has been fixed.



CR:321052
CR Number:   321052
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1080 04 Jun 2003 Fixed
Description
When attempting to translate a trigger or procedure from one dialect, (ie Watcom-SQL or Transact-SQL), to the other then back again, would not have resulted in the original text. For 9.0.0, the translate operations were changed to translate the SQL in the editor, rather than the SQL in the database, leading the the problem. The original 8.0 behaviour has now been restored.



CR:321132
CR Number:   321132
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Linux
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Sep 2003 Not reproducible with latest version of the product available as of Resolution Date
Description
The java.util.TimeZone.getTimeZone returns an java.lang.ExceptionInInitializerError: java.lang.NullPointerException(TimeZone.java:342) error.

The same loaded class file works fine on Windows. The database hwas created with jdk 1.3.

and the java file has been compiled with target 1.1.



CR:321146
CR Number:   321146
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   4.2.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1077 03 Jun 2003 Fixed
Description
When performing an edit using Table Editor, the changes would have been discarded when refreshing the folder or refreshing all. This has been fixed.



CR:321160
CR Number:   321160
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1094 18 Jun 2003 Fixed
8.0.3 4693 18 Jun 2003 Fixed
8.0.2 4273 18 Jun 2003 Fixed
Description
The error, "-189 - Unable to find in index '{index name}' for table '{table name}', would have been reported whenever INSERT ... ON EXISTING UPDATE was used on a table having computed columns and the computed column expressions referenced an indexed column.



For example:

create table T1(pk int not null primary key ,csc int null compute (pk+0));

insert into T1 (pk) Values(3);

commit;

insert into T1 (pk) on existing update values(3);



This has now been fixed.



CR:321289
CR Number:   321289
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1080 04 Jun 2003 Fixed
8.0.3 4685 04 Jun 2003 Fixed
8.0.2 4265 04 Jun 2003 Fixed
8.0.1 3118 04 Jun 2003 Fixed
Description
If an integrated login attempt failed because of a communications error, the client application could have crashed. This would only have happened if the connection string, (or data source if the DSN parameter was used), contained all of Integrated=YES, Userid and Password. This has been fixed.



CR:321344
CR Number:   321344
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)
9.0.0 1080 04 Jun 2003 Fixed
Description
Trying to generate an Ultralite plan for a query containing an EXISTS or NOT IN subquery may have failed with SQLCODE -727: "The optimizer was unable to construct a valid access plan." This has been fixed.



CR:321355
CR Number:   321355
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1080 04 Jun 2003 Fixed
8.0.3 4685 04 Jun 2003 Fixed
8.0.2 4265 04 Jun 2003 Fixed
Description
When executing a command to update numeric fields with parameters, the AsaClient needs to convert .Net numeric values to ASA numeric values. If the scale of a numeric value was incorrect, the command would have failed and an exception thrown. This has been fixed.



CR:321429
CR Number:   321429
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)
9.0.0 1074 04 Jun 2003 Fixed
8.0.3 4679 04 Jun 2003 Fixed
8.0.2 4261 04 Jun 2003 Fixed
Description
The 32-bit Windows support on Win64 for Itanium does not include Address Windowing Extensions (AWE) and scattered reads. Attempting to create an AWE cache in this environment would have failed with "Insufficient memory". Similarly, if a scattered read were attempted in this environment, the IO would have failed with the server reporting an assertion failure. Now, AWE caches are not allowed in this environment and a conventional cache is used instead. Scattered reads are simulated using a large contiguous buffer (as done on other platforms).



Win64 for AMD64 supports both AWE and scattered reads for 32-bit executables.



Running the 32-bit engine on Win64 is not recommended. Running the native 64-bit executable is preferred.



CR:321464
CR Number:   321464
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1089 18 Jun 2003 Fixed
Description
If you perform the following steps, a stack trace will occur.

1. Connect to database in Sybase Central 4.2

2. Create a new table

3. Add a column and define its datatype

4. Select the table name in the table tree view (left pane)

5. Right mouse click Delete

6. Verify the Save changes request



If using "fast launcher", the stack trace remains until the "fast launcher" is restarted or stopped.



CR:321541
CR Number:   321541
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.4 3462 04 Jun 2003 Fixed
Description
The messages installed for the Windows Performance Monitor for ASA Database, Server and Connection counters were in English only, even if a localized version of SAS was installed. This problem is now fixed.
Workaround Description
 The simplest workaround of deleting the dbctrs.ini

before applying the 7.0.4 ebf apparently works.

[possibly because it is the one from 7.0.3]



I have also placed a copy of the one from the 7.0.3

branch on the ftp site though they would need to

m



CR:321585
CR Number:   321585
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)
9.0.0 1085 06 Jun 2003 Fixed
Description
If the same database file was specified twice on the server command line, the server would have reported a meaningless error on startup: "Unknown error(x)", where x was a large number. This has been fixed.



CR:321594
CR Number:   321594
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1085 06 Jun 2003 Fixed
8.0.3 4686 06 Jun 2003 Fixed
8.0.2 4268 06 Jun 2003 Fixed
Description
The list of tables in the Synchronization Properties were not being sorted. Now they are



CR:321610
CR Number:   321610
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)
9.0.0 1085 10 Jun 2003 Fixed
Description
The way Java handled focus changed between JRE 1.3 and 1.4. This caused navigating around the objects in a window, using the mouse or the tab key, to not always work correctly. This has been fixed.



CR:321611
CR Number:   321611
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1086 10 Jun 2003 Fixed
8.0.3 4686 10 Jun 2003 Fixed
8.0.2 4268 10 Jun 2003 Fixed
8.0.1 3118 10 Jun 2003 Fixed
Description
If when using the QueryEditor to create a derived table, a column was aliased with a reserved word (eg "from"), the generated SQL did not quote the alias in the list of columns for the derived table. This has been fixed so that now it does.



CR:321664
CR Number:   321664
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1086 06 Jun 2003 Fixed
8.0.3 4686 06 Jun 2003 Fixed
8.0.2 4268 06 Jun 2003 Fixed
Description
The Monitor was sorting the worker threads as strings. Now they are sorted numerically by the stream number, then numerically by the thread number.



CR:321665
CR Number:   321665
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)
9.0.0 1086 05 Jun 2003 Fixed
Description
Attempting to run the server with AWE support enabled (ie the -cw commandline option) would have caused the server to crash. This is now fixed.



CR:321666
CR Number:   321666
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1095 18 Jun 2003 Fixed
8.0.3 4694 18 Jun 2003 Fixed
8.0.2 4273 18 Jun 2003 Fixed
Description
Sequential table scans at isolation levels 1 and 2 did not block on uncommitted deletes from other transactions, but skipped the rows. READ_PAST_DELETED has now been added which changes this behaviour. When ON, (the default), sequential scans at isolation 1 and 2 will skip uncommitted deleted rows as before, but when OFF, sequential scans will block on uncommitted deleted rows at isolation levels 1 and 2, until the deleting transaction commits or rolls back.
Workaround Description
 None.



CR:321682
CR Number:   321682
Product Name:   UltraLite
Product Component:   Analyser Java Classes
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1087 11 Jun 2003 Fixed
8.0.3 4687 11 Jun 2003 Fixed
8.0.2 4269 11 Jun 2003 Fixed
Description
Attempting to run ulinit or ulgen against an ASA reference database with a Turkish collation, eg 1254TRK, would have caused the error 揟able 憇ysarticle not found. This has been fixed.



CR:321729
CR Number:   321729
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)
9.0.0 1077 10 Jun 2003 Fixed
8.0.3 4687 10 Jun 2003 Fixed
8.0.2 4268 10 Jun 2003 Fixed
Description
When running the Win32 server or client software on a Win64 platform, the SPX port would not have been started. The SPX port is now disabled for 32-bit software running on 64-bit platforms.



CR:321743
CR Number:   321743
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)
9.0.0 1086 10 Jun 2003 Fixed
8.0.3 4686 10 Jun 2003 Fixed
8.0.2 4268 10 Jun 2003 Fixed
Description
If a database or transaction log file was NTFS-compressed, the file fragment count could have been incorrect. NTFS-compressed file are now handled correctly.

Note, the file fragment count is available through the system functions db_property('DBFileFragments') and db_property( 'LogFileFragments' ), and can be displayed in a warning at startup if the fragment count is high.



CR:321775
CR Number:   321775
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)
9.0.0 1055 10 Jun 2003 Fixed
Description
A database that had been the remote in a Mobilink synchronization, may have caused a server crash if it required recovery from the transaction log. The problem has now been fixed.



CR:321799
CR Number:   321799
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1092 12 Jun 2003 Fixed
Description
When saving the command history, DBISQL now obfuscates the following statements if they contain password information:



GRANT CONNECT TO ... IDENTIFIED BY ...

GRANT REMOTE DBA TO ... IDENTIFIED BY ...

CONNECT ... IDENTIFIED BY ...

CONNECT USING ... (where a password is given)

CREATE EXTERNLOGIN ... IDENTIFIED BY ...



The password is replaced by an ellipsis. The rest of the statement is left as-is, though comments are removed and white space is coalesced. If the statement does not contain a password, it is not obfuscated in any way; any comments it contains are left as-is.



CR:321812
CR Number:   321812
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)
9.0.0 1086 06 Jun 2003 Fixed
8.0.3 4686 06 Jun 2003 Fixed
8.0.2 4268 06 Jun 2003 Fixed
Description
A new server-level property, "NativeProcessorArchitecture", has been added. On platforms where a processor can be emulated (such as X86 on Win64), this property returns a string that identifies the native processor type. In all other cases, property( 'NativeProcessorArchitecture' ) will be equal to property( 'ProcessorArchitecture' ).



For example, the following values are returned:

For the 32-bit (X86) Windows NT engine running on Win64 for Itanium

Property( 'NativeProcessorArchitecture' ) returns 'IA64'

Property( 'ProcessorArchitecture' ) returns 'X86'

For the 32-bit (X86) Windows NT engine running on Win64 for AMD64

Property( 'NativeProcessorArchitecture' ) returns 'AMD64'

Property( 'ProcessorArchitecture' ) returns 'X86'

In all other cases, property( 'NativeProcessorArchitecture' ) returns the same value as property( 'ProcessorArchitecture' )



CR:321813
CR Number:   321813
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1087 10 Jun 2003 Fixed
Description
The Cut, Copy and Paste menu items and toolbar buttons only supported cutting, copying and pasting text within a text field in the Table Editor. Now, the Cut, Copy and Paste menu items and toolbar buttons support the cutting, copying and pasting of database

columns. The Ctrl-X, Ctrl-C and Ctrl-V accelerators can still be used while editing within a text field in the Table Editor to cut, copy and paste text. Since the Delete menu item and toolbar button can now be used to delete columns, the Delete Column menu item (in the File menu) and toolbar button (on the plug-in's toolbar) have been removed.



CR:321834
CR Number:   321834
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1087 11 Jun 2003 Fixed
8.0.3 4687 11 Jun 2003 Fixed
8.0.2 4269 11 Jun 2003 Fixed
8.0.1 3118 11 Jun 2003 Fixed
7.0.4 3463 11 Jun 2003 Fixed
Description
When a START ENGINE statement was executed in dbisql, the quotation marks from the engine name parameter was not stripped off. For example, the following statement would start an engine called 'Test' rather than Test.



START ENGINE AS 'Test'



Now, the quotation marks do not appear as part of the started engine's name.



CR:321844
CR Number:   321844
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1087 11 Jun 2003 Fixed
8.0.3 4687 11 Jun 2003 Fixed
8.0.2 4269 11 Jun 2003 Fixed
Description
The list of columns in the table did not reverse the sort order if the header was clicked more than once, as is standard. Now when a column header is clicked more than once, the sort order alternates between ascending and descending.



CR:321859
CR Number:   321859
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1087 11 Jun 2003 Fixed
Description
The MobiLink Monitor was failing to recognize some MobiLink events. The events that were unrecognized are currently for internal use only, and are now ignored by the Monitor.



CR:321929
CR Number:   321929
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1091 12 Jun 2003 Fixed
8.0.3 4691 12 Jun 2003 Fixed
8.0.2 4271 12 Jun 2003 Fixed
8.0.1 3119 12 Jun 2003 Fixed
Description
If the value specified for a Global Autoincrement partition size in the Column property sheet or the Domain wizard, was larger than 2^31-1, then the value would have been ignored. Now, the arbitrarily large values are respected.



CR:321934
CR Number:   321934
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4756 22 Aug 2003 Fixed
8.0.2 4304 22 Aug 2003 Fixed
8.0.1 3128 22 Aug 2003 Fixed
Description
In the Create Database, Restore Database, Compress Database, Uncompress Database, Create Write File and Erase Database wizards, if the option to have the wizards start a new local server automatically was selected, and for some reason the server could not be started or the connection could not be established, then the wizards would have displayed an internal error. This has been fixed.



CR:321970
CR Number:   321970
Product Name:   UltraLite
Product Component:   Analyser Java Classes
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1094 17 Jun 2003 Fixed
8.0.3 4693 17 Jun 2003 Fixed
8.0.2 4273 17 Jun 2003 Fixed
Description
When a query made use of an index on a column that allowed NULLs, it was possible that the UltraLite analyzer would have generated code that referenced the identifier ULConstantNull_ANY. Since this constant was not defined, the application would consequently not compile. This has been fixed.





--------------------------------------华丽的分割线-------------------------------------------------------------------------
之前就已经研发成功了能够从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等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------