The environment is Oracle 9.2.0.6 on SunOs 5.10
We needed to restore a large amount of archive logs on our primary database server after an issue with our standby server.
The standard archive log area on the primary was not large enough to accomodate all the logs we needed to recover so we restored to a temporary location using :
set archivelog destination to ... ;
The logs were then scp-ed to the standby server and applied.
After being scp-ed they were removed.
This led to subsequent backups of the primary failing as the 'backup archive log all' command wanted to backup the archive logs that had been restored.
So the restore has updated the control file of the primary database to reference the restored archive logs.
My question is, could we have performed the restore such that the control file was not updated, i.e. is there a restore option we could have used?
My initial feeling was 'why the hell is Oracle trying to backup archive logs that it has recently recovered?', but I'm guessing the control file update is in case you have a situation where the original archive log destination is no longer available and, going forward, a new archive log destination is to be used. To me, updating the control file when restoring archive logs seems something of a strange thing to do, as it's forcing a backup of something that's been recovered from an existing backup.
If somebody could provide firm answers to this I'd be grateful.