delete filespaces on primary that have not been on on the replica? I have seen a lot of that going on, you get stale filespaces on the replica with the metadata but due to deduplication the impact is largest on the database. If this is not it I would run the IBM database reorg perl script, you might be able to do a few reduce max commands that will solve the problem.
On Sat, Feb 2, 2019 at 7:55 PM Sasa Drnjevic <sasa.drnje...@srce.hr> wrote: > Hi, > are you sure that all of the policies are the same? > > All retention periods are the same? > > And are you sure that expiration process regularly runs on the target > server? Chec for errors in the activity log... > > Rgds, > > -- > Sasa Drnjevic > www.srce.unizg.hr/en/ > > > > > On 2019-02-02 15:10, Saravanan Palanisamy wrote: > > Hello Experts, > > > > What cases repl server would have more db usage than primary server. > Here I go with one setup in similar situation. > > Primary server db usage - 67% (out of 6TB) > > Replication Server db usage - 96% (out of 6TB) > > > > repli server uses only for replication purpose, no there native backups > configured over there. > > > > suggestion pl. > > > > - Saravanan > > >
