Shulou(Shulou.com)05/31 Report--

This article mainly shows you "DG how to ensure that archived logs can not be deleted at will". The content is simple and clear. I hope it can help you solve your doubts. Let me lead you to study and learn this article "DG how to ensure that archived logs can not be deleted at will".

Four methods to ensure that archived logs cannot be deleted at will

Http://blog.itpub.net/30126024/viewspace-1982071/

RMAN configure Archive Log deletion Policy

Https://blog.csdn.net/cuiyan1982/article/details/45721433

-- query archive deletion strategy

Show archivelog deletion policy

-- detailed description of the method

1. SQL > alter system set log_archive_dest_2='service=testdb1dg lgwr async db_unique_name=slave MANDATORY'

2. RMAN > CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON STANDBY

Or

RMAN > CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY

Setting it to CONFIGURE ARCHIVELOG DELETION POLICY TO NONE removes the restriction.

However, the premise of the second method is that there is already a configuration of the first method (the second method is an enhancement based on the first method), otherwise an error will be reported.

RMAN-08591: WARNING: invalid archived log deletion policy

The above two methods are suitable for the master database in the dataguard environment to ensure that the master database log cannot be deleted casually, but neither of these methods is pushed on the master station.

Recommended, because the premise is that MANDATORY will cause the main library hang to live.

3.RMAN > configure archivelog deletion policy to backed up X times to device type disk

Execution of delete noprompt archivelog until time "sysdate-XX" above x > = 1 will result in an error RMAN-08138

Setting it to CONFIGURE ARCHIVELOG DELETION POLICY TO NONE removes the restriction.

None of the above three methods automatically delete the archive, but confirm whether it meets the criteria when deleting, and avoid deleting the archive logs required by other functions.

4. In addition to the above three cases, there is a fourth special case, even without the above three settings, if it is a standby library in the dataguard environment, the main library is transferred.

The archive log has not been prepared by the library recover. If the standby database executes delete noprompt archivelog until time "sysdate-XX", it will also report an error RMAN-08137.

Methods such as 1 and 2 are used to confirm whether the archive has been applied by DATA GUARD. If it is not applied by DATA GUARD, perform delete all input or

Delete input or delete noprompt archivelog until time "sysdate-XX" will report an error.

If it is only the first method above, an error will be reported.

RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process .

If it is the second method above, an error will be reported.

RMAN-08120: WARNING: archived log not deleted, not yet applied by standby

But it can still be manually deleted through the OS layer.

The MANDATORY option cannot be randomly configured in the remote archive path. Once selected, if the network is interrupted, the following will occur, which will affect the main database and cause the main database to live in hang.

ORA-16014: log 1 sequence# 565 not archived, no available destinations

The above is all the contents of the article "how to ensure that archived logs cannot be deleted at will by DG". Thank you for reading! I believe we all have a certain understanding, hope to share the content to help you, if you want to learn more knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.