远程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:686036
CR Number:   686036
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Solaris
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3468 05 Oct 2011 Fixed
12.0.0 2743 05 Oct 2011 Fixed
11.0.1 2688 05 Oct 2011 Fixed
Description
Attempting to make a Remote Data Access connection to an Oracle database, using an ODBC driver other than the iAnywhere Oracle ODBC driver, could have caused the server to crash when running on a Unix system. This problem has now been fixed.



CR:686039
CR Number:   686039
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3466 04 Oct 2011 Fixed
11.0.1 2685 04 Oct 2011 Fixed
Description
After sending the upload and applying the download, UltraLiteJ sends a message to the server telling it the synch is complete. If there was a network error while sending this message, it would have been reported to the application, implying the sync had failed even though the download was applied correctly. This has been fixed and now the application no longer gets an error if the sync otherwise succeeded.



CR:686040
CR Number:   686040
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3465 03 Oct 2011 Fixed
11.0.1 2685 03 Oct 2011 Fixed
Description
UltraLiteJ could have caused the MobiLink server to report spurious protocol errors in the MobiLink server log. This has been fixed.



CR:686041
CR Number:   686041
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)
11.0.1 2685 03 Oct 2011 Fixed
Description
The MobiLink server would have reported an unnecessary protocol error when the first command of a request was a NOOP. This has been corrected.



CR:686057
CR Number:   686057
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3467 03 Oct 2011 Fixed
Description
An optional ias-rs-status-refresh-sec query parameter has been added to the status url for controlling the auto refresh rate of the status page. A refresh interval of 0 means auto refresh is not wanted and users are expected to use the refresh button on the browser to refresh the status. The following information was also added to the status page:

- Service start time in UTC.

- Status capture time in UTC.

- Status refresh interval, or indication that manual refresh is expected.



CR:686183
CR Number:   686183
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3471 07 Oct 2011 Fixed
12.0.0 2745 07 Oct 2011 Fixed
11.0.1 2689 07 Oct 2011 Fixed
Description
If an application using the UTF8 character set connected via jConnect or Open Client to a blank padded non-UTF8 database and fetched a non-nullable char(n) value, then the returned value would have been blank padded to n*3 bytes. This problem has now been fixed.



CR:686202
CR Number:   686202
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3476 17 Oct 2011 Fixed
11.0.1 2693 17 Oct 2011 Fixed
Description
For recurring scheduled events, there were several errors in how end times were computed:

1. If an end-time was specified (i.e., "BETWEEN start-time AND end-time"), then:

a. Seconds were being ignored. For example, an end-time of '23:59:59' was being interpreted as '23:59:00'.

b. The end-time was tested as an exclusive endpoint rather than an inclusive endpoint, contrary to the documentation of the BETWEEN ... AND clause. For example, the schedule "BETWEEN '9:00' AND '17:00' EVERY 60 MINUTES" would cause the event to fire last at 16:00, rather than 17:00.



2. If an end-time was not specified (i.e., "START TIME start-time"), the end-time for each day was implicitly being treated as '23:59:00' exclusive, instead of '23:59:59' inclusive.



The combined effect of these error were that no scheduled events would fire in the minute from 23:59:00 until midnight. This has been fixed.



CR:686203
CR Number:   686203
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3468 04 Oct 2011 Fixed
12.0.0 2743 04 Oct 2011 Fixed
11.0.1 2688 04 Oct 2011 Fixed
Description
Cancelling an external environment call call immediately after making the external call, could in very rare cases have caused the server to crash. This problem has now been fixed.



CR:686204
CR Number:   686204
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3469 04 Oct 2011 Fixed
12.0.0 2743 04 Oct 2011 Fixed
11.0.1 2688 04 Oct 2011 Fixed
Description
Cancelling an external environment call that was in the process of returning a large result set, could in very rare cases have caused the server to crash. This problem has now been fixed.



CR:686237
CR Number:   686237
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3468 05 Oct 2011 Fixed
12.0.0 2743 05 Oct 2011 Fixed
11.0.1 2688 05 Oct 2011 Fixed
Description
Relay Server web server extensions may have crashed if the URL contained redundant leading forward slashes. This has been fixed.



CR:686304
CR Number:   686304
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3478 18 Oct 2011 Fixed
12.0.0 2749 18 Oct 2011 Fixed
11.0.1 2696 18 Oct 2011 Fixed
Description
When SQL Anywhere components were running in the isolated session 0 (ie, the services session) of Vista and later Windows operating systems, but were not actually running as services, the components could have attempted to display GUI elements. Due to session 0 isolation, these GUI elements were not accessible to users. To execute as a non-service within session 0, the program was likely to have been launched as a child of a service. On Vista and later versions of Windows, SQL Anywhere components now suppress GUI components when running in session 0 rather than just when running as a service.



CR:686407
CR Number:   686407
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3487 26 Oct 2011 Fixed
11.0.1 2701 26 Oct 2011 Fixed
Description
In rare cases where a primary server lost its connections to both the mirror and the arbiter servers as a checkpoint was performed, the next time the primary and mirror servers were connected and attempted to synchronize, the mirror server may have reported the error: 'Database "<name>" mirroring: database is not compatible with primary; files must be replaced' and then stop with the message: 'Database server shutdown due to incompatible files for database mirroring'. This has been fixed so as to reduce the possibility of this occurring. In rare cases this could still occur and the database running on the current primary must be manually copied or backed up to the mirror server so that the server can successfully synchronize again.



Note, this extends the changes made by Engineering case 660851.



