IV30808: VMOTION CHANGES ARE NOT REFLECTED IN TBSM

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as documentation error.

Error description

  • VMotion changes are not reflected in TBSM.  A recent import from
    TADDM finished successfully and invalidation of the Imported
    Business Service does not update the relationships associated
    with the virtual system.
    

Local fix

  • To correct this:
    
    - stop the TBSM data server.  It is important that the data
    server is stopped because we are going to update the database
    and we do not want the in memory model different than the
    database.
    - cd $TBSM_HOME/XMLtoolkit/bin
    - ./dumpsql.sh -t DB2 -s db-cleanup.sql
    - cd $TBSM_HOME/XMLtoolkit/log/DB2
    - take db-cleanup.sql and run each line individually.   This can
    be done from the DB2 Control Center or another equivalent query
    analyzer.
    - start the TBSM data server
    - invalidate the Imported Business Service
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All TBSM Discovery Library Toolkit Users                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * An import from TADDM finished successfully, but invalidation *
    * of the Imported Business Service does not update service     *
    * relationships.                                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Add 1 new sub sections to section Discovery Library toolkit  *
    * issues.                                                      *
    ****************************************************************
    

Problem conclusion

  • Text below will be included in next Refresh of TBSM 610
    documentation.
    
    Problem
    
    Relationship change in TADDM is not reflected in TBSM after
    import.
    
    Symptom
    
    A re-import of moved resources from TADDM is not reflected in
    the TBSM Service Tree.
    
    Cause
    
    The above issue can be seen if the TBSM Service Model is
    corrupted in the TBSM database. A fix has been delivered in
    6.1.0-TIV-BSM-FP0001 to address a TBSM database corruption issue
    (see APAR IV15748). However, if the relationships are already
    corrupted, the TADDM import will not update relationships.
    
    Resolving the problem
    
    To fix the relationships complete the following steps:
    1. Stop the TBSM data server.  It is important that the data
    server is stopped to ensure the in-memory model is not different
    to the database model.
    2. cd $TBSM_HOME/XMLtoolkit/bin
    3. Run the following script
      ./dumpsql.sh -t DB2 -s db-cleanup.sql
    4. cd $TBSM_HOME/XMLtoolkit/log/DB2
    5. Using db-cleanup.sql, run each line within the file
    individually.   This can be done from the DB2 Control Center or
    another equivalent query analyzer.
    6. Start the TBSM data server
    7. Invalidate the Imported Business Service to trigger the ESDA
    and fix the relationships.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IV30808

  • Reported component name

    TIV BUS SERV MG

  • Reported component ID

    5724C5100

  • Reported release

    610

  • Status

    CLOSED DOC

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-10-24

  • Closed date

    2012-11-12

  • Last modified date

    2012-11-12

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

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

Publications Referenced
GI11805708        

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Business Service Manager

Software version:

610

Reference #:

IV30808

Modified date:

2012-11-12

Translate my page

Machine Translation

Content navigation