远程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:611985
CR Number:   611985
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2372 13 Apr 2010 Fixed
11.0.1 2424 13 Apr 2010 Fixed
Description
Software installs that were built using merge modules (MSM files) created by the SQL Anywhere Deployment Wizard would have failed to generate the .jpr files needed to register plugins for Sybase Central. Consequently, the following error would have occurred:

Error - EXCEPTION: java.io.FileNotFoundException: C:\Program Files\SQL Anywhere 11\java\SQLAnywhere.jpr (the System cannot find the file specified).



A similar error message would also have appeared for the file Mobilink.jpr



This has been fixed, so that MSMs now work correctly as well.



Note, MSI installs built with the Deployment Wizard did not exhibit this behavior.
Workaround Description
 Edit away the custom actions in the MSM files that would have registered the jpr files. Then the customer inform end users do the following steps to install the SQL Anywhere plugin manually:



1. Starting Sybase Central

2. Click Tools -> Plug-ins

3. In the Sybase Central Plug-ins window that appears, click Register

4. In the Register a Plug-in Wizard window that appears, choose Register a plug-in by specifying a JAR file, browse to the Java subfolder under the SQL Anywhere 11 install folder, and choose saplugin.jar

5. Click Finish



CR:612094
CR Number:   612094
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2366 21 Dec 2009 Fixed
10.0.1 4003 21 Dec 2009 Fixed
Description
An incorrect response length may have been recorded in the SQLAnywhere HTTP log for a long lived HTTP connection, such as a pipelined connection wacorrect, subsequent response lengths were cumulative. The problem occurred when HTTP logging was enabled and the @L LogFormat specified the logging of the response length (default). This has now been fixed.



CR:612128
CR Number:   612128
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2366 22 Dec 2009 Fixed
Description
Clicking the "GENERATE/INSERT statement" menu item in the Results panel, when the row contained a long character column (e.g. more than 100K), the Interactive SQL utility could have taken a very long time to generate the statement. This has been corrected so thgat it now happens almost instantaneously.



CR:612268
CR Number:   612268
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)
11.0.1 2367 22 Dec 2009 Fixed
Description
While rare, a CREATE VIEW statement could have caused a server crash. This has been fixed.



CR:612269
CR Number:   612269
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)
11.0.1 2367 21 Dec 2009 Fixed
Description
The SQL Anywhere HTTP log did not allow a format option to specify the logging of the client port used in an HTTP request. Both the client IP address and port were required to demarcate the use of a specific connection within the log when a client made several keep-alive HTTP connections. The LogFormat protocol option has been changes sp that it now supports the "@J" format-string code to specify logging of the client port. The following LogFormat is recommended to include the logging of the client port since this will be the default in future releases:



@T - @W - @I:@J - @P - "@M @U @V" - @R - @L - @E



CR:612295
CR Number:   612295
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3934 22 Dec 2009 Fixed
Description
Using the DBS connection parameter with a value that included quotes may have caused the connection fail. This has been fixed.



CR:612301
CR Number:   612301
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)
11.0.1 2367 22 Dec 2009 Fixed
Description
If an error (such as "disk full") was encountered while extending a dbspace, it was possible that the dbspace would be corrupted. Subsequent startups may have reported assertion failure 201129 (file is shorter than expected), or one of several other assertion failures. This problem has been fixed.



Note that the problem did not affect growth of the transaction log.



CR:612409
CR Number:   612409
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2370 05 Jan 2010 Fixed
10.0.1 4010 05 Jan 2010 Fixed
Description
When connected to a multi-byte character set database, if an application attempted to create a proxy table to a remote table that had an underscore in its name, then there was a chance the server would fail the request with the error "the table specification '<location-string>' identifies more than one remote table". This problem would only have occurred if the remote had multiple tables whose names differed only by the character in the underscore location. For example, if a remote had tables named tab_1 and tabx1, and if the application attempted to create a proxy table to map to tab_1, then the server would give the "more than one remote table" error. This problem has now been fixed.



CR:612462
CR Number:   612462
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.0 2221 04 Jan 2010 Fixed
11.0.1 2368 26 Jan 2010 Fixed
10.0.1 4019 26 Jan 2010 Fixed
Description
Queries that contained a subquery that was rewritten by semantic transformations to flatten subqueries, could have failed with the error "Assertion failure 106104 (...) Field unexpected during compilation". This problem would only have occurred if the query block that was being flattened had a subquery in the SELECT list with outer references. This has now been fixed.



Note, a potential workaround is to modify the query so that it is no longer suitable for the semantic transformation that flattens the query block.



CR:612491
CR Number:   612491
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2368 23 Dec 2009 Fixed
Description
When connected to an UltraLite databaseand trying to import table data from a database using the Import Wizard, a dialog would have been displayed asking to select a database name from an empty list of databases. The list of databases is no longer offered since the concept has no meaning when connected to an UltraLite database.



CR:612617
CR Number:   612617
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.0 2234 19 Feb 2010 Fixed
11.0.1 2386 19 Feb 2010 Fixed
11.0.0 1654 19 Feb 2010 Fixed
10.0.1 4022 19 Feb 2010 Fixed
Description
If the row containing a particular unique value changed from one row to another, and then back again, snapshot transactions open before or during the updates might not return a row when expected, or return two copies of the expected row. This has now been corrected.



CR:612641
CR Number:   612641
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2197 05 Jan 2010 Fixed
11.0.1 2368 05 Jan 2010 Fixed
10.0.1 4005 05 Jan 2010 Fixed
Description
The Deployment wizard would have failed to work properly on Windows Vista and Windows 7. The wizard would have claimed to complete successfully, but the resulting MSI was invalid. The wizard was attempting to create a temporary file in the Program Files directory, which is disallowed by Windows Vista and Windows 7. This has now been corrected.



A workaround for this issue is to run the deployment wizard as an administrator.
Workaround Description
 - Run the deployment wizard as administrator