CR:686409
CR Number:   686409
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)
12.0.1 3470 06 Oct 2011 Fixed
12.0.0 2744 06 Oct 2011 Fixed
11.0.1 2689 06 Oct 2011 Fixed
Description
If an IPv6 address that included a port number was specified in square brackets, rather than parenthesis, the server or client libraries would not have parsed it correctly. For example, if a connection string included ";HOST=[<ipv6_addr>]:<port>", the error "No IP address found for [<ipv6_addr>]:port." This has been fixed.



Note, this applies to addresses in connection strings (using the LINKS or HOST parameters), the -x and -xs switches on the server, and URLs in web service procedures.



CR:686415
CR Number:   686415
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3470 06 Oct 2011 Fixed
12.0.0 2744 06 Oct 2011 Fixed
11.0.1 2689 06 Oct 2011 Fixed
Description
Relay Server shutdown may have taken unnecessarily long, or even crashed. This would have occurred if the shutdown was requested when a new client session was waiting for backend server assignment while all Outbound Enablers of the backend farm had been disconnected. This has been fixed.



CR:686428
CR Number:   686428
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3507 21 Nov 2011 Failed
Description
In a mirroring system, it was possible for multiple servers to deadlock, waiting for responses from each other. This has been fixed.



CR:686501
CR Number:   686501
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3471 07 Oct 2011 Fixed
12.0.0 2745 07 Oct 2011 Fixed
Description
Debug logging level 3 or higher would have produced logging of OE_UPCHANNEL_CONNECT packets with the oei field equal to "older than 12.0". This is misleading and the packet doesn't contain such a field. The misleading information has been removed.



CR:686519
CR Number:   686519
Product Name:   UltraLite
Product Component:   UltraLite for M-Business Anywhere
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3491 01 Nov 2011 Fixed
12.0.0 2755 01 Nov 2011 Fixed
Description
Calling PreparedStatement.setBytesParameter would have truncated a byte array with more than 32k elements. This has been fixed.



Note, it is recommended that large binary parameters be set using PreparedStatement.appendBytesParameter().



CR:686524
CR Number:   686524
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3471 07 Oct 2011 Fixed
12.0.0 2745 07 Oct 2011 Fixed
Description
The SQL Anywhere Monitor was incorrectly reporting the total disk space as the current Relay Server log's file size. This has been fixed.



CR:686561
CR Number:   686561
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3471 07 Oct 2011 Fixed
12.0.0 2745 07 Oct 2011 Fixed
11.0.1 2689 07 Oct 2011 Fixed
Description
If any of the following occurred while starting a database, the server could have crashed, although it would only occur in very rare situations:

1. An error was encountered while starting the database

2. Logs were being applied to a database at startup with -a, -ad or -ar but the -as switch was not used

3. The engine was requested to stop while the database was starting.



This has now been fixed.



CR:686575
CR Number:   686575
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows 2000
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3480 20 Oct 2011 Failed
Description
Very complex disjuncts in the WHERE clause were not able to be used for index scans. Now, IN predicates are generated if at all possible. These new IN predicates can then be used to drive an index scan improving the execution times for this type of query.



CR:686586
CR Number:   686586
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3472 12 Oct 2011 Fixed
12.0.0 2745 12 Oct 2011 Fixed
Description
A lengthy Relay Server alert may have been corrupted by having extra non-break space tokens ( ) broken up by exclamation marks. This has been fixed.



CR:686790
CR Number:   686790
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3472 11 Oct 2011 Fixed
Description
When the server was starting a database, statistics collection may be performed on the database tables even though the statistics are not updated. This has been corrected so that statistics collection is now disabled on a database that is being started.



CR:686791
CR Number:   686791
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3488 27 Oct 2011 Fixed
11.0.1 2702 27 Oct 2011 Fixed
Description
In a mirroring system, if the primary server made changes faster than the mirror server could apply them, and if the connection between the two servers was dropped, in rare timing dependent cases, the mirror server could have hung with 1 CPU at 100%. Stopping the server or the database during the 100% CPU hang would have succeeded. This has now been fixed.



CR:686822
CR Number:   686822
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3479 19 Oct 2011 Fixed
12.0.0 2750 19 Oct 2011 Fixed
Description
If an ALTER PUBLICATION or a DROP PUBLICATION command was executed by the MobiLink client inside the sp_hook_dbmlsync_schema_upgrade hook, it was possible for the command to have thrown an 100904 assertion ("Failed to redo a database operation ...") if the database server had to replay the operation during recovery. This has now been fixed.



CR:686869
CR Number:   686869
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3484 25 Oct 2011 Fixed
Description
When a database page was reused, the unused portion of the page was not always set to zeros, possibly resulting in exposure of decrypted data when that page was written out. This has now been corrected.



CR:687157
CR Number:   687157
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3549 23 Jan 2012 Fixed
12.0.0 2774 23 Jan 2012 Fixed
Description
Upload rows sent by clients might not have been applied to the consolidated database on a SQL Anywhere or Sybase IQ database server if a redundant synchronization request was received by the MobiLink server, and the MobiLink server aborted the request with the following error:

User 'a_ml_user_name' has the row in 'ml_database' locked (ODBC State = 40001, Native error code = -210)



The new synchronization must also have contained an upload that included upload rows for multiple synchronization tables, and reused the database connection that was used for processing the redundant synchronization. This problem is fixed now.



Note, all connections used by a MobiLink server are shown in the MobiLink server logging file with a prefix SPID when a minimal verbosity is specified in the MobiLink command line.



