Networker control file restoration error: RMAN-06172: no AUTOBACKUP found or specified handle is not a valid copy or piece

Hi Sabarna_Deb,

Seems that the AUTOBACKUP was set to OFF during the backup from oracle machine, You have to turn the autobackup feature ON, by running the following command “CONFIGURE CONTROLFILE AUTOBACKUP ON”

Hope this helps you to solve the issue,

Thanks,

Ahmed Bahaa

Additionally, With a control file autobackup, RMAN can recover the database even if the current control file, recovery catalog, and server parameter file are inaccessible.

A control file autobackup lets you restore the RMAN repository contained in the control file when the control file is lost and you have no recovery catalog. You do not need a recovery catalog or target database control file to restore the control file autobackup. Whenever you add a datafile/s, resize, increase/decrease the size of datafile/s or etc, controlfile is automatically backed up.

If CONFIGURE CONTROLFILE AUTOBACKUP is ON, then RMAN automatically backs up the control file and the current server parameter file (if used to start up the database) in one of two circumstances: when a successful backup must be recorded in the RMAN repository, and when a structural change to the database affects the contents of the control file which therefore must be backed up.

Thanks,

Ahmed Bahaa

Hi,

That i will check and Could you plz guide me how to restore the controlfile of source database to another server (remote) prior to start the duplicate command? I have created the RMAN duplicate script through NMO wizard.  I believe if i used same controlfile restore script to original server then it will work. Might be different procedure for restoring controlfile to remote host.

Hi Sabarna_Deb,

I am not sure of the restoration process of controle file to remote host for database duplication ,  I am not sure as well if it is required or not for duplicate database because i cannot find any information for restoring control file to remote host on Powerlink,NMO guides or even Oracle website.

Thanks,

Ahmed Bahaa

Hi Sabrana_Deb,

Any updates regarding this issue , did you manage to sort it out ?

Thanks,

Ahmed Bahaa

Yes, actually database on cluster enviroment. During tape backups i have specifically mention NSR_CLIENT="one of the Physical_hostname". Not virtual_hostname. Online database backup taken from "Physical_hostname" which i have mentioned in RMAN script during backup and unfortunately (i do not know how) control file backup has been taken from another physical_hostname (in pair). I came to know when i checked in tapes, control file belongs to which physical_client. Previously during Control file restoration, i have wrongly mentioned "NSR_CLIENT=". Now i was able to restore control file by refering correct "NSR_CLIENT=".

Thanks for that information and the updates on how you sort out that issue Sabarna,

Did you configured as well the AUTOBACKUP to be ON as i mentioned before in my posts ?

Thanks,

Ahmed Bahaa

Hi Sabarna_Deb,

Was the control file backed up or not?  If the log shows which backup piece the controlfile was backed up to, simply try the following:

restore controlfile from ' ';

Actually this is More Oracle issue, not related to NetWorker, So it needs some more investigation from Oracle configurations side.

I will be waiting your updates.

Thanks,

Ahmed Bahaa

Hi Sabarna_Deb,

I am totally agree with you regarding that

Would you please mark this post as Answered ?

Thanks,

Ahmed Bahaa

Has to work I did it few months ago, as first step you have to verify which client own indexes on backup server. In restore script use this name, in NSR CLIENT variable. Don’t forget to set remote access on the client’s resource which owns indexes, set it to @ for the tests…

Regards

Lukas