Previous Topic: Triggers Are Not Firing As ExpectedNext Topic: Best Practices


A Policy is Not Working or Cannot Be Edited

Symptom:

If a policy stops working or cannot be be edited, it may be corrupt. When you try to edit a corrupt policy, an error message indicates a failure to load a policy from the database.

A corrupt policy can manifest itself in various ways:

Solution:

The Infrastructure Failure setting controls how CA DataMinder responds when the infrastructure fails to start. Find this setting in the user policy System Settings, Initialization folder. For example, you specify that only CA DataMinder is disabled, or you can also disable all browser and e-mail applications integrated into CA DataMinder (this prevents users running their browser or e-mail applications until the infrastructure restarts).

To overcome a corrupt policy

  1. First, you must identify the .BLB file containing the corrupt policy. To identify the corrupt policy, run:
    wgninfra -exec wigan/infrastruct/policy/PolicySetup PolicyCheck
    

    Note: These commands are case-sensitive.

  2. This command forces CA DataMinder to examine each policy file on the CMS. If a corrupt policy is detected, an identifying entry is written to the latest System log.
  3. When you have identified the corrupt policy and the associated file, please contact CA Technical Support for further advice: http://ca.com/support.