CR:687162
CR Number:   687162
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)
12.0.1 3912 14 Oct 2011 Fixed
Description
When using a trigger to maintain a timestamp column in a synchronized table in a synchronization model, the generated update trigger would have fired when any column except the timestamp column was updated. If the table included a computed column, this would have caused an error when creating the trigger, even if one disabled synchronization for the computed column (as suggested in the "Limitations of synchronization models" documentation). This has been fixed. Now the generated update trigger only fires if a synchronized column or delete tracking column (if using logical deletes) is modified. A workaround is to deploy to a SQL file and edit the trigger definition.



CR:687264
CR Number:   687264
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3476 17 Oct 2011 Fixed
Description
The server's http log did not display the query component of the request URI. This has been fixed.



CR:687273
CR Number:   687273
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3476 18 Oct 2011 Fixed
Description
The HTTPS parameter was not mentioned in the usage text description of the Relay Server Outbound Enabler's -cs option, nor do any cert parameters mention that it is required. This is also the case for the usage for the -cr option, where HTTPS was not mentioned anywhere. Descriptions have now been added to the usage text for these options, as well as a mention that HTTPS=1 is required for any of the cert parameters. Also the -cs https=1 default port was set to 80, this has now been changed to 443 instead.



CR:687277
CR Number:   687277
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3476 18 Oct 2011 Fixed
Description
The Relay Server Outbound Enabler (RSOE) didn't complain about typos in the -cs and -cr command line options. For example, if trusted_certificates was entered as trusted_certificate, RSOE would not stopped with an error right at start-up. Also, when HTTPS related parameters were specified and HTTPS=1 was not set, RSOE would also silently attempt to make an HTTP connection. These problem have been fixed so that RSOE will detect these problem, report an error, and abort.



CR:687393
CR Number:   687393
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3483 25 Oct 2011 Fixed
12.0.0 2751 25 Oct 2011 Fixed
11.0.1 2698 25 Oct 2011 Fixed
Description
Under very rare circumstances, a server could have crashed during backup if many connections are committing transactions at the same time. Live backups were the most likely to suffer from this problem. This has been fixed. No workaround is known.



CR:687411
CR Number:   687411
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   7.0.4
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3477 18 Oct 2011 Fixed
11.0.1 2695 18 Oct 2011 Fixed
Description
When an ALTER DATABASE UPGRADE statement is executed, events are suspended in order to avoid having active connections while upgrading. Once upgrading is done, events are re-enabled. Running simultaneous ALTER DATABASE UPGRADE statements could have left events permanently suspended on the server. No events on any database would have been executed. This problem has been fixed. Also, when upgrading a single database, the server suspended events for all databases that爓ere running. This was unnecessary and the server now only suspend events in the database that is being upgraded.



CR:687447
CR Number:   687447
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3477 18 Oct 2011 Fixed
11.0.1 2695 18 Oct 2011 Fixed
Description
In rare, timing dependent cases the server could have had incorrect behaviour when a connection had at least 20 prepared statements with cached prepared statements, or at least 20 cursors open. The incorrect behaviour could have varied, and the only known symptom was incorrectly returning the error "Resource governor for 'prepared statements' exceeded", but it may also have been possible for server crashes or assertions to have occurred. This has now been fixed.



CR:687567
CR Number:   687567
Product Name:   SQL Anywhere Monitor
Product Component:   SQL Anywhere Monitor
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3478 18 Oct 2011 Fixed
Description
The SQL Anywhere Monitor may have missed counting some uncommon Relay Server errors. These errors were:



FARM_CHANNEL_CONNECT_WITH_INVALID_SERVER_IDX 2006

SERVER_DISCONNECT_EARLY 3014

FARM_FAIL_ACCESS 12000

SERVER_FAIL_NEWING_CLIENT_STATISTIC 13011



This has been fixed.



CR:687570
CR Number:   687570
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3588 01 Mar 2012 Fixed
Description
A .NET Policy DLL and the associated iAnywhere.MobiLink.Client.config file are now installed and configured. The .NET Policy DLL will allow .NET applications compiled against any build of v12.x of the iAnywhere.MobiLink.Client assembly to automatically re-direct to the most recent build of the assembly installed on the machine, if the desired build of the assembly could not be located on the machine. Before these files were installed and configured, an application.config file or machine.config file could have been used to get the same functionality.



CR:687571
CR Number:   687571
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3479 19 Oct 2011 Fixed
Description
If Relay Server State Manager failed to initialize on startup during creating the shared memory step, it did not output a detailed message with the system error code and message. This has been corrected.



CR:687578
CR Number:   687578
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3466 21 Oct 2011 Fixed
12.0.0 2742 21 Oct 2011 Fixed
11.0.1 2685 21 Oct 2011 Fixed
10.0.1 4279 21 Oct 2011 Fixed
Description
Applications using the .Net provider could have crashed after running for some time. In rare occasions, the provider could have attempted to drop a prepared statement twice. This has now been fixed.



CR:687596
CR Number:   687596
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3478 19 Oct 2011 Fixed
12.0.0 2749 19 Oct 2011 Fixed
11.0.1 2696 19 Oct 2011 Fixed
Description
When shutting down a server that was running as a Windows service, the server could have crashed. Although the problem was only seen when shutting down an interactive service on Windows XP by using the 'Shutdown' button on the server window, the problem was a timing issue and could have occurred when the server was shut down in other ways. The problem has been corrected.



CR:687604
CR Number:   687604
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3472 18 Oct 2011 Fixed
Description
INSERT performance was 25-35% slower than version 11.0. The problem has been fixed.



CR:687747
CR Number:   687747
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)
12.0.1 3479 19 Oct 2011 Fixed
Description
If the server was shutdown while a mirrored database was in the process of starting on the server, the server could have crashed. This has been fixed.



