Standby recovery problem

i have a production and standby db
9i release 2 on oralinux
on my production database
select name from v$datafile;
NAME
/oracle/oradata/eims/system01.dbf
/oracle/oradata/eims/undotbs01.dbf
/oracle/oradata/eims/cwmlite01.dbf
/oracle/oradata/eims/drsys01.dbf
/oracle/oradata/eims/example01.dbf
/oracle/oradata/eims/indx01.dbf
/oracle/oradata/eims/odm01.dbf
/oracle/oradata/eims/tools01.dbf
/oracle/oradata/eims/users01.dbf
/oracle/oradata/eims/xdb01.dbf
/oracle/oradata/eims/INVENTORY01.dbf
NAME
/oracle/oradata/eims/APR_DATA11.dbf
/oracle/oradata/eims/APR_DATA21.dbf
/oracle/oradata/eims/APR_MMS1.dbf
/oracle/oradata/eims/APR_MVIEWS1.dbf
/oracle/oradata/eims/HR_DATA21.dbf
/oracle/oradata/eims/DTS_DATA11.dbf
/oracle/oradata/eims/dts_data12.dbf
/oracle/oradata/eims/undotbs0.dbf2.dbf
/oracle/oradata/eims/APR_DATA22.dbf
/oracle/oradata/eims/INVENTORY11.dbf ( this file not present on standby db)
21 rows selected.
on my standby db:
select name from v$datafile;
NAME
/oracle/oradata/eims/system01.dbf
/oracle/oradata/eims/undotbs01.dbf
/oracle/oradata/eims/cwmlite01.dbf
/oracle/oradata/eims/drsys01.dbf
/oracle/oradata/eims/example01.dbf
/oracle/oradata/eims/indx01.dbf
/oracle/oradata/eims/odm01.dbf
/oracle/oradata/eims/tools01.dbf
/oracle/oradata/eims/users01.dbf
/oracle/oradata/eims/xdb01.dbf
/oracle/oradata/eims/INVENTORY01.dbf
NAME
/oracle/oradata/eims/APR_DATA11.dbf
/oracle/oradata/eims/APR_DATA21.dbf
/oracle/oradata/eims/APR_MMS1.dbf
/oracle/oradata/eims/APR_MVIEWS1.dbf
/oracle/oradata/eims/HR_DATA21.dbf
/oracle/oradata/eims/DTS_DATA11.dbf
/oracle/oradata/eims/dts_data12.dbf
/oracle/oradata/eims/undotbs0.dbf2.dbf
/oracle/oradata/eims/APR_DATA22.dbf ( the recovery error come with this datafile)
20 rows selected.
but when I
SQL> recover standby database;
ORA-00283: recovery session canceled due to errors
ORA-01110: data file 20: '/oracle/oradata/eims/APR_DATA22.dbf'
ORA-01157: cannot identify/lock data file 20 - see DBWR trace file
ORA-01110: data file 20: '/oracle/oradata/eims/APR_DATA22.dbf'
the diffrence in both primary and standby db is
/oracle/oradata/eims/INVENTORY11.dbf (present on primary) but not on standby db. the error message when i recover standby database should with this datafile
however in recovery the error message is (data file 20: '/oracle/oradata/eims/APR_DATA22.dbf') not with
(/oracle/oradata/eims/INVENTORY11.dbf)
how i can over come with this
regards
rehan
Edited by: user10204771 on Feb 6, 2009 12:18 AM

/oracle/oradata/eims/APR_DATA22.dbf this also created in standby and production db at 15-jan-09.
/oracle/oradata/eims/INVENTORY11.dbf this file is created on primary db on 15-jan-09 but not on standby.
     /oracle/oradata/eims/system01.dbf system
/oracle/oradata/eims/undotbs01.dbf RECOVER
     /oracle/oradata/eims/cwmlite01.dbf
     /oracle/oradata/eims/drsys01.dbf
     /oracle/oradata/eims/example01.dbf
     /oracle/oradata/eims/indx01.dbf
     /oracle/oradata/eims/odm01.dbf
     /oracle/oradata/eims/tools01.dbf
     /oracle/oradata/eims/users01.dbf
     /oracle/oradata/eims/xdb01.dbf
     /oracle/oradata/eims/INVENTORY01.dbf
     /oracle/oradata/eims/APR_DATA11.dbf      /oracle/oradata/eims/APR_DATA21.dbf
     /oracle/oradata/eims/APR_MMS1.dbf
     /oracle/oradata/eims/APR_MVIEWS1.dbf
     /oracle/oradata/eims/HR_DATA21.dbf
     /oracle/oradata/eims/DTS_DATA11.dbf
     /oracle/oradata/eims/dts_data12.dbf
     /oracle/oradata/eims/undotbs0.dbf2.dbf
