提供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:494192
CR Number:   494192
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.5.10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.11 05 May 2008 Fixed
Description
ORACLE ONLY: ConcurrentModificationException

occurs during skip operations list truncation.



CR:494288
CR Number:   494288
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.6.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.07 07 Jul 2008 Fixed
5.7.00 07 Jul 2008 Fixed
Description
ORACLE ONLY: The device status returned by

ra_helpdevice is incorrect if the device is

stored under ASM.



CR:494320
CR Number:   494320
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Generic
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 400 07 Apr 2008 Fixed
15.1 400 10 Jul 2008 Fixed
Description
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.



CR:494368
CR Number:   494368
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Linux
Original Version:   12.6 ESD#10
Fixed Version Build Resolution Date Closure Code (If Appropriate)
06 Apr 2009 Insufficient priority to fix
Description
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)
Workaround Description
 Please unify all charsets.



CR:494611
CR Number:   494611
Product Name:   Rep Serv Admin Guide
Product Component:   Rep Serv Admin Guide
Status:   Closed
OS:   all
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 May 2008 Added to user documentation
Description
cannot use "use dump marker" clause with XPDL process
Workaround Description
 If using xpdl to load the target, use the create option. At the time of this writing, the reason why xpdl will not work with "use dump marker" is because the transaction log needs to be truncated and the database be put into single user mode, in order to get a "clean" dump for the xpdl process.



CR:494701
CR Number:   494701
Product Name:   Rep Serv Install Guide
Product Component:   Rep Serv Install Guide
Status:   Closed
OS:   NA
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Jul 2008 Fixed
Description
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.



CR:494740
CR Number:   494740
Product Name:   RepConnector
Product Component:   Run-time Engine
Status:   Open
OS:   Microsoft Windows
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Fixed
Description
RepConnector is creating file EAServer\bin\mqjms.trc and it keeps growing and consuming disk space.



CR:494811
CR Number:   494811
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   5.5.09
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.11 05 May 2008 Fixed
5.6.05 10 Jun 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
ORACLE ONLY: Replication Agent processing fails

with error: "ChainedOperationException: Could not

concatenate chained operation because: Error

processing record with supplemental data whose

column index duplicates other data columns".



CR:494819
CR Number:   494819
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   Windows XP
Original Version:   tyresias
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
comments for user and groups in repository are not shown if using proxy connection to repository after a logout/login -> comments are lost.



Workaround: use direct connection to repository



CR:495027
CR Number:   495027
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Microsoft Windows
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
10 Feb 2009 Fixed
12 Feb 2009 Fixed
23 Apr 2009 Fixed
Description
Issuing command "create connection ... set dsi_replication_ddl 'on'" may cause the Replication Server to terminate unexpectedly.
Workaround Description
 create connection without dsi_replication_ddl on, then alter the connection and set dsi_replication_ddl 'on'.

cccc



CR:495244
CR Number:   495244
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   Log Admin
Status:   Closed
OS:   Generic
Original Version:   5.6.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 31 Jul 2008 Fixed
5.8.00 31 Jul 2008 Fixed
5.5.17 31 Jul 2008 Fixed
5.7.01 05 Feb 2009 Fixed
Description
If the pdb_xlog_prefix_chars configuration

parameter is set to a value that does not

contain an underscore, Replication Agent will

create system objects with delimited names

in the primary database during initialization.

This may cause Replication Agent api commands

to fail.



CR:495246
CR Number:   495246
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.6.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.8.00 30 Aug 2008 Fixed
5.6.04 07 May 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
ORACLE ONLY: Replication Agent fails with a

NULLPointerException when attempting to read

a redo log on an AIX raw device.
Workaround Description
 Force Oracle to write to the unused redo log group.



This can be accomplished by forcing Oracle to "switch" the on-line logs that is currently active, using Oracle command "ALTER SYSTEM SWITCH LOGFILE".



This command may need to be executed as many as 5 times, in order to get Oracle to cycle over to the redo log group that has an "unused" status.



Status of the on-line redo logs can be checked using the following Oracle command:

SELECT * FROM V$LOG:



Once Oracle has used the redo log (Status of CURRENT or INACTIVE), the Rep Agent pdb_xlog init command can be re-run.



CR:495258
CR Number:   495258
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.6.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.10 25 Feb 2009 Fixed
5.8.00 25 Feb 2009 Fixed
Description
ORACLE ONLY: The locator is not getting updated

when the database is inactive with respect to

replicated changes, even after reading to the end

of a log file or when reading at the end of the

log.



CR:495380
CR Number:   495380
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)
31 Aug 2008 Fixed
23 Sep 2008 Fixed
23 Sep 2008 Fixed
23 Sep 2008 Fixed
04 Aug 2009 Fixed
Description
The Replication Server can terminate

unexpectedly in its attempt to log an

error message. This can occur when

specific internal resources are not

available during the process of logging

the error message.
Workaround Description
 Please increase num_msgs parameter if the stack trace in a core file contains srv__allocmsg() or srv_putmsgq().



CR:495416
CR Number:   495416
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.6.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.8.00 30 Aug 2008 Fixed
5.7.00 30 Aug 2008 Fixed
5.6.04 07 May 2008 Fixed
5.7.00 14 Apr 2008 Fixed
Description
ORACLE ONLY: Command

'ra_config pdb_archive_remove, true' fails with

exception "Could not find Resource Bundle

containing index: LR_BAD_ARC_DIR_ACCESS_WRITE".



CR:495445
CR Number:   495445
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/UDB
Status:   Closed
OS:   Generic
Original Version:   5.6.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.8.00 30 Aug 2008 Fixed
5.6.04 07 May 2008 Fixed
Description
UDB ONLY: pdb_setreptable command does not display

case-sensitive replicate table name correctly.



CR:495568
CR Number:   495568
Product Name:   Rep Serv Commands Ref
Product Component:   Rep Serv Commands Ref
Status:   Closed
OS:   all
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 13 May 2008 Fixed
Description
create encryption key, alter encryption key, and drop encryption key are replicated by the ASE Rep Agent.



CR:495591
CR Number:   495591
Product Name:   Sybase Replication Server
Product Component:   rs_init
Status:   Closed
OS:   AIX
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
26 Mar 2008 Fixed
26 Mar 2008 Fixed
27 Mar 2008 Fixed
27 Mar 2008 Fixed
Description
After completing all tasks, 'rs_init'

