提供7*24专业Sybase数据库远程及现场技术支持,Sybase ASE及Sybase SQL Anywhere数据库修复服务,
请联系电话: (微信),QQ: 289965371!
We supply technical support for Sybase ASE and Sybase SQL Anywhere, also have many years of experience in recovering data from damanged Sybase devices.
Please contact us:
Phone:
Wechat: 13811580958
QQ: 289965371 联系我们获取数据库技术支持!
Email: 289965371@qq.com
扫描下方微信,联系我们:
扫描雨翰数据恢复官方微信获取专业数据库恢复服务

 

随着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:407953
CR Number:   407953
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.1.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
ORACLE ONLY: Procedures containing the

RETURNING keyword are not successfully

marked for replication.



CR:408081
CR Number:   408081
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.1.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Bundled Request
Description
ORACLE ONLY: Replication of a large LOB value

fails with a NullPointerException.



CR:408103
CR Number:   408103
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.1.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.2.01 23 Jan 2006 Fixed
5.4.00 19 May 2008 Fixed
Description
ORACLE ONLY: RepAgent fails to handle

ALTER TABLE DDL operations containing constraint

changes. This fix requires that the RepAgent

PDS_USERNAME user has the SELECT privilege in

Oracle on the SYS.CON$ and SYS.CDEF$ tables.

This fix also requires that you re-initialize

your instance using "pdb_xlog init, force".



CR:408237
CR Number:   408237
Product Name:   Sybase Replication Server
Product Component:   rsmsrvr
Status:   Closed
OS:   AIX
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
23 Oct 2009 EOL'd version. Not to be Fixed.
Description
View of data of a queue in Replication Manager plug-in may make Repserver hang, until the data in the window is completely scrolled thro'.



CR:408373
CR Number:   408373
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   Minerva
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
*** Monday, October 31, 2005 2:24:24 PM *** ahill *** 11.1.10 EBF6



In the repository the customer would like the ability to update the permission of a 'child' with the parent's permission. However, they do not want to lose the 'child's' permission.



For example:

In the repository, create two groups

Add two folders. 1 - folder is the parent and the second folder is the child

Add group_2 to the child folder

Add group_1 to the parent folder



From the property sheet of the parent folder, if you click the 'Copy permissions to child folder' tool, the permissions of the parent folder are copied and replace the permissions of the child folder. (this is expected.)



However, the customer would like to have the parent permissions updated to the child folder but to have an option to preserve the divergenet permissions already associated with the child folder.



CR:408485
CR Number:   408485
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   NA
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Nov 2005 Fixed
15.0 201 28 Mar 2006 Fixed
05 Mar 2006 Fixed
Description
Event triggers that you create are executed only if Replication Manager (RM) is connected to RMS. Event triggers should execute regardless of whether RM is connected to RMS.



CR:408699
CR Number:   408699
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
5.0.00 18 Mar 2010 Presently Not Targeted For Any Future Release Of This Product
Description
ORACLE ONLY: Marking or listing tables or

procedures that contain an underscore in the name

may result in the following error: Could not list

metadata for table <WZB_TS_TST> because: Too many

entries found in <or920tm1> for <WZB_TS_TST>.

Specify owner.



CR:408788
CR Number:   408788
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.07
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6.09 07 14 Feb 2006 Fixed
Description
RA DB2 without replication activity, attempts to restart at a log record whose DB2 log has already expired.



CR:408981
CR Number:   408981
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.3.00 19 May 2008 Fixed
5.2.01 23 Jan 2006 Fixed
5.2.01 23 Jan 2006 Fixed
Description
ORACLE ONLY: Message "Error initializing change

vector" received when an insert statement using a

SELECT INTO clause contains a NULL value.



CR:409346
CR Number:   409346
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.3.00 19 May 2008 Fixed
Description
ORACLE ONLY: "OracleDDLException: Failed to create

a procedure" error occurs when DDL for a procedure

with a BOOLEAN argument is encountered.



CR:409357
CR Number:   409357
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.1.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 07 Jan 2006 Fixed
Description
ORACLE ONLY: Message "Skipping operation because

the transaction context does not exist." occurs

too frequently.



CR:409412
CR Number:   409412
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
ORACLE ONLY: RepAgent cannot handle a CREATE TABLE

operation with any of the system-defined types in

the USERDEF category like URITYPE, HTTPURITYPE,

ORDAUDIO, etc.



CR:409524
CR Number:   409524
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.3.00 19 May 2008 Fixed
Description
ORACLE ONLY: "Failed to alter a user" error

message received after altering an Oracle user

in the Primary database.



CR:409547
CR Number:   409547
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   SunOS
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Sep 2006 One-off Provided
24 Jul 2006 Fixed
25 Jul 2006 Fixed
25 Jul 2006 Fixed
10 May 2007 Fixed
Description
Replication Server reports parsing errors in the unpacker or parser, transaction will complete if connection is resumed.



CR:409644
CR Number:   409644
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.3.00 19 May 2008 Fixed
Description
ORACLE ONLY: "Failed to alter a user" error

message received after altering an Oracle user

in the Primary database.



CR:409908
CR Number:   409908
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
ORACLE ONLY: Invoking the 'pdb_xlog' command with

no option results in a ClassCastException after

applying Replication Agent/Oracle 12.6 ESD #1

Build 5200.



CR:410006
CR Number:   410006
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.3.00 19 May 2008 Fixed
Description
ORACLE ONLY: Failed processing a redo log record

for a CREATE GLOBAL TEMPORARY TABLE command.



CR:410026
CR Number:   410026
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Jul 2006 Fixed
11 Jul 2006 Fixed
19 Jul 2006 Fixed
Description
rs_locater entry for route can disappear from rs_locater table.
Workaround Description
 None. This situation only becomes a problem if a save interval is used. Workaround is not to use a save interval or don't use a save interval that is very long.



