This content has been marked as final. Show 2 replies
You can create sql script and call it before "delete obsolete". The script will query v$archived_log and find all logs that were not sent to standby. For all logs it will generate OS command to copy the log to some location. For example :1 person found this helpful
select 'cp '||name||' to /backup_dir' from v$archived_log where dest_id=1 and not exists (...
Hello;1 person found this helpful
This is not true or it does not have to be true :
Unless there's a great business reason I would always set this :
I cannot set RMAN policy on primary to APPLIED ON STANDBY as it requires archive log dest. to be MANDATORY which would cause primary database unavailable in case of standby going down.
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
If the business says you cannot lose data, but does not provide you the resources for this requirement than you are in situation where you cannot succeed. At some point you have to push back.
I believe you are talking about "Protection mode". These are two very different things.
Can you post your Protection mode?
SQL> SELECT PROTECTION_MODE FROM V$DATABASE;
Mihael is correct, you can use a script to remove/move archive. But it reinvents the wheel. If you have space for Archive let Oracle manage it. If you use a script to move it you will need another to remove it and still another to move it back if you need it. Oracle already handles these things so all you end up doing is making the job harder.
If you have APPLIED ON STANDBY set RMAN will bark when you try to delete Archive not yet applied.
OK, I think I understand your question better, you are saying " MANDATORY" will shutdown the Primary if redo cannot be written. I guess that could happen. I would not set a system like this if I could avoid it.
Chapter 15 of Data Guard Concepts and Administration 11g Release 2 (11.2) E10700-02 has a good "Mandatory" section.
Unless you have a good business reason set it to "Optional" ( default )
If you are saying "MANDATORY is requirement on primary" it is not. Keep it simple. Use FRA and RMAN to manage your archive.
1. Why is MANDATORY a requirement on the Primary? Is this a business requirement? Why can't you have a third DEST_ID for Archive to handle this?
2. Why do you need to delete archive so fast? Do you have a space limit? If yes why can you not add more disk?
3. What is wrong with the Standby site that you are so concerned about the Standby going down? Do you have network issues?
4. Why use DELETE OBSOLETE without a retention policy?
Edited by: mseberg on Feb 7, 2013 12:26 PM