远程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:370456
CR Number:   370456
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2944 04 Nov 2004 Fixed
9.0.2 2529 04 Nov 2004 Fixed
9.0.1 1941 04 Nov 2004 Fixed
9.0.0 1384 04 Nov 2004 Fixed
8.0.3 5179 04 Nov 2004 Fixed
8.0.2 4496 04 Nov 2004 Fixed
Description
Executing a VALIDATE TABLE statement, and using the WITH EXPRESS clause, (or dbvalid -fx), would have failed with the error "Not enough memory to start", if the currently available cache space was not large enough. If cache resizing is possible, the server will now try to increase the cache size to the amount required.



CR:370567
CR Number:   370567
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)
2942 01 Nov 2004 Fixed
9.0.2 2529 01 Nov 2004 Fixed
9.0.1 1939 01 Nov 2004 Fixed
9.0.0 1381 01 Nov 2004 Fixed
8.0.3 5177 01 Nov 2004 Fixed
8.0.2 4492 01 Nov 2004 Fixed
Description
The Unload utility dbunload, may have crashed if the command line option -ar (rebuild and replace database) was used with a database that had no online transaction log. This problem has been fixed.



CR:370585
CR Number:   370585
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)
2944 02 Nov 2004 Fixed
9.0.2 2529 03 Nov 2004 Fixed
9.0.1 1941 03 Nov 2004 Fixed
Description
If an HTTP or HTTPS response was more than a few kilobytes in size, and the server was on Unix, NetWare or Windows 95, 98 or Me, the response could have been truncated, contain unexpected data and/or include fatal error text. This was more likely to occur if the server machine was lightly loaded and was faster than the client machine, or the client and server machine were separated by a slow network link. This has been fixed.



CR:370604
CR Number:   370604
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2942 22 Nov 2004 Fixed
9.0.2 2532 22 Nov 2004 Fixed
9.0.1 1951 22 Nov 2004 Fixed
8.0.3 5186 22 Nov 2004 Fixed
8.0.2 4502 22 Nov 2004 Fixed
Description
In ODBC, changing the option for a cursor's scrollability, could have caused the driver to change the cursor type as well. For instance if the cursor type was forward-only, changing the scrollability to scrollable would have changed the cursor type to dynamic. The problem was that the driver was always changing the cursor type to dynamic regardless of the existing cursor type. This has been corrected.



CR:370609
CR Number:   370609
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)
2943 01 Nov 2004 Fixed
9.0.2 2529 01 Nov 2004 Fixed
9.0.1 1940 01 Nov 2004 Fixed
9.0.0 1382 01 Nov 2004 Fixed
8.0.3 5178 01 Nov 2004 Fixed
8.0.2 4493 01 Nov 2004 Fixed
Description
The MobiLink Client dbmlsync, would have complained of an "invalid option ...", if it was started with a configuration file, @filename, and filename contained any extended options specified as

-e opt1="val1";opt2=val2;...

even if all the extended options were valid. This problem is fixed now.



CR:370699
CR Number:   370699
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2943 01 Nov 2004 Fixed
9.0.2 2529 01 Nov 2004 Fixed
Description
Upgrading an ASE or Microsoft SQL Server QAnywhere consolidated database from 9.0.1 to 9.0.2 would have caused all server-side queued messages to have been lost if the server-side message store had at least one message queued (ie. the ml_qa_repository table is non-empty). This has now been fixed.



CR:370712
CR Number:   370712
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2943 01 Nov 2004 Fixed
9.0.2 2529 01 Nov 2004 Fixed
Description
Upgrading an Oracle consolidated database from 9.0.1 to 9.0.2 would have left the stored procedure ml_qa_staged_msg_for_client, instead of dropping it. The undropped procedure wouldn't have affected the behaviour after the upgrade, it just would never have been used. It is now dropped.



CR:370717
CR Number:   370717
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2943 02 Nov 2004 Fixed
9.0.2 2529 02 Nov 2004 Fixed
Description
The setup script for Microsoft SQL Server was missing the last_modified column in the ml_qa_messages view. While this column is not essential, it is useful for debugging and manually tracking when messages change status on the server side. The column has been added.



CR:370722
CR Number:   370722
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2945 05 Nov 2004 Fixed
9.0.2 2529 05 Nov 2004 Fixed
9.0.1 1944 05 Nov 2004 Fixed
Description
The QAnywhere Stop utility qastop, was added in an EBF after the GA release of 9.0.1. The CE EBF installer was updated at the same time to expect qastop to be present. If a subsequent EBF was applied, the installer would have failed, with the following message:

Error: File 'c:\program files\sybase\asa9\ce\arm.30\qastop.exe' not found.

This has been fixed.



CR:370724
CR Number:   370724
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2943 02 Nov 2004 Fixed
9.0.2 2529 02 Nov 2004 Fixed
9.0.1 1940 02 Nov 2004 Fixed
9.0.0 1382 02 Nov 2004 Fixed
8.0.3 5178 02 Nov 2004 Fixed
8.0.2 4493 02 Nov 2004 Fixed
Description
The Unload utility dbunload, would have silently placed old transaction log files into the root directory, when the command line option -ar (rebuild and replace database) was used and no log directory was specified, for databases that were involved in synchronization/replication using RepAgent. Now, if this situation occurs, the old transaction log file will be placed in the log directory of the database.



CR:370726
CR Number:   370726
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2943 02 Nov 2004 Fixed
9.0.2 2529 02 Nov 2004 Fixed
9.0.1 1940 02 Nov 2004 Fixed
Description
The Interactive SQl utility dbisql, would have failed to process statements in a file read by the READ command if the file used UTF8 encoding and the file started with an endian indicator (typically 0xef 0xbb 0xbf on Windows). Now the endian indicator is handled appropriately.



CR:370744
CR Number:   370744
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2946 24 Nov 2004 Fixed
9.0.2 2946 21 Jan 2005 Fixed
Description
In order to run a service under an account other than LocalSystem, that account must have been granted the "Login as a service" privilege. Sybase Central can detect when the account does not have this privilege, ask the user whether to grant it, and grant it if so, but the Create Service utility dbsvc, did not have this ability. Now, dbsvc will ask the whether to grant this privilege, and grant it if so, if the -a (account name to use)command line option is used rather than the -as option, and the account does not have this privilege already.



Notes:

- if the user running dbsvc does not have Administrator privileges, then granting the privilege will fail. However, users without Administrator privileges cannot create services anyway

- if the -y option is used, then dbsvc will attempt to grant the "Login as a

service" privilege without prompting the user



