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.
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 am trying to create the Physical StandBy Database in the same server. Till last 2 Final steps, everything went on well. In the final steps, when I try to open the StandBy Database, it throws the following Error:
******************************************************* SQL...> alter database open; alter database open * ERROR at line 1: ORA-01154: database busy. Open, close, mount, and dismount not allowed now
I tried creating the Physical Standby with the following Steps.into that & tell me whether I have done any mistake.Also tell me any step I have missed from the following list of steps:
Environment: Oracle Release 10.2.0.1.0 / Windows 2003 Server Enterprise Edition SP2 Primary DB = 'PrimDB' StandBy DB to be created = 'StBy1DB'
In the same Server, location for PrimDB datafiles = 'F:\oracle\product\10.2.0\oradata\PrimDB\Data\', StandBy Datafiles = 'E:\StandBy_DB\Data\'
[code]...
ERROR at line 1: ORA-01154: database busy. Open, close, mount, and dismount not allowed now
I am trying to create materialized views based on a few tables in a logical standby database.
The target database (11g R2) where the MVs will be created is a stand-alone database.
The DB where the base tables reside is a logical standby database (11g R2).
The requirement is to do a "FAST REFRESH" of the Materialized Views.
My questions are :
1. Can I create MV logs in the logical standby DB?
2. If the answer to question no. 1 is "Yes", do I need to do anything different or configure the logical standby DB in a specific manner in order to create MV logs. From what I understand, the objects in the logical standby database are in a locked state.
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 am currently running my production database server on win 2003 with oracle9i, I want to create a physical standby server, so I had created new server with same configuration. Need command to apply these datafiles and archives which are generating everyday in my primary database server.
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 ?
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?
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 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.
DB1 <Primary> - Production DB2 <Physial Standby> - DR
I will need to startup my DB2 in DR segment for testing.If i perform the below, will it affect my Production DB? I need it to be up and running as well.
DR: recover managed standby database cancel; shutdown immediate; startup nomount; alter database mount standby database; recover standby database until cancel; alter database activate standby database;
I need to drop standby database completeley and rebuilt physical standby for the same database. We identified there are lot of inconsistencies between primary and standby. How do i need to remove the standby? And what is the best procedure?
I was able to create the standby database on different server with the same name for the primary and standby database but I want to know that can I create a standby database with different database name than that of the primary database server.
