Data Guard :: Configuration - Incompatible Media Recovery Is Active
Dec 1, 2011
I have created dataguard between two instances hosted in two different servers. I have done switchover from primary to standby & then again standby to primary with DGMGRL utility.
1- When I done switchover to primary & trying to open standby database in readonly mode it was giving below error-
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
Why this error was coming ?
2- As I was not able to open standby database in read only mode, I have executed below command-
alter database recover managed standby database disconnect from session;
which return an error as-
ORA-01153: an incompatible media recovery is active
After this I have executed-
alter database recover managed standby database cancel;
which executed successfully.
& then after standby database open in read only mode.
Why above error was coming ?
3- After this I had tried to check the checkpoint_change# & controlfile_change# from primary database and result shows both number were different.
I noticed that my standby server was behind the prduction one.In the error log I noticed: ORA-00600: internal error code, arguments: [kcbr_apply_change_11], [], [], [], [], [], [], [], [], [], [], []
then MRP0: Background Media Recovery terminated with error 448 Recovered data files to a consistent state at change 286116915
This error happens in sequence: Recovery of Online Redo Log: Thread 1 Group 4 Seq 8830 Reading mem 0I found this archive log in standby and it is same size as in the production one.
I am getting starting with rac environments. I need to configure a two nodes active/active with rac and I need to know if always using rac both nodes will be active or if I have to do that at some point when installing. I have reading some docs from oracle and others authors about rac and its configuration process but that is not understood for my yet.
I have a database for which I use RMAN for backup & recovery. The database is in archivelog mode. Online redo log files are multiplexed and I have more than one destinations for archive logs. If, due to a disk crash, all data files and redo log files are gone - and I have archive logs, one member of each redo log group and a full database backup available, I can recover till the last archived log. But I want to ask that what about the transactions which were not archived at the time of media failure? How can I recover committed transactions which were not archived at the time of crash, and I have a mirrored copy of log group which was current at the time of failure?
Statspack has been configured for Active Dataguard on Primary database.We got an spike of Buffer busy waits for about 5 min in Active Dataguard, this was causing worse Application SQL's response time during this 5 min window.Below is what i got from statspack report for one hour
Snapshot Snap Id Snap Time Sessions Curs/Sess Comment ~~~~~~~~ ---------- ------------------ -------- --------- ------------------- Begin Snap: 18611 21-Feb-13 22:00:02 236 2.2 End Snap: 18613 21-Feb-13 23:00:02 237 2.1 Elapsed: 60.00 (mins) [code]...
Why there could sudden spike of demand on UNDO data in Active Data Guard ?
tell me about data guard accommodate with 11g database standard additions or not if no,is there any way to make it working under this edition?one more thing may i have the steps of configuration data guard in real time for anew server.
just realised the data guard configuration seems to be workin but the error kepps appearing on the alert log of both primary and physical standby that i configured. below is my primary and standby pfiles.
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_2='SERVICE=demodb' scope=both;
System altered.
SQL> ALTER SYSTEM SET LOG_ARCHIVE_DEST_STATE_2=ENABLE SCOPE=BOTH;
System altered.
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
Database altered.
SQL> recover managed standby database cancel; Media recovery complete. SQL> alter database open read only; alter database open read only * ERROR at line 1: ORA-16004: backup database requires recovery ORA-01152: file 1 was not restored from a sufficiently old backup ORA-01110: data file 1: '/u002/app/OraDB10g/stdemo/oradata/system01.dbf'
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH; ALTER DATABASE RECOVER MANAGED STANDBY DATABASE FINISH * ERROR at line 1:
- Oracle 11.2.0.3 - RHEL 4.6 64 bits - Active Data Guard - Broker configured - DBconsole configured on primary server
Now, I have server PRIM with the primary database, and server STB with the standby server. For now, the dbconsole is configured in the PRIM server.When I do a switchover (to the standby on STB), EM is not configured, so I use RepManager.sh to clean the sysman user, and I use emca to recreate the dbconsole. After this, everything works.
Once I switch back, the EM is no longer configured on PRIM, so I repeat the previous steps (repManager and emca). Everything is ok after this. I can access the EM on the primary normaly, and this gets information from the broker to provide basic information on the STB (like db status, apply, and so forth).
For the maximum protection and maximum availability as well as to enable Real Time Apply we need to setup the standby redo log group. My question is what would be the standby redo log group configuration in case if we setup single instance standby database for 2-Node RAC primary database. Do we require a separate standby redo thread for each primary online redo thread or RFS use the Multiple Standby redo group from the same thread to receive the redo changes from both the node ?
We have 10g physical standby set in our environment and we are migrating to 11g now. We want to use the active data guard feature of 11g to run the live reports on standby rather production. Questions I have is:
1) On our current 10g standby environment, we use db_name=cusms which is exactly matching with the production database name. I don't see we are using database_unique name on our standby. But I have read several blogs where everyone talks about using db_unique name on standby and db_name can be exactly matching with production on 11g. I wanted to know, is db_unique name a new requirement to have on 11g? can I go ahead and not use db_unique name and just have db_name exactly matching with production? What are the implications of doing so? The reason we want to stick to this is in-case of failover we want the database name to be the same. But I want to hear your thoughts on this:
2)While building standby, I did noticed few things and want your clarifications:
a.On standby database, should I mount instance using pfile or spfile or it doesn't matter? b. Lets say if I use either spfile or pfile, can I just have db_unique name in that file and just start the instance in no mount and do the duplicate from rman? c.As soon as my duplicate target database for standby from active database got finished, I usually exit the rman session and go to sqlplus and shutdown the standby instance. (Is this ok to do) d.Then I start the standby instance with startup (mount and open the database) this should open the standby database in read only mode. Following I issue alter database recover managed standby database using current logfile disconnect to put the database in recovery mode. (any steps missing here) e.Then go to primary and do few log switches and come back to standby to see if the primary changes moved to secondary or not.
But what I have observed is:
a. When I do the duplicate it runs successful. But during the course of duplicate, primary system generates few archives which are not shipped or applied on standby. When I go to standby to recover the database, it says media recovery needed and ask for archives files. I need to manually move this files from primary to standby to apply. Isn/t this automatically taken care? b. I also noticed after I can not open the standby database in read only mode after the duplicate command. While trying to open, it says database media recovery needed. What's the best procedure to open the database in read only mode immediately? c. On my standby init.ora lets say if I use db_unique name, where would my control file be place? Will oracle create controlfile from primary and put it on my standby database and put an update an entry into my pfile or spfile?
We are planning to create physical standby database for 4-node RAC primary to a 4-node RAC standby using Active database duplicate with ASM and OMF
1. while using active database duplicate, do we need to set cluster_database=FALSE in spfile clause and create standby,next change it back to TRUE at standby. Or we don't need to touch it. And also do we need to include instance_number parameter 2. We are using OMF, can we use log_file_name_convert parameter in spfile clause of duplicate. Documentation says log_file_name_convert cannot be used if standby is going to have OMF. Because we have 5 groups for each thread, which are on 5 different disk groups. When standby is created all the logs are created in only one disk group pointed by db_create_online_file_dest_1. 3. To enable force logging at primary do we need to shutdown the database?
I did standby before and it works wighout any disturbations and even configuration seems to me not very complicated - but it was before. now i am trying to do standby configuration once again. there is database named DESK.
two physical serwers: sczepl-db07 - primary r00979 - standby
on each for this serwer there is listener listening on port 1521, and on each is tnsnames configured properly:
We have a request to configure data guard for databases on the production server. Here is my situation:
We have a backup strategy in place where the backups are being taken on a regular basis. Archive logs are deleted as soon as they are backed up.
My question now is , is there a way of configuring the Data guard in such a way that there would be no change to existing backup strategy (RMAN) and still duplicate the archive logs to another destination and not delete the archive logs by RMAN backup process on that destination while the first destination is deleted.
We will be deleting the logs in the second archive destination using a script which checks if the logs were applied.
I am trying to move my data files from one location to other as i ran out of space.
SQL> alter database rename file 'C:oracleproduct10.2.0oradataSPF433SPF433ADW_DATA.DBF' to 'D:OracleDatafilesSPF433SPF433ADW_DATA.DBF'; Database Altered
SQL> alter database rename file 'C:oracleproduct10.2.0oradataSPF433SPF433ADW_DATATEMP.DBF' to 'D:OracleDatafilesSPF433SPF433ADW_DATATEMP.DBF' Database Altered
Now when i am trying to run Alter Database open I get ORA-01113: file 5 needs media recovery error
I have recently configure Data guard with Database 10g (10.2.0.4-64 bits) on Windows 2007 server.My Data Gurad Configuration show Success status with 2 databases on same (or local) location.My questions are
1-When I query SHOW PARAMETER LOG ARCH
DG_CONFIG(PRMDB)
ONLY 1 (PRIMARY DATABASE IS DISPLAYED ONLY NOT 2 DTATABASES e.g. DG_CONFIG(PRMDB, STLDB)
2- How to check the log applied interval or time (either transaction by transaction, timing etc)
I am using 64bit RHL machine which is with oracle 11g. i was having one problem earlier
ORA-01116: error in opening database file 6ORA-01110: data file 6: '/u01/app/oracle/product/11.2.0/db_1/dbs/tbs_data.dat'ORA-27041: unable to open fileLinux Error: 2: No such file or directory So what i did was SQL> select tablespace_name from dba_data_files where file_id = 6;SQL> alter tablespace sa offline immediate; RMAN> restore datafile 6;RMAN> recover datafile 6;
failure of recover command at 06/27/2013 13:31:44RMAN-06053: unable to perform media recovery because of missing log SQL> alter tablespace sa online;alter tablespace sa online*ERROR at line 1:ORA-01113: file 6 needs media recoveryORA-01110: data file 6: '/u01/app/oracle/product/11.2.0/db_1/dbs/tbs_data.dat'
what is the reason for this. There is no data in 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 just installed Oracle XE on my local computer Windows 7. When I run STARTUP command I get this error:
SQL> startup; ORACLE instance started. Total System Global Area 535662592 bytes Fixed Size 1384760 bytes Variable Size 226496200 bytes Database Buffers 301989888 bytes Redo Buffers 5791744 bytes Database mounted. ORA-01113: file 1 needs media recovery ORA-01110: data file 1: 'D:ORACLEXEAPPORACLEORADATAXESYSTEM.DBF'
I try to fix it by recover but unsuccessfully:
SQL> recover datafile 'D:ORACLEXEAPPORACLEORADATAXESYSTEM.DBF' ORA-00283: recovery session canceled due to errors ORA-16433: The database must be opened in read/write mode.
We are using oracle as database in our application. For high availability we have a cluster of multiple nodes and the data is replicated using oracle streams. All the nodes in the cluster are active. We do not have any concept of stand-by.
Now we are planning to use oracle RMAN for backup and recovery. RMAN user's guide doesn't recommend any strategies for such deployments. It mainly focuses on primary/stand-by deployments.
RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of crosscheck command at 06/30/2012 14:25:12 ORA-19554: error allocating device, device type: SBT_TAPE, device name: ORA-27211: Failed to load Media Management Library
RMAN> configure default device type to disk;
old RMAN configuration parameters: CONFIGURE DEFAULT DEVICE TYPE TO DISK; new RMAN configuration parameters: CONFIGURE DEFAULT DEVICE TYPE TO DISK; new RMAN configuration parameters are successfully stored
RMAN> show all;
RMAN configuration parameters are: CONFIGURE RETENTION POLICY TO REDUNDANCY 1; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; CONFIGURE CONTROLFILE AUTOBACKUP ON; CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO '%F'; # defa [code]....
in a RAC multi-node environment with single instance dataguard..Recovery is not running automatically I have to re-run the recovery command to make them sync and this command works for already archived log files no upcoming archive log file applied I have to re-run the recovery command again for newly archived log files.
I have a SAN systems with primary and secondary interfaces. i need to know what is best practice of oracle to use disaster recovery features, with automatic or manual failover concept.
example.
Primary Server Duty Station 1 New York
Secondary Server Duty Station 2 Los Angelous
requirement : If primary server in DS 1 gets fire and completed get down then secondary server DS 2 should become primary server and reply to client request with AUTO or Manual failover concept.
My standby database was working fine which was running in maximum performance mode .Suddenly i found that logs are not being applied though archived logs are received from primary database.i issued the command in mount mode: alter database recover managed standby database disconnect from session;
altered database this command runs successfully. but MRP process in not initiated which i confirmed with the query (select process,status from v$managed_standby;)
i have done oracle data guard between two databases (database A is the primary) and (database B is the standby), and it was working fine for two weeks, then the network admin did some changes on the firewall on standby side, which made the primary database can not write on standby redo log , so archives was generated on primary and do not generated on standby by, now we solve the firewall probelm and new archives generated on primary is generated on atandby too, but now i have a gap in archives on standby database and standby database now is not synchronized with primary database, and data changes happen on primary is not reflected on standby, also archives that were generated on primary and did not generated on standby during the problem time is not registered in V$ARCHIVED_LOG neither on primary database nor on standby database
Do we have any plan to create DR ( disaster site) for ORACLE 10G standard version. Since, Data Guard is not available with Standard version, can we have any another plan for the same.
