Data Guard :: Ora-03113 Network I/O When Adding Standby To Broker
Dec 13, 2011
I got a primary database which ships logs successfully to a standby database where it is applied successfully as well.
I can connect using the tns name defined for data guard (which are already used for log shipping) in sqlplus.
Yet, at the time of configuring data guard broker,the command add database 'standby' connect identifier is 'to_standby'; fails.
Looking into drc<instance>.log, I see the error ora-03113 network I/O.
I haven't seen any error like that online and I can't explain why it does that when logs can ship already with the same connection identifier.
I have edited dest_2 with and without parameters LGWR and SYNC and reconfigured the broker without success. I've removed the configuration files and tried again.
I've checked that the password file is the same on both servers as well.Nothing seems to work. Is there a parameter I'm missing somewhere.
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 checked lots of pages but I'm not able to find a solution für my problem. I already set up a primary and a standby database (prim = ALPHA1 / standby = ALPHA2). After enabling my dgmgrl configuration I got two errors:
DGM-17016: failed to retrieve status for database "alpha2" ORA-16664: unable to receive the result from a database
The dg log from ALPHA1 says:
06/04/2013 16:06:57 Site alpha2 returned ORA-16664. Data Guard Broker Status Summary: Type Name Severity Status Configuration alphadgb Warning ORA-16607 Primary Database alpha1 Success ORA-00000 Physical Standby Database alpha2 Error ORA-16664
While the dg log from ALPHA2 (standby) says:
06/04/2013 16:43:28 SPFILE is missing value for property 'LogArchiveFormat' with sid='ALPHA2' Warning: Property 'LogArchiveFormat' has inconsistent values:METADATA='arch_ALPHA2_%S_%t_%r.arc', SPFILE='(missing)', DATABASE='arch_ALPHA2_%S_%t_%r.arc' Failed to connect to remote database alpha1. Error is ORA-12514 Failed to send message to site alpha1. Error code is ORA-12514.
How can I solve this issue? Every type of tnsping is successfull. The sqlplus login from the primary to the standby database works, the other way round works too! Therefore the tnsnames and listener data seems to be correct.
My configuration for ALPHA1 (primary db): --------------------------------------------------------------- Listener --------------------------------------------------------------- LISTENER_ALPHA1 = (DESCRIPTION_LIST = (DESCRIPTION = (ADDRESS_LIST =
I am fairly new to Oracle and have recently started learning the basics of Data Guard. I have set-up a Primary 11g database which successfully ships and applies logs to a Single Standby (on the same server) as expected. Manual switchovers work fine; however, I have found a slight problem when performing switchovers using the Data Guard Broker utility.
The switchover is successful- but the broker cannot restart the Primary instance. The strange thing is that when I perform a switchover in the opposite direction (i.e. the new Primary goes back to standby again) it works fine. The error is receive is: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor.
The majority of posts I have seen on this topic seem to point to incorrect listener / tnsnames set up but they have exactly the same values. If both databases are identical, why does it work one way but not the other? I will provide any necessary files to pinpoint where the issue could be.
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.)
1.create a primary database 2.duplicate a physical standby database; 3.turn on flashback on both databases. 4.record SCN xxx on physical standby database. 5.convert physical standby to logical standby (using keep identity statement) 6.flashback to logical standby to xxx 7.convert logical standby to physical standby 8.using real time apply I got errors: Fast Parallel Media Recovery enabledManaged Standby Recovery starting Real Time ApplyMRP0:
Background Media Recovery waiting for new incarnation during transient logical upgrade procedure
Errors in file /home ora/ app/ oracle/ diag/ rdbms/ ora11gr1dg/ora11gr1dg/trace/ora11gr1dg_mrp0_10120.trc:ORA-19906: recovery target incarnation changed during recoveryManaged Standby Recovery not using Real Time ApplyErrors in file /home/ ora/app/ oracle/diag/ rdbms/ ora11gr1dg/ ora11gr1dg/ trace/ora11gr 1dg_mrp0_ 10120.trc:ORA-19906: recovery target incarnation changed during recovery
Errors appears every 10 seconds. Seems MPR0 is waiting for new incarnation for a long time. So am I.Standby database incarnation:
List of Database IncarnationsDB Key Inc Key DB Name DB ID STATUS Reset SCN Reset Time-------1 1 ORA11GR1 3853851354 CURRENT 1 08/09/2013 01:02:182 2 ORA11GR1 3853851354 ORPHAN 2127877 08/28/2013 19:22:01 BGV
I am working in a bank as an system consultant, i have a SAN Storage Area and oracle as below.
SAN 1
This interface includes the DATA FILES of the oracle tablespace
SAN 2
SAN1 Mirrors the DATA FILES of the oracle tablespace to SAN 2
1. Can i rely on real time data recovery from SAN2 ? 2. if SAN1 (Data Files are currupted) will the SAN2 Data Files will be currupted as well. 3. If the SAN2 is currupted then what Oracle Features can be used to have uncurrupted data.
I have created 2 PCs (1 for Primary DB (IT_SERVER), 2 for Standby DB (IT_SERVER2) on Oracle VM Virtual Box in order to check my Data Guard configuration.
I have created a Shared Folder on 2nd PC (IT_SERVER2) for Oracle Standby DB. Now when I issue my query from 1st PC (Primary DB) to Create a Parameter file on 2nd PC Shared Oracle Folder, it returns following errors
SQL> CREATE PFILE='\IT_SERVER2E:ORACLEPFILESTLDB2.ORA' FROM SPFILE; CREATE PFILE='\IT_SERVER2E:ORACLEPFILESTLDB2.ORA' FROM SPFILE * ERROR at line 1: ORA-09210: sftopn: error opening file OSD-04002: unable to open file O/S-Error: (OS 67) The network name cannot be found.
Then I try this
SQL> CREATE PFILE=\IT_SERVER2'E:ORACLEPFILESTLDB2.ORA' FROM SPFILE; CREATE PFILE=\IT_SERVER2'E:ORACLEPFILESTLDB2.ORA' FROM SPFILE * ERROR at line 1: ORA-00911: invalid character
GROUP# THREAD# SEQUENCE# sizeMB ARC STATUS T ---------- ---------- ---------- ---------- --- ---------------- - 1 1 115 512 YES CLEARING O 2 1 116 512 YES CURRENT O 6 1 114 512 YES CLEARING O 4 1 112 512 YES CLEARING O 5 1 113 512 YES CLEARING O 3 1 111 512 YES CLEARING O
6 rows selected. [code]...
Above result is from standby database.I am trying to understand the concept of standby redo log.My stadby database protection_mode is MAXIMUM PERFORMANCE.
i have configured physical standby in my local system, to check logshipping i created a table at primary db, wen i tried to check in standby, it says table does not exist..below are primary & standby alert entries..
Primary alert log
Fatal NI connect error 12514, connecting to: (DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=172.16.0.98)(PORT=1522))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=STAND)(SERVER=dedicat ed)(CID=(PROGRAM=d:oracle11gappadministratorproduct11.1.0db_1inORACLE.EXE)(HOST=A960M)(USER=SYSTEM))(SERVER=dedicated))) VERSION INFORMATION: TNS for 64-bit Windows: Version 11.1.0.6.0 - Production
1) scn differs wrt primary in standby (i checked, 1day difference), how to make scn same?
2)i created a table in primary, its not refelecting in standby, (below i ve pasted alertlog entries)
ORA-27041: unable to open file OSD-04002: unable to open file O/S-Error: (OS 2) The system cannot find the file specified. Errors in file d:oracle11gappadministratordiag dbmsstandstand racestand_dbw0_6916.trc: ORA-01157: cannot identify/lock data file 2 - see DBWR trace file ORA-01110: data file 2: 'D:ORACLE11GAPPADMINISTRATORORADATASTANDSYSAUX01.DBF'
[code]....
3)wen i try to open standby database in read only mode gives below error..
ERROR at line 1: ORA-16004: backup database requires recovery ORA-01157: cannot identify/lock data file 1 - see DBWR trace file ORA-01110: data file 1: 'D:ORACLE11GAPPADMINISTRATORORADATASTANDSYSTEM01.DBF'
I have to implement Physical standby using same SID. parameters required to set on Primary and standby. Also what entries are required to do in TNS file. Recently we have faced hardware failure.
i have attended an interview there i got a question like--->There are 100 archives generated in standby in that a series of five archives are missing and those are not available in the primary then how will you do.....
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
I have an issue whereby our standby instance was down for a couple of days and when it came back online we found an archivelog file was missing, so recovery only happened up to a point. It appears that the archivelog was deleted therefore we are unable to continue with this standby. We are now planning to rebuild the standby database. As far as i know all of the steps originally performed need not be performed to complete this task.
1. Shutdown standby 2. Delete all datafiles & redo logs 3. Copy over datafiles to respective directories 4. Copy online logs and archivelogs to standby. 5. Create a control file for standby database 6. Startup mount standby database 7. start redo apply
We are planning to setup a data guard (Maximum performance configuration ) between two Oracle 9i databases on two different servers.
The archive logs on the primary servers are deleted via a RMAN job bases on a policy , just wondering how I should delete the archive logs that are shipped to the standby.
Is putting a cron job on the standby to delete archive logs that are say 2 days old the proper approach or is there a built in data guard option that would some how allow archive logs that are no longer needed or are two days old deleted automatically.
SQL> ALTER DATABASE OPEN READ ONLY; ALTER DATABASE OPEN READ ONLY * ERROR at line 1: ORA-16004: backup database requires recovery ORA-01194: file 1 needs more recovery to be consistent ORA-01110: data file 1: '/u01/app/oracle/oradata/PBLSTAN/system01.dbf'
I want to know that what will happen when I will resize database file from 32G to 5G on primary server or add file to tablespace. Will standby server do the same automatically or I have to to something with standby server?
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:
I've a primary database and a physical standby.Logs are shipping perfectly from primary to standby.The logs that are applied on the standby are getting stored in a mount point(LINUX-/opt2) which consumes more space(160 GB). Will that be right if I go ahead and delete them?
My rman configurations in primary is:
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 4; CONFIGURE BACKUP OPTIMIZATION OFF; # default CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default CONFIGURE CONTROLFILE AUTOBACKUP ON;
We recently configured data guard in test machine.Archives not applied in physical standby.Where i need to start investigation?
Primary SQL> select THREAD#,max(sequence#) from v$archived_log where applied='YES' group by thread#; THREAD# MAX(SEQUENCE#) ---------- -------------- 1 301 [code]...
Today, I am learning dataguard 11.2.0.1. The docs said:A. Monitoring Standby DB Application of redo logs may be monitored by issuing the SQL command:
SQL> select client_dbid, process, sequence#, status from v$managed_standby;
In the primary database, the sequence# with the status “WRITING” would refer to the current redo log sequence#In the standby database, if the status of the process MRPO is “APPLYING LOG” and the status of the process LGWR is “IDLE”, then application of redo logs is up to dateI see that that MRPO at standby is "WAIT_FOR_GAP". How do I resolve this gap.
We have a 11r2 primary and standby running on RHEL 5. The primary lost network connectivity for a time and VMWare locked up. The VM admin restarted the primary VM (it was a hard-boot). This all happened while I was gone and when I came into work, the primary database appeared to be working. I decided to dig deeper and check out the standby. On the standby...
My oracle version is 11.2.0.2 RAC RDBMS on RHEL 5.6.
At my standby site my physical standby database is on 4 node cluster with all 4 instances up. I need to disable 3,4 instances so that we want it to run on only 1,2 instances.To disable the instances do i need to stop apply(mrp) process. And the apply node is node 1.
