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:
For example, any browser or e-mail integration features and the infrastructure will stop working (see below). If a common client machine policy or a common gateway policy is affected, this will affect all client machines or all gateways respectively.
In particular, triggers will not activate. It may also cause e-mail and Web applications to be disabled, depending on how the Infrastructure Failure setting is configured (see below). The position of the associated user or group within the user hierarchy is also important because any child policies will also be adversely affected.
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
wgninfra -exec wigan/infrastruct/policy/PolicySetup PolicyCheck
Note: These commands are case-sensitive.
Copyright © 2014 CA.
All rights reserved.
|
|