Hi Faan,
Thanks Faan for this effectively critical point. Like
you I have faced this problem after applying some
patch (FND patches on 11.5.7) and since I have standby
database as emergency environment. It was big problem.
I wrote a scripts to detect such events and I read
some metalink docs
Sai - All data in the database? How large, how active is the source
database?
Dennis Williams
DBA
Lifetouch, Inc.
[EMAIL PROTECTED]
-Original Message-
Sent: Monday, November 17, 2003 4:10 PM
To: Multiple recipients of list ORACLE-L
hi
data movement for a reporting database from a OLTP
Sonja,
that is a very interesting question.
I have tested the source/target scenario under Digital Unix.
We did come across a command that allowed you to mount the devices with the
same name on the same server
with a mount /ignore(?).
There may well be a ruse to rename the whole battle ship.
It
Tom,
One of the big advantages of a "standby" database is that it can be opened in the
"read only" mode just for the purpose of a report type database.
Be sure to check all of your options before you make the final decision. The report
database and the OLTP database could/should have different
You can use the standby database in read only mode if
you are going to do reporting only.
--- "Terrian, Thomas"
[EMAIL PROTECTED] wrote:
How are you all creating reporting databases? We
currently have an OLTP
database and we wish to create a reporting database
from it. As I see it,
we
If your production database can afford a short downtime. You can copy all
the datafiles and rename the database. We did this way. Refreshed the
database everyday. 15GB database needs 15 min. downtime on the production
database. Depends on your system I guess. Or using hot backup recover to
You don't need replication. You can simply create tables on one
machine across a db link fom the first. Depends on the volume and
type of data.
We (only a few Gb) rebuild our reporting environment from transaction.
Reporting doesn't have ALL the tables from OLTP, just the ones we need,
somewhat
A large client that I worked with last year had a very high volume OLTP
system and they implemented Quest's SharePlex for a reporting database. It
worked well for them. Oracle's current method of replication could never
have approached the speed they needed and it would have added overhead
