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

Similar Messages

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.

Creating Transformations -- Automatic Rules not Generating

Hi All,
I am Trying to create Transformations from Data source to DSO,
Automatic Rules not Generating, I have more that 120 Objects in DSO but it is generating only 2 roles , I am manually creating remaining rules
For automatic rules generation what I have to do ???
Regards,
Shaik

Hi Anil,
Thanks for quick Response ,
I am trying this , I am installing Transfer rules from BC, once Transfer rules Activate, I think it will work,
I need to know from u is this right way to do this????
Regards
Shaik

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?

Mutidimensional model does not generate any ddl

After building a model logical-relational and them adding the multidimensional on that.... selecting the engineer to oracle model only seems to update the colors in the relational and logical views. generating ddl does not add any dimension type ddl.
What is the multidimensional for?

selecting the engineer to oracle model only seems to update the colors in the relational and logical views. generating ddl does not add any dimension type ddlYou need open physical model when do that step and dimensions levels and hierarchies will be created there. You can find dimensions in physical model. You need that physical model open when generate DDL and statements for dimensions will be included.
Philip

View Properties - Header Aliases not generated in DDL

Hi
Using OSDDM 3.3.
I have defined a view in the relational model. I have only needed to specify 'Header Alias' for three of the columns in the view. The other columns I want to just keep their own names.
When the DDL is generated, this view does not have those Header Aliases specified.
Only if I provide a Header Alias for every single column does the DDL contain the needed definition for the view to specify the aliases.
Is this intended or a bug?
I would think a bug, since I only want to alias the columns I need/want to. not have to specify an alias that is just the same as the column being included in the view.
Your thoughts, please?
Thank you & Regards

Hi Philip
Sorry for the long time to reply on this.
I agree with what you say about the view header alias being a way to hide what is underneath, but sometimes we only need to alias certain view columns and the rest are ok to stay the same as the column names.
Thus (if coding by hand) we do have view creation DDL that aliases some columns (from "below") and the others are just the same as the column names.
So, if you guys do not agree with that, I would like to then request an enhancement request be logged, as you mention in your reply, for a way to indicate that we are ok for only some header alias to be defined and have the DDL contain those aliases, plus column names (as aliases) for columns not so formally aliased.
Thank you & Regards

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

On commit for mview refresh is not generated in DDL

New design > relational > new table w/ single numeric column
New Oracle 11g physical > new materialized view > on prebuilt table from above > Refresh Clause tab > select ON COMMIT action
-- add a body for grins
resulting XML in saved design:
<?xml version = '1.0' encoding = 'UTF-8'?>
<SnapshotOraclev11g class="oracle.dbtools.crest.model.design.storage.oracle.v11g.SnapshotOraclev11g" name="TABLE_1" id="E092B588-B0A8-437A-4187-9999090405D9" directorySegmentName="seg_0">
<createdBy>kdavis1</createdBy>
<createdTime>2012-07-18 15:28:57 UTC</createdTime>
<ownerDesignName>OTN_Issue_20120717a</ownerDesignName>
<action>ON COMMIT</action>
<defaultSegment>NO</defaultSegment>
<onPrebuiltTable>8332B16F-E06B-86AC-E123-DDA4F5DFF794</onPrebuiltTable>
</SnapshotOraclev11g>
Resulting DDL lacks ON COMMIT:
-- Generated by Oracle SQL Developer Data Modeler 3.1.1.703
-- at: 2012-07-18 11:47:26 EDT
-- site: Oracle Database 11g
-- type: Oracle Database 11g
CREATE TABLE "TABLE_1"
"Column_1" NUMBER
LOGGING
CREATE MATERIALIZED VIEW "TABLE_1"
ON PREBUILT TABLE
AS select sum(foo) from bar
-- Oracle SQL Developer Data Modeler Summary Report:
-- CREATE TABLE 1
-- CREATE INDEX 0
-- ALTER TABLE 0
-- CREATE VIEW 0
-- CREATE PACKAGE 0
-- CREATE PACKAGE BODY 0
-- CREATE PROCEDURE 0
-- CREATE FUNCTION 0
-- CREATE TRIGGER 0
-- ALTER TRIGGER 0
-- CREATE STRUCTURED TYPE 0
-- CREATE COLLECTION TYPE 0
-- CREATE CLUSTER 0
-- CREATE CONTEXT 0
-- CREATE DATABASE 0
-- CREATE DIMENSION 0
-- CREATE DIRECTORY 0
-- CREATE DISK GROUP 0
-- CREATE ROLE 0
-- CREATE ROLLBACK SEGMENT 0
-- CREATE SEQUENCE 0
-- CREATE MATERIALIZED VIEW 1
-- CREATE SYNONYM 0
-- CREATE TABLESPACE 0
-- CREATE USER 0
-- DROP TABLESPACE 0
-- DROP DATABASE 0
-- ERRORS 0
-- WARNINGS 0
Posts reviewed: (materialized && view) || mview || mv