may suspend and not terminate. This can

occur if 'rs_init' fails to properly

spawn a Replication Server process.



CR:495761
CR Number:   495761
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Generic
Original Version:   5.6.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.8.00 30 Aug 2008 Fixed
5.7.00 30 Aug 2008 Fixed
5.6.04 07 May 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: Replication Agent fails

during DDL replication with error "The object whose id is

XXX is not a valid object." after the Replication

Agent has been re-initialized.
Workaround Description
 I tried number(*,50), it is OK.



CR:495783
CR Number:   495783
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
02 Apr 2008 Fixed
28 Apr 2008 Fixed
28 Apr 2008 Fixed
28 Apr 2008 Fixed
Description
For the ASE messages 13925 and 13905,

the 'assign action' values should be set

to 'warn' rather than

'stop_replication'.
Workaround Description
 This fix was put into EBF between 15.01 ESD #3 and #4, as well as RS 15.1 ESD #1 in rs_install_systables_*.sql.



insert rs_erroractions (ds_errorid, errorclassid, action, prsid) values (13905,

0x0000000001000002, 3, 0)

go

insert rs_erroractions (ds_errorid, errorclassid, action, prsid) values (13925,

0x0000000001000002, 3, 0)

go



CR:495834
CR Number:   495834
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.6.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.06 13 Jun 2008 Fixed
5.7.00 15 Jun 2008 Fixed
5.5.17 17 Jun 2008 Fixed
Description
ORACLE ONLY: Replication of a LOB value, which

immediately follows the insertion of an empty LOB

in the same location, fails with an error in

Replication Server indicating "The data row that

the writetext command is associated with is

missing."



CR:495856
CR Number:   495856
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   5.6.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
29 May 2008 Not reproducible with latest version of the product available as of Resolution Date
Description
Sybase Replication Agent for Unix & Windows/15.1.0.5602 is stopping abnormally when executed by the windows service manager starting a batch file.
Workaround Description
 -Xrs command line option was added in the last line of the

%SYBASE%\RAX-15_1\bin\ra.bat ...

"%JRE%" -server -Xrs -Xmx%RA_JAVA_MAX_MEM% %FILENC% "-Dinstall.root=...

... see the following information for full details .



The customer has done the following...used the combination of the three items below to stablize the repagent running as a windows service under the windows service manger that starts the batch file for repagent

...the caveat here is this...

State Street created their Windows Service for starting rep agent under the

Windows Service Manager by copying(pse believes they did this by exporting a

key in regedit...changed it using a hexeditor and then importing it) an

existing service in the registry and then changing the name of that newly

copied service from whatever it was on the copied service to RAM_ONYX ...



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RAM_ONYX]



...then they changed the EXPANDABLE STRING VALUE (REG_EXPAND_SZ) item named

ImagePath in the registry under...

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RAM_ONYX]

...to use the batch file used to start rep agent ...

ImagePath REG_EXPAND_SZ C:\Sybase\RAX-15_1\RAM_ONYX\RUN_RAM_ONYX_ADMIN.bat

1>> C:\SYBASE\RAX-15_1\RAM_ONYX\RAM_ONYX.log 2>&1



1) used ...

C:\Sybase\RAX-15_1\RAM_ONYX\RUN_RAM_ONYX_ADMIN.bat 1>> C:\SYBASE\RAX-15_1\RAM_ONYX\RAM_ONYX.log 2>&1



... in their image path in the registry key for their user-defined service to be started by the windows service manager

... we are unsure how they created this service([HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RAM_ONYX])



here is the information we gleaned out of their exported registry key...



[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RAM_ONYX]

(Default) REG_SZ (value not set)

DisplayName REG_SZ Replication Agent for Microsoft SQL Server

ErrorControl REG_DWORD 0x00000001 (1)

ImagePath REG_EXPAND_SZ C:\Sybase\RAX-15_1\RAM_ONYX\RUN_RAM_ONYX_ADMIN.bat 1>> C:\SYBASE\RAX-15_1\RAM_ONYX\RAM_ONYX.log 2>&1

ObjectName REG_SZ GA\mssql_service_acct

Start REG_DWORD 0x00000003(3)

Type REG_DWORD 0x00000010(16)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RAM_ONYX\Enum]

(Default) REG_SZ (value not set)

0 REG_SZ Root\LEGACY_RAM_ONYX\0000

Count REG_DWORD 0x00000001(1)

NextInterface REG_DWORD 0x00000001(1)

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RAM_ONYX\Security]

(Default) REG_SZ (value not set)

Security REG_BINARY 01,00,14,80,b8,00,00,00,c4,00,00,00,14,00,00,00,30,00,00,00,02,00,1c,00,01,00,00,00,02,80,14,00,ff,01,0f,00,01,01,00,00,00,00,00,01,00,00,00,00,02,00,88,00,06,00,00,00,00,00,14,00,fd,01,02,00,01,01,00,00,00,00,00,05,12,00,00,00,00,00,18,00,ff,01,0f,00,01,02,00,00,00,00,00,05,20,00,00,00,20,02,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,04,00,00,00,00,00,14,00,8d,01,02,00,01,01,00,00,00,00,00,05,06,00,00,00,00,00,14,00,00,01,00,00,01,01,00,00,00,00,00,05,0b,00,00,00,00,00,18,00,fd,01,02,00,01,02,00,00,00,00,00,05,20,00,00,00,23,02,00,00,01,01,00,00,00,00,00,05,12,00,00,00,01,01,00,00,00,00,00,05,12,00,00,00







2) used a C:\Sybase\RAX-15_1\RAM_ONYX\RUN_RAM_ONYX_ADMIN.bat file according to the following ...

type C:\Sybase\RAX-15_1\RAM_ONYX\RUN_RAM_ONYX_ADMIN.bat

@echo off

set RA_JAVA_DFLT_CHARSET=

set RA_JAVA_MAX_MEM=256m

set SYBASE=C:\Sybase

set CLASSPATH=C:\Sybase\sqljdbc_1.2\enu\sqljdbc.jar



CALL %SYBASE%\RAX-15_1\bin\ra.bat -i RAM_ONYX







3) changed the last line in the C:\Sybase\RAX-15_1\bin\ra.bat to include the -Xrs arguement option when java is started

... from ...

