存档
专注于Sybase ASE以及Sybase ASA数据库文件的恢复。专注于各种勒索病毒加密数据库的修复。
联系手机： 13811580958（微信），QQ： 289965371！
郑重承诺，修不好不收费。客户验证数据的正确性后，再付款。
一、Sybase ASE数据库恢复工具READSYBDEVICE主要功能有：
- 被勒索病毒加密数据文件及备份文件情况下的恢复；
- 系统崩溃只剩下数据文件的情况下的恢复，甚至数据库文件不存在而只有损坏的备份文件情况下的恢复；
- 因断电、硬盘坏道等造成数据库文件损坏情况下的恢复；
- delete数据恢复、误update数据恢复、误删除表(drop）恢复、误truncate表恢复 等；
- 各种sybase内部系统表损坏、索引错误的修复；
- master数据库损坏而无法正常运行情况下的恢复；
- sybase数据库被标记为可疑，不可用等情况的恢复；
- sybase数据库中数据文件内部出现坏块情况下的恢复；
- sybase数据库无数据文件但有日志文件的情况下的恢复；
- sybase数据库只有数据文件无任何日志文件的情况下的恢复；
- sybase数据文件被误删除情况下的碎片提取恢复；
- 磁盘阵列上的sybase数据库被误格式化情况下的数据库恢复；
- 数据库sysobjects等系统表损坏无法正常应用情况下的恢复；
- sybase数据库还原数据库出现失败情况下的恢复；
- sybase数据库只剩下损坏的备份文件情况下的恢复。
二、Sybase ASE数据库恢复工具READSYBDEVICE支持的版本：
Sybase ASE 11.0.x，11.5.x，11.9.2，12.0.x，12.5.x，15.0.x，15.5.x，15.7.x，16.0.x
三、Sybase SQL Anywhere （ASA）数据库恢复工具ReadASADB功能：
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具
- 适用于所有的SQL Anywhere版本 包括：5.x,6.x,7.x,8.x,9.x,10.x,11.x,12.x,16.x
- 适用于所有的UltraLite版本
- 能够恢复出来表结构和数据
- 能够恢复自定义数据类型
- 能够恢复存储过程等对象的语法
- 能够导出到目标数据库
- 能够导出到SQL文件并生成导入脚本
- 支持多种字符集 包括：cp850、cp936、gb18030、utf8等
- 能够恢复未加密或者简单加密类型的数据
- 简单易用
- 限制：不支持AES加密的数据文件
四、Sybase SQL Anywhere （ASA）数据库恢复工具ReadASADB适用场景：
各种误操作：
- 误截断表(truncate table)
- 误删除表(drop table)
- 错误的where条件误删数据
- 误删除db或log文件
- 误删除表中的字段
随着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信息！
不仅仅包括BUG的详细描述信息，还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程；有些BUG还提供了Workaround来临时解决该BUG带来问题。
SQL Anywhere的所有已知BUG列表（1）
SQL Anywhere的所有已知BUG列表（2）
SQL Anywhere的所有已知BUG列表（3）
SQL Anywhere的所有已知BUG列表（4）
SQL Anywhere的所有已知BUG列表（5）
SQL Anywhere的所有已知BUG列表（6）
SQL Anywhere的所有已知BUG列表（7）
SQL Anywhere的所有已知BUG列表（8）
| CR Number |
Description |
| 740222 | When describing a cloud server running on a Linux host, the TCP addresses listed may have include �::1�. This has been fixed. |
| 740226 | Using '*' when specifying the publication list would have caused the UltraLite runtime to crash during a synchronization. This has been fixed. |
| 740328 | The Relay Server would have incorrectly stopped relaying and reported the error RSE4008 with 揗alformed HTTP chunk� when it encountered chunked server responses with valid extensions or trailers (see RFC2616 section 3.6.1). This has been fixed. Logging of the extensions and trailers were added for log level 4 and higher. |
| 740334 | The ICommandPersist interface methodes, LoadCommand, DeleteCommand, and SaveCommand, did not qualify system tables references with an owner name. This has been corrected. |
| 740400 | In rare cases, a copy node or mirror server could have used more memory than expected. If this occurred, the extra memory would typically have been less than 1MB. This has been fixed. |
| 740412 | The 32-bit version of the Version 9 or earlier physical store library (dboftsp.dll) was not installed on a 64-bit OS when the 32-bit Client feature was selected. Furthermore, dboftsp.dll was not installed when the MobiLink or SQL Remote features were selected. This has been fixed. |
| 740414 | The SQL Anywhere Extension Agent library (dbsnmp*.dll) was not being installed on a 64-bit systems. The 64-bit install needs to put down the 32-bit dbsnmp*.dll to support Microsoft SNMP, which is a 32-bit only service. This has been fixed. |
随着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信息！
不仅仅包括BUG的详细描述信息，还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程；有些BUG还提供了Workaround来临时解决该BUG带来问题。
SQL Anywhere的所有已知BUG列表（1）
SQL Anywhere的所有已知BUG列表（2）
SQL Anywhere的所有已知BUG列表（3）
SQL Anywhere的所有已知BUG列表（4）
SQL Anywhere的所有已知BUG列表（5）
SQL Anywhere的所有已知BUG列表（6）
SQL Anywhere的所有已知BUG列表（7）
SQL Anywhere的所有已知BUG列表（8）
| CR Number |
Description |
| 665116 | The UltraLite Unload utility (ulunload) would not have unloaded an empty Synchronization Profile, such as:
CREATE SYNCHRONIZATION PROFILE "sp" '' The query used to obtain the profile string for a specified Synchronization Profile returned null. This would have resulted in the profile being skipped during the unload. This has been fixed. |
| 665140 | For MobiLink clients that support ECC TLS, support has now been added for RFC 4492 and 256-bit AES ECC cipher suites as well, in addition to the Draft 3 128-bit AES ECC cipher suite they previously supported. |
| 665158 | For servers that support ECC TLS, support has now been added for RFC 4492 and 256-bit AES ECC cipher suites as well, in addition to the Draft 3 128-bit AES ECC cipher suite they previously supported. |
| 665176 | The NEXTVAL operation on sequences did not return an error when executed in a read-only database. This has been corrected. The operation should return an error because the sequence value cannot be updated in the catalog table. |
| 665184 | The server would have incorrectly returned the error "XPath parser error: syntax error at or before character 0 <--" if a stored procedure contained a SELECT statement with an openxml clause that used a variable for the xpath string. This has been fixed. |
| 665195 | If a column or variable name was misspelled in a function that was inlined, and the scope into which inlining was performed contained an object with a matching name, incorrect results, or an incorrect error, could have been returned. This has been fixed.
Example: CREATE FUNCTION func1( @a integer) RETURNS INTEGER BEGIN DECLARE @ret INTEGER; SET @ret = ( a + 10 ) / 100; RETURN @ret; END; SELECT a, func1( b + c ) as ret FROM tab; Expected error is 慍olumn 揳� not found�. |
随着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信息！
不仅仅包括BUG的详细描述信息，还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程；有些BUG还提供了Workaround来临时解决该BUG带来问题。
SQL Anywhere的所有已知BUG列表（1）
SQL Anywhere的所有已知BUG列表（2）
SQL Anywhere的所有已知BUG列表（3）
SQL Anywhere的所有已知BUG列表（4）
SQL Anywhere的所有已知BUG列表（5）
SQL Anywhere的所有已知BUG列表（6）
SQL Anywhere的所有已知BUG列表（7）
SQL Anywhere的所有已知BUG列表（8）
| CR Number |
Description |
| 612094 | 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. |
| 612128 | 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. |
| 612268 | While rare, a CREATE VIEW statement could have caused a server crash. This has been fixed. |
| 612269 | 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 |
| 612295 | Using the DBS connection parameter with a value that included quotes may have caused the connection fail. This has been fixed. |
| 612301 | 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. |
随着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信息！
不仅仅包括BUG的详细描述信息，还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程；有些BUG还提供了Workaround来临时解决该BUG带来问题。
SQL Anywhere的所有已知BUG列表（1）
SQL Anywhere的所有已知BUG列表（2）
SQL Anywhere的所有已知BUG列表（3）
SQL Anywhere的所有已知BUG列表（4）
SQL Anywhere的所有已知BUG列表（5）
SQL Anywhere的所有已知BUG列表（6）
SQL Anywhere的所有已知BUG列表（7）
SQL Anywhere的所有已知BUG列表（8）
| CR Number |
Description |
| 542516 | Shutting down the Relay Server Outbound Enabler could have caused the communication error message: "Communication error! Failed reading." to be logged in the Relay Server log file. This has been fixed. |
| 542519 | If an application made a large number of remote calls to fetch data from a JDBC based Remote Data Access server, then there was a chance the server would have crashed. For this problem to have occurred, the remote table and/or column names must have been longer than 30 characters. This problem has now been fixed. |
| 542521 | On Unix systems, when an application crashed, rather that aborting or exiting, it may have gone intio a state of 100% CPU utilization. This would have occurred when the following conditions occurred in order:
1. The application loaded one of SQL Anywhere's client libraries (JDBC driver, ODBC driver, DBLIB), which automatically install a signal handler. 2. The application installs its own signal handler function 3. An application fault happens which causes the application's signal handler to call the SA signal handler. The SA signal handler will return without causingan abort and the application fault would have been re-triggered. The re-trigger of the signal and the return without handling the signal generated 100% CPU utilization. This has been fixed. |
| 542522 | In rare cases, executing an invalid ALTER PROCEDURE statement could have caused a server crash or an incorrect error message. This has been fixed. |
| 542523 | It was possible for a mirroring connection (i.e. a connection from one server to another server in a high availability configuration) to have failed with no error message being written to the console. This has been fixed. |
| 542524 | If an application on a Unix system used the iAnywhere JDBC driver to connect to a DB2 server using a 64-bit DB2 ODBC driver, then calling the Connection.getTransactionIsolationLevel() method may have crashed the client. This problem has been fixed. |
| 542528 | An application using the iAnywhere JDBC driver may have in rare cases received a Null Pointer Exception when calling Connection.close(). This problem has now been fixed. |
| 542622 | If a database contained userids which had been assigned non-default login policies, running the Extraction utility (dbxtract) would have generated a reload script containing references to those users, even though some of them might not be defined in the extracted database. This has been fixed. |
随着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信息！
不仅仅包括BUG的详细描述信息，还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程；有些BUG还提供了Workaround来临时解决该BUG带来问题。
SQL Anywhere的所有已知BUG列表（1）
SQL Anywhere的所有已知BUG列表（2）
SQL Anywhere的所有已知BUG列表（3）
SQL Anywhere的所有已知BUG列表（4）
SQL Anywhere的所有已知BUG列表（5）
SQL Anywhere的所有已知BUG列表（6）
SQL Anywhere的所有已知BUG列表（7）
SQL Anywhere的所有已知BUG列表（8）
| CR Number |
Description |
| 463608 | When generating sortkeys for the following collations, the generated sortkeys were default UCA keys, rather than the keys appropriate to the language or region:
47 scandict 48 scannocp 58 rusdict 59 rusnocs 63 cyrdict 64 cyrnocs 65 elldict 69 hundict 71 hunnocs 70 hunnoac 72 turdict 74 turnocs 73 turnoac 1 thaidict This has been corrected so that appropriate keys are now generated. It is highly recommended that any columns which store SORTKEY values using these collations be recomputed, as comparisons and sort order will be affected. |
| 463613 | Opening online help in Sybase Central may not have worked the first time it was asked for, although subsequent requests would have succeeded. The problem was timing and operating system dependent. It has been fixed. |
| 463614 | When attempting to add a row to a table that had constraints that were not checked until the transaction was committed, and the new row violated those constraints, it was not possible to cancel the insertion. The same problem affected table row modifications. This has been fixed. |
| 463662 | In general, the optimizer enumerates all valid plans which compute the correct result set for a given query. For each such plan, the optimizer estimates an execution cost measured in microseconds. The plan with the smallest estimated cost is then chosen as the execution plan for a query (aka the 'best plan' for a query). If the database option Optimization_goal is set to FIRST-ROW, the estimated cost for a plan enumerated by the optimizer is the estimated time to compute the first row of the result set of the query. If the optimization goal is set to ALL-ROWS, the estimated cost for a plan enumerated by the optimizer is the estimated time to compute all the rows in the result set of the query. The optimizer was not enumerating plans with complete index scans on the right hand side of a MERGE JOIN. This has now been fixed. |
随着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信息！
不仅仅包括BUG的详细描述信息，还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程；有些BUG还提供了Workaround来临时解决该BUG带来问题。
SQL Anywhere的所有已知BUG列表（1）
SQL Anywhere的所有已知BUG列表（2）
SQL Anywhere的所有已知BUG列表（3）
SQL Anywhere的所有已知BUG列表（4）
SQL Anywhere的所有已知BUG列表（5）
SQL Anywhere的所有已知BUG列表（6）
SQL Anywhere的所有已知BUG列表（7）
SQL Anywhere的所有已知BUG列表（8）
| CR Number |
Description |
| 391900 | Intreactive SQL could have reported an 'internal error' if the Import Wizard was used to read data from an ASCII file into an existing table, and there were fewer columns in the file than columns in the table. This has been fixed. |
| 392015 | Server-side transmission rules, including references to more than one custom message property, may under certain circumstances have evaluated as if one or more of the custom property values was null. This may have occurred if the transmission rule referred to two or more custom message properties in the same rule and the server delete rules included a reference to one of the same custom message properties. This problem has been fixed. |
| 392017 | If a shared connection profile was created, it was not saved if Sybase Central terminated abnormally after the connection profile dialog is closed. Private connection profiles were saved properly. This has now been fixed. |
| 392029 | The server would have returned either -9 or a conversion error from the following query, depending on the platform:
select hextoint('fffffffffffffff7'); This problem has been fixed. The server will now consistently return -9 for the result. In furthering compatibility with Adaptive Server Enterprise, the following examples now return errors, since they contain invalid hexadecimal characters. select hextoint('ffffJackf7') |
随着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信息！
不仅仅包括BUG的详细描述信息，还包括首次报告BUG的平台、数据库版本以及BUG修复历史过程；有些BUG还提供了Workaround来临时解决该BUG带来问题。
SQL Anywhere的所有已知BUG列表（1）
SQL Anywhere的所有已知BUG列表（2）
SQL Anywhere的所有已知BUG列表（3）
SQL Anywhere的所有已知BUG列表（4）
SQL Anywhere的所有已知BUG列表（5）
SQL Anywhere的所有已知BUG列表（6）
SQL Anywhere的所有已知BUG列表（7）
SQL Anywhere的所有已知BUG列表（8）
| CR Number |
Description |
| 341769 | When Remote Data Access was used to query information from a Lotus Notes database, the column names in queries sent to the Lotus Notes ODBC driver were not always quoted. As a result, querying Notes tables with a column named that was a keyword, would have failed. This problem has now been fixed. |
| 341770 | As of 9.0.0, the EXECUTE IMMEDIATE statement supports returning a result set. A side-effect of this change was that procedures that contained an EXECUTE IMMEDIATE statement were marked as returning a result set, even if no result set was returned. This change in behavior has caused compatibility problems for customers moving from prior releases. For this reason, the WITH RESULT SET clause was introduced (see Engineering issue 339798), allowing users to indicate that no result set would be generated. With the present change, the default setting has been changed to OFF, restoring the behavior from earlier versions.
For EXECUTE IMMEDIATE, the new syntax is: EXECUTE營MMEDIATE燵爀xecute-option燷爏tring-expression execute-option: 牋WITH燪UOTES燵燨N爘燨FF燷 |燱ITH燛SCAPES爗燨N爘燨FF爙 | WITH RESULT SET { ON | OFF } Now, if an EXECUTE IMMEDIATE statement is intended to be used to return a result set, it must be specified as follows: EXECUTE IMMEDIATE WITH RESULT SET ON string-expression If the "WITH RESULT SET ON" clause is included, the containing procedure is marked as returning a result set. Failure to include this clause will result in an error being reported when the procedure is called if the statement does produce a result set. |