远程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:308349
CR Number:   308349
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4573 10 Feb 2003 Fixed
8.0.2 4119 10 Feb 2003 Fixed
Description
The QueryEditor would not have allowed an ORDER BY for the case were a table was being joined to itself and the same column from each aliased table was being used in the ORDER BY. This has now been corrected.

For example:



SELECT "m"."emp_lname", "e"."emp_lname"

FROM "DBA"."employee" AS m JOIN "DBA"."employee" AS e

ON "m"."emp_id" = "e"."manager_id"

ORDER BY "m"."emp_lname" ASC , "e"."emp_lname" ASC



CR:308370
CR Number:   308370
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4572 10 Feb 2003 Fixed
Description
Entering a non-numberic value in the Go To Line dialog would have caused dbisql to crash. This is now fixed.



CR:308372
CR Number:   308372
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4572 10 Feb 2003 Fixed
Description
When using the Find facility, the last character of last line was never found when the search direction was up. This is now fixed.



CR:308440
CR Number:   308440
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4578 07 Feb 2003 Fixed
8.0.2 4212 07 Feb 2003 Fixed
8.0.1 3099 07 Feb 2003 Fixed
Description
Running 'TRUNCATE TABLE' on an already corrupted table could have resulted in other database objects also becoming corrupted and would only have happened in extrememly rare circumstances. 'VALIDATE TABLE' would have found the corruption both before and after the 'TRUNCATE TABLE' command. Assertion 200607 has now been added to catch this case.



CR:308449
CR Number:   308449
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4578 10 Feb 2003 Fixed
8.0.2 4212 10 Feb 2003 Fixed
8.0.1 3099 10 Feb 2003 Fixed
7.0.4 3416 10 Feb 2003 Fixed
Description
The ODBC driver may have occasionally reported the lengths of strings incorrectly, when dealing with multibyte character sets. The data was returned correctly, but the length would sometimes be too long. The length reported should now be correct.



CR:308450
CR Number:   308450
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   8.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4574 07 Feb 2003 Fixed
8.0.2 4209 07 Feb 2003 Fixed
8.0.1 3097 07 Feb 2003 Fixed
Description
In version 8.0.1, the UltraLite schema information output by the analyzer was extended to support additional features, including sending column names to Mobilink. This resulted in more data segment usage by the generated code, possibly exceeding the Palm limitation of 64kb. The extended schema information for columns may now be omitted to decrease data segment usage. To enable this feature, define the preprocessor symbol UL_OMIT_COLUMN_INFO before compiling all generated files. (In CodeWarrior, this #define should be added to your prefix file; for PRCTools, use the -D option.)



Note: when this feature is enabled, the following features are not available and must not be used:

- send_column_names synchronization parameter

- schema upgrades (applies to 8.0.2 and later)



CR:308453
CR Number:   308453
Product Name:   UltraLite
Product Component:   Analyser Java Classes
Status:   Closed
OS:   Generic
Original Version:   8.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4575 07 Feb 2003 Fixed
8.0.2 4209 07 Feb 2003 Fixed
8.0.1 3098 07 Feb 2003 Fixed
Description
For Palm applications, the ULSEGDB segment output by the analyzer contains row management code for all tables. If an application had a large number of tables, the ULSEGDB segment may have exceeded the maximum size of 64k. A workaround when this occurs is to edit the generated file and insert extra segments manually.



The analyzer now outputs optional segment divisions within ULSEGDB code which are enabled individually by defining a corresponding preprocessor symbol. There is an optional segment division at each table. The segments are named ULSTn where n is an integer (the table number), and each is activated by defining UL_ENABLE_SEGMENT_ULSTn.



For example, suppose an application has 5 tables. The generated code will resemble:



start ULSEGDB segment

start ULST1 segment (if UL_ENABLE_SEGMENT_ULST1 defined)

<code for first table>

start ULST2 segment (if UL_ENABLE_SEGMENT_ULST2 defined)

<code for second table>

...

start ULST5 segment (if UL_ENABLE_SEGMENT_ULST5 defined)

<code for fifth table>



Defining only UL_ENABLE_SEGMENT_ULST4 will leave tables 1 through 3 in ULSEGDB but put tables 4 and 5 into ULST4.



Extra segments should be enabled as required to avoid exceeding the segment maximum size. Note also this assumes generated code segments have been enabled by defining UL_ENABLE_SEGMENTS (and UL_ENABLE_GNU_SEGMENTS if applicable). In CodeWarrior, these #defines should be added to the prefix file; for PRCTools, use the -D option.



CR:308507
CR Number:   308507
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)
8.0.3 4578 11 Feb 2003 Fixed
8.0.2 4212 11 Feb 2003 Fixed
8.0.1 3099 11 Feb 2003 Fixed
8.0.0 2360 11 Feb 2003 Fixed
7.0.4 3416 11 Feb 2003 Fixed
Description
When connected to a database via the JDBC-ODBC bridge, the "Auto commit" option was implicitly on all the time, so that a commit was being done after every statement. This has been fixed so that commits are now implicitly done only if the "Auto_commit" option is "On".



This problem did not affect connections that used jConnect.



CR:308527
CR Number:   308527
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   8.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.1 3103 27 Feb 2003 Fixed
8.0.2 4221 27 Feb 2003 Fixed
8.0.3 4595 27 Feb 2003 Fixed
Description
If a database was initialized with the blank padding option, (dbinit -b), it was impossible for dbmlsync to hover at the end of the transaction log. This has now been fixed.



CR:308632
CR Number:   308632
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)
8.0.2 4213 13 Feb 2003 Fixed
8.0.3 4579 13 Feb 2003 Fixed
9.0.0 531 13 Feb 2003 Fixed
Description
Adaptive Server Anywhere allows one index on a table to be specified as clustered. This specification can now be changed via the ALTER INDEX statement without the need to recreate the index. Note that this statement only changes the specification of the index but does not reorganize the data. So, if the clustered index on a table is changed, then depending upon the key composition for the old and the new clustered index, the data may no longer be clustered on the new clustered index. Remember that the clustering of an index in ASA is only a hint to the server and the clustering of data is not guaranteed. However, if so desired, clustering can be restored by using the REORGANIZE TABLE statement.



CR:308639
CR Number:   308639
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.0 2360 13 Feb 2003 Fixed
8.0.1 3100 13 Feb 2003 Fixed
8.0.2 4213 13 Feb 2003 Fixed
8.0.3 4579 13 Feb 2003 Fixed
9.0.0 532 13 Feb 2003 Fixed
Description
When the server running a remote database encountered an error during download, and the MobiLink server was expecting a download acknowledgement, there would have been extra communication errors in the MobiLink log. The first error would have been "Download failed with client error -NNN", and then spurious communication errors would have followed. This has now been fixed.



