Rec/client parameter & Performance Impact
We have been asked by our audit team to set the parameter Rec/client=300 (our production client) in our production system.
But when we read few forums & notes, we feel that setting this parameter Rec/client=300 will definetly impact the performance.
So before setting this parameters we need to evaluate the performance impact in our ECC 6.0 system by setting this parameter, can anyone help us to evaluate the performace impact of this parameter settings in our below system
- ECC 6.0 / oracle 10g / HPUX - 64 bit / 3500 users / 2.5 terabyte data
Normally only customizing tables should have the logging flag. You can verify it in SE13 -> <table> -> Log data changes.
To list all tables with logging on, you can use this select statement:
SQL> select tabname, protokoll from sapr3.dd09l where protokoll = 'X';
As long as only so called customizing tables are logged, you should be fine. If you have some heavy traffic Z* tables, then two things might happen:
- performance might suffer
- the logging table DBTABLOG will explode
So please make sure only the necessary tables are logged and if possible test on the QAS system, if the logging leads to performance problems.