Setting "Segment Templates" on tables in physical model

Yesterday I set different "segment templates" to corresponding tables and indexes. It worked fine but, today, DDL generator does not apply them. Is it possible? Apparently, segment templates are easy to define and simple to set.
Thank you.
Bernat Fabregat

It is possible that "segment template" application were lost after closing and reopening.did you save your physical model? Usually it asks for that.
no sequences, no partitions, etcdo you see them in physical model? If not can you check design directories structure (for sequences) - are there files (*.xml) under directory "Sequence" - they are not directly in that directory - there are other directories with names like seg_0...
Philip

Similar Messages

How to specify COMPRESS FOR OLTP on a table in physical model?

Hi,
we have licensed Oracle's Advanced Compression and want to use the OLTP compression on some tables. I am looking for a way to specify COMPRESS FOR OLTP on a table in the physical model. So far, I can only set "Data Compression" to YES or NO.
Are you going to add the "new" compression modes in the next release?
Thanks,
Frank
Version of SQL Developer Data Modeler is 3.1.3.709

Hi Frank,
Are you going to add the "new" compression modes in the next release?There is support for compression type (including OLTP) in DM 3.3 EA and you can download it from OTN.
Philip

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

SQL Dev Data Modeller: Auto-generate Surrogate PKs in the Physical Model ?

How can I have the logical modeller allow the user to design with logical PKs, but then have surrogate primary keys be auto-generated off sequences by the modeller when it comes to create the physical model - as in conventional application design?
Without this facility, this tool is useless, IMO.
I want:
i). sequences to become the physical PKs by default, and that what were the logical PKs in the logical model, to become a unique key in the physical model.
ii). I want this set by default when generating the physical model....
iii). ....with an option to turn this off on a entity-by-entity basis (as not all tables will necessarily require such a surrogate PK; so the logical PK may remain the physical PK).