- If only deploying the admin tools, also include the Databases->SQL Anywhere->Client Interfaces->ODBC option as well. All other client interfaces and other SQL Anywhere components can be un-selected.



CR:613078
CR Number:   613078
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2122 04 Jan 2010 Fixed
Description
Upgrading a database that did not have a userid named DBA would have failed, intentionally leaving the database in an unusable state. This has been fixed by removing unnecessary grants to the DBA user. A workaround is to create a DBA userid before upgrading and drop it after upgrading.



CR:613079
CR Number:   613079
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.0 2122 04 Jan 2010 Fixed
Description
Applications using the version 6.x or 7.x ODBC driver or SQL Anywhere interface library (DBLib), would not have been able to connect to a version 12.x server. Connection attempts would have failed with the error "Connection error: Found server but communication error occurred." The server has been fixed so that applications using these client libraries can now connect successfully.



CR:613261
CR Number:   613261
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2201 07 Jan 2010 Fixed
11.0.1 2369 07 Jan 2010 Fixed
10.0.1 4010 07 Jan 2010 Fixed
9.0.2 3940 07 Jan 2010 Fixed
Description
Executing a query like the following from SQL Server Management Studio (2005):



select * from saoledblink..SYS.syscollation;



would have failed with the error:



Msg 7356, Level 16, State 1, Line 1

The OLE DB provider "SAOLEDB.11" for linked server "saoledblink" supplied nconsistent metadata for a column. The column "collation_order" (compile-time ordinal 4) of object ""SYS"."syscollation"" was reported to have a "DBCOLUMNFLAGS_ISFIXEDLENGTH" of 0 at compile time and 16 at run time.



The problem occurred for BINARY(n) columns. The DBCOLUMNFLAGS_ISFIXEDLENGTH schema attribute was set true (0x10) at run time. This problem has been fixed.



CR:613299
CR Number:   613299
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 3294 22 Feb 2011 Fixed
12.0.0 2649 22 Feb 2011 Fixed
11.0.1 2566 22 Feb 2011 Fixed
Description
Queries involving indexes could return incorrect results, and using tools such as the Validate Database Wizard in Sybase Central, or the Validation utility, could have reported index corruption when there was in fact none. For this to have occurred, the index must not have been unique and there must be many consecutive rows with the same indexed value. This has been fixed.



CR:613341
CR Number:   613341
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.0 2217 20 Jan 2010 Fixed
11.0.1 2378 20 Jan 2010 Fixed
10.0.1 4016 20 Jan 2010 Fixed
Description
If an application that was connected using jConnect or Open Client, queried the metadata of a long nvarchar, nvarchar, nchar, date or time column, then the metadata returned by the server would have been incorrect. This problem has now been resolved.



Note, in addition to getting an updated server, an ALTER DATABASE UPGRADE must be execute on each database, to update the metadata for jConnect and Open Client applications.



CR:613425
CR Number:   613425
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.0 2122 05 Jan 2010 Fixed
Description
When running a non-upgraded version 10 or 11 database, the server could have crashed when a user was dropped. This has been fixed.



CR:613426
CR Number:   613426
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.0 2122 08 Jan 2010 Fixed
Description
A change was made to improve the performance of Watcom SQL procedural language (stored procedures, batches, triggers and events).



CR:613429
CR Number:   613429
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2371 08 Jan 2010 Fixed
Description
An UltraLiteJ database with many committed transactions (more than the row maximum threshold) may have encountered a Null pointer exception during deletes and updates. This has been fixed.



CR:613436
CR Number:   613436
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2121 06 Jan 2010 Fixed
Description
A client application running on Windows Vista or Windows 7, could have crashed just after disconnecting the last connection. Specifically, the crash could have occurred just after the client library DLL (such as the ODBC driver) was unloaded. This has been fixed.



CR:613455
CR Number:   613455
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2265 06 Jan 2010 Fixed
Description
The SQL Anywhere Update Service could have recommended the incorrect bitness of a Windows EBF. For example, the Update Service could have recommended both bitnesses of the 11.0.1 Maintenance Release to customers of 11.0.0; or, it may recommended a 64-bit EBF to customers running 32-bit Windows. This has been corrected.



CR:613637
CR Number:   613637
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2374 12 Jan 2010 Fixed
Description
Unloading a version 11 database using the Unload utility (dbunload) such that dbunload used its internal unload/reload mechanism (i.e. -ii), could have then caused the Translation utility (dbtran) to crash when scanning the new database's transaction log for particular tables (command line option -it).



CR:613638
CR Number:   613638
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Mar 2011 Fixed
Description
The default settings for the way results are displayed can now set. In the OEM.ini file, the following values in the "[dbisql]" section are now recognized:



defaultShowResultsForAllStatements=false

defaultShowMultipleResultSets=false



These lines, if present, control the default behavior for displaying results. In the "Options" window, these options are displayed in the "Results Processing" box on the "Results" tab when "SQL Anywhere", "UltraLite", or "Sybase IQ" are selected. The default for both options is "false".



An optional prefix can be used to limit the effect to a specific database type. If no prefix is present, the directive applies to all database types. The prefixes are:



SQLAnywhere. For SQL Anywhere

Ultralite. For Ultralite

SybaseIQ. For IQ



For example,



defaultShowResultsForAllStatements=true



would change the default for all database types to show results for all statements, but



SQLAnywhere.defaultShowResultsForAllStatements=true



would change the default only for SQL Anywhere databases. The defaults for Ultralite and IQ would be unaffected. If a directive appears both with and without a prefix, the prefixed one has precendence for the given database type.



These directives can be specified independently. If one is missing, its default value (false) is assumed.



Notes:



1. These lines control only the default values for the two preferences. The defaults are used only if no saved user perferences are found. The user preferences are saved each time DBISQL is run.



2. "defaultShowMultipleResultSets" does not apply to UltraLite because UltraLite statements cannot return more than one result set.



