Skip to Content
Information

This site will undergo a brief period of maintenance on Thursday, 23 April at 2:30 AM Central/1:00 PM IST. During a 30 minute window, site availability may be intermittent.

E-Bonding Runbook Data Cleanup

E-Bonding Runbook contains multiple BMC Remedy ARS Forms and database tables. This forms / tables can store large amounts of records after a while of use. This chapter describes the forms and tables that store log and transaction data.
 By default, E-Bonding Runbook does not contain cleanup mechanisms. It's recommended to implement such mechanisms for productive installations of E-Bonding Runbook.

BMC Remedy ARS Forms

The following BMC Remedy ARS Forms should be cleaned up in time intervals:

  • VIP:BGI:Log
  • VIP:BGI:KPIData
  • VIP:BGI:CORE:GenerateGUID
  • VIP:BGI:IM:ProcessingEventHistory
  • VIP:BGI:IM:ProcessingTicketStore
  • VIP:BGI:CM:ProcessingEventHistory
  • VIP:BGI:CM:ProcessingTicketStore

Customers can use Remedy Escalations or Archive Forms for the cleanups.

Database Tables

The following database tables should be cleaned up in time intervals:

  • EVENTS (obsolete from version 2.0 on)
  • MESSAGES
  • TRANSACTION

Customers can use specific DBMS functions for the cleanups (Stored Procedures, Trigger, etc.).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

VIPCON E-Bonding Run Book for BMC Atrium Orchestrator version 2.0