CR:370835
CR Number:   370835
Product Name:   MobiLink
Product Component:   scripts
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2944 02 Nov 2004 Fixed
9.0.2 2529 02 Nov 2004 Fixed
Description
Scripts for upgrading DB2 from 8.0.x and 9.0.0 short schema to 9.0.2, were missing the MobiLink system triggers. This would have resulted in MobiLink not working correctly after an upgrade. There are no scripts for upgrading from 7.0.x and 8.0.0 long schema to 9.0.2, so upgrading from 7.0.x and 8.0.0 long schema to 9.0.2 is not possible. The 9.0.1 upgrade script would not have dropped the old ml_qa_repository_content table. The 8.0.0 upgrade script would not have dropped the old ml_add_lang_connec stored procedure. These have been corrected.



CR:370840
CR Number:   370840
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)
2946 02 Nov 2004 Fixed
9.0.2 2529 03 Nov 2004 Fixed
9.0.1 1944 03 Nov 2004 Fixed
9.0.0 1386 03 Nov 2004 Fixed
Description
Shutting down the server while debugging database objects, would have caused Sybase Central to go to 100% CPU usage. This has been fixed.



CR:370852
CR Number:   370852
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2944 02 Nov 2004 Fixed
9.0.2 2529 03 Nov 2004 Fixed
Description
If an ASA database, created or upgraded to version 9.0.1, was used as a consolidated server for MobiLink with QAnywhere messaging, then attempting to upgrade the database to version 9.0.2 using dbunload would have failed with a conversion error on the reload of the table dbo.ml_qa_repository.



For example, if the database was qanyserv.db, then the following command would fail:



dbunload -c "dbf=qanyserv.db;uid=dba;pwd=sql" -ar .



This problem has been fixed, but there are a couple work-arounds. Rather than using dbunload to upgrade a database from 9.0.1 to 9.0.2 one can use the tool dbupgrad. For example:



dbupgrad -c "dbf=qanyserv.db;uid=dba;pwd=sql"



If unload and reload of the database is required, then another work-around is to run dbunload, and then modify the reload.sql file to remove the reloading of rows into the tables dbo.ml_qa_repository and dbo.ml_qa_repository_props. These rows represent QAnywhere messages, so removing them will cause the reloaded database to lose those messages.



CR:370861
CR Number:   370861
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2944 03 Nov 2004 Fixed
9.0.2 2529 03 Nov 2004 Fixed
9.0.1 1941 03 Nov 2004 Fixed
Description
If a request log file was generated using:



call sa_server_option('Request_level_logging','sql+plan+hostvars');



and a plan string in the request log exceeded approximately 325 bytes, then calling sa_get_request_times to process the resulting file may have resulted in the error:



Primary key for table 'satmp_request_time' is not unique



Whether or not the error was given depended on what other requests were active at the time the statement with the long plan was executed. The request log file will now be output correctly.



CR:370899
CR Number:   370899
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)
2960 19 Nov 2004 Fixed
9.0.2 2533 19 Nov 2004 Fixed
9.0.1 1951 19 Nov 2004 Fixed
8.0.3 5206 18 Jan 2005 Fixed
8.0.2 4512 18 Jan 2005 Fixed
Description
Several race conditions in the server while starting and stopping databases have now been fixed:



- The server could have autostopped a database when it should not have, or not autostopped a database when it should have.



- In rare timing dependent cases, the server could have deadlocked, asserted or possibly crashed, when a database was starting up or shutting down.



Also in rare timing dependent cases, the server could have asserted or possibly crashed if HTTP or HTTPS requests were made to a database that was starting up or shutting down.



CR:370905
CR Number:   370905
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2950 11 Nov 2004 Fixed
9.0.2 2531 11 Nov 2004 Fixed
9.0.1 1946 11 Nov 2004 Fixed
9.0.0 1387 11 Nov 2004 Fixed
8.0.3 5182 11 Nov 2004 Fixed
8.0.2 4498 11 Nov 2004 Fixed
Description
An ODBC application that allocated both an ODBC 2.0 style environment handle and an ODBC 3.0 style environment handle, could have have returned ODBC 3.0 result codes when functions were called in the ODBC 2,0 environment, or vice versa. This could have lead to subsequent function calls failing with erroneous error messages, including 'function sequence error'. Now, the driver will always allocate a separate environment handle each time SQLAllocEnv or SQLAllocHandle is called.



CR:370914
CR Number:   370914
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2945 03 Nov 2004 Fixed
9.0.2 2529 03 Nov 2004 Fixed
Description
The MobiLink Monitor was not able to connect to the synchronization server via HTTPS. This has been fixed.



CR:370998
CR Number:   370998
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2944 03 Nov 2004 Fixed
9.0.2 2529 03 Nov 2004 Fixed
9.0.1 1941 03 Nov 2004 Fixed
9.0.0 1382 03 Nov 2004 Fixed
8.0.3 5178 03 Nov 2004 Fixed
8.0.2 4494 03 Nov 2004 Fixed
Description
The problem addressed by changes for Engineering Case 323973, was reintroduced by the changes for Case 369727.



A server crash at an inopportune moment could have resulted in a corrupt database. This was more likely to have occurred with 9.x servers, and with 8.x servers running 8.x databases. It was unlikely to have occurred with 8.x and earlier servers when running against 7.x or earlier databases.



This has now been fixed.



CR:371032
CR Number:   371032
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2945 05 Nov 2004 Fixed
9.0.2 2529 05 Nov 2004 Fixed
9.0.1 1944 05 Nov 2004 Fixed
9.0.0 1385 05 Nov 2004 Fixed
8.0.3 5179 05 Nov 2004 Fixed
8.0.2 4496 05 Nov 2004 Fixed
Description
If a query referenced both proxy and local tables, or proxy tables from different servers, then it will have to be executed in 'no passthru' or 'partial passthru' mode. If such a query also contained column references of the form 'user.table.column', then the query would have failed with error -845 "Owner '<owner name>' used in qualified column reference does not match correlation name '<table name>'". This problem has now been fixed.



CR:371180
CR Number:   371180
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2943 04 Nov 2004 Fixed
9.0.2 2529 04 Nov 2004 Fixed
9.0.1 1941 04 Nov 2004 Fixed
Description
The server could have failed with assertion 104000 when attempting to execute a query with a large IN list. An IN list of size roughly (1/32)*(page-size)^2 could have generated the assertion failure on 32 bit platforms, and a value half that size would on 64 bit platforms. This has now been fixed, and IN lists are supported up to the available cache memory.



Now, for IN lists bigger than the above limit, the "IN list optimization" is not used, and a virtual table is not introduced. This may result in a sudden performance difference when the IN list size crosses this size threshold. It is not recommended to use very large IN lists.