CR:308663
CR Number:   308663
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 4579 11 Feb 2003 Fixed
8.0.2 4214 11 Feb 2003 Fixed
8.0.1 3100 11 Feb 2003 Fixed
8.0.0 2360 11 Feb 2003 Fixed
7.0.4 3417 11 Feb 2003 Fixed
Description
If the option wait_for_commit was on, it was possible to commit a transaction that had inserted a foreign key with no matching primary key. For this to have happened, all of the following conditions must hold:

- the foreign key in question must have been larger than any existing primary key,

- another transaction (also with the wait_for_commit option on) must have inserted the same foreign key before the first transaction commited, and must have done so while the foreign key was greater than any existing primary key,

- between the two foreign key insertions, enough primary keys must have been added to fill the last leaf page and at least one of these keys must be subsequently deleted (before the second foreign key insertion).

- the index used to enforce the constraint must have been a uncombined (split) comparision-based index.

This has now been fixed.



CR:308693
CR Number:   308693
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4579 11 Feb 2003 Fixed
8.0.2 4213 11 Feb 2003 Fixed
Description
When the name of a file was entered in the "Database File" field on the "Database" page of the "Connect" dialog, and then the ESCAPE key was pressed while the "Database File" field still had focus, an internal error would have occurred.



This has been fixed.



This problem also affected the ASA plug-in for Sybase Central, the Stored Procedure Debugger, and DBConsole.



CR:308770
CR Number:   308770
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 4579 11 Feb 2003 Fixed
8.0.2 4214 13 Feb 2003 Fixed
Description
If the length of the view's name in a CREATE VIEW statement exceeded 119 bytes, the server would have crashed. Now names of up to 128 bytes are allowed. If the size of the name is over 128 bytes, the error 'Identifier ... too long' will be reported.



CR:308815
CR Number:   308815
Product Name:   UltraLite
Product Component:   UltraLite Schema Painter
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.2 4214 13 Feb 2003 Fixed
8.0.3 4579 13 Feb 2003 Fixed
9.0.0 531 13 Feb 2003 Fixed
Description
The UltraLite Schema Painter would have given a warning if an attempt was made to create a table with a name that was already in use. Clicking OK on the error message and providing a new name for the table would have caused the Schema Painter to crash. This is now fixed.



CR:308830
CR Number:   308830
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.2 4215 13 Feb 2003 Fixed
8.0.3 4580 13 Feb 2003 Fixed
9.0.0 532 13 Feb 2003 Fixed
Description
Command line options have been added to the MobiLink Monitor so that it can open a file or connect to a MobiLink server on startup. This allows for file associations to be setup for MLM files or have the Monitor connect to a MobiLink server, then close and save results to a file when disconnected (either from the GUI or from the the MobiLink server shutting down). The following command will show the options: dbmlmon -?



CR:308844
CR Number:   308844
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)
8.0.2 4214 13 Feb 2003 Fixed
8.0.3 4579 13 Feb 2003 Fixed
9.0.0 531 13 Feb 2003 Fixed
Description
The dbtsinfo utility would have always displayed NULL for a database property called PatriciaTrees. This property had been replaced by one called CompressedBTrees, but dbtsinfo continued to refer to the old name. This is now fixed.



CR:308847
CR Number:   308847
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.2 4214 13 Feb 2003 Fixed
8.0.3 4579 13 Feb 2003 Fixed
9.0.0 531 13 Feb 2003 Fixed
Description
If an attempt to connect failed, an error dialog with a "Show Details" button appeared. Clicking this button shows a summary of the connection parameters used in the attempt. Prior to this fix, the user name and password were displayed twice and the password was shown in clear text. Now the user name and password appear only once and the password is displayed as a series of asterisks.



CR:308855
CR Number:   308855
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)
8.0.3 4583 18 Feb 2003 Fixed
8.0.2 4216 18 Feb 2003 Fixed
Description
When connecting to an authenticated ASA remote server using Remote Data Access, the connection would not have been auto-authenticated. As a result, the connection would become read only after the 30 second time out. This problem has now been resolved and all connections to ASA remotes are now auto-authenticated. Note that the Remote Data Access class must be either asaodbc or asajdbc.



CR:308876
CR Number:   308876
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4636 14 Apr 2003 Fixed
8.0.2 4241 14 Apr 2003 Fixed
7.0.4 3440 14 Apr 2003 Fixed
Description
If CHAINED was set to off (as is the default with TDS connections) and a statement was closed, then all locks were not released even though they should have been. This problem has now been fixed.



CR:308965
CR Number:   308965
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)
8.0.3 4582 17 Feb 2003 Fixed
8.0.2 4216 17 Feb 2003 Fixed
Description
A new option, OPTIMISTIC_WAIT_FOR_COMMIT, has been added to aid in migrating 5.x applications to 8.x. By default, OPTIMISTIC_WAIT_FOR_COMMIT is 'off', when it is set to 'on' locking behaviour when WAIT_FOR_COMMIT='on' is changed as follows:

- no locks are placed on primary key rows when adding an orphan (fk row with no matching pk row)

- if a transaction adds a primary row, it will be allowed to commit only if the transaction has exclusive locks on all foreign rows that reference the primary row at the time the primary row is added.



This option is meant to mimic 5.x locking behaviour when transactions add foreign rows before primary rows (with the proviso that no two transactions concurrently add foreign rows with the same key value). Note that this option is not recommended for general use as there are a number of scenarios in which transactions will (counterintuitively) not be allowed to commit, including:

- if transactions concurrently add foreign rows with the same key value when the primary row does not exist, at most 1 of the transactions will be allowed to commit (the one that adds the corresponding primary row).

- if a transaction deletes a primary row and then adds it back, it likely will not be allowed to commit (unless it has somehow obtained exclusive locks on all of the matching foreign rows).



CR:308999
CR Number:   308999
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.2 4214 13 Feb 2003 Fixed
8.0.3 4580 13 Feb 2003 Fixed
9.0.0 533 13 Feb 2003 Fixed
Description
Clicking the Help button while in the Query Editor, would have done nothing. It now correctly displays the help screen.



CR:309015
CR Number:   309015
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)
8.0.2 4214 13 Feb 2003 Fixed
8.0.3 4580 13 Feb 2003 Fixed
9.0.0 532 13 Feb 2003 Fixed
Description
When an event is executed, it runs on its own connection. If an event connection was dropped (either from Sybase Central or using the DROP CONNECTION statement), the server would have crashed, if it had been started with the -z switch. This has now been fixed.



