This problem can occur with non-Sybase primary databases. Replication Agents have configuration parameters that must be set to request that the native date or time datatypes in the primary database be converted to Sybase datetime formats for replication. If this conversion is not requested, the default date format returned from the primary database is used, which may not provide a time value. For example, the Oracle default date display format is DD-MON-YY. If the Replication Agent is not configured to convert this display to a format that includes time (for example, CCYY-MM-DD hh.mm.ss.mmm), then the time value will be all zeroes whenever the date is replicated.
See the Replication Agent for DB2 UDB for OS/390 User’s and Troubleshooting Guide for more information about the Date_in_char parameter. For more information about the pdb_convert_datetime parameter, see the Sybase Replication Agent Administration Guide.
When using a Replication Server datatype for a non-Sybase data server, you must ensure that the date datatype specified in a replication definition map to clause includes a time value.
The Sybase Replication Agent pdb_convert_datetime configuration parameter
must be set before a table or procedure is
marked for replication in a DB2 UDB, Informix, Microsoft SQL Server,
or Oracle database. The Replication Agent uses that parameter value
to determine how to configure the translation of the data from that
specific table or procedure.