CR:371202
CR Number:   371202
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2945 05 Nov 2004 Fixed
9.0.2 2529 05 Nov 2004 Fixed
9.0.1 1944 05 Nov 2004 Fixed
Description
The system procedure sa_get_request_times, would have stored a conn_id of 0 in the table satmp_request_time for any connections established before request-level logging was enabled, for the file being processed. If sa_get_request_times was called with a conn_id parameter to limit the information collected from the log, it would not have stored any information for a connection started before logging was enabled. Now, the connection id will match the connection handle value for this situation.



CR:371203
CR Number:   371203
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)
2951 12 Nov 2004 Fixed
9.0.2 2531 12 Nov 2004 Fixed
9.0.1 1946 12 Nov 2004 Fixed
9.0.0 1388 12 Nov 2004 Fixed
Description
A warning message that the server was not licenced for the appropriate number of CPUs on the machine, was being given at each checkpoint. The warning message is now only given at startup.



CR:371373
CR Number:   371373
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Sep 2005 Presently Not Targeted For Any Future Release Of This Product
Description
The customer does not want request level logging in ASA ( -zr -zo ) to log any passwords as this breaches their internal security standards.



The customer is requesting that this feature be added to the engine and not solely to dbisql since they use different means to administer users. We could capture and parse out the password from the "grant connect to..." out of the STMT_PREPARE and the STMT_EXECUTE_IMM and/or STMT_EXECUTE_ANY_IMM before it gets to the parser and then the logger.



CR:371376
CR Number:   371376
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
An EBF install would have created the "Sample Applications and Projects" icon in the default "SQL Anywhere 9" folder, even if the original install used a different folder. This has been corrected.



CR:371389
CR Number:   371389
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2946 09 Nov 2004 Fixed
9.0.2 2529 10 Nov 2004 Fixed
9.0.1 1935 10 Nov 2004 Fixed
Description
When the QAnywhere Agent was set up to use a primary server and a secondary server, and it was performing synchronizations frequently, a failover to the secondary server may have occurred, even though the primary server was reachable. This has been fixed. Two new command line options have now been added: -fr <n>, which specifies the number of retries to connect to the primary server after a connection failure (default 0), and -fd <n>, which is the delay, in seconds, between retry attempts to the primary server (default 0). It is recommended that the retry delay be a relatively small value, perhaps 10 seconds or less.



CR:371411
CR Number:   371411
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)
2946 09 Nov 2004 Fixed
9.0.2 2529 09 Nov 2004 Fixed
9.0.1 1944 09 Nov 2004 Fixed
9.0.0 1386 09 Nov 2004 Fixed
8.0.3 5180 09 Nov 2004 Fixed
8.0.2 4496 09 Nov 2004 Fixed
Description
The isolation level for a transaction was being set to 1 when the connection was opened. Now, the isolation level is no longer set to any specific value. The server default is the value defined for the connection by the database option Isolation_level.



Note, this problem was introduced in the following builds:

8.0.3 5128

8.0.2 4442

9.0.2 2528

9.0.0 1333

9.0.1 1887

The old behavior is now restored



CR:371423
CR Number:   371423
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2946 09 Nov 2004 Fixed
9.0.2 2529 10 Nov 2004 Fixed
9.0.1 1944 10 Nov 2004 Fixed
Description
Ultralite Dynamic SQL would have failed to create a foreign key which referenced the same table as was being created by the CREATE TABLE statement. This has been fixed.



CR:371549
CR Number:   371549
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2965 25 Nov 2004 Fixed
9.0.2 2535 25 Nov 2004 Fixed
9.0.1 1954 25 Nov 2004 Fixed
Description
If a query performed a join between a local table and a remote table with an ON condition, then there was a very good chance that the query would have been processed in 'partial passthru' mode and returned an incorrect result. This problem has now been fixed.



CR:371558
CR Number:   371558
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2949 09 Nov 2004 Fixed
9.0.2 2530 11 Nov 2004 Fixed
Description
When the QAnywhere library is used to receive a message using a transactional manager, it is possible to roll back the receiving of messages. If the receive of a message is rolled back, then the next time the message is received, the Redelivered property of the message (getRedelivered() in C++) should be true. In this situation though, the Redelivered property was always being set to false. The Redelivered property of a message whose receive was rolled back is now correctly set.



CR:371843
CR Number:   371843
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2942 11 Nov 2004 Fixed
9.0.2 2529 11 Nov 2004 Fixed
9.0.1 1939 11 Nov 2004 Fixed
Description
When running an EBF install on Linux or Solaris systems, selecting the Japanese license agreement would have caused the install to exit before applying the EBF. The problem has now ben fixed.



CR:371849
CR Number:   371849
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2955 16 Nov 2004 Fixed
9.0.2 2531 16 Nov 2004 Fixed
9.0.1 1950 16 Nov 2004 Fixed
9.0.0 1388 16 Nov 2004 Fixed
Description
Executing long statements, which contained the CASE keyword, could have caused the Interactive SQL utility dbisql to appear to hang. The statement will eventually execute, but the length of time required will be unreasonably long. This problem does not affect all statements which contained a CASE keyword. This has been corrected.
Workaround Description
 We have found that by changing the way we do comments, we can avoid (on say

build 1922) the problems of the programs hanging.





Or if we don't change the comments



changing from dbisqlg.exe to dbisqlc.exe can avert the problem too. The hanging happens regardless of whether I use the iAnywhere native driver or jConnect in my ISQL session



CR:371856
CR Number:   371856
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)
2950 11 Nov 2004 Fixed
9.0.2 2531 11 Nov 2004 Fixed
9.0.1 1945 11 Nov 2004 Fixed
Description
When doing incremental uploads, dbmlsync was making several errors when estimating the size of the upload. As a result the size of the upload increments were sometimes very different from the size requested using the increment extended option. The following sources of estimation error have been fixed:



1) Blobs were not being included in the estimate of the upload size.

2) When synchronizing a subscription for a user with more than one subscription, some operations were being included in the estimate that were not being uploaded.



CR:371870
CR Number:   371870
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2951 11 Nov 2004 Fixed
9.0.2 2531 11 Nov 2004 Fixed
9.0.1 1946 11 Nov 2004 Fixed
9.0.0 1388 11 Nov 2004 Fixed
Description
When using Server-Initiated Synchronization, the Listener could have hung on shutdown, leaving an unresponsive console. A race condition has been fixed.