CR:410135
CR Number:   410135
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.3.00 25 Aug 2006 Fixed
5.3.00 18 Mar 2008 Fixed
5.2.01 19 May 2008 Fixed
5.2.01 26 Jan 2006 Fixed
Description
ORACLE ONLY: Error "Error occurred processing

operation <> RBA <>: Failed to create a table.."

occurs for a table that is recreated.



CR:410232
CR Number:   410232
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6.09 07 10 Feb 2006 Fixed
Description
New configuration parameter DetectDataCapture. Valid values are Yes and No. Default setting is No. A setting of Yes causes RA DB2 to read substantially more log records to detect when the DB2 table is toggled for datacapture changes/none and print messages in the JESMSGLG when detecting the change.



CR:410254
CR Number:   410254
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   Utilities
Status:   Closed
OS:   NA
Original Version:   5.1.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
The VM % Max Memory Used statistic is always 0.



CR:414514
CR Number:   414514
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   Windows XP
Original Version:   penelope
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Dec 2005 Fixed
Description
Repository history:

Originally created 10/3/02 (PD 9.5.x?)and migrated PD 10, 10.1, 11.0 to PD 11.1.0



The customer is consolidating a PDM that contains views. Whether consolidating as a new model or as an update, the consolidation fails with the following ODBC error:



[S1010] [Microsoft][ODBC Driver Manager] Function sequence error (0)

[22018] [DataDirect] [ODBC Sybase Wire Protocol driver] [Sql Server] Implicit conversion from datatype 'INT' to 'VARCHAR' is not allowed. Use the CONVERT function to run this query.



Using the customer's repository, this issue is reproducable. Using a newly installed repository, the customer's PDM consolidates without problems.



In review of the ODBC trace file, the problem appears in the PMPDMVIWC table.

In the customer's repository, the 'CCMT' column has a datatype of 'Varchar(254)'.

In the newly created repository, this same column has a datatype of 'int'.

In both instances, the insert statement for this column is inserting an 'integer'.





09/30/2005

This issue has been addressed via CR 398220 which has been resolved in 11.1.0 EBF6



CR:415044
CR Number:   415044
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.3.00 19 May 2008 Fixed
Description
ORACLE ONLY: IllegalArgumentException logged

against CVData.java:81



CR:415152
CR Number:   415152
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   AIX
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Apr 2006 Fixed
Description
On AIX, RS cores on ll_del and aix_get_lock
Workaround Description
 Turn SMP off



CR:415246
CR Number:   415246
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6.09 05 14 Feb 2006 Fixed
Description
After shutdown request is made, RA DB2 will sometimes issue an 0C4



CR:415270
CR Number:   415270
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.1.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
ORACLE ONLY: NullPointerException in

OracleSessionContext sends RepAgent to

ADMIN state.



CR:415273
CR Number:   415273
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
ORACLE ONLY: The database generation ID

configuration setting (the 'pdb_gen_id' command)

is reset after invoking the 'pdb_xlog init,force'

command.



CR:415281
CR Number:   415281
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   Log Admin
Status:   Open
OS:   Generic
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
06 Mar 2008 Fixed
5.3.00 05 Mar 2008 Fixed
5.2.01 23 Jan 2006 Fixed
5.3.01 06 Jun 2006 Fixed
Description
RepAgent has a new command -- ra_migrate -- now

used to migrate the installed RepAgent version to

the current version.



Description:

Performs migration tasks (as necessary)

between releases of Replication Agent.



Syntax:

ra_migrate



Usage:

- When you apply an EBF of the Replication

Agent release, you may be required to run

this command to upgrade to the latest

version of the Replication Agent.

- When ra_migrate is invoked, it will migrate

the installed Replication Agent version to

the new current version.

- It will update the XLog system table with

the latest build version if the Replication

Agent was previously initialized.

- This command does not support migration to

an earlier version of Replication Agent.

- This command must be run in ADMIN mode.



CR:415396
CR Number:   415396
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.2.01 19 May 2008 Fixed
Description
ORACLE ONLY: When a table contains null columns,

a NullPointerException occurs.



CR:415559
CR Number:   415559
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   Management
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.4.00 04 Dec 2006 Fixed
Description
Refactory code to enable user

to support localization.



CR:415906
CR Number:   415906
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 22 Aug 2007 Fixed
Description
No confirmation of trunc=next command completion.
Workaround Description
 compare before and after values of the type E record in the RSSD.rs_locater.



CR:416121
CR Number:   416121
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 Dec 2005 Fixed
13 Dec 2005 Fixed
Description
Charset for eRSSD is automatically selected to match RS charset closest during rs_init.

However, sometimes the ASA charset has a slightly different name (especially on NT), if we can't find the same charset in ASA and the default for the OS is used.

In these cases, we print the following message:

W. 2005/12/08 16:28:08. WARNING #13092 GLOBAL RS(GLOBAL RS) - seful/cm.c(5833)

The Data Server 'erssd' is using the 'xxx' character set for

Database 'erssd'. The Replication Server is using the 'yyy' character set.

Unexpected results may occur.



CR:416322
CR Number:   416322
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   12.6.0.5200P1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 05 Jun 2006 Fixed
Description
ORACLE ONLY: Agent initialization used only the

Oracle database instance to locate the

timezone.dat file. This could be inaccurate under

certain conditions. Now, the agent first uses the

ORACLE_HOME environment variable, then the Oracle

database instance before reporting an error.



CR:416326
CR Number:   416326
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   Utilities
Status:   Closed
OS:   Generic
Original Version:   12.6.0.5200P1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
No message in trace log file indicating that it

has filled up and that it is no longer being used.



CR:416352
CR Number:   416352
Product Name:   Rep Serv Commands Ref
Product Component:   Rep Serv Commands Ref
Status:   Closed
OS:   NA
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 18 Jan 2006 Fixed
Description
Add to doc:



Run rs_subcmp when Primary changes are not occurring.
Workaround Description
 if the data in the rows are changing constantly, rs_subcmp is not a good tool for measuring inconsistencies. However, if the row changes only a few times, then have rs_subcmp run though more iterations so that it will compare in-flight data that resides within Rep Server.



