JR35419: PROBLEMS IMPORTING METADATA FOR ADDITIONAL COLUMNS INTO EXISTING TABLES IN IA 8.1 USING IMPORT EXPORT MANAGER

APAR status

• Closed as fixed if next.

Error description

• If I import additional tables using the same host system name
  [FEDERATED SERVER PRODUCTION] and same database name [General
  Discovery] and same schema name [DB2ADMIN]:
  1. The tables are imported into the repository under the correct
  host system name.
  2. The import creates a new copy of the database name in the
  repository.
  3. The tables do not appear in IA (only the original tables
  appear in IA)
  4. However -- on shut down and restart of the IA client, the
  original tables do not appear in IA but the new tables do.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users importing metadata using Import Export manager and using
  IA client to concurrently view the imported metadata.
  ****************************************************************
  PROBLEM DESCRIPTION:
  If additional tables are imported using an existing host name,
  database name and schema name
  1. The tables are imported into the repository under the
  correcthost system name.
  2. The import creates a new copy of the database name in the
  repository.
  3. The new tables do not appear in IA (only the original tables
  appear in IA)
  4. However -- on shut down and restart of the IA client, the
  original tables do not appear in IA but the new tables do.
  
  This is a variation of the behavior described in APAR JR35333
  ****************************************************************
  RECOMMENDATION:
  rejected as a Duplicate
  ****************************************************************
  

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

• R810 PSN

     UP