CR:371909
CR Number:   371909
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2951 12 Nov 2004 Fixed
9.0.2 2531 12 Nov 2004 Fixed
Description
When running the UltraLite Interactive SQL utility ulisql with the Plan tab selected, executing a query, then disconnecting, then reconnecting again and re-executing the query, would have caused ulisql to crash. This has been fixed.



CR:371911
CR Number:   371911
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2951 15 Nov 2004 Fixed
9.0.2 2531 15 Nov 2004 Fixed
Description
Two problems with the UltraLite Interactive SQL utilitu ulisql, have been fixed. First, statements with carriage returns and tabs had these characters stripped off after they were executed. Recalling the statement would have caused it to have been displayed all on one line. Now the format is preserved. Second, when ulisql was launched, immediately recalling the last command would have incorrectly displayed the second last command.



CR:371930
CR Number:   371930
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2949 11 Nov 2004 Fixed
9.0.2 2531 11 Nov 2004 Fixed
9.0.1 1945 11 Nov 2004 Fixed
Description
It was possible, (although rare, it was more likely on 64 bit Unix systems), that Interactive SQL dbisql, could have crashed when it was being shut down. This has been fixed.



CR:371941
CR Number:   371941
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)
10.0.0 1663 08 Apr 2005 Fixed
9.0.2 3109 08 Apr 2005 Fixed
9.0.1 2011 08 Apr 2005 Fixed
Description
The server command line options -c, -cl, and -ch allow cache sizes and limits to be specified in terms of "percentage of total physical RAM installed in the system". On systems where there was more physical RAM installed than there was address space available to the server process, using percentage notation could have caused the server to attempt to allocate a cache larger than it could possibly allocate. For example, -c75p on a system with 8GB of RAM installed would attempt to create a 6GB cache. Percentage notation for these options are now defined as a percentage of available address space or total physical RAM, which ever is less.



On all 32-bit systems other than Windows, available address space is defined as 2GB less 256MB. On Windows, available address space is computed accurately on startup. Note

that each process on 32-bit Windows is given a total of 2GB of address space (that's an OS and 32-bit architecture limitation) except on Windows 32-bit Advanced Server, Enterprise Server and Datacenter Server, where they are given 3GB of address space in total provided "/3GB /PAE" is in the boot.ini and there is no more than 16GB of RAM installed. Again, these are OS and 32-bit architecture limitations. 32-bit programs running on Windows x64 Edition are given the full 4GB of address space. Available address space is then defined as total address space less address space in use by the database server at startup.



For AWE caches ('-cw' is on the command line), the definition of percentage notation has not changed and remains as a percentage of total physical memory on the system.



CR:371958
CR Number:   371958
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 2531 11 Nov 2004 Fixed
2952 11 Nov 2004 Fixed
Description
Running the Collation utility dbcollat with the -z command line option (specify collation sequence label), can no longer be used to write a collation definition to a file. To get a particular collation definition, a database must now be built with the desired collation, and then dbcollat, without -z, can be run to extract it. The -z option will be removed in a future version of SQL Anywhere.



CR:372064
CR Number:   372064
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2952 15 Nov 2004 Fixed
9.0.2 2531 15 Nov 2004 Fixed
9.0.1 1947 15 Nov 2004 Fixed
Description
When using the MacOS version of Sybase Central to edit a table and clicking in the Data Type or Value column, by default most of the column's width would have been taken up by the "..." button, leaving very little room to see the current value. Now, the button is only as wide as required to show the "..." text.



CR:372065
CR Number:   372065
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2952 15 Nov 2004 Fixed
9.0.2 2531 15 Nov 2004 Fixed
9.0.1 1947 15 Nov 2004 Fixed
Description
When run on MacOS systems, after successfully running a utility wizard that displayed a messages dialog, Sybase Central would needed to have been restarted in order to use the menu bar items. Otherwise, selecting a menu item would have provided no response. This has been fixed.



CR:372069
CR Number:   372069
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2952 15 Nov 2004 Fixed
9.0.2 2531 15 Nov 2004 Fixed
9.0.1 1947 15 Nov 2004 Fixed
Description
In the MacOS version of Sybase Central, attempting to use the ENTER key in a non-editable combo box, to commit the current selection in the drop down list, would have caused the drop down list to be closed, but the current item would not have been selected. This has now been fixed.



CR:372074
CR Number:   372074
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)
2954 16 Nov 2004 Fixed
9.0.2 2531 16 Nov 2004 Fixed
9.0.1 1950 16 Nov 2004 Fixed
Description
If an INSERT .... ON EXISTING statement used DEFAULT in the VALUES clause for any primary key column of the table, the server would have crashed. This has been corrected.



CR:372085
CR Number:   372085
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)
2953 15 Nov 2004 Fixed
9.0.2 2531 15 Nov 2004 Fixed
9.0.1 1948 15 Nov 2004 Fixed
9.0.0 1388 15 Nov 2004 Fixed
8.0.3 5184 15 Nov 2004 Fixed
8.0.2 4499 15 Nov 2004 Fixed
Description
When the Synchronization Client dbmlsync crashed it would have left behind a temporary file, which would never have been deleted. Now, a check is made at startup for any temporary files left from previous runs and deletes them if they exist.



CR:372086
CR Number:   372086
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2950 12 Nov 2004 Fixed
9.0.2 2531 12 Nov 2004 Fixed
9.0.1 1945 12 Nov 2004 Fixed
Description
If a query referenced a procedure in the FROM clause, and the procedure in turn had a query that referenced a remote server, but could not be executed in full passthrough mode, and the query also referenced a procedure variable, then a syntax error could have resulted. This has been corrected.



CR:372098
CR Number:   372098
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2964 23 Nov 2004 Fixed
9.0.2 2529 23 Nov 2004 Fixed
9.0.1 1953 23 Nov 2004 Fixed
8.0.3 5188 23 Nov 2004 Fixed
8.0.2 4502 23 Nov 2004 Fixed
Description
In rare circumstances, an upload could have failed with the error "Unknown Client Error n", where n was some random large number. This error was usually followed by another error reporting that "A protocol error occurred when attempting to retrieve the remote client's synchronization log". Although there are circumstances where this is a valid error to report, an instance where this error was incorrectly reported has now been fixed.



CR:372122
CR Number:   372122
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Linux
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2954 15 Nov 2004 Fixed
9.0.2 2531 15 Nov 2004 Fixed
9.0.1 1949 15 Nov 2004 Fixed
9.0.0 1388 15 Nov 2004 Fixed
8.0.3 5185 15 Nov 2004 Fixed
8.0.2 4500 15 Nov 2004 Fixed
Description
Engineering Case 304975 added support for handling UUID/GUID columns in proxy tables to remote servers. Unfortunately, that change had the side effect of disallowing creation of existing proxy tables with smalldatetime columns. The problem with the smalldatetime column has now been fixed.
Workaround Description
 Short of never using datetime datatypes, or never upgrading to 9.0.1 there appears no

