Standby database recovery error
Dear All,
When Im trying to apply redologs for my standby database, the following error is coming up
ORA-00279: change 276067636 generated at 08/22/2010 05:03:25 needed for thread 1
ORA-00289: suggestion : /oracle/BWP/oraarch/BWParch1_30490_684267445.dbf
ORA-00280: change 276067636 for thread 1 is in sequence #30490
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
AUTO
ORA-00283: recovery session canceled due to errors
ORA-00368: checksum error in redo log block
ORA-00353: log corruption near block 32769 change 276075175 time 08/22/2010 05:03:49
ORA-00334: archived log: '/oracle/BWP/oraarch/BWParch1_30490_684267445.dbf'
ORA-01112: media recovery not started
Could you please help out.
Thanks n Regards,
KK
Hi Stefan,
Oracle data guard is implemented by one of the expert on the same.
The following is result of the command you listed.
NAME TYPE VALUE
log_archive_dest string /oracle/BWP/oraarch/BWParch
log_archive_dest_1 string
log_archive_dest_10 string
log_archive_dest_2 string
log_archive_dest_3 string
log_archive_dest_4 string
log_archive_dest_5 string
log_archive_dest_6 string
log_archive_dest_7 string
log_archive_dest_8 string
log_archive_dest_9 string
NAME TYPE VALUE
log_archive_dest_state_1 string enable
log_archive_dest_state_10 string enable
log_archive_dest_state_2 string defer
log_archive_dest_state_3 string enable
log_archive_dest_state_4 string enable
log_archive_dest_state_5 string enable
log_archive_dest_state_6 string enable
log_archive_dest_state_7 string enable
log_archive_dest_state_8 string enable
log_archive_dest_state_9 string enable
Thanks,
Anees
Similar Messages
-
Standby database recovery problems....
HP-UX 11.23
oracle 10.2.0.2
I know that this has been discussed quite a bit. I've spent a number of hours on this forum alone today just reading through the search hits. I've tried some of the 'tricks' that have been described in the threads. But I'm still getting the same error....
My standby database lost connectivity with my primary, and stopped receiving logs. I got no notification, because my scripts were not set up to catch this event...
The retention policy on my primary is 30 days of archive logs. After that, they are deleted. (I don't agree with it, but not my call)
The standby got more than 30 days out of sync, so I decided to just refresh the whole standby.
Since cold backups are not an option, I did an alter system checkpoint to flush all archive logs. Then I issued a complete hot backup.
Once completed, I went ahead and created a fresh standby control file, as well as a fresh backup control file. In that exact order.
I transferred all db files, archive logs, and control files over to the standby.
I ran the commands:
startup nomount;
(SUCCESSFUL)
alter database mount standby database;
(SUCCESSFUL)
recover standby database;
I let it run through all the archive log files until it errored saying it couldn't find "X" file being the next sequence that wasn't in the directory. Which to my understanding, is normal...time to quit recovery.
When I entered cancel, I get the following error.
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00279: change 7313561157126 generated at 12/17/2008 19:01:02 needed for
thread 1
ORA-00289: suggestion : /oraarch/swesc/1_13729_640853326.arc
ORA-00280: change 7313561157126 for thread 1 is in sequence #13729
ORA-00278: log file '/oraarch/swesc/1_13728_640853326.arc' no longer needed for
this recovery
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
CANCEL
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: '/ora1/oradata/peregrine/system01.dbf'
So my understanding of this is that it means that you still need to apply logs.
So I grabbed the logs that had been auto created during the time that I was rebuilding everything and applied them.
Same errors.
I'm at a loss here. How can it still be out of sync? Is there a way to force it to a specific sequence so that I can successfully open it and then shut it down to complete the sequence?
Thanks.Thanks OrionNet. Great info!!
Here is the response.
OrionNet wrote:
select * from v$archive_gap
NO ROWS SELECTED.
and all the logs got applied
select applied , count(*) from v$archived_log;
-- This should return 1 rows with "YES", number of logs applied.
I had to change change this as it complained about "not a single-group group function
I changed it by adding group by applied to the end...
NO ROWS SELECTED
Then you should try activating standby database
SQL> alter database force nomount pfile='....'; -- or without the pfile
SQL> alter database mount standby database;
-- If all the archived logs have been applied to your standby then stop recovery
SQL> alter database recover manated standby cancel;
-- Note if it fails on activating the database ;shutdown and mount it again and activate (skip stopping recovery step).
SQL> alter database activate standby database;
IF successfull, then perform followin
SQL> alter database open;Regards
OrionNet;
I thought that in a primary/standby scenario, thiat this action would automatically shut down the primary. I can't have that.
HOLDING OFF ON REST FOR RESPONSE...
Edited by: WillyB on Dec 17, 2008 9:40 PM -
Standby database creating error oracle 10g
Hi
i created standby database,but i cannot access primary database data. the standby database opened read only.
but i cannot access data from primary.so i check query in standby database,
SQL> SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
no rows selected.
what i mistake
Regards
S.AzarIt you are not seeing any errors in the primary alert log, then I think that you have defined log_archive_dest_2 to use LOCATION instead of SERVICE. Archive logs have to be transmitted through Oracle Net in order to be automatically registered by the standby database.
Hope this helps.
Regards,
Satishbabu Gunukula
http://oracleracexpert.blogspot.com
[Backup and Recovery of OCR|http://oracleracexpert.blogspot.com/2009/08/backup-and-recovery-of-ocr-oracle.html] -
Standby Database gives error ORA-03113:ORA-03114
Hi
I am using oracle 9iR2 on standby database when i recover it return errors like
SQL> recover standby database;
ORA-00279: change 8209765386 generated at 07/18/2008 12:10:41 needed for thread
1
ORA-00289: suggestion : J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC
ORA-00280: change 8209765386 for thread 1 is in sequence #86548
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
auto
ORA-00279: change 8209782309 generated at 07/18/2008 12:22:05 needed for thread
1
ORA-00289: suggestion : J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86549.ARC
ORA-00280: change 8209782309 for thread 1 is in sequence #86549
ORA-00278: log file 'J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC' no
longer needed for this recovery
ORA-03113: end-of-file on communication channel
ORA-03114: not connected to ORACLE
Alert log display
Starting datafile 1 recovery in thread 1 sequence 86551
Datafile 1: 'E:\ORANT\ORADATA\APR1\SYSTEM01.DBF'
Starting datafile 3 recovery in thread 1 sequence 86551
Datafile 3: 'E:\ORANT\ORADATA\APR1\CWMLITE01.DBF'
Starting datafile 4 recovery in thread 1 sequence 86551
Datafile 4: 'E:\ORANT\ORADATA\APR1\DRSYS01.DBF'
Starting datafile 5 recovery in thread 1 sequence 86551
Datafile 5: 'E:\ORANT\ORADATA\APR1\EXAMPLE01.DBF'
Starting datafile 6 recovery in thread 1 sequence 86551
Datafile 6: 'E:\ORANT\ORADATA\APR1\INDX01.DBF'
Starting datafile 7 recovery in thread 1 sequence 86551
Datafile 7: 'E:\ORANT\ORADATA\APR1\ODM01.DBF'
Starting datafile 8 recovery in thread 1 sequence 86551
Datafile 8: 'E:\ORANT\ORADATA\APR1\TOOLS01.DBF'
Starting datafile 9 recovery in thread 1 sequence 86551
Datafile 9: 'J:\ORACLE\ORADATA\APR1\USERS01.DBF'
Starting datafile 10 recovery in thread 1 sequence 86551
Datafile 10: 'E:\ORANT\ORADATA\APR1\XDB01.DBF'
Starting datafile 11 recovery in thread 1 sequence 86551
Datafile 11: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_E.DBF'
Starting datafile 12 recovery in thread 1 sequence 86549
Datafile 12: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_C.DBF'
Starting datafile 13 recovery in thread 1 sequence 86550
Datafile 13: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_D.DBF'
Starting datafile 14 recovery in thread 1 sequence 86550
Datafile 14: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_A.DBF'
Starting datafile 15 recovery in thread 1 sequence 86548
Datafile 15: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_B.DBF'
Starting datafile 16 recovery in thread 1 sequence 86550
Datafile 16: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_A.DBF'
Starting datafile 17 recovery in thread 1 sequence 86550
Datafile 17: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_B.DBF'
Starting datafile 18 recovery in thread 1 sequence 86550
Datafile 18: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_A.DBF'
Starting datafile 19 recovery in thread 1 sequence 86549
Datafile 19: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_B.DBF'
Starting datafile 20 recovery in thread 1 sequence 86549
Datafile 20: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_C.DBF'
Starting datafile 25 recovery in thread 1 sequence 86550
Datafile 25: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_A.DBF'
Starting datafile 26 recovery in thread 1 sequence 86550
Datafile 26: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_B.DBF'
Starting datafile 27 recovery in thread 1 sequence 86550
Datafile 27: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_C.DBF'
Starting datafile 28 recovery in thread 1 sequence 86550
Datafile 28: 'J:\ORACLE\ORADATA\APR1\APR_MVIEWS_A.DBF'
Starting datafile 29 recovery in thread 1 sequence 86550
Datafile 29: 'J:\ORACLE\ORADATA\APR1\BLOB_A.DBF'
Starting datafile 30 recovery in thread 1 sequence 86549
Datafile 30: 'J:\ORACLE\ORADATA\APR1\HR_DATA1_A.DBF'
Starting datafile 31 recovery in thread 1 sequence 86548
Datafile 31: 'J:\ORACLE\ORADATA\APR1\HR_DATA2_A.DBF'
Starting datafile 32 recovery in thread 1 sequence 86550
Datafile 32: 'J:\ORACLE\ORADATA\APR1\HR_INDX1_A.DBF'
Starting datafile 33 recovery in thread 1 sequence 86550
Datafile 33: 'J:\ORACLE\ORADATA\APR1\HR_INDX2_A.DBF'
Starting datafile 34 recovery in thread 1 sequence 86548
Datafile 34: 'J:\ORACLE\ORADATA\APR1\INVENTORY_A.DBF'
Starting datafile 35 recovery in thread 1 sequence 86550
Datafile 35: 'J:\ORACLE\ORADATA\APR1\INVENTORY_INDX_A.DBF'
Starting datafile 36 recovery in thread 1 sequence 86550
Datafile 36: 'E:\ORANT\ORADATA\APR1\SAMPLE_DATA1_A.DBF'
Starting datafile 37 recovery in thread 1 sequence 86550
Datafile 37: 'J:\ORACLE\ORADATA\APR1\VMS_DATA1_A.DBF'
Starting datafile 38 recovery in thread 1 sequence 86550
Datafile 38: 'J:\ORACLE\ORADATA\APR1\APR_MMS_A.DBF'
Starting datafile 39 recovery in thread 1 sequence 86550
Datafile 39: 'J:\ORACLE\ORADATA\APR1\AUDIT_DATA_A.DBF'
Starting datafile 40 recovery in thread 1 sequence 86549
Datafile 40: 'J:\ORACLE\ORADATA\APR1\UNDOTBS.DBF'
Starting datafile 41 recovery in thread 1 sequence 86550
Datafile 41: 'J:\ORACLE\ORADATA\APR1\APR_DATA1_C.DBF'
Starting datafile 42 recovery in thread 1 sequence 86549
Datafile 42: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_E.DBF'
Starting datafile 43 recovery in thread 1 sequence 86548
Datafile 43: 'J:\ORACLE\ORADATA\APR1\APR_DATA2_C.DBF'
Starting datafile 44 recovery in thread 1 sequence 86550
Datafile 44: 'J:\ORACLE\ORADATA\APR1\APR_INDX1_E.DBF'
Starting datafile 46 recovery in thread 1 sequence 86550
Datafile 46: 'E:\ORANT\ORADATA\APR1\SYSTEM02.DBF'
Starting datafile 47 recovery in thread 1 sequence 86550
Datafile 47: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_A.DBF'
Starting datafile 48 recovery in thread 1 sequence 86549
Datafile 48: 'J:\ORACLE\ORADATA\APR1\APR_DATA4.DBF'
Starting datafile 49 recovery in thread 1 sequence 86550
Datafile 49: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_A.DBF'
Starting datafile 50 recovery in thread 1 sequence 86548
Datafile 50: 'J:\ORACLE\ORADATA\APR1\APR_DATA4_B.DBF'
Starting datafile 51 recovery in thread 1 sequence 86550
Datafile 51: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_B.DBF'
Starting datafile 52 recovery in thread 1 sequence 86550
Datafile 52: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_A.DBF'
Starting datafile 53 recovery in thread 1 sequence 86550
Datafile 53: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_B.DBF'
Starting datafile 54 recovery in thread 1 sequence 86550
Datafile 54: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_C.DBF'
Starting datafile 55 recovery in thread 1 sequence 86550
Datafile 55: 'J:\ORACLE\ORADATA\APR1\APR_DATA5_D.DBF'
Starting datafile 56 recovery in thread 1 sequence 86549
Datafile 56: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_C.DBF'
Starting datafile 57 recovery in thread 1 sequence 86550
Datafile 57: 'J:\ORACLE\ORADATA\APR1\APR_INDX3_F.DBF'
Starting datafile 58 recovery in thread 1 sequence 86550
Datafile 58: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_A.DBF'
Starting datafile 59 recovery in thread 1 sequence 86548
Datafile 59: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_B.DBF'
Starting datafile 60 recovery in thread 1 sequence 86549
Datafile 60: 'J:\ORACLE\ORADATA\APR1\APR_DATA6_C.DBF'
Starting datafile 61 recovery in thread 1 sequence 86549
Datafile 61: 'J:\ORACLE\ORADATA\APR1\APR_INDX4_D.DBF'
Starting datafile 62 recovery in thread 1 sequence 86550
Datafile 62: 'J:\ORACLE\ORADATA\APR1\APR_INDX5_A.DBF'
Starting datafile 63 recovery in thread 1 sequence 86550
Datafile 63: 'J:\ORACLE\ORADATA\APR1\APR_INDX5_B.DBF'
Starting datafile 64 recovery in thread 1 sequence 86550
Datafile 64: 'E:\ORANT\ORADATA\APR1\USERS01_A.DBF'
Starting datafile 65 recovery in thread 1 sequence 86550
Datafile 65: 'J:\ORACLE\ORADATA\APR1\GMT1_DATA.DBF'
Starting datafile 66 recovery in thread 1 sequence 86548
Datafile 66: 'J:\ORACLE\ORADATA\APR1\GMT1_INDX.DBF'
Starting datafile 67 recovery in thread 1 sequence 86550
Datafile 67: 'J:\ORACLE\ORADATA\APR1\APR_DATA7.DBF'
Starting datafile 68 recovery in thread 1 sequence 86550
Datafile 68: 'J:\ORACLE\ORADATA\APR1\APR_INDX7A.ORA'
Starting datafile 69 recovery in thread 1 sequence 86550
Datafile 69: 'J:\ORACLE\ORADATA\APR1\APR_INDX8_A.DBF'
Starting datafile 70 recovery in thread 1 sequence 86550
Datafile 70: 'J:\ORACLE\ORADATA\APR1\APR_INDX8_B.DBF'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
Wed Jul 23 11:26:24 2008
ALTER DATABASE RECOVER CONTINUE DEFAULT
Wed Jul 23 11:26:24 2008
Media Recovery Log J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86548.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Wed Jul 23 11:26:25 2008
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log J:\ORACLE\ORADATA\APR1\ARCHIVE\APR1T001S86549.ARC
Wed Jul 23 11:26:53 2008
Some recovered datafiles maybe left media fuzzy
Media recovery may continue but open resetlogs may fail
Wed Jul 23 11:26:53 2008
ARC0: terminating instance due to error 472
Instance terminated by ARC0, pid = 2100
Tell me the solution.
Thanks in advanceI think your database is not going in begin backup mode...
this is my standby database server Pratap is there any method to check backup mode .
Thanks -
Data Guard - MRP stuck issues on a physical standby database
Hi,
Oracle 11.2.0.3 DG running. When i do a switchover the physical standby database has error with following error
ARC0: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance <primaryDB> - Archival Error
On standby DB
SQL>select process, thread#, sequence#, status from v$managed_standby where process='MRP0';
PROCESS THREAD# SEQUENCE# STATUS
MRP0 1 548 APPLYING_LOG
So according to Oracle support link i executed following
SQL>recover managed standby database cancel;
SQL>recover automatic standby database;
The above seems to resolve the issue. What is causing is this?Hello again;
Those both look perfect. I combed through my notes and found nothing like this for your version.
Yes, I would open an SR since it appears you have done everything correct.
ORA-600 [3020] "Stuck Recovery" [ID 30866.1]
The "Known Bugs" section of the above has a few 11.2.0.3 entries.
Generally the MRP gets stuck because data Guard thinks there's a GAP, you run out of room in the FRA on the Standby, or redo logs are too small and the system is switching very fast.
Best Regards
mseberg
Later
Never asked you but this "log_archive_max_processes" can be set as high as 30.
Edited by: mseberg on Jul 16, 2012 8:01 PM
h2. Still later
Found this which is closer :
Bug 13553883 - Archiver stuck but no ORA-19xxx error in alert log (messages need changing) [ID 13553883.8] -
Trying to recover an standby database
- Oracle 10.2.0.4 Standard Edition
- O/S: Windows Server 2003
- Phisically Standby
We have primary and a standby database. My standby database was synchronized through copying archive redo logs from Primary to Standby. They were copied every 15 min to standby server and then they were recovered from there. Because a lot of archive logs were missed for ever, now my standby database is not synchronized with my primary.
In order to recover my Standby, one week ago I followed these instructions:
Step 1: On the standby database check the current scn.
STDBY> select current_scn from v$database;
CURRENT_SCN
2527075174
Step 2: On the primary database create the needed incremental backup from the above SCN
C:\Documents and Settings\frego>rman target /
run {
allocate channel c1 type disk;
BACKUP INCREMENTAL FROM SCN 2527075174 DATABASE
format '\\srvbackup\archiveslogs-35\arch\incr_bkp_%U';
Step 3: Cancel managed recovery at the standby database
STDBY>alter database recover managed standby database cancel;
Media recovery complete.
Copied the backup files to standby server to "D:\arch\" folder.
Step 4: Catalog the Incremental Backup Files at the Standby Database
D:\arch> rman target /
RMAN> CATALOG START WITH 'D:\arch\';
Step 5: Apply the Incremental Backup to the Standby Database
RMAN> RECOVER DATABASE NOREDO;
Step 6: Put the standby database back to managed recovery mode.
STDBY>> recover managed standby database disconnect;
Media recovery complete.
Step 7: On the primary create new standby controlfile
PRIM>alter database create standby controlfile as 'C:\incr_bkp\standby01.ctl';
System altered.
Step 8: At Standby .. Replace standby controlfile at all location as shown by controle_files parameter.
Copy the standby control file to the standby site. Shutdown the standby database and replace the stanby controlfiles and restart the >standby database in managed recovery mode...
Problem was that there were new datafiles created in primary that didn't exist in standby. I had to created them manually on standby:
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB3.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB3.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB4.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB4.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BKP.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BKP.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB5.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB5.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_A.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_A.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_B.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_B.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_C.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_C.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_D.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_DATA\SIPESG_BLOB_D.ORA';
ALTER DATABASE CREATE DATAFILE 'D:\ORADATA\PROD\OPEXT\DATAFILES_IDX\PADRONIDX17.ORA' AS 'D:\ORADATA\PROD\OPEXT\DATAFILES_IDX\PADRONIDX17.ORA';
Also, I tried this commands:
On Standby:
RMAN> SHUTDOWN;
RMAN> STARTUP NOMOUNT;
RMAN> RESTORE STANDBY CONTROLFILE FROM 'D:\arch\standby01.ctl';
RMAN> SHUTDOWN;
RMAN> STARTUP MOUNT;
STDB> ALTER DATABASE CLEAR LOGFILE GROUP 1;
STDB> ALTER DATABASE CLEAR LOGFILE GROUP 2;
STDB> ALTER DATABASE CLEAR LOGFILE GROUP 3;
STDB> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
Database altered.
SQL> alter database open read only;
alter database open read only
ERROR at line 1:
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
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: 'D:\ORADATA\PROD\OPEXT\SYSTEM01.DBF'My Questions:
- What is missing in order to open standby database?
- Can I again generate rman incremental backups on Primary (from SCN 2527075174), copy them to Standby and start recovery again? Would it generate duplicate records on tables?
- Should I generate new rman incremental backup pieces on Primary (from last SCN of Standby), copy them to standby and apply there?
Remember that my Primary is growing every day and those rman backup pieces and standby01.ctl, that are copied on my standby server, are from one week ago.
Thanks
Edited by: user521219 on 22-jun-2012 9:31user521219 wrote:
Should I restart and mount my standby database again?
If I apply Step 3 now:
STB> alter database recover managed standby database cancel;
ERROR at line 1:
ORA-16136: Managed Standby Recovery not activeRefer the above mentioned link. First restore controlfile & then perform recovery on standby database.
>
user521219
Newbie
Handle: user521219
Status Level: Newbie
Registered: Jul 20, 2006
Total Posts: 48
Total Questions: 29 (23 unresolved)
>
Consider closing your threads and keep the forum clean.
Edited by: CKPT on Jun 22, 2012 10:43 PM -
Data Guard Broker connecting to standby database fails
Hello everybody
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 =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1521))
SID_LIST_LISTENER_ALPHA1 =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = ALPHA1_DGMGRL)
(ORACLE_HOME = /oracle/ALPHA1/orahome)
(SID_NAME = ALPHA1)
tnsnames.ora
ALPHA1.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(CONNECT_DATA =
(SID = ALPHA1)
ALPHA2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1522))
(CONNECT_DATA =
(SID = ALPHA2)
DG_ALPHA1.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = ALPHA1_DGMGRL)
DG_ALPHA2.WORLD =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = 10.12.3.13)(PORT = 1522))
(CONNECT_DATA =
(SERVICE_NAME = ALPHA2_DGMGRL)
Parameters
archive_lag_target integer 0
log_archive_config string DG_CONFIG=(ALPHA2,ALPHA1)
log_archive_dest string
log_archive_dest_1 string LOCATION=USE_DB_RECOVERY_FILE_DEST valid_for=(all_logfiles,all_roles) DB_UNIQUE_NAME=ALPHA2
log_archive_dest_2 string SERVICE=ALPHA1 SYNC valid_for=(online_logfiles,primary_role) DB_UNIQUE_NAME=ALPHA1
log_archive_format string arch_ALPHA2_%S_%t_%r.arc
log_archive_local_first boolean TRUE
log_archive_max_processes integer 4
log_archive_min_succeed_dest integer 1
log_archive_start boolean FALSE
log_archive_trace integer 0
standby_archive_dest string ?/dbs/arch
For the DG Broker configuration
DGMGRL> connect sys/dgalpha42@DG_ALPHA1
DGMGRL> create configuration ALPHADGB
DGMGRL> primary database is ALPHA1
DGMGRL> connect identifier is DG_ALPHA1
DGMGRL> ;
DGMGRL> add database ALPHA2
DGMGRL> connect identifier is DG_ALPHA2
DGMGRL> maintained as physical
DGMGRL> ;
There were no errors.
DGMGRL> show database verbose ALPHA1
Database - alpha1
Role: PRIMARY
Intended State: TRANSPORT-ON
Instance(s):
ALPHA1
Properties:
DGConnectIdentifier = 'dg_alpha1'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA2, ALPHA1'
LogFileNameConvert = 'ALPHA2, ALPHA1'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA1'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA1_DGMGRL)(INSTANCE_NAME=ALPHA1)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA1_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
SUCCESS
DGMGRL> show database verbose ALPHA2
Database - alpha2
Role: PHYSICAL STANDBY
Intended State: APPLY-ON
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
ALPHA2
Properties:
DGConnectIdentifier = 'dg_alpha2'
ObserverConnectIdentifier = ''
LogXptMode = 'SYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA1, ALPHA2'
LogFileNameConvert = 'ALPHA1, ALPHA2'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA2'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA2_DGMGRL)(INSTANCE_NAME=ALPHA2)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA2_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DGM-17016: failed to retrieve status for database "alpha2"
ORA-16664: unable to receive the result from a database
Can anybody help me to find a solution for this?Hey
thanks for the answer. I followed you recommendations but I got the same error again. I restored/recovered the old status and looked deeper into the dgmgrl configuration before enabling. I found an interesting point. (show database verbose ALPHAx)
Database - alpha1
Role: PRIMARY
Intended State: OFFLINE
Instance(s):
ALPHA1
Properties:
DGConnectIdentifier = 'dg_alpha1'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'optional'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA2, ALPHA1'
LogFileNameConvert = 'ALPHA2, ALPHA1'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA1'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA1_DGMGRL)(INSTANCE_NAME=ALPHA1)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA1_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DISABLED
Database - alpha2
Role: PHYSICAL STANDBY
Intended State: OFFLINE
Transport Lag: (unknown)
Apply Lag: (unknown)
Real Time Query: OFF
Instance(s):
ALPHA2
Properties:
DGConnectIdentifier = 'dg_alpha2'
ObserverConnectIdentifier = ''
LogXptMode = 'ASYNC'
DelayMins = '0'
Binding = 'OPTIONAL'
MaxFailure = '0'
MaxConnections = '1'
ReopenSecs = '300'
NetTimeout = '30'
RedoCompression = 'DISABLE'
LogShipping = 'ON'
PreferredApplyInstance = ''
ApplyInstanceTimeout = '0'
ApplyParallel = 'AUTO'
StandbyFileManagement = 'AUTO'
ArchiveLagTarget = '0'
LogArchiveMaxProcesses = '4'
LogArchiveMinSucceedDest = '1'
DbFileNameConvert = 'ALPHA1, ALPHA2'
LogFileNameConvert = 'ALPHA1, ALPHA2'
FastStartFailoverTarget = ''
InconsistentProperties = '(monitor)'
InconsistentLogXptProps = '(monitor)'
SendQEntries = '(monitor)'
LogXptStatus = '(monitor)'
RecvQEntries = '(monitor)'
SidName = 'ALPHA2'
StaticConnectIdentifier = '(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=oraprakt)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=ALPHA2_DGMGRL)(INSTANCE_NAME=ALPHA2)(SERVER=DEDICATED)))'
StandbyArchiveLocation = 'USE_DB_RECOVERY_FILE_DEST'
AlternateLocation = ''
LogArchiveTrace = '0'
LogArchiveFormat = 'arch_ALPHA2_%S_%t_%r.arc'
TopWaitEvents = '(monitor)'
Database Status:
DISABLED
As the listener are configured ALPHA1 (prim) should be on port 1521 while ALPHA2 (stby) should work on 1522. In the configuration of DGMGRL only appears port 1521 (look at StaticConnectIdentifier). Is this maybe the reason of the networking problems with DG Broker? How can I fix this?
Regards Mirko
Edited by: 1009733 on 04.06.2013 09:22 -
Hi anyone,
im trying to create physical standby db, oracle10g release 1 running on windows NT. currently i cannot mount the standby database receive error as:
SQL> alter database mount standby database;
alter database mount standby database
ERROR at line 1:
ORA-01102: cannot mount database in EXCLUSIVE mode
and when i shutdown the primary db, i retry to mount standby db but receive another error,
SQL> alter database mount standby database;
alter database mount standby database
ERROR at line 1:
ORA-01665: controlfile is not a standby controlfile
what should i do?
can someone advice me?
regards,
Nonieim trying to create physical standby db, oracle10g
release 1 running on windows NT. currently i cannot
mount the standby database receive error as:
SQL> alter database mount standby database;
alter database mount standby database
ERROR at line 1:
ORA-01102: cannot mount database in EXCLUSIVE mode
Look likes , you setup standby on same machine , try init.ora parameter LOCK_NAME_SPACE. Also make sure you use standby control file for standby database.
ALTER DATABASE CREATE STANDBY CONTROLFILE AS '<location>'
- Virag Sharma
http://virag.sharma.googlepages.com
http://viragsharma.blogspot.com -
Physical standby database backup issue
Hello
We have a Data Guard environment if I open Physical Standby database for query by this statement:
"Alter database recover managed standby database cancel" and then start redo apply by
"alter database recover managed standby database using current logfile" and then backup the Physical standby database by RMAN
for example
RMAN> backup database;
I will get this error :
Starting backup at 03-FEB-09
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 02/03/2009 15:36:45
ORA-01219: database not open: queries allowed on fixed tables/views only
but if before restarting redo apply after opening standby database for query I shutdown the database first and then start redo apply I don't get that error while backing up
If DataGuard mode is Maximum Performance or Maximum Availability shutting down the standby database before
restarting redo apply is possible but if DataGuard mode is Maximum Protection shutting down the standby database
cause failing Primary database
do you know what is problem and it's solution ?
thankslike I said bro, i have made standby controlfile....
I made it on Primary Database (DG1)...........
but when I copied it to Physical Standby Database, the error message raised "DBID IS NOT SAME",
thanks Renato OCP for uR attention..........
is there any other suggestion.............?
regards
abip -
Problem in switchover to physical standby database
Hi All,
I am doing switchover from primary to physical standby database. Physical standby is in 'managed recovery' mode using real time apply and is in mount mode. I executed alter database commit to switchover to physical standby with session shutdown command. Now i am waiting for standby mrp to exit after processing eor record, but it seems mrp was hanged.
Below is the content from standby database:
Recovery of Online Redo Log: Thread 1 Group 5 Seq 620 Reading mem 0
Mem# 0: /oracle/app/oracle/dbrac/th1-redo5a.log
Resetting standby activation ID 749049115 (0x2ca5951b)
Media Recovery End-Of-Redo indicator encountered
Media Recovery Continuing
Media Recovery Waiting for thread 1 sequence 621
Archived Log entry 14 added for thread 1 sequence 620 ID 0x2ca5951b dest 1:
Need some help to resolve.
Thanks
Sandy.Hello;
After after you issue ( successfully ) a :
alter database commit to switchover to physical standby with session shutdownYou need to :
Shutdown the former primary and mount as a standby databaseCheck out my step by step :
http://www.visi.com/~mseberg/data_guard/Data_Guard_switchover.html
Read everything ( all the steps ) before you proceed.
Best Regards
mseberg -
Error while trying to open physical standby database - (DATA GUARD)
Hi Everyone,
I have problems in opening the database of the physical standby in read- write mode/ read only mode. I have a primary server which is running on 2 node RAC and the standby on a seperate single server being used as DR. I recently got this server and my aim was to isolate the standby server from primary server and perform few test. As it has never been tested even once.
Primary Database spec: (2 Node Rac on ASM)
Oracle Version : 10.2.0.3.0
O/s : HP-UX B.11.23
Standby Database spec: (Single Node)
Oracle Version : 10.2.0.3.0
O/s: HP-UX db01 B.11.23
Error:
alter database recover managed standby database cancel;
Database altered.
SQL> alter database open
2 ;
alter database open
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: '+DATA/dprod/datafile/system01.dbf'
Parameters :
log_archive_dest_2 string SERVICE=PROD1 LGWR ASYNC VALID
FOR=(ONLINELOGFILES,PRIMARY_
ROLE) DB_UNIQUE_NAME=PROD
remote_archive_enable string true
fal_client string DPROD
fal_server string PROD1, PROD2
Steps tried so far:
Changed log_archive_dest_2 = DEFER on both the primary nodes
Standby :
startup nomount
alter database mount standby database;
alter database recover managed standby database disconnect;
alter database recover managed standby database cancel;
alter database open/readonly (tried both)
Same error.
On Primary:
SQL> select max(sequence#) from v$log_history;
MAX(SEQUENCE#)
55702
on Standby:
MAX(SEQUENCE#)
33289
Primary Database:
SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#;
SEQUENCE# FIRST_TIME NEXT_TIME
55700 13-JUN-11 13-JUN-11
55700 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
55702 13-JUN-11 13-JUN-11
60824 rows selected.
Standby Database:
SEQUENCE# FIRST_TIME NEXT_TIME
55698 13-JUN-11 13-JUN-11
55699 13-JUN-11 13-JUN-11
55700 13-JUN-11 13-JUN-11
55701 13-JUN-11 13-JUN-11
15206 rows selected.
Additional Information :
There is a delay of 20 minutes before the logs get applied. which has been intentional set by team.
Any help will be highly appreciated. Thanks in advance
SadiqHi,
Primary Database:
select status,checkpoint_count from v$datafile_header;
STATUS CHECKPOINT_COUNT
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
STATUS CHECKPOINT_COUNT
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 672472065
ONLINE 59736
ONLINE 59736
ONLINE 59736
ONLINE 59736
ONLINE 59736
STATUS CHECKPOINT_COUNT
ONLINE 57717
ONLINE 57717
57 rows selected.
Standby Database;
select status,checkpoint_count from v$datafile_header;
STATUS CHECKPOINT_COUNT
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445072
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
STATUS CHECKPOINT_COUNT
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 672445071
ONLINE 32742
ONLINE 32742
ONLINE 32742
ONLINE 32742
ONLINE 32742
STATUS CHECKPOINT_COUNT
ONLINE 30723
ONLINE 30723
57 rows selected.
Archieve log list :
Primary database:
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 49110
Next log sequence to archive 49111
Current log sequence 49111
Standby Database:
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination USE_DB_RECOVERY_FILE_DEST
Oldest online log sequence 49110
Next log sequence to archive 0
Current log sequence 49111
I tried log switch multiple times in primary database i saw that its getting highlighted in standby database. -
ERROR in creating a Physical Standby Database
Hello all,
I am using a Windows Vista O/S and Oracle 10g Enterprise Edition. Both my primary and standby are on the same host. Created standby instance using oradim.
I have followed instruction in the documentation and created a manual standby database.
primary database is 'orcl'
standby database is 'stby'
My primary archives is not being copied to the the stby location as confirmed by an error shown:
SQL> select dest_name, status from v$archive_dest_status
DEST_NAME
STATUS
LOG_ARCHIVE_DEST_1
VALID
LOG_ARCHIVE_DEST_2
ERROR
Also my standby does not open in read only mode, error:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
ERROR at line 1:
ORA-01153: an incompatible media recovery is active
SQL> ALTER DATABASE open read only;
ALTER DATABASE open read only
ERROR at line 1:
ORA-01154: database busy. Open, close, mount, and dismount not allowed now
I have copied both my prim and stby init.ora here for your reference
PRIMARY INIT
============================================
orcl.__db_cache_size=394264576
orcl.__java_pool_size=20971520
orcl.__large_pool_size=4194304
orcl.__shared_pool_size=184549376
orcl.__streams_pool_size=0
*.audit_file_dest='E:\oracle\product\10.2.0\admin\orcl\adump'
*.background_dump_dest='E:\oracle\product\10.2.0\admin\orcl\bdump'
*.compatible='10.2.0.3.0'
*.control_files='E:\oracle\product\10.2.0\oradata\orcl\control01.ctl'
*.core_dump_dest='E:\oracle\product\10.2.0\admin\orcl\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='orcl'
*.db_unique_name=orcl
*.db_recovery_file_dest_size=2147483648
*.db_recovery_file_dest='E:\oracle\product\10.2.0\flash_recovery_area'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
*.job_queue_processes=10
*.nls_language='ENGLISH'
*.nls_territory='UNITED KINGDOM'
*.open_cursors=300
*.pga_aggregate_target=203423744
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=611319808
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='E:\oracle\product\10.2.0\admin\orcl\udump'
*.standby_file_management=AUTO
*.log_archive_dest_1='location=E:\oracle\product\10.2.0\flash_recovery_area\orcl\archivelog valid_for=(all_logfiles,primary_role) db_unique_name=orcl'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_2='SERVICE=stby LGWR ASYNC valid_for=(online_logfiles,primary_role) db_unique_name=stby'
*.log_archive_dest_state_2='ENABLE'
*.log_archive_config='DG_CONFIG=(orcl,stby)'
*.db_file_name_convert='orcl','stby'
*.fal_client='orcl'
*.fal_server='stby'
*.db_file_name_convert='E:\oracle\product\10.2.0\oradata\stby', 'E:\oracle\product\10.2.0\oradata\orcl'
*.log_file_name_convert='E:\oracle\product\10.2.0\oradata\stby', 'E:\oracle\product\10.2.0\oradata\orcl'
*.standby_file_management=AUTO
======================================
STANDBY INIT.ora
stby.__db_cache_size=423624704
stby.__java_pool_size=4194304
tby.__large_pool_size=4194304
stby.__large_pool_size=4194304
stby.__shared_pool_size=171966464
stby.__streams_pool_size=0
*.audit_file_dest='E:\oracle\product\10.2.0\admin\stby\adump'
*.background_dump_dest='E:\oracle\product\10.2.0\admin\stby\bdump'
*.compatible='10.2.0.3.0'
*.control_files='E:\oracle\product\10.2.0\oradata\stby\CONTROL_SB01.CTL'
*.core_dump_dest='E:\oracle\product\10.2.0\admin\stby\cdump'
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_file_name_convert='orcl','stby'
*.db_name='orcl'
*.db_recovery_file_dest_size=2147483648
*.db_recovery_file_dest='E:\oracle\product\10.2.0\flash_recovery_area\STBY'
*.db_unique_name='stby'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=orclXDB)'
*.fal_client='stby'
*.fal_server='orcl'
*.job_queue_processes=10
*.log_archive_config='DG_CONFIG=(orcl,stby)'
*.log_archive_dest_1='location=E:\oracle\product\10.2.0\flash_recovery_area\stby valid_for=(all_logfiles,primary_role) db_unique_name=stby'
*.log_archive_dest_2='SERVICE=stby LGWR ASYNC valid_for=(online_logfiles,primary_role) db_unique_name=orcl'
*.log_archive_dest_state_1='ENABLE'
*.log_archive_dest_state_2='ENABLE'
*.log_file_name_convert='E:\oracle\product\10.2.0\oradata\orcl','E:\oracle\product\10.2.0\oradata\stby'
*.nls_language='ENGLISH'
*.nls_territory='UNITED KINGDOM'
*.open_cursors=300
*.pga_aggregate_target=203423744
*.processes=150
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=611319808
*.standby_archive_dest='USE_DB_RECOVERY_FILE_DEST'
*.standby_file_management='AUTO'
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='E:\oracle\product\10.2.0\admin\stby\udump'
=================================================
Any help would be much appreciated. Apologies for my ignorance!
Thanks!
null
nullOK that solves part of the problem.
Now this is very strange error I am getting. The path it looks to recover from archive is not right, it should point as per my actual archive log dest. See below.
Standby:
=================
SQL> alter database open;
alter database open
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: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SYSTEM01.DBF'
SQL> recover standby database until cancel;
ORA-00279: change 619067 generated at 06/22/2008 13:20:14 needed for thread 1
ORA-00289: suggestion :
E:\ORACLE\PRODUCT\10.2.0\DB_1\RDBMS\ARC00006_0658028298.001
ORA-00280: change 619067 for thread 1 is in sequence #6
Specify log: {<RET>=suggested | filename | AUTO | CANCEL}
ORA-00308: cannot open archived log
'E:\ORACLE\PRODUCT\10.2.0\DB_1\RDBMS\ARC00006_0658028298.001'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 2) The system cannot find the file specified.
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01152: file 1 was not restored from a sufficiently old backup
ORA-01110: data file 1: 'E:\ORACLE\PRODUCT\10.2.0\ORADATA\STBY\SYSTEM01.DBF'
==================================================
Why is not pointing to the destination below, where the above archives reside??
=====================================
SQL> archive log list
Database log mode Archive Mode
Automatic archival Enabled
Archive destination E:\oracle\product\10.2.0\flash_recovery_area\stby
Oldest online log sequence 12
Next log sequence to archive 0
Current log sequence 14
================= -
Hi Guys..
I am using oracle 10.2.0.4.0 on windows 2003 server. I created a physical standby database successfully.
On standby database, I fired the following query
SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#
SEQUENCE# FIRST_TIM NEXT_TIME
10715 02-AUG-10 02-AUG-10
10716 02-AUG-10 02-AUG-10
10717 02-AUG-10 03-AUG-10
10718 03-AUG-10 03-AUG-10
10719 03-AUG-10 03-AUG-10
10720 03-AUG-10 03-AUG-10
10721 03-AUG-10 03-AUG-10
10722 03-AUG-10 03-AUG-10
10723 03-AUG-10 03-AUG-10
10724 03-AUG-10 03-AUG-10
10725 03-AUG-10 03-AUG-10
SEQUENCE# FIRST_TIM NEXT_TIME
10726 03-AUG-10 03-AUG-10
10727 03-AUG-10 03-AUG-10
10728 03-AUG-10 03-AUG-10
10729 03-AUG-10 03-AUG-10
I then did alter system switch logfile on primary database
Then on standby I fired the above query
SELECT SEQUENCE#, FIRST_TIME, NEXT_TIME FROM V$ARCHIVED_LOG ORDER BY SEQUENCE#
SEQUENCE# FIRST_TIM NEXT_TIME
10715 02-AUG-10 02-AUG-10
10716 02-AUG-10 02-AUG-10
10717 02-AUG-10 03-AUG-10
10718 03-AUG-10 03-AUG-10
10719 03-AUG-10 03-AUG-10
10720 03-AUG-10 03-AUG-10
10721 03-AUG-10 03-AUG-10
10722 03-AUG-10 03-AUG-10
10723 03-AUG-10 03-AUG-10
10724 03-AUG-10 03-AUG-10
10725 03-AUG-10 03-AUG-10
SEQUENCE# FIRST_TIM NEXT_TIME
10726 03-AUG-10 03-AUG-10
10727 03-AUG-10 03-AUG-10
10728 03-AUG-10 03-AUG-10
10729 03-AUG-10 03-AUG-10
*10730 03-AUG-10 03-AUG-10*
My question is everytime I do alter systyem switch logfile on primary , two trace files are generated on primary database which are:
stutest_lns1_5764.trc
Dump file c:\oracle\admin\stutest\bdump\stutest_lns1_5764.trc
Tue Aug 03 15:50:35 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 8 - type 8664, 2 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:8414M/16378M, Ph+PgF:10750M/17814M
Instance name: stutest
Redo thread mounted by this instance: 1
Oracle process number: 43
Windows thread id: 5764, image: ORACLE.EXE (LNS1)
*** SERVICE NAME:(SYS$BACKGROUND) 2010-08-03 15:50:35.996
*** SESSION ID:(213.29604) 2010-08-03 15:50:35.996
*** 2010-08-03 15:50:35.996 60512 kcrr.c
LNS1: initializing for LGWR communication
LNS1: connecting to KSR channel
Success
LNS1: subscribing to KSR channel
Success
*** 2010-08-03 15:50:35.996 60565 kcrr.c
LNS1: initialized successfully ASYNC=1
Destination is specified with ASYNC=61440
Redo shipping client performing standby login
*** 2010-08-03 15:50:36.043 68145 kcrr.c
Logged on to standby successfully
Client logon and security negotiation successful!
Archiving to destination STUSTDBY ASYNC blocks=20480
Allocate ASYNC blocks: Previous blocks=0 New blocks=20480
Log file opened [logno 2]
*** 2010-08-03 16:00:58.344
Archiving to destination STUSTDBY ASYNC blocks=20480
Log file opened [logno 1]
*** 2010-08-03 16:04:44.383
Archiving to destination STUSTDBY ASYNC blocks=20480
Log file opened [logno 3]
*** 2010-08-03 16:07:36.794
Archiving to destination STUSTDBY ASYNC blocks=20480
Log file opened [logno 2]
stutest_lgwr_4092.trc
Dump file c:\oracle\admin\stutest\bdump\stutest_lgwr_4092.trc
Fri Jul 30 17:01:59 2010
ORACLE V10.2.0.4.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 8 - type 8664, 2 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:13601M/16378M, Ph+PgF:10927M/17814M
Instance name: stutest
Redo thread mounted by this instance: 1
Oracle process number: 6
Windows thread id: 4092, image: ORACLE.EXE (LGWR)
*** 2010-07-30 17:01:59.622
*** SERVICE NAME:() 2010-07-30 17:01:59.606
*** SESSION ID:(221.1) 2010-07-30 17:01:59.606
Maximum redo generation record size = 156160 bytes
Maximum redo generation change vector size = 150676 bytes
*** 2010-07-30 22:01:00.446
Warning: log write time 770ms, size 2KB
*** 2010-07-30 22:08:37.586
Warning: log write time 1120ms, size 9KB
*** 2010-07-30 22:08:41.258
Warning: log write time 680ms, size 7KB
*** 2010-07-30 22:09:58.244
Warning: log write time 660ms, size 1KB
*** 2010-07-30 22:11:21.388
Warning: log write time 860ms, size 6KB
*** 2010-07-30 23:42:11.203
Warning: log write time 580ms, size 1KB
*** 2010-07-31 00:04:13.917
Warning: log write time 980ms, size 8KB
*** 2010-07-31 00:06:40.422
Warning: log write time 930ms, size 22KB
*** 2010-07-31 00:08:11.940
Warning: log write time 1800ms, size 23KB
*** 2010-07-31 21:13:33.694
Warning: log write time 1460ms, size 40KB
*** 2010-07-31 21:13:39.522
Warning: log write time 2790ms, size 87KB
*** 2010-07-31 21:13:46.054
Warning: log write time 4940ms, size 69KB
*** 2010-07-31 21:13:50.038
Warning: log write time 3980ms, size 81KB
*** 2010-07-31 21:13:55.616
Warning: log write time 5580ms, size 61KB
*** 2010-07-31 21:14:01.726
Warning: log write time 6110ms, size 77KB
*** 2010-07-31 21:14:08.258
Warning: log write time 3530ms, size 140KB
*** 2010-07-31 21:14:19.508
Warning: log write time 1500ms, size 3KB
*** 2010-07-31 22:07:49.954
Warning: log write time 930ms, size 1KB
*** 2010-07-31 23:16:01.054
Warning: log write time 1080ms, size 103KB
*** 2010-07-31 23:17:52.854
Warning: log write time 1360ms, size 3KB
*** 2010-07-31 23:23:26.631
Warning: log write time 710ms, size 2KB
*** 2010-08-01 00:04:58.476
Warning: log write time 690ms, size 13KB
*** 2010-08-01 00:06:51.980
Warning: log write time 590ms, size 20KB
*** 2010-08-01 00:07:38.153
Warning: log write time 1540ms, size 28KB
*** 2010-08-01 00:08:02.748
Warning: log write time 770ms, size 64KB
*** 2010-08-01 00:11:04.628
Warning: log write time 1140ms, size 43KB
*** 2010-08-01 17:05:49.886
Warning: log write time 780ms, size 3KB
*** 2010-08-01 21:00:46.571
Warning: log write time 910ms, size 365KB
*** 2010-08-01 21:09:22.447
Warning: log write time 2910ms, size 22KB
*** 2010-08-01 21:09:27.932
Warning: log write time 4430ms, size 62KB
*** 2010-08-01 21:09:34.010
Warning: log write time 6060ms, size 74KB
*** 2010-08-01 21:09:40.088
Warning: log write time 3080ms, size 150KB
*** 2010-08-01 21:09:45.495
Warning: log write time 2410ms, size 99KB
*** 2010-08-01 21:09:50.370
Warning: log write time 4870ms, size 40KB
*** 2010-08-01 21:09:55.401
Warning: log write time 5030ms, size 82KB
*** 2010-08-01 21:09:59.151
Warning: log write time 3610ms, size 65KB
*** 2010-08-01 23:05:40.560
Warning: log write time 720ms, size 4KB
*** 2010-08-01 23:06:05.030
Warning: log write time 1670ms, size 21KB
*** 2010-08-01 23:17:55.537
Warning: log write time 1540ms, size 116KB
*** 2010-08-01 23:23:35.891
Warning: log write time 600ms, size 1KB
*** 2010-08-02 00:05:52.363
Warning: log write time 1340ms, size 48KB
*** 2010-08-02 00:06:43.427
Warning: log write time 1060ms, size 24KB
*** 2010-08-02 00:06:50.177
Warning: log write time 1730ms, size 209KB
*** 2010-08-02 00:07:08.256
Warning: log write time 950ms, size 17KB
*** 2010-08-02 00:11:25.436
Warning: log write time 1690ms, size 8KB
*** 2010-08-02 00:12:11.313
Warning: log write time 850ms, size 45KB
*** 2010-08-02 00:13:55.754
Warning: log write time 560ms, size 3KB
*** 2010-08-02 11:27:52.686
Warning: log write time 1440ms, size 46KB
*** 2010-08-02 11:27:58.780
Warning: log write time 3790ms, size 54KB
*** 2010-08-02 11:28:02.546
Warning: log write time 3760ms, size 70KB
*** 2010-08-02 11:28:08.483
Warning: log write time 5940ms, size 74KB
*** 2010-08-02 11:28:13.812
Warning: log write time 2330ms, size 139KB
*** 2010-08-02 11:28:18.796
Warning: log write time 1980ms, size 79KB
*** 2010-08-02 11:28:25.093
Warning: log write time 3360ms, size 88KB
*** 2010-08-02 11:28:29.421
Warning: log write time 4330ms, size 38KB
*** 2010-08-02 16:10:45.927
Warning: log write time 590ms, size 3KB
*** 2010-08-02 22:08:57.806
Warning: log write time 700ms, size 37KB
*** 2010-08-02 23:07:22.262
Warning: log write time 1750ms, size 234KB
*** 2010-08-02 23:13:44.993
Warning: log write time 1410ms, size 17KB
*** 2010-08-03 00:04:08.387
Warning: log write time 670ms, size 6KB
*** 2010-08-03 00:07:44.347
Warning: log write time 1890ms, size 1024KB
*** 2010-08-03 00:08:14.395
Warning: log write time 1680ms, size 1024KB
*** 2010-08-03 00:08:26.817
Warning: log write time 570ms, size 36KB
*** 2010-08-03 00:08:39.427
Warning: log write time 1540ms, size 1024KB
*** 2010-08-03 00:08:50.818
Warning: log write time 1810ms, size 1025KB
*** 2010-08-03 00:08:58.990
Warning: log write time 1640ms, size 942KB
*** 2010-08-03 00:09:21.303
Warning: log write time 1580ms, size 1024KB
*** 2010-08-03 00:09:33.710
Warning: log write time 1790ms, size 1025KB
*** 2010-08-03 00:09:42.382
Warning: log write time 1860ms, size 1024KB
*** 2010-08-03 00:09:50.945
Warning: log write time 1590ms, size 1024KB
*** 2010-08-03 10:28:34.753
Warning: log write time 2330ms, size 47KB
*** 2010-08-03 10:29:44.440
Warning: log write time 810ms, size 1KB
*** 2010-08-03 10:32:27.392
Warning: log write time 890ms, size 1KB
*** 2010-08-03 10:36:02.536
Warning: log write time 2070ms, size 8KB
*** 2010-08-03 10:44:34.174
Warning: log write time 740ms, size 7KB
*** 2010-08-03 12:04:46.687
Warning: log write time 2850ms, size 86KB
*** 2010-08-03 12:04:52.656
Warning: log write time 2970ms, size 85KB
*** 2010-08-03 12:04:54.547
Warning: log write time 1810ms, size 45KB
*** 2010-08-03 14:06:20.827
Warning: log write time 500ms, size 0KB
*** 2010-08-03 14:13:46.404
Warning: log write time 820ms, size 0KB
*** 2010-08-03 15:50:32.996
*** 2010-08-03 15:50:32.996 57052 kcrr.c
Initializing NetServer[LNS1] for dest=STUSTDBY mode ASYNC
Initializing PGA storage for Netserver communication
LNSb is not running anymore.
Check if new Async LNS1 needs to be started..
.. yes it needs to be started
Starting LNS1 ...
Subscribing to KSR Channel [id=1]
success!
Indicating recv buffer for KSR Channel [id=1]
success
Waiting for LNS1 to initialize itself
*** 2010-08-03 15:50:36.012 57343 kcrr.c
Netserver LNS1 [pid 5764] for mode ASYNC has been initialized
Performing a channel reset to ignore previous responses
Connecting as publisher to KSR Channel [id=1]
Successfully started LNS1 [pid 5764] for dest STUSTDBY mode ASYNC ocis=0x00000000144AE5B0
*** 2010-08-03 15:50:36.012 57846 kcrr.c
Making upiahm request to LNS1 [pid 5764]: Begin Time is <08/03/2010 15:50:32>. NET_TIMEOUT = <10> seconds
*** 2010-08-03 16:00:58.266
*** 2010-08-03 16:00:58.266 57052 kcrr.c
Initializing NetServer[LNS1] for dest=STUSTDBY mode ASYNC
LNSb is not running anymore.
Check if new Async LNS1 needs to be started..
Previous Async LNS1 [pid 5764] is running .. no need to start another one
LGWR detected that Async LNS1 [pid 5764] is already running
*** 2010-08-03 16:04:44.289
*** 2010-08-03 16:04:44.289 57052 kcrr.c
Initializing NetServer[LNS1] for dest=STUSTDBY mode ASYNC
LNSb is not running anymore.
Check if new Async LNS1 needs to be started..
Previous Async LNS1 [pid 5764] is running .. no need to start another one
LGWR detected that Async LNS1 [pid 5764] is already running
*** 2010-08-03 16:07:36.747
*** 2010-08-03 16:07:36.747 57052 kcrr.c
Initializing NetServer[LNS1] for dest=STUSTDBY mode ASYNC
LNSb is not running anymore.
Check if new Async LNS1 needs to be started..
Previous Async LNS1 [pid 5764] is running .. no need to start another one
LGWR detected that Async LNS1 [pid 5764] is already running
*** 2010-08-03 16:13:06.633
Warning: log write time 570ms, size 0KB
Did I miss something while creating standby.???
Thanks for the helpare these databases on same server.
BTW These are not errors, they are warning ... I have also seen these kind of warning many times. they can be ignored if ur shipping and recovery on standby is Preperly happening.
Regards
jasbir -
I got the above error while i restore the standby database using RMAN backu
Dear All,
RMAN> crosscheck archivelog all;
using target database controlfile instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=14 devtype=DISK
specification does not match any archive log in the recovery catalogi got the above error while i restore the standby database using RMAN backup from production.
Help need.i take the backup without catalog database.
regards,
DBrman> list backup;
it shows lengthier but i showed only the corresponding
BS Key Type LV Size Device Type Elapsed Time Completion Time
3479 Full 17G DISK 01:29:42 09-FEB-13
BP Key: 3479 Status: AVAILABLE Tag: 09FEB13_FULL_ESMSRV1_DB
Piece Name: /oradatabkp/rman/esmsrv1_full_db_09feb13
SPFILE Included: Modification time: 08-FEB-13
List of Datafiles in backup set 3479
File LV Type Ckp SCN Ckp Time Name
1 Full 1759250260 09-FEB-13 /esmsrv1/dbs/system01.dbf
2 Full 1759250260 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
3 Full 1759250260 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
4 Full 1759250260 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
5 Full 1759250260 09-FEB-13 /esmsrv1/dbs/example01.dbf
6 Full 1759250260 09-FEB-13 /esmsrv1/dbs/indx01.dbf
7 Full 1759250260 09-FEB-13 /esmsrv1/dbs/odm01.dbf
8 Full 1759250260 09-FEB-13 /esmsrv1/dbs/tools01.dbf
9 Full 1759250260 09-FEB-13 /esmsrv1/dbs/users01.dbf
10 Full 1759250260 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
11 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
12 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
13 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
14 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
15 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
16 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
17 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
18 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
19 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
20 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
21 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
22 Full 1759250260 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
23 Full 1759250260 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
39 Full 1759250260 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
3480 Full 17G DISK 01:21:30 09-FEB-13
BP Key: 3480 Status: EXPIRED Tag: TAG20130209T200021
Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_full_Feb09
SPFILE Included: Modification time: 08-FEB-13
List of Datafiles in backup set 3480
File LV Type Ckp SCN Ckp Time Name
1 Full 1759422265 09-FEB-13 /esmsrv1/dbs/system01.dbf
2 Full 1759422265 09-FEB-13 /esmsrv1/dbs/undotbs01.dbf
3 Full 1759422265 09-FEB-13 /esmsrv1/dbs/cwmlite01.dbf
4 Full 1759422265 09-FEB-13 /esmsrv1/dbs/drsys01.dbf
5 Full 1759422265 09-FEB-13 /esmsrv1/dbs/example01.dbf
6 Full 1759422265 09-FEB-13 /esmsrv1/dbs/indx01.dbf
7 Full 1759422265 09-FEB-13 /esmsrv1/dbs/odm01.dbf
8 Full 1759422265 09-FEB-13 /esmsrv1/dbs/tools01.dbf
9 Full 1759422265 09-FEB-13 /esmsrv1/dbs/users01.dbf
10 Full 1759422265 09-FEB-13 /esmsrv1/dbs/xdb01.dbf
11 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_default_seg_001.dbf
12 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_ind_seg_001.dbf
13 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_property_seg_001.dbf
14 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_ind_seg_001.dbf
15 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_upload_seg_001.dbf
16 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_ind_seg_001.dbf
17 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_rate_seg_001.dbf
18 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_ind_seg_001.dbf
19 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_001.dbf
20 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_001.dbf
21 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_overflow_seg_002.dbf
22 Full 1759422265 09-FEB-13 /esmsrv1/dbs/dpipe_summary_seg_002.dbf
23 Full 1759422265 09-FEB-13 /esmsrv1/dbs/perfstat_001.dbf
39 Full 1759422265 09-FEB-13 /esmsrv1/dbs/oem_repository.dbf
BS Key Type LV Size Device Type Elapsed Time Completion Time
3481 Full 4M DISK 00:00:03 09-FEB-13
BP Key: 3481 Status: AVAILABLE Tag: TAG20130209T212205
Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_controlfile_copy_Feb09
Controlfile Included: Ckp SCN: 1759462488 Ckp time: 09-FEB-13
BS Key Type LV Size Device Type Elapsed Time Completion Time
3482 Full 0 DISK 00:00:01 09-FEB-13
BP Key: 3482 Status: AVAILABLE Tag: TAG20130209T212212
Piece Name: /oradatabkp/rman/esmsrv1/esmsrv1_spfile_copy_Feb09
SPFILE Included: Modification time: 08-FEB-13
ls -l /oradatabkp
root@drsrv1#ls -l /oradatabkp
total 1108672
drwxr-xr-x 2 ovsd dba 96 Sep 27 2009 alert_bkp
-rw-r--r-- 1 oracle dba 195 Mar 15 2007 create.sql
drwxr-xr-x 2 oracle dba 8192 Aug 7 2009 ctrl_bkp
-rw-r--r-- 1 root sys 565114880 Apr 24 2007 drsrv1.tar
drwxrwxrwx 2 root sys 96 Jun 17 2011 drsrv2-ignitebkp
drwxr-xr-x 4 root sys 96 Apr 24 2007 esmsrv1
-rw-r----- 1 root sys 1613824 Feb 22 2007 esmsrv1stby.ctl
-rw-r--r-- 1 esmsrv1 dba 5120 Dec 31 2009 esmtables.dmp
-rw-r--r-- 1 esmsrv1 dba 538 Dec 31 2009 esmtables.log
drwxrwxrwx 4 root sys 8192 Mar 10 2009 export
drwxr-xr-x 8 root sys 8192 Apr 24 2007 finalbackup
-rw-r--r-- 1 oracle dba 3820 Sep 5 2008 invalid.sql
-rw-r--r-- 1 esmsrv1 dba 303104 Dec 31 2009 kirdevports.dmp
-rw-r--r-- 1 esmsrv1 dba 591 Dec 31 2009 kirdevports.log
drwxr-xr-x 2 root root 96 Feb 12 2007 lost+found
-rw-r--r-- 1 oracle dba 24954 Aug 9 2009 ovcontrol-090909.ctl
drwxr-xr-x 22 root sys 8192 Apr 24 2007 ovpi
drwxr-xr-x 2 oracle dba 8192 Aug 7 2009 pfile_bkp
drwxrw-rw- 4 oracle dba 8192 Feb 10 15:25 rman
drwxr-xr-x 28 root sys 8192 Feb 1 17:15 schedbkp
drwxr-xr-x 2 oracle dba 8192 Jul 11 2011 sdnnm
-rw-r--r-- 1 esmsrv1 dba 2196 Dec 31 2009 srirdevports.log
drwxr-xr-x 2 oracle dba 96 Mar 13 2009 statsreport
-rw-r--r-- 1 oracle dba 966 Mar 15 2007 tbs.sql
drwxr-xr-x 5 oracle dba 96 Mar 16 2007 testov
drwxr-xr-x 2 root sys 442368 Mar 11 2009 trendadm_files
root@drsrv1#ls -l /oradatabkp/rman
total 37244448
drwxr-xr-x 2 oracle dba 8192 Feb 10 15:25 esmsrv1
-rw-r----- 1 oracle dba 19068198912 Feb 9 14:21 esmsrv1_full_db_09feb13
drwxrw-rw- 2 oracle dba 8192 Feb 9 21:36 openview
-rw-r--r-- 1 oracle dba 920442 Feb 9 21:37 rmanbkp-all.log -
Error in starting MRP process in Standby database.
Hi All,
OS:Windows server 03
DB:11g
I am creating a Standby database, everything is fine until i fire the below command to start the MRP process to start the recovery of the database.
alter database recover managed standby database disconnect from session;MRP0 started with pid=27, OS id=6640
2013-02-07 17:59:48.515000 +05:30
started logmerger process
Managed Standby Recovery not using Real Time Apply
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSAUX01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'D:\APP\ORACLE\ORADATA\TEST\TEST\UNDOTBS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_dbw0_6000.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'D:\APP\ORACLE\ORADATA\TEST\TEST\USERS01.DBF'
ORA-27086: unable to lock file - already in use
OSD-00002: additional error information
O/S-Error: (OS 32) The process cannot access the file because it is being used by another process.
MRP0: Background Media Recovery terminated with error 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_pr00_7984.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Recovery Slave PR00 previously exited with exception 1110
Errors in file d:\app\oracle\diag\rdbms\testdr\testdr\trace\testdr_mrp0_6640.trc:
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\APP\ORACLE\ORADATA\TEST\TEST\SYSTEM01.DBF'
Completed: alter database recover managed standby database disconnect from session
Can anyone tell me why is this comming?
Regards,
SphinxHi ,
Yes, it is on the same server.
I have used the below mentioned parameters to rename the files
At Primary Pfile:
*.db_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\datafiles\')
*.log_file_name_convert=('D:\app\oracle\oradata\test\test\','D:\app\oracle\testdr\oradata\redologs\')
At Standby:
*.db_file_name_convert=('D:\app\oracle\testdr\oradata\datafiles\','D:\app\oracle\oradata\test\test\')
*.log_file_name_convert=('D:\app\oracle\testdr\oradata\redologs\','D:\app\oracle\oradata\test\test\')
But the output of v$datafile at standby is showing the path of Primary datafiles
I manually tried recovering them but it is prompting me the same error.
Regards
Edited by: $phinx19 on Feb 7, 2013 6:23 AM
Maybe you are looking for
-
What is the BEST way to get my macbook with lion on it, to communicate with my Canon 40D camera?
What is the BEST way to get my macbook with lion on it, to communicate with my Canon 40D camera? It says the utility disk is a PowerPC app and that is no longer supported. What do I do now? I can't upload photos from my camera.
-
The audio does not play back from the speakers of my laptop, it plays only through headphones ?
Hi, I am not able to hear playback of audio from the speakers on my laptop. Only if I connect a headphone I am able to hear. Kindly help resolve. Regards, Vivek. V.
-
NW04s WAS 7.0 displays some texts in chinese language
I have installed NW04s ABAP instance (WAS 7.0)with all the default settings. When I logged in to the SAP system, I noticed that all the text messages are being shown in some Chinese language. Later I realized that, not only this screen but also all t
-
Settling Internal Orders to a AUC
Hi, Can somebody please help me. I need the tcodes and steps to create an internal order which will settle to a AUC. Will assign points if useful Thanks
-
Hello, I am newbe in Oracle SQL.I need help in parsing Strings. Example: ID Name Address num 1 Peter 123 park st,223 park st 123,223 Answer ID Name Address num 1 Peter 123 park st 123 1 Peter 223 Park St 223 Please Help me. Thanks.