CR:416407
CR Number:   416407
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Dec 2008 Fixed
11 Dec 2008 Fixed
5.5.23 07 Jan 2009 Fixed
Description
ORACLE ONLY: When the command

"insert into select from with all NULLs "

is executed in Oracle, this can cause

Replication Server to fail with the error:

ERROR #1028 DSI EXEC(105(1) or920sh2.or920sh2) -

dsiqmint.c(3034)



CR:416423
CR Number:   416423
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: Executing 'ra_devicepath'

command with a non-existent device id

results in a NullPointerException.



CR:416427
CR Number:   416427
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   NA
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Jan 2006 Fixed
Description
Add 4985, 4986, 4987, 4988 return codes from ASE to default action ignore in rs_sqlserver_error_class
Workaround Description
 Add a custom error class that maps these four actions to ignore



--OR--



add these four error codes to the rs_sqlserver_error_class. The sql to do this would be:



insert rs_erroractions (ds_errorid, errorclassid, action, prsid) values (4985, 0

x0000000001000002, 1, 0)

insert rs_erroractions (ds_errorid, errorclassid, action, prsid) values (4986, 0

x0000000001000002, 1, 0)

insert rs_erroractions (ds_errorid, errorclassid, action, prsid) values (4987, 0

x0000000001000002, 1, 0)

insert rs_erroractions (ds_errorid, errorclassid, action, prsid) values (4988, 0

x0000000001000002, 1, 0)



CR:416457
CR Number:   416457
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
5.3.00 07 Mar 2006 Fixed
5.3.00 25 Aug 2006 Fixed
5.3.00 08 Apr 2009 Presently Not Targeted For Any Future Release Of This Product
5.3.00 06 Mar 2008 Fixed
Description
ORACLE ONLY: The new configuration parameter

'pdb_automark_tables' now determines whether

or not the Agent automatically marks user

tables for replication. If the value is set

to true, user tables are marked during

initialization and DDL replication (when

replication of DDL commands is enabled).

If the value is set to false, user tables

are never automatically marked; they must

be explicitly marked using the

pdb_setreptable' command. The default

value is 'false'.



CR:416476
CR Number:   416476
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Feb 2006 Fixed
23 Feb 2006 Fixed
25 Jun 2007 Fixed
16 Oct 2007 Fixed
16 Oct 2007 Fixed
Description
Parallel DSI causes a memory leak when

'dsi_sqt_max_cache_size' is set to a large value

(e.g. 1MB) and 'dsi_max_xacts_group' is set to a

value greater than 1.



CR:416484
CR Number:   416484
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Jul 2006 Fixed
20 Jul 2006 Fixed
20 Jul 2006 Fixed
14 Aug 2006 Fixed
14 Aug 2006 Fixed
24 Jan 2007 Fixed
24 Jan 2007 Fixed
Description
Modify rs_helpfstring to ensure the order of the text is in rs_systext.sequence order.
Workaround Description
 select objname+'.'+c.name , ""+d.textval+""

from rs_objects a, rs_functions b, rs_funcstrings c, rs_systext d

where a.objid = b.objid and b.funcid = c.funcid and

c.fstringid = d.parentid and

d.prsid = (select id from rs_sites where name = '<Rep Svr Name>')

order by objname, sequence



CR:416489
CR Number:   416489
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   Log Reader
Status:   Closed
OS:   Generic
Original Version:   12.6.0.4053P11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
Determination of owner mode is incorrect.



CR:416492
CR Number:   416492
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
31 May 2006 Fixed
15.0 31 May 2006 Fixed
12.6 31 May 2006 Fixed
Description
Minor memory leak in DSI unpacking function, pak_unpack_command().
Workaround Description
 1. create a replication definition

2. create a subscription

3. replicate a row



Optional:

4. drop the subscription

5. drop the replication definition



CR:416684
CR Number:   416684
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
ORACLE ONLY: When initializing and the timezone

file is not configured and ORACLE_HOME is not set,

RepAgent returns a garbled message: Replication

initialization failed because: Could not find

Resource Bundle containing index: FILE_NO_EXIST

and args=String index out of range: -1



CR:416919
CR Number:   416919
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY Command pdb_xlog create fails with a

NullPointerException.



CR:417173
CR Number:   417173
Product Name:   Sybase Replication Server
Product Component:   RSMJavaPlugin
Status:   Closed
OS:   Solaris
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 302 10 May 2006 Fixed
15.0.1 31 Jan 2007 Fixed
Description
The RM Plug-in does not provide the hide connection status feature for an RMS domain. The RMS EBF #1 provides the ability to hide the status of either the rep agent or DSI thread in a connection. The RM Plug-in will support this feature for an RMS.



CR:417549
CR Number:   417549
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.01 11 Nov 2008 Fixed
5.8.00 06 Jan 2009 Fixed
5.5.23 07 Jan 2009 Fixed
Description
ORACLE ONLY: When the command

"rs_zeroltm rao, pdb" is issued to

Replication Server system database and

"ra_locator zero" is issued in

Replication Agent, the Replication Agent

starts the log scan with an incorrect

locator.



CR:417874
CR Number:   417874
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Workaround
5.3.00 25 Aug 2006 Fixed
5.3.00 02 Apr 2010 Insufficient priority to fix
5.3.00 02 Apr 2010 Insufficient priority to fix
5.3.00 02 Apr 2010 Insufficient priority to fix
Description
ORACLE ONLY: When replicating Oracle DDL commands,

stored procedures created with compile errors

return error code 4025. By default Replication

Server stops processing when this error code is

seen.



In order to allow Replication Server to continue

processing after receiving this error, Replication

Server must be configured to list a warning

message instead of stopping replication.



Issue the following commands to instruct

Replication Server to produce a warning message in

the Replication Server log when return code 4025

is received.



1 Create an error class for Oracle.

2 Initialize the new error class.

