Propagate a deleted attribute from Logical to Relational

SQL Developer Data Modeler 4.0.0.825
Hi. From what I gather from the manual, when we delete an attribute from an entity in the Logical model, then Engineer the Relational model, the change should be detected and allow up to decide how the chage is handled in the "Synchronization of Deleted Objects" table of the Engineer to Relational wizard.
But the deletion is not showing in "Synchronization of Deleted Objects" and it does not get deleted in the Relational Model.
Here's what I am doing.
Create the "Library" model in the SQL Developer Data Modeler tutorial
Engineer a Relational Model
Add a new attribute "Date of Birth" to the Patrons entity in the Logical
Re-Engineer the Relational (new column is created)
Delete "Date of Birth" from Patrons in the Logical model
Re-engineer Relational
There are no little "change" icons in the comparison screen - it looks like there are no changes at all
Nothing appears in the Synchronization of Deleted Objects tab
When I click "Engineer", there Date_of_Birth column is not deleted from the Relational model
Am I doing something wrong?
If I reverse engineer from Relational back to Logical, it DOES identify the Date_of_Birth column as a difference and it wants to copy it back to the Logical.

Hi Ross,
you need to download DM 4.0 production release (4.0.0.833) - it should work there.
Philip

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

  • Views always appear as different when engineering from Logical to Relational

    I created some views in my logical model. After I engineer them to relational model, they appear in relational with an exclamation mark near the upper left corner. If I try to generate ddl for them, I get an error (--  ERROR: Invalid View VwTest). I realized that I have to "validate selected views", in order for the eclamation mark to disappear, and then I am able to generate ddl for them. After that, when I engineer from logical to relational again, it always shows me that my views are different. The difference is that in logical, my entities are shown between double quotes ("), while in relational, after the validation, the tables are not between double quotes. Is there a way to overcome this?
    Thanks

    Hi,
    Thanks for reporting this problem.  It appears that this is happening when the Entity name contains lower-case letters.
    David

  • Cannot delete attribute from attribute set

    I removed all business partners associated to the marketing attribute using Marketing Expert Tools, which I've done in the past with no problems.  I then went to the attribute set and removed the attribute that I want to delete, but when I tried to save the system told me that I could not do it in dialog as there are more than 400 business partners associated to the attribute set (not attribute but the attribute set).  It said I needed to run report RMCLMDEL, which is in CL6K transaction.
    Is there any other way to remove this attribute without having to run that report?
    Thank you.

    Prakash,
    Thanks for the tip, however, I must not have made myself clear in my message.  I had already tried that and although it seems to work once you actually go back to the attribute set the system still will not allow you to delete the attribute from the set if the attribute set is associated with more than 400 business partners.
    I also found OSS Note 772711 question 4 that validates this.   I guess I will have to use the CL6K transaction afterall.  Once again, thanks for your input

  • Column Prefix from Logical to Relational Model

    Hi,
    is there any option, that data modeler append an prefix (table short name) to a column, when the logical model will be transformed to relational model? (Same behavior as Oracle Designer)
    Example:
    Logical Model
    TABLE: PERSON
    TABLE-SHORT: PERS
    COLUMN-1: ID
    COLUMN-1: NAME
    Relational-Model
    TABLE: PERSON
    COLUMN-1: PERS_ID
    COLUMN-2: PERS_NAME
    Kind Regards,
    Stefan

    Thanks for your answer!
    This Script is not really working for me, because of our foreign keys.
    All our Foreign-Keys are named "ID" (for nummeric column) or "INDEX" (for a varchar column). After the transformation form logical to relational all the foreign-keys are named like "ID1", "ID2", "ID3", "INDEX1", "INDEX2" etc.
    There is no way to apply this script before the foreign-keys where added in the tables?
    The Second Way is to create a new script for this task.
    am i the only one with this problem? :-/

  • Engineering to and from logical and relational models

    I have tried to modify a logical model entity by adding an attribute or two, tried to engineer to the associated relational model, only to have the engineering process create a brand new table rather than adding the new column or two to the existing table.
    Creating the column in the table first and engineering back to the logical model didn't appear to do anything, although I might have missed a new logical entity.
    Is this how the product is supposed to work?

    Hello,
    I'm sorry but your steps are not evident for me.How it works - you can start from table or entity, it doesn't matter which one is first you should be able to synchronize changes.
    Let's assume you have two relational models RM1 and RM2 and table TABLE_1 in RM1. if you engineer RM1 to logical model then entity will be created that corresponds to TABLE_1 in RM1 (and it will be named TABLE_1 if you don't use glossary that provides replacement of TABLE with something else).
    You can add attribute to entity and engineer logical model to other relational model (RM2) - new table will be created in RM2.
    Add one more attribute to entity and engineer to RM1 - two attributes will appear showing that two new columns can be created - they are not selected and you have to select them if you want columns to be created.
    You'll get only one new attribute (column) if you engineer to RM2 - the first added attributed is already there as column.
    Of course you can add columns in tables and can synchronize them with entity in logical model.
    Philip

  • New Guy Question about Name Changes from Logical to Relational

    Sorry for the "New Guy" question. I am trying to do this the way I wished it worked rather than the way it does.
    Lets say I have an Entity named "Current Database" with an Attribute named "Current Database Name". All this is in plan english for the Logical Model. Now when I generate the Relational Model I would like the Table named "CDCD_CURRENT_DB" and the column named "CURRENT_DB_NAME".
    I have been working with a Glossary and some other features trying to get this to work. It kind of does but I do not fully get it and I think I am missing out on much of the power of the product. I have been forcing the Nickname "CDCD" (As we call it) and the "Database" to "DB" in the "Preferred Abbreviation" of the Entity.
    I am working with v3.3.0.734
    Thanks for the help.

    Hi Sky13,
    it can be done with glossary but it looks to me what you want is not that native to glossary approach.
    it's good to look here for basics http://www.oracle.com/technetwork/developer-tools/datamodeler/datamodelernamingstandards-167685.pdf
    Example here also could be useful if you want to go with glossary - Re: Data Modeler: Naming
    If you want to use preferred abbreviation then it should be CDCD_CURRENT_DB.
    For me CDCD_ is just a prefix - you can handle it separately in relational model - on whole model, on subview and in both cases classification types also can be used to determine how objects are prefixed.
    You don't want Current to be abbreviated then do not put it in glossary however you need to check "Incomplete modifiers" check box in glossary.
    Entity property "Short name" goes to table abbreviation during engineering. There is a transformation script which will prefix table columns with table abbreviation if you need it. And another one can remove the prefix.
    You can define plural name in glossary and if entity name is a single word then plural will be used during name translation.
    Philip

  • Skip the DELETE command on logical standby

    Hi All,
    I want to skip the DELETE command on logical standby.
    DB Version - 10.2
    OS - Linux
    Primary DB and logical standby DB .
    In our DB schema some transaction tables. We delete data from those tables by delete commands.
    Delete command, also delete data from logical standby DB. But we want to skip on logical standby DB .
    I use following for that and get error.
    ALTER DATABASE STOP LOGICAL STANDBY APPLY;
    EXECUTE DBMS_LOGSTDBY.SKIP (stmt =>'DELETE TABLE', schema_name =>'TEST',object_name =>'TRANS',proc_name => null);
    ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;
    But I got error
    ERROR at line 1:
    ORA-06550: line 1, column 7:
    PLS-00306: wrong number or types of arguments in call to 'SKIP'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    When I change stmt =>'DELETE TABLE' to stmt =>'DML', no error happen
    Please help me to solve this issue . This is urgent.
    Thanks in advance.
    Regards

    Dear aditi2,
    Actually it is so simple to understand the problem. Please read the following documentation and try to understand the SKIP procedure.
    http://download.oracle.com/docs/cd/B14117_01/appdev.101/b10802/d_lsbydb.htm#997290
    *SKIP Procedure*
    Use the SKIP procedure to define filters that prevent the application of SQL statements on the logical standby database.
    By default, all SQL statements executed on a primary database are applied to a logical standby database.
    If only a subset of activity on a primary database is of interest for application to the standby database,
    you can use the SKIP procedure to define filters that prevent the application of SQL statements on the logical standby database.
    While skipping (ignoring) SQL statements is the primary goal of filters,
    it is also possible to associate a stored procedure with a DDL filter so that runtime determinations can be made whether to skip the statement,
    execute this statement, or execute a replacement statement.
    Syntax
    DBMS_LOGSTDBY.SKIP (
         stmt                      IN VARCHAR2,
         schema_name               IN VARCHAR2,
         object_name               IN VARCHAR2,
         proc_name                 IN VARCHAR2,
         use_like                  IN BOOLEAN,
         esc                       IN CHAR1);Hope That Helps.
    Ogan
    Edited by: Ogan Ozdogan on 30.Tem.2010 13:03

  • Engineering (logical to relational) does not do name translation/variable population as expected

    I am using OSDDM 3.3.0.747.
    I have set up the following template formats, e.g.
    Foreign Key: {table}_FK{seq nr}
    Unique Constraint: {table}_UK{seq nr}
    When I engineer from logical to relational model, I get generated names like the following:
    {TABLE}_FK3
    TENANTS_UK{SEQ_NR}
    TENANTS_UK{SEQ_NR}v1
    How do I stop this from happening?

    Hi,
    thanks for reporting the problem. I logged a bug for problem related to Unique constraint.
    For foreign key - there is no variable {table} in template  for FK. You can use {child} or {child abbr} instead.
    As workaround for Unique constraint - you can apply naming standards for whole relational model - "Apply Naming standards for Keys and Constraint" in context menu for relational model in browser, or at table level - table dialog
    Philip

  • Engineer to Relational Model: deleted attributes / undeleted columns

    Hello,
    I am using Datamodeler 3.3.0.744.
    I'm modifying an existing logical model: I'm deleting one or more attributes in an Entity.
    Then I'm executing "Engineer to Relational Model" in oder to get an up to date Relational Model (it existed already).
    The corresponding columns are not deleted in the Relational Model, even though attributes don't exist anymore at the logical level.
    I can't find any option available in order to do that...
    In the previous release (3.1), it worked fine, I could choose the behavior related to the deleted attributes (deleting or not deleting corresponding columns).
    Edited by: user4995029 on 27 mai 2013 02:43

    When your forward engineer for a 2nd time you should see a dialog that has the logical on the left and the relational on the right. Entities that are new or changes have an exclamation point next to them. If you open that you will eventually drill down to see the attribute/columns. Where your dropped an attribute it will say "To drop". The check box is unchecked by default. If you check it then when you forward engineer those should get dropped from the associated table.
    Is it not working that way in 3.3?

  • Deleting the data from logical file/unix file

    Hi all.
        I need to delete the all the data from logical file (application server file/unix file).But I dont want to delete the logical file ( only data in the logical file should be deleted, i.e making file empty)
    Thanks in advance.
    Cheers.
    sami

    Hi Sami,
    Refer thsi document https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/4d7aeb7d-0c01-0010-fa8a-a4a8e8968a93.
    Regards,
    Flavya

  • Using the Null function to delete an attribute from a user in the metaverse

    RC1 Update 3 adds a new Null function, which (to me) sounds like it should flow a null value into the destination attribute.  I have a case where i am flowing a date from SQL into the metaverse.  Just for testing, I tried a basic flow of:
    Null()->employeeEndDate
    This seems to function the same as this:
    ""-employeeEndDate
    Both will add the employeeEndDate attribute to the metaverse object with a blank (not null) value.  To me, Null() seems like it should be equivalent of mventry("employeeEndDate").Delete, but it doesn't seem to.  Ultimately, what I want is to flow the value in if it is present in my connector space, and delete it if it is not.  Something like this:
    IIF(IsPresent(TermDate),DateTimeFormat(TermDate,"yyyy-MM-ddTHH:mm:ss.000"),Null())
    Anyone have any thouse on this?  Is there an easier to way to do this that I am overlooking?
    Thanks,
    Keith

    So here is a new update on this, with somewhat of a workaround.  I ran into a scenario where I wanted to delete attributes upon removal of a sync rule.  Unless I am missing something, this can't be done normally.  When my sync rule is removed,
    the attributes are no longer flowed from the MV to the CS, but they aren't removed from the object in the CS either.
    My Scenario:
    Only certain users should flow their location info to AD for display in the GAL.
    My Solution (these aren’t the real Set/Rule/WF/MPR names, it just makes it easier to understand):
    1.      
    Create two sets: “Show Info” & “Hide Info”
    2.      
    Create Sync Rule: “Flow info to AD”
    a.      
    Dependent on a Sync Rule “AD Base”
    3.      
    Create Workflow “Apply Flow Info to AD” to apply “Flow Info to AD” Sync Rule
    4.      
    Create MPR to apply the “Apply Flow info to AD” Workflow on Transition In to “Show Info”
    5.      
    Create a new Metaverse attribute for people called “nullString”
    6.      
    Create Sync Rule: “Null Info to AD”
    a.      
    Dependent on “AD Base”
    b.     
    Flows the nullString attribute to all AD attributes that need to be blanked out
    7.      
    Create Workflow “Remove Flow Info to AD” to remove “Flow Info to AD” Sync Rule
    8.      
    Create Workflow “Apply Null Info to AD” to apply “Null Info to AD” Sync Rule
    9.      
    Create MPR to apply “Remove Flow Info to AD” and “Apply Null Info to AD” Workflows on Transition In to “Hide Info” set.
    Obviously, you’ll need a null MV attribute for each data type you need to blank out, but it works.
    I haven't tried it, but it's likely this could also be done on inbound flows, provided you have unused attributes of each type in your data set (with a view you could
    just create them).  If X, then flow regular attribute from the CS in to the MV; if not X then flow the "null" attribute from the CS into the MV.
    Keith

  • How to show relation attribute on logical model

    Hi.
    How to show child entity relation attributes on logical model?
    Entity properties attribute list contains relation attributes, LM dont show they.
    I have model with several subviews. I need to show some entity without related entities but need to save "semantic" of relations on this subview. When relation attributes does not visible - no information about invisible relations on this subview.
    I can create my own visible attribute like "reference to customer" to make sense the relation with entity "Customer". This case problem is relation attribute presents in entity implicitly and relation model have 2 attribute - my own and generated FK column.
    In logical model i can`t replace child table relation attribute to my own "visible" attribute.
    In relational model i should redefine FK manually. Transformation script is posible but very odd way.
    Any advice appreciated.

    I am confused.
    I think the legacy Oracle Designer Barker notation could show reation attributes optional or by default, int`t it?
    Thanks a lot anyway.

  • Strange mapping of Boolean from Logical to DB2 Relational model

    Hi guys,
    Using most recent version of Data Modeler (3.3.0.747) I notice strange behavior:
    Attribute, declared as Boolean in Logical model is engineered to a column, with type CHAR(1) in Relational Model, when "RDBMS Type" is Oracle, but when "RDBMS Type" is "DB2", column type is CHAR(254)
    Is this a bug or a feature?
    Is there any way, where I can control type mapping between logical and relational model?
    Well, I can just go and change CHAR(254) to CHAR(1) all over my Relational Model, but this is pretty frustrating.
    MfG,
    Stoyan Tsonev

    Hi Stoyan,
    Is there any way, where I can control type mapping between logical and relational model?In fact mapping is between logical data type and database native types - Tools>Types Administration.
    You need to change mapping for Boolean logical data type - check "size" check box and put value in text field to define default size. Default size will be used when there is no explicitly defined size in column/domain definition.
    Philip

  • Audio Units won't delete from Logic Pro

    Recently I deleted a few AU that didn't work. They were originally installed by dragging them into the Components folder. As far as I can tell there is no trace of them in the Hard Drive. Logic still recognizes them and insists on scanning them every time I open Logic. I tried it on another user account and I tried trashing the prefferences for logic, but it still tries and fails the scan every time I open logic and they appear in the Audio Units Manager. I am beyond confused as to how to fix this issue. If anyone has any ideas or has had a similar issue I would apreciate it!

    First, delete the cache file found here..
    ~/Library/Caches/com.apple.audiounits.cache
    (Note: This is found in your User Library.. not the Local Library found in the Root of your System Hard Drive)
    Restart your Mac and restart Logic. It will then rescan all your AU plugins.. and see if that fixes things...
    If not then....
    If you have truly deleted them from the correct Library then Logic cannot see them... so they must still be in one of the two libraries..
    Check both the Library in the root of your System drive and the Library under your User name..
    If that fails...
    Download FindAnyFile from here
    http://apps.tempel.org/FindAnyFile/
    and use that to hunt them down...

Maybe you are looking for