It is common practice that physical PKs in Oracle tables are defined from sequences (surrogate PKs), and that the logical PK from the entity becomes a unique key in the table.
This may not always be the case in every application out there, and some people may disagree, but it is nonetheless a needed feature.
My new Feature Request is therefore:
I would like to see the following additions to the product.
1. In the Preferences -> Data Modeler -> Model -> Logical, a flag that by default indicates whether the designer wishes to opt to enable this feature (ie; have all logical PKs converted to unique keys, and replaced by sequence nos. in the physical model). This flags needs to be there since in real life, albeit erroneously IMO, some people will choose not to opt to use this functionality.
2. On every entity created in the model, there needs to be a flag that allows to override this default option, as not every table will require a surrogate PK to be generated. Being able to (re)set a flag located on the entity properties (perhaps under 'Engineer To'), will accomplish this.
3. When Forward Engineering to the physical model from the logical, the following should happen.
ENTITY 1 ---------->TABLE 1
---------------------> P * Surrogate PK
* Attribute 1 -----> U * Column 1
* Attribute 2 -----> U * Column 2
o Attribute 3 ----------> Column 3
Here you can see,
- Attributes 1 & 2 (the logical PK) of the entity become a unique key in the table (columns 1 & 2),
- optional Attribute 3 becomes NULLable column 3,
- and a physical surrogate PK column is added (type unbounded INTEGER, PRIMARY KEY constraint added).
From entity DEPT as: (Examples based on SCOTT schema)
DEPTNO NUMBER(2) NOT NULL <-- Logical primary key on entity
DNAME VARCHAR2(14)
LOC VARCHAR2(13)
CREATE TABLE DEPT
(PK_DEPT INTEGER, -- New column becomes surrogate physical PK, driven from sequence defined later
DEPTNO NUMBER(2) NOT NULL, -- Former logical PK becomes a UK
DNAME VARCHAR2(14),
LOC VARCHAR2(13))
ALTER TABLE DEPT
ADD CONSTRAINT PK_DEPT PRIMARY KEY (PK_DEPT) USING INDEX PCTFREE 0
ALTER TABLE DEPT
ADD CONSTRAINT UKLPK_DEPTNO UNIQUE (DEPTNO) USING INDEX PCTFREE 0 -- Former logical PK becomes a UK (constraint name reflects this)
CREATE SEQUENCE PK_DEPT_SEQ
CREATE TRIGGER PK_DEPT_SEQ_TRG
BEFORE INSERT ON DEPT
FOR EACH ROW
WHEN (new.PK_DEPT IS NULL)
BEGIN
SELECT PK_DEPT_SEQ.NEXTVAL
INTO :new.PK_DEPT
FROM DUAL;
-- Or from 11g onwards, simply,
:new.PK_DEPT := PK_DEPT_SEQ.NEXTVAL;
END;
From entity EMP as:
EMPNO NUMBER(4) NOT NULL -- Logical primary key on entity
ENAME VARCHAR2(10)
JOB VARCHAR2(9)
MGR NUMBER(4)
HIREDATE DATE
SAL NUMBER(7,2)
COMM NUMBER(7,2)
DEPTNO NUMBER(2)
CREATE TABLE EMP
(PK_EMP INTEGER, -- New column becomes surrogate physical PK, driven from sequence defined later
FK_DEPT INTEGER, -- New FK to surrogate PK in DEPT table (maybe NOT NULL depending on relationship with parent)
EMPNO NUMBER(4) NOT NULL, -- Former logical PK becomes a UK
ENAME VARCHAR2(10),
JOB VARCHAR2(9),
MGR NUMBER(4),
HIREDATE DATE,
SAL NUMBER(7,2),
COMM NUMBER(7,2),
DEPTNO NUMBER(2))
ALTER TABLE EMP
ADD CONSTRAINT PK_EMP PRIMARY KEY (PK_EMP) USING INDEX PCTFREE 0
ALTER TABLE EMP
ADD CONSTRAINT FK_DEPT FOREIGN KEY (FK_DEPT) REFERENCES DEPT (PK_DEPT)
ALTER TABLE EMP
ADD CONSTRAINT UKLPK_EMPNO UNIQUE (EMPNO) USING INDEX PCTFREE 0 -- Former logical PK becomes a UK (constraint name reflects this)
CREATE SEQUENCE PK_EMP_SEQ
CREATE TRIGGER PK_EMP_SEQ_TRG
BEFORE INSERT ON EMP
FOR EACH ROW
WHEN (new.PK_EMP IS NULL)
BEGIN
SELECT PK_EMP_SEQ.NEXTVAL
INTO :new.PK_EMP
FROM DUAL;
-- Or from 11g onwards, simply,
:new.PK_EMP := PK_EMP_SEQ.NEXTVAL;
END;
[NOTE: I use PCTFREE 0 to define the index attributes for the primary & unique keys since the assumption is that they will in general not get updated, thereby allowing for the denser packing of entries in the indexes and the (albeit minor) advantages that go with it.
This is certainly always true of a sequence-driven primary key (as it is by its very nature immutable), but if the unique key is likely to be frequently updated, then this PCTFREE option could be user-configurable on a per table basis (perhaps under Table Properties -> unique Constraints).
For non-sequence-driven primary keys, this storage option could also appear under Table Properties -> Primary Key.
I notice no storage options exist in general for objects, so you may like to consider adding this functionality overall].
Associated Issues :
- Preferences, 'Naming Standard: Templates' should be updated to allow for the unique key/constraint to be called something different, thus highlighting that it comes from the logical PK. I've used 'UKLPK' in this example.
- Mark the physical PK as being generated from a sequence; perhaps a flag under Table Properties -> Primary Key.
- When Forward Engineering, if an entity exists without a logical PK, the forward engineering process should halt with a fatal error.
!!! MODERATOR PLEASE DELETE ME !!!

How to set border lines in table and also in template in the smartforms ?

How to set border lines in table and also in template in the smartforms ?
As I have to create table with following detals
total row = 3
row1 = 3 column
row2 = 6 column
row3 = 9 column
for 2nd and 3rd row data to be fetched using coding.
so can anybody explain me what should i use
Table or Template ?
and I want the border like excel format.
Can anybody suggest me ?
Thanks
naresh

if the data is multiple i.e. line items choose table.
if the data is single i.e. fixed choose template.
Create table
> Draw u r no lines
> choose option select pattern
> select display framed patterns
Choose u r required one.
out lined, or full lined. u can choose option.
same procedure to be followed for template also.
with regards,
Kiran.G

Physical Model - Propagate table property "Tablespace" doesn't seem to be working in 4.0EA2