"%JRE%" -server -Xmx%RA_JAVA_MAX_MEM% %FILENC% "-Dinstall.root=%RAX_DIR%" "-DSYSAM_LICDIR=%SYSAM%\licenses" -classpath "%RAX_JARS%;%JCONN_CLASSES%\jconn3.jar;%JCONN_CLASSES%\jTDS3.jar;%JHOME%\lib\charsets.jar;%RAX_DIR%\classes\sylapi.jar;%CLASSPATH%" com.sybase.ra.RepAgent %*

... to ...

"%JRE%" -server -Xrs -Xmx%RA_JAVA_MAX_MEM% %FILENC% "-Dinstall.root=%RAX_DIR%" "-DSYSAM_LICDIR=%SYSAM%\licenses" -classpath "%RAX_JARS%;%JCONN_CLASSES%\jconn3.jar;%JCONN_CLASSES%\jTDS3.jar;%JHOME%\lib\charsets.jar;%RAX_DIR%\classes\sylapi.jar;%CLASSPATH%" com.sybase.ra.RepAgent %*



CR:495884
CR Number:   495884
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Solaris
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 May 2008 Fixed
19 May 2008 Fixed
15.0 03 Jul 2008 Fixed
15.2 03 Jul 2008 Fixed
Description
The Replication Server may go into an

infinite loop when executing the 'resume

connection skip transaction' command

which may cause the complete consumption

of RSSD log space or ASE locks. This

can occur if the ASE and the Replication

Server are both configured with

multi-byte character sets.



CR:496135
CR Number:   496135
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   15.0.0.5509P6a-ONE_OFF
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.12 06 May 2008 Fixed
5.6.04 07 May 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
ORACLE ONLY: Date values that occur during

Daylight Saving Time transition are incorrectly

adjusted by one hour.



CR:496199
CR Number:   496199
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)
02 Apr 2008 Fixed
02 Apr 2008 Fixed
Description
When upgrading Replication Server 12.6

to Replication 15.0 or higher, an

'assign action' value is incorrectly

created for ASE error #41880 rather than

#418801.



CR:496332
CR Number:   496332
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.6.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.07 01 Jul 2008 Fixed
5.7.00 01 Jul 2008 Fixed
Description
ORACLE ONLY: Configuration property

lr_ntext_byte_order is hidden, and can not be

set by user.



CR:496471
CR Number:   496471
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Generic
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Aug 2008 Presently Not Targeted For Any Future Release Of This Product
Description
RMS performance is severely impacted when monitoring several hundred event triggers. RMS monitoring causes the Replication Server to deny access to other processes. The RMS consumes 95-100% of the CPU. The RMS can take up to 30 minutes to start.



CR:496499
CR Number:   496499
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
24 Aug 2008 Fixed
24 Aug 2008 Fixed
02 Sep 2008 Fixed
Description
An update to the 'rs_last_commit' table

could fail yet still allow the

associated transaction to incorrectly

commit. This can occur when the failure

is caused by insufficient ASE procedure

cache.
Workaround Description
 Change to rs_commit function was made in 15.0.1 ESD #4 (and some of the EBFs between #3 and #4) as well as RS 15.1 ESD #1. The change is in the rs_install_systables_ase.sql and rs_install_systables_asa.sql scripts. Therefore older installations would not have this change. Here is the change:



Sanity check: what the old strings look like:



1> select * from rs_systext where prsid = 0 and parentid = 0x0000000008000002 and texttype = 'O'

2> go

prsid parentid texttype sequence

textval



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

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

---------

0 0x0000000008000002 O 1

execute rs_update_lastcommit @origin = ?rs_origin!sys?, @origin_qid = ?

rs_origin_qid!sys?, @secondary_qid = ?rs_secondary_qid!sys?, @origin_ti

me = ?rs_origin_commit_time!sys?; commit transaction





1> select * from rs_systext where prsid = 0 and parentid = 0x000000000fffff02 and texttype = 'O'

2> go

prsid parentid texttype sequence

textval



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

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

---------

0 0x000000000fffff02 O 1

execute rs_update_lastcommit @origin = ?rs_origin!sys?, @origin_qid = ?

rs_origin_qid!sys?, @secondary_qid = ?rs_secondary_qid!sys?, @origin_ti

me = ?rs_origin_commit_time!sys?; commit transaction



(1 row affected)



Delete the two rows from rs_systext and insert the new rows:





insert rs_systext

values (

0, /* prsid */

0x0000000008000002, /* parentid */

'O', /* texttype */

1, /* sequence */

"execute rs_update_lastcommit @origin = ?rs_origin!sys?, @origin_qid = ?

rs_origin_qid!sys?, @secondary_qid = ?rs_secondary_qid!sys?, @origin_time = ?rs_

origin_commit_time!sys?; if @@error <> 0 rollback transaction; commit transactio

n"

)



insert rs_systext

values (

0, /* prsid */

0x000000000fffff02, /* parentid */

'O', /* texttype */

1, /* sequence */

"execute rs_update_lastcommit @origin = ?rs_origin!sys?, @origin_qid = ?

rs_origin_qid!sys?, @secondary_qid = ?rs_secondary_qid!sys?, @origin_time = ?rs_

origin_commit_time!sys?; if @@error <> 0 rollback transaction; commit transactio

n"

)



The reboot the RS.



CR:496624
CR Number:   496624
Product Name:   Rep Serv Commands Ref
Product Component:   Rep Serv Commands Ref
Status:   Closed
OS:   all
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15.1 13 May 2008 Fixed
Description
Examples in filter connection in Replication Monitoring Services API are incorrect
Workaround Description
 Examples of good runs:



1> filter redak1501i.p2 for repit126repa

2> go

RepServer Connection Dsi Rep agent

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

repit126repa redak1501i.p2 on on



(1 row affected)

1> filter redak1501i.p2 for repit126repa dsi = off

2> go

Action Result

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

Filter Set the dsi state filter for the connection redak1501i.p2 to off.



(1 row affected)

1> filter redak1501i.p2 for repit126repa rep agent = off

2> go

Action

Result

-------

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

Filter

Set the rep agent state filter for the connection redak1501i.p2 to off.





(1 row affected)

1> filter redak1501i.p2 for repit126repa

2> go

RepServer Connection Dsi Rep agent

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

repit126repa redak1501i.p2 off off



(1 row affected)



CR:496774
CR Number:   496774
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   tyresias
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Large model consolidates/extracts very slowly.



