tag:blogger.com,1999:blog-2530682427657016426.post5199916128873827878..comments2024-03-28T08:29:25.033+01:00Comments on Marko Sutic's Database Blog: RMAN Duplicate from Active Database - ASM to non-ASMMarko Sutichttp://www.blogger.com/profile/08926232581329666732noreply@blogger.comBlogger11125tag:blogger.com,1999:blog-2530682427657016426.post-51448199216678025152018-08-07T10:18:23.928+02:002018-08-07T10:18:23.928+02:00Thanks Marco. I've done lots of backup-based d...Thanks Marco. I've done lots of backup-based duplication, but not active duplication for many years and not asm / omf to non-rac. I ran into the same errors you did yesterday and did not finish, so I was researching some more to fix the remaining errors. I found a Oracle doc stating that omf named source files cannot use db_file_name_convert to rename them. Your nice writeup confirms that, as I had planned to use set newname today to hopefully fix my remaining errors. <br /> I have another wrinkle I need to solve and that is to duplicate from db1 instance name / db database name in rac/asm to db instance name / db database name non asm. I seemed to have had some connectivity errors early on using same names on source and dest, so I changed to different name for dest just to get past those problems. After getting the basic duplication working, I'm going to return to the same name issue. Should be doable as it works in non-rac. Thanks for taking the time to share this.Bonehttps://www.blogger.com/profile/02633889211285284537noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-28579755100415630532014-02-18T11:18:02.914+01:002014-02-18T11:18:02.914+01:00Well done keep updates, thanks.Well done keep updates, thanks.oracle recruitment grouphttp://www.oracleconnections.com/opensocial/ningapps/show?appUrl=http://apps.io/listings/?ning-app-status%3Dnetwork&owner=2d4tvhv2r7yi5noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-25595649584113048882014-01-13T21:56:42.500+01:002014-01-13T21:56:42.500+01:00Hello J.A.,
have you tried to add SET CLUSTER_DAT...Hello J.A.,<br /><br />have you tried to add SET CLUSTER_DATABASE=FALSE in RMAN duplicate command? You're probably using CLUSTER_DATABASE=TRUE for non-RAC database.<br /><br />Note that I haven't tried RAC ASM to non-RAC non-ASM scenario so I might be wrong with my advice.<br /><br />Thanks for comment.<br /><br />Regards,<br />Marko<br />Marko Sutichttps://www.blogger.com/profile/08926232581329666732noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-20889770525695406962014-01-13T19:55:11.656+01:002014-01-13T19:55:11.656+01:00Hi, I have found very interesting your post, thanx...Hi, I have found very interesting your post, thanx a lot for it...<br /><br />I have to duplicate a database that is in RAC with ASM to a Non-RAC and Non-ASM database, in different server, but I'm getting this messages:<br /><br />connected to auxiliary database (not started)<br />RMAN-00571: ===========================================================<br />RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============<br />RMAN-00571: ===========================================================<br />RMAN-03002: failure of Duplicate Db command at 01/13/2014 12:43:38<br />RMAN-05501: aborting duplication of target database<br />RMAN-03015: error occurred in stored script Memory Script<br />RMAN-04014: startup failed: ORA-00439: feature not enabled: Real Application Clusters<br /><br />Do you have any idea to avoid/fix it???<br /><br />Thank for your atention...<br /><br />Regards...<br /><br />J.A....<br />Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-27754544038687140402013-10-17T14:37:21.551+02:002013-10-17T14:37:21.551+02:00No problem Babak.
Your comment was still useful to...No problem Babak.<br />Your comment was still useful to me. Error you've experienced was unknown to me.<br /><br />Thanks again for your feedback.<br /><br />Regards,<br />Marko<br />Marko Sutichttps://www.blogger.com/profile/08926232581329666732noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-15414698126204023662013-10-17T14:16:17.203+02:002013-10-17T14:16:17.203+02:00Hey Marko,
I believe I've made a mistake in j...Hey Marko,<br /><br />I believe I've made a mistake in judging your script; I had to startup my "duplicate" instance using spfile, so I had to change the script (to remove the SPFILE clause). So obviously my circumstances were different, and that must have caused me issues.<br /><br />Sorry for the confusion, and thanks again for the guide. It was very useful to me.<br /><br />B.<br /><br />Babak Touranihttps://www.blogger.com/profile/13242865000119781400noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-55893989631992629572013-10-17T12:43:53.127+02:002013-10-17T12:43:53.127+02:00Hello Babak,
I have checked Metalink note you spe...Hello Babak,<br /><br />I have checked Metalink note you specified.<br />Script noted there in "SYMPTOMS" cannot relate to my script as I'am not using log_file_name_convert in DUPLICATE clause.<br /><br />You can see in my scripts that log_file_name_convert is added in SPFILE and cause of that I don't experience RMAN-06588 error.<br /><br />Thanks for comment.<br /><br />Regards,<br />MarkoMarko Sutichttps://www.blogger.com/profile/08926232581329666732noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-73389172098683985362013-10-16T14:27:31.287+02:002013-10-16T14:27:31.287+02:00Hi, Thanks for the guide, very useful for a simila...Hi, Thanks for the guide, very useful for a similar task I was doing (file system to ASM though). <br /><br />Just one thing: I think you might need a change on the Rman script: on 11g I came across RMAN-06588 errors, while everything seemed ok. <br /><br />As it turns out: "DUPLICATE does not have a log_file_name_convert clause. Thus the string log_file_name_clause is considered another DB_FILE_NAME_CONVERT pattern." (Metalink 1130929.1). <br /><br />I deleted log convert clause and everything went fine. <br /><br />Thanks again for the guide.Babak Touranihttps://www.blogger.com/profile/13242865000119781400noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-20822493984358769252013-10-14T16:30:02.600+02:002013-10-14T16:30:02.600+02:00Really a very good post thanks for sharing your or...Really a very good post thanks for sharing your <a href="http://www.oracleconnections.com" rel="nofollow">oracle</a> knowledge<br />Anonymoushttps://www.blogger.com/profile/12511713606636809918noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-43152740109491551862013-10-14T13:36:36.602+02:002013-10-14T13:36:36.602+02:00Hello Nerendra,
source database is on 192.168.56....Hello Nerendra,<br /><br />source database is on 192.168.56.109 host and it is duplicated to 192.168.56.107 host - check my tnsnames.ora file.<br /><br />But you are correct - it is little confusing. I could use names instead of IP addresses and set different name for duplicate database to avoid confusion.<br /><br />Thanks for comment.<br /><br />Regards,<br />Marko<br /><br /><br /><br /><br /><br />Marko Sutichttps://www.blogger.com/profile/08926232581329666732noreply@blogger.comtag:blogger.com,1999:blog-2530682427657016426.post-61065926791372701742013-10-14T13:04:28.183+02:002013-10-14T13:04:28.183+02:00Marko,
I am bit confused with the naming conventi...Marko,<br /><br />I am bit confused with the naming convention you have used here. Which DB instance is being duplicated? Is the database on 192.168.56.107 being duplicated over to on 192.168.56.109 ?Narendrahttps://www.blogger.com/profile/14645699853364658640noreply@blogger.com