HD56946: EXTRANEOUS LINKS ARE POPULATING THE DATABASE FOR PRODUCT SPEC S

APAR status

• Closed as unreproducible in next release.

Error description

• Extraneous Links are populating the database for
  Product Specs.
  .
  Pre-requisites for replaying the scenario - none
  Settings/RunTime Flags/VPM Settings-
  Portal setting :
  Create configured part reference = TRUE
  .
  Abstract :
  Extraneous Links are populating the database for
  Product Specs.
  .
  Steps To Reproduce:
  1. Create a Category of type Product with 4
  product Specifications attached to it.
  .
  2. Open a PRC ProdSpec1, which has the same
  name as the product spec which has three Parts
  and then configure them.
  .
  Query the database for the SPECLNK and CATLNK
  returns the following:
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 56
  Category Link Count: select count (*) from
  schema.CATLNK Result: 14
  .
  3. Add a Part to the PRC:
  .
  Query the database for the SPECLNK and CATLNK
  returns the following:
  .
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 60
  Category Link Count: select count (*) from
  schema.CATLNK Result: 15
  .
  The SPECLNK s are growing for each Configured
  Part by the number of Product Specifications.
  .
  Some more links have been added such that there
  is now another Product Specification.
  .
  The query of the database yields:
  .
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 93
  Category Link Count: select count (*) from
  schema.CATLNK Result: 21
  .
  Add another Product Specification:
  .
  Query the database for the SPECLNK and CATLNK
  returns the following:
  .
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 97
  Category Link Count: select count (*) from
  schema.CATLNK Result: 21
  .
  Add another Part to PRC ProdSpec1:
  .
  Now, the query reveals:
  .
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 103
  Category Link Count: select count (*) from
  schema.CATLNK Result: 22
  .
  

Local fix

Problem summary

• Extraneous Links are populating the database for Product Spec s
  Extraneous Links are populating the database for
  Product Specs.
  .
  Pre-requisites for replaying the scenario - none
  Settings/RunTime Flags/VPM Settings-
  Portal setting :
  Create configured part reference = TRUE
  .
  Abstract :
  Extraneous Links are populating the database for
  Product Specs.
  .
  Steps To Reproduce:
  1. Create a Category of type Product with 4
  product Specifications attached to it.
  .
  2. Open a PRC ProdSpec1, which has the same
  name as the product spec which has three Parts
  and then configure them.
  .
  Query the database for the SPECLNK and CATLNK
  returns the following:
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 56
  Category Link Count: select count (*) from
  schema.CATLNK Result: 14
  .
  3. Add a Part to the PRC:
  .
  Query the database for the SPECLNK and CATLNK
  returns the following:
  .
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 60
  Category Link Count: select count (*) from
  schema.CATLNK Result: 15
  .
  The SPECLNK s are growing for each Configured
  Part by the number of Product Specifications.
  .
  Some more links have been added such that there
  is now another Product Specification.
  .
  The query of the database yields:
  .
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 93
  Category Link Count: select count (*) from
  schema.CATLNK Result: 21
  .
  Add another Product Specification:
  .
  Query the database for the SPECLNK and CATLNK
  returns the following:
  .
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 97
  Category Link Count: select count (*) from
  schema.CATLNK Result: 21
  .
  Add another Part to PRC ProdSpec1:
  .
  Now, the query reveals:
  .
  Specification Link Count: select count (*) from
  schema.SPECLNK Result: 103
  Category Link Count: select count (*) from
  schema.CATLNK Result: 22
  .
  

Problem conclusion

Temporary fix

Comments

• THE PROBLEM WAS SUBMITTED ON :
  ENOVIA VERSION 5 RELEASE 16.
  THIS PROBLEM IS NOT REPRODUCIBLE ON :
  ENOVIA VERSION 5 RELEASE 18 GA level AND ON
  V5R17SP02 AND V5R16SP08.
  .
  

APAR Information

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

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

Fix information

• Fixed component name

  ENOVIA LCA AIX

• Fixed component ID

  569101700

Applicable component levels

• R516 PSN

     UP

• R517 PSN SP51702

     UP06/10/24 I 1000