PITR involving physical db changes (new files/tablespaces)

Perhaps someone can assist me in understanding this recovery scenario.

I have very large SAP (2TB+) databases that are up and running for weeks at a time. During that time files are added to tablespaces as necessary. On very rare occasions a new tablespace will be added. Archiving is enabled.

During a Point-In-Time-Recovery, which I haven't had to do yet, what will happen when during that recovery process a physical change is encountered in the archive log?

Will the recovery process pause, tell me perhaps a file was added, and give me a change to again add that file?

I'd surely appreciate the input of the experts here, and/or a better strategy or process that I could follow when making physical changes to the databases.

I take split-mirror backups 3 times a week on the database, and really don't take online backups since they run for days at a time.

I'd also appreciate being directed to a whitepaper or something more than just RTFM.

Thank you all.

Charles Received on Mon Sep 13 2004 - 15:45:57 CDT