RE: Need two databases same name, same cluster, different versions

From: Robert Freeman <rfreeman_at_businessolver.com>
Date: Fri, 11 Mar 2016 23:55:21 +0000
Message-ID: <BY2PR10MB07446C04DB399F67D6118BBAD5B50_at_BY2PR10MB0744.namprd10.prod.outlook.com>



Bet it’s off the shelf… Probably originally built for SQL Server and ported to Oracle when they realized that they needed a real database.

From: Peter Sharman [mailto:pete.sharman_at_oracle.com] Sent: Friday, March 11, 2016 5:51 PM
To: sbecker6925_at_gmail.com; Robert Freeman <rfreeman_at_businessolver.com> Cc: Mark W. Farnham <mwf_at_rsiz.com>; oracle-l <oracle-l_at_freelists.org> Subject: RE: Need two databases same name, same cluster, different versions

Spinning down the stupid d’uhvelopers that created an app with a hardcode DB name in it is also something that should be on your to-do list! ☹

Pete
[Oracle logo]
Pete Sharman
Database Architect, DBaaS / DBLM
Enterprise Manager Product Suite
33 Benson Crescent CALWELL ACT 2905 AUSTRALIA Phone: +61262924095<tel:+61262924095> | | Mobile: +61414443449 Email: pete.sharman_at_oracle.com<mailto:pete.sharman_at_oracle.com> Twitter: @SharmanPete LinkedIn: au.linkedin.com/in/petesharman Website: petewhodidnottweet.com



"Controlling developers is like herding cats." Kevin Loney, Oracle DBA Handbook

"Oh no, it's not, it's much harder than that!" Bruce Pihlamae, long term Oracle DBA


From: Sandra Becker [mailto:sbecker6925_at_gmail.com] Sent: Friday, March 11, 2016 4:41 AM
To: Robert Freeman <rfreeman_at_businessolver.com<mailto:rfreeman_at_businessolver.com>> Cc: Mark W. Farnham <mwf_at_rsiz.com<mailto:mwf_at_rsiz.com>>; oracle-l <oracle-l_at_freelists.org<mailto:oracle-l_at_freelists.org>> Subject: Re: Need two databases same name, same cluster, different versions

Spinning up a couple of RAC VMs isn't an option for me, but definitely a worthwhile idea. Sandy

On Thu, Mar 10, 2016 at 9:17 AM, Robert Freeman <rfreeman_at_businessolver.com<mailto:rfreeman_at_businessolver.com>> wrote: For something like this, I'd spin up a couple of RAC VM's and an application VM and do some testing to figure out what is really required to make the whole thing work successfully before I'd haul off and upgrade anything in real life. The ability to screw up VM's beyond recognition and then *poof* just restore them is wonderful! :)

On Mar 10, 2016, at 9:51 AM, Sandra Becker <sbecker6925_at_gmail.com<mailto:sbecker6925_at_gmail.com>> wrote:

I don't have any more information other than "the dbname is hardcoded in the app". I also was told no changes would be allowed to the app, which came as no surprise. I figured a TNS entry with an alias pointing to a new database would do the trick since I've done that before. I was told this would not work, they had tried it before and there was some issue with the scan listener. I don't know enough about RAC to say otherwise.

I'm going to upgrade GRID and the other three databases then try to get more details about why a tns entry didn't work before. The best solution would be to move the production app to a production database and I'll try to push that too. Sandy

On Thu, Mar 10, 2016 at 6:35 AM, Mark W. Farnham <mwf_at_rsiz.com<mailto:mwf_at_rsiz.com>> wrote: Explain more about EXACTLY what you mean when you write that the “database name” is hardcoded in the app.

I’m particularly interested in how this affects which instance or service they connect to from the application and whether it matters.

mwf

From: oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org> [mailto:oracle-l-bounce_at_freelists.org<mailto:oracle-l-bounce_at_freelists.org>] On Behalf Of Sandra Becker Sent: Wednesday, March 09, 2016 4:31 PM To: oracle-l
Subject: Need two databases same name, same cluster, different versions

What they want
(Servers are Linux)
Current database: ver. 11.2.0.4, 2-node RAC, dbname=DEVDB, hosts production application New database: ver. 12.1.0.2, 2-node RAC (same two nodes as the 11.2.0.4 DB), dbname=DEVDB, will host production application

Background on the request and suggested strategy

I was doing the prep work for upgrading four development RAC (GRID/ASM) databases to 12c when I ran into a lot of serious issues with one of them that we determined were too numerous to consider fixing before upgrading. I suggested just creating a new database with a different name, expdp/impdp the critical schemas and create developer schemas as needed. I was told we couldn't do that because the current database actually hosts a production application and the database name is hardcoded in the app. So now I have a poorly designed production app on a really messed up development database.

The decision was made not to upgrade this particular database, but rather create a new 12c RAC (GRID/ASM) database with the same name on the same cluster. I'm not that experienced with GRID/ASM or RAC, so I'm not sure this is possible. Am I mistaken in my belief that GRID/ASM wouldn't like two databases with the same name even if they were different versions? If it is possible, can someone point me to a white paper/website to help me work through the process?

My team lead made the suggestion to create a RAC OneNode database on one of the nodes in the cluster with the same dbname, do the necessary expdp/impdp, and simply shutdown the 11g database. Then convert the OneNode to a Cluster database. I can do that, but wouldn't that affect the installation option I need to upgrade the other three RAC databases? What about installing Cluster software in one OracaleHome and OneNode in a different OracleHome? I'm thinking that would solve the issue of OneNode vs. Cluster installation, but I'm not positive. And how would that affect converting it to a Cluster database later on? I'm sure I've left out details/information. I'm just not sure how to proceed with this request. I have to upgrade GRID and the other three databases this week. The "messed up" one can wait a week or two. Comments and suggestions are welcome and thank you.

--

Sandy B.

--

Sandy B.

--

Sandy B.



--

http://www.freelists.org/webpage/oracle-l

image001.jpg
Received on Sat Mar 12 2016 - 00:55:21 CET

Original text of this message