Control Center problems

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • kooltop@hotmail.com

    Control Center problems


    Server: DB2 LUW 9.5 on Solaris 10
    Client: DB2 Data Server Client 9.5 (= Control Center) on a Win XP
    SP2

    Problems:

    (1) Tools --Wizards -- "Backup Wizard" and press OK. In the
    next pop-up window I see all available
    systems correctly listed, but selecting any system won't
    display that system's instances and databases.
    The two boxes on the right side of of the SYSTEMS window remain
    empty no matter what I do.

    *** Note: The DAS (administration server) is up, and the 3
    config files are as follows:

    - In DBM CFG, the DISCOVER parameter is currently set to
    "SEARCH"
    - In DB CFG, the DISCOVER_DB parameter is currently set to
    "ENABLE"
    - In ADMIN (DAS) CFG, the DISCOVER parameter is currently
    set to "SEARCH"



    (2) OK, now I try in a different way... I right-mouse click on the
    database, select "Configure Automatic
    Maintenance" and I get the hour-glass for the next 5-10-15
    minutes... The system never comes back
    and eventually I have to kill the control center if I want to
    regain control.


    Any ideas on why this is not working as intended ? perhaps there is a
    fix that I need to apply ? I have
    installed V9.5 but I'm not aware of any fixes available.

    Thanks,
    Orlando



  • Mark A

    #2
    Re: Control Center problems

    <kooltop@hotmai l.comwrote in message
    news:139ac5b9-0972-437a-a1aa-e49e885f9811@f3 6g2000hsa.googl egroups.com...
    >
    Server: DB2 LUW 9.5 on Solaris 10
    Client: DB2 Data Server Client 9.5 (= Control Center) on a Win XP
    SP2
    >
    Problems:
    >
    (1) Tools --Wizards -- "Backup Wizard" and press OK. In the
    next pop-up window I see all available
    systems correctly listed, but selecting any system won't
    display that system's instances and databases.
    The two boxes on the right side of of the SYSTEMS window remain
    empty no matter what I do.
    >
    *** Note: The DAS (administration server) is up, and the 3
    config files are as follows:
    >
    - In DBM CFG, the DISCOVER parameter is currently set to
    "SEARCH"
    - In DB CFG, the DISCOVER_DB parameter is currently set to
    "ENABLE"
    - In ADMIN (DAS) CFG, the DISCOVER parameter is currently
    set to "SEARCH"
    >
    >
    >
    (2) OK, now I try in a different way... I right-mouse click on the
    database, select "Configure Automatic
    Maintenance" and I get the hour-glass for the next 5-10-15
    minutes... The system never comes back
    and eventually I have to kill the control center if I want to
    regain control.
    >
    >
    Any ideas on why this is not working as intended ? perhaps there is a
    fix that I need to apply ? I have
    installed V9.5 but I'm not aware of any fixes available.
    >
    Thanks,
    Orlando
    You need to catalog the remote node and the database first on your Windows
    workstation. You can do this via the command line (catalog tcpip node,
    catalog database in Command Reference Manual) or try the Configuration
    Assistant GUI. The discover does not always work, so make sure you have the
    host name, port number (default is 50000) and database name. Make sure you
    use "authentica tion server" parm in the catalog database.

    Automatic maintenance requires a TOOLSDB or TOOLS schema be created and I
    believe that the Administrative Server must be active.


    Comment

    • thatdbaCLK

      #3
      Re: Control Center problems

      On Jul 22, 4:37 pm, "Mark A" <nob...@nowhere .comwrote:
      <kool...@hotmai l.comwrote in message
      >
      news:139ac5b9-0972-437a-a1aa-e49e885f9811@f3 6g2000hsa.googl egroups.com...
      >
      >
      >
      >
      >
      >
      >
      Server:   DB2 LUW 9.5 on Solaris 10
      Client:    DB2 Data Server Client 9.5  (= Control Center) on a Win XP
      SP2
      >
      Problems:
      >
      (1)  Tools --Wizards  -- "Backup Wizard" and press OK.  In the
      next pop-up window I see all available
           systems correctly listed,  but selecting any system won't
      display that system's instances and databases.
           The two boxes on the right side of of the SYSTEMS window remain
      empty no matter what I do.
      >
           *** Note: The DAS  (administration server) is up,  and the 3
      config files are as follows:
      >
               - In DBM CFG,  the DISCOVER parameter is currentlyset to
      "SEARCH"
               - In DB CFG,  the DISCOVER_DB  parameter is currently set to
      "ENABLE"
               - In ADMIN (DAS) CFG,  the DISCOVER parameter is currently
      set to "SEARCH"
      >
      (2)  OK, now I try in a different way...  I right-mouse click on the
      database,  select  "Configure Automatic
           Maintenance"  and I get the hour-glass for the next  5-10-15
      minutes...  The system never comes back
           and eventually I have to kill the control center if I want to
      regain control.
      >
      Any ideas on why this is not working as intended ?  perhaps there is a
      fix that I need to apply ?  I have
      installed V9.5  but I'm not aware of any fixes available.
      >
      Thanks,
      Orlando
      >
      You need to catalog the remote node and the database first on your Windows
      workstation. You can do this via the command line (catalog tcpip node,
      catalog database in Command Reference Manual) or try the Configuration
      Assistant GUI. The discover does not always work, so make sure you have the
      host name, port number (default is 50000) and database name. Make sure you
      use "authentica tion server" parm in the catalog database.
      >
      Automatic maintenance requires a TOOLSDB or TOOLS schema be created and I
      believe that the Administrative Server must be active.- Hide quoted text -
      >
      - Show quoted text -
      Yes the ADMIN (DAS) should be activated! Some folks thinks its not
      important but will find out having DAS down kills a lot of
      communitication !

      Comment

      Working...