Posted: 24 Nov 2016 6:29 EST Last activity: 4 Oct 2018 13:54 EDT
Unable to delete a rule.
I want to lock a ruleset 01-01-03 for QA deployment, when i am trying to lock a ruleset, in that one rule is checked out, when i opened the rule. It is saying. "There has been issue;Please consult your system administrator"
Can you please let me know, in this senario, how to checkout the rule.
***Updated by moderator: Lochan to add Categories***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
This issue we have faced few times. I'm not sure about the root cause of this but I've noticed I can access the rule when I use a different node in same environment. So it might be some node specific cache issue. As an escape route you can either delete this rule using an admin activity or executing a delete query in database directly if you have the permission.
@Prudhvi_N, We cannot create Connect-SQL on internal tables.
@shwetha, Can you please let us know if you have tried to know who checked out the particular record and ask them to check out or discard the rule.
If you can't find them, I'm afraid you'll have to delete the rule entry in pr4_rule and also delete the same from the table pwbv4_rule_locking. All checked out rules are present in the user specific ruleset. The ruleset of the checked out rule will be operator ID. Using the above statement we can find the checked out rule and delete it.
Just wondering, did Shweta mention that the corrupted rule is a property? (If she mentioned that the rule is a property I'm pretty sure there is some problem with PDN loading comments in my login). Coz, only property rules will be saved under pr4_rule_property table. As the size of properties, flows etc are large, for faster query execution we save some rule types in separate tables rather than pr4_rule. If the corrupted rule is a property, then yes, we have to delete it from pr4_rule_property table.
Now, coming to the connect-SQL rule, They are meant for external database tables. Yes, we can create the connector directly using the create menu on internal tables and we can execute them. But that is not a recommended approach. If you use connector and metadata wizard to create the connector, it will not allow you to create the connector on tables which contain keys starting with px,py,pz.
@Shweta: This issue might be resolved for you. But please find the solution below for future reference.
The above problem usually appear when we delete /delete checkout one rule, but accidental pressing continues <-- (Backspace button), server slowness or some other technical issue the rule got corrupted.
1- Create an Activity
2- Open the object (obj-open) , pass the class name and rule name
We had similar issue as some of the rules got corrupted. Since we wanted to use the same name as the rule was being referred in multiple places, we had to delete and recreate the rule. We wrote a simple activity with following steps to delete the rule.
1. Open the object (obj-open) , pass the rule name and class name of the rule instance type for example to delete a data flow open class Rules-Decision-DDF