My standby got corrupted and I need to restore from Primary database. As it is already setup , no need to configure listener and tnsnames.
At Primary site
==========
1. After shutting down the primary database.
2. copying all .dbf and log files. (need to query v$datafile and v$logfile)
3. Copying archive logs. (not sure about this step)
4. Again restart, create control file for standby database.
5. Restart primary database.
Standby
=====
1. After changing the location of control file on standby parameter file (initSTANDBYDB.ora)
2. Startup nomount pfile='/pfile/location'
3. Mount the standby database.
4. Putting database in MRM mode.
I have One Production and one logical standby database . Due to tape problem we are unable to take backups of primary . And due to business , we cannot take back up on disk in hot period(Bank database ) .
If i take logical standby database backup(level 0 ) using RMAN , then will i be able to restore it on production dtbs (In case Production down) ? . Logical standby is in sync with primary .
I just duplicate my PRODUCTION database to TEST database (11.2.0.1 both) on windows 7.
I just create a backup from PRODUCTION:
RMAN> backup full database format ='C:Usersmy_usermiBBDDflash_recovery_are aTESTdatabase_%U';and controlfile backup:
RMAN> backup current controlfile format='C:Usersmy_usermiBBDDflash_recover y_areaTESTCONTROL_FILE_%U';now i'm trying to restore this backup into TEST with this script:
RMAN CONNECT TARGET / STARTUP NOMOUNT; SET DBID 486238190; #DBID of TEST database RUN
[Code]....
but i'm having a similar error when i tried to duplicate both databases ( post -->Error duplicate databases fallo de la recuperaci¾n del medio fÝsico canal liberado: c1
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: fallo del comando recover en 08/06/2012 11:53:06 ORA-00283: recovery session canceled due to errors RMAN-11003: fallo al analizar/ejecutar la sentencia SQL: alter database recover
if needed start until cancel using backup controlfile
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 1: 'C:USERSmy_userMIBBDDORADATAPRODUCTIONSYSTEM01. D BF' ORA-01157: cannot identify/lock data file 1 - see DBWR trace file ORA-01110: data file 1: 'C:USERSmy_userMIBBDDORADATAPRODUCTIONSYSTEM01.D BF'
Controlfile was restored correctly. what am I doing wrong?
I'm testing out various RMAN restore/recovery scenarios for 10g R1. Took a full level-0 backup of one of our larger databases (16 tb) and I'm trying to restore the whole thing on another server. While the backup was running (for about a day & a half), a few datafiles were added. The backup completed fine, including "backup current controlfile;". Now my restore is failing with "RMAN-06023: no backup or copy of datafile xxxx found to restore", with reference to the 4 files that were added while the backup was in progress.
I guess if the datafiles were added after the backup had finished, we'd be fine because they'd be created during recovery with our archive logs (we have all of those).
I found some suggestions for first doing a "restore controlfile;" -- did that and it worked fine -- then mounting the database and creating the datafiles manually. I added that to my RMAN restore script and tried it, like so:
run { allocate channel d4 type disk format '/BK01/dbX/stream1/df_%t_s%s_s%p' ; sql "alter database create datafile ''/uXX/oradata/dbX/datafile_58.dbf''"; restore database ; }
The datafiles were created successfully, and the restore began .. but then it failed with this:
creating datafile fno=4216 name=/uXX/oradata/dbX/datafile_58.dbf ... RMAN-03002: failure of restore command at 06/20/2013 17:27:28 ORA-01119: error in creating database file '/uXX/oradata/dbX/datafile_58.dbf ORA-27038: created file already exists
So RMAN seems to be telling me that if these 4 datafiles don't exist in the backupset, then RMAN won't automatically create them. But if I manually create them first, then RMAN will try to restore them and complain that they already exist. And for that matter, I would have expected that RMAN would be smart enough to detect that those 4 files were added while the backup was active, and just include them in the backup. Maybe there's something I needed to do to tell RMAN to do that?
This is just a test, so of course I can redo the backup from scratch and try again, but we have some pretty large databases which cannot be shut down for cold backups, so it's entirely possible this scenario could show up in a real disaster recovery. RMAN does such a good job of managing things.
i am trying to restore database using rman backup on same machine using command
RMAN> run { 2> set until sequence 23; 3> restore database; 4> recover database; 5> } but it will give me error. RMAN-00571: ======================================================= RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =========== RMAN-00571: ======================================================= RMAN-03002: failure of restore command at 03/31/2011 19:18:11 [code]....
I have dataguard configuration operating in maximum availability mode with a local standby db (A - lgwr sync not using real time apply) and a remote standby db (B - lgwr async). I then simualted a crash of my primary database with batch jobs running. Since the stby db A is in lgwr sync option ,all the commited data in the current online redo log has been transmitted to stby A and is present in its stby redo log (Group 2).How do I apply this stby redo log to the remote stby db.
Tried the following methods.
1.ftp the stby redo log to the remote db and tried to regiter it, got an error that it is not completely archived.
2.issued the recover standby database command and supplied the stby redo log when it asked for the sequence in the stby redo, got an error saying there is corruption in a block(tried this option multiple times ended up with the same result.)
I have an issue with restoring a RMAN backup that i have with me to a new database instance. What i have with me are: 1. Backup of SPFile.
(O1_MF_NCNNF_CTLFILE_BU_92DVGYO2_.BKP)2. Backup of Control file (O1_MF_NNSNF_SPFILE_BU_92DVGW9H_.BKP)3. Full database backup (O1_MF_NNSNF_FULLPROD_BU_92DVGW9H_.BKP)
I have received these files from a customer environment and I need to restore these to a new database instance in a local machine. I have given a attempt as follows (in Oracle 10g): 1, Created a new database instance (Test75) using Oracle Database Configuration Assistant2. SET ORACLE_SID = Test753. Connected to this instance using RMAN4. Tried to restore the SPFILE from the received BKP file.I am getting errors and cannot proceed. I am not sure whether I am executing the correct steps.
I've read a lot about the different types of backup available with Oracle (hot and cold backup). However, I was thinking of a different way of performing this task. I'm currently using Windows Server 2008 R2 and Oracle 11g Standard Edition. I'd like to schedule an entire backup of my server via the utility "Windows Server Backup" (available for free).That way, I could recover my entire server with all the programs and files in case the latter crashes.I'm wondering if this solution could be used as a way of backing up (and recovering) the Oracle database. Should I still set up a regular hot backup with the Archivelog mode enabled in case some operations/transactions were being done at the time of the crash (for the data integrity)?
I got a primary database with a logical standby database running Oracle 11g. I got two client applications, one is the production site pointing to the primary one, another one is just a backup site pointing to the logical one.Things will only be written into the primary database every mid night and client applications can only query the database but not add, update nor delete.And now, I want to apply the latest patch on both of my databases. I am also the DNS administrator, I can make the name server pointing to the backup site instead of the production one.I want to firstly apply the patch on the logical one, and then the physical one.
I found some reference which explains how to apply patches by adopting "Rolling Upgrade Method". however, I want to avoid doing any "switch over" mentioned in the reference because I can make use of name server. Can I just apply patches as the following way?
1)Stop SQL apply 2)Apply patches on logical standby database 3)let the name server point to the backup site 4)Apply patches on the primary database 5)Start SQL apply 6)Let the name server point back to the production site
If flashback is enable in physical standby database 1. If we failover at 11AM can I flash back NEW primary database to 6 AM ? 2. if I convert physically standby database to snapshot standby database at 11AM , Can I flashback snapshot standby database to 6 AM and do some works on it (DML operations) then converting the snapshot standby database into physical standby database ?
creating the standby database from Active database using RMAN and getting the below issue after i executed the duplicate command.
Version of Database:11g(11.2.0.1.0) Operating System:Linux 5 Error: RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of Duplicate Db command at 12/21/2012 17:26:52 RMAN-03015: error occurred in stored script Memory Script RMAN-04006: error from auxiliary database: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor [code]....
provide any work arounds to proceed further in creating the standby database.
I have installed oracle 11g standard edition one and created both primary and standby database. now i want to know how to switch(convert) primary database to standby database.
The script has successfully created on standby db all controlfiles and also has copied 2 data files DATA01.DBF and DATA02.DBF into the correct location. Then the errors above kicked in and stopped the rman dup process.
I am migrating one of my live database from 10g to 11g, which is having its standby database.how can we migrate standby database as well in 11g. do we need to create standby database again or is there any steps?
I am trying to create a physical standby database using the add standby database option within OEM 10g. This is something we have done numerous times before on 10g and 11g db's without a single issue, but for some reason, this time after selecting my RMAN backup location and staging area location , I am getting the following error when I click Next:
RMAN Backup Location - The specified RMAN backup is invalid. Could not identify controlfile from the backup
It is the latest backup (using RMAN catalog) from the previous evening and includes datafiles and control file.
Here is the output for List backup:
BS Key Size Device Type Elapsed Time Completion Time ------- ---------- ----------- ------------ --------------- 1741586 7.70G DISK 00:03:26 06-DEC-12 BP Key: 1741590 Status: AVAILABLE Compressed: NO Tag: TAG20121206T220033 Piece Name: /carebackup/oradata/CARELIVE/carelive/backup/df_CARELIVE_4811_1.bus
[code].....
The only difference between creating a standby for this db and others we have created is that the file system the backups are stored on is on a non-global zone shared via nfs mount.
I know that when I try and share that filesystem with other servers I get the message: share_nfs: Cannot share filesystems in non-global zones If the /backup filesystem is not shared with any other servers would OEM be able to read from that NGZ? The filesystem is available to connect to using ssh from other locations, but not sure how OEM handles this part of the process.
I need to rename an Oracle9i database on windows which has a physical standby database running on a different machine.
I have the steps to rename the primary database but am unsure of it's impact on the physical standby database. It seems like I will have to re-create the physical standby database, since renaming the primary database involves opening the db with "resetlogs". It's a production environment hence can't play with it without knowing the results.
we are getting below error on alert log file in logical standby database from May 2013 how can find time of sequence creation and how can restore these sequence redo files and sysnc databases primary and standby
Snipped of alert log: Wed Jun 10 15:29:40 2013 Fetching gap sequence in thread 1, gap sequence 62079-62178 Wed Jun 10 15:29:50 2013 Fetching gap sequence in thread 1, gap sequence 62079-62178 Wed Jun 10 15:30:01 2013 Fetching gap sequence in thread 1, gap sequence 62079-62178
I have changed from the "ARCH" attribute to "LGWR" attribute of the LOG_ARCHIVE_DEST_n initialization parameter. But I have not changed the protection mode(Maximum Performance). I would like to know whether there is any impact in the behavior of the database, if we do not change the mode from "MAXIMUM PERFORMANCE" to "MAXIMUM AVAILABILITY"?
We're currently in a situation where the primary database server fs size does not match the standby database server fs size.
Standby database filesystem is almost 100% utilized, and we suggested to move some of the datafiles first to avoid threshold alerts and archive gaps.
Now, if we're gonna move datafiles on the physical standby, I believe the process would be stop managed redo apply -> shutdown standby -> OS move -> startup mount -> alter rename -> start managed redo apply. Is this correct? If not, how?
Also, would it have an effect if the controlfiles of primary and standby do not match because of the movement?
I have a setup where i have one physical and logical standby from a primary database. In case of switch over between primary and physical database my logical apply gets stopped. Can a logical database be applied from a physical standby ?
I want to get the execute plan of a sql in standby database(read only),but failed,how can i do?
SQL> explain plan for select count(1) from hxl.tb_objects; explain plan for select count(1) from hxl.tb_objects * ERROR at line 1: ORA-00604: error occurred at recursive SQL level 2 ORA-16000: database open for read-only access
Suddenly I can't open any of my physical standby databases read only. Alert log snippet and trace files follow post. I'm running 9.2.0.1.0 on all hosts, which are running AIX 5.2. I've successfully opened all physical standby databases read only numerous times in the past. Is it possible that these standby databases cannot be switched over to primary should the need arise?
Here's how I typically open a physical standby database read only:
alter database recover managed standby database cancel; alter database open read only;
Errors in file /ora/product/9.2.0.1.0/rdbms/log/icps1_ora_27382.trc: ORA-00604: error occurred at recursive SQL level 1 ORA-16000: database open for read-only access Error 604 happened during db open, shutting down database USER: terminating instance due to error 604
we had our Oracle RAC database at primary and Standby database as DR. It was running in 10g (10.2.0.1.0) in HP UX 11i platform.
We need to upgrade both the setups from 10.2.0.1.0 to 10.2.0.4.0 . I will go through the upgrade guide, i like to know is there any special case for upgrading when we do for both primary and standby database.
And whether i need to create a new Oracle home with 10.2.0.4.0 software or i can upgrade in the same oracle home which already exists.
for rman backup with standby database with datagaurd but no active DG. I wanted to do a rman tablespace backup. but I am stuck at sql 'alter system archive log current' in rman with standby as target. which gives following errors with or without noswitch clause
RMAN> sql 'alter system archive log current noswitch';sql statement: alter system archive log current noswitch RMAN-00571: ===========================================================RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============RMAN-00571: ===========================================================RMAN-03009: failure of sql command on default channel at 10/05/2013 18:15:12RMAN-11003: failure during parse/execution of SQL statement: alter system archive log current noswitchORA-01109: database not open Recovery Manager: Release 11.2.0.1.0Oracle databaes Release 11.2.0.1.0 64 bitOS:RHEL 6 x86-64 bit Secondly,
do I need to cancel manged recovery while taking rman backups on standby. I scanned thru MOS but could find solutions for rman with active DG.
