UNCATALOG/CATALOG

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • maricel
    #1

    UNCATALOG/CATALOG

    Could somebody confirm the behavior of UNCATALOG & CATALOG command based on
    the following situation:

    There are two NODES on DB2 UDB v8.1, MYNODEA & MYNODEB. MYNODEA has two
    databases proda & prodb & MYNODEB has an alias database dbload - catalog
    from proda initially. Three end-users are currently connected to dbload.

    NODE MYNODEA:
    Databases:
    PRODA
    PRODB
    NODE MYNODEB
    DBLOAD (PRODA) (catalog from proda)


    users connected to DBLOAD:

    user1 - currently processing long running query
    user2 - connected to DBLOAD doing nothing
    user3 - connected to DBLOAD doing nothing

    What will happen to these end-users after the following command is issued:
    UNCATALOG DATABASE DBLOAD;
    CATALOG DB PRODB AS DBLOAD AT NODE MYNODE;

    Questions:
    1) Is the query processing run by USER1 will stop?
    2) What will happen to USER1, is it going to be disconnected?
    3) What will happen to USER1 & USER2, are they automatically disconnected as
    well & if they run queries after UNCATALOGing the DBLOAD, can they still run
    the query & which database they are pointing to?


    Your help would be highly appreciated.


    maricel.









    Tags: None
    • Knut Stolze
      #2
      Re: UNCATALOG/CATALOG

      maricel <maricel@xtra.c o.nz> wrote:
      [color=blue]
      > Could somebody confirm the behavior of UNCATALOG & CATALOG command based
      > on the following situation:
      >
      > There are two NODES on DB2 UDB v8.1, MYNODEA & MYNODEB. MYNODEA has two
      > databases proda & prodb & MYNODEB has an alias database dbload - catalog
      > from proda initially. Three end-users are currently connected to dbload.
      >
      > NODE MYNODEA:
      > Databases:
      > PRODA
      > PRODB
      > NODE MYNODEB
      > DBLOAD (PRODA) (catalog from proda)
      >
      >
      > users connected to DBLOAD:
      >
      > user1 - currently processing long running query
      > user2 - connected to DBLOAD doing nothing
      > user3 - connected to DBLOAD doing nothing
      >
      > What will happen to these end-users after the following command is issued:
      > UNCATALOG DATABASE DBLOAD;
      > CATALOG DB PRODB AS DBLOAD AT NODE MYNODE;[/color]

      Nothing. They are still connected to PRODA.
      [color=blue]
      > Questions:
      > 1) Is the query processing run by USER1 will stop?[/color]

      No.
      [color=blue]
      > 2) What will happen to USER1, is it going to be disconnected?[/color]

      No.
      [color=blue]
      > 3) What will happen to USER1 & USER2, are they automatically disconnected
      > as well & if they run queries after UNCATALOGing the DBLOAD, can they
      > still run the query & which database they are pointing to?[/color]

      They stay connected and run their queries against PRODA.

      The db2agent processes that act on behalf of your users have the directory
      information cached. The cache is not changed on the fly.

      --
      Knut Stolze
      Information Integration
      IBM Germany / University of Jena

        Comment

        • maricel
          #3
          Re: UNCATALOG/CATALOG

          Thanks for this info.
          How are you going to re-direct those currently connected users to point to
          the new database?
          Is there a mechanism to update their directory cache to point to PRODB on
          the fly?

          Many Thanks,
          maricel

          "Knut Stolze" <stolze@de.ibm. com> wrote in message
          news:c0fane$uf7 $1@fsuj29.rz.un i-jena.de...[color=blue]
          > maricel <maricel@xtra.c o.nz> wrote:
          >[color=green]
          > > Could somebody confirm the behavior of UNCATALOG & CATALOG command based
          > > on the following situation:
          > >
          > > There are two NODES on DB2 UDB v8.1, MYNODEA & MYNODEB. MYNODEA has two
          > > databases proda & prodb & MYNODEB has an alias database dbload - catalog
          > > from proda initially. Three end-users are currently connected to dbload.
          > >
          > > NODE MYNODEA:
          > > Databases:
          > > PRODA
          > > PRODB
          > > NODE MYNODEB
          > > DBLOAD (PRODA) (catalog from proda)
          > >
          > >
          > > users connected to DBLOAD:
          > >
          > > user1 - currently processing long running query
          > > user2 - connected to DBLOAD doing nothing
          > > user3 - connected to DBLOAD doing nothing
          > >
          > > What will happen to these end-users after the following command is[/color][/color]
          issued:[color=blue][color=green]
          > > UNCATALOG DATABASE DBLOAD;
          > > CATALOG DB PRODB AS DBLOAD AT NODE MYNODE;[/color]
          >
          > Nothing. They are still connected to PRODA.
          >[color=green]
          > > Questions:
          > > 1) Is the query processing run by USER1 will stop?[/color]
          >
          > No.
          >[color=green]
          > > 2) What will happen to USER1, is it going to be disconnected?[/color]
          >
          > No.
          >[color=green]
          > > 3) What will happen to USER1 & USER2, are they automatically[/color][/color]
          disconnected[color=blue][color=green]
          > > as well & if they run queries after UNCATALOGing the DBLOAD, can they
          > > still run the query & which database they are pointing to?[/color]
          >
          > They stay connected and run their queries against PRODA.
          >
          > The db2agent processes that act on behalf of your users have the directory
          > information cached. The cache is not changed on the fly.
          >
          > --
          > Knut Stolze
          > Information Integration
          > IBM Germany / University of Jena[/color]


            Comment

            • Pierre Saint-Jacques
              #4
              Re: UNCATALOG/CATALOG

              If you do not want to have to update any client files, then you will have to
              work from MYNODEB. Make sure that on MYNODEB, the instance that owns DBLOAD
              is active.
              Beacuase DBLOAD is the alias of PRODA it means that MYNODEA is already
              identified to MYNOEDB
              UNCATALOG DATABASE DBLOAD
              CATALOG DATABASE PRODB AS DBLOAD AT NODE MYNODEA

              As these execute, whoever was connected to PRODA via DBLOAD will stay there
              until they connect reset,
              I believe that for the new connection requests, instead of reading the
              cache, the instance will realize that the file has been changed and the new
              connection requests should go to to PRODB via DBLOAD.

              To ensure that it is the case, if you can afford it, stop/start the
              instance. If not, and you're on V*, look at using the QUIESCE command at
              either/or the instance or db level.
              HTH, Pierre.
              "maricel" <maricel@xtra.c o.nz> a écrit dans le message de
              news:qn0Xb.4297 8$9k7.887157@ne ws.xtra.co.nz.. .[color=blue]
              > Thanks for this info.
              > How are you going to re-direct those currently connected users to point to
              > the new database?
              > Is there a mechanism to update their directory cache to point to PRODB on
              > the fly?
              >
              > Many Thanks,
              > maricel
              >
              > "Knut Stolze" <stolze@de.ibm. com> wrote in message
              > news:c0fane$uf7 $1@fsuj29.rz.un i-jena.de...[color=green]
              > > maricel <maricel@xtra.c o.nz> wrote:
              > >[color=darkred]
              > > > Could somebody confirm the behavior of UNCATALOG & CATALOG command[/color][/color][/color]
              based[color=blue][color=green][color=darkred]
              > > > on the following situation:
              > > >
              > > > There are two NODES on DB2 UDB v8.1, MYNODEA & MYNODEB. MYNODEA has[/color][/color][/color]
              two[color=blue][color=green][color=darkred]
              > > > databases proda & prodb & MYNODEB has an alias database dbload -[/color][/color][/color]
              catalog[color=blue][color=green][color=darkred]
              > > > from proda initially. Three end-users are currently connected to[/color][/color][/color]
              dbload.[color=blue][color=green][color=darkred]
              > > >
              > > > NODE MYNODEA:
              > > > Databases:
              > > > PRODA
              > > > PRODB
              > > > NODE MYNODEB
              > > > DBLOAD (PRODA) (catalog from proda)
              > > >
              > > >
              > > > users connected to DBLOAD:
              > > >
              > > > user1 - currently processing long running query
              > > > user2 - connected to DBLOAD doing nothing
              > > > user3 - connected to DBLOAD doing nothing
              > > >
              > > > What will happen to these end-users after the following command is[/color][/color]
              > issued:[color=green][color=darkred]
              > > > UNCATALOG DATABASE DBLOAD;
              > > > CATALOG DB PRODB AS DBLOAD AT NODE MYNODE;[/color]
              > >
              > > Nothing. They are still connected to PRODA.
              > >[color=darkred]
              > > > Questions:
              > > > 1) Is the query processing run by USER1 will stop?[/color]
              > >
              > > No.
              > >[color=darkred]
              > > > 2) What will happen to USER1, is it going to be disconnected?[/color]
              > >
              > > No.
              > >[color=darkred]
              > > > 3) What will happen to USER1 & USER2, are they automatically[/color][/color]
              > disconnected[color=green][color=darkred]
              > > > as well & if they run queries after UNCATALOGing the DBLOAD, can they
              > > > still run the query & which database they are pointing to?[/color]
              > >
              > > They stay connected and run their queries against PRODA.
              > >
              > > The db2agent processes that act on behalf of your users have the[/color][/color]
              directory[color=blue][color=green]
              > > information cached. The cache is not changed on the fly.
              > >
              > > --
              > > Knut Stolze
              > > Information Integration
              > > IBM Germany / University of Jena[/color]
              >
              >[/color]

                Comment

                Previous template Next
                Working...