PM95792: Build Forge 8.0 upgrade under DB2 fails database test if schema name different from database name

Rational Build Forge Fix Pack 1 (8.0.0.1) for 8.0
Rational Build Forge Fix Pack 2 (8.0.0.2) for 8.0
Rational Build Forge Interim Fix 3 for 8.0.0.2
Rational Build Forge Fix Pack 3 (8.0.0.3) for 8.0
Rational Build Forge Fix Pack 4 (8.0.0.4) for 8.0
Rational Build Forge Fix Pack 5 (8.0.0.5) for 8.0
Rational Build Forge Fix Pack 6 (8.0.0.6) for 8.0
Rational Build Forge Fix Pack 7 (8.0.0.7) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.2
Rational Build Forge Fix Pack 8 (8.0.0.8) for 8.0
Rational Build Forge Fix Pack 9 (8.0.0.9) for 8.0
Rational Build Forge Fix Pack 10 (8.0.0.10) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.10
Rational Build Forge Fix Pack 11 (8.0.0.11) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.11
Rational Build Forge Fix Pack 12 (8.0.0.12) for 8.0
Rational Build Forge Fix Pack 13 (8.0.0.13) for 8.0
Rational Build Forge Fix Pack 14 (8.0.0.14) for 8.0
Rational Build Forge Fix Pack 15 (8.0.0.15) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.15
Rational Build Forge Fix Pack 16 (8.0.0.16) for 8.0
Rational Build Forge Fix Pack 17 (8.0.0.17) for 8.0
Rational Build Forge Fix Pack 19 (8.0.0.19) for 8.0
Rational Build Forge Fix Pack 18 (8.0.0.18) for 8.0
Rational Build Forge Fix Pack 20 (8.0.0.20) for 8.0
Rational Build Forge Fix Pack 21 (8.0.0.21) for 8.0
Rational Build Forge Fix Pack 22 (8.0.0.22) for 8.0

APAR status

• Closed as program error.

Error description

• During the attempt to upgrade to Build Forge 8.0 with DB2
  database backend, the database test will fail with the following
  error if the schema name is different from the database name.
  
  ERROR[1]:Database Schema name: This schema name is invalid.
  Schema names are case sensitive, please be certain that your
  schema name is [database name]
  
  Steps to reproduce:
  
  - Create a pre-8.0 Build Forge installation with DB2 database
  using a schema name different from the database name.
  
  Expected result:
  
  Database test should complete without issue.
  
  Actual result:
  
  Database test fails indicating the schema name is invalid, but
  listing the database name instead.
  
  Workaround:
  
  Generate alias for the Build Forge tables against the schema to
  match the database name.
  The following will generated the queries needed to create the
  table alias, which can be used to script the table alias
  queries.
  
  SELECT 'CREATE ALIAS ?dbname?.' || NAME || ' FOR ?dbschema?.' ||
  NAME FROM SYSIBM.SYSTABLES WHERE CREATOR = '?dbschema?'
  
  ie:
  SELECT 'CREATE ALIAS BUILD.' || NAME || ' FOR BFSCHMA.' || NAME
  FROM SYSIBM.SYSTABLES WHERE CREATOR = 'BFSCHMA'
  

Local fix

Problem summary

• The installer will read the schema name properly when upgrading
  

Problem conclusion

• The installer will read the schema name properly when upgrading
  Fixed in 8.0.0.1
  

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

• Fixed component name

  BUILD FORGE EE

• Fixed component ID

  5724S2702

Applicable component levels

• R713 PSY

     UP