3 Assign the action 'warn' for error 4025.

4 Alter any Replication Server connection

that replicates TO Oracle to use this

new error class





1 Issue this command in Replication Server

to create the oracle error class



>create error class oracle_error_class

>go



2 Issue this command in the RSSD

to initialize the oracle error class



>rs_init_erroractions oracle_error_class,

>rs_sqlserver_error_class

>go



3 Issue this command in Replication Server

to update the oracle error class



>assign action warn for oracle_error_class

>to 4025

>go



4 Issue this command in Replication Server

to alter an existing connection to use

the oracle error class just created

after changing {pds}.{pdb} to the

appropriate values for your connection.



>alter connection to {pds}.{pdb}

>set error class to oracle_error_class

>go
Workaround Description
 -- In order to allow Replication Server to

-- continue processing after receiving this

-- error, Replication Server must be configured

-- to list a warning message instead of stopping

-- replication.

--

-- Issue the following commands to instruct

-- Replication Server to produce a warning

-- message in the Replication Server log when

-- return code 4025 is received.

--

-- 1 Create an error class for Oracle.

-- 2 Initialize the new error class.

-- 3 Assign the action 'warn' for error 4025.

-- 4 Alter any Replication Server connection

-- that replicates TO Oracle to use this

-- new error class

--



-- 1 Issue this command in Replication Server

-- to create the oracle error class



create error class oracle_error_class

go



-- 2 Issue this command in the RSSD

-- to initialize the oracle error class



rs_init_erroractions oracle_error_class,

rs_sqlserver_error_class

go



-- 3 Issue this command in Replication Server

-- to create the oracle error class



assign action warn for oracle_error_class

to 4025

go



-- 4 Issue this command in Replication Server

-- to alter an existing connection to use

-- the oracle error class just created

-- after changing {pds}.{pdb} to the

-- appropriate values for your connection.



alter connection to {pds}.{pdb}

set error class to oracle_error_class

go



CR:417884
CR Number:   417884
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
5.3.00 19 May 2008 Fixed
5.3.00 07 Mar 2006 Fixed
5.3.00 07 Mar 2006 Fixed
5.5.00 06 Mar 2008 Fixed
5.5.00 14 Jan 2008 Fixed
Description
ORACLE ONLY: Similar to support for table and

procedure replication, Oracle Sequences can be

individually marked for replication using the new

Replication Agent command pdb_setrepseq.



pdb_setrepseq



Description: Returns the sequence replication

marking status; marks specified sequence for

replication; unmarks all marked sequences or a

specified sequence; enables or disables

replication for all marked sequences or a

specified sequence. This command is available for

Oracle only.



Syntax:



To return sequence replication marking status:



pdb_setrepseq

[sequence_name|mark|unmark|enable|disable]



To unmark, enable, or disable all marked

sequences:



pdb_setrepseq all, {unmark[, force]

|enable|disable}



To mark, unmark, enable, or disable a specified

sequence:



pdb_setrepseq sequence_name, {mark|unmark[, force]

|enable|disable}



To mark a specified sequence for replication with

a replicated name:



pdb_setrepseq sequence_name, repname, mark



Parameters:



sequence_name



The name of a user sequence in the

primary database. The sequence_name option can be

delimited with quote characters to specify the

character case. If mixed character case (both

uppercase and lowercase) is required, the name

must be delimited. For example: "Sequence".



The sequence_name parameter can be owner-qualified

to include the primary sequence owner name, with

each element separated by a period. For example:

owner.sequence



Note If you must use an object name case that does

not match the setting of the ltl_character_case

parameter, the object name must be delimited. If

an object name contains any non-alphanumeric

characters, such as spaces, periods, and so forth,

it must be delimited with quote characters. For

example:



"sequence name"

owner."sequence name"





repname



The replicated name of the sequence to be updated

at the replicate site, if desired to be different

than the sequence name at the primary site. The

repname option can be delimited with quote

characters to specify character case. See the

previous description of the sequence_name

parameter for details. By specifying a replicated

name, sequence updates can be replicated to a

sequence in the replicate database that has a

different sequence name from the primary database.



The repname option can be owner-qualified to

include the replicate sequence owner name, with

each element separated by a period. For example:



repowner.repname



all



A keyword that refers to all user sequences in the

primary database. By using the all keyword, you

can unmark all user sequences, or apply an enable

or disable operation to all marked sequences.



mark



A keyword that refers to marking user sequences

for replication.



unmark



A keyword that refers to unmarking marked

sequences.



force



A keyword that refers to the unmark operation.

When the force keyword follows the unmark keyword,

the pdb_setrepseq command immediately unmarks the

specified sequence in the primary database,

without first checking the enable status of the

sequence. When the force keyword follows the

unmark keyword and the all keyword, the

pdb_setrepseq command immediately removes

replication marking from all marked sequences in

the primary database, regardless of their enable

status.



enable



A keyword that refers to enabling replication for

marked sequences.



disable



A keyword that refers to disabling replication for

marked sequences.



----------------------------------

Understanding Sequence Replication



Logging of sequence information



Individual sequence changes are not logged in the

Oracle database log file. But changes to Oracle

Sequence do impact (update) the Oracle sys.seq$

table. These changes do not occur with each new

sequence value generated. Instead, the sys.seq$

table is updated periodically, based on sequence

caching refresh activity or other system changes.

The value stored in the sys.seq$ table for a

sequence is the 'next' value to be assigned

'after' the existing cache of values has been

exhausted.



As an example, a newly created sequence starts

with a value of 1, increments by 1 and has a cache

value of 20. These are all default values and can

all be customized. The value stored in the

sys.seq$ record for this new sequence is 21.

This indicates that the 'next' value to be used by

the sequence, after the existing cache of 20

numbers is used, is 21. The record in sys.seq$

does not change until the sequence value hits 21.

At that time, Oracle will 'cache' the next 20

values for the sequence, and the sys.seq$ record

will be updated to 41. It is this value (41)

recorded in change to the sequences sys.seq$

