远程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:444418
CR Number:   444418
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3267 12 Oct 2006 Fixed
10.0.0 2718 12 Oct 2006 Fixed
Description
The TYPE clause for a SQL Anywhere web service client has been extended to allow the specification of a mime type. The value of the mime type specification is used to set the Content-Type request header and set the mode of operation to allow only a single call parameter to populate the body of the request. At most one parameter may remain when making a web service stored procedure (or function) call after parameter substitutions have been processed. Calling a web service procedure with a null or no parameter (after substitutions) will result in a request with no body and a content-length of zero.



The behaviour has not changed if a mime type is not specified. Parameter names and values (multiple parameters are permitted) are url encoded within the body of the http request.



Examples:



call sa_make_object( 'procedure', 'setmime' );

alter procedure setmime( val long varchar, mime long varchar, anurl long varchar)

url '!anurl'

type 'http:post:!mime';



from dbisql:

call setmime('hello, this is plain text', 'text/plain', 'http://localhost/someservice'); // POST body is not url encoded, it contains hello, this is plain text, Content-Type: text/plain

call setmime('<hello>this is xml</hello>', 'text/xml', 'http://localhost/someservice'); // POST body is not url encoded, it contains <hello>this is xml</hello>, Content-Type: text/xml

call setmime(null, 'text/plain', 'http://localhost/someservice'); // POST body is empty, Content-Type: text/plain, Content-Length: 0



- SQL Syntax of TYPE clause for create/alter stored procedure



HTTP:POST[:type/subtype]



- Error checking



Minimum error checking is provided for the mime type specification. A mime type specifier must contain a slash character. The colon delimiter may be padded on both sides by one or more spaces. Only a single parameter (after parameter substitutions) may contain the value used to populate the body of the HTTP request.



CR:444429
CR Number:   444429
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3271 12 Oct 2006 Fixed
10.0.0 2729 12 Oct 2006 Fixed
9.0.2 3389 12 Oct 2006 Fixed
Description
Web service SOAP client calls could have used temporary file pages without releasing them, with at most one page would have been leaked per SOAP request. The visible result of this leak was that the temporary file could slowly grow in size over time when SOAP client calls were made. Since the leaked pages were left in the cache, the effective size of the cache would also have decreased over time. This has been fixed.



CR:444436
CR Number:   444436
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   5.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3290 16 Nov 2006 Fixed
10.0.0 2755 16 Nov 2006 Fixed
9.0.2 3407 16 Nov 2006 Fixed
Description
The SQL preprocessor sqlpp could have generated incorrect code if the following two statements were one after the other:

EXEC SQL SELECT ... INTO <hostvar list>;

EXEC SQL DROP ...;



The DROP would have been missing from the generated. This has been fixed.



CR:444438
CR Number:   444438
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2729 12 Oct 2006 Fixed
Description
If one or more remote columns were changed to be not synchronized, by selecting the columns in the column mapping editor and then selecting the File -> Synchronize menu item, there would not have been the same warning that was shown when the corresponding Synchronize check boxes were unchecked. This has been fixed so that the same warning is displayed in both situations.



CR:444457
CR Number:   444457
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)
10.0.1 3271 16 Oct 2006 Fixed
10.0.0 2729 16 Oct 2006 Fixed
9.0.2 3389 16 Oct 2006 Fixed
Description
If the server displayed the message: "Cannot create stream controller thread" on startup, it may not have been possible to connect to a server in this state, and applications that were able to connect may have received communication errors. This error only occurred if the server ran out of address space (approximately 2GB of address space is available on 32bit Windows operating systems). This has been fixed so that the server will now fail to start if this error occurs. When this error occurs, the maximum cache size should be reduced by at least 10MB.



CR:444467
CR Number:   444467
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3271 12 Oct 2006 Fixed
10.0.0 2728 12 Oct 2006 Fixed
Description
If a character variable was bound to a numeric output parameter of a procedure, and the numeric value being returned by the procedure ended in two or more zeroes, the output value assigned to the variable may have been a single "?" character. A problem with the function that calculated precision and scale has been corrected.



CR:444472
CR Number:   444472
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 19 Oct 2006 Fixed
10.0.0 2735 19 Oct 2006 Fixed
9.0.2 3393 19 Oct 2006 Fixed
8.0.3 5455 19 Oct 2006 Fixed
Description
Using Interactive SQL with the -q command line option ("Suppress non-critical messages"), would have caused all messages to be suppressed. This was not correct, and has been fixed. Now, error messages are displayed regardless of whether -q is used or not.



CR:444473
CR Number:   444473
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3299 16 Oct 2006 Fixed
10.0.0 2736 16 Oct 2006 Fixed
Description
The DESCRIBE statement would have reported that a database object (ie table, view, procedure etc) could not be found if its name contained a tilde (~) character. This has been fixed.



CR:444498
CR Number:   444498
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3271 13 Oct 2006 Fixed
10.0.0 2730 13 Oct 2006 Fixed
9.0.2 3389 13 Oct 2006 Fixed
Description
The UltraLite stream objects, reader and writer, were not being released correctly when ResultSet pods object is closed. This memory leak has now been fix.



CR:444560
CR Number:   444560
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3359 25 Jan 2007 Fixed
10.0.0 2796 25 Jan 2007 Fixed
Description
If the Java VM was started, and then at a later time an attempt to execute an ALTER or DROP DBSPACE it would have failed with the error: "Not allowed while 'user' is using the database', where "user" was the userid of the Java main connection. This problem has now been fixed.