CR:613642
CR Number:   613642
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)
11.0.1 2371 07 Jan 2010 Fixed
Description
It was not possible to set an HTTP status that was not explicitly supported (or known) by the SQLAnywhere server. This has now been fixed. Any three digit status code with an optional colon (':') delimited text message may now be specified.



Examples:

CALL SA_SET_HTTP_HEADER( '@HTTPSTATUS', '999:User Code'); // outputs status code with message: '999 User Code'

CALL SA_SET_HTTP_HEADER( '@HTTPSTATUS', '999'); // output status code only with no text message: '999'



Limitations/Recommendations:

- Status codes must be >= 100 and <= 999.

- A user defined status text message is not translated into database character-set when logged (log protocol option).

- It is recommended that user defined status messages are in English.



HTTP status code/message additions:

305 Use Proxy

307 Temporary Redirect

415 Unsupported Media Type

416 Requested Range Not Satisfiable

417 Expectation Failed

505 HTTP Version Not Supported



CR:613669
CR Number:   613669
Product Name:   SQL Anywhere
Product Component:   OLEDB Client Library
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2203 07 Jan 2010 Fixed
Description
Corrections and additions have been made to some of the SQL Anywhere OLE DB schema rowsets.



Changes to DBSCHEMA_PROVIDER_TYPES:

Changed CHAR type so that IS_FIXEDLENGTH is now FALSE (0).

Changed NCHAR type so that IS_FIXEDLENGTH is now FALSE (0).

Changed NUMERIC type so that IS_FIXEDLENGTH is now TRUE (1).

Changed DECIMAL type so that IS_FIXEDLENGTH is now TRUE (1).

Changed LONG NVARCHAR type so that IS_LONG is now TRUE (1).

As a result of these changes, "compile time" results will now agree with "run time" results (ref. MS Linked Servers).



Support was added for ST_GEOMETRY and TIMESTAMP WITH TIME ZONE types.



Changes to DBSCHEMA_COLUMNS:

The COLUMN_FLAGS column of the OLE DB schema rowset has been corrected.

The DBCOLUMNFLAGS_ISFIXEDLENGTH indicator is now set on for fixed length types (e.g., smallint, float, money).

The DBCOLUMNFLAGS_ISLONG indicator is now set on for LONG types (e.g., LONG VARCHAR).

Added support for ST_GEOMETRY and TIMESTAMP WITH TIME ZONE types.



Changes to DBSCHEMA_PROCEDURE_COLUMNS:

Added support for ST_GEOMETRY and TIMESTAMP WITH TIME ZONE types.



Changes to DBSCHEMA_PROCEDURE_PARAMETERS:

Added support for ST_GEOMETRY and TIMESTAMP WITH TIME ZONE types.



CR:613672
CR Number:   613672
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)
11.0.1 2370 11 Jan 2010 Fixed
Description
The server may have crashed during query optimization for a statement with subqueries which were flattened (i.e., transformed into joins). At least one of the subquery must have contained a DUMMY table and the main query block must have required a DISTINCT to be done. This has been fixed.



An example:



select * from

product p

where exists (select 30 as id from dummy, product p2 where p2.id-1 > 30+p.id )

and p.id+1 = 301 and exists(select 1 from sales_order_items soi where soi.id > p.id)



CR:613816
CR Number:   613816
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.0 2204 08 Jan 2010 Fixed
11.0.1 2371 08 Jan 2010 Fixed
10.0.1 4011 08 Jan 2010 Fixed
Description
If an application connects using an older version of jConnect or Open Client, and subsequently fetches a Time or Timestamp value, then the server is required to round the fractional seconds portion of the Time/Timestamp value up to the nearest 1/300th of a second. For these older versions of jConnect or Open Client, the server would not always have properly rounded the fractional seconds portion up to the nearest 1/300th of a second. This problem has now been fixed.



Note that newer versions of jConnect and Open Client support microsecond precision, so no rounding to 1/300th of second will occur if an application uses these newer versions.



CR:613838
CR Number:   613838
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2371 08 Jan 2010 Fixed
Description
When a row minimum threshold was specified that was too low (< 200), UltraLiteJ would have chosen 200, and then checked the maximum threshold. If the maximum threshold was less than the (adjusted) minimum threshold, it would choose minimum+500. This has been corrected so that it now accepts a minimum row threshold of 100 and if the maximum is less than theminimum, the maximum is set to minimum + 50.



Note that applications may be forced to use small threshold values if they have many transactions awaiting synchronization. This is fixed by synchronizing more frequently.



CR:613984
CR Number:   613984
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2218 22 Jan 2010 Fixed
11.0.1 2378 22 Jan 2010 Fixed
10.0.1 4017 22 Jan 2010 Fixed
Description
Rebuilding version 9 or earlier databases using the Unload utility (dbunload) could have failed with the error "Unable to start specified database: autostarting database failed" if the old database had been run with database auditing. This has been fixed.



CR:613986
CR Number:   613986
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2371 12 Jan 2010 Fixed
Description
Synchronizations could have failed after multiple updates and database closings. This has now been fixed.



CR:613999
CR Number:   613999
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)
11.0.1 2373 12 Jan 2010 Fixed
10.0.1 4013 12 Jan 2010 Fixed
Description
OEM Edition servers would have crashed when started with the -fips switch. This has been fixed.



CR:614016
CR Number:   614016
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Generic
Original Version:   6.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2375 13 Jan 2010 Fixed
Description
Attempting to rename a Maintenance Plan using the wizard would always have failed with the error "A maintenance plan with the specified name already exists in this database". The old and new names were not being tracked correctly by the wizard. This has been fixed.



CR:614034
CR Number:   614034
Product Name:   MobiLink
Product Component:   QAnywhere server
Status:   Closed
OS:   Windows 2000
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2372 11 Jan 2010 Fixed
10.0.1 4012 11 Jan 2010 Fixed
Description
When a 9.0.2 QAnywhere client synchronized, the MobiLink server would have displayed the following errors:

Expecting 1 parameters in script, but only found 4: update ml_qa_global_props set modifiers = ?, value = ? where client = ? and name = ?