way to avoid this.



CR:372175
CR Number:   372175
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Microsoft Windows 95
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2960 24 Nov 2004 Fixed
9.0.2 2533 24 Nov 2004 Fixed
9.0.1 1951 24 Nov 2004 Fixed
9.0.0 1388 24 Nov 2004 Fixed
8.0.3 5187 24 Nov 2004 Fixed
8.0.2 4502 24 Nov 2004 Fixed
Description
The server could have leaked memory, eventually resulting in an 'Out of Memory' error. This could have occurred while executing INSERT or LOAD TABLE statements for tables which the server maintains statistics. This has been fixed



CR:372181
CR Number:   372181
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)
2954 16 Nov 2004 Fixed
9.0.2 2531 16 Nov 2004 Fixed
9.0.1 1949 16 Nov 2004 Fixed
9.0.0 1388 16 Nov 2004 Fixed
Description
Selecting a table in the tree and then clicking on the Data tab in the right pane, would have caused any attempt to unload either the table's data or the entire database to block, until the unload operation was cancelled and another item was selected in the tree. Note that selecting another tab in the right pane was not sufficient to remove the block. Now, the unload operation will proceed regardless of which tab is selected in the right pane, and there is no need to change the tree selection to proceed with the unload.



CR:372196
CR Number:   372196
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.0 1389 26 Nov 2004 Fixed
9.0.1 1955 26 Nov 2004 Fixed
9.0.2 2453 26 Nov 2004 Fixed
Description
When running on Unix systems, the server could have crashed while shutting down with active TCP/IP connection. This would likely have been very rare, and has now been fixed.



CR:372205
CR Number:   372205
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2959 18 Nov 2004 Fixed
9.0.2 2533 18 Nov 2004 Fixed
9.0.1 1951 18 Nov 2004 Not a Bug
Description
When the Synchronization Server was run using the HTTP stream (ie -x http), a synchronization failure could have caused the server to crash. This has been fixed.



CR:372220
CR Number:   372220
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Novell NetWare
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2995 20 Dec 2004 Fixed
9.0.2 2453 20 Dec 2004 Fixed
9.0.1 1966 20 Dec 2004 Fixed
9.0.0 1393 20 Dec 2004 Fixed
Description
When running on NetWare systems, the ASA server would have stopped executing scheduled events and automatic checkpoints, about 66 hours after the ASA server was started. This has been fixed.



CR:372230
CR Number:   372230
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)
2960 17 Nov 2004 Fixed
9.0.2 2960 21 Jan 2005 Fixed
Description
The reference to "DT2.*" in the following query:



SELECT 1 FROM ( SELECT DT2.* FROM ( select 1 c ) DT1 ) DT2



should have given an error, since it occurred inside the derived table DT2. An error would only have been given if DT2 was specified with a column list. Now, an error will always be reported for this situation.



CR:372231
CR Number:   372231
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2955 16 Nov 2004 Fixed
9.0.2 2531 16 Nov 2004 Fixed
9.0.1 1950 16 Nov 2004 Fixed
9.0.0 1388 16 Nov 2004 Fixed
Description
The server could have deadlocked while running simultaneous queries containing joins of the same tables.



For example, the following might have caused such a deadlock.

select * from a,b where a.a2 = b.b2; //connection 1

select * from a,b where b.b2 = a.a2; //connection 2



This would only have occurred if there was no index or key on the columns a2 and b2. This would most likely have occurred on a multi-CPU machine. This has now been fixed.



CR:372236
CR Number:   372236
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2954 16 Nov 2004 Fixed
9.0.2 2531 16 Nov 2004 Fixed
9.0.1 1949 16 Nov 2004 Fixed
Description
If the QAnywhere JMS connector received a JMS message having a non-null JMSCorrelationID, then the QAnywhere server may have failed to receive the message indicating a NullPointerException. The problem would have occurred even if the JMSCorrelationID did not refer to a QAnywhere message id. This problem has been fixed.



CR:372239
CR Number:   372239
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2954 16 Nov 2004 Fixed
9.0.2 2531 16 Nov 2004 Fixed
Description
An HTTP or web service procedure, or a function with a remote address given in dotted quad notation (e.g., http://192.168.0.1/), may have sometimes failed to resolve, or have resolved incorrectly. This has been fixed.



CR:372262
CR Number:   372262
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2963 22 Nov 2004 Fixed
9.0.2 2534 22 Nov 2004 Fixed
9.0.1 1952 22 Nov 2004 Fixed
9.0.0 1389 22 Nov 2004 Fixed
8.0.3 5188 22 Nov 2004 Fixed
8.0.2 4502 22 Nov 2004 Fixed
Description
Connecting to the MobiLink server immediately after a successful autodial could have failed with error WSAEHOSTUNREACH (10065). The fix is to repeatedly attempt to open the session until it is successful, or the network_connect_timeout expires, default 2 minutes.



CR:372279
CR Number:   372279
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2992 20 Dec 2004 Fixed
9.0.2 2545 20 Dec 2004 Fixed
Description
When opening a cursor for a statement that contained an outer join, it was possible for the server enter an endless loop. For this to have occurred, the table on the null-supplying side had to have a computed column that was a complex expression of some other table columns, and the cursor must have been opened 'for-update' (implying that Ansi_update_constraints was off), and the computed column must have been nested within two outer joins. This problem has been fixed.



For example, the following situation caused the problem:



set option public.ansi_update_constraints = 'off';

create table T1 ( a varchar(10), c varchar(10) compute ( a+'' ) );

create table T2 ( f int );

create table T3 ( z int );



select * from T3 left outer join

( T2 left outer join T1 on T2.f = T1.c )

on T3.z = T2.f

for update;
Workaround Description
 SET OPTION "PUBLIC"."Ansi_update_constraints" = 'ON' (DEFAULT)



CR:372289
CR Number:   372289
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2954 16 Nov 2004 Fixed
9.0.2 2531 16 Nov 2004 Fixed
Description
On PalmOS devices, if a user entered the M-Business Client, and then exited to the home screen without doing anything, it would have crashed. This has now been corrected.



CR:372331
CR Number:   372331
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 1648 05 Apr 2005 Fixed
9.0.2 3103 05 Apr 2005 Fixed
9.0.1 2006 05 Apr 2005 Fixed
8.0.3 5233 05 Apr 2005 Fixed
Description
During synchronization it was possible for a Windows CE device to go into sleep mode. Now the MobiLink client makes system calls to ensure that this does not happen. It is still possible for a device to go into sleep mode during a delay caused by the sp_hook_dbmlsync_delay hook or during the pause between scheduled synchronizations.



CR:372374
CR Number:   372374
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2955 17 Nov 2004 Fixed
9.0.2 2531 17 Nov 2004 Fixed
9.0.1 1950 17 Nov 2004 Fixed
Description
The JMS connectror dead message address is an address to which messages are forwarded if it is determined that the message is undeliverable (for example, the address is not a valid JMS address). If the dead message address was badly formed, (for example, missing an agentid), then the undeliverable message would be queued but would be otherwise unreceivable. Now, if the dead message address is badly formed, the connector will fail to start with an appropriate connector initialization error message. This will ensure messages queued against a dead message address will always be receivable.



CR:372406
CR Number:   372406
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.1 1950 17 Nov 2004 Fixed
Description
Using the QAnywhere Agent with scheduled transmission rules would have resulted in invalid messages being received. This has now been fixed. This was a regression introduced with changes for Engineering Case 371389.



CR:372469
CR Number:   372469
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)
2956 17 Nov 2004 Fixed
9.0.2 2532 17 Nov 2004 Fixed
9.0.1 1950 17 Nov 2004 Fixed
9.0.0 1388 17 Nov 2004 Fixed
Description
If EXECUTE IMMEDIATE WITH RESULT SET ON was used to execute a string representing a multi-statement batch, it would have failed with the error:

Result set not permitted in '<batch statement>'

The batch will now be executed correctly and its result set returned.



CR:372481
CR Number:   372481
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)
2955 17 Nov 2004 Fixed
9.0.2 2531 17 Nov 2004 Fixed
9.0.1 1950 17 Nov 2004 Fixed
9.0.0 1388 17 Nov 2004 Fixed
8.0.3 5185 17 Nov 2004 Fixed
8.0.2 4501 17 Nov 2004 Fixed
Description
The estimate of the rate at which pages are being dirtied has been made less pessemistic (a smoothed version of the estimates used in 7.x). Also, on 32 bit Windows systems, the server now measures the random write times rather than using the cost model estimates, as this caused the estimates to be off by a factor of 50 in some cases.



This is a further performance improvement to the issue originally addressed by Engineering Case 355123.



CR:372484
CR Number:   372484
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.1 1951 18 Nov 2004 Fixed
Description
When the Synchronization Server was run using the HTTP stream (ie -x http), the server could have failed to shutdown in rare cases. This has now been fixed.



CR:372485
CR Number:   372485
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2985 17 Nov 2004 Fixed
9.0.2 2532 17 Nov 2004 Fixed
9.0.1 1950 17 Nov 2004 Fixed
Description
When run on Linux or Solaris systems, the Interactive SQL utilities Import Wizard could have reported an internal error (NullPointerException) if a file was imported in a file format other than ASCII, and the "File type" field was not set to the appropriate type. This has been fixed.



CR:372513
CR Number:   372513
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)
2958 18 Nov 2004 Fixed
9.0.2 2532 18 Nov 2004 Fixed
9.0.1 1950 18 Nov 2004 Fixed
8.0.3 5186 18 Nov 2004 Fixed
Description
The UltraLite Schema painter could have crashed when creating a foreign key. This has been fixed.



CR:372522
CR Number:   372522
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)
2959 19 Nov 2004 Fixed
9.0.2 2959 21 Jan 2005 Fixed
Description
The server could have started processing requests while the HTTP and HTTPS communications links were still being initialized. Now, requests received by the server before it is fully initialized will wait until startup is complete.



CR:372605
CR Number:   372605
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)
2958 19 Nov 2004 Fixed
9.0.2 2532 19 Nov 2004 Fixed
9.0.1 1951 19 Nov 2004 Fixed
8.0.3 5186 19 Nov 2004 Fixed
8.0.2 4502 19 Nov 2004 Fixed
Description
If an application, connected to a server via jConnect, cancelled a request or closed a JDBC statement, the cancel or close could have failed and/or dropped the connection entirely. This problem has been fixed.



CR:372615
CR Number:   372615
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2971 06 Dec 2004 Fixed
9.0.2 2538 06 Dec 2004 Fixed
9.0.1 1957 06 Dec 2004 Fixed
8.0.3 5193 06 Dec 2004 Fixed
Description
When the UltraLite Initialization utility ulinit, was run against a blank padded ASA database, each object (table, column, index, publication etc.) in the generated UltraLite schema was padded by many spaces. Since the 杬 switch on ulinit (specify a table ordering) required a list of tables, ulinit could not properly handle this switch. This has been fixed.



The workaround is to unload and reload the ASA database into a non-blank padded reference database.



CR:372635
CR Number:   372635
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2963 24 Nov 2004 Fixed
9.0.2 2535 24 Nov 2004 Fixed
9.0.1 1955 24 Nov 2004 Fixed
Description
Ultralite Dynamic SQL was failing to respect an ORDER BY clause when there was an index that could have been used to satisfy the ordering and there existed another index that could have been used to optimize the search conditions. This has now been corrected.



CR:372644
CR Number:   372644
Product Name:   UltraLite
Product Component:   HotSync Conduit
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2958 25 Nov 2004 Fixed
9.0.2 2532 25 Nov 2004 Fixed
9.0.1 1950 25 Nov 2004 Fixed
9.0.0 1388 25 Nov 2004 Fixed
Description
When the UltraLite HotSync conduit is loaded by the HotSync Manager (on desktops), it will now attempt to load the plug-in DLL, if the value "PluginDLL" is specified in the following registry key:



Software\Sybase\Adaptive Server Anywhere\<version>\Conduit\<CRID>



where <CRID> is the creator ID that was used in an UltraLite Palm application on the remote. The "PluginDLL" value should be set to the plug-in DLL location.



The conduit plug-in DLL should have the exported function ULCondGetExtraStreamParms specified:



Prototype

bool ULCondGetExtraStreamParms( char * stream_parms, unsigned short buffer_len )



Parameters

stream_parms: Pointer to a buffer in which to return the extra stream parameters.

buffer_len: The length of *stream_parms in bytes.



Remarks

The function should return false on error; otherwise, return true on success. The extra parameters returned will be appended to the existing stream parameters in the UL database.
Workaround Description
 None



CR:372680
CR Number:   372680
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)
2960 22 Nov 2004 Fixed
9.0.2 2960 21 Jan 2005 Fixed
Description
A query that used an outer join inside a lateral derived table may have failed with the error -727 "The optimizer was unable to construct a valid access plan".



