Re: RAMAN is not backing a set of archivelogs from the database server

Hello Abdellah, The following commands helped me to catalog the orphan archive log files. I still don't understand why these logs were orphaned in the first palace. But it is all good now.

CATALOG START WITH '/your_dir_location';

then do your regular backup. The backup will take those 13 archivelogs.

Thanks everyone for your tips and support.

Ashoke

On Wed, May 19, 2021 at 10:22 AM Abdellah DANY <abd.dany_at_gmail.com> wrote:

> Hi,
>
> rman target /
>
> CATALOG START WITH '/your_dir_location';
>
> then do your regular backup. The backup will take those 13 archivelogs.
>
>
> Le mer. 19 mai 2021 à 16:13, Ashoke Mandal <ramukam1983_at_gmail.com> a
> écrit :
>
>> Hello Andrew, THe archive logs are located at the regular archive log
>> location. All other archive logs are backed from the same location except
>> these 13 logs.
>>
>> Thanks,
>> Ashoke
>>
>> On Wed, May 19, 2021 at 9:06 AM Andrew Kerber <andrew.kerber_at_gmail.com>
>> wrote:
>>
>>> Where are the archivelogs located? what directory that is.
>>>
>>> On Wed, May 19, 2021 at 8:52 AM Ashoke Mandal <ramukam1983_at_gmail.com>
>>> wrote:
>>>
>>>> Hello Todd and Abdellah, Thanks for your response. We use RMAN catalog
>>>> database and following are the RMAN configuration parameters for database
>>>> this database:
>>>> CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 3000 DAYS;
>>>> CONFIGURE BACKUP OPTIMIZATION ON;
>>>> CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
>>>> CONFIGURE CONTROLFILE AUTOBACKUP ON;
>>>> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO
>>>> '%F';
>>>> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F';
>>>> CONFIGURE DEVICE TYPE 'SBT_TAPE' PARALLELISM 2 BACKUP TYPE TO BACKUPSET;
>>>> CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET;
>>>> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
>>>> CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
>>>> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE 'SBT_TAPE' TO 1;
>>>> CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1;
>>>> CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS
>>>> 'ENV=(NB_ORA_SERV=<backup_serv_name>, NB_ORA_CLIENT=<db_serv>,
>>>> NB_ORA_POLICY=ora_phxsdmas6),SBT_LIBRARY=/usr/openv/netbackup/bin/libobk.so64.1';
>>>> CONFIGURE MAXSETSIZE TO UNLIMITED;
>>>> CONFIGURE ENCRYPTION FOR DATABASE OFF;
>>>> CONFIGURE ENCRYPTION ALGORITHM 'AES128';
>>>> CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT'
>>>> OPTIMIZE FOR LOAD TRUE ; # default
>>>> CONFIGURE ARCHIVELOG DELETION POLICY TO NONE;
>>>> CONFIGURE SNAPSHOT CONTROLFILE NAME TO
>>>> '/phxsdmas6/u01/app/oracle/product/11.2.0/db_3/dbs/snapcf_rdmas.f'; #
>>>> default
>>>>
>>>> Please send me the exact commands on how to catalog these 13
>>>> archivelogs and then back these up.
>>>>
>>>> Ashoke
>>>>
>>>> On Tue, May 18, 2021 at 10:10 PM Todd Bellaver <todd.bellaver_at_gmail.com>
>>>> wrote:
>>>>
>>>>> Hey there,
>>>>>
>>>>> Are these the oldest archivelogs? If so what
>>>>> is CONTROL_FILE_RECORD_KEEP_TIME set to, please? The suggestion below
>>>>> assumes archivelogs are older than the keep time. If they are not, send
>>>>> more details. Happy to help.
>>>>>
>>>>> RMAN only manage archivelogs that are listed in the controlfile.
>>>>> Details about archivelogs are retained in the controlfile upto the
>>>>> CONTROL_FILE_RECORD_KEEP_TIME (default is 7 days). If archivelogs are
>>>>> older than CONTROL_FILE_RECORD_KEEP_TIME then 'catalog start' will not
>>>>> appear to add older archivelogs because they will automatically age out.
>>>>>
>>>>> If these archivelogs are older and they have not been backed up yet
>>>>> then consider:
>>>>>
>>>>> 1. Increasing the CONTROL_FILE_RECORD_KEEP_TIME using 'alter
>>>>> system set control_file_record_keep_time=[*Number of Days*]
>>>>> scope=spfile;'
>>>>> 2. Using rman to backup the archivelogs
>>>>>
>>>>> Best regards,
>>>>>
>>>>> Todd
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Tue, May 18, 2021 at 7:15 PM Abdellah DANY <abd.dany_at_gmail.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> You have to catalog them in your controlfile or rman catalog (with
>>>>>> catalog start with command) then backup them and delete them using RMAN...
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Wed, May 19, 2021, 00:05 Ashoke Mandal <ramukam1983_at_gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hello, One of my Oracle 11.2.0.3 databases is behaving unusually.
>>>>>>> There are 13 archivelogs files sitting at archivelog directory on the
>>>>>>> database server. I have verified using the following command that these 13
>>>>>>> archive logs are not backed up. But when I run the archivelog backup or
>>>>>>> full backup including archivelog it doesn't backup these 13 archivelogs. It
>>>>>>> backs up other archivelogs though.
>>>>>>>
>>>>>>> RMAN> LIST BACKUP OF ARCHIVELOG FROM TIME 'sysdate-40';
>>>>>>>
>>>>>>> I am not able to run "CROSSCHECK ARCHIVELOG ALL;" and getting the
>>>>>>> error
>>>>>>>
>>>>>>> RMAN> CROSSCHECK ARCHIVELOG ALL;
>>>>>>> specification does not match any archived log in the repository
>>>>>>>
>>>>>>> Any idea how to backup these 13 archivelogs? I can delete these
>>>>>>> archivelogs and move on but I was looking for a way to back these up.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Ashoke
>>>>>>>
>>>>>>>
>>>
>>> --
>>> Andrew W. Kerber
>>>
>>> 'If at first you dont succeed, dont take up skydiving.'
>>>
>>

--
http://www.freelists.org/webpage/oracle-l