Our database uses Active Data Guard.
If I create a user in primary database, will that be automatically created in DR database ?
the DR is maintained by applying all of the redo that is generated on the primary. Thus all activity on the primary should be replicated on the DR. It wouldn't make much sense if the DR were not kept as a mirror copy of the primary, would it?
The answer is: Yes, the user you created in the PD will be created in the ADG.
An oracle ADG is a physical standby which enables read-only access while Redo Apply is active.
There are three types of standby database in Oracle.
Physical standby - Apply changes through Redo (actually it's block-level-copy)
Logically standby - Apply changes through SQL statements (exacted automatically by LogMiner).
Snapshot standby - Receive and archive, not apply.
An Active Data Guard is a physical standby.
Related
I have setup a data guard on two separate servers (primary and standby).
All the steps have been completed and when I make a change in the primary database and commit, it is also applied to the standby server.
Now I want it to be OK without committing the changes on the standby server.
For example, if a record is inserted in the primary database table, that record will also be inserted in the standby database table and there is no need to commit.
I have not found a solution.
Lets put aside the standby for a second. If you make a change on a database and commit it, that the change is now there permanently. If you do not commit, it can be considered as never happened, ie, you rolled it back, or not yet happened (the transaction is open).
Having a standby or not does not impact this fundamental premise.
I've lost two hard disks yesterday . One contains an Oracle Datafile and another contains part of archive logs generated in the past 2 days. (say, arch_5.dbf and arch_6.dbf are lost, in the set of arch_1 to arch_10).
I have switched over to my standby site as part of business continuity plan.
Now, I have to recover the missed datafile. It requires the missed two archive log files for recovery.
Is is possible to apply the same set of archivelogs from standby to production, in order to recover the datafile ?
Kindly advise.
~SK~
It might prove a bit easier to
Use RMAN Incremental Backups to Refresh a Standby Database
you could use the archives that are transported to the standby site but they won't help with the recovery of the lost datafiles, unless their creation is logged in the archives.
Using the incremental backup option is easier.
Yesterday, I made some migrations to a website that I had to rollback. Luckily, I had a backup of the database, and was able to restore the lead database to a "good" state using Heroku's pg:backup:restore facility.
The lead database is followed by another database. Does the follower also get "restored" when I restore the lead? Will it contain the same data as the leader?
You can't rollback an existing database. When you use the rollback functionality you're actually forking the targeted database and thereby creating an entirely new database without any followers. If you need to do this operation for your primary database, you'll need to put the application maintenance mode before creating the rollback database, promote it to primary and then recreate the any followers.
I had configure oracle D ML replication using oracle golden gate successfully but is there any query to check source and target is in sync or not or how to verify IT.
No replication tool has the functionality to check if the database is in sync. The idea of asynchronous replication is that it is never fully in sync - the target is always late compared to the source database. Only fully synchronized disk replication allows a full in sync copy of the data.
You might want check if the "not recently changed" data is the same using a compare-every-row technology. Oracle has a product called Veridata which can do the job.
You might also want to check if the replication stream is working (it is not stopped). But this check does not check if the data is in sync. Someone might modify the target data and you might not be able to check that. The heartbeat technology just checks if the replication stream is not broken. OGG 12.2 has special build in commands for that.
Please check:
ADD HEARTBEATTABLE command for ggsci
ENABLE_HEARTBEAT_TABLE parameter for processes
After setting up primary database which is setup with Raid1. I break the mirror and physically transfer it to the standby database hardware and did a Raid1 sync. With that I have exact replicate of the primary database on the standby database.
However, since the standby database's data is exactly the same as primary database, I have to change it to become the standby database.
example:
Primary database server oracle_sid=chicago
Standby database server oracle_sid=chicago (since its a replicated data)
I need to change the standby database oracle_sid to boston.
I believe it is not a simple case of changing the oracle_sid to boston since the database name is chicago.
Appreciate any specific and detailed steps to make the changes.
You should probably ask this on Serverfault. However, I'll mention here using Recovery Manager (instead of your method) to create the standby database will eliminate most of the manual work in renaming the database, recreating the control files, etc.