存档

Archive by ,文章数:325

随着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.

随着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
279353 When an SPX connection to an ASA server running on NetWare was disconnected, it was possible for the NetWare server to abend. This has been fixed.
279359 When using the Procedure Debugger, the wrong source code would be displayed if the following occurred:

1 - Connected to a database,

2 - Disconnected from the database,

3 - Connected to a different database

From then on, attempting to display the source to any stored procedure usually displayed source for a different procedure. This problem is now fixed.

279372 When multiple MobiLink users were defined on a remote database, with overlapping publications, synchronization may not have proceed correctly. This problem could have manifested itself on a remote database where all the following were true.

- at least 2 MobiLink users were defined, say U1 and U2

- at least 2 publications are defined, say P1 and P2

- there existed some operation O, that affected both P1 and P2

- only U1 had a subscription to P1

- only U2 had a subscription to P2

Under these circumstances, if the subscription U1/P1 was synchronized, followed by the subscription U2/P2, then O may have been uploaded for U1/P1 but not U2/P2. This problem is now fixed and did not occur if the -u switch was used to specify the MobiLink user on the dbmlsync command-line.

随着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带来问题。

Adaptive Server Enterprise的所有已知BUG列表(1)
Adaptive Server Enterprise的所有已知BUG列表(2)
Adaptive Server Enterprise的所有已知BUG列表(3)
Adaptive Server Enterprise的所有已知BUG列表(4)
Adaptive Server Enterprise的所有已知BUG列表(5)
Adaptive Server Enterprise的所有已知BUG列表(6)
Adaptive Server Enterprise的所有已知BUG列表(7)
Adaptive Server Enterprise的所有已知BUG列表(8)
Adaptive Server Enterprise的所有已知BUG列表(9)
 

CR
Number
Description
776152 The message "current process infected with 11 (SIGSEGV)" in the module 慸bts_ptscmp� together with a stack trace which includes the modules 憈h_lct_admin� and 憂um_logpages� may be reported in the SAP ASE error log when the lct_admin() built-in is used to get total number of log pages for databases with mixed log and data segments.
776153 Master db replication of passwords do not allow utilization of pwdhistory table at the replicate site.
776170 A 622 error, "Opentable was passed a varno of 0. Object <> in database <> already has that session descriptor in use. This occured while opening object id <> in database id <>.", together with a stack trace which includes the modules 'crt_main' and 'sdes_hookup' may be reported in the error log when CREATE TABLE following ONLINE CREATE INDEX on a hot table is executed.
776176 A 1142 error, "Invalid OAM Page <oampgid>. Found pstat=<page_status>, object=<objid>, database=<dbid>, indid=<indid>.", may be reported when CREATE INDEX and DROP INDEX commands are executed in a user transaction and while the database option 'ddl in tran' is enabled.
776222 A 644 error, "Index row entry for data row id (<page#>, <row#>) is missing from index page <page#> of index id <value> of table '<name>' in database 'name'. Xactid is (<page#>,<row#>) ). Drop and re-create the index.", may be reported on little-endian platforms when a clustered index on a Data Only Locked table permits duplicate keys and the index refers to pages of which the hex value of lowest two bytes is 0xffff.
776266 In rare cases, a 1503 error, "Sort Internal Error: The Root page of right/left sub-index tree is missing." may be reported if LAVA parallel index creation is ongoing and one of the child thread is killed by SQL command: "KILL <spid>".

随着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带来问题。

Adaptive Server Enterprise的所有已知BUG列表(1)
Adaptive Server Enterprise的所有已知BUG列表(2)
Adaptive Server Enterprise的所有已知BUG列表(3)
Adaptive Server Enterprise的所有已知BUG列表(4)
Adaptive Server Enterprise的所有已知BUG列表(5)
Adaptive Server Enterprise的所有已知BUG列表(6)
Adaptive Server Enterprise的所有已知BUG列表(7)
Adaptive Server Enterprise的所有已知BUG列表(8)
Adaptive Server Enterprise的所有已知BUG列表(9)
 

