Convert 32 bit Linux to 64 bit - R12.1.3

[satish]

Hi Erman,
 

Existing environment:

Operating System RHEL 5.5 32-bit

Oracle Database 11.1.0.7 32-bit

Oracle Apps version 12.1.3 32-bit

Single node environment where database and apps hosted on the same server.

 

Requirement is to migrate 32-bit environment to 64-bit. As per our understanding, In outline:

 

Since RHEL Linux 5.5 -32 bit is not certified with any one of the EBS database and to be in valid certified configuration, we need to upgrade the OS version from RHEL 5.5 to RHEL -6 32-bit for to certify the database of version 11.2.0.4
 

DB will be upgraded from 11.1.0.7 to 11.2.0.4 which is certified with RHEL 6 32-bit.
 

Once database is upgraded, we will install RHEL 6 32-bit on new server.
 

We will Clone apps and database to the new server after meeting all the prerequisites in both Source and Target.(471566.1)
 

Then we will do actual OS 32 bit to 64-bit migration.
 

Please let us know if there is any change in above steps.

 

Thanks,

Satish

Oracle ERP Support

[ErmanArslansOracleBlog]

Hi, you will follow -> Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit (Doc ID 471566.1)


11.1.0.7 is not certified with RHEL 6, but 11.2.0.4 is certified with RHEL 5 32bit & 64 bit.

If the requirement is just migrating 32-bit environment to 64-bit, then it seems you can do it already..
But using 11.1.0.7 is not a good idea.. You should use 19C.. So you should upgrade to 11.2.0.4 and then you should consider upgrading 19C.

Note that, 19C requires Linux 7..

There are 2 ways;

If you want to upgrade your database during this process, then you can upgrade it in place (so upgrade 11.2.0.4 while you are using RHEL5), then you
can migrate to 64 bit (to Redhat 7 or Oracle Linux 7) -- (but this move is a little tricky because it involves both migration + OS upgrade) and then do the 19C upgrade..

or

As you say; migrate to Redhat 5 64 bit. Upgrade your database to 11.2.0.4 there and then migrate your database to Redhat 7 64 bit and upgrade your database to 19C while you are on Redhat 7 64bit :) this is also a good plan.. I feel myself closer to this one..

[satish]

Thanks for the update erman.

1) 11.2.0.4 certification is withdrawn for rhel 5 32 bit and 64 bit...
It's certified with Rhel 6/7 32 and 64bit...

Will it be feasible to go with option 2.Need your valuable suggestions


Thanks,
Satish

[ErmanArslansOracleBlog]

"11.2.0.4 certification is withdrawn for rhel 5 32 bit and 64 bit..." - who says that?? where did you read that?

Oracle Database 11.2.0.4.0 is certified on Linux Red Hat Enterprise Linux 5.
See -> Certification Information for Oracle Database on Linux x86 (Doc ID 1307056.1)
& also see -> Certification Tab on Oracle Support.

Yes. You can go with option 2 -> migrate to Redhat 5 64 bit. Upgrade your database to 11.2.0.4 there and then migrate your database to Redhat 7 64 bit and upgrade your database to 19C while you are on Redhat 7 64bit :)

I already said this was also a good plan and I felt myself closer to this one..

[satish]

Thanks as always.
Actually we have verified in certification tab in my oracle support.

We are trying option 2 as you suggested.

Acording to note id Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit ( DOc ID 471566.1 ).

Prior to performing the migration, both the source and target systems must meet the requirements documented in the Installation and Upgrade Notes Linux 32-bit and Linux 64-bit, respectively) and
Cloning Oracle Applications Release 12 with
Rapid Clone.


1) Pre-reqs in existing 32 bit server and pre-reqs for new target 64 bit server is done (installing rpmms, setting kernel parameters)--->Done
2) Following Cloning Oracle Applications Release
12 with Rapid Clone ( Doc ID 406982.1 )
Section 1: Prerequisite Tasks of the Cloning
Oracle Applications Release 12 with Rapid
Clone-->In Progress
Verify OS requirements on target system-->done
Verify source and target system software components and versions-->done
Apply the latest AD patch-->Applied
Apply the latest AutoConfig template patch---Applied
Apply the latest Rapid Clone patches--->Applied
Run AutoConfig on the application tiers---Failed
Synchronize appsutil on the database tier
nodess--->
Run AutoConfig on the database tiers--->
Maintain Snapshot Informations--->


Patches that we applied;

Latest AD patch 23569686 R12.AD.B.delta.8
Latest Autoconfig Patch 27135327 R12.TXK.B.delta.4
Latest Rapid Clone consolidated patch 27102203 OAM



Issue comes here:
--------------------------------
But after applying TXK delta 4,when we run autoconfig, it fails with error as stated in note id autoconfiq Retruned Error java.lang.NullPointerException' On Script adgentns.pl After Applying Patch R12.TXK.B.delta.4 (Doc ID 2507695.1)


This is what oracle support says:
Its just an auto-config issue, due to R12.TXK.B.Delta.4, which has brought additional checks for 11.2.x, 12.1.x, 12.2.x via ACUtil.java
120.3.12010000.4,this check is failing for 11.1.0.7 DB, and hence
auto-config is failing.
 R12.TXK.B.Delta.3 does not have this additional checks.issue is specific to 11.1.0.7 DB it seems, as the note suggests.

