Hi Teju,
While it's not very common to have a landscape with different OS's on the different application servers such as you describe, it's not unheard-of, and it is supported. I caution you that I have not had to support this setup myself, so this is just my understanding of how applying kernel updates or upgrades in such a heterogeneous environment works.
If you look on your SAPGLOBALHOST system, the one where SAPMNT resides, you'll see a folder structure like this:
\usr
...\sap
......\sys
.........\exe
............\uc (or possibly nuc)
...............\<platform1>
...............\<platform2>
<platform1> and <platform2> should represent your Windows and AIX platforms, respectively. In the case of Windows, it will be \ntadm64. I'm not sure what it will be for AIX.
So, the key will be to copy the binaries for each respective platform into the appropriate folder on the global host. Then the sapcpe process on each local host should take care of copying the platform-specific files to itself appropriately.
However, that is dependent upon the global host's filesystem being compatible with the local hosts. If you're using Windows for your global host, you may need to have SAPMNT mounted as an NFS share, or something like that, so that AIX can access it, and vice versa. If this isn't the case, then you may just have to manually perform the file copies yourself onto each respective platform, i.e. into \ASCS00\exe, \DVEBMGS01\exe, and/or \D00\exe on the respective hosts.
You can find some more details about what goes on under the hood with all this in the blog https://blogs.sap.com/2006/10/03/sap-netweaver-7x-kernel-updates-explained-part-ii/. Unfortunately, the author doesn't seem to have followed up with the heterogeneous update details as he promised in that blog.
And, of course, the master Note for kernel updates is 19466.
Cheers,
Matt
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.