EBS 12.2 Apps Clone issue

[Hassan141]

I have been trying to run post clone EBS 12.2.6 on OL8.6 and getting this message again and again. I have read from your threads that XFS is not supported for Oracle EBS 12.2 but my DB size is more than 1.8 TB and ext4 supports upto 1TB. Funny part is I was successful during my first attempt, everything was fine but it was never successful again. in another post you also mentioned RPM binutils-2 version.

Enter the APPS password :
Error: missing `server' JVM at `/hello/d02/fs2/EBSapps/comn/clone/jre/lib/i386/server/libjvm.so'.
Please install or use the JRE or JDK that contains these missing components.
chmod: cannot access '/hello/d02/fs2/EBSapps/comn/clone/bin/../FMW/tempinfoApps.txt': No such file or directory


Kindly help, its getting on my nerves.

Regards,
Hassan Saeed

[ErmanArslansOracleBlog]

ext4 support upto 1TB -> This is not correct.
But maybe you are on a 32 bit platform, if so then maybe you re right.

And yes, libjvm.so problem in XFS environments right? yeah... Tell me about it...

See ->

https://ermanarslan.blogspot.com/2016/11/ebs-122-problem-installing-ebs-on-xfs.html

This error is caused by the filesystem, that EBS stage and installation directories reside, being XFS.
I wasn't there when the problem was encountered but according to my research, I can say that it is caused by the enhancements that are done in modern XFS filesystems.
The most significant feature that will cause this issue is the 64 bit inodes. Especially when the filesystem size is more than 1 TB, these 64 bit inodes became a problem for 32 bit java.. (You see the above path , I mean the Rapidwiz java path path.. It says i386 there..)

Anyways, a workaround for this problem is to use another fileystem, like ext3 or ext4 on Linux. (tested & verified)

Note that, ext4 also supports 64 bit inodes, but it is off by default. following is from the manual;
i_version ->  Enable 64-bit inode version support. This option is off by default.
Relocating the stage and startCD location to a smaller filesystem(<1tb) can be a workaround too .

SEE HERE -->>>
Also, the mount point (with xfs filesytem) can be unmounted and remounted using "-o inode32" argument. After this move, the stage directory should be recreated in the mount point (recopied to the mount point)  to guarantee all its files are associated with 32 bit inodes...

One final note on this: Use of XFS with Oracle Database is not supported. :)