CR:444561
CR Number:   444561
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3272 13 Oct 2006 Fixed
10.0.0 2730 13 Oct 2006 Fixed
Description
DETACH TRACING did not fully clean up connections established via ATTACH TRACING. After several thousand ATTACH TRACING calls, any further connections would have been denied, and the message "Out of StreamPool objects. Failed to create a new connection." would have appeared in the console. This has been fixed.



CR:444592
CR Number:   444592
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3272 16 Oct 2006 Fixed
10.0.0 2491 16 Oct 2006 Fixed
Description
String expressions formed from a large number of concatenations could have resulted in a stack overflow when the expression was evaluated. The number of concatenations required to see the failure was very large; while platform dependant, it was on the order of many thousands. This condition was more likely to manifest itself on UNIX platforms than on Windows. This has been fixed.



CR:444594
CR Number:   444594
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3273 25 Oct 2006 Fixed
10.0.0 2495 25 Oct 2006 Fixed
Description
The entry fields in the Install Key dialog allowed the entry of more than 5 characters, which would usually result in an invalid Install Key. This has been fixed by ignoring key presses if there are 5 characters already in the field.



CR:444614
CR Number:   444614
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3272 16 Oct 2006 Fixed
10.0.0 3272 12 Mar 2007 Fixed
Description
Synchronizations via HTTP could have failed, apparently at random. The frequency of these failures would have been very low. This has been fixed.



CR:444627
CR Number:   444627
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3389 16 Oct 2006 Fixed
Description
Simple SELECT queries may have had a less than optimal query plan, which may have resulted in poor performance. A bypass cursor has built for queries that selected from a single table, even if the WHERE clause referenced only some of the columns of the primary key with equality predicates. This has been fixed.



CR:444743
CR Number:   444743
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)
10.0.1 3273 16 Oct 2006 Fixed
10.0.0 2733 16 Oct 2006 Fixed
Description
A new MobiLink server HTTP stream option, called session_key, has been added. This option determines how the MobiLink server tracks non-persistent HTTP sessions (i.e. when the MobiLink client specifies 'persistent=0'). The option is used as follows:



mlsrv10 ... -xo http(...session_key=[cookie|header];...) ...



When the session_key is 'cookie', which is the default, an HTTP cookie with name JSESSIONID is used to track HTTP sessions. When the session key is 'header', an HTTP header is used. The 'header' option is useful if the cookie name of JSESSIONID conflicts with an existing cookie, in which case MobiLink will track HTTP synchronizations using a custom header entry that will not conflict with any other HTTP infrastructure. In order to implement this feature in the MobiLink server, changes were also required to the MobiLink client. Thus to get the new behaviour, clients need to be upgraded as well.



Note, the session_key option is supported by the -xo option only.



CR:444758
CR Number:   444758
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3273 16 Oct 2006 Fixed
10.0.0 2733 16 Oct 2006 Fixed
9.0.2 3390 16 Oct 2006 Fixed
Description
When run on Windows CE, if the server executable was located on a filesystem controlled by the Intel Persistent Storage Manager (IPSM), typically rooted at the \IPSM directory, then the server and the Windows CE device could have hung. The hang only occurred while writing data to a non-database file which is also located on the IPSM, such as the server output log (-o command line option), and was due to a problem with the IPSM driver. A work around to this problem has been implemented. Moving non-database files to RAM is a workaround.



The following is a copy of the IPSM bug description from Intel:



Note that other ASA components or 3rd party applications which might write compiled-in strings to a file on IPSM will also be susceptible to this bug. For 3rd party applications (or for ASA components prior to this fix), the user can avoid the problem by copying the executables & DLLs into the RAM disk or onto another flash device and running them from there instead of from IPSM.



CR:444770
CR Number:   444770
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3273 17 Oct 2006 Fixed
10.0.0 2733 17 Oct 2006 Fixed
Description
It was possible, although likely rare, for the server to crash after applying a transaction log, but before shutting down. The database file produced would still have been valid. A race condition in the server has been fixed.



CR:444896
CR Number:   444896
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 20 Oct 2006 Fixed
10.0.0 2735 20 Oct 2006 Fixed
9.0.2 3392 20 Oct 2006 Fixed
Description
The performance of unprepared commands was slower than prepared commands when calling ExecuteNonQuery. This problem has been fixed.



CR:444897
CR Number:   444897
Product Name:   MobiLink
Product Component:   Streams
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3390 18 Oct 2006 Fixed
Description
The changes for Engineering case 426484 would have caused the server to silently ignore client requests if clients were upgraded to a version with the change, but the server was not. This has been fixed so that newer clients with this change can synchronize with servers that have not yet been upgraded to a version with the change. Thus to solve this problem, the server must be upgraded to build 3342 or later, or the client must be upgraded to build 3390 or later.



CR:444898
CR Number:   444898
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3552 14 Mar 2007 Fixed
9.0.2 3410 11 Sep 2007 Fixed
Description
The server may have crashed when using cached plans in nested procedures. This crash would have been rare, and was likely to appear only when there was heavy competition for cache memory. This has been fixed.



CR:444904
CR Number:   444904
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   7.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3392 19 Oct 2006 Fixed
Description
When the MobiLink server was listening for HTTP or HTTPS connections, it would have silently ignored invalid connections/requests. It now displays an error for each invalid request.



