Skip to Content
avatar image
Former Member

Rec/client parameter & Performance Impact

Hi all,

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

Thanks

Senthil

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

4 Answers

  • Best Answer
    avatar image
    Former Member
    Jul 21, 2008 at 12:40 PM

    Hello

    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.

    Best regards

    Michael

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jul 21, 2008 at 04:28 AM

    Hi Senthil,

    Logging table changes for Customizing is activated via the profile parameters rec/client.

    The default value for this parameter in NW4S is OFF. The decision of whether activate this parameter or not depends on your security requirements. Please notice this parameter turns on/off the logging for client-dependent tables, which also needs to be specified in SE11.

    You can read more about this parameter in note 139418, Logging user actions.

    Also refer to SAP note 608835 for further information about the impact of activating the table logging.

    Hope it helps.

    Regards,

    Rupali

    Edited by: Rupali Goyal on Jul 21, 2008 6:33 AM

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 16, 2008 at 02:26 AM

    Having read this posting.

    since you have 2.5 TB database size.

    Do you archive your data or data archiving is implemented or not.

    Audit team look at system from different angle and tech guys differently.

    I would suggest if you have plans to activate recording of client,I would suggest implement the archiving for DBTABLOG.

    Else check the logging on for specific tables ?

    Other way round ,You can check with the audit team if they require recording on for certain tables.

    hope it helps,

    Thanks

    Amit

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Aug 18, 2008 at 01:58 PM

    Hello Senthil,

    we run the same environment (HPUX 11, ORACLE 10g) with rec/client enabled. Same thing with the audit team here. ;-(

    In our SAP use cases we found no performance impact due to rec/client parameter. But this depends on the tables to be logged. The default is to log around 28.000 tables (See DD09L-PROTOKOLL).

    These tables are customizing tables and usually under no frequent changes.

    Only if you have a process which changes a lot of customizing (i.e. generating shifts in HCM in table T552A) then you run into higher cpu and db time.

    Kind regards, Hinrich

    Add comment
    10|10000 characters needed characters exceeded