CR:687749
CR Number:   687749
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3489 28 Oct 2011 Fixed
12.0.0 2754 28 Oct 2011 Fixed
11.0.1 2702 28 Oct 2011 Fixed
Description
A query using aggregate functions may have caused a server crash if its select list contained a derived table with an outer reference to the query, and the outer reference did not appear in the queries group by list. At least one of the following conditions must also have been trun:

1) The derived table contained a procedure call in its FROM clause and the procedure argument expression contained the outer reference.

2) The derived table contained a OPENSTRING clause in its FROM clause and its value expression contained the outer reference.

3) The derived table contained another derived table and the outer reference was inside this other derived table.



The below query shows an example of condition 3).



select ( select V0.e from (

select T3.e from T3 where T3.e = T2.c ) V0

) c1,

max(T1.b) as c2

from T1 join T2 on T1.a = T2.c



This problem has been fixed. The engine will now correctly return the error SQLE_INVALID_GROUP_SELECT, since the outer reference column has to be specified in the GROUP BY clause. Specifying the outer reference column in the GROUP BY clause (in the above example: group by T2.c) is also the work around to this problem.



CR:687761
CR Number:   687761
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3478 19 Oct 2011 Fixed
11.0.1 2696 19 Oct 2011 Fixed
12.0.0 2749 19 Oct 2011 Fixed
Description
The dbisqlc utility would have reported a syntax error whenever it tried to execute a 'STOP SERVER' statement. This problem has been fixed. The statement used to be 'STOP ENGINE ...' and dbisqlc did support (and continues to support) that variant; however, it was never updated when the statement was changed to 'STOP SERVER'.



CR:687769
CR Number:   687769
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3479 19 Oct 2011 Fixed
11.0.1 2696 19 Oct 2011 Fixed
Description
In some circumstances, the Long.MIN_VALUE (-2^63) was incorrectly stored internally as a NUMERIC value. This resulted in incorrect values during expession evaluation. This has been fixed.



CR:687773
CR Number:   687773
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)
12.0.1 3479 19 Oct 2011 Fixed
Description
In extremely rare cases, the server could have crashed when request level logging was enabled. The problem has now been corrected.



CR:687776
CR Number:   687776
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3479 20 Oct 2011 Fixed
Description
The changes for Engineering case 686057 made have caused the server to crash when using URL query parameters. This has been fixed.



CR:687786
CR Number:   687786
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3477 19 Oct 2011 Fixed
Description
An interactive quick setup feature has been added to help users with deploying Relay Server components to Microsoft IIS 6.0 on Windows Server 2003. This is being provided as an alternative to the manual procedure documented in the Relay Server Guide.



Setup is automated but also interactive. It creates a demo application and a Quick Reference Guide to assist in subsequent Relay Server server maintenance. The Quick Reference is launched automatically as part of the setup.



Setup is comprised of the following major steps:

1. Introduction

2. Customization

3. Create a Backup

4. Deploy and Start the Relay Service

5. Generate and Launch the Quick Reference

6. Launch the Relay Server Status Page

7. Launch the SimpleTestApp Client

8. Shut down



To deploy the Relay Server components to Microsoft IIS 6.0 on Windows Server 2003, run rs-setup.bat from the SQLANY12%/RelayServer/IIS/quicksetup_iis6 directory



CR:687796
CR Number:   687796
Product Name:   SQL Anywhere
Product Component:   JDBC Client Library
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3480 19 Oct 2011 Fixed
12.0.0 2750 19 Oct 2011 Fixed
11.0.1 2696 19 Oct 2011 Fixed
Description
If an application using the SQL Anywhere JDBC driver attempted to exit, then there was a very small chance the client would crash on non-MacOS systems; however, on MacOS systems, the crash would have occurred every time. This problem has now been fixed. Note that the original problem was introduced with the fix for Engineering case 680183.



CR:687835
CR Number:   687835
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3485 19 Dec 2011 Fixed
12.0.0 2752 19 Dec 2011 Fixed
11.0.1 2701 19 Dec 2011 Fixed
Description
If an MSI install was built using the Deployment wizard, and Sybase Central was selected but Interactive SQL was deselected, the subsequent install of Sybase Central would have failed on exit. The error:

Interactive SQL could not be launched.

Please change the plug-in properties and

add the isql.jar file to its path.



was due to Sybase Central expecting ISQL.jar to be installed. This has been corrected by adding a dependency on ISQL.jar when an install of Sybace Central is created.



CR:687837
CR Number:   687837
Product Name:   MobiLink
Product Component:   Monitor
Status:   Closed
OS:   Generic
Original Version:   8.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3480 20 Oct 2011 Fixed
Description
If an Overview color in the Options dialog was changed, the Overview display would have been erased. This has been corrected. A workaround is to disable, then re-enable, the Overview or change, then change back, the option to keep the Overview window attached to the main window.



CR:687840
CR Number:   687840
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)
12.0.1 3605 19 Mar 2012 Fixed
11.0.1 2777 19 Mar 2012 Fixed
Description
The initial primary mirror server could have crashed or not correctly processed requests in rare timing dependent cases after executing the "ALTER DATABASE SET PARTNER FAILOVER" statement. This problem could have also occurred when a preferred partner server became available after being disconnected. This has been fixed.



CR:687973
CR Number:   687973
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3481 20 Oct 2011 Fixed
Description
Calling the system procedures sp_remote_tables or sp_remote_columns for an ASE or MS SQL Server remote server would have failed if the catalog argument was specified as NULL. This problem was introduced in 12.0.1 GA and has now been fixed.



CR:687980
CR Number:   687980
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3480 20 Oct 2011 Fixed
Description
UltraLite is now supported on the Pocket PC 2003 platform. Support for TLS and HTTPS sync encryption, however, is not available for this platform.



