Physical model attribute "Partition Scheme" not saved. (SS2000)

Hello,
I believe this is a bug report.
Scenario:
I have a physical model of a SQL Server database. The model contains partitioned tables, 1 partitioning function and 1 partitioning scheme. If I open the physical model properties of an index or a table, set the "Partition Scheme" attribute, save, close and re-open the model, the "Partition Scheme" attribute is lost. If I don't close out and just re-open the properties page, the attribute is retained. Some how, the attribute is lost in the persistence layer.
If there is a reason the attribute is being reset, please let me know.
Thank for your help, and all the great products you guys make,
Kurt
DataModeler v 3.1.1

Hi Kurt,
If there is a reason the attribute is being resetUnfortunately there is a bug causing the problem. Fix will be available in next patch release.
Philip

Similar Messages

  • Data Modeler EA1 - Print settings not saved

    Is there any way of saving page/print settings?
    Getting print settings/layout right often takes several changes in setup, at the moment it appears to make me do it every time I print.

    Not for now. I logged enhancement request for that.
    Philip

  • Attributes For SQL Server Physical Models Aren't Saved

    In version 3.0.0.665, a physical implementation implementation of data model was persisted to SQL Server 2005. The physical implementation required the use of IDENTITIES; the equivalence to an Oracle sequence.
    The functionality works fine because the DDL generated correctly and the script was persisted to the target database without incidence. Both the physical model and DMD were saved. After deployment, the client required the addition of several attributes into the model. Since the model hadn't populated yet, the desired approach involved dropping the SQL SERVER database (Oracle Schema), applying the changes to the data model, generating the DDL, and creating the SQL SERVER database.
    Upon inspection of the generated DDL, the IDENTITY directives were absence. Further research discovered the attributes were absence from the property sheets attached to the various physical tables. Further testing uncovered that these attributes only persist throughout the lifetime of the data modeling session.
    I have not had this experience with Oracle physical models e.g.(creating trigger, sequences, etc). Most likely this is a defect in the software, but I was curious to know, if anyone else as run across this opportunity.
    Warm regards,
    Greg

    In version 3.0.0.665, a physical implementation implementation of data model was persisted to SQL Server 2005. The physical implementation required the use of IDENTITIES; the equivalence to an Oracle sequence.
    The functionality works fine because the DDL generated correctly and the script was persisted to the target database without incidence. Both the physical model and DMD were saved. After deployment, the client required the addition of several attributes into the model. Since the model hadn't populated yet, the desired approach involved dropping the SQL SERVER database (Oracle Schema), applying the changes to the data model, generating the DDL, and creating the SQL SERVER database.
    Upon inspection of the generated DDL, the IDENTITY directives were absence. Further research discovered the attributes were absence from the property sheets attached to the various physical tables. Further testing uncovered that these attributes only persist throughout the lifetime of the data modeling session.
    I have not had this experience with Oracle physical models e.g.(creating trigger, sequences, etc). Most likely this is a defect in the software, but I was curious to know, if anyone else as run across this opportunity.
    Warm regards,
    Greg

  • Data modeler saving Physical model changes not saved

    I am using version 2.0.0.584.
    The bug fix list contains: 8722310: Save does not save physical model changes
    Hovever I still see unexpected behaviour.
    I created a physical model for "Oracle database 10g" and allocated a couple of tables to a different tablespace.
    I saved the physical model via Physical model--> right mouse button --> save all.
    I saved the model with File--> save
    I close the model.
    After opening, the physical model is not available anymore.
    After Physical model--> right mouse button --> open (for Oracle 10g) the contents are not the same anymore.
    Tablespaces with name "TableSpace3" and "TableSpace4" are added and objects belong to this tablespace.
    We do not have currently a workaround for this behaviour.
    Can anyone help?
    Thanks
    Edited by: 793016 on 06-Sep-2010 03:10
    Edited by: 793016 on Sep 6, 2010 12:14 PM

    Hi Philip,
    default tablespaces were defined and I removed this. It did not have a positive effect.
    Checking the log files was a good idea.
    The log file contained errors about files which could not be found on the system.
    I will do some additional tests and let you know.
    Thanks.
    Kind regards,
    Maurice

  • Delete several partitions in physical model

    Hi All,
    I don't know if someone has the same necessity than me, if not maybe is because I don't know how to do something that is already implemented,
    anyway, my question is:
    How can I delete several partitions (400) at the same time from the same table in the physical model?
    I can select the partitions but the contextual menu is not working, I can press delete button into the toolbar but is doing nothing,
    I imported from my data dictionary a schema with several tables that have a lot of partitions and I'm not interested to save these partitions,
    when I try to generate the DDL is generating all of the partitions and I don't want the DDL with thousands of partitions inside,
    the number of tables with partitions is not so high but is not comfortable to go one by one selecting the partitions and deleting the object (400 times in one table),
    I can modify the table to say that is not partitioned and all the partitions will disappear but I then need to modify again the tables and include the fields for the partitions and sub-partitions, not useful,
    another option could be to select during the import if I want to import only one partition of each table
    but I 'm not sure is at the end it's needed just because I think that only deleting the partitions with one operation should be enough, at least for me
    thanks in advance

    Hi David,
    First of all thanks for your quick response and for your help logging the enhancement request,
    I am testing more or less your suggestion but I  am not sure if I understood exactly what you mean,
    1)I imported from data dictionary in a new model and into the options menu on the schema select screen I un-ckecked partitions and triggers,
    I guessed that the import should not get from the data dictionary the information about the partitions but the result is that the tables partitioned (by list in this case) are partitioned by range without fields into the physical model on SDDM,
    2)I select one of the tables modify a NO partitioned option and propagate the option for the rest of the tables
    3) I imported again from data dictionary but this time I included the partitions into the option menu on select schema screen,
    into tabular view on compare models screen I can select all the tables with different partitioned option, also I can change for "list partitions" and select only the partitions that I want to import.
    So I have a solution for my problem, thanks a lot for your suggestion
    The second step I'm not sure is needed or maybe I can avoid the step with some configuration setting in any of the preferences screen,
    if not, I think the options to not include partitions into select schema screen are not so clear, at least for me,
    please, could you confirm me if a way to avoid the second step exists or if I misunderstood this option?
    thanks in advance

  • Schemas to Users in Oracle Physical Model

    I created a relation model and sorted out the tables among the schemas. Now I am trying to create a physical model (Oracle 11g). It works and the tables are created in but there are only two Oracle users (PUBLIC & MDSYS). All the tables in the physical model have blank user (schema) field. Does it mean that I should create the users (schemas) again and sorted out the tables in the physical model?
    I cannot find an option that allows me to transform the schemas in the relation model into the users in the physical model saving the links between the users and the tables.
    Does this option (way) exist?
    Regards,
    userIV

    Thank you for the prompt answer.
    Anyway it seems to me strange why schemes can not be auto created ion the physical level - I think it's quite rare situation when definition in the relational model can be different from the physical one. Fortunately it's no so many users I need in mu case.

  • Physical attributes for index on temp tables (using physical model)

    I need create index on temp tables.
    When I generate DDL, it includes physical attributes like ‘LOGGING NOCOMPRESS NOPARALLEL’.
    I get error "ORA – 14451 (unsupported feature w/temporary tables)"
    I’ve to use physical model in OSDM. How do I get rid of physical attributes in DDL for index?

    Hi,
    Thanks for reporting this problem.
    You can remove the LOGGING clause by opening the Properties dialog for the Index in the Physical model and setting its Logging property to the blank option.
    However it's not possible to suppress the NOCOMPRESS and NOPARALLEL at the moment.
    I've logged a bug on this.
    As a workaround, you could do a global edit on the DDL file to remove all instances of NOCOMPRESS and NOPARALLEL.
    David

  • Extended VO Attributes are not saved

    Hi,
    I build new Extend VO based on EO.
    I add 2 attributes in the VO query.
    The problem is that those attributes values are not been saved.
    when i look in the attribute mappings Tab i can see the mapping is incorrect.
    I try to fix it but it always keep mapping them to wrong attributes.
    Please help with that issue!
    Thanks,

    Hi,
    Thanks for your replay.
    My need is to add 2 attributes to VO based on EO, to enable entering additional info, with some fields validations.
    My plan is to Extent the VO adding those 2 attributes, create items through Personalization and eventually add validition in the Exstended controller.
    i verify that the VO EO includes the new attributes.
    so i did the following:
    1. Extent the VO - Create VO Sustitution, adding attributes in the VO Query.
    2. Deploy the VO
    3. Create Page personalization - create 2 items, connected to the Extended VO
    When i Enter the VO in the application i can see the new attributes with db selected values, But when i try to update them the change not been saved.
    I check the attributes mappings and see that the mapping is incorrect.
    I try to remapp the attribute to the correct ones from the EO but is always keep the wrong mapping.
    i assume that i can add some logic in the controller to set those attributes but i think that this can be done in the VO attribute mapping?
    Thanks for your help.

  • GenIL Model Attribute Structure not getting updated with new fields added

    Hi All,
    I have modelled the service interface using GenIL Modelling in Duet Enterprise 1.0. Later, I added some fields to the read operation in the Enterprise Services Builder in the ESR system.
    But in the Read Operation mapper method "/IWFND/IF_SRD_BOP_MAP_GET_OBJ~MAP_POST_GET_OBJECTS",  when I try to define an object of type GenIL model Attribute Structure (ZMDLZPRGET_DETAIL),  Iam unable to access the newly added fields in the read operation.
    In transaction " GENIL_MODEL_EDITOR ", under Root Objects, when I open the Attribute Structure name, only the old fields are available, newly added fields are not updated.
    But I was able to see the newly added fields in the READ OPERATION data types of Enterprise Services Browser in SE80.
    Please help me how to update the new fields for GenIL Model Attribute Structure(ZMDLZPRGET_DETAIL).
    Thanks,
    Kris

    Hi sap_wiz,
    Thanks for your reply.
    My problem solved,
    Thanks
    Kris

  • Arc is not implemented for SQL Server 2005 physical model

    I added the Arc in my relational model, which is supposed to provide that references are mutually exclusive (so only one refering column can be not null). However there is not any implementation for this in the SQL Server 2005 physical model. The SQL code generated simply ignores the Arc and allows any values for the columns covered by Arc. If we check Oracle physical model. then it generates some trigger, which controls how many columns have values assigned - this is actually an implementation of Arc. But there is nothing of this kind for SQL Server model...
    By the way, implementing this Arc by trigger looks like to heavy approach. The very simple table level check constraint will do the same job. But this is a different subject though.
    Edited by: Otbl on Nov 3, 2011 7:34 PM

    Hi Dmitry,
    it's fixed in Data Modeler 3.1 EA2.
    Philip

  • Attribute subtreeaci is not supported in schema.

    As part of integrating OIM/OAM into LDAP i have followed the preparing identity store steps which is part of the preconfig... in the last part where i set the correct rights for my oimadmin user (Set Up Oracle Virtual Directory–Oracle Identity Manager Access Control Lists)... I'm failing on ldapmodify. This is the install guide http://docs.oracle.com/cd/E21764_01/core.1111/e12035/prep_is_ps.htm#BABBFHHB.
    My ldif file is as follows:
    dn: dc=com
    changetype: modify
    add: subtreeACI
    subtreeACI: grant:b,t,a,d,n#[entry]#authzID-dn:cn=oimadmin,cn=systemids,dc=com
    subtreeACI: grant:s,r,w,o,c,m#[all]#authzID-dn:cn=oimadmin,cn=systemids,dc=com
    dn: cn=changelog
    changetype: modify
    add: subtreeACI
    subtreeACI: grant:b,t,a,d,n#[entry]#authzID-dn:cn=oimadmin,cn=systemids,dc=com
    subtreeACI: grant:s,r,w,o,c,m#[all]#authzID-dn:cn=oimadmin,cn=systemids, dc=com
    When running my ldapmodify command the following error is thrown:
    modifying entry dc=com
    ldap_modify: Undefined attribute type
    ldap_modify: additional info: Attribute subtreeaci is not supported in schema.
    What may be wrong?
    Thanks

    Olaf,
    Thanks a lot for support!
    I have got following data in Security section:
    [root]
    Under Tree Access:
    Structural Access Elements: none
    Content Access Elements: none
    Local Access:
    Structural Access Elements: grant-entry; entry; returnDN:browseDN; public; NONE
    Content Access Elements: grant-attributes; all; *; search:read, public; NONE
    cn=schema
    Under Tree Access:
    Structural Access Elements: none
    Content Access Elements: none
    Local Access:
    Structural Access Elements: grant-entry; entry; returnDN:browseDN; public; NONE
    Content Access Elements: grant-attributes; all; *; search:compare:read; public; NONE
    cn=changelog
    Under Tree Access:
    Structural Access Elements: grant-entry; entry; renameDN:returnDN:browseDN:return:add; authorizedId; cn=oimLDAP, cn=systemids, dc=mydomain,dc=com
    Content Access Elements: grant-attributes; all; *; obliterate:search:compare:write:read:make; authorizedId; cn=oimLDAP, cn=systemids, dc=mydomain,dc=com
    Local Access:
    Structural Access Elements: none
    Content Access Elements: none
    dc=maindomain
    Under Tree Access:
    Structural Access Elements: grant-entry; entry; returnDN:browseDN; public; NONE
    grant-entry; entry; renameDN:returnDN:browseDN:return:add; authorizedId; cn=oimLDAP, cn=systemids, dc=mydomain,dc=com
    Content Access Elements: grant-attributes; all; *; search:compare:read; public; NONE
    deny-attributes; attributes; userpassword; compare:read; public; NONE
    grant-attributes; attributes; userpassword; read; this; NONE
    grant-attributes; attributes; userpassword:description:postaladdress:thelnumber:title; obliterate:write; this; NONE
    grant-attributes; all; *; obliterate:search:compare:write:read:make; authorizedId; cn=oimLDAP, cn=systemids, dc=mydomain,dc=com
    Local Access:
    Structural Access Elements: none
    Content Access Elements: none
    Daniel

  • MITI Integrator for Erwin 4.1 - Physical Model does not import

    Hello,
    I'm running the MITI integrator in BOMM 3.0 for Ewrin 4.1
    I'm using an ER1 file that contains both the Logical and physical data model.
    When i explor the data in BOMM Explorer, i can only see the  Logical model.  There is a loose link to the physical model in the Technical Name field - but this does not seem to be completely accurate.  It looks like the integrator just takes the Logical name and replaces spaces with underscores.  This works in the following example where the logical name and physical name are essentially the same:
    Logical name: Customer Names
    Physical name: customer_names
    Technical name (parsed?): customer_names
    In the above example BOMM will generate a same as relationship between tables called customer_names and the Logical table "Customer Names".  this is what we are hoping to see. 
    The following example is where the problem occurs.
    Logical Name: Customer Names
    Physical Name: cstmr_nm
    Technical Name (parsed?): customer_names
    In the above scenario, BOMM is no longer able to draw the relationship from the logical name to the physical name.
    As I stated at the beginning  - it seems that the Integrator is only importing the logical model and then parsing the technical name out of that - we are using an NSM file to convert common terms to erwin standard abbreviations and we were wondering if the ingtegrator could leverege this file in some way.

    Hello,
    I'm running the MITI integrator in BOMM 3.0 for Ewrin 4.1
    I'm using an ER1 file that contains both the Logical and physical data model.
    When i explor the data in BOMM Explorer, i can only see the  Logical model.  There is a loose link to the physical model in the Technical Name field - but this does not seem to be completely accurate.  It looks like the integrator just takes the Logical name and replaces spaces with underscores.  This works in the following example where the logical name and physical name are essentially the same:
    Logical name: Customer Names
    Physical name: customer_names
    Technical name (parsed?): customer_names
    In the above example BOMM will generate a same as relationship between tables called customer_names and the Logical table "Customer Names".  this is what we are hoping to see. 
    The following example is where the problem occurs.
    Logical Name: Customer Names
    Physical Name: cstmr_nm
    Technical Name (parsed?): customer_names
    In the above scenario, BOMM is no longer able to draw the relationship from the logical name to the physical name.
    As I stated at the beginning  - it seems that the Integrator is only importing the logical model and then parsing the technical name out of that - we are using an NSM file to convert common terms to erwin standard abbreviations and we were wondering if the ingtegrator could leverege this file in some way.

  • Save point with POJO DataControl not saving model state

    Hi Guys,
    JDEV 11.1.1.6 64bit
    I was able to get save points working with ADF BC (AppMod, View & Entity objects)
    but when I tried to do the exact same with Pojo DataControls, I won't save
    the current state of the model - meaning things are not "selected" to the
    proper record when the SP is restored. I don't get any errors, it just
    shows the wrong data.
    Example:
    The BTF is marked as must have transaction(tried either way), but this is Pojo, and doesn't support Trx.
    edit-emp-dept.jspx (with BTF Region)
    BTF START
        STEP 1: RichTable with bindings to Pojo DataControl (value="#{bindings.allDepts.collectionModel}")
                     (user selects the 3 record => sales department)
        STEP 2: Edit Sales Dept & on click to next step create SP
        STEP 3: View Emps (Rich Table of ALL emps in that DEPT)
        STEP 4: Edit Emp
        FINAL: COMMIT (save to pojo list) or CANCEL (don't save to pojo list)
    /BTF END
    At STEP 1 -> STEP 2, the SP is created, and when I close the browser at STEP2, 3  or 4, and
    restart, and choose SP to restore, it takes me to proper page (STEP 2)  but the wrong Department is
    selected to edit (it shows "Finance" instead of "Sales") & if I hit my ADF back button, it shows
    the table with "finance" selected.  In the ADF BC world it works perfectly.
    I know the docs say: the ADF Model is saved, so the question is why bindings.allDepts.collectionModel
    not "saved" here for Pojo DC and the ADF BC af:table value="#{bindings.DepartmentsView1.collectionModel}"
    it is "saved".
    Thanks for any insight or work-around.
    Sincerely,
    Joel
    edit-emp-dept.jspx:
    <?xml version='1.0' encoding='UTF-8'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
              xmlns:f="http://java.sun.com/jsf/core"
              xmlns:h="http://java.sun.com/jsf/html"
              xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
      <jsp:directive.page contentType="text/html;charset=UTF-8"/>
      <f:view>
        <af:document id="d1">
          <af:form id="f1">
            <af:region value="#{bindings.btfpojodc1.regionModel}" id="r1"/>
          </af:form>
        </af:document>
      </f:view>
    </jsp:root>

    Hi,
    the problem with POJO DC and other non-ADF BC models is that they don't passivate their state. In JDeveloper 12c we allow developers to extend their POJO classes with ADF lifecycle methods that allows them to save the model state themselves. Its a known issue that the transaction state cannot be saved for non-ADF BC models. I checked the bug database for bugs filed against this behavior but could not find one- I can imagine that with 12c we would have a chance to allow developers to handle passivation / activation for non-ADF BC model states. So if this is a feature you need then filing an enhancement request would make sense
    Frank

  • After i bought mac os x lion from web then download , after that to install but when they ask me to choose disk to install i can not choose, it say this disk does not use the GUID partiton table scheme. use disk utility to change the partition scheme. but

    after i bought mac os x lion from web then download , after that to install but when they ask me to choose disk to install i can not choose, it say this disk does not use the GUID partiton table scheme. use disk utility to change the partition scheme. but

    after i bought mac os x lion from web then download , after that to install but when they ask me to choose disk to install i can not choose, it say this disk does not use the GUID partiton table scheme. use disk utility to change the partition scheme. but

  • HT2434 does anybody know what happens if I dont update the firmware of my macbook pro (does not have a guid partition scheme))

    does anybody know what happens if I dont update the firmware of my macbook pro (does not have a guid partition scheme)?

    Apple will hire a high school girls clique to follow you around, make fun of you & post disparaging comments on Facebook .

Maybe you are looking for