CR:444919
CR Number:   444919
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3273 18 Oct 2006 Fixed
10.0.0 2734 18 Oct 2006 Fixed
Description
When the Interactive SQL utility opens a file, it scans the file to determine the character encoding used. If that encoding is different from the encoding used by the operating system, a dialog is opened which allows selecting the encoding to be used when reading the file. There is a "(Default)" encoding which means that the system character encoding is used. Opening a file could have failed if the file was not encoded in the system file encoding, and "(Default)" was explicitly selected in the "Open File" dialog. This has been fixed.



CR:444924
CR Number:   444924
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3275 17 Oct 2006 Fixed
10.0.0 2733 17 Oct 2006 Fixed
Description
A query that used a full index scan without predicates on a prefix of the index, but with predicates on other index columns, could have crashed the server. This has been fixed.



CR:444926
CR Number:   444926
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   8.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3266 18 Oct 2006 Fixed
Description
The dbisqlc utility would have failed to connect to a server if the option sql_flagger_error_level was set to any value except 'W' (Allow all supported syntax). This has been fixed by setting the option to 'W' temporarily on startup.



CR:444936
CR Number:   444936
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3283 06 Nov 2006 Fixed
10.0.0 2751 06 Nov 2006 Fixed
Description
An attempt to display the dialog giving the option to re-enter an install key or to install the evaluation version, which is displayed when an invalid install key is entered in the Install Key dialog, would have generated a non-fatal missing string error. This has been fixed.



CR:444941
CR Number:   444941
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   7.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3273 18 Oct 2006 Fixed
Description
Attempting to create an event with a non-recurring schedule that had a start time in the past, would have caused the error: "Invalid start date/time for event '<event-name>'". This has been fixed so that now the following error message is displayed:



You cannot create a non-recurring schedule with a start time

in the past, since such a schedule can never trigger an event.

You must either specify a recurrence interval and/or days,

or change the start time to a time in the future.



CR:444986
CR Number:   444986
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3273 19 Oct 2006 Fixed
10.0.0 2735 19 Oct 2006 Fixed
Description
SELECT expressions, which were not just a reference to a column, could have been improperly evaluated when the cursor was not read-only, and when temporary tables were involved. This has been fixed. The work-around is to add the FOR READ ONLY clause to the SELECT statement.



CR:445021
CR Number:   445021
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3280 31 Oct 2006 Fixed
10.0.0 2749 31 Oct 2006 Fixed
Description
The syshistory logging entries for DTT and LAST_DTT did not include the correct detail

information for dbspaces other than SYSTEM. For non-SYSTEM dbspaces, the detail information of the main dbspace was entered. If the drive type was "UNKNOWN", the detail information was incorrectly deleted when moving a LAST_DTT to DTT. This has now been fixed.



CR:445035
CR Number:   445035
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 19 Oct 2006 Fixed
10.0.0 2497 19 Oct 2006 Fixed
Description
On Unix systems, specifying an IPv6 address with the MYIP parameter would have caused the server to fail to start. For IPv4 addresses, when listening on a UDP port Unix requires that you listen on the broadcast address, not the actual address. However, for IPv6 addresses, you must listen on the actual address. This has been fixed.



CR:445042
CR Number:   445042
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Windows CE 2.11
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 25 Oct 2006 Fixed
10.0.0 2745 25 Oct 2006 Fixed
9.0.2 3395 25 Oct 2006 Fixed
Description
On Windows CE systems, the MobiLink client could have crashed when the QAnywhere agent was shut down. This has been fixed.



CR:445043
CR Number:   445043
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 27 Oct 2006 Fixed
10.0.0 2744 27 Oct 2006 Fixed
Description
The use of indexes may have caused poor query peformance when the server was under heavy load. This has been corrected.



CR:445049
CR Number:   445049
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 19 Oct 2006 Fixed
10.0.0 2735 19 Oct 2006 Fixed
9.0.2 3393 19 Oct 2006 Fixed
Description
If an EXECUTE IMMEDIATE statement was used to execute a string representing a compound statement having a single executable statement and an exception handler, the exception handler would have been ignored. This has been fixed. Adding a RETURN before the EXCEPTION would be a work around.



CR:445050
CR Number:   445050
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3280 31 Oct 2006 Fixed
10.0.0 2749 31 Oct 2006 Fixed
Description
An INSERT statement may use a work table in order to provide the required semantic guarantees. In such cases, it was possible for autoincrement columns to be incremented by 2 instead of by 1. The consequence of this would be gaps in the values inserted into autoincrement columns. This has now been fixed.



CR:445062
CR Number:   445062
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 19 Oct 2006 Fixed
10.0.0 2735 19 Oct 2006 Fixed
9.0.2 3393 19 Oct 2006 Fixed
Description
Typically, ResultSet.getBlob() is used to retrieve columns of type long binary, however, there is no reason an application cannot use the getBlob() method to retrieve a column of type VARBINARY or BINARY. Unfortunately, getBlob() did not work properly for columns of type VARBINARY or BINARY. This problem has now been fixed.



CR:445065
CR Number:   445065
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3277 18 Oct 2006 Fixed
10.0.0 2503 18 Oct 2006 Fixed
Description
The MobiLink server could have crashed if the number of columns in a table uploaded from a remote client did not match the number of columns defined in the ml_column table. Now, the error: "The number of columns in client table <table name> does not agree with the number defined in ml_column" is displayed, and the synchronization is aborted.



CR:445069
CR Number:   445069
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 19 Oct 2006 Fixed
10.0.0 2735 19 Oct 2006 Fixed
9.0.2 3393 19 Oct 2006 Fixed
Description
If a statement representing a query was dropped before the cursor using it was closed, the system procedure sa_get_request_times() could have reported a time for the statement which was too low. The sa_get_request_times() procedure calculates statement duration using the enter and exit times for a subset of the requests associated with that statement. Individual FETCH requests are not considered, since request logs frequently do not contain that level of detail. For queries, most of the time occurs between OPEN and CLOSE, so sa_get_request_time() calculates the difference between the enter time for the OPEN and the exit time for the CLOSE and adds that to the total for the statement. While processing the log, it only keeps track of statements which it considers "active". It discards its knowledge of a statement when it sees a DROP for the statement. Many (if not most) applications perform queries using the following sequence:

PREPARE

DESCRIBE

OPEN

FETCH ...

CLOSE

DROP



While the server can handle the statement being dropped before a cursor using that statement is closed, sa_get_request_times() could not. This has been fixed.



One possible workaround is to remove the lines representing the statement DROP from the request log before calling sa_get_request_times(). Assuming that statement handles are not re-used within the request log, this should allow the correct times to be obtained.



CR:445072
CR Number:   445072
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 20 Oct 2006 Fixed
10.0.0 2735 20 Oct 2006 Fixed
Description
If an UltraLite client attempted to connect to a server that was in the process of shutting down, there was a small possibility that the connection attempt would hang. This has been fixed.



CR:445185
CR Number:   445185
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   7.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3273 19 Oct 2006 Fixed
10.0.0 2734 19 Oct 2006 Fixed
Description
When the MobiLink server was listening for HTTP or HTTPS connections, it would have silently ignored invalid connections/requests. It now displays an error for each invalid request. This has been fixed, but only affects the -xo command line option. The -x option already displays one of a number of different HTTP errors when an invalid connection/request comes in, so no fix is needed for it.



CR:445186
CR Number:   445186
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 20 Oct 2006 Fixed
Description
An attempt to convert a value from a numeric domain to a binary domain would have resulted in a conversion error. For example, the statement

select cast( cast( 17 as numeric(5,2) ) as varbinary )

would result in error -157: "Cannot convert numeric to a varbinary." This has been fixed.



CR:445193
CR Number:   445193
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 20 Oct 2006 Fixed
10.0.0 2736 20 Oct 2006 Fixed
9.0.2 3393 20 Oct 2006 Fixed
Description
Calling the method SACommand.ExecuteNonQuery with invalid parameter values, could have caused an NullReferenceException to be thrown. This problem has been fixed.



A C# example:



SAConnection conn = new SAConnection("dsn=SQL Anywhere 10 Demo;uid=dba;pwd=sql");

conn.Open();



SACommand cmd = new SACommand( "DELETE FROM Departments WHERE DepartmentID = ?", conn );

cmd.Parameters.Add( "p1", SADbType.Integer );

cmd.Parameters[0].Value = "xxx";



int rowsAffected = cmd.ExecuteNonQuery();



CR:445195
CR Number:   445195
Product Name:   MobiLink
Product Component:   Sample
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 20 Oct 2006 Fixed
10.0.0 2498 20 Oct 2006 Fixed
Description
The CustDB sample was registering unsynchronized columns in the ml_column table. This has been fixed. In order to fully implement this fix, the CustDB consolidated database(s) must be rebuilt, as an accompanying fix to the MobiLinl server will cause synchronizations to fail. To do this, go to the %SQLANY10%\samples\UltraLite\CustDB directory and run newdb.bat.



CR:445212
CR Number:   445212
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3284 09 Nov 2006 Fixed
10.0.0 2752 09 Nov 2006 Fixed
Description
When executong a LOAD TABLE statement, if the server read a UTF16 or UTF8 data file that contained a byte order mark (BOM) as the first character, the BOM would have been interpreted as column data, rather than being skipped. If the first column contained numeric data for example, a conversion error would have been reported. If the first column contained string data, the BOM would have been included as part of the first string value for that column. This has been corrected by skipping BOMs.



Note that SQL Anywhere just skips over the BOM even for UTF16. It does not currently allow the BOM to control the endian-ness of the data in the file (it is always assumed to be in platform endian). BOMs in UTF8 are meaningless but the Unicode standard does allow them. Some utilities such as Notepad on Windows put a BOM into files encoded in UTF8.



For detailed information on BOMs, see http://unicode.org/unicode/faq/utf_bom.html.



CR:445219
CR Number:   445219
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 20 Oct 2006 Fixed
10.0.0 2736 20 Oct 2006 Fixed
9.0.2 3393 20 Oct 2006 Fixed
Description
When the ULPod method ResultSetSchema.close() was called, the UltraLite runtime object ResultSetSchema was released twice. This may have caused rare crashes to have occurred. This has been fixed.



CR:445246
CR Number:   445246
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 20 Oct 2006 Fixed
10.0.0 2736 20 Oct 2006 Fixed
Description
If a Java stored procedure fetched a numeric InOut or Out variable from JAVA, the numeric value returned could have been a '?', instead of the actual value.



Note, this problem is a side effect of the changes made for Engineering case 443233. Both this problem, and the original problem for case 443233, have now been resolved.



CR:445341
CR Number:   445341
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3275 20 Oct 2006 Fixed
10.0.0 2738 20 Oct 2006 Fixed
Description
The row number on the Results tab could have been clipped (i.e. shown the first digit followed by an ellipsis), if the "Show multiple result sets" option was on and the result set contained thousands of rows. This has been fixed.



CR:445367
CR Number:   445367
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3275 20 Oct 2006 Fixed
10.0.0 2738 20 Oct 2006 Fixed
Description
When unloading a database using the Unload utilty, Sybase Central, or through the dbtools 'DBUnload()' function, the unloading application (i.e., dbunload, Sybase Central, or caller of DBUnload()), could have crashed. This would only have happened with the "verbose" option set to ON (such as would be the case with an unload from Sybase Central, or with the -v option of dbunload). This has now been fixed.



CR:445369
CR Number:   445369
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3275 20 Oct 2006 Fixed
10.0.0 2738 20 Oct 2006 Fixed
9.0.2 3393 20 Oct 2006 Fixed
Description
If an INSERT ... SELECT query involved both remote and local tables, and the table being inserted into was a view, then the query would have failed with a "column not found" error. This problem has now been fixed.



CR:445373
CR Number:   445373
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3275 20 Oct 2006 Fixed
10.0.0 2738 20 Oct 2006 Fixed
Description
The Interactive SQL utility could have crashed on startup if a badly-formed TrueType font was installed on the machine. This has been fixed.



CR:445374
CR Number:   445374
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 25 Oct 2006 Fixed
10.0.0 2745 25 Oct 2006 Fixed
Description
The MobiLink Contact sample had incorrect columns in the ml_column table. This caused the MobiLink server to assign incorect values to named parameters, which caused uploads to fail. The script 'build_consol.sql' has been corrected. In order to implement the fix, the Contact sample must be rebuilt by running the clean step followed by the build step.



CR:445378
CR Number:   445378
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3275 23 Oct 2006 Fixed
10.0.0 2738 23 Oct 2006 Fixed
Description
Importing binary data into an UltraLite database using the Interactive SQL utility could have failed to load correctly. The UltraLite ODBC driver was not treating SQL_VARBINARY as the same as SQL_BINARY, so binding a parameter as SQL_VARBINARY would have caused no data to be loaded. This has now been fixed.



CR:445382
CR Number:   445382
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3277 26 Oct 2006 Fixed
10.0.0 2746 26 Oct 2006 Fixed
9.0.2 3395 26 Oct 2006 Fixed
Description
The server now makes use of direct I/O on Solaris, AIX, and Linux sytems where possible. If direct I/O is not available the server will revert to using synchronized I/O data integrity completion as before. Using direct I/O will significantly improve some disk operations, such as extending a databse or transaction log file.
Workaround Description
 None.



CR:445429
CR Number:   445429
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3284 23 Oct 2006 Fixed
10.0.0 2753 23 Oct 2006 Fixed
Description
The MobiLink Monitor would only have shown statistics for one synchronized table. The server was passing a truncated table_id to the Monitor. This has been fixed.



CR:445439
CR Number:   445439
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3275 23 Oct 2006 Fixed
10.0.0 2739 23 Oct 2006 Fixed
Description
The UltraLite runtime could have crashed when attempting the execute a query with IN or ANY operators that used a subquery. This was corrected.



CR:445529
CR Number:   445529
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3278 27 Oct 2006 Fixed
10.0.0 2519 27 Oct 2006 Fixed
Description
If a row had a wide index entry (i.e. many columns or a single long column, or some combination), and one of the columns that was part of that entry was updated, there was a chance that the index would have been corrupted. If the update happened to be rolled back, the corruption would typically have been removed. This could only happened on non-catalog, non-temporary, base tables. This has been fixed.



CR:445540
CR Number:   445540
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3271 23 Oct 2006 Fixed
10.0.0 2488 23 Oct 2006 Fixed
Description
On Unix systems, the iAnywhere ODBC Driver Manager always loaded the threaded version of the ODBC driver, regardless of whether it was being used by a threaded or a non-threaded application. This has been fixed.



CR:445542
CR Number:   445542
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3264 23 Oct 2006 Fixed
10.0.0 2488 23 Oct 2006 Fixed
Description
Applications (including SA utilities) initiated with the locale set to EUCJP, or with the charset connection parameter containing a value greater than 19 characters, would have failed to connect. This has been fixed.



CR:445543
CR Number:   445543
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3393 23 Oct 2006 Fixed
Description
When run on HP-UX systems, connection attemps using TCPIP would have failed when using the single threaded 32-bit client libraries. This problem has been corrected.



CR:445544
CR Number:   445544
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3306 01 Dec 2006 Fixed
Description
If a database which uses dbspaces is started and one of its dbspaces cannot be found, executing an "ALTER DBSPACE ... RENAME" will now cause the server to attempt to open the dbspace after the catalog has been updated. If the dbspace cannot be opened, it will remain inaccessible and no error is returned. Previously, the dbspace would not be accessible until the database had been restarted. An application can determine if a dbspace is open by examining the result of db_extended_property('FileSize','<dbspace-name>'). If the result is NULL, the dbspace is not open.
Workaround Description
 None.