/oracle/oradata/eims/APR_DATA22.dbf RECOVER
the staus of these two files is recover , all other datafile status is onlline.
regards rehan

Similar Messages

Physica standby recovery problem

Hi,
I am trying to recover physical standby database manually
I am getting below error:
alter database recover standby database parallel (degree 32);
alter database recover standby database parallel (degree 32)
ERROR at line 1:
ORA-01153: an incompatible media recovery is active
I have tried to cancel managed recovery, but no managed recovery is active.
alter database recover managed standby database cancel;
alter database recover managed standby database cancel
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active
select distinct recovery_mode from v$archive_dest_status;
RECOVER
IDLE
Please help me to resolve this. Thanks in advance.
regards,
Narendra

Apparently this is bug 5084496, related to parallel recovery on 10.1 and below (ML note 361883.1). You may avoid this bug if you don't use parallel recovery. It looks like there are no one-off patches available, so you are stuck with either serial recovery or upgrade to 10.2 or higher :-(
Regards,
Jeremiah Wilton
ORA-600 Consulting
http://www.ora-600.net

Standby sync problem.

Hi,
DB Version:10g R2
OS:LINUX
We have configured the physical standby database and it was running as expected, but due to some un know reasons one of the archivelog at primary side has been deleted and it is no longer available to be transferred and applied at standby side and hence now standby is not sysnc with primary DB. In this case how i can make the standby in sync with primary DB.
No backup of delete archivelog is avaliable.
I really appreciate the help.

Hi
THIS WORKS TRY THIS
In 10g you can use an incremental backup and recover the standby using the same to compensate for the missing archivelogs as shown below
In the case below archivelogs with sequence numbers 137 and 138 which are required on the standby are deleted to simulate this problem.
Step 1: On the standby database check the current scn.
STDBY>>select current_scn from v$database;
CURRENT_SCN
4793543
Step 2: On the primary database create the needed incremental backup from the above SCN
C:\Documents and Settings\frego>rman target /
Recovery Manager: Release 10.2.0.2.0 - Production on Wed Oct 25 13:39:04 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: USYD (DBID=768471617)
RMAN> BACKUP DEVICE TYPE DISK INCREMENTAL FROM SCN 4793543 DATABASE
FORMAT 'C:\temp\bkup_%U';
Starting backup at 25/OCT/06
using channel ORA_DISK_1
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00001 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\USYD\SYSTEM01.DBF
input datafile fno=00002 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\USYD\UNDOTBS01.DBF
input datafile fno=00003 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\USYD\SYSAUX01.DBF
input datafile fno=00004 name=C:\ORACLE\PRODUCT\10.2.0\ORADATA\USYD\USERS01.DBF
channel ORA_DISK_1: starting piece 1 at 25/OCT/06
channel ORA_DISK_1: finished piece 1 at 25/OCT/06
piece handle=C:\TEMP\BKUP_02I0NSNE_1_1 tag=TAG20061025T134102 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:35
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
including current control file in backupset
including current SPFILE in backupset
channel ORA_DISK_1: starting piece 1 at 25/OCT/06
channel ORA_DISK_1: finished piece 1 at 25/OCT/06
piece handle=C:\TEMP\BKUP_03I0NSOI_1_1 tag=TAG20061025T134102 comment=NONE
channel ORA_DISK_1: backup set complete, elapsed time: 00:00:02
Finished backup at 25/OCT/06
Step 3: Cancel managed recovery at the standby database
STDBY>>recover managed standby database cancel;
Media recovery complete.
Move the backup files to a new folder called INCR_BACKUP so that they are the only files in that folder.
Step 4: Catalog the Incremental Backup Files at the Standby Database
C:\oracle\product\10.2.0\db_1\database>rman target /
Recovery Manager: Release 10.2.0.2.0 - Production on Wed Oct 25 14:54:27 2006
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: USYD (DBID=768471617, not open)
RMAN> CATALOG START WITH 'C:\temp\INCR_BACKUP';
searching for all files that match the pattern C:\temp\INCR_BACKUP
List of Files Unknown to the Database
=====================================
File Name: C:\TEMP\INCR_BACKUP\BKUP_02I0NSNE_1_1
File Name: C:\TEMP\INCR_BACKUP\BKUP_03I0NSOI_1_1
Do you really want to catalog the above files (enter YES or NO)? YES
cataloging files...
cataloging done
List of Cataloged Files
=======================
File Name: C:\TEMP\INCR_BACKUP\BKUP_02I0NSNE_1_1
File Name: C:\TEMP\INCR_BACKUP\BKUP_03I0NSOI_1_1
Step 5: Apply the Incremental Backup to the Standby Database
RMAN> RECOVER DATABASE NOREDO;
Starting recover at 25/OCT/06
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=151 devtype=DISK
channel ORA_DISK_1: starting incremental datafile backupset restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00001: C:\ORACLE\PRODUCT\10.2.0\ORADATA\STDB
Y\SYSTEM01.DBF
destination for restore of datafile 00002: C:\ORACLE\PRODUCT\10.2.0\ORADATA\STDB
Y\UNDOTBS01.DBF
destination for restore of datafile 00003: C:\ORACLE\PRODUCT\10.2.0\ORADATA\STDB
Y\SYSAUX01.DBF
destination for restore of datafile 00004: C:\ORACLE\PRODUCT\10.2.0\ORADATA\STDB
Y\USERS01.DBF
channel ORA_DISK_1: reading from backup piece C:\TEMP\INCR_BACKUP\BKUP_02I0NSNE_
1_1
channel ORA_DISK_1: restored backup piece 1
piece handle=C:\TEMP\INCR_BACKUP\BKUP_02I0NSNE_1_1 tag=TAG20061025T134102
channel ORA_DISK_1: restore complete, elapsed time: 00:00:03
Finished recover at 25/OCT/06
Step 6: Put the standby database back to managed recovery mode.
STDBY>> recover managed standby database nodelay disconnect;
Media recovery complete.
From the alert.log you will notice that the standby database is still looking for the old log files
FAL[client]: Failed to request gap sequence
GAP - thread 1 sequence 137-137
DBID 768471617 branch 600609988
This is because the controlfile has not been updated.
Hence the standby controlfile has to be recreated
On the primary
PRIM>>alter database create standby controlfile as 'C:\temp\standby01.ctl';
System altered.
Copy the standby control file to the standby site and restart the standby database in managed recovery mode...
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 2 processes
Media Recovery Waiting for thread 1 sequence 139
As you can see from the above output the standby is now looking for the next archivelog.
If you have the luxury of time at your disposal you can do an export of the standby database in read only mode.
Cheers
Kanchana.