record, that will be used for replication. The key

point then is recognizing that not every

individual sequence update is recorded in the log,

and is therefore not available for replication.



Replicating sequence changes



When a sequence is marked for replication, changes

to that sequence against sys.seq$ are captured and

sent to Replication Server in the form of

parameters passed to a procedure. The procedure

(rs_update_sequence) must be installed at the

standby site as part of system setup, as well as a

function replication definition for that

procedure. At the standby site, an implementation

of rs_update_sequence will increment a same-named

sequence until its value is equal to that at the

primary.



Scripts are provided to create the

rs_update_sequence stored procedure and function

replication definition. The scripts can be found

in the Replication Agent installation as:



$SYBASE/RAX-12_6/scripts/

oracle_create_replicate_sequence_proc.sql

$SYBASE/RAX-12_6/scripts/

oracle_create_rs_sequence_repdef.sql



Performance considerations



Compared to the performance of incrementing a

sequence at the Primary database, particularly

where sequence values are cached, the effort to

increment the same sequence at the standby site

may be less efficient. The stored procedure must

dynamically determine the sequence to increment,

and must loop internally, incrementing the

sequence until the primary value has been reached.

The loop is required because there is no way to

'assign' a specific value to a sequence.



Since the name of the sequence is passed as a

parameter, Oracle cannot pre-compile the procedure

for efficiency. With the addition of the looping

activity required to properly increment the

sequence, the performance of the solution may

impact some environments where a large number of

highly used sequences is the norm.



Sequence replication alternatives



If the performance of sequence replication is a

concern, there are other alternatives to

replication that support primary and standby use

of the same sequence. These alternatives are

currently suggested by Oracle and others

interested in providing sequence coordination

between multiple sites.



1) Assuming the sequence is being used to generate

primary key values, the sequence at each site can

be concatenated with something unique to the site.

For example, use a sequence number concatenated

with the database name, site name or something

similar. This technique allows each site to

maintain a unique 'range' of sequence of numbers.

Each site having a unique range would mean there

would be no value in sending (replicating) changes

of one site's range to another site.



2) Similar to concatenating, each site could

obtain a different range of numbers by having

different starting points, or increment values,

for the same sequence. As an example, the sequence

at one site could start at one and increment by

two to generate odd numbers (1, 3, 5, etc) while

the other site starts at two and generates even

numbers (2, 4, 6 etc). Again, each site would

have a unique range and could avoid any need for

replication.



3) A third option is available to standby

solutions, where the standby site is for read-

only, and does not access the sequence value until

fail-over. Rather than continually replicating a

sequence's value, the value of the sequence at the

standby site could be updated as part of the

failover tasks. After failover and before the

standby allows connection to client applications,

a script or procedure could query the last used

sequence value (based on the last table to use it

for a primary key) and update or redefine the

sequence once, based on that calculated value.



CR:418003
CR Number:   418003
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: Executing 'ra_helpfield' with

a non-numeric value for the version or

field id field results in a

NumberFormatException.



CR:418021
CR Number:   418021
Product Name:   Sybase Replication Server
Product Component:   RSMJavaPlugin
Status:   Closed
OS:   Solaris
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Jan 2007 Fixed
15.0.1 07 Mar 2007 Fixed
Description
The add server wizard fails to add a server and does not display an error when the interface file entry for the server to be added is incorrect or if the server to be added is down.



CR:418026
CR Number:   418026
Product Name:   Sybase Replication Server
Product Component:   RSMJavaPlugin
Status:   Closed
OS:   Solaris
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Sep 2009 Presently Not Targeted For Any Future Release Of This Product
Description
When a remote RMS is added to a 3-tier environment, the reason field in the detail window is not updated until the user does a manual refresh.



CR:418128
CR Number:   418128
Product Name:   Sybase Replication Server
Product Component:   RSMJavaPlugin
Status:   Open
OS:   Solaris
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
In a 3-tier/RMS environment, the roll-up status for an ASE may not accurately reflect the state of its components.



CR:418136
CR Number:   418136
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Generic
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 Mar 2006 Fixed
15.0 201 28 Mar 2006 Fixed
Description
RMS is not sending updates on changes to its own status to other client applications.



CR:418171
CR Number:   418171
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 Mar 2006 Fixed
21 Mar 2006 Fixed
20 Jul 2006 Fixed
Description
Connection established to materialize a subscription may not get closed after the materialization procedure completes.



CR:418268
CR Number:   418268
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: Replication Server script

hds_oracle_setup_for_replicate.sql is missing

synonyms required for DDL replication.



CR:418272
CR Number:   418272
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
5.5.00 19 May 2008 Fixed
5.3.00 24 Aug 2006 Fixed
Description
ORACLE ONLY: Date datatype value fails to

replicate when pdb_convert_datetime is false.



CR:418624
CR Number:   418624
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: Re-initialization will clear

out the repository if the connection to the

primary database is not available.



CR:418646
CR Number:   418646
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 23 Jan 2006 Fixed
Description
ORACLE ONLY: Redo log truncation fails with SQL

error ORA-01000: maximum open cursors exceeded.

If redo log truncation fails, Oracle will

eventually run out of log space, which will cause

all primary database activity to stop.



CR:418751
CR Number:   418751
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
RS doesn't release memory when MSA repdef and subscription is on the same database as table repdef and subscription.
Workaround Description
 Reboot RS. When the primary connection is dropped, the memory is released from admin statistics, "mem_in_use" however, the OS still shows the process has that much memory allocated.



CR:418781
CR Number:   418781
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Linux
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 Feb 2006 Fixed
28 Feb 2006 Fixed
15.0.1 21 Feb 2007 Fixed
Description
Introduce a server wide Repserver configuration parameter, deferred_queue_size, for setting

OCS deferred queue size.



CR:418789
CR Number:   418789
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   penelope
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
PowerDesigner does not close all connections when disconnecting from a repository hosted on Microsoft SQL Server 2000. A repository connection remains open on MS SQL Server for each connection made to the repository. As a result, the amount of open/orphan connections increases by one on the server for each repository connect/disconnect process.



