1 2 Previous Next 25 Replies Latest reply on Jan 9, 2019 1:45 AM by Dude!

Duplicate Database with additional incremental

serandrzej Dec 7, 2018 11:07 AM

Hello,

I want to migrate Oracle database from server1 to server2. I ran full incremental level 0 on source copied it to destination and started database duplication. All worked fine.

Now I have to keep databases in sync for few days. (Without any changes and not accessible) So I am doing incremental level 1 backups on source, copy them to dest and now came the problem. How can I apply them?

Of course I can start again duplication with full backup and then all incrementals in backup location will be applied automatically but as db is big it will take ages so this is not an option for me.

Is there any option in Duplicate command not to open db and keep it able to aplly subsequent level 1 incrementals? If not how I can deal with it ?

1. Re: Duplicate Database with additional incremental

Joerg.Sobottka Dec 7, 2018 11:18 AM (in response to serandrzej)

Well, the best solution is working with rolling forward image copies instead of cloning it. You can find how to do it well described e.g. at https://oracle-base.com/articles/misc/incrementally-updated-image-copy-backups
Another solution which is a little bit more difficult is, you can clone it "for standby" and do rman backups "from SCN" and recover them at the target. See e.g. https://www.thegeekdiary.com/how-to-roll-forward-a-standby-database-using-rman-incremental-backup-in-11g/
Like Show 0 Likes(0)

Actions
2. Re: Duplicate Database with additional incremental

serandrzej Dec 7, 2018 11:23 AM (in response to Joerg.Sobottka)

I cannot use those options as they require EE. Additionally idea is that in the switch day only small incremental will be copied not whole full backup with integrated incrementals. Servers are far away from each other and copy data takes many hours. So in the switch date I will copy last incremental and apply it and finally open database.
Like Show 0 Likes(0)

Actions
3. Re: Duplicate Database with additional incremental

Joerg.Sobottka Dec 7, 2018 11:50 AM (in response to serandrzej)

Why do you think rolling forward image copies or clone for standby does need EE? That isn't true...
You will not use Data Guard but incremental backups, you will not use Block Change Tracking files for fast incremental backups.
All you need is part of SE(2)!
https://docs.oracle.com/database/121/DBLIC/editions.htm#DBLIC116
Like Show 0 Likes(0)

Actions
4. Re: Duplicate Database with additional incremental

Joerg.Sobottka Dec 7, 2018 11:54 AM (in response to serandrzej)

Or you do it with more manual / scripted work than the other 2 solutions I have mentioned:
Alternative for standby database in standard edition (Doc ID 333749.1)
Like Show 0 Likes(0)

Actions
5. Re: Duplicate Database with additional incremental

serandrzej Dec 7, 2018 11:56 AM (in response to Joerg.Sobottka)

Maybe I understood this wrongly. But with incrementally updated copy I have to transfer new copy to destination which takes many hours. Or am I wrong ?
Like Show 0 Likes(0)

Actions
6. Re: Duplicate Database with additional incremental

serandrzej Dec 7, 2018 12:53 PM (in response to Joerg.Sobottka)

Yes this doco I know. I just wanted to have it simple. So as I see there is no way to use duplicate command. Alternatively I can manually catalog backups on destination do database restore, and after each incremental daily basis database recover and finally open database with resetlogs when to finally switch dbs. This would be simpler than standby for SE.
Like Show 1 Likes(1)

Actions
7. Re: Duplicate Database with additional incremental

PraveenKumarTm-Oracle Dec 7, 2018 1:33 PM (in response to serandrzej)

This thread has been moved to RMAN team.
Like Show 0 Likes(0)

Actions
8. Re: Duplicate Database with additional incremental

Dude! Dec 7, 2018 3:46 PM (in response to serandrzej)

You cannot use RMAN duplicate for such purpose since it generates a new DBID for the clone database and essentially creates another database. It is not possible to use the incremental level 1 backups or archivelogs from one database to recover another.

You can however create a standby database on another server and convert the existing physical standby database to a "snapshot standby database." You can then do the required testing on the snapshot database and convert it back to a physical standby to continue synchronizing with the primary database.

You can also restore and recover a database on another server and keep copying archivelogs and incremental level 1 backups, and continue the recovery process as long as you do not open the restored database.
Like Show 0 Likes(0)

Actions
9. Re: Duplicate Database with additional incremental

serandrzej Dec 7, 2018 5:34 PM (in response to Dude!)

Database duplication failed with message:

Starting recover at 07-DEC-18
starting media recovery
unable to find archived log
archived log thread=1 sequence=742644
Oracle instance started
Total System Global Area   32068440064 bytes
Fixed Size                     2269072 bytes
Variable Size              15569256560 bytes
Database Buffers           16441671680 bytes
Redo Buffers                  55242752 bytes
contents of Memory Script:
{
   sql clone "alter system set db_name =
''orcl'' comment=
''Reset to original value by RMAN'' scope=spfile";
   sql clone "alter system reset db_unique_name scope=spfile";
   shutdown clone immediate;
}
executing Memory Script

Errors in memory script
RMAN-03015: error occurred in stored script Memory Script
RMAN-06136: ORACLE error from auxiliary database: ORA-01507: Database is niet aangekoppeld.
ORA-06512: in "SYS.X$DBMS_RCVMAN", regel 13658
ORA-06512: in regel 1
RMAN-03015: error occurred in stored script Memory Script
RMAN-20000: abnormal termination of job step
RMAN-06054: media recovery requesting unknown archived log for thread 1 with sequence 742644 and starting SCN of 21595507990
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 12/07/2018 05:21:24
RMAN-05501: aborting duplication of target database

Can I consider this as a succesfull duplication ? If not how can I fix this ?
Like Show 0 Likes(0)

Actions
10. Re: Duplicate Database with additional incremental

Marshall Pyle Dec 7, 2018 6:47 PM (in response to serandrzej)

Hi,

It appears you are missing an archivelog for the RMAN duplicate to use making the datafiles consistent enough to open resetlogs. Look on your primary database server for the missing archivelog and copy over to your auxiliary server re-run the duplicate.

Thanks,
Marshall
Like Show 0 Likes(0)

Actions
11. Re: Duplicate Database with additional incremental

Dude! Dec 7, 2018 6:48 PM (in response to serandrzej)

Again, RMAN duplicate is not the solution according to your initial question.

RMAN-05501: aborting duplication of target database

Can I consider this as a succesfull duplication ? If not how can I fix this ?

How can this be successful?

If you still want to duplicate the database and have run into Problems please create a new thread with a new topic.
Like Show 0 Likes(0)

Actions
12. Re: Duplicate Database with additional incremental

serandrzej Dec 7, 2018 7:15 PM (in response to Dude!)

Ok to clarify this process Is it not enough to have full backup without archivelogs to run database duplicate ? And for manual restore, recover process, is it enough to have full and incrementals or I need to have archive logs as well ?
Like Show 0 Likes(0)

Actions
13. Re: Duplicate Database with additional incremental

serandrzej Dec 7, 2018 7:31 PM (in response to serandrzej)

Ok I tested only full and incremental and it did not work. So I will add all archive logs done after incremental. Would it work ?
Like Show 0 Likes(0)

Actions
14. Re: Duplicate Database with additional incremental

Dude! Dec 7, 2018 9:09 PM (in response to serandrzej)

So I will add all archive logs done after incremental.
What do you hope to accomplish? Again, after RMAN duplicate, you have essentially a new database and you cannot use recovery or restore data from another or the "original" database. You have other options. Please see my first response.
Like Show 0 Likes(0)

Actions

1 2 Previous Next

Go to original post