Troubleshooting System Recovery Problems

A System Recovery is a useful tool to return your Windows 8 tablet back to factory defaults. However, what do you do when the System Recovery isn't working!?
A full System Recovery can be a lengthy process as there is a lot of data being transferred. Patience is the key, as a full Recovery can take two to four hours to complete.
For more information check out HP's Troubleshooting HP System Recovery Problems for Windows 8. This document will help you get your Windows 8 tablet back up and running.
TIP: If you are planning on using the System Recovery make sure that you do not change or delete the HP Recovery Partition as that will make all but impossible to Restore your tablet using the HP Recovery Manager.
Please click “Accept as Solution ” if you feel my post solved your issue.
Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
Thank you,
BHK6
I work on behalf of HP

Have you created this disc on your own or you use original toshiba disc?
Do you use it for the first time?

Managed Standby Recovery not active

Dear All,
My database version is:
SQL> select banner from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Prod
PL/SQL Release 10.2.0.1.0 - Production
CORE 10.2.0.1.0 Production
TNS for Linux: Version 10.2.0.1.0 - Production
NLSRTL Version 10.2.0.1.0 - Production
OS:RedHat 5.5
My current configuration is:
We have two node RAC primary database and a local standby database.
And TWO NODE RAC DR (REMOTE)STANDBY DATABASE
while checking (REMOTE WHICH IS TWO NODE RAC)dr synchronization we found archive since yesterday has not been applied.
But local dr is fully sinc with the primary database.
When i have executed 'ALTER DATABASE RECOVER MANAGED STANDBY DATABASE CANCEL' it says
SQL> alter database recover managed standby database cancel;
alter database recover managed standby database cancel
ERROR at line 1:
ORA-16136: Managed Standby Recovery not active
I manually copied the archive log which where missing in the remote standby database and then register those archive log.
after that when i manually tried to recover the standby database it has given me following error.
sql>recover automatic standby database;
ORA-00283: recovery session canceled due to errors
ORA-01124: cannot recover data file 1 - file is in use or recovery
ORA-01110:data file 1: '/database/ctmis/system01.dbf'
please please help me to resolve the issue.
Thanks and Regards
Monoj Das

according to my understand
Node1,Node2 is having node1-standby node2-standby in RAC environment right?
on which node logs ur trying to apply on which node standby? (node1 ==>node1-standby or node2 ==>node2-standby)
check it...hope it will work or not sure :)
standby side...
rman target /
RMAN>crosscheck archivelog all
then try to recover..will see ..
if not
check with support.oracle.com through SR.

Standby Server Problem