CR:445546
CR Number:   445546
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 24 Oct 2006 Fixed
10.0.0 2743 24 Oct 2006 Fixed
9.0.2 3394 24 Oct 2006 Fixed
Description
Calling an SA client SOAP procedure, from within the Interactive SQL utility, may have returned unexpected HTML encoded data within the result set. Some characters were being displayed in their html encoded form (i.e. an apostrophe (') as '). This has been fixed.



CR:445559
CR Number:   445559
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 26 Oct 2006 Fixed
10.0.0 2747 26 Oct 2006 Fixed
Description
When creating indexes in UltraLite databases, the maximum hash size for the index can be specified, although the full hash size specified might not be needed to accurately represent an index value. For example, if the maximum hash size is set to 6 and the index is one integer column, only 4 bytes is required. UltraLite should only use the number of bytes required up to the maximum value specified, but was using the maximum hash size specified instead of the potentially lesser value of what was required. So, if a maximum hash size of 6 was specified for an index of only one column, 6 bytes was used instead of only 4. This would waste 2 bytes for every index entry, leading to pages that are not as full as could be. This has been fixed so that new indexes created will only use the space needed for them. For compatibility reasons, existing indexes continue to use the hash size with which they were created (they will continue to potentially waste space). Existing databases can be unloaded and reloaded to take full advantage of this fix.



CR:445568
CR Number:   445568
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 23 Oct 2006 Fixed
10.0.0 2742 23 Oct 2006 Fixed
Description
Calling the ODBC function SQLTables() returns a result set of table owners, table names, and table types. When SQLTables() was called with SQL_ALL_TABLE_TYPES it should have returned a result set with a list of all possible table types, but "SYSTEM VIEW" and "MATERIALIZED VIEW" were missing. Support for these two new types was missing, but has now been added.



CR:445570
CR Number:   445570
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3267 23 Oct 2006 Fixed
10.0.0 2482 23 Oct 2006 Fixed
Description
While do a Linux install, if only x86_64 (64-bit) components were installed, sa_config.sh and sa_config.csh were not be generated. This has been fixed.



Note, the Linux Itanium install is not affected by this problem.



CR:445586
CR Number:   445586
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 24 Oct 2006 Fixed
10.0.0 2743 24 Oct 2006 Fixed
Description
The changes for Enginering case 444112 caused connection attempts using connection strings with errors in the TCPIP parameter to return SQLCODE -100 'Database server not running', rather than the correct SQLCODE -832 'Connection error: ...'. This has been

corrected.



CR:445593
CR Number:   445593
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 24 Oct 2006 Fixed
10.0.0 2743 24 Oct 2006 Fixed
Description
If there was a fatal startup error, and the MobiLink server was running in a GUI, the MobiLink server would not have displayed an error dialog. This has been fixed.



CR:445626
CR Number:   445626
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3477 10 Apr 2007 Fixed
10.0.0 2832 10 Apr 2007 Fixed
9.0.2 3479 10 Apr 2007 Fixed
Description
Attempting to start a database with the wrong log file could have failed with the error "Unable to start specified database: ??? belongs to a different database". This has been fixed so that the log file name now correctly appears in the error message.



CR:445675
CR Number:   445675
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 24 Oct 2006 Fixed
10.0.0 2745 24 Oct 2006 Fixed
Description
When the server was run on Windows CE devices, database unload progress messages could have been truncated when the database collation used a multi-byte charset. This has been fixed.



CR:445677
CR Number:   445677
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 24 Oct 2006 Fixed
10.0.0 2745 24 Oct 2006 Fixed
9.0.2 3395 24 Oct 2006 Fixed
Description
Interactive SQL could have reported an internal error if an accelerator key (e.g. CTRL+N) was used while it was busy (e.g. saving a file). This has been fixed.



CR:445684
CR Number:   445684
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   9.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 24 Oct 2006 Fixed
10.0.0 2503 24 Oct 2006 Fixed
9.0.2 3395 24 Oct 2006 Fixed
Description
On NetWare, certain operations were slower than in previous ASA versions. Particularly, operations which involved processing many rows for each row returned in the result set were noticeably affected. This has been fixed so that the performance of these operations has been improved.



CR:445688
CR Number:   445688
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 24 Oct 2006 Fixed
10.0.0 2743 24 Oct 2006 Fixed
Description
For messages coming from a JMS system, the QAnywhere JMS connector now maps the JMSTimestamp header to a message property of the QAnywhere message with name "JMSTimestamp" and type LONG. Also, in this case, the message property "ias_Timestamp" of the QAnywhere message is set to the time that the QAnywhere message is created.



CR:445695
CR Number:   445695
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)
10.0.1 3276 24 Oct 2006 Fixed
10.0.0 2745 24 Oct 2006 Fixed
Description
A QAnywhere client application wass not be able to get a message that had been received, but not acknowledged, and for which the expiry time had passed. This has been fixed. Now, QAnywhere clients can always get, or browse messages, that had been received at least once before the expiry time has passed.



CR:445707
CR Number:   445707
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)
10.0.1 3276 26 Oct 2006 Fixed
10.0.0 2745 26 Oct 2006 Fixed
9.0.2 3395 26 Oct 2006 Fixed
Description
The Interactive SQL utility could have crashed if it was closed while executing a statement if all of the following were true:



- it was running as a windowed application

- a .SQL file had been opened,

- the file had been modified in the "SQL Statements" field,

- the file had not yet been saved,

- when prompted whether to save the file or not, the "Yes" button was clicked.



This has been fixed.



CR:445710
CR Number:   445710
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3274 24 Oct 2006 Fixed
10.0.0 2735 24 Oct 2006 Fixed
9.0.2 3392 24 Oct 2006 Fixed
Description
The default value of SACommand.UpdateRowSource has been changed from UpdateRowSource.Both, to UpdateRowSource.OutputParameters. This change can improve the performance of SADataAdapter.Update. If the value of SACommand.UpdateRowSource is UpdateRowSource.OutputParameters, the provider will call ExecuteNonQuery to update rows. If the value is UpdateRowSource.Both, ExecuteDataReader is called to update rows.



