RMAN-08137: WARNING: archived log not deleted

-
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
When we are taking archive log backup with delete then got an error.
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/pac/lci9t1/arch/redo_1_16470_842608348.arc thread=1 sequence=16470
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process
archived log file name=/pac/lci9t1/arch/redo_1_16471_842608348.arc thread=1 sequence=16471
RMAN-08137: WARNING: archived log not deleted, needed for standby or upstream capture process

SOLUATION:

Cause: The archive logs seems that it is not yet applied in the standby database.
                        Select sequence# , applied from v$archived_log;

Action: Check the standby database and apply the logs manually and the start the deletion process.
              I can delete the archive logs by force using the below command.

      RMAN > delete noprompt force archivelog all;

But I don't want to delete the archives which are not applied in standby  so i'm changing the configuration
             
RMAN> show all;

Old configuration:

CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default

Change as Below:

RMAN> CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;

new RMAN configuration parameters:

CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;

new RMAN configuration parameters are successfully stored

RMAN-08591: WARNING: invalid archived log deletion policy

Now check the configuration:

RMAN> show all;

CONFIGURE ARCHIVELOG DELETION POLICY TO SHIPPED TO STANDBY;

Now I am able to delete those archivelogs now.

RMAN> delete noprompt archivelog all;

RMAN> crosscheck archivelog all;

Once I deleted those logs, I changed the rman configuration by the default one.

RMAN> CONFIGURE ARCHIVELOG DELETION POLICY CLEAR;
RMAN> Show all;

Comments

  1. zulalinho7 September 2021 at 16:53

    Hi Dinesh
    I could not find any contact address , so I am posting here.
    I assume that you commented on Mike's blog about Error: UPG-1401. I am getting same error. I am using latest autoupgrade.jar (2021 july version) .
    The upgrade process is from 19c to 21c.

    https://mikedietrichde.com/2019/04/29/the-new-autoupgrade-utility-in-oracle-19c/

    Could you please clarify the steps how did you start your database with newly created spfile while autoupgrade job is running.
    Thanks

    ReplyDelete

Post a Comment

Popular posts from this blog

steps to setup rman

-
Steps to setup RMAN This article is tested in oracle12C R1. How do we setup the RMAN in oracle? There are couple of ways, we can setup the RMAN. We can use control file to store backup catalog info or we can have separate database to store catalog info. Here I am using separate database to store backup catalog information. I am using Linux OS. Please remember, the directories and folder might change based on the operating system and environment. But the below steps are pretty much same for any environment. Here i am using ORCL as primary database and CATDB as catalog database.   Step1  Enabling Archive log. See the following link for the First step  Click Here Step2  Create the tablespace and user in catalog database to hold backup information. SQL> CONNECT sys/password@catdb AS SYSDBA Connected. SQL> CREATE TABLESPACE RMAN 2 DATAFILE '/app/oracat/oradata/catdb/rman01.dbf' SIZE 6208K REUSE 3 AUTOEXTEND ON NEXT 64K MAXSIZE 32767M ...
Read more

Enabling Archive log

-
Enabling Archive log in RMAN This article is tested in oracle12C R1. How do we setup the RMAN in oracle? There are couple of ways, we can setup the RMAN. We can use control file to store backup catalog info or we can have separate database to store catalog info. Here I am using separate database to store backup catalog information. I am using Linux OS. Please remember, the directories and folder might change based on the operating system and environment. But the below steps are pretty much same for any environment. Here i am using ORCL as primary database and CATDB as catalog database. Step1  Enable the archive log in ORCL database. Step 1.1  We need to build the pfile from spfile to add new entries. If you  already have recent pfile, the you do not need to do this step. Login as sys user and execute this to create pfile. create pfile='/u01/app/oraint/product/12.1.0/dbhome_1/dbs/pfile.ora' from spfile; Step 1.2  Once pfile is created, t...
Read more