| Discoverer against readonly database [message #288696] |
Tue, 18 December 2007 06:19  |
funky
Messages: 4
Registered: December 2007
Location: Zagreb
|
Junior Member |
|
|
We are planning to use standby database for data mining. Plan is to open standby database in readonly mode, and next day continue recover db with new archive logs and reopen in read only and so on.
Our users are keeping their reports in database, so it looks that it cannot be changed on "standby" database.
Any hints how to put that alive under mentioned conditions...
THX
|
|
|
|
|
|
| Re: Discoverer against readonly database [message #288729 is a reply to message #288705] |
Tue, 18 December 2007 07:54  |
skooman
Messages: 913
Registered: March 2005
Location: Netherlands
|
Senior Member |
|
|
I assume you are not yet on 11g, but is might be worth looking at that. I saw a presentation stating that one of the new functionality is to use a standby/mirroring database for reporting purposes.
On 10g it must be possible I assume, but it would be best to investigate this with the help of an experienced DBA or so I guess. This has little to do with reporting and more with the use of replicated databases etc.
|
|
|
|
| Re: Discoverer against readonly database [message #288752 is a reply to message #288696] |
Tue, 18 December 2007 10:21 |
funky
Messages: 4
Registered: December 2007
Location: Zagreb
|
Junior Member |
|
|
THX for all your contribution.
standby database like this is something that I havce done for reporting (sql or Toad interface) but never for discoverer.
We are on 10gR2 (as written on the top of the thread .... so 11g is not an option for a standby version.
Materilazed view still read data from disks where other datafiles are...and spent a lot of buffer for nothing.
|
|
|
|
| Re: Discoverer against readonly database [message #288987 is a reply to message #288752] |
Wed, 19 December 2007 03:44 |
skooman
Messages: 913
Registered: March 2005
Location: Netherlands
|
Senior Member |
|
|
The reason that standby will work for SQL*Plus, Toad etc, and not for Discoverer, is that Discoverer stores metadata in the database itself. So, a readonly database will not be sufficient.
As for the materialized views: I guess LF was referring to creating MV's in the actual online database and refresh them overnight to minimize the impact on the transactional capacity. Since the basic idea of having Discoverer run on a standby (readonly) database will not work, he was getting into "the creative modus". Like stated, please discuss this with you DBA an bear in mind that Discoverer needs write access to the source database...
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