CR:445714
CR Number:   445714
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3276 24 Oct 2006 Fixed
10.0.0 2745 24 Oct 2006 Fixed
Description
Interactive SQL could have crashed, following an attempt to execute a statement if the server had previously closed the connection, and the "auto_commit" option was ON. This has been fixed



CR:445741
CR Number:   445741
Product Name:   UltraLite
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3277 25 Oct 2006 Fixed
10.0.0 2746 25 Oct 2006 Fixed
Description
The Initialize Database utility ULINIT, would have failed with an internal syntax error when processing a UNIQUEIDENTIFIER column that had a DEFAULT of NEWID(). This has been fixed. The work around is to drop the DEFAULT in the reference database, then run ULINIT to create an UltraLite database, and then go back and restore the DEFAULT.



CR:445836
CR Number:   445836
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3277 25 Oct 2006 Fixed
10.0.0 2746 25 Oct 2006 Fixed
9.0.2 3395 25 Oct 2006 Fixed
Description
In the dbisqlc Statistics window, messages such as "execution time xx.yyy seconds..." could have had an incorrect number of seconds. This has been fixed so that xx.y seconds is now reported (i.e. seconds including tenths), and this time is accurate.



CR:445847
CR Number:   445847
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)
10.0.1 3277 25 Oct 2006 Fixed
10.0.0 2746 25 Oct 2006 Fixed
9.0.2 3395 25 Oct 2006 Fixed
Description
On Unix systems, if the environment variable ASTMP (9.0) or SATMP (10.0) contained a path, where the final two or more component directories did not exist, client utilities would have crashed on startup with the error message "Failed to create directory '<path>': No such file or directory". This has been fixed.



Note that the network server is not affected by this.



CR:445855
CR Number:   445855
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   5.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3277 25 Oct 2006 Fixed
10.0.0 2746 25 Oct 2006 Fixed
Description
When run on Windows XP, Sybase Central could have crashed on startup if a custom desktop theme was being used, and this theme supplied its own resource file for system bitmaps that did not contain equivalents for all of the usual system bitmaps. This has been fixed so that when this situation is detected, it will not attempt to use the missing bitmaps.



CR:445878
CR Number:   445878
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   5.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.0 2746 26 Oct 2006 Fixed
Description
Creating a table, then selecting the table's node in the tree, and answering "yes" to save it, would have resulted in a NullPointerException. This has been fixed.



CR:445879
CR Number:   445879
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3277 26 Oct 2006 Fixed
10.0.0 2746 26 Oct 2006 Fixed
Description
When deploying a synchronization model the generated calls to the ml_add_column stored procedure could have been in the wrong order, leading to synchronization errors. This has been fixed so that the generated calls to ml_add_column now occur in the same order as the column order in the remote database. A workaround is to deploy to a SQL file for the consolidated database, and edit the file so that the ml_add_column calls are in the same order order as the columns in the remote database.



CR:445898
CR Number:   445898
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3277 26 Oct 2006 Fixed
10.0.0 2747 26 Oct 2006 Fixed
9.0.2 3454 20 Feb 2007 Fixed
Description
When inserting a negative value into a column with an autoincrement default, the error callback function is called if one was registered with the runtime. The error passed to the callback was SQLE_OVERFLOW_ERROR however, no error would have been signaled when checking immediately after the Insert call. This has been fixed so that no error is now raised at all.



CR:445966
CR Number:   445966
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3277 26 Oct 2006 Fixed
10.0.0 2744 26 Oct 2006 Fixed
Description
If the extended option DownloadOnly was set to 'ON', the MobiLink client would not have sent authentication parameters specified by the -ap optiion to the MobiLink server. Authentication parameters were being sent for normal synchronizations. This has now been fixed.



CR:445997
CR Number:   445997
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3277 27 Oct 2006 Fixed
10.0.0 2747 27 Oct 2006 Fixed
Description
An application using jConnect could have caused a server crash when calling a stored procedure. This has been fixed.



CR:446001
CR Number:   446001
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3279 30 Oct 2006 Fixed
10.0.0 2744 30 Oct 2006 Fixed
Description
The MobiLink client could have crashed whenever a synchronization was attempted if no communication address were specified for connecting to the Mobilink server, such that the default values were used. This would have occurred when the 'log_sent' and 'progress' columns in the syssync table were not equal, and the 'progress' column did not equal the 'created' column. The crash would normally have occurred after a synchronization failed during the upload phase of synchronization. This has been fixed.



CR:446003
CR Number:   446003
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)
10.0.1 3277 27 Oct 2006 Fixed
10.0.0 2747 27 Oct 2006 Fixed
9.0.2 3396 27 Oct 2006 Fixed
Description
Importing text files encoded with UTF-8, using the INPUT command, would have failed if the file had a 3 byte endian header. This has been fixed.



Note that some text editors (e.g. Notepad) write the 3 byte header, but others do not.



CR:446050
CR Number:   446050
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3278 30 Oct 2006 Fixed
10.0.0 2744 30 Oct 2006 Fixed
Description
Stored procedures that execute a very large number of of simple statements, such as control statements, could have run slower than earlier versions of the server. This performance problem has been resolved.



CR:446052
CR Number:   446052
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3278 30 Oct 2006 Fixed
10.0.0 2747 30 Oct 2006 Fixed
Description
When the Unload utility, or Sybase Central, ws used to rebuild a database that was running on a server on a different physical machine, the rebuild could have failed. This has now been fixed. This would only have happened when the -an option (create a new database and reload), or the Sybase Central equivalent, was specified. Also, because rebuilding a pre-10.0 to 10.0 database requires that dbunload be on the same machine as the database being rebuilt, this problem only happened when rebuilding a 10.0 database.