Initial testing:



PDM file 22.1 MB



Proxy(TBONE server):

Consolidation: 36 minutes

Extraction: 14 minutes



No proxy(TBONE server):

Consolidation: 20 minutes

Extraction: 13 minutes



CR:496889
CR Number:   496889
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
"admin who_is_down" should list threads in CONNECTING status. "admin who_is_down" is intended to provide a succinct list of issues requiring user attention. A DSI EXEC thread in a persistent CONNECTING state is such an issue.



CR:496901
CR Number:   496901
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Generic
Original Version:   15.1.0.5602
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.04 07 May 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: Date values that occur

during Daylight Saving Time transition are

incorrectly adjusted by one hour.



CR:496903
CR Number:   496903
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   MRAgent/ASE
Status:   Closed
OS:   Generic
Original Version:   15.0.0.5500
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 21 Jul 2008 Fixed
5.5.15 10 Jun 2008 Fixed
5.6.05 10 Jun 2008 Fixed
Description
ASE ONLY: Date values that occur during

Daylight Saving Time transition are

incorrectly adjusted by one hour.



CR:496985
CR Number:   496985
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Solaris
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Aug 2008 Presently Not Targeted For Any Future Release Of This Product
Description
The 'get status description' command does not always return the correct descriptions. The command will sometimes return an empty results set.
Workaround Description
 unknown at this time



CR:496987
CR Number:   496987
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Solaris
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Aug 2008 Presently Not Targeted For Any Future Release Of This Product
Description
The result set returned by the 'get status descriptions' command contains 'NULL' rows if the ASE servers in a warm standby configuration are not being monitored by the RMS.
Workaround Description
 Add the ASE servers of both sides of the warm standby to RMA.



CR:496990
CR Number:   496990
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Solaris
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Aug 2008 Presently Not Targeted For Any Future Release Of This Product
Description
RMA needs to find a better way to get server/RA status without requring the server to be added (thus automatically monitored) to the RMA
Workaround Description
 None known - filter <connection> will not work around this behavior.



CR:496991
CR Number:   496991
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Solaris
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Aug 2008 Presently Not Targeted For Any Future Release Of This Product
Description
Allow event trigger to be created at the server level instead of the component level.



CR:497093
CR Number:   497093
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   Windows XP
Original Version:   tyresias
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Please make Configurations scriptable. Add Repository Configuration Objects to the Powerdesigner Metamodel and Scripting. Currently we access the Repository Database directly to retrieve informations about the configurations.



CR:497205
CR Number:   497205
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   MRAgent/ASE
Status:   Closed
OS:   Generic
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 30 Aug 2008 Fixed
5.6.05 14 May 2008 Presently Not Targeted For Any Future Release Of This Product
Description
ASE ONLY:

Support ASE dump transaction command with

parameter "standby_access".



CR:497275
CR Number:   497275
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   15.0.0.5509P6a-ONE_OFF
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.11 06 May 2008 Fixed
5.6.04 07 May 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
ORACLE ONLY: Error "Failed to handle the DDL

operations because there is no object information

in the LogRecord" occurred against an "ALTER

PROCEDURE ... COMPILE" command issued against a

procedure whose owner is in the Replication

Agent's owner filter list.



CR:497321
CR Number:   497321
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Apr 2008 Fixed
12 Jun 2008 Fixed
Description
If the number of CPUs exceeds the amount

allowed by the license, the Replication

Server will incorrectly start rather

than terminate. This can occur only

when using an un-served license.



CR:497499
CR Number:   497499
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.5.12
Fixed Version Build Resolution Date Closure Code (If Appropriate)
01 Sep 2008 Fixed
Description
ORACLE ONLY: ra_truncateusers causes

IllegalStateException if Replication

Agent is never resumed.



CR:497530
CR Number:   497530
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Solaris
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Aug 2008 Presently Not Targeted For Any Future Release Of This Product
Description
The RMS reports the rep agent thread for the active connection in a warm standby as suspended when it is active and transactions are being replicated. This occurs when the active ASE dataserver is part of the RMS environment but the standby ASE dataserver has not been added to the RMS environment.
Workaround Description
 Add both ASE servers, for the active and the standby, to RMA



CR:497537
CR Number:   497537
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Solaris
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Sep 2009 Presently Not Targeted For Any Future Release Of This Product
Description
Messages continue to to be sent out to stdout, hence the window after startup.
Workaround Description
 close the window all the way; do not plan on re-using the window --or --

redirect the stdout file and make sure that it is purged as it will continue to grow as long as agent is up.



CR:497693
CR Number:   497693
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.5.17
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.17 08 Jan 2009 Fixed
5.7.01 10 Nov 2008 Fixed
5.8.00 10 Nov 2008 Fixed
Description
ORACLE ONLY: pdb_setreptable all, mark fails to

mark all user tables in the primary database.



CR:497728
CR Number:   497728
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   NA
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
25 Aug 2008 Presently Not Targeted For Any Future Release Of This Product
Description
Improve method to determine queue latency.



CR:497852
CR Number:   497852
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   Linux
Original Version:   12.6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
*** glibc detected *** double free or corruption (!prev): 0x08a37af0 ***

*** glibc detected *** corrupted double-linked list: 0x08a0d908 ***

Theses errors occurs on RS126E6 when the standby side of replication is stopped when data is being replicated.



CR:497929
CR Number:   497929
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   MRAgent/ASE
Status:   Closed
OS:   Generic
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 30 Aug 2008 Fixed
5.6.05 10 Jun 2008 Fixed
5.5.15 10 Jun 2008 Fixed
Description
ASE ONLY: Generated repdefs for encrypted columns

will generate a DSI 32058 error in Replication

Server with a length mismatch. The error is

similar to "The value given for

'<repdef name>.<encrypted column name>' cannot be

translated from datatype 'binary' to the required

datatype 'varbinary'. Value length is '33';

Maximum target length is '11'."
Workaround Description
 Delete repdef.



CR:498013
CR Number:   498013
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   15.0.0.5509P6a-ONE_OFF
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.13 06 May 2008 Fixed
5.6.04 07 May 2008 Fixed
5.7.00 10 Jun 2008 Fixed
Description
ORACLE ONLY: Replication fails with a duplicate

key violation at the replicate database because

an insert rolled back at the primary database is

incorrectly replicated.



