存档

‘Replication Server’ 分类的存档,文章数:5

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

Replication Server的所有已知BUG列表(1)
Replication Server的所有已知BUG列表(2)
Replication Server的所有已知BUG列表(3)
 

CR
Number
Description
685119 MICROSOFT SQL SERVER ONLY: Replication Agent

encounters a java.lang.NullPointerException

when resuming replication after changing the

maintenance user id.

685330 When creating a replication definition, the Replication Manager Plugin incorrectly uses the datatype numeric for identity columns. The default value should remain as an identity datatype.
685331 Create subscription with atomic materialization puts text data to incorrect row.
685438 Customer is RepServer 15.6 GA under AIX platform.

Customer have installed "rs_install_statreport_v1510_ase.sql".

When Customer populate statistics using "rs_stat_popultae", this store proc call "rs_stat_populate_netspd" which report duplicate key error:

1> rs_stat_populate

2> go

We are going to populate report. Script version 1510. :-)

Msg 2601, Level 14, State 2:

Server 'SYBASE_MEDISREP2', Procedure 'rs_stat_populate_netspd', Line 189:

Attempt to insert duplicate key row in object 'rs_statreport' with unique index 'rs_key_statreport'

Command has been aborted.

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

Replication Server的所有已知BUG列表(1)
Replication Server的所有已知BUG列表(2)
Replication Server的所有已知BUG列表(3)
 

CR
Number
Description
494288 ORACLE ONLY: The device status returned by

ra_helpdevice is incorrect if the device is

stored under ASM.

494320 The RMS heartbeat process has been enhanced to use the new rs_ticket version 2.0 feature if the controlling Replication Server is version 15.1 or higher. The RMS will retrieve ticket information from the rs_ticket_history table.
494368 Repserver cannot convert EUC half size kana into SJIS half size kana correctly.This issue is reproduced when the character codes of REP and IQ differ. ASE(EUCJIS) -> REP(SJIS) -> IQ(EUC_JAPAN)
494611 cannot use "use dump marker" clause with XPDL process
494701 When you run the pdb_get_columns command, incorrect

datatypes are returned for varchar(max), nvarchar(max), and varbinary(max)

datatypes.

Workaround: Ensure that the replication agents in your replication environment

are version 15.1 ESD #1.

494740 RepConnector is creating file EAServer\bin\mqjms.trc and it keeps growing and consuming disk space.

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

Replication Server的所有已知BUG列表(1)
Replication Server的所有已知BUG列表(2)
Replication Server的所有已知BUG列表(3)
 

CR
Number
Description
214559 1. Create a new user and attach it to a group having the Connect RIght.

2. Go to the Rights tab of the User prop sheet. Note that the Connect right has not been added to the user.

We should have a mechanism a checked-grayed box for inherited rights.

It could also be a "show inherited rights" icon like in member tab for a group.

221815 7.5.0.715

BUG when creating repository tables. No confirmation message to say "Finished creating tables."

I know that this is not a major issue, but from the customer's perspective, they need to know when a PowerDesigner process has completed.

224873 7.5.0.739

During consolidation of large models, PD shell stops responding to Windows (doesn't update display, etc). Need more than just "Saving the local document in the repository..."

1) Import model into PD7 and save it

2) Then consolidate that model into your favorite repository.

3) When it gives you the "Saving the local document..." message, launch the TaskManager and check out the PowerDesigner program.

NOTE: It will be listed as "Not responding".

4) If you have another application open, move its window around in front of the PD GUI.

Notice that it doesn't refresh the display. This is not good.

It takes a long time (anything over a minute or so is too long, but I'm talking 30 minutes and longer here) before it will update the GUI.

What I want to see is more GUI refreshes and some kind of status update in the message window, like what happens when I Reverse Engineer a database. The old MetaWorks gave me more information than this when it was working. Just giving me an hourglass is not acceptable

在Sybase官方网站上存在页面Sybase Certifications: http://certification.sybase.com/ucr/search.do 可以查询Sybase产品在各操作系统平台上的认证情况。
随着Sybase被完全整合到SAP下,Sybase原来的支持网站被SAP Support Portal取代。
只有购买了SAP服务的用户才能使用账号登录SAP Support Portal进行介质下载、补丁升级、报Incident等。
按照Sybase的惯例,在被原厂认证的操作系统平台上部署的Sybase产品才会得到支持。虽然某个版本在原厂未认证的一些操作系统平台上也能够成功安装,但还是建议在生产环境上使用认证的操作系统平台。
考虑到Sybase数据库的初学者或者没有购买原厂服务的Sybase客户情况,现提供Sybase部分产品在各操作系统平台上的认证情况。
下面是Sybase Replication Server在各操作系统平台上的认证情况,根据Replication Server版本号进行逆序排序的结果:(还有根据操作系统版本排序的结果)

Product Prod Version WordSize OS Version More Information
Replication Server 15.7.1 64-bit Red Hat EL 5.0 (AMD64/EM64T) view more
Replication Server 15.7.1 64-bit Red Hat EL 6.0 (AMD64/EM64T) view more
Replication Server 15.7.1 64-bit Sun Solaris 11 (SPARC) view more
Replication Server 15.7.1 64-bit Sun Solaris 11 (x64) view more
Replication Server 15.7 64-bit HP-UX 11.31(ia) view more
Replication Server 15.7 64-bit IBM AIX 6.1 view more
Replication Server 15.7 64-bit IBM AIX 7.1 view more
Replication Server 15.7 64-bit Red Hat EL 5.0 (AMD64/EM64T) view more
Replication Server 15.7 64-bit Red Hat EL 5.0 (IBM POWER) view more
Replication Server 15.7 64-bit Red Hat EL 6.0 (AMD64/EM64T) view more
Replication Server 15.7 64-bit Red Hat EL 6.0 (IBM POWER) view more
Replication Server 15.7 64-bit SuSE SLES 10 (AMD64/EM64T) view more
Replication Server 15.7 64-bit SuSE SLES 10 (IBM POWER) view more
Replication Server 15.7 64-bit SuSE SLES 11 (AMD64/EM64T) view more
Replication Server 15.7 64-bit SuSE SLES 11 (IBM POWER) view more
Replication Server 15.7 64-bit Sun Solaris 10 (SPARC) view more
Replication Server 15.7 64-bit Sun Solaris 10 (x64) view more
Replication Server 15.7 32-bit Windows 2008 (x86) view more
Replication Server 15.7 64-bit Windows 2008 R2 (x64) view more

Replication Server 15.2复制服务器不能同步数据,复制节点的DSI线程异常关闭。

RS的日志文件中显示错误日志如下:

E. 2011/03/03 19:25:33. ERROR #5074 DSI EXEC(1011(1) v890f_REP.ultranms2) - dsiqmint.c(1616)
        A transaction marked TO_PRIMARY for database 'v890f_REP.ultranms2' has the same user name as the maintenance user for the database. This transaction should be skipped, or the maintenance user name for the database needs to be changed.
I. 2011/03/03 19:25:33. The DSI thread for database 'v890f_REP.ultranms2' is shutdown.
 

使用 admin logical_status 看到