CR:687998
CR Number:   687998
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   6.0.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3482 20 Oct 2011 Fixed
12.0.0 2750 20 Oct 2011 Fixed
11.0.1 2697 20 Oct 2011 Fixed
Description
While extremely rare, the server may have crashed while executing a query that referenced proxy tables. The problem has now been fixed.



CR:687999
CR Number:   687999
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)
12.0.1 3528 19 Dec 2011 Fixed
Description
In rare timing dependent cases, a transaction which was successfully committed on a primary server could have been lost. In order for there to have been a chance of this occurring, all of the following needed to be true:

- the application was connected to a primary server that lost quorum (the server lost the connection to both the mirror and arbiter servers)

- the application stayed connected to this server (the old primary server) even though the network connection to other servers dropped

- the application was in the middle of committing a transaction between the time that the old primary server lost its connection to the mirror and arbiter server, and when the old primary server restarted as the new mirror server because it lost quorum

- the old mirror server took over as the new primary (the mirror server must have been able to connect to the arbiter server for this to occur)



This problem has now been fixed.



CR:688019
CR Number:   688019
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)
12.0.1 3482 21 Oct 2011 Fixed
11.0.1 2698 21 Oct 2011 Fixed
Description
When connected to the utility database (utility_db), if a statement that was not supported was prepared, the PREPARE may not have generated an error when it should have. This has been fixed so that the unsupported prepare now returns the error "Permission denied: you do not have permission to execute a statement of this type."



CR:688116
CR Number:   688116
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3475 21 Oct 2011 Fixed
Description
Support has now been added to the Relay Server to allow it to extract identity information from client certificate and then forward them in HTTP headers that SAP Gateway or Web Dispatcher understands. To turn on the feature for a backend farm, set the following new backend farm property in the Relay Server configuration file:

forward_x509_identity = yes



In the case were there is a chain of SAP intermediaries, the client identity headers may already present in the request. However not all clients may be granted a permission to act as such forwarder. So the default behavior is to replace the existing headers with the identity of the forwarder. To grant permission for a forwarder to forward its client identity without being overwritten by its identity, the following new pair of backend farm properties may be in the Relay Server configuration file:

forwarder_certificate_subject = <match-string>

forwarder_certificate_issuer = <match-string>



The <match-string> is used to check against a serialized form of the corresponding compound name field in the certificate. A '?' can be used to match any character and a '*' can be used to match any string. A '\' can be used as the leading escape character for '?', '*' or '\' of they need to be matched literally.



For example:

forwarder_certificate_subject = 'CN = mySapWD??.my.com, OU = Sybase, O = SAP, *'

forwarder_certificate_issuer = 'CN = quicksigner, OU = security department, O = my coop, L = my city, S = my state, C = my country'



To obtain the subject or issuer string of a forwarder, simply perform a forwarding without setting up the match requirement. The following error messages in the Relay Server log will reveal the full subject or issuer which fails the default empty match-string:

Forwarder certificate subject '<full-subject-string>' does not match pattern '' required in farm '<farm>'

Forwarder certificate issuer '<full-issuer-string>' does not match pattern '' required in farm '<farm>'



CR:688149
CR Number:   688149
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Jun 2013 Bundled Request
Description
New OUTPUT command options to control column names.



CR:688272
CR Number:   688272
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3484 24 Oct 2011 Fixed
Description
If an INSERT or an UPDATE failed, due to a unique constraint violation for example, a row may have been left behind in the store. This would have resulted it unrecoverable database growth. This has been fixed.



CR:688435
CR Number:   688435
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3484 25 Oct 2011 Fixed
Description
An IS [NOT] DISTINCT FROM predicate may have been incorrectly evaluated for some data types, such as string datatypes. The incorrect evaluation would have been observed if the predicate was not used in a Hash Join, Merge Join, or as a sargable predicate for a partial index scan. This has been fixed.



CR:688459
CR Number:   688459
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3486 26 Oct 2011 Fixed
Description
Queries that use temporary tables could have produced incorrect results when UltraLiteJ was configured with row limitations (i.e. using ConfigPersistent.setRowScoreMaximum or ConfigPersistent.setRowScoreFlushSize). This has been fixed.



CR:688468
CR Number:   688468
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3486 26 Oct 2011 Fixed
Description
The UltraLite runtime library for iPhone would have failed to build with recent Xcode/SDKs (Xcode 4.2 with iOS 5.0 SDK, for example), as gcc-4.2 was no longer being shipped (the command wais not found while trying to run build.sh). This has been fixed by having the UltraLite runtime makefile now simply use 'gcc'.



This problem can be worked-around by creating a symlink for gcc-4.2 -> gcc in the /Developer/Platforms/iPhoneOS.platform/Developer/usr/bin and similar Simulator directories, or by modifying the makefile or build.sh used by UltraLite.



CR:688573
CR Number:   688573
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3487 28 Oct 2011 Fixed
Description
An interactive quick setup feature has been added to help users with deploying Relay Server components to Microsoft IIS 7.0 or 7.5 on Windows Server 2008/Windows Server 2008 R2. This is being provided as an alternative to the manual procedure documented in the Relay Server Guide.



Setup is automated but also interactive. It installs IIS7, turns on required IIS7 features, configures IIS7 for Relay Server, creates a demo application and a Quick Reference Guide to assist in subsequent Relay Server server maintenance. The Quick Reference is launched automatically as part of the setup.



Setup is comprised of the following major steps:

1. Introduction

2. Customization

3. Install IIS7 and Required Features

4. Create a Backup

5. Deploy and Start the Relay Service