I'm to switching from v3.3.0.747 to 4.0EA2 but experiencing some issues.
In the physical model when I try to propagate the table property "Tablespace" for the remaining tables a silent error happens and as result the value is not propagated.
The error appears in the log file:
2013-09-24 16:31:31,776 [AWT-EventQueue-0] WARN PropertyWrapper - oracle.dbtools.crest.model.design.storage.oracle.v11g.TableProxyOraclev11g.setTableSpace(oracle.dbtools.crest.model.design.storage.oracle.TableSpaceOracle)
java.lang.NoSuchMethodException: oracle.dbtools.crest.model.design.storage.oracle.v11g.TableProxyOraclev11g.setTableSpace(oracle.dbtools.crest.model.design.storage.oracle.TableSpaceOracle)
at java.lang.Class.getMethod(Class.java:1624)
at oracle.dbtools.crest.util.propertymap.PropertyWrapper.setValue(PropertyWrapper.java:65)
at oracle.dbtools.crest.swingui.editor.storage.PropertiesPropagationDialog.applyTo(PropertiesPropagationDialog.java:353)
at oracle.dbtools.crest.swingui.editor.storage.PropertiesPropagationDialog.setProperties(PropertiesPropagationDialog.java:337)
at oracle.dbtools.crest.swingui.editor.storage.PropertiesPropagationDialog.access$400(PropertiesPropagationDialog.java:46)
at oracle.dbtools.crest.swingui.editor.storage.PropertiesPropagationDialog$11.actionPerformed(PropertiesPropagationDialog.java:300)
at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2018)
at javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2341)
at javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402)
at javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)
at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(BasicButtonListener.java:252)
at java.awt.Component.processMouseEvent(Component.java:6505)
However if I try to propagate the tablespace value for indexes this works fine.
Some ideas?
Thanks.

Hi,
Thanks for reporting this. I've logged a bug.
I'm afraid you won't be able to propagate Tablespaces on Tables until it's fixed.
David

Unable to include a table in a Physical Model Diagram via the RON

Hi,
In Designer 10g I am unable to include a table in a Physical Model Diagram (Edit > Include) if I open the diagram via the RON, but it works if the diagram is opened via the Design Editor.
I found Doc ID268944.999 on Metalink which seems to detail the same problem, but no solution. So does this only work via the Design Editor now?
Thanks,
Antony

I tried to find the item on Metalink but could not find it.
I have never tried to move tables in the RON to an SMD.
Of course I do not know why you would want to do that. The DE does it so nicly.
What error message are you getting?
Tell me exactly what your doing and I will try it here.

Probelm Addind new Table in Physical Layer, Create Dim in Business Model ..

I have completed a task for a dash board, that is running sucessfully.
Now I added a new table in "physical layer", (file->import->from database), table added successfully
Now, I droped this table in "business model", but when I want to create its dimension, there is no any option (when I right click on this table)
there are two cases
case 1:
I did not added modified fact table (with foreign key of new table) in "physical layer" and not in "business model and mapping"
case 2:
I added new table and modified "fact table (with foreign key of new table)" in "physical layer" and "business model and mapping"
but in both cases there is no "create dimension" button to create dimension
Please let me know the how to solve this problem, kindly define it in steps
thanks

Hi thr,
Create Dimensions is only available if the selected logical table is a dimension table (defined by 1:N logical joins) and no dimension has been associated with this table.
In you case, once you have imported the table successfully in physical layer, then join your table to fact table. Drag n drop in BMM under a new logical table and then join it to BMM Logical fact using complex join. Now, if you right click, you see the last option as 'Create Dimension'
Hope you find it useful..

Table properties doesn't propagate from Relational Model to physical model

Hi all,
I have a relationnal model with several tables and several schema.
When i create a new table in the relational model with a specified schema, the table is created on the physicla model, but the schema is not prapagate.
Is there a way to do this automatically ?
Or do i have to specify the schema on the relationnal and on the physical.
Thank you

Hi,
schema object in relational model needs to be implemented in physical model - user is the implementation of schema in Oracle physical model. User has property "implements schema". You also can omit this redirection and can assign directly user to table but in this case you'll lose the flexibility.
Here is how DDL is impacted using different option (schema_1 and table_1 in relational model):
1) physical model is not open - no implementation details
CREATE TABLE Schema_1.TABLE_1
     Column_1 NUMBER
;2) physical model is open - Schema_1 is not implemented
CREATE TABLE TABLE_1
     Column_1 NUMBER
    ) LOGGING