To close the open/orphan connections, either shutdown the PD application or kill the processes in Sql Server.



CR:418803
CR Number:   418803
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   AIX
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Apr 2006 Fixed
Description
Failed to assert 'element_ptr->sync_spinlock_owner == RSHandle' at 5434,

'eneric/useful/sync.c' with debug binary.
Workaround Description
 I believe the problem does not occur with SMP off or if the optimized binary is used. On the other hand, this assertion error could be hiding a problem that the optimized binary would have.



CR:418961
CR Number:   418961
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   12.6.0.5201P2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: The configuration parameter

'truncation_type' is incorrectly initialized to

'interval', not 'locator_update'.



CR:419049
CR Number:   419049
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: Marking a table or procedure that has

a delimited name fails with an error similar to:

Table <"qa1_Char"> could not be marked because:

Table <"qa1_Char"> is not in database <or920sh3>.



CR:419094
CR Number:   419094
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
RS stacks after deleting row from rs_subscription.
Workaround Description
 Reboot of RS after stack, then continue to do the work. In this case, after the RS came up, we were able to delete the row for the database out of rs_repdbs and drop the msa replication definition through normal means.



CR:419176
CR Number:   419176
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Microsoft Windows
Original Version:   12.5
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Jul 2006 Presently Not Targeted For Any Future Release Of This Product
Description
RS suddenly slows down for no apparent reason and stays slow
Workaround Description
 reboot the RS



CR:419212
CR Number:   419212
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Microsoft Windows
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Replication Server stack traces on windows when a lot of routes are being dropped at the same time.



CR:419300
CR Number:   419300
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Linux
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
14 Mar 2006 Fixed
14 Mar 2006 Fixed
Description
The SMP feature is not available on Linux in GA RS 15.0 release.



CR:419311
CR Number:   419311
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: The 'ra_updatedevices'

command does not update the devices

information.



CR:419312
CR Number:   419312
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.2.01 26 Jan 2006 Fixed
Description
ORACLE ONLY: Warning message for invalid (null)

DDL operation is unnecessarily filling up the log.



CR:419342
CR Number:   419342
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6.09 08 14 Feb 2006 Fixed
Description
High extracted RBA and High extracted LRSN in the status display, may not be from the same DB2 member.
Workaround Description
 Once you see the LRSN, find the LRSN amongst the individual DB2 members and get the RBA that way.



CR:419394
CR Number:   419394
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6.09 07 10 Feb 2006 Fixed
Description
ERROR_CODE should be set to 04 for tables in LTMOBJECTS that do not exist.



CR:419425
CR Number:   419425
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: The Replication Agent log reader is

always using iso_1 for char/varchar column

encoding, regardless of the default JAVA

file.encoding or the RA_JAVA_DFLT_CHARSET

environment variable setting.



CR:419517
CR Number:   419517
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6.09 08 17 Feb 2006 Fixed
Description
0C4 in module LTMAPI while handling an incorrect DB2 IMAGE COPY file



CR:419599
CR Number:   419599
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   NA
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
07 Feb 2006 Fixed
08 Mar 2006 Fixed
Description
DSI does not translate numerics correctly with DB2 function string class on utf8 RS.
Workaround Description
 None at this moment (unless use a non-utf8 RS)



CR:419769
CR Number:   419769
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
06 Nov 2008 Fixed
Description
ORACLE ONLY: Un-marking of a table

followed by re-marking of the same table

allowed un-marked rows to be replicated.



CR:419786
CR Number:   419786
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   12.5.0.303P2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.5.0.304P3 12 Apr 2006 Third Party Problem
Description
ORACLE ONLY -- Workaround: A bug exists in

Oracle 9.2.0.6 UTF8 with the 9.2.0.5 and 9.2.0.6

Oracle JDBC drivers. The bug occurs when selecting

from a column defined as char(1) -- instead of the

select returning a single character, it returns

the character plus a blank (for example, "A ").

The workaround is to use the Oracle 10.1.0.2

JDBC driver.
Workaround Description
 Use the Oracle 10.1.0.2 JDBC driver.



CR:419790
CR Number:   419790
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6.09 07 10 Feb 2006 Fixed
Description
Data is replicated when DATACAPTURE CHANGES and LTMOBJECTS.ERROR_CODE is 12.



CR:419838
CR Number:   419838
Product Name:   Sybase Replication Server
Product Component:   InstallShield
Status:   Closed
OS:   Generic
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 May 2008 Fixed
Description
InstallShield considers the French, Chinese and Japanese languages as components to RS 15.0 and therefore they are not listed specifically listed in the RS Language Modules as part of a "Full" install. These languages will be installed as part of the "Full" installation.



This could be confusing to the user who would expect to see all of the "feature" languages (which are listed) as well as the "component" languages which are not.



CR:419922
CR Number:   419922
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.2.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
5.3.00 25 Jul 2008 Fixed
Description
ORACLE ONLY: Un-marking of a table

followed by re-marking of the same table

failed to reflect change in owner mode.



CR:419971
CR Number:   419971
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   12.6.0.5201P2
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: On Unix, when starting the

Replication Agent as a background process in a

Korn or Bourne login shell, the Replication Agent

System Database (RASD) would shut down when

logging off or causing other signals to be raised.
Workaround Description
 Start Rep Agent from csh.



CR:420168
CR Number:   420168
Product Name:   Rep Serv Troubleshoot Guide
Product Component:   Rep Serv Troubleshoot Guide
Status:   Closed
OS:   all
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0 21 Feb 2007 Fixed
Description
Include ERROR #21 DSI(157ds.db) - open server call to routine 'srv_spawn' failed. message in the Troubleshooting Guide.
Workaround Description
 This problem is already in Infobase that is distributed as "additional documentation." We would like to include this in the Troubleshooting Guide. The Open Server doc does not indicate which parameter needs to be increased if the srv_spawn function fails in Rep Server.