Yes but then shouldn't "Refresh Type" be blank (instead of FAST) like "Refresh Action" is blank by default.
Or better yet, you already fill the mview name upon selection of a table for on prebuilt -- so should you select refresh YES upon choosing a type and/or action?
Seems to be an inconsistency here.

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

DM 3.0.0.665 instead of triggers not generating DDL correctly

There seems to be a bug in the DDL generation for manually created INSTEAD OF triggers on views. The INSTEAD OF trigger does not have the INSTEAD OF clause upon DDL generation. Instead, it has the BEFORE clause. It seems to be treating INSTEAD OF triggers as normal triggers. Note: When I reversed engineered a database that already had an INSTEAD OF trigger, it imported and generated DDL was fine. This bug shows itself when manually creating INSTEAD OF triggers.
Steps to replicate:
1. In any design that has a view.
2. In the physical model, find the view, expand it, right click to create Trigger for view
3. By definition, a trigger on a view can only be an instead of trigger.
4. The dialog box will have the 'Triggering time' showing as INSTEAD OF. You can't change it. (Which there is no reason to do anyway)
5. Generate DDL. When generating the DDL, the trigger will not be generated as INSTEAD OF, it will be generated as a BEFORE (INSERT/UPDATE/DELETE).
Included DDL generation from a simple database (I did not modify the DDL generated):
-- Generated by Oracle SQL Developer Data Modeler 3.0.0.665
-- at: 2011-03-30 13:16:32 EDT
-- site: Oracle Database 10g
-- type: Oracle Database 10g
-- CREATE DATABASE DB2
-- CONTROLFILE REUSE
-- MAXLOGFILES 1
-- MAXLOGMEMBERS 1
-- MAXLOGHISTORY 0
-- MAXDATAFILES 10
-- MAXINSTANCES 1
-- ARCHIVELOG
-- FORCE LOGGING
-- DATAFILE
-- '' SIZE 0 K REUSE
CREATE TABLE TABLE_1
Column_1 VARCHAR2 (1)
) LOGGING
CREATE OR REPLACE VIEW VIEW_1 ( Column_1 )
AS SELECT
TABLE_1.Column_1
FROM
TABLE_1 TABLE_1 ;
CREATE OR REPLACE TRIGGER Trg1
BEFORE INSERT ON VIEW_1
FOR EACH ROW
BEGIN
NULL;
END;
-- Oracle SQL Developer Data Modeler Summary Report:
-- CREATE TABLE 1
-- CREATE INDEX 0
-- ALTER TABLE 0
-- CREATE VIEW 1
-- CREATE PACKAGE 0
-- CREATE PACKAGE BODY 0
-- CREATE PROCEDURE 0
-- CREATE FUNCTION 0
-- CREATE TRIGGER 1
-- CREATE STRUCTURED TYPE 0
-- CREATE COLLECTION TYPE 0
-- CREATE CLUSTER 0
-- CREATE CONTEXT 0
-- CREATE DATABASE 1
-- CREATE DIMENSION 0
-- CREATE DIRECTORY 0
-- CREATE DISK GROUP 0
-- CREATE ROLE 0
-- CREATE ROLLBACK SEGMENT 0
-- CREATE SEQUENCE 0
-- CREATE MATERIALIZED VIEW 0
-- CREATE SYNONYM 0
-- CREATE TABLESPACE 0
-- CREATE USER 0
-- DROP TABLESPACE 0
-- DROP DATABASE 0
-- ERRORS 0
-- WARNINGS 0

Hi,
Thanks for reporting this problem. I logged a bug on it.
David

Validate Rules on Generating DDL

Hello,
What to do to create custom rules to be validated at the moment of generating DDLs ?
Regards
Nelson Antonio Alberti da Rosa

Hi Nelson,
Maybe I misunderstand, but I think you're missing something. Purpose of the design rules is to check your model (logical, relational, and process models) before generating DDL script. So there are only two places that you can apply some (all) rule:
1. From the menu tools->Design Rules->Design Rules
2. From DDL Generation Options screen, there is 'Design Rules' button at the bottom
DDL generation will not stop if some of the design rule is not met. If there is design rule error it will not go in DDL script.
So, everything you did is fine. If the rule works from above two places - it's Okay.
Please elaborate if I misunderstood.

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

Deleted Event Log Alerting Rule Still Generating Thousands of Alerts

I deleted a rule that is somehow still sending a ton of alerts.
---Deleted Rule
---Deleted agent server from SCOM
I cannot find where this is coming from.
Any tips guys?
Thanks

Hi You may want to check on the sql level to see if the agent is existing as a ghost. Follow this post to get the verification and remediation http://scompanion.wordpress.com/2013/10/22/ghostorphaned-entries-in-scom-console-windows-computer-view/
Blog: http://theinfraguys.com
Follow me at Facebook
The Infra Guys Facebook Page
Please remember to click Mark as Answer on the answer if it helps you in anyway

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

Delete rule not generated in DDL

Similar Messages

Maybe you are looking for