Deleting rule in MARS

How do you delete an inspection rule in MARS

Hi Lewis,
The inspection rules cannot be deleted. They can only be made inactive.
The original reasoning was that if you were doing some forensic investigation and a rule was no longer on the system then the database would be corrupt.
You are not the first person to ask for this and I believe Cisco is considering this feature request.
In the meantime, when you need to make a change to a rule just clone the original and then make the original inactive. In this way if you make a mistake you can make this rule inactive. You can then clone the original rule again and fine tune what you are trying to accomplish.
Hope this helps.
Paul

Similar Messages

Delete rule from logical to relational model

hello!
I use data modeler Version 3.1.0.700 and I have some problems with delete rule.
I have set delete rule in logical model on every relation (NO ACTION) but when i engineer it to relational there is everything randomized.
How do i change this to be as it is in logical model?
Thank you for your answer in advance!
Grega

as I explained in previous post "delete rule"in logical model is used in only one case:
the setting in logical model is used only when relationship will be transformed into optional foreign key with non mandatory FK columns.Settings in compare/copy options" tab are used to exclude some properties from compare and engineer process.
Philip

Delete rule not being generated in DDL

Hi,
I've only recently started using SQL Developer Data Modeler (coming from the Designer world), and it's been a good learning experience. There's a piece that I can't seem to figure out though, and it's related to the generation of DDL for foreign keys. In all my models (logical, relational, physical, I have the Delete Rule set to "Restrict". This isn't just the default preference I'm talking about, when I actually drill down to the properties of the FK, it says that the delete rule is restrict. However, when I generate the DDL, no delete rule is generated. The only option generated is NOT DEFERRABLE.
There are two issues with this:
1) The rule isn't going into the DB unless I manually alter the DDL, and
2) Every time I re-import the DB to generate ALTER statements, the comparison detects that the rule in the DB (NO ACTION) is different than the rule in the model (RESTRICT), so it deletes and re-generates the FK. However, it re-generates it still not having the delete rule set, so it doesn't fix the problem.
Is this a known bug, or is there some way of telling the program to generate the delete rule in DDL that I'm missing? I should add I'm using version 3.1.1.703.
Thanks in advance for your help.
Mike
Edited by: user10832262 on Apr 12, 2012 9:53 AM

I did some more research and I think I was completely misunderstanding Oracle's implementation of delete rules. Now I believe that Oracle implements the "RESTRICT" option in SQL Developer Data Modeler as "No Action", which is the default option, hence why no DDL option is generated. However, it would still be nice if Data Modeler could detect this fact when comparing two models. What I mean it, if comparing an Oracle DB to a model, treat Restrict and No Action as the same, and thus don't attempt to re-generate the DDL for this "difference". For now, I'll just change the action on my models to No Action, and this should resolve the issue.

How to set Delete Rule to SET NULL while designing relational model .

Dear All,
Am new to SQL Developer Data Modeler and was doing some relational and logical design using Data modeler and i want to generate DDL script, while doing i was struck up with this issue.
I have two table and tried to give Primary key and Foreign key relationship, in foreign key table i want to set the Delete rule has SET NULL, but it is not found. I have other three options like CASCADE, RESTRICT,NO ACTION. Whereas in logical design i can find SET NULL, NO ACTION and RESTRICT....
But the DDL script is getting generated based on Relational design , i want to set foreign key has SET NULL in delete rule how to accomplish that?
Please help me......
Thanks in Advance
Ramkumar.S

Hi Ramkumar,
If you unset the Mandatory property on the Foreign Key, you should then be able to set the Delete Rule to SET NULL.
David

Logical M:N Relation with Delete Rule:"NO ACTION" creates "CASCADE" FK