Unable to open upload_update .



This has been fixed by a change to the upload_update script for the table ml_qa_global_props, version ml_qa_2.
Workaround Description
 None.



CR:614064
CR Number:   614064
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2373 11 Jan 2010 Fixed
Description
UltraLiteJ databases created as File Write At End or In Memory, would not have allowed alter operations if there transactions with multiple operations on the same row.



For example:

Given a table Test that had synchronization disabled, after the sequence

INSERT INTO Test( num, val ) VALUES( 1, 0 )

UPDATE Test SET val = 2 WHERE num = 1

COMMIT

it would have no longer been possible to alter the schema of table Test. Attempts to do so would have resulted in UltraLiteJ Error[-121]: Permission denied: unsynced transactions



This has now been fixed.



CR:614245
CR Number:   614245
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)
11.0.1 2373 12 Jan 2010 Fixed
Description
When more than one Relay Server Outbound Enabler (RSOE) in the same backend server farm used the same server id to connect to the Relay Server, the Relay Server would have reported that there was a conflict, and let the newer RSOE instance win over the existing RSOE connection. There was a small chance that the old RSOE connection may have reported the error "Internal error! Freeing already freed memory!" during the disconnect process. Although the memory manager in versions 11.0.1 2335 or higher of the Relay Server is immune from such memory problems, and will keep working normally, a fix has been made to further stop the cause of this memory problem in order to stop the internal error from occuring at all.



CR:614247
CR Number:   614247
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)
11.0.1 2373 11 Jan 2010 Fixed
Description
The server may have crashed after query optimization of a statement with a parallel plan, for which the EXCHANGE physical operator must preserve the ordering of the rows from the input stream, and a prefilter predicate exists before the Exchange operator. This has been fixed.



For example, if the query below has the plan "p<xx> Exchange p<xx>", the output of the Exchange operator must preserve the ordering of the rows on "p.id" provided by the scans of the index "xx". This query crashed the server before this fix. The prefilter predicate is "now() > now()".



select * into #temp1 from product;

create index xx on #temp1(id);



select p.id from #temp1 p where now() > now() order by p.id;



CR:614405
CR Number:   614405
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.0 2123 13 Jan 2010 Fixed
11.0.1 2374 13 Jan 2010 Fixed
11.0.0 1654 13 Jan 2010 Fixed
10.0.1 4013 13 Jan 2010 Fixed
Description
The server could have have an assertion, or crashed, when reinserting a deleted non-null value into a unique index. In rare cases, database corruption was possible. System and temporary table indexes were not affected. This has now been fixed.



CR:614417
CR Number:   614417
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)
11.0.1 2376 19 Jan 2010 Fixed
10.0.1 4016 19 Jan 2010 Fixed
Description
The MobiLink server could have crashed when processing a synchronization request from a client, if the client was older than version 10 and was syncing UUID columns. This has been fixed.



CR:614432
CR Number:   614432
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.0 2210 13 Jan 2010 Fixed
Description
The Information utility (dbinfo) will now show the CHAR collation specification, CHAR encoding, NCHAR collation specification and NCHAR encoding, instead of the old "Respect letter-case when comparing" and "Collation sequence" fields.



For example, the following two lines of dbinfo:

Respect letter-case when comparing: No ('A' equal to 'a')

Collation sequence: 1252LATIN1 (Code Page 1252, Windows Latin 1, Western)

have been replaced by:

CHAR collation sequence: 1252LATIN1(CaseSensitivity=Ignore)

CHAR character set encoding: windows-1252

NCHAR collation sequence: UCA(CaseSensitivity=Ignore; AccentSensitivity=Ignore; PunctuationSensitivity=Primary)

NCHAR character set encoding: UTF-8

which matches the output displayed by the Initialization utility.



CR:614592
CR Number:   614592
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.0 2211 13 Jan 2010 Fixed
Description
One of the values that could have been returned for the lock_type column of the sa_locks procedure was 'WriteNonPK', which is longer than the the char(9) column definition. This was corrected by shortening the 'WriteNonPK' value to 'WriteNoPK'



CR:614625
CR Number:   614625
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.0 2211 15 Jan 2010 Fixed
11.0.1 2375 15 Jan 2010 Fixed
Description
The MobiLink client would have ignored the command line option -a. This has been fixed.



CR:614632
CR Number:   614632
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 4014 18 Jan 2010 Fixed
Description
In rare circumstances, calling the system function db_property() to retrieve a database property from a database other than the one connected to (for example, when calling sa_db_info()), may have resulted in invalid data being returned. This would only have occurred if the property being requested returned a string, and conversion between the character sets of the two databases was unnecessary. This has been fixed.



CR:614778
CR Number:   614778
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.0 2121 14 Jan 2010 Fixed
Description
When loading geometry values from an ESRI shapefile, the incorrect grid size and tolerance were applied during the loading process. This could have lead to geometries being improperly rejected with an error at load time. This problem primarily arose for round-Earth spatial reference systems and those with a non-default grid size or tolerance. This has been fixed.



CR:614782
CR Number:   614782
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.0 2213 19 Jan 2010 Fixed
11.0.1 2376 19 Jan 2010 Fixed
Description
If the plan chosen for a query used a nested-loops outer join, and the cursor was used with a mixture of forward and backward fetches, it was possible for the server to return the wrong answer for the query. This has been fixed. A possible work-around for the problem is to use an insensitive or keyset-driven cursor type.



CR:614805
CR Number:   614805
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.0 2212 18 Jan 2010 Fixed
Description
Clicking the "Test Connection" button in the SQL Anywhere Monitor when creating a MobiLink resource would have caused the Monitor to hang. The MobiLink server log would have contained the errors: "<4> [-10004] Protocol version mismatch -- expecting 34 but received 49" and " "<4> failed reading command with id:1 and handle:26". This has been fixed.



