Skip to main content

RMAN : Duplicate database without connecting to target

Using "backup location", I do not need to connect to target database, but how do I know what "until time" is available in the backup pieces? one way is to find the backup piece information from target database by using "list backup...", but what if I do not have the target database at all? while, I can arbitrarily give a time, then RMAN will tell me what is the time in those back pieces, nice!

Steps captured!

1.create the RAC database using dbca
2.create spfile='+oradata/bcfw/spfileBCFW.ora' from pfile='/tmp/pfile.ora'. 
   alter system set cluster_database=false scope=memory
3.srvctl start instance -d dbname -i dbname1 -o nomount
4.export NLS_DATE_FORMAT='yyyymmdd hh24:mi:ss'
5.rman> duplicate database
/* the backup was done using this:
RUN
{
  ALLOCATE CHANNEL ch11 TYPE DISK MAXPIECESIZE 1G;
  BACKUP as COMPRESSED backupset
  FORMAT '/u01/dba/jsun/%d_D_%T_%u_s%s_p%p'
  DATABASE
  PLUS ARCHIVELOG
  FORMAT '/u01/dba/jsun/%d_A_%T_%u_s%s_p%p';
  RELEASE CHANNEL ch11;
 }
*/

Duplicate database:
Method 1: get the until scn from target database.

export NLS_DATE_FORMAT='yyyymmdd hh24:mi:ss'
rman>
 list archivelog time between 'sysdate-1' and 'sysdate';
 list backup of archivelog time between 'sysdate-1' and 'sysdate';

On auxiliary database:
connect auxiliary  /
connect target sys/syspassword@targetdb
RUN
{
  ALLOCATE auxiliary  CHANNEL ch11 TYPE DISK MAXPIECESIZE 1G;
  set until scn 9776681621703;
  duplicate target database to 'BCFW' NOFILENAMECHECK;
  RELEASE   CHANNEL ch11;
 }

Method 2: replicate database using backup location without connecting to target database

export NLS_DATE_FORMAT='yyyymmdd hh24:mi:ss'
connect auxiliary  /
RUN
{
  ALLOCATE auxiliary  CHANNEL ch11 TYPE DISK MAXPIECESIZE 1G;
  duplicate database to 'BCFW' NOFILENAMECHECK until time "to_date('04-04-2019 13:31:18','dd-mm-yyyy hh24:mi:ss')" backup location '/u01/dba/jsun';
  RELEASE   CHANNEL ch11;
}

Errors in memory script
RMAN-06617: UNTIL TIME (20190404:13:31:18) is ahead of last NEXT TIME in archived logs (20190404:10:56:44)

Bingo! Now we get the correct time from the error 20190404:10:56:44

RUN
{
  ALLOCATE auxiliary  CHANNEL ch11 TYPE DISK MAXPIECESIZE 1G;
  duplicate database to 'BCFW' NOFILENAMECHECK until time "to_date('04-04-2019 10:56:44','dd-mm-yyyy hh24:mi:ss')" backup location '/u01/dba/jsun';
  RELEASE   CHANNEL ch11;
}

The duplicating database finish successfully!

6.
alter system set cluster_database=true scope=spfile;
select group#,member,status from gv$logfile;
select group#,thread#,bytes,status from gv$log;
alter database drop logfile group 21; ---... there are redundant redo groups.
alter database add logfile thread 2 group 4 ('+oraDATA01','+oraFLASH01') size 524288000 reuse;
alter database add logfile thread 2 group 5 ('+oraDATA01','+oraFLASH01') size 524288000 reuse;
alter database add logfile thread 2 group 6 ('+oraDATA01','+oraFLASH01') size 524288000 reuse;
alter database add logfile thread 3 group 7 ('+oraDATA01','+oraFLASH01') size 524288000 reuse;
alter database add logfile thread 3 group 8 ('+oraDATA01','+oraFLASH01') size 524288000 reuse;
alter database add logfile thread 3 group 9 ('+oraDATA01','+oraFLASH01') size 524288000 reuse;
alter database enable public thread 2;
alter database enable public thread 3;
show parameter undo
show parameter spfile; if you are using wrong spfile, correct that.
create pfile='/u01/dba/jsun/d' from spfile;  -- theck the parameters and make sure they are correct
select tablespace_name,file_name, bytes,autoextensible from dba_data_files where tablespace_name like '%UNDO%';
drop tablespace undotbs5; ... --- there are redundant undo...
#create undo tablespace UNDOTBS2 datafile  '+oraDATA01' size 500M;

