IBM Support

JR33747: CHANGING "SYSTEM NAME" OR "HOSTNAME" IN CONFIG ASSISTANT FOR ONE DB IS AUTOMATICALLY ALSO UPDATING OTHER DATABASES.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Changing "System name" or "Hostname" in Config  Assistant, tab
    '6. System Options.' is causing all other db entries with the
    same original system name or hostname to be also modified to the
    new name.
    
    The scenario is this:
    
    Databases A, B, C have same system name and hostnames. Now the
    customer realized that for database C, the system name/hostname
    should be something different while A and B are correct. He
    wants to be able to modify/fix database C without changing A or
    B. He uses the Configuration Assistant to do this:
    right click on database C and change the system name/hostname
    however it changes ALL databases: A,B and C. He only wants to
    change C.
    
    Two related problems observed:
    
    - changing the System Name and hostname in CA for one
    db causes all dbs with the same original System Name and/or
    hostname to be also changed which may not be desirable if this
    is correct for some of the dbs but incorrect for others.
    
    - changing just the hostname for one db will cause all other dbs
    with the same System Name to be also updated to the new
    hostname. this again is not always desirable.
    

Local fix

  • none
    defect = wsdbu00544926, module = ca
    

Problem summary

  • Users Affected: All Users
    
    Problem Description:
    Changing "System name" or "Hostname" in Config  Assistant, tab
    '6. System Options.' is causing all other db entries with the
    same original system name or hostname to be also modified to the
    new name.
    
    
    Problem Summary:
    Changing "System name" or "Hostname" in Config  Assistant, tab
    '6. System Options.' is causing all other db entries with the
    same original system name or hostname to be also modified to the
    new name.
    
    The scenario is this:
    
    Databases A, B, C have same system name and hostnames. Now the
    customer realized that for database C, the system name/hostname
    should be something different while A and B are correct. He
    wants to be able to modify/fix database C without changing A or
    B. He uses the Configuration Assistant to do this:
    right click on database C and change the system name/hostname
    however it changes ALL databases: A,B and C. He only wants to
    change C.
    
    Two related problems observed:
    
    - changing the System Name and hostname in CA for one
    db causes all dbs with the same original System Name and/or
    hostname to be also changed which may not be desirable if this
    is correct for some of the dbs but incorrect for others.
    
    - changing just the hostname for one db will cause all other dbs
    with the same System Name to be also updated to the new
    hostname. this again is not always desirable.
    

Problem conclusion

  • 'First fixed in DB2 UDB Version 9.1, FixPak 8'
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR33747

  • Reported component name

    DB2 CEE WINDOWS

  • Reported component ID

    5765F3001

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-21

  • Closed date

    2009-07-21

  • Last modified date

    2009-07-21

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

    JR28201

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

Fix information

  • Fixed component name

    DB2 CEE WINDOWS

  • Fixed component ID

    5765F3001

Applicable component levels

  • R910 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
12 October 2021