CR:420195
CR Number:   420195
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6.09 08 Mar 2006 Fixed
Description
Maclib members, APIXITCA and LECMDEXT, required for user exits are missing.



CR:420208
CR Number:   420208
Product Name:   Other - Docs: Rep Server
Product Component:   Other - Docs: Rep Server
Status:   Closed
OS:   NA
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
09 Feb 2009 Fixed
Description
To use batching in replication to DB2, alter connection to set batch_begin to "off" and set dsi_cmd_separator to ";"
Workaround Description
 Without the two parameters set, batch must be set to off to get the connection to stay up.



CR:420212
CR Number:   420212
Product Name:   Replication HDS
Product Component:   HDS scripts
Status:   Closed
OS:   Unknown
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
28 Oct 2009 Not a Bug
Description
hds_xxx_connection_sample.sql implies that batch must be off and the batch clause cannot be included in the create connection command.



CR:420232
CR Number:   420232
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.3.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: Inability to find the Oracle

timezone.dat file is reported after the Oracle

database metadata is loaded.



CR:420384
CR Number:   420384
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.1.01
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: Objects that contain unsupported

data types can not be marked for replication.



The unsupported data types for tables are:

SYS.UriType, SYS.DBUriType, SYS.HttpUriType,

SYS.FTPUriType, ORDSYS.ORDAudio, ORDSYS.ORDImage,

ORDSYS.ORDVideo, ORDSYS.ORDDOC,

MDSYS.SDO_GEOMETRY, all reference types, all

opaque types, the nested table and VARRAY

collection types and the MLSLABEL type.



The unsupported data types for procedures are:

all user-defined data types, including object

types, all reference types, all opaque types,

the nested table and VARRAY collection types,

the MLSLABEL type and the BOOLEAN type.



CR:420403
CR Number:   420403
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Microsoft Windows
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
21 May 2008 Fixed
Description
When Replication Server 15.0 is installed on top of existing Replication Server 12.6 directory and SYSAM has already been installed as a service by Replication Server 12.6 installation, SYSAM needs to be re-installed again in order to use Replication Server 15.0 release.



In order to do this:



Go to %SYBASE%\%SYBASE_SYSAM%\bin



and run



sysam uninstall

sysam install



This will install and start SYSAM service using Replication Server 15.0 release.



CR:420474
CR Number:   420474
Product Name:   RepAgent for MVS
Product Component:   DB2
Status:   Closed
OS:   MVS
Original Version:   12.6.08
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12.6.09 09 08 Mar 2006 Fixed
Description
Value in High Extracted RBA is for the wrong DB2 member when DB2 member display does not list members in ID order.
Workaround Description
 The H/W RBA info in the loginfo display is correct. Match up the extracted RBA to the member that is closest to the H/W RBA



CR:420502
CR Number:   420502
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
08 Feb 2006 Fixed
21 Feb 2006 Fixed
Description
The SYNC module has a small memory(16K) leak when memory for the key value is not de-allocated on the global memory header when the SYNC module is managing pointer handles.



CR:420553
CR Number:   420553
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.3.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: 'pdb_setreptable mark' command

does not return all marked tables.



CR:420554
CR Number:   420554
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.3.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
5.3.00 14 Jan 2008 Fixed
Description
ORACLE ONLY: When a new user is added to

the owner filter list and the RepAgent is

restarted, the objects owned by the user

are not filtered out for replication.



CR:420612
CR Number:   420612
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.3.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 07 Mar 2006 Fixed
5.3.00 07 Mar 2006 Fixed
Description
ORACLE ONLY: Tables that include long columns may

be incorrectly read. Fix requires that

pds_username have 'SELECT' privilege on table

SYS.COLTYPE$.