CR:309074
CR Number:   309074
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)
8.0.2 4214 13 Feb 2003 Fixed
8.0.3 4580 13 Feb 2003 Fixed
9.0.0 533 13 Feb 2003 Fixed
Description
When connected via the JDBC-ODBC bridge, if an output parameter was registered as DECIMAL and then subsequently fetched using getBigDecimal, the bridge would have thrown a "Rounding Necessary" error, instead of properly returning the output parameter. This is now fixed.



CR:309181
CR Number:   309181
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 4580 17 Feb 2003 Fixed
8.0.2 4215 17 Feb 2003 Fixed
8.0.1 3100 17 Feb 2003 Fixed
8.0.0 2360 17 Feb 2003 Fixed
Description
Inserting a new row into a table, (via right-clicking Results pane a selecting "Add"), which contained a BIT column, would have inserted the wrong BIT value in the following were true:

- if the BIT value had a default of "1", and

- if the BIT value was not explicitly set by the user, and

- connected using jConnect.



This has been fixed. This bug affected the table "Data" panel in the Adaptive Server Anywhere plug-in for Sybase Central as well.



CR:309290
CR Number:   309290
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.1 1608 28 Jul 2003 Fixed
9.0.0 1198 28 Jul 2003 Fixed
8.0.3 4737 28 Jul 2003 Fixed
8.0.2 4295 28 Jul 2003 Fixed
7.0.4 3478 28 Jul 2003 Fixed
Description
An UPDATE statement of the form:

update Employee e

set e.emp_fname ('x')

where:

- the column to be updated was qualified with a correlation name

- the "=" was missing

- the expression being assigned was enclosed in parentheses

would result in a server crash. An error (Set clause for column 'a' used incorrectly) will now be reported.



CR:309294
CR Number:   309294
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4581 17 Feb 2003 Fixed
8.0.2 4215 17 Feb 2003 Fixed
8.0.1 3100 17 Feb 2003 Fixed
Description
When specifying connection parameters, if one of them was the "Encryption" parameter and it had an incorrect value, then an unhelpful error message is reported.



Example:

LINKS=TCPIP;ENC=ECC-TLS(trusted_certificates=sample.crt)



would have displayed the following message:

Parse error: Bad value near ''



This has been fixed. The following message is now displayed:



Parse error: Bad value near 'ECC-TLS(trusted_certificates=sample.crt)'



CR:309296
CR Number:   309296
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 4581 17 Feb 2003 Fixed
8.0.2 4215 17 Feb 2003 Fixed
8.0.1 3100 17 Feb 2003 Fixed
8.0.0 2360 17 Feb 2003 Fixed
7.0.4 3419 17 Feb 2003 Fixed
Description
In the presence of concurrent DDL or LOCK TABLE operations, it was possible to commit a transaction that had inserted a foreign key with no matching primary key. For this to have occurred, all of the following conditions must have been true:

- the committing transaction must have deleted a primary row for which there were foreign references

- another transaction must have had the foreign table's schema locked exclusively (via DDL or LOCK TABLE)

- the DDL or LOCK TABLE operation must have been the first use of the foreign table since it was loaded

- the committing transaction must have had blocking off (or possibly be involved in a deadlock)

- the index used to enforce the constraint must have been an uncombined (split) index.



This problem, which could also have resulted in a server crash, is now fixed.



CR:309298
CR Number:   309298
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)
8.0.3 4581 17 Feb 2003 Fixed
8.0.2 4215 17 Feb 2003 Fixed
8.0.1 3100 17 Feb 2003 Fixed
Description
When using SQLGetData to fetch Unicode strings, the indicator could occasionally have been incorrect, multiple columns were being fetched from the same row, and if the strings were being fetched in pieces. This has been fixed.



CR:309299
CR Number:   309299
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4580 17 Feb 2003 Fixed
8.0.2 4215 17 Feb 2003 Fixed
8.0.1 3100 17 Feb 2003 Fixed
8.0.0 2360 17 Feb 2003 Fixed
Description
When the database store was set as in-memory (ie no persistent file), Java UltraLite would have experienced corrupted temp table when doing updates. This is now fixed.



CR:309350
CR Number:   309350
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 4581 17 Feb 2003 Fixed
8.0.2 4215 17 Feb 2003 Fixed
8.0.1 3100 17 Feb 2003 Fixed
8.0.0 2360 17 Feb 2003 Fixed
Description
When trying to view the table data for a proxy table, if the data could not be retrieved because the userid or password for the remote database was no longer valid, the "Add" (row) toolbar button and context menu items were still enabled. This was inappropriate, and could have caused an internal error if clicked.



This has been fixed; the toolbar buttons and menu items in the context menu are now properly enabled.



CR:309512
CR Number:   309512
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4585 25 Feb 2003 Fixed
8.0.2 4218 25 Feb 2003 Fixed
8.0.1 3100 25 Feb 2003 Fixed
Description
The error and warning counts passed to the following scripts:



upload_statistics

download_statistics

synchronization_statistics



could have been wrong. The most likely wrong value was one that was non-zero when it should have been zero. Less likely, the counts could have been smaller than expected. Similarly, the error and warning counts displayed by the MobiLink Monitor could also have been wrong. This has ben fixed.



CR:309611
CR Number:   309611
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   4.1.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4587 24 Feb 2003 Fixed
8.0.2 4218 24 Feb 2003 Fixed
Description
If a column having a default value was modified using Sybase Central to remove the default, the catalog change would have been made immediately, but inserts into the table would continue to use the default until the database was restarted. This has now been fixed.
Workaround Description
 Restart the engine



CR:309620
CR Number:   309620
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4633 14 Apr 2003 Fixed
8.0.2 4240 14 Apr 2003 Fixed
8.0.1 3110 14 Apr 2003 Fixed
8.0.0 2360 14 Apr 2003 Fixed
Description
If a file selected via the "File/Run Script" menu item, was in a directory starting with the letter "n" (e.g. "c:\new\test.sql"), and the platform was Windows, a file not found error would have occurred. This has now been fixed.



CR:309628
CR Number:   309628
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4585 20 Feb 2003 Fixed
8.0.2 4217 20 Feb 2003 Fixed
8.0.1 3101 20 Feb 2003 Fixed
7.0.4 3420 20 Feb 2003 Fixed
Description
When fetching data via ASAProv from a database which used a multibyte collation, and charset conversion was requested, the returned length of the converted string was not set correctly. This could have caused unintended behaviour in ADO applications. This is now fixed.



CR:309653
CR Number:   309653
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)
8.0.3 4591 26 Feb 2003 Fixed
8.0.2 4218 26 Feb 2003 Fixed
8.0.1 3101 26 Feb 2003 Fixed
8.0.0 2360 26 Feb 2003 Fixed
Description
Executing an UPDATE WHERE CURRENT OF cursor statement in a batch or stored procedure would have caused the server to hang, if the cursor was not updateable and ansi_update_constraints was on. This is now fixed.
Workaround Description
 None



CR:309658
CR Number:   309658
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 4586 20 Feb 2003 Fixed
8.0.2 4217 20 Feb 2003 Fixed
7.0.4 3421 20 Feb 2003 Fixed
Description
Database validation would fail to recognize missing entries in a PK with respect to a FK. Validation was not finding missing entries in a primary key when checking a foreign key. As a result, it was possible to get referential integrity violations while rebuilding a database or index even though validation showed the database was fine. The validation now occurs as documented. That is, for foreign key indexes, validation ensures that the corresponding row exists in the primary table. As a result of this change, database validation may now take longer.



CR:309682
CR Number:   309682
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)
8.0.2 4217 24 Feb 2003 Fixed
Description
When starting the MobiLink Notifier in an environment where the default locale language was either German or French, would have caused the exception "java.util.MissingResourceException". This problem is now fixed. A workaround is to execute java.util.Locale.setDefault( new Locale( "en" ) ) in a static initializer in the first class listed in the StartClasses or by some other mean for changing the default locale for the JVM instance (e.g. setting System.properties in java code or using the -D switch. Please see, Sun's documentation)



CR:309847
CR Number:   309847
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 4589 25 Feb 2003 Fixed
8.0.2 4218 25 Feb 2003 Fixed
Description
An expression such as "x LIKE y" would have caused the server to crash if 'y' evaluated to a string longer than the database page size (approximately). Now, the server will report the error, SQLSTATE_PATTERN_TOO_LONG if 'y' is longer than one page.



CR:310019
CR Number:   310019
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4600 06 Mar 2003 Fixed
8.0.2 4224 06 Mar 2003 Fixed
8.0.1 3105 06 Mar 2003 Fixed
7.0.4 3426 06 Mar 2003 Fixed
Description
The returned value for SQL_DBMS_VER was only displaying the major version of the server that the driver was connected to. For example, for ASA 7.0.4, the string returned was "07.00.0000" and, for Adaptive Server IQ 12.4.3, the string "12.00.0000" was returned.



This has been corrected. For Adaptive Server Anywhere version 7.0.4 the string returned for SQL_DBMS_VER is now "07.00.0004". For Adaptive Server IQ version 12.4.3, the string "12.04.0003" will be returned.



CR:310101
CR Number:   310101
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4592 07 Mar 2003 Fixed
8.0.2 4219 07 Mar 2003 Fixed
8.0.1 3101 07 Mar 2003 Fixed
7.0.4 3423 07 Mar 2003 Fixed
Description
Trying to disable OLE DB Connection Pooling by adding "OLE DB Services = -2" in the connection string of the ASA OLEDB provider, would have caused a "R6025 Pure Virtual Function Call" error, when a second query was executed. This has now been fixed.



CR:310190
CR Number:   310190
Product Name:   UltraLite
Product Component:   UltraLite Schema Painter
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4594 05 Mar 2003 Fixed
8.0.2 4219 05 Mar 2003 Fixed
Description
The collation info in schema files (.usm), required to sort Unicode characters, was corrupt. The schema files generated by ulview, ulinit or ulxml, all showed the same problem. The effect of this was that Unicode strings with non-ascii characters (ie Unicode values >= 128 ) may have had unexpected results; values may have sorted incorrectly, and upper/lower case conversions may have been incorrect. This has now been corrected.



CR:310279
CR Number:   310279
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)
8.0.3 4601 05 Mar 2003 Fixed
8.0.2 4224 05 Mar 2003 Fixed
Description
In certain circumstances, if a sort operation ran out of memory, rows could have been incorrectly omitted from the result of a query. In the case where rows were omitted, the QueryLowMemoryStrategy property would be incremented. This has been fixed.



CR:310304
CR Number:   310304
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.2 4220 05 Mar 2003 Fixed
8.0.1 3102 05 Mar 2003 Fixed
8.0.0 2360 05 Mar 2003 Fixed
7.0.4 3424 05 Mar 2003 Fixed
Description
The documentation incorrectly states that when using the C++ API, storage parameters can be passed to the UltraLite runtime either by using the UL_STORE_PARMS macro or by passing them directly to the ULData::Open method. Actually, using the ULData::Open method is the only way parameters can be passed.



CR:310325
CR Number:   310325
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)
8.0.3 4592 25 Feb 2003 Fixed
8.0.2 4219 25 Feb 2003 Fixed
Description
This change implements a Greek collation, 1253ELL, for the Windows code page 1253. The "collation name" or description is "Code Page 1253, Windows Greek, ISO8859-7 with extensions". When creating a new database in a Greek Windows environment, 1253ELL will be selected automatically if a collation is not specified.



CR:310458
CR Number:   310458
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 546 05 Mar 2003 Fixed
Description
For an outer join query with constant columns on the null-supplying side, the constant columns would not have been set to NULL in null-supplied rows. For example, the result of the query:



select * from employee left outer join (select 102) dt(x) on (emp_id=x)



would have had 102 in the x column of every row. Now, the value 102 appears only for rows where emp_id is 102, and NULL in every other row. The same error occurred for subqueries in the select list. For example:



select * from employee left outer join (select (select first emp_id from employee)) dt(x) on (emp_id=x)



This problem is now fixed.



CR:310577
CR Number:   310577
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 3444 23 Apr 2003 Fixed
8.0.1 3112 23 Apr 2003 Fixed
8.0.2 4245 23 Apr 2003 Fixed
8.0.3 4645 23 Apr 2003 Fixed
9.0.0 1052 23 Apr 2003 Fixed
Description
If dbremote was running in hover mode or if dbmlsync was running on a schedule, and either process was running with the -x switch to rename and restart the transaction log, then after the log was renamed for the first time, neither dbremote nor dbmlsync would have sent changes to the consolidated database until the process was restarted. Now, if the online log is renamed when in hover-mode, the data in the last page is processed and then the log-scanning process is shutdown and restarted.
Workaround Description
 Don't use -x



CR:310616
CR Number:   310616
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4599 05 Mar 2003 Fixed
Description
A failed connection attempt could have returned the error "Server not found" (-100) when there was a failure other than just not finding the server. Now connection failures will return the error "Connection error: %1" (-832), where %1 gives some information about the failure. Creating a debug log file using the LogFile connection parameter usually provides more detailed information about the failure.



Examples of where "Connection error" is now returned where "Server not found" was previously returned include:

dbping -c "links=tcpip" - missing server name

dbping -c "links=tcpip{dobroad=none};eng=myengine" - missing host parameter

dbping -c "links=tcpip{clientport=7777};eng=myengine" - if TCP/IP port 7777 is already in use (eg from a previous connection)

dbping -c "links=tcpip;eng=myengine" - if the machine is out of available TCP/IP ports etc.



The behaviour of links=all was also changed to always attempt the shared memory connection before other links are attempted (to be consistent with links=tcpip,shmem, for example). Previously, if an application had used the connection string including "links=tcpip" and then one including "links=all", the second connection would attempt to connect over TCP/IP before shared memory, but now attempts to connect over shared memory first.



CR:310638
CR Number:   310638
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   4.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4595 06 Mar 2003 Fixed
8.0.2 4221 06 Mar 2003 Fixed
8.0.1 3103 06 Mar 2003 Fixed
8.0.0 2360 06 Mar 2003 Fixed
7.0.4 3425 06 Mar 2003 Fixed
Description
A table containing an indexed numeric column could have become corrupt if the value of the precision option was changed to a value smaller than that of some of the values that existed in the table, and rows containing such values were subsequently modified. This has been fixed.



CR:310640
CR Number:   310640
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)
8.0.3 4615 21 May 2003 Fixed
7.0.4 3432 21 May 2003 Fixed
Description
The ASE compatibility procedure, sp_columns, now orders the result set so as to be in the same order as if run on an ASE system.



CR:310658
CR Number:   310658
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   7.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4601 07 Mar 2003 Fixed
8.0.2 4126 07 Mar 2003 Fixed
8.0.1 3105 07 Mar 2003 Fixed
7.0.4 3426 07 Mar 2003 Fixed
Description
If a database server was started as an NT service, using the LocalSystem account, non-administrative users would still have been able to kill the database server process using the task manager or a command-line based kill program. With this fix, non-administrative users no longer have the ability to kill the database server process.



CR:310700
CR Number:   310700
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)
8.0.3 4628 07 Mar 2003 Fixed
8.0.2 4236 07 Mar 2003 Fixed
8.0.1 3110 07 Mar 2003 Fixed
8.0.0 2360 07 Mar 2003 Fixed
7.0.4 3436 07 Mar 2003 Fixed
Description
When purging locks from the lock table, the lock table entries could have become misordered. It was unlikely that this would have caused problems other than assertions 200300, 200301 or 200302. For this problem to have occurred, there must have been active keyset cursors and the database either must have had more than 1 dbspace, or more than 1,000,000 pages in the system dbspace. This is now fixed.



CR:310709
CR Number:   310709
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)
8.0.3 4596 28 Feb 2003 Fixed
8.0.2 4126 07 Mar 2003 Fixed
Description
Queries containing ANY or ALL subqueries may have returned errors (such as SQLE_CANNOT_OPTIMZE_QUERY). if the ANY/ALL subquery contained aliases on subselects.



For example:

select (select count(*) from R) as A

from T

where 1 <> ALL (select A from S )



This has now been corrected.
Workaround Description
 none



CR:310784
CR Number:   310784
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)
8.0.3 4596 05 Mar 2003 Fixed
8.0.2 4222 05 Mar 2003 Fixed
Description
The persistent index statistics could have been incorrect after an index reorganization. This problem only affected trie-based indexes and has now been fixed.



CR:310792
CR Number:   310792
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4606 18 Mar 2003 Fixed
Description
When running dbconsole, the dialog that opens when right-clicking on a connection and choosing Details, could have opened too high, such that the title bar and some of the buttons and fields were off the top of the screen. This has now been corrected.



CR:310866
CR Number:   310866
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4599 06 Mar 2003 Fixed
8.0.2 4223 06 Mar 2003 Fixed
8.0.1 3105 06 Mar 2003 Fixed
7.0.4 3426 06 Mar 2003 Fixed
Description
ASAProv was returning incorrect string values for database with a UTF8 collation. The UFT8 string values were converted to the required string type(ie DBTYPE_STR, DBTYPE_WSTR or DBTYPE_BSTR), but the null terminator was not being set. This is now fixed by null terminating the string.



CR:310881
CR Number:   310881
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)
8.0.3 4604 12 Mar 2003 Fixed
8.0.2 4226 12 Mar 2003 Fixed
8.0.1 3105 12 Mar 2003 Fixed
8.0.0 2360 12 Mar 2003 Fixed
7.0.4 3429 12 Mar 2003 Fixed
Description
When altering a table involved adding a column with a computed or default value, row locks were obtained which, if table was large, could have caused the operation to fail. The row locks were redundant, since there already was an exclusive schema lock. The row locks are no longer obtained.



CR:310887
CR Number:   310887
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4599 05 Mar 2003 Fixed
8.0.2 4223 05 Mar 2003 Fixed
Description
DBISQL would have reported an internal error, if it was opened from Sybase Central, (Right-click on the database icon and click "Open Interactive SQL"), and a number of statements were executed all at once, followed by an EXIT statement.

For example:



CREATE VARIABLE value INT;

SET value = 1;

EXIT value



It did not matter what the statements did, just that there were more than one, and that the last one was an EXIT.



This problem has been fixed.



CR:310912
CR Number:   310912
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)
8.0.3 4599 06 Mar 2003 Fixed
8.0.2 4223 06 Mar 2003 Fixed
Description
When using the JDBC?ODBC bridge, warnings were not always being reported back to the application.

For example, using DBISQL connected via the JDBC-ODBC bridge, executing the following:



set temporary option ansinull = 'on';

select count(NULL) from dummy;



will cause an warning dialog "null value eliminated in aggregate function". Executing the following statement:



select top 10 * from rowgenerator;



would have return no. This problem has now been fixed.



CR:310932
CR Number:   310932
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)
8.0.3 4599 07 Mar 2003 Fixed
8.0.2 4223 07 Mar 2003 Fixed
Description
Queries containing the NUMBER(*) function and an EXISTS predicate could have returned incorrect values for the NUMBER(*) function, if the EXISTS sub-query was flattened. The incorrect values would have been zero for each row. After this fix, the correct row number is returned.



CR:311055
CR Number:   311055
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)
8.0.3 4630 02 Apr 2003 Fixed
8.0.2 4237 02 Apr 2003 Fixed
Description
If a computed column referenced another column which appeared in a CHECK constraint, the computed column could be incorrectly set to NULL.



For example, the following table definition would have caused the problem:

create table T(

x integer check( 2*x >= 0 ),

y integer COMPUTE (2+x)

)



An UPDATE statement that modified 'x' (to a non-NULL value) would have left 'y' set incorrectly to NULL. This problem has now been fixed.
Workaround Description
 Workaround is to return the computed columns in a query.



