PK89976: PHYSICAL TO LOGICAL CONVERSION LOSES QUALIFIERS FOR INVALID TYPES

APAR status

• Closed as fixed if next.

Error description

• CR ID# 51509
  
  Environment: Windows XP
  
  SA Version: 10.8
  
  Description: In SA, conversion of Physical Data Model diagram
  named <Location> to Logical Data Model diagram does not copy the
  ?Qualifiers? values onto the newly created Logical Data Model.
  --------------------------
  
  Expected Result: Conversion of Physical Data Model diagram
  <Location> to Logical Data Model diagram should copy exactly the
  same values for all the properties of the Physical Data Model
  diagram onto the new Logical Data Model diagram.
  
  Actual Result: Currently, after converting and comparing the
  Physical Data Model <Location> to Logical Data Model it is found
  that the values of the ?Qualifiers? is not copied onto the newly
  created Logical Data Model diagram.
  
  Reproducible: - Yes
  
  Steps to Reproduce:-
  ?Restore the encyclopedia backup in SAEM
  ?Launch SA and open the Physical Data Model diagram named
  <Location>
  ?Go to Dictionary>Create Data Mode>Logical Data Model
  ?Under the ?Create Logical Model? window keep the collision
  options as default. (i.e. select ?Create New?).
  ?Click OK
  ?When prompted, select the DBMS option as SQL Server 2005.
  ?Once the Logical Data Model diagram is created, compare any two
  symbol properties and it is found that the ?Qualifiers? values
  are not copied onto the Logical Data Model diagram.
  
  Support Observation: Client mentioned that while creating the
  Physical Data Model the DBMS used was "MS Access". Now they are
  trying to convert the Physical Data Models to the Logical Data
  Models with the DBMS option as SQL Server 2005.
  It is possible to manually check all the qualifiers values, but
  that does not seem to be a feasible option as the client has
  huge amount of data to change manually.
  
  We also observed that irrespective of the collision options
  selection (i.e. Overwrite) the ?Qualifiers? does not get copied
  onto the Logical Data Model diagram. Also, keeping the DBMS
  option same i.e. MS Access did not help to get past the issue.
  
  Please refer to the attached files for the further investigation
  and suggest on this.
  

Local fix

• No known workaround
  

Problem summary

• A testFix was provided to the customer.
  

Problem conclusion

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• RB30 PSY

     UP