RE: Force users to use Active DG for reporting
- From: "Ric Van Dyke" <ric.van.dyke@xxxxxxxxxx>
- To: <ricard.martinez@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Mon, 31 Mar 2014 11:40:21 -0500
Tell just a few users that RO is a secret database built just for them
to do blazing fast reports on and not to tell anyone else about it.....
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Ricard Martinez
Sent: Monday, March 31, 2014 11:55 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Force users to use Active DG for reporting
Hi list,
We got an environment formed by one standalone 11g database (lets call
it RW) with an active dataguard on another server (lets call it RO)
We have provided to the users 2 tnsnames, one pointing to RW and the
other to the RO, and we have told them to use the first one for DML, etc
and the RO only for runing the reporting statments.
As good users, they just ignore us and run all on the RW database, so we
want to force them to use the RO for reporting.
Meanwhile they got the 2 tnsnames entries, i see no real options to
force them to use the RW, unless we separate the schema in two (one with
insert/update, the other only with select), and we kill any session of
the select schema on the RO (using a cron maybe, forcing them to use RW
to be able to end their reports)
Has any of you found in a similar situation, or can think in other
options?
Thanks
Other related posts:
