Thinking Out Loud

October 27, 2013

Playing with RMAN Merged Incremental Backup

Filed under: RMAN — mdinh @ 10:02 pm

Here are 2 good documents for reference:
Merged Incremental Backup Strategies (Doc ID 745798.1)
Oracle Backup and Recovery for a VLDB

You can find my playing around here

I did find the results of switch database to copy awkward with the data file name.

LAX:(SYS@db01)> show parameter db_create
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
db_create_file_dest                  string      /oracle/oradata
db_create_online_log_dest_1          string      /oracle/oradata
db_create_online_log_dest_2          string      /oracle/oradata
db_create_online_log_dest_3          string
db_create_online_log_dest_4          string
db_create_online_log_dest_5          string
LAX:(SYS@db01)> alter system set db_create_file_dest='/oracle/datafilecopy';
System altered.
LAX:(SYS@db01)> create tablespace testing datafile size 16m;
Tablespace created.
LAX:(SYS@db01)> select name from v$datafile;
NAME
--------------------------------------------------------------------------------
/oracle/datafilecopy/data_D-DB01_I-1452485914_TS-SYSTEM_FNO-1_pbonf3p6.dbf
/oracle/datafilecopy/data_D-DB01_I-1452485914_TS-SYSAUX_FNO-2_pconf3pm.dbf
/oracle/datafilecopy/data_D-DB01_I-1452485914_TS-UNDOTBS_FNO-3_p9onf3nk.dbf
/oracle/datafilecopy/data_D-DB01_I-1452485914_TS-USER_DATA_FNO-4_paonf3on.dbf
/oracle/datafilecopy/LAX_DB01/datafile/o1_mf_testing_96v0nk2p_.dbf
LAX:(SYS@db01)>

Is this something that can be lived with?

About these ads

2 Comments »

  1. Hi Michael,
    I’m not sure how it is supposed to work when You are doing ‘backup as >compressed< backupset check logical incremental level 1' .
    I mean compressed backupset is not the thing You can switch database to as far as I know .
    Regards
    GG

    Comment by goryszewskigGG — October 28, 2013 @ 7:58 am | Reply

    • Hi GG,
      Compress might not be absolutely necessary as the backup compress becomes obsolete after recovery copy of database is performed from the commands below:
      recover copy of database with tag MIB_UPDATE;
      delete noprompt obsolete redundancy=1;

      If you take a look at the log, I highlighted the deleted backupset.

      Think of it like performing backup and recovering in another database, but a little more simpler. I think backup should be done with check logical to detect corruption.

      Comment by mdinh — October 28, 2013 @ 2:00 pm | Reply


RSS feed for comments on this post. TrackBack URI

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

The Rubric Theme. Create a free website or blog at WordPress.com.

Follow

Get every new post delivered to your Inbox.

Join 300 other followers

%d bloggers like this: