Re: Replicated Databases

Carlos,

You can use the distributed option to achieve your goal, and the effects will be immediate. Make sure the distributed option is installed for all three databases. Then, you can design the tools which manage the administration database to do statements like:

	INSERT INTO admin_table( columns . . .)
	VALUES( values . . . . .);

	INSERT INTO admin_table_at_query_db1( columns . . .)
	VALUES( values . . . . .);

	INSERT INTO admin_table_at_query_db2( columns . . .)
	VALUES( values . . . . .);

	COMMIT;

Like this, the new row will become visible in all 3 databases at once.

Another alternative would be to put triggers on all of the tables managed via the administration database, and to have the triggers to the distributed inserts, updates, and deletes (but be sure to commit OUTSIDE of the trigger).

Good Luck,

--
Rich Goldkamp		rjgoldka_at_dcss.com
Digital Consulting & Software Services
(504) 523-5005	x2736


Carlos A. Gonzalez <carlos_a_gonzalez_at_us.dell.com> wrote in article
<7dg4ki$856$1_at_galaxy.us.dell.com>...


> Hi all:

> 

> here is my problem:

> 

> The design of a new application requires 3 Oracle databases.

> 

> All 3 databases are the same (Strcture and data).

> One is going to be used for Administration. (Manually updating deleting,

> adding rows in tables)

> The other two are being used by the application (Mostly querys)

> 

> One of their requirements is to update the other databases as soon as the

> administration database has been changed

> Exporting the data is out of the question. Takes too long and it will be

 an


> endles process.

> 

> This data has to be available to the other two databases immediatly after

> the administration database has been changed.

> 

> Sugestions are welcome

> 

> Thanks

> 

> Carlos

> 

> 

>