Known Issues for Microsoft SQL Server

Cannot use a database replication definition and database subscription with dsi_alt_writetext set to dcany.

Workaround: Use table replication definition and table subscriptions.

RAM stops scanning with NoSuchElementException error when processing rollback.

Workaround: None.

RAM stops scanning with VirtualFileNotFoundException error when RAM reaches the end of the virtual file and moves to the next virtual file.

Workaround: Resume Replication Agent.

Cannot replicate some rows containing image data.

RAM loses part of LOB data when replicating an image column, thus some rows cannot be replicated.

Workaround: None.

The physical machine's license capacity setting cannot be recognized on Solaris virtual machine.

The SYBASE_SAM_CAPACITY licensing capacity setting is not intended for 
this system. This machine partition or virtual machine does not appear 
to be part of the machine from which the SYBASE_SAM_CAPACITY value was 
obtained.

Workaround: None. This will be fixed in version 2.2.0.9 of the sysamcap utility. Check http://www.sybase.com/sysam Web site for an updated sysamcap utility or contact Sybase Technical Support.

pdb_xlog init fails when Microsoft SQL Server 2008 is upgraded to the developer version.

pdb_xlog init fails when a SQL Server instance is upgraded from Microsoft SQL Server 2008 standard version to the developer version. This is a limitation of Microsoft SQL Server—during SQL Server upgrading, the “Agent XPs” component is turned off, which prevents pdb_xlog init from succeeding.

Incorrect LTL generated.

Incorrect LTL may be generated in a partition schema for an update transaction that affects the primary-key column of a table referenced by the cascading foreign-key column of another table. For example, two tables are created, one with a primary-key column referenced by the foreign-key column of the other table. This causes updates to cascade to the primary-key column of the first table:

create table table1 (id int constraint PK_1 PRIMARY KEY 
CLUSTERED WITH FILLFACTOR=90 on myRangePS1(id), 
value1 varchar(8) null); 

create table table2 (id int constraint FK_1 FOREIGN KEY 
REFERENCES table1(id) ON UPDATE CASCADE, 
value1 varchar(8) null); 

Data is inserted into both tables:

insert into table1 values(3,'aaa'); 
insert into table2 values(3,'aaa');

The primary-key column of the first table is subsequently updated:

update table1 set id =4

The resulting update transaction results in the following logged commands:

LOP_BEGIN_XACT NULL 
LOP_BEGIN_UPDATE NULL 
LOP_DELETE_ROWS dbo.table1.PK_1 
LOP_INSERT_ROWS dbo.table1.PK_1 
LOP_DELETE_ROWS dbo.table2 
LOP_INSERT_ROWS dbo.table2 
LOP_END_UPDATE NULL 
LOP_COMMIT_XACT NULL

The LTL generated for this transaction does not identify that the delete operations are grouped with insert operations as part of an overall update operation. Consequently, Replication Server is suspended.

Workaround: Drop the foreign key constraint in your replicate database. This will not result in data loss because both the original delete and the cascade delete commands are sent to the replicate database.

An error occurs when applying service patch.

When you run the SQL Server 2008 service patch, the Replication Agent system tables sys.sp_SybSetLogforLOBCol and sys.sp_SybSetLogforReplTable are deleted from the resource database, triggering error 29537:

MSP Error: 29537 SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client]
[SQL Server]Could not find stored procedure 'sys.sp_SybSetLogforLOBCol'.. To continue, correct the
problem, and then run SQL Server Setup again.

Workaround: Before you apply the service patch, disable the database triggers that Replication Agent created:

1. Log in to the primary database.
2. Disable the automark trigger if it is enabled. For example:

   DISABLE TRIGGER ra_createtable_trig_ ON DATABASE

   where ra_createtable_trig_ is the automark trigger created by Replication Agent.

3. Disable the data definition language (DDL) trigger. For example:

   DISABLE TRIGGER ra_ddl_trig_ ON DATABASE

   where ra_ddl_trig_ is the DDL trigger created by Replication Agent.

Microsoft SQL Server 2008 log error prevents LTL processing.

The partial update of varchar (max) or varbinary (max) with off-row storage cannot be replicated correctly due to a Microsoft SQL Server 2008 logging error. The LTL does not process the partial update.

Workaround: None.

Replication Agent instance fails to start after upgrading a version 15.0 on a UNIX platform to a Windows platform.

When you upgrade a Replication Agent 15.0 instance to version 15.1 or later by migrating from a non-Microsoft Windows platform to a Microsoft Windows platform, the instance may encounter this error during start up:

Error setting logging directory for instance XXX
because: <Log directory <YYY> does not exist>.

Workaround: After upgrading the Replication Agent instance, edit its configuration file to modify the value of the log_directory parameter to point to the correct path of the Replication Agent instance log directory. By default, the log directory resides under the Replication Agent instance directory.

For example, change this line:

log_directory=/opt/Sybase/RAX-15_0/myra/log

to

log_directory=c\:\\sybase\\RAX-15_5\\myra\\log