IV29629: TADDM IMPORT FROM ORACLE DATABASE TAKING EXCESSIVELY LONG

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Problem title
    
    TADDM to TBSM Bulk load performance is slow
    .
    Problem description
    We are working with Jeff Ferla on this.  He was on site at our
    location
    this past Monday and Tuesday (9/24 & 25).
    
    Jeff feels that the 5 hours it took (down from 12 hours) is not
    what it
    should be.
    
    Jeff is investigating other customer experiences like ours here
    at
    Cigna that use Oracle DB's in their TADDM environments.
    
    Both TADDM and TBSM are running RHEL 5.5, but TADDM is an Oracle
    DB,
    and TBSM is DB2.
    .
    Business impact ( BusImpact )
    Impacting development of TBSM 6.1 in our environment.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All TBSM Users                                               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Importing data from an Oracle TADDM database is taking       *
    * excessively long.                                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * TADDM 7.2.1 switched to using NRS for naming. The NRS table  *
    * defined the columns holding the GUIDs at type raw, where as  *
    * earlier                                                      *
    * releases of TADDM had the columns as String.  The query to   *
    * the aliases table needed to convert the string GUIDs         *
    * specified in the                                             *
    * IN() clause to raw.  Passing in strings on the IN() clause   *
    * resulted in Oracle converting performing the conversion      *
    * internally in a very                                         *
    * non-optimal manner. This has now been rectified.             *
    ****************************************************************
    Review of the GTMCL5328I message in the traceGTM_XT.log.0 shows
    most of the time was spent retrieving the aliases.
    

Problem conclusion

  • The fix for this APAR is contained in the following
    maintenance packages:
    |Interim Fix | 6.1.0.1-TIV-BSM-IF0003
    |Fix Pack | 6.1.0-TIV-BSM-FP0002
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV29629

  • Reported component name

    TIV BUS SERV MG

  • Reported component ID

    5724C5100

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-08

  • Closed date

    2012-10-15

  • Last modified date

    2013-02-14

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • UNKNOWN
    

Fix information

  • Fixed component name

    TIV BUS SERV MG

  • Fixed component ID

    5724C5100

Applicable component levels

  • R610 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Business Service Manager

Software version:

610

Reference #:

IV29629

Modified date:

2013-02-14

Translate my page

Machine Translation

Content navigation