Hi,
I am using oracle 10gR1on windows.I have created a standby machine(Physical standby) and want to open in read only mode first time it is open in read only mode but after manually recovery want to open in read only mode.It is not open in read only mode after recover standby database.
Here is Alertlog
Wed Feb 04 15:19:28 2009
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
KCCDEBUG_LEVEL = 0
Autotune of undo retention is turned on.
Dynamic strands is set to TRUE
Running with 1 shared and 18 private strand(s). Zero-copy redo is FALSE
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
Starting up ORACLE RDBMS Version: 10.1.0.2.0.
System parameters with non-default values:
processes = 150
shared_pool_size = 83886080
large_pool_size = 8388608
java_pool_size = 50331648
control_files = D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\CONTROL01.CTL, D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\CONTROL02.CTL, D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\CONTROL03.CTL
db_block_size = 8192
db_cache_size = 25165824
compatible = 10.1.0.2.0
log_archive_start = TRUE
log_archive_dest_1 = LOCATION=E:\oracle\mtm\archives
log_archive_dest_state_1 = enable
standby_archive_dest = E:\oracle\mtm\archives
log_archive_format = mtm_%d_%t_%s_%r.arc
db_file_multiblock_read_count= 16
db_recovery_file_dest = d:\oracle\product\10.1.0\flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=mtmXDB)
job_queue_processes = 10
background_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\MTM\BDUMP
user_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\MTM\UDUMP
core_dump_dest = D:\ORACLE\PRODUCT\10.1.0\ADMIN\MTM\CDUMP
sort_area_size = 65536
db_name = mtm
open_cursors = 300
pga_aggregate_target = 25165824
Deprecated system parameters with specified values:
log_archive_start
End of deprecated system parameter listing
PMON started with pid=2, OS id=1916
MMAN started with pid=3, OS id=1168
DBW0 started with pid=4, OS id=1152
LGWR started with pid=5, OS id=4044
CKPT started with pid=6, OS id=3464
SMON started with pid=7, OS id=1952
RECO started with pid=8, OS id=3312
CJQ0 started with pid=9, OS id=3300
Wed Feb 04 15:19:28 2009
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Wed Feb 04 15:19:37 2009
alter database mount standby database
Wed Feb 04 15:19:37 2009
Controlfile identified with block size 16384
Wed Feb 04 15:19:41 2009
Setting recovery target incarnation to 2
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=13, OS id=3376
ARC0: Archival started
ARC1 started with pid=14, OS id=688
Wed Feb 04 15:19:41 2009
ARCH: STARTING ARCH PROCESSES COMPLETE
Wed Feb 04 15:19:41 2009
ARC1: Archival started
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC1: Thread not mounted
Wed Feb 04 15:19:41 2009
ARC0: Becoming the heartbeat ARCH
ARC0: Thread not mounted
Wed Feb 04 15:19:41 2009
Successful mount of redo thread 1, with mount id 2667150665
Wed Feb 04 15:19:41 2009
Physical Standby Database mounted.
Completed: alter database mount standby database
Wed Feb 04 15:19:49 2009
alter database open read only
Wed Feb 04 15:19:49 2009
SMON: enabling cache recovery
Wed Feb 04 15:19:50 2009
WARNING: The following temporary tablespaces contain no files.
This condition can occur when a backup controlfile has
been restored. It may be necessary to add files to these
tablespaces. That can be done using the SQL statement:
ALTER TABLESPACE <tablespace_name> ADD TEMPFILE
Alternatively, if these temporary tablespaces are no longer
needed, then they can be dropped.
Empty temporary tablespace: TEMP
Empty temporary tablespace: TEMPA
Database Characterset is WE8MSWIN1252
Wed Feb 04 15:19:50 2009
Published database character set on system events channel
Wed Feb 04 15:19:50 2009
All processes have switched to database character set
replication_dependency_tracking turned off (no async multimaster replication found)
Wed Feb 04 15:19:52 2009
Starting background process MMON
MMON started with pid=15, OS id=3828
Wed Feb 04 15:19:53 2009
Starting background process MMNL
MMNL started with pid=16, OS id=3692
Wed Feb 04 15:19:53 2009
Physical standby database opened for read only access.
Wed Feb 04 15:19:54 2009
Errors in file d:\oracle\product\10.1.0\admin\mtm\udump\mtm_ora_3672.trc:
ORA-00604: error occurred at recursive SQL level 1
ORA-16000: database open for read-only access
ORA-06512: at line 6
Completed: alter database open read only
Wed Feb 04 15:20:48 2009
ALTER DATABASE RECOVER standby database
Wed Feb 04 15:20:48 2009
Stopping background process MMNL
Wed Feb 04 15:20:49 2009
Stopping background process MMON
Wed Feb 04 15:20:50 2009
Stopping Job queue slave processes
Wed Feb 04 15:20:50 2009
Stopping background process CJQ0
Wed Feb 04 15:20:50 2009
Job queue slave processes stopped
Waiting for dispatcher 'D000' to shutdown
All dispatchers and shared servers shutdown
Wed Feb 04 15:20:52 2009
SMON: disabling cache recovery
Wed Feb 04 15:20:53 2009
Media Recovery Start
Managed Standby Recovery not using Real Time Apply
Starting datafile 1 with incarnation depth 0 in thread 1 sequence 33047
Datafile 1: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\SYSTEM01.DBF'
Starting datafile 2 with incarnation depth 0 in thread 1 sequence 33047
Datafile 2: 'F:\ORACLE\ORADATA\MTM\UNDOTBS01.DBF'
Starting datafile 3 with incarnation depth 0 in thread 1 sequence 33047
Datafile 3: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\SYSAUX01.DBF'
Starting datafile 4 with incarnation depth 0 in thread 1 sequence 33047
Datafile 4: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\USERS01.DBF'
Starting datafile 5 with incarnation depth 0 in thread 1 sequence 33047
Datafile 5: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\EXAMPLE01.DBF'
Starting datafile 6 with incarnation depth 0 in thread 1 sequence 33047
Datafile 6: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\GMS'
Starting datafile 7 with incarnation depth 0 in thread 1 sequence 33047
Datafile 7: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\HRMS.ORA'
Starting datafile 8 with incarnation depth 0 in thread 1 sequence 33047
Datafile 8: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\UMS.ORA'
Starting datafile 9 with incarnation depth 0 in thread 1 sequence 33047
Datafile 9: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\USERS02.DBF'
Starting datafile 10 with incarnation depth 0 in thread 1 sequence 33047
Datafile 10: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\MMS.DBF'
Starting datafile 11 with incarnation depth 0 in thread 1 sequence 33047
Datafile 11: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\HISTORY.ORA'
Starting datafile 13 with incarnation depth 0 in thread 1 sequence 33047
Datafile 13: 'D:\ORACLE\PRODUCT\10.1.0\ORADATA\MTM\SMS.ORA'
Media Recovery Log
ORA-279 signalled during: ALTER DATABASE RECOVER standby database ...
Wed Feb 04 15:21:01 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_33047_500044525.ARC
ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Wed Feb 04 15:21:11 2009
ALTER DATABASE RECOVER CONTINUE DEFAULT
Media Recovery Log E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_33048_500044525.ARC
Errors with log E:\ORACLE\MTM\ARCHIVES\MTM_945F37AC_1_33048_500044525.ARC
ORA-308 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
Wed Feb 04 15:21:11 2009
ALTER DATABASE RECOVER CANCEL
Media Recovery Canceled
Completed: ALTER DATABASE RECOVER CANCEL
Wed Feb 04 15:21:50 2009
idle dispatcher 'D000' terminated, pid = (10, 1)
Wed Feb 04 15:21:51 2009
alter database open read only
Wed Feb 04 15:21:52 2009
SMON: enabling cache recovery
Please suggest me waht step i shoud take.
Regards