I think I've detected a bug in the generation of FK when we have"N: N" relations, give me idea that the delete rule that is defined in the relationship of logical model is ignored.
So I give you a small example to reproduce it:
I've a simple example of 2 entities:
Logical Model:
Entity_A(#id_a, desc)
Entity_B(#id_b, desc)
M:N Relation between Entity_A and Entity_B (REL_A_B) with Delete Rule: "NO ACTION".
When apply "Engineer to Relational Model" I've as result 3 tables:
Relational Model:
Entity_A(#id_a, desc)
Entity_B(#id_b, desc)
REL_A_B(#id_a, #id_b) but the generated foreign keys are defined using Delete rule "CASCADE".
Is not supposed to have been generated with delete rule "NOT ACTION"?
As result the generation of DDL scripts is creating FKs with the clause " ON DELETE CASCADE", which was not originally intended.
I try to change this value in logical model but I've seen not effect on result.
I hope I have helped!

Hi Ariel,
thanks for reporting the problem. I assume it's for Data Modeler 3.3.
I logged a bug for that.
Philip

Delete Rules between Logical Model and Relational Model are different

Relation Properties in Logical model has three Delete Rules: "RESTRICT", "NO_ACTION", "SET NULL".
1. "RESTRICT" and "NO_ACTION" are same
2. "CASCADE" is missing.
However, Foreign Key Properties in Physical model has three Delete Rules: "RESTRICT", "NO_ACTION", "CASCADE".
1. "RESTRICT" and "NO_ACTION" are same
2. "SET NULL" is missing in this case.
They are supposed to have "NO_ACTION or RESTRICT", "SET NULL", and "CASCADE".
Please fix this ASAP. It is really annoying in Engineering process. Modeler creates duplicate wrong relationships while it engineers.
Thanks.
Edited by: hayangae on Oct 9, 2012 1:01 PM
Edited by: hayangae on Apr 3, 2013 4:08 PM

Hi,
it seems you are not using the latest version 3.3. In earlier versions - delete rule set on relationship was used only in some cases to set delete rule on related foreign key. Now delete rule is transferred to FK as it's defined on relationship.
I assume you are using Oracle database - "Restrict" doesn't appear anymore for Oracle.
2. "SET NULL" is missing in this case.Most likely the foreign key is set as mandatory thus you cannot use "set null" as option.
Modeler creates duplicate wrong relationships while it engineers.Can you elaborate on that - example?
Philip

Delete rule not generated in DDL

Hello,
I am using SQL Developer Data Modeler (Version 3.1.1.703) and experience the following issue:
I have a table with a foreign key and a delete rule "SET NULL". However if I generate the DDL for "SQL Server 2005" then the rule is not there. Only if I change the rule to "CASCADE" then it is generated properly. Is that a bug or am I missing something?
Thanks in advance for your help,
Michael

Hi Philip,
when can we expect a fix for that since it is kind of an important function for us because without it we can't export a valid database structure.
Thanks in advance,
Michael

FK DELETE RULE problem when importing 8i SCHEMA on 10g

Hi everyone,
I´m having the following problem:
When importing a SCHEMA dump from an 8i database to a 10g one, some foreign key´s delete rule are changed from 'no action' to 'set null' automatically, even though the whole SCHEMA was imported.
Has anyone ever had the same problem?
Thanks a lot,
Bruno

I did some more research and I think I was completely misunderstanding Oracle's implementation of delete rules. Now I believe that Oracle implements the "RESTRICT" option in SQL Developer Data Modeler as "No Action", which is the default option, hence why no DDL option is generated. However, it would still be nice if Data Modeler could detect this fact when comparing two models. What I mean it, if comparing an Oracle DB to a model, treat Restrict and No Action as the same, and thus don't attempt to re-generate the DDL for this "difference". For now, I'll just change the action on my models to No Action, and this should resolve the issue.

Want to remove cascade delete rule alone , but not referential functionalty

Hi All,
i need a help. i have a table (B) in production which is having a column with on delete cascade rule & it is a foreign key.whenever i delete a row from table A , the corresponding referential row in table B will be deleted. but,what i need here is, i want to remove cascade delete rule alone , but not the referential functionality(Foreign key functionality).
Can any one please guide me......Thanks in Advance.

Hi,
You need to recreate(drop and create) foreign key without "on delete cascade" clause.

Compare/Merge Models does not recognise changes to FK delete rules

Hi,
I think I have found some functional gap in the data modeler (Version 3.0.0.665) comparison tool. I'd be glad to learn that I am wrong, but otherwise please consider this for a future version.
Start with model "A"
Model "B" = "A" + changed delete rules for some foreign keys, e.g. from CASCADE to RESTRICT.
If I now compare A and B via Tools > Compare/Merge models, the ddl preview is empty.
I only realised that because I explicitly tried to change FK delete rules in my db. I guess that if you do delete rule changes on the side of many other changes, you might easily overlook that the according constraint changes are missing in the ddl.
Best regards,
Martin

Hi Martin,
thanks for feedback. I logged bug on that.
Philip

Delete Rule for ActiveSync

Hi all,
idm version SP4
I have a configured MySQL resource with ActiveSync.
My table has a field 'type' that says if it's a delete or not.
I want configure a delete rule depending value's field 'type', but I don't Know do it.
How works delete rule?
Can you help me, please?
Thanks
Kiernan

Ignore my previous post, I had an unnecessary table in the join. Let's try again.
Query:
select
   ou.name as constraint_owner,
   oc.name as constraint_name,
   decode (c.refact, 1, 'CASCADE', 2, 'SET NULL', 'NO ACTION') as delete_rule
from
   sys.con$ oc, sys.user$ ou,
   sys.cdef$ c
where
   oc.owner# = ou.user#
   and oc.con# = c.con#
   and c.type# = 4 ;Example:
SQL> select
2     ou.name as constraint_owner,
3     oc.name as constraint_name,
4     decode (c.refact, 1, 'CASCADE', 2, 'SET NULL', 'NO ACTION') as delete_rule
5 from
6     sys.con$ oc, sys.user$ ou,
7     sys.cdef$ c
8 where
9     oc.owner# = ou.user#
10     and oc.con# = c.con#
11     and c.type# = 4
12     and ou.name = 'SPC_TBL_OWNER'
13     and oc.name = 'HUMID_SPOT_HISTORY_FK1' ;
CONSTRAINT_OWNER               CONSTRAINT_NAME                DELETE_RU
SPC_TBL_OWNER                  HUMID_SPOT_HISTORY_FK1         SET NULL

How do you handle update and delete rules for fact tables?

I have a fact table with a composite key of 5 columns. Two of the columns are FKs to the date dimension. I was setting the delete/update rules for the FK relationship in SSMS and it had a problem with me creating cascade action on the FKs that connected
to the date dimension.
What is the proper way to set up FK relationships in fact tables with SSMS when you have composite keys as most fact tables do?

Yeah I understand all that. What I'm trying to do is to protect my database from RI violations that occur by production support people blowing away stuff in a dimension table but forgetting to blow away related records in the fact table. I want those fact
records deleted automatically so we don't have orphan records which was a real issue at a previous engagement. Production support is usually just people that know SQL and some relational modeling. It's not too likely they will understand the details of dimensional
modeling enough such that they would know that they had to blow away the fact record first.
My problem is I have a FK to a role playing dimension (the date dimension in this case). So basically I have to columns in the fact table that have a FK relationship to the PK of the date dimension. When I create both relationships SSMS and try to have both
of them cascade delete SSMS has an issue with it.
The error I get is:
Unable to create relationship '[relationship name]'
Introducing Foreign Key constraint '[constraint name]' on table '[table name]' may cause cycles or multiple cascade paths. Specify ON DELETE NO ACTION or ON UPDATE NO ACTION, or modify other foreign key constraints.
I can go ahead and put no action and the table will save fine. The question now becomes how does the cascade delete actually work. Can I just set one part of the key to cascade delete?
Actually I just realized that this is an even bigger design issue. What DOES happen to a fact record when one of it's dimensions gets deleted and I've got full RI set up on the table?
Or am I totally thinking about this wrong. Do you set up cascade deletes in a dimensional model? Is there a way to prevent deletes from the dimension table if there are related fact records?

Delete rule not working

I subscribe to a mailing list using a particular email address (not my primary account), all mail for which is redirected into a mailbox. I only want to keep messages from the last five days. I have a Rule which is set as follows:
If ALL of the following conditions are met:
Account = <the account>
Date Received is Greater Than 5 days old
Perform the following actions:
Delete Message
This rule does does not work. It is the first rule in my list of Rules. And it simply does nothing. Why?

Maxplanar,
Mail rules only run when the item is first processed. So you are in effect going to delete things only when they are received in an "old" state.
I would set up a smart mailbox or two. One to only show the 5 days of mail you want to pay attention to. Optionally make another smart mailbox to contain messages older than 5 days. You can just refer to the first mailbox and only see the messages you want. The other mailbox will be there for once a month when you select all the messages and delete them.
Most macs can handle 5 to 10 thousand messages without even starting to slow down. Perhaps once you have a managable folder that shows you the messages you care to see, you can live with manually cleaning up much less often?

Query regarding Rules in MARS

Hello Friends,
Please let me know what type of Event these rules will trigger? (REFER ATTACHED DOC SCREENSHOT)
Specifically I want to know the meaning behind “Count”. If I increase the count field to 2 or 3 what will it do.
Also the time I configured is 10 minutes. Is it like it will check the condition for a time period of 10 minutes? What is the significance of time field here?

Hi Rashid,
The below link should give the description of each of the fields:
http://www.cisco.com/en/US/docs/security/security_management/cs-mars/6.0/user/guide/combo/rules.html#wp532081
The field "Count" refers to the number of times the event in the "Event" field has to fire within the "Time Range" specified for this Rule for the condition to be met. Hope this helps!!
Regards,
Prapanch

Delete rule not deleting in Mail

Hi,
I have a KILL rule where certain addresses are meant to be deleted. Since Mavericks, This is not working. They just stay in Junk. Any reason why?
Cheers,
Michael

Hi Philip,
when can we expect a fix for that since it is kind of an important function for us because without it we can't export a valid database structure.
Thanks in advance,
Michael

Deleting rule in MARS

Similar Messages

Maybe you are looking for