Known Issues

When a table in a comparison has more than two billion rows, the create compareset command with map all fails.

Workaround: Execute create compareset without the map all parameter to compare all compareset columns successfully.

SAP Adaptive Server (SAP ASE) database connections with secure socket layer (SSL) configuration hangs while connecting to non SSL-enabled SAP Adaptive Servers.

create connection ase_ssl
      set type      ASE
  and set agent     localagent
  and set host      soka2
  and set port      5000
  and set database  dadb
  and set user      dauser
  and set password  dauser
  with properties
     set SYBSOCKET_FACTORY 'com.sybase.da.jdbc.AseSslSocketFactory'
  go

test connection ase_ssl 
go

Workaround: Restart DA server and correct the connection settings before reconnecting to the SAP ASE instance.

In an IBM DB2 UDB 9.5 in a homogeneous comparison environment, DA cannot obtain column metadata for the DECFLOAT datatype.

create compareset example1
    with source pri_udb95 A_USER EXAMPLE1 s
         target rep_udb95 A_USER EXAMPLE1 t
    map all
  go

show compareset example1 columns
  go
   TYPE CONNECTION OWNER  TABLE    MAPID COLUMN  PKEY
   ---- ---------- ------ -------- ----- ------- ----
   S    pri_udb95  A_USER EXAMPLE1 1     A_LABEL N
   T    rep_udb95  A_USER EXAMPLE1 1     A_LABEL N
   S    pri_udb95  A_USER EXAMPLE1 2     ID      Y
   T    rep_udb95  A_USER EXAMPLE1 2     ID      Y

create compareset example1
    with source pri_udb95 A_USER EXAMPLE1 s
         target rep_udb95 A_USER EXAMPLE1 t
    map s.ID         = t.ID set key=true
    and s.A_LABEL    = t.A_LABEL
    and s.AN_AVERAGE = t.AN_AVERAGE
  go

create job demo1 add comparison example1 set compareset example1
  go

run job demo1
  go

monitor job demo1
  go

 COMPARISON PART STATUS  SUBMIT TIME         END TIME            RUN PROGRESS NEXT RETRY ERROR
   ---------- ---- ------- ------------------- ------------------- --- -------- ---------- -----------------------------------------
   c          0    ABORTED 2013-08-16 09:36:22 2013-08-16 09:36:30 1   100%                No metadata for source column: AN_AVERAGE

create connection command for SAP HANA database requires an unnecessary database parameter.

DA connection configuration objects require a database parameter to use with the JDBC driver for SAP Adaptive Server, Oracle, and SAP IQ databases. The SAP HANA database JDBC driver does not require this parameter.

However, if you create the SAP HANA database connection without a database parameter, DA will not create the connection. DA assumes all connection objects require a database parameter.

Workaround: When you create an SAP HANA database connection, set the database parameter to a placeholder value.

create connection myHDBconn1
       set type     = HANADB
   and set agent    = myagent
   and set host     = "10.0.14.119"
   and set port     = 30315
   and set database = placeholder
   and set user     = HAUSER
   and set password = Pa55word
  go

TIMESTAMP reconciliation issue with Data Assurance (DA) in non-SAP Adaptive Server databases replication environment.

DA does not compare the second-fractions of TIMESTAMP values beyond the first three, of a total of nine digits.

For example, 2009-01-16 18:55:33.213000000 is considered equal to 2009-01-16 18:55:33.213666666 when compared by DA. Additionally, DA reconciles all nine digits, which leads to an SAP Replication Server error, when you are replicating TIMESTAMP columns in non-SAP Adaptive Server databases.

Workaround: None.

The SAP HANA database alphanum datatype is not supported in heterogeneous comparisons with DA.

For example, in an Oracle-to-SAP HANA database heterogeneous comparison environment, you cannot compare Oracle varchar2 datatype with the SAP HANA database alphanum datatype.

• When you insert 202 into SAP HANA database alphanum, DA receives it as 0000000000000202.

• When insert you 202 into Oracle varchar2, DA receives it as 202.

This SAP HANA database alphanum datatype mapping issue causes comparison failure.

Workaround: Compare SAP HANA database alphanum datatypes only in SAP HANA to SAP HANA database comparisons.

The DA server license is not checked in after the JVM is terminated with Ctrl+C.

If the JVM for the DA server process fails or is terminated from the operating system, DA server cannot complete tasks it would normally perform before shutdown, such as checking in the license. DA server may also not check in the license if its JVM is terminated with Ctrl+C on a Windows machine.

Workaround: Stop DA server from isql with the SAP Replication Server shutdown command.

Uninstallation issues occur when SAP Replication Server DA Option is installed in the same directory as older Sybase products which used InstallShield.

If new Sybase products that use InstallAnywhere (like DA Option) are installed in the same directory as the older Sybase products which used InstalledShield, uninstalling one of the products may make the others unusable because some of the shared components are removed by the uninstaller.

For example, if DA is installed in the same directory as Replication Server 15.2 and Replication Manager (RM) plug-in 15.2, and the RM plug-in is uninstalled, the DA server cannot be started because the JRE on the /shared directory has been removed.

Starting DA server or agent on Windows 7 fails.

DA server or agent can not start properly on Windows 7 if you run the RUN_instance_32.bat or RUN_instance_64.bat script using the Run option.

Workaround: Use the Run as Administrator option instead of the Run option when running the start-up scripts.