For manually defined Indexes, the Index Template is applied when the Index is initially created. I suspect you may have created your Indexes before you set up the Index Template?
(For automatically generated Indexes, the Index Template values at the time of the DDL generation are used.)
thanks for your reply. After I read your answer I took my some time to experiment a little bit, therefore my reply is a little late, sorry for that.
I checked that the index template is properly defined and activated in the preferences/data modeler/model/physical/oracle.
Then I created a new model with only one table and three columns, one is the PK, the others a varchar and number.
The model specific settings are under Properties/DDL/automatic index generation to generate an index for the PK automatically.
Then I generated the DDL and the index for the PK shows up with the tablespace clause.
I added a new index on the varchar column.
I generated the DDL and the index for the PK column shows up with the tablespace clause, whereas the index for varchar column shows up without the tablespace clause.
Then I added a physical model to the relational one and in the physical model I added the tablespace which is referred to in the index template.
I generated the DDL again and now both indexes show up with the proper tablespace clause.
So to me it seems that for manually created indexes the tablespace clause is only generated when the tablespace is found in the physical model, which I think is not correct. If a tablespace clause can be generated for automatically generated indexes without a physical model it should possible also for manually created indexes.
What do you think?
Yes. You're right. For manually defined Indexes, the Index Template is applied when the Index is initially created. As these properties are held in the Physical Model, it is only effective if the relevant Physical Model is open when the Index is initially created. The Tablespace defined in the Template is only applied if the Physical Model contains a Tablespace with that name.
I guess it is a bit inconsistent that for automatically generated indexes the Tablespace clause is generated even when the Physical Model is not open.
thanks for the confirmation. If there is anything I can do so that the behaviour of the index types is unified please let me. My personnel preference would be that the manually generated index behaves the same way as automatically generated one, because like that I wouldn't need to create physical model behind.
Thanks a lot,