Hi,
I have a problem with the replication.

In an industrial application I have to copy the data from the principal
database to the historical database that deals him with to visualize
through a dedicated software the oldest data leaving in the first solo
the least necessary for the industrial application.

The first server has alias launchings and link that identifies the
various database necessary to the application. This results to be
replied on a secondary server that works as on-line "backup" of the data
of the principal.

When I perform the copy:

(Historical database - first server)
INSERT INTO S_DMIXER_BY3
SELECT * FROM "DATI_MCS". S_DMIXER_BY3
WHERE PROG_STORICO>=1 AND PROG_STORICO <=200

they are connected to the Historical database to allow the queue of
replication to work and, in effects, the system perfectly works.
Finished the query of "INSERT INTO..." (the copy) the software changes
alias his aiming at the principal database to perform the cancellation
of the copied records.

(Principal database - first server)
DELETE FROM S_DMIXER_BY3
WHERE PROG_STORICO>=1 AND PROG_STORICO <=200

I have realized that the queue of replication is not loaded during the
phase of cancellation (the file server is still elaborating the queue of
replication of the Historical database: "INSERT INTO.... ")

How come does this happen, considering that we have 2 distinct alias on
the same server both with function of replication on the secondary file
server?

What can I do for resolving the problem?