RFC-Trace Reset - Parameter rdisp/TRACE_LOGGING?

[Private_Member_19084]

Hi experts,

I found an site which describes, that with the parameter rdisp/TRACE_LOGGING it can be controlled, that the following traces are reseted automatically.

- Work process traces dev_w*

- Dispatcher trace dev_disp

- Gateway trace dev_rd

- ICM trace dev_icm

- Message server trace dev_ms

My questions is, what about dev_rfc*?
Will they also be reseted with this parameter?

Thank you

[former_member188883 · Accepted solution]

Hi Christian,

As per SAP help link

Trace Logging (SAP Library - Tools for Monitoring the System)

Profile parameter rdisp/TRACE_LOGGING will activate trace for

• Work process traces dev_w*
• Dispatcher trace dev_disp
• Gateway trace dev_rd
• ICM trace dev_icm
• Message server trace dev_ms

If the trace file reaches that size, the content is written to a log file with the name of the trace file and the extension .old. The current trace file is then reset.The parameter rdisp/autothtime is used to define how often the trace file should be checked and, if necessary, reset.The default is 60 seconds.     

To activate RFC traces

You activate RFC traces in transaction SM59. You can use the authorization object S_RFC_ADM to control access to this transaction.Transaction SM50 allows you to display traces. You control access to traces with the authorization object S_ADMI_FCD (parameter PADM).

Refer SAP note 532918  (RFC Trace Generation)

Hope this helps.

Regards,

Deepak Kori

[Private_Member_19084 · Accepted solution]

Hello Deepak Kori,

this is exactly the same page I found on the internet, and therefore I did create this thread.

Because, I don't know, how can the RFC-Trace be limited automatically?

Also in the note there is no description about this.

Kind regards

[former_member188883 · Accepted solution]

Hi Christian,

Refer the SAP note shared above.

Regards,

Deepak Kori

[Private_Member_19084 · Accepted solution]

You are talking about this note 532918  ?

Because I can't find the solution in there.

Kind regards

[former_member188883 · Accepted solution]

Hi Christian,

Please refer SAP Note 573800 - Reasons for trace files increasing in size

How can I prevent trace files that are increasing in size from filling the hard disk and causing the system to shut down?
Answer (workaround):

6. Reset the trace files (as described as Section 1 of note 532918).

7. Set the "rdisp/TRACE_LOGGING = on, 10 m" profile parameter

• (10 m corresponds to a size of 10 megabytes)

8. If you do not want a trace to be propagated in your system, set the following profile parameter:

• gw/accept_remote_trace_level = 0 (as of Kernel 46D)
  Remark:
  The "rdisp/accept_remote_trace_level = 0" profile parameter prevents the trace from being propagated internally in the local host and does not affect external connections transmitted via the SAP gateway.

Hope this helps.

Regards,

Deepak Kori

[Private_Member_19084 · Accepted solution]

Thank you so much.

So it seems, as the same parameter is also controlling the dev_rfc* traces.

Kind regards

[former_member182657]

Hi Christian,

Please follow scn link

Hope this will help you.

Regards,

Gaurav

[Private_Member_19084]

Hello Gaurav,

I know this - this thread was also from me.

But my question is, how can I limit the size of RFC-Trace files?

Kind regards