CR:614818
CR Number:   614818
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2272 23 Feb 2010 Fixed
11.0.1 2399 23 Feb 2010 Fixed
Description
When deploying support for dbunload to a windows CE device, the following scripts were missing: unloadold.sql, optdeflt.sql and opttemp.sql. These are now deployed to the device.



CR:614976
CR Number:   614976
Product Name:   MobiLink
Product Component:   Relay Server
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2206 15 Jan 2010 Fixed
11.0.1 2373 15 Jan 2010 Fixed
Description
The Relay Server Outbound Enabler (RSOE) may not have relayed backend server responses when under a sustained high load of requests. The problem was more likely to occur when the network between the client and Relay Server (RS), as well as the network between the RS and the RSOE, were both very fast while the backend server machine was relatively slow in processing. Turning on high RSOE verbosity in such situation would have caused this problem to be more likely to occur. A fix has now been made in the RSOE to solve this problem.



CR:615212
CR Number:   615212
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.0 2233 02 Feb 2010 Fixed
11.0.1 2385 02 Feb 2010 Fixed
10.0.1 4022 02 Feb 2010 Fixed
Description
When computing an aggregate function such as AVG() or SUM(), it was possible for the result of the calculation to overflow the bounds of the data type used for accumulation, leading to an answer that was not numerically correct. Even if the option Ansi_integer_overflow was set to 'On', the overflow was not reported as an error. If AVG() or SUM() overflowed an INT type, then the argument to the aggregate can be cast to DOUBLE or NUMERIC to avoid the overflow (with a concomitant performance degradation). In specific conditions, an arithmetic operation could have caused a server crash. This has been fixed.



CR:615239
CR Number:   615239
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.0 2217 22 Jan 2010 Fixed
11.0.1 2378 22 Jan 2010 Fixed
Description
A web services stored procedure did not automatically process query parameters for HTTP PUT and POST methods. This has been fixed.



Examples:

CREATE SERVICE echo ...

CREATE SERVICE echo_elem URL ELEMENTS ...

CREATE SERVICE echo_path URL ON ...



HTTP Requests:

PUT echo?id=1 HTTP/1.1 ==>

HTTP_VARIABLE('id') == 1,

HTTP_HEADER('@HTTPQUERYSTRING') == id=1

PUT echo_elem/one/two?id=1 HTTP/1.1 ==>

HTTP_VARIABLE('id') == 1,

HTTP_VARIABLE('url1') == one,

HTTP_VARIABLE('url2') == two,

HTTP_HEADER('@HTTPQUERYSTRING') == id=1

PUT echo_path/one/two?id=1 HTTP/1.1 ==>

HTTP_VARIABLE('id') == 1,

HTTP_VARIABLE('url') == one/two,

HTTP_HEADER('@HTTPQUERYSTRING') == id=1



CR:615254
CR Number:   615254
Product Name:   SQL Anywhere
Product Component:   DBLIB Client Library
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2216 19 Jan 2010 Fixed
11.0.1 2377 19 Jan 2010 Fixed
10.0.1 4016 19 Jan 2010 Fixed
Description
If a percent character "%" was used in a RAISERROR statement, then retrieving the error using sqlany_error() would have returned garbage characters for the percent character. This has been fixed.



CR:615255
CR Number:   615255
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)
12.0.0 2216 19 Jan 2010 Fixed
11.0.1 2377 19 Jan 2010 Fixed
10.0.1 4016 19 Jan 2010 Fixed
Description
When run on Windows CE, the server may have reported an inaccurate reason when a file error occurred. A server that was using the ICU library (dbicudtnn.dll) could have reported a general I/O error if the database file did not exist. A server that was not using ICU could report that a database file did not exist error when a different file error occurred. This has been fixed.



CR:615422
CR Number:   615422
Product Name:   MobiLink
Product Component:   Synchronization Server
Status:   Open
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2213
Description
It was not possible to use Java or .NET scripts for the authenticate_file_upload event. This has been fixed.



CR:615446
CR Number:   615446
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.0 2217 20 Jan 2010 Fixed
Description
A "long" hex constant string in a SQL query would have been treated as being a CHAR() datatype, rather than BINARY() data. In this case "long" refers to a string which is longer than approximately one database page size after converting the hex to binary (ie, the original hex string is approximately two pages in length). This problem has been fixed.



CR:615447
CR Number:   615447
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.0 2217 20 Jan 2010 Fixed
11.0.1 2377 20 Jan 2010 Fixed
Description
Queries containing procedure calls in the FROM clause may have failed to execute, or the procedure was not in-lined which may have resulted in very poor performance. For this problem to have occurred, the procedure must have contained common table expressions defined with the "WITH [RECURSIVE] ..." clause, and the procedure must have qualified to be in-lined into the query block in which it was used. This has been fixed.



For more information on in-lining procedures see "SQL Anywhere 11.0.1 SQL Anywhere Server - SQL Usage Query Processing Query optimization and execution Semantic query transformations In-lining simple system procedures "



http://dcx.sybase.com/index.html#1101en/dbusage_en11/ug-optimizer-s-4906935.html



CR:615448
CR Number:   615448
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.0 2217 20 Jan 2010 Fixed
Description
Certain database objects, such as stored procedures, are stored in canonical form. When "long" CHAR or NCHAR constants in a SQL statement were transformed into canonical form, the canonical form could have been incorrect, such that the canonical statement could not be parsed, or that the original data would not be returned when it was parsed. A "long" constant in this context is one in which the internal representation is approximately one database page size in length or longer. This problem has been fixed.



CR:615473
CR Number:   615473
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10.0.1 4030 22 Feb 2010 Fixed
Description
When installing the Japanese 10.0.1 3990 EBF, some of the characters in various buttons of the installer containing an unintelligible sequence of characters (mojibake). The character encoding used when compiling the installer was incorrect, this has been fixed.



Note, the installer for the 10.0.1 3976 EBF worked correctly.