CR:311099
CR Number:   311099
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)
8.0.3 4602 12 Mar 2003 Fixed
8.0.2 4225 12 Mar 2003 Fixed
Description
When describing a read only cursor result set of a stored procedure or batch which has references to tables contained in publication articles, the error "QOG_BUILDEXPR: could not build EXISTS" could have been reported. THis is now fixed.



CR:311194
CR Number:   311194
Product Name:   UltraLite
Product Component:   UltraLite for AppForge MobileVB
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4601 07 Mar 2003 Fixed
8.0.2 4224 07 Mar 2003 Fixed
Description
When a table was opened with an index, after column objects for that table had been referenced, may have thrown the error SQLE_METHOD_CANNOT_BE_CALLED.This has now been fixed.



CR:311195
CR Number:   311195
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4629 02 Apr 2003 Fixed
8.0.2 4236 02 Apr 2003 Fixed
8.0.1 3110 02 Apr 2003 Fixed
7.0.4 3437 02 Apr 2003 Fixed
Description
In versions of ASA earlier than 8.0.0, assertions 101201, 104802 and 104803 could have occurred while defragmenting a database log file, if it was in use by a server running with the -m command line option to truncate the log file at a checkpoint. In versions 8.0.0 and later, assertions 100908, 100909 and 104802 could have occurred in this same situation.

When running with the -m option, the log file is truncated at each checkpoint, but this truncation could not have occurred if the file was being defragmented concurrently. This has now been fixed.



Note: Use of the -m switch is not advised, please read the documentation before using this server command line switch. To avoid database file fragmentation, it is recommended that where this option is used, the transaction log be placed on a separate device or partition from the database itself.

It is also not recommended to defragment any database files while they are in use.



CR:311234
CR Number:   311234
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)
8.0.3 4606 19 Mar 2003 Fixed
8.0.2 4226 19 Mar 2003 Fixed
8.0.1 3106 19 Mar 2003 Fixed
7.0.4 3428 19 Mar 2003 Fixed
Description
When connected to a database with a UTF8 collation,ASAProv converts from UTF8 to Unicode. This conversion may have used a wrong string length, which would have caused the run-time heap to have become corrupted. Also, the string buffer was not initialized before converting the UFT8 strings. These problem lead to various failures using VS.Net, and have now been fixed.



CR:311274
CR Number:   311274
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)
8.0.1 3116 05 Mar 2003 Fixed
8.0.2 4127 07 Mar 2003 Fixed
8.0.1 3116 21 May 2003 Fixed
Description
When using database with a Japanese collation, characters with a second byte of \x7d, would have caused a syntax error (ASA error -131) if they appearred in object names in CREATE PROCEDURE/FUNCTION/TRIGGER statements. This problem has been fixed.



CR:311280
CR Number:   311280
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)
8.0.3 4623 31 Mar 2003 Fixed
8.0.2 4234 31 Mar 2003 Fixed
8.0.1 3109 31 Mar 2003 Fixed
7.0.4 3435 31 Mar 2003 Fixed
Description
When querying the datatype of TIME, DATE, or TIMESTAMP columns of an ASA database, the ASA provider returned different values than Microsoft's provider, MSDASQL. This has now been corrected.



CR:311508
CR Number:   311508
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4615 25 Mar 2003 Fixed
8.0.2 4230 25 Mar 2003 Fixed
8.0.1 3107 25 Mar 2003 Fixed
8.0.0 2360 25 Mar 2003 Fixed
7.0.4 3432 25 Mar 2003 Fixed
Description
Binary data imported from an ASCII formatted file would not have been loaded correctly if the data appeared as an unquoted sequence of hex digits, prefixed by "0x". (This is the format generated by DBUNLOAD and DBISQL's OUTPUT statment.) This has now been fixed.
Workaround Description
 Use LOAD TABLE.



CR:311526
CR Number:   311526
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)
8.0.3 4602 07 Mar 2003 Fixed
8.0.2 3105 07 Mar 2003 Fixed
8.0.1 3105 07 Mar 2003 Fixed
Description
Calling SQLFetchScroll or SQLExtendedFetch, with a rowset size of more than 32767 rows, would have failed with incorrect results, if the result set was larger than the rowset. This is now fixed.



CR:311584
CR Number:   311584
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4602 07 Mar 2003 Fixed
8.0.2 4225 07 Mar 2003 Fixed
Description
If any any of the following conditions were true, dbisql, (or any of the administration tools), could have failed to connect to a database:



- the "Connect" dialog was being used

- the JDBC-ODBC bridge was being used

- a value in the "Start line" field contained a blank.



The exact error message varied, depending on what other connection parameters were specified and whether the database server was already running or not. This problem has been fixed. A workaround is to connect using the jConnect driver instead of the JDBC-ODBC bridge. Note, this was a problem in the administration tools, not the JDBC-ODBC bridge per-se.



CR:311704
CR Number:   311704
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 4603 13 Mar 2003 Fixed
8.0.2 4225 13 Mar 2003 Fixed
8.0.1 3105 13 Mar 2003 Fixed
8.0.0 2360 13 Mar 2003 Fixed
Description
When editing table data in the "Results" panel of DBISQL an internal error could have been reported if an existing cell was being edited and an invalid value for the cell was entered, or a new row was added and invalid data was entered in one or more of the cells,

and then a different row was selected by clicking with the mouse or by pressing the UP or DOWN keys. An error message about the invalid data would have ben displayed, and the row selection would change. Attempting to go back to the row with the bad data and correct it would then have caused an internal error. This problem has been fixed. Note, this problem also applied to the ASA plug-in for Sybase Central.



CR:311850
CR Number:   311850
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   4.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4612 18 Mar 2003 Fixed
8.0.2 4229 18 Mar 2003 Fixed
7.0.4 3432 18 Mar 2003 Fixed
Description
When creating a stored procedure which returned a result set and the result set datatypes were not explicitly specified, if one of the result set columns was NUMERIC and the precision of the column was calculated as greater than 128, a server crash would have resulted. This has been fixed. A workaround is to explicitly specify the result set datatypes.



CR:311851
CR Number:   311851
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 4605 13 Mar 2003 Fixed
8.0.2 4226 13 Mar 2003 Fixed
8.0.1 3105 13 Mar 2003 Fixed
8.0.0 2360 13 Mar 2003 Fixed
Description
Scrolling through a trie-based index to before the first row and then scrolling forwards, could have resulted in the scan terminating prematurely. This is now fixed.



CR:311888
CR Number:   311888
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.4 3438 14 Apr 2003 Fixed
Description
A query with a GROUP BY clause that involved concatenation, could have caused a server crash.

Far example:

create table B( city char(20), state char(20));



select city || state

from B

where city || state not in

(select city || state from B

group by city || state);