CR
Number
Description
732410 In rare cases, dataserver can hang due to this deadlock situation: one session sleeps on grabbing DES while updating statistic in rollback a DELETE; the other session sleeps on writing dirty buffers when scavenging a DES.
732482 A query against a remote table may get a signal 11 during UPDATE STATISTICS.
732503 The message "current process infected with 11 (SIGSEGV)" in the module 'des__clean' together with a stack trace which includes the modules 'des_refreshall' and 'online_database' may be reported in the SAP ASE error log when multiple sessions are executing the ONLINE DATABASE command simultaneously for the same database. This will result in SAP ASE shutting down implicitly.
732560 ASE attempts to checkout a license after it is already checked-out.
732588 Under certain circumstances when a threshold action is defined, and user is dropping a procedure, and the procedure happens to be the last row of the sysprocedures page, an 873 error may be reported when log space is low, and the threshold proc gets spawned.
732604 The summary stats for histogram (i.e. unique count, density) generated by hash based statistics gathering may be inaccurate. This could occur when OPTDIAG labels a histogram as "high domain".
732613 The Job Scheduler fails to start if quoted_identifier property is set for the connection (which is used to start the Job Scheduler). The following error is logged in the SAP ASE errorlog: "Job Scheduler: IS_ISQL_EXT failed [set nocount on use sybmgmtdb print ":s: %1!", "sybmgmtdb"]"
732631 REORG REBUILD <table_name> WITH ONLINE command, does not update the index create time-stamp(index_created field in sp_helpindex output) for the indexes rebuilt.
732640 Schema lock displayed as GUID lock in sp_lock output
732693 ALTER TABLE <TABLENAME> SPLIT PARTITION may fail with errors such as 2601 (Attempt to insert duplicate key row in object <name> with unique index <name>) when there is a non-clustered index.
732723 typos and fix problems for fast bcp section of utility guide
732728 The unreserved space stored in the table sysusages can become a huge number bigger than the fragment itself if the number of allocated pages indicated in the OAM pages for some objects becomes corrupted and show pages allocated that are not.
732777 Under some circumstances, a 4720 error "Cannot truncate table '%.*s' because there are one or more isolation level 0 scans, or REORG command, active on the table." may be reported while a temporray is being dropped. Such temporary table is found to have a dlevel0cnt = 12.
732841 RepAgent won't connect to RepServer when 'cis connect timeout' > 2147.
732911 If a table has constraint check and its name is quoted identifier, when migrate the table, sybmigrate failed in the error like that: SqlState: 42000 java.sql.SQLException: Incorrect syntax near
732921 A 8201 error, "Keep count of descriptor (objid=14, dbid=<value>) was expected to be 1. Instead 0 was found" followed by a stack trace that includes the module 'des__unkeep' may be raised if ASE fails to allocate space for either SYSGAMS or SYSDAMS.

随着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带来问题。

Adaptive Server Enterprise的所有已知BUG列表(1)
Adaptive Server Enterprise的所有已知BUG列表(2)
Adaptive Server Enterprise的所有已知BUG列表(3)
Adaptive Server Enterprise的所有已知BUG列表(4)
Adaptive Server Enterprise的所有已知BUG列表(5)
Adaptive Server Enterprise的所有已知BUG列表(6)
Adaptive Server Enterprise的所有已知BUG列表(7)
Adaptive Server Enterprise的所有已知BUG列表(8)
Adaptive Server Enterprise的所有已知BUG列表(9)
 

CR
Number
Description
670907 ASE may crash unrecoverably with signal 11 in ct_poll when a connection to a remote server

running an SQL query is killed.

670973 When more than one column is encrypted with same key encrypted by user password, even if wrong password is specified for one of the columns during bcp out, no error is given and bcp succeeds.
671049 sp_sysmon I/Os Delayed by is not reported correct for linux 64 bit platform.
671084 Error 644 may be reported on a nonclustered index of an APL table that has a clustered index that allows duplicates, and the row being inserted is a duplicate.
671096 A query involving a join between proxy tables may receive an infected with 11 with a stacktrace containing the function CtlibRemoteAccess::cursorClose(_cscommand*, CtlibRemoteAccess::CURSOR_STATE, char*, const char*, bool)
671101 For a new XSM, the default code format is Mixed Case; suggest it should be Upper CamelCase, to avoid generating tag names with underscores
671104 When adding attributes to elements, the element symbol overlaps nearby symbols. There is noway to correct the diagram except to toggle the Display Preferences\orientation attribute from horizontal to vertical

To reproduce:

1) create a new XML model

2) create a new element (element_1)

3) add three new elements to element(element_1)

(The three new elements branch off the sequence)

4) add several attributes to element_2

NOTE: element_2 now overlaps the other elements

Neither collapsing the sequence, auto-layout, nor redisplay corrects the issue.

The only workaround is to change the orientation from horizontal to vertical

随着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带来问题。

Adaptive Server Enterprise的所有已知BUG列表(1)
Adaptive Server Enterprise的所有已知BUG列表(2)
Adaptive Server Enterprise的所有已知BUG列表(3)
Adaptive Server Enterprise的所有已知BUG列表(4)
Adaptive Server Enterprise的所有已知BUG列表(5)
Adaptive Server Enterprise的所有已知BUG列表(6)
Adaptive Server Enterprise的所有已知BUG列表(7)
Adaptive Server Enterprise的所有已知BUG列表(8)
Adaptive Server Enterprise的所有已知BUG列表(9)
 

CR
Number
Description
585221 In rare circumstances, the message "current process infected

with 11" in the module 'des_rekeep' together with a stack trace

which includes the modules 'proc__linktopss' and 'lwp_proc_setup'

may be reported in the error log when a client application is

