Conference orarep::nomahs::dbintegrator_public_public

1120.0. "How to creat link for multpile DBI logical db's?" by chsr38.ch.oracle.com::ROHR (The Packers did it!) Thu Jan 30 1997 05:51

    I am looking for the syntax to create a link from 1 catalogue to
    another catalogue that finally links into a physical Rdb database.
    
    I.e., put into practice what page 2.6 of the integrator Handbook is
    talking about.
    
    Thanks,
    Regina
    
$sql
crea data file db1 protection is ansi;
crea data file db2 protection is ansi;
att 'alias db1 filename db1';
grant distribtrans on database alias db1 to public;
commit;
att 'alias db2 filename db2';
grant distribtrans on database alias db2 to public;
commit;
disconn all;
create datab file '/type=dbi/dbname=db1' protection is ansi;
create datab file '/type=dbi/dbname=db2' protection is ansi;
attach 'filename /type=dbi/dbname=db1';
create link db1link1 to 'db$61:mfp61';
create link db1link2 to 'db$61:personnel';
create table employees_db1 link to employees using db1link1;
create table departments_db1 link to departments using db1link2;
commit;
disconn all;
attach 'filename /type=dbi/dbname=db2';
create link db2link1 to 'db$61:mfp61';
create link db2link2 to 'db$61:personnel';
create table employees_db2 link to employees using db2link1;
create table jobs_db1 link to jobs using db2link2;
commit;
disconn all;
!!
crea data file dbtop protection is ansi;
att 'alias dbtop filename dbtop';
grant distribtrans on database alias dbtop to public;
commit;
disconn all;
create datab file '/type=dbi/dbname=dbtop' protection is ansi;
discon all;
attach 'filename /type=dbi/dbname=dbtop';
create link toplink1 to 'db1';
create link toplink2 to 'db2';
create table emp1_top link to employees_db1 using toplink1;
!%RDB-E-NO_META_UPDATE, metadata update failed
!-DBI-F-IMPORT_FAIL, Import of object EMPLOYEES_DB1 failed.
!-DBI-E-DDRV_OBJNOTFND, Object does not exist in target database

The above original error from the customer try makes sense as linking to the 
physical DB1 database will only see the DBI tables but not the imported tables 
from the underlying MFP61 and PERSONNEL databases.

create link toplink3 to '/type=dbi/dbname=db1';
create table emp1_top link to employees_db1 using toplink3;
!%RDB-F-SYS_REQUEST, error from system services request
!-DBI-E-ATTLNKERR, Error attaching database, Link name='TOPLINK3', Connect
!string='0::/type=dbi/dbname=db1'
!-RDB-E-BAD_DB_FORMAT, /type=DBI/dbname=db1 does not reference a database known
!to DBI
!-DBI-F-CAT_ACC_FAIL, Fatal DBI physical database access failure
!-RDB-E-BAD_DB_FORMAT, db1 does not reference a database known to Rdb
!-RMS-E-FNF, file not found
 
    So how do you do this?
    

The problem with the last attempt appears to be with the fact that a dbi-dbi
link makes a remote connection.  

Notice in the error the connect string of "0::/type=dbi/dbname=db1". If the link
does not have an explicit remote connection, then in the case of a dbi link, an 
implicit (0::) remote conection is made. 

Therefore, I suspect that the proxy account, or the login.com (I'm assuming vms)
are not setup for the attach to the dbi catalog (rdb version, logicals db1...)

    So my syntax was almost correct. 
    
    create link toplink3 to '/type=dbi/dbname=dev:[dir]db1';
    
    Indicating device and directory did the trick, together with a set
    version in the login.com of the connecting user. 
    
    Thanks a bunch,
    Regina