CR:498030
CR Number:   498030
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
16 Apr 2008 Fixed
22 Sep 2008 Fixed
Description
An RSI internal list can be empty at the

time an SQM callback is executed.

Although this is a valid state for the

RSI internal list, the SQM callback is

unprepared for this state which can

result in a failure of the SQM.



CR:498124
CR Number:   498124
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   LTI Driver
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   5.5.12
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.14 28 May 2008 Fixed
5.6.05 10 Jun 2008 Fixed
5.8.00 30 Aug 2008 Fixed
Description
MICROSOFT SQL SERVER and UDB ONLY: A

"Replication Definition Not Found" Exception may

occur if a table is re-marked for replication

using the pdb_setreptable command. Table is marked

once with the "owner" keyword and once without the

"owner" keyword.
Workaround Description
 create replication definition ms2005pdb1_qaf_tint_rep with primary at ram5512_w2003m200564.ms2005pdb1 with primary table named

qaf_tint with replicate table named 'qaf_tint' (pkey numeric, t_tinyint tinyint, t_smallint smallint, t_int

int) primary key (pkey)



pdb_setreptable qaf_tint, qaf_tint, mark



CR:498130
CR Number:   498130
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   5.5.12
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.14 28 May 2008 Fixed
5.6.04 07 May 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: pdb_date command fails

with error "The date time string is invalid and

can not be parsed correctly."



CR:498233
CR Number:   498233
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   AIX
Original Version:   5.5.11
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 May 2008 Bundled Request
Description
ORACLE ONLY: Replication Agent processing fails

with error: "ChainedOperationException: Could not

concatenate chained operation because: Error

processing record with supplemental data whose

column index duplicates other data columns".



CR:498279
CR Number:   498279
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Generic
Original Version:   5.6.04
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.04 07 May 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: Replication Agent fails

with a NullPointerException on a 'resume' command

when the owner of the primary database can not be

found in sys.sysusers view.



CR:498376
CR Number:   498376
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.6.06
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.07 04 Jul 2008 Fixed
5.7.00 29 Jun 2008 Fixed
5.5.17 09 Oct 2008 Consult Complete
Description
ORACLE ONLY: Command pdb_setrepcol fails to find

a table when a synonym is passed as a parameter



CR:498379
CR Number:   498379
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.5.13
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.14 28 May 2008 Fixed
5.6.05 10 Jun 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
ORACLE ONLY: Non-zero generation ID field value

in session repository version locators prevents

truncation.
Workaround Description
 Reset the database generation id to 0 and re-initialize (pdb_xlog init, force) the Replication Agent.



CR:498424
CR Number:   498424
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
22 Jan 2009 Fixed
16 Apr 2009 Fixed
12 Feb 2009 Fixed
16 Apr 2009 Fixed
Description
New subscriptions cannot be validated at the standby target database in a mixed-version environment (Replication Server 12.6->Replication Server 15.1) The "send_enc_password" parameter blocks this creation if the replicated Replication Server has "net password encryption reqd" set to "0".



CR:498467
CR Number:   498467
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
11 Jul 2008 Fixed
11 Jul 2008 Fixed
Description
RS may fail with a stack trace during

function replication if the primary

function name and the replicate function

name differ.



CR:498564
CR Number:   498564
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.6.05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Oct 2008 Fixed
5.8.00 10 Nov 2008 Fixed
5.5.18 10 Dec 2008 Presently Not Targeted For Any Future Release Of This Product
Description
ORACLE ONLY:

Two new Replication Agent commands:

"ra_deviceoffset", "ra_helpdeviceoffset"



ra_deviceoffset

Description

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

Note This command is available only for Oracle.

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

Changes the raw disk device read offset for a

log device recorded in the RASD.



Syntax

ra_deviceoffset device_id, device_offset



Parameters

device_id The device ID is the Oracle redo log

"Group number".

device_offset The offset of the raw device,

from which Replication Agent starts log scan.



Examples

ra_deviceoffset 1, 20

This command specifies the raw device read off-

set to the log device ID "1" as: 20.



Usage

- When ra_deviceoffset is invoked, Sybase Replica-

tion Agent records the specified raw device read

offset for the specified log device in the RASD.



- To get information about log devices stored in

the RASD, use the ra_helpdevice command.



- When ra_updatedevices is invoked, device offset

will not be reset to default value.

The default device read offset is zero.



- If ra_deviceoffset is invoked when the Sybase

Replication Agent instance is in Replicating

state, it returns an error.



- The ra_deviceoffset command is valid only

when the Sybase Replication Agent instance is

in Admin state.



See also

ra_helpdeviceoffset, ra_devicepath,

ra_helpdevice, ra_updatedevices



ra_helpdeviceoffset

Description

Note This command is available only for Oracle.

Returns device offset information about primary

database log devices from the RASD log device

repository.



Syntax

ra_helpdeviceoffset [device]



Parameters

device

The device ID of the primary database log device.



Examples

Example 1

ra_helpdeviceoffset

This command returns device offset information

about all primary database log devices recorded

in the log device repository.

Example 2

ra_helpdeviceoffset 1

This command returns information about the pri-

mary database log device ID "1" in the log

device repository

Usage

- The ra_helpdeviceoffset command returns the

following information for each primary database

log device recorded in the RASD:

Device ID - the log device ID defined by the

primary data server.

Note For Oracle, the ID is the value of the

Oracle Redo Log Group to which this file

belongs.

Database name - the name of the primary

database associated with the log device.

Device name - the logical name of the log

device defined by the primary data server.

Server device path - the path to a multi-

plexed version of the log device.

Disk device path - the path to the log

device (at the standby site).

Disk device offset - the offset from which

Sybase Replication Agent starts scan Oracle

redo log in the log device. The value of

device offset displayed is the value of

"raw_device_offset" property in the Rep-

lication agent configuration file plus the

offset value set by command "ra_deviceoffset".

Disk device status - the current status of

the server device path (ACCESSIBLE, NOT_VALID,

or OPEN).

- The disk device path is the current value

recorded in the RASD. Sybase Replication Agent

uses the disk device path recorded in its RASD

to find each log device.

- For each log device recorded in the RASD, you

can set or change the disk device path with the

ra_devicepath command and set or change the

device offset with the ra_deviceoffset command.

- If you do not specify a disk device path (using

ra_devicepath), the value recorded for the disk

device path is DEFAULT, and Sybase Replication