6. Generate and Launch the Quick Reference

7. Launch the Relay Server Status Page

8. Launch the SimpleTestApp Client

9. Shut down



To deploy the Relay Server components to Microsoft IIS 7.0 or 7.5 on Windows Server 2008/Windows Server 2008 R2, run rs-setup.bat from the SQLANY12%/RelayServer/IIS/quicksetup_iis7 directory.



CR:688581
CR Number:   688581
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3488 27 Oct 2011 Fixed
Description
In a read-only scale-out system, if the non-primary server (say S) in the read-only scale-out tree had more than ten direct or indirect children, then S's parent could have hung, in rare timing dependent cases. This problem was introduced by changes made for Engineering case 681813, and has now been fixed.



CR:688720
CR Number:   688720
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3492 03 Nov 2011 Fixed
Description
UltraLite could have returned fewer rows than expected for queries utilizing an index scan with conditions on multiple columns in the index. This has now been fixed.



CR:688788
CR Number:   688788
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3488 28 Oct 2011 Fixed
11.0.1 2702 28 Oct 2011 Fixed
Description
In rare timing dependent cases, if a mirror server was using all available workers, it was possible for the server to hang, or for a mirror database to not restart after loss of quorum. The maximum number of workers is defined by -gnh (in version 12) or by -gn (in version 11). This has been fixed.



CR:688888
CR Number:   688888
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3489 02 Nov 2011 Fixed
Description
The ENCRYPTED KEY option of the OPENSTRING clause can now specify a variable name rather than a string.

For example:

create variable mykey varchar(50);

set mykey='TheActualEncryptionKey';

select * from openstring(...) with (...) option (encrypted key mykey);



CR:688891
CR Number:   688891
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Apr 2012 Fixed
Description
It is now possible to disable the fast launcher feature of the Interactive SQL utility using the oem.ini file. To disable the fast launcher add the line "fastLauncherEnabled=false" to the "dbisql" section of the OEM.INI file. This option disables the fast launcher but does not prevent a user from re-enabling it using the options dialog. To prevent users from re-enabling fast launching add "fastLauncherEnabled" to the value of the "lockedPreferences" option in the OEM.INI file. So, with both options set you OEM.INI would look something like this:



[dbisql]

lockedPreferences=fastLauncherEnabled

fastLauncherEnabled=false



CR:688892
CR Number:   688892
Product Name:   MobiLink
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3490 31 Oct 2011 Fixed
Description
When running mlgenreplayapi with a non-existent recorded protocol file, and/or using the -d switch with a non-existent directory, no error messages was displayed at the console. However, if the -o or -ot switch was used, the errors were logged in the log file. Now, if no -o or -ot options are specified for mlreplay and mlgenreplayapi, all output goes to stdout.



As well, mlgenreplayapi will now create the directory specified by the -d option (the directory in which to put the generated code) when it does not exist.



CR:688896
CR Number:   688896
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3493 28 Oct 2011 Fixed
11.0.1 2701 03 Nov 2011 Fixed
12.0.0 2782 19 Mar 2012 Fixed
Description
If an application crashed during synchronization it was possible that subsequent sync attempts would have failed with server errors. The MobiLink server would have reported a progress mismatch and the log could have shown multiple instances of the same publications. This has been fixed.



CR:689047
CR Number:   689047
Product Name:   UltraLite
Product Component:   Runtime Libraries
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3490 31 Oct 2011 Fixed
11.0.1 2704 31 Oct 2011 Fixed
Description
An HTTP or HTTPS synchronization through the Relay Server could have failed with stream error STREAM_ERROR_HTTP_HEADER_PARSE_ERROR. This has been fixed.



CR:689167
CR Number:   689167
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3491 01 Nov 2011 Fixed
Description
After using the "Find" button to find a network server, the message "You cannot use the Host connection parameter and advanced network parameters at the same time." could have been returned, even though nothing was specified on the "Network" tab. For this problem to have occurred, the "Action" field had to have been set initially to "Connect to a running database on nother computer". The problem would not have occurred if the "Action" value had been changed prior to clicking the "Connect" button. This has been fixed.



In a related issue, the above error message should have been displayed, but was not, in a number of other cases. This has also been fixed.



CR:689174
CR Number:   689174
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3491 02 Nov 2011 Fixed
Description
The Relay Server was sensitive to the networking environment and how quickly the web server detected read errors (RSE3004) caused by network problems on the down channel between the Outbound Enabler and the Relay Server. If there was enough delay so that the Outbound Enabler had already recovered the channels before the detection occur, the Relay Server would have failed subsequent client requests targeting this back-end server and reported the following warning:

W. 2011-10-28 21:23:36. <5608.2420.F5fcB0S456bR0> Server response NOT completed. Remaining 0 of 0 bytes.



Restarting the Outbound Enabler would have resolved the issue. This has now been fixed so that client requests will not be affected by the delay and restarting Outbound Enabler is no longer required.



CR:689193
CR Number:   689193
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3494 04 Nov 2011 Fixed
11.0.1 2706 04 Nov 2011 Fixed
Description
The changes for Engineering case 682512 introduced a problem where stopping a high availability primary server while it was connected to its partner (mirror) server could have resulted in the database not being able to start. Specifically, in timing dependent cases, attempting to restart the primary mirror server could fail with the "Database cannot be started -- <database name> not expecting any operations in transaction log". This has been fixed.



CR:689194
CR Number:   689194
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Linux
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3500 11 Nov 2011 Fixed
11.0.1 2709 11 Nov 2011 Fixed
Description
When synchronizing with a SQL Anywhere remote using the MobiLink client running on a non-English operating system, it was possible for the following message to be generated by the MobiLink server:



