JR40389: Problem importing Oracle metadata via Information Analyzer

APAR status

• Closed as program error.

Error description

• Problem importing Oracle metadata via InformationAnalyzer
  8.5.0.1.
  ImportErrorSt E   2 imported objects of type
  "http:///4.0/ASCLModel.ecoreKeyComponent" have the identity
  

Local fix

• N/A
  

Problem summary

• Users Affected:
  Users affected include those who wish to import table
  definitions and other metadata with Oracle Connector where
  multiple tables exist with same key name, perhaps in different
  schemas.
  
  Problem Description:
  Attempts to import table definitions via InformationAnalyzer
  fail due to multiple keys named the same in different tables or
  in different schemas. This could also happen for metadata import
  in DataStage Designer Client using Connector Import Wizard and
  selecting all possible views and keys.
  

Problem conclusion

• Problem Conclusion:
  The SELECT statements used to obtain information from Oracle
  about tables, views, keys, etc are now fully qualified with
  schema name.
  Apply the Oracle Connector patch JR40389 after applying the
  Connector Access Service (CAS) patch JR39952.
  

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

  WIS INFORM ANAL

• Fixed component ID

  5724Q36IA

Applicable component levels

• R811 PSY

     UP

• R812 PSY

     UP

• R850 PSY

     UP

• R870 PSY

     UP