CR:446064
CR Number:   446064
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3278 30 Oct 2006 Fixed
10.0.0 2747 30 Oct 2006 Fixed
Description
Validating an index could have caused a server crash if the index was concurrently being updated. Checks were missing to see if a page had changed across a context switch. This has been fixed.



CR:446066
CR Number:   446066
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3398 31 Oct 2006 Fixed
Description
The Backup utility would have given a poor error message when backing up a database with one or more missing dbspaces. It would have reported the following messages:



Database backup not started

Database backup failed



These messages were not very informative. This has been fixed so that the following messages are now displayed:



Backup is unable to open database file '<file name>'

Database backup failed



CR:446067
CR Number:   446067
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3280 31 Oct 2006 Fixed
10.0.0 2510 31 Oct 2006 Fixed
Description
If an external stored procedure had OUT or INOUT parameters of type SMALLINT, then the result of these parameters could have been interpreted incorrectly for negative values. For example, the comparison "x < 0" could have failed even though the parameter x was assigned a negative value. This has been fixed,



CR:446094
CR Number:   446094
Product Name:   MobiLink
Product Component:   Java Plugin for Sybase Central
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3278 30 Oct 2006 Fixed
10.0.0 2748 30 Oct 2006 Fixed
Description
When a new remote database was created, based on an Oracle database with DATE columns, the SQL Anywhere or UltraLite remote database would have had DATE columns. However Oracle's DATE type includes time information which would have been lost when downloading to the remotes. This has been fixed. Now new remotes have TIMESTAMP columns for Oracle DATE columns in the consolidated. This will cause a warning about timestamp precision mismatch unless the remote database is changed to have the same timestamp precision as Oracle's DATE type. This is not done automatically in Model Mode when Oracle TIMESTAMP columns are also being synchronized.



If time information is important, then you should consider changing DATE columns to TIMESTAMP columns in your Oracle database.



CR:446220
CR Number:   446220
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3471 09 Nov 2006 Fixed
10.0.0 2752 09 Nov 2006 Fixed
9.0.2 3403 09 Nov 2006 Fixed
9.0.1 2195 08 Jan 2007 Fixed
Description
Calling a stored procedure that did not return a result set, could have caused a "cursor not open" error. This problem has been fixed.



CR:446233
CR Number:   446233
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3281 02 Nov 2006 Fixed
10.0.0 2750 02 Nov 2006 Fixed
9.0.2 3398 02 Nov 2006 Fixed
Description
It was possible that some components could have generated errors, or created files with invalid names, when using files with names that had missing attributes. For example, backing up a database and transaction log, where the log file had no extension (ie. demo as opposed to demo.log), could have generated an error that the log file could not be backed up and that the backup failed. This has been fixed.
Workaround Description
 Use the extension .log when initializing the database.



CR:446241
CR Number:   446241
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3282 06 Nov 2006 Fixed
10.0.0 2750 06 Nov 2006 Fixed
Description
If a DELETE trigger referenced values from the NEW row, it was possible for the server to have crashed. This has been fixed; attempts to set values in the NEW row result in an error.



CR:446243
CR Number:   446243
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3280 01 Nov 2006 Fixed
10.0.0 2748 01 Nov 2006 Fixed
Description
The network protocol option network_name did not work on Windows CE. This has been fixed.



CR:446262
CR Number:   446262
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3280 31 Oct 2006 Fixed
10.0.0 2748 31 Oct 2006 Fixed
Description
The Import Wizard would have displayed text data which contained escape sequences incorrectly in the preview table. For this to occur, the imported data must have been ASCII formatted, and the data had to contain an escape sequence (e.g. "\0x0a"). This has been fixed.



CR:446269
CR Number:   446269
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3281 03 Nov 2006 Fixed
10.0.0 2750 03 Nov 2006 Fixed
9.0.2 3398 03 Nov 2006 Fixed
Description
Interactive SQL could have run out of memory when it executed a SQL file. Running into this problem would have been more likely if the the SQL file was large and run in batch mode from a command-line, the "-onerror continue" command line option was used, or the script included an equivalent SET OPTION statement in the SQL file itself, and executing the SQL file caused tens or hundreds of thousands of errors to be reported. This is now fixed.



CR:446387
CR Number:   446387
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3280 31 Oct 2006 Fixed
10.0.0 2749 31 Oct 2006 Fixed
Description
If the QAnywhere client was started with scheduled policy, after previously being started with a short (< 5 seconds) schedule interval, it could have failed to start, and issued an internal error 'ml_qa_sync_event_0 in use'. This has been fixed.



CR:446388
CR Number:   446388
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3280 31 Oct 2006 Fixed
10.0.0 2750 31 Oct 2006 Fixed
Description
The Import Wizard was not consistently providing default widths for columns when importing a file into a new table. The problem was that only a limited set of data types were getting default values. This has been fixed.



CR:446393
CR Number:   446393
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Generic
Original Version:   10.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 3280 31 Oct 2006 Fixed
10.0.0 2750 31 Oct 2006 Fixed
Description
When MobiLink was running a QAnywhere connector and then shut down, some JDBC connections to the consolidated database were not closed. This has been fixed so that all JDBC connections used by QAnywhere connectors are now closed when MobiLink is shut down.





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