7. srvctl start database -d BCFW; srvctl status database -d BCFW
8. srvctl add service -d BCFW -s BCFW_TAF -r "BCFW1,BCFW2,BCFW3"
srvctl modify service -d BCFW -s BCFW_TAF -e SELECT -m BASIC  -z 5 -w 0
/* options for srvctl modify service
 -P {NONE | BASIC | PRECONNECT} TAF policy specification
 -l <role> Role of the service (primary, physical_standby, logical_standby, snapshot_standby)
 -y <policy> Management policy for the service (AUTOMATIC or MANUAL)
 -e <Failover type> Failover type (NONE, SESSION, or SELECT)
 -m <Failover method> Failover method (NONE or BASIC)
 -w <integer> Failover delay
 -z <integer> Failover retries
*/

Comments

Post a Comment

Popular posts from this blog

Opatch apply/lsinventory error: oneoff is corrupted or does not exist

I am applying the quarterly patch for 19c RDBMS, I tried using napply but failed, but somehow it corrupted the inventory though nothing applied. further apply and lsinventory command ran into error like this: $ ./OPatch/opatch lsinventory Oracle Interim Patch Installer version 12.2.0.1.21 Copyright (c) 2020, Oracle Corporation.  All rights reserved. Oracle Home       : /u02/app/oracle/19.0.0 Central Inventory : /u01/app/oraInventory    from           : /u02/app/oracle/19.0.0/oraInst.loc OPatch version    : 12.2.0.1.21 OUI version       : 12.2.0.7.0 Log file location : /u02/app/oracle/19.0.0/cfgtoollogs/opatch/opatch2020-09-08_13-35-59PM_1.log Lsinventory Output file location : /u02/app/oracle/19.0.0/cfgtoollogs/opatch/lsinv/lsinventory2020-09-08_13-35-59PM.txt -------------------------------------------------------------------------------- Inventory load failed... OPatch cannot load inventory ...
Post a Comment
Read more

oracle dba_hist_sysmetric_summary

found this blog is helpful to get CPU and IO statistics on oracle database. http://shob-dbadmin.blogspot.ca/2012/12/how-to-find-total-io-of-database.html courtesy to  Shomil Bansal , below are hist writing, not mine. How to find total IO of the database instance Total IO of database instance is sum of the physical reads, physical writes and redo writes. There are several views to find these values. v$sysmetric  - Reports metric values for only the most current time sample 60 secs. v$sysmetric_summary  - Reports metric values for time sample of 1 hour. v$sysmetric_history  - Reports metric values every 60 sec from the time instance is up. Better way to analyse IO using this view to take deltas between two time periods. dba_hist_sysmetric_history  - All the above views are refreshed when the instance is restarted. This view, part of AWR, stores the historical stats. I have used this view for my report. Query: ====== set lines 350...
Post a Comment
Read more

Oracle ASM DISK IO performance

Oracle OEM show a chart of disk performance, as shown in the chart below. when the OEM target database is 10gr2, the number of average disk response time (ms) is 0.01 ms, which unreasonable low. when the target database is 11gr2, the number is about 10ms, which I think is reasonable. it's time to find out where the discrepency comes from. The backend query is this one: set linesize 200 col name format a9 col path format a19 --col MB_per_sec format select t3.name,t2.name,t2.path,t2.reads,t2.read_time,round(t2.read_time/t2.reads*1000,3) rd_rspd_ms,t2.writes,round(t2.write_time/t2.writes*1000,3) wr_rspd_ms, round((t2.read_time+t2.write_time)/(t2.reads+t2.writes)*1000,3) dsk_rspd_ms,round((t2.bytes_read+t2.bytes_written)/1024/1024/(t2.read_time+t2.write_time))  MB_per_sec from V$asm_disk t2, v$asm_diskgroup t3 where t3.group_number=t2.group_number order by 1,2 / NAME      NAME      PATH               ...
Post a Comment
Read more