Learn how to detect and resolve system transaction execution failures.
truncate table and certain supported DDL commands are not logged, although they can be replicated to standby and replicate databases. See the Adaptive Server Enterprise Reference Manual for information about each DDL command.
Replication Server copies these commands as system transactions, in which Replication Server “sandwiches” the truncate table or similar command between two complete transactions. Execution of the first transaction is recorded in the replicate database in the secondary_qid column of the rs_lastcommit table and in the origin_qid column of that table. If Replication Server records the second transaction, the system transaction has completed, and Replication Server clears the secondary_qid column.
5152 DSI_SYSTRAN_SHUTDOWN,"There is a system transaction whose state is not known. DSI will be shutdown."
resume connection to data_server.database skip transaction
resume connection to data_server.database execute transaction
You must include the skip transaction or execute transaction clause with resume connection. Otherwise, Replication Server does not reset the secondary_qid correctly, and the error message reappears.