Hemant K Chitale
It just updated the profile with backup information ?
did you have change to create SR with Oracle support ?
currently tested again.
- login at one RAC node.
- run rman
- connect catalog ****
- connect target /
- restore spfile to '/tmp/test.ora' => success
- exit rman
- check: srvctl config database -d db*** gives updated "Spfile Parameter" Spfile: /tmp/test.ora
- Have to reset it: srvctl modify database -d db*** -spfile +DATA/db***/PARAMETERFILE/spfile.267.950865923
Yes, it seems that the restore command performes an implicit update of the db CRS-resource.
OL 7.4 RDBMS/GI 12.2
I don't know should that be a new feature. What do you think? I will open a SR as soon as possible.
As an example:
We take backup to NFS (/backup_nfs)
After this, for some reason if I do restore of spfile from this location, it has to restore not to update the resource profile to the backup location instead, it may have to update the restored location with a filename.
In RAC database, this backup location need not to be shared location, then how it will work ?
if we try to restore spfile from tape backup, then will it access the tape ? and will it update the backup piece name of spfile in resource profile ?
With my understanding, this is looks problem.
IMO, it doesn update any backuplocations.
It will update in the CRS database profile the spfile parameter to the in previous restored location of spfile.
If you hit "rman>restore spfile to '/tmp/test123.ora' it will implicit update the spfile parameter of db resource to '/tmp/test123.ora', too. That's very very worth to know! It's a mean trap.
I am sorry.... I misunderstood.
it is perfect... it updates the spfile value to the restored file.
it should be expected.