Gtk-CRITICAL **:gtk_text_buffer_emit_insert:assertion 'g_utf8_validate (text, len, NULL)' faild



This problem has been fixed. As a consequence, the message output in the MobiLink server log when a synchronization request is received from a SA remote will change from:



Request from "Dbmlsync Version 16.0.0.3940" for: remote ID: ...



to:



Request from "Dbmlsync 16.0.0.3940" for: remote ID: ...



CR:689233
CR Number:   689233
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3492 02 Nov 2011 Fixed
12.0.0 2755 02 Nov 2011 Fixed
11.0.1 2705 02 Nov 2011 Fixed
Description
Opening a procedure in a new window, deleting the procedure from the main Sybase Central window, and then attempting to save the procedure from the new window, would have caused Sybase Central to crash. The same problem occurred for views, functions, triggers and events. These issues have been fixed.



CR:689315
CR Number:   689315
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3492 02 Nov 2011 Fixed
12.0.0 2756 02 Nov 2011 Fixed
11.0.1 2705 02 Nov 2011 Fixed
Description
When connected via jConnect or Open Client to a blank padded UTF8 database and a non-nullable char(n) value was fetchesd, the client may have experienced protocol errors if n was less than 3. This problem was introduced by the fix for Engineering case 686183 and has now been fixed.



CR:689451
CR Number:   689451
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)
12.0.1 3933 03 Nov 2011 Fixed
Description
If the server was forcibly shut down while an encrypted database was in the process of starting or stopping, the server could have crashed. This has been fixed.



CR:689464
CR Number:   689464
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3494 04 Nov 2011 Fixed
12.0.0 2757 04 Nov 2011 Fixed
11.0.1 2706 04 Nov 2011 Fixed
Description
The Property() function would have displayed negative values for the server properties 'HttpPorts' and 'HttpsPorts' when the port numbers were above 32768. This has been fixed.



CR:689511
CR Number:   689511
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3493 04 Nov 2011 Fixed
12.0.0 2757 04 Nov 2011 Fixed
11.0.1 2706 04 Nov 2011 Fixed
Description
In some extremely rare cases, the transaction log may not have been committed to disk when a COMMIT operation was performed.



Also, if a transaction only modified temporary tables, it was possible that the transaction log would have been committed to disk although it didn't need to be.



These problems have been fixed.



CR:689614
CR Number:   689614
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3496 08 Nov 2011 Fixed
11.0.1 2708 08 Nov 2011 Fixed
Description
In rare cases in a mirroring system, where a mirror server lagged far behind the primary in applying changes, it was possible for the primary and mirror server to hang. This has been fixed.



CR:689657
CR Number:   689657
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3493 07 Nov 2011 Fixed
Description
Three new properties have been added:



LastCommitRedoPos: This property is available at both the connection-level and the database-level. The value returned is the redo log position after the last COMMIT operation was written to the transaction log by the connection or database.



LastWrittenRedoPos: This is a database-level property only. The value returned is the last redo position for which a write was issued to disk. The write is not necessarily synced to the physical medium as it may still be cached by the OS, disk controller or disk drive.



LastSyncedRedoPos: This is a database-level property only. The value returned is the last redo position for which a write was issued to disk and the data was synched to the physical medium. Data prior to this position is expected to be present on disk even in the event of a power failure.



CR:689696
CR Number:   689696
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3589 28 Feb 2012 Fixed
11.0.1 2768 28 Feb 2012 Fixed
Description
In exceptionally rare circumstances, the server may have failed with assertion errors 200130, 200131, 200106, 108701, or others, on index pages. The problem was seen on multi-core machines under very high index contention, that included index updates and deletes. This has been fixed.



CR:689764
CR Number:   689764
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3495 08 Nov 2011 Fixed
12.0.0 2758 08 Nov 2011 Fixed
11.0.1 2707 08 Nov 2011 Fixed
Description
The assembly names of version 3.5 and 4.0 providers in the policy config file were not correct. This meant that version 3.5 and 4.0 policy files did not redirect old versions to a newer version. This has been corrected



CR:689781
CR Number:   689781
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3495 08 Nov 2011 Fixed
12.0.0 2758 08 Nov 2011 Fixed
11.0.1 2758 08 Nov 2011 Fixed
Description
The ADO .Net provider now supports Microsoft Entity Framework 4.2. To use the new Entity Framework 4.2, it must be added to Visual Studio projects using the Visual Studio tool NuGet.



CR:689792
CR Number:   689792
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3496 09 Nov 2011 Fixed
12.0.0 2758 09 Nov 2011 Fixed
Description
Requests to 12.0 MobiLink servers from MobiLink clients without the changes made for Engineering case 471582, where the MobiLink client included version and build number in each synchronization, could have ended with an "Unknown request completed" in the MobiLink server log. Also, error "[-10344] The remote database identified by remote ID '89d85096-0006-11e1-8000-8a42a227c45d' is already synchronizing: orphaned UltraLite synchronization" could have been reported for requests from MobiLink clients without this change as well. These issues have been fixed.



CR:689907
CR Number:   689907
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3744 08 Jun 2012 Fixed
Description
The Interactive SQL utility would not have reported an error if an unknown encoding name was used in the READ statement's ENCODING clause. This has been corrected so that now it does.



CR:689910
CR Number:   689910
Product Name:   UltraLite
Product Component:   UltraLite Engine
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3518 05 Dec 2011 Fixed
Description
Extra rows were returned when executing a query using UNION where the subqueries contained joins with ON conditions. This has now been fixed.



