Re: ER: send queue grows

The bulk of the stuff in the queue are the data changes for the transaction. Prior to 9.3, the bulk was stored in partition blobs within the stable queue space. With 9.3 this was moved to a smartblob space. smartblobs are reclaimed by the smartblob space when the smartblob is deleted. Partition blobs space is not reclaimed by the table space when they are freed. "Ph. Chantry" <nospam@nomail.com> wrote in message news:<baknm1$r1s$1@news-reader12.wanadoo.fr>... > Hi all. > > We have 3 servers using ER: > - Server A, primary, IDS 9.21.UC4,Linux > - Server B1, target, IDS 9.21.UC4, Linux > - Server B2, target, IDS 9.30.FC3, Solaris 8 > > The 3 replication servers have been created with the send and receive queues > in a dbspace called "physdbs". On each server, this dbspace is only used by > the replication queues. > > Every thing seems to be OK (transactions are applied on both target > servers), but we observe that the "physdbs" dbspaces continuously fills on > server A and on server B1. The dbspace does not fill on server B2. > > Could you tell me what happens to servers A and B1 ? A known problem with ER > 9.21.UC4 ? Do I Need to purge the queues myself on these servers ? The only > way I have found to empty the physdbs is to "cdr delete server"... > > Note that we have defined two separate sets of replicates: one for A-B1 and > one for A-B2. > > Thank you for your help, > Philippe