CR:615481
CR Number:   615481
Product Name:   SQL Anywhere
Product Component:   Sybase Central Plug-in
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2228 27 Oct 2010 Fixed
11.0.1 2382 02 Feb 2010 Fixed
Description
When doing a 64 bit install, if only the SQL Anywhere and Administration Tool features were selected, some operations in Sybase Central would have failed. This has been fixed.



CR:615614
CR Number:   615614
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.0 2218 22 Jan 2010 Fixed
11.0.1 2378 22 Jan 2010 Fixed
Description
Dropping a login policy, or a synchronization profile, would not have also deleted the corresponding row in the system table ISYSOBJECT. This has been fixed.



CR:615617
CR Number:   615617
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.0 2337 26 Mar 2010 Fixed
11.0.1 2414 26 Mar 2010 Fixed
10.0.1 4048 26 Mar 2010 Fixed
Description
If an application connected via jConnect attempted to retrieve the column metadata of a result set that contained a varbit, long varbit, nchar, nvarchar long nvarchar, or uniqueidentifier column, then the column metadata would have been returned with an unknown datatype. This problem has now been fixed.



CR:615627
CR Number:   615627
Product Name:   SQL Anywhere
Product Component:   Server
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2218 22 Jan 2010 Fixed
11.0.1 2378 22 Jan 2010 Fixed
10.0.1 4017 22 Jan 2010 Fixed
Description
When using snapshot isolation, the Validate utility (dbvalid), or the "VALIDATE DATABASE" statement, may have spuriously report the error "Database validation failed for page xxxx of database file". These errors would then have disappeared after a clean shutdown of the database. This has been fixed.



CR:615655
CR Number:   615655
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   10.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2218 22 Jan 2010 Fixed
11.0.1 2378 22 Jan 2010 Fixed
10.0.1 4017 22 Jan 2010 Fixed
Description
For some types of page corruption, the Validate utility (dbvalid) could have reported incorrect page numbers. This has now been corrected.



CR:615671
CR Number:   615671
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.0 2218 22 Jan 2010 Fixed
Description
Commas appearing anywhere in an index hint would have been interpreted as index name deliminators. For instance, the hint INDEX([a, b], c) would have been interpreted to mean the indexes "a", "b", and "c", rather than an index named "a, b" and an index named "c". This has been fixed so that it is now possible to supply hints for indexes

with a comma in their names, provided the name is properly quoted.



CR:615813
CR Number:   615813
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.0 2218 25 Jan 2010 Fixed
11.0.1 2378 25 Jan 2010 Fixed
Description
The Relay Server does not support running more than one Outbound Enabler per backend server if they are started with the same backend server id. If this limitation for a unique backend server id was violated, some traffic to that backend server may either have failed, or suffered slowness. This problem has been fixed. The Relay service to other backend servers is no longer affected by this issue. The second and subsequent instances are not functional.



CR:615828
CR Number:   615828
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.0 2208 22 Jan 2010 Fixed
11.0.1 2373 22 Jan 2010 Fixed
Description
The Relay Server Outbound Enabler (RSOE) could have sporadically crashed on startup. This has been fixed.



CR:615834
CR Number:   615834
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.0 2220 22 Jan 2010 Fixed
11.0.1 2379 22 Jan 2010 Fixed
Description
The REGEXP_SUBSTR function could have returned incorrect results when the start-offset parameter was specified. In particular, regular expressions with '^' (match start of string) may not have matched when they should have, and lookbehind assertions may have matched when they should not have. Also, specifying an invalid start-offset or occurrance-number, may have returned a match when it should not have. This has been fixed so that the start-offset specifies the beginning of the expression to match, and '^' will match the beginning of the expression starting at start-offset.



CR:615855
CR Number:   615855
Product Name:   MobiLink
Product Component:   ASA Client
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2213 22 Jan 2010 Fixed
11.0.1 2376 22 Jan 2010 Fixed
Description
The MobiLink client (dbmlsync) could have crashed on shutdown when run on linux systems.

This problem also affected applications using dbmlsync through the dbtools interface. They could have crashed when DBToolsFini was called. This has now been fixed.



CR:615861
CR Number:   615861
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.0 2220 25 Jan 2010 Fixed
11.0.1 2379 25 Jan 2010 Fixed
Description
The Relay Server Outbound Enabler was over using memory for buffering upward data. This has been fixed.



CR:615994
CR Number:   615994
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.0 2221 25 Jan 2010 Fixed
11.0.1 2379 25 Jan 2010 Fixed
Description
If a domain was created after editing columns in a table, then the newly created domain would not have appeared in the Table Editor's Data Type drop-down list until the table was manually refreshed by pressing F5. This has been fixed.



CR:616015
CR Number:   616015
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2221 25 Jan 2010 Fixed
11.0.1 2379 25 Jan 2010 Fixed
Description
The QAnywhere Agent could have failed with the error: "Internal error: Too many MESSAGE ... FOR CONNECTION messages". This has been fixed.



CR:616017
CR Number:   616017
Product Name:   MobiLink
Product Component:   QAnywhere client
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2378 25 Jan 2010 Fixed
11.0.1 2218 25 Jan 2010 Fixed
Description
The QAnywhere Agent would have failed to upgrade 9.0.2 message stores that were created with SQL Anywhere 9.0.2 builds 3654 and later. This has been fixed.



CR:616031
CR Number:   616031
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   11.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2221 26 Jan 2010 Fixed
11.0.1 2379 26 Jan 2010 Fixed
Description
On Unix systems other than Linux, JAR files were installed with 0700 permissions, which meant that they were only usable by the user who ran the install. This has been fixed so that executables, shared objects, and shell scripts are now installed with 0555 permissions, while the permissions of all other files will be 0444.



As a workaround, the following command may be run to fix the permissions of the JAR files:



find $SQLANY11 -name "*.jar" -exec chmod 444 {} \;



CR:616038
CR Number:   616038
Product Name:   SQL Anywhere
Product Component:   Utilities
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2227 28 Jan 2010 Fixed
11.0.1 2383 28 Jan 2010 Fixed
Description
If the Log Translation utility (dbtran) was run using both the -m (read log files from a directory) and -ir (range of log offsets) flags, the following error would have been reported:

Transaction log file '<logfile1>' overlaps with transaction log file '<logfile2>'

This has been fixed.



CR:616040
CR Number:   616040
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.0 2221 26 Jan 2010 Fixed
11.0.1 2379 26 Jan 2010 Fixed
Description
When the Relay Server Outbound Enabler console was opened with high verbosity logging set, the Outbound Enabler performance could have been significantly degraded. This has been fixed by removing log information at verbosity level 1 and above from the console display, but leave them in the log file only. To restored the old behavior of displaying all information to the console, use the new -dl command line option.



CR:616196
CR Number:   616196
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 2380 26 Jan 2010 Fixed
Description
Older MobiLink clients (prior to Version 10) would have caused the server to log a Protocol Error, when attempting to restart a download. This has been fixed. Restartable downloads for older clients is not supported, so the server will now log the restart failure and send a status code to the client.



CR:616214
CR Number:   616214
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.0 2228 02 Feb 2010 Fixed
11.0.1 2383 02 Feb 2010 Fixed
Description
The server allows the LOAD TABLE statement to be executed in a mode where the contents of the input file are recorded into the transaction log so that the original data source is no longer needed in the event of the database recovery. The logging of file contents in the transaction log can be triggered explicitly, e.g., if the WITH CONTENT LOGGING clause is used, or implicitly for certain forms of LOAD TABLE, e.g., when the USING CLIENT FILE clause is used. The LOAD TABLE statement could have failed with an error when executed from within a stored procedure if the user executing the procedure was different from the login user for the connection. This has been fixed so that the server now executes the LOAD TABLE statement correctly in these circumstances.
Workaround Description
 *** Monday, January 25, 2010 10:01:52 AM *** lewist ***

We have been able to create a work-around using temporary tables. If a temporary table is created at the beginning of a stored procedure with the ON COMMIT PRESERVE ROWS clause it can be populated using the "LOAD TABLE ... USING CLIENT FILE ..." statement. The rows from the temporary table can then be inserted into the table owned by the stored procedure's owner.



CR:616221
CR Number:   616221
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.0 2123 26 Jan 2010 Fixed
Description
Estimates of the number pages for tables and indexes in the cache, that were used by the optimizer, were not being correctly maintained, causing poor plan selection. This has been corrected.



CR:616222
CR Number:   616222
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.0 2123 26 Jan 2010 Fixed
Description
Comments were not being saved on sequence objects. This has been fixed.



CR:616227
CR Number:   616227
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.0 2224 27 Jan 2010 Fixed
11.0.1 2380 27 Jan 2010 Fixed
Description
Connection attempts that used TLS would have failed with handshake failures on 64-bit Mac clients. This has been fixed.



CR:616231
CR Number:   616231
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.0 2381 26 Jan 2010 Fixed
11.0.1 2225 26 Jan 2010 Fixed
Description
An HTTP/SOAP request may have caused the SQL Anywhere server to crash under certain circumstances. This has been fixed.



CR:616239
CR Number:   616239
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.0 2224 26 Jan 2010 Fixed
11.0.1 2380 26 Jan 2010 Fixed
Description
Under sustained high load from a Relay Server, the Outbound Enabler may not have performed well enough, resulting in client timeouts. A performance improvement has been made to the Outbound Enabler to correct this problem.



CR:616385
CR Number:   616385
Product Name:   SQL Anywhere
Product Component:   ODBC Client Library
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2238 28 Jan 2010 Fixed
11.0.1 2388 28 Jan 2010 Fixed
10.0.1 4023 28 Jan 2010 Fixed
Description
When making continuous ODBC connections and disconnections, using the ANSI entry points to SQLConnect() and SQLDisconnect(), a memory leak would have occurred in the application. The UNICODE versions of SQLConnect() and SQLDisconnect() (i.e., SQLConnectW() ) were not affected by this problem. The process heap will continue to grow as the application loops. This problem has been fixed.



See also Engineering case 608095.



CR:616395
CR Number:   616395
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.0 2225 26 Jan 2010 Fixed
11.0.1 2381 26 Jan 2010 Fixed
10.0.1 4019 26 Jan 2010 Fixed
Description
The system procedure sa_split_list() did not work as expected when a multi-character delimiter was provided, and the string to be split was shorter than the delimiter. No rows were returned, whereas the expected result was a single row containing the string to be split. This has been fixed.



CR:616435
CR Number:   616435
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.0 2225 28 Jan 2010 Fixed
11.0.1 2381 28 Jan 2010 Fixed
Description
When using the Create Database wizard to create a database on the local machine while having no servers running the local machine, the newly created database would have been started on the server, but would not have been the local machine's default server. This has been fixed.



CR:616437
CR Number:   616437
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.0 2225 01 Feb 2010 Fixed
11.0.1 2381 01 Feb 2010 Fixed
Description
Selecting a server's "All Connections" tab could have caused an error and fail to display the list of connections, if Sybase Central was connected only to the server's utility database. This has been fixed.



CR:616635
CR Number:   616635
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2123 27 Jan 2010 Fixed
Description
Header files for external libraries to be used with full text searching were missing from the installed software. This has been fixed.



CR:616637
CR Number:   616637
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.0 2226 09 Feb 2010 Fixed
Description
A query in which a SELECT FROM DML DTB appeared within one of the query blocks inside a query expression (a UNION, EXCEPT or INTERSECT query) could have given the error "Update operation attempted on non-updatable query" (SQLCODE -192). This has been fixed.



