Data Replication issue for R/3 on i5

Question

QUESTION:
1) Do we need the data in following 2 files to be replicated when the production operation runs on
Stand-by system?
DBSTATIDB4 Index Sizes in the Database (statistical data)
DBSTATTDB4 Table Sizes in the Database (statistical data)
2) If we don't need data in those 2 files when production operation is underway on Stand-by,
please let us know any considerations if you have.
BACKGROUND INFO:
Although our customer has two R/3 system on i5 configured as a production and a stand-by system
and replicate R/3 production data to stand-by system using data replication tool called MIMIX,
sometimes we encounter a problem with the data of following files are out of synchronization.
Files cannot be replicated:
DBSTATIDB4     F@Index Sizes in the Database (statistical data)
DBSTATTDB4     F@Table Sizes in the Database (statistical data)
The reason for that is  because of the new DB function called fast-delete since V5R3.
This problem happens due to the fact that this function execute ENDJRN/STRJRN and it makes
problem within MIMIX replication operation.
In order to avoid this problem, we'd like to make sure that it's possible to eliminate these files
out of synchronization and need more information for these files.

Answer 1

Hello Yuhko,
first of all thank you very much, that you are the first user/customer, that is using this new and great forum !!!
We will move lot's of further customers into this forum soon.
Fortunately, yes you can ignore these 2 tables if you like - they are not really interesting for the healthy of your SAP system. But, are you really on the latest PTF Levels of V5R3 - because I know this error and it should be fixed in the meantime - perhaps you need a newer MIMIX version as well - you should at least check.
Then you could configure to run this "crazy" job not twice a day, but once a week only - that makes even your system faster ... This could be done in ST03 in the collector configuration. It is RSORATDB or RSDB_TDB in TCOLL - depending on your SAP release.
But again:
If you want to exclude these 2 tables from replication you are fine as well - but I would make this job even more rarely for better performance.
Regards