Saturday, June 03, 2006

Our current E-Biz work

In one of my previous entry, I talked about the licencing pricing that we had to get in order to ensure that our Oracle Financials implementation is properly licenced and for the future, our Supply Chain components too.

So, as a result, we had to migrate our existing Oracle Financials environment from a two server box to new servers (properly sized to meet current and future needs). Well, you would think that it's a no-brainer after all there are a lot of documentation in Metalink that show how an E-biz suite install can be "rapidly cloned" to new infrastructure, right? Errr...not really as it depends on the hardware involved and the nature of the "move".

In our case, we are moving from HP-UX (PA-RISC) to HP-UX (Itanium) and with Itanium in the picture, things gets a little bit complicated. Let me paint you a picture of what we current have. We currently have a separate server for the application tier which is a PA-RISC HP-UX server and it has everything except the database, the Concurrent Manager and the Reports Server which are on another PA-RISC HP-UX server. We want to move towards a totally separate database server without the Concurrent Manger and Reports Server which should be moved back to the application tier.

Since HP do not plan to carry the PA-RISC processor line beyond this calendar year, it does not make sense for us to keep our database on the PA-RISC server. Instead, we intend to move it over to one of the new Itanium servers and we would have loved to also move the Application tier to another Itanium server but unfortunately that has not been certified by Oracle yet (64-bit code). In this situation, we will be running the E-biz suite in what Oracle term a "split configuration" with the application tier on a PA-RISC server and the database tier on an Itanium server. Metalink has lots of articles on the various configuration including an FAQ. To further complicate things, we also want to upgrade the database version from 9.2.0.6 to 10.1.0.3 (10gR1). You might well asked, why not 10gR2? It's just that eventhough 10gR2 has been certified on the Itanium HP-UX server, E-biz itself has not been certified on the 10gR2 HP-UX split configuration although it has been certified for Linux Itanium. Go figure. Oracle plans to have the complete E-biz suite certified for HP-UX Itanium before the end of the calendar year.

Back to the approach that we are taking. First we have to do a merge since we are going from two application tier servers to one (remember, the Concurrent Manager and Reports Server are on a different server than the rest of the application tier). Since we are also moving to new hardware too, it will also be a clone and a database migration (to the new Itanium server) and finally an upgrade from 9.2.0.7 to 10.1.0.3. Whew! That's it. As part of the database upgrade, we will also need to follow the steps listed in the 10g Interoperability article. The challenge is that although Oracle has posted metalink articles on how to do each of these scenarios, nothing has been posted on how to do them all in one go so we are working out the timing and we will have to compress the actual work that needed to be done for final cut over as we probably only have a 48 hour window (the weekend) to shut down the existing Oracle Financials production environment, cut over, verify and start up the new environment for use come Monday morning.

It's all pretty exciting and we have already ran into obstacles and challenges which is a very good thing as it provides a fuller learning experience than if everything goes smoothly.

Once we are done in mid-July, I will provide a more detailed post on the actual steps that we took and the miscellaneous problems that we ran into.

Update June 9/06: I should note that this entry is a result of the work done by my team and the Oracle consultant who was contracted to help us with the migration.

2 comments:

Herod T said...

We too are moving our oracle financials this year, by september is the goal.

Believe it or not we are running 11.5.9 on a 8.1.7.4 database still.
It is certified, even though the database is defunct.

The web server sits on a linux server and the database and the rest of the application are all on an HPUX server.

I too raised the issue that we should move to what is going to be a supported configuration, but I was over ruled, the database and app stay on HPUX for the time being.

Not what I wanted, but I have been overruled.

So we have to take the database from 8.1.7.4 to 10gR2 as 10gR2 is certified with our linux front end.

Please, let me know of any major hurdles you come up against, there are only going to be 3 of us doing the conversion and one of those three we are hiring next week.

Atul Kumar said...

Peter ,
Have you thought of staged migration to reduce downtime ? ( You can create a staged middle tier ready before actual migration date & just migrate database with in given downtime . Its similar to staged appl_top approach used to reduce downtime during Upgrades .

Herod , We recently upgraded from 9.2.0.6 to 10GR2 & it was perfect . (2 Middle Tier Self SErvice on linux, 4 miidle tier for core applications on solaris, 1 database node on solaris with Reports & CM. There were no major issues .

Atul
http://becomeappsdba.blogspot.com