executing a query using "dynamic sql" and the system is configured

with a low value for the configuration parameter "number of

open objects" according to its workload.

585260 Unnecessary recompilations may happen if 'open by name' trace flag 299 is activated

and a temporary table has at least one BIT column.

585267 Derived table without specifying column name in the embedded select doesn't work
585304 Parallel BCPs into a semantically partitioned DOL table can deadlock when two sessions perform

allocation at the same time. The deadlock information will consistently show the deadlock

ccurring on rowid 0 for both spids.

585313 Create proxy_table fails when ECDA backend table has default values specified.
585444 This introduces "ULC flushes by Log Markers" entry in the ASE sp_sysmon report.

A high value for 揵y Log markers� indicates that Adaptive Server is flushing the ULCs because of

permanent log marker scans (a permanent log marker scan indicate that syslogs includes the log

record). Adaptive Server uses the log records for operations like executing triggers, rollbacks,

aborts, and so on. When Adaptive Server needs a permanent log marker but does not have one, it

flushes the ULC to create a new log marker. When 揵y Log markers� displays a large percentage of ULC

flushes, you may need to reduce the number of unnecessary or redundant triggers, rollbacks, or aborts.

随着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带来问题。

Adaptive Server Enterprise的所有已知BUG列表(1)
Adaptive Server Enterprise的所有已知BUG列表(2)
Adaptive Server Enterprise的所有已知BUG列表(3)
Adaptive Server Enterprise的所有已知BUG列表(4)
Adaptive Server Enterprise的所有已知BUG列表(5)
Adaptive Server Enterprise的所有已知BUG列表(6)
Adaptive Server Enterprise的所有已知BUG列表(7)
Adaptive Server Enterprise的所有已知BUG列表(8)
Adaptive Server Enterprise的所有已知BUG列表(9)
 

CR
Number
Description
499408 When real time messaging is enabled on ASE to use MQ. The additional engine spawned to handle MQ tasks uses up very high cpu even when there is only 1 messaging operation.
499413 Include available sort order options all the time when using sqlloc with X.
499448 Procedural query with FOR READ ONLY option may incorrectly raise error 7304 "FOR READ ONLY can

not be used in a SELECT which is not part of the declaration of a cursor or which is not inside

a stored procedure"

499455 Dynamic partition elimination may not be applied, when processing an ad-hoc sql query or stored procedure, with variable SARGs and range predicates, against a table that has a composite partition key.
499485 On Windows platforms that have Virtual Adaptors the SySAM properties file can grow over time causing delays in startup.
499490 Compilation of an UPDATE query that contains a join and at least one IN-list or OR clauses

on the same column can choose deferred update mode, when direct update mode is possible.

As a result performance of the UPDATE query can be negatively impacted.

An example query is:

update t1 set c2 = 3 from t1, t2 where t1.c1 in (1,2,3,4,5,6,7,8,9) and t1.c2 = t2.d2

where table t1 is being updated and the query joins tables t1 and t2 and there is a IN-list

on column c1 of table t1.

随着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带来问题。

Adaptive Server Enterprise的所有已知BUG列表(1)
Adaptive Server Enterprise的所有已知BUG列表(2)
Adaptive Server Enterprise的所有已知BUG列表(3)
Adaptive Server Enterprise的所有已知BUG列表(4)
Adaptive Server Enterprise的所有已知BUG列表(5)
Adaptive Server Enterprise的所有已知BUG列表(6)
Adaptive Server Enterprise的所有已知BUG列表(7)
Adaptive Server Enterprise的所有已知BUG列表(8)
Adaptive Server Enterprise的所有已知BUG列表(9)
 

CR
Number
Description
455707 Previously a server's preferences (such as number of lines of server log to retrieve) were lost when the server was cut and pasted. Now the preferences for the server are preserved when the server is cut.
455721 Need information update on the tempdb and indexing on Performance and Tuning Guide
455779 Problem:

Project execution might become unresponsive when database runs out of space.

Resolution:

When a database involved in a data transfer runs out of space, the execution of a project might stop responding. This is because the database driver does not return with an error message but waits until space is available to continue. Please ensure that sufficient space is available before running a project or job.

455781 The Historical Server reports an incorrect time value on the windows platforms.
455812 index name in sp_create_text_index should be from local db only, documentation needs to be corrected to reflect that.
455819 FTS core dumps when creating index with universal style
455826 If a kerberos login gets a timeslice error during security session establishment,

the engine-wide semaphore is not released, causing all the other kerberos logins on that engine to block.

455839 Concurrency problems are found when using MIT Kerberos client libraries version 1.3.x and 1.4.x

or earlier, causing ASE crash or blocking all Kerberos logins when there are concurrent Kerberos

authentication attempts.

ASE now supports concurrent Kerberos authentication requests by default.

Trace flag 7844 is no longer needed and can be used if concurrent Kerberos authentications is not required.