Further, if the lateral derived table was flattenable and there was a reference from the null-supplying side of the outer join to a table outside the lateral derived table, then the target of the reference needed to be treated as part of the preserved side. This was not happening, Therefore, the optimizer could, in some cases, choose an incorrect plan with the table in question appearing above the outer join rather than on its preserved side.



Both these issues have now been fixed.



CR:372736
CR Number:   372736
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2971 30 Nov 2004 Fixed
9.0.2 2537 30 Nov 2004 Fixed
Description
If a stored procedure opened a cursor on a declared temporary table, but did not close the cursor before exiting, the server could have crashed when the procedure was called. Failure to close the cursor might have been caused by the procedure exiting due to an error. This has been fixed.



CR:372743
CR Number:   372743
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2960 22 Nov 2004 Fixed
9.0.2 2533 22 Nov 2004 Fixed
9.0.1 1951 22 Nov 2004 Insufficient priority to fix
Description
The QAnywhere JMS connector places a message in the dead-letter queue when it is determined the message is undeliverable. Binary content messages that were placed in the dead-letter queue were losing their content. This has been fixed, such that any new binary messages put in the dead-letter queue will not lose content.



CR:372770
CR Number:   372770
Product Name:   UltraLite
Product Component:   UltraLite.NET
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2960 23 Nov 2004 Fixed
9.0.2 2533 24 Nov 2004 Fixed
Description
String transfers to UltraLite, on Windows CE devices, was slower than neccessary. This has been fixed in the iAnywhere.Data.UltraLite namespace only.



CR:372775
CR Number:   372775
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2960 22 Nov 2004 Fixed
9.0.2 2533 22 Nov 2004 Fixed
Description
On Windows CE systems, an HTTP or web service procedure would have hung when issuing the request to the web server. The procedure would have returned when the web server issued a timeout for the request. This has been fixed.



CR:372785
CR Number:   372785
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2960 22 Nov 2004 Fixed
9.0.2 2533 22 Nov 2004 Fixed
9.0.1 1951 22 Nov 2004 Fixed
Description
HTTP authentication would fail with Microsoft's Internet Security and Acceleration Server 2004. When sending back an authentication challenge, ISA 2004 would send back the HTTP header "Connection: Keep-Alive", even though the client sent the header "Proxy-Connection: close", which caused the client to become confused. This is fixed by having the client ignore connection keep-alive requests.



CR:372800
CR Number:   372800
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.2 2533 23 Nov 2004 Fixed
9.0.1 1951 23 Nov 2004 Fixed
9.0.0 1388 23 Nov 2004 Fixed
Description
When clicking on the "..." button for a table column's data type, the mnemonics would not work initially on the property dialog that appears. This has now been fixed.



CR:372882
CR Number:   372882
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2966 26 Nov 2004 Fixed
9.0.2 2535 26 Nov 2004 Fixed
9.0.1 2535 26 Nov 2004 Fixed
8.0.3 5190 26 Nov 2004 Fixed
8.0.2 4503 26 Nov 2004 Fixed
Description
If a view was created with an owner like: "create view dba.V1 as select c1 from T1" the preserved source of this view (column SOURCE in SYSTABLE) would have contained an space character following the owner; e.g "create view dba .V1 as select c1 from T1".



As well, if a view was created with a "select * ...", the view definition (column VIEW_DEF in SYSTABLE) was unparsed without the space between the "select" and "*"; e.g. "select* ...".



Neither of these errors caused problems in ASA, but did cause problems for Powerdesigner. Both issues have been fixed.
Workaround Description
 turn PRESERVE_SOURCE_FORMAT off will correct view definitions not using a single * as the column list in the select statement



or



one can perform the following steps:



unload DB's structure

In each of the CREATE VIEW statement having the problem, edit out the extra space between the qualifier and the period in the "COMMENT TO PRESERVE FORMAT ON VIEW" section, and change all these to ALTER VIEW statements to reexecute each one of them in an ISQL session



CR:372896
CR Number:   372896
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2963 23 Nov 2004 Fixed
9.0.2 2534 23 Nov 2004 Fixed
Description
The optimizer occasionally recommends indexes that, if created, would degrade query performance. If the Index Consultant detects this case, it discards the query from its analysis. A check for whether a query had been discarded or not was missing from the new Analysis Viewer, which could cause the Index Consultant to fail with a NullPointer exception, making the analysis results unviewable. This has been fixed.



CR:372897
CR Number:   372897
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   8.0.3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2963 23 Nov 2004 Fixed
9.0.2 2534 23 Nov 2004 Fixed
9.0.1 1952 23 Nov 2004 Fixed
8.0.3 5188 23 Nov 2004 Fixed
Description
If a database consisted of more dbspaces other than just the SYSTEM dbspace, and an attempt was made to unload the data from this database to another database with the same structure using the Unload utility dbunload:

DBUNLOAD -d -ac <connection-parameters-to-new-database>

The Unload utility would have attempted to create a dbspace for the new database and would have reported an error if the dbspace already existed. Now, dbunload will not attempt to create dbspaces when reloading into another database if the -d command-line option is used.



CR:372922
CR Number:   372922
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)
2963 23 Nov 2004 Fixed
9.0.2 2534 23 Nov 2004 Fixed
Description
A cast from a domain to an equivalent user type could have been ignored. For example, the following should skip quoting the result of the html_encode()



