Local or remote instances.

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Raquel

    Local or remote instances.

    I read in the manual:

    "Instances are cataloged as either local or remote in the node
    directory."

    How is this done? How is the correspondence between nodes and instances
    defined? There is a REMOTE_INSTANCE parameter on the CATALOG NODE
    command. Is it used for this purpose?

    Here is my understanding: A server with a logical IP address of "svr"
    has two instances "inst1" (with database "db1") and "inst2" (with
    database "db2"). So, on a client, to enable access to the two instances, we
    would execute the following commands:

    CATALOG tcpip NODE node1 REMOTE svr SERVER portnum1 REMOTE_INSTANCE
    inst1
    CATALOG tcpip NODE node2 REMOTE svr SERVER portnum2 REMOTE_INSTANCE
    inst2

    Note that in the above commands, the correspondence between NODEs and
    INSTANCEs is defined. Is this the way it is done?

    And then catalog the databases that exist on those instances.

    CATALOG DATABASE db1 AS db1 AT NODE node1
    CATALOG DATABASE db2 AS db1 AT NODE node2

    Is this correct?

    In UDB Command reference, here is the description of ATTACH command:

    "Enables an application to specify the *instance* at which
    instance-level commands (CREATE DATABASE and FORCE APPLICATION, for example) are to
    be executed".

    But the syntax of ATTACH command is:

    ATTACH to *nodename*

    So, it seems that nodename and instance-name have been used
    synonymously. I am really confused....

    TIA
    Raquel.
  • Mark A

    #2
    Re: Local or remote instances.


    "Raquel" <raquel_rodrigu ezus@yahoo.com> wrote in message
    news:9a73b58d.0 312050747.59f91 5d7@posting.goo gle.com...[color=blue]
    > I read in the manual:
    >
    > "Instances are cataloged as either local or remote in the node
    > directory."
    >
    > How is this done? How is the correspondence between nodes and instances
    > defined? There is a REMOTE_INSTANCE parameter on the CATALOG NODE
    > command. Is it used for this purpose?
    >
    > Here is my understanding: A server with a logical IP address of "svr"
    > has two instances "inst1" (with database "db1") and "inst2" (with
    > database "db2"). So, on a client, to enable access to the two instances,[/color]
    we[color=blue]
    > would execute the following commands:
    >
    > CATALOG tcpip NODE node1 REMOTE svr SERVER portnum1 REMOTE_INSTANCE
    > inst1
    > CATALOG tcpip NODE node2 REMOTE svr SERVER portnum2 REMOTE_INSTANCE
    > inst2
    >
    > Note that in the above commands, the correspondence between NODEs and
    > INSTANCEs is defined. Is this the way it is done?
    >
    > And then catalog the databases that exist on those instances.
    >
    > CATALOG DATABASE db1 AS db1 AT NODE node1
    > CATALOG DATABASE db2 AS db1 AT NODE node2
    >
    > Is this correct?
    >
    > In UDB Command reference, here is the description of ATTACH command:
    >
    > "Enables an application to specify the *instance* at which
    > instance-level commands (CREATE DATABASE and FORCE APPLICATION, for[/color]
    example) are to[color=blue]
    > be executed".
    >
    > But the syntax of ATTACH command is:
    >
    > ATTACH to *nodename*
    >
    > So, it seems that nodename and instance-name have been used
    > synonymously. I am really confused....
    >
    > TIA
    > Raquel.[/color]

    The tcpip nodes really an alias for the tcpip server/instance combination.


    Comment

    Working...