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.
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 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 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
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.
I was using physical standby but my primary database had had some HW issue.So I had activated standby database to handle production.During 3 months, standby database was our live database and our old primary was unavailable.Now HW issue on primary has been fixed.And I want to set again my old configuration : means set primary and standby db.
I have set up a single instance standbys for rac databases. Now, I need to offload the backups from the primary on to the standbys.
1. cancel managed recovery
2. connect to target(standby) and catalog and backup the standby
3. put standby in managed recovery mode.
I think following these steps, I can restore primary(?). Now, My question is, how can I use these standby backups to clone/refresh databases? I tried it by connecting to target(primary), catalog and auxiliary but rman is using the primary backups instead of standby's to refresh the auxiliary database.
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
I have a primary and standby DB using data guard 10.2.0.3.I want to upgrade oracle to 11G.I know that primary and standby should have same version even if data guard will not work again.I want to know what is the steps by steps action to properly upgrade both DB : primary and Standby.
I am trying to create the Standby database using RMAN.
I have first created an auxiliary instance followed by the password file for the instance and the registering it it listener.
Below are the parameters of the pfile of the standby database and followed by the command issued at the RMAN prompt.
PFILE parameters [STANDBY] orcl.__db_cache_size=293601280 orcl.__java_pool_size=8388608 orcl.__large_pool_size=8388608 orcl.__oracle_base='F:appdsharma'#ORACLE_BASE set from environment
I have Oracle database on Oracle 10g R2 with physical as well as logical standby database.
1) Is is necessary to take Physical standby database backup? 2) If 1) yes then Which RMAN backup is preferred?with catalog or default?How to take backup as different location? 3)how to Restore that backup?How to ensure backup is valid?
I have created a physical standby database and in it the logs are not getting applied.following is an extract of the standby alert log
Wed Sep 05 07:53:59 2012 Media Recovery Log /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc Error opening /u01/oracle/oradata/ABC/archives/1_37638_765704228.arc Attempting refetch Media Recovery Waiting for thread 1 sequence 37638 Fetching gap sequence in thread 1, gap sequence 37638-37643 Wed Sep 05 07:53:59 2012 RFS[46]: Assigned to RFS process 3081 RFS[46]: Allowing overwrite of partial archivelog for thread 1 sequence 37638 RFS[46]: Opened log for thread 1 sequence *37638* dbid 1723205832 branch 765704228 Wed Sep 05 07:55:34 2012 RFS[42]: Possible network disconnect with primary database
However, the archived files are getting copied to the standby server.I tried registering and recovering the logs but it also failed..Follows some of the information,
Primary Oralce 11R2 EE SQL> select max(sequence#) from v$log where archived='YES'; MAX(SEQUENCE#) -------------- 37668 [code]...
We already have one standby database, but now, I want to create another standby database on another server, which ultimately I will make primary and then replace and destroy our current primary/standby databases.
Also, just for the heck of it, I tried to look in our DB Console, and the "Add standby database" is grey'd out.
Is this because I am only using DB Console, and not Grid?But if that were the case, why would the option even be in DB Console, or perhaps is there a lmiitation to the number of standby databases you can manage with DB Console?
I successfully created the standby database and the archive logs were properly moving on both the primary and the standby databases. For the proper transfer of the archive logs on the STANDBY database I used "FAL_CLIENT AND FAL_SERVER" in the pfile of the primary database specifying the location of the primary and the Standby respectively.
When I removed both the parameters from the pfile of the primary database still there was the transfer of the archive logs however there should not be "If I am not wrong" as I have removed both the parameters.
why there is still the transfer of the archive logs on the standby database.
we have two primary databases (Oracle release 9.2.0.8, HP-UX 11.31) installed on the same server. The corresponding standby-databases (Oracle release 9.2.0.8, HP-UX 11.31)are configured on one server, too.It happens once in a while that the server of the standby-databases struggles and performs a shutdown. The primary- and standby-databases are configured with Data Guard. If the server of the standy-databases is not reachable anymore that should not really cause any problems,meaning that both primary databases can be used as usual. One of our primary database behaves like this: the applications can connect to the database and work like as expected. The other primary database behaves different: the applications can't connect anymore. But the database is still up and running. When looking at the alert.log file the following messages can be found:
Fri Oct 4 03:19:51 2013ARC1: Evaluating archive log 3 thread 1 sequence 335372ARC1: Unable to archive log 3 thread 1 sequence 335372 Log actively being archived by another processFri Oct 4 03:20:51 2013ARC1: Evaluating archive log 3 thread 1 sequence 335372ARC1: Unable to archive log 3 thread 1 sequence 335372 Log actively being archived by another processFri Oct 4 03:21:51 2013ARC1: Evaluating archive log 3 thread 1 sequence 335372ARC1: Unable to archive log 3 thread 1 sequence 335372 Log actively being archived by another process Fri Oct 4 03:22:51 2013ARC1: Evaluating archive log 3 thread 1 sequence 335372ARC1: Unable to archive log 3 thread 1 sequence 335372 Log actively being archived by another processFri Oct 4 03:23:51 2013ARC1: Evaluating archive log 3 thread 1 sequence 335372ARC1: Unable to archive log 3 thread 1 sequence 335372 Log actively being archived by another processFri Oct 4 03:24:51 2013ARC1: Evaluating archive log 3 thread 1 sequence 335372ARC1: Unable to archive log 3 thread 1 sequence 335372
Log actively being archived by another process Trying to connect to the database is not possible - the database seems to be busy with something... We have two archiver processes for each primary database. One process of the primary database which can't be reached anymore seems to hang. Executing the command SQL> alter system archive log all;seems to run forever. Instead of shutting down ands starting the instance killing one of the archiver-processes solves the issue. Maybe some of you have made the same experiences? I do not understand why the one database doesn't have any issues (which is expected behaviour) but the other database is not reachable anymore due to some issue with the archiving process.
i want to stop log shipping to standby database. the whole configuration was done by someone else and now i have been ask to stop it. it is done on test bases and now want to stop it.what i have got from internet is as follows:
Alter system set log_archive_dest_2='DEFER'; and i have got the fol error ORA-32107:failure in updating spfile ORA-16179:Incremental changes to "Log_archive_dest_2" not allowed
1> Does dataguard in 10g use ftp/rsh to transfer archived log files to standby database or some other protocol?
2> In my primary database, archives are getting generated normally, there is no error in alert log file. But archives are not getting transferred to standby database. I am able to connect through sys user from primary server to standby database & vice versa.
Also, tnsping is working fine.
All was working fine till 2 days back & no parameter has been changed from database side. I am not able to transfer the file manually through FTP to standby server. Does it is the problem? Or dataguard doesnt use FTP protocol to transfer the files?