Agent uses the value recorded for the server

device path to find the log device.

- The disk device status is updated by the Log

Reader component each time you invoke the

ra_helpdeviceoffset command.

- If ra_helpdeviceoffset is invoked with no option,

it returns information for all log devices

recorded in the RASD log device repository.

- If ra_helpdeviceoffset is invoked with the device

option, it returns information only for the

specified log device.

- The ra_helpdevice command is valid when the

Sybase Replication Agent instance is in

either Admin or Replicating state.



See also

ra_deviceoffset, ra_helpdevice,

ra_updatedevices



CR:498570
CR Number:   498570
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)
10 Aug 2009 Fixed
Description
0C4 in LTMAPI, reason code 11 at offset 203B0
Workaround Description
 Start up RA DB2



CR:498650
CR Number:   498650
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   NA
Original Version:   15.0
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Jul 2008 Fixed
Description
In RS 15.x 'RS System Table Diagram' badly describes rs_dbsubsets system table.



CR:499292
CR Number:   499292
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   LTI Driver
Status:   Closed
OS:   Generic
Original Version:   15.0.0.5500
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.14 28 May 2008 Fixed
5.6.04 07 May 2008 Fixed
5.7.00 30 Aug 2008 Fixed
5.5.15 10 Jun 2008 Fixed
5.6.05 10 Jun 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
Configuration parameter lti_send_only_primary_keys,

when set to false, sends all before column images

regardless of columns identified in the

associated Replication Definition.



CR:499317
CR Number:   499317
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.6.05
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.05 10 Jun 2008 Fixed
5.7.00 30 Aug 2008 Fixed
Description
ORACLE ONLY: IllegalArgumentException during log

scanning stops replication.



CR:499543
CR Number:   499543
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   5.6.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.07 03 Jul 2008 Fixed
Description
ORACLE ONLY: After marking a table with its

synonym, no information was given back when you

try to query marked table through its synonym.



CR:499826
CR Number:   499826
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Generic
Original Version:   5.6.03
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.05 10 Jun 2008 Fixed
5.7.00 14 Jul 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: Replication Agent throws

a SQLException error when invoking the ra_migrate

command.



CR:499978
CR Number:   499978
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.5.14
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.01 24 Oct 2008 Fixed
5.8.00 02 Nov 2008 Fixed
Description
ORACLE ONLY: The Replication Agent response

file processing fails with the error

"Device <+XYZ> does not exist" when the parameter

"pdb_archive_path" is set to an ASM disk group

name.
Workaround Description
 Set the configuration property pdb_include_archives value to false. After instance creation, reconfigure it to true.



CR:500150
CR Number:   500150
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   15.0.0.5508P6
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.17 26 Jun 2008 Fixed
5.6.07 27 Jun 2008 Fixed
5.7.00 27 Jun 2008 Fixed
Description
ORACLE ONLY: When altering a function or

procedure to add new arguments, an

"Unsupported SQL type 1111" error occurs.



CR:500312
CR Number:   500312
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Microsoft Windows
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Aug 2009 Presently Not Targeted For Any Future Release Of This Product
Description
After a RMS server shutdown, status information in RMPlug-in is not updated when the server is restarted. Currently, there is no way for a RMPlug-in user to tell that the RMS server has been restarted other than disconnecting and then reconnecting to RMServices. Once the user has reconnected to the RMServices icon, correct status is returned.



CR:500356
CR Number:   500356
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Solaris
Original Version:   15.0.1 ESD#3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 Jan 2009 Fixed
08 Oct 2008 Fixed
08 Oct 2008 Fixed
Description
If (1) a warm standby database is registered

with the Replication Server, (2) an MSA database

is also registered with the Replication Server

and (3) a replication definition is created for

a table in the warm standby database, then the

active connection to the warm standby database

cannot be dropped even after the replication

definition has been successfully dropped.
Workaround Description
 *** Wednesday, July 30, 2008 4:16:30 PM *** brozovic ***

Workaround from engineering:



update rs_objects set dbid = 0 where objname like "rs_drp%" and dbid = <the dbid of the connection being dropped> before dropping the connection.



*** Wednesday, July 30, 2008 4:16:13 PM *** brozovic ***





Only do this if you can afford to lose all the data in the queue (do this in exact order):



1. In the RS, sysadmin hibernate_on

2. sysadmin sqm_purge_queue for the connection that will not drop (which is probably the inbound queue of the logical connection)

3. sysadmin hibernate_off

4. Shutdown the Rep Server

5. delete the "deleted rep def" out of rs_objects

6. Start up RS again

7. Drop the connection using isql into RS



WARNING: It is possible that after you do these steps, the RS will not come back up or the RS will say that a queue is corrupt. If you do get these messages, bring up the RS in standalone mode and purge the queue again and then try and bring back up the RS. In the worst case scenario, you may have to manually drop the partition which implies finding out which queues are using this partition and purging the queues for those connections also.



CR:500368
CR Number:   500368
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Solaris
Original Version:   15.0.1 ESD#3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
15 Jul 2008 Not a Bug
Description
Table replication definition and subscription does not override the exclusion from msa repdef all the time.
Workaround Description
 None, however, once encountering this situation, if you want to change the repdef and subscription name, do the following:



a. Drop subscriptions to the 2nd replicate (msa and table) and drop the table repdef (this must be done).

b. Drop the connection to the 2nd replicate

c. Reboot the Rep Server

d. use rs_init to add the connection back to the rep Server

e. Choose a shorter length name for both the replication definition and the subscription



CR:500445
CR Number:   500445
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   MRAgent/ASE
Status:   Closed
OS:   Generic
Original Version:   15.0.0.5500
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 14 Jul 2008 Fixed
5.5.15 10 Jun 2008 Fixed
5.3.08 30 Aug 2008 Fixed
Description
ASE ONLY: Invalid LTL command sent to Replication

Server causes Replication Agent to go to ADMIN

state with an error similar to

"com.sybase.jdbc3.jdbc.SybSQLException: Line 1,

character 120: Incorrect syntax with the keyword

'_bf'" because a delete operation row has all

NULL data fields.



CR:500492
CR Number:   500492
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Solaris
Original Version:   15.0.1 ESD#3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
13 Feb 2009 Fixed
25 Jan 2011 Fixed
11 Jan 2012 Fixed
26 Jan 2011 Fixed
Description
The RS script 'rsupgr_ase.sql' incorrectly