CR:420634
CR Number:   420634
Product Name:   Sybase Replication Server
Product Component:   RSMJavaPlugin
Status:   Closed
OS:   NA
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.0.1 403 22 Jan 2007 Fixed
15.0.1 403 07 Mar 2007 Fixed
Description
These two files are not used or needed in the 15.0 release of Sybase Central and the Replication Manager Plugin. Execution of these scripts will result in an error, but will do no harm. The 15.0 installer automatically registers the RMP. If a user ever needs to manually register the plugin, they should use the procedure documented in the Replication Manager online Help (select Tools | Plug-ins, click Register, and then specify the plug-in either by registration file or JAR file (you can also browse for the file).



CR:420645
CR Number:   420645
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Extra rows are put into rs_routes when a new route is created that is already a source of other routes.
Workaround Description
 The extra rows in rs_routes is causing the error in reporting. When the route is dropped, the extra rows are dropped also. The route data is correct, it is just that there is no site information for that RSid in the route table. If the customer wants to show the site information, they could copy the row from rs_sites to this RSSD so that the name can be resolved.



CR:420772
CR Number:   420772
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.3.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.3.00 22 Feb 2006 Fixed
Description
ORACLE ONLY: On Linux, putting the Replication

Agent instance in the background causes the

Replication Agent System Database (RASD) to

shut down when logging off or causing

other signals to be raised.
Workaround Description
 Instead of starting the Rep Agent instance and then putting it in the background, start the instance with the & initially, or leave the Rep Agent in the foreground. The ASA stays running, and the pdb_xlog_init succeeds. RWA.



CR:421079
CR Number:   421079
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Mar 2006 Fixed
15.0 08 May 2006 Fixed
15.0 08 May 2006 Fixed
12.6 08 May 2006 Fixed
Description
Repserver may read uninitialized memory when when executing _sts_free_or_transfer_obj().



CR:421237
CR Number:   421237
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Solaris
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Prompt does not return from suspend connection if replicate site is in log suspend status.
Workaround Description
 Clear the problem with the log suspend (e.g. add more log space or dump the tranaction log). If a customer doesn't want to do these things to clear up the log suspend, RS must shutdown for Rep Server to release the prompt. Also note that when the RS comes back up, the connection is suspended. If one tries to resume the connection without clearing the log suspend, the prompt does come back from the resume.



CR:421335
CR Number:   421335
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Generic
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
MSA replication definition is case sensitive, in a nocase enviroment.
Workaround Description
 In the database replication definition, one has to use the exact case.





--------------------------------------华丽的分割线-------------------------------------------------------------------------

Sybase SQL Anywhere数据库恢复工具ReadASADB:

之前就已经研发成功了能够从Sybase SQL Anywhere的DB文件中恢复数据的工具: ReadASADB。
此工具支持ASA v5.0, v6.0, v7.0, v8.0, v9.0, v10.0, v11.0, v12.0, v16.0, v17.0等版本。
能够从损坏的SQL Anywhere数据文件(.db)和UltraLite数据文件(.udb)上提取数据的非常规恢复工具。
恢复Sybase SQL Anywhere的工具在国内处于领先水平。

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,16.x,17.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使用介绍

Sybase SQL Anywhere数据库恢复工具ReadASADB适用场景

各种误操作:

  1. 误截断表(truncate table)
  2. 误删除表(drop table)
  3. 错误的where条件误删数据
  4. 误删除db或log文件
  5. 误删除表中的字段

Sybase SQL Anywhere数据库恢复工具ReadASADB的应用场景:

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
7、*** ERROR *** Assertion failed: 201417 (7.0.4.3541) Invalid count or free space offset detected on a table page
8、Internal database error *** ERROR *** Assertion failed: 201425 (8.0.3.5594) Invalid count or free space offset detected on a free list page -- transaction rolled back.
9、Internal database error *** ERROR *** Assertion failed: 100702 (8.0.1.2600) Unable to modify indexes for a row referenced in rollback log -- transaction rolled back


-------------------------------------------------------------------------------------------

Sybase ASE数据库恢复工具READSYBDEVICE:

一个不依赖数据库管理系统、直接从Sybase数据库设备文件上提取数据的业内领先的恢复工具!
能够从损坏的Sybase ASE设备文件(.dat)上提取数据的非常规恢复工具。

Sybase ASE数据库恢复工具READSYBDEVICE的主要功能:

  1. 被勒索病毒加密数据文件及备份文件情况下的恢复;
  2. 系统崩溃只剩下数据文件的情况下的恢复,甚至数据库文件不存在而只有损坏的备份文件情况下的恢复;
  3. 因断电、硬盘坏道等造成数据库文件损坏情况下的恢复;
  4. delete数据恢复、误update数据恢复、误删除表(drop)恢复、误truncate表恢复 等;
  5. 各种Sybase内部系统表损坏、索引错误的修复;
  6. master数据库损坏而无法正常运行情况下的恢复;
  7. Sybase数据库被标记为可疑,不可用等情况的恢复;
  8. Sybase数据库中数据文件内部出现坏块情况下的恢复;
  9. Sybase数据库无数据文件但有日志文件的情况下的恢复;
  10. Sybase数据库只有数据文件无任何日志文件的情况下的恢复;
  11. Sybase数据文件被误删除情况下的碎片提取恢复;
  12. 磁盘阵列上的Sybase数据库被误格式化情况下的数据库恢复;
  13. 数据库sysobjects等系统表损坏无法正常应用情况下的恢复;
  14. Sybase数据库还原数据库出现失败情况下的恢复;
  15. Sybase数据库只剩下损坏的备份文件情况下的恢复。

Sybase ASE数据库恢复工具READSYBDEVICE支持的版本:

Sybase ASE 11.0.x,11.5.x,11.9.x,12.0.x,12.5.x,15.0.x,15.5.x,15.7.x,16.0.x


-------------------------------------------------------------------------------------------

SQL Server数据库恢复工具SQLRescue:

一个不依赖数据库管理系统、直接从SQL Server数据库文件上提取数据的业内领先的恢复工具!
能够从损坏的SQL Server数据库文件(.mdf)上提取数据的非常规恢复工具。

SQL Server数据库恢复工具SQLRescue的主要功能:

  1. 系统崩溃只剩下数据文件的情况下的恢复,即无日志文件或者日志文件损坏情况下的恢复;
  2. 断电导致数据库文件损坏情况下的恢复;
  3. 硬盘坏道造成数据库损坏情况下的恢复;
  4. 数据文件内部存在坏页情况下的恢复;
  5. 企业管理器误删除数据表记录,管理软件误删除数据表记录的恢复;
  6. 并闩锁错误、格式化、误删除后导致软件不能使用的情况;
  7. 无法读取并闩锁页sysindexes失败情况下的修复;
  8. 数据文件被误删除情况下的碎片提取恢复;
  9. 系统表损坏、索引错误、误删除数据库表、删除记录的数据找回;
  10. master数据库损坏而无法正常运行情况下的恢复;
  11. 数据文件无法附加情况下的数据恢复;
  12. 数据库被标记为可疑,质疑,不可用等情况的恢复;
  13. 数据库sysobjects等系统表损坏情况下的恢复;
  14. 数据被误(drop、delete、truncate)删除表数据的恢复,误update后的数据恢复等;
  15. 还原时报一致性错误,错误823等情况下的数据恢复,各种错误提示的数据库文件修复;
  16. 数据库被误格式化等情况下的数据库恢复;
  17. 日志收缩造成数据库损坏情况下的恢复;
  18. 仅剩损坏的备份文件情况下的恢复。

SQL Server数据库恢复工具SQLRescue技术特点:

只要SQL Server数据库的数据文件存在,我们就有办法帮您从数据文件中找回重要数据。
  1. 从数据文件中直接恢复数据
  2. 不能附加时直接恢复数据并生成新的数据库
  3. 系统表损坏的数据库修复
  4. 快速修复SQL 823错误、连接中断错误

SQL Server数据库恢复工具SQLRescue支持的版本:

Microsoft SQL Server 7.0, 2000, 2005, 2008, 2008R2, 2012, 2014, 2016, 2017,2019。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------