Any plan do suggest now?Can we skip this AD/TXK delta 4 and proceed further or any idea or suggestion?

Is it mandatory to apply these patches?currently we are on AD/TXK delta 3

Thanks,
Satish

[ErmanArslansOracleBlog]

Yes.. First start following -> Migrating Oracle E-Business Suite R12 from Linux 32-bit to Linux 64-bit ( DOc ID 471566.1 ).

Your first task it to migrate to 64 bit with the same OS version.
step by step.

Follow that document line by line and you ll be good.
If you any specific questions, you can ask me, but please don't send me all the steps in the document.. The things written in that document is already clear.
Thank you.

[satish]

Thank you.

Noted.

We are following the same document.

Patches that we applied;

Latest AD patch 23569686 R12.AD.B.delta.8
Latest Autoconfig Patch 27135327 R12.TXK.B.delta.4
Latest Rapid Clone consolidated patch 27102203 OAM



Issue
--------------------------------
After applying TXK delta 4,when we run autoconfig, it fails with error as stated in note id autoconfiq Retruned Error java.lang.NullPointerException' On Script adgentns.pl After Applying Patch R12.TXK.B.delta.4 (Doc ID 2507695.1)


This is what oracle support says:
Its just an auto-config issue, due to R12.TXK.B.Delta.4, which has brought additional checks for 11.2.x, 12.1.x, 12.2.x via ACUtil.java
120.3.12010000.4,this check is failing for 11.1.0.7 DB, and hence
auto-config is failing R12.TXK.B.Delta.3 does not have this additional
checks issue is specific to 11.1.0.7 DB it seems, as the
note suggests.

Is this patch mandatory to apply?

Any plan do suggest now?

Thanks a lot

[ErmanArslansOracleBlog]

Yes. That patch should be there, applied.

There in ACUtil.java, in isCDB method; we have a query like "select cdb from v$database", and probably, that's why you get null pointer.

that java can be modified and compiled according to your needs, but this would be a custom move and you will be desupported. There are things that can be done, but these all will make you desupported, so no need. Ask Oracle Support and request them to send you a modified ACUTil.java.

You can also ask them to approve using TXK Delta 3 instead (just for this case due to the lack of solution in TXK Delta 4)

[satish]

Thanks erman.

We started the migration.Following 762669.1 which is a part from 471566.1 ,as we are on 11.1.0.7

We have installed rhel 5.5 4bit on new server and all prerequisites are met.

Step 2 says to create rdbms oracle home on target machine.
That means do we have to install 11.1.0.7 64 bit software?

Thank you

[ErmanArslansOracleBlog]

Yes

[satish]

Dear erman,

Latest AD patch 23569686
R12.AD.B.delta.8----->applied
Latest Autoconfig Patch 27135327
R12.TXK.B.delta.4-->skipped
Latest Rapid Clone consolidated patch
27102203 OAM--->failed--it needs minimum
R12.TXK.B.delta.4 but we are on AD/TXK delta 3
Error:
Missing prerequisite codelevel for entity 'txk'.
This patch requires the following codelevel or
higher: 'R12.TXK.B.4'.
The current on-site codelevel for the entity 'txk'
is : 'R12.TXK.B.3'.
In order to apply this patch you must first apply
a patch that introduces
at least the minimum required codelevel.
Can we skip this patch and migrate to rhel 5.5
64 bit

From your experience,is it really required to apply these last 2 patches?

Thanks,
Satish

[satish]

Hi Erman,

We are not getting updates in sr and we are still following up.
Mostly,it seems like they may not approve to skip TXK delta 4.This issue seems specific to 11.1.0.7 database
issue will not occur if we upgrade the database to 11.2.0.4.In this case,we cannot go with option 2.

As our first option is tricky and complicated,can we go with below option

1)upgrade database from 11.1.0.7 to 11.2.0.4

2) Apply AD/TXK patches and run autoconfig (this time it should not fail)

3)Install rhel 5.5 64 bit on new server
4)Migrate database and application to this new server (This will complete 32 bit to 64 bit migration)

5)Then we will install rhel 7 in new server
6)Migrate app and db to this new server and start upgrading database to 19c.

Is this sounds better than option 1 which we discuss earlier?pls comment.

Thanks,
Satish

[ErmanArslansOracleBlog]

Facts:

11.1.0.7 is not certified with RHEL 6
11.2.0.4 is certified with RHEL 5 32bit & 64 bit.

In option 1 we said;

If the requirement is just migrating 32-bit environment to 64-bit, then it seems you can do it already..
But using 11.1.0.7 is not a good idea.. You should use 19C.. So you should upgrade to 11.2.0.4 and then you should consider upgrading 19C.

->-----------
If you want to upgrade your database during this process, then you can upgrade it in place (so upgrade 11.2.0.4 while you are using RHEL5), then you
can migrate to 64 bit (to Redhat 7 or Oracle Linux 7) -- (but this move is a little tricky because it involves both migration + OS upgrade) and then do the 19C upgrade..
->-----------

So, you can upgrade your db in-place and then convert to 64 it (by installing a rhel 5 64 bit and doing the migration) .. Then! You should install Linux 7 64 bit and migrate to there and lastly upgrade your db to 19C .. Linux 7 is required for 19C.