Re: Sharing tables from multiple instances ?

You have two obvious options.

1. One database to hold the ZIP code table (why are you using ZIP codes in the UK ?) and a database link from all the other databases.

        Drawback - the first database must be up if any
        other database wants to see the ZIP codes.

        Benefit - easy to set up

b)    Use Oracle's Replication option.  One database to
        be the master database holding the ZIP code table;
        the other databases to hold snapshots.

        Drawback - depending on the way in which you use
        and/or refresh the table, and the version of Oracle
        it can be a pain in the backside to make this
        work properly.

        Drawback 2 - a snapshot may not be exactly the
        same as the master at all times

        Drawback 3 - if you want all some (all) databases
        to be able to update the ZIP code data then you
        have to start worrying about collision resolution
        and time lost with DBAs fixing up update conflicts

    Benefit - none of the databases depend on a central
        database being live.

--

Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk

Edwin Hartog wrote in message <7r5jli$sh5_at_romeo.logica.co.uk>...
>Many applications get data from a large table (ZIP code). Several instances
>are copied from a production dump, including this table, for parallel
>developments. Is it possible to have one copy of the ZIP code table, which
>can be accessed from all the different instances ?
>
Received on Wed Sep 08 1999 - 07:33:25 CDT