Re: referential integrity across databases

Hi,

This could be one of the possible ways to solve your problem. Have your = contact tables in one database let say the sid is db1.

You need to reference the contact information in other instances like = db2 and db3.

Create a database link 'contactlink' pointing to the db1 instance.

Note: If you want to set the database link to a different name than the = oracle sid of db1 then make sure that

          global_name = False in the init.ora of db1.

Now create view in db2 and db3 looking like :

create view contact
as select * from contact_at_contactlink --> This is the dblink name.

This way you have one centeralized data and the other instances can = refer to the same data instead of duplicating the information.

Hope that helps.
Krishnan
krishnan_at_cdgpd.com

    Kent Eilers wrote in message <35FFC9D8.96B1E688_at_pca.state.mn.us>...     We have a 'core' database which centralizes shared information (e.g. = addresses, contacts) used by several programs - each with their own = respective database.

    The issues we are dealing with is how to avoid orphans (in program = db's) when the core data is dedupped.

    An example is as follows:

        Program A references core record 'Smith Inc.' and program B = references 'Smith H. Inc.' Our

        monthly cleanup of the core db discovers 'Smith Inc.' is the = same company as 'Smith H Inc.' and

        removes Smith H. Inc. Now all records which referenced 'Smith = H' are orphaned in program B's db.

    Options entertained so far include:

-the use of triggers on the Core db to check program =
references

-additional tables in the core db registering program =
references

    I suspect this issue is quite common - what have you done? Does = Oracle have specific options for this?

    Thanks. Received on Wed Sep 16 1998 - 14:05:56 CDT