From yours alert logfile one can be reason for inexisteing of temp file at standby database make sure the temp file exist on physical standby database as same as to primary database.
WARNING: The following temporary tablespaces contain no files.
This condition can occur when a backup controlfile has
been restored. It may be necessary to add files to these
tablespaces. That can be done using the SQL statement:
ALTER TABLESPACE <tablespace_name> ADD TEMPFILEKhurram

ORA-16136: Managed Standby Recovery not active

Hi
I am trying implement the dataguard in the windows platform. And this is my first time. Right now iam trying on physical standby. i have done everything as per the document. But iam getting some error. After giving the
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION;
SQL> ALTER SYSTEM SWITCH LOGFILE;
SQL> recover managed standby database cancel;
// I am getting error
ORA-16136: Managed Standby Recovery not active
When just like that i tried to open the standby database in read only mode, i am getting error
SQL> alter database open read only;
alter database open read only
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: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\DB1\SYSTEM01.DBF'
When i checked the alert log file of Primary Database, it shows:
PING[ARCo]: Heartbeat failed to connect to standby 'db2sby'. Error is 1031.
Wed Sep 01 14:10:27 2010
Thread 1 advanced to log sequence 337 (LGWR switch)
Current log# 2 seq# 337 mem# 0: C:\ORACLE\PRODUCT\10.2.0\ORADATA\DB1\REDO02.LOG
Wed Sep 01 14:10:28 2010
Deleted Oracle managed file C:\ORACLE\PRODUCT\10.2.0\FLASH_RECOVERY_AREA\DB1\ARCHIVELOG\2010_02_25\O1_MF_1_224_5RD10Z5V_.ARC
Wed Sep 01 14:14:53 2010
Error 1031 received logging on to the standby
Wed Sep 01 14:14:53 2010
Errors in file c:\oracle\product\10.2.0\admin\db1\bdump\db1_arco_2156.trc:
ORA-01031: insufficient privileges
PING[ARCo]: Heartbeat failed to connect to standby 'db2sby'. Error is 1031.
Wed Sep 01 14:19:53 2010
Error 1031 received logging on to the standby
Wed Sep 01 14:19:53 2010
Errors in file c:\oracle\product\10.2.0\admin\db1\bdump\db1_arco_2156.trc:
ORA-01031: insufficient privileges
And when i checked alert log file of stand by database:
Wed Sep 01 14:13:19 2010
Errors in file c:\oracle\product\10.2.0\standbyy\admin\db2\bdump\db2sby_dbw0_3060.trc:
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: 'C:\TSUNDO12.DBF'
ORA-27086: unable to lock file - already in use
OSD-00001: additional error information
O/S-Error: (OS 101) The exclusive semaphore is owned by another process
--> The above error of Standby was coming for each datafile such as system, users etc.
Kindly Help me.
Shiyas M