CR:689943
CR Number:   689943
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3496 08 Nov 2011 Fixed
Description
With UltraLiteJ, committing a SQL statement that updated a table containing a large BLOB or CLOB could have caused an ArrayIndexOutOfBoundsException. This has been fixed.



CR:689954
CR Number:   689954
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Solaris
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3518 02 Dec 2011 Fixed
12.0.0 2768 02 Dec 2011 Fixed
11.0.1 2722 02 Dec 2011 Fixed
Description
An ODBC application could have crashed when attempting to connect if a thread was unable to be started. This has been fixed.



CR:690075
CR Number:   690075
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3518 09 Nov 2011 Fixed
12.0.0 2762 09 Nov 2011 Fixed
11.0.1 2713 09 Nov 2011 Fixed
Description
Events run on temporary connections, but those connections did not always have the correct locale information. In particular, functions such as errormsg() would have returned strings encoded in the OS character set rather than in the database character set. This problem has been fixed.



CR:690114
CR Number:   690114
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3497 09 Nov 2011 Fixed
12.0.0 2759 09 Nov 2011 Fixed
11.0.1 2708 09 Nov 2011 Fixed
Description
Recovery could have failed if an operation in the transaction log required access to a feature that was secured on the command line via the -sf option. The operation could have entered the log, either by having the operation performed on a server where the feature was not secured, or if security was permitted, on the given connection via the -sk server option and setting the secure_feature_key option to match. The failure would have been displayed as assertion number 100904 "Failed to redo a database operation". This has now been fixed.



Note, not all secured features add entries to the transaction log. For example, the READ_FILE secured feature blocks access to xp_read_file which would not get logged; however, the REMOTE_DATA_ACCESS secured feature blocks access to statements such as CREATE SERVER does get logged.



CR:690133
CR Number:   690133
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3515 30 Nov 2011 Fixed
12.0.0 2768 30 Nov 2011 Fixed
11.0.1 2721 30 Nov 2011 Fixed
Description
When connected via jConnect or Open Client, retrieving the metadata of a long nvarchar or ntext column may have incorrectly indicated that the column was a long binary value. This problem has now been fixed.



CR:690224
CR Number:   690224
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
30 Sep 2013 Fixed
Description
The database properties CurrIO, MaxIO, CurrRead, MaxRead, CurrWrite, and MaxWrite, in some cases were not be maintained correctly. This has been fixed.



CR:690250
CR Number:   690250
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3517 11 Nov 2011 Fixed
11.0.1 2709 02 Dec 2011 Fixed
Description
The UltraLiteJ runtime now supports restartable HTTP synchronizations. With restartable HTTP enabled, UltraLiteJ applications can tolerate network interruptions, so synchronizations will fail less often on unreliable networks. Restartable HTTP is disabled by default. To enable, use the following new methods on the StreamHTTPParms class:



/**

* Enables or disables restartable HTTP. With restartable HTTP enabled,

* UltraLiteJ can tolerate network interruptions, so synchronizations will fail

* less often on unreliable networks.

* <p>

* To use restartable HTTP, both UltraLiteJ and the MobiLink server must have

* applied CR#690250.

*

* @param isRestartable Pass true to enable restartable HTTP, and false to

* disable. The default is false.

* @see #isRestartable()

*/

public void setRestartable( boolean isRestartable );



/**

* Returns true if restartable HTTP will be used, and false otherwise.

*

* @return Whether restartable HTTP will be used.

* @see #setRestartable(boolean)

*/

public boolean isRestartable();





To use this change, both remotes and servers must be upgraded. It is safe to upgrade only one of the remote or the server, as long as setRestartable is not called on the remote.



CR:690254
CR Number:   690254
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)
12.0.1 3500 11 Nov 2011 Fixed
11.0.1 2709 11 Nov 2011 Fixed
Description
When request logging is enabled with ALL or PLAN, the server may have crashed if the following sequence occurred:

- Connection A opened a cursor that included fetching rows from a procedure

- Connection B dropped the procedure used by connection A

- Connection A then closed its cursor



This problem has been fixed.



CR:690291
CR Number:   690291
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3505 18 Nov 2011 Fixed
Description
An UltraLiteJ database that was created from a file using the method DatabaseManager.importDatabaseFile() could have been invalid in rare circumstances. The circumstances in which this was more likely were when the page size of the database was small (1 KB or less). This has been fixed.



CR:690295
CR Number:   690295
Product Name:   SQL Anywhere
Product Component:   ADO.Net Managed Provider
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3499 11 Nov 2011 Fixed
12.0.0 2759 11 Nov 2011 Fixed
11.0.1 2709 11 Nov 2011 Fixed
10.0.1 4297 11 Nov 2011 Fixed
Description
An IIS web server application could have crashed after running for a few days. This has now been fixed.



CR:690373
CR Number:   690373
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3500 11 Nov 2011 Fixed
Description
Statements with virtual tables referencing user-defined functions, and stored procedures which qualify for in-lining, may crashed the server or returned incorrect results. This has been fixed.



CR:690393
CR Number:   690393
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.1 3501 14 Nov 2011 Fixed
Description
The changes for Engineering cases 673184 and 673184 may have caused non-lazy loading databases to encounter SQLE_ERROR and ArrayIndexOutOfBounds. This has been fixed.



CR:690627
CR Number:   690627
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)
4157 08 Jun 2012 Fixed
Description
If a stored procedure is called from the Interactive SQL utility, and that procedure performed a client-side file operation, the user is asked whether the operation should be allowed or not. Previously, if dbisql was run with the -q command line option, the prompt was not displayed, and "Allow" was assumed. Now, the prompt is displayed even if the -q option is used, and the initially selected option has been changed from "Allow" as default, to "Disallow".





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