populates an RSSD table with the value 'set

computed_dml on'. The correct value is 'set

dml_on_computed on'.
Workaround Description
 Edit the script for the proper syntax.



CR:500890
CR Number:   500890
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Open
OS:   NA
Original Version:   15.0.1 ESD#3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
More efficient processing of changes to cached that are identified to sts_full_cache_<tablename>
Workaround Description
 It is not necessary to fully cache tables. STS cache automatically does that for RS and is quite efficient. If there are frequent changes to RS like adding/dropping repdefs and subscriptions, it is best NOT to fully cache those tables, but to increase the sts_cachesize to hold more entries.



CR:528338
CR Number:   528338
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Solaris
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Aug 2009 Presently Not Targeted For Any Future Release Of This Product
Description
Using an interfaces file with a full IPV6 hex hostname address on Unix platforms does not get parsed correctly. The result is that RMS cannot add the server, and returns an error message "Incorrect URL format. java.lang.NumberFormatException for input string." The workaround is to use the IPV6 name format for the hostname in the interfaces file.
Workaround Description
 Rather than using the IPV6 hex format of:

columbia

master tcp ether fd77:55d:59d9:167:203:baff:fe2c:89da 41015

query tcp ether fd77:55d:59d9:167:203:baff:fe2c:89da 41015



use the .v6 shortened IPV6 format that is successful:

columbia

master tcp ether columbia.v6 41015

query tcp ether columbia.v6 41015



CR:528395
CR Number:   528395
Product Name:   Mirror Replication Agent
Product Component:   MRAgent/ASE
Status:   Closed
OS:   Generic
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 16 May 2008 Presently Not Targeted For Any Future Release Of This Product
Description
MRA ONLY:

Resume failure may happen when executing

'pdb_xlog move,force' before 'pdb_init'

and 'ra_init'.



In case of this failure, please issue

command 'pdb_init move_truncpt' to reset

truncation point and 'resume' MRA again.



CR:528401
CR Number:   528401
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Generic
Original Version:   5.6.02
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.05 10 Jun 2008 Fixed
5.7.00 03 Jul 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY:

VirtualFileNotFoundException error is thrown after

the primary database is restored.
Workaround Description
 1) Log into RSSD and execute rs_zeroltm

2) Log into RA and execute "ra_locator zero"

3) Restart RA

4) Resume



CR:528438
CR Number:   528438
Product Name:   Sybase Replication Server
Product Component:   RMA
Status:   Closed
OS:   Microsoft Windows
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
05 Aug 2009 Presently Not Targeted For Any Future Release Of This Product
Description
Using a sql.ini file with a full IPV6 hex hostname address on Windows platforms does not get parsed correctly. The result is that RMS cannot add the server, and returns an error message "Incorrect URL format. java.lang.NumberFormatException for input string." The workaround is to use the IPV6 name format for the hostname in the sql.ini file.
Workaround Description
 Instead of using the full hex values for servers in the sql.ini file, use the "server_name.v6.sybase.com" and the servers may be added to the RMS successfully.



CR:528546
CR Number:   528546
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 03 Jul 2008 Fixed
5.6.05 10 Jun 2008 Fixed
5.6.05 16 May 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: A stored procedure fails

to replicate after the following sequence of steps:

1. Create a stored procedure and mark it for

replication.

2. Unmark and drop the stored procedure

3. Re-create the procedure with the same name,

mark, execute it.



CR:528691
CR Number:   528691
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 03 Jul 2008 Fixed
5.6.05 10 Jun 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: During unmark

processing, the article's version in the RASD is

not correctly updated which may cause some

operations to be missed when Replication Agent

re-scans the log.



CR:528695
CR Number:   528695
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Solaris
Original Version:   15.0.1 ESD#3
Fixed Version Build Resolution Date Closure Code (If Appropriate)
12 Feb 2009 Fixed
15.0 17 Feb 2009 Fixed
15.1 17 Feb 2009 Fixed
15.5 02 Apr 2009 Fixed
12.6 17 Feb 2009 Not a Bug
15.2 07 Apr 2009 Fixed
Description
Immediately after adding a partition, stored procedure 'rs_helppartition' incorrectly

reports 'Segments Allocated' for the new partition as '1' if the stored procedure is invoked without parameters. If the stored procedure is invoked with the new partition name as the parameter, the 'Segments Allocated' field is correctly reported as '0'.



CR:528722
CR Number:   528722
Product Name:   Sybase Replication Server
Product Component:   repserver
Status:   Closed
OS:   Generic
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
19 Aug 2008 Fixed
19 Aug 2008 Fixed
Description
The command 'admin config, dsi_alt_writetext'

does not return the value for the

'dsi_alt_writetext' parameter.



CR:528882
CR Number:   528882
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Generic
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 03 Jul 2008 Fixed
5.6.05 10 Jun 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: Table dbo.sysdiagrams is

incorrectly marked for replication.



CR:529131
CR Number:   529131
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   MRAgent/ASE
Status:   Closed
OS:   Generic
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 03 Jul 2008 Fixed
Description
For internal use only (new development):

Support migration to mra151.



CR:529153
CR Number:   529153
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Generic
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 03 Jul 2008 Fixed
5.6.05 10 Jun 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: Replication definition

can not be automatically created for a table with

a column containing 'sysname' datatype.



CR:529242
CR Number:   529242
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Generic
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 03 Jul 2008 Fixed
5.6.06 13 Jun 2008 Fixed
Description
ORACLE ONLY: The replication agent needs to have

the ability to read redo logs that are mirrored

and also remain replicating if it cannot connect

to ASM when attempting to refresh log devices.



CR:529326
CR Number:   529326
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   MRAgent/ASE
Status:   Closed
OS:   Generic
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 09 Jun 2008 Fixed
5.6.06 11 Jun 2008 Fixed
Description
ASE ONLY:

pdb_setreptable can not

recognize tables with long

names having '_' and '%'.

The length of table name cannot

exceed 255.



CR:529367
CR Number:   529367
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   15.0.0.5514P7b-ONE_OFF
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.15 10 Jun 2008 Fixed
5.6.05 10 Jun 2008 Fixed
5.7.00 03 Jul 2008 Fixed
Description
ORACLE ONLY: The Replication Agent stops

replicating due to an error. The error log

displays an error similar to:

"ChainedOperationException: Could not set header