here is the pfile of Primary Database:
db1.__db_cache_size=188743680
db1.__java_pool_size=4194304
db1.__large_pool_size=4194304
db1.__shared_pool_size=83886080
db1.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0/admin/db1/adump'
*.background_dump_dest='C:\oracle\product\10.2.0/admin/db1/bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\oradata\db1\control01.ctl','C:\oracle\product\10.2.0\oradata\db1\control02.ctl','C:\oracle\product\10.2.0\oradata\db1\control03.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0/admin/db1/cdump'
*.db_16k_cache_size=4194304
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='db1'
*.DB_UNIQUE_NAME='db1prim'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(db1,db2sby)'
*.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\ARCHIVELOG VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db1prim'
*.LOG_ARCHIVE_DEST_2='SERVICE=db2sby LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db2sby'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE
*.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
*.LOG_ARCHIVE_MAX_PROCESSES=30
*.FAL_SERVER=db2sby
*.FAL_CLIENT=db1
*.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
*.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
*.STANDBY_FILE_MANAGEMENT=AUTO
*.db_recovery_file_dest='C:\oracle\product\10.2.0/flash_recovery_area'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=db1XDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=95420416
*.processes=150
*.recyclebin='OFF'
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=287309824
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0/admin/db1/udump'
*.utl_file_dir='OCM_CONFIG_HOME/state'
Here is the Pfile of standby database:
db1.__db_cache_size=188743680
db1.__java_pool_size=4194304
db1.__large_pool_size=4194304
db1.__shared_pool_size=83886080
db1.__streams_pool_size=0
*.audit_file_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\adump'
*.background_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\bdump'
*.compatible='10.2.0.1.0'
*.control_files='C:\oracle\product\10.2.0\Standbyy\oradata\db2\control001.ctl','C:\oracle\product\10.2.0\Standbyy\oradata\db2\control002.ctl','C:\oracle\product\10.2.0\Standbyy\oradata\db2\control003.ctl'
*.core_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2'
*.db_16k_cache_size=4194304
*.db_block_size=8192
*.db_domain=''
*.db_file_multiblock_read_count=16
*.db_name='db1'
*.DB_UNIQUE_NAME='db2sby'
*.LOG_ARCHIVE_CONFIG='DG_CONFIG=(db1,db2sby)'
*.LOG_ARCHIVE_DEST_1='LOCATION=C:\oracle\product\10.2.0\ARCHIVELOG VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=db2sby'
*.LOG_ARCHIVE_DEST_2='SERVICE=db1 LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=db1'
*.LOG_ARCHIVE_DEST_STATE_1=ENABLE
*.LOG_ARCHIVE_DEST_STATE_2=ENABLE
*.LOG_ARCHIVE_FORMAT=%t_%s_%r.arc
*.LOG_ARCHIVE_MAX_PROCESSES=30
*.FAL_SERVER=db1
*.FAL_CLIENT=db2sby
*.DB_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
*.LOG_FILE_NAME_CONVERT='C:\oracle\product\10.2.0\Standbyy\oradata\DB2','C:\oracle\product\10.2.0\oradata\db1'
*.STANDBY_FILE_MANAGEMENT=AUTO
*.db_recovery_file_dest='C:\oracle\product\10.2.0\flash_recovery_area\DB2SBY'
*.db_recovery_file_dest_size=2147483648
*.dispatchers='(PROTOCOL=TCP) (SERVICE=db1XDB)'
*.job_queue_processes=10
*.open_cursors=300
*.pga_aggregate_target=95420416
*.processes=150
*.recyclebin='OFF'
*.remote_login_passwordfile='EXCLUSIVE'
*.sga_target=287309824
*.undo_management='AUTO'
*.undo_tablespace='UNDOTBS1'
*.user_dump_dest='C:\oracle\product\10.2.0\Standbyy\admin\db2\udump'
*.utl_file_dir='OCM_CONFIG_HOME/state'

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

Manual Standby Recovery

Hi Friendz,
Oracle Db 9i
I have configured a manual standby database(I am not using Dataguard or "create standby database" command ) I only copy the cold backup to the target recovery server. I have been applying archive logs to it for a week now. I use the "recover automatic database using backup controlfile" command.
My problem is, when I try to "alter database open resetlogs" so I can test if I can open it, It is asking for the next archive log and message "that the system01.dbf needs recovery". How can I open my standby database and force it to stop recovery?
Thanks a lot
Ms Inday