For the crash to have occurred, the table B must have contained a combination of empty and non-empty strings. This has been fixed.
Workaround Description
 none



CR:312098
CR Number:   312098
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)
8.0.3 4609 14 Mar 2003 Fixed
8.0.2 4229 14 Mar 2003 Fixed
8.0.1 3106 14 Mar 2003 Fixed
8.0.0 2360 14 Mar 2003 Fixed
Description
The server could have attempted to update the wrong database page. If a number of transactions, (two or more), were concurrently reading a page, and one transaction updated the page, there was a very small, but non-zero, chance that it might have updated the wrong page. In many cases this would have resulted in an assertion indicating a page number or page type mismatch. This would likely only have occurred on Unix and multiprocessor (hyperthreaded) NT systems. This is now fixed.



CR:312114
CR Number:   312114
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4607 17 Mar 2003 Fixed
8.0.2 4227 17 Mar 2003 Fixed
Description
Table lists in the Test Script's Options dialog sometimes didn't reflect the current setting of the order of tables for testing. Synchronization tables could have disappeared in both the 'Synchronized Table Order' list and the 'Synchronization Tables' list and thus would have been unable to be selected for testing.



For example, if a few tables were added to the 'Synchronized Table Order' list, OK was clicked in the Options dialog and then the Options dialog was opened again, the selected tables would all applear in the 'Synchronization Tables' list and the tables that were previously in 'Synchronizaton Tables' would have disappared.



This problem has been fixed.



CR:312221
CR Number:   312221
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)
8.0.3 4608 13 Mar 2003 Fixed
8.0.2 4228 13 Mar 2003 Fixed
8.0.1 3106 13 Mar 2003 Fixed
8.0.0 2359 13 Mar 2003 Fixed
7.0.4 3429 13 Mar 2003 Fixed
Description
A permissions problem with derived tables has been fixed.



CR:312222
CR Number:   312222
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)
8.0.3 4637 15 Apr 2003 Fixed
8.0.2 4241 15 Apr 2003 Fixed
Description
If a table in the FROM clause of an EXISTS or IN subquery had a local predicate of the form "T.X = T.Y", the query may have returned an incorrect result set. For this to have happened, T.X or T.Y must be in the select list or be used in another predicate of the form "T.X = outer reference column".



For xample:

select *

from R, S

where R.X IN ( select T.X

from T

where T.X = T.Y )

and S.Z = R.Z



CR:312241
CR Number:   312241
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)
8.0.3 4608 12 Mar 2003 Fixed
8.0.2 4228 12 Mar 2003 Fixed
Description
A PRINT statement could have displayed an unreadable message in the server console or log file if the database's character set(for example utf8) was different from the OS's character set ( for example Japanese CP932 ). This has been fixed.



CR:312345
CR Number:   312345
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
7.0.4 3431 17 Mar 2003 Fixed
12 May 2003 Fixed
Description
If an EXECUTE IMMEDIATE expression in a stored procedure contained a reference to an undefined variable, the server would have crashed.

For example:

CREATE procedure foo( IN tablename varchar(256) )

BEGIN

EXECUTE IMMEDIATE 'SELECT * FROM ' || table_name;

END ;



call foo('DBA.sales_order_items');



The problem has been fixed and a "Column not found" error is now generated.



CR:312388
CR Number:   312388
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)
8.0.3 4628 04 Apr 2003 Fixed
8.0.2 4236 04 Apr 2003 Fixed
7.0.2 1614 04 Apr 2003 Fixed
8.0.1 3110 04 Apr 2003 Fixed
8.0.0 2360 04 Apr 2003 Fixed
Description
Severs running on Win32 multi-processor systems could have hung, crashed or failed with an assertion, due to a bug which allowed two threads to be active simultaneously in a critical section. This issue was unlikely to have appeared on single processor systems. It has now been fixed.



CR:312389
CR Number:   312389
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   8.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4608 17 Mar 2003 Fixed
8.0.2 4228 17 Mar 2003 Fixed
8.0.1 3105 17 Mar 2003 Fixed
Description
When disconnecting from a MobiLink server, the ASA client, dbmlsync, may have crashed, hung, or have issued a spurious error at the end of a synchronization. This is now fixed.



CR:312536
CR Number:   312536
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4609 14 Mar 2003 Fixed
8.0.2 4229 14 Mar 2003 Fixed
8.0.1 3106 14 Mar 2003 Fixed
7.0.4 3431 14 Mar 2003 Fixed
Description
The next available value for a GLOBAL AUTOINCREMENT column could have been set incorrectly in the following situation:

- an INSERT into the table was executed using a value for the column outside the range for the current setting of Global_database_id. This could happen if rows from other databases were downloaded as part of a synchronization.

- the server was shutdown abnormally (e.g. by powering off) before a checkpoint occurred.



The next time the database was started, the next available value for the column would have been set incorrectly. If an INSERT was then attempted with no value provided for the column, the error "Column '<col>' in table '<table>' cannot be NULL" would have been reported. If the database was again shut down and restarted, an INSERT into the table would have attempted to use the first available value in the range for the current setting of Global_database_id. Note that if rows had been deleted from the table, this could result in a value being generated which had previously been used and which might still exist in another database. Resetting the value using sa_reset_identity() would correct the problem, assuming an appropriate value to use can be determined. This problem has now been fixed.



CR:312697
CR Number:   312697
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4622 28 Mar 2003 Fixed
Description
The dbunload utility will now unload a column list to LOAD TABLE statements that it generates in the reload.sql file. This is to facilitate easier reordering of the columns in a table. One can now unload data using dbunload, drop the tables and recreate them with the new column order and the reload.sql can be used to repopulate them.



CR:312857
CR Number:   312857
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4615 26 Mar 2003 Fixed
8.0.2 4230 26 Mar 2003 Fixed
8.0.1 3107 26 Mar 2003 Fixed
7.0.4 3433 07 May 2003 Fixed
Description
A call to SQLMoreResults was returning SQL_NO_DATA_FOUND, instead of SQL_ERROR, when a batch contained a statement with an error. According to the ODBC specification, if one of the statements in a batch fails, and the failed statement was the last statement in the batch, SQLMoreResults should return SQL_ERROR. This has been corrected.



CR:312905
CR Number:   312905
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4614 20 Mar 2003 Fixed
8.0.2 4230 20 Mar 2003 Fixed
7.0.4 3432 20 Mar 2003 Fixed
Description
Fetching more that 200 characters, using the OLEDB provider, into a DBTYPE_BSTR could have left garbage data following the valid column data. This has been fixed.



