IBM Support

JR39952: RE-IMPORTING THE TABLES AFTER REMOVING THE PRIMARY KEY FROM THE SOURCE DATABASE FAILS DUE TO LOWER BOUND CONSTRAINT VIOLATION.

 

APAR status

  • Closed as program error.

Error description

  • If a table is imported through IA console and the table has a
    primary
    key, then CA is run against table, then the table modified by
    removing
    the primary key, then the table is attempted to reimport, the
    reimport
    fails.
    

Local fix

Problem summary

  • 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

  • The SELECT statements used to obtain information from Oracle
    about tables, views, keys, etc are now fully qualified with
    schema name.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR39952

  • Reported component name

    WIS INFORM ANAL

  • Reported component ID

    5724Q36IA

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-06-28

  • Closed date

    2011-11-29

  • Last modified date

    2011-11-29

  • 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

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSZJLG","label":"InfoSphere Information Analyzer"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5"}]

Document Information

Modified date:
12 October 2021