select xmlelement( name p, cast( html_encode('''') as xml ) )



However, the usertype "xml" is defined as long varchar which happens to be the return type of html_encode(). Therefore, the cast is silently dropped and the quoting happens anyway. This has been fixed.



CR:373028
CR Number:   373028
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)
2964 24 Nov 2004 Fixed
9.0.2 2535 24 Nov 2004 Fixed
9.0.2 2535 24 Nov 2004 Fixed
9.0.1 1953 24 Nov 2004 Fixed
8.0.3 5189 24 Nov 2004 Fixed
8.0.2 4502 24 Nov 2004 Fixed
Description
Stopping a server while a database was in the process of either starting or stopping, could have caused incorrect behaviour, such as the database requiring recovery the next time it is started, or the server asserting, crashing or hanging. Now, server shutdown waits for databases which are not active, to finish starting or stopping before shutting down, and ensures that a database is not stopped twice.



CR:373035
CR Number:   373035
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
8.0.2 4502 24 Nov 2004 Fixed
8.0.3 5198 24 Nov 2004 Fixed
9.0.1 1953 24 Nov 2004 Fixed
9.0.2 2535 24 Nov 2004 Fixed
2964 24 Nov 2004 Fixed
Description
Performing a synchronization that downloaded rows to a table on which a cursor had been opened, could have resulted in the cursor being positioned on an incorrect row following an ABSOLUTE fetch.



UltraLite tries to optimize ABSOLUTE fetches by replacing them with RELATIVE ones (if it thinks it will be more efficient). The algorithm first verifies that no tables in the cursor have been modified, otherwise it does not attempt the optimization. The problem occurred due to the synchronization code not marking the tables as modified. Now they are.



CR:373037
CR Number:   373037
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)
2964 24 Nov 2004 Fixed
9.0.2 2964 21 Jan 2005 Fixed
Description
In rare circumstances, databases using a 1K page size, could have become corrupted during database recovery. This could have resulted in the error 'Unknown device error', an assertion error, or some other error indicating that the server was reading beyond the end of the file. This has now been fixed.



CR:373039
CR Number:   373039
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2964 23 Nov 2004 Fixed
9.0.2 2534 23 Nov 2004 Fixed
9.0.1 1953 23 Nov 2004 Fixed
8.0.3 5188 23 Nov 2004 Fixed
Description
An attempt to create two user-defined types, whose names were the same except for case, in a case sensitive database was permitted. This now results in an error, since these names should always be case insensitive.



Also, dropping a user-defined type required the name to have matching case, in a case sensitive database. This is no longer required.



CR:373086
CR Number:   373086
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2965 24 Nov 2004 Fixed
9.0.2 2535 24 Nov 2004 Fixed
9.0.1 1954 24 Nov 2004 Fixed
8.0.3 5189 24 Nov 2004 Fixed
8.0.2 4502 24 Nov 2004 Fixed
Description
If a JDBC cursor was positioned on a row with a LONG VARCHAR column, then calling ResultSet.getString() on the column would have returned the proper value for the first call, but each subsequent call would have returned NULL if the cursor had not been repositioned. This problem has now been fixed.



CR:373130
CR Number:   373130
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.1 1951 24 Nov 2004 Fixed
9.0.2 2533 24 Nov 2004 Fixed
2965 24 Nov 2004 Fixed
Description
The QAnywhere Agent window did not have a way to be minimized on some Windows CE operating systems. This has been fixed by adding a Hide button to the dialog, similar to the Database Server window.



CR:373157
CR Number:   373157
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)
2965 25 Nov 2004 Fixed
9.0.2 2535 25 Nov 2004 Fixed
Description
The long plan text (i.e. from the plan() function) is currently English only. However, the selectivity source names (e.g. Bounded, Index, etc.) were being displayed in the client language, causing an inconsistent appearance to the plans. This has been fixed so that English only is displayed.



CR:373172
CR Number:   373172
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2966 26 Nov 2004 Fixed
9.0.2 2535 26 Nov 2004 Fixed
9.0.1 1955 26 Nov 2004 Fixed
9.0.0 1389 26 Nov 2004 Fixed
8.0.3 5189 26 Nov 2004 Fixed
8.0.2 4503 26 Nov 2004 Fixed
Description
In the Translate Log File wizard, selecting 'Include trigger generated transactions' and 'Include as comments only', would have included the trigger generated transactions as statements rather than as comments. This has been fixed.
Workaround Description
 dbtran -z still works in 9.0.2 but

not the equivalent function from SCJVIEW



CR:373173
CR Number:   373173
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2966 29 Nov 2004 Fixed
9.0.2 2536 29 Nov 2004 Fixed
Description
Using the index hints "CUSTERED INDEX" or "NO INDEX" in a query could have caused the server to crash, if workload capturing for the Index Consultant had been turned on while the query was executed. This problem has been resolved.



CR:373179
CR Number:   373179
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)
2965 25 Nov 2004 Fixed
9.0.2 2535 25 Nov 2004 Fixed
9.0.1 1954 25 Nov 2004 Fixed
8.0.3 5189 25 Nov 2004 Fixed
Description
If two instances of the SQL preprocessor, sqlpp run at the same time, the generated code may be invalid. The concurrently running preprocesor's could attempt to use the other's temporary file, and silently generate invalid code. This problem has been fixed by including the process pid in the temporary file.



CR:373206
CR Number:   373206
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)
2965 25 Nov 2004 Fixed
9.0.2 2535 25 Nov 2004 Fixed
9.0.1 1954 25 Nov 2004 Fixed
9.0.0 1389 25 Nov 2004 Fixed
Description
In the Table wizard, when specifying a value other than the default for the percentage of free space to be reserved on each page, the 'number of bytes' value displayed was not updated as the percentage was changed. This has now been fixed.



CR:373215
CR Number:   373215
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2966 30 Nov 2004 Fixed
9.0.2 2536 30 Nov 2004 Fixed
Description
Ultralite Dynamic SQL could have produced incorrect results when the left table expression of a LEFT OUTER JOIN contained multiple INNER JOIN expressions. This has been fixed.



CR:373248
CR Number:   373248
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)
2966 26 Nov 2004 Fixed
9.0.2 2535 26 Nov 2004 Fixed
9.0.1 1955 26 Nov 2004 Fixed
8.0.3 5189 26 Nov 2004 Fixed
Description
When creating a foreign key with the UltraLite Schema Painter, the table for which the foreign key is being created (the table doing the referencing) was not listed as a table that could be referenced. This has been fixed, self-referencing foreign keys can now be created.



CR:373250
CR Number:   373250
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2966 26 Nov 2004 Fixed
9.0.2 2535 26 Nov 2004 Fixed
9.0.1 1955 26 Nov 2004 Fixed
8.0.3 5189 26 Nov 2004 Fixed
Description
When creating a foreign key with one of the UltraLite utilities (Schema Painter, ULXML, ulload, ulcreate, ulconv or ulisql), the application could have crashed, if the foreign key referenced a table that had a self-referencing foreign key. This is now fixed.



CR:373253
CR Number:   373253
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)
2964 26 Nov 2004 Fixed
9.0.2 2534 26 Nov 2004 Fixed
9.0.1 1953 26 Nov 2004 Fixed
Description
When a table was removed from a query using the QueryEditor, the generated query statement was not updated to reflect the change. This has been fixed.



Note, this same problem affected the QueryEditor in Sybase Central, and is fixed as well



CR:373254
CR Number:   373254
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)
2965 26 Nov 2004 Fixed
9.0.2 2535 26 Nov 2004 Fixed
9.0.1 1955 26 Nov 2004 Fixed
Description
When the QueryEditor was opened with a query with SELECT FIRST *, the query would have been changed to SELECT *. 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等等。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------