SQL Developer Data Modeler

Hello

My goal is to synchronize partition elements on tables via both ways

-> synchronize data dictionary (database) with model (data modeler)

<- synchronize model (data modeler) with data dictionary (database)

To contextualize, I use the latest version of the tool (OSDDM 18.3) and I have the following model structure

Logical model

Relational model: R1                           

Table: schema1.table1

Physical model: DEV

Table: schema1.table1

               Physical model: DEV is a physical model based on my own RDBMS site I edited first and call it DEV and relates it to an Oracle database 11g database type as the distant database is an Oracle database 11g version

To reach my goal, I use the dedicated synchronize functionalities offered by OSDDM but I notice the following issues when using them

Issue 1: -> synchronize data dictionary (database) with model (data modeler)

When I want to synchronize the partition elements of the table schema1.table1 located in the data dictionary (database) with the definition of the Physical model: DEV, the system doesn’t create the partition statements in the alter ddl script.

So I can't synchronize data dictionary (database) with my Physical model: DEV

Issue 2: <- synchronize model (data modeler) with data dictionary (database)

When I want to synchronize the partition elements of the table schema1.table1 located in the Physical model: DEV with the definition of the data dictionary (database), the system creates a completely new physical model called Oracle database 11g that includes the table schema1.table1

After this action, the model structure resulting is

Logical model

Relational model: R1

Table: schema1.table1

Physical model: DEV

Table: schema1.table1 (not updated with partition from data dictionary)

Physical model: Oracle database 11g

Table: schema1.table1 (updated with partition from data dictionary)

So I can't synchronize my Physical model: DEV based on my own RDBMS site DEV with data dictionary (database)

Issue 3:

On the other hand after obtain the new physical Physical model: Oracle database 11g model (see issue 2) the data dictionary (database) can be synchronize with change that occurs in it exclusively

After all, OSDDM seems affected as follow

1. Use our own RDBMS site to identify specifically our Physical models has no effect when using synchronize functionalities
2. The system creates a default physical model when using functionality <- synchronize model (data modeler) with data dictionary (database)

My question are the following according to the actual way the system working

1. Is issue 1 and issue 2 are bugs ?
2. Is the default physical model created when synchronize model (data modeler) with data dictionary (database) (see issue 2) is based on the version of distant databases ?

       E.g.

• if distant database = Oracle database 11g then physical model realates about Oracle database 11g database type
• if distant database = Oracle database 12cR2 then physical model realates about Oracle database 12cR2 database type

Thanks for your answers