CR:616654
CR Number:   616654
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.0 2226 28 Jan 2010 Fixed
Description
Certain client-side error messages in a dblib application could have been returned in the OS character set, rather than the character set that the application had chosen for the connection. The affected messages were typically generated by an attempt to use a connection that had terminated abnormally, in which case dblib used the OS character set because it lost track of the connection's character set when the connection terminated. Of course, if the connection had chosen to use the OS character set the problem would not be noticed. This problem has been fixed by keeping track of the character set of the last connection that was used with each SQLCA and returning error messages in that character set. Dblib tracks any change to a connection's character set when communicating with a database server which is version 11.0.0 or newer. When connected to servers earlier than version 11.0.0, dblib is unable to track the character set of a connection if the application calls db_change_char_charset() with a character set name of "none" (ie, equivalent to database CHAR character set) but it will track the change when the character set is changed to an explicit name (eg "UTF-8").



CR:616656
CR Number:   616656
Product Name:   SQL Anywhere
Product Component:   Other
Status:   Closed
OS:   Microsoft Windows
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.0.0 2265 18 Feb 2010 Fixed
11.0.1 2395 18 Feb 2010 Fixed
10.0.1 4029 18 Feb 2010 Fixed
Description
When using the SQL Anywhere PHP module, and binding a null numeric value to a statement with sasql_stmt_bind_param_ex, the null value would have been converted to a 0. This resulted in a 0 being passed in the statement instead of the desired null value. Resetting the variable to null after binding would have given the desired behavior. This has now been fixed.



CR:616657
CR Number:   616657
Product Name:   UltraLiteJ
Product Component:   Runtime
Status:   Closed
OS:   Generic
Original Version:   12.0.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
2226 28 Jan 2010 Fixed
11.0.1 2381 28 Jan 2010 Fixed
Description
On BlackBerry devices and simulators, very large tables/databases (many rows) could have resulted in an OutOfMemory error, even when lazy loading and row limiting was enabled. This has been fixed.



CR:616829
CR Number:   616829
Product Name:   SQL Remote for SQL Anywhere
Product Component:   SQL Remote for Adaptive Server Anywhere
Status:   Closed
OS:   Generic
Original Version:   9.0.2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
9.0.2 3950 28 Jan 2010 Fixed
10.0.1 4020 28 Jan 2010 Fixed
11.0.0 1654 28 Jan 2010 Fixed
11.0.1 2383 28 Jan 2010 Fixed
12.0.0 2227 01 Feb 2010 Fixed
Description
If the SQL Remote Message Agent (dbremote) connected to a database that had remote or consolidated users defined, but did not have a publisher defined, then dbremote would not have reported any errors, but would have simply reported "Execution Complete". This has been corrected so that dbremote will now report an error indicating that no publisher was defined in the database.



CR:616956
CR Number:   616956
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.0 2228 01 Feb 2010 Fixed
11.0.1 2384 01 Feb 2010 Fixed
Description
When clicking the 'View Code' button in the breakpoints dialog, the error "The source code could not be displayed for the <procedure/event/trigger> because the database filter is excluding it." may have been shown. This has now been fixed.



CR:616981
CR Number:   616981
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.0 2245 09 Feb 2010 Fixed
11.0.1 2391 09 Feb 2010 Fixed
Description
An ALTER VIEW statement that changed the view definition, would have silently dropped any INSTEAD OF triggers on the view. This has been fixed so that the server will now return the error "Operation failed because table or view '%1' has an INSTEAD OF trigger".



CR:616985
CR Number:   616985
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.0 2228 02 Feb 2010 Fixed
11.0.1 2384 02 Feb 2010 Fixed
10.0.1 4021 02 Feb 2010 Fixed
Description
If an application attempted to fetch long string data from a proxy table, and the ODBC driver being used to connect to the remote server did not support UNICODE entry points, then there was a chance the fetched data would have been missing some characters. This problem has now been fixed.



Note, there are very few ODBC drivers that do not support UNICODE entry points. As a result, this problem affects a very small number of applications that use remote servers.



CR:616997
CR Number:   616997
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.0 2228 02 Feb 2010 Fixed
11.0.1 2384 02 Feb 2010 Fixed
Description
Relay Server Ooutbound Enabler could have been slow in connecting to a backend server when it used a host name, instead of a dotted IP address, in the -cs option. This connect performance issue has been fixed. Using a host name in the -cs switch should no longer causes performance issues. The workaround is to use dotted ip address.



CR:617154
CR Number:   617154
Product Name:   SQL Anywhere
Product Component:   ISQL
Status:   Closed
OS:   Generic
Original Version:   11.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11.0.1 2383 01 Feb 2010 Fixed
Description
The Interactive SQL utility (dbisql) could have failed to connect when using a Japanese DSN name that was passed as a connection parameter. Double-byte characters were being mangled when provided in a parameter to dbisql. This has now been fixed.



CR:617161
CR Number:   617161
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.0 2232 02 Feb 2010 Fixed
11.0.1 2385 02 Feb 2010 Fixed
Description
An HTTP request requiring certain character set conversion criteria may have caused the SQL Anywhere server to crash. This has been fixed.



CR:617165
CR Number:   617165
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.0 2124 03 Feb 2010 Fixed
11.0.1 2387 03 Feb 2010 Fixed
Description
INSTEAD OF triggers on views were not being unloaded by the Unload utility (dbunload). This has been fixed.



CR:617169
CR Number:   617169
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.0 2228 02 Feb 2010 Fixed
Description
If a query contained a predicate "a = b" for geometry values a and b, it was possible in some cases for the server to crash. This has been fixed.



CR:617177
CR Number:   617177
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.0 2235 04 Feb 2010 Fixed
11.0.1 2386 04 Feb 2010 Fixed
10.0.1 4022 04 Feb 2010 Fixed
Description
On Solaris SPARC systems, the 32-bit SQL Anywhere libraries were linked against libC.so.5, the compatibility libC variant, even though the libraries were not compiled in compatibility mode (i.e., -compat=4 was not used when compiling the libaries). A C++ application that was not itself linked against libC.so.5 could have crashed when trying to load these libraries. The libraries are no longer linked against libC.so.5 and now are only linked against libCrun.so.1. C++ client applications compiled with the -compat=4 compatibility flag, or linked against libC.so.5, are not supported.





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