存档
随着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带来问题。
PB Enterprise的所有已知BUG列表（1）
PB Enterprise的所有已知BUG列表（2）
PB Enterprise的所有已知BUG列表（3）
PB Enterprise的所有已知BUG列表（4）
PB Enterprise的所有已知BUG列表（5）
PB Enterprise的所有已知BUG列表（6）
PB Enterprise的所有已知BUG列表（7）
PB Enterprise的所有已知BUG列表（8）
PB Enterprise的所有已知BUG列表（9）
PB Enterprise的所有已知BUG列表（10）
| CR Number |
Description |
| 187847 | When using the Pipeline object and using the properties for this object RowsWritten this should equal RowsRead minus RowsInError. It appears in all versions of PB tested from PB 5.0.03 through PB 7.0 that the RowsWritten is always equal to the RowsRead and does not reflect the subtraction due to RowsInError although RowsInError is detecting the error.
This has been reported previously in Case 40385070 in PB 4.0 and was tested in PB 5.0.04 build 18 with a different sample and was reported to work there. With this current sample I was unable to get RowsWritten to reflect correct value in any version of PB 5.0, 6.0 or 7.0. |
| 187872 | If a graph is displayed on a machine running in 32 bit true color mode, you will see "hashed" patterns. If you change the display mode to 24 bit true color, or any other mode, you will see solid colors in the graph. |
| 187881 | When a standard visual UO of type "tab" is created, you cannot place any controls onto the UO until you have closed and saved the UO, then re-opened it again.
I have reproduced this against build 4021 of PB 7.0 I also found the following additional problems while testing the above problem. - When the tab UO is initially created, there is no initial tab page, unlike in PB 6.x. So after you have saved it and re-opened it, you can add controls onto the UO. If you add a command button onto the UO, you will get an application error: "The instruction at 0x111f405b" referenced memory at "0x00000018". The memory could not be "read"". - After you have manually inserted a tab page onto the user object. If you place a tab control onto the tab page. You cannot alter it's position by using the mouse. There is also no position property for the tab control, so you cannot alter these values manually. - After you have manually inserted a tab page onto the user object. You can place a control onto the tab object instead of the tab page (which is not allowed in PB 6.x). If you placed a static text control onto the tab object, you cannot see it or alters its properties, but you can select it from the control list. If you placed a command button onto the tab object, then you would get another application error: "The instruction at 0x111f405b" referenced memory at "0x00000018". The memory could not be "read"". |
随着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带来问题。
PB Enterprise的所有已知BUG列表（1）
PB Enterprise的所有已知BUG列表（2）
PB Enterprise的所有已知BUG列表（3）
PB Enterprise的所有已知BUG列表（4）
PB Enterprise的所有已知BUG列表（5）
PB Enterprise的所有已知BUG列表（6）
PB Enterprise的所有已知BUG列表（7）
PB Enterprise的所有已知BUG列表（8）
PB Enterprise的所有已知BUG列表（9）
PB Enterprise的所有已知BUG列表（10）
| CR Number |
Description |
| 161678 | ***6.0.00 Regression*** Two DataWindows, using ShareData() and synchronizing the vertical scrolling in the ScrollVertical event using the scrollpos arg and then setting the Datawindow.VerticalScrollPosition of the second dw to the scrollpos from the first window. When you scroll after row 1318 in the top dw, the bottom dw with go back to row 1. |
| 161691 | Dropdownlistbox control for window has a horizontal scrollbar attribute "hscrollbar" that does not work when set to true ( the scrollbar doesn't appear when data overflows the dialog in the horizontal direction). The vertical scrollbar works fine.. |
| 161696 | ----5.0 and 6.0 regression connecting to SQL Anywhere.
Only 5.0 Gold desplays appropriate behaviour. Broken in 5.02 and up, 6.0 and 6.01 ----6.0 regression connecting to MS SQL Server. Works in all versions of 5.0, but broken in 6.0 and 6.01 SetTransPool() is not reusing opened connections until the maximum amount of connections allowed has been reached. Then opened connections are destroyed and reopened again |
| 161700 | Datawindow radio button edit style not working correctly with settext() in querymode. It should "check" the value that matches the entry from settext. Edit styles such as ddlb work fine |
| 161709 | Problem with 16 bit PB and ImportFile function. It gets stuck in an infinite loop processing the same information from the file over and over. |
| 161737 | ***6.0 Regression*** CrossTab datawindow: If multiple columns are selected for 'Rows' in a Crosstab definition and are of type date, datetime, integer or number, values of only one of those source columns is appearing correctly. Dates display as ??/??/00 and integer/numbers display 0 (zero). |
随着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带来问题。
PB Enterprise的所有已知BUG列表（1）
PB Enterprise的所有已知BUG列表（2）
PB Enterprise的所有已知BUG列表（3）
PB Enterprise的所有已知BUG列表（4）
PB Enterprise的所有已知BUG列表（5）
PB Enterprise的所有已知BUG列表（6）
PB Enterprise的所有已知BUG列表（7）
PB Enterprise的所有已知BUG列表（8）
PB Enterprise的所有已知BUG列表（9）
PB Enterprise的所有已知BUG列表（10）
| CR Number |
Description |
| 146833 | Enhancement. Datawindow support for TIFF (TIF) files. |
| 146940 | On the Control menu on a datawindow, the dropdown menu says "Close" is Alt-F4. Choosing "Close" from the menu with the mouse or with keyboard closes the datawindow control correctly, but if you use "Alt-F4", the shortcut, it closes the application instead of just the datawindow control. |
| 146949 | when you click the arrow in a dropdown datawindow it does not depress. This is a windows standard and the customer thinks this is a bug in powerbuilder. |
| 146950 | Difficulties with cut/copy/paste in the datawindow painter PBL on network. |
| 147037 | Enhancement. Make the additional operands from the SQL Painter available in querymode and querysort and in Prompt for Criteria. It's a real restriction not to be able to use "between" or Basically all operators available in the SQL Painter should be available in Querymode and Prompt for Criteria.
Others are Between Exists Not Between Not Exists Not In Not Like Is Is Not |
| 147046 | Datawindow with a very large summary section. When you page down to the bottom of the datawindow, if there is a page break within the summary band, there are 2 problems: the page number and page count are incorrect and the column values in the header section of the last page are missing. |
随着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. |