CR:312906
CR Number:   312906
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4622 21 Mar 2003 Fixed
8.0.2 4233 21 Mar 2003 Fixed
7.0.4 3432 21 Mar 2003 Fixed
Description
The SQL generated by the ASA provider's ITableDefinition and IOpenRowset methods was not being correctly quoted. These methods would have failed if the table name was specified as owner.name or if any object name was a keyword or not a valid identifier. For 7.0.4 only, if ITableDefinition or IAlterTable methods generated SQL that was over 255 characters, these methods could fail. This has been fixed.



CR:312932
CR Number:   312932
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4613 21 Mar 2003 Fixed
8.0.2 4230 21 Mar 2003 Fixed
8.0.1 3107 21 Mar 2003 Fixed
Description
Using statement-based scripts could have caused an ODBC error, if the -zd switch was not used when starting the MobiLink server. The upload_new_row_insert and upload_old_row_insert events were affected by this. This has now been fixed.



CR:312950
CR Number:   312950
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4633 08 Apr 2003 Fixed
8.0.2 4240 08 Apr 2003 Fixed
Description
The following problems, all related to the way DBISQL handled the DBKEY connection parameter, have been fixed.



- DBKEY values which contained number sign ('#') characters were being mangled. This would have prevented connecting to an encrypted database.



- if the DBKEY parameter was specified on the DBISQL command line, but there was not enough information to connect, the Connect dialog was opened, but the Encryption Key field was not filled in. Instead, the DBKEY value appeared in the Advanced Parameters field.
Workaround Description
 Use dbisqlc or configure an ODBC dsn to use in the dbisql connection string as a work around for the time being.



CR:313070
CR Number:   313070
Product Name:   UltraLite
Product Component:   UltraLite for eMbedded Visual Basic
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4615 25 Mar 2003 Fixed
8.0.2 4230 25 Mar 2003 Fixed
Description
The ULPublicationSchema.Mask property was always returning 0. This is now fixed



CR:313144
CR Number:   313144
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Windows CE 2.11
Original Version:   8.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4621 28 Mar 2003 Fixed
8.0.2 4233 31 Mar 2003 Fixed
8.0.1 3109 31 Mar 2003 Fixed
Description
When using the OLEDB driver, (or ODBC), on Windows CE devices, Japanese characters with object names (e.g. table names) having a second byte of \x7b, could have caused access violations or application errors in client applications. A workaround is to use double quotes to quote the object names. This problem is now fixed.



CR:313209
CR Number:   313209
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)
8.0.3 4629 07 Apr 2003 Fixed
8.0.2 4237 07 Apr 2003 Fixed
Description
For very complex WHERE clauses in disjunctive form, new IN predicates are now generated that can be used as sargable predicates. For an IN predicate of the form "T.X IN ( constant_1, constant_2, ...)" to be generated, it is necessary to have in each term of the disjunction, a predicate of the form "T.X = constant_i". In the example below, the query Q1 is transformed into the query Q2 where two new sargable IN predicates were generated.



Example:

Q1:

select *

from T

where (T.X = c1 and T.Y = c2) or

(T.X =c3 and T.Y = c4) or

(T.X = c5 and T.Y = c6) or

(T.X =c7 and T.Y = c8) or

(T.X = c9 and T.Y = c10) or

(T.X =c11 and T.Y = c12)



Q2:

select *

from T

where T.X IN ( c1, c3, c5, c7, c9, c11) and T.Y IN (c2, c4, c6, c8, c10, c12)

and ((T.X = c1 and T.Y = c2) or

(T.X =c3 and T.Y = c4) or

(T.X = c5 and T.Y = c6) or

(T.X =c7 and T.Y = c8) or

(T.X = c9 and T.Y = c10) or

(T.X =c11 and T.Y = c12))
Workaround Description
 Customer has temporary workaround at this point.



CR:313305
CR Number:   313305
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4638 17 Apr 2003 Fixed
8.0.2 4241 17 Apr 2003 Fixed
8.0.1 3111 17 Apr 2003 Fixed
Description
When run on Solaris, the server could have crashed on a CREATE PROCEDURE statement if it included a statement like: UPDATE ... SET ... FROM, and the FROM clause

had more than 4 tables. This has been fixed.
Workaround Description
 Customer found that using 4 table join with subquery worked fine. 5 table join with system tables described fails.



CR:313309
CR Number:   313309
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4617 27 Mar 2003 Fixed
8.0.2 4231 27 Mar 2003 Fixed
8.0.1 3107 27 Mar 2003 Fixed
7.0.4 3433 27 Mar 2003 Fixed
Description
Calling a stored procedure in Visual Basic .Net could have resulted in the error "syntax error or access violation: near '?' " This is now fixed.



CR:313392
CR Number:   313392
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.1 1673 28 Oct 2003 Fixed
9.0.0 1231 28 Oct 2003 Fixed
8.0.3 4819 28 Oct 2003 Fixed
8.0.2 4334 28 Oct 2003 Fixed
Description
If the GA install of SQL Anywhere did not use the default Start Menu folder, (ie Programs\SybaseSQL Anywhere xx), subsequent EBFs would have created this folder. This has been corrected, no folder is created by the EBF.
Workaround Description
 Copy the UltraLite short cuts to the appropriate location after the install is done.



CR:313503
CR Number:   313503
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   7.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4620 27 Mar 2003 Fixed
8.0.2 4232 27 Mar 2003 Fixed
Description
When the dbmlsync command line contained a site or publication name that encoded differently in the remote database, the synchronization would have failed. The problem is now fixed.



CR:313603
CR Number:   313603
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   7.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4620 31 Mar 2003 Fixed
8.0.2 4232 31 Mar 2003 Fixed
8.0.1 3109 31 Mar 2003 Fixed
7.0.4 3434 31 Mar 2003 Fixed
Description
If a sitename contained characters from a Multi-Byte Character Set, dbmlsync would have failed to find the subscription or perhaps crashed. This problem is now fixed.



CR:313686
CR Number:   313686
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)
8.0.3 4621 31 Mar 2003 Fixed
8.0.2 4233 31 Mar 2003 Fixed
Description
If a stored prcedure executed a RAISERROR statement to signal a user defined error, the provider would not have returned the exception to the application. Instead, the application would have received the error "object reference not set to instance of an object". The correct RAISERROR message will now be returned.



CR:313708
CR Number:   313708
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.3 4621 31 Mar 2003 Fixed
8.0.2 4233 31 Mar 2003 Fixed
7.0.4 3434 31 Mar 2003 Fixed
Description
If the fetch of a row from a result set resulted in some sort of error (eg. conversion error), this error was suppressed by the provider and the rowset was marked as having no more rows. Now the error is properly propogated back to the client.



CR:313762
CR Number:   313762
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
04 Apr 2003 Duplicate
Description
The customers application gets assertion 200302





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