Skip to main content
8 events
when toggle format what by license comment
Jan 26, 2017 at 16:23 comment added ArtOfWarfare @KrisJohnston - I've updated my question (see Update #2) to show everything I've tried since. I'm stuck again.
Jan 25, 2017 at 18:18 comment added Kris Johnston Restoring the controlfile to your dev database won't change the SID, but it will change the database name (if they are different). It will also set the paths to all of the data files, redo log files... You "may" have to : RMAN> set dbid 1345519754; restore controlfile from...; but I would try the restore controlfile first and see if that works.
Jan 25, 2017 at 17:52 comment added Kris Johnston @ArtOfWarfare There is no way to tell from the filenames. If you can get the other team to do a RMAN> show all; from the production environment, that will tell you how the CF autobackup is named: from the show all line: CONFIGURE CONTROLFILE AUTOBACKUP FORMAT... The CF autobackup is usually pretty small, so odds are, it would be the smallest file. If the CF backup is part of the database backup, it may be included in the last file (based on the last write date/time).
Jan 25, 2017 at 17:52 comment added ArtOfWarfare @KrisJohnston - Also, what would restoring the controlfile actually do? Would that change the SID of the database?
Jan 25, 2017 at 17:45 comment added ArtOfWarfare @KrisJohnston - I edited my question to include the names of all the files I was provided with at the end. Do you think any of those might be the control file?
Jan 25, 2017 at 17:40 comment added Kris Johnston @ArtOfWarfare You need to restore the controlfile first. Provided the production environment is taking a control file autobackup, have them send you that backup (they may have already sent you that piece, or the controlfile backup could have been included with the database backup), then: RMAN> shutdown immediate; startup nomount; restore controlfile from '<full path of controlfile backup>'; alter database mount; catalog start with... ;
Jan 25, 2017 at 15:58 comment added ArtOfWarfare Okay - thank you for that. Now I'm hitting this issue - it's not cataloging any of the files. For every file, it spat out this error message: RMAN-07518: Reason: Foreign database file DBID: 1345519754 Database Name: COOVZP. How can I fix this? If possible, I'd rather not change our database SID... we already have dozens of machines successfully connecting to the database and I don't want to have to go through and change them all. I'm fine with changing the DBID... I don't think that's used anywhere.
Jan 25, 2017 at 15:39 history answered Philᵀᴹ CC BY-SA 3.0