Conference orarep::nomahs::dbintegrator_public_public

    
    Hi Elaine,
    
    All they should *have* to do is install the common components from the
    Rdb kit (and they might as well go for the 6.1 common components rather
    than the 6.0 ones).  They will need DDTM and they will need to grant
    distribtran on their existing Rdb 4.2 databases.  I wouldn't think that
    installing common components from the 6.1 kit would break any
    applications but I believe right now the minimum version of Rdb
    supported is 5.1 so there probably isn't much testing being done
    against 4.2.  
    
    If I were them (assuming they are running 4.2 standard [as opposed to
    4.2 multi-version]) I would install multi-versioned common components from
    the Rdb 6.1 multiversioned kit and try to work with this minimal
    perturbation of their environment.  It shouldn't effect their current
    applications (if it is multi-versioned the users would have to
    explicitly set up to it to use it - the current applications would set
    up to use the new common components hence they should be OK).
    
    The only time folks would have to use the new (6.1) SQL would be when
    they are creating their DBI objects.  When using DBI, the other common
    component (DISPATCH) would have to remain at the higher version.
    
    I hope you have encouraged the customer to upgrade.  Rdb has come a
    loooong way since 4.2, and if they did run up against a problem it
    might be difficult getting support.
    
    Thanks,
    
    dan
    
    

Elaine,

>    A customer just received their DBI kit from Oracle and was told that
>    installing multi-version RDB would allow them to have the required 6.0
>    for the global catalog and keep their applications on RDB 4.2 since
>    they do not want to update those databases.  However, they have also been 
>    told that running multi-version RDB could have implications for their 4.2 
>    applications and are very concerned about it.    

If I understand what you are asking correctly, you want to used an Rdb 6.0 
database as your catalogue, and have that catalogue reference data in Rdb 
4.2 databases on the same node.

You cannot reference more than one Rdb version at the same time on the same 
machine. You can attach to a remote database of a different version though. 
The best thing is to use the same Rdb version for you catalogue as is used 
for the data.

Cheers,

Mark.

    
    Thanks Mark, that is another good reason to keep your catalog at Rdb
    V4.2.  If you don't, as Mark mentioned, at least one of your attach strings
    will have to be remote (if you have a remote catalog then that would be
    one remote process, if you go with a local catalog at Rdb6.0 then the
    two other Rdb 4.2 database attach strings would have to be remote). 
    The remote could be to the same node.
    
    It's best to stick with uniform Rdb versions for the catalog and databases
    if you can get away with it.

    Thank you, the only problem is that one of the databases is from a
    third party product that hasn't been updataed (for one reason or
    another).  I'll talk further with them and try to get them to at least
    upgrade the one used for their "in-house" applications...
    
    Thanks again!
    
    Elaine