tajinderpal
asked on
Oracle database T-1 Setup
Hi,
We currently have a production Oracle database which we use to run various reports throughout the day.
However we know have a requirement where we need to setup another oracle database server which is a day behind production server.
So to my knowledge this will mean having to do a database import at the end of the day.
Does anyone know of an efficient way of setting this up, and how best to accomplish this task.
Many Thanks
We currently have a production Oracle database which we use to run various reports throughout the day.
However we know have a requirement where we need to setup another oracle database server which is a day behind production server.
So to my knowledge this will mean having to do a database import at the end of the day.
Does anyone know of an efficient way of setting this up, and how best to accomplish this task.
Many Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I would think that with expdp you would most likely need to use the FLASHBACK_TIME parameter to get a consistent as of a specific time dump. That may require additional setup. Honestly, I haven't used expdp to do something like this.
All you really need are the archive logs and if your production database isn't in archive log mode, you have bigger issues. And RMAN isn't the only way to backup and restore a database. For a one time operation like this, there are much easier ways.
All you really need are the archive logs and if your production database isn't in archive log mode, you have bigger issues. And RMAN isn't the only way to backup and restore a database. For a one time operation like this, there are much easier ways.
ASKER
Thank you all for your comments.
Just a couple of things to add, DB Size is 160GB and growing.
Plus I need to set this up so that it works constantly, it is not a one time operation.
Ideally would like to use anything that is built in to oracle and requires minimal user intervention.
Just a couple of things to add, DB Size is 160GB and growing.
Plus I need to set this up so that it works constantly, it is not a one time operation.
Ideally would like to use anything that is built in to oracle and requires minimal user intervention.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks Johnsone, your comments helped a lot.
We will have a cut off time like 10pm and the T-1 database will be database as it 10pm.
Can this be achieved via the Standby Database function within Oracle?
We will have a cut off time like 10pm and the T-1 database will be database as it 10pm.
Can this be achieved via the Standby Database function within Oracle?
Looking through some of the documentation, I don't believe you can do it with a managed standby. Maybe you can, but I don't see it in the documentation. That doesn't mean you can't do it, it just means you have to do the legwork.
You can get close using managed standby, but I don't think you can get an exact cutoff with managed standby. If you want to do it with managed standby, then you would have to have a job that does a switch logfile at 10:00. Note the logfile that was switched to. Then send all the archives from the last standby update through the one that was just created to the standby. You couldn't use Oracle's log transport for this because you want to control which logs get there. Again, this can be scripted, but you have to do it, Oracle won't. At this point, you would shut down the standby, recover it, then open it again. This would be strictly a read only version of the database.
To do it completely unmanaged, which is probably the easier way for what you are trying to do. Keep in mind that a standby database is really nothing more than a database that is in constant recovery mode, putting a fancy name on it doesn't change that, especially for what you are trying to use it for. You need a copy of the primary on the second server. At 10:00 do the log switch on the primary. Do a rman archive log backup to get all the logs backed up. Then on the secondary server within rman you issue a recover until 10:00 pm. Once that completes, you shut it down, make a copy of it and then open the copy.
You can get close using managed standby, but I don't think you can get an exact cutoff with managed standby. If you want to do it with managed standby, then you would have to have a job that does a switch logfile at 10:00. Note the logfile that was switched to. Then send all the archives from the last standby update through the one that was just created to the standby. You couldn't use Oracle's log transport for this because you want to control which logs get there. Again, this can be scripted, but you have to do it, Oracle won't. At this point, you would shut down the standby, recover it, then open it again. This would be strictly a read only version of the database.
To do it completely unmanaged, which is probably the easier way for what you are trying to do. Keep in mind that a standby database is really nothing more than a database that is in constant recovery mode, putting a fancy name on it doesn't change that, especially for what you are trying to use it for. You need a copy of the primary on the second server. At 10:00 do the log switch on the primary. Do a rman archive log backup to get all the logs backed up. Then on the secondary server within rman you issue a recover until 10:00 pm. Once that completes, you shut it down, make a copy of it and then open the copy.
RMAN restore is more complex technically and needs full backup and archives logs available to be done.