to operation... because the chained operation

header.... is already set."

The error is caused by a failure to handle a

rollback operation applied to one log operation

of a chained operation.



CR:529380
CR Number:   529380
Product Name:   RepConnector
Product Component:   Run-time Engine
Status:   Closed
OS:   Generic
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
18 Mar 2009 Fixed
18 Mar 2009 Fixed
Description
RepConnector: some control characters in character data can cause an error: An exception while operating the statement.

java.lang.ArrayIndexOutOfBoundsException: Array index out of range: 0
Workaround Description
 Avoid replicating columns with control characters.



CR:529413
CR Number:   529413
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   15.0.0.5500
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.17 07 Oct 2008 Fixed
5.7.01 20 Oct 2008 Fixed
5.8.00 28 Oct 2008 Fixed
19 Sep 2008 Fixed
Description
ORACLE ONLY: "IndexOutOfBoundsException: Index: 6,

Size: 6" occurred with primary Oracle multi-block

undo enabled.



CR:529738
CR Number:   529738
Product Name:   Repository
Product Component:   Repository
Status:   Closed
OS:   Windows XP
Original Version:   tyresias
Fixed Version Build Resolution Date Closure Code (If Appropriate)
17 Jun 2008 Fixed
Description
Seems there are added additional and wrong informations in the configuration dialog. Members and version are inconsitant.



CR:529741
CR Number:   529741
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   tyresias
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Add a frozen document to a repository configuration.

Update consolidation adds the latest frozen version of the document in addition to the document version you added first as a configuration member.



CR:529907
CR Number:   529907
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   MRAgent/ASE
Status:   Closed
OS:   Microsoft Windows NT
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 03 Jul 2008 Fixed
5.6.06 13 Jun 2008 Fixed
Description
ASE Only:(windows)

pdb_date can not return

the correct month infomation

if OS regional is Chinese.
Workaround Description
 set OS regional to English and restart RA.



CR:529921
CR Number:   529921
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   NA
Original Version:   5.7.00
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.7.00 16 Jul 2008 Fixed
5.6.07 16 Jul 2008 Fixed
5.5.17 16 Jul 2008 Fixed
Description
ORACLE ONLY: NullPointerException will be

thrown when replicating nested UDD type.



CR:529922
CR Number:   529922
Product Name:   Sybase Replication Server
Product Component:   rsm server
Status:   Closed
OS:   Solaris
Original Version:   15.0.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
28 Aug 2009 Presently Not Targeted For Any Future Release Of This Product
Description
Some signs cannot be included in the password of RMServies.
Workaround Description
 do not use following signes. @ # " ` & ! % ' ~ | [ ] { } + * < > ? ,



CR:529924
CR Number:   529924
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/MsSQL
Status:   Closed
OS:   Generic
Original Version:   15.1.0.5602
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.05 10 Jun 2008 Fixed
5.7.00 03 Jul 2008 Fixed
Description
MICROSOFT SQL SERVER ONLY: Replication Agent fails

to replicate commands whose log record "Flag Bits"

are set to value 3600.
Workaround Description
 1) Log into RSSD and execute rs_zeroltm

2) Log into RA and execute "ra_locator zero"

3) Restart RA

4) Resume



CR:530598
CR Number:   530598
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   Solaris
Original Version:   15.0.0.5514P7b-ONE_OFF
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.5.15 10 Jun 2008 Fixed
5.6.05 10 Jun 2008 Fixed
5.7.00 03 Jul 2008 Fixed
Description
ORACLE ONLY: The Replication Agent sends a

rollback record to Replication Server that

incorrectly removes the begin transaction record,

causing Replication Server to fail with error:

"#9022 DIST Cannot deliver a command since no

transaction is open".



CR:530692
CR Number:   530692
Product Name:   Sybase Replication Server
Product Component:   RSMJavaPlugin
Status:   Closed
OS:   Generic
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
23 Oct 2009 Fixed
Description
Replication Manager online help may not display when running in a Chinese environment (set LANG=zh_CN.UTF8 or zh_CN.gbk or zh_CN.gb18030 and so on).
Workaround Description
 Add $SYBASE/RMP-15_1/help/rmzh.jar to the Replication Manager plugin.



CR:530706
CR Number:   530706
Product Name:   Sybase Replication Agents for Unix and Windows
Product Component:   RepAgent/Oracle
Status:   Closed
OS:   HP-UX
Original Version:   15.1.0.5603P1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
5.6.07 01 Jul 2008 Fixed
5.5.17 01 Jul 2008 Fixed
5.7.00 09 Jul 2008 Fixed
Description
ORACLE ONLY: When altering a table to rename the

table, or to add or delete columns, a

NullPointerException occurs.



CR:530800
CR Number:   530800
Product Name:   Sybase Replication Server
Product Component:   InstallShield
Status:   Closed
OS:   Generic
Original Version:   15.1
Fixed Version Build Resolution Date Closure Code (If Appropriate)
20 Sep 2010 Presently Not Targeted For Any Future Release Of This Product
Description
If the user chooses an installation type of 'Typical', 'Full' or

'Custom' and then decides to navigate backwards to choose a different

installation type, the component subset is not properly changed to match

the installation type.
Workaround Description
 Navigate back one panel further to where the user specifies the

installation directory. When the user then navigates forward to chose a

different installation type, the proper component subset is displayed.



CR:530820
CR Number:   530820
Product Name:   Repository
Product Component:   Repository
Status:   Open
OS:   all
Original Version:   tyresias
Fixed Version Build Resolution Date Closure Code (If Appropriate)
Description
Track user modifications at the model artifact attribute level



Customer's description:



Currently, PD keeps track of the changes we make at the object level and automatically places check marks next to the updates that we have initiated when consolidating with the repository. However, if there are multiple changes to the same object, PD shows all the changes and we have to select which attribute changes that we have generated. We need PD to keep track of the changes down to the attribute level and automatically check only those changes at the attribute level that we have initiated. We realize that this can be done by manually modifying the check boxes at the attribute level; however, when you have a team of 8 people working on the same model and updating the same requirements, (modifications from a review perspective, modification from a consistency perspective and modifications from a content perspective), the number of modifcations is great and the time that it takes to step through each individual attribute is extensive. Fixing this would greatly reduce people clobbering eachother's work.





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

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。
+-------------------------------------华丽的分割线-------------------------------------------------------------------------