;3) physical model is open - Schema_1 is implemented by User1
CREATE TABLE User1.TABLE_1
     Column_1 NUMBER
    ) LOGGING
;4) physical model is open - Schema_1 is implemented by User1; Table_1 is directly assigned to User2 in physical model
CREATE TABLE User2.TABLE_1
     Column_1 NUMBER
    ) LOGGING
;Philip

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

Physical model disabled

I'm trying to create a Partition using sql developer/modeler
my physical model all the options or disabled(greyed out) when it is connected to live database how do I over come this

Hi,
You need to open the Physical Model properties dialog for the Table (from the Physical model part of the Browser tree) and set the Partitioned property (on its General tab) to YES.
You will then be able to use the Partitioning tab in this dialog, to set Partitioning type and other Partitioning properties.
Also, after you've closed this dialog, you can create Partition instances by selecting New from the right-click menu for the Partitions node (subordinate to the Table's node in the Physical model part of the tree).
David

Physical Model Data Type Issue

Hi,
I have created ware house tables using E-business suite tables for general ledger model and exported into physical model. I could see all my keys/IDs which were numbers have been converted into decimal.
Ex: journal_id in my oracle table is number (ex:1234). But when I exported into OBIEE and used view data option. All the IDs(data type number) data is showing as decimal format (1234.00).
Ex: If I want to see data for check number in answers, then it is showing as 112456.00 instead of 112456.
Please anyone had this kind of issue. how to resolve?
Is there any default setting which is causing this problem.how to find?
OBIEE version : 10.1.3.2
Appreciate your help.

Hi Sandeep,
When I opened the rpd in offline mode, it is saying the repository can only be opened as Read-Only. I clicked Yes for this and entered admin user name and password. But in Physical model, when I right clicked any table, I couldnt see find any place to modify. I tried with properties also. I am not able change data type as it read-only. How to do it in offline?
FYI,
I opened rpd when OC4J was stopped. Aslo I opened when OC4J is running. But both times I am not able to change datat type.
Thanks!!

Check constraint generation in physical model in 3.1.1.

My question: Is it possible to set Use Domain Constraints ticked as default (or another way to get them in DDL) if the Domain with Check constraint is set for the column. I assume it's logical as if I bind a column to the domain then use the domain constraint as default policy. It's not a big deal if you have a few but in my case I do re-modelling just for physical model level and I have tens column in the tables based on a domain. So, I have first to set the domain as a column type and then in another screen tick Use Domain Constraints
Thank you

Hi,
Is it possible to set Use Domain Constraints ticked as default (or another way to get them in DDL) if the Domain with Check constraint is set for the column.No it's not possible I logged bug for that.
So, I have first to set the domain as a column type How do you set domain as data type? Do you have more than one columns using the same domain? In such cases you can use domain dialog (in the browser) and "Used in" page in order to assign domain to several columns/attributes at once.
You can use the script below to set use domain constraints on columns that use domain as data type
Philip
var model;
tables = model.getTableSet().toArray();
for (var t = 0; t<tables.length;t++){
table = tables[t];
columns = table.getElements();
for (var i = 0; i < columns.length; i++) {
     column = columns;
     if(column.getUse() == 0 && column.getDomain()!=null){
          if(!column.getUseDomainConstraints()){
               column.setUseDomainConstraints(true);
               table.setDirty(true);

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

How to implement more than one physical models from the same model

Hello,
We have designed a relational model for our application and now, we would like to implement it for our 4 environments: Development, Test, User-Test and Real. Each one has the same logical schema but, different physical clauses (i.e.: in development environment we will not use partitioning clauses).
Is this possible?
Thank you,
Bernat Fabregat

Hello Bernat,
yes it's possible:
1) open your design and go to Tools>"RDBMS site administration"
2) add your sites there (Current design) - Development, Test, User-Test and Real; press ok when finish
3) go to "Physical models" node in browser and use "new" from pop-up menu - your sites will appear in list
4) after you set physical objects in one model (need to save it as well)l, you can clone those objects in other models - you can clone from lower or the same database version
You can consider usage of "name substitution" functionality during DDL generation if objects should have different name (prefix) in different environment - in this there will be no need to change the name of objects in models.
Philip

Setting "Segment Templates" on tables in physical model

Similar Messages

Maybe you are looking for