I am looking into the following concept, and would like some ideas on
the best way to approach the problem.
We have a single table that contains audit information, and would like to
create an identical table on a separate server that we will update at the
same time we update the primary server table. Multiple primary servers
could exist throughout the system, and a common backup server could be
shared by multiple primary servers. The inserts, updates, and deletes
would be done from pro*c library routines that would exist on client
machines.
A simple solution would be to create a database link to the backup table, and
whenever we update the primary table we will send a second update to
the backup table (via the database link). This approach works fine as long
as the servers are up, but raises issues in the case if one or both is down
at update time.
What other alternatives can we look into? Is the Parallel Server concept an
overkill?
Many thanks for any input.
John Armani
[EMAIL PROTECTED]
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author:
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