ALTER DATABASE RECOVER automatic database using backup controlfile
Media Recovery Start
Sun Dec 19 18:33:14 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40621.dbf
Sun Dec 19 18:33:14 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40622.dbf
Sun Dec 19 18:33:18 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40623.dbf
Sun Dec 19 18:33:22 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40624.dbf
Sun Dec 19 18:33:25 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40625.dbf
Sun Dec 19 18:33:26 2010
Media Recovery Log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40626.dbf
Errors with log /u02/oracle/oaproddb/9.2.0/dbs/arch/1_40626.dbf
ORA-279 signalled during: ALTER DATABASE RECOVER automatic database using b...
Sun Dec 19 18:33:26 2010
ALTER DATABASE RECOVER    CANCELThis is the alert when I try to open it using resetlogs.
ALTER DATABASE   MOUNT
Sun Dec 19 19:29:56 2010
Successful mount of redo thread 1, with mount id 4188096816
Sun Dec 19 19:29:56 2010
Database mounted in Exclusive Mode.
Completed: ALTER DATABASE   MOUNT
Sun Dec 19 19:29:56 2010
ALTER DATABASE OPEN
ORA-1589 signalled during: ALTER DATABASE OPEN...
Sun Dec 19 19:30:51 2010
alter database open noresetlogs
Sun Dec 19 19:30:51 2010
ORA-1588 signalled during: alter database open noresetlogs...
Sun Dec 19 19:31:18 2010
alter database open resetlogs
Sun Dec 19 19:31:20 2010
ORA-1113 signalled during: alter database open resetlogs...
Sun Dec 19 19:32:00 2010
ALTER DATABASE RECOVER database
Sun Dec 19 19:32:00 2010
Media Recovery Start
Sun Dec 19 19:32:00 2010
Media Recovery failed with error 1610
ORA-283 signalled during: ALTER DATABASE RECOVER database ...
Sun Dec 19 19:32:56 2010
ALTER DATABASE RECOVER database using backup controlfile
Sun Dec 19 19:32:56 2010
Media Recovery Start
ORA-279 signalled during: ALTER DATABASE RECOVER database using backup cont...
Sun Dec 19 19:33:12 2010
ALTER DATABASE RECOVER    CANCEL
Sun Dec 19 19:33:12 2010
Media Recovery Cancelled
Completed: ALTER DATABASE RECOVER    CANCEL
Sun Dec 19 19:33:31 2010
alter database open resetlogs
Sun Dec 19 19:33:31 2010
ORA-1113 signalled during: alter database open resetlogs...
Sun Dec 19 19:34:15 2010Thanks

HP G56 System Recovery Problem after removing disk 4 black screen

hi everyone
this is my first time, im helping my nextdoor neighbours laptop hp g56,
the hard drive has been fried and i have intalled my old playstation 3 40 gb hard drive into it.
after the recovery system finished and told me to remove disk 4 it restarts and now have a black screen, does this mean its still installing because i turned it off and then on and now say no bootbale device.
windows 7
40 gb hard drive (ps3 40gb)

pepe999 wrote:
selinacartwrigh wrote:
my system comes on and then stop before it opens the key board and say disk boot failure insert system disk how could find a disk I cant even get in
The message means that your internal hard has been damaged. This message always comes up when the file system is corrupted. I suggest to remove it, connect the hard drive into a different computer as an external drive (use usb caddy), perform a backup if possible and the format the hard drive and restore the factory settings. I'm afraid that you have to reformat the hard drive, a checkdisk scan won't help..
The error message means that the Boot Sector is corrupt or has been damaged. It does not mean that the hard disk is damaged.
This is a fixable issue. There are a few command line tools that can be used.
You will need to make an appropriate version (32-bit / 64-bit) of the Windows 7 repair disc from a working Windows 7 installation. You will need either a USB or CD to create your rapair CD/USB. Follow the instructions on this video to create the repair installation of your choice..You will will be using the manual boot sector repair that is described in this video to repair your Windows 7 Boot sector. Use the Windows 7 repair disc or repair USB thumb drive that you created earlier to accomplish the repair.
Best regards,
erico
****Please click on Accept As Solution if a suggestion solves your problem. It helps others facing the same problem to find a solution easily****
2015 Microsoft MVP - Windows Experience Consumer

Windows 8.1 recovery problem and install dell backup and recovery software...

i had upgrade my windows to 8.1, the problem is that i cant install Dell backup & recovery, when i installing and updating PE I get FACTORY SETUP ERROR 5
is there any technical help me please...thx
however...its cant recovery or reset my laptop back to factory image...
just like this photo...
recovery cant... refresh also cant...

