Retention Guarentee on Standby Database
Hi
i am facing frequent Ora-01555 on my 11.1.0.7 standby database used for reporting.
I increased UNDO_RETENTION=50000
I increased UNOD tablespace size to 40Gb
I checked the usage of UNDO tablespace its 99% free
UNDO_MANAGEMENT is AUTO
Again the ora-01555 comes up.
I wanted to enable retention guarentee on my Standby database :
I did : alter tablespace UNDOTBS retention guarantee; got an error stating database open for read access only
I did : alter tablespace UNDOTBS retention guarantee; on primary and switched log , checked that log applied .
Log applied on Standby , but still when i do :
select retention ,tablespace_name
from dba_tablespaces where tablespace_name like 'UNDOTBS';
NOGUARENTEE is the value .
but GUARENTEE in Primary
Please , how can i do this ?
Thanks
My point was that since your Standby is Read Only, there are no writes to Undo -- you can't set RETENTION GUARANTEE.
So it would seem that, at the point in time when you OPEN READ ONLY, many of the Undo Extents have already been expired -- from the Primary.
OR your ORA-1555s are resulting from some other issues -- eg the Transaction Slot in the Undo Segment Header has already been overwritten --- from the Primary.
At what point in time, relative to the transaction activity, do you OPEN READ ONLY ? Can you open the database at some other (earlier) time ?
Hemant K Chitale
Similar Messages
-
How to delete the foreign archivelogs in a Logical Standby database
How do I remove the foreign archive logs that are being sent to my logical standby database. I have files in the FRA of ASM going back weeks ago. I thought RMAN would delete them.
I am doing hot backups of the databases to FRA for both databases. Using ASM, FRA, in a Data Guard environment.
I am not backing up anything to tape yet.
The ASM FRA foreign_archivelog directory on the logical standby FRA keeps growing and nothing is get deleted when
I run the following command every day.
delete expired backup;
delete noprompt force obsolete;
Primary database RMAN settings (Not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD' CONNECT IDENTIFIER 'WMRTPRD_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD2' CONNECT IDENTIFIER 'WMRTPRD2_CWY';
CONFIGURE DB_UNIQUE_NAME 'WMRTPRD3' CONNECT IDENTIFIER 'WMRTPRD3_DG';
CONFIGURE ARCHIVELOG DELETION POLICY TO APPLIED ON ALL STANDBY;
Logical standby database RMAN setting (not all of them)
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 9 DAYS;
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
How do I cleanup/delete the old ASM foreign_archivelog files?OK, the default is TRUE which is what it is now
from DBA_LOGSTDBY_PARAMETERS
LOG_AUTO_DELETE TRUE SYSTEM YES
I am not talking about deleting the Archive logs files for the Logical database that it is creating, but the Standby archive log files being sent to the Logical Database after they have been applied.
They are in the alert log as follows under RFS LogMiner: Registered logfile
RFS[1]: Selected log 4 for thread 1 sequence 159 dbid -86802306 branch 763744382
Thu Jan 12 15:44:57 2012
*RFS LogMiner: Registered logfile [+FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297] to LogM*
iner session id [1]
Thu Jan 12 15:44:58 2012
LOGMINER: Alternate logfile found. Transition to mining archived logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/
foreign_archivelog/wmrtprd/2012_01_12/thread_1_seq_158.322.772386297
LOGMINER: End mining logfile for session 1 thread 1 sequence 158, +FRA/wmrtprd2/foreign_archivelog/wmrtprd/2012_01_12/threa
d_1_seq_158.322.772386297
LOGMINER: Begin mining logfile for session 1 thread 1 sequence 159, +DG1/wmrtprd2/onlinelog/group_4.284.771760923 -
Manual Standby Database (10.2.0.2.0) on Windows 2003 R2
Hi,
We are setting up a standby database on a remote site for a simple oracle DB. As we already have a standby/master for another Oracle DB (from SAP) we want to stay as close as possible as what already exist.
For the SAP Oracle standby, we are copying manualy all archive to the stand by and apply them with brarchive. All is working fine.
For the new standby, we can not use brarchive as there is no SAP install on the standby but we stay with the "manual" copy of the archive from the master to the standby (using robocpy). It means all archive are on the standby (K:\oracle\oradata\archive).
The creation of the standby DB seems to be OK as i can open it, but i can't manage to apply de redo logs.
I'm quite new to oracle, so it's maybe a very basic issue, but i've already spent 3 days on it...
To start the DB, we lauch a bat script :
sqlplus /nolog @c:\backup\standby.sql
pause
the standby.sql:
connect /@TECDB01 as sysdba
startup nomount;
alter database mount standby database;
exit;
Then i connect to sqlplus and enter:
alter database recover managed standby database;
In another sqlplus session :
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;
wich give me :
PROCESS STATUS THREAD# SEQUENCE# BLOCK# BLOCKS
ARCH CONNECTED 0 0 0 0
ARCH CONNECTED 0 0 0 0
MR(fg) WAIT_FOR_GAP 1 45400 0 0
RFS IDLE 0 0 0 0
The sequence 45400 seems to be ok regarding the time of the backup restored on the standby.
The archive is well on the server, but it won't apply it.
The Alert_TECDB01.log :
Fri Oct 29 11:03:43 2010
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =121
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.2.0.
System parameters with non-default values:
processes = 999
sga_target = 7214202880
control_files = I:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, J:\ORACLE\ORADATA\CNTRL\STANDBY.CTL, K:\ORACLE\ORADATA\CNTRL\STANDBY.CTL
db_block_size = 8192
compatible = 10.2.0.2.0
log_archive_dest_1 = LOCATION=K:\oracle\oradata\archive
log_archive_dest_2 = SERVICE=TECDB01
log_archive_dest_state_1 = enable
log_archive_dest_state_2 = enable
standby_archive_dest = K:\oracle\oradata\archive
archive_lag_target = 1800
db_file_multiblock_read_count= 16
undo_management = AUTO
undo_tablespace = RBS
undo_retention = 10800
recyclebin = OFF
remote_login_passwordfile= EXCLUSIVE
db_domain = WORLD
dispatchers = (ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)
shared_servers = 100
local_listener = (ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))
session_cached_cursors = 300
utl_file_dir = \\srvuniway.vrithoff.srwt.tec-wl.be\hotspots
job_queue_processes = 10
audit_file_dest = I:\ORACLE\ADMIN\TECDB01\ADUMP
background_dump_dest = I:\ORACLE\ADMIN\TECDB01\BDUMP
user_dump_dest = I:\ORACLE\ADMIN\TECDB01\UDUMP
core_dump_dest = I:\ORACLE\ADMIN\TECDB01\CDUMP
db_name = TECDB01
open_cursors = 3000
pga_aggregate_target = 1086324736
PMON started with pid=2, OS id=4012
PSP0 started with pid=3, OS id=3856
MMAN started with pid=4, OS id=3580
DBW0 started with pid=5, OS id=1084
LGWR started with pid=6, OS id=576
CKPT started with pid=7, OS id=3516
SMON started with pid=8, OS id=508
RECO started with pid=9, OS id=3068
CJQ0 started with pid=10, OS id=2448
MMON started with pid=11, OS id=2840
MMNL started with pid=12, OS id=3024
Fri Oct 29 11:03:44 2010
starting up 4 dispatcher(s) for network address '(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))'...
starting up 100 shared server(s) ...
Fri Oct 29 11:03:45 2010
alter database mount standby database
Fri Oct 29 11:03:51 2010
Setting recovery target incarnation to 2
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=118, OS id=3584
Fri Oct 29 11:03:51 2010
ARC0: Archival started
ARC1 started with pid=119, OS id=3688
Fri Oct 29 11:03:51 2010
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Fri Oct 29 11:03:51 2010
ARC0: Becoming the 'no FAL' ARCH
Fri Oct 29 11:03:51 2010
Successful mount of redo thread 1, with mount id 3987142355
Fri Oct 29 11:03:51 2010
ARC0: Becoming the 'no SRL' ARCH
Fri Oct 29 11:03:51 2010
ARC1: Becoming the heartbeat ARCH
Fri Oct 29 11:03:51 2010
Physical Standby Database mounted.
Completed: alter database mount standby database
Fri Oct 29 11:04:06 2010
alter database recover managed standby database
Fri Oct 29 11:04:06 2010
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 7 processes
Media Recovery Waiting for thread 1 sequence 45400
Fetching gap sequence in thread 1, gap sequence 45400-45499
+FAL[client]: Error fetching gap sequence, no FAL server specified+
Fri Oct 29 11:04:37 2010
+FAL[client]: Failed to request gap sequence+
GAP - thread 1 sequence 45400-45499
DBID 3776455083 branch 670241032
+FAL[client]: All defined FAL servers have been attempted.+
Check that the CONTROL_FILE_RECORD_KEEP_TIME initialization
parameter is defined to a value that is sufficiently large
enough to maintain adequate log switch information to resolve
archivelog gaps.
Fri Oct 29 11:04:51 2010
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3452
RFS[1]: Identified database type as 'physical standby'
Fri Oct 29 11:04:51 2010
RFS LogMiner: Client disabled from further notification
The tecdb01_arc1_3688.trc :
Dump file i:\oracle\admin\tecdb01\bdump\tecdb01_arc1_3688.trc
Fri Oct 29 11:03:51 2010
ORACLE V10.2.0.2.0 - 64bit Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
With the Partitioning, OLAP and Data Mining options
Windows NT Version V5.2 Service Pack 2
CPU : 8 - type 8664, 2 Physical Cores
Process Affinity : 0x0000000000000000
Memory (Avail/Total): Ph:7467M/9215M, PhPgF:2454M/10796M+
Instance name: tecdb01
Redo thread mounted by this instance: 1
Oracle process number: 119
Windows thread id: 3688, image: ORACLE.EXE (ARC1)
*** SERVICE NAME:() 2010-10-29 11:03:51.177
*** SESSION ID:(1088.1) 2010-10-29 11:03:51.177
kcrrwkx: nothing to do (start)
*** 2010-10-29 11:04:51.129
Redo shipping client performing standby login
*** 2010-10-29 11:04:51.176 64529 kcrr.c
Logged on to standby successfully
Client logon and security negotiation successful!
kcrrwkx: nothing to do (end)
*** 2010-10-29 11:05:51.285
kcrrwkx: nothing to do (end)
*** 2010-10-29 11:06:51.300
kcrrwkx: nothing to do (end)
The initTECDB01.ora :
# Copyright (c) 1991, 2001, 2002 by Oracle Corporation
# Archive
archive_lag_target=1800
log_archive_dest_1='LOCATION=K:\oracle\oradata\archive'
# Cache and I/O
db_block_size=8192
db_file_multiblock_read_count=16
# Cursors and Library Cache
open_cursors=3000
session_cached_cursors=300
# Database Identification
db_domain=WORLD
db_name=TECDB01
# Diagnostics and Statistics
background_dump_dest=I:\oracle\admin\TECDB01\bdump
core_dump_dest=I:\oracle\admin\TECDB01\cdump
user_dump_dest=I:\oracle\admin\TECDB01\udump
# File Configuration
control_files=("I:\oracle\oradata\cntrl\standby.ctl", "J:\oracle\oradata\cntrl\standby.ctl", "K:\oracle\oradata\cntrl\standby.ctl")
# Job Queues
job_queue_processes=10
# Miscellaneous
compatible=10.2.0.2.0
recyclebin=OFF
# Processes and Sessions
processes=999
# SGA Memory
sga_target=6880M
# Pools
#java_pool_size=150M
# Security and Auditing
audit_file_dest=I:\oracle\admin\TECDB01\adump
remote_login_passwordfile=EXCLUSIVE
# Shared Server
shared_servers=100
dispatchers="(ADDRESS=(PROTOCOL=tcp)(HOST=xxx.xxx.xxx.92))(DISPATCHERS=4)(CONNECTIONS=1000)"
#dispatchers="(PROTOCOL=TCP) (SERVICE=TECDB01XDB)"
# Sort, Hash Joins, Bitmap Indexes
pga_aggregate_target=1036M
# System Managed Undo and Rollback Segments
undo_management=AUTO
undo_retention=10800
undo_tablespace=RBS
local_listener="(ADDRESS=(PROTOCOL=TCP)(HOST=xxx.xxx.xxx.92)(PORT=1521))"
# NIDA - 28.10.2010 - redo apply
log_archive_dest_state_1=enable
log_archive_dest_2 = 'SERVICE=TECDB01'
log_archive_dest_state_2=enable
#standby_file_management=auto
standby_archive_dest=K:\oracle\oradata\archive
And the TNSNAMES.ora :
# tnsnames.ora Network Configuration File: C:\oracle\102\network\admin\tnsnames.ora
# Generated by Oracle configuration tools.
#this is the standby
TECDB01.VRITHOFF.SRWT.TEC-WL.BE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.92)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = TECDB01)
# This file is written by Oracle Services For MSCS
# on Sat Nov 08 10:44:27 2008
#this is the master
PRIMARY.VRITHOFF.SRWT.TEC-WL.BE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = xxx.xxx.xxx.246)(PORT = 1521))
(CONNECT_DATA =
(SID = TECDB01)
EXTPROC_CONNECTION_DATA.VRITHOFF.SRWT.TEC-WL.BE =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = TECDB01))
(CONNECT_DATA =
(SERVICE_NAME = TECDB01)
Hope you have all information to bring me in the right way.
Regards,
NicolasHi,
The recover automatic is working fine, but I still have problems with the recover managed
Here is the Alert log :(the 46626 was there at 11:30)
Mon Nov 15 11:31:13 2010
alter database recover managed standby database using current logfile
Managed Standby Recovery starting Real Time Apply
parallel recovery started with 7 processes
Media Recovery Waiting for thread 1 sequence 46626
Mon Nov 15 16:36:01 2010
alter database recover managed standby database cancel
Mon Nov 15 16:36:05 2010
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
Mon Nov 15 16:36:06 2010
Media Recovery user canceled with status 16037
ORA-16043 signalled during: alter database recover managed standby database using current logfile...
Mon Nov 15 16:36:07 2010
Completed: alter database recover managed standby database cancel
Mon Nov 15 16:36:37 2010
ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
Mon Nov 15 16:36:37 2010
Media Recovery Start
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 7 processes
Mon Nov 15 16:36:39 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46626_0670241032.001
Mon Nov 15 16:36:45 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46627_0670241032.001
Mon Nov 15 16:37:11 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46628_0670241032.001
Mon Nov 15 16:37:30 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46629_0670241032.001
Mon Nov 15 16:37:48 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46630_0670241032.001
Mon Nov 15 16:37:59 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46631_0670241032.001
Mon Nov 15 16:38:15 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46632_0670241032.001
Mon Nov 15 16:38:28 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46633_0670241032.001
Mon Nov 15 16:38:47 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46634_0670241032.001
Mon Nov 15 16:39:34 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46635_0670241032.001
Mon Nov 15 16:40:43 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46636_0670241032.001
Mon Nov 15 16:42:03 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46637_0670241032.001
Mon Nov 15 16:43:18 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46638_0670241032.001
Mon Nov 15 16:44:38 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46639_0670241032.001
Mon Nov 15 16:45:45 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46640_0670241032.001
Mon Nov 15 16:46:37 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46641_0670241032.001
Mon Nov 15 16:47:48 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46642_0670241032.001
Mon Nov 15 16:49:07 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46643_0670241032.001
Mon Nov 15 16:50:04 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46644_0670241032.001
Mon Nov 15 16:51:13 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46645_0670241032.001
Mon Nov 15 16:52:16 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46646_0670241032.001
Mon Nov 15 16:53:07 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46647_0670241032.001
Mon Nov 15 16:54:28 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46648_0670241032.001
Mon Nov 15 16:55:47 2010
Media Recovery Log K:\ORACLE\ORADATA\ARCHIVE\ARC46649_0670241032.001
Mon Nov 15 16:56:35 2010
Incomplete Recovery applied until change 4037420604
Completed: ALTER DATABASE RECOVER automatic standby database until time'2010-11-15:15:50:00'
I don't catch why the system wait for a sequence that is available...
Regards,
Nico -
Ora 00364,ora 00305 ora 00312 errors in standby database
hii friends i got a problem in my standby database yesterday i performed database restoration activity, restoration is done and database is in MRM modemout stage, archive gap sequence is completed and is in synchronize with primary but suddenly after some time i got in alertlog media recovery waiting for thread one and from there its is showing nothing in alert log after stoping mrm and restarting database i got few errors please check them and suggest me some solution
alert log file
RFS[87]: Assigned to RFS process 7912
RFS[87]: Identified database type as 'physical standby'
Tue Jan 4 17:12:14 2011
RFS[87]: Archived Log: '/backup/standby_archivelogs/1_87532_622555682.dbf'
Tue Jan 4 17:12:17 2011
Media Recovery Log /backup/standby_archivelogs/1_87532_622555682.dbf
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:55:35 2011
alter database recover managed standby database cancel
Tue Jan 4 17:55:38 2011
MRP0: Background Media Recovery cancelled with status 16037
Tue Jan 4 17:55:38 2011
Errors in file /oracle/app/oracle/admin/****/bdump/*******mrp03017.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Jan 4 17:55:39 2011
Waiting for MRP0 pid 3017 to terminate
Tue Jan 4 17:55:39 2011
Errors in file /oracle/app/oracle/admin/****/bdump/****mrp03017.trc:
ORA-16037: user requested cancel of managed recovery operation
Tue Jan 4 17:55:39 2011
MRP0: Background Media Recovery process shutdown (****)
Tue Jan 4 17:55:40 2011
Managed Standby Recovery Canceled (****)
Completed: alter database recover managed standby database cancel
Tue Jan 4 17:55:56 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:55:56 2011
Attempt to start background Managed Standby Recovery process (****)
MRP0 started with pid=16, OS id=9300
Tue Jan 4 17:55:56 2011
MRP0: Background Managed Standby Recovery process started (****)
Managed Standby Recovery not using Real Time Apply
Tue Jan 4 17:56:01 2011
Errors in file /oracle/app/oracle/admin/****/bdump/****mrp09300.trc:
ORA-00367: checksum error in log file header
ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 /dev/vg04/rREDOR21
Clearing online log 2 of thread 1 sequence number 87533
Tue Jan 4 17:56:01 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 complete
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:56:02 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:57:56 2011
alter database recover managed standby database cancel
Tue Jan 4 17:57:56 2011
MRP0: Background Media Recovery cancelled with status 16037
Tue Jan 4 17:57:56 2011
Errors in file /oracle/app/oracle/admin/APMBDRDB/bdump/apmbdrdb_mrp0_9300.trc:
ORA-16037: user requested cancel of managed recovery operation
Recovery interrupted!
Tue Jan 4 17:57:57 2011
Waiting for MRP0 pid 9300 to terminate
Tue Jan 4 17:57:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09300.trc:
ORA-16037: user requested cancel of managed recovery operation
Tue Jan 4 17:57:57 2011
MRP0: Background Media Recovery process shutdown (*****)
Tue Jan 4 17:57:58 2011
Managed Standby Recovery Canceled (*****)
Completed: alter database recover managed standby database cancel
Tue Jan 4 17:58:10 2011
Shutting down instance: further logons disabled
Tue Jan 4 17:58:10 2011
Stopping background process CJQ0
Tue Jan 4 17:58:10 2011
Stopping background process MMNL
Tue Jan 4 17:58:11 2011
Stopping background process MMON
Tue Jan 4 17:58:12 2011
Shutting down instance (immediate)
License high water mark = 3
Tue Jan 4 17:58:12 2011
Stopping Job queue slave processes
Tue Jan 4 17:58:12 2011
Job queue slave processes stopped
Tue Jan 4 17:58:12 2011
ALTER DATABASE CLOSE NORMAL
ORA-1109 signalled during: ALTER DATABASE CLOSE NORMAL...
Tue Jan 4 17:58:12 2011
ALTER DATABASE DISMOUNT
Completed: ALTER DATABASE DISMOUNT
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Tue Jan 4 17:58:17 2011
ARCH shutting down
ARC1: Archival stopped
Tue Jan 4 17:58:22 2011
ARCH shutting down
ARC0: Archival stopped
Tue Jan 4 17:58:24 2011
ARCH: Archival disabled due to shutdown: 1089
Shutting down archive processes
Archiving is disabled
Archive process shutdown avoided: 0 active
Tue Jan 4 17:58:33 2011
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 3
Autotune of undo retention is turned on.
IMODE=BR
ILAT =242
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 2000
sga_max_size = 3221225472
__shared_pool_size = 1006632960
shared_pool_size = 637534208
__large_pool_size = 503316480
large_pool_size = 503316480
__java_pool_size = 16777216
__streams_pool_size = 0
sga_target = 3221225472
control_files = /dev/vg01/rCTRLR1, /dev/vg01/rCTRLR2, /dev/vg01/rCTRLR3
db_block_size = 8192
__db_cache_size = 1677721600
db_cache_size = 637534208
compatible = 10.2.0.1.0
log_archive_config = DG_CONFIG=(APMBPROD,APMBDRDB)
log_archive_dest_1 = LOCATION=/archive/archivelogs/ valid_for=(ONLINE_LOGFILES,ALL_ROLES)
DB_UNIQUE_NAME=APMBDRDB
log_archive_dest_2 =
log_archive_dest_4 = service=APMBPROD LGWR ASYNC VALID_FOR=(ONLINE_LOGFILES,PRIMARY_ROLE) DB_UNIQUE_NAME=APMBPROD
log_archive_max_processes= 2
standby_archive_dest = /backup/standby_archivelogs
fal_client = APMBDRDB
fal_server = APMBPROD
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
job_queue_processes = 10
background_dump_dest = /oracle/app/oracle/admin/APMBDRDB/bdump
user_dump_dest = /oracle/app/oracle/admin/APMBDRDB/udump
core_dump_dest = /oracle/app/oracle/admin/APMBDRDB/cdump
audit_file_dest = /oracle/app/oracle/admin/APMBDRDB/adump
db_name = APMBPROD
db_unique_name = APMBDRDB
open_cursors = 300
pga_aggregate_target = 1703936000
PMON started with pid=2, OS id=9371
PSP0 started with pid=3, OS id=9373
MMAN started with pid=4, OS id=9375
DBW0 started with pid=5, OS id=9377
LGWR started with pid=6, OS id=9380
CKPT started with pid=7, OS id=9382
SMON started with pid=8, OS id=9384
RECO started with pid=9, OS id=9386
CJQ0 started with pid=10, OS id=9388
MMON started with pid=11, OS id=9390
MMNL started with pid=12, OS id=9392
Tue Jan 4 17:58:35 2011
ALTER DATABASE MOUNT
Tue Jan 4 17:58:39 2011
Setting recovery target incarnation to 2
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=14, OS id=9395
Tue Jan 4 17:58:39 2011
ARC0: Archival started
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Tue Jan 4 17:58:39 2011
ARC0: Becoming the 'no FAL' ARCH
ARC0: Becoming the 'no SRL' ARCH
ARC0: Thread not mounted
ARC1 started with pid=15, OS id=9397
ARC1: Becoming the heartbeat ARCH
ARC1: Thread not mounted
Tue Jan 4 17:58:39 2011
Successful mount of redo thread 1, with mount id 3471861451
Tue Jan 4 17:58:39 2011
Physical Standby Database mounted.
Completed: ALTER DATABASE MOUNT
Tue Jan 4 17:58:51 2011
ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 17:58:51 2011
Attempt to start background Managed Standby Recovery process ()
MRP0 started with pid=16, OS id=9400
Tue Jan 4 17:58:51 2011
MRP0: Background Managed Standby Recovery process started
Managed Standby Recovery not using Real Time Apply
Tue Jan 4 17:58:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
ORA-00367: checksum error in log file header
ORA-00305: log 2 of thread 1 inconsistent; belongs to another database
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 /dev/vg04/rREDOR21
Clearing online log 2 of thread 1 sequence number 87533
Tue Jan 4 17:58:57 2011
Errors in file /oracle/app/oracle/admin/*****/bdump/*****mrp09400.trc:
ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/dev/vg04/rREDOR21'
Clearing online redo logfile 2 complete
Media Recovery Waiting for thread 1 sequence 87533
Tue Jan 4 17:58:57 2011
Completed: ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT FROM SESSION
Tue Jan 4 19:37:24 2011
alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
Tue Jan 4 19:37:24 2011
There are 1 logfiles specified.
ALTER DATABASE REGISTER [PHYSICAL] LOGFILE
Completed: alter database register logfile '/backup/standby_archivelogs/1_87533_622555682.dbf'
Tue Jan 4 19:37:27 2011
Media Recovery Log /backup/standby_archivelogs/1_87533_622555682.dbf
Tue Jan 4 19:37:43 2011
Media Recovery Waiting for thread 1 sequence 87534
from here it is showing no errors or nothing in my alert log file from yesterday eveningNo version number, no definition of what you mean by "standby database" and not a clue as to what you mean by "restore" or why you did it.
No help is possible at this time.
PS: We do not guess at what someone means by "MRM modemout stage" ... you need to define your terms. -
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 -
ORA-01403: no data found on LOGICAL STANDBY database
Hi ,
Logical Standby issue :
Oracle 10.2.0.2 enterprise edition .
M Working on LOGICAL Standby since 1 yrs but still i havent got this ......................................
I m getting countinuously no data foud errror on logical standby database .
I found the table causing the proble(db_logstdby_events) and skipped that table and instanciated table using bwlow package:
exec dbms_logstdby.instantiate_table (.......................................
but when i start apply process on logical standby it again give no data found for new table :
Even i tried to instantiate the table using EXPORT/IMPORT during down time but the same facing same problem .
As much as i known abt the error that is :
table1
id
10
20
30
Now if sql apply process on logical standby tries to performe the update transaction(for example) as belows
update table1 set id=100 where id=50;
above query will not be completed cos it will never find the values 50 which is not in table .Thts why this error comming ..
Now my worry is ... no users dare to change/make such changes on Logical standby .So if there is no changes in tables then sqll apply should get all the values to be needded for an update ......
watingggg guyssss/......Troubleshooting ORA-1403 errors with Flashback Transaction
In the event that the SQL Apply engine errors out with an ORA-1403, it may be possible to utilize flashback transaction on the standby database to reconstruct the missing data. This is reliant upon the undo_retention parameter specified on the standby database instance.
ORA-1403: No Data Found
Under normal circumstances the ORA-1403 error should not be seen in a Logical Standby environment. The error occurs when data in a SQL Apply managed table is modified directly on the standby database, and then the same data is modified on the primary database.
When the modified data is updated on the primary database and received by the SQL Apply engine, the SQL Apply engine verifies the original version of the data is present on the standby database before updating the record. When this verification fails, an ORA-1403: No Data Found error is thrown by Oracle Data Guard: SQL Apply.
The initial error
When the SQL Apply engine verification fails, the error thrown by the SQL Apply engine is reported in the alert log of the logical standby database as well as a record being inserted into the DBA_LOGSTDBY_EVENTS view. The information in the alert log is truncated, while the error is reported in it's entirety in the database view.
LOGSTDBY stmt: update "SCOTT"."MASTER"
set
"NAME" = 'john'
where
"PK" = 1 and
"NAME" = 'andrew' and
ROWID = 'AAAAAAAAEAAAAAPAAA'
LOGSTDBY status: ORA-01403: no data found
LOGSTDBY PID 1006, oracle@staco03 (P004)
LOGSTDBY XID 0x0006.00e.00000417, Thread 1, RBA 0x02dd.00002221.10
The Investigation
The first step is to analyze the historical data of the table that threw the error. This can be achieved using the VERSIONS clause of the SELECT statement.
SQL> select versions_xid
, versions_startscn
, versions_endscn
, versions_operation
, pk
, name
from scott.master
versions between scn minvalue and maxvalue
where pk = 1
order by nvl(versions_startscn,0);
VERSIONS_XID VERSIONS_STARTSCN VERSIONS_ENDSCN V PK NAME
03001900EE070000 3492279 3492290 I 1 andrew
02000D00E4070000 3492290 D 1 andrew
Depending upon the amount of undo retention that the database is configured to retain (undo_retention) and the activity on the table, the information returned might be extensive and the versions between syntax might need to be changed to restrict the amount of information returned.
From the information returned, it can be seen that the record was first inserted at scn 3492279 and then was deleted at scn 3492290 as part of transaction ID 02000D00E4070000. Using the transaction ID, the database should be queried to find the scope of the transaction. This is achieved by querying the flashback_transaction_query view.
SQL> select operation
, undo_sql
from flashback_transaction_query
where xid = hextoraw('02000D00E4070000');
OPERATION UNDO_SQL
DELETE insert into "SCOTT"."MASTER"("PK","NAME") values
('1','andrew');
BEGIN
Note that there is always one row returned representing the start of the transaction. In this transaction, only one row was deleted in the master table. The undo_sql column when executed will restore the original data into the table.
SQL> insert into "SCOTT"."MASTER"("PK","NAME") values ('1','andrew');
SQL> commit;
The SQL Apply engine may now be restarted and the transaction will be applied to the standby database.
SQL> alter database start logical standby apply; -
How to restore a database from backup taken in standby database
Its our environment standard to run backup in standby database.
Now we have to perform refresh production database to UAT database.
I have performed normal refresh/duplicate. Is there any additional procedures need to be followed to perform refresh from standby database backupRMAN Restoration to New Server with Different Directory and New Database Name
In this case, I have an existing production database with RMAN Level 0 backup:
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO 'C:\flash_recovery_area\galaxy\backupsets\autobackup\SAMSUNG-ctl_%F';
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 7 DAYS;
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT 'C:\flash_recovery_area\galaxy\backupsets\level0\level0-%d-%T-%U' MAXPIECESIZE 4G;
DELETE NOPROMPT ARCHIVELOG ALL COMPLETED BEFORE 'SYSDATE - 7';
SHOW ALL;
REPORT SCHEMA;
LIST BACKUP OF DATABASE;
REPORT NEED BACKUP;
REPORT UNRECOVERABLE;
LIST EXPIRED BACKUP BY FILE;
LIST ARCHIVELOG ALL;
REPORT OBSOLETE;
CROSSCHECK BACKUP DEVICE TYPE DISK;
CROSSCHECK COPY OF ARCHIVELOG ALL;
DELETE NOPROMPT EXPIRED BACKUP DEVICE TYPE DISK;
DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
RUN {
sql 'alter system archive log current';
BACKUP INCREMENTAL LEVEL 0 DATABASE PLUS ARCHIVELOG DELETE INPUT;
LIST BACKUP OF DATABASE;
REPORT NEED BACKUP;
REPORT UNRECOVERABLE;
LIST EXPIRED BACKUP BY FILE;
LIST ARCHIVELOG ALL;
REPORT OBSOLETE;
CROSSCHECK BACKUP DEVICE TYPE DISK;
CROSSCHECK COPY OF ARCHIVELOG ALL;
DELETE NOPROMPT EXPIRED BACKUP DEVICE TYPE DISK;
DELETE NOPROMPT OBSOLETE DEVICE TYPE DISK;
The backupsets will be restored into a new server with different file structure. The database will also be different. In the new server, I have created a blank database (SID or CUSTOM database with the name DBGRID). This is easier so I won't have to create any directories, user ORADIM or create new PWFile.
This document assumes that a blank (starter) database has been created in the new server. The RDBMS version is the same as the source database.
In this example, the source database name is GALAXY and the target database name is DBGRID.
Let me know if you have any feedback or comments. All I want is to share these steps with you and make it better so we can help other DBA's as well.
Steps start here
-->
ORIGINAL DATABASE: GALAXY
DUPLICATE DATABASE: DBGRID
FROM THE SOURCE DATABASE (GALAXY)
1. Backup the database using RMAN incremental backups.
2. Check the RMAN logs generated and look for the result of the command:
C:\Users\Administrator>set ORACLE_SID=GALAXY
C:\Users\Administrator>rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Aug 1 06:55:08 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: GALAXY (DBID=3578870300)
RMAN> report schema;
using target database control file instead of recovery catalog
Report of database schema for database with db_unique_name GALAXY
List of Permanent Datafiles
===========================
File Size(MB) Tablespace RB segs Datafile Name
1 680 SYSTEM *** C:\ORACLE\ORADATA\GALAXY\SYSTEM01.DBF
2 510 SYSAUX *** C:\ORACLE\ORADATA\GALAXY\SYSAUX01.DBF
3 140 UNDOTBS1 *** C:\ORACLE\ORADATA\GALAXY\UNDOTBS01.DBF
4 5 USERS *** C:\ORACLE\ORADATA\GALAXY\USERS01.DBF
5 106 EXAMPLE *** C:\ORACLE\ORADATA\GALAXY\EXAMPLE01.DBF
6 2048 ALLINDEX *** C:\ORACLE\ORADATA\GALAXY\ALLINDEX01.DBF
List of Temporary Files
=======================
File Size(MB) Tablespace Maxsize(MB) Tempfile Name
1 29 TEMP 32767 C:\ORACLE\ORADATA\GALAXY\TEMP01.DBF
This command shows all the physical database files that will be backed-up by the current RMAN job.
List the online redolog files:
SQL> select * from v$logfile;
GROUP# STATUS TYPE MEMBER IS_
3 ONLINE C:\ORACLE\ORADATA\GALAXY\REDO03A.LOG NO
3 ONLINE C:\ORACLE\ORADATA\GALAXY\REDO03B.LOG NO
2 ONLINE C:\ORACLE\ORADATA\GALAXY\REDO02A.LOG NO
2 ONLINE C:\ORACLE\ORADATA\GALAXY\REDO02B.LOG NO
1 ONLINE C:\ORACLE\ORADATA\GALAXY\REDO01A.LOG NO
1 ONLINE C:\ORACLE\ORADATA\GALAXY\REDO01B.LOG NO
6 rows selected.
3. Since the target server has different structure, it is easier to use a pfile to startup the database rather than restoring the spfile from backup.
C:\Users\Administrator>set ORACLE_SID=GALAXY
C:\Users\Administrator>sqlplus / as sysdba
SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 1 06:56:14 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> create pfile='C:\TEMP\initGALAXYrman.ora' from spfile;
File created.
4. Edit the pfile to have the following parameters:
(These parameters has been edited to fit the target database requirements)
galaxy entries has been changed to dbgrid. Directories has been corrected as well.
dbgrid.__db_cache_size=192937984
dbgrid.__java_pool_size=4194304
dbgrid.__large_pool_size=4194304
dbgrid.__oracle_base='D:\app\Administrator'#ORACLE_BASE set from environment
dbgrid.__pga_aggregate_target=281018368
dbgrid.__sga_target=524288000
dbgrid.__shared_io_pool_size=0
dbgrid.__shared_pool_size=301989888
dbgrid.__streams_pool_size=4194304
*.audit_file_dest='D:\app\Administrator\admin\DBGRID\adump'
*.audit_trail='db'
*.compatible='11.2.0.0.0'
*.control_files='D:\oradata\DBGRID\control01.ctl','D:\oradata\DBGRID\control02.ctl'
*.db_block_size=8192
*.db_domain=''
Leave as it is for now --> *.db_name='GALAXY'
*.db_recovery_file_dest='D:\fra\backupsets\duplicate'
*.DB_RECOVERY_FILE_DEST_SIZE=4G
*.diagnostic_dest='D:\app\Administrator'
*.dispatchers='(PROTOCOL=TCP) (SERVICE=DBGRIDXDB)'
*.job_queue_processes=1000
*.log_archive_dest_1='location=D:\fra\backupsets\archs'
*.log_buffer=10485760
*.memory_target=805306368
*.open_cursors=300
*.processes=800
*.remote_login_passwordfile='EXCLUSIVE'
*.session_cached_cursors=300
*.sessions=885
*.undo_tablespace='UNDOTBS1'
Make sure that all the directory values in this edited pfile are existing in the target server.
5. Copy all the RMAN backup pieces generated in the source database. Transfer the edited pfile as well. Make sure that all directories presented in the pfile exists in the target server.
In this example, RMAN backupsets are located at:
Backupsets:
Level0 and Level1 = D:\fra\backupsets\duplicate\level0 , D:\fra\backupsets\duplicate\level1
Controlfile and Spfile Autobackup = D:\fra\backupsets\duplicate\autobackup
Edited pfile initGALAXYrman= C:\TEMP\initDBGRIDnew.ora
FROM THE TARGET DATABASE (DBGRID)
6. Connect to RMAN and perform database duplication using RMAN backup restoration
C:\Users\Administrator>rman target /
Recovery Manager: Release 11.2.0.1.0 - Production on Wed Aug 1 07:26:45 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database (not started)
RMAN> set dbid = 3578870300; --> THIS IS THE DBID OF THE SOURCE DATABASE!
executing command: SET DBID
RMAN> startup nomount pfile='C:\TEMP\initDBGRIDnew.ora'; -->restore the edited pfile
Oracle instance started
Total System Global Area 535662592 bytes
Fixed Size 1375792 bytes
Variable Size 327156176 bytes
Database Buffers 192937984 bytes
Redo Buffers 14192640 bytes
RMAN> restore controlfile from 'D:\fra\backupsets\duplicate\autobackup\SAMSUNG-CTL_C-3578870300-20120801-00'; -->restore the correct controlfile
Starting restore at 01-AUG-12
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
channel ORA_DISK_1: restoring control file
channel ORA_DISK_1: restore complete, elapsed time: 00:00:07
output file name=D:\ORADATA\DBGRID\CONTROL01.CTL
output file name=D:\ORADATA\DBGRID\CONTROL02.CTL
Finished restore at 01-AUG-12
RMAN> alter database mount; -->mount the database
database mounted
released channel: ORA_DISK_1
RMAN> catalog start with "D:\fra\backupsets\duplicate";
--> catalog the location of the backup pieces to make it known to the control file
Starting implicit crosscheck backup at 01-AUG-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
Crosschecked 3 objects
Finished implicit crosscheck backup at 01-AUG-12
Starting implicit crosscheck copy at 01-AUG-12
using channel ORA_DISK_1
Finished implicit crosscheck copy at 01-AUG-12
searching for all files in the recovery area
cataloging files...
no files cataloged
searching for all files that match the pattern D:\fra\backupsets\duplicate
List of Files Unknown to the Database
=====================================
File Name: D:\FRA\BACKUPSETS\duplicate\autobackup\SAMSUNG-CTL_C-3578870300-20120801-00
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-01NHGTGV_1_1
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-03NHGTMT_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: D:\FRA\BACKUPSETS\duplicate\autobackup\SAMSUNG-CTL_C-3578870300-20120801-00
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-01NHGTGV_1_1
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1
File Name: D:\FRA\BACKUPSETS\duplicate\level0\LEVEL0-GALAXY-20120801-03NHGTMT_1_1
RMAN> list backup summary; -->check your backup they are now known
List of Backups
===============
Key TY LV S Device Type Completion Time #Pieces #Copies Compressed Tag
1 B A A DISK 01-AUG-12 1 2 NO TAG20120801T011054
2 B 0 A DISK 01-AUG-12 1 2 NO TAG20120801T011137
3 B A A DISK 01-AUG-12 1 2 NO TAG20120801T011405
RMAN> list archivelog all; -->list you archivelog for point in time recovery
List of Archived Log Copies for database with db_unique_name GALAXY
=====================================================================
Key Thrd Seq S Low Time
26 1 29 A 01-AUG-12
Name: D:\FRA\BACKUPSETS\ARCHS\ARC0000000029_0785167457.0001
Perform database restoration and recovery. The sequence number is Seq+1 for complete recovery, so that will be 29 + 1 = 30. You can also do recovery via SCN or time based recovery.
Remember in the previous step: RMAN> REPORT SCHEMA;
Each datafile has a corresponding datafile number.
Follow the format to convert them into their respective new restoration directory in the target server.
SET NEWNAME has the format:
SET NEWNAME FOR DATAFILE [FILE NUMBER IN THE REPORT SCHEMA COMMAND] TO
‘[NEW LOCATION AND FILENAME OF THE DATAFILES]’;
RMAN> run {
2> SET UNTIL SEQUENCE 30 THREAD 1;
3> set newname for datafile 1 to 'D:\oradbgrid\oradata\SYSTEM01.DBF';
4> set newname for datafile 2 to 'D:\oradbgrid\oradata\SYSAUX01.DBF';
5> set newname for datafile 3 to 'D:\oradbgrid\oradata\UNDOTBS01.DBF';
6> set newname for datafile 4 to 'D:\oradbgrid\oradata\USERS01.DBF';
7> set newname for datafile 5 to 'D:\oradbgrid\oradata\EXAMPLE01.DBF';
8> set newname for datafile 6 to 'D:\oradbgrid\oradata\ALLINDEX01.DBF';
9> restore database;
10> switch datafile all;
11> recover database;
12> }
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 01-AUG-12
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=19 device type=DISK
channel ORA_DISK_1: starting datafile backup set restore
channel ORA_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_DISK_1: restoring datafile 00001 to D:\oradbgrid\oradata\SYSTEM01.DBF
channel ORA_DISK_1: restoring datafile 00002 to D:\oradbgrid\oradata\SYSAUX01.DBF
channel ORA_DISK_1: restoring datafile 00003 to D:\oradbgrid\oradata\UNDOTBS01.DBF
channel ORA_DISK_1: restoring datafile 00004 to D:\oradbgrid\oradata\USERS01.DBF
channel ORA_DISK_1: restoring datafile 00005 to D:\oradbgrid\oradata\EXAMPLE01.DBF
channel ORA_DISK_1: restoring datafile 00006 to D:\oradbgrid\oradata\ALLINDEX01.DBF
channel ORA_DISK_1: reading from backup piece D:\FRA\BACKUPSETS\DUPLICATE\LEVEL0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1
channel ORA_DISK_1: piece handle=D:\FRA\BACKUPSETS\DUPLICATE\LEVEL0\LEVEL0-GALAXY-20120801-02NHGTIA_1_1 tag=TAG20120801T011137
channel ORA_DISK_1: restored backup piece 1
channel ORA_DISK_1: restore complete, elapsed time: 00:02:06
Finished restore at 01-AUG-12
Starting recover at 01-AUG-12
using channel ORA_DISK_1
starting media recovery
archived log for thread 1 with sequence 29 is already on disk as file D:\FRA\BACKUPSETS\ARCHS\ARC0000000029_0785167457.0001
archived log file name=D:\FRA\BACKUPSETS\ARCHS\ARC0000000029_0785167457.0001 thread=1 sequence=29
media recovery complete, elapsed time: 00:00:01
Finished recover at 01-AUG-12
Log in to SQL*Plus to recreate the redolog files.
Format:
ALTER DATABASE RENAME FILE ‘[OLD REDOLOG LOCATION]’ TO ‘[NEW REDOLOG LOCATION]’;
C:\Users\Administrator>sqlplus "/ as sysdba"
SQL*Plus: Release 11.2.0.1.0 Production on Wed Aug 1 08:54:27 2012
Copyright (c) 1982, 2010, Oracle. All rights reserved.
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> select instance_name, status from v$instance;
INSTANCE_NAME STATUS
dbgrid MOUNTED
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO03A.LOG' TO 'C:\oracle\oradata\dbgrid\REDO03A.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO03B.LOG' TO 'C:\oracle\oradata\dbgrid\REDO03B.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO02A.LOG' TO 'C:\oracle\oradata\dbgrid\REDO02A.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO02B.LOG' TO 'C:\oracle\oradata\dbgrid\REDO02B.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO01A.LOG' TO 'C:\oracle\oradata\dbgrid\REDO01A.LOG';
Database altered.
SQL> ALTER DATABASE RENAME FILE 'C:\ORACLE\ORADATA\GALAXY\REDO01B.LOG' TO 'C:\oracle\oradata\dbgrid\REDO01B.LOG';
Database altered.
Open the database in resetlogs option. Create spfile from the edited pfile then bounce the database.
RMAN> alter database open resetlogs;
database opened
SQL> create spfile from pfile='C:\TEMP\initDBGRIDnew.ora';
File created.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
ORACLE instance started.
Total System Global Area 535662592 bytes
Fixed Size 1375792 bytes
Variable Size 327156176 bytes
Database Buffers 192937984 bytes
Redo Buffers 14192640 bytes
Database mounted.
Database opened.
SQL> select instance_name, status from v$instance;
INSTANCE_NAME STATUS
dbgrid OPEN
Create a new TEMP tablespace, make this as the new default temporary tablespace. Drop the old TEMP tablespace. Restart the database.
SQL> CREATE TEMPORARY TABLESPACE TEMP01 TEMPFILE 'D:\oradbgrid\oradata\TEMP0101.dbf' SIZE 200M;
Tablespace created.
SQL> ALTER DATABASE DEFAULT TEMPORARY TABLESPACE TEMP01;
Database altered.
SQL> drop tablespace TEMP including contents and datafiles;
Tablespace dropped.
SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup mount;
ORACLE instance sta -
Creating Standby Database / Steps might be missing..
I have created standby database..
The archives are copied except one archived log and those copied archived are not applied at Standby database.
Besides this issue, I just checked the alert log file and pasting its contents here.
Do check it and let me know If I m missing any paramter[s].
Dump file c:\oracle\product\10.2.0\admin\rockstd\bdump\alert_rockstd.log
Mon May 12 15:23:42 2008
ORACLE V10.2.0.1.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Windows XP Version V5.1 Service Pack 2
CPU : 2 - type 586
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:1194M/2038M, Ph+PgF:1368M/2641M, VA:1940M/2047M
Mon May 12 15:23:42 2008
Starting ORACLE instance (normal)
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 0
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
sga_target = 167772160
control_files = C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\ROCKSTD.CTL
db_block_size = 8192
compatible = 10.2.0.1.0
log_archive_dest_1 = location=C:\oracle\product\10.2.0\oradata\rockstd\Archive_rock
log_archive_dest_state_1 = ENABLE
log_archive_format = arc_%s_%t_%r.arc
fal_client = ROCKSTD
fal_server = ROCK
db_file_multiblock_read_count= 16
db_recovery_file_dest = C:\oracle\product\10.2.0\flash_recovery_area\rockstd
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
db_domain =
dispatchers = (PROTOCOL=TCP) (SERVICE=rockXDB)
job_queue_processes = 10
audit_file_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\ADUMP
background_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\BDUMP
user_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\UDUMP
core_dump_dest = C:\ORACLE\PRODUCT\10.2.0\ADMIN\ROCKSTD\CDUMP
db_name = rock
db_unique_name = rockstd
open_cursors = 300
pga_aggregate_target = 16777216
PMON started with pid=2, OS id=3656
PSP0 started with pid=3, OS id=504
MMAN started with pid=4, OS id=2544
DBW0 started with pid=5, OS id=3652
LGWR started with pid=6, OS id=552
CKPT started with pid=7, OS id=2688
SMON started with pid=8, OS id=3436
RECO started with pid=9, OS id=3696
CJQ0 started with pid=10, OS id=1636
MMON started with pid=11, OS id=2072
MMNL started with pid=12, OS id=3812
Mon May 12 15:23:43 2008
starting up 1 dispatcher(s) for network address '(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))'...
starting up 1 shared server(s) ...
Mon May 12 15:24:06 2008
alter database mount standby database
Mon May 12 15:24:11 2008
Setting recovery target incarnation to 14
ARCH: STARTING ARCH PROCESSES
ARC0 started with pid=16, OS id=3536
Mon May 12 15:24:11 2008
ARC0: Archival started
ARC1 started with pid=17, OS id=4084
Mon May 12 15:24:12 2008
ARC1: Archival started
ARCH: STARTING ARCH PROCESSES COMPLETE
Mon May 12 15:24:12 2008
ARC1: Becoming the 'no FAL' ARCH
ARC1: Becoming the 'no SRL' ARCH
ARC1: Thread not mounted
Mon May 12 15:24:12 2008
Successful mount of redo thread 1, with mount id 3275426006
Mon May 12 15:24:12 2008
Physical Standby Database mounted.
Mon May 12 15:24:13 2008
ARC0: Becoming the heartbeat ARCH
Completed: alter database mount standby database
Mon May 12 15:25:02 2008
Using STANDBY_ARCHIVE_DEST parameter default value as C:\oracle\product\10.2.0\oradata\rockstd\Archive_rock
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[1]: Assigned to RFS process 3444
RFS[1]: Identified database type as 'physical standby'
Mon May 12 15:25:02 2008
RFS LogMiner: Client disabled from further notification
Mon May 12 15:25:21 2008
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.
Mon May 12 15:26:19 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo04.log' size 50m
Mon May 12 15:26:20 2008
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo04.log' size 50m
Mon May 12 15:26:27 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo05.log' size 50m
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo05.log' size 50m
Mon May 12 15:26:33 2008
alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo06.log' size 50m
Mon May 12 15:26:34 2008
Completed: alter database add standby logfile 'C:\oracle\product\10.2.0\oradata\rockstd\redo06.log' size 50m
Mon May 12 15:27:20 2008
alter database recover managed standby database disconnect from session
MRP0 started with pid=19, OS id=596
Managed Standby Recovery not using Real Time Apply
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\UNDOTBS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSAUX01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\TESTING1.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM03.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_dbw0_3652.trc:
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\ABAMCO_TEST01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
MRP0: Background Media Recovery terminated with error 1110
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_mrp0_596.trc:
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
Mon May 12 15:27:26 2008
Errors in file c:\oracle\product\10.2.0\admin\rockstd\bdump\rockstd_mrp0_596.trc:
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'D:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCK\SYSTEM01.DBF'
Mon May 12 15:27:27 2008
Completed: alter database recover managed standby database disconnect from session
Mon May 12 15:30:18 2008
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[2]: Assigned to RFS process 2456
RFS[2]: Identified database type as 'physical standby'
Primary database is in MAXIMUM PERFORMANCE mode
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 15:30:22 2008
Redo Shipping Client Connected as PUBLIC
-- Connected User is Valid
RFS[3]: Assigned to RFS process 3124
RFS[3]: Identified database type as 'physical standby'
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 15:53:45 2008
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 15:53:46 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 15:53:58 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:06 2008
RFS[3]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:09 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Mon May 12 16:00:14 2008
RFS[3]: Successfully opened standby log 5: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO05.LOG'
Mon May 12 16:00:18 2008
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Primary database is in MAXIMUM PERFORMANCE mode
RFS[2]: Successfully opened standby log 4: 'C:\ORACLE\PRODUCT\10.2.0\ORADATA\ROCKSTD\REDO04.LOG'
Regards,
Rakesh Soni.Done, I've given the same path in Standby Database [datafiles, controlfiles] as it has been given in the Primary Database.
MoreOver, I m manually switching logfiles at primary database [alter system switch logfile] they are copied and applied sucessfully at standby database. But the archived files that I have copied with cold backup are not applied yet. Infact they are not retrieved executing the below query.
select name, applied from v$archived_log;
How can I apply those archived logs? [archives that copied with cold backup]
Regards. -
Primary and Physical Standby databases hanging on sqlplus shell command...
I am primarily a java developer that has had the task of oracle dba thrust upon me due to circumstances that are beyond my control. In the QA lab we have two oracle 10 g release 1 instances running. They set up in a dataguard configuration: one is the primary and the other is in a physical standby.
Last week I noticed that the disk space on the primary database was at 100%. After some investigation I discovered that a good deal of the files taking up space on the box were log files and the best solution that I could think of would be to delete all old archive files. So I deleted the old archive files that were at least two weeks old using RMAN.
During this week the database started to shutdown automatically. The QA associate restarted the database twice using the ‘STARTUP’ command from sqlplus. Additionally, the standby database began to have issues: when login in to sqlplus the application would just hang: no ‘SQL” prompt or anything. Finally today the primary database has also begun to hang in a similar manner.
I have looked at many of the trace files and alert logs but haven’t been able to really discern what the real problem is with the database and the proper rectification for the database. Does anyone have a clue into what is going on? If someone could even point me in the right direction it would be greatly appreciated.Guessing that your flash recovery area is full, archiving is stopped so the instance appears to hang.
Do you see messages like so in the alert log:
You have following choices to free up space from flash recovery area:
1. Consider changing RMAN RETENTION POLICY. If you are using Data Guard,
then consider changing RMAN ARCHIVELOG DELETION POLICY.
2. Back up files to tertiary device such as tape using RMAN
BACKUP RECOVERY AREA command.
3. Add disk space and increase db_recovery_file_dest_size parameter to
reflect the new space.
4. Delete unnecessary files using RMAN DELETE command. If an operating
system command was used to delete files, then use RMAN CROSSCHECK and
DELETE EXPIRED commands.
************************************************************************ -
Hi All,
I am getting the following error when trying to CONFIGURE STANDBY database using rman,db version 10.2.0.2(HP-UX 11.2),library link seems to be fine.
do i have to relink the library to oracle on the stanby db host too? any suggestion please.
connect target / catalog rman@xx auxiliary sys@aux
RMAN> run {
allocate channel c1 device type 'sbt_tape';
ALLOCATE AUXILIARY CHANNEL aux1 DEVICE TYPE 'SBT_TAPE';
duplicate target database for standby dorecover;}2> 3> 4>
allocated channel: c1
channel c1: sid=164 instance=WWPODSP1 devtype=SBT_TAPE
channel c1: Data Protector A.06.00/331
released channel: c1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of allocate command on aux1 channel at 05/09/2007 16:57:07
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 11
RMAN> show all;
RMAN configuration parameters are:
CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 45 DAYS;
CONFIGURE BACKUP OPTIMIZATION ON;
CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE 'SBT_TAPE' TO 'control_file_%F';
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '%F'; # default
CONFIGURE DEVICE TYPE SBT_TAPE PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DEVICE TYPE DISK PARALLELISM 1 BACKUP TYPE TO BACKUPSET; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE SBT_TAPE TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE CHANNEL DEVICE TYPE 'SBT_TAPE' PARMS 'SBT_LIBRARY=/opt/omni/lib/libob2oracle8_64bit.so';
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/10.2.0/db_1/dbs/snapcf_WWPODSP1.f'; # defaultsorry here is the exact commands.
rman TARGET / AUXILIARY sys/xxx@WWPODSS catalog rman@rman
Recovery Manager: Release 10.2.0.2.0 - Production on Wed May 9 17:29:37 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
connected to target database: WWPODSP (DBID=669261963)
recovery catalog database Password:
connected to recovery catalog database
connected to auxiliary database: WWPODSP (not mounted)
RMAN> run
2> {
3> duplicate target database for standby dorecover;}
Starting Duplicate Db at 09-MAY-07
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 05/09/2007 17:33:35
ORA-19554: error allocating device, device type: SBT_TAPE, device name:
ORA-27211: Failed to load Media Management Library
Additional information: 11
RMAN> -
Ensure temporary files exist on the standby database
Hi,
in a datagurd configuration (10g R2 on Windows) how to Ensure temporary files exist on the standby database that match the temporary files on the primary database ?
Many thanks.setting the retention target doesnt mean that the unnecessary flashback logs get deleted automatically, its just a threshold, that has to be guaranteed
the database works like "ok i can fulfill the desired flashback retention target with the current flashback logs, but there are some (a lot of) extra free space left in the FRA (db_recovery_file_dest_size = 100 GB), so lets just continue writing flashback logs, meaning that you will be able to flashback to an even earlier time/SCN if you wish"
once the FRA gets full, and something else needs the space in the FRA (archivelog, newer flashback log, etc), THEN the old flashback logs will be deleted
if it really annoys you, you can force the deletion of flashback logs by setting the db_recovery_file_dest_size parameter temporarily to a lower value (not too low, check before how much space is really needed in there), then the database will delete the unnecessary files from there - then set it back to its original value -
Hi
Current 10.2.0.4 Setup is with Dataguard Broker (Unix/No OEM Setup):
Rac Primary 2node cluster
Rac Standby 2node cluster
The rac Standby Database are going to be opened read/write.
Then will require a rebuild of standby ie delete db files and duplicate db using rman
1) My questions is how do I rebuild of a rac standby database with an existing enabled dg broker?
2) Are there any documentation on the steps to follow.
3) Should the dg broker config be dropped or just disabled and if so at which stage?
Config on Rac primary should be kept to a minimum as its being used so no outage expected here.
Regards
MeHave you given any thought to using flashback (depending on how long your standby will be open for read/write)? You could (before you open read/write) copy your dr*.dat files (broker config files), stop the broker and create a guarenteed restore point. After you have finished and ready to convert back to standby you would flashback your database to the restore point, convert back to a physical standby, restart the broker and shutdown. Restore the dr*.dat files to their location and then startup the standby. From there it should fetch the logs from the time the broker was down and catch back up.
If you would rather rebuild, again you would need to take the broker out of the equation and use RMAN to create a clone for standby and then once in place you would reconfigure the broker (may be able to just restore the dr*.dat files from before the open operation but unsure. -
Standby database is not applying redo logs due to missing archive log
We use 9.2.0.7 Oracle Database. My goal is to create a physical standby database.
I have followed all the steps necessary to fulfill this in Oracle Data Guard Concepts and Administration manual. Archived redo logs are transmitted from primary to standby database regularly. But the logs are not applied due to archive log gap.
SQL> select process, status from v$managed_standby;
PROCESS STATUS
ARCH CONNECTED
ARCH CONNECTED
MRP0 WAIT_FOR_GAP
RFS RECEIVING
RFS ATTACHED
SQL> select * from v$archive_gap;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 503 677
I have tried to find the missing archives on the primary database, but was unable to. They have been deleted (somehow) regularly by the existing backup policy on the primary database. I have looked up the backups, but these archive logs are too old to be in the backup. Backup retention policy is 1 redundant backup of each file. I didn't save older backups as I didn't really need them from up to this point.
I have cross checked (using rman crosscheck) the archive log copies on the primary database and deleted the "obsolete" copies of archive logs. But, v$archived_log view on the primary database only marked those entries as "deleted". Unfortunately, the standby database is still waiting for those logs to "close the gap" and doesn't apply the redo logs at all. I am reluctant to recreate the control file on the primary database as I'm afraid this occurred through the regular database backup operations, due to current backup retention policy and it probably might happen again.
The standby creation procedure was done by using the data files from 3 days ago. The archive logs which are "producing the gap" are older than a month, and are probably unneeded for standby recovery.
What shall I do?
Kind regards and thanks in advance,
MilivojOn a physical standby database
To determine if there is an archive gap on your physical standby database, query the V$ARCHIVE_GAP view as shown in the following example:
SQL> SELECT * FROM V$ARCHIVE_GAP;
THREAD# LOW_SEQUENCE# HIGH_SEQUENCE#
1 7 10
The output from the previous example indicates your physical standby database is currently missing log files from sequence 7 to sequence 10 for thread 1.
After you identify the gap, issue the following SQL statement on the primary database to locate the archived redo log files on your primary
database (assuming the local archive destination on the primary database is LOG_ARCHIVE_DEST_1):
SQL> SELECT NAME FROM V$ARCHIVED_LOG WHERE THREAD#=1 AND DEST_ID=1 AND 2> SEQUENCE# BETWEEN 7 AND 10;
NAME
/primary/thread1_dest/arcr_1_7.arc /primary/thread1_dest/arcr_1_8.arc /primary/thread1_dest/arcr_1_9.arc
Copy these log files to your physical standby database and register them using the ALTER DATABASE REGISTER LOGFILE statement on your physical standby database. For example:
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_7.arc';
SQL> ALTER DATABASE REGISTER LOGFILE
'/physical_standby1/thread1_dest/arcr_1_8.arc';
After you register these log files on the physical standby database, you can restart Redo Apply.
Note:
The V$ARCHIVE_GAP fixed view on a physical standby database only returns the next gap that is currently blocking Redo Apply from continuing. After resolving the gap and starting Redo Apply, query the V$ARCHIVE_GAP fixed view again on the physical standby database to determine the next gap sequence, if there is one. Repeat this process until there are no more gaps.
Restoring the archived logs from the backup set
If the archived logs are not available in the archive destination then at that time we need to restore the required archived logs from the backup step. This task is accomplished in the following way.
To restore range specified archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore'
Restore archivelog from logseq=<xxxxx> until logseq=<xxxxxxx>
To restore all the archived logs:
Run {
Set archivelog destination to '/oracle/arch/arch_restore';
Restore archivelog all;
} -
Failed to clone DB from StandBy database
Hello,
I need to perform a clone of Data Guard physical standby database (production) to use in preproduction. we have a full RMAN backup of standby database.
My restore is failed, i use this steps:
* full RMAN backup of standby database
* backup control file of primary
* on a new database server, copy backup
* RMAN > restore control file (of brimary)
* RMAN > CATALOG START WITH ' Path of backup'
* crosscheck backup
* restore database
-> the restore is failed with errors messages :
RMAN-06026: some targets not found - aborting restore
RMAN-06023: no backup or copy of datafile 4 found to restore
RMAN-06023: no backup or copy of datafile 3 found to restore
RMAN-06023: no backup or copy of datafile 2 found to restore
RMAN-06023: no backup or copy of datafile 1 found to restore
I retry restore database after restoring a standby control file, it's failed with the same message.
can you help me ,please, to resolve this issue
Regards
DjThank's AbuFazalMdAbbas for your reply,
RMAN > list backup : i display only 3 Piece Name
BS Key Type LV Size Device Type Elapsed Time Completion Time
18364 Incr 1 36.56M DISK 00:22:11 29-JUL-13
BP Key: 18364 Status: AVAILABLE Compressed: YES Tag: DIGI_SEC_DB1_DAT
Piece Name: /mnt/backup/RMAN/SEC_DB1/files/rman_SEC_DB1_29_01_0fofu8j3_1_1
List of Datafiles in backup set 18364
File LV Type Ckp SCN Ckp Time Name
17 1 Incr 22020167729 29-JUL-13 +DATA/DB1/datafile/indx_fusion54_purge.277.753031091
25 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.284.762608775
44 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.303.799865601
64 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.324.809446025
BS Key Type LV Size Device Type Elapsed Time Completion Time
18365 Incr 1 11.17M DISK 00:22:12 29-JUL-13
BP Key: 18365 Status: AVAILABLE Compressed: YES Tag: DIGI_SEC_DB1_DAT
Piece Name: /mnt/backup/RMAN/SEC_DB1/files/rman_SEC_DB1_29_01_0gofu8j3_1_1
List of Datafiles in backup set 18365
File LV Type Ckp SCN Ckp Time Name
18 1 Incr 22020167729 29-JUL-13 +DATA/DB1/datafile/indx_fusion54_purge.279.753031091
26 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.285.762622281
45 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.304.800028323
65 1 Incr 22020167729 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.325.814713695
BS Key Type LV Size Device Type Elapsed Time Completion Time
18366 Incr 1 49.25M DISK 00:11:54 29-JUL-13
BP Key: 18366 Status: AVAILABLE Compressed: YES Tag: DIGI_SEC_DB1_DAT
Piece Name: /mnt/backup/RMAN/SEC_DB1/files/rman_SEC_DB1_29_01_0hofu9sq_1_1
List of Datafiles in backup set 18366
File LV Type Ckp SCN Ckp Time Name
4 1 Incr 22021555818 29-JUL-13 +DATA/DB1/datafile/users.281.753031093
27 1 Incr 22021555818 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.286.763655749
47 1 Incr 22021555818 29-JUL-13 +DATA/SEC_DB1/datafile/indx_cmsco.306.800463801
66 1 Incr 22021555818 29-JUL-13 +DATA/SEC_DB1/datafile/data_cmsco.326.817754983
# cd <location where backup files were copied>
# ls -lrt
ALL files (piece name in list backup) exist on file System, and it's owner by oracle
# show all
RMAN> show all;
using target database control file instead of recovery catalog
RMAN configuration parameters for database with db_unique_name RSP are:
CONFIGURE RETENTION POLICY TO REDUNDANCY 1; # default
CONFIGURE BACKUP OPTIMIZATION OFF; # default
CONFIGURE DEFAULT DEVICE TYPE TO DISK; # default
CONFIGURE CONTROLFILE AUTOBACKUP ON;
CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '+RECO/ctrl_%F';
CONFIGURE DEVICE TYPE DISK PARALLELISM 2 BACKUP TYPE TO COMPRESSED BACKUPSET;
CONFIGURE DATAFILE BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE ARCHIVELOG BACKUP COPIES FOR DEVICE TYPE DISK TO 1; # default
CONFIGURE MAXSETSIZE TO UNLIMITED; # default
CONFIGURE ENCRYPTION FOR DATABASE OFF; # default
CONFIGURE ENCRYPTION ALGORITHM 'AES128'; # default
CONFIGURE COMPRESSION ALGORITHM 'BASIC' AS OF RELEASE 'DEFAULT' OPTIMIZE FOR LOAD TRUE ; # default
CONFIGURE ARCHIVELOG DELETION POLICY TO NONE; # default
CONFIGURE SNAPSHOT CONTROLFILE NAME TO '/u01/app/oracle/product/11.2.0/db/dbs/snapcf_MNTRSP.f'; # default -
Creating a new schema in a Logical Standby Database
Hi All,
I am experimenting with logical standby databases for the purpose of reporting, and have not been able to create a new schema in the logical standby database - one of the key features of logical standbys.
I have setup primary and logical standby databases, and they seem to be running just fine - changes are moved from the primary to the standby and queries on the standby seem to run ok.
However, If I try to create a new schema on the logical standby, that does not exist on the primary, I get "ORA-01031: insufficient privileges" errors when I try to create new objects.
Show below are the steps I have taken to create the new schema on the logical standby. Any help would be greatly appreciated.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_new
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user new
2 identified by new
3 default tablespace ts_new
4 temporary tablespace temp
5 quota unlimited on ts_new
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to new
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to new
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to new
SYS@UATDR> select * from dba_sys_privs where grantee='NEW'
2 /
GRANTEE PRIVILEGE ADM
NEW CREATE ANY TABLE NO
NEW CREATE TABLE NO
NEW UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect new/new
Connected.
NEW@UATDR>
NEW@UATDR> -- prove ability to create tables
NEW@UATDR> create table new
2 (col1 number not null)
3 tablespace ts_new
4 /
create table new
ERROR at line 1:
ORA-01031: insufficient privileges
NEW@UATDR>
NEW@UATDR>HI Daniel,
I appreciate your quick response.
My choice of name may not have been ideal, however changing new to another name - like gav - does not solve the problem.
SYS@UATDR> connect / as sysdba
Connected.
SYS@UATDR>
SYS@UATDR> select name, log_mode, database_role, guard_status, force_logging, flashback_on, db_unique_name
2 from v$database
3 /
NAME LOG_MODE DATABASE_ROLE GUARD_S FOR FLASHBACK_ON DB_UNIQUE_NAME
UATDR ARCHIVELOG LOGICAL STANDBY ALL YES YES UATDR
SYS@UATDR>
SYS@UATDR> create tablespace ts_gav
2 /
Tablespace created.
SYS@UATDR>
SYS@UATDR> create user gav
2 identified by gav
3 default tablespace ts_gav
4 temporary tablespace temp
5 quota unlimited on ts_gav
6 /
User created.
SYS@UATDR>
SYS@UATDR> grant connect, resource to gav
2 /
Grant succeeded.
SYS@UATDR> grant unlimited tablespace, create table, create any table to gav
2 /
Grant succeeded.
SYS@UATDR>
SYS@UATDR> -- show privs given to gav
SYS@UATDR> select * from dba_sys_privs where grantee='GAV'
2 /
GRANTEE PRIVILEGE ADM
GAV CREATE TABLE NO
GAV CREATE ANY TABLE NO
GAV UNLIMITED TABLESPACE NO
SYS@UATDR>
SYS@UATDR> -- create objects in schema
SYS@UATDR> connect gav/gav
Connected.
GAV@UATDR>
GAV@UATDR> -- prove ability to create tables
GAV@UATDR> create table gav
2 (col1 number not null)
3 tablespace ts_gav
4 /
create table gav
ERROR at line 1:
ORA-01031: insufficient privileges
GAV@UATDR>
Maybe you are looking for
-
Hi, Further to my previous posting yesterday I have somehow miraculously managed to find and restore my playlist folders (although some of my playlists that I created are missing tracks for some reason - any suggestions???). However, as happy as I am
-
File is being truncated by Sender File Adapter
Hello, My input file is very wide. It has got 175 fields and is around 4000+ char wide. When file adapter loads it, the inbound payload does not contain all the fields (i.e. it is being truncated). Any idea that how can I load this too wide file! Tha
-
Hi, when promoting "Crystal Report 2013" report (with data connectivity BW MDX Query) from BO DEV to BO PROD with BO Promotion Mgmt (LCM), we get the following error message in LCM jobs history: Resolution Status=Overwritten, Dependency Status=All th
-
Element type "translatable" must be declared. Message - my first faces page
Good day, I kept getting this stack trace on my first adf faces page test. I am deploying the application on glassfish but I don't think that it should be a problem because I have deployed the adffaces demo. The stacktrace is [#|2009-07-02T20:46:11.3
-
What ver of 64 bit itunes do i d/l
which version of itunes 64 bit does one use? I have Vista