HD27601: NOT POSSIBLE TO MIGRATE FROM R12 TO R13 IF EV5ADM NOT I S THE SAME AS DB DICTIONARY OWNER

APAR status

• Closed as unreproducible in next release.

Error description

• Not possible to migrate from R12 to R13 if EV5Adm
  not         is the same as DB Dictionary Owner
  .
  DETAILED DESCRIPTION:
  It is not possible to migrate from R12 to R13, if you
  have different
  users for "ENOVIA Administrator", "Database
  Administrator" and "ENOVIA
  Dictionary Owner".
  Script "~/code/command/Upgrade513_Enovia.sh"
  is not
  correct. I have only tested the "standard migration"
  but it seems to be
  the same problem in the "customised migration"-
  part also. (why do you
  duplicated some of the code ?)
  .
  According to the "Online documentation" (ex.
  V5R12SP2, V5R13SP2),
  "Enterprise Architecture Installation Guide"
  and "Different Userids
  Involved When Installing ENOVIA LCA V5", is it
  NOT nessecary to have
  the "ENOVIA Administrator" and the "ENOVIA
  Dictionary Owner" as the
  same user.
  .
  The installation make it possible to have different
  users for "ENOVIA
  Administrator", "ENOVIA Dictionary Owner"
  and "DBA user name".
  .
  But it is impossible to run the migrations script if
  you have different
  users.
  .
  When checking the script we found the following:
  1. Script test if variable "AdmUsr" is the same as
  the unix-user running
  the script. This is ok.
  2. In function "ProcessDatabaseEnv", the sqlplus-
  command uses "AdmUsr",
  this will not work if "ENOVIA Dictionary Owner" is a
  different user!!
  3. In function "GENERATEDDL", "select distinct
  vmetadataname from
  ${AdmUsr}.adminid where vmetadataname not in
  ('SHEETMODE');" is
  executed.
  For this to work "AdmUsr" and "ENOVIA Dictionary
  Owner" must be the
  same.
  4. Also in "GENERATEDDL", when
  running "ENOUpgrade", "AdmUsr" is used as
  DBTablesOwner and TablesOwner. For this to
  work "AdmUsr" and "ENOVIA
  Dictionary Owner" must be the same.
  5. In function "DROPVIEWS", "AdmUsr" is also used
  instead of "ENOVIA
  Dictionary Owner". The sql will not work, if different
  userids are
  used.
  .
  .
  Step by step scenario:
  .
  1. Install V5R12, with dirrerent userids for "ENOVIA
  Administrator",
  "Database Administrator" and "ENOVIA Dictionary
  Owner".
  2. Use the migrate script in V5R13SP4
  "~/code/command/Upgrade513_Enovia.sh" to
  upgrade the V5R12
  installation.
  3. Try to put in correct parameters to the script.
  Not possible to run
  the script without errors.
  .
  .
  

Local fix

Problem summary

• Not possible to migrate from R12 to R13 if EV5Adm not         i
  s the same as DB Dictionary Owner
  Not possible to migrate from R12 to R13 if EV5Adm
  not         is the same as DB Dictionary Owner
  .
  DETAILED DESCRIPTION:
  It is not possible to migrate from R12 to R13, if you
  have different
  users for "ENOVIA Administrator", "Database
  Administrator" and "ENOVIA
  Dictionary Owner".
  Script " /code/command/Upgrade513_Enovia.sh"
  is not
  correct. I have only tested the "standard migration"
  but it seems to be
  the same problem in the "customised migration"-
  part also. (why do you
  duplicated some of the code ?)
  .
  According to the "Online documentation" (ex.
  V5R12SP2, V5R13SP2),
  "Enterprise Architecture Installation Guide"
  and "Different Userids
  Involved When Installing ENOVIA LCA V5", is it
  NOT nessecary to have
  the "ENOVIA Administrator" and the "ENOVIA
  Dictionary Owner" as the
  same user.
  .
  The installation make it possible to have different
  users for "ENOVIA
  Administrator", "ENOVIA Dictionary Owner"
  and "DBA user name".
  .
  But it is impossible to run the migrations script if
  you have different
  users.
  .
  When checking the script we found the following:
  1. Script test if variable "AdmUsr" is the same as
  the unix-user running
  the script. This is ok.
  2. In function "ProcessDatabaseEnv", the sqlplus-
  command uses "AdmUsr",
  this will not work if "ENOVIA Dictionary Owner" is a
  different user!!
  3. In function "GENERATEDDL", "select distinct
  vmetadataname from
  ${AdmUsr}.adminid where vmetadataname not in
  ('SHEETMODE');" is
  executed.
  For this to work "AdmUsr" and "ENOVIA Dictionary
  Owner" must be the
  same.
  4. Also in "GENERATEDDL", when
  running "ENOUpgrade", "AdmUsr" is used as
  DBTablesOwner and TablesOwner. For this to
  work "AdmUsr" and "ENOVIA
  Dictionary Owner" must be the same.
  5. In function "DROPVIEWS", "AdmUsr" is also used
  instead of "ENOVIA
  Dictionary Owner". The sql will not work, if different
  userids are
  used.
  .
  .
  Step by step scenario:
  .
  1. Install V5R12, with dirrerent userids for "ENOVIA
  Administrator",
  "Database Administrator" and "ENOVIA Dictionary
  Owner".
  2. Use the migrate script in V5R13SP4
  " /code/command/Upgrade513_Enovia.sh" to
  upgrade the V5R12
  installation.
  3. Try to put in correct parameters to the script.
  Not possible to run
  the script without errors.
  .
  .
  

Problem conclusion

Temporary fix

Comments

• THE PROBLEM WAS SUBMITTED ON :
  ENOVIA VERSION 5 RELEASE 13.
  THIS PROBLEM IS NOT REPRODUCIBLE ON :
  ENOVIA VERSION 5 RELEASE 15 GA level AND ON
  V5R14SP01 AND V5R13SP07.
  .
  

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

• R513 PSN SP51307

     UP04/11/05 N 1000

• R514 PSN

     UP