Same problem here: windows 8.1, dell backup and recovery 1.6.2.4. During the installation, when the box of "updating PE environment" appears, i get "factory error 5"
Is there any solution?
Regards

Recovery Problem

I have a Dell Latitude X200 laptop (with Windows XP Pro) and a Zire 31. My use of the Zire is restricted to its Calendar and Contacts features. On April 29 the Palm data on the Dell was seriously corrupted. The Zire has not been HotSynced for over a month. BUT, by using the “Export” option in the Zire’s Calendar and Contacts sections, I had saved those two datasets to a flash drive on April 27. I want to: 1) Remove all present data from the Dell and the Zire. 2) Copy the saved Calendar and Contacts data from the flash drive into the Dell. 3) Perform a “HotSync” to copy the correct data in the Dell into the Zire. Is there any hope that I can get my April 27 data back into the Dell where it belongs, and then into the Zire?

A couple of things:
Reset system bios to the defaults - F2 at start up to enter the bios f9 to set to defaults and then f10 to save.
then try to start.
Did you have any problems before trying to recover, slow or lagging response, etc. These problems can be caused by virus/maleware and also a failing hard drive.
The recovery may not be completing because of bad sectors on the drive - a failing hard drive.
Your support page is here - http://support.toshiba.com/support/modelHome?freeText=3567388
S70-ABT2N22 Windows 7 Pro & 8.1Pro, C55-A5180 Windows 8.1****Click on White “Kudos” STAR to say thanks!****

HP Pavilion dv6-3023sy: Recovery problems. Help me!

I have a problem with Recovery:
After that: Insert Recovery Media ...
Help me, please ...
And if you can, please in Russian
This question was solved.
View Solution.

This recovery is from partition or your HP Disk?
Probably you recovery is corrupt.
If you don't have the HP Disk you can make the download here :
If this don't work or your computer is very slow before show this message, Probably is a error in Hard Disk:
https://h10025.www1.hp.com/ewfrf/wc/mediaOrder?softwareitem=585237-001&cc=us&dlc=en&lc=en&os=4063&pr...=
Run the diagnostic to see if your HD is damage:
Shutdown your computer and press the Key ESC a lot times.
Showed: STart Up Menu and a lot options.
Click the Key F10
GO to Diagnostic> Primary Hard Disk Self Test > Press Enter and let run the diagnostic.
If any error message appear, let me know.
If this answer help you click in Kudos to tanks.
If you don't have more question click in Accept as Solution to close this case.
Best Regards Cristian Derick.
Senior Support Analyst.

Mac OS recovery problem. Need help

Hello toevery one.
I have defective SATA cable to HD bay now. And also new clean SDD Samsung 840 Pro 240 GB (without data or any OS on it) installed in HD bay
I've ordered a new cable, but I'd like to use the SSD untill then, if it was possible so I decided to change my HDD (that on working properly SATA cable) and SDD (that on defective SATA cable) in places and restore Mac OS via external HDD with Time Machine image on faster SSD. So now my new SSD on the optical drive bay with working properly SATA cable and HDD on HD bay with defective SATA cable.
And I faced a problem...
1. I've made configuration of SSD and erased the contents of the SSD and formated it as "Mac O S Extended (Journaled)" with a single GUID partition.
2. I chose the most fresh Image on my HDD that has been prepared in advance and started to wait.
3. The recovery of the system froze on 0,5% and estimated time started to rapidly increase. I've cancelled it when estimated time of full recovery was about 24 hours. System hanged and I turned it off by pressing POWER button.
4. I repeated all the operations again.
5. The recovery froze on 3,8% and estimated time started to grow up again.
6. I've took a look on log file and saw that some host can't be reached or found.
Do you know what is the problem?
Thank you!

Corrections:
1. SDD Samsung 840 Pro 256 GB
2. Mac OS Lion

Logical Standby Creation Problems "Create STatus Unknown"

We are using Grid Control 10.2.0.3 on Oracle 10.2..0.3 databases, Windows 2003 sp2 machines.
We have a primary and fsfo physical standby working properly. We went to create a logical standby on a separate server and had problems. it turned out that the listener on the server was not discovered on the target. we fixed that problem and finished the creation of the logical standby and it seems to be functioning properly now.
However, the status on the data guard page for the logical standby shows Create Status Unknown and we are unable to proceed on to create an additional standby database for other purposes. We have tried removing the logical standby target and re-discovering it but status still shows Create Status Unknown.
Is there any way to clear this status without having to drop the logical standby and completely recreate it.

The status on the agent shows it uploading successfully.
We resolved the issue by removing the logical standby from the configuration and selecting to retain the log apply. We then re-added the standby selecting to manage an existing standby database and the status went to normal.

Standby recovery problem

Similar Messages

Maybe you are looking for