As of SP 1, this group includes all the system parameters related to the generation of thread dump files that are generated by the following triggers in a running instance of the SAP CC Core Server system:

• A reached scheduling period
• An exceeded threshold relating to CPU time
• An exceeded threshold relating to the number of written output items
• An exceeded threshold relating to the number of rating contexts that are used
• An exceeded threshold relating to the execution time of SQL queries
• A timeout of a given charging request
• An unsupported exception which occurred

The thread dump files facilitate your technical operations by providing advanced supportablity tools. Your SAP Support Team may ask you to configure these settings. See the SAP CC Operations Guide.

Every trigger associated to a threshold can be configured using a dedicated system parameter, in order to fit specific needs. In addition to these configuration parameters, it is also possible to configure:

• The directory that is used by each instance so store the dump files whose size are not limited which thus implies a systematic ZIP compression
• The frequency of the dump files generation
• The retention period for the generated dump files, that is used to determine which dump file must be removed from the storage location automatically

Every dump file contains information related to the execution context of a given thread, formatted using an XML representation. Depending on the trigger that is responsible for the creation of the dump file, this information may contain the following elements:

• Number of logic calls, start time and duration of the current operation and associated result
• Number of incoming requests and queue status
• ID, source, read time, timeout status and internal status of each incoming request
• SQL queries history (start time, duration and result set status)
• SQL queries commit information (start time, duration)
• List of memory-impacted subscriber accounts, including the following information:
  
  • ID of the subscriber account
  • Number of counters, contracts, mapping tables, range tables
  • Type of performed operation (creation, modification, or deletion)
  • List of charging sessions (ID and performed action)
• List of memory-impacted charging contracts, including the following information:
  
  • ID of the charging contract
  • Type of the charging contract (root or linked)
  • Number of counters associated to this contract
  • Number of allowances associated to this contract
  • Type of performed operation (creation, modification, or deletion)
• List of memory-impacted subscriber mapping and range tables, including the following information:
  
  • ID of the table
  • Type of performed operation (creation, modification, or deletion)
• Additional information in case the memory impact is a modification:
  
  • Number of created, updated or deleted counters
  • Information about notifications (number of notifications with start time and duration)
  • Information about renew reservations notifications (number of received renew reservation notifications with receipt time and duration)
  • Information about spending statuses (number of sent spending statuses with sending start time and duration)
  • Information about the solicitation of the session database, if the Dual Database feature